Data transmission method, device and system, communication equipment and storage medium

Abstract

The invention relates to a data transmission method and device, communication equipment, a storage medium and a computer program product. The method is applied to network element equipment, and comprises the following steps: if user equipment is registered in a satellite store-and-forward mode, sending a store-and-forward mode identifier and data pre-estimation transmission time to a server; by adopting the method, the communication quality can be improved.

Description

Technical Field

[0001] This application relates to the field of communication network technology, and in particular to a data transmission method, apparatus, system, communication equipment, storage medium, and computer program product. Background Technology

[0002] With the development of communication technology, the application of IoT-NTN (Internet of Things - Non-Ground Network) technology is becoming increasingly widespread. In IoT-NTN, store-and-forward mode is an important operating mode. When user equipment and network equipment are operating in store-and-forward mode, ground servers (such as AS (Application Server) or SCS (ServicesCapability Server)) can communicate with user equipment in the Internet of Things through network equipment.

[0003] However, based on the current communication rules, SCS / AS cannot know the current operating mode of the user equipment in a timely manner, thus it cannot communicate with the user equipment, resulting in low communication quality. Summary of the Invention

[0004] This application provides a data transmission method, apparatus, system, communication device, storage medium, and computer program product that can improve communication quality.

[0005] A data transmission method, applied to a network element device, the method comprising:

[0006] If the user equipment is registered in satellite store-and-forward mode, it sends a store-and-forward mode identifier and an estimated data transmission time to the server.

[0007] In one embodiment, the method further includes:

[0008] Receive uplink non-IP data sent by the user equipment and query whether the user equipment is registered in satellite store-and-forward mode.

[0009] In one embodiment, sending the store-and-forward mode identifier and estimated data transmission time to the server includes:

[0010] Send a non-IP data request message to the server, the non-IP data request message containing at least a store-and-forward mode identifier and an estimated data transmission time.

[0011] In one embodiment, the method further includes:

[0012] Receive downlink non-IP data sent by the server and query whether the user equipment is registered in satellite store-and-forward mode.

[0013] In one embodiment, sending the store-and-forward mode identifier and estimated data transmission time to the server includes:

[0014] Send a non-IP data response message to the server, the non-IP data response message containing at least a store-and-forward mode identifier and an estimated data transmission time.

[0015] In one embodiment, the method further includes:

[0016] If the user equipment is registered in satellite store-and-forward mode and the service link is unavailable, the downlink non-IP data is cached.

[0017] In one embodiment, after caching the downlink non-IP data, the method further includes:

[0018] If the service link is available, the downlink non-IP data is sent to the user equipment;

[0019] Send a new non-IP data response message to the server; wherein the new non-IP data response message carries an updated operating mode identifier and / or an updated estimated data transmission time, the operating mode identifier being used to indicate whether the user equipment is registered in satellite store-and-forward mode.

[0020] In one embodiment, the method further includes:

[0021] Receive downlink data notification messages;

[0022] If the current service link is unavailable, a downlink data confirmation message is returned, and if a reachability notification flag is set after downlink data transmission failure, the user equipment is queried to see if it is registered in satellite store-and-forward mode.

[0023] In one embodiment, sending the store-and-forward mode identifier and estimated data transmission time to the server includes:

[0024] Send an event monitoring message to the server to notify of reachability after downlink data transmission failure; the event monitoring message carries a store-and-forward mode identifier and an estimated data transmission time.

[0025] In one embodiment, the method further includes:

[0026] If a reachability notification flag is not currently set after downlink data transmission failure, then the reachability notification flag is set.

[0027] In one embodiment, if the user equipment is registered in satellite store-and-forward mode, sending a store-and-forward mode identifier and an estimated data transmission time to the server includes:

[0028] If the monitoring detects that the user equipment has successfully registered in the satellite store-and-forward mode, a first event notification message is sent to the server. The first event notification message carries the store-and-forward mode identifier.

[0029] If the monitoring detects the existence of transmission data corresponding to the user equipment and the user equipment is currently registered in satellite store-and-forward mode, a second event notification message is sent to the server. The second event notification message carries at least the estimated data transmission time.

[0030] In one embodiment, the method further includes:

[0031] Monitoring events configured for satellite store-and-forward mode; and,

[0032] Configure monitoring events for estimated data transmission time.

[0033] In one embodiment, the network element device is an MME or an HSS.

[0034] A data transmission method, applied to a server, the method comprising:

[0035] The network element sends the user equipment's store-and-forward mode identifier and estimated data transmission time.

[0036] In one embodiment, the store-and-forward mode identifier and estimated data transmission time corresponding to the user equipment sent by the receiving network element include:

[0037] Receive a non-IP data request message sent by a network element device, wherein the non-IP data request message includes at least a store-and-forward mode identifier and an estimated data transmission time.

[0038] In one embodiment, the method further includes:

[0039] Send downlink non-IP data to the network element device;

[0040] The store-and-forward mode identifier and estimated data transmission time corresponding to the user equipment sent by the receiving network element device include:

[0041] Receive a non-IP data response message sent by a network element device, wherein the non-IP data response message includes at least a store-and-forward mode identifier and an estimated data transmission time.

[0042] In one embodiment, the method further includes:

[0043] Send downlink IP data to the gateway device so that the gateway device sends a downlink data notification message to the network element device;

[0044] The store-and-forward mode identifier and estimated data transmission time corresponding to the user equipment sent by the receiving network element device include:

[0045] The system receives an event monitoring message from a network element device notifying the network that downlink data transmission has failed. The event monitoring message carries a store-and-forward mode identifier and an estimated data transmission time.

[0046] In one embodiment, the store-and-forward mode identifier and estimated data transmission time corresponding to the user equipment sent by the receiving network element include:

[0047] Receive a first event notification message sent by a network element device, wherein the first event notification message carries a store-and-forward mode identifier;

[0048] The network element receives a second event notification message, which carries at least the estimated data transmission time.

[0049] In one embodiment, the method further includes:

[0050] Based on the store-and-forward mode identifier and the estimated data transmission time, the downlink data transmission strategy corresponding to the user equipment is adjusted.

[0051] In one embodiment, adjusting the downlink data transmission strategy corresponding to the user equipment based on the store-and-forward mode identifier and the estimated data transmission time includes:

[0052] If downlink data corresponding to the user equipment exists, the downlink data transmission strategy corresponding to the user equipment is adjusted based on the store-and-forward mode identifier and the estimated data transmission time.

[0053] In one embodiment, adjusting the downlink data transmission strategy corresponding to the user equipment based on the store-and-forward mode identifier and the estimated data transmission time includes:

[0054] If there is remaining downlink data corresponding to the user equipment, the downlink data transmission strategy corresponding to the user equipment is adjusted based on the store-and-forward mode identifier and the estimated data transmission time.

[0055] A data transmission apparatus, applied to a network element device, the apparatus comprising:

[0056] The first sending module is used to send a store-and-forward mode identifier and an estimated data transmission time to the server if the user equipment is registered in satellite store-and-forward mode.

[0057] In one embodiment, the device further includes:

[0058] The first receiving module is used to receive uplink non-IP data sent by the user equipment and to query whether the user equipment is registered in satellite store-and-forward mode.

[0059] In one embodiment, the first sending module is specifically used for:

[0060] Send a non-IP data request message to the server, the non-IP data request message containing at least a store-and-forward mode identifier and an estimated data transmission time.

