Data transmission method, device and equipment

The data transmission method ensures accurate data reception in non-end-to-end connections by using a session with fixed identification and time information to maintain resource allocation, addressing the challenge of undefined data delivery in such scenarios.

CN119135236APending Publication Date: 2024-12-13DATANG MOBILE COMM EQUIP CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310697642.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-06-13
Publication Date
2024-12-13

AI Technical Summary

Technical Problem

In non-end-to-end connections, there is no clear definition on how a terminal obtains downlink data from a remote application server, leading to inaccurate delivery of data to the target terminal.

Method used

A data transmission method involving a terminal receiving first information of a first session from a satellite device, which includes fixed session identification and time information, allowing the terminal to accurately receive downlink data through a session that continuously occupies allocated resources.

Benefits of technology

Ensures accurate data reception by the target terminal in non-end-to-end connections by maintaining a session that continuously occupies allocated resources, enabling the network to determine the correct terminal for data delivery.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119135236A_ABST
    Figure CN119135236A_ABST
Patent Text Reader

Abstract

The invention provides a data transmission method, device and equipment, and the method comprises the steps: receiving first information of a first session sent by satellite equipment; receiving downlink data through the first session according to the first information; wherein the first session refers to a session continuously occupying the allocated resources; the first information comprises fixed session identification information and time information of continuously occupying the allocated resources by the session. According to the scheme, the terminal can accurately receive the corresponding downlink data through the maintained first session; under the condition of supporting non-end-to-end connection, the network can accurately determine the terminal corresponding to the downlink data through the maintained first session, thereby ensuring that the target terminal accurately receives the downlink data; the problem that in the prior art, under the condition of non-end-to-end connection, it cannot be guaranteed that the target terminal accurately receives downlink data is well solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a data transmission method, device and equipment. Background Art

[0002] In the prior art, data exchange between terminals and application servers relies on end-to-end connections. When the network enables on-board store-and-forward operations from terminals to servers, the end-to-end connection between the terminal and the application server will no longer exist, and data cannot be exchanged in real time through end-to-end connections. However, there is currently no clear definition of how a terminal can obtain downlink data from a remote application server through a non-end-to-end connection.

[0003] From the above, at present, there is no clear definition on how the terminal obtains downlink data from the application server based on a non-end-to-end connection after enabling on-board store-and-forwarding; and based on this, in the case of such a non-end-to-end connection, the network cannot accurately determine the target terminal corresponding to the downlink data, which makes it impossible to ensure that the target terminal accurately receives the downlink data. Summary of the invention

[0004] The purpose of the present application is to provide a data transmission method, device and equipment to solve the problem in the prior art that in the case of non-end-to-end connection, it is impossible to ensure that the target terminal accurately receives downlink data.

[0005] In order to solve the above technical problems, an embodiment of the present application provides a data transmission method, which is applied to a terminal, including:

[0006] receiving first information of a first session sent by a satellite device;

[0007] receiving downlink data through the first session according to the first information;

[0008] The first session refers to a session that continuously occupies the allocated resources;

[0009] The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

[0010] Optionally, the first information further includes at least one of the following:

[0011] A response method for receiving downlink data;

[0012] Paging time window;

[0013] Periodic registration timer;

[0014] Satellite identification.

[0015] Optionally, before receiving the first information of the first session sent by the satellite device, the method further includes:

[0016] Sending a first request to the satellite device according to the downlink data receiving demand information;

[0017] The receiving first information of the first session sent by the satellite device includes:

[0018] receiving a first response fed back by the satellite device, where the first response carries first information of a first session;

[0019] The first request carries at least one of the following:

[0020] Receive uplink data delivery confirmation;

[0021] Waiting to receive downlink data;

[0022] Receiving priority of downlink data;

[0023] Service type corresponding to the session.

[0024] Optionally, also include:

[0025] According to the first response, retaining air interface resources and session information corresponding to the session;

[0026] The air interface resources are used to receive downlink data.

[0027] Optionally, before receiving downlink data through the first session according to the first information, the method further includes:

[0028] Accessing the satellite device according to the first parameter, and sending a second request to the satellite device, wherein the second request is used to obtain information of a downlink data buffer component on the satellite device or to indicate receiving downlink data or to request registration or to request sending uplink data;

[0029] receiving a second response fed back by the satellite device, where the second response carries information of the downlink data buffer component or carries indication information instructing the terminal to use resources corresponding to the first session to receive downlink data;

[0030] The receiving downlink data through the first session according to the first information includes:

[0031] receiving, through the first session, downlink data sent by the downlink data buffer component on the satellite device according to the first information and the information of the downlink data buffer component or the indication information;

[0032] The first parameter includes at least one of: uplink data transmission status, candidate response modes for receiving downlink data, locally stored first session information, reasons for network paging, and relevant identifiers of the satellite device.

[0033] Optionally, the second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving mode for downlink data supported by the terminal;

[0034] And / or, the second response carries a downlink data receiving mode allowed by the satellite device.

[0035] Optionally, also include:

[0036] A receiving mode for downlink data supported by the terminal is sent to the satellite device.

[0037] Optionally, the receiving, through the first session, downlink data sent by a downlink data buffer component on the satellite device includes:

[0038] The downlink data sent by the satellite device according to the receiving mode and using the downlink data buffer component on the satellite device is received through the first session.

[0039] Optionally, also include:

[0040] Determine a first mapping relationship between the session identification information of the first session and the air interface resources;

[0041] The step of accessing the satellite device according to the first parameter includes:

[0042] The satellite device is accessed according to the first parameter and the first mapping relationship.

[0043] Optionally, the first session is a protocol data unit (PDU) session or a non-PDU session.

[0044] The embodiment of the present application also provides a data transmission method, which is applied to a satellite device, including:

[0045] Sending first information of a first session to a terminal;

[0046] Sending downlink data to the terminal through the first session according to the first information;

[0047] The first session refers to a session that continuously occupies the allocated resources;

[0048] The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

[0049] Optionally, the first information further includes at least one of the following:

[0050] A response method for receiving downlink data;

[0051] Paging time window;

[0052] Periodic registration timer;

[0053] Satellite identification.

[0054] Optionally, also include:

[0055] Determine the response mode for receiving downlink data according to the reference information; wherein the reference information includes: the time information, and at least one of the downlink receiving priority;

[0056] And / or, determining a paging time window or a periodic registration timer corresponding to the terminal according to the ephemeris information of the satellite device.

[0057] Optionally, also include:

[0058] Determining, according to the response mode for receiving downlink data, to initiate paging or wait for the terminal to access;

[0059] Wherein, when it is determined to initiate paging, the terminal is instructed to receive downlink data in the paging reason.

[0060] Optionally, before sending the first information of the first session to the terminal, the method further includes:

[0061] receiving a first request sent by the terminal;

[0062] The sending the first information of the first session to the terminal includes:

[0063] Feedback a first response to the terminal according to the first request, where the first response carries first information of the first session;

[0064] The first request carries at least one of the following:

[0065] Receive uplink data delivery confirmation;

[0066] Waiting to receive downlink data;

[0067] Receiving priority of downlink data;

[0068] Service type corresponding to the session.

[0069] Optionally, also include:

[0070] Reserving system resources and session information of the session corresponding to the first response;

[0071] The system resources are used to send downlink data.

[0072] Optionally, feeding back a first response to the terminal according to the first request includes:

[0073] In a case where the first request indicates a request to activate the on-board store-and-forward operation or the terminal has activated the on-board store-and-forward operation, allocating resources and establishing a first session or updating an existing session to the first session according to the first request;

[0074] According to the first session, a first response is fed back to the terminal.

[0075] Optionally, before sending downlink data to the terminal through the first session according to the first information, the method further includes:

[0076] receiving a second request sent by the terminal, where the second request is used to obtain information of a downlink data buffer component on the satellite device or to indicate receiving downlink data or to request registration or to request sending uplink data;

[0077] Feedback a second response to the terminal according to the second request, where the second response carries information of the downlink data buffer component or carries indication information instructing the terminal to use the resources corresponding to the first session to receive downlink data;

[0078] The sending downlink data to the terminal through the first session according to the first information includes:

[0079] According to the first information and the information of the downlink data buffer component or the indication information, the downlink data is sent to the terminal through the first session by utilizing the downlink data buffer component on the satellite device.

[0080] Optionally, the second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving mode for downlink data supported by the terminal;

[0081] And / or, the second response carries a downlink data receiving mode allowed by the satellite device.

[0082] Optionally, also include:

[0083] A receiving mode for downlink data supported by the terminal is received and sent by the terminal.

[0084] Optionally, the sending the downlink data to the terminal through the first session by using the downlink data buffer component on the satellite device includes:

[0085] According to the first information and the receiving mode for downlink data supported by the terminal, the downlink data is sent to the terminal through the first session by utilizing the downlink data buffer component on the satellite device.

[0086] Optionally, the first session is a protocol data unit (PDU) session or a non-PDU session.

[0087] Optionally, also include:

[0088] caching a notification for the terminal, the notification being used to indicate that the terminal has activated an on-board store-and-forward operation;

[0089] The notification carries downlink data storage and forwarding information, and the downlink data storage and forwarding information includes: downlink data sending mode, the terminal identifier, PDU session identifier, on-board storage configuration, candidate user address identifier, and at least one of the candidate user IP addresses.

[0090] Optionally, also include:

[0091] The notification is sent to a server.

[0092] Optionally, before sending downlink data to the terminal through the first session according to the first information, the method further includes:

[0093] Determining a downlink data sending mode according to the second information;

[0094] The second information includes: at least one of the intersatellite link status information and the server's downlink data storage and forwarding request; the downlink data storage and forwarding request includes: at least one of the downlink forwarding strategy, forwarding priority and downlink data delivery confirmation method.

[0095] Optionally, also include:

[0096] Feedback a downlink data storage and forwarding response to the server according to the downlink data sending mode;

[0097] Among them, the downlink data storage forwarding response carries downlink data storage forwarding information, and the downlink data storage forwarding information includes: the downlink data sending method, the terminal identifier, the PDU session identifier, the on-board storage configuration, the expected time of delivery of the downlink data, the candidate user address identifier, and at least one of the candidate user IP addresses.

[0098] Optionally, the on-board storage configuration includes: at least one of a cache space and a retention time of cached data;

[0099] Alternatively, the on-board storage configuration does not include: cache space and retention time of cache data, and the downlink data storage and forwarding information also includes: cache space, and at least one of retention time of cache data.

[0100] Optionally, the downlink data storage and forwarding information also includes: relevant information for monitoring the satellite device.

[0101] Optionally, also include:

[0102] Determine a second mapping relationship between the identifier of the terminal, the identifier of the first session, and a related identifier of the server.

[0103] The embodiment of the present application also provides a data transmission method, which is applied to a server, including:

[0104] Receiving downlink data storage and forwarding information sent by satellite equipment;

[0105] Sending downlink data to the satellite device according to the downlink data storage and forwarding information;

[0106] The downlink data storage and forwarding information includes: downlink data sending mode, terminal identifier, PDU session identifier, on-board storage configuration, estimated time of downlink data delivery, candidate user address identifier, and at least one of the candidate user IP address;

[0107] The downlink data storage and forwarding information is carried in a notification to the terminal, where the notification is used to indicate that the terminal has activated the on-board storage and forwarding operation, or is carried in a downlink data storage and forwarding response.

[0108] Optionally, the sending downlink data to a satellite device according to the downlink data storage and forwarding information includes any one of the following:

[0109] In the process of receiving the uplink buffer data, sending the downlink data to the satellite device according to the downlink data storage and forwarding information;

[0110] The downlink data is sent to the satellite device according to the downlink data storage and forwarding information and the downlink data sending requirement information.

[0111] Optionally, before receiving the downlink data storage and forwarding information sent by the satellite device, the method further includes:

[0112] Sending a downlink data storage and forwarding request of the server to the satellite device;

[0113] The downlink data storage and forwarding request includes: at least one of a downlink forwarding strategy, a forwarding priority, and a downlink data delivery confirmation method.

[0114] The embodiment of the present application further provides a data transmission device, which is a terminal and includes a memory, a transceiver, and a processor:

[0115] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0116] Receiving, by the transceiver, first information of a first session sent by a satellite device;

[0117] receiving downlink data through the first session according to the first information;

[0118] The first session refers to a session that continuously occupies the allocated resources;

[0119] The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

[0120] Optionally, the first information further includes at least one of the following:

[0121] A response method for receiving downlink data;

[0122] Paging time window;

[0123] Periodic registration timer;

[0124] Satellite identification.

[0125] Optionally, the operation further includes:

[0126] Before receiving the first information of the first session sent by the satellite device, sending a first request to the satellite device through the transceiver according to the downlink data reception requirement information;

[0127] The receiving first information of the first session sent by the satellite device includes:

[0128] receiving a first response fed back by the satellite device, where the first response carries first information of a first session;

[0129] The first request carries at least one of the following:

[0130] Receive uplink data delivery confirmation;

[0131] Waiting to receive downlink data;

[0132] Receiving priority of downlink data;

[0133] Service type corresponding to the session.

[0134] Optionally, the operation further includes:

[0135] According to the first response, retaining air interface resources and session information corresponding to the session;

[0136] The air interface resources are used to receive downlink data.

[0137] Optionally, the operation further includes:

[0138] Before receiving downlink data through the first session according to the first information, accessing the satellite device according to the first parameter, and sending a second request to the satellite device through the transceiver, the second request being used to obtain information of a downlink data buffer component on the satellite device or to indicate receiving downlink data or to request registration or to request sending uplink data;

[0139] receiving, by the transceiver, a second response fed back by the satellite device, where the second response carries information of the downlink data buffer component or carries indication information instructing the terminal to use resources corresponding to the first session to receive downlink data;

[0140] The receiving downlink data through the first session according to the first information includes:

[0141] receiving, through the first session, downlink data sent by the downlink data buffer component on the satellite device according to the first information and the information of the downlink data buffer component or the indication information;

[0142] The first parameter includes at least one of: uplink data transmission status, candidate response modes for receiving downlink data, locally stored first session information, reasons for network paging, and relevant identifiers of the satellite device.

[0143] Optionally, the second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving mode for downlink data supported by the terminal;

[0144] And / or, the second response carries a downlink data receiving mode allowed by the satellite device.

[0145] Optionally, the operation further includes:

[0146] The receiving mode for downlink data supported by the terminal is sent to the satellite device through the transceiver.

[0147] Optionally, the receiving, through the first session, downlink data sent by a downlink data buffer component on the satellite device includes:

[0148] The downlink data sent by the satellite device according to the receiving mode and using the downlink data buffer component on the satellite device is received through the first session.

[0149] Optionally, the operation further includes:

[0150] Determine a first mapping relationship between the session identification information of the first session and the air interface resources;

[0151] The step of accessing the satellite device according to the first parameter includes:

[0152] The satellite device is accessed according to the first parameter and the first mapping relationship.

[0153] Optionally, the first session is a protocol data unit (PDU) session or a non-PDU session.

[0154] The embodiment of the present application further provides a data transmission device, which is a satellite device, including a memory, a transceiver, and a processor:

[0155] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0156] Sending, via the transceiver, first information of a first session to a terminal;

[0157] Sending downlink data to the terminal through the first session according to the first information;

[0158] The first session refers to a session that continuously occupies the allocated resources;

[0159] The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

[0160] Optionally, the first information further includes at least one of the following:

[0161] A response method for receiving downlink data;

[0162] Paging time window;

[0163] Periodic registration timer;

[0164] Satellite identification.

[0165] Optionally, the operation further includes:

[0166] Determine the response mode for receiving downlink data according to the reference information; wherein the reference information includes: the time information, and at least one of the downlink receiving priority;

[0167] And / or, determining a paging time window or a periodic registration timer corresponding to the terminal according to the ephemeris information of the satellite device.

[0168] Optionally, the operation further includes:

[0169] Determining, according to the response mode for receiving downlink data, to initiate paging or wait for the terminal to access;

[0170] Wherein, when it is determined to initiate paging, the terminal is instructed to receive downlink data in the paging reason.

[0171] Optionally, the operation further includes:

[0172] Before sending first information of a first session to a terminal, receiving, by the transceiver, a first request sent by the terminal;

[0173] The sending the first information of the first session to the terminal includes:

[0174] Feedback a first response to the terminal according to the first request, where the first response carries first information of the first session;

[0175] The first request carries at least one of the following:

[0176] Receive uplink data delivery confirmation;

[0177] Waiting to receive downlink data;

[0178] Receiving priority of downlink data;

[0179] Service type corresponding to the session.

[0180] Optionally, the operation further includes:

[0181] Reserving system resources and session information of the session corresponding to the first response;

[0182] The system resources are used to send downlink data.

[0183] Optionally, feeding back a first response to the terminal according to the first request includes:

[0184] In a case where the first request indicates a request to activate the on-board store-and-forward operation or the terminal has activated the on-board store-and-forward operation, allocating resources and establishing a first session or updating an existing session to the first session according to the first request;

[0185] According to the first session, a first response is fed back to the terminal.

[0186] Optionally, the operation further includes:

[0187] Before sending downlink data to the terminal through the first session according to the first information, receiving a second request sent by the terminal through the transceiver, the second request being used to obtain information of a downlink data buffer component on the satellite device or to indicate receiving downlink data or to request registration or to request sending uplink data;

[0188] Feedback a second response to the terminal according to the second request, where the second response carries information of the downlink data buffer component or carries indication information instructing the terminal to use the resources corresponding to the first session to receive downlink data;

[0189] The sending downlink data to the terminal through the first session according to the first information includes:

[0190] According to the first information and the information of the downlink data buffer component or the indication information, the downlink data is sent to the terminal through the first session by utilizing the downlink data buffer component on the satellite device.

[0191] Optionally, the second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving mode for downlink data supported by the terminal;

[0192] And / or, the second response carries a downlink data receiving mode allowed by the satellite device.

[0193] Optionally, the operation further includes:

[0194] A receiving mode for downlink data supported by the terminal and sent by the terminal is received through the transceiver.

[0195] Optionally, the sending the downlink data to the terminal through the first session by using the downlink data buffer component on the satellite device includes:

[0196] According to the first information and the receiving mode for downlink data supported by the terminal, the downlink data is sent to the terminal through the first session by utilizing the downlink data buffer component on the satellite device.

[0197] Optionally, the first session is a protocol data unit (PDU) session or a non-PDU session.

[0198] Optionally, the operation further includes:

[0199] caching a notification for the terminal, the notification being used to indicate that the terminal has activated an on-board store-and-forward operation;

[0200] The notification carries downlink data storage and forwarding information, and the downlink data storage and forwarding information includes: downlink data sending mode, the terminal identifier, PDU session identifier, on-board storage configuration, candidate user address identifier, and at least one of the candidate user IP addresses.

