Short message management method and device, electronic equipment and nonvolatile storage medium

Abstract

The application discloses a short message management method and device, electronic equipment and a nonvolatile storage medium. The method comprises the following steps: receiving a short message service request message sent by a terminal device, and determining an access type of the terminal device, wherein the short message service request message comprises a short message status report request identifier; forwarding the short message service request message to a short message center, and receiving a status report value returned by the short message center, wherein the short message center is used for processing the short message service request message and generating a corresponding processing result, and the status report value is used for representing a state category corresponding to the processing result; determining an execution strategy of short message status report issuing according to the access type and the status report value, and sending the short message status report to the terminal device according to the execution strategy. The application solves the technical problems of complex short message status report issuing process and satellite resource occupation caused by signaling interaction in the related art.

Description

Technical Field

[0001] This application relates to the field of satellite communication technology, and more specifically, to a text messaging management method, apparatus, electronic device, and non-volatile storage medium. Background Technology

[0002] With the rapid development of high-throughput satellite communication technology and low-Earth orbit satellite constellations such as Starlink and OneWeb, satellite networks have significantly improved their communication capabilities in terms of speed, latency, and reliability. They can complement and coordinate with terrestrial networks, and in some application scenarios, they can even replace terrestrial networks. In a satellite-terrestrial converged network architecture, when a terminal interacts with the network via Short Message Service (SMS), it follows the SMS signaling and service procedures defined in the 3GPP standard. Specifically, when a mobile terminal (MS) initiates a Short Message Sending (MO SMS) procedure, if it wants to know the message processing result, it will carry a Short Message Status Report Request identifier (TP-SRR bit set to 1) in the signaling. After receiving this request, the Short Message Service Center (SMSC), after completing the submission, storage, and forwarding of the SMS, will proactively initiate a Short Message Receiving (MT SMS) procedure to the terminal that initiated the MO based on this identifier. It will then send an SMS Status Report to the terminal through paging and the MT procedure, containing the processing result (such as successful delivery, blocked, service rejected, etc.).

[0003] In existing terrestrial mobile communication standards, the SMS status report delivery mechanism primarily relies on terminal-initiated requests triggering network-side responses. However, in satellite-terrestrial converged networking scenarios, satellite networks possess characteristics such as wide coverage, high mobility, multiple coverage layers for cell information, and instantaneous nature, while satellite link resources are relatively limited. If the terrestrial network processing mechanism is directly adopted, regardless of the specific content of the SMS status report, the network side will execute MT SMS and Paging procedures to deliver the report to the terminal via the satellite link. This leads to unnecessary signaling interactions consuming significant amounts of satellite radio resources, increasing the complexity of signaling interactions, and reducing resource utilization efficiency. Especially when the terminal is in a satellite access scenario, frequent status report delivery significantly increases satellite resource overhead, failing to meet the resource-saving and efficient interaction requirements of satellite-terrestrial converged networks.

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

[0005] This application provides a text message management method, device, electronic device, and non-volatile storage medium to at least solve the technical problems of complex text message status report delivery process and signaling interaction occupying satellite resources in related technologies under satellite-ground integrated networks.

[0006] According to one aspect of the embodiments of this application, a text message management method is provided, comprising: receiving a text message service request message sent by a terminal device and determining the access type of the terminal device, wherein the text message service request message includes a text message status report request identifier, the text message status report request identifier is used to request the network side to return a text message status report to the terminal device after the text message processing is completed, and the access type is used to characterize the link type used by the terminal device to access the network; forwarding the text message service request message to a short message service center and receiving a status report value returned by the short message service center, wherein the short message service center is used to process the text message service request message and generate a corresponding processing result, and the status report value is used to characterize the status category corresponding to the processing result; determining an execution strategy for sending the text message status report based on the access type and the status report value, and sending the text message status report to the terminal device according to the execution strategy.

[0007] Optionally, the access type includes: satellite link access and terrestrial link access; the execution strategy for sending SMS status reports is determined based on the access type and the status report value, including: when the access type is terrestrial link access, sending SMS status reports directly to the terminal device through the current access network; when the access type is satellite link access, determining the notification priority corresponding to the status report value, and determining the execution strategy for sending SMS status reports based on the notification priority, wherein the notification priority is used to characterize the urgency of the service processing result indicated by the status report value.

[0008] Optionally, the notification priority includes: a first priority and a second priority, wherein the first priority is higher than the second priority; the execution strategy for issuing SMS status reports based on the notification priority includes: when the notification priority corresponding to the status report value is the first priority, directly issuing an SMS status report to the terminal device through the current access network, wherein the status report value of the first priority includes at least one of the following: SMS forwarding blocked, service denied; when the notification priority corresponding to the status report value is the second priority, temporarily suspending the issuance of SMS status reports to the terminal device, wherein the status report value of the second priority includes at least one of the following: SMS successfully delivered, SMS sent to the destination address but not confirmed to have arrived, SMS replaced, target address terminal busy, target address no response, specified service invalid.

[0009] Optionally, temporarily suspending the delivery of SMS status reports to terminal devices includes: caching the SMS status reports in the core network and recording the timestamp of the SMS service request message corresponding to the SMS status reports.

[0010] Optionally, after temporarily suspending the delivery of SMS status reports to terminal devices, the method further includes: monitoring the access type of the terminal device; and proactively delivering a cached SMS status report to the terminal device when the access type of the terminal device is detected to have switched from satellite link access to terrestrial link access. The SMS status report carries a receiving timestamp, which is used to assist the terminal device in identifying the SMS service request message corresponding to the SMS status report.

[0011] Optionally, the method further includes: receiving network activity signaling initiated by the terminal device through a terrestrial base station, wherein the network activity signaling includes at least one of the following: registration request, location update request, service request, periodic registration update; extracting access type indication information from the network activity signaling, and determining that the access type of the terminal device is switched from satellite link access to terrestrial link access when the access type indication information indicates terrestrial link access.