[0061] In one embodiment, the device further includes:

[0062] The second receiving module is used to receive downlink non-IP data sent by the server and query whether the user equipment is registered in satellite store-and-forward mode.

[0063] In one embodiment, the first sending module is specifically used for:

[0064] Send a non-IP data response message to the server, the non-IP data response message containing at least a store-and-forward mode identifier and an estimated data transmission time.

[0065] In one embodiment, the device further includes:

[0066] The caching module is used to cache the downlink non-IP data if the user equipment is registered in satellite store-and-forward mode and the service link is unavailable.

[0067] In one embodiment, the device further includes:

[0068] The second sending module is used to send the downlink non-IP data to the user equipment if the service link is available;

[0069] The third sending module is used to send a new non-IP data response message to the server; wherein the new non-IP data response message carries an updated operating mode identifier and / or an updated estimated data transmission time, and the operating mode identifier is used to indicate whether the user equipment is registered in satellite store-and-forward mode.

[0070] In one embodiment, the device further includes:

[0071] The third receiving module is used to receive downlink data notification messages;

[0072] The fourth sending module is used to return a downlink data confirmation message if the current service link is unavailable, and, if a downlink data transmission failure reachability notification flag is set, to query whether the user equipment is registered in satellite store-and-forward mode.

[0073] In one embodiment, the first sending module is specifically used for:

[0074] Send an event monitoring message to the server to notify of reachability after downlink data transmission failure; the event monitoring message carries a store-and-forward mode identifier and an estimated data transmission time.

[0075] In one embodiment, the device further includes:

[0076] The setting module is used to set the downlink data transmission failure reachability flag if the downlink data transmission failure reachability flag is not currently set.

[0077] In one embodiment, the first sending module is specifically used for:

[0078] If the monitoring detects that the user equipment has successfully registered in the satellite store-and-forward mode, a first event notification message is sent to the server. The first event notification message carries the store-and-forward mode identifier.

[0079] If the monitoring detects the existence of transmission data corresponding to the user equipment and the user equipment is currently registered in satellite store-and-forward mode, a second event notification message is sent to the server. The second event notification message carries at least the estimated data transmission time.

[0080] In one embodiment, the device further includes:

[0081] The configuration module is used to configure monitoring events for satellite store-and-forward mode and to configure monitoring events for estimated data transmission time.

[0082] In one embodiment, the network element device is an MME or an HSS.

[0083] A data transmission apparatus, applied to a server, the apparatus comprising:

[0084] The first receiving module is used to receive the store-and-forward mode identifier and estimated data transmission time of the user equipment sent by the network element device.

[0085] In one embodiment, the first receiving module is specifically used for:

[0086] Receive a non-IP data request message sent by a network element device, wherein the non-IP data request message includes at least a store-and-forward mode identifier and an estimated data transmission time.

[0087] In one embodiment, the device further includes:

[0088] The first sending module is used to send downlink non-IP data to the network element device;

[0089] The first receiving module is specifically used for:

[0090] Receive a non-IP data response message sent by a network element device, wherein the non-IP data response message includes at least a store-and-forward mode identifier and an estimated data transmission time.

[0091] In one embodiment, the device further includes:

[0092] The second sending module is used to send downlink IP data to the gateway device so that the gateway device sends a downlink data notification message to the network element device.

[0093] The first receiving module is specifically used for:

[0094] The system receives an event monitoring message from a network element device notifying the network that downlink data transmission has failed. The event monitoring message carries a store-and-forward mode identifier and an estimated data transmission time.

[0095] In one embodiment, the first receiving module is specifically used for:

[0096] Receive a first event notification message sent by a network element device, wherein the first event notification message carries a store-and-forward mode identifier;

[0097] The network element receives a second event notification message, which carries at least the estimated data transmission time.

[0098] In one embodiment, the device further includes:

[0099] The adjustment module is used to adjust the downlink data transmission strategy corresponding to the user equipment based on the store-and-forward mode identifier and the estimated data transmission time.

[0100] In one embodiment, the adjustment module is specifically used for:

[0101] If downlink data corresponding to the user equipment exists, the downlink data transmission strategy corresponding to the user equipment is adjusted based on the store-and-forward mode identifier and the estimated data transmission time.

[0102] In one embodiment, the adjustment module is specifically used to: if there is remaining downlink data corresponding to the user equipment, adjust the downlink data transmission strategy corresponding to the user equipment based on the store-and-forward mode identifier and the estimated data transmission time.

[0103] A data transmission system comprising network element devices and a server; wherein:

[0104] The network element device is used to send a store-and-forward mode identifier and an estimated data transmission time to the server if the user equipment is registered in the satellite store-and-forward mode.

[0105] The server is used to receive the store-and-forward mode identifier and estimated data transmission time of the user equipment sent by the network element device.

[0106] A communication device, comprising: a transmitter;

[0107] The transmitter is used to send a store-and-forward mode identifier and an estimated data transmission time to the server if the user equipment is registered in satellite store-and-forward mode.

[0108] A communication device includes: a receiver;

[0109] The receiver is used to receive the store-and-forward mode identifier and estimated data transmission time of the user equipment sent by the network element device.

[0110] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method.

[0111] A computer program product includes a computer program that, when executed by a processor, implements the steps of the above-described method.

[0112] In the aforementioned data transmission methods, devices, communication equipment, storage media, and computer program products, if the network element determines that the user equipment is registered in satellite store-and-forward mode, the network element can send a store-and-forward mode identifier and an estimated data transmission time to the server. In this way, the server (SCS / AS) can promptly learn the current operating mode of the user equipment and obtain the estimated data transmission time, providing a basis for downlink data transmission, thereby enabling communication between the server and the user equipment and improving communication quality. Attached Figure Description

[0113] Figure 1 This is a diagram illustrating an application scenario of a data transmission method in one embodiment.

[0114] Figure 2 This is a flowchart illustrating a data transmission method in one embodiment;

[0115] Figure 3 This is a flowchart illustrating the data transmission method in another embodiment;

[0116] Figure 4 This is a flowchart illustrating the data transmission method in another embodiment;

[0117] Figure 5 A flowchart illustrating the data transmission method when a UE sends uplink non-IP data;

[0118] Figure 6 A flowchart illustrating the data transmission method when sending downlink non-IP data to SCS / AS;

[0119] Figure 7 A flowchart illustrating the data transmission method when sending downlink IP data to SCS / AS;

[0120] Figure 8 This is a flowchart illustrating the data transmission method based on newly added monitoring events;

[0121] Figure 9 This is a structural block diagram of a data transmission device in one embodiment;

[0122] Figure 10 This is a structural block diagram of a data transmission device in one embodiment;

[0123] Figure 11 This is an internal structural diagram of a communication device in one embodiment. Detailed Implementation

[0124] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0125] Figure 1 This is a schematic diagram illustrating an application scenario of a data transmission method provided in an embodiment of this application. For example... Figure 1 As shown, the scenario includes user equipment 100, network element equipment 200, and server 300. User equipment 100 and network element equipment 200 can communicate via a communication link.

[0126] Optionally, user equipment 100 may be a wireless terminal. A wireless terminal may be a device providing voice and / or other service data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The wireless terminal may communicate with one or more core networks via a Radio Access Network (RAN). The wireless terminal may be a mobile terminal, such as a mobile phone (or "cellular" phone), or a computer with a mobile terminal, for example, a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device, which exchanges voice and / or data with the radio access network. The wireless terminal may also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile, remote station, remote terminal, access terminal, user terminal, user agent, or other Internet of Things (IoT) device, without limitation herein.