[0201] Optionally, the operation further includes:

[0202] The notification is sent to a server via the transceiver.

[0203] Optionally, the operation further includes:

[0204] Before sending downlink data to the terminal through the first session according to the first information, determining a downlink data sending mode according to the second information;

[0205] The second information includes: at least one of the intersatellite link status information and the server's downlink data storage and forwarding request; the downlink data storage and forwarding request includes: at least one of the downlink forwarding strategy, forwarding priority and downlink data delivery confirmation method.

[0206] Optionally, the operation further includes:

[0207] Feedback a downlink data storage and forwarding response to the server according to the downlink data sending mode;

[0208] Among them, the downlink data storage forwarding response carries downlink data storage forwarding information, and the downlink data storage forwarding information includes: the downlink data sending method, the terminal identifier, the PDU session identifier, the on-board storage configuration, the expected time of delivery of the downlink data, the candidate user address identifier, and at least one of the candidate user IP addresses.

[0209] Optionally, the on-board storage configuration includes: at least one of a cache space and a retention time of cached data;

[0210] Alternatively, the on-board storage configuration does not include: cache space and retention time of cache data, and the downlink data storage and forwarding information also includes: cache space, and at least one of retention time of cache data.

[0211] Optionally, the downlink data storage and forwarding information also includes: relevant information for monitoring the satellite device.

[0212] Optionally, the operation further includes:

[0213] Determine a second mapping relationship between the identifier of the terminal, the identifier of the first session, and a related identifier of the server.

[0214] The embodiment of the present application further provides a data transmission device, which is a server and includes a memory, a transceiver, and a processor:

[0215] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0216] Receiving downlink data storage and forwarding information sent by satellite equipment through the transceiver;

[0217] Sending downlink data to the satellite device through the transceiver according to the downlink data storage and forwarding information;

[0218] The downlink data storage and forwarding information includes: downlink data sending mode, terminal identifier, PDU session identifier, on-board storage configuration, estimated time of downlink data delivery, candidate user address identifier, and at least one of the candidate user IP address;

[0219] The downlink data storage and forwarding information is carried in a notification to the terminal, where the notification is used to indicate that the terminal has activated the on-board storage and forwarding operation, or is carried in a downlink data storage and forwarding response.

[0220] Optionally, the sending downlink data to a satellite device according to the downlink data storage and forwarding information includes any one of the following:

[0221] In the process of receiving the uplink buffer data, sending the downlink data to the satellite device according to the downlink data storage and forwarding information;

[0222] The downlink data is sent to the satellite device according to the downlink data storage and forwarding information and the downlink data sending requirement information.

[0223] Optionally, the operation further includes:

[0224] Before receiving the downlink data storage and forwarding information sent by the satellite device, sending a downlink data storage and forwarding request of the server to the satellite device through the transceiver;

[0225] The downlink data storage and forwarding request includes: at least one of a downlink forwarding strategy, a forwarding priority, and a downlink data delivery confirmation method.

[0226] The embodiment of the present application also provides a data transmission device, applied to a terminal, including:

[0227] A first receiving unit, configured to receive first information of a first session sent by a satellite device;

[0228] A second receiving unit, configured to receive downlink data through the first session according to the first information;

[0229] The first session refers to a session that continuously occupies the allocated resources;

[0230] The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

[0231] Optionally, the first information further includes at least one of the following:

[0232] A response method for receiving downlink data;

[0233] Paging time window;

[0234] Periodic registration timer;

[0235] Satellite identification.

[0236] Optionally, also include:

[0237] A first sending unit is configured to send a first request to the satellite device according to the downlink data reception requirement information before receiving the first information of the first session sent by the satellite device;

[0238] The receiving first information of the first session sent by the satellite device includes:

[0239] receiving a first response fed back by the satellite device, where the first response carries first information of a first session;

[0240] The first request carries at least one of the following:

[0241] Receive uplink data delivery confirmation;

[0242] Waiting to receive downlink data;

[0243] Receiving priority of downlink data;

[0244] Service type corresponding to the session.

[0245] Optionally, also include:

[0246] A first processing unit, configured to reserve air interface resources and session information corresponding to a session according to the first response;

[0247] The air interface resources are used to receive downlink data.

[0248] Optionally, also include:

[0249] a second processing unit, configured to access the satellite device according to a first parameter and send a second request to the satellite device before receiving downlink data through the first session according to the first information, wherein the second request is used to obtain information of a downlink data buffer component on the satellite device or to indicate receiving downlink data or to request registration or to request sending uplink data;

[0250] A third receiving unit is configured to receive a second response fed back by the satellite device, where the second response carries information of the downlink data buffer component or carries indication information instructing the terminal to use the resources corresponding to the first session to receive downlink data;

[0251] The receiving downlink data through the first session according to the first information includes:

[0252] receiving, through the first session, downlink data sent by the downlink data buffer component on the satellite device according to the first information and the information of the downlink data buffer component or the indication information;

[0253] The first parameter includes at least one of: uplink data transmission status, candidate response modes for receiving downlink data, locally stored first session information, reasons for network paging, and relevant identifiers of the satellite device.

[0254] Optionally, the second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving mode for downlink data supported by the terminal;

[0255] And / or, the second response carries a downlink data receiving mode allowed by the satellite device.

[0256] Optionally, also include:

[0257] The second sending unit is used to send the receiving mode for downlink data supported by the terminal to the satellite device.

[0258] Optionally, the receiving, through the first session, downlink data sent by a downlink data buffer component on the satellite device includes:

[0259] The downlink data sent by the satellite device according to the receiving mode and using the downlink data buffer component on the satellite device is received through the first session.

[0260] Optionally, also include:

[0261] A first determining unit, configured to determine a first mapping relationship between the session identification information of the first session and air interface resources;

[0262] The step of accessing the satellite device according to the first parameter includes:

[0263] The satellite device is accessed according to the first parameter and the first mapping relationship.

[0264] Optionally, the first session is a protocol data unit (PDU) session or a non-PDU session.

[0265] The embodiment of the present application also provides a data transmission device, which is applied to satellite equipment, including:

[0266] A third sending unit, configured to send first information of a first session to a terminal;

[0267] a fourth receiving unit, configured to send downlink data to the terminal through the first session according to the first information;

[0268] The first session refers to a session that continuously occupies the allocated resources;

[0269] The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

[0270] Optionally, the first information further includes at least one of the following:

[0271] A response method for receiving downlink data;

[0272] Paging time window;

[0273] Periodic registration timer;

[0274] Satellite identification.

[0275] Optionally, also include:

[0276] A second determining unit, configured to determine the response mode for receiving downlink data according to reference information; wherein the reference information includes: the time information, and at least one of the downlink receiving priority;

[0277] And / or, determining a paging time window or a periodic registration timer corresponding to the terminal according to the ephemeris information of the satellite device.

[0278] Optionally, also include:

[0279] A third determining unit, configured to determine, according to the response mode for receiving downlink data, whether to initiate paging or wait for the terminal to access;

[0280] Wherein, when it is determined to initiate paging, the terminal is instructed to receive downlink data in the paging reason.

[0281] Optionally, also include:

[0282] a fourth receiving unit, configured to receive a first request sent by the terminal before sending the first information of the first session to the terminal;

[0283] The sending the first information of the first session to the terminal includes:

[0284] Feedback a first response to the terminal according to the first request, where the first response carries first information of the first session;

[0285] The first request carries at least one of the following:

[0286] Receive uplink data delivery confirmation;

[0287] Waiting to receive downlink data;

[0288] Receiving priority of downlink data;

[0289] Service type corresponding to the session.

[0290] Optionally, also include:

[0291] a third processing unit, configured to retain system resources and session information of a session corresponding to the first response;

[0292] The system resources are used to send downlink data.

[0293] Optionally, feeding back a first response to the terminal according to the first request includes:

[0294] In a case where the first request indicates a request to activate the on-board store-and-forward operation or the terminal has activated the on-board store-and-forward operation, allocating resources and establishing a first session or updating an existing session to the first session according to the first request;

[0295] According to the first session, a first response is fed back to the terminal.

[0296] Optionally, also include:

[0297] a fifth receiving unit, configured to receive a second request sent by the terminal before sending downlink data to the terminal through the first session according to the first information, wherein the second request is used to obtain information of a downlink data buffer component on the satellite device or to indicate receiving downlink data or to request registration or to request sending uplink data;

[0298] A first feedback unit is configured to feed back a second response to the terminal according to the second request, where the second response carries information about the downlink data buffer component or carries indication information instructing the terminal to use resources corresponding to the first session to receive downlink data;

[0299] The sending downlink data to the terminal through the first session according to the first information includes:

[0300] According to the first information and the information of the downlink data buffer component or the indication information, the downlink data is sent to the terminal through the first session by utilizing the downlink data buffer component on the satellite device.

[0301] Optionally, the second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving mode for downlink data supported by the terminal;

[0302] And / or, the second response carries a downlink data receiving mode allowed by the satellite device.

[0303] Optionally, also include:

[0304] A sixth receiving unit is used to receive a receiving mode for downlink data supported by the terminal and sent by the terminal.

[0305] Optionally, the sending the downlink data to the terminal through the first session by using the downlink data buffer component on the satellite device includes:

[0306] According to the first information and the receiving mode for downlink data supported by the terminal, the downlink data is sent to the terminal through the first session by utilizing the downlink data buffer component on the satellite device.

[0307] Optionally, the first session is a protocol data unit (PDU) session or a non-PDU session.

[0308] Optionally, also include:

[0309] A first cache unit, configured to cache a notification for the terminal, wherein the notification is used to indicate that the terminal has activated an on-board store-and-forward operation;

[0310] The notification carries downlink data storage and forwarding information, and the downlink data storage and forwarding information includes: downlink data sending mode, the terminal identifier, PDU session identifier, on-board storage configuration, candidate user address identifier, and at least one of the candidate user IP addresses.

[0311] Optionally, also include:

[0312] The fifth sending unit is used to send the notification to the server.

[0313] Optionally, also include:

[0314] a fourth determining unit, configured to determine a downlink data sending mode according to second information before sending downlink data to the terminal through the first session according to the first information;

[0315] The second information includes: at least one of the intersatellite link status information and the server's downlink data storage and forwarding request; the downlink data storage and forwarding request includes: at least one of the downlink forwarding strategy, forwarding priority and downlink data delivery confirmation method.

[0316] Optionally, also include:

[0317] A second feedback unit, configured to feed back a downlink data storage and forwarding response to the server according to the downlink data sending mode;

[0318] Among them, the downlink data storage forwarding response carries downlink data storage forwarding information, and the downlink data storage forwarding information includes: the downlink data sending method, the terminal identifier, the PDU session identifier, the on-board storage configuration, the expected time of delivery of the downlink data, the candidate user address identifier, and at least one of the candidate user IP addresses.

[0319] Optionally, the on-board storage configuration includes: at least one of a cache space and a retention time of cached data;

[0320] Alternatively, the on-board storage configuration does not include: cache space and retention time of cache data, and the downlink data storage and forwarding information also includes: cache space, and at least one of retention time of cache data.

[0321] Optionally, the downlink data storage and forwarding information also includes: relevant information for monitoring the satellite device.

[0322] Optionally, also include:

[0323] The fifth determining unit is used to determine a second mapping relationship between the identifier of the terminal, the identifier of the first session, and a related identifier of the server.

[0324] The embodiment of the present application also provides a data transmission device, which is applied to a server and includes:

[0325] A seventh receiving unit, used for receiving downlink data storage and forwarding information sent by the satellite device;

[0326] A sixth sending unit, configured to send downlink data to a satellite device according to the downlink data storage and forwarding information;

[0327] The downlink data storage and forwarding information includes: downlink data sending mode, terminal identifier, PDU session identifier, on-board storage configuration, estimated time of downlink data delivery, candidate user address identifier, and at least one of the candidate user IP address;

[0328] The downlink data storage and forwarding information is carried in a notification to the terminal, where the notification is used to indicate that the terminal has activated the on-board storage and forwarding operation, or is carried in a downlink data storage and forwarding response.

[0329] Optionally, the sending downlink data to a satellite device according to the downlink data storage and forwarding information includes any one of the following:

[0330] In the process of receiving the uplink buffer data, sending the downlink data to the satellite device according to the downlink data storage and forwarding information;

[0331] The downlink data is sent to the satellite device according to the downlink data storage and forwarding information and the downlink data sending requirement information.

[0332] Optionally, also include:

[0333] A seventh sending unit, configured to send a downlink data storage and forwarding request of the server to the satellite device before receiving the downlink data storage and forwarding information sent by the satellite device;

[0334] The downlink data storage and forwarding request includes: at least one of a downlink forwarding strategy, a forwarding priority, and a downlink data delivery confirmation method.

[0335] An embodiment of the present application also provides a non-transitory readable storage medium, which stores a computer program, and the computer program is used to enable a processor to execute the above-mentioned terminal side, satellite device side or server side method.

[0336] The beneficial effects of the above technical solution of the present application are as follows:

[0337] In the above scheme, the data transmission method receives the first information of the first session sent by the satellite device; according to the first information, receives the downlink data through the first session; wherein, the first session refers to a session that continuously occupies the allocated resources; the first information includes: fixed session identification information, and time information for the session to continuously occupy the allocated resources; it can be achieved that the terminal can accurately receive the corresponding downlink data through the maintained first session; it supports that in the case of non-end-to-end connection, through the maintained first session, the network can accurately determine the terminal corresponding to the downlink data, thereby ensuring that the target terminal accurately receives the downlink data; it is a good solution to the problem in the prior art that in the case of non-end-to-end connection, the target terminal cannot be guaranteed to accurately receive the downlink data. BRIEF DESCRIPTION OF THE DRAWINGS

[0338] Figure 1 A schematic diagram of the wireless communication system architecture of an embodiment of the present application;

[0339] Figure 2 A schematic diagram of a remote area tracking scenario according to an embodiment of the present application;

[0340] Figure 3 This is a schematic diagram of an on-board store-and-forward model of an embodiment of the present application;

[0341] Figure 4 The data transmission method of the present invention is shown in the following figure. Figure 1 ;

[0342] Figure 5 The data transmission method of the present invention is shown in the following figure. Figure 2 ;

[0343] Figure 6 The data transmission method of the present invention is shown in the following figure. Figure 3 ;

[0344] Figure 7 The data transmission method of the present invention is specifically implemented as follows: Figure 1 ;

[0345] Figure 8 The data transmission method of the present invention is specifically implemented as follows: Figure 2 ;

[0346] Fig. 9 The data transmission method of the present invention is specifically implemented as follows: Figure 3 ;

[0347] Fig.10 The data transmission method of the present invention is specifically implemented as follows: Figure 4 ;

[0348] Fig.11 The data transmission method of the present invention is specifically implemented as follows: Figure 5 ;

[0349] Fig.12 The data transmission method of the present invention is specifically implemented as follows: Figure 6 ;

[0350] Fig.13 The data transmission device structure of the embodiment of the present application is shown in FIG. Figure 1 ;

[0351] Fig.14 The data transmission device structure of the embodiment of the present application is shown in FIG. Figure 2 ;

[0352] Fig.15 The data transmission device structure of the embodiment of the present application is shown in FIG. Figure 3 ;

[0353] Fig.16 The structure of the data transmission device of the embodiment of the present application is shown as follows: Figure 1 ;

[0354] Fig.17 The structure of the data transmission device of the embodiment of the present application is shown as follows: Figure 2 ;

[0355] Fig.18 The structure of the data transmission device of the embodiment of the present application is shown as follows: Figure 3 . DETAILED DESCRIPTION

[0356] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0357] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0358] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0359] It is explained here that the technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new radio (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0360] Figure 1A block diagram of a wireless communication system applicable to the embodiments of the present application is shown. The wireless communication system includes a terminal device (also referred to as a terminal) and a network device.

