Paging management method and device for short message status report

Abstract

This application discloses a paging management method and apparatus for SMS status reports. The method includes: monitoring the air interface load status of access network equipment; when preset conditions are met, sending a load status message to core network equipment to trigger the core network equipment to adjust its strategy for sending SMS status report paging messages to access network equipment; responding to a location update request message initiated by a terminal, determining the target file corresponding to the terminal, the target file including the terminal's demand status for SMS status reports and historical response status; after the terminal sends an SMS, responding to a target SMS status report paging message sent by the core network equipment for the terminal, determining the processing method for the target SMS status report paging message based on the target file and real-time air interface load status, including immediate delivery, delayed delivery, or direct filtering. This application solves the technical problem that traditional SMS status report paging schemes in satellite communication scenarios easily cause service congestion and waste of air interface resources.

Description

Technical Field

[0001] This application relates to the field of satellite communication technology, and more specifically, to a paging management method and apparatus for SMS status reporting. Background Technology

[0002] Satellite networks are characterized by wide coverage, diverse terminal types, and poor stability due to factors such as satellite link attitude and atmospheric obstruction. In existing satellite communication systems, SMS (Short Message Service) is a core application. After a terminal sends an SMS, the SMS service center typically needs to return an SMS status report to the sending terminal. However, existing technologies mainly use the paging mechanism of terrestrial cellular networks, failing to fully adapt to the unique characteristics of satellite scenarios. This results in severe service congestion and wasted air interface resources during SMS status report paging processing, specifically manifested as follows:

[0003] First, in scenarios involving large-scale satellite roaming, when a terminal roams between different access network devices, the new access network devices often lack the terminal's historical response characteristics and specific service requirement files. This makes it impossible to accurately determine the terminal's needs for different types of reports, often requiring multiple probing paging requests to ascertain the terminal's response capabilities. Under conditions of high satellite link latency, this probing mechanism not only significantly increases core paging latency, causing service congestion, but also leads to a waste of a large amount of ineffective air interface signaling resources.

[0004] Second, in satellite communication scenarios, the air interface load fluctuates dramatically, but in existing technologies, core network equipment cannot obtain the air interface load status of access network equipment in real time, and only issues paging commands according to a fixed strategy. This leads to the core network continuing to issue low-priority paging commands when the access network is overloaded, further aggravating access network congestion, causing high-priority core service transmission to be blocked, and also resulting in the ineffective occupation of air interface resources during overload periods;

[0005] Third, the instability of satellite links can easily cause load monitoring failures, missing fields, or terminal unresponsiveness. Existing technologies usually adopt simple discard or fixed-duration retransmission strategies. However, fixed retransmission strategies often initiate transmission again when resources are still scarce, resulting in repeated invalid occupation of air interface resources. This not only fails to solve the service blockage problem but also exacerbates the risk of signaling loss.

[0006] There is currently no effective solution to the above problems. Summary of the Invention

[0007] This application provides a paging management method and apparatus for SMS status reports, which at least solves the technical problem that traditional SMS status report paging schemes in satellite communication scenarios are prone to causing service blockage and waste of air interface resources.

[0008] According to one aspect of the embodiments of this application, a paging management method for SMS status reports is provided, comprising: monitoring the air interface load status of an access network device, and sending a load status message to a core network device when the air interface load status meets preset conditions, wherein the load status message is used to trigger the core network device to adjust the strategy of sending SMS status report paging messages to the access network device; in response to a location update request message initiated by a target terminal, determining a target file corresponding to the target terminal, wherein the target file includes the target terminal's demand status for SMS status reports and historical response status; after the target terminal sends an SMS, in response to a target SMS status report paging message sent by the core network device for the target terminal, determining a processing method for the target SMS status report paging message based on the target file and the real-time air interface load status, wherein the processing method includes one of the following: immediate delivery, delayed delivery, and direct filtering.

[0009] Optionally, when the air interface load status meets preset conditions, a load status message is sent to the core network device, including: when the air interface load status changes from not meeting the preset overload conditions to meeting the preset overload conditions, a load warning message is sent to the core network device, wherein the load warning message is used to trigger the core network device to reduce the number of low-priority SMS status report paging messages sent to the access network device based on the preset SMS status report paging message sending strategy; when the air interface load status changes from meeting the preset overload conditions to not meeting the preset overload conditions, a load recovery message is sent to the core network device, wherein the load recovery message is used to trigger the core network device to restore the preset SMS status report paging message sending strategy.

[0010] Optionally, in response to a location update request message initiated by the target terminal, determining the target file corresponding to the target terminal includes: upon receiving a location update request message sent by the target terminal, querying whether a target file is stored locally; if no target file exists locally, obtaining the target file from an earlier access network device through the core network device and storing the target file locally, wherein the earlier access network device is the access network device that last recorded the target terminal's location information before the target terminal accessed the current access network.

[0011] Optionally, obtaining the target file from the prior access network device through the core network device includes: sending a terminal file request message to the core network device based on a preset synchronization interface to instruct the core network device to send a file synchronization request message to the prior access network device and receive a file synchronization response message carrying the target file from the prior access network device; and receiving a terminal file response message carrying the target file from the core network device.

[0012] Optionally, if no terminal file response message is received from the core network device after a first preset time period, a target file is constructed based on a preset demand state and a preset historical response state, and the terminal file request message is retransmitted to the core network device based on a preset number of retransmissions and a preset retransmission time interval; if a terminal file response message is received from the core network device after retransmitting the terminal file request message, the constructed target file is replaced with the target file carried in the terminal file response message.

[0013] Optionally, if the location update request message carries a new demand status for the target terminal's SMS status report, the locally stored target file is updated based on the new demand status.

[0014] Optionally, the processing method for the target SMS status report paging message is determined based on the target profile and real-time air interface load status, including: if the target profile indicates that the target terminal has no need for the target SMS status report paging message, the target SMS status report paging message is directly filtered; if the target profile indicates that the target terminal has a need for the target SMS status report paging message, the processing method for the target SMS status report paging message is further determined based on the following judgment logic: if the real-time air interface load status does not meet the preset overload condition, the target SMS status report paging message is immediately sent; if the real-time air interface load status meets the preset overload condition, the target SMS status report paging message is added to the message queue, wherein all SMS status report paging messages in the message queue are sent sequentially from high to low according to their corresponding priorities, and the priority of each SMS status report paging message is determined based on the message arrival time, report type, and the historical response status of the corresponding terminal to the SMS status report.