[0127] The network element device 200 can be an MME (Mobility Management Entity) or an HSS (Home Subscriber Server). The MME can be applied to terrestrial and satellite MME separation architectures (MME-SAT and MME-Ground) and full-core satellite architectures. That is, the MME in this application can be a terrestrial MME or a satellite MME; this embodiment does not limit the specific application.

[0128] Server 300 can be either AS (Application Server) or SCS (ServicesCapability Server).

[0129] In IoT-NTN, store-and-forward mode is an important operating mode. When user equipment and network equipment are operating in store-and-forward mode, ground servers (such as AS (Application Server)) can communicate with user equipment in the Internet of Things through network equipment.

[0130] However, based on current communication rules, the SCS / AS cannot promptly ascertain the current operating mode of the user equipment. Specifically, the service link and the power supply link may not be available simultaneously, leading to untimely communication; and traditional monitoring event notifications cannot reflect the UE's connection status (even if the UE is woken up, it may still be unreachable due to satellite link issues). Thus, the SCS / AS cannot promptly ascertain the terminal's operating mode, resulting in a lack of effective planning and judgment for data transmission, leading to data transmission failures and poor communication quality.

[0131] Based on the aforementioned traditional technologies, this application provides a data transmission method. If a network element determines that a user equipment (UE) is registered in satellite store-and-forward mode, the network element can send a store-and-forward mode identifier and an estimated data transmission time to the server. The server can receive the store-and-forward mode identifier and estimated data transmission time corresponding to the UE sent by the network element. This allows the SCS / AS to promptly learn the current operating mode of the UE and adjust its downlink data transmission strategy, thereby achieving communication with the UE and improving communication quality. It should be noted that the beneficial effects or technical problems solved by this application are not limited to this one; other implicit or related problems may also exist, as detailed in the following description of the embodiments.

[0132] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0133] In one embodiment, such as Figure 2 As shown, a data transmission method is provided, which is applied to... Figure 1 Taking network element devices as an example, the explanation includes the following steps:

[0134] Step 202: If the user equipment is registered in satellite store-and-forward mode, send the store-and-forward mode identifier and the estimated data transmission time to the server.

[0135] In this embodiment, the user equipment (UE) can support store-and-forward mode and can register in satellite store-and-forward mode. During the UE registration process, the network element can store the UE's registration information, which indicates that the UE is registered in satellite store-and-forward mode. The network device can determine whether a UE is registered in satellite store-and-forward mode by querying the locally stored registration information. If the UE is registered in satellite store-and-forward mode, the network element can send a store-and-forward mode identifier and an estimated data transmission time to the server. The server can then adjust its downlink data transmission strategy based on the store-and-forward mode identifier and the estimated data transmission time. In this embodiment, the network element can be an MME or an HSS; this embodiment uses an MME as an example, and other cases are similar.

[0136] This solution enables the SCS / AS to promptly determine the current operating mode of the user equipment and adjust its downlink data transmission strategy, thereby improving communication quality. When the UE is operating in satellite store-and-forward mode, it avoids the problem of low data transmission success rate and resource waste caused by the SCS / AS's inability to determine the UE's operating mode during application data transmission.

[0137] Optionally, the method further includes: receiving uplink non-IP data sent by the user equipment and querying whether the user equipment is registered in satellite store-and-forward mode.

[0138] In this embodiment of the application, when the UE initiates uplink non-IP data, after the MME receives the uplink non-IP data, the MME can query the local registration information to determine whether the user equipment is registered in satellite store-and-forward mode.

[0139] Optionally, send a store-and-forward mode identifier and estimated data transmission time to the server, including sending a non-IP data request message to the server.

[0140] Non-IP data request messages must include at least a store-and-forward mode identifier and an estimated data transmission time.

[0141] In this embodiment, for uplink non-IP data initiated by the UE, if the MME finds that the UE is registered in satellite store-and-forward mode, the MME sends a NIDD (Non-IP Data Delivery) request, i.e., a non-IP data request message, to the SCEF (Service Capability Exposure Function). The non-IP data request message may at least include a store-and-forward mode identifier and an estimated data transmission time, and may also include NIDD-related parameters such as non-IP data, identity identifier, and EPS (Evolved Packet System) bearer information.

[0142] The SCEF forwards the non-IP data request message to the SCS / AS. Upon receiving the non-IP data request message, the SCS / AS can send a NIDD response message to the SCEF, which then forwards the NIDD response message to the MME. Additionally, upon receiving the non-IP data request message, the SCS / AS can parse it to obtain the store-and-forward mode identifier and the estimated data transmission time. Based on the store-and-forward mode identifier, the SCS / AS can determine that the UE is operating in store-and-forward mode. In this mode, if there is downlink data to be transmitted, the SCS / AS adjusts the downlink data transmission strategy based on the estimated data transmission time and the SCEF buffer settings.

[0143] With this solution, in scenarios where the UE initiates uplink non-IP data, the SCS / AS can learn the current operating mode of the user equipment and adjust the downlink data transmission strategy to achieve communication with the user equipment and improve communication quality.

[0144] Optionally, the method further includes: receiving downlink non-IP data sent by the server and querying whether the user equipment is registered in satellite store-and-forward mode.

[0145] In this embodiment, when the SCS / AS sends downlink non-IP data to the UE, the SCS / AS can send a downlink non-IP data request to the SCEF. This downlink non-IP data request carries the downlink non-IP data. The SCEF then forwards the downlink non-IP data request to the MME. After receiving the downlink non-IP data request, the MME can determine whether the UE is registered in satellite store-and-forward mode.

[0146] Optionally, send a store-and-forward mode identifier and estimated data transmission time to the server, including sending a non-IP data response message to the server.

[0147] Non-IP data response messages must include at least a store-and-forward mode identifier and an estimated data transmission time.

[0148] In this embodiment, when the SCS / AS sends downlink non-IP data to the UE, if the MME determines that the UE is registered in satellite store-and-forward mode and the current service link is unavailable, the MME returns a non-IP data response message to the SCEF. This non-IP data response message carries a store-and-forward mode identifier and an estimated data transmission time. Then, the SCEF forwards the non-IP data response message to the SCS / AS. Upon receiving the non-IP data response message, the SCS / AS can parse it to obtain the store-and-forward mode identifier and the estimated data transmission time. Based on the store-and-forward mode identifier, the SCS / AS can determine that the UE is operating in store-and-forward mode. If there is remaining downlink data, the SCS / AS adjusts the downlink data transmission strategy based on the estimated data transmission time and the SCEF buffer settings.

[0149] With this solution, in scenarios where the SCS / AS sends downlink non-IP data to the UE, the SCS / AS can know the current operating mode of the user equipment and adjust the downlink data transmission strategy to achieve communication with the user equipment and improve communication quality.

[0150] Optionally, the method further includes: if the user equipment is registered in satellite store-and-forward mode and the service link is unavailable, then caching downlink non-IP data. After the MME caches the downlink non-IP data, the method further includes: if the service link is available, then sending downlink non-IP data to the user equipment; sending a new non-IP data response message to the server; wherein the new non-IP data response message carries an updated operating mode identifier and / or an updated estimated data transmission time, the operating mode identifier being used to indicate whether the user equipment is registered in satellite store-and-forward mode.