[0361] The terminal device involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0362] The network device involved in the embodiments of the present application may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long-term evolution (long term evolution, LTE) system, a 5G base station (the next Generation Node B, gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.

[0363] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoded transmission or beamforming transmission, etc.

[0364] The following first introduces the contents involved in the solution provided in the embodiment of the present application.

[0365] In areas where it is difficult to deploy ground base stations, such as remote areas or disaster areas, mobile communication networks can provide terminals with communication services to access the ground network via satellite. However, in actual deployment, due to the limited number of gateways or restricted sites, there may be some areas (such as the sea and the polar regions) that are covered by satellite base stations but have no local gateways to provide real-time connections to the ground network. In addition, non-geostationary orbit satellites (such as low-orbit satellites) move quickly relative to the ground, and the feeder link from the satellite base station to the ground network may be intermittent or temporarily unavailable. At this time, the mobile communication network will not be able to provide the terminal with an end-to-end connection to the ground server via satellite to transmit the terminal's business data to the ground network or obtain data from the ground server in real time.

[0366] In view of the above situation, when the terminal does not have high requirements for data transmission delay, the mobile communication network can cache the terminal's uplink data in the onboard device, and forward it to the ground network when the satellite and the gateway establish an available link, or the received ground server data can be cached in the onboard device and sent to the terminal after the satellite and the terminal establish a connection, providing a non-real-time connection communication service between the terminal and the application server, which can be called a communication service based on on-board storage and forwarding.

[0367] The following is a detailed introduction to the relevant content.

[0368] 1. Scenarios where on-board storage and forwarding is required;

[0369] Current research mentions some scenarios where IoT devices are deployed remotely for data collection. For example, scientific research institutions collect data on polar animals to study their living habits or movement trajectories. Figure 2As shown in the figure, government departments conduct remote measurements for disaster warning (such as submarine cable detection). These deployed IoT devices mainly work in remote geographical locations or special environmental areas, so it is difficult to obtain support from ground base stations. They are more likely to rely on satellites for remote data transmission. Since they do not have high requirements for latency, and there may be no gateway deployed at the location or it may not be able to connect stably to the local gateway for various reasons, the data can be uploaded and cached in the onboard device, and then forwarded when the satellite can connect to the gateway or terminal.

[0370] 2. On-board store-and-forward model;

[0371] To support the above scenarios, the study provides the following Figure 3 The on-board store-and-forward model is shown in Figure 1. The terminal sends data to the satellite for caching or obtains cached data on the satellite. When the satellite is connected to a gateway or to other gateways via an intersatellite link, it sends the cached data to the ground network or obtains data from the ground network. In terms of network architecture, it is possible to consider deploying base stations and possible core network elements on the satellite.

[0372] 3. 5G architecture;

[0373] In the reference point architecture of the 5G core network, N6 is the interface between the User Plane Function (UPF) and the Data Network (DN), and N33 is the direct interface between the Network Exposure Function (NEF) and the Application Function (AF), which is used for the capability exposure of the core network. DN and AF can be deployed together or separately.

[0374] 4. Non-IP Data Delivery (NIDD) of the Internet of Things;

[0375] Currently, the control plane Cellular Internet of Things (CIoT) 5G system (5GSystem, 5GS) optimization features are defined:

[0376] The control plane CIoT 5GS is optimized for exchanging user data between the terminal (User Equipment, UE) and the session management function (Session Management Function, SMF) as the payload of the non-access layer (Non-Access-Stratum, NAS) message in the uplink and downlink directions, avoiding the establishment of the user plane connection of the protocol data unit (Protocol Data Unit, PDU) session. The UE and the access and mobility management function (Access and Mobility Management Function, AMF) perform integrity protection and encryption on the user data by using NAS PDU integrity protection and encryption. For IP (network association) and Ethernet data, the UE and SMF can negotiate and perform header compression.

[0377] Specifically, the UE and AMF negotiate to support and use the control plane CIoT 5GS optimization. When the control plane CIoT 5GS optimization function is used and the PDU session type is unstructured, the SMF selects NEF or UPF based on the UE subscription information.

[0378] During the PDU session establishment process, AMF indicates to SMF that the control plane CIoT 5GS optimization is available for data transmission.

[0379] In addition, the Non-IP Data Delivery (NIDD) feature is currently defined.

[0380] The core network establishes an unstructured PDU session between the UE and the AF to complete the transmission of uplink and downlink data. Usually, the application programming interface (API) provided by the NEF to the AF can be used for delivery, or the point-to-point N6 tunnel can be used to deliver using the UPF.

[0381] Based on the above, the embodiments of the present application provide a data transmission method, device and equipment to solve the problem in the prior art that the target terminal cannot accurately receive downlink data in the case of non-end-to-end connection. Among them, the method, device and equipment are based on the same application concept. Since the principles of solving the problems by the method, device and equipment are similar, the implementation of the method, device and equipment can refer to each other, and the repeated parts will not be repeated.

[0382] The data transmission method provided in the embodiment of the present application is applied to a terminal, such as Figure 4 As shown, including:

[0383] Step 41: receiving first information of a first session sent by a satellite device;

[0384] Step 42: Receive downlink data through the first session according to the first information; wherein the first session refers to a session that continuously occupies the allocated resources; the first information includes: fixed session identification information, and time information for which the session continuously occupies the allocated resources.

[0385] The time information may include: the term type, such as a permanent term (ie, always) or a limited term. For a limited term, the time information may also include the specific time of the limited term, but is not limited thereto.

[0386] The "downlink data" may include: application or user-related data sent by the application server, which may be used for communication between the terminal and a remote user, or configuration update of the application in the terminal, indication of subsequent operations, etc. The downlink data may be application data; specifically, "receiving downlink data through the first session" may include: establishing a link for information interaction through the first session, and using the link to carry downlink data for transmission, but is not limited thereto.

[0387] The data transmission method provided in the embodiment of the present application receives the first information of the first session sent by the satellite device; receives downlink data through the first session according to the first information; wherein the first session refers to a session that continuously occupies the allocated resources; the first information includes: fixed session identification information, and time information for the session to continuously occupy the allocated resources; it can enable the terminal to accurately receive the corresponding downlink data through the maintained first session; it supports that in the case of non-end-to-end connection, through the maintained first session, the network can accurately determine the terminal corresponding to the downlink data, thereby ensuring that the target terminal accurately receives the downlink data; it well solves the problem in the prior art that in the case of non-end-to-end connection, the target terminal cannot be guaranteed to accurately receive the downlink data.

[0388] The first information further includes at least one of the following: a response method for receiving downlink data; a paging time window; a periodic registration timer; and a satellite identifier.

[0389] This can support resource management. The response method may correspond to paging or active access, but is not limited thereto.

[0390] Furthermore, before receiving the first information of the first session sent by the satellite device, it also includes: sending a first request to the satellite device according to the downlink data receiving demand information; the receiving of the first information of the first session sent by the satellite device includes: receiving a first response fed back by the satellite device, the first response carrying the first information of the first session; wherein the first request carries at least one of the following: receiving uplink data delivery confirmation; waiting for receiving downlink data; receiving priority of downlink data; service type corresponding to the session.

[0391] This can also support the implementation of resource management. After receiving the first response, the terminal can complete the establishment or update of the session, save the satellite identifier (and / or base station identifier and / or cell identifier), session information, and allocated air interface resources, and establish a mapping relationship between the configuration and the air interface resources (see the first mapping relationship below). Subsequently, when the terminal needs to initiate a registration process or needs to access the network due to sending uplink data, it can give priority to the satellite access network for establishing the session, but is not limited to this.

[0392] In the embodiment of the present application, the data transmission method further includes: according to the first response, reserving the air interface resources and session information of the corresponding session; wherein the air interface resources are used to receive downlink data.

[0393] This can also support resource management and ensure the transmission of subsequent downlink data. Among them, "reserving the air interface resources corresponding to the session" can omit the re-negotiation process, and new resource negotiation can be triggered only when the resource cannot complete the receiving operation, but it is not limited to this.

[0394] Furthermore, the data transmission method, before receiving downlink data through the first session according to the first information, further includes: accessing the satellite device according to the first parameter, and sending a second request to the satellite device, the second request being used to obtain information of a downlink data cache component on the satellite device or indicating receiving downlink data or requesting registration or requesting sending uplink data; receiving a second response fed back by the satellite device, the second response carrying information of the downlink data cache component or carrying indication information indicating that the terminal uses the resources corresponding to the first session to receive downlink data; receiving downlink data through the first session according to the first information includes: receiving downlink data sent by the downlink data cache component on the satellite device through the first session according to the first information and the information of the downlink data cache component or the indication information; wherein the first parameter includes: uplink data sending status, candidate response methods for receiving downlink data, locally stored first session information, reasons for network paging, and at least one of the relevant identifiers of the satellite device.

[0395] This can support the process of accurately implementing downlink data reception.

[0396] The second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving method for downlink data supported by the terminal; and / or the second response carries a receiving method for downlink data allowed by the satellite device.

[0397] This can also support the process of accurately receiving downlink data.

[0398] Furthermore, the data transmission method further includes: sending a receiving mode for downlink data supported by the terminal to the satellite device.

[0399] This makes it easier for the satellite device to accurately obtain the receiving mode.

[0400] The receiving of the downlink data sent by the downlink data cache component on the satellite device through the first session includes: receiving the downlink data sent by the satellite device according to the receiving mode and using the downlink data cache component on the satellite device through the first session.

[0401] This makes it easier to accurately receive downlink data.

[0402] Furthermore, the data transmission method also includes: determining a first mapping relationship between session identification information of the first session and air interface resources; accessing the satellite device according to the first parameter includes: accessing the satellite device according to the first parameter and the first mapping relationship.

[0403] This allows accurate access to satellite equipment.

[0404] The first session is a protocol data unit (PDU) session or a non-PDU session.

[0405] This can ensure the diversity of the implementation of this solution.

[0406] The present application also provides a data transmission method, which is applied to satellite equipment, such as Figure 5 As shown, including:

[0407] Step 51: Sending first information of a first session to a terminal;

[0408] Step 52: according to the first information, sending downlink data to the terminal through the first session; wherein the first session refers to a session that continuously occupies the allocated resources; the first information includes: fixed session identification information, and time information for which the session continuously occupies the allocated resources.

[0409] The data transmission method provided in the embodiment of the present application is through sending the first information of the first session to the terminal; according to the first information, sending downlink data to the terminal through the first session; wherein the first session refers to a session that continuously occupies the allocated resources; the first information includes: fixed session identification information, and time information for the session to continuously occupy the allocated resources; it is possible to enable the terminal to accurately receive the corresponding downlink data through the maintained first session; it supports that in the case of non-end-to-end connection, through the maintained first session, the network can accurately determine the terminal corresponding to the downlink data, thereby ensuring that the target terminal accurately receives the downlink data; it is a good solution to the problem in the prior art that in the case of non-end-to-end connection, the target terminal cannot be guaranteed to accurately receive the downlink data.

[0410] The first information further includes at least one of the following: a response method for receiving downlink data; a paging time window; a periodic registration timer; and a satellite identifier.

[0411] This can support resource management. The response method may correspond to paging or active access, but is not limited thereto.

[0412] Furthermore, the data transmission method also includes: determining the response method for receiving downlink data based on reference information; wherein the reference information includes: the time information, and at least one item of the downlink reception priority; and / or determining the paging time window or periodic registration timer corresponding to the terminal based on the ephemeris information of the satellite device.

[0413] In this way, the above-mentioned response mode and / or the paging time window or periodic registration timer corresponding to the terminal can be accurately obtained.

[0414] In an embodiment of the present application, the data transmission method further includes: determining whether to initiate paging or wait for the terminal to access according to the response method for receiving downlink data; wherein, when it is determined to initiate paging, the terminal is instructed to receive downlink data in the paging reason.

[0415] This can ensure that the terminal receives downlink data accurately. Specifically, the satellite device decides to initiate paging or wait for the terminal to access according to the response mode. Initiate paging and instruct the terminal to receive downlink buffer data in the paging reason.

[0416] Furthermore, before sending the first information of the first session to the terminal, it also includes: receiving a first request sent by the terminal; sending the first information of the first session to the terminal includes: according to the first request, feeding back a first response to the terminal, the first response carrying the first information of the first session; wherein the first request carries at least one of the following: receiving an uplink data delivery confirmation; waiting for receiving downlink data; receiving priority of downlink data; service type corresponding to the session.

[0417] This can support resource management. “Feeding back a first response to the terminal according to the first request” may include: feeding back a first response to the terminal according to the first request and ephemeris information, but is not limited thereto.

[0418] In an embodiment of the present application, the data transmission method further includes: reserving system resources and session information of a session corresponding to the first response; wherein the system resources are used to send downlink data.

[0419] This can also support resource management to ensure the transmission of subsequent downlink data. Specifically, the session information and allocated resource configuration can be retained during the session preservation period, but the present invention is not limited thereto.

[0420] Among them, the feeding back a first response to the terminal according to the first request includes: when the first request indicates a request to activate the on-board store-and-forward operation or the terminal has activated the on-board store-and-forward operation, according to the first request, allocating resources and establishing a first session or updating the existing session to the first session; according to the first session, feeding back a first response to the terminal.

[0421] This allows accurate feedback of the first response.

[0422] Furthermore, before sending downlink data to the terminal through the first session according to the first information, it also includes: receiving a second request sent by the terminal, the second request is used to obtain information of the downlink data cache component on the satellite device or indicate receiving downlink data or for requesting registration or for requesting sending uplink data; according to the second request, feeding back a second response to the terminal, the second response carries information of the downlink data cache component or carries indication information instructing the terminal to use the resources corresponding to the first session to receive downlink data; sending downlink data to the terminal through the first session according to the first information includes: according to the first information and the information of the downlink data cache component or the indication information, using the downlink data cache component on the satellite device to send downlink data to the terminal through the first session.

[0423] This can support the process of accurately implementing downlink data reception.

[0424] The second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving method for downlink data supported by the terminal; and / or the second response carries a receiving method for downlink data allowed by the satellite device.

[0425] This can also support the process of accurately receiving downlink data.

[0426] Furthermore, the data transmission method further includes: receiving a receiving mode for downlink data sent by the terminal and supported by the terminal.

[0427] In this way, the receiving mode can be accurately obtained.

[0428] Among them, using the downlink data caching component on the satellite device to send downlink data to the terminal through the first session includes: using the downlink data caching component on the satellite device to send downlink data to the terminal through the first session according to the first information and the receiving method for downlink data supported by the terminal.

[0429] This allows downlink data to be sent accurately.

[0430] In an embodiment of the present application, the first session is a protocol data unit PDU session or a non-PDU session.

[0431] This can ensure the diversity of the implementation of this solution.

[0432] Furthermore, the data transmission method also includes: caching a notification for the terminal, the notification being used to indicate that the terminal has activated an on-board storage and forwarding operation; wherein the notification carries downlink data storage and forwarding information, and the downlink data storage and forwarding information includes: a downlink data sending mode, an identifier of the terminal, a PDU session identifier, an on-board storage configuration, a candidate user address identifier, and at least one of a candidate user IP address.

[0433] This can support the process of accurately implementing downlink data caching.

[0434] In the embodiment of the present application, the data transmission method further includes: sending the notification to the server.

[0435] This can support triggering related operations on the server side.

[0436] Furthermore, before sending downlink data to the terminal through the first session according to the first information, it also includes: determining the downlink data sending method according to the second information; wherein the second information includes: at least one of the intersatellite link status information and the server's downlink data storage and forwarding request; the downlink data storage forwarding request includes: at least one of the downlink forwarding strategy, forwarding priority and downlink data delivery confirmation method.

[0437] This can further support the process of accurately implementing downlink data caching.

[0438] In an embodiment of the present application, the data transmission method further includes: according to the downlink data sending method, feeding back a downlink data storage forwarding response to the server; wherein the downlink data storage forwarding response carries downlink data storage forwarding information, and the downlink data storage forwarding information includes: the downlink data sending method, the terminal identifier, the PDU session identifier, the on-board storage configuration, the expected time of delivery of the downlink data, the candidate user address identifier, and at least one of the candidate user IP addresses.

[0439] This can also further support the process of accurately implementing downlink data caching.

[0440] Among them, the on-board storage configuration includes: cache space, and at least one of the retention time of cache data; or, the on-board storage configuration does not include: cache space and the retention time of cache data, and the downlink data storage forwarding information also includes: cache space, and at least one of the retention time of cache data.

[0441] This ensures that the on-board storage configuration includes at least one of the cache space and the retention time of the cached data.

[0442] Furthermore, the downlink data storage and forwarding information also includes: relevant information for monitoring the satellite equipment.

[0443] This makes it easier for the server to accurately monitor the target satellite. The relevant information of the satellite device may include at least one of the satellite identification, the transmission time window and the like.

[0444] In the embodiment of the present application, the data transmission method further includes: determining a second mapping relationship between the identifier of the terminal, the identifier of the first session, and a related identifier of the server.

[0445] This can also further support the process of accurately implementing the downlink data cache. The second mapping relationship can be used to manage data or notifications, for example, it can be used to process the cached "notification for the terminal", but is not limited thereto.

[0446] The present application also provides a data transmission method, which is applied to a server, such as Figure 6 As shown, including:

[0447] Step 61: receiving downlink data storage and forwarding information sent by the satellite device;

[0448] Step 62: Send downlink data to the satellite device according to the downlink data storage and forwarding information; wherein the downlink data storage and forwarding information includes: downlink data sending mode, terminal identifier, PDU session identifier, on-board storage configuration, expected time for delivery of downlink data, candidate user address identifier, and at least one of the candidate user IP addresses; the downlink data storage and forwarding information is carried in a notification to the terminal, the notification is used to indicate that the terminal has activated the on-board storage and forwarding operation, or is carried in a downlink data storage and forwarding response.

[0449] The data transmission method provided in the embodiment of the present application receives downlink data storage and forwarding information sent by a satellite device; sends downlink data to the satellite device according to the downlink data storage and forwarding information; wherein the downlink data storage and forwarding information includes: a downlink data sending mode, a terminal identifier, a PDU session identifier, an on-board storage configuration, an expected time for delivery of downlink data, a candidate user address identifier, and at least one of a candidate user IP address; the downlink data storage and forwarding information is carried in a notification for the terminal, the notification is used to indicate that the terminal has activated the on-board storage and forwarding operation, or is carried in a downlink data storage and forwarding response; it can support the terminal to accurately receive the corresponding downlink data through the maintained first session; it supports that in the case of a non-end-to-end connection, the network can accurately determine the terminal corresponding to the downlink data through the maintained first session, thereby ensuring that the target terminal accurately receives the downlink data; it well solves the problem in the prior art that in the case of a non-end-to-end connection, the target terminal cannot accurately receive the downlink data.

[0450] Among them, sending downlink data to the satellite device according to the downlink data storage and forwarding information includes any one of the following: sending downlink data to the satellite device according to the downlink data storage and forwarding information during the process of receiving uplink cache data; sending downlink data to the satellite device according to the downlink data storage and forwarding information and downlink data sending demand information.

[0451] In this way, downlink data can be sent in a diversified manner. Among them, "sending downlink data to the satellite device according to the downlink data storage and forwarding information and the downlink data sending demand information" can be understood as: when downlink data needs to be sent, sending downlink data to the satellite device according to the downlink data storage and forwarding information, but it is not limited to this.

[0452] Furthermore, before receiving the downlink data storage forwarding information sent by the satellite device, it also includes: sending a downlink data storage forwarding request of the server to the satellite device; wherein the downlink data storage forwarding request includes: at least one of a downlink forwarding strategy, a forwarding priority, and a downlink data delivery confirmation method.

[0453] This can support the server to accurately obtain the corresponding downlink data storage and forwarding response.

[0454] The data transmission method provided in the embodiment of the present application is illustrated below by way of example, with the server taking an application server as an example and the first session taking a PDU session as an example.

[0455] In view of the above technical problems, an embodiment of the present application provides a data transmission method, which can be specifically implemented as a method for a terminal to obtain downlink data from a server (it can also be called a method for a terminal to obtain downlink data under an on-board store-and-forward operation) to achieve end-to-end (i.e., application server to terminal) transmission of downlink data. This solution mainly involves: for a UE with activated store-and-forward, if the UE indicates the network (i.e., indicates to the network) that there is expected downlink data (e.g., end-to-end confirmation information for uplink data, information that the UE has been pre-configured to receive downlink data, etc.), then the network reserves the allocated network resources for the UE until the UE completes the reception of the downlink data. If the UE is unaware of whether there is downlink data, but the application server has data (e.g., UE configuration information) to send, then the network (corresponding to the above-mentioned satellite device) instructs the application server to prioritize the reuse of the uplink data storage and forwarding resources allocated to the UE in accordance with a certain principle.

[0456] The following is a specific example to illustrate this solution.

[0457] Example 1: The UE has activated on-board store-and-forward or requested to activate store-and-forward, or the network activates the store-and-forward operation according to the power supply situation, and the UE expects to receive downlink data, and the network establishes a keep-alive PDU session (corresponding to the first session above);

[0458] Architecture 1: Base station + lightweight core network (AMF + SMF + unified data management (UDM) function + UPF + NEF) deployed on the same satellite;

[0459] Architecture 2: Base stations + UPF are deployed on low-orbit satellites, and lightweight core networks (AMF + SMF + UDM) are deployed on high-orbit satellites;

[0460] like Figure 7 As shown, the solution of this example includes the following steps:

[0461] 1-2. In one or more of the following situations, the terminal carries information indicating the reception of downlink data in the request to establish or update a PDU session (i.e., a PDU session establishment / update request; corresponding to the above-mentioned first request), such as an "uplink data delivery confirmation" indication or an "expecting to receive downlink data" indication, and the reception priority of the downlink data.

[0462] Case (1): The terminal needs to receive confirmation information from the server for uplink data;

[0463] Case (2): The terminal needs to receive the server's response information for uplink data;

[0464] Case (3): According to pre-configuration, the terminal needs to receive downlink data from the application server.

[0465] 3.AMF forwards the PDU session establishment / update request to SMF, specifically:

[0466] 3a. The PDU session establishment / update request carries the information for activating on-board store-and-forward (and may also carry the information carried in the first request);

[0467] Or, 3b.AMF determines that the terminal has activated on-board store-and-forward or activates on-board store-and-forward according to the power supply situation, and notifies SMF when forwarding the PDU session establishment / update request;

[0468] Or, 3c.SMF queries AMF or UDM whether the terminal activates on-board store-and-forward.

[0469] 4. Based on the information that the terminal has activated or requested to activate on-board storage and forwarding and receiving downlink data requests, such as the "uplink data delivery confirmation" indication or the "expecting to receive downlink data" indication, the SMF determines to establish a keep-alive PDU session in the UPF or NEF or update the existing PDU session to a keep-alive PDU session (i.e., a PDU session that reserves resources, that is, continues to occupy the allocated resources and does not release them, and each network element will store the relevant context); corresponding to the above-mentioned allocation of resources and establishment of the first session or updating the existing session to the first session according to the first request. The SMF determines one or more parameters of the PDU session, such as always keeping alive, keeping alive for a limited period, and keeping alive for a valid period (corresponding to the time information of the above-mentioned session continuously occupying the allocated resources) according to the UE's subscription information, PDU session type (such as IP session, unstructured session, etc.), downlink data reception priority (such as high priority, low priority, etc.), and ephemeris information. Specifically:

[0470] 4a. If the PDU session is an IP session, the UPF on the same satellite as the base station is used as the anchor point, and the network keeps the UE IP address unchanged (i.e. the selected UPF is located on the same satellite as the base station, and the IP address assigned to the terminal remains unchanged);

[0471] Or 4b. [Applicable to Architecture 1] If the PDU session is an unstructured session, the NEF on the same satellite as the base station is used as an anchor point, and the network maintains the mapping relationship between the UE identifier (such as the Generic Public Subscription Identifier (GPSI)), the PDU session identifier and the AF (server) identifier (corresponding to the second mapping relationship between the identifier of the above terminal, the identifier of the first session and the relevant identifier of the server). If the NEF cannot obtain the NIDD (non-IP data transmission) information in the UE contract information or configuration, because the N33 interface between the NEF and the AF is unavailable, the NEF or SMF requests the UE to report the target server identifier or the target server address identifier; or allocates a temporary AF identifier, and establishes a mapping between the UE identifier, the PDU session identifier, the DN information and the temporary AF identifier.

[0472] 5a.SMF sends a PDU session establishment or update response message to AMF, including information such as keep-alive session identifier (corresponding to the PDU session kept alive in the figure), always keep-alive, limited keep-alive, keep-alive validity period, allowed downlink reception priority, etc.

[0473] Optionally, it may also include: 5b. SMF has an event subscription to notify AF, triggering NEF to notify AF that the UE activates store-and-forward and establishes PDU session information; specifically, the event that triggers notification of AF (UE identity, activation of store-and-forward, PDU session information, etc.).

[0474] 6.AMF determines the recommended or preferred response mode of the UE (such as waiting for paging or UE active access, both of which are acceptable) based on the downlink reception priority based on one or more information that the PDU session is a keep-alive session and is always keep-alive, keep-alive for a limited period, and the validity period of the keep-alive, and determines the UE-specific paging time window or UE periodic registration timer based on the ephemeris information; corresponding to the above-mentioned determination of the response mode for receiving downlink data based on the reference information; wherein the reference information includes: the time information, and at least one of the downlink reception priorities; and / or, determining the paging time window or periodic registration timer corresponding to the terminal based on the ephemeris information of the satellite device.

[0475] 7.AMF sends the PDU session establishment or update response and PDU session information (keep-alive PDU session, always keep-alive, limited keep-alive, keep-alive validity period) to the UE through a NAS message; and sends one or more of the "recommended or preferred response method" indication, UE-specific paging time window, and periodic registration timer to the UE through the same NAS message or by initiating the UE configuration update process.

[0476] 8. The UE saves the mapping relationship between the satellite identifier, base station identifier and / or cell identifier (corresponding to the relevant identifiers of the above-mentioned satellite equipment) and the PDU session and (UE) configuration information (corresponding to the above-mentioned first mapping relationship).

[0477] It is explained here that Example 1 involves establishing a keep-alive session and allocating resources, and can be combined with any of the following examples to complete downlink data transmission, but is not limited to this.

[0478] Example 2: Base station + lightweight core network (AMF+SMF+UDM+UPF+NEF) are deployed on the same satellite, and downlink data is stored on the UPF through user plane transmission.

[0479] In this scenario, when the UE accesses the service satellite 1, there is no power supply available between the satellite 1 and the ground gateway, and the control plane information and user plane data cannot reach the ground in time. When the satellite moves to be able to connect to the gateway, the UE may no longer be in the coverage of the satellite, that is, the air interface connection between the UE and the base station has been disconnected.

[0480] Specific as Figure 8 As shown, the solution of this example includes the following steps:

[0481] 0. The UE has activated store-and-forward and the network has established a PDU session for the UE. As the satellite moves, the feeder link between the satellite and the gateway becomes available and the N6 and N33 connections are established. Further:

[0482] [Scenario A] 0a. The UE has uplink data cached in the UPF. At this time, the network maintains the UE's registration status and PDU session information.

[0483] 0b. When the N6 interface is established, the UPF forwards the uplink data to the ground server. The server obtains the UE identifier, UE IP address and PDU session information.

[0484] [Scenario B] The UE has no uplink data cache, but has established a keep-alive PDU session anchored at the UPF. The network retains the UE's registration status and PDU session information.

[0485] 0c-0e. When the UE registers, based on the UE's subscription information or UE Policy, the AMF or UDM subscribes to the SMF to notify the target AF of the event of activating the store-and-forward UE; or, the NEF subscribes to the SMF to notify the target AF of the event of activating the store-and-forward UE; when the notification is triggered, the target AF's information (such as AF identifier, server IP address, data network name DNN, data network access identifier DNAI) can be transmitted. When the network activates store-and-forward for the UE and establishes a keep-alive PDU session, the SMF notifies the NEF to trigger the "event of notifying the AF (i.e., notifying the target AF of the event of activating the store-and-forward UE)", and carries the UE identifier, the activation store-and-forward identifier, the target AF's information, and the PDU session information (such as the PDU session identifier, the PDU session type, the UE UP address, etc.). The NEF caches the notification (also referred to as the activation store-and-forward notification; corresponding to the above-mentioned cached notification for the terminal, the notification is used to indicate that the terminal has activated the on-board store-and-forward operation), and after the feeder link is available to establish the N33 interface, the notification is forwarded to the AF or a third-party server.

[0486] 1. The AF or third-party server has UE downlink data to send (such as delivery confirmation of uplink data (i.e. confirmation information), other data (such as notification information), etc.), and selects a satellite that can provide store-and-forward services. Among them, the PDU session and service satellite recorded when receiving uplink data (scenario A, 0b) or receiving activation store-and-forward notification (scenario B, 0c-0e) can be selected to be reused. If no record exists, an active query can be initiated, see 2a below.

[0487] 2a. Optionally, when the feeder link is available, the AF queries the UE through the NEF based on the UE identifier and AF information whether an available PDU session supporting store-and-forward is established (ie, queries whether the UE has activated store-and-forward and PDU session information).

[0488] 3. When the feed is available, AF obtains the allocated cache space size, cache data retention time, and supported forwarding strategies (such as timely forwarding or delay-tolerant forwarding, both are acceptable) from NEF or SMF, that is, queries the storage forwarding information. Based on one or more of the above information and the ephemeris information, it decides whether to select the current satellite. If the requirements are not met, the satellite is abandoned and waits to connect to the next satellite and repeats the above content of steps 1-3 of this example.

[0489] 4. Select the satellite, and AF sends a request for downlink data storage and forwarding to NEF or SMF (such as the expected downlink forwarding strategy, forwarding priority, downlink data delivery confirmation, etc.). NEF or SMF feeds back a response for downlink data storage and forwarding. Specifically:

[0490] 4a.SMF determines the downlink forwarding mode (i.e., forwarding through intersatellite link relay or forwarding retained on the local satellite) based on the expected forwarding strategy (such as timely forwarding or delay-tolerant forwarding), one or more forwarding priorities (high priority or low priority), and the availability of the intersatellite link. For example, for data with a forwarding strategy of "timely forwarding", the forwarding mode of intersatellite link relay can be selected; for data with a forwarding strategy of "delay-tolerant forwarding", the forwarding mode of retaining on the local satellite can be selected.

[0491] 4b. After receiving the confirmation (i.e., the response of the downlink data storage and forwarding), the AF sends the downlink data to the UPF cache.

[0492] 5-7. Satellites use different forwarding methods:

[0493] [Method A] Relay forwarding via intersatellite links;

[0494] 5a. SMF finds the current service satellite of UE - Satellite 2, or selects Satellite 2 that can serve UE faster according to the arrival time of other satellites at the terminal, UPF cache space and other information, and forwards the data to the corresponding UPF (specifically, the existing mechanism can be used, which will not be repeated here). Then, the following [Method B] or [Method C] can be used on Satellite 2.

[0495] [Mode B] This satellite forwards, the allowed downlink reception priority = high priority;

[0496] 5b. UPF or SMF notifies AMF that there is downlink data retention (i.e. notifies AMF to establish a user plane connection with the UE). The UE's preferred response method is paging or both (i.e. paging and active access). AMF determines that the UE is reachable as soon as possible.

[0497] 6. The AMF determines the reachable time of the UE based on the ephemeris information and the UE location, initiates paging before the paging time window is reached, or notifies the RAN of the reachable time of the UE and the RAN determines the paging time.

[0498] 7. The UE restores the user plane tunnel from the UE to the RAN and the possible N3 tunnel (ie, restores the user plane connection) through the service request process; this may correspond to the above-mentioned second request for indicating the reception of downlink data.

[0499] 8.AMF notifies SMF that "UE is reachable", and UPF forwards the downlink cache data (i.e. the cached downlink data) to the UE.

[0500] [Mode C] This satellite forwards, the allowed downlink reception priority = low priority;

[0501] 5c. UPF or SMF notifies AMF that there is downlink data retention, and the UE's preferred response method is UE active access. AMF does not initiate paging but waits for UE active access.

[0502] 6-7. The UE initiates a registration request (or service request, carrying PDU session information; it can correspond to the second request mentioned above for requesting registration) to the AMF according to the periodic registration timer configured by the network. The AMF determines that the current UE is the target UE for retained data based on the UE identifier, and carries the identifier of "activating the user plane connection of the PDU session" or the identifier of "downlink data arrival" and the PDU session information in the registration request response (or request response). The UE activates the user plane connection based on the response;

[0503] When the UE has uplink data to send, it can preferentially access the current satellite and initiate a service request (corresponding to the above-mentioned access to the satellite device according to the first parameter and sending a second request to the satellite device; the second request is used to request to send uplink data) based on the locally stored keep-alive PDU session information and satellite identifier (and / or base station identifier and / or cell identifier; corresponding to the relevant identifier of the above-mentioned satellite device), and carry PDU session information (such as PDU session identifier). Based on the UE identifier and PDU session identifier, the AMF determines that the current UE is the target UE for the retained data and executes the service request response process to activate the user plane connection.

[0504] 8.AMF notifies SMF that "UE is reachable", and UPF forwards the downlink cache data to the UE (corresponding to the above-mentioned terminal receiving downlink data through the first session based on the first information).

[0505] Example 3: Base station + UPF is deployed on low-orbit satellites, and a lightweight core network (AMF + SMF + UDM) is deployed on high-orbit satellites. NEF is deployed on high-orbit satellites or on the ground, and transmitted through the user plane. Downlink data is stored on UPF.

[0506] In this scenario, the high-orbit satellite is connected to the ground gateway through a continuously available or intermittently available feed to send control plane information to the ground. When the low-orbit satellite serves the UE, there is no feed to the ground gateway, and the user plane data cannot reach the ground in time. When the low-orbit satellite moves to the point where it can connect to the gateway, the UE may no longer be within the satellite's coverage, that is, the air interface connection between the UE and the base station has been disconnected.

[0507] Specific as Fig. 9 As shown, the solution of this example includes the following steps:

[0508] 0a-c.AF or third-party server subscribes to NEF or other network functions (NF) to notify AF of events (which may carry AF identification, information of UE activating store-and-forward, etc.): AF is notified when a UE activates the store-and-forward service. When the network activates the store-and-forward operation for the UE or establishes a keep-alive PDU session, it triggers NEF or other NF to send a notification to the AF, carrying the UE identification and service satellite identification, and optionally, one or more information of PDU session information, indication of the existence of uplink cache data, and uplink data delivery confirmation indication.

[0509] Here, "activating the store-and-forward operation" means that the UE has an established keep-alive or non-keep-alive PDU session.

[0510] 1. When the server (including AF or third-party server) has downlink data, it sends a "downlink data storage and forwarding request" message to NEF or other NF, carrying one or more information such as UE identification, data service type, downlink data volume, expected retention time, expected downlink data sending method, forwarding priority, and downlink data delivery confirmation.

[0511] 2.NEF or other NF (such as SMF or network storage function NRF or UDM or network data analysis function NWDAF) determines the downlink data sending mode (such as simultaneous sending and receiving, immediate sending, etc.; corresponding to the above-mentioned determination of the downlink data sending mode based on the second information) according to the information in the "downlink data storage and forwarding request" message (such as data service type, downlink data volume, expected retention time, expected downlink data sending mode, forwarding priority, at least one of the downlink data delivery confirmation), the PDU session available to the UE, the indication of the existence of uplink cache data, the indication of uplink data delivery confirmation, and at least one of the information, as well as the ephemeris information, selects the UPF that caches the downlink data, and determines the transmission time window for the server to connect to the network.

[0512] 3-7.SMF or NEF executes different processes according to different sending methods:

[0513] [A, sending and receiving at the same time: select the UPF with uplink cache data retention]

[0514] 3a.NEF or other NF sends a response message to the downlink data storage and forwarding request to AF or a third-party server. The AF is notified to send downlink data while waiting to receive uplink data through the information in the message (such as the indication sent when waiting to receive uplink data, the confirmed downlink sending method, etc.), and the information required to monitor the target satellite is given (such as satellite identification, transmission time window; corresponding to the above downlink data storage and forwarding information, it also includes: relevant information for monitoring the satellite equipment). Specifically, the response message may carry downlink data storage and forwarding information, and the downlink data storage and forwarding information includes: the downlink data sending method, the terminal identification, the PDU session identification, the on-board storage configuration, the estimated time of delivery of downlink data, the candidate user address identification, and at least one of the candidate user IP addresses.

[0515] 4a. When the feeder link of the low-orbit satellite is available, the N6 connection is established and the UPF forwards the uplink data to the ground server. The server obtains the UE identity, UE IP address and PDU session information.

[0516] 5a. AF queries NEF or SMF for PDU session information, allowed cache space, and cache data retention time (i.e., queries for store-and-forward information).

[0517] [B, receive immediately: select the most recently arrived UPF that meets the store-and-forward requirements]

[0518] 3b. The UPF selected by SMF can be the UPF anchor point of the keep-alive PDU session or the UPF anchor point of the unreleased non-keep-alive PDU session. SMF notifies the selected UPF to establish or update the N4 session through the inter-satellite link, and provides information such as UE identification, PDU session identification, allocated cache space, data retention time, etc.

[0519] 4b.SMF sends a PDU session update instruction to AMF, updates the PDU session to a keep-alive PDU session or modifies session parameters (which may correspond to the allocation of resources and establishment of a first session or updating an existing session to a first session according to the first request). The message may carry one or more information of UE identification, PDU session identification, always keep-alive indication, limited-time keep-alive indication, and keep-alive validity period. At the same time, the AMF is informed of the selected UPF identification or the identification of the satellite where it is located.

[0520] 5b.AMF determines the paging time window of the UE or the periodic registration timer of the UE according to the ephemeris information based on the PDU session being a keep-alive session and one or more information of always keep-alive, limited keep-alive, and keep-alive validity period, and the forwarding priority given in the "Downlink Data Storage Forwarding Request" message (corresponding to the above-mentioned determination of the paging time window or periodic registration timer corresponding to the terminal according to the ephemeris information of the satellite device).

[0521] 6.AMF sends PDU session update instructions and UE configuration update information through the UE's current serving satellite (which may be different from the satellite where the selected UPF is located). Similar to steps 7-8 of Example 1: Step 7 of Example 1.AMF sends the PDU session establishment or update response and PDU session information (keep-alive PDU session, always keep-alive, keep-alive for a limited period, keep-alive validity period) to the UE through a NAS message; and sends one or more of the "recommended or preferred response method" indication, UE-specific paging time window, and periodic registration timer to the UE through the same NAS message or by initiating the UE configuration update process. Step 8 of Example 1.UE saves the mapping relationship between satellite identifier, base station identifier and / or cell identifier and PDU session and configuration information.

[0522] 7. SMF or NEF or other NF sends a response message to the downlink data storage and forwarding request to AF, notifies AF through the information in the message (such as the confirmed downlink sending method) that the data can be sent immediately, and gives the UPF information providing the service (such as UE identifier, confirmed downlink data sending method, PDU session identifier, UE IP address, UPF identifier, UPF address identifier, allowed cache space, cache data retention time) and the information required to monitor the target satellite (such as satellite identifier, transmission time window).

[0523] 8. The server monitors the target satellite and sends the downlink data to the UPF cache when the feeder link from the satellite to the ground is available.

[0524] 9. UPF notifies SMF that downlink data has arrived. SMF queries AMF for UE reachability and notifies that downlink data is stuck (establishes a user plane connection with the UE). Similar to 5b or 5c in Example 2: Step 5b of Example 2. UPF or SMF notifies AMF that downlink data is stuck. The UE's preferred response method is paging or both (i.e., paging and active access). AMF determines that the UE is reachable as soon as possible. Step 5c of Example 2. UPF or SMF notifies AMF that downlink data is stuck. The UE's preferred response method is UE active access. AMF does not initiate paging but waits for the UE to actively access.

[0525] 10. Data forwarding process: The satellite pages the UE or the UE actively accesses the satellite to obtain the downlink data cached by the UPF. Similar to steps 6-8 in Example 2:

[0526] [Method B] Step 6 of Example 2. AMF determines the reachable time of the UE based on the ephemeris information and the UE location, initiates paging before the paging time window is reached, or notifies the RAN of the reachable time of the UE and the RAN determines the paging time. Step 7 of Example 2. The UE restores the user plane tunnel and possible N3 tunnel from the UE to the RAN (i.e., restores the user plane connection) through the service request process. Step 8 of Example 2. AMF notifies the SMF that "UE is reachable", and the UPF forwards the downlink buffer data (i.e., the buffered downlink data) to the UE.

[0527] [Method C] Steps 6-7 of Example 2. The UE initiates a registration request (or service request, carrying PDU session information) to the AMF according to the periodic registration timer configured by the network. The AMF determines that the current UE is the target UE for the retained data based on the UE identifier, and carries the identifier of "activating the user plane connection of the PDU session" or the identifier of "downlink data arrival" and the PDU session information in the registration request response (or request response). The UE activates the user plane connection based on the response; when the UE has uplink data to send, it can preferentially access the current satellite based on the locally stored keep-alive PDU session information and satellite identifier (and / or base station identifier and / or cell identifier; corresponding to the relevant identifiers of the above-mentioned satellite equipment), initiate a service request, and carry the PDU session information (such as the PDU session identifier). The AMF determines that the current UE is the target UE for the retained data based on the UE identifier and the PDU session identifier, and executes the service request response process to activate the user plane connection. Step 8 of Example 2. The AMF notifies the SMF that "UE is reachable", and the UPF forwards the downlink cached data to the UE.

[0528] Example 4: Base station + lightweight core network (AMF+SMF+UDM+UPF+NEF) are deployed on the same satellite, and downlink data is transmitted through the control plane and stored on UPF or AMF.

[0529] Specific as Fig.10 As shown, the solution of this example includes the following steps:

[0530] 0-4. Same as steps 0-4 in Example 2, specifically:

[0531] 0. The UE has activated store-and-forward and the network has established a PDU session for the UE. As the satellite moves, the feeder link between the satellite and the gateway becomes available and the N6 and N33 connections are established. Further:

[0532] [Scenario A] 0a. The UE has uplink data cached in the UPF. At this time, the network maintains the UE's registration status and PDU session information.

[0533] 0b. When the N6 interface is established, the UPF forwards the uplink data to the ground server. The server obtains the UE identifier, UE IP address and PDU session information.

[0534] [Scenario B] The UE has no uplink data cache, but has established a keep-alive PDU session anchored at the UPF. The network retains the UE's registration status and PDU session information.

[0535] 0c-0e. When the UE registers, based on the UE's subscription information or UE Policy, the AMF or UDM subscribes to the SMF to notify the target AF of the event of activating the store-and-forward UE; or, the NEF subscribes to the SMF to notify the target AF of the event of activating the store-and-forward UE; when the notification is triggered, the target AF's information (such as AF identifier, server IP address, data network name DNN, data network access identifier DNAI) can be transmitted. When the network activates store-and-forward for the UE and establishes a keep-alive PDU session, the SMF notifies the NEF to trigger the "event of notifying the AF (i.e., notifying the target AF of the event of activating the store-and-forward UE)", and carries the UE identifier, the activation store-and-forward identifier, the target AF's information, and the PDU session information (such as the PDU session identifier, the PDU session type, the UE UP address, etc.). The NEF caches the notification (also referred to as the activation store-and-forward notification; corresponding to the above-mentioned cached notification for the terminal, the notification is used to indicate that the terminal has activated the on-board store-and-forward operation), and after the feeder link is available to establish the N33 interface, the notification is forwarded to the AF or a third-party server.

[0536] 1. The AF or third-party server has UE downlink data to send (such as delivery confirmation of uplink data (i.e. confirmation information), other data (such as notification information), etc.), and selects a satellite that can provide store-and-forward services. Among them, the PDU session and service satellite recorded when receiving uplink data (scenario A, 0b) or receiving activation store-and-forward notification (scenario B, 0c-0e) can be selected to be reused. If no record exists, an active query can be initiated, see 2a below.

[0537] 2a. Optionally, when the feeder link is available, the AF queries the UE through the NEF based on the UE identifier and AF information whether an available PDU session supporting store-and-forward is established (ie, queries whether the UE has activated store-and-forward and PDU session information).

[0538] 3. When the feed is available, AF obtains the allocated cache space size, cache data retention time, and supported forwarding strategies (such as timely forwarding or delay-tolerant forwarding, both are acceptable) from NEF or SMF, that is, queries the storage forwarding information. Based on one or more of the above information and the ephemeris information, it decides whether to select the current satellite. If the requirements are not met, the satellite is abandoned and waits to connect to the next satellite and repeats the above content of steps 1-3 of this example.

[0539] 4. Select the satellite, and AF sends a request for downlink data storage and forwarding to NEF or SMF (such as the expected downlink forwarding strategy, forwarding priority, downlink data delivery confirmation, etc.). NEF or SMF feeds back a response for downlink data storage and forwarding. Specifically:

[0540] 4a.SMF determines the downlink forwarding mode (i.e., forwarding through intersatellite link relay or forwarding retained on the local satellite) based on the expected forwarding strategy (such as timely forwarding or delay-tolerant forwarding), one or more forwarding priorities (high priority or low priority), and the availability of the intersatellite link. For example, for data with a forwarding strategy of "timely forwarding", the forwarding mode of intersatellite link relay can be selected; for data with a forwarding strategy of "delay-tolerant forwarding", the forwarding mode of retaining on the local satellite can be selected.

[0541] 4b. After receiving the confirmation (i.e., the response of the downlink data storage and forwarding), the AF sends the downlink data to the UPF cache.

[0542] 5-9. Satellites use different forwarding methods:

[0543] [Method A] Relay forwarding via intersatellite links;

[0544] 5a. SMF finds the current service satellite of UE - Satellite 2, or selects Satellite 2 that can serve UE faster according to the time when other satellites arrive at the terminal, UPF cache space and other information, and forwards the data to the corresponding UPF (specifically, existing mechanisms can be used, which will not be repeated here). Then, the following [Method B] or [Method C] can be used on Satellite 2.

[0545] Or, 5b. UPF forwards the data to the AMF on the same satellite. AMF finds the current service satellite of UE - satellite 2, or selects satellite 2 that serves UE faster according to the time when other satellites arrive at the terminal, AMF cache space and other information, and forwards the data to the corresponding AMF (specifically, the existing mechanism can be used, which will not be repeated here). Then, steps 6-9 of [method B] or steps 6-8 of [method C] can be adopted on satellite 2.

[0546] [Method B] This satellite forwards and configures the cache in UPF.

[0547] 5c. UPF or SMF notifies AMF: Enable UE to be reachable (downlink data is retained in UPF). This notification can carry the PDU session identifier and the following situation 1 or situation 2 can be executed later:

[0548] Case 1, [Allowed downlink reception priority = high priority] AMF determines that the UE is reachable as soon as possible and pages the UE. Specifically:

[0549] 6a-7.AMF determines the reachable time of the UE based on the ephemeris information and the UE location, initiates paging before the paging time window is reached, or informs the RAN of the reachable time of the UE to determine the paging time. The UE responds to the paging to establish a Radio Resource Control (RRC) connection. Then, steps 8-9 of this method are executed.

[0550] Case 2, [Allowed downlink reception priority = low priority] AMF does not initiate a call and waits for UE to actively access. Specifically:

[0551] 6b. The UE initiates a registration request (carrying a PDU session identifier) ​​to the AMF according to the periodic registration timer configured by the network; or when the UE has uplink data to send, it preferentially accesses the current satellite and establishes an RRC connection based on the locally stored keep-alive PDU session information and satellite identifier (and / or base station identifier and / or cell identifier; corresponding to the relevant identifiers of the above-mentioned satellite equipment), and the message carries the PDU session identifier. The AMF determines that the current UE is the target UE for the retained data based on the UE identifier, and carries the "activate the PDU session" identifier or the "downlink data has arrived" identifier and the PDU session information in the response message. Subsequently, steps 8-9 under this method are executed.

[0552] 8-9.AMF notifies SMF that "UE is reachable (corresponding to the Enable UE reachable response in the figure)". UPF forwards the downlink buffered data to AMF via SMF and sends it to UE via downlink NAS message.

[0553] [Method C] This satellite forwards and configures caching in AMF.

[0554] 5d.UPF forwards the data to AMF. The specific forwarding message may carry the PDU session identifier and downlink data.

[0555] 6a\6b\7. Same as [Method B], specifically:

[0556] Case 1, [Allowed downlink reception priority = high priority] AMF pages UE. Specifically:

[0557] 6a-7.AMF determines the reachable time of the UE based on the ephemeris information and the UE location, initiates paging before the paging time window arrives, or informs the RAN of the reachable time of the UE to determine the paging time. The UE responds to the paging to establish an RRC connection. Then, step 8 of this method is executed.

[0558] Case 2, [Allowed downlink reception priority = low priority] AMF does not initiate a call and waits for UE to actively access. Specifically:

[0559] 6b. The UE initiates a registration request (carrying a PDU session identifier) ​​to the AMF according to the periodic registration timer configured by the network; or when the UE has uplink data to send, it preferentially accesses the current satellite and establishes an RRC connection based on the locally stored keep-alive PDU session information and satellite identifier (and / or base station identifier and / or cell identifier; corresponding to the relevant identifiers of the above-mentioned satellite equipment), and the message carries the PDU session identifier. The AMF determines that the current UE is the target UE for the retained data based on the UE identifier, and carries the "activate the PDU session" identifier or the "downlink data has arrived" identifier and the PDU session information in the response message. Subsequently, execute step 8 under this method.

[0560] 8.AMF sends the buffered data (i.e., buffered downlink data) to the UE via a downlink NAS message.

[0561] Example 5: Base station + lightweight core network (AMF+SMF+UDM+UPF+NEF) are deployed on the same satellite, non-IP data is transmitted through the control plane, and downlink data is stored on SMF or NEF.

[0562] Specific as Fig.11 As shown, the solution of this example includes the following steps:

[0563] 0. The UE has activated store-and-forward, and the network establishes an unstructured PDU session for the UE. As the satellite moves, the feeder link between the satellite and the gateway becomes available, and an N33 connection is established. Further:

[0564] [Scenario A] 0a. The UE has uplink data cached in the NEF. At this time, the network maintains the UE's registration status and PDU session information.

[0565] 0b. When the N33 interface is established, the NEF sends a message to the ground server (such as a delivery notification request Nnef_NIDD_DeliveryNotify Request) and forwards the uplink data. The AF (or a third-party server) obtains the UE identifier and PDU session information. If it carries the "store and forward" identifier, it determines that the UE activates the store and forward function.

[0566] [Scenario B] The UE has no uplink data cache, but establishes a PDU session anchored at the NEF. The network retains the UE's registration status and PDU session information.

[0567] 0c-0e. When the UE registers, based on the UE's contract information or UE Policy, the AMF or UDM subscribes to the SMF or NEF to notify the target AF of the event of activating storage and forwarding of the UE. When the notification is triggered, the information of the target AF (such as AF identifier, server IP address, DNN, DNAI) can be transmitted. When the network activates storage and forwarding for the UE and establishes an unstructured PDU session, the SMF or NEF triggers the "event notifying AF" and carries the UE identifier, activation storage and forwarding identifier, target AF information, and PDU session information (such as PDU session identifier, unstructured PDU session indication (i.e. unstructured indication), allocated cache space, and cache data retention time). The NEF caches the notification and forwards the notification to the AF or a third-party server after the feeder link is available to establish the N33 interface.

[0568] 1. AF or third-party server has UE downlink data to send (such as delivery confirmation of uplink data (i.e. confirmation information), other data (such as notification information), etc.), and selects a satellite that can provide store-and-forward service. Among them, you can choose to reuse the satellite that receives uplink data (scenario A, 0b) or receives the activation store-and-forward notification (scenario B, 0c-0e). If there is no record, you can initiate an active query (see step 2a below).

[0569] 2a. Optionally, when power feeding is available, the AF queries the UE through the NEF based on the UE identity and AF information whether the UE has activated the store-and-forward and the unstructured PDU session supporting store-and-forward (corresponding to the PDU session information).

[0570] 3.AF knows that the UE has activated the store-and-forward function, and obtains the allocated cache space size, cache data retention time, and supported forwarding strategies (such as timely forwarding or delay-tolerant forwarding, both are acceptable) from NEF or SMF, that is, queries the store-and-forward information. Based on one or more of the above information and the ephemeris information, it decides whether to select the current satellite. If the requirements are not met, the satellite is abandoned and waits to connect to the next satellite and repeats the above content of steps 1-3 of this example.

[0571] 4. The satellite is selected, and the AF sends a message (such as a delivery request) to the NEF or SMF, carrying information related to storage and forwarding (such as the expected downlink forwarding strategy, forwarding priority, and delivery confirmation of downlink data). Further:

[0572] 4a.NEF or SMF determines the downlink forwarding mode (i.e., forwarding through intersatellite link relay, or forwarding retained on the local satellite) based on the expected downlink forwarding strategy (such as timely forwarding or delay-tolerant forwarding), one or more forwarding priorities (high priority or low priority), and information such as the availability of the intersatellite link. For example, for data with a forwarding strategy of "timely forwarding", the forwarding mode of intersatellite link relay can be selected; for data with a forwarding strategy of "delay-tolerant forwarding", it can be selected to forward retained on the local satellite.

[0573] 4b. After receiving the confirmation (i.e., the delivery response), the AF sends the downlink data to the NEF cache. The response may carry a confirmation that a sending indication or a receiving indication (indicating that the server data is sent to the satellite), a downlink forwarding strategy, and an estimated time of arrival of the downlink data.

[0574] 5-9. Satellites use different forwarding methods. Similar to step 5c / 5d-9 in example 4, the main difference is that the network element involved in forwarding data is SMF or NEF. For details, please refer to the following:

[0575] [Method B] This satellite forwards and configures the cache in NEF.

[0576] 5c.NEF or SMF notifies AMF: Enable UE to be reachable (downlink data is stuck in NEF), and the notification can carry the PDU session identifier. The following case 1 or case 2 can be executed later:

[0577] Case 1, [Allowed downlink reception priority = high priority] AMF determines that the UE is reachable as soon as possible and pages the UE. Specifically:

[0578] 6a-7.AMF determines the reachable time of the UE based on the ephemeris information and the UE location, initiates paging before the paging time window arrives, or informs the RAN of the reachable time of the UE and the RAN determines the paging time. The UE responds to the paging to establish an RRC connection. Then, steps 8-9 of this method are executed.

[0579] Case 2, [Allowed downlink reception priority = low priority] AMF does not initiate a call and waits for UE to actively access. Specifically:

[0580] 6b. The UE initiates a registration request (carrying a PDU session identifier) ​​to the AMF according to the periodic registration timer configured by the network; or when the UE has uplink data to send, it preferentially accesses the current satellite and establishes an RRC connection based on the locally stored keep-alive PDU session information and satellite identifier (and / or base station identifier and / or cell identifier; corresponding to the relevant identifiers of the above-mentioned satellite equipment), and the message carries the PDU session identifier. The AMF determines that the current UE is the target UE for the retained data based on the UE identifier, and carries the "activate the PDU session" identifier or the "downlink data has arrived" identifier and the PDU session information in the response message. Subsequently, steps 8-9 under this method are executed.

[0581] 8-9.AMF notifies SMF that "UE is reachable (corresponding to the Enable UE reachable response in the figure)". NEF forwards the downlink buffered data to AMF via SMF and sends it to the UE via a downlink NAS message.

[0582] [Method C] This satellite forwards and configures the cache in SMF.

[0583] 5d.NEF forwards the data to SMF. The specific forwarding message may carry the PDU session identifier and downlink data.

[0584] 6a\6b\7. Same as [Method B], specifically:

[0585] Case 1, [Allowed downlink reception priority = high priority] AMF pages UE. Specifically:

[0586] 6a-7.AMF determines the reachable time of the UE based on the ephemeris information and the UE location, initiates paging before the paging time window arrives, or informs the RAN of the reachable time of the UE to determine the paging time. The UE responds to the paging to establish an RRC connection. Then, step 8 of this method is executed.

[0587] Case 2, [Allowed downlink reception priority = low priority] AMF does not initiate a call and waits for UE to actively access. Specifically:

[0588] 6b. The UE initiates a registration request (carrying a PDU session identifier) ​​to the AMF according to the periodic registration timer configured by the network; or when the UE has uplink data to send, it preferentially accesses the current satellite and establishes an RRC connection based on the locally stored keep-alive PDU session information and satellite identifier (and / or base station identifier and / or cell identifier; corresponding to the relevant identifiers of the above-mentioned satellite equipment), and the message carries the PDU session identifier. The AMF determines that the current UE is the target UE for the retained data based on the UE identifier, and carries the "activate the PDU session" identifier or the "downlink data has arrived" identifier and the PDU session information in the response message. Subsequently, execute step 8 under this method.

[0589] 8.AMF sends the buffered data (i.e., buffered downlink data) to the UE via a downlink NAS message.

[0590] Example 6: Base station + edge computing server are deployed on the same satellite, and downlink data is stored on the satellite's edge computing server.

[0591] Specific as Fig.12 As shown, the solution of this example includes the following steps:

[0592] 1. The UE accesses the base station to prepare to send uplink data or pre-configure resources for receiving downlink data; the first RRC message (e.g., RRC establishment request, reconstruction request, recovery request) sent to base station 1 on satellite 1 may carry security parameters, service type (e.g., reliability service), target server parameters (e.g., address identifier, server identifier), "uplink data delivery confirmation" or "expecting to receive downlink data" indication, priority for receiving downlink data, etc., such as: UE identifier, service type, target server parameters, uplink data delivery confirmation, expectation to receive downlink data, downlink data reception priority, etc.

[0593] 2-4. The base station activates the store-and-forward operation according to the UE request or the feeder link situation. Specifically, the RRC authentication is completed according to the contract information, UE identification, and security parameters; the allocated UE cache space and data retention time are determined; and the air interface resource configuration, the preferred response method, the exclusive paging time window, and the UE periodic access timer are determined. Among them, the recommended or preferred response method can be determined based on the ephemeris information, the service type, the priority of receiving downlink data, etc. When the service is a reliability service and uplink data delivery confirmation is required, a dedicated paging time window is configured for the UE; otherwise, a periodic access timer can be configured for the UE.

[0594] 5. The UE receives a first RRC response message sent by the base station, which may include: an allocated UE address identifier, a UE identifier, activation of storage and forwarding, on-board edge server parameters (such as edge server address, address identifier), allocated cache space, air interface resource configuration parameters, UE configuration parameters (such as UE-specific paging time window, periodic access timer), satellite identifier, base station identifier, cell identifier, and one or more of the preferred response method.

[0595] 6 The base station forwards the data sent by the UE to the edge server cache (specifically: the UE sends the uplink data to the base station, and the base station forwards it).

[0596] 7. When the application server (i.e. AF or third-party server) has downlink data to send and waits for the feeder link between the satellite and the gateway to be available, the onboard edge server (i.e. edge computing server 1 in the figure) establishes a connection with the third-party application server and completes security authentication (i.e. server authentication).

[0597] 8. After the security authentication is passed, the uplink data and related information (such as UE identification and "store and forward activated" identification) are sent to the application server. The application server determines whether there is downlink data that needs to be sent to the UE based on the UE identification.

[0598] 9. Optionally, the application server queries the base station for allocated cache space, cache data retention time, etc.; that is, queries for storage and forwarding information.

[0599] 10. If satellite 1 is selected, a request message for downlink data storage and forwarding is sent to satellite 1, which may carry one or more information including UE identification, service type, cached data volume, expected downlink forwarding strategy, forwarding priority, and downlink data delivery confirmation.

[0600] 11. Based on the contract information and service type in the request message, expected downlink forwarding strategy, forwarding priority, downlink data delivery confirmation and other information, the base station authorizes the application server to send data to the UE using a store-and-forward operation and determines the forwarding method for the downlink data (such as relaying via intersatellite links, retaining the data on the satellite, etc.).

[0601] 12. The base station sends a response of downlink data storage and forwarding to the application server, and carries the data cache space, cache retention time, estimated downlink data delivery time, and / or edge server address.

[0602] 13. The base station executes the following corresponding processes according to different forwarding modes:

[0603] Intersatellite Link Relay

[0604] 13a. The application server sends the downlink data to the base station buffer.

[0605] 14. The base station determines the service satellite of the current UE or the satellite that is about to reach the UE based on the ephemeris information, and forwards the downlink data and configuration information (such as UE identification, service type, service priority, delivery confirmation of downlink data, server address, etc.) to the selected satellite base station (such as forwarding downlink data and configuration information to other satellites) or edge server through the inter-satellite link.

[0606]

Retransmitted by this satellite

[0607] 13b. The application server sends the downlink data to the on-board edge server cache.

[0608] 14. The edge server notifies base station 1 that data has arrived, and the base station (i.e., base station 1) determines whether to initiate paging to the UE or wait for the UE to actively access based on the ephemeris information, the stored UE context, the downlink data reception priority, etc.

[0609] 15. Optionally, after the base station reaches the coverage area of ​​the UE, the base station initiates paging to the UE, carrying a "downlink data retained" indication or the paging reason is data or retained data.

[0610] 16. The UE responds to receiving a paging message for retained downlink data, or when the time window for periodic access is reached, or when there is uplink data to be sent, it preferentially chooses to access the base station and sends a second RRC message, which may carry the UE identifier, UE address identifier, an indication of allowing reception of offline data, and supported reception methods (such as pull and push).

[0611] Subsequent execution of 17a-18a or 17b-19:

[0612] 17a-18a: The base station sends a second RRC message response, carrying the UE identifier, the allowed receiving mode (such as pull, push), and the edge server address. When the receiving mode is pull, the UE establishes a connection with the edge server and extracts the cached downlink data.

[0613] 17b-19: The base station sends a second RRC message response, carrying the UE identifier and the allowed receiving mode. When the receiving mode is push, the UE maintains the RRC connection, and the base station notifies the edge server to send data to the UE.

[0614] Based on the above, the solution provided by the embodiment of the present application involves the following contents:

[0615] 1. The terminal negotiates and manages the resources for receiving downlink data with the base station or core network;

[0616] Terminal side:

[0617] (1) The UE carries one or more information related to receiving downlink data, including an "uplink data delivery confirmation" indication, an "expectation to receive downlink data" indication, a downlink data reception priority, and a service type (such as reliability service) in an RRC or NAS message according to the need to receive downlink data (corresponding to the above-mentioned downlink data reception requirement information); sends a first request to the satellite device according to the above-mentioned downlink data reception requirement information; receives a first response fed back by the satellite device, the first response carrying first information of a first session; wherein the first request carries at least one of the following: receiving uplink data delivery confirmation; waiting to receive downlink data; downlink data reception priority; and service type corresponding to the session.

[0618] (2) The UE selectively monitors the wireless signal of the target satellite according to the "recommended or preferred response method (corresponding to the above-mentioned response method for receiving downlink data)" indicated by the base station or core network, the UE-specific paging time window, the periodic registration timer, and the satellite identifier, and responds to the network's paging message or actively accesses the network to receive downlink data.

[0619] (3) The UE reserves the air interface resources and PDU session information pre-configured by the network, and preferentially uses them for receiving downlink data; corresponding to the above-mentioned first response, the air interface resources and session information of the corresponding session are reserved; wherein the air interface resources are used for receiving downlink data.

[0620] Core network side:

[0621] (1) The SMF determines to establish or update an existing PDU session in the UPF or NEF as a PDU session with reserved resources (a keep-alive PDU session) based on the activation of on-board storage and forwarding information, the information of receiving downlink data requests (such as an "uplink data delivery confirmation" indication or an "expecting to receive downlink data" indication), UE subscription, downlink data reception priority, and ephemeris information, and determines one or more parameters of the PDU session, such as always keeping alive, keeping alive for a limited period, and keeping alive for a valid period. Corresponding to the above-mentioned receiving the first request sent by the terminal; according to the first request, feeding back a first response to the terminal.

[0622] (2) The AMF determines the UE's recommended or preferred response mode (such as waiting for paging, UE active access, or both) based on whether the PDU session is a keep-alive session, keep-alive parameters (such as always keep-alive, limited keep-alive, and keep-alive validity period), downlink reception priority, etc., and determines one or more of the UE-specific paging time window, UE periodic registration timer, and UE periodic access timer based on the ephemeris information. Corresponding to the above, the response mode for receiving downlink data is determined based on the reference information; and / or, based on the ephemeris information of the satellite device, the paging time window or periodic registration timer corresponding to the terminal is determined.

[0623] (3) For the PDU session that is kept alive, each NF in the core network retains the session information and the allocated resource configuration during the PDU session keep alive period, and gives priority to using the configured resources when resuming data transmission. Corresponding to the above-mentioned retention of the system resources and session information of the session corresponding to the first response; wherein the system resources are used to send downlink data.

[0624] 2. Downlink data caching process (core network side);

[0625] (1) When each NF in the core network activates store-and-forward for the UE and establishes a PDU session, the NEF cache sends to the AF a notification that the UE has activated store-and-forward (corresponding to the notification of the above cache for the terminal, the notification is used to indicate that the terminal has activated the on-board store-and-forward operation), including the UE identifier, the PDU session identifier, the on-board storage configuration (such as the storage space size, the retention validity period), and the optional UE UP address; and forwards it to the AF after the connection with the AF is established.

[0626] (2) The SMF processes the server's downlink data storage and forwarding request message and information (such as the expected downlink forwarding strategy (such as timely forwarding or delay-tolerant forwarding, either is acceptable), forwarding priority, and downlink data delivery confirmation); and determines the downlink data forwarding method (such as intersatellite link relay forwarding, or retaining forwarding on the current satellite) based on the downlink forwarding strategy, forwarding priority, and intersatellite link status information; corresponding to the above, determines the downlink data sending method based on the second information.

[0627] (3) SMF determines the receiving mode of downlink data, generates and sends a downlink data storage and forwarding response message, carrying the confirmed downlink sending mode (such as sending and receiving at the same time, or sending immediately) and the UPF information providing services (such as PDU session identifier, UEIP address, UPF identifier, UPF address identifier, allowed cache space, cache data retention time) and information required for monitoring the target satellite (such as satellite identifier, transmission time window). Corresponding to the above, according to the downlink data sending mode, a downlink data storage and forwarding response is fed back to the server; the downlink data storage and forwarding information also includes: relevant information for monitoring the satellite equipment.

[0628] (4) NEF or SMF allocates a temporary AF identifier, establishes a mapping between the UE identifier, the PDU session identifier, the DN information and the temporary AF identifier (corresponding to the second mapping relationship between the identifier of the terminal, the identifier of the first session and the relevant identifier of the server determined above), and manages cached data.

[0629] 3. The process of receiving downlink data;

[0630] Terminal side:

[0631] (1) The UE preferentially selects the base station deployed by the satellite to access the network according to the current uplink data transmission status, the response mode configured by the AMF or the base station, the locally stored keep-alive PDU information, and the satellite identifier (and / or the base station identifier and / or the cell identifier), initiates a NAS message or an RRC message to the network, and obtains the device information (such as the device identifier and the address identifier) ​​of the downlink data cache; corresponding to the above-mentioned first parameter, accesses the satellite device and sends a second request to the satellite device, the second request is used to obtain the information of the downlink data cache component on the satellite device or to indicate the reception of downlink data or to request registration or to request the transmission of uplink data; receives a second response fed back by the satellite device, the second response carries the information of the downlink data cache component or carries the indication information indicating that the terminal uses the resources corresponding to the first session to receive downlink data; wherein the first parameter includes at least one of: the uplink data transmission status, the candidate response mode for receiving downlink data, the locally stored first session information, the reason for network paging, and the relevant identifier of the satellite device.

[0632] (2) When the UE sends a NAS or RRC message for accessing the network, it carries an indication of allowing reception of downlink data and a supported reception mode (such as pull or push); corresponding to the above-mentioned second request, it carries an indication that the terminal is allowed to receive downlink data and / or a reception mode for downlink data supported by the terminal.

[0633] Base station or network side:

[0634] (1) The base station or AMF determines whether and when to initiate paging to the UE or wait for the UE to actively access the network based on the downlink reception priority, preferred response mode and ephemeris information.

[0635] (2) The base station confirms and informs the UE of the receiving mode of the downlink data. When the receiving mode is push, the base station notifies the edge server to send data to the UE. (1)+(2) on this side corresponds to the above-mentioned sending of downlink data to the terminal through the first session using the downlink data buffer component on the satellite device according to the first information and the receiving mode for downlink data supported by the terminal.

[0636] In summary, the embodiments of the present application provide a method for a terminal to obtain remote application server data based on on-board storage and forwarding operations. For scenarios where a real-time connection from the terminal to the server cannot be established via a satellite, the method tries to meet the needs of the terminal to obtain the downlink data sent by the application server in a timely and efficient manner, thereby realizing end-to-end downlink data transmission.

[0637] It is to be noted here that the relevant contents between the above examples and between the execution entities (such as UE, base station, etc.) can refer to each other, and the repeated contents will not be repeated.

[0638] The embodiment of the present application also provides a data transmission device, wherein the data transmission device is a terminal, such as Fig.13 As shown, it includes a memory 131, a transceiver 132, and a processor 133:

[0639] The memory 131 is used to store computer programs; the transceiver 132 is used to send and receive data under the control of the processor 133; the processor 133 is used to read the computer program in the memory 131 and perform the following operations:

[0640] Receiving, by the transceiver 132, first information of a first session sent by a satellite device;

[0641] receiving downlink data through the first session according to the first information;

[0642] The first session refers to a session that continuously occupies the allocated resources;

[0643] The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

[0644] The data transmission device provided in the embodiment of the present application receives the first information of the first session sent by the satellite device; receives downlink data through the first session according to the first information; wherein the first session refers to a session that continuously occupies the allocated resources; the first information includes: fixed session identification information, and time information for the session to continuously occupy the allocated resources; it is possible to enable the terminal to accurately receive the corresponding downlink data through the maintained first session; it supports that in the case of non-end-to-end connection, through the maintained first session, the network can accurately determine the terminal corresponding to the downlink data, thereby ensuring that the target terminal accurately receives the downlink data; it is a good solution to the problem in the prior art that in the case of non-end-to-end connection, the target terminal cannot be guaranteed to accurately receive the downlink data.

[0645] Specifically, the transceiver 132 is used to receive and send data under the control of the processor 133.

[0646] Among them, Fig.13In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 133 and various circuits of memory represented by memory 131 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 132 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, including wireless channels, wired channels, optical cables, and other transmission media. For different user devices, the user interface 134 may also be an interface capable of externally and internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0647] The processor 133 is responsible for managing the bus architecture and general processing, and the memory 131 can store data used by the processor 133 when performing operations.

