A short message reply processing method and system, electronic equipment and storage medium

Abstract

The application discloses a short message reply processing method and system, electronic equipment and a storage medium. The method comprises the following steps: obtaining a plurality of short message replies, analyzing the plurality of short message replies, and determining user information; dividing the plurality of short message replies according to the user information to obtain a plurality of reply groups containing short message replies and memory resources; in response to a user pull request, determining a first target group from the plurality of reply groups according to the user pull request, forwarding the first target group, and locking the first target group; grouping the obtained short message replies, forwarding the reply group when the user pulls the short message reply, and realizing multi-thread batch processing of the short message reply; meanwhile, the forwarded first target group is locked, the repeated pulling of the short message reply is reduced, the processing efficiency is improved, the resources occupied by the short message reply storage are reduced, and the use cost is reduced; and the application can be widely applied to the technical field of data processing.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular to a short message receipt processing method and system, an electronic device and a storage medium. BACKGROUND

[0002] In the existing short message delivery processing scheme, a short message service system forwards a short message issued by a user to an operator, obtains a short message receipt or a status report returned by the operator through a channel, stores the obtained short message receipt in a database, queries the database when the user requests the short message receipt, and returns the short message receipt to the user in batches. With the continuous growth of short message services, the existing scheme needs to continuously expand the database to accommodate short message receipts, thereby increasing the use cost. Meanwhile, the writing and reading of short message data are limited by the database, and the processing efficiency is low. SUMMARY

[0003] The main purpose of the embodiments of the present application is to provide a short message receipt processing method and system, an electronic device and a storage medium, which can reduce the use cost and improve the processing efficiency.

[0004] To achieve the above-mentioned purpose, one aspect of the embodiments of the present application provides a short message receipt processing method, which comprises the following steps:

[0005] Obtaining a plurality of short message receipts, analyzing the plurality of short message receipts, and determining user information;

[0006] Dividing the plurality of short message receipts according to the user information to obtain a plurality of receipt groups; wherein the receipt group comprises a plurality of short message receipts and memory resources;

[0007] In response to a user pull request, determining a first target group according to the user pull request and the plurality of receipt groups, locking the first target group, and forwarding the first target group according to the user pull request.

[0008] In some embodiments, the step of dividing the plurality of short message receipts according to the user information to obtain a plurality of receipt groups specifically comprises:

[0009] Analyzing the user information to determine user concurrency information, and determining a plurality of information slots according to the user concurrency information;

[0010] Allocating memory resources to the plurality of information slots to obtain a plurality of memory slots, and allocating the plurality of short message receipts according to the plurality of memory slots to obtain the plurality of receipt groups.

[0011] In some embodiments, after the step of forwarding the first target group according to the user pull request, the method further comprises:

[0012] obtaining a user request, parsing the user request, determining a request type;

[0013] if the request type is a user pull request, determining a second target group according to the user request and a plurality of the receipt groups, and forwarding the second target group according to the user request; wherein the second target group comprises the un-locked receipt groups;

[0014] if the request type is a data confirmation request, performing a first operation on the locked first target group according to the user request, to obtain a released first target group.

[0015] In some embodiments, the performing a first operation on the locked first target group according to the user request, to obtain a released first target group, specifically comprises:

[0016] parsing the user request to determine data confirmation information, performing data deletion on the locked first target group according to the data confirmation information, generating deletion information and feeding back to the user, so as to make the user confirm the deletion information and generate deletion confirmation information;

[0017] in response to the deletion confirmation information, unlocking the first target group after data deletion to obtain the released first target group.

[0018] In some embodiments, the method further comprises:

[0019] obtaining current memory usage information according to a preset period, and comparing the current memory usage information with a preset threshold;

[0020] if the current memory usage information is less than the preset threshold, performing the dividing a plurality of the short message receipts to obtain a plurality of receipt groups according to the user information;

[0021] if the current memory usage information is greater than or equal to the preset threshold, stopping the dividing a plurality of the short message receipts.

[0022] In some embodiments, the method further comprises:

[0023] obtaining a first time value, comparing the first time value with a preset time threshold, and unlocking the locked first target group if the first time value is greater than or equal to the preset time value; wherein the first time value represents the locking time of the first target group.

[0024] In some embodiments, the method further comprises:

[0025] The short message receipts are obtained, the short message receipts are sent to a message queue, the short message receipts are obtained from the message queue, the short message receipts are parsed, and user information is determined.