[0151] In this embodiment, if the UE is registered in satellite store-and-forward mode and the service link is unavailable, the MME can also cache downlink non-IP data. Thus, after the service link is restored, the MME detects that the service link is available and can send downlink non-IP data to the UE. Additionally, the MME can determine whether the UE's operating mode identifier and the estimated data transmission time have been updated. If either of these has been updated, a new non-IP data response message can be generated. This new non-IP data response message carries the updated operating mode identifier and / or the updated estimated data transmission time. The operating mode identifier indicates whether the user equipment is registered in satellite store-and-forward mode. The SCEF can forward the updated non-IP data response message to the SCS / AS.

[0152] This solution enables the MME to buffer downlink non-IP data when the SCS / AS sends it to the UE. If the serving link is unavailable, the MME can then send the downlink non-IP data to the UE upon the return of the serving link, ensuring successful transmission. Furthermore, the MME can update the operating mode identifier and estimated data transmission time in real time and notify the SCS / AS, allowing the SCS / AS to be aware of the latest operating mode identifier and estimated data transmission time and adjust its downlink data transmission strategy accordingly, thereby improving communication quality.

[0153] Optionally, the method further includes: receiving a downlink data notification message; if the current service link is unavailable, returning a downlink data confirmation message, and, if a reachability notification flag is set after downlink data transmission failure, querying whether the user equipment is registered in satellite store-and-forward mode.

[0154] In this embodiment, when the SCS / AS needs to send downlink IP data, the SCS / AS can send downlink IP data to the PGW. The PGW forwards the downlink IP data to the SGW, and then the SGW sends a downlink data notification message (DDN) to the MME. Upon receiving the downlink data notification message, the MME determines whether the current service link is available. If available, it continues the transmission of downlink IP data. If unavailable, the MME determines that a downlink data transmission failure event has occurred, sends a downlink data confirmation message to the SGW, and, if a reachability notification flag is set after downlink data transmission failure, queries whether the user equipment is registered in satellite store-and-forward mode.

[0155] Optionally, the store-and-forward mode identifier and estimated data transmission time are sent to the server, including: sending an event monitoring message to the server to notify the server of reachability after downlink data transmission failure; the event monitoring message carries the store-and-forward mode identifier and estimated data transmission time.

[0156] In this embodiment, when the SCS / AS needs to send downlink IP data, if the MME determines that the user equipment is registered in satellite store-and-forward mode, it triggers a Notify-on-available-after-DDN-failure event notification. The MME sends an event monitoring message of downlink data transmission failure reachability notification to the SCEF. This event monitoring message carries a store-and-forward mode identifier and an estimated data transmission time. The SCEF forwards this event monitoring message to the SCS / AS. The SCS / AS can parse the event monitoring message to obtain the store-and-forward mode identifier and the estimated data transmission time. Based on the store-and-forward mode identifier, the SCS / AS can determine that the UE is operating in store-and-forward mode and adjust the downlink data transmission strategy based on the estimated data transmission time and SCEF buffer settings.

[0157] Optionally, the method further includes: if a reachability notification flag is not currently set after downlink data transmission failure, then setting the reachability notification flag after downlink data transmission failure.

[0158] In this embodiment, if the current service link is unavailable, the MME determines whether the Notify-on-available-after-DDN-failure flag (i.e., the reachability notification flag after downlink data transmission failure) is set. If it is not set, the MME can set the Notify-on-available-after-DDN-failure flag; if it is set, the MME performs a judgment on whether the user equipment is registered in satellite store-and-forward mode, and subsequent processing.

[0159] This solution extends the existing available-after-DDN-failure event to scenarios where the SCS / AS sends downlink IP data to the UE. When the UE is registered in store-and-forward mode, the event monitoring message for this event is still triggered even if the UE is unreachable. The event monitoring message carries parameters such as the store-and-forward mode identifier and the estimated data transmission time. The SCS / AS can then know the current operating mode of the user equipment and adjust the downlink data transmission strategy to achieve communication with the user equipment and improve communication quality.

[0160] Optionally, if the user equipment is registered in satellite store-and-forward mode, it sends a store-and-forward mode identifier and an estimated data transmission time to the server, including: if the user equipment is detected to have successfully registered in satellite store-and-forward mode, it sends a first event notification message to the server, the first event notification message carrying the store-and-forward mode identifier; if the user equipment is detected to have corresponding data transmission and the current user equipment is registered in satellite store-and-forward mode, it sends a second event notification message to the server, the second event notification message carrying at least the estimated data transmission time.

[0161] In this embodiment, the MME or HSS can monitor whether the UE is registered in the satellite store-and-forward mode based on pre-configured monitoring events of the satellite store-and-forward mode. If the MME or HSS detects that the user equipment has successfully registered in the satellite store-and-forward mode, it sends a first event notification message to the SCEF. The first event notification message carries a store-and-forward mode identifier. The SCEF then forwards the first event notification message to the SCS / AS.

[0162] The MME can also monitor for data transmission events targeting the UE based on pre-configured data transmission time estimation monitoring events. These data transmission events can include, but are not limited to, uplink and downlink data transmissions. The transmitted data can be IP data or non-IP data; this embodiment does not impose any limitations. If the MME detects data transmission corresponding to the UE and the UE is currently registered in satellite store-and-forward mode, it sends a second event notification message to the SCEF. This second event notification message carries at least the estimated data transmission time. It may also carry a store-and-forward mode identifier. The SCEF then forwards the second event notification message to the SCS / AS.

[0163] SCS / AS can determine whether the terminal is operating in store-and-forward mode based on the received store-and-forward mode identifier, and adjust the downlink data transmission strategy based on information such as the estimated data transmission time and SCEF buffer settings.

[0164] Optionally, the method also includes: configuring monitoring events for satellite store-and-forward modes; and configuring monitoring events for estimated data transmission time.

[0165] In this embodiment of the application, monitoring events for satellite store-and-forward mode can be pre-configured in the MME or HSS; and monitoring events for estimated data transmission time can be configured in the MME.

[0166] This solution allows for the configuration of continuous, repeatable monitoring events for satellite store-and-forward mode and data estimated transmission time monitoring events for the MME and / or HSS. When the UE's operating mode changes to satellite store-and-forward mode during registration, or when data transmission is performed and the UE is found to be registered in satellite store-and-forward mode, corresponding event notifications are triggered, informing the SCS / AS of the store-and-forward mode identifier and data estimated transmission time, respectively. The SCS / AS can then determine the current operating mode of the user equipment and adjust its downlink data transmission strategy to achieve communication with the user equipment and improve communication quality.

[0167] In one embodiment, such as Figure 3 As shown, a data transmission method is provided, which is applied to... Figure 1 Taking the server in the example, the following steps are included:

[0168] Step 302: Receive the store-and-forward mode identifier and estimated data transmission time corresponding to the user equipment sent by the network element device.

[0169] In this embodiment, the SCS / AS can receive the store-and-forward mode identifier and estimated data transmission time sent by the MME or HSS via SCEF. The specific transmission process can be referred to... Figure 2 The relevant steps will not be repeated here.

[0170] This solution allows the SCS / AS to promptly determine the current operating mode of the user equipment and adjust downlink data transmission strategies, thereby improving communication quality. When the UE is operating in satellite store-and-forward mode, it avoids the problem of low data transmission success rates and resource waste caused by the SCS / AS's inability to determine the UE's operating mode during application data transmission.