[0015] Optionally, if any SMS status report paging message in the message queue remains in the queue for more than a second preset time, the SMS status report paging message is removed from the message queue, and a paging timeout message is sent to the core network equipment.

[0016] Optionally, after sending the target SMS status report paging message, if no paging response message is received from the target terminal after a third preset time period, the priority of the target SMS status report paging message is determined; if the priority is higher than the preset level, the target SMS status report paging message is retransmitted; if no paging response message is received from the target terminal after a third preset time period, a paging failure message is sent to the core network equipment; if the priority is not higher than the preset level, the retransmission of the target SMS status report paging message is abandoned.

[0017] Optionally, upon detecting a preset abnormal event, a fallback decision-making process and a source tracing feedback process are executed. The preset abnormal events include at least one of the following: air interface load monitoring failure, missing fields in paging messages sent by core network equipment, or missing terminal files. The fallback decision-making process includes: determining the fallback rule corresponding to the abnormal event type from a preset policy table, and determining the processing method for the target SMS status report paging message based on the fallback rule. The fallback rule prioritizes ensuring the delivery of paging messages of type SMS sending failure report. The source tracing feedback process includes: sending an alarm message to the core network equipment or operation and maintenance system, including the abnormal event type, the time of abnormal occurrence, and a fault identifier, to trigger fault location for the abnormal event.

[0018] According to another aspect of the embodiments of this application, a paging management device for SMS status reports is also provided, comprising: a load monitoring module, used to monitor the air interface load status of access network equipment, and when the air interface load status meets preset conditions, send a load status message to the core network equipment, wherein the load status message is used to trigger the core network equipment to adjust the strategy of sending SMS status report paging messages to access network equipment; a file management module, used to determine the target file corresponding to the target terminal in response to a location update request message initiated by the target terminal, wherein the target file includes the target terminal's demand status for SMS status reports and historical response status; and a paging management module, used to determine the processing method for the target SMS status report paging message based on the target file and real-time air interface load status in response to a target SMS status report paging message sent by the core network equipment after the target terminal sends an SMS, wherein the processing method includes one of the following: immediate delivery, delayed delivery, and direct filtering.

[0019] According to another aspect of the embodiments of this application, a computer program product is also provided, the computer program product comprising: a computer program, wherein when the computer program is executed by a processor, it implements the above-described paging management method for SMS status reporting.

[0020] According to another aspect of the embodiments of this application, an electronic device is also provided, the electronic device including: a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the above-described paging management method for SMS status reporting through the computer program.

[0021] In this embodiment, the air interface load status is monitored in real time, and a load status message is sent to the core network equipment when the air interface load status meets preset conditions to trigger the core network equipment to dynamically adjust the SMS status report paging message delivery strategy. At the same time, in response to the location update request message initiated by the target terminal, the target file corresponding to the target terminal is determined, eliminating the delivery of tentative paging messages. Combined with real-time load, the processing method of SMS status report paging messages is intelligently decided, realizing real-time coordinated linkage of the load status of the core network and the access network, as well as rapid synchronization and accurate matching of file information in terminal roaming scenarios. This avoids service blockage caused by access network equipment overload, and reduces the waste of invalid air interface signaling resources. It effectively solves the technical problem that traditional SMS status report paging schemes in satellite communication scenarios are prone to causing service blockage and air interface resource waste. Attached Figure Description

[0022] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0023] Figure 1 This is a flowchart illustrating an optional paging management method for SMS status reporting according to an embodiment of this application;

[0024] Figure 2 This is a schematic diagram of an optional target file determination process according to an embodiment of this application;

[0025] Figure 3 This is a schematic diagram of an optional target SMS status report paging message processing flow according to an embodiment of this application;

[0026] Figure 4 This is a schematic diagram of an optional communication system according to an embodiment of this application;

[0027] Figure 5 This is a schematic diagram of the structure of an optional SMS status reporting paging management device according to an embodiment of this application;

[0028] Figure 6 This is a schematic diagram of an optional electronic device according to an embodiment of this application. Detailed Implementation

[0029] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0030] It should be noted that the terms "first," "second," etc., used in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0031] To better understand the embodiments of this application, the following is a translation and explanation of some nouns or terms that appear in the description of the embodiments of this application:

[0032] Roaming refers to the ability of a mobile phone or mobile terminal to continue using call, text message, or data services through other networks after leaving the coverage area of ​​its original network due to a change in location.

[0033] Profile: A core concept in mobile communication networks, it is a structured data packet that a terminal registers with and uploads to the network side. It details the technical features, capability parameters, and functional limitations supported by the terminal. When a terminal registers with the network, the network side requests this profile from the terminal to understand the service requirements of the terminal.

[0034] The S1-MME interface (S1 Mobility Management Entity Interface) is a standardized interface defined in satellite communication protocols between the core network (such as mobility management entities, access and mobility management functions, etc.) and the access network. It is mainly used to transmit paging commands, terminal registration signaling, etc., and is a key communication channel for core network equipment to send SMS status report paging messages to access network equipment.

[0035] International Mobile Subscriber Identity (IMSI): This is a globally unique and permanent identifier for a terminal. It consists of 15 digits and is stored in the terminal's SIM (Subscriber Identity Module) card. Access network equipment can identify the terminal's identity through the IMSI, which serves as the terminal's identification field.

[0036] Temporary Mobile Subscriber Identity (TMSI): This is a temporary identifier assigned to a terminal by the core network equipment. It is used to replace the IMSI in the communication channel and communication interface, avoiding the security risks caused by the plaintext transmission of the IMSI.

[0037] Fallback rule: This is a general concept widely used in technical systems, business logic, and other fields. Its core meaning is: a set of backup plans that are activated to maintain the smooth execution of priority protection types when the main process, normal logic, or specific conditions cannot be met.