[0648] Optionally, the processor 133 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD), and the processor may also adopt a multi-core architecture.

[0649] The processor calls the computer program stored in the memory to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

[0650] The first information further includes at least one of the following: a response method for receiving downlink data; a paging time window; a periodic registration timer; and a satellite identifier.

[0651] Furthermore, the operation also includes: before receiving the first information of the first session sent by the satellite device, according to the downlink data receiving demand information, sending a first request to the satellite device through the transceiver; the receiving of the first information of the first session sent by the satellite device includes: receiving a first response fed back by the satellite device, the first response carrying the first information of the first session; wherein the first request carries at least one of the following: receiving uplink data delivery confirmation; waiting for receiving downlink data; receiving priority of downlink data; service type corresponding to the session.

[0652] In the embodiment of the present application, the operation further includes: according to the first response, reserving the air interface resources and session information of the corresponding session; wherein the air interface resources are used to receive downlink data.

[0653] Further, the operation also includes: before receiving downlink data through the first session according to the first information, accessing the satellite device according to a first parameter, and sending a second request to the satellite device through the transceiver, the second request is used to obtain information of a downlink data cache component on the satellite device or indicate receiving downlink data or for requesting registration or for requesting sending uplink data; receiving a second response fed back by the satellite device through the transceiver, the second response carries information of the downlink data cache component or carries indication information indicating that the terminal uses the resources corresponding to the first session to receive downlink data; receiving downlink data through the first session according to the first information includes: receiving downlink data sent by the downlink data cache component on the satellite device through the first session according to the first information and the information of the downlink data cache component or the indication information; wherein the first parameter includes: uplink data sending status, candidate response methods for receiving downlink data, locally stored first session information, reasons for network paging, and at least one of the relevant identifiers of the satellite device.