[0171] Optionally, receiving the store-forward mode identifier and estimated data transmission time of the user equipment sent by the network element device includes: receiving a non-IP data request message sent by the network element device, wherein the non-IP data request message at least includes the store-forward mode identifier and the estimated data transmission time.

[0172] In this embodiment of the application, for uplink non-IP data initiated by the UE, the SCS / AS can receive a non-IP data request message sent by the MME. The non-IP data request message includes at least a store-and-forward mode identifier and an estimated data transmission time.

[0173] With this solution, in scenarios where the UE initiates uplink non-IP data, the SCS / AS can learn the current operating mode of the user equipment and adjust the downlink data transmission strategy to achieve communication with the user equipment and improve communication quality.

[0174] Optionally, the method further includes: sending downlink non-IP data to the network element device; correspondingly, receiving the store-forward mode identifier and estimated data transmission time corresponding to the user equipment sent by the network element device, including: receiving a non-IP data response message sent by the network element device, wherein the non-IP data response message at least includes the store-forward mode identifier and the estimated data transmission time.

[0175] In this embodiment, when the SCS / AS sends downlink non-IP data to the UE, the SCS / AS can send downlink non-IP data to the network element device so that the MME can query whether the UE is registered in satellite store-and-forward mode. If the UE is registered in satellite store-and-forward mode, the MME sends a non-IP data response message to the SCS / AS. The non-IP data response message includes at least a store-and-forward mode identifier and an estimated data transmission time. After receiving the non-IP data response message from the MME, the SCS / AS can parse the message to obtain the store-and-forward mode identifier and the estimated data transmission time. Based on the store-and-forward mode identifier, the SCS / AS can determine that the UE is operating in store-and-forward mode. If there is remaining downlink data, the SCS / AS adjusts the downlink data transmission strategy based on the estimated data transmission time and SCEF buffer settings.

[0176] With this solution, in scenarios where the SCS / AS sends downlink non-IP data to the UE, the SCS / AS can know the current operating mode of the user equipment and adjust the downlink data transmission strategy to achieve communication with the user equipment and improve communication quality.

[0177] Optionally, the method further includes: sending downlink IP data to the gateway device so that the gateway device sends a downlink data notification message to the network element device; correspondingly, receiving the store-and-forward mode identifier and estimated data transmission time of the user equipment sent by the network element device, including: receiving an event monitoring message of downlink data transmission failure reachability notification sent by the network element device; the event monitoring message carries the store-and-forward mode identifier and estimated data transmission time.

[0178] In this embodiment, when the SCS / AS needs to send downlink IP data, the SCS / AS can send downlink IP data to the PGW. The PGW forwards the downlink IP data to the SGW, and then the SGW sends a downlink data notification message to the MME. After receiving the downlink data notification message, the MME determines whether the current service link is available. If available, it continues the transmission of downlink IP data. If unavailable, the MME determines that a downlink data transmission failure event has occurred, sends a downlink data confirmation message to the SGW, and, if a downlink data transmission failure reachability notification flag is set, queries whether the UE is registered in satellite store-and-forward mode.

[0179] If the UE is registered in satellite store-and-forward mode, the MME sends an event monitoring message to the server to notify the UE of downlink data transmission failure. This event monitoring message carries a store-and-forward mode identifier and an estimated data transmission time. The SCS / AS can parse the event monitoring message to obtain the store-and-forward mode identifier and the estimated data transmission time. Based on the store-and-forward mode identifier, the SCS / AS can determine whether the UE is operating in store-and-forward mode and adjust the downlink data transmission strategy based on the estimated data transmission time and SCEF buffer settings.

[0180] This solution extends the existing available-after-DDN-failure event to scenarios where the SCS / AS sends downlink IP data to the UE. When the UE is registered in store-and-forward mode, the event monitoring message for this event is still triggered even if the UE is unreachable. The event monitoring message carries parameters such as the store-and-forward mode identifier and the estimated data transmission time. The SCS / AS can then know the current operating mode of the user equipment and adjust the downlink data transmission strategy to achieve communication with the user equipment and improve communication quality.

[0181] Optionally, receiving the store-and-forward mode identifier and estimated data transmission time corresponding to the user equipment sent by the network element device includes: receiving a first event notification message sent by the network element device, the first event notification message carrying the store-and-forward mode identifier; and receiving a second event notification message sent by the network element device, the second event notification message carrying at least the estimated data transmission time.

[0182] In this embodiment, the MME or HSS can monitor whether the UE is registered in the satellite store-and-forward mode based on pre-configured monitoring events of the satellite store-and-forward mode. If the MME or HSS detects that the UE has successfully registered in the satellite store-and-forward mode, it sends a first event notification message to the SCEF. The first event notification message carries a store-and-forward mode identifier. The SCEF then forwards the first event notification message to the SCS / AS. After receiving the first event notification message, the SCS / AS can parse it to obtain the store-and-forward mode identifier.

[0183] The MME can also monitor for data transmission events targeting the UE based on pre-configured data transmission time estimation monitoring events. These data transmission events can include, but are not limited to, uplink and downlink data transmissions. The transmitted data can be IP data or non-IP data; this embodiment does not impose any limitations. If the MME detects data transmission corresponding to the UE and the UE is currently registered in satellite store-and-forward mode, it sends a second event notification message to the SCEF. The second event notification message carries at least the estimated data transmission time. It may also carry a store-and-forward mode identifier. The SCEF then forwards the second event notification message to the SCS / AS. Upon receiving the second event notification message, the SCS / AS can parse it to obtain the estimated data transmission time and, optionally, the store-and-forward mode identifier.

[0184] This solution allows for the configuration of continuous, repeatable monitoring events for satellite store-and-forward mode and data estimated transmission time monitoring events for the MME and / or HSS. When the UE's operating mode changes to satellite store-and-forward mode during registration, or when data transmission is performed and the UE is found to be registered in satellite store-and-forward mode, corresponding event notifications are triggered, informing the SCS / AS of the store-and-forward mode identifier and data estimated transmission time, respectively. The SCS / AS can then determine the current operating mode of the user equipment and adjust its downlink data transmission strategy to achieve communication with the user equipment and improve communication quality.

[0185] Optionally, the method further includes: adjusting the downlink data transmission strategy of the user equipment based on the store-and-forward mode identifier and the estimated data transmission time.

[0186] In this embodiment, the SCS / AS can determine that the terminal is operating in store-and-forward mode based on the received store-and-forward mode identifier, and adjust the downlink data transmission strategy based on information such as the estimated data transmission time and SCEF buffer settings. Specifically, the SCS / AS can determine the downlink data transmission interval based on the estimated data transmission time; for example, it can wait for the estimated data transmission time before sending downlink data. The SCEF buffer settings can include the SCEF buffer capacity, and the SCS / AS can determine the amount of downlink data to be sent based on the SCEF buffer capacity to avoid downlink data exceeding the SCEF buffer capacity and causing data loss.

[0187] This solution allows the SCS / AS to adjust downlink data transmission strategies, enabling communication with user equipment and improving communication quality. When the UE is operating in satellite store-and-forward mode, it avoids the problem of low data transmission success rates and resource waste caused by the SCS / AS's inability to determine the UE's operating mode during application data transmission.

[0188] Optionally, the downlink data transmission strategy corresponding to the user equipment can be adjusted based on the store-and-forward mode identifier and the estimated data transmission time, including: if there is downlink data corresponding to the user equipment, the downlink data transmission strategy corresponding to the user equipment can be adjusted based on the store-and-forward mode identifier and the estimated data transmission time.