[0038] Traceability Feedback is a concept widely used in fields such as quality management, software engineering, supply chain management, and cybersecurity. It refers to the process of not only solving the current problem after discovering a problem or anomaly, but also tracing the cause upstream and feeding back the results to the source, thereby preventing the problem from recurring or optimizing the upstream process.

[0039] Example 1

[0040] According to an embodiment of this application, a paging management method for SMS status reporting is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0041] Figure 1 This is a flowchart illustrating a paging management method for SMS status reporting provided in an embodiment of this application, as shown below. Figure 1 As shown, the method includes the following steps S102-S106:

[0042] Step S102: Monitor the air interface load status of the access network device, and when the air interface load status meets the preset conditions, send a load status message to the core network device. The load status message is used to trigger the core network device to adjust the strategy of sending SMS status report paging messages to the access network device.

[0043] Step S104: In response to the location update request message initiated by the target terminal, determine the target file corresponding to the target terminal, wherein the target file includes the target terminal's demand status for SMS status reports and its historical response status.

[0044] Step S106: After the target terminal sends an SMS message, in response to the target SMS status report paging message sent by the core network equipment for the target terminal, determine the processing method for the target SMS status report paging message based on the target file and the real-time air interface load status. The processing method includes one of the following: immediate delivery, delayed delivery, or direct filtering.

[0045] The following section explains each step of the paging management method for SMS status reports, using a specific implementation process as an example.

[0046] As an optional solution, in order to avoid resource scheduling imbalance caused by poor air interface load status of access network devices, regarding the above step S102, the access network device monitors its own air interface load status and sends a load status message to the core network device when the air interface load status meets the preset conditions.

[0047] In the embodiments of this application, the aforementioned air interface load status is a real-time quantitative evaluation indicator of the current air interface radio resource usage by the access network device, which includes, but is not limited to, fields such as channel occupancy rate, random access volume, and comprehensive air interface load rate calculated based on a weighted algorithm.

[0048] In this embodiment, the aforementioned load status message is a signaling notification sent by the access network device to the core network device to indicate the current air interface resource shortage and to trigger the core network device to adjust its strategy for sending SMS status report paging messages to the access network device. It includes, but is not limited to, load warning messages or load recovery messages.

[0049] Optionally, load status messages can be sent to the core network equipment based on the air interface load status of the access network equipment in the following manner:

[0050] Step S11: Monitor the air interface load status of the access network device and determine whether the air interface load status meets the preset overload conditions.

[0051] For example, step S11 above can be understood as follows: First, acquire basic physical layer data such as channel occupancy rate and random access volume of access network devices in real time; second, perform weighted fusion calculation on the collected data according to a preset weighting algorithm (e.g., channel occupancy rate accounts for 70% weight, random access volume accounts for 30% weight) to obtain the real-time comprehensive air interface load status; finally, compare the calculated air interface load status with preset overload conditions. When the air interface load status is detected to exceed the preset overload threshold in the first time period (e.g., air interface load status is greater than 90% for 5 consecutive minutes) or the air interface load status shows a significant jump in the second time period (e.g., air interface load status increases by more than 30% within 1 minute), it is determined that the air interface load status meets the preset overload conditions. The time span of the first time period is longer than that of the second time period.

[0052] Step S12: When the air interface load status changes from not meeting the preset overload condition to meeting the preset overload condition, a load warning message is sent to the core network equipment.

[0053] In this embodiment of the application, the aforementioned load warning message includes, but is not limited to, fields such as access network device identifier, current real-time air interface load status value, overload duration, or specific reason identifier for triggering overload.

[0054] Optionally, after the access network device sends a load warning message to the core network device, the core network device may perform the following steps:

[0055] First, the core network equipment receives load warning messages from the access network equipment and parses them to obtain the identifier and real-time load rate of the currently overloaded access network equipment.

[0056] Then, the core network equipment queries the global access network load distribution status and identifies other access network devices with load rates lower than a preset threshold as target migration objects.

[0057] Finally, the core network equipment readjusted the number of low-priority SMS status report paging messages originally planned to be sent to the overloaded access network and rescheduled them to the low-load access network equipment, while maintaining the normal sending ratio of high-priority paging messages in the original overloaded access network, thereby achieving dynamic balance of paging load across the entire network.

[0058] Step S13: When the air interface load status changes from meeting the preset overload conditions to not meeting the preset overload conditions, a load recovery message is sent to the core network equipment.

[0059] In this embodiment of the application, the aforementioned load recovery message is an interactive signaling used to trigger the core network device to restore the preset SMS status report paging message distribution strategy, which includes, but is not limited to, fields such as access network device identifier and current real-time air interface load status value.

[0060] Optionally, after the access network device sends a load recovery message to the core network device, the core network device can restore the preset SMS status report paging message delivery strategy in the following manner: The core network device receives the load recovery message from the access network device, parses and obtains the identifier and real-time load rate of the current access network device, removes the low-priority paging restriction on the original overloaded access network, and restores the preset SMS status report paging message delivery strategy.

[0061] Through the embodiments of this application, a two-way linkage mechanism is established to send a load warning message to trigger the core network to reduce the issuance of low-priority paging when the air interface load status changes from not meeting to meeting the preset overload conditions, and to send a load recovery message to trigger the core network to restore the preset strategy when the preset overload conditions change from meeting to not meeting the preset overload conditions. This mechanism alleviates the transmission congestion when the access network equipment is overloaded and avoids the problem of continuous air interface resource shortage caused by the access network equipment blindly receiving paging messages issued by the core network equipment.

[0062] As an optional solution, to meet dynamically changing terminal needs and avoid paging decision lag, Figure 2 This is a schematic diagram of an optional target file determination process according to an embodiment of this application, such as... Figure 2 As shown, regarding step S104 above, the target file corresponding to the target terminal can be determined in the following manner in response to the location update request message initiated by the target terminal:

[0063] Step S21: Upon receiving a location update request message from the target terminal, check whether the target file is stored locally.