[0012] According to another aspect of the embodiments of this application, another SMS management method is provided, including: sending an SMS service request message to the network side, wherein the SMS service request message includes an SMS status report request identifier, which is used to request the network side to return an SMS status report to the terminal device after the SMS processing is completed; receiving an SMS status report issued by the network side after determining an execution policy based on the status report value and the access type of the terminal device, wherein the access type is used to characterize the link type used by the terminal device to access the network, and the status report value is used to characterize the status category corresponding to the processing result generated by the network side in processing the SMS service request message; and determining whether to continue sending SMS service request messages to the network side through the current access network based on the status report value in the SMS status report and the current access type of the terminal device.

[0013] Optionally, determining whether to continue sending SMS service request messages to the network side through the current access network based on the status report value in the SMS status report and the current access type of the terminal device includes: stopping the sending of SMS service request messages to the network side through the satellite link when the status report value indicates that SMS forwarding is blocked or service is rejected, and the access type is satellite link access.

[0014] According to another aspect of the embodiments of this application, a text message management device is also provided, comprising: an access type determination module, configured to receive a text message service request message sent by a terminal device and determine the access type of the terminal device, wherein the text message service request message includes a text message status report request identifier, the text message status report request identifier is used to request the network side to return a text message status report to the terminal device after the text message processing is completed, and the access type is used to characterize the link type used by the terminal device to access the network; a report value acquisition module, configured to forward the text message service request message to the short message center and receive the status report value returned by the short message center, wherein the short message center is used to process the text message service request message and generate a corresponding processing result, and the status report value is used to characterize the status category corresponding to the processing result; and a sending strategy determination module, configured to determine the execution strategy for sending the text message status report based on the access type and the status report value, and send the text message status report to the terminal device according to the execution strategy.

[0015] According to another aspect of the embodiments of this application, an electronic device is also provided, including: a memory and a processor, the processor being configured to run a program stored in the memory, wherein the program executes a text message management method during runtime.

[0016] According to another aspect of the embodiments of this application, a non-volatile storage medium is also provided, the non-volatile storage medium including a stored computer program, wherein the device where the non-volatile storage medium is located executes a text message management method by running the computer program.

[0017] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps of a text message management method.

[0018] In this embodiment, a receiving terminal device sends an SMS service request message, and the access type of the terminal device is determined. The SMS service request message includes an SMS status report request identifier, which requests the network side to return an SMS status report to the terminal device after SMS processing is completed. The access type characterizes the link type used by the terminal device to access the network. The SMS service request message is forwarded to the Short Message Service Center (SMS Center), and the status report value returned by the SMS Center is received. The SMS Center processes the SMS service request message and generates corresponding processing results. The status report value characterizes the status category corresponding to the processing result. Based on the access... The system determines the execution strategy for sending SMS status reports based on the type and status report value, and sends SMS status reports to terminal devices according to the execution strategy. By making dynamic decisions based on the access type and status report value of the terminal device, it selectively sends SMS status reports immediately or caches and triggers delayed sending in satellite link access scenarios. This achieves the goal of reducing unnecessary SMS status report sending processes and paging signaling interactions in satellite access scenarios while ensuring timely feedback of critical business status. This effectively saves satellite radio resource overhead and solves the technical problems of complex SMS status report sending processes and signaling interactions occupying satellite resources in satellite-ground integrated networks. Attached Figure Description

[0019] 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:

[0020] Figure 1 This is a schematic diagram of the protocol layer architecture of a short message service in a related art according to an embodiment of this application;

[0021] Figure 2 This is a schematic diagram of a mobile station initiating SMS communication in a related technology according to an embodiment of this application;

[0022] Figure 3 This is a schematic diagram of a mobile station termination process in which the SMS center returns a status report to the originating terminal based on a status report request, according to an embodiment of this application.

[0023] Figure 4 This is a hardware structure block diagram of a computer terminal (or electronic device) for implementing a method for SMS management according to an embodiment of this application;

[0024] Figure 5 This is a schematic diagram of a method flow for SMS management applied on the network side according to an embodiment of this application;

[0025] Figure 6 This is a schematic diagram of a satellite-ground integrated networking architecture provided according to an embodiment of this application;

[0026] Figure 7 This is a schematic diagram of a method flow for SMS management in a satellite-ground converged network according to an embodiment of this application;

[0027] Figure 8 This is a schematic diagram of a method flow for SMS management applied on the terminal side according to an embodiment of this application;

[0028] Figure 9 This is a schematic diagram of the structure of a text message management 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., in the specification, claims, and accompanying 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] With the rapid development of high-throughput satellite communication technology and low-Earth orbit satellite constellations represented by Starlink and OneWeb, satellite networks have significantly improved their communication capabilities in terms of speed, latency, and reliability. They can complement and coordinate with terrestrial networks, and in some application scenarios, they can even replace terrestrial networks. However, there are still significant differences between satellite networks and terrestrial networks, such as dynamic networking, instantaneity, and limited resources. Therefore, in the context of satellite-terrestrial converged networking, the existing technical solutions for terrestrial networks still need further optimization to be applicable to both satellite access and terrestrial access scenarios.

[0032] In relevant mobile communication standards, the Short Message Service (SMS) technology related to this solution is mainly defined in the 3GPP TS 23.040 specification. This specification details the signaling definition and service flow of SMS. The description of Status Report Capabilities states that the Short Message Service Center (SC) has the ability to notify the Mobile Station (MS) of the status of previously sent Mobile Originated Short Messages. This status includes successful delivery to the destination Short Message Entity (SME), or the SMS Center's inability to forward the message to the destination Short Message Entity. The latter may be a permanent error or a temporary error. Permanent errors include validity period expired and invalid destination address, while temporary errors include SC-SME connection being down and the destination entity being temporarily unavailable. This function is implemented by the SMS center returning a Status Report TPDU (SMS-STATUS-REPORT) to the originating mobile station after the SMS status is determined. This status report can be triggered by a Status Report Request in the SMS sent by the mobile station, and during transmission, it is treated by the SMS center as an SMS Deliver TPDU, for example, using the same paging mechanism (Alerting Mechanism). It should be noted that the status reporting capability is optional, and whether to provide it is decided by the SMS center operator.