[0654] The second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving method for downlink data supported by the terminal; and / or the second response carries a receiving method for downlink data allowed by the satellite device.

[0655] Furthermore, the operation also includes: sending, through the transceiver, a receiving mode for downlink data supported by the terminal to the satellite device.

[0656] The receiving of the downlink data sent by the downlink data cache component on the satellite device through the first session includes: receiving the downlink data sent by the satellite device according to the receiving mode and using the downlink data cache component on the satellite device through the first session.

[0657] Further, the operation also includes: determining a first mapping relationship between session identification information of the first session and air interface resources; accessing the satellite device according to the first parameter includes: accessing the satellite device according to the first parameter and the first mapping relationship.

[0658] The first session is a protocol data unit (PDU) session or a non-PDU session.

[0659] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment on the above-mentioned terminal side, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0660] The embodiment of the present application also provides a data transmission device, wherein the data transmission device is a satellite device, such as Fig.14 As shown, it includes a memory 141, a transceiver 142, and a processor 143:

[0661] The memory 141 is used to store computer programs; the transceiver 142 is used to send and receive data under the control of the processor 143; the processor 143 is used to read the computer program in the memory 141 and perform the following operations:

[0662] Sending first information of a first session to a terminal through the transceiver 142;

[0663] Sending downlink data to the terminal through the first session according to the first information;