[0026] To achieve the above-mentioned purpose, another aspect of the embodiment of the present application provides a short message receipt processing system, the system comprises:

[0027] The first module is used for obtaining a plurality of short message receipts, parsing the short message receipts, and determining user information.

[0028] The second module is used for dividing the short message receipts according to the user information to obtain a plurality of receipt groups; wherein the receipt group comprises a plurality of short message receipts and memory resources.

[0029] The third module is used for responding to a user pull request, determining a first target group according to the user pull request and the plurality of receipt groups, locking the first target group, and forwarding the first target group according to the user pull request.

[0030] To achieve the above-mentioned purpose, another aspect of the embodiment of the present application provides an electronic device, the electronic device comprises a memory and a processor, the memory stores a computer program, and the processor implements the method described above when executing the computer program.

[0031] To achieve the above-mentioned purpose, another aspect of the embodiment of the present application provides a computer readable storage medium, the computer readable storage medium stores a computer program, and the computer program is executed by the processor to implement the method described above.

[0032] The embodiment of the present application has the following beneficial effects: the embodiment provides a short message receipt processing method, system, electronic device and storage medium, the method obtains a plurality of short message receipts, parses the short message receipts, and determines user information; the short message receipts are divided according to the user information to obtain a plurality of receipt groups containing short message receipts and memory resources; in response to a user pull request, a first target group is determined from the plurality of receipt groups according to the user pull request, and the first target group is forwarded; by grouping the obtained short message receipts, the receipt group is forwarded when the user pulls the short message receipt, the multi-thread batch processing of the short message receipt is realized; at the same time, the first target group is locked for forwarding, the repeated pulling of the short message receipt is reduced, the processing efficiency is improved, the resources occupied by the short message receipt storage are reduced, and the use cost is reduced. BRIEF DESCRIPTION OF DRAWINGS

[0033] Figure 1 is a step flowchart of a short message receipt processing method provided by the embodiment of the present application;

[0034] Figure 2 is a step flow diagram of determining a receipt group in a short message receipt processing method provided by an embodiment of the present application;

[0035] Figure 3 is a step flow diagram of processing a user request in a short message receipt processing method provided by an embodiment of the present application;

[0036] Figure 4 is a step flow diagram of performing a second operation in a short message receipt processing method provided by an embodiment of the present application;

[0037] Figure 5 is a step flow diagram of determining a receipt group according to memory usage in a short message receipt processing method provided by an embodiment of the present application;

[0038] Figure 6 is a structure diagram of a short message service system in a specific embodiment provided by an embodiment of the present application;

[0039] Figure 7 is a step flow diagram of a specific embodiment provided by an embodiment of the present application;

[0040] Figure 8 is a structure diagram of a redis slot in a specific embodiment provided by an embodiment of the present application;

[0041] Figure 9 is a structure block diagram of a short message receipt processing system provided by an embodiment of the present application;

[0042] Figure 10 is a hardware structure diagram of an electronic device provided by an embodiment of the present application;

[0043] wherein, 1 is a user issuing module, 2 is a user pulling status report module, 3 is a short message receiving module, 4 is a channel, 5 is an operator, 6 is a rocketmq queue, 7 is a receipt distribution module, 8 is a high-speed memory redis, and 9 is a receipt obtaining module. DETAILED DESCRIPTION

[0044] The present application will be further described in detail below with reference to the accompanying drawings and specific embodiments. For the step numbers in the following embodiments, only the setting is for the convenience of description, and the order between the steps is not limited in any way, and the execution order of each step in the embodiments can be adaptively adjusted according to the understanding of those skilled in the art.

[0045] In the following description, reference is made to "some embodiments", which describe a subset of all possible embodiments, but it is understood that "some embodiments" can be the same subset or different subsets as each other and can be combined with each other as long as there is no conflict.

[0046] In the following description, the terms "first\second\third" are only to distinguish similar objects, and do not represent a specific order of the objects. It is understood that "first\second\third" can be interchanged in a specific order or sequence as long as it is allowed, so that the embodiments of the application described herein can be implemented in an order other than that illustrated or described herein.

[0047] Unless otherwise defined, all technical and scientific terms used in the embodiments of the application have the same meanings as those commonly understood by one skilled in the art to which the embodiments of the application belong. The terms used in the embodiments of the application are only for the purpose of describing the embodiments of the application and are not intended to limit the application.