[0033] At the protocol architecture level, the protocol layer structure of the short message service is as follows: Figure 1As shown, this includes the Short Message Application Layer (SM-AL), Short Message Transfer Layer (SM-TL), Short Message Relay Layer (SM-RL), and Short Message Lower Layer (SM-LL). The network elements involved include the Short Message Service Center (SMS-SC), SMS Gateway Mobile Switching Center / SMS Interoperability Mobile Switching Center (SMS-GMSC / SMS-IWMSC), Short Message Router (SMS Router), Mobile Switching Center / Visitor Location Register or Serving General Packet Radio Service Support Node (MSC / VLR or SGSN), and Mobile Station (MS). The SMS Router is an optional functional entity, used only in Mobile Terminated (MT) scenarios. The Short Message Transfer Layer provides services to the Short Message Application Layer, supporting the transmission and reception of short messages, as well as the reporting and feedback of early transmission requests. The Short Message Service (SMS) transport layer includes six types of Transport Protocol Data Units (PDUs): SMS Deliver Unit (SMS-DELIVER) for transmitting short messages from the SMS Center to the mobile station; SMS Deliver Report Unit (SMS-DELIVER-REPORT) for reporting failure reasons and confirmation information; SMS Submit Unit (SMS-SUBMIT) for sending short messages from the mobile station to the SMS Center; SMS Submit Report Unit (SMS-SUBMIT-REPORT) for confirming SMS submission or SMS commands; SMS Status Report Unit (SMS-STATUS-REPORT) for transmitting status reports from the SMS Center to the mobile station; and SMS Command Unit (SMS-COMMAND) for sending commands from the mobile station to the SMS Center.

[0034] The fifth bit of the first byte of the SMS-DELIVER unit contains a Status Report Indication field (TP-Status-Report-Indication, TP-SRI). When this bit is 1, it indicates that a status report should be returned to the SMS entity (SME). Correspondingly, the fifth bit of the first byte of the SMS-SUBMIT unit and the SMS-COMMAND unit contains a Status Report Request field (TP-Status-Report-Request, TP-SRR). When this bit is 1, it indicates that a status report is requested. See the table below.

[0035]

[0036] As shown in the table above, in the basic elements of the mobile station termination data (RP-MT-DATA), the Message Type Indicator (RP-MTI) field is used to distinguish whether the transport protocol data unit is a text message delivery or a text message status report. When the value of this field is 0, it indicates a text message delivery (SMS Deliver), and when the value is 1, it indicates a text message status report (SMS Status Report). The Home Location Register (HLR) can use this to distinguish between them in order to avoid implementing a filtering mechanism based on the originating short message entity address (RP-SMEA) during the transmission of text message status reports. In addition, RP-MT-DATA also contains other basic elements, such as the Priority Request parameter (RP-PRI), which indicates whether SMS transmission should be stopped when the originating SMS center address is already included in the Message Waiting in the SC (MWD); the More Messages to Send parameter (RP-MMS), which indicates whether there are more messages waiting to be sent in the SMS center; the Originating Address (RP-OA), which is the address of the originating SMS center; the Destination Address (RP-DA), which is the address of the destination mobile station; and the User Data (RP-UD), which contains the Transport Protocol Data Unit.

[0037] Short Message Service (SMS) comprises three fundamental procedures. The Short Message Mobile Terminated (STM) procedure covers all operations required to transmit a short message or status report from the SMS center to the mobile station, as well as the operation of returning a message delivery attempt result report to the SMS center. The procedures for providing SMS service via Generic IP CAN are described in 3GPP TS 23.204.

[0038] Based on the above standards, the triggering process for a mobile station originating terminal to receive SMS status reports in related technologies. Figure 2 This demonstrates the process of a mobile station initiating an SMS message, such as... Figure 2 As shown, after the terminal (UE) triggers a service request and receives an acceptance response, it transmits the SMS content via uplink non-access stratum signaling (Uplink NAS). This message carries a status report request identifier (TP-SRI). The access and mobility management function (AMF) forwards the SMS content to the short message service function (SMF) through the Nsmf_SMService_UplinkSMS interface. The SMF then forwards the mobile station's originating SMS (Forward MO) to the SMS center (SC) through the SMS gateway mobile switching center (SMS-GMSC). After completing the message exchange or attempt (Msg xfer / rpt), the SMS center submits a report to the SMF. This report is transmitted back to the terminal via downlink non-access stratum signaling (Downlink NAS) through the AMF. The terminal then returns an acknowledgment (CP ack) via uplink non-access stratum signaling, completing the entire mobile station originating process.

[0039] Figure 3 This demonstrates the mobile station termination process where the SMS center returns a status report to the originating terminal based on a status report request, such as... Figure 3As shown, after the SMS center completes message exchange, the SMS gateway mobile switching center sends a Send Routing Info for SM request to the Home Subscriber Server (UDM). After obtaining the routing information, the SMF requests the AMF to trigger terminal reachability via Namf_MT_EnableReachabilityRequest. The AMF executes the Paging / Service Request procedure, establishes a connection with the terminal, and transmits the SMS body to the terminal via downlink non-access stratum signaling through the Namf_Communication_N1N2MessageTransfer interface. Upon receiving the message, the terminal returns an acknowledgment and simultaneously sends a Delivery Report (RPT) via uplink non-access stratum signaling. This report is forwarded to the SMS center by the SMF (Delivery Report), completing the status report feedback. The RP-MTI indicates that the message type is a Status Report, distinguishing it from ordinary SMS delivery.

[0040] Specifically, when a mobile station initiates a SMS Mobile Station Origination (SMS MO) procedure, it carries an SMS Status Report Request identifier. The SMS center sets the Status Report Request bit value to 1 (TP-SRR bit value is set to 1) and initiates an SMS Mobile Station Termination (SMS MT) procedure to return the SMS Status Report to the initiating mobile station. The SMS status report contains multiple fields, including the Short Message Service Center (SMSC) number, Transport Protocol Data Unit Header (TP-DUH), Message Reference (TP-MR), Recipient Address (TP-RA), Service Center Time Stamp (TP-SCTS), Discharge Time (TP-DT), Status Code (TP-ST), Parameter Indicator (TP-PI), Protocol Identifier (TP-PID), Data Coding Scheme (TP-DCS), User Data Length (TP-UDL), and User Data (TP-UD). The status code indicates the specific status of the SMS message.

