WO2017220021A1 - 短信息处理方法及装置 - Google Patents
短信息处理方法及装置 Download PDFInfo
- Publication number
- WO2017220021A1 WO2017220021A1 PCT/CN2017/089762 CN2017089762W WO2017220021A1 WO 2017220021 A1 WO2017220021 A1 WO 2017220021A1 CN 2017089762 W CN2017089762 W CN 2017089762W WO 2017220021 A1 WO2017220021 A1 WO 2017220021A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service data
- service
- short message
- service node
- data
- Prior art date
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
- the present application relates to the field of communications, for example, to a short message processing method and apparatus.
- the Network Function Virtualization (NFV) architecture carries software for many functions by using general-purpose hardware such as x86 and virtualization technology. Thereby reducing the cost of equipment expensive in the network.
- the hardware and software decoupling and functional abstraction can be used to make the network device function no longer depend on the dedicated hardware.
- the resources can be fully flexibly distributed, realize the rapid development and deployment of new services, and automatically deploy, flexibly, and fault based on actual service requirements. Isolation and self-healing.
- the SMS center cannot adapt to the architecture of the new platform, and cannot fully utilize the advantages of the new platform.
- the traditional short message center usually stores information related to business processing in the service.
- the local memory database of the node the business process directly accesses the local memory.
- the service node elastic scaling operation occurs, local memory information cannot be migrated between nodes and cannot be accessed by other nodes, which will result in information loss or improper processing, and at the same time in the context of today's cloud computing big data.
- Local storage affects business processing capabilities and will have a direct impact on operations in terms of efficiency. Therefore, in the related art, there is no better solution to the problem of poor service processing caused by local memory storage and service-related information, and improper information processing.
- the embodiments of the present disclosure provide a short message processing method and apparatus to solve at least the problem of low service processing capability and improper information processing caused by local memory storage and service related information in the related art.
- a short message processing method including: optionally acquiring access control information of a service node, and service data corresponding to a short message to be processed in the service node; The service data and the access control information are stored to the network side device.
- the method further includes: acquiring the service data from the network side device, and sending the service data to the mobile service node of the service data. .
- the method further includes: changing access control information of the egress service node of the service data and the embedding service node, where the service data is obtained from the network side device;
- the access control information of the migrating service node and the migrating service node is stored in the network side device.
- the access control information includes at least one of the following: a service node identifier, a home subscriber group identifier, and an access state identifier.
- the access status identifier includes one of: supporting a normal state of processing the service data, indicating an unattributed state that does not need to process the service data, a temporary state being moved in, and being moved out. Temporary status.
- the method further includes: storing the changed service data in the network side device, and waiting for resending to carry Transmitting the short message of the service data after the change; when the waiting time reaches the specified time point, sending, to the service node, an indication that the short message carrying the changed service data is re-delivered; When the short message carrying the changed service data is resent, the indication message corresponding to the changed service data is obtained, where the indication message is used to indicate that the update or deletion of the service data is completed. .
- the short message carrying the changed service data is not required to be re-sent: the short message carrying the changed service data is successfully delivered, and the re-request is not required.
- the time when the short message carrying the changed service data is delivered or re-issued is greater than the valid time.
- the service data includes at least one of the following: a short message table corresponding to the to-be-processed message, a short message receiver information table, and a timing queue.
- storing the service data and the access control information to the network side device includes: storing the service data and the access control information into a distributed in-memory database on the network side.
- a short message processing apparatus including: a business office
- the management module is configured to acquire access control information of the service node, and service data corresponding to the short message to be processed in the service node;
- the first storage module is configured to use the service data and the access control information Store to the network side device.
- the device when the service data in the service node is migrated, the device further includes: a first sending module, configured to acquire the service data from the network side device, and send the service data to Move to the business node.
- a first sending module configured to acquire the service data from the network side device, and send the service data to Move to the business node.
- the device further includes: a change module configured to change access control information of the migrated service node and the migrated service node; and a second storage module configured to change the migrated service node and the The access control information of the inbound service node is stored to the network side device.
- a change module configured to change access control information of the migrated service node and the migrated service node
- a second storage module configured to change the migrated service node and the The access control information of the inbound service node is stored to the network side device.
- the device further includes: a third storage module, configured to: when the service node fails to send the to-be-processed short message, store the changed service data to the network side device, And waiting to resend the short message carrying the changed service data; the second sending module is configured to send, when the waiting time reaches the specified time point, the carrying the re-issued carrying change And the obtaining the short message of the service data; the acquiring module is configured to: when the short information carrying the changed service data is not required to be resent, obtain the corresponding service data corresponding to the change The indication message, wherein the indication message is used to indicate that the update is completed or the service data is deleted.
- a third storage module configured to: when the service node fails to send the to-be-processed short message, store the changed service data to the network side device, And waiting to resend the short message carrying the changed service data
- the second sending module is configured to send, when the waiting time reaches the specified time point, the carrying the re-issued carrying change And the
- a storage medium is also provided.
- the storage medium is arranged to store program code for performing the following steps:
- S11 Obtain access control information of the service node, and service data corresponding to the short message to be processed in the service node;
- the storage medium is further configured to store program code for performing the following steps: when the business data in the service node is migrated:
- S21 Obtain the service data from the network side device, and send the service data to the mobile service node.
- the storage medium is further configured to store program code for performing the following steps: when the business data in the service node is migrated:
- the storage medium is further configured to store program code for performing the following steps: when the service node fails to deliver the to-be-processed short message:
- the changed service data is stored in the network side device, and waits to resend the short information that carries the changed service data.
- the storage medium may be a transitory computer readable storage medium or a non-transitory computer readable storage medium.
- An embodiment of the present disclosure further provides an electronic device, including:
- At least one processor At least one processor
- the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the method described above.
- the access control information of the service node and the service data corresponding to the short message to be processed are stored in the network side device, not in the local memory mentioned in the related art. Therefore, the problem of low service processing capability and improper information processing caused by the information related to the service in the local memory storage can be solved, the separation of the service and the data in the short message is realized, and the elastic compression is easy, and the system is improved. Reliability and storage efficiency effects.
- FIG. 1 is a block diagram showing the hardware structure of a computer terminal of a short message processing method according to an embodiment of the present disclosure
- FIG. 2 is a flowchart of a short message processing method according to an embodiment of the present disclosure
- FIG. 3 is a flow chart of another short message processing method in accordance with an embodiment of the present disclosure.
- FIG. 4 is a structural diagram of a short message processing apparatus according to an embodiment of the present disclosure.
- FIG. 5 is a structural diagram of another short message processing apparatus according to an embodiment of the present disclosure.
- FIG. 6 is a structural diagram of still another short message processing apparatus according to an embodiment of the present disclosure.
- FIG. 7 is a structural diagram of still another short message processing apparatus according to an embodiment of the present disclosure.
- FIG. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
- FIG. 1 is a hardware structural block diagram of a computer terminal of a short message processing method according to an embodiment of the present disclosure.
- computer terminal 10 may include one or more (only one shown) processor 102 (processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA)
- processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA)
- a memory 104 configured to store data
- a transmission device 106 configured as a communication function.
- computer terminal 10 may also include more or fewer components than shown in FIG. 1, or have Figure 1 shows the different configurations.
- the memory 104 can be configured as a software program and a module for storing application software, such as program instructions/modules corresponding to the short message processing method in the embodiment of the present disclosure, and the processor 102 executes the software program and the module stored in the memory 104, thereby The above methods are implemented by performing various functional applications and data processing.
- Memory 104 may include high speed random access memory, and may also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
- memory 104 may include memory remotely located relative to processor 102, which may be coupled to computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
- Transmission device 106 is configured to receive or transmit data via a network.
- the network examples described above may include a wireless network provided by a communication provider of computer terminal 10.
- the transmission device 106 includes a Network Interface Controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet.
- the transmission device 106 can be a Radio Frequency (RF) module configured to communicate with the Internet wirelessly.
- NIC Network Interface Controller
- RF Radio Frequency
- FIG. 2 is a flowchart of a short message processing method according to an embodiment of the present disclosure. As shown in FIG. 2, the process includes the following steps. :
- Step S202 acquiring access control information of the service node, and service data corresponding to the short message to be processed in the service node;
- Step S204 Store the service data and the access control information to a network side device.
- the foregoing access control information is information used to indicate a relationship between the service node and the network side device, and includes at least one of the following: a service node identifier, a home subscriber group identifier, and an access state identifier.
- the access status identifier may include: a normal state supporting the processing of the service data, indicating an unattributed state that does not need to process the service data, a temporary state being moved in, and a temporary state being moved out.
- the foregoing service data is information related to the service in the short message, and may include but is not limited to: the to-be-served The short message table corresponding to the message, the short message receiver information table, and the timing queue are processed.
- step S204 may be implemented in the following implementation form: storing the service data and the access control information into a distributed in-memory database on the network side.
- the distributed in-memory database may be a database in a cloud service platform, or may be a large-capacity virtual network disk, but is not limited thereto.
- the access control information of the service node and the service data corresponding to the short message to be processed can also be physically stored, and the backup of the information data can be realized, and the user who is convenient to access can be locally called at any time.
- the service data in the service node is migrated, the service data is obtained from the network side device and sent to the inbound service node of the service data.
- the service node 1 When the service node 1 is unable to process the service data corresponding to the short message to be processed that needs to be processed by the service node 1, the service node 1 at this time searches for the other service node to replace the service node 1 to process the service data, that is, Said that the business data in the business node 1 has migrated. For example, if the service node 2 can process the service data A in the service node 1, and the service node 3 can process the service data B in the service node 1, then at this time, the service node 2 acquires the service data A from the network side device. The service node 3 acquires the service data B from the network side device.
- the service node 1 Since the service node 1 cannot process the service data A and the service data B, and the service node 1 stores the service data A and the service data B in advance in the network side device, the service node 1 will use the service data A and the service data. B delete, so that the business data that cannot be processed occupies memory. Finally, the service node 1 sends the service data B deletion request to the network side device and requests the service data corresponding to the service node 1 in the network side device to perform the deletion operation, and the service node 2 and the service node 3 will move the migrated service data again. Send to the network side device for update.
- the access control information of the migration service node of the service data and the migration service node is changed while the service data is acquired from the network side device; and the changed migration service is changed.
- the access control information of the node and the inbound service node is stored in the network side device.
- the network side device not only stores the service data to be processed by the service node, but also stores the access control information of the service node. Therefore, when the service data in the service node is migrated, the access status identifier in the access control information needs to be performed. migrate.
- Table 1 shows the relationship between the service node and the service data and access status identifier before the migration.
- the service node 1 can process the service data A and the service data D normally before the migration. Therefore, the access status identifier corresponding to the service data A and D is normal at this time.
- Table 2 is a migration status table when the service data A is migrated from the service node 1 to the service node 2.
- the service node 1 when the service node 1 cannot process the service data A and the service data A is moved out, the service node 1 performs the migration of the access state identifier in the order of normal-migrating-non-attributing according to the time axis.
- the service node 2 is the party to which the service data A is moved. Therefore, the service node 2 performs the migration of the access state identifier in the order of non-attribute-in-migration-normal according to the time axis.
- the real-time migration and removal of the service node access status identifier is implemented.
- the immigration means that the service node obtains the service data corresponding to the short message to be processed from the network side device.
- the meaning of being moved out is the process in which the service node sends the service data corresponding to the short message to be processed.
- Table 3 shows the relationship between the service node and the service data and access status identifier after the migration.
- the service node 1 After the migration, the service node 1 cannot process the service data A and D. Therefore, the service data A and D are not attributed to the service node 1, and the service nodes 2 and 3 are respectively moved into the service data A and D, so the corresponding access is performed. The status is marked as normal.
- FIG. 3 is a flow chart of another short message processing method in accordance with an embodiment of the present disclosure. As shown in FIG. 3, on the basis of FIG. 2, the method further includes the following steps: when the service node fails to send the to-be-processed short message:
- the changed service data is stored in the network side device, and waits to resend the short information that carries the changed service data.
- the short message delivery fails, it is necessary to process the short message short message table, the short message receiver information table, and the service data such as the time queue to update or insert new service data, so that the next time the short message is retransmitted Sent successfully.
- the specified time point may be a preset time to resend the short message.
- the short message carrying the changed service data is not required to be re-sent: the short message carrying the changed service data is successfully delivered, and the re-request is not required.
- the short message that carries the changed service data is delivered or re-issued
- the time is greater than the effective time.
- the indication message indicates that the updated service data stored in the network side device does not need to be deleted.
- the indication message instructs the network side device to delete the updated service data, if the resending of the short message carrying the changed service data is longer than the effective time.
- the method according to the foregoing embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware.
- the technical solution of the present disclosure which is essential or contributes to the related art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, CD-ROM).
- the instructions include a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present disclosure.
- a short information processing device is also provided, which is configured to implement the above-mentioned embodiments and implementation manners, and details have been omitted for description.
- the term "module” may implement a combination of software and/or hardware of a predetermined function.
- FIG. 4 is a structural diagram of a short message processing apparatus according to an embodiment of the present disclosure. As shown in FIG. 4, the apparatus includes a service processing module 42 and a first storage module 44.
- the service processing module 42 is configured to acquire service data in the short message to be processed in the service node and invoke the access control information of the service node;
- the first storage module 44 is configured to store the service data and the access control information to a network side device.
- the foregoing access control information may be information for indicating a relationship between the service node and the network side device, and includes at least one of the following: a service node identifier, a home subscriber group identifier, and an access state identifier.
- the access status identifier may include: a normal state supporting the processing of the service data, indicating an unattributed state that does not need to process the service data, a temporary state being moved in, and a temporary state being moved out.
- the foregoing service data is the service-related information stored in the short message, and may include: a short message table corresponding to the to-be-processed message, a short message receiver information table, and a timing queue.
- storing the service data and the access control information to the network side device includes: storing the service data and the access control information into a distributed in-memory database on the network side.
- the distributed in-memory database may be a database in a cloud service platform or a large-capacity virtual network disk.
- the access control information of the service node and the service data corresponding to the short message to be processed can also be physically stored, and the backup of the information data can be realized, and the user who is convenient to access can be locally called at any time.
- FIG. 5 is a structural diagram of another short information processing apparatus according to an embodiment of the present disclosure. As shown in FIG. 5, the apparatus includes a first transmitting module 52 in addition to all the modules shown in FIG.
- the first sending module 52 is configured to acquire the service data from the network side device and send the data to the mobile service node.
- the service node 1 When the service node 1 is unable to process the service data corresponding to the short message to be processed that needs to be processed by the service node 1, the service node 1 at this time searches for the other service node to replace the service node 1 to process the service data, that is, Said that the business data in the business node 1 has migrated. For example, if the service node 2 can process the service data A in the service node 1, and the service node 3 can process the service data B in the service node 1, then at this time, the service node 2 acquires the service data A from the network side device. The service node 3 acquires the service data B from the network side device.
- the service node 1 Since the service node 1 cannot process the service data A and the service data B, and the service node 1 stores the service data A and the service data B in advance in the network side device, the service node 1 will use the service data A and the service data. B delete, so that the business data that cannot be processed occupies memory. Finally, the service node 1 sends the service data B deletion request to the network side device and requests the service data corresponding to the service node 1 in the network side device to perform the deletion operation, and the service node 2 and the service node 3 will move the migrated service data again. Send to the network side device for update.
- FIG. 6 is a structural diagram of still another short message processing apparatus according to an embodiment of the present disclosure. As shown in FIG. 6, when the service node fails to deliver the to-be-processed short message, the apparatus includes the following FIG. In addition to all the modules, the change module 62 and the second storage module 64 are also included.
- the change module 62 is configured to change access control information of the migration service node and the migration service node;
- the second storage module 64 is configured to store the changed access control information of the migrating service node and the migrating service node to the network side device.
- the network side device not only stores the service data to be processed by the service node, but also stores the access control information of the service node. Therefore, when the service data in the service node is migrated, the access status identifier in the access control information needs to be performed. migrate.
- the service node 1 can process the service data A and the service data D normally before the migration. Therefore, the access status identifier corresponding to the service data A and D is normal at this time.
- the service node 1 when the service node 1 cannot process the service data A and the service data A is moved out, the service node 1 performs the migration of the access state identifier in the order of normal-migrating-non-attributing according to the time axis.
- the service node 2 is the party to which the service data A is moved. Therefore, the service node 2 performs the migration of the access state identifier in the order of non-attribute-in-migration-normal according to the time axis.
- the real-time migration and removal of the service node access status identifier is implemented.
- the immigration means that the service node obtains the service data corresponding to the short message to be processed from the network side device.
- the meaning of being moved out is that the business node will
- the service node 1 cannot process the service data A and D. Therefore, the service data A and D are not attributed to the service node 1, and the service nodes 2 and 3 are respectively moved into the service data A and D. Therefore, the corresponding access status is identified as normal.
- FIG. 7 is a structural diagram of a short message processing apparatus according to an embodiment of the present disclosure. As shown in FIG. 7, the apparatus includes, in addition to all the modules shown in FIG. 4, a third storage module 72, and a second transmission. Module 74 and acquisition module 76.
- the third storage module 72 is configured to store the changed service data in the network side device, and wait to resend the short information that carries the changed service data;
- the short message short message table, the short message receiver information table, and the service data such as the timing queue need to be updated or inserted to enable the short message to succeed in the next retransmission.
- the second sending module 74 is configured to: when the waiting time reaches the specified time point, send an indication to the service node that the short message carrying the changed service data is re-delivered;
- the preset threshold may be the time at which the short message is resent.
- the obtaining module 76 is configured to: when the short message carrying the changed service data is not required to be resent, obtain the indication message corresponding to the changed service data, where the indication message is used by Instructing to complete the update or delete the business data.
- the indication message may indicate that the updated service data stored in the network side device does not need to be deleted.
- the indication message instructs the network side device to delete the updated service data, if the resending of the short message carrying the changed service data is longer than the effective time.
- each of the above modules may be implemented by software or hardware.
- the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
- the forms are located in different processors.
- Embodiments of the present disclosure also provide a storage medium, which may be a transitory computer readable storage medium or a non-transitory computer readable storage medium.
- a storage medium may be configured to store program code for performing the following steps:
- S11 Obtain access control information of the service node, and service data corresponding to the short message to be processed in the service node;
- the storage medium is further configured to store program code for performing the following steps: when the business data in the service node is migrated:
- S21 Obtain the service data from the network side device, and send the service data to the inbound service node of the service data.
- the storage medium is further configured to store program code for performing the following steps: when the business data in the service node is migrated:
- the storage medium is further configured to store program code for performing the following steps: when the service node fails to deliver the to-be-processed short message:
- the changed service data is stored in the network side device, and waits to resend the short information that carries the changed service data.
- the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
- ROM Read-Only Memory
- RAM Random Access Memory
- a mobile hard disk e.g., a hard disk
- magnetic memory e.g., a hard disk
- the embodiment of the present disclosure further provides a schematic structural diagram of an electronic device.
- the electronic device includes:
- At least one processor 80 which is exemplified by a processor 80 in FIG. 8; and a memory 81, may further include a communication interface 82 and a bus 83.
- the processor 80, the communication interface 82, and the memory 81 can complete communication with each other through the bus 83.
- Communication interface 82 can be used for information transfer.
- Processor 80 can invoke logic instructions in memory 81 to perform the methods of the above-described embodiments.
- logic instructions in the memory 81 described above can be implemented in the form of software functional units and When sold or used as a stand-alone product, it can be stored on a computer readable storage medium.
- the memory 81 is used as a computer readable storage medium for storing software programs, computer executable programs, and program instructions/modules corresponding to the methods in the embodiments of the present disclosure.
- the processor 80 executes the function application and the data processing by executing the software programs, the instructions, and the modules stored in the memory 81, that is, the short message processing method in the above method embodiments.
- the memory 81 may include a storage program area and an storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to use of the terminal device, and the like. Further, the memory 81 may include a high speed random access memory, and may also include a nonvolatile memory.
- the technical solution of the embodiments of the present disclosure may be embodied in the form of a software product stored in a storage medium, including one or more instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in the embodiments of the present disclosure.
- the foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like.
- modules or steps of the present disclosure described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
- the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. As such, the disclosure is not limited to any specific combination of hardware and software.
- the short message processing method and device provided by the present application solves the problem of low service processing capability and improper information processing caused by local memory storage and service-related information, and realizes separation of service and data in short information, and is easy to be elastically compressed. At the same time, it has also improved the reliability and storage efficiency of the system.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
本申请提供了一种短信息处理方法及装置，其中，该方法包括：获取业务节点的访问控制信息，以及与所述业务节点中与待处理短消息对应的业务数据；将所述业务数据以及所述访问控制信息存储至网络侧设备。通过本申请，解决了通过本地内存存储与业务相关的信息所引起的业务处理能力低下，信息处理不当的问题，实现了短信息中业务与数据的分离，易于弹性压缩，同时还达到了提高了系统的可靠性以及存储效率效果。
Description
本申请涉及通信领域，例如涉及一种短信息处理方法及装置。
网络功能虚拟化(Network Function Virtualization，简称为NFV)架构通过使用x86等通用性硬件以及虚拟化技术，来承载很多功能的软件处理。从而降低网络昂贵的设备成本。可以通过软硬件解耦及功能抽象，使网络设备功能不再依赖于专用硬件，资源可以充分灵活分布式，实现新业务的快速开发和部署，并基于实际业务需求进行自动部署、弹性伸缩、故障隔离和自愈等。
随着电信领域云化NFV平台架构的建设，短信中心不能适应新平台的架构，不能充分发挥新平台的优势，例如在数据存储方面，传统短消息中心通常将与业务处理相关的信息存储在业务节点的本地内存数据库，业务处理直接访问本地内存。在NFV架构下，当发生业务节点弹性伸缩操作时，本地内存信息无法在节点间迁移，不能被其它节点访问，这将会造成信息遗失或者被不当处理，同时，在当今云计算大数据的背景下，本地存储影响业务处理能力，在效率方面也将给运营带来直接影响。因此，针对相关技术中，通过本地内存存储与业务相关的信息所引起的业务处理能力低下，信息处理不当的问题，还没有一种比较好的解决方法。
发明内容
本公开实施例提供了一种短信息处理方法及装置，以至少解决相关技术中通过本地内存存储与业务相关的信息所引起的业务处理能力低下，信息处理不当的问题。
根据本公开的一个实施例，提供了一种短信息处理方法，包括：可选地，获取业务节点的访问控制信息，以及与所述业务节点中与待处理短消息对应的业务数据；将所述业务数据以及所述访问控制信息存储至网络侧设备。
可选地，当所述业务节点中的所述业务数据发生迁移时，所述方法还包括：从所述网络侧设备中获取所述业务数据，并发送给所述业务数据的迁入业务节点。
可选地，从所述网络侧设备中获取所述业务数据的同时，所述方法还包括：改变所述业务数据的迁出业务节点与所述迁入业务节点的访问控制信息；将改变后的所述迁出业务节点与所述迁入业务节点的访问控制信息存储于所述网络侧设备当中。
可选地，所述访问控制信息包括以下至少之一：业务节点标识，归属用户组标识以及访问状态标识。
可选地，所述访问状态标识包括以下之一：支持处理所述业务数据的正常状态，用于指示不需要处理所述业务数据的不归属状态，正在迁入的临时状态以及正在迁出的临时状态。
可选地，当所述业务节点下发所述待处理短消息失败时，所述方法还包括：将变更后的所述业务数据存储于所述网络侧设备当中，并等待重新发送携带有所述变更后的所述业务数据的短信息；当等待时间到达指定时间点时，向所述业务节点发送携带有重新下发携带有变更后的所述业务数据的短信息的指示；当不需要重新发送所述携带有变更后的所述业务数据的短信息时，获取所述变更后的所述业务数据对应的指示消息，其中，所述指示消息用于指示完成更新或者删除所述业务数据。
可选地，在以下情况下确定不需要重新发送所述携带有变更后的所述业务数据的短信息：重新下发携带有变更后的所述业务数据的短信息成功，不需要再次进行重新下发，或者重新下发携带有变更后的所述业务数据的短信息的时间大于有效时间。
可选地，所述业务数据至少包括以下其中之一：所述待处理消息对应的短消息表，短信息接收方信息表以及定时队列。
可选地，将所述业务数据以及所述访问控制信息存储至网络侧设备，包括：将所述业务数据以及所述访问控制信息存储至网络侧的分布式内存数据库中。
根据本公开的另一个实施例，提供了一种短信息处理装置，包括：业务处
理模块，被配置为获取业务节点的访问控制信息，以及与所述业务节点中与待处理短消息对应的业务数据；第一存储模块，被配置为将所述业务数据以及所述访问控制信息存储至网络侧设备。
可选地，当所述业务节点中的所述业务数据发生迁移时，所述装置还包括：第一发送模块，被配置为从所述网络侧设备中获取所述业务数据，并发送给所述迁入业务节点。
可选地，所述装置还包括：改变模块，被配置为改变迁出业务节点与迁入业务节点的访问控制信息；第二存储模块，被配置为将改变后的所述迁出业务节点与所述迁入业务节点的访问控制信息存储至所述网络侧设备。
可选地，所述装置还包括：第三存储模块，被配置为在所述业务节点下发所述待处理短消息失败时，将变更后的所述业务数据存储至所述网络侧设备，并等待重新发送携带有所述变更后的所述业务数据的短信息；第二发送模块，被配置为在等待时间到达指定时间点时时，向所述业务节点发送携带有重新下发携带有变更后的所述业务数据的短信息的指示；获取模块，被配置为在不需要重新发送所述携带有变更后的所述业务数据的短信息时，获取所述变更后的所述业务数据对应的指示消息，其中，所述指示消息用于指示完成更新或者删除所述业务数据。
根据本公开的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：
S11，获取业务节点的访问控制信息，以及与所述业务节点中与待处理短消息对应的业务数据；
S12，将所述业务数据以及所述访问控制信息存储至网络侧设备。
可选地，存储介质还设置为存储用于执行以下步骤的程序代码：当所述业务节点中的所述业务数据发生迁移时：
S21，从所述网络侧设备中获取所述业务数据，并发送给所述迁入业务节点；
可选地，存储介质还设置为存储用于执行以下步骤的程序代码：当所述业务节点中的所述业务数据发生迁移时：
S31，改变所述业务数据的迁出业务节点与所述迁入业务节点的访问控制信
息；
S32，将改变后的所述迁出业务节点与所述迁入业务节点的访问控制信息存储于所述网络侧设备当中。
可选地，存储介质还设置为存储用于执行以下步骤的程序代码：当所述业务节点下发所述待处理短消息失败时：
S41，将变更后的所述业务数据存储于所述网络侧设备当中，并等待重新发送携带有所述变更后的所述业务数据的短信息；
S42，当等待时间到达指定时间点时，向所述业务节点发送携带有重新下发携带有变更后的所述业务数据的短信息的指示；
S43，当不需要重新发送所述携带有变更后的所述业务数据的短信息时，获取所述变更后的所述业务数据对应的指示消息，其中，所述指示消息用于指示完成更新或者删除所述业务数据。
所述存储介质可以是暂态计算机可读存储介质，也可以是非暂态计算机可读存储介质。
本公开实施例还提供了一种电子设备，包括：
至少一个处理器；以及
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器执行上述的方法。
通过本公开，由于将业务节点的访问控制信息以及待处理短消息对应的业务数据存储在网络侧设备当中，而非相关技术所提及的本地内存当中。因此，可以解决通过本地内存存储与业务相关的信息所引起的业务处理能力低下，信息处理不当的问题，实现了短信息中业务与数据的分离，易于弹性压缩，同时还达到了提高了系统的可靠性以及存储效率效果。
附图概述
此处所说明的附图用来提供对本公开的理解，构成本申请的一部分，本公
开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是本公开实施例的一种短信息处理方法的计算机终端的硬件结构框图；
图2是根据本公开实施例的一种短信息处理方法的流程图；
图3是根据本公开实施例中的另一种短信息处理方法的流程图；
图4是根据本公开实施例的一种短信息处理装置的结构图；
图5是根据本公开实施例的另一种短信息处理装置的结构图；
图6是根据本公开实施例的又一种短信息处理装置的结构图；
图7是根据本公开实施例的再一种短信息处理装置的结构图；以及
图8是根据本公开实施例的电子设备的结构示意图。
下文中将参考附图并结合实施例来详细说明本公开。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本申请实施例一所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在计算机终端上为例，图1是本公开实施例的一种短信息处理方法的计算机终端的硬件结构框图。如图1所示，计算机终端10可以包括一个或多个(图中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)、被配置为存储数据的存储器104、以及被配置为通信功能的传输装置106。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述电子装置的结构造成限定。例如，计算机终端10还可包括比图1中所示更多或者更少的组件，或者具有与
图1所示不同的配置。
存储器104可被配置为存储应用软件的软件程序以及模块，如本公开实施例中的短信息处理方法对应的程序指令/模块，处理器102通过运行存储在存储器104内的软件程序以及模块，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至计算机终端10。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106被配置为经由一个网络接收或者发送数据。上述的网络实例可包括计算机终端10的通信供应商提供的无线网络。在一个实例中，传输装置106包括一个网络适配器(Network Interface Controller，NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置106可以为射频(Radio Frequency，RF)模块，其被配置为通过无线方式与互联网进行通讯。
在本实施例中提供了一种运行于上述计算机终端的短信息处理方法，图2是根据本公开实施例的一种短信息处理方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，获取业务节点的访问控制信息，以及与所述业务节点中与待处理短消息对应的业务数据；
步骤S204，将所述业务数据以及所述访问控制信息存储至网络侧设备。
可选地，上述访问控制信息为用于指示业务节点与网络侧设备之间关系的信息，至少包括以下其中之一：业务节点标识，归属用户组标识以及访问状态标识。
访问状态标识可以包括：支持处理所述业务数据的正常状态，用于指示不需要处理所述业务数据的不归属状态，正在迁入的临时状态以及正在迁出的临时状态。
上述业务数据为短信息中与业务相关的信息，可以包括但不限于：所述待
处理消息对应的短消息表，短信息接收方信息表以及定时队列。
可选地，步骤S204可以表现为以下实现形式：将所述业务数据以及所述访问控制信息存储至网络侧的分布式内存数据库中。其中，该分布式内存数据库可以是云服务平台中的数据库，也可以是大容量的虚拟网盘等，但不限于此。
在本实施中，业务节点的访问控制信息以及与待处理短消息对应的业务数据同样也可以进行物理存储，能够实现对上述信息数据的备份，同时还便于访问的用户能够随时在本地调用。
可选地，在当所述业务节点中的所述业务数据发生迁移时，从所述网络侧设备中获取所述业务数据，并发送给所述业务数据的迁入业务节点。
由于业务节点1由于本身原因导致需要其处理的待处理短消息对应的业务数据不能够进行处理时，此时的业务节点1会寻找其他业务节点替代业务节点1对该业务数据进行处理，也就是说，业务节点1中的业务数据发生迁移。例如，如果业务节点2能够处理业务节点1中的业务数据A，业务节点3能够处理业务节点1中的业务数据B的话，那么此时，业务节点2就会从网络侧设备当中获取业务数据A，而业务节点3就会从网络侧设备当中获取业务数据B。而由于业务节点1无法处理业务数据A以及业务数据B，同时由于业务节点1将业务数据A以及业务数据B事先存储在网络侧设备当中，因此，业务节点1就会将业务数据A以及业务数据B删除，以免无法处理的业务数据占用内存。最后，业务节点1向网路侧设备发送业务数据B的删除请求并请求网络侧设备中业务节点1对应的业务数据进行删除操作，而业务节点2以及业务节点3会将迁入的业务数据再次发送至网络侧设备进行更新。
可选地，从所述网络侧设备中获取所述业务数据的同时，改变所述业务数据的迁出业务节点与所述迁入业务节点的访问控制信息；将改变后的所述迁出业务节点与所述迁入业务节点的访问控制信息存储于所述网络侧设备当中。
由于网络侧设备不仅仅存储了业务节点待处理的业务数据，同时还存储了业务节点的访问控制信息，因此，在业务节点当中的业务数据发生迁移时，需要对访问控制信息中访问状态标识进行迁移。
表1是未迁移前，业务节点与业务数据和访问状态标识对应的关系。
如表1所示，在未迁移前业务节点1能够正常处理业务数据A以及业务数据D。因此，此时业务数据A、D对应的访问状态标识为正常。
表2是业务数据A在从业务节点1迁移到业务节点2时的迁移状态表。
如表2所示，业务节点1无法处理业务数据A并将业务数据A迁出时，业务节点1根据时间轴按照正常-正在迁出-不归属的顺序进行访问状态标识的迁移。而业务节点2是业务数据A迁入的一方，因此，业务节点2根据时间轴按照不归属-正在迁入-正常的顺序进行访问状态标识的迁移。根据表2，实现了对业务节点访问状态标识的实时迁入与迁出。
需要指出的是，业务节点1将业务数据D迁移至业务节点3也同样适用于表2中记载的迁移顺序。
需要指出的是，正在迁入的含义为，业务节点从网络侧设备当中获取待处理短消息对应的业务数据的过程。正在迁出的含义为，业务节点发送待处理短消息对应的业务数据的过程。
表3是迁移后，业务节点与业务数据和访问状态标识对应的关系。
在迁移后业务节点1由于无法处理业务数据A、D，因此，业务数据A、D不归属业务节点1，而由于业务节点2、3分别迁入了业务数据A、D，因此，对应的访问状态标识为正常。
通过上述实施例中记载的内容，可以实现不同业务节点之间业务数据的实时迁移。
图3是根据本公开实施例中的另一种短信息处理方法的流程图。如图3所示，在图2的基础之上，还包括以下步骤：当所述业务节点下发所述待处理短消息失败时：
S302，将变更后的所述业务数据存储于所述网络侧设备当中，并等待重新发送携带有所述变更后的所述业务数据的短信息；
由于短信息下发失败，因此，需要对待处理短信息短消息表，短信息接收方信息表以及定时队列等业务数据进行更新或者插入新的业务数据，以使在下一次的重发短信息时能够发送成功。
S304，当等待时间达到指定时间点时，向所述业务节点发送携带有重新下发携带有变更后的所述业务数据的短信息的指示；
该指定时间点可以是预先设置的重新发送短信息的时刻。
S306，当不需要重新发送所述携带有变更后的所述业务数据的短信息时，获取所述变更后的所述业务数据对应的指示消息，其中，所述指示消息用于指示完成更新或者删除所述业务数据。
可选地，在以下情况下确定不需要重新发送所述携带有变更后的所述业务数据的短信息：重新下发携带有变更后的所述业务数据的短信息成功，不需要再次进行重新下发，或者重新下发携带有变更后的所述业务数据的短信息的时
间大于有效时间。
所述指示消息在重新下发成功时，指示网络侧设备中存储的更新后的业务数据不需要进行删除。而如果在不需要再次进行重新下发，或者重新下发携带有变更后的所述业务数据的短信息的时间大于有效时间时，所述指示消息指示网络侧设备删除更新的业务数据。
通过上述步骤，通过本地内存存储与业务相关的信息所引起的业务处理能力低下，信息处理不当的问题，实现了短信息中业务与数据的分离，易于弹性压缩，同时还达到了提高了系统的可靠性以及存储效率的效果。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件实现。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法。
实施例2
在本实施例中还提供了一种短信息处理装置，该装置被配置为实现上述实施例及实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图4是根据本公开实施例的一种短信息处理装置的结构图，如图4所示，该装置包括：业务处理模块42以及第一存储模块44。
业务处理模块42，被配置为获取业务节点中待处理短消息中的业务数据并调用所述业务节点的访问控制信息；
第一存储模块44，被配置为将所述业务数据以及所述访问控制信息存储至网络侧设备。
上述访问控制信息可以为用于指示业务节点与网络侧设备之间关系的信息，至少包括以下其中之一：业务节点标识，归属用户组标识以及访问状态标识。
访问状态标识可以包括：支持处理所述业务数据的正常状态，用于指示不需要处理所述业务数据的不归属状态，正在迁入的临时状态以及正在迁出的临时状态。
上述业务数据为短信息中存储的与业务相关的信息，可以包括：所述待处理消息对应的短消息表，短信息接收方信息表以及定时队列。
可选地，将所述业务数据以及所述访问控制信息存储至网络侧设备，包括：将所述业务数据以及所述访问控制信息存储至网络侧的分布式内存数据库中。
上述分布式内存数据库可以是云服务平台中的数据库，也可以是大容量的虚拟网盘。
在本实施中，业务节点的访问控制信息以及与待处理短消息对应的业务数据同样也可以进行物理存储，能够实现对上述信息数据的备份，同时还便于访问的用户能够随时在本地调用。
图5是根据本公开实施例的另一种短信息处理装置的结构图，如图5所示，该装置除包括图4所示的所有模块外，还包括：第一发送模块52。
第一发送模块52，被配置为从所述网络侧设备中获取所述业务数据，并发送给所述迁入业务节点。
由于业务节点1由于本身原因导致需要其处理的待处理短消息对应的业务数据不能够进行处理时，此时的业务节点1会寻找其他业务节点替代业务节点1对该业务数据进行处理，也就是说，业务节点1中的业务数据发生迁移。例如，如果业务节点2能够处理业务节点1中的业务数据A，业务节点3能够处理业务节点1中的业务数据B的话，那么此时，业务节点2就会从网络侧设备当中获取业务数据A，而业务节点3就会从网络侧设备当中获取业务数据B。而由于业务节点1无法处理业务数据A以及业务数据B，同时由于业务节点1将业务数据A以及业务数据B事先存储在网络侧设备当中，因此，业务节点1就会将业务数据A以及业务数据B删除，以免无法处理的业务数据占用内存。最后，业务节点1向网路侧设备发送业务数据B的删除请求并请求网络侧设备中业务节点1对应的业务数据进行删除操作，而业务节点2以及业务节点3会将迁入的业务数据再次发送至网络侧设备进行更新。
图6是根据本公开实施例的又一种短信息处理装置的结构图，如图6所示，当所述业务节点下发所述待处理短消息失败时，该装置除包括图5所示的所有模块外，还包括：改变模块62以及第二存储模块64。
改变模块62，被配置为改变迁出业务节点与迁入业务节点的访问控制信息；
第二存储模块64，被配置为将改变后的所述迁出业务节点与所述迁入业务节点的访问控制信息存储至所述网络侧设备。
由于网络侧设备不仅仅存储了业务节点待处理的业务数据，同时还存储了业务节点的访问控制信息，因此，在业务节点当中的业务数据发生迁移时，需要对访问控制信息中访问状态标识进行迁移。
如表1所示，在未迁移前业务节点1能够正常处理业务数据A以及业务数据D。因此，此时业务数据A、D对应的访问状态标识为正常。
如表2所示，业务节点1无法处理业务数据A并将业务数据A迁出时，业务节点1根据时间轴按照正常-正在迁出-不归属的顺序进行访问状态标识的迁移。而业务节点2是业务数据A迁入的一方，因此，业务节点2根据时间轴按照不归属-正在迁入-正常的顺序进行访问状态标识的迁移。根据表2，实现了对业务节点访问状态标识的实时迁入与迁出。
需要指出的是，业务节点1将业务数据D迁移至业务节点3也同样适用于表2中记载的迁移顺序。
需要指出的是，正在迁入的含义为，业务节点从网络侧设备当中获取待处理短消息对应的业务数据的过程。正在迁出的含义为，业务节点将
如表3所示，在迁移后业务节点1由于无法处理业务数据A、D，因此，业务数据A、D不归属业务节点1，而由于业务节点2、3分别迁入了业务数据A、D，因此，对应的访问状态标识为正常。
图7是根据本公开实施例的一种短信息处理装置的结构图，如图7所示，该装置除包括图4所示的所有模块外，还包括：第三存储模块72、第二发送模块74以及获取模块76。
第三存储模块72，被配置为将变更后的所述业务数据存储于所述网络侧设备当中，并等待重新发送携带有所述变更后的所述业务数据的短信息；
由于短信息下发失败，因此，需要对待处理短信息短消息表，短信息接收方信息表以及定时队列等业务数据进行更新或者插入，以使能短信息在下一次的重发时成功。
第二发送模块74，被配置为当等待时间达到指定时间点时，向所述业务节点发送携带有重新下发携带有变更后的所述业务数据的短信息的指示；
该预设阈值可以是重新发送短信息的时刻。
获取模块76，被配置为当不需要重新发送所述携带有变更后的所述业务数据的短信息时，获取所述变更后的所述业务数据对应的指示消息，其中，所述指示消息用于指示完成更新或者删除所述业务数据。
所述指示消息在重新下发成功时，可以指示网络侧设备中存储的更新后的业务数据不需要进行删除。而如果在不需要再次进行重新下发，或者重新下发携带有变更后的所述业务数据的短信息的时间大于有效时间时，所述指示消息指示网络侧设备删除更新的业务数据。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本公开的实施例还提供了一种存储介质，该存储介质可以是暂态计算机可读存储介质，也可以是非暂态计算机可读存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S11，获取业务节点的访问控制信息，以及与所述业务节点中与待处理短消息对应的业务数据；
S12，将所述业务数据以及所述访问控制信息存储至网络侧设备。
可选地，存储介质还设置为存储用于执行以下步骤的程序代码：当所述业务节点中的所述业务数据发生迁移时：
S21，从所述网络侧设备中获取所述业务数据，并发送给所述业务数据的迁入业务节点；
可选地，存储介质还设置为存储用于执行以下步骤的程序代码：当所述业务节点中的所述业务数据发生迁移时：
S31，改变所述业务数据的迁出业务节点与所述迁入业务节点的访问控制信息；
S32，将改变后的所述迁出业务节点与所述迁入业务节点的访问控制信息存储于所述网络侧设备当中。
可选地，存储介质还设置为存储用于执行以下步骤的程序代码：当所述业务节点下发所述待处理短消息失败时：
S41，将变更后的所述业务数据存储于所述网络侧设备当中，并等待重新发送携带有所述变更后的所述业务数据的短信息；
S42，当等待时间达到指定时间点时，向所述业务节点发送携带有重新下发携带有变更后的所述业务数据的短信息的指示；
S43，当不需要重新发送所述携带有变更后的所述业务数据的短信息时，获取所述变更后的所述业务数据对应的指示消息，其中，所述指示消息用于指示完成更新或者删除所述业务数据。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本公开实施例还提供了一种电子设备的结构示意图。参见图8，该电子设备包括：
至少一个处理器(processor)80，图8中以一个处理器80为例；和存储器(memory)81，还可以包括通信接口(Communications Interface)82和总线83。其中，处理器80、通信接口82、存储器81可以通过总线83完成相互间的通信。通信接口82可以用于信息传输。处理器80可以调用存储器81中的逻辑指令，以执行上述实施例的方法。
此外，上述的存储器81中的逻辑指令可以通过软件功能单元的形式实现并
作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。
存储器81作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序，如本公开实施例中的方法对应的程序指令/模块。处理器80通过运行存储在存储器81中的软件程序、指令以及模块，从而执行功能应用以及数据处理，即实现上述方法实施例中的短信息处理方法。
存储器81可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据终端设备的使用所创建的数据等。此外，存储器81可以包括高速随机存取存储器，还可以包括非易失性存储器。
本公开实施例的技术方案可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括一个或多个指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开实施例所述方法的全部或部分步骤。而前述的存储介质可以是非暂态存储介质，包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等多种可以存储程序代码的介质，也可以是暂态存储介质。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开实施例的范围之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。
本申请提供的短信息处理方法及装置，解决了通过本地内存存储与业务相关的信息所引起的业务处理能力低下，信息处理不当的问题，实现了短信息中业务与数据的分离，易于弹性压缩，同时还达到了提高了系统的可靠性以及存储效率效果。
Claims (14)
- 一种短信息处理方法，包括：获取业务节点的访问控制信息，以及与所述业务节点中与待处理短消息对应的业务数据；将所述业务数据以及所述访问控制信息存储至网络侧设备。
- 根据权利要求1所述的方法，其中，当所述业务节点中的所述业务数据发生迁移时，所述方法还包括：从所述网络侧设备中获取所述业务数据，并发送给所述业务数据的迁入业务节点。
- 根据权利要求2所述的方法，其中，从所述网络侧设备中获取所述业务数据的同时，所述方法还包括：改变所述业务数据的迁出业务节点与所述迁入业务节点的访问控制信息；将改变后的所述迁出业务节点与所述迁入业务节点的访问控制信息存储于所述网络侧设备当中。
- 根据权利要求1所述的方法，其中，所述访问控制信息包括以下至少之一：业务节点标识，归属用户组标识以及访问状态标识。
- 根据权利要求4所述的方法，其中，所述访问状态标识包括以下之一：支持处理所述业务数据的正常状态，用于指示不需要处理所述业务数据的不归属状态，正在迁入的临时状态以及正在迁出的临时状态。
- 根据权利要求1所述的方法，其中，当所述业务节点下发所述待处理短消息失败时，所述方法还包括：将变更后的所述业务数据存储于所述网络侧设备当中，并等待重新发送携 带有所述变更后的所述业务数据的短信息；当等待时间到达指定时间点时，向所述业务节点发送携带有重新下发携带有变更后的所述业务数据的短信息的指示；当不需要重新发送所述携带有变更后的所述业务数据的短信息时，获取所述变更后的所述业务数据对应的指示消息，其中，所述指示消息用于指示完成更新或者删除所述业务数据。
- 根据权利要求6所述的方法，其中，在以下情况下确定不需要重新发送所述携带有变更后的所述业务数据的短信息：重新下发携带有变更后的所述业务数据的短信息成功，不需要再次进行重新下发，或者重新下发携带有变更后的所述业务数据的短信息的时间大于有效时间。
- 根据权利要求1所述的方法，其中，所述业务数据至少包括以下其中之一：所述待处理消息对应的短消息表，短信息接收方信息表以及定时队列。
- 根据权利要求1所述的方法，其中，将所述业务数据以及所述访问控制信息存储至网络侧设备，包括：将所述业务数据以及所述访问控制信息存储至网络侧的分布式内存数据库中。
- 一种短信息处理装置，包括：业务处理模块，被配置为获取业务节点中待处理短消息中的业务数据并调用所述业务节点的访问控制信息；第一存储模块，被配置为将所述业务数据以及所述访问控制信息存储至网络侧设备。
- 根据权利要求10所述的装置，其中，当所述业务节点中的所述业务数据发生迁移时，所述装置还包括：第一发送模块，被配置为从所述网络侧设备中获取所述业务数据，并发送给所述迁入业务节点。
- 根据权利要求11所述的装置，还包括：改变模块，被配置为改变迁出业务节点与迁入业务节点的访问控制信息；第二存储模块，被配置为将改变后的所述迁出业务节点与所述迁入业务节点的访问控制信息存储至所述网络侧设备。
- 根据权利要求10所述的装置，还包括：第三存储模块，被配置为在所述业务节点下发所述待处理短消息失败时，将变更后的所述业务数据存储至所述网络侧设备，并等待重新发送携带有所述变更后的所述业务数据的短信息；第二发送模块，被配置为在等待时间满足预设阈值时，向所述业务节点发送携带有重新下发携带有变更后的所述业务数据的短信息的指示；获取模块，被配置为在不需要重新发送所述携带有变更后的所述业务数据的短信息时，获取所述变更后的所述业务数据对应的指示消息，其中，所述指示消息用于指示完成更新或者删除所述业务数据。
- 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行权利要求1-9中任一项的方法。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610466225.5 | 2016-06-23 | ||
| CN201610466225.5A CN107548038A (zh) | 2016-06-23 | 2016-06-23 | 短信息处理方法及装置 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2017220021A1 true WO2017220021A1 (zh) | 2017-12-28 |
Family
ID=60784290
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2017/089762 WO2017220021A1 (zh) | 2016-06-23 | 2017-06-23 | 短信息处理方法及装置 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107548038A (zh) |
| WO (1) | WO2017220021A1 (zh) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112632033A (zh) * | 2020-12-16 | 2021-04-09 | 深圳前海微众银行股份有限公司 | 集群数据迁移方法、装置及电子设备 |
| CN112738742A (zh) * | 2020-12-15 | 2021-04-30 | 平安普惠企业管理有限公司 | 与用户通信的方法、装置、电子设备及介质 |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111796950B (zh) * | 2020-07-16 | 2023-06-30 | 网易（杭州）网络有限公司 | 数据处理方法和系统 |
| CN113542013B (zh) * | 2021-06-24 | 2023-04-07 | 新华三大数据技术有限公司 | 虚拟化网络功能管理消息分配方法、装置及设备 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2001058186A1 (en) * | 2000-02-01 | 2001-08-09 | Markport Limited | A messaging applications router |
| CN1859606A (zh) * | 2005-07-24 | 2006-11-08 | 华为技术有限公司 | 一种分流短消息的方法及其系统 |
| CN101068382A (zh) * | 2007-06-13 | 2007-11-07 | 中兴通讯股份有限公司 | 一种短消息中心容灾分流的处理系统和方法 |
| CN102075884A (zh) * | 2009-11-20 | 2011-05-25 | 中国移动通信集团山东有限公司 | 一种将短消息进行网络存储和查询的系统和方法 |
-
2016
- 2016-06-23 CN CN201610466225.5A patent/CN107548038A/zh active Pending
-
2017
- 2017-06-23 WO PCT/CN2017/089762 patent/WO2017220021A1/zh active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2001058186A1 (en) * | 2000-02-01 | 2001-08-09 | Markport Limited | A messaging applications router |
| CN1859606A (zh) * | 2005-07-24 | 2006-11-08 | 华为技术有限公司 | 一种分流短消息的方法及其系统 |
| CN101068382A (zh) * | 2007-06-13 | 2007-11-07 | 中兴通讯股份有限公司 | 一种短消息中心容灾分流的处理系统和方法 |
| CN102075884A (zh) * | 2009-11-20 | 2011-05-25 | 中国移动通信集团山东有限公司 | 一种将短消息进行网络存储和查询的系统和方法 |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112738742A (zh) * | 2020-12-15 | 2021-04-30 | 平安普惠企业管理有限公司 | 与用户通信的方法、装置、电子设备及介质 |
| CN112738742B (zh) * | 2020-12-15 | 2022-11-18 | 平安普惠企业管理有限公司 | 与用户通信的方法、装置、电子设备及介质 |
| CN112632033A (zh) * | 2020-12-16 | 2021-04-09 | 深圳前海微众银行股份有限公司 | 集群数据迁移方法、装置及电子设备 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107548038A (zh) | 2018-01-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7401575B2 (ja) | 通信方法、アクセスネットワークデバイス、およびコアネットワークデバイス | |
| CN110167051B (zh) | 集中式单元-分布式单元架构下的通信方法、通信设备 | |
| EP4247057A2 (en) | Session processing method and related device | |
| WO2019007345A1 (zh) | 网络切片的选择方法、装置及系统、存储介质 | |
| US11140737B2 (en) | Session processing method in wireless communications and terminal device | |
| WO2021223335A1 (zh) | 应用程序的路由选择方法及相关装置 | |
| WO2017220021A1 (zh) | 短信息处理方法及装置 | |
| CN111083690B (zh) | 用户面功能实体信息的上报方法及装置 | |
| CN110650029B (zh) | 一种配置方法及装置 | |
| US11497071B2 (en) | Association handling method and device | |
| CN105282803A (zh) | 通讯接口和基于通讯接口的信息传递方法及系统 | |
| WO2020042848A1 (zh) | 一种网络切片管理方法及装置 | |
| WO2019173951A1 (zh) | 一种ue策略的更新方法及装置、计算机存储介质 | |
| WO2019196963A1 (zh) | 接入网络切片的方法及装置、存储介质、电子装置 | |
| CN107105501A (zh) | 一种基于网络分片的寻呼方法、装置和系统 | |
| CN103200620B (zh) | 一种lte系统中接入核心网的方法及装置 | |
| CN109803333B (zh) | 偶联重定向方法及装置 | |
| WO2022041854A1 (zh) | 一种通信方法及通信装置 | |
| WO2016177135A1 (zh) | 资源管理方法、装置及控制终端 | |
| CN104660506A (zh) | 一种数据包转发的方法、装置及系统 | |
| US9742927B2 (en) | Online charging method for always on IP connectivity | |
| CN109150606B (zh) | 数据处理方法及设备 | |
| US10003657B2 (en) | Data transmission processing method and apparatus | |
| CN115517005B (zh) | 用于优化用户设备和网络之间的pdn同步的系统和方法 | |
| JP7303402B1 (ja) | ネットワークスライスを制御するための方法、情報処理装置およびシステム |
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: 17814759 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: 17814759 Country of ref document: EP Kind code of ref document: A1 |