[0048] Figure 1 is an optional flowchart of a short message receipt processing method provided by the embodiments of the application, Figure 1 The method in can include but is not limited to steps S101-S103.

[0049] Step S101, obtaining a plurality of short message receipts, parsing the plurality of short message receipts, and determining user information;

[0050] Step S102, dividing the plurality of short message receipts according to the user information to obtain a plurality of receipt groups; wherein, the receipt group includes a plurality of short message receipts and memory resources;

[0051] Step S103, in response to a user pull request, determining a first target group according to the user pull request and the plurality of receipt groups, locking the first target group, and forwarding the first target group according to the user pull request.

[0052] The steps S101-S103 shown in the embodiments of the application, the short message receipt processing method provided by the embodiments of the application is applied to a short message service system; a user sends a short message to an operator through the short message service system, the operator generates a corresponding short message receipt or status report after processing the sent short message, and returns to the short message service system; the short message service system obtains the short message receipt through a corresponding channel, parses the short message receipt, extracts the user information therein, and groups the obtained short message receipt according to the user information, and when the user requests, batch forwards the grouped short message receipt; at the same time, the forwarded short message receipt is locked to avoid forwarding repeated short message receipts when the user requests, so as to improve the processing efficiency.

[0053] In step S101 of some embodiments, the obtained short message receipts can be temporarily cached in a database, such as mysql, to improve the processing capacity of data. A message queue with high write performance can also be used, and the short message receipts or status reports returned by the operator are first written into the message queue for caching. A function module for distributing short message receipts in the system reads the short message receipts from the message queue for distribution, such as rocketmq.

[0054] Referring to Figure 2 In some embodiments, step S102 can include but is not limited to steps S201 to S202:

[0055] In step S201, the user information is parsed to determine the user concurrency information, and a plurality of information slots are determined according to the user concurrency information.

[0056] In step S202, memory resources are allocated to the plurality of information slots to obtain a plurality of memory slots, and the plurality of short message receipts are distributed according to the plurality of memory slots to obtain a plurality of receipt groups.

[0057] In step S201 of some embodiments, the obtained short message receipts are parsed to determine the concurrency information in the user information, which is the maximum number of simultaneous pull forwarding of the user. The system determines to divide the short message receipts into a corresponding number of short message receipt groups according to the concurrency information of the user, and forwards the corresponding number of short message receipt groups when the user pulls the short message receipts. The data forwarding capacity and data processing efficiency are improved through the way of multi-threading and multi-processing. In this embodiment, the short message receipts are grouped by using high-speed cache redis.

[0058] In step S202 of some embodiments, after determining the number of short message receipt groups, the system allocates corresponding resources in the memory device, and then allocates a certain number of short message receipts to obtain a short message receipt group after processing such as encapsulation. In this embodiment, the system constructs the same number of redis structure slots in the redis cache according to the concurrency data of the user and allocates corresponding memory resources for distributing short message receipts. The system distributes the short message receipts into the corresponding redis structure slots according to the user information of the short message receipts. For example, the system distributes the short message receipts according to the message ID of the short message receipts, or distributes them according to the timestamp information of the short message receipts, etc.

[0059] Referring to Figure 3 In this embodiment, after step S103, steps S301 to S303 can be included but are not limited to:

[0060] In step S301, a user request is obtained, and the user request is parsed to determine the request type.

[0061] Step S302: If the request type is a user pull request, determine a second target group based on the user request and several receipt groups, and forward the second target group according to the user request; wherein, the second target group includes unlocked receipt groups;

[0062] Step S303: If the request type is a data confirmation request, perform the first operation on the locked first target group according to the user request to obtain the released first target group.

[0063] In step S301 of some embodiments, after the system responds to the user's request and forwards the SMS receipt group, the system monitors the user request information sent by the user terminal in real time, parses the received user request, determines the type of user request, and determines whether to unlock and release the locked SMS receipt group or forward the remaining SMS receipt groups based on the type of user request.

[0064] In step S302 of some embodiments, the system parses the received user request, determines that the user request is a pull request, and then selects one from the remaining unlocked SMS receipt groups for forwarding based on the user request. For example, the system queries the remaining unlocked SMS receipt groups based on the user ID information and operator information in the user request, determines the SMS receipt group that matches both the user ID information and operator information, forwards the SMS receipt group, and locks the SMS receipt group to prevent the forwarding of SMS receipts with the same content in subsequent forwardings.