[0041] The specific meanings of status codes (TP-ST) cover a variety of processing results, including successful transmission and receipt by the recipient (0x00: successful transmission, successful receipt by the recipient), the SMS message has been sent to the destination address by the SMS center but it cannot be confirmed that it has arrived (0x01: the SMS message has been sent to the destination address by the SMSC, but it cannot be confirmed that it has arrived), the SMS message has been replaced by the SMS center (0x02: the SMS message has been replaced by the SMSC), forwarding is blocked (0x20: blocked), the destination address terminal is busy (0x21: the destination address terminal is busy), the destination address does not respond (0x22: the destination address does not respond), service is denied (0x23: service is denied), and the specified service is invalid (0x24: the specified service is invalid), etc.

[0042] In the standard business process of related technologies, when a terminal device initiates a Short Message Service (MO SMS) and requests a status report, regardless of the final processing result, the network side follows the existing standard process, performing a Short Message Service (MT SMS) reception and paging process via satellite link to send a short message status report containing the processing result to the terminal. However, satellite networks have characteristics such as wide coverage, high mobility, multiple coverage of cell information, and instantaneous nature, and satellite link resources are relatively limited. This "sending a report regardless of the result" mechanism leads to frequent unnecessary signaling interactions that consume valuable satellite radio resources, increasing the complexity of signaling interactions, reducing resource utilization efficiency, and failing to meet the resource-saving and efficient interaction requirements of satellite-ground converged networks.

[0043] To address the aforementioned issues, this application proposes a multi-dimensional information-based dynamic decision-making mechanism for issuing SMS status reports. This mechanism enables network-side dynamic control to handle the issuance of SMS status reports requested by terminals, moving away from passively executing standard procedures and instead introducing a comprehensive judgment logic based on the terminal device's access type and status report value. First, by determining the terminal device's access type, the cost baseline for the current signaling interaction (satellite access or terrestrial access) is clarified. Second, by receiving the status report value returned by the SMS center, the specific status category of the service result is determined. Finally, based on these two key elements (access type and status report value), the execution strategy for issuing SMS status reports is dynamically determined. This means that the network side can flexibly decide whether to issue the report immediately, postpone it, or adopt other strategies based on the access type, resource status, and the specific importance of the status report, thereby achieving refined control over resource consumption. A detailed explanation follows.

[0044] According to an embodiment of this application, a method embodiment for SMS management 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.

[0045] The methods and embodiments provided in this application can be executed on mobile terminals, computer terminals, or similar computing devices. Figure 4 A hardware structure block diagram of a computer terminal (or electronic device) for implementing a text messaging management method is shown. Figure 4 As shown, the computer terminal 40 (or electronic device) may include one or more processors 402 (shown as 402a, 402b, ..., 402n in the figure) (processor 402 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 404 for storing data, and a transmission device 406 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) 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 4 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 40 may also include... Figure 4 The more or fewer components shown, or having the same Figure 4 The different configurations shown.

[0046] It should be noted that the aforementioned one or more processors 402 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 within the computer terminal 40 (or electronic device). 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).

[0047] The memory 404 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the SMS management method in this embodiment. The processor 402 executes various functional applications and data processing by running the software programs and modules stored in the memory 404, thereby realizing the above-mentioned SMS management method. The memory 404 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 404 may further include memory remotely located relative to the processor 402, and these remote memories can be connected to the computer terminal 40 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.

[0048] The transmission device 406 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 computer terminal 40. In one example, the transmission device 406 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 406 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0049] The display can be, for example, a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the computer terminal 40 (or electronic device).

[0050] Under the above operating environment, this application provides a network-side SMS management method. Figure 5 This is a schematic diagram of a method flow for SMS management with a core network element as the execution subject, according to an embodiment of this application. Figure 5 As shown, the method includes the following steps:

[0051] Step S502: Receive the SMS service request message sent by the terminal device and determine the access type of the terminal device. The SMS service request message contains an SMS status report request identifier, which is used to request the network side to return an SMS status report to the terminal device after the SMS processing is completed. The access type is used to characterize the link type used by the terminal device to access the network.

[0052] Step S504: Forward the SMS service request message to the SMS center and receive the status report value returned by the SMS center. The SMS center is used to process the SMS service request message and generate the corresponding processing result. The status report value is used to characterize the status category corresponding to the processing result.

[0053] The aforementioned Short Message Service (SMS) center, as a business processing system, primarily undertakes the functions of submitting, storing, and forwarding SMS messages. Its internal logic is responsible for receiving SMS service requests from terminals and performing corresponding business processing. Once the SMS center has completed processing the SMS service request message, it generates a processing result. To feed this processing result back to the network side or terminal, the SMS center generates a status report value. This status report value is not the original business data, but rather an abstract representation of the processing result, specifically used to indicate the specific status category to which the processing result belongs (e.g., success, blocked, or service rejected). By obtaining this status report value, the system can determine the final processing status of the SMS service request, providing data basis for subsequent execution of corresponding control processes based on this status category (e.g., determining whether to send a report via satellite access).

[0054] Step S506: Based on the access type and status report value, determine the execution strategy for sending SMS status reports, and send SMS status reports to the terminal devices according to the execution strategy.

[0055] In this embodiment, the mechanism for dynamically sending SMS status messages requested by the terminal can be executed based on the current terminal's access type and status report value. Here, the access type determines the overhead sensitivity of wireless resources, while the status report value represents the final result of service processing; together, they constitute the basic logic for decision-making. Based on this, the system can send SMS status reports to the terminal device according to the determined execution strategy. This dynamic matching and sending action based on access type and status report value directly achieves differentiated processing of signaling interactions, avoiding the blind reporting of non-critical status reports in resource-constrained satellite access scenarios, thereby reducing unnecessary signaling interaction frequency at the source.

[0056] Through the above steps, dynamic decision-making is made based on the access type and status report value of the terminal device. In satellite link access scenarios, SMS status reports are selectively delivered immediately or delayed after being cached. This achieves the goal of reducing unnecessary SMS status report delivery processes and paging signaling interactions in satellite access scenarios while ensuring timely feedback of critical business status. This effectively saves satellite radio resource overhead and solves the technical problems of complex SMS status report delivery processes and signaling interactions occupying satellite resources in satellite-ground integrated networks.