[0064] In this embodiment, the aforementioned location update request message is an identity registration and status synchronization signaling initiated by the target terminal to the access network device when roaming to a new access network device or performing periodic location registration. It includes, but is not limited to, the International Mobile Subscriber Identity (IMSI), the Temporary Mobile Subscriber Identity (TMS), the access network device identifier, and service fields indicating that the terminal needs to update the SMS status report.

[0065] For example, step S21 above can be understood as follows: First, the access network device receives the location update request message initiated by the target terminal and extracts the terminal identification information therein; then, the access network device uses the terminal identification as an index to query the target file corresponding to the terminal identification in its locally maintained terminal status management module or database; finally, it determines whether there is a target file for the target terminal that has been established locally based on the query result. If the query result is empty, it is determined that the target file is not stored locally, thereby triggering the subsequent target file synchronization process.

[0066] Step S22: If the target file does not exist locally, obtain the target file from the prior access network device through the core network device and store the target file locally.

[0067] In this embodiment of the application, the aforementioned prior access network device is the access network device that last recorded the target terminal's location information before the target terminal accesses the current access network.

[0068] Alternatively, the target file can be obtained from the prior access network equipment via the core network equipment in the following manner:

[0069] Step S221: Send a terminal file request message to the core network device based on the preset synchronization interface, so as to instruct the core network device to send a file synchronization request message to the prior access network device and receive a file synchronization response message carrying the target file from the prior access network device.

[0070] In step S222, the access network device receives and parses the terminal file response message carrying the target file from the core network device, and obtains key fields such as the historical response status and demand status of the target terminal carried in the target file.

[0071] In this embodiment of the application, the aforementioned historical response status is a comprehensive evaluation index derived by the access network device based on the interaction records of the terminal's past SMS status report paging messages. It includes, but is not limited to, SMS success report response rate (which can be represented by the successReportResponseRate field in the target file) and SMS failure report response rate (which can be represented by the failureReportResponseRate field in the target file).

[0072] In this embodiment, the aforementioned demand status is a demand identifier generated based on the target terminal's demand for SMS status reports. It is used to reflect the terminal's demand preference for SMS status reports and can be represented as the ueSmStatusReportReqInd field in the target file. It includes, but is not limited to, a first demand identifier for representing that the terminal only needs an SMS sending failure status report, a second demand identifier for representing that the terminal needs both an SMS sending success status report and an SMS sending failure status report, and a third demand identifier for representing that the terminal does not need either an SMS sending success status report or an SMS sending failure status report. The first demand identifier, the second demand identifier, and the third demand identifier can be represented as 00, 01, and 10 respectively in binary encoding.

[0073] For example, step S221 above can be understood as:

[0074] The first step is for the access network device to send a terminal file request message containing the target terminal identifier and its own access network device identifier to the core network device through a preset synchronization interface (such as the S1-MME interface).

[0075] The second step is that after receiving the file request message from the terminal, the core network equipment queries the previous access network equipment where the target terminal was originally registered and sends a file synchronization request message including the target terminal identifier to it.

[0076] The third step is to first access the network device (which can be represented as the sourceAnId field in the target file) to extract the target file corresponding to the target terminal from the local terminal status management module, and send a file synchronization response message carrying the target file to the core network device;

[0077] Step 4: The core network equipment sends a terminal file response message carrying the target file to the access network equipment;

[0078] Step 5: The access network device receives and parses the terminal file response message to obtain key fields such as the historical response status and demand status of the target terminal carried in the target file.

[0079] Alternatively, to achieve lightweight design, the data structure of the aforementioned target file can be represented as follows:

[0080] {

[0081] "roamingSyncId": "RS-20240601110000-001", —— Unique synchronization identifier

[0082] "ueIdentity": "460139876543210", ——Terminal IMSI

[0083] "sourceAnId": "AN-001", ——Identifier of the first network access device

[0084] "targetAnId": "AN-002", —— Identifier for new access network equipment

[0085] "syncData": {

[0086] "ueSmStatusReportReqInd": "00", ——Terminal Requirements

[0087] "successReportResponseRate": 30, ——Success report response rate (%)

[0088] "failureReportResponseRate": 95, —— Failure report response rate (%)

[0089] "syncTimestamp": 1717234800000 —— Synchronization timestamp (milliseconds)

[0090] }

[0091] }

[0092] The lightweight data structure described above reveals key information such as: the terminal requirement is to send a failed SMS report, the terminal's successful report response rate is 30%, and the first access network device is identified as AN-001.

[0093] It should be noted that, considering the instability of satellite networks, to prevent message loss or changes in terminal status due to excessively long response times, a first preset time period can be set. If the access network device does not receive a terminal file response message from the core network device after the first preset time period, it constructs a target file based on a preset demand state and a preset historical response state, and retransmits the terminal file request message to the core network device based on a preset number of retransmissions and a preset retransmission interval. If a terminal file response message is received from the core network device after retransmitting the terminal file request message, the constructed target file is replaced with the target file carried in the terminal file response message. If the preset number of retransmissions is exceeded and the access network device still does not receive a terminal file response message from the core network device, retransmission is stopped, and the terminal file request message is re-initiated when a location update request message sent by the target terminal is received again.

[0094] Furthermore, considering the dynamic changes in terminal requirements, in order to solve the problem of the lag in the requirement status in the target file stored locally by the access network device, the access network device parses the location update request message initiated by the target terminal, and updates the target file stored locally based on the new requirement status when the location update request message carries the new requirement status of the target terminal for SMS status report, so as to ensure that the subsequent processing method of the target SMS status report paging message is always based on the latest terminal requirements.

[0095] Through the embodiments of this application, when the target file does not exist locally, the core network device obtains and stores the target file locally from the prior access network device that records the last location information of the target terminal. This avoids multiple tentative paging attempts when the terminal accesses a new network device, significantly shortens paging latency, reduces waste of air interface resources, and improves communication efficiency in roaming scenarios.