[0664] The first session refers to a session that continuously occupies the allocated resources;

[0665] The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

[0666] The data transmission device provided in the embodiment of the present application sends the first information of the first session to the terminal; according to the first information, sends downlink data to the terminal through the first session; wherein the first session refers to a session that continuously occupies the allocated resources; the first information includes: fixed session identification information, and time information for the session to continuously occupy the allocated resources; it is possible to enable the terminal to accurately receive the corresponding downlink data through the maintained first session; it supports that in the case of non-end-to-end connection, through the maintained first session, the network can accurately determine the terminal corresponding to the downlink data, thereby ensuring that the target terminal accurately receives the downlink data; it is a good solution to the problem in the prior art that in the case of non-end-to-end connection, the target terminal cannot be guaranteed to accurately receive the downlink data.

[0667] Specifically, the transceiver 142 is used to receive and send data under the control of the processor 143.

[0668] Among them, Fig.14In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 143 and various circuits of memory represented by memory 141 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 142 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 143 is responsible for managing the bus architecture and general processing, and the memory 141 may store data used by the processor 143 when performing operations.

[0669] The processor 143 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0670] The first information further includes at least one of the following: a response method for receiving downlink data; a paging time window; a periodic registration timer; and a satellite identifier.

[0671] Furthermore, the operation also includes: determining the response method for receiving downlink data based on reference information; wherein the reference information includes: the time information, and at least one item of the downlink reception priority; and / or determining the paging time window or periodic registration timer corresponding to the terminal based on the ephemeris information of the satellite device.

[0672] In an embodiment of the present application, the operation further includes: determining whether to initiate paging or wait for the terminal to access according to the response method for receiving downlink data; wherein, when it is determined to initiate paging, instructing the terminal to receive downlink data in the paging reason.

[0673] Furthermore, the operation also includes: before sending the first information of the first session to the terminal, receiving a first request sent by the terminal through the transceiver; sending the first information of the first session to the terminal includes: according to the first request, feeding back a first response to the terminal, the first response carrying the first information of the first session; wherein the first request carries at least one of the following: receiving an uplink data delivery confirmation; waiting for receiving downlink data; receiving priority of downlink data; service type corresponding to the session.

[0674] In an embodiment of the present application, the operation also includes: reserving system resources and session information of a session corresponding to the first response; wherein the system resources are used to send downlink data.

[0675] Among them, the feeding back a first response to the terminal according to the first request includes: when the first request indicates a request to activate the on-board store-and-forward operation or the terminal has activated the on-board store-and-forward operation, according to the first request, allocating resources and establishing a first session or updating the existing session to the first session; according to the first session, feeding back a first response to the terminal.

[0676] Further, the operation also includes: before sending downlink data to the terminal through the first session according to the first information, receiving a second request sent by the terminal through the transceiver, the second request is used to obtain information of the downlink data cache component on the satellite device or indicate receiving downlink data or for requesting registration or for requesting sending uplink data; according to the second request, feeding back a second response to the terminal, the second response carries information of the downlink data cache component or carries indication information instructing the terminal to use the resources corresponding to the first session to receive downlink data; sending downlink data to the terminal through the first session according to the first information includes: according to the first information and the information of the downlink data cache component or the indication information, using the downlink data cache component on the satellite device to send downlink data to the terminal through the first session.

[0677] The second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving method for downlink data supported by the terminal; and / or the second response carries a receiving method for downlink data allowed by the satellite device.

[0678] Furthermore, the operation also includes: receiving, through the transceiver, a receiving mode for downlink data supported by the terminal and sent by the terminal.

[0679] Among them, using the downlink data caching component on the satellite device to send downlink data to the terminal through the first session includes: using the downlink data caching component on the satellite device to send downlink data to the terminal through the first session according to the first information and the receiving method for downlink data supported by the terminal.