[0065] In step S303 of some embodiments, the system parses the received user request and determines that the user's request is a confirmation message. The system can determine that the user has received a forwarded SMS receipt group. The system can process the locked SMS receipt group accordingly, unlocking and releasing the SMS receipt group for new SMS receipt allocation. At the same time, the corresponding memory resources are released, reducing the occupation of system resources by SMS receipts, thereby reducing the system expansion requirements and lowering the usage cost.

[0066] Please see Figure 4 In some embodiments, step S303 may include, but is not limited to, steps S401 to S402:

[0067] Step S401: Parse the user request, determine the data confirmation information, delete the data in the locked first target group according to the data confirmation information, generate deletion information and send it back to the user so that the user can confirm the deletion information and generate deletion confirmation information.

[0068] In step S402, in response to the deletion confirmation information, the first target group after data deletion is unlocked, and the released first target group is obtained.

[0069] In step S401 of some embodiments, after the system determines that the user has returned a confirmation request, the system parses the received confirmation request and extracts the data confirmation information therein; the system determines the locked target SMS receipt group based on the extracted data confirmation information, such as the SMS receipt group number or user ID in the data confirmation message; after the system determines the locked target SMS receipt group, it deletes the SMS receipt data in the target SMS receipt group and generates a deletion confirmation message to send to the user terminal.

[0070] In step S402 of some embodiments, the user confirms the deletion confirmation message sent by the system and sends it back to the system. After receiving the feedback information, the system unlocks the locked target SMS receipt group. Since the SMS receipt data in the target SMS receipt group has been deleted, the system can reallocate SMS receipts to the target SMS receipt group.

[0071] Please see Figure 5 In some embodiments, the SMS receipt processing method provided by the present invention may also include, but is not limited to, steps S501 to S503:

[0072] Step S501: Obtain current memory usage information according to a preset period, and compare the current memory usage information with a preset threshold.

[0073] Step S502: If the current memory usage information is less than a preset threshold, perform the division of several SMS receipts according to user information to obtain several receipt groups.

[0074] Step S503: If the current memory usage information is greater than or equal to a preset threshold, stop dividing several SMS receipts.

[0075] In step S501 of some embodiments, the system constructs information slots based on user concurrency information, allocates memory resources to each information slot, and then assigns SMS receipts to each information slot that has been allocated memory resources. The system periodically obtains the usage of memory resources in the system and judges whether the current memory resources of the system are sufficient based on a preset threshold, so as to reduce the risk of excessive use of system memory resources and affecting business processing.

[0076] In step S502 of some embodiments, if the memory resource usage in the system is less than a preset threshold, the system normally performs the SMS receipt distribution operation, constructs information slots according to user concurrency information, allocates corresponding memory resources and SMS receipts to the information slots, and forwards the grouped SMS receipts when the user requests to retrieve them.

[0077] In step S503 of some embodiments, if the memory resource usage in the system is greater than or equal to a preset threshold, the system stops allocating SMS receipts to avoid excessive memory usage affecting system operation. Corresponding processing strategies can be executed to release some memory resources in the message slots and reduce memory resource usage. In this embodiment, when the memory resource usage is greater than or equal to the preset threshold, the system stops obtaining SMS receipts from the message queue RocketMQ, waits for user confirmation to delete forwarded SMS receipt groups, releases the memory resources of these SMS receipt groups, and then allocates newly obtained SMS receipts.

[0078] In some embodiments, the system locks the SMS receipt group forwarded in response to a user's retrieval request. When the user requests to retrieve again, the system will not forward the locked SMS receipt group, thereby reducing the forwarding of duplicate data. When the user confirms the SMS receipt data forwarded by the system, the system deletes the data in the locked SMS receipt group. After the user confirms the deletion, the system unlocks the locked SMS receipt group to release memory. If the system does not receive confirmation from the user within a preset time after forwarding and locking the SMS receipt group, such as 180 seconds, it can be determined that there may be an anomaly on the user's end, such as a malfunction in the SMS receipt acquisition module on the user's end, or the user's SMS receipt processing speed is too slow, resulting in the loss or error of the SMS receipt data forwarded by the system, and the user's end cannot confirm the data. The system unlocks the locked SMS receipt group, and the user can retrieve the data in the SMS receipt group again for processing.

[0079] The following is a detailed description and explanation of the solutions in the embodiments of the present invention, using specific application examples:

[0080] Please see Figure 6 , Figure 6 This is a schematic diagram of the structure of a text messaging service system in a specific application of this invention. The system includes a text messaging receiving module, a channel, a receipt distribution module, a receipt retrieval module, a high-speed memory Redis, and a RocketMQ queue. The text messaging receiving module is connected to the channel and several user-sending modules within the user modules accessing the text messaging service. It receives text messages sent by users and sends them to the operator through the channel. The operator returns text messaging receipts to the channel, which are then processed by the receipt distribution module, the receipt retrieval module, the high-speed memory Redis, and the RocketMQ queue before being sent to the user retrieval status report module within the several user modules accessing the text messaging service. Please refer to [link to relevant documentation]. Figure 7The SMS service system sends the received SMS receipts to RocketMQ, a high-performance write server, for persistent storage. The receipt distribution module periodically checks the usage of high-speed Redis to determine if Redis memory is sufficient. When Redis memory is sufficient, it retrieves the SMS receipts from RocketMQ, analyzes them to determine user account information, and constructs a concurrency structure based on the user's concurrent retrieval volume within the user account information. Figure 8 The obtained SMS receipts are distributed to the Redis slots shown. When the receipt acquisition module receives a request for SMS receipts from the user's pull status report module, it randomly selects a Redis slot with allocated SMS receipts and forwards it to the user pull status report module. Simultaneously, it locks the selected Redis slot and waits for confirmation from the user pull status report module. If the user pull status report module does not provide confirmation, it performs a second pull, randomly selecting an unlocked Redis slot for forwarding. If the user pull status report module provides confirmation, it deletes the SMS receipt data from the locked Redis slot and provides deletion information. Once the user pull status report module confirms the deletion, the corresponding locked Redis slot is unlocked, and the receipt distribution module can then distribute SMS receipts to that Redis slot.

[0081] The implementation of this invention provides the following beneficial effects: This embodiment offers a method, system, electronic device, and storage medium for processing SMS receipts. The method acquires several SMS receipts, parses them to determine user information, divides the receipts according to the user information to obtain several receipt groups containing SMS receipts and memory resources, responds to user retrieval requests, determines a first target group from the receipt groups based on the user retrieval request, and forwards the first target group, grouping the acquired SMS receipts and forwarding the receipt groups when the user retrieves the SMS receipts, thus achieving multi-threaded batch processing of SMS receipts. Simultaneously, locking the first target group for forwarding reduces repeated retrieval of SMS receipts, improves processing efficiency, reduces the resources occupied by SMS receipt storage, and lowers usage costs. Regularly monitoring the system's memory usage reduces the need for memory expansion due to excessive memory usage, achieving peak shaving and valley filling.

[0082] like Figure 9 As shown, this embodiment of the invention also provides an SMS receipt processing system, which can implement the above-described SMS receipt processing method. The system includes:

[0083] The first module is used to obtain several SMS receipts, parse the SMS receipts, and determine user information.

[0084] The second module is used to divide the several SMS receipts according to the user information to obtain several receipt groups; wherein, the receipt group includes several SMS receipts and memory resources;

[0085] The third module is used to respond to a user pull request, determine a first target group based on the user pull request and several receipt groups, lock the first target group, and forward the first target group according to the user pull request.

[0086] It is evident that the content of the above method embodiments is applicable to this system embodiment. The specific functions implemented in this system embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0087] This application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the aforementioned SMS receipt processing method. This electronic device can be any smart terminal, including tablet computers, in-vehicle computers, etc.

[0088] It is understood that the content of the above method embodiments is applicable to this device embodiment. The specific functions implemented by this device embodiment are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0089] Please see Figure 10 , Figure 10 The hardware structure of an electronic device according to another embodiment is illustrated. The electronic device includes:

[0090] The processor 1001 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0091] The memory 1002 can be implemented as a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1002 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1002 and is called and executed by the processor 1001 to execute a text message receipt processing method according to an embodiment of this application.

[0092] Input / output interface 1003 is used to implement information input and output;

[0093] The communication interface 1004 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0094] Bus 1005 transmits information between various components of the device (e.g., processor 1001, memory 1002, input / output interface 1003, and communication interface 1004);

[0095] The processor 1001, memory 1002, input / output interface 1003 and communication interface 1004 are connected to each other within the device via bus 1005.

[0096] The memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. The memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, the memory may optionally include remote memory located remotely relative to the processor, which can be connected to the processor 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.