[0096] Optionally, to reduce the consumption of valuable satellite air interface resources and improve user experience and network service reliability, after the target terminal sends an SMS, in response to the target SMS status report paging message sent by the core network equipment for the target terminal, the access network equipment no longer blindly and unconditionally sends all target SMS status report paging messages sent by the core network equipment. Instead, it determines the processing method for the target SMS status report paging message based on the target profile and the real-time air interface load status. The target profile is used to reflect the target terminal's willingness to receive the target SMS status report, and the real-time air interface load status is used to reflect the current air interface resource shortage of the access network equipment.

[0097] As an alternative solution, Figure 3 This is a schematic diagram of an optional target SMS status report paging message processing flow according to an embodiment of this application, such as... Figure 3 As shown, the access network device can determine the processing method for the target SMS status report paging message based on the target profile and real-time air interface load status as follows:

[0098] Obtain the demand status and target SMS status report paging message from the target file, and determine whether the target terminal has a demand for the target SMS status report paging message: when the demand status is the third demand identifier, the target SMS status report paging message is an SMS success report paging message, and the demand status is the first demand identifier, it is determined that the target terminal has no demand for the target SMS status report paging message; when the demand status is the second demand identifier, the target SMS status report paging message is an SMS failure report paging message, and the demand status is the first demand identifier, it is determined that the target terminal has no demand for the target SMS status report paging message.

[0099] If the target file indicates that the target terminal does not require the target SMS status report paging message, the target SMS status report paging message is directly filtered.

[0100] If the target file indicates that the target terminal requires a target SMS status report paging message, the processing method for the target SMS status report paging message shall be determined based on the following judgment logic:

[0101] If the real-time air interface load status does not meet the preset overload conditions, immediately send a target SMS status report paging message;

[0102] When the real-time air interface load status meets the preset overload conditions, the target SMS status report paging message is added to the message queue. All SMS status report paging messages in the message queue are sent out in descending order of priority. The priority of each SMS status report paging message is determined based on the message arrival time, report type, and the historical response status of the corresponding terminal to the SMS status report.

[0103] For example, the method for determining the priority of the above-mentioned SMS status report paging message can be understood as follows: First, receive the target SMS status report paging message to be processed, and extract its arrival timestamp, report type (including SMS success report and SMS failure report), and the historical response status of the target terminal, adding it to the message queue; then, according to the preset priority sorting rules, perform hierarchical calculations on the three dimensions of arrival time, report type, and historical response status of the SMS status report paging messages corresponding to multiple terminals in the message queue, where the report type is usually given the highest priority to ensure the priority delivery of core services; the historical response status has the second highest priority, and so on. To ensure timely response to reachable terminals, messages with low arrival time are prioritized to maintain a first-in, first-out (FIFO) principle for messages of the same report type and historical response status. Finally, the calculated overall priority is used as the sorting criterion to update the message order in the message queue, ensuring that high-priority messages (i.e., SMS failure report paging messages) take precedence over low-priority messages (i.e., SMS success report paging messages). For paging messages with the same report type, they are sorted according to their historical response status. For paging messages with the same report type and historical response status, those with the same priority and historical response status are arranged in order of arrival time, thus completing the dynamic reconstruction and priority establishment of the message queue.

[0104] Through the embodiments of this application, paging messages without demand are directly filtered based on the terminal demand status in the target file. When the terminal has demand, the real-time air interface load status is combined to immediately send messages when the overload condition is not met, and dynamically send messages according to priority when the overload condition is met. This significantly reduces the transmission of invalid signaling and ensures that high-priority services are delivered in a timely manner in overload scenarios. This improves the utilization rate of air interface resources while ensuring the high reliability of core paging services.

[0105] It should be noted that if any SMS status report paging message in the message queue remains in the queue for more than the second preset time, the SMS status report paging message will be removed from the message queue and a paging timeout message will be sent to the core network equipment.

[0106] After sending the target SMS status report paging message, if no paging response message is received from the target terminal after a third preset time period, the priority of the target SMS status report paging message is determined, and whether to retransmit it is determined based on the priority as follows:

[0107] If the priority is higher than the preset level, the target SMS status report paging message is retransmitted. If no paging response message is received from the target terminal after the third preset time, a paging failure message is sent to the core network equipment.

[0108] If the priority is not higher than the preset level, the retransmission of the target SMS status report paging message will be abandoned.

[0109] Through the embodiments of this application, based on the target SMS status report paging message priority, high-priority messages are retransmitted once and a failure message is sent to the core network if there is still no response, while low-priority messages are directly abandoned for retransmission, thus avoiding low-priority paging messages repeatedly occupying air interface resources and improving the overall availability of the satellite network.

[0110] In response to the characteristics of unstable satellite network links and the wide variety of terminal types covered, preset abnormal events are set for the entire SMS status report delivery process, including: air interface load monitoring failure, missing fields in paging messages sent by core network equipment, and missing terminal files. When a preset abnormal event is detected, to ensure that core services are not interrupted, a fallback decision-making process and a source tracing feedback process can be executed as follows:

[0111] The fallback decision-making process includes: determining the fallback rule corresponding to the abnormal event type from the preset strategy table, and determining the processing method of the target SMS status report paging message based on the fallback rule. The fallback rule is used to prioritize the delivery of the SMS sending failure report paging message.

[0112] For example, Table 1 shows the correspondence between the abnormal event types and the fallback rules in the preset strategy table:

[0113] Table 1

[0114]

[0115] The source tracing and feedback process includes sending an alarm message to the core network equipment or operation and maintenance system, which includes the type of abnormal event, the time of the abnormality, and the fault identifier, in order to trigger the fault location of the abnormal event.

[0116] Through the embodiments of this application, when a preset abnormal event is detected, a fallback decision process that prioritizes ensuring the issuance of failure report paging and a source tracing feedback process that includes the abnormal type and fault identifier are executed in parallel. In abnormal scenarios such as unstable links or missing files, the continuity of core business is ensured and the efficiency of fault location is improved.