[0189] In this embodiment, for uplink non-IP data initiated by the UE, after receiving the non-IP data request message, the SCS / AS can parse the message to obtain the store-and-forward mode identifier and the estimated data transmission time. Based on the store-and-forward mode identifier, the SCS / AS can determine that the UE is operating in store-and-forward mode. If there is downlink data to be sent, the SCS / AS adjusts the downlink data transmission strategy based on the estimated data transmission time and SCEF buffer settings.

[0190] Optionally, the downlink data transmission strategy corresponding to the user equipment can be adjusted based on the store-and-forward mode identifier and the estimated data transmission time, including: if there is remaining downlink data corresponding to the user equipment, the downlink data transmission strategy corresponding to the user equipment can be adjusted based on the store-and-forward mode identifier and the estimated data transmission time.

[0191] In this embodiment, when the SCS / AS sends downlink non-IP data to the UE, after receiving the non-IP data response message, the SCS / AS can parse the message to obtain the store-and-forward mode identifier and the estimated data transmission time. Based on the store-and-forward mode identifier, the SCS / AS can determine that the UE is operating in store-and-forward mode. If there is remaining downlink data, the SCS / AS adjusts the downlink data transmission strategy based on the estimated data transmission time and SCEF buffer settings.

[0192] Understandable, refer to Figure 4 This is a schematic diagram of a data transmission method in an embodiment of this application. In this solution, during the UE registration process, the MME adds a monitoring event for the satellite store-and-forward mode. During data transmission, the store-and-forward mode identifier and the estimated data transmission time are sent by means of non-IP data request messages / non-IP data response messages, or by extending the existing available-after-DDN-failure event, or by adding a monitoring event for the estimated data transmission time. This enables the SCS / AS to know the current working mode of the user equipment and adjust the downlink data transmission strategy to achieve communication with the user equipment and improve communication quality.

[0193] In one embodiment, a data transmission system is provided, the system comprising network element devices and a server; wherein:

[0194] The network element device is used to send a store-and-forward mode identifier and an estimated data transmission time to the server if the user equipment is registered in the satellite store-and-forward mode.

[0195] The server is used to receive the store-and-forward mode identifier and estimated data transmission time of the user equipment sent by the network element device.

[0196] In this scheme, if the network element determines that the user equipment is registered in satellite store-and-forward mode, it can send a store-and-forward mode identifier and an estimated data transmission time to the server. The server can receive the store-and-forward mode identifier and estimated data transmission time corresponding to the user equipment sent by the network element. This allows the SCS / AS to promptly know the current operating mode of the user equipment and adjust its downlink data transmission strategy, thus enabling communication with the user equipment and improving communication quality.

[0197] In one embodiment, such as Figure 5 As shown, this application provides an example of a data transmission method that can be applied to a communication system. This communication system includes at least a UE and MME, an HSS, a SCEF, and a server. The user equipment is registered in satellite store-and-forward mode, and the user equipment establishes a PDN connection with the SCEF. The server is an SCS / AS. Specific steps include:

[0198] Step 501: The UE sends MO non-IP data (i.e., uplink non-IP data) to the MME.

[0199] Step 502: The MME determines whether the UE is registered in satellite store-and-forward mode.

[0200] If the UE is registered in satellite store-and-forward mode, proceed to step 503; otherwise, no processing is performed.

[0201] Step 503: The MME sends a NIDD transmission request (i.e., a non-IP data request message) to the SCEF.

[0202] The NIDD sending request includes a store-and-forward mode identifier and an estimated data transmission time. Optionally, the NIDD sending request may also include NIDD-related parameters such as non-IP data, identity identifier, and EPS bearer information.

[0203] Step 504: SCEF forwards the NIDD request to SCS / AS.

[0204] Step 505: SCS / AS sends a NIDD response message to SCEF.

[0205] Step 506: SCEF forwards the NIDD response message to MME.

[0206] Step 507: SCS / AS sends a request based on NIDD to determine that the UE is working in store-and-forward mode. If there is downlink data to be sent, SCS / AS adjusts the downlink data transmission strategy based on the estimated transmission time of the downlink data, SCEF buffer settings, and other information.

[0207] In one embodiment, such as Figure 6 As shown, this application provides an example of a data transmission method that can be applied to a communication system. This communication system includes at least a UE and MME, an HSS, a SCEF, and a server. The user equipment is registered in satellite store-and-forward mode, and the user equipment establishes a PDN connection with the SCEF. The SCEF stores the terminal's context information, and the server is an SCS / AS. The specific steps include:

[0208] Step 601: SCS / AS sends a downlink non-IP data request to SCEF.

[0209] The downlink non-IP data request contains downlink non-IP data.

[0210] Step 602: SCEF forwards the downlink non-IP data request to MME.

[0211] Step 603: The MME determines whether the UE is registered in satellite store-and-forward mode.

[0212] If the UE is registered in satellite store-and-forward mode, proceed to step 604; otherwise, no processing is performed.

[0213] Step 604: If the current service link is unavailable, store the downlink non-IP data.

[0214] Step 605: The MME returns a NIDD response message to the SCEF. The NIDD response message carries the store-and-forward mode identifier and the estimated data transmission time.

[0215] Step 606: SCEF forwards the NIDD response message to SCS / AS.

[0216] Step 607: Based on the NIDD response message, the SCS / AS determines that the terminal is working in store-and-forward mode. If there is downlink data to be sent, the SCS / AS adjusts the downlink data transmission strategy based on the estimated transmission time of the downlink data, SCEF buffer settings, and other information.

[0217] Step 608: When the service link is available, the MME sends the stored downlink non-IP data to the UE.

[0218] Step 609: The MME sends an updated NIDD response message to the SCEF.

[0219] The NIDD response message carries an updated operating mode identifier and / or an updated estimated data transmission time. The operating mode identifier is used to indicate whether the user equipment is registered in satellite store-and-forward mode.

[0220] Step 610: SCEF forwards the updated NIDD response message to SCS / AS.

[0221] In one embodiment, such as Figure 7 As shown, this application provides an example of a data transmission method that can be applied to a communication system. This communication system includes at least a UE and MME, an HSS, an SCEF, and a server. The user equipment is registered in satellite store-and-forward mode, the server is an SCS / AS, and the SCS / AS needs to send downlink IP data. Specific steps include:

[0222] Step 701: SCS / AS sends downlink IP data to PGW / SGW.

[0223] Step 702: SGW sends a DDN message to MME.

[0224] Step 703: If the current service link is unavailable, the MME determines that a DDN failure has occurred and returns DDNAcknowledge to the SGW.

[0225] Step 704: The MME determines whether the Notify-on-available-after-DDN-failure flag is set.

[0226] If not set, proceed to step 705; if set, proceed to step 706.

[0227] Step 705: Set the Notify-on-available-after-DDN-failure flag.

[0228] Step 706: The MME determines that the UE is registered in satellite store-and-forward mode and triggers a Notify-on-available-after-DDN-failure event notification. The MME sends a Notify-on-available-after-DDN-failure event monitoring message to the SCEF.

[0229] The event monitoring message includes a store-and-forward mode identifier and an estimated data transmission time.

[0230] Step 707: SCEF forwards the event monitoring message to SCS / AS.