[0057] The SMS management method in steps S502 to S506 of this embodiment can be applied to, for example... Figure 6 The satellite-ground converged networking scenario shown involves the signaling interaction process between the terminal and the core network, as well as the enhancement of the core network functions, which will be further introduced below.

[0058] In this embodiment, the core network first parses and processes the SMS service request message received from the terminal device. If the request message explicitly carries an SMS status report request identifier, the network side needs to send a corresponding SMS status report to the requesting terminal device after the SMS processing flow is completed. Based on this, the core network can simultaneously determine and obtain the current access type of the terminal device. This access type, as a key status parameter, is used to characterize the specific link type used by the terminal device when it is currently connected to the network, thereby providing a basis for dynamically adjusting the SMS status report delivery strategy based on access link differences, as follows.

[0059] In some embodiments of this application, the access type includes: satellite link access and terrestrial link access; the execution strategy for issuing SMS status reports based on the access type and the status report value includes: when the access type is terrestrial link access, directly issuing SMS status reports to terminal devices through the current access network; when the access type is satellite link access, determining the notification priority corresponding to the status report value, and determining the execution strategy for issuing SMS status reports based on the notification priority, wherein the notification priority is used to characterize the urgency of the service processing result indicated by the status report value.

[0060] Specifically, in this embodiment, the access type specifically covers two scenarios: satellite link access and terrestrial link access. Satellite link access refers to the terminal device connecting to the core network through a satellite communication link, while terrestrial link access refers to connecting through a traditional terrestrial cellular network (such as a 4G / 5G base station).

[0061] In this embodiment of the application, the network side can process the subsequent SMS Statusreport (i.e., SMS status report) sent to the MO terminal based on the access type of the terminal device and the SSR identifier (i.e., the SMS service request identifier) ​​carried by the terminal MO SMS (i.e., the SMS status report request message).

[0062] Figure 7 This is a schematic diagram of a method flow for SMS management in a satellite-ground converged network according to an embodiment of this application, as shown below. Figure 7 As shown, after the terminal initiates a registration request, the core network completes the authentication and registration process based on the MO user subscription and obtains the terminal access type.

[0063] If the MO SMS terminal accesses from a terrestrial base station and the MO SMS carries an SMS status report request, the network side will execute the corresponding status report delivery process according to the relevant standards in the relevant technologies and process the SMS status report requested by the MO terminal normally. That is, if it is determined to be a terrestrial link access, since the terrestrial network has sufficient bandwidth and low latency, the system will directly send the SMS status report to the terminal through the current access network without additional processing.

[0064] If an MO terminal accesses via a satellite network and initiates an MO SMS carrying an SMS status report request (or the SMS carrying the SMS status report request is initiated from a terrestrial base station, and the terminal moves to satellite access after the core network receives it), the core network can determine whether to execute the report MT procedure to the MO terminal based on the user's access network type, service subscription, and current network status. That is, if it is a satellite link access, given the preciousness of satellite resources and high transmission costs, the system will not blindly send all reports, but will extract the notification priority corresponding to the status report value, and then determine the sending strategy based on the priority, as follows.

[0065] In some embodiments of this application, the notification priority includes: a first priority and a second priority, wherein the first priority is higher than the second priority; the execution strategy for issuing SMS status reports based on the notification priority includes: when the notification priority corresponding to the status report value is the first priority, directly issuing an SMS status report to the terminal device through the current access network, wherein the status report value of the first priority includes at least one of the following: SMS forwarding blocked, service rejected; when the notification priority corresponding to the status report value is the second priority, temporarily suspending the issuance of SMS status reports to the terminal device, wherein the status report value of the second priority includes at least one of the following: SMS successfully delivered, SMS sent to the destination address but not confirmed to have arrived, SMS replaced, target address terminal busy, target address no response, specified service invalid.

[0066] Specifically, in this embodiment, the notification priority can be divided into a first priority and a second priority. The first priority represents a business processing result with a high degree of urgency, such as situations where SMS forwarding is blocked or services are rejected, requiring immediate notification to the user or intervention from the network side. The second priority represents a normal or low-urgency result, such as SMS successfully delivered, sent to the destination address but not confirmed to have arrived, SMS being replaced, the target address terminal being busy, the target address not responding, or the specified service being invalid. These scenarios usually allow for a certain degree of delay in processing.

[0067] When a terminal device accesses the network via a satellite link, the system dynamically adjusts its execution strategy based on the notification priority: for status reports with the highest priority, the system directly sends the report to the terminal device through the current access network to ensure that critical information can be delivered in a timely manner and to guarantee the reliability of communication; for example, if the core network determines that the report status value is "blocked" or "service denied", the core network will execute the MT SMS process through satellite access and send the corresponding reason value to the MO terminal.

[0068] For status reports belonging to the second priority category, a strategy of delaying their issuance is adopted, meaning that the report is not immediately transmitted via the satellite link. For example, if the core network determines that the report status value is any value other than "blocked" or "service denied," the core network will suspend the execution of the MT SMS service process via satellite access and suspend the issuance of the report to the MO terminal until the terminal accesses the network through a terrestrial base station.

[0069] The temporary suspension of sending SMS status reports to terminal devices includes: caching the SMS status reports in the core network and recording the timestamp of the SMS service request message corresponding to the SMS status report. Specifically, after determining that the access type is satellite link and the status report priority is second priority (e.g., low-urgency scenarios such as successful SMS delivery), the core network does not immediately initiate the mobile terminal (MT) process via satellite link. Instead, it temporarily stores the status report data to be sent in the core network server, and extracts and stores the system time when the terminal initially initiated the SMS service request as a unique identifier.

[0070] This priority-based differentiated processing mechanism avoids the real-time transmission of a large number of non-urgent status reports (such as successful delivery confirmations or busy tone prompts) in scenarios where satellite resources are relatively scarce and signaling interaction costs are high. This effectively reduces the frequency of signaling interaction on the satellite link, reduces the occupation of wireless resources and signaling overhead, while ensuring the real-time nature of emergency status reports, and achieves a balance between resource utilization efficiency and service response speed in the satellite-ground converged network.