[0117] Through the steps described in this embodiment, the air interface load status of the access network device is monitored, and when the air interface load status meets preset conditions, a load status message is sent to the core network device. This breaks down the information silos between the core network device and the access network device. The core network device can dynamically adjust the number of paging messages sent according to the air interface load status of the access network device, effectively suppressing the surge in paging messages caused by concentrated terminal access, avoiding long-term overload of air interface resources of the access network device, and improving the overall resource utilization of the Tiantong satellite network. In response to the location update request message initiated by the target terminal, the target file corresponding to the target terminal is determined, avoiding the use of trial paging (i.e., multiple trial-and-error paging) due to the lack of target files for the terminal, which leads to a significant increase in paging latency and signaling overhead. Through the target file, the terminal's response habits and demand preferences for different types of reports are recorded. The access network device performs paging management based on the target file, which can accurately determine the service type that the terminal really needs, avoiding sending invalid paging to terminals that do not need or cannot respond, and reducing unnecessary air interface resources. Source occupancy; after the target terminal sends an SMS, in response to the target SMS status report paging message sent by the core network equipment, the processing method for the target SMS status report paging message is determined based on the target profile and real-time air interface load status. When the terminal's historical response rate is low and the terminal has no demand, low-priority SMS success report paging messages are directly filtered out, avoiding invalid transmission on the high-latency, high-loss satellite link and saving air interface bandwidth. When the air interface load is overloaded, the target SMS status report paging message is placed in the message queue and sent after the load is restored, avoiding packet loss or retransmission caused by forced sending and improving the transmission success rate. For high-priority failure reports, regardless of the load, priority is given to immediate sending, ensuring that users can know the reason for SMS sending failure in time, meeting the timeliness requirements of core information in emergency communication scenarios. Through dual-dimensional decision-making, both user business needs and network carrying capacity are considered, enabling the satellite network to prioritize core services when resources are scarce and improve user experience when resources are abundant.

[0118] Example 2

[0119] This application proposes a paging management method for SMS status reporting, which can be applied to, for example... Figure 4 The communication system shown, such as Figure 4 As shown, the communication system 400 can be applied to terrestrial communication scenarios or satellite-ground integrated communication scenarios.

[0120] Specifically, the aforementioned communication system 400 includes at least: a core network device 401, an access network device 402, and a target terminal 403, wherein:

[0121] The core network device 401 is used to send a target SMS status report paging message to the access network device 402 after the target terminal 403 sends an SMS message;

[0122] Access network device 402 is used to obtain its own air interface load status within a preset sampling period and send a load status message to core network device 401 based on the air interface load status; respond to the location update request message initiated by target terminal 403 and determine the target file corresponding to target terminal 403; receive target SMS status report paging message sent by core network device 401, and determine the processing method of target SMS status report paging message based on air interface load status and target file, wherein the processing method includes one of the following: immediate delivery, delayed delivery, or direct filtering.

[0123] The target terminal 403 is used to initiate a location update request message to the access network device 402 and send a text message to the core network device 401.

[0124] The aforementioned access network device 402 is a key network node in the satellite network responsible for connecting ground core network equipment and terminals. It includes, but is not limited to, the access network infrastructure centered on the earth station, the radio resource controller that performs radio resource control, and the network entity responsible for air interface resource scheduling and paging management.

[0125] The aforementioned terminal 403 includes, but is not limited to, devices configured to receive / transmit communication signals via wired connections, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM radio transmitters; and / or other terminal devices; and / or Internet of Things (IoT) devices. Terminal devices configured to communicate via wireless interfaces may be referred to as "wireless communication terminals," "wireless terminals," or "mobile terminals." Examples of mobile terminals include, but are not limited to, satellite or cellular phones; personal communications system (PCS) terminals that can combine cellular radiotelephony with data processing, fax, and data communication capabilities; PDAs that may include radiotelephones, pagers, Internet / intranet access, web browsers, notebooks, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or handheld receivers or other electronic devices that include radiotelephone transceivers. Terminal equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile devices, user terminals, terminals, wireless communication equipment, user agents, or user equipment. Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in future PLMNs, etc.

[0126] According to an embodiment of this application, a paging management device for SMS status reporting is also provided for implementing the paging management method for SMS status reporting in Embodiment 1, such as... Figure 5 As shown, the paging management device for the SMS status report includes at least: a load monitoring module 51, a file management module 52, and a paging management module 53, wherein:

[0127] The load monitoring module 51 is used to monitor the air interface load status of the access network device and send a load status message to the core network device when the air interface load status meets the preset conditions. The load status message is used to trigger the core network device to adjust the strategy of sending SMS status report paging messages to the access network device.

[0128] The file management module 52 is used to respond to the location update request message initiated by the target terminal and determine the target file corresponding to the target terminal. The target file includes the target terminal's request status for SMS status reports and its historical response status.

[0129] The paging management module 53 is used to respond to the target SMS status report paging message sent by the core network equipment after the target terminal sends an SMS. Based on the target file and the real-time air interface load status, it determines the processing method for the target SMS status report paging message. The processing method includes one of the following: immediate delivery, delayed delivery, or direct filtering.

[0130] The following section explains the functions of each module of the paging management device for SMS status reports, based on a specific implementation process.

[0131] Optionally, the aforementioned load monitoring module is further configured to send a load status message to the core network device when the air interface load status meets preset conditions in the following manner: when the air interface load status changes from not meeting the preset overload conditions to meeting the preset overload conditions, a load warning message is sent to the core network device, wherein the load warning message is used to trigger the core network device to reduce the number of low-priority SMS status report paging messages sent to the access network device based on a preset SMS status report paging message sending strategy; when the air interface load status changes from meeting the preset overload conditions to not meeting the preset overload conditions, a load recovery message is sent to the core network device, wherein the load recovery message is used to trigger the core network device to restore the preset SMS status report paging message sending strategy.

[0132] Optionally, the aforementioned file management module is further configured to respond to a location update request message initiated by the target terminal and determine the target file corresponding to the target terminal in the following manner: upon receiving a location update request message sent by the target terminal, querying whether a target file is stored locally; if no target file exists locally, obtaining the target file from the prior access network device through the core network device and storing the target file locally, wherein the prior access network device is the access network device that last recorded the target terminal's location information before the target terminal accessed the current access network.