[0680] In an embodiment of the present application, the first session is a protocol data unit PDU session or a non-PDU session.

[0681] Furthermore, the operation also includes: caching a notification for the terminal, the notification being used to indicate that the terminal has activated the on-board storage and forwarding operation; wherein the notification carries downlink data storage and forwarding information, and the downlink data storage and forwarding information includes: downlink data sending mode, the terminal identifier, the PDU session identifier, on-board storage configuration, the candidate user address identifier, and at least one of the candidate user IP addresses.

[0682] In the embodiment of the present application, the operation also includes: sending the notification to the server through the transceiver.

[0683] Furthermore, the operation also includes: before sending downlink data to the terminal through the first session according to the first information, determining the downlink data sending method according to the second information; wherein the second information includes: at least one of the intersatellite link status information and the server's downlink data storage and forwarding request; the downlink data storage forwarding request includes: at least one of the downlink forwarding strategy, forwarding priority and downlink data delivery confirmation method.

[0684] In an embodiment of the present application, the operation also includes: according to the downlink data sending method, feeding back a downlink data storage forwarding response to the server; wherein the downlink data storage forwarding response carries downlink data storage forwarding information, and the downlink data storage forwarding information includes: the downlink data sending method, the terminal identifier, the PDU session identifier, the on-board storage configuration, the expected time of delivery of the downlink data, the candidate user address identifier, and at least one of the candidate user IP addresses.

[0685] Among them, the on-board storage configuration includes: cache space, and at least one of the retention time of cache data; or, the on-board storage configuration does not include: cache space and the retention time of cache data, and the downlink data storage forwarding information also includes: cache space, and at least one of the retention time of cache data.

[0686] In the embodiment of the present application, the downlink data storage and forwarding information also includes: relevant information for monitoring the satellite device.

[0687] Furthermore, the operation also includes: determining a second mapping relationship between the identifier of the terminal, the identifier of the first session, and a related identifier of the server.

[0688] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment on the above-mentioned satellite equipment side, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

[0689] The embodiment of the present application also provides a data transmission device, wherein the data transmission device is a server, such as Fig.15 As shown, it includes a memory 151, a transceiver 152, and a processor 153:

[0690] The memory 151 is used to store computer programs; the transceiver 152 is used to send and receive data under the control of the processor 153; the processor 153 is used to read the computer program in the memory 151 and perform the following operations:

[0691] Receiving downlink data storage and forwarding information sent by the satellite equipment through the transceiver 152;

[0692] Sending downlink data to the satellite device through the transceiver 152 according to the downlink data storage and forwarding information;

[0693] The downlink data storage and forwarding information includes: downlink data sending mode, terminal identifier, PDU session identifier, on-board storage configuration, estimated time of downlink data delivery, candidate user address identifier, and at least one of the candidate user IP address;

[0694] The downlink data storage and forwarding information is carried in a notification to the terminal, where the notification is used to indicate that the terminal has activated the on-board storage and forwarding operation, or is carried in a downlink data storage and forwarding response.

[0695] The data transmission device provided in the embodiment of the present application receives downlink data storage and forwarding information sent by a satellite device; sends downlink data to the satellite device according to the downlink data storage and forwarding information; wherein the downlink data storage and forwarding information includes: downlink data sending mode, terminal identifier, PDU session identifier, on-board storage configuration, expected time for delivery of downlink data, candidate user address identifier, and at least one of the candidate user IP addresses; the downlink data storage and forwarding information is carried in a notification for the terminal, and the notification is used to indicate that the terminal has activated the on-board storage and forwarding operation, or is carried in a downlink data storage and forwarding response; it can support the terminal to accurately receive the corresponding downlink data through the maintained first session; it supports that in the case of non-end-to-end connection, through the maintained first session, the network can accurately determine the terminal corresponding to the downlink data, thereby ensuring that the target terminal accurately receives the downlink data; it is a good solution to the problem in the prior art that in the case of non-end-to-end connection, the target terminal cannot accurately receive the downlink data.

[0696] Specifically, the transceiver 152 is used to receive and send data under the control of the processor 153.

[0697] Among them, Fig.15 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 153 and various circuits of memory represented by memory 151 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 152 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 153 is responsible for managing the bus architecture and general processing, and the memory 151 may store data used by the processor 153 when performing operations.

[0698] The processor 153 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0699] Among them, sending downlink data to the satellite device according to the downlink data storage and forwarding information includes any one of the following: sending downlink data to the satellite device according to the downlink data storage and forwarding information during the process of receiving uplink cache data; sending downlink data to the satellite device according to the downlink data storage and forwarding information and downlink data sending demand information.

[0700] Furthermore, the operation also includes: before receiving the downlink data storage forwarding information sent by the satellite device, sending a downlink data storage forwarding request of the server to the satellite device through the transceiver; wherein the downlink data storage forwarding request includes: at least one of a downlink forwarding strategy, a forwarding priority, and a downlink data delivery confirmation method.

[0701] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment on the server side, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

[0702] The present application also provides a data transmission device, which is applied to a terminal, such as Fig.16 As shown, including:

[0703] The first receiving unit 161 is used to receive first information of a first session sent by a satellite device;

[0704] A second receiving unit 162, configured to receive downlink data through the first session according to the first information;

[0705] The first session refers to a session that continuously occupies the allocated resources;

[0706] The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

[0707] The data transmission device provided in the embodiment of the present application receives the first information of the first session sent by the satellite equipment; receives downlink data through the first session according to the first information; wherein the first session refers to a session that continuously occupies the allocated resources; the first information includes: fixed session identification information, and time information for the session to continuously occupy the allocated resources; it can enable the terminal to accurately receive the corresponding downlink data through the maintained first session; it supports that in the case of non-end-to-end connection, through the maintained first session, the network can accurately determine the terminal corresponding to the downlink data, thereby ensuring that the target terminal accurately receives the downlink data; it well solves the problem in the prior art that in the case of non-end-to-end connection, the target terminal cannot be guaranteed to accurately receive the downlink data.

[0708] The first information further includes at least one of the following: a response method for receiving downlink data; a paging time window; a periodic registration timer; and a satellite identifier.

[0709] Furthermore, the data transmission device also includes: a first sending unit, used to send a first request to the satellite device according to the downlink data receiving demand information before receiving the first information of the first session sent by the satellite device; the receiving of the first information of the first session sent by the satellite device includes: receiving a first response fed back by the satellite device, the first response carrying the first information of the first session; wherein the first request carries at least one of the following: receiving uplink data delivery confirmation; waiting for receiving downlink data; receiving priority of downlink data; service type corresponding to the session.

[0710] In the embodiment of the present application, the data transmission device further includes: a first processing unit, used to reserve air interface resources and session information of the corresponding session according to the first response; wherein the air interface resources are used to receive downlink data.

[0711] Further, the data transmission device further includes: a second processing unit, used to access the satellite device according to a first parameter and send a second request to the satellite device before receiving downlink data through the first session according to the first information, the second request being used to obtain information of a downlink data cache component on the satellite device or indicating receiving downlink data or requesting registration or requesting sending uplink data; a third receiving unit, used to receive a second response fed back by the satellite device, the second response carrying information of the downlink data cache component or carrying indication information indicating that the terminal uses resources corresponding to the first session to receive downlink data; receiving downlink data through the first session according to the first information includes: receiving downlink data sent by the downlink data cache component on the satellite device through the first session according to the first information and the information of the downlink data cache component or the indication information; wherein the first parameter includes at least one of: uplink data sending status, candidate response methods for receiving downlink data, locally stored first session information, reason for network paging, and relevant identification of the satellite device.

[0712] The second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving method for downlink data supported by the terminal; and / or the second response carries a receiving method for downlink data allowed by the satellite device.

[0713] Furthermore, the data transmission device also includes: a second sending unit, used to send a receiving mode for downlink data supported by the terminal to the satellite device.

[0714] The receiving of the downlink data sent by the downlink data cache component on the satellite device through the first session includes: receiving the downlink data sent by the satellite device according to the receiving mode and using the downlink data cache component on the satellite device through the first session.

[0715] Furthermore, the data transmission device also includes: a first determination unit, used to determine a first mapping relationship between the session identification information of the first session and the air interface resources; accessing the satellite device according to the first parameter includes: accessing the satellite device according to the first parameter and the first mapping relationship.

[0716] The first session is a protocol data unit (PDU) session or a non-PDU session.

[0717] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment on the above-mentioned terminal side, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

[0718] The present application also provides a data transmission device, which is applied to satellite equipment, such as Fig.17 As shown, including:

[0719] The third sending unit 171 is configured to send first information of a first session to a terminal;

[0720] A fourth receiving unit 172, configured to send downlink data to the terminal through the first session according to the first information;

[0721] The first session refers to a session that continuously occupies the allocated resources;

[0722] The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

[0723] The data transmission device provided in the embodiment of the present application sends the first information of the first session to the terminal; according to the first information, sends downlink data to the terminal through the first session; wherein the first session refers to a session that continuously occupies the allocated resources; the first information includes: fixed session identification information, and time information for the session to continuously occupy the allocated resources; it is possible to enable the terminal to accurately receive the corresponding downlink data through the maintained first session; it supports that in the case of non-end-to-end connection, through the maintained first session, the network can accurately determine the terminal corresponding to the downlink data, thereby ensuring that the target terminal accurately receives the downlink data; it is a good solution to the problem in the prior art that in the case of non-end-to-end connection, the target terminal cannot be guaranteed to accurately receive the downlink data.

[0724] The first information further includes at least one of the following: a response method for receiving downlink data; a paging time window; a periodic registration timer; and a satellite identifier.

[0725] Furthermore, the data transmission device also includes: a second determination unit, used to determine the response method for receiving downlink data based on reference information; wherein the reference information includes: the time information, and at least one item of the downlink reception priority; and / or, based on the ephemeris information of the satellite device, determine the paging time window or periodic registration timer corresponding to the terminal.

[0726] In an embodiment of the present application, the data transmission device further includes: a third determination unit, used to determine whether to initiate paging or wait for the terminal to access according to the response method for receiving downlink data; wherein, when it is determined to initiate paging, the terminal is instructed to receive downlink data in the paging reason.

[0727] Furthermore, the data transmission device also includes: a fourth receiving unit, used to receive a first request sent by the terminal before sending the first information of the first session to the terminal; the sending of the first information of the first session to the terminal includes: according to the first request, feeding back a first response to the terminal, the first response carrying the first information of the first session; wherein the first request carries at least one of the following: receiving an uplink data delivery confirmation; waiting for receiving downlink data; receiving priority of downlink data; service type corresponding to the session.

[0728] In the embodiment of the present application, the data transmission device further includes: a third processing unit, used to reserve system resources and session information of the session corresponding to the first response; wherein the system resources are used to send downlink data.

[0729] Among them, the feeding back a first response to the terminal according to the first request includes: when the first request indicates a request to activate the on-board store-and-forward operation or the terminal has activated the on-board store-and-forward operation, according to the first request, allocating resources and establishing a first session or updating the existing session to the first session; according to the first session, feeding back a first response to the terminal.

[0730] Furthermore, the data transmission device also includes: a fifth receiving unit, used to receive a second request sent by the terminal before sending downlink data to the terminal through the first session according to the first information, the second request being used to obtain information of a downlink data cache component on the satellite device or to indicate receiving downlink data or to request registration or to request sending uplink data; a first feedback unit, used to feed back a second response to the terminal according to the second request, the second response carrying information of the downlink data cache component or carrying indication information instructing the terminal to use the resources corresponding to the first session to receive downlink data; sending downlink data to the terminal through the first session according to the first information includes: sending downlink data to the terminal through the first session using the downlink data cache component on the satellite device according to the first information and the information of the downlink data cache component or the indication information.

[0731] The second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving method for downlink data supported by the terminal; and / or the second response carries a receiving method for downlink data allowed by the satellite device.

[0732] Furthermore, the data transmission device further includes: a sixth receiving unit, configured to receive a receiving mode for downlink data sent by the terminal and supported by the terminal.

[0733] Among them, using the downlink data caching component on the satellite device to send downlink data to the terminal through the first session includes: using the downlink data caching component on the satellite device to send downlink data to the terminal through the first session according to the first information and the receiving method for downlink data supported by the terminal.

[0734] In an embodiment of the present application, the first session is a protocol data unit PDU session or a non-PDU session.

[0735] Furthermore, the data transmission device also includes: a first cache unit, used to cache notifications for the terminal, the notification is used to indicate that the terminal has activated the on-board storage and forwarding operation; wherein the notification carries downlink data storage and forwarding information, and the downlink data storage and forwarding information includes: downlink data sending mode, the terminal identifier, PDU session identifier, on-board storage configuration, candidate user address identifier, and at least one of the candidate user IP addresses.

[0736] In the embodiment of the present application, the data transmission device further includes: a fifth sending unit, configured to send the notification to the server.

[0737] Furthermore, the data transmission device also includes: a fourth determination unit, used to determine the downlink data sending method according to the second information before sending the downlink data to the terminal through the first session according to the first information; wherein the second information includes: at least one of the intersatellite link status information and the server's downlink data storage and forwarding request; the downlink data storage forwarding request includes: at least one of the downlink forwarding strategy, forwarding priority and downlink data delivery confirmation method.

[0738] In an embodiment of the present application, the data transmission device further includes: a second feedback unit, which is used to feed back a downlink data storage forwarding response to the server according to the downlink data sending method; wherein the downlink data storage forwarding response carries downlink data storage forwarding information, and the downlink data storage forwarding information includes: the downlink data sending method, the terminal identifier, the PDU session identifier, the on-board storage configuration, the expected time of delivery of the downlink data, the candidate user address identifier, and at least one of the candidate user IP addresses.

[0739] Among them, the on-board storage configuration includes: cache space, and at least one of the retention time of cache data; or, the on-board storage configuration does not include: cache space and the retention time of cache data, and the downlink data storage forwarding information also includes: cache space, and at least one of the retention time of cache data.

[0740] In the embodiment of the present application, the downlink data storage and forwarding information also includes: relevant information for monitoring the satellite device.

[0741] Furthermore, the data transmission device further includes: a fifth determining unit, configured to determine a second mapping relationship between the identifier of the terminal, the identifier of the first session, and a related identifier of the server.

[0742] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment on the above-mentioned satellite equipment side, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

[0743] The present application also provides a data transmission device, which is applied to a server, such as Fig.18 As shown, including:

[0744] The seventh receiving unit 181 is used to receive downlink data storage and forwarding information sent by the satellite device;

[0745] A sixth sending unit 182, configured to send downlink data to a satellite device according to the downlink data storage and forwarding information;

[0746] The downlink data storage and forwarding information includes: downlink data sending mode, terminal identifier, PDU session identifier, on-board storage configuration, estimated time of downlink data delivery, candidate user address identifier, and at least one of the candidate user IP address;

[0747] The downlink data storage and forwarding information is carried in a notification to the terminal, where the notification is used to indicate that the terminal has activated the on-board storage and forwarding operation, or is carried in a downlink data storage and forwarding response.

[0748] The data transmission device provided in the embodiment of the present application receives downlink data storage and forwarding information sent by a satellite device; sends downlink data to the satellite device according to the downlink data storage and forwarding information; wherein the downlink data storage and forwarding information includes: a downlink data sending mode, a terminal identifier, a PDU session identifier, an on-board storage configuration, an expected time for delivery of downlink data, a candidate user address identifier, and at least one of a candidate user IP address; the downlink data storage and forwarding information is carried in a notification for the terminal, the notification is used to indicate that the terminal has activated the on-board storage and forwarding operation, or is carried in a downlink data storage and forwarding response; it can support the terminal to accurately receive the corresponding downlink data through the maintained first session; it supports that in the case of a non-end-to-end connection, the network can accurately determine the terminal corresponding to the downlink data through the maintained first session, thereby ensuring that the target terminal accurately receives the downlink data; it well solves the problem in the prior art that in the case of a non-end-to-end connection, the target terminal cannot accurately receive the downlink data.

[0749] Among them, sending downlink data to the satellite device according to the downlink data storage and forwarding information includes any one of the following: sending downlink data to the satellite device according to the downlink data storage and forwarding information during the process of receiving uplink cache data; sending downlink data to the satellite device according to the downlink data storage and forwarding information and downlink data sending demand information.

[0750] Furthermore, the data transmission device also includes: a seventh sending unit, which is used to send a downlink data storage forwarding request of the server to the satellite device before receiving the downlink data storage forwarding information sent by the satellite device; wherein the downlink data storage forwarding request includes: at least one of a downlink forwarding strategy, a forwarding priority, and a downlink data delivery confirmation method.

[0751] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment on the server side, and can achieve the same technical effect. The parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0752] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0753] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially 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, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0754] An embodiment of the present application also provides a non-transitory readable storage medium, which stores a computer program, and the computer program is used to enable a processor to execute the above-mentioned terminal side, satellite device side or server side method.

[0755] The non-transitory readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical (MO)), etc.), optical storage (such as compact discs (CD), digital video discs (DVD), Blu-ray discs (BD), high-definition versatile discs (HVD), etc.), and semiconductor memories (such as ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read only memory (EEPROM), non-volatile memory (NAND (Non-volatile Memory Device) FLASH), solid-state drives (SSD)), etc.

[0756] Among them, the implementation embodiments of the methods on the above terminal side, satellite device side or server side are all applicable to the embodiments of the non-transitory readable storage medium, and can also achieve the same technical effects.

[0757] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0758] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0759] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0760] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0761] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A data transmission method, applied to a terminal, characterized in that: include: receiving first information of a first session sent by a satellite device; receiving downlink data through the first session according to the first information; The first session refers to a session that continuously occupies the allocated resources; The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

2. The data transmission method according to claim 1, characterized in that: The first information also includes at least one of the following: A response method for receiving downlink data; Paging time window; Periodic registration timer; Satellite identification.

3. The data transmission method according to claim 1, characterized in that: Before receiving the first information of the first session sent by the satellite device, the method further includes: Sending a first request to the satellite device according to the downlink data receiving demand information; The receiving first information of the first session sent by the satellite device includes: receiving a first response fed back by the satellite device, where the first response carries first information of a first session; The first request carries at least one of the following: Receive uplink data delivery confirmation; Waiting to receive downlink data; Receiving priority of downlink data; Service type corresponding to the session.

4. The data transmission method according to claim 3, characterized in that: Also includes: According to the first response, retaining air interface resources and session information corresponding to the session; The air interface resources are used to receive downlink data.