[0231] Step 708: SCS / AS determines that the terminal is operating in store-and-forward mode and adjusts the downlink data transmission strategy based on information such as downlink data estimated transmission time and SCEF buffer settings.

[0232] In one embodiment, such as Figure 8 As shown, this application provides an example of a data transmission method that can be applied to a communication system. This communication system includes at least a UE and MME, an HSS, an SCEF, and a server. The user equipment is registered in satellite store-and-forward mode, and the server is an SCS / AS. The specific steps include:

[0233] Step 801: Configure monitoring events for satellite store-and-forward mode in MME or HSS; and configure monitoring events for estimated data transmission time.

[0234] Step 802: If the MME or HSS detects that the user equipment has successfully registered in satellite store-and-forward mode, it sends a first event notification message to the SCEF.

[0235] The first event notification message carries a store-and-forward mode identifier.

[0236] Understandable Figure 8 The following explanation uses MME execution steps 801 and 802 as examples; the execution process of HSS is not shown in the diagram.

[0237] Step 803: SCEF forwards the first event notification message to SCS / AS.

[0238] Step 804: If the MME detects that there is transmission data corresponding to the UE and the current UE is registered in satellite store-and-forward mode, it sends a second event notification message to the SCEF.

[0239] The second event notification message contains at least the estimated data transmission time.

[0240] Step 805: SCEF forwards the second event notification message to SCS / AS.

[0241] Step 806: The SCS / AS determines that the terminal is operating in store-and-forward mode and adjusts the downlink data transmission strategy based on information such as downlink data estimated transmission time and SCEF cache settings.

[0242] It should be understood that, although Figure 2-8 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figure 2-8At least some of the steps in the process may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but may be executed at different times. The execution order of these steps or stages is not necessarily sequential, but may be executed in turn or alternately with other steps or at least some of the steps or stages in other steps.

[0243] In one embodiment, such as Figure 9 As shown, a data transmission device 900 is provided, which is applied to a network element device. The device includes:

[0244] The first transmitting module 910 is used to send a store-and-forward mode identifier and an estimated data transmission time to the server if the user equipment is registered in satellite store-and-forward mode.

[0245] In one embodiment, the device further includes:

[0246] The first receiving module is used to receive uplink non-IP data sent by the user equipment and to query whether the user equipment is registered in satellite store-and-forward mode.

[0247] In one embodiment, the first sending module is specifically used for:

[0248] Send a non-IP data request message to the server, the non-IP data request message containing at least a store-and-forward mode identifier and an estimated data transmission time.

[0249] In one embodiment, the device further includes:

[0250] The second receiving module is used to receive downlink non-IP data sent by the server and query whether the user equipment is registered in satellite store-and-forward mode.

[0251] In one embodiment, the first sending module is specifically used for:

[0252] Send a non-IP data response message to the server, the non-IP data response message containing at least a store-and-forward mode identifier and an estimated data transmission time.

[0253] In one embodiment, the device further includes:

[0254] The caching module is used to cache the downlink non-IP data if the user equipment is registered in satellite store-and-forward mode and the service link is unavailable.

[0255] In one embodiment, the device further includes:

[0256] The second sending module is used to send the downlink non-IP data to the user equipment if the service link is available;

[0257] The third sending module is used to send a new non-IP data response message to the server; wherein the new non-IP data response message carries an updated operating mode identifier and / or an updated estimated data transmission time, and the operating mode identifier is used to indicate whether the user equipment is registered in satellite store-and-forward mode.

[0258] In one embodiment, the device further includes:

[0259] The third receiving module is used to receive downlink data notification messages;

[0260] The fourth sending module is used to return a downlink data confirmation message if the current service link is unavailable, and, if a downlink data transmission failure reachability notification flag is set, to query whether the user equipment is registered in satellite store-and-forward mode.

[0261] In one embodiment, the first sending module is specifically used for:

[0262] Send an event monitoring message to the server to notify of reachability after downlink data transmission failure; the event monitoring message carries a store-and-forward mode identifier and an estimated data transmission time.

[0263] In one embodiment, the device further includes:

[0264] The setting module is used to set the downlink data transmission failure reachability flag if the downlink data transmission failure reachability flag is not currently set.

[0265] In one embodiment, the first sending module is specifically used for:

[0266] If the monitoring detects that the user equipment has successfully registered in the satellite store-and-forward mode, a first event notification message is sent to the server. The first event notification message carries the store-and-forward mode identifier.

[0267] If the monitoring detects the existence of transmission data corresponding to the user equipment and the user equipment is currently registered in satellite store-and-forward mode, a second event notification message is sent to the server. The second event notification message carries at least the estimated data transmission time.

[0268] In one embodiment, the device further includes:

[0269] The configuration module is used to configure monitoring events for satellite store-and-forward mode and to configure monitoring events for estimated data transmission time.

[0270] In one embodiment, the network element device is an MME or an HSS.

[0271] In one embodiment, such as Figure 10 As shown, a data transmission device 1000 is provided, which is applied to a server, and the device includes:

[0272] The first receiving module 1010 is used to receive the store-and-forward mode identifier and estimated data transmission time of the user equipment sent by the network element device.

[0273] In one embodiment, the first receiving module is specifically used for:

[0274] Receive a non-IP data request message sent by a network element device, wherein the non-IP data request message includes at least a store-and-forward mode identifier and an estimated data transmission time.

[0275] In one embodiment, the device further includes:

[0276] The first sending module is used to send downlink non-IP data to the network element device;

[0277] The first receiving module is specifically used for:

[0278] Receive a non-IP data response message sent by a network element device, wherein the non-IP data response message includes at least a store-and-forward mode identifier and an estimated data transmission time.

[0279] In one embodiment, the device further includes:

[0280] The second sending module is used to send downlink IP data to the gateway device so that the gateway device sends a downlink data notification message to the network element device.

[0281] The first receiving module is specifically used for:

[0282] The system receives an event monitoring message from a network element device notifying the network that downlink data transmission has failed. The event monitoring message carries a store-and-forward mode identifier and an estimated data transmission time.

[0283] In one embodiment, the first receiving module is specifically used for:

[0284] Receive a first event notification message sent by a network element device, wherein the first event notification message carries a store-and-forward mode identifier;

[0285] The network element receives a second event notification message, which carries at least the estimated data transmission time.

[0286] In one embodiment, the device further includes:

[0287] The adjustment module is used to adjust the downlink data transmission strategy corresponding to the user equipment based on the store-and-forward mode identifier and the estimated data transmission time.

[0288] In one embodiment, the adjustment module is specifically used for:

[0289] If downlink data corresponding to the user equipment exists, the downlink data transmission strategy corresponding to the user equipment is adjusted based on the store-and-forward mode identifier and the estimated data transmission time.

[0290] In one embodiment, the adjustment module is specifically used to: if there is remaining downlink data corresponding to the user equipment, adjust the downlink data transmission strategy corresponding to the user equipment based on the store-and-forward mode identifier and the estimated data transmission time.