[0071] Furthermore, in this embodiment, if an MO terminal accessing via satellite receives a status report value of "blocked" or "service denied" from the core network, it will no longer initiate MO SMS via satellite access. That is, when the SMS status report sent by the network side shows that the SMS processing result is "forwarding blocked" or "service denied," and the terminal device is currently accessing the network via a satellite link, the terminal device actively terminates subsequent operations to initiate new SMS service requests via that satellite link. Here, "forwarding blocked" typically refers to the message failing to be delivered due to network congestion, routing failure, etc., while "service denied" refers to the network side explicitly refusing to accept the request due to reasons such as user non-payment or insufficient permissions. Both states indicate that the current SMS service has failed under the current link or network conditions.

[0072] This mechanism prevents terminal devices from repeatedly attempting to send new SMS requests even when they know the transmission has failed and satellite link resources are expensive and latency is high. It significantly reduces the number of unnecessary signaling interactions, thereby effectively saving valuable satellite communication resources and improving resource utilization efficiency in the space-ground integrated network. Compared with the existing technology that may continuously initiate requests regardless of the status, it achieves more precise resource management.

[0073] When the MO terminal returns to the terrestrial access network, the network side will send the cached report to the MO terminal, along with the time when the network side received the MO SMS (to help the user determine which SMS report it belongs to). Details are as follows.

[0074] In some embodiments of this application, after temporarily suspending the delivery of SMS status reports to the terminal device, the method further includes: monitoring the access type of the terminal device; and when it is detected that the access type of the terminal device has switched from satellite link access to terrestrial link access, actively delivering a cached SMS status report to the terminal device, wherein the SMS status report carries a receiving timestamp, which is used to assist the terminal device in identifying the SMS service request message corresponding to the SMS status report.

[0075] Specifically, after temporarily suspending the issuance of SMS status reports, the network side can continuously listen to and capture signaling interactions initiated by the terminal device to maintain or restore network connectivity, in order to monitor the access type of the terminal device. These signaling signals are necessary for the terminal device to establish or maintain a communication connection with the ground base station during movement, as detailed below.

[0076] In some embodiments of this application, the method further includes: receiving network activity signaling initiated by the terminal device through a terrestrial base station, wherein the network activity signaling includes at least one of the following: registration request, location update request, service request, periodic registration update; extracting access type indication information from the network activity signaling, and determining that the access type of the terminal device is switched from satellite link access to terrestrial link access when the access type indication information indicates terrestrial link access.

[0077] In this embodiment, data bits that clearly identify the current communication link attributes can be obtained by parsing the header or payload fields of the received signaling messages. For example, in 5G or 4G signaling protocols, this indication information is usually reflected in the message type of the Access and Mobility Management Function (AMF / MME) interaction or a specific access network type identifier. When the indication information clearly points to a terrestrial cellular network (such as 4G / 5G NR or LTE) rather than a satellite network, it is confirmed that the terminal has completed the link handover action.

[0078] When the network detects that the access type of a terminal device has switched from satellite link access to terrestrial link access, the network side can proactively trigger the sending of a cached SMS status report to the terminal device. At the same time, the SMS status report carries a receiving timestamp, which refers to the specific time information recorded by the core network when it initially receives the SMS service request message sent by the terminal. The core network saves this timestamp when caching the status report and appends it to the status report in subsequent sending. Since multiple status reports that are temporarily delayed under satellite link may accumulate, and the terminal device may have initiated a new SMS service after switching back to terrestrial link, the correspondence between the received status report order or content and the original request becomes unclear. Carrying the receiving timestamp is equivalent to giving each status report a unique time tag. After receiving the report, the terminal device can compare the timestamp in it with the time information of historical SMS service request messages recorded locally, so as to accurately identify which specific historical SMS service request message the status report corresponds to.

[0079] By using the above steps, with access type switching as the trigger and timestamp as the matching basis, the problem of delayed report delivery caused by the temporary delay in satellite link delivery is solved. It also ensures that when multiple cached reports are delivered concurrently, the terminal device can accurately associate the status report with the corresponding original request, thereby improving the accuracy of SMS status receipts and user experience.

[0080] In this application, the core network can dynamically adjust the SMS status report delivery mechanism requested by the MO terminal based on the status request and report reason value carried in the MO SMS message and the current access network type of the user. This reduces the service request and MT process of the MO terminal in satellite access scenarios and dynamically executes the delivery strategy of the SMS status message requested by the terminal. Through this strategy selection mechanism based on the dual dimensions of access link type and processing result, the adaptive adjustment of the SMS status report delivery process can be directly realized, avoiding the processing redundancy caused by the unified and complex signaling interaction process in the satellite-ground converged network environment. This effectively solves the technical problems of complex SMS status report delivery process and satellite resource occupation of signaling interaction in the prior art, achieving the technical effect of optimizing the signaling interaction process, reducing satellite link resource occupation, and thus improving the SMS service processing efficiency in the satellite-ground converged network.

[0081] According to an embodiment of this application, a terminal-side SMS management method is also provided. Figure 8 This is a schematic diagram of a method flow for SMS management with a terminal device as the execution subject, according to an embodiment of this application. Figure 8 As shown, the method includes the following steps:

[0082] Step S802: Send an SMS service request message to the network side. The SMS service request message includes an SMS status report request identifier, which is used to request the network side to return an SMS status report to the terminal device after the SMS processing is completed.

[0083] Step S804: Receive the SMS status report sent by the network side after determining the execution policy based on the status report value and the access type of the terminal device. The access type is used to characterize the link type used by the terminal device to access the network, and the status report value is used to characterize the status category corresponding to the processing result generated by the network side in processing the SMS service request message.

[0084] Step S806: Based on the status report value in the SMS status report and the current access type of the terminal device, determine whether to continue sending SMS service request messages to the network side through the current access network.

[0085] In some embodiments of this application, determining whether to continue sending SMS service request messages to the network side through the current access network based on the status report value in the SMS status report and the current access type of the terminal device includes: stopping the sending of SMS service request messages to the network side through the satellite link when the status report value indicates that SMS forwarding is blocked or service is rejected, and the access type is satellite link access.