5. The data transmission method according to claim 1, characterized in that: Before receiving downlink data through the first session according to the first information, the method further includes: Accessing the satellite device according to the first parameter, and sending a second request to the satellite device, wherein the second request is used to obtain information of a downlink data buffer component on the satellite device or to indicate receiving downlink data or to request registration or to request sending uplink data; receiving a second response fed back by the satellite device, where the second response carries information of the downlink data buffer component or carries indication information instructing the terminal to use resources corresponding to the first session to receive downlink data; The receiving downlink data through the first session according to the first information includes: receiving, through the first session, downlink data sent by the downlink data buffer component on the satellite device according to the first information and the information of the downlink data buffer component or the indication information; The first parameter includes at least one of: uplink data transmission status, candidate response modes for receiving downlink data, locally stored first session information, reasons for network paging, and relevant identifiers of the satellite device.

6. The data transmission method according to claim 5, characterized in that: The second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving mode for downlink data supported by the terminal; And / or, the second response carries a downlink data receiving mode allowed by the satellite device.

7. The data transmission method according to claim 5, characterized in that: Also includes: A receiving mode for downlink data supported by the terminal is sent to the satellite device.

8. The data transmission method according to claim 6 or 7, characterized in that: The receiving, through the first session, the downlink data sent by the downlink data buffer component on the satellite device comprises: The downlink data sent by the satellite device according to the receiving mode and using the downlink data buffer component on the satellite device is received through the first session.

9. The data transmission method according to claim 5, characterized in that: Also includes: Determine a first mapping relationship between the session identification information of the first session and the air interface resources; The step of accessing the satellite device according to the first parameter includes: The satellite device is accessed according to the first parameter and the first mapping relationship.

10. The data transmission method according to claim 1, characterized in that: The first session is a protocol data unit (PDU) session or a non-PDU session.

11. A data transmission method, applied to satellite equipment, characterized in that: include: Sending first information of a first session to a terminal; Sending downlink data to the terminal through the first session according to the first information; The first session refers to a session that continuously occupies the allocated resources; The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

12. The data transmission method according to claim 11, characterized in that: The first information also includes at least one of the following: A response method for receiving downlink data; Paging time window; Periodic registration timer; Satellite identification.

13. The data transmission method according to claim 12, characterized in that: Also includes: Determine the response mode for receiving downlink data according to the reference information; wherein the reference information includes: the time information, and at least one of the downlink receiving priority; And / or, determining a paging time window or a periodic registration timer corresponding to the terminal according to the ephemeris information of the satellite device.

14. The data transmission method according to claim 12, characterized in that: Also includes: Determining, according to the response mode for receiving downlink data, to initiate paging or wait for the terminal to access; Wherein, when it is determined to initiate paging, the terminal is instructed to receive downlink data in the paging reason.

15. The data transmission method according to claim 11, characterized in that: Before sending the first information of the first session to the terminal, the method further includes: receiving a first request sent by the terminal; The sending the first information of the first session to the terminal includes: Feedback a first response to the terminal according to the first request, where the first response carries first information of the first session; The first request carries at least one of the following: Receive uplink data delivery confirmation; Waiting to receive downlink data; Receiving priority of downlink data; Service type corresponding to the session.

16. The data transmission method according to claim 15, characterized in that: Also includes: Reserving system resources and session information of the session corresponding to the first response; The system resources are used to send downlink data.

17. The data transmission method according to claim 15, characterized in that: The feeding back a first response to the terminal according to the first request includes: In a case where the first request indicates a request to activate the on-board store-and-forward operation or the terminal has activated the on-board store-and-forward operation, allocating resources and establishing a first session or updating an existing session to the first session according to the first request; According to the first session, a first response is fed back to the terminal.

18. The data transmission method according to claim 11, characterized in that: Before sending downlink data to the terminal through the first session according to the first information, the method further includes: receiving a second request sent by the terminal, where the second request is used to obtain information of a downlink data buffer component on the satellite device or to indicate receiving downlink data or to request registration or to request sending uplink data; Feedback a second response to the terminal according to the second request, where the second response carries information about the downlink data buffer component or carries indication information instructing the terminal to use resources corresponding to the first session to receive downlink data; The sending downlink data to the terminal through the first session according to the first information includes: According to the first information and the information of the downlink data buffer component or the indication information, the downlink data is sent to the terminal through the first session by utilizing the downlink data buffer component on the satellite device.

19. The data transmission method according to claim 18, characterized in that: The second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving mode for downlink data supported by the terminal; And / or, the second response carries a downlink data receiving mode allowed by the satellite device.

20. The data transmission method according to claim 18, characterized in that: Also includes: A receiving mode for downlink data supported by the terminal is received and sent by the terminal.

21. The data transmission method according to claim 19 or 20, characterized in that: The sending downlink data to the terminal through the first session by using the downlink data buffer component on the satellite device includes: According to the first information and the receiving mode for downlink data supported by the terminal, the downlink data is sent to the terminal through the first session by utilizing the downlink data buffer component on the satellite device.

22. The data transmission method according to claim 11, characterized in that: The first session is a protocol data unit (PDU) session or a non-PDU session.

23. The data transmission method according to claim 11, characterized in that: Also includes: caching a notification for the terminal, the notification being used to indicate that the terminal has activated an on-board store-and-forward operation; The notification carries downlink data storage and forwarding information, and the downlink data storage and forwarding information includes: downlink data sending mode, the terminal identifier, PDU session identifier, on-board storage configuration, candidate user address identifier, and at least one of the candidate user IP addresses.

24. The data transmission method according to claim 23, characterized in that: Also includes: The notification is sent to a server.

25. The data transmission method according to claim 11, characterized in that: Before sending downlink data to the terminal through the first session according to the first information, the method further includes: Determining a downlink data sending mode according to the second information; The second information includes: at least one of the intersatellite link status information and the server's downlink data storage and forwarding request; the downlink data storage and forwarding request includes: at least one of the downlink forwarding strategy, forwarding priority and downlink data delivery confirmation method.

26. The data transmission method according to claim 25, characterized in that: Also includes: Feedback a downlink data storage and forwarding response to the server according to the downlink data sending mode; Among them, the downlink data storage forwarding response carries downlink data storage forwarding information, and the downlink data storage forwarding information includes: the downlink data sending method, the terminal identifier, the PDU session identifier, the on-board storage configuration, the expected time of delivery of the downlink data, the candidate user address identifier, and at least one of the candidate user IP addresses.

27. The data transmission method according to claim 23 or 26, characterized in that: The on-board storage configuration includes: cache space, and at least one of the retention time of cache data; Alternatively, the on-board storage configuration does not include: cache space and retention time of cache data, and the downlink data storage and forwarding information also includes: cache space, and at least one of retention time of cache data.

28. The data transmission method according to claim 23 or 26, characterized in that: The downlink data storage and forwarding information also includes: relevant information for monitoring the satellite equipment.

29. The data transmission method according to claim 11, characterized in that: Also includes: Determine a second mapping relationship between the identifier of the terminal, the identifier of the first session, and a related identifier of the server.

30. A data transmission method, applied to a server, characterized in that: include: Receiving downlink data storage and forwarding information sent by satellite equipment; Sending downlink data to the satellite device according to the downlink data storage and forwarding information; The downlink data storage and forwarding information includes: downlink data sending mode, terminal identifier, PDU session identifier, on-board storage configuration, estimated time of downlink data delivery, candidate user address identifier, and at least one of the candidate user IP address; The downlink data storage and forwarding information is carried in a notification to the terminal, where the notification is used to indicate that the terminal has activated the on-board storage and forwarding operation, or is carried in a downlink data storage and forwarding response.

31. The data transmission method according to claim 30, characterized in that: The sending of downlink data to the satellite device according to the downlink data storage and forwarding information includes any one of the following: In the process of receiving the uplink buffer data, sending the downlink data to the satellite device according to the downlink data storage and forwarding information; The downlink data is sent to the satellite device according to the downlink data storage and forwarding information and the downlink data sending requirement information.

32. The data transmission method according to claim 30, characterized in that: Before receiving the downlink data storage and forwarding information sent by the satellite device, it also includes: Sending a downlink data storage and forwarding request of the server to the satellite device; The downlink data storage and forwarding request includes: at least one of a downlink forwarding strategy, a forwarding priority, and a downlink data delivery confirmation method.

33. A data transmission device, the data transmission device being a terminal, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Receiving, by the transceiver, first information of a first session sent by a satellite device; receiving downlink data through the first session according to the first information; The first session refers to a session that continuously occupies the allocated resources; The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

34. The data transmission device according to claim 33, characterized in that: The first information also includes at least one of the following: A response method for receiving downlink data; Paging time window; Periodic registration timer; Satellite identification.

35. The data transmission device according to claim 33, characterized in that: The operations also include: Before receiving the first information of the first session sent by the satellite device, sending a first request to the satellite device through the transceiver according to the downlink data reception requirement information; The receiving first information of the first session sent by the satellite device includes: receiving a first response fed back by the satellite device, where the first response carries first information of a first session; The first request carries at least one of the following: Receive uplink data delivery confirmation; Waiting to receive downlink data; Receiving priority of downlink data; Service type corresponding to the session.

36. The data transmission device according to claim 35, characterized in that: The operations also include: According to the first response, retaining air interface resources and session information corresponding to the session; The air interface resources are used to receive downlink data.

37. The data transmission device according to claim 33, characterized in that: The operations also include: Before receiving downlink data through the first session according to the first information, accessing the satellite device according to the first parameter, and sending a second request to the satellite device through the transceiver, the second request being used to obtain information of a downlink data buffer component on the satellite device or to indicate receiving downlink data or to request registration or to request sending uplink data; receiving, by the transceiver, a second response fed back by the satellite device, where the second response carries information of the downlink data buffer component or carries indication information instructing the terminal to use resources corresponding to the first session to receive downlink data; The receiving downlink data through the first session according to the first information includes: receiving, through the first session, downlink data sent by the downlink data buffer component on the satellite device according to the first information and the information of the downlink data buffer component or the indication information; The first parameter includes at least one of: uplink data transmission status, candidate response modes for receiving downlink data, locally stored first session information, reasons for network paging, and relevant identifiers of the satellite device.

38. The data transmission device according to claim 37, characterized in that: The second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving mode for downlink data supported by the terminal; And / or, the second response carries a downlink data receiving mode allowed by the satellite device.

39. The data transmission device according to claim 37, characterized in that: The operations also include: The receiving mode for downlink data supported by the terminal is sent to the satellite device through the transceiver.

40. The data transmission device according to claim 38 or 39, characterized in that: The receiving, through the first session, the downlink data sent by the downlink data buffer component on the satellite device comprises: The downlink data sent by the satellite device according to the receiving mode and using the downlink data buffer component on the satellite device is received through the first session.

41. The data transmission device according to claim 37, characterized in that: The operations also include: Determine a first mapping relationship between the session identification information of the first session and the air interface resources; The step of accessing the satellite device according to the first parameter includes: The satellite device is accessed according to the first parameter and the first mapping relationship.

42. The data transmission device according to claim 33, characterized in that: The first session is a protocol data unit (PDU) session or a non-PDU session.

43. A data transmission device, the data transmission device being a satellite device, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Sending, via the transceiver, first information of a first session to a terminal; Sending downlink data to the terminal through the first session according to the first information; The first session refers to a session that continuously occupies the allocated resources; The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

44. The data transmission device according to claim 43, characterized in that: The first information also includes at least one of the following: A response method for receiving downlink data; Paging time window; Periodic registration timer; Satellite identification.

45. The data transmission device according to claim 44, characterized in that: The operations also include: Determine the response mode for receiving downlink data according to the reference information; wherein the reference information includes: the time information, and at least one of the downlink receiving priority; And / or, determining a paging time window or a periodic registration timer corresponding to the terminal according to the ephemeris information of the satellite device.

46. ​​The data transmission device according to claim 44, characterized in that: The operations also include: Determining, according to the response mode for receiving downlink data, to initiate paging or wait for the terminal to access; Wherein, when it is determined to initiate paging, the terminal is instructed to receive downlink data in the paging reason.

47. The data transmission device according to claim 43, characterized in that: The operations also include: Before sending first information of a first session to a terminal, receiving, by the transceiver, a first request sent by the terminal; The sending the first information of the first session to the terminal includes: Feedback a first response to the terminal according to the first request, where the first response carries first information of the first session; The first request carries at least one of the following: Receive uplink data delivery confirmation; Waiting to receive downlink data; Receiving priority of downlink data; Service type corresponding to the session.

48. The data transmission device according to claim 47, characterized in that: The operations also include: Reserving system resources and session information of the session corresponding to the first response; The system resources are used to send downlink data.

49. The data transmission device according to claim 47, characterized in that: The feeding back a first response to the terminal according to the first request includes: In a case where the first request indicates a request to activate the on-board store-and-forward operation or the terminal has activated the on-board store-and-forward operation, allocating resources and establishing a first session or updating an existing session to the first session according to the first request; According to the first session, a first response is fed back to the terminal.

50. The data transmission device according to claim 43, characterized in that: The operations also include: Before sending downlink data to the terminal through the first session according to the first information, receiving a second request sent by the terminal through the transceiver, the second request being used to obtain information of a downlink data buffer component on the satellite device or to indicate receiving downlink data or to request registration or to request sending uplink data; Feedback a second response to the terminal according to the second request, where the second response carries information about the downlink data buffer component or carries indication information instructing the terminal to use resources corresponding to the first session to receive downlink data; The sending downlink data to the terminal through the first session according to the first information includes: According to the first information and the information of the downlink data buffer component or the indication information, the downlink data is sent to the terminal through the first session by utilizing the downlink data buffer component on the satellite device.

51. The data transmission device according to claim 50, characterized in that: The second request carries an indication that the terminal is allowed to receive downlink data, and / or a receiving mode for downlink data supported by the terminal; And / or, the second response carries a downlink data receiving mode allowed by the satellite device.

52. The data transmission device according to claim 50, characterized in that: The operations also include: A receiving mode for downlink data supported by the terminal and sent by the terminal is received through the transceiver.

53. The data transmission device according to claim 51 or 52, characterized in that: The sending downlink data to the terminal through the first session by using the downlink data buffer component on the satellite device includes: According to the first information and the receiving mode for downlink data supported by the terminal, the downlink data is sent to the terminal through the first session by utilizing the downlink data buffer component on the satellite device.

54. The data transmission device according to claim 43, characterized in that: The first session is a protocol data unit (PDU) session or a non-PDU session.

55. The data transmission device according to claim 43, characterized in that: The operations also include: caching a notification for the terminal, the notification being used to indicate that the terminal has activated an on-board store-and-forward operation; The notification carries downlink data storage and forwarding information, and the downlink data storage and forwarding information includes: downlink data sending mode, the terminal identifier, PDU session identifier, on-board storage configuration, candidate user address identifier, and at least one of the candidate user IP addresses.

56. The data transmission device according to claim 55, characterized in that: The operations also include: The notification is sent to a server via the transceiver.

57. The data transmission device according to claim 43, characterized in that: The operations also include: Before sending downlink data to the terminal through the first session according to the first information, determining a downlink data sending mode according to the second information; The second information includes: at least one of the intersatellite link status information and the server's downlink data storage and forwarding request; the downlink data storage and forwarding request includes: at least one of the downlink forwarding strategy, forwarding priority and downlink data delivery confirmation method.

58. The data transmission device according to claim 57, characterized in that: The operations also include: Feedback a downlink data storage and forwarding response to the server according to the downlink data sending mode; Among them, the downlink data storage forwarding response carries downlink data storage forwarding information, and the downlink data storage forwarding information includes: the downlink data sending method, the terminal identifier, the PDU session identifier, the on-board storage configuration, the expected time of delivery of the downlink data, the candidate user address identifier, and at least one of the candidate user IP addresses.

59. The data transmission device according to claim 55 or 58, characterized in that: The on-board storage configuration includes: cache space, and at least one of the retention time of cache data; Alternatively, the on-board storage configuration does not include: cache space and retention time of cache data, and the downlink data storage and forwarding information also includes: cache space, and at least one of retention time of cache data.

60. The data transmission device according to claim 55 or 58, characterized in that: The downlink data storage and forwarding information also includes: relevant information for monitoring the satellite equipment.

61. The data transmission device according to claim 43, characterized in that: The operations also include: Determine a second mapping relationship between the identifier of the terminal, the identifier of the first session, and a related identifier of the server.

62. A data transmission device, the data transmission device being a server, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Receiving downlink data storage and forwarding information sent by satellite equipment through the transceiver; Sending downlink data to the satellite device through the transceiver according to the downlink data storage and forwarding information; The downlink data storage and forwarding information includes: downlink data sending mode, terminal identifier, PDU session identifier, on-board storage configuration, estimated time of downlink data delivery, candidate user address identifier, and at least one of the candidate user IP address; The downlink data storage and forwarding information is carried in a notification to the terminal, where the notification is used to indicate that the terminal has activated the on-board storage and forwarding operation, or is carried in a downlink data storage and forwarding response.

63. The data transmission device according to claim 62, characterized in that: The sending of downlink data to the satellite device according to the downlink data storage and forwarding information includes any one of the following: In the process of receiving the uplink buffer data, sending the downlink data to the satellite device according to the downlink data storage and forwarding information; The downlink data is sent to the satellite device according to the downlink data storage and forwarding information and the downlink data sending requirement information.

64. The data transmission device according to claim 62, characterized in that: The operations also include: Before receiving the downlink data storage and forwarding information sent by the satellite device, sending a downlink data storage and forwarding request of the server to the satellite device through the transceiver; The downlink data storage and forwarding request includes: at least one of a downlink forwarding strategy, a forwarding priority, and a downlink data delivery confirmation method.

65. A data transmission device, applied to a terminal, characterized in that: include: A first receiving unit, configured to receive first information of a first session sent by a satellite device; A second receiving unit, configured to receive downlink data through the first session according to the first information; The first session refers to a session that continuously occupies the allocated resources; The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

66. A data transmission device, applied to satellite equipment, characterized in that: include: A third sending unit, configured to send first information of a first session to a terminal; a fourth receiving unit, configured to send downlink data to the terminal through the first session according to the first information; The first session refers to a session that continuously occupies the allocated resources; The first information includes: fixed session identification information and time information of the session continuously occupying the allocated resources.

67. A data transmission device, applied to a server, characterized in that: include: A seventh receiving unit, used for receiving downlink data storage and forwarding information sent by the satellite device; A sixth sending unit, configured to send downlink data to a satellite device according to the downlink data storage and forwarding information; The downlink data storage and forwarding information includes: downlink data sending mode, terminal identifier, PDU session identifier, on-board storage configuration, estimated time of downlink data delivery, candidate user address identifier, and at least one of the candidate user IP address; The downlink data storage and forwarding information is carried in a notification to the terminal, where the notification is used to indicate that the terminal has activated the on-board storage and forwarding operation, or is carried in a downlink data storage and forwarding response.

68. A non-transitory readable storage medium, characterized in that The non-transitory readable storage medium stores a computer program, and the computer program is used to cause a processor to execute the method according to any one of claims 1 to 32.