[0133] Optionally, the aforementioned file management module is further configured to obtain the target file from the prior access network device through the core network device in the following manner: sending a terminal file request message to the core network device based on a preset synchronization interface, so as to instruct the core network device to send a file synchronization request message to the prior access network device and receive a file synchronization response message carrying the target file from the prior access network device; and receiving a terminal file response message carrying the target file from the core network device.

[0134] Optionally, if no terminal file response message is received from the core network device after a first preset time period, a target file is constructed based on a preset demand state and a preset historical response state, and the terminal file request message is retransmitted to the core network device based on a preset number of retransmissions and a preset retransmission time interval; if a terminal file response message is received from the core network device after retransmitting the terminal file request message, the constructed target file is replaced with the target file carried in the terminal file response message.

[0135] Optionally, the aforementioned file management module is also used to update the locally stored target file based on the new demand status when the location update request message carries a new demand status of the target terminal for the SMS status report.

[0136] Optionally, the paging management module described above is further configured to determine the processing method for target SMS status report paging messages based on the target profile and real-time air interface load status in the following ways: when the target profile indicates that the target terminal has no need for the target SMS status report paging message, directly filter the target SMS status report paging message; when the target profile indicates that the target terminal has a need for the target SMS status report paging message, continue to determine the processing method for the target SMS status report paging message based on the following judgment logic: when the real-time air interface load status does not meet the preset overload condition, immediately send the target SMS status report paging message; when the real-time air interface load status meets the preset overload condition, add the target SMS status report paging message to the message queue, wherein all SMS status report paging messages in the message queue are sent sequentially from high to low according to their corresponding priorities, and the priority of each SMS status report paging message is determined based on the message arrival time, report type, and the historical response status of the corresponding terminal to the SMS status report.

[0137] Optionally, if any SMS status report paging message in the message queue remains in the queue for more than a second preset time, the SMS status report paging message is removed from the message queue, and a paging timeout message is sent to the core network equipment.

[0138] Optionally, the above-mentioned device is further configured to, after sending a target SMS status report paging message, if no paging response message is received from the target terminal after a third preset time period, determine the priority of the target SMS status report paging message; if the priority is higher than a preset level, retransmit the target SMS status report paging message; if no paging response message is received from the target terminal after a third preset time period, send a paging failure message to the core network equipment; if the priority is not higher than a preset level, abandon the retransmission of the target SMS status report paging message.

[0139] Optionally, the above-mentioned device is further configured to execute a fallback decision-making process and a source tracing feedback process when a preset abnormal event is detected; wherein, the preset abnormal event includes at least one of the following: air interface load monitoring failure, missing fields in paging messages issued by core network equipment, and missing terminal files; the fallback decision-making process includes: determining the fallback rule corresponding to the abnormal event type from a preset policy table, and determining the processing method of the target SMS status report paging message based on the fallback rule, wherein the fallback rule prioritizes the issuance of paging messages of type SMS sending failure report; the source tracing feedback process includes: sending an alarm message including the abnormal event type, the time of abnormal occurrence, and the fault identifier to the core network equipment or operation and maintenance system to trigger fault location of the abnormal event.

[0140] It should be noted that each module in the paging management device for SMS status reporting in this embodiment corresponds one-to-one with each implementation step of the paging management method for SMS status reporting in Embodiment 1. Since Embodiment 1 has been described in detail, some details not shown in this embodiment can be referred to Embodiment 1, and will not be elaborated further here.

[0141] Example 3

[0142] According to an embodiment of this application, a computer program product is also provided, which includes a computer program, wherein when the computer program is executed by a processor, it implements the paging management method for SMS status reporting in Embodiment 1.

[0143] According to an embodiment of this application, a non-volatile storage medium is also provided, which includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the paging management method for SMS status reporting in Embodiment 1 by running the computer program.

[0144] According to an embodiment of this application, a processor is also provided for running a computer program, wherein the computer program executes the paging management method for SMS status reporting in Embodiment 1 when it runs.

[0145] According to an embodiment of this application, an electronic device is also provided, comprising: a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the paging management method for SMS status reporting in Embodiment 1 through the computer program.

[0146] Specifically, the computer program executes the following steps during runtime: It monitors the air interface load status of the access network device and, when the air interface load status meets preset conditions, sends a load status message to the core network device. This load status message triggers the core network device to adjust its strategy for sending SMS status report paging messages to the access network device. In response to a location update request message initiated by the target terminal, it determines the target file corresponding to the target terminal. The target file includes the target terminal's demand status for SMS status reports and its historical response status. After the target terminal sends an SMS message, in response to a target SMS status report paging message sent by the core network device for the target terminal, it determines the processing method for the target SMS status report paging message based on the target file and the real-time air interface load status. The processing method includes one of the following: immediate delivery, delayed delivery, or direct filtering.

[0147] As an alternative implementation, the above-mentioned electronic device may exist in the form of a mobile terminal, a computer terminal, or a similar computing device. Figure 6 A hardware block diagram of an electronic device for implementing a paging management method for SMS status reporting is shown. Figure 6 As shown, the electronic device 60 may include one or more (shown as 602a, 602b, ..., 602n) processors 602 (processors 602 may include, but are not limited to, processing devices such as microprocessors or programmable logic devices), a memory 604 for storing data, and a transmission device 606 for communication functions. In addition, it may also include: a display, an input / output interface, a universal serial bus port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 6 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, electronic device 60 may also include components that are more... Figure 6 The more or fewer components shown, or having the same Figure 6 The different configurations shown.

[0148] It should be noted that the aforementioned one or more processors 602 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element of the electronic device 60. As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0149] The memory 604 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the paging management method for SMS status reporting in this embodiment. The processor 602 executes various functional applications and data processing by running the software programs and modules stored in the memory 604, thereby realizing the aforementioned paging management method for SMS status reporting. The memory 604 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. In some instances, the memory 604 may further include memory remotely located relative to the processor 602, and these remote memories can be connected to the electronic device 60 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0150] The transmission device 606 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the electronic device 60. In one example, the transmission device 606 includes a network adapter that can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 606 may be a radio frequency module used for wireless communication with the Internet.

[0151] The display can be, for example, a touchscreen LCD display that allows the user to interact with the user interface of the electronic device 60.