[0086] By sending an SMS service request message containing an SMS status report request identifier to the network side, and after receiving an SMS status report issued by the network side based on the status report value and the terminal device's access type, the terminal device determines whether to continue sending new SMS service request messages to the network side through the current access network based on the status report value in the SMS status report and the terminal device's current access type. This method enables the terminal device to proactively decide the subsequent SMS service sending path based on the specific service processing result (i.e., status report value) fed back by the network side and the current network access environment (i.e., access type). When in a satellite access scenario and the status report value indicates a non-urgent failure status, the terminal can avoid immediately initiating new signaling interactions or waiting for unnecessary status report confirmations, thereby effectively reducing the frequency of signaling interactions and wireless resource occupation of the terminal under the satellite link, and improving the transmission efficiency and resource utilization of short message services in a satellite-ground converged network environment.

[0087] It should be noted that the SMS management method on the terminal side provided in this embodiment is similar to... Figure 5 The method embodiments corresponding to the network-side SMS management method shown are as follows: Therefore, the relevant explanations and descriptions of the above SMS management method also apply to the embodiments of this application, and will not be repeated here.

[0088] According to an embodiment of this application, an embodiment of a text message management device is also provided. Figure 9 This is a schematic diagram of a text message management device according to an embodiment of this application. Figure 9 As shown, the device includes:

[0089] The access type determination module 90 is used to receive the SMS service request message sent by the terminal device and determine the access type of the terminal device. The SMS service request message contains an SMS status report request identifier, which is used to request the network side to return an SMS status report to the terminal device after the SMS processing is completed. The access type is used to characterize the link type used by the terminal device to access the network.

[0090] The report value acquisition module 92 is used to forward SMS service request messages to the SMS center and receive status report values ​​returned by the SMS center. The SMS center is used to process the SMS service request messages and generate corresponding processing results. The status report value is used to characterize the status category corresponding to the processing result.

[0091] The sending strategy determination module 94 is used to determine the execution strategy for sending SMS status reports based on the access type and status report value, and send SMS status reports to the terminal device in accordance with the execution strategy.

[0092] Optionally, the access type includes: satellite link access and terrestrial link access; the execution strategy for sending SMS status reports is determined based on the access type and the status report value, including: when the access type is terrestrial link access, sending SMS status reports directly to the terminal device through the current access network; when the access type is satellite link access, determining the notification priority corresponding to the status report value, and determining the execution strategy for sending SMS status reports based on the notification priority, wherein the notification priority is used to characterize the urgency of the service processing result indicated by the status report value.

[0093] Optionally, the notification priority includes: a first priority and a second priority, wherein the first priority is higher than the second priority; the execution strategy for issuing SMS status reports based on the notification priority includes: when the notification priority corresponding to the status report value is the first priority, directly issuing an SMS status report to the terminal device through the current access network, wherein the status report value of the first priority includes at least one of the following: SMS forwarding blocked, service denied; when the notification priority corresponding to the status report value is the second priority, temporarily suspending the issuance of SMS status reports to the terminal device, wherein the status report value of the second priority includes at least one of the following: SMS successfully delivered, SMS sent to the destination address but not confirmed to have arrived, SMS replaced, target address terminal busy, target address no response, specified service invalid.

[0094] Optionally, temporarily suspending the delivery of SMS status reports to terminal devices includes: caching the SMS status reports in the core network and recording the timestamp of the SMS service request message corresponding to the SMS status reports.

[0095] Optionally, after temporarily suspending the delivery of SMS status reports to the terminal device, the method further includes: monitoring the access type of the terminal device; and proactively delivering a cached SMS status report to the terminal device when the access type of the terminal device is detected to have switched from satellite link access to terrestrial link access. The SMS status report carries a receiving timestamp, which is used to assist the terminal device in identifying the SMS service request message corresponding to the SMS status report.

[0096] Optionally, the SMS management device is further configured to: receive network activity signaling initiated by the terminal device through a terrestrial base station, wherein the network activity signaling includes at least one of the following: registration request, location update request, service request, periodic registration update; extract access type indication information from the network activity signaling, and determine that the access type of the terminal device is switched from satellite link access to terrestrial link access when the access type indication information indicates terrestrial link access.

[0097] It should be noted that the modules in the above-mentioned SMS management device can be program modules (such as a set of program instructions to implement a certain function) or hardware modules. For the latter, they can be in the following forms, but are not limited to these: each of the above modules is in the form of a processor, or the functions of each of the above modules are implemented by a processor.

[0098] It should be noted that the SMS management device provided in this embodiment can be used to perform... Figure 5 or Figure 8 The SMS management method shown above is also applicable to the embodiments of this application, and will not be repeated here.

[0099] This application embodiment also provides a non-volatile storage medium, which includes a stored computer program, wherein the device containing the non-volatile storage medium executes the following SMS management method by running the computer program:

[0100] The system receives SMS service request messages from terminal devices and determines the access type of the terminal devices. The SMS service request message includes an SMS status report request identifier, which requests the network side to return an SMS status report to the terminal devices after SMS processing. The access type represents the link type used by the terminal devices to access the network. The system forwards the SMS service request message to the Short Message Service Center (SMSC) and receives the status report value returned by the SMSC. The SMSC processes the SMS service request message and generates corresponding processing results, and the status report value represents the status category corresponding to the processing result. Based on the access type and the status report value, the system determines the execution strategy for issuing the SMS status report and sends the SMS status report to the terminal devices according to the execution strategy.

[0101] Alternatively, the terminal device can send an SMS service request message to the network side, which includes an SMS status report request identifier. This identifier requests the network side to return an SMS status report to the terminal device after SMS processing is complete. The terminal device then receives an SMS status report from the network side after determining the execution policy based on the status report value and the terminal device's access type. The access type represents the link type used by the terminal device to access the network, and the status report value represents the status category corresponding to the processing result generated by the network side in processing the SMS service request message. Based on the status report value in the SMS status report and the terminal device's current access type, the terminal device determines whether to continue sending SMS service request messages to the network side through the current access network.

[0102] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the SMS management method described in various embodiments of this application:

[0103] The system receives SMS service request messages from terminal devices and determines the access type of the terminal devices. The SMS service request message includes an SMS status report request identifier, which requests the network side to return an SMS status report to the terminal devices after SMS processing. The access type represents the link type used by the terminal devices to access the network. The system forwards the SMS service request message to the Short Message Service Center (SMSC) and receives the status report value returned by the SMSC. The SMSC processes the SMS service request message and generates corresponding processing results, and the status report value represents the status category corresponding to the processing result. Based on the access type and the status report value, the system determines the execution strategy for issuing the SMS status report and sends the SMS status report to the terminal devices according to the execution strategy.

[0104] Alternatively, the terminal device can send an SMS service request message to the network side, which includes an SMS status report request identifier. This identifier requests the network side to return an SMS status report to the terminal device after SMS processing is complete. The terminal device then receives an SMS status report from the network side after determining the execution policy based on the status report value and the terminal device's access type. The access type represents the link type used by the terminal device to access the network, and the status report value represents the status category corresponding to the processing result generated by the network side in processing the SMS service request message. Based on the status report value in the SMS status report and the terminal device's current access type, the terminal device determines whether to continue sending SMS service request messages to the network side through the current access network.

[0105] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0106] 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.

[0107] 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 instance, 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 coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0108] 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.

[0109] 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.

[0110] 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 described in 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 (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0111] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A short message management method, characterized by, include: The system receives a text message service request message sent by a terminal device and determines the access type of the terminal device. The text message service request message contains a text message status report request identifier, which is used to request the network side to return a text message status report to the terminal device after the text message processing is completed. The access type is used to characterize the link type used by the terminal device to access the network. The SMS service request message is forwarded to the SMS center, and the status report value returned by the SMS center is received. The SMS center is used to process the SMS service request message and generate a corresponding processing result. The status report value is used to characterize the status category corresponding to the processing result. Based on the access type and the status report value, an execution strategy for sending SMS status reports is determined, and an SMS status report is sent to the terminal device according to the execution strategy.

2. The short message management method of claim 1, wherein, The access types include: satellite link access and terrestrial link access; based on the access type and the status report value, the execution strategy for issuing SMS status reports includes: When the access type is the terrestrial link access, the SMS status report is sent directly to the terminal device through the current access network; When the access type is the satellite link access, the notification priority corresponding to the status report value is determined, and the execution strategy for sending the SMS status report is determined based on the notification priority, wherein the notification priority is used to characterize the urgency of the service processing result indicated by the status report value.

3. The SMS management method according to claim 2, characterized in that, The notification priority includes a first priority and a second priority, wherein the first priority is higher than the second priority; the execution strategy for issuing the SMS status report is determined based on the notification priority, including: When the notification priority corresponding to the status report value is the first priority, the SMS status report is sent directly to the terminal device through the current access network. The status report value of the first priority includes at least one of the following: SMS forwarding blocked, service rejected. When the notification priority corresponding to the status report value is the second priority, the delivery of the SMS status report to the terminal device is temporarily suspended. The status report value of the second priority includes at least one of the following: SMS successfully delivered, SMS sent to the destination address but not confirmed, SMS replaced, target address terminal busy, target address no response, and specified service invalid.

4. The SMS management method according to claim 3, characterized in that, The suspension of sending the SMS status report to the terminal device includes: The SMS status report is cached in the core network, and the timestamp of the SMS service request message corresponding to the SMS status report is recorded.

5. The SMS management method according to claim 4, characterized in that, After temporarily suspending the delivery of the SMS status report to the terminal device, the method further includes: Monitor the access type of the terminal device; When the terminal device is detected to have switched its access type from satellite link access to terrestrial link access, the system proactively sends a cached SMS status report to the terminal device. The SMS status report carries a receiving timestamp, which is used to help the terminal device identify the SMS service request message corresponding to the SMS status report.

6. The SMS management method according to claim 5, characterized in that, The method further includes: The terminal device receives network activity signaling initiated by a ground base station, wherein the network activity signaling includes at least one of the following: registration request, location update request, service request, and periodic registration update. The access type indication information is extracted from the network activity signaling, and if the access type indication information indicates that the terrestrial link access is used, the access type of the terminal device is determined to switch from the satellite link access to the terrestrial link access.

7. A method for managing text messages, characterized in that, include: Send an SMS service request message to the network side, wherein the SMS service request message includes an SMS status report request identifier, which is used to request the network side to return an SMS status report to the terminal device after the SMS processing is completed; The system receives an SMS status report issued by the network side after determining the execution strategy based on the status report value and the access type of the terminal device. The access type is used to characterize the link type used by the terminal device to access the network, and the status report value is used to characterize the status category corresponding to the processing result generated by the network side in processing the SMS service request message. Based on the status report value in the SMS status report and the current access type of the terminal device, determine whether to continue sending SMS service request messages to the network side through the current access network.

8. The SMS management method according to claim 7, characterized in that, Determining whether to continue sending SMS service request messages to the network side through the current access network based on the status report value in the SMS status report and the current access type of the terminal device includes: If the status report value indicates that SMS forwarding is blocked or service is denied, and the access type is satellite link access, then the sending of the SMS service request message to the network side via satellite link shall be stopped.

9. A text message management device, characterized in that, include: The access type determination module is used to receive SMS service request messages sent by terminal devices and determine the access type of the terminal devices. The SMS service request message includes an SMS status report request identifier, which is used to request the network side to return an SMS status report to the terminal devices after the SMS processing is completed. The access type is used to characterize the link type used by the terminal devices to access the network. The report value acquisition module is used to forward the SMS service request message to the SMS center and receive the status report value returned by the SMS center. The SMS center is used to process the SMS service request message and generate a corresponding processing result. The status report value is used to characterize the status category corresponding to the processing result. The sending strategy determination module is used to determine the execution strategy for sending SMS status reports based on the access type and the status report value, and send the SMS status report to the terminal device according to the execution strategy.

10. An electronic device, characterized in that, include: A memory and a processor, the processor being configured to run a program stored in the memory, wherein the program, when running, executes the SMS management method according to any one of claims 1 to 8.

11. A non-volatile storage medium, characterized in that, The non-volatile storage medium includes a stored computer program, wherein the device containing the non-volatile storage medium executes the SMS management method according to any one of claims 1 to 8 by running the computer program.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the SMS management method according to any one of claims 1 to 8.

Images