[0097] Furthermore, this application also discloses a computer program product or computer program stored in a computer-readable storage medium. A processor of a computer device can read the computer program from the computer-readable storage medium, and the processor executes the computer program, causing the computer device to perform the described method. Similarly, the content of the above method embodiments is applicable to this storage medium embodiment. The specific functions implemented in this storage medium embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0098] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described SMS receipt processing method.

[0099] It is understood that the content of the above method embodiments is applicable to this storage medium embodiment. The specific functions implemented in this storage medium embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0100] It is understood that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0101] The above is a detailed description of the preferred embodiments of the present invention. However, the present invention is not limited to the embodiments described. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. A method for handling short message return receipt, characterized in that, The method comprises the following steps: acquiring a plurality of short message receipts, parsing the plurality of short message receipts to determine user information; dividing the plurality of short message receipts according to the user information to obtain a plurality of receipt groups; wherein the receipt group comprises a plurality of short message receipts and memory resources; in response to a user pull request, determining a first target group according to the user pull request and the plurality of receipt groups, locking the first target group, and forwarding the first target group according to the user pull request; processing the user request and the plurality of receipt groups; wherein the user request is determined by real-time monitoring of the user end after forwarding the first target group, and the processing comprises forwarding or unlocking.

2. The method of claim 1, wherein, The dividing the plurality of short message receipts according to the user information to obtain a plurality of receipt groups specifically comprises: parsing the user information to determine user concurrency information, and determining a plurality of information slots according to the user concurrency information; allocating memory resources to the plurality of information slots to obtain a plurality of memory slots, and allocating the plurality of short message receipts according to the plurality of memory slots to obtain the plurality of receipt groups.

3. The method of claim 1, wherein, The processing the user request and the plurality of receipt groups specifically comprises: acquiring a user request, and parsing the user request to determine a request type; if the request type is a user pull request, determining a second target group according to the user request and the plurality of receipt groups, and forwarding the second target group according to the user request; wherein the second target group comprises the receipt groups that are not locked; if the request type is a data confirmation request, performing a first operation on the locked first target group according to the user request to obtain a released first target group.

4. The method of claim 3, wherein, The performing a first operation on the locked first target group according to the user request to obtain a released first target group specifically comprises: parsing the user request to determine data confirmation information, performing data deletion on the locked first target group according to the data confirmation information, generating deletion information and feeding back to the user to enable the user to confirm the deletion information, and generating deletion confirmation information; in response to the deletion confirmation information, unlocking the first target group after data deletion to obtain the released first target group.

5. The method of claim 1, wherein, The method further comprises: acquiring current memory usage information according to a preset period, and comparing the current memory usage information with a preset threshold; if the current memory usage information is less than the preset threshold, performing the dividing the plurality of short message receipts according to the user information to obtain a plurality of receipt groups; if the current memory usage information is greater than or equal to the preset threshold, stopping the dividing the plurality of short message receipts.

6. The method of claim 1, wherein, The method further comprises: acquiring a first time value, comparing the first time value with a preset time threshold, and unlocking the locked first target group if the first time value is greater than or equal to the preset time threshold; wherein the first time value represents the locking time of the first target group.

7. The method of claim 1, wherein, The method further comprises: Obtaining a plurality of short message receipts, sending the plurality of short message receipts to a message queue, obtaining a plurality of short message receipts from the message queue, performing the parsing of the plurality of short message receipts, and determining user information.

8. A short message receipt processing system characterized by comprising: The method comprises: A first module for obtaining a plurality of short message receipts, parsing the plurality of short message receipts, and determining user information; A second module for dividing the plurality of short message receipts according to the user information to obtain a plurality of receipt groups; wherein the receipt group comprises a plurality of short message receipts and memory resources; A third module for responding to a user pull request, determining a first target group according to the user pull request and the plurality of receipt groups, locking the first target group, and forwarding the first target group according to the user pull request; processing the user request and the plurality of receipt groups; wherein the user request is determined by real-time monitoring of the user end after forwarding the first target group, and the processing includes forwarding or unlocking.

9. An electronic device, comprising: The method comprises: At least one processor; At least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the method of any one of claims 1-7.

10. A computer readable storage medium having stored therein a program which is executable by a processor, characterized in that, The program executable by the processor, when executed by the processor, is used to execute the method of any one of claims 1-7.

Images