[0291] Specific limitations regarding the data transmission device can be found in the limitations regarding the data transmission method above, and will not be repeated here. Each module in the aforementioned data transmission device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0292] In one embodiment, Figure 11 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device can be a network element or a server. The communication device may include a receiver 1101, a memory 1102, a processor 1103, at least one communication bus 1104, and a transmitter 1105. The communication bus 1104 is used to implement communication connections between components. The memory 1102 may include high-speed RAM, and may also include non-volatile memory (NVM), such as at least one disk storage. The memory 1102 can store various programs for performing various processing functions and implementing the method steps of this embodiment. In this embodiment, the transmitter 1105 can be a radio frequency processing module or a baseband processing module in the communication device, and the receiver 1101 can also be a radio frequency processing module or a baseband processing module in the communication device. The transmitter 1105 and receiver 1101 can be integrated together to form a transceiver. Both the transmitter 1105 and receiver 1101 can be coupled to the processor 1103, and can perform receiving or transmitting actions under the instruction or control of the processor 1103.

[0293] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described above.

[0294] In one embodiment, a computer program product includes a computer program that, when executed by a processor, implements the steps of the method described above.

[0295] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0296] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0297] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A data transmission method, characterized in that, The method is applied to network element devices, and the method includes: If the user equipment is registered in satellite store-and-forward mode, it sends a store-and-forward mode identifier and an estimated data transmission time to the server.

2. The method according to claim 1, characterized in that, The method further includes: Receive uplink non-IP data sent by the user equipment and query whether the user equipment is registered in satellite store-and-forward mode.

3. The method according to claim 2, characterized in that, Sending the store-and-forward mode identifier and estimated data transmission time to the server includes: Send a non-IP data request message to the server, the non-IP data request message containing at least a store-and-forward mode identifier and an estimated data transmission time.

4. The method according to claim 1, characterized in that, The method further includes: Receive downlink non-IP data sent by the server and query whether the user equipment is registered in satellite store-and-forward mode.

5. The method according to claim 4, characterized in that, Sending the store-and-forward mode identifier and estimated data transmission time to the server includes: Send a non-IP data response message to the server, the non-IP data response message including at least a store-and-forward mode identifier and an estimated data transmission time.

6. The method according to claim 4, characterized in that, The method further includes: If the user equipment is registered in satellite store-and-forward mode and the service link is unavailable, the downlink non-IP data is cached.

7. The method according to claim 6, characterized in that, After caching the downlink non-IP data, the method further includes: If the service link is available, the downlink non-IP data is sent to the user equipment; Send a new non-IP data response message to the server; wherein the new non-IP data response message carries an updated operating mode identifier and / or an updated estimated data transmission time, the operating mode identifier being used to indicate whether the user equipment is registered in satellite store-and-forward mode.

8. The method according to claim 1, characterized in that, The method further includes: Receive downlink data notification messages; If the current service link is unavailable, a downlink data confirmation message is returned, and if a reachability notification flag is set after downlink data transmission failure, the user equipment is queried to see if it is registered in satellite store-and-forward mode.

9. The method according to claim 8, characterized in that, Sending the store-and-forward mode identifier and estimated data transmission time to the server includes: Send an event monitoring message to the server to notify that downlink data transmission has failed; the event monitoring message carries a store-and-forward mode identifier and an estimated data transmission time.

10. The method according to claim 8, characterized in that, The method further includes: If a reachability notification flag is not currently set after downlink data transmission failure, then the reachability notification flag is set.

11. The method according to claim 1, characterized in that, If the user equipment is registered in satellite store-and-forward mode, sending a store-and-forward mode identifier and estimated data transmission time to the server includes: If the monitoring detects that the user equipment has successfully registered in the satellite store-and-forward mode, a first event notification message is sent to the server. The first event notification message carries the store-and-forward mode identifier. If the monitoring detects the existence of transmission data corresponding to the user equipment and the user equipment is currently registered in satellite store-and-forward mode, a second event notification message is sent to the server. The second event notification message carries at least the estimated data transmission time.

12. The method according to claim 11, characterized in that, The method further includes: Monitoring events configured for satellite store-and-forward mode; and, Configure monitoring events for estimated data transmission time.

13. The method according to any one of claims 1 to 12, characterized in that, The network element device is an MME or an HSS.

14. A data transmission method, characterized in that, The method is applied to a server, and the method includes: The network element sends the user equipment's store-and-forward mode identifier and estimated data transmission time.

15. The method according to claim 14, characterized in that, The store-and-forward mode identifier and estimated data transmission time corresponding to the user equipment sent by the receiving network element device include: Receive a non-IP data request message sent by a network element device, wherein the non-IP data request message includes at least a store-and-forward mode identifier and an estimated data transmission time.

16. The method according to claim 14, characterized in that, The method further includes: Send downlink non-IP data to the network element device; The store-and-forward mode identifier and estimated data transmission time corresponding to the user equipment sent by the receiving network element device include: Receive a non-IP data response message sent by a network element device, wherein the non-IP data response message includes at least a store-and-forward mode identifier and an estimated data transmission time.

17. The method according to claim 14, characterized in that, The method further includes: Send downlink IP data to the gateway device so that the gateway device sends a downlink data notification message to the network element device; The store-and-forward mode identifier and estimated data transmission time corresponding to the user equipment sent by the receiving network element device include: The system receives an event monitoring message from a network element device notifying the network that downlink data transmission has failed. The event monitoring message carries a store-and-forward mode identifier and an estimated data transmission time.

18. The method according to claim 14, characterized in that, The store-and-forward mode identifier and estimated data transmission time corresponding to the user equipment sent by the receiving network element device include: Receive a first event notification message sent by a network element device, wherein the first event notification message carries a store-and-forward mode identifier; The network element receives a second event notification message, which carries at least the estimated data transmission time.

19. The method according to any one of claims 14 to 18, characterized in that, The method further includes: Based on the store-and-forward mode identifier and the estimated data transmission time, the downlink data transmission strategy corresponding to the user equipment is adjusted.

20. The method according to claim 19, characterized in that, The step of adjusting the downlink data transmission strategy corresponding to the user equipment based on the store-and-forward mode identifier and the estimated data transmission time includes: If downlink data corresponding to the user equipment exists, the downlink data transmission strategy corresponding to the user equipment is adjusted based on the store-and-forward mode identifier and the estimated data transmission time.

21. The method according to claim 19, characterized in that, The step of adjusting the downlink data transmission strategy corresponding to the user equipment based on the store-and-forward mode identifier and the estimated data transmission time includes: If there is remaining downlink data corresponding to the user equipment, the downlink data transmission strategy corresponding to the user equipment is adjusted based on the store-and-forward mode identifier and the estimated data transmission time.

22. A data transmission device, characterized in that, The device is applied to a network element device, and the device includes: The first sending module is used to send a store-and-forward mode identifier and an estimated data transmission time to the server if the user equipment is registered in satellite store-and-forward mode.

23. A data transmission device, characterized in that, The device is used in a server, and the device includes: The first receiving module is used to receive the store-and-forward mode identifier and estimated data transmission time of the user equipment sent by the network element device.

24. A data transmission system, characterized in that, The system includes network element devices and servers; wherein: The network element device is used to send a store-forward mode identifier and an estimated data transmission time to the server if the user equipment is registered in the satellite store-forward mode. The server is used to receive the store-and-forward mode identifier and estimated data transmission time of the user equipment sent by the network element device.

25. A communication device, characterized in that, include: Transmitter; The transmitter is used to send a store-and-forward mode identifier and an estimated data transmission time to the server if the user equipment is registered in satellite store-and-forward mode.

26. A communication device, characterized in that, include: Receiver; The receiver is used to receive the store-and-forward mode identifier and estimated data transmission time of the user equipment sent by the network element device.

27. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 13 or claims 14 to 21.

28. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 13 or claims 14 to 21.

Images