[0152] The sequence numbers of the above embodiments are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0153] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0154] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0155] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0156] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0157] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory, random access memory, portable hard drive, magnetic disk, or optical disk.

[0158] The above are merely preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A paging management method for SMS status reports, applied to access network equipment, characterized in that, include: Monitor the air interface load status of the access network device, and when the air interface load status meets the preset conditions, send a load status message to the core network device, wherein the load status message is used to trigger the core network device to adjust the strategy of sending SMS status report paging messages to the access network device; In response to a location update request message initiated by a target terminal, a target file corresponding to the target terminal is determined, wherein the target file includes the target terminal's demand status for SMS status reports and its historical response status; After the target terminal sends an SMS message, in response to the target SMS status report paging message sent by the core network device for the target terminal, the processing method for the target SMS status report paging message is determined based on the target file and the real-time air interface load status. The processing method includes one of the following: immediate delivery, delayed delivery, or direct filtering.

2. The method according to claim 1, characterized in that, When the air interface load status meets preset conditions, a load status message is sent to the core network equipment, including: When the air interface load state changes from not meeting the preset overload condition to meeting the preset overload condition, a load warning message is sent to the core network device. The load warning message is used to trigger the core network device to reduce the number of low-priority SMS status report paging messages sent to the access network device based on the preset SMS status report paging message sending strategy. When the air interface load status changes from meeting the preset overload condition to not meeting the preset overload condition, a load recovery message is sent to the core network device, wherein the load recovery message is used to trigger the core network device to restore the preset SMS status report paging message delivery strategy.

3. The method according to claim 1, characterized in that, In response to a location update request message initiated by the target terminal, the target file corresponding to the target terminal is determined, including: Upon receiving a location update request message from the target terminal, check whether the target file is stored locally. If the target file does not exist locally, the core network device obtains the target file from the prior access network device and stores the target file locally. The prior access network device is the access network device that last recorded the location information of the target terminal before the target terminal accesses the current access network.

4. The method according to claim 3, characterized in that, Obtaining the target file from the prior access network device through the core network device includes: Based on a preset synchronization interface, a terminal file request message is sent to the core network device to instruct the core network device to send a file synchronization request message to the prior access network device and to receive a file synchronization response message carrying the target file from the prior access network device. Receive the terminal file response message carrying the target file from the core network device.

5. The method according to claim 4, characterized in that, The method further includes: If the terminal file response message is not received from the core network device after a first preset time period, a target file is constructed based on the preset demand status and preset historical response status, and the terminal file request message is retransmitted to the core network device based on the preset number of retransmissions and the retransmission time interval. If a terminal file response message is received from the core network device after retransmitting the terminal file request message, the constructed target file is replaced based on the target file carried in the terminal file response message.

6. The method according to claim 3, characterized in that, include: If the location update request message carries a new requirement status for the target terminal's SMS status report, the target file stored locally is updated based on the new requirement status.

7. The method according to claim 1, characterized in that, The processing method for the target SMS status report paging message is determined based on the target file and real-time air interface load status, including: If the target file indicates that the target terminal does not require the target SMS status report paging message, the target SMS status report paging message is directly filtered. If the target file indicates that the target terminal requires the target SMS status report paging message, the processing method for the target SMS status report paging message is further determined based on the following judgment logic: If the real-time air interface load status does not meet the preset overload conditions, the target SMS status report paging message shall be sent immediately. When the real-time air interface load status meets the preset overload conditions, the target SMS status report paging message is added to the message queue. All SMS status report paging messages in the message queue are sent out in descending order of priority. The priority of each SMS status report paging message is determined based on the message arrival time, report type, and the historical response status of the corresponding terminal to the SMS status report.

8. The method according to claim 7, characterized in that, The method further includes: If any SMS status report paging message in the message queue remains in the queue for more than a second preset time, the SMS status report paging message is removed from the message queue, and a paging timeout message is sent to the core network device.

9. The method according to claim 1, characterized in that, The method further includes: If, after the target SMS status report paging message is sent, no paging response message is received from the target terminal after a third preset time period, the priority of the target SMS status report paging message is determined. If the priority is higher than the preset level, the target SMS status report paging message is retransmitted. If no paging response message is received from the target terminal after a third preset time, a paging failure message is sent to the core network device. If the priority is not higher than the preset level, the retransmission of the target SMS status report paging message is abandoned.

10. The method according to claim 1, characterized in that, The method further includes: When a pre-defined abnormal event is detected, a fallback decision-making process and a source tracing and feedback process are executed. The preset abnormal events include at least one of the following: air interface load monitoring failure, missing fields in paging messages sent by core network equipment, and missing terminal files; The fallback decision-making process includes: determining the fallback rule corresponding to the abnormal event type from the preset strategy table, and determining the processing method of the target SMS status report paging message based on the fallback rule. The fallback rule prioritizes the delivery of the SMS sending failure report paging message. The source tracing and feedback process includes sending an alarm message to the core network equipment or operation and maintenance system, which includes the type of abnormal event, the time of the abnormal event, and the fault identifier, to trigger the fault location of the abnormal event.

11. A paging management device for SMS status reporting, characterized in that, include: The load monitoring module is used to monitor the air interface load status of the access network device, and when the air interface load status meets the preset conditions, it sends a load status message to the core network device. The load status message is used to trigger the core network device to adjust the strategy of sending SMS status report paging messages to the access network device. The file management module is used to respond to a location update request message initiated by a target terminal and determine the target file corresponding to the target terminal, wherein the target file includes the target terminal's request status for SMS status reports and its historical response status. The paging management module is used to respond to the target SMS status report paging message sent by the core network device after the target terminal sends an SMS, and determine the processing method of the target SMS status report paging message based on the target file and the real-time air interface load status. The processing method includes one of the following: immediate delivery, delayed delivery, and direct filtering.

12. A computer program product, characterized in that, include: A computer program, wherein when executed by a processor, the computer program implements the paging management method for SMS status reporting as described in any one of claims 1 to 10.

13. An electronic device, characterized in that, include: A memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute, via the computer program, the paging management method for SMS status reporting as described in any one of claims 1 to 10.

Images