Communication method, communication apparatus, and communication system

By selecting appropriate satellites through mobility management network elements and session management network elements, and using satellite-based user-surface network elements and satellite-based application servers for data storage and forwarding, the problem of terminal equipment communication interruption under satellite discontinuous coverage is solved, and the communication interruption of terminal equipment is realized. Correct communication of terminal devices and reduced pressure on 3GPP networks.

WO2024239660A1PCT designated stage expired Publication Date: 2024-11-28HUAWEI TECH CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/070300
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-19
Filing Date
2024-01-03
Publication Date
2024-11-28

AI Technical Summary

Technical Problem

In the scenario of satellite discontinuous coverage, the terminal equipment cannot establish a connection with the satellite and the ground core network at the same time, resulting in interruption of communication and it is difficult for the prior art to achieve correct communication of the terminal equipment.

Method used

Through the mobility management network element and the session management network element, select appropriate satellites according to the communication plan of the terminal device, and data storage and forwarding are carried out through the satellite-based user-surface network element and the satellite-based application server to ensure that the terminal device cannot use the satellite on the satellite. Communication can still be achieved when the core network is connected.

Benefits of technology

It realizes correct communication between terminal devices in satellite discontinuous coverage scenarios, reduces the storage pressure of the 3GPP network, and improves communication efficiency and reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024070300_28112024_PF_FP_ABST
    Figure CN2024070300_28112024_PF_FP_ABST
Patent Text Reader

Abstract

The present application provides a communication method, a communication apparatus, and a communication system. In the method, in a scenario in which a satellite cannot be simultaneously connected to a terminal device and a core network, a mobility management network element selects, for the terminal device according to a communication plan of the terminal device, a first satellite providing service, and sends the identifier of the first satellite to a session management network element, and the session management network element selects, for the terminal device on the basis of the identifier of the first satellite, a satellite-borne user plane network element providing service for the terminal device, thereby achieving correct communication of the terminal device.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method, communication device and communication system

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 19, 2023, with application number 202310578093.5 and application name “A communication method, communication device and communication system”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of wireless communication technology, and in particular to a communication method, a communication device, and a communication system. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) considers satellites supporting data processing, that is, considering that satellites provide non-transparent forwarding capabilities (or called renewable capabilities). Therefore, by deploying access network equipment on satellites, satellites can be equipped with data processing capabilities.

[0005] Since non-geosynchronous satellites such as medium earth orbit (MEO) and low earth orbit (LEO) move relative to the ground, a single satellite or multiple satellites that do not yet have inter-satellite link networking cannot always provide signal coverage to terminal devices, resulting in discontinuous coverage when terminal devices use satellite access.

[0006] The discontinuous coverage scenario currently being discussed by 3GPP assumes that when a terminal device is covered by a satellite, the satellite can also establish a connection with the terrestrial core network through a ground gateway. In other words, the satellite can establish connections with both the terminal device and the core network at the same time.

[0007] However, in other scenarios with discontinuous satellite coverage, such as when a terminal device is located over the ocean, on an isolated island, or in polar regions, the satellite cannot establish a connection with the terrestrial core network through the ground gateway when the terminal device is covered by the satellite. This means that the satellite cannot simultaneously establish a connection with both the terminal device and the core network. Ensuring proper communication between the terminal device and the core network in these scenarios remains a challenge.

[0008] Summary of the Invention

[0009] The present application provides a communication method, a communication device and a communication system for achieving correct communication of terminal devices.

[0010] In a first aspect, an embodiment of the present application provides a communication method, which can be performed by a mobility management network element or a module (such as a chip) applied to the mobility management network element. The method includes: determining, based on a communication plan of a terminal device, a first satellite that is expected to provide communication services for the terminal device; and sending an identifier of the first satellite to a session management network element. The communication plan includes the identifier of at least one satellite to be used. Alternatively, the communication plan includes at least two sets of service information, the at least two sets of service information including a first set of service information and a second set of service information, the first set of service information including first communication location information and first communication time information, the first communication location information indicating a first location at which the terminal device is expected to use satellite communication, the first communication time information indicating a first time at which the terminal device is expected to use satellite communication at the first location, and the second set of service information including second communication location information and second communication time information, the second communication location information indicating a second location at which the terminal device is expected to use satellite communication, and the second communication time information indicating a second time at which the terminal device is expected to use satellite communication at the second location, the second time being different from the first time.

[0011] In the above scheme, in a scenario where the satellite cannot be connected to the terminal device and the core network at the same time, the mobility management network element selects a first satellite that provides services for the terminal device based on the communication plan of the terminal device, and sends the identifier of the first satellite to the session management network element. The session management network element selects a satellite-based user plane network element that provides services for the terminal device based on the identifier of the first satellite, thereby achieving correct communication of the terminal device.

[0012] In one possible implementation method, the first communication time information includes at least two of a first start time, a first communication duration, or a first end time; the second communication time information includes at least two of a second start time, a second communication duration, or a second end time.

[0013] In a possible implementation method, the first position is different from the second position.

[0014] In one possible implementation method, when the communication plan includes the identifier of the at least one satellite expected to be used, the communication plan also includes communication time information corresponding to the at least one satellite expected to be used, and the communication time information corresponding to the first satellite is used to indicate the time when the terminal device expects to use the first satellite to communicate.

[0015] The above scheme includes communication time information in the communication plan, which is conducive to more accurately selecting a satellite to provide services for the terminal equipment.

[0016] In a possible implementation method, the method further includes: receiving the communication plan from the terminal device, the ground application server or the network management device.

[0017] In a possible implementation method, the method further includes: sending an access stratum context of the terminal device to the first satellite, where the access stratum context is used to establish a connection between the first satellite and the terminal device.

[0018] The above solution sends the context of the terminal device to the first satellite, so that the first satellite can quickly establish a connection with the terminal device based on the access layer context, thereby improving communication efficiency.

[0019] In a possible implementation method, the method further includes: sending indication information to the session management network element, where the indication information is used to trigger selection of a satellite-based user plane network element that provides services for the terminal device.

[0020] The above solution triggers the session management network element to provide services to the satellite user plane network element of the terminal device in an explicit manner, which helps to accurately notify the session management network element to provide services to the satellite user plane network element of the terminal device.

[0021] In a possible implementation method, the method also includes: receiving the storage and forwarding contract data of the terminal device from the unified data management network element, the storage and forwarding contract data is used to indicate that the terminal device has signed a contract for the storage and forwarding service; sending the indication information to the session management network element includes: sending the indication information to the session management network element according to the storage and forwarding contract data.

[0022] In one possible implementation method, the method further includes: receiving a session establishment request from the terminal device and a DNN requested by the terminal device, the session establishment request is used to request establishment of a session, and the data network corresponding to the DNN is used to provide on-board storage and forwarding services; sending indication information to the session management network element includes: sending the indication information to the session management network element according to the DNN.

[0023] In a possible implementation method, the communication plan is determined based on satellite coverage information, feeder link information, and communication requirements of the terminal device.

[0024] In a possible implementation method, the satellite coverage information includes a coverage time and a coverage area, and the satellite coverage information is used to indicate that the coverage area will be covered by a satellite within the coverage time.

[0025] In a possible implementation method, the satellite coverage information includes coverage time, coverage area and satellite identifier, and the satellite coverage information is used to indicate that the coverage area will be covered by the satellite indicated by the satellite identifier within the coverage time.

[0026] In a possible implementation method, the feeder link information includes an identifier of the satellite and an available time and / or an available area. The feeder link information is used to indicate that the satellite can establish a feeder link within the available time and / or available area.

[0027] In one possible implementation method, the communication requirements of the terminal device include but are not limited to at least one of the following information: the time when the terminal device uses the satellite communication service, the location where the terminal device uses the satellite communication service, the delay requirement of the terminal device's service, and the bandwidth requirement of the terminal device's service.

[0028] In a second aspect, embodiments of the present application provide a communication method that can be performed by a session management network element or a module (such as a chip) applied to the session management network element. The method includes: receiving session management subscription information for a first session of a terminal device from a unified data management network element, the session management subscription information including a DNN, the data network corresponding to the DNN being used to provide an onboard store-and-forward service; and selecting an onboard user plane network element based on the DNN.

[0029] In the above solution, the session management network element selects the satellite user plane network element that provides services to the terminal device based on the DNN, and the satellite user plane network element provides data forwarding services to the terminal device, which can achieve correct communication of the terminal device.

[0030] In one possible implementation method, the session management subscription information also includes a store-and-forward indication, which is used to indicate that the data network corresponding to the DNN is used to provide on-board store-and-forward services; selecting an on-board user plane network element based on the DNN includes: selecting an on-board user plane network element based on the DNN and the store-and-forward indication.

[0031] The above solution triggers the session management network element to provide services to the satellite user plane network element of the terminal device in an explicit manner, which helps to accurately notify the session management network element to provide services to the satellite user plane network element of the terminal device.

[0032] In one possible implementation method, the method also includes: receiving traffic description information from a ground application server; sending forwarding rules to a selected satellite user plane network element, wherein the forwarding rules are used by the satellite user plane network element to forward the uplink service flow that matches the traffic description information to the satellite application server.

[0033] The above solution determines the forwarding rules according to the traffic description information and sends the forwarding rules to the satellite user plane network element. The satellite user plane network element provides data forwarding services to the terminal device based on the forwarding rules, which can realize correct communication of the terminal device.

[0034] In a possible implementation method, the traffic description information includes a DNAI; the method further includes: selecting a satellite-borne user plane network element according to the DNAI.

[0035] In a third aspect, embodiments of the present application provide a communication method that can be executed by a satellite-based application server or a module (such as a chip) applied to the satellite-based application server. The method includes: receiving a downlink service flow from a terminal device on a ground-based application server; storing the downlink service flow; and sending the stored downlink service flow to the satellite-based user plane network element after receiving an uplink service flow from the terminal device or during the satellite communication time of the terminal device, where the satellite communication time indicates the time when the terminal device uses satellite communication.

[0036] In the above solution, in a scenario where the satellite cannot be connected to the terminal device and the core network at the same time, the onboard application server in the 3GPP external network stores and forwards the downlink service flow that needs to be sent to the terminal device, thereby achieving correct communication of the terminal device. In addition, since the 3GPP network does not need to store the downlink service flow, the pressure on the 3GPP network can be reduced.

[0037] In a possible implementation method, the method further includes: receiving satellite communication time of the terminal device.

[0038] In a possible implementation method, the satellite communication time information includes at least two of a start time, a communication duration, or an end time.

[0039] In a fourth aspect, embodiments of the present application provide a communication method that can be executed by an onboard application server or a module (such as a chip) applied to the onboard application server. The method includes: receiving an uplink service flow from a terminal device of an onboard user plane network element; storing the uplink service flow; and, upon successful establishment of a connection between the onboard application server and a ground application server, sending the stored uplink service flow to the ground application server.

[0040] In the above solution, in a scenario where the satellite cannot be connected to the terminal device and the core network at the same time, the onboard application server in the 3GPP external network stores and forwards the uplink service flow that needs to be sent to the terminal device, thereby achieving correct communication of the terminal device. In addition, since the 3GPP network does not need to store the uplink service flow, the pressure on the 3GPP network can be reduced.

[0041] In a possible implementation method, the method also includes: when the onboard application server successfully establishes a connection with the ground application server, receiving the downlink business flow of the terminal device from the ground application server; storing the downlink business flow; after receiving the uplink business flow from the terminal device or within the satellite communication time of the terminal device, sending the stored downlink business flow to the onboard user plane network element, the satellite communication time is used to indicate the time when the terminal device uses satellite communication.

[0042] In a possible implementation method, the method further includes: receiving satellite communication time of the terminal device.

[0043] In a possible implementation method, the satellite communication time information includes at least two of a start time, a communication duration, or an end time.

[0044] In a fifth aspect, embodiments of the present application provide a communication method, which can be performed by an onboard user plane network element or a module (such as a chip) applied to the onboard user plane network element. The method includes: receiving a forwarding rule from a session management network element, the forwarding rule being used by the onboard user plane network element to forward an uplink service flow of a terminal device to an onboard application server; receiving an uplink service flow from the terminal device; and sending the uplink service flow of the terminal device to the onboard application server according to the forwarding rule.

[0045] In the above solution, the satellite-borne user plane network element provides data forwarding services to the terminal device based on the forwarding rules, which can realize the correct communication of the terminal device.

[0046] In one possible implementation method, the forwarding rule is also used by the onboard user plane network element to send a downlink service flow to the terminal device; the method also includes: receiving the downlink service flow of the terminal device from the onboard application server; and sending the downlink service flow to the terminal device according to the forwarding rule.

[0047] In a sixth aspect, embodiments of the present application provide a communications device, which may be a mobility management network element or a chip for a mobility management network element. The device has the function of implementing any of the implementation methods of the first aspect described above. The function may be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

[0048] In a seventh aspect, embodiments of the present application provide a communications device, which may be a session management network element (SME) or a chip for a SME. The device has the functionality to implement any of the implementation methods of the second aspect described above. The functionality may be implemented via hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functionality.

[0049] In an eighth aspect, embodiments of the present application provide a communications device, which may be a satellite-based application server or a chip for a satellite-based application server. The device has the functionality to implement any of the implementation methods of the third and fourth aspects described above. This functionality may be implemented via hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functionality.

[0050] In a ninth aspect, an embodiment of the present application provides a communications device, which may be a satellite-based user plane network element or a chip for a satellite-based user plane network element. The device has the function of implementing any of the implementation methods of the fifth aspect described above. The function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

[0051] In a tenth aspect, an embodiment of the present application provides a communication device, comprising a processor coupled to a memory, the processor configured to call a program stored in the memory to execute any of the implementation methods described in aspects 1 to 5 above. The memory may be located within or outside the device, and the processor may be one or more.

[0052] In the eleventh aspect, an embodiment of the present application provides a communication device, comprising a processor and a memory; the memory is used to store computer instructions, and when the device is running, the processor executes the computer instructions stored in the memory to enable the device to execute any implementation method in the above-mentioned first to fifth aspects.

[0053] In the twelfth aspect, an embodiment of the present application provides a communication device, comprising a unit or means for executing each step of any implementation method in the above-mentioned first to fifth aspects.

[0054] In a thirteenth aspect, an embodiment of the present application provides a communication device, comprising a processor and an interface circuit, wherein the processor is configured to communicate with other devices via the interface circuit and execute any of the implementation methods described in the first to fifth aspects above. The processor comprises one or more.

[0055] In the fourteenth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, which, when run on a communication device, enables any implementation method in the above-mentioned first to fifth aspects to be executed.

[0056] In the fifteenth aspect, an embodiment of the present application further provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are run by a communication device, any implementation method in the above-mentioned first to fifth aspects is executed.

[0057] In the sixteenth aspect, an embodiment of the present application also provides a chip system, including: a processor, used to execute any implementation method in the above-mentioned first to fifth aspects.

[0058] In the seventeenth aspect, an embodiment of the present application further provides a communication system, comprising a session management network element, and a mobility management network element for executing any method of the first aspect; the session management network element is used to receive an identifier of the first satellite.

[0059] In the eighteenth aspect, an embodiment of the present application also provides a communication system, including a unified data management network element, and a session management network element for executing any method of the second aspect; the unified data management network element is used to send session management signing information of the first session of the terminal device to the session management network element.

[0060] In the nineteenth aspect, an embodiment of the present application also provides a communication system, including a ground application server and a satellite application server for executing any method of the third aspect; the ground application server is used to send the downlink service flow of the terminal device to the satellite application server.

[0061] In the twentieth aspect, an embodiment of the present application also provides a communication system, including a ground application server, and a satellite application server for executing any method of the fourth aspect; the ground application server is used to receive an uplink service flow from a terminal device of the satellite application server. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] Figure 1 is a schematic diagram of a 5G network architecture based on a service-oriented architecture;

[0063] Figure 2(a) is a schematic diagram of a satellite access scenario in which onboard access network equipment is deployed on a satellite;

[0064] Figure 2(b) is a schematic diagram of a satellite access scenario where onboard access network equipment and onboard UPF are deployed on a satellite;

[0065] Figure 3 is a schematic diagram of a scenario with discontinuous satellite coverage;

[0066] FIG4( a ) is a flow chart of a communication method provided in an embodiment of the present application;

[0067] FIG4( b ) is a flow chart of a communication method provided in an embodiment of the present application;

[0068] FIG4( c ) is a flow chart of a communication method provided in an embodiment of the present application;

[0069] FIG5 is an example diagram of satellite communications;

[0070] FIG6 is a flow chart of a communication method provided in an embodiment of the present application;

[0071] FIG7 is a schematic diagram of a communication device provided in an embodiment of the present application;

[0072] FIG8 is a schematic diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0073] Figure 1 is a schematic diagram of a 5G network architecture based on a service-oriented architecture. The 5G network architecture shown in Figure 1 includes a data network (DN) and a carrier network. The following briefly describes the functions of some of these network elements.

[0074] The operator network includes one or more of the following network elements: an authentication server function (AUSF) network element (not shown in the figure), a unified data management (UDM) network element, a unified data repository (UDR) network element, a network repository function (NRF) network element (not shown in the figure), a network exposure function (NEF) network element (not shown in the figure), an application function (AF) network element, a policy control function (PCF) network element, an access and mobility management function (AMF) network element, a session management function (SMF) network element, a user plane function (UPF) network element, and access network (AN) equipment (radio access network (RAN) equipment is used as an example in the figure). In the above-mentioned operator network, network elements or equipment other than access network equipment can be referred to as core network network elements or core network equipment.

[0075] Access network equipment includes wired access network equipment and wireless access network equipment. Among them, the wireless access network equipment can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation base station (next generation NodeB, gNB) in a 5G mobile communication system, a next-generation base station in a sixth-generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system, etc.; it can also be a module or unit that completes part of the functions of a base station, for example, it can be a centralized unit (CU) or a distributed unit (DU). The wireless access network equipment can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, etc. The embodiments of the present application do not limit the specific technology and specific equipment form adopted by the access network equipment.

[0076] Terminal devices that communicate with access network devices include terminals, user equipment (UE), mobile stations, mobile terminals, etc. The figure takes the terminal device as an example of UE. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver function, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home device, etc. The embodiments of this application do not limit the specific technology and specific device form adopted by the terminal device.

[0077] Access network equipment and terminal devices can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of access network equipment and terminal devices.

[0078] The mobility management network element is mainly used for the attachment, mobility management, and tracking area update (TAU) processes of terminal devices in mobile networks. The access management network element terminates the non-access stratum (NAS) message, completes registration management, connection management, reachability management, and mobility management, allocates the tracking area list (TA list), and transparently routes the session management (SM) message to the session management network element. In 5G, the mobility management network element can be an AMF network element. In future communications such as the 6th generation (6G), the mobility management network element can still be an AMF network element or have other names, which are not limited in this application.

[0079] The session management network element is a control plane network element provided by the operator network, which is responsible for managing the protocol data unit (PDU) session of the terminal device. The PDU session is a channel for transmitting PDUs, and the terminal device needs to transmit PDUs to each other with the DN through the PDU session. The SMF network element is responsible for establishing, maintaining and deleting PDU sessions. The session management network element includes session management (such as session establishment, modification and release, including tunnel maintenance between user plane network elements and access network equipment), selection and control of user plane network elements, service and session continuity (SSC) mode selection, roaming and other session-related functions. In 5G, the session management network element can be an SMF network element. In future communications such as 6G, the session management network element can still be an SMF network element, or have other names, which are not limited in this application.

[0080] The user plane network element is a gateway provided by the operator and serves as the gateway for communication between the operator network and the DN. The user plane network element includes user plane related functions such as data packet routing and transmission, packet detection, service usage reporting, quality of service (QoS) processing, lawful interception, uplink packet detection, downlink data packet storage, etc. In 5G, the user plane network element can be a UPF network element. In future communications such as 6G, the user plane network element can still be a UPF network element or have other names, which are not limited in this application.

[0081] The data management network element is a control plane network element provided by the operator, responsible for storing information such as the subscriber permanent identifier (SUPI), credentials, security context, and subscription data of subscribers in the operator network. The information stored by the data management network element can be used for authentication and authorization of terminal devices to access the operator network. Among them, the subscribers of the above-mentioned operator network can specifically be users who use the services provided by the operator network, such as users who use China Telecom's mobile phone SIM cards, or users who use China Mobile's mobile phone SIM cards, etc. The SUPI of the above-mentioned subscribers can be the number of the mobile phone SIM card, etc. The credentials and security context of the above-mentioned subscribers can be small files storing the encryption key of the mobile phone SIM card or information related to the encryption of the mobile phone SIM card, which are used for authentication and / or authorization. The above-mentioned security context can be data (cookie) or token stored on the user's local terminal (such as a mobile phone). The subscription data of the above-mentioned subscribers can be the supporting services of the mobile phone SIM card, such as the data package of the mobile phone SIM card or the network used. It should be noted that SUPI, credentials, security context, authentication data (cookie), and token are equivalent to authentication and authorization-related information. In this application document, for the sake of convenience of description, no distinction or restriction is made. Unless otherwise specified, the embodiments of this application will be described using security context as an example, but the embodiments of this application are also applicable to authentication and / or authorization information expressed in other ways. In 5G, the data management network element can be a UDM network element. In future communications such as 6G, the data management network element can still be a UDM network element, or have other names, which are not limited in this application.

[0082] The unified database network element is a control plane network element provided by the operator, which includes the access function of executing contract data, policy data, application data, and other types of data. In 5G, the unified database network element can be a UDR network element. In future communications such as 6G, the unified database network element can still be a UDR network element or have other names, which are not limited in this application.

[0083] The network open network element is a control plane network element provided by the operator. The network open network element opens the external interface of the operator network to a third party in a secure manner. When the session management network element needs to communicate with the network element of a third party, the network open network element can serve as a relay for the communication between the session management network element and the network element of the third party. When the network open network element acts as a relay, it can translate the identification information of the subscriber, as well as the identification information of the third-party network element. For example, when the network open network element sends the SUPI of the subscriber from the operator network to a third party, the SUPI can be translated into its corresponding external identity. Conversely, when the network open network element sends the external ID (the network element ID of the third party) to the operator network, it can be translated into SUPI. In 5G, the network open network element can be a NEF network element. In future communications such as 6G, the network open network element can still be a NEF network element, or have other names, which are not limited in this application.

[0084] The application function network element is used to convey the application side's requirements to the network side, such as quality of service (QoS) requirements or user status event subscriptions. The application function network element can be a third-party functional entity or an application server deployed by the operator. In 5G, the application function network element can be an AF network element. In future communications such as 6G, the application function network element can still be an AF network element or have other names, which are not limited in this application.

[0085] The policy control network element is a control plane function provided by the operator, including user subscription data management, policy control, charging policy control, QoS control, etc. In 5G, the policy control network element can be a PCF network element. In future communications such as 6G, the policy control network element can still be a PCF network element or have other names, which are not limited in this application.

[0086] The network storage function network element can be used to provide network element discovery function, and provide network element information corresponding to the network element type based on the request of other network elements. The network storage function network element also provides network element management services, such as network element registration, update, deregistration, and network element status subscription and push. In 5G, the network storage function network element can be an NRF network element. In future communications such as 6G, the network storage function network element can still be an NRF network element, or have other names, which are not limited in this application.

[0087] A DN is a network located outside of a carrier network. A carrier network can connect to multiple DNs, and a variety of services can be deployed on the DN, providing data and / or voice services to terminal devices. For example, a DN is the private network of a smart factory. Sensors installed in the workshop can be terminal devices. The DN houses a sensor control server, which provides services to the sensors. Sensors can communicate with the control server, receive instructions from the control server, and transmit collected sensor data to the control server based on the instructions. Another example is a DN that is a company's internal office network. An employee's mobile phone or computer can be a terminal device, allowing them to access information and data resources on the company's internal office network.

[0088] In Figure 1, Npcf, Nudr, Nudm, Naf, Namf, and Nsmf are service-oriented interfaces provided by the PCF, UDR, UDM, AF, AMF, and SMF network elements, respectively, for invoking corresponding service-oriented operations. N1, N2, N3, N4, and N6 are interface serial numbers, and their meanings are as follows:

[0089] 1) N1: The interface between the AMF network element and the UE, which can be used to deliver non-access stratum (NAS) signaling (such as QoS rules from the AMF network element) to the UE.

[0090] 2) N2: The interface between the AMF network element and the radio access network equipment, which can be used to transmit radio bearer control information from the core network side to the radio access network equipment.

[0091] 3) N3: The interface between the wireless access network equipment and the UPF network element, mainly used to transmit uplink user plane data and / or downlink user plane data between the wireless access network equipment and the UPF network element.

[0092] 4) N4: The interface between the SMF network element and the UPF network element, which can be used to transmit information between the control plane and the user plane, including controlling the issuance of forwarding rules, QoS rules, traffic statistics rules, etc. for the user plane and reporting information on the user plane.

[0093] 5) N6: The interface between the UPF network element and the DN, used to transmit uplink user data flow and / or downlink user data flow between the UPF network element and the DN.

[0094] It is understood that the above-mentioned network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the above-mentioned network element or function can be implemented by a single device, or by multiple devices, or can be a functional module within a single device, and this is not specifically limited in the embodiments of the present application.

[0095] In the embodiments of the present application, the PCF network element, SMF network element, AMF network element, and UDM network element are described as an example of a policy control network element, a session management network element, a mobility management network element, and a unified data management network element, and the PCF network element, SMF network element, AMF network element, and UDM network element are abbreviated as PCF, SMF, AMF, and UDM, respectively.

[0096] To facilitate understanding of the content of this application, the nouns or terms involved in this application are introduced below.

[0097] 1. The 5th generation system (5GS)

[0098] 5GS boasts high bandwidth, high reliability, and low latency. With the development of satellite communication technology, the bandwidth capacity of communication satellites has increased significantly, while costs have decreased. The integration of satellite networks with 5G networks is emerging, and their powerful coverage capabilities can help 5G networks reach remote areas with sparse populations, as well as areas such as oceans and isolated islands that are difficult for terrestrial networks to reach.

[0099] 2. Integration of Satellite Communications and 5GS

[0100] 3GPP considers using satellites as radio frequency modules of access network equipment to provide transparent forwarding capabilities. In addition, 3GPP also considers satellites to support data processing, that is, considering satellites to provide non-transparent forwarding capabilities (or called renewable capabilities). Specifically, it considers deploying access network equipment on satellites, or deploying access network equipment and UPF on satellites. This application assumes that satellites have renewable capabilities, and considers deploying onboard access network equipment on satellites, or deploying onboard access network equipment and onboard UPF at the same time. Terminal equipment can access the 5G core network through onboard access network equipment. Among them, onboard access network equipment is also called onboard RAN, access network equipment on satellites, access network equipment deployed on satellites, etc. For the sake of convenience, this application uniformly refers to them as onboard access network equipment. Onboard UPF is also called UPF on satellites, UPF deployed on satellites, etc. For the sake of convenience, this application uniformly refers to them as onboard UPF.

[0101] Figure 2(a) shows a schematic diagram of a satellite access scenario with onboard access network equipment deployed on a satellite. The access network equipment, also called onboard access network equipment, is deployed on the satellite and has data processing and storage and forwarding capabilities.

[0102] Figure 2(b) illustrates a satellite access scenario in which onboard access network equipment and an onboard UPF are deployed on a satellite. The onboard access network equipment and the UPF are deployed on a satellite. The onboard access network equipment, also known as the onboard access network equipment, and the UPF, also known as the onboard UPF, have data processing and storage and forwarding capabilities, while the onboard UPF has data storage and forwarding capabilities.

[0103] 3. Discontinuous Satellite Coverage

[0104] Since non-geosynchronous satellites such as MEO and LEO move relative to the ground, a single satellite may not yet have multiple satellites networked based on inter-satellite links, or may have a constellation with a few sparse inter-satellite links. When terminal devices use satellite access, discontinuous coverage will occur.

[0105] The discontinuous coverage scenario currently being discussed in 3GPP assumes that when a terminal device is covered by a satellite, the satellite can also establish a connection (i.e., a feeder link) with a ground gateway. However, in reality, a terminal device may be located over the ocean, on an isolated island, or in polar regions. When the terminal device is covered by a satellite, the satellite cannot establish a connection with the ground gateway. Existing technologies cannot support communication in this scenario. Figure 3 illustrates a discontinuous satellite coverage scenario. At time T1, the satellite is located over the ocean and can cover the terminal device, but the satellite cannot establish a connection with the 5GC on land through the ground gateway. At time T2, the satellite moves over land and can access the 5GC through the ground gateway, but the satellite cannot communicate with the terminal device in the ocean. At time T3, the satellite again covers the terminal device over the ocean. The satellite can now communicate with the terminal device, but the satellite cannot establish a connection with the 5GC on land through the ground gateway. Therefore, in this scenario, the satellite cannot communicate with the terminal device and 5GC at the same time. If the terminal device is to send and receive data, the satellite needs to support the store-and-forward function. For example, an access network device is deployed on the satellite and the access network device supports caching of uplink and downlink data, or an access network device and UPF are deployed and the UPF supports caching of uplink and downlink data to achieve tolerance for delays and interruptions.

[0106] Figure 4(a) is a flow chart of a communication method provided in an embodiment of the present application. The method is applied to scenarios where satellite coverage is discontinuous and the satellite cannot establish a connection with the terminal device and 5GC at the same time. The method includes the following steps:

[0107] In step 401a, the AMF determines a first satellite that is expected to provide communication services to the terminal device based on the communication plan of the terminal device.

[0108] In one implementation method, the communication plan can be determined by negotiation between the terminal device and the ground application server. For example, when the terminal device is on land, it uses the ground network to register and establish a PDU session. Alternatively, if a satellite can simultaneously establish a connection with the terminal device and 5GC, the terminal device can also use the satellite to register and establish a PDU session when on land. After completing registration and establishing a PDU session, the terminal device negotiates with the ground application server to obtain a communication plan. Exemplarily, the communication plan is determined based on satellite coverage information, feeder link information, and the communication needs of the terminal device.

[0109] The satellite coverage information may be used to indicate satellite coverage. For example, when the satellite coverage information includes coverage time and coverage area, the satellite coverage information may be used to indicate that the coverage area will be covered by a satellite during the coverage time. For another example, when the satellite coverage information includes coverage time, coverage area, and satellite identifier, the satellite coverage information may be used to indicate that the coverage area will be covered by the satellite indicated by the satellite identifier during the coverage time.

[0110] The feeder link information may be used to indicate the availability of the satellite's feeder link. For example, when the feeder link information includes a satellite identifier and an available time and / or available area, the feeder link information indicates that the satellite can establish a feeder link within the available time and / or available area.

[0111] Among them, the communication requirements of the terminal device include but are not limited to at least one of the following information: the time when the terminal device uses the satellite communication service, the location where the terminal device uses the satellite communication service, the delay requirement of the terminal device's service, and the bandwidth requirement of the terminal device's service.

[0112] The communication plan may be used to indicate how the terminal device obtains satellite communication services.

[0113] In one implementation, the communication plan includes an identifier of at least one satellite intended for use. Exemplarily, the communication plan also includes communication time information corresponding to each of the at least one satellite intended for use. The communication time information corresponding to each satellite intended for use indicates the time at which the terminal device intends to communicate using the satellite. For example, if the at least one satellite intended for use includes a first satellite, the communication time information corresponding to the first satellite indicates the time at which the terminal device intends to communicate using the first satellite.

[0114] In another implementation method, the communication plan includes at least two sets of service information, including a first set of service information and a second set of service information. The first set of service information includes first communication location information and first communication time information. The first communication location information indicates a first location at which the terminal device is expected to use satellite communication, and the first communication time information indicates a first time at which the terminal device is expected to use satellite communication at the first location. The second set of service information includes second communication location information and second communication time information. The second communication location information indicates a second location at which the terminal device is expected to use satellite communication, and the second communication time information indicates a second time at which the terminal device is expected to use satellite communication at the second location, the second time being different from the first time. The first and second locations may be the same or different. Exemplarily, the first communication time information includes at least two of a first start time, a first communication duration, or a first end time. The second communication time information includes at least two of a second start time, a second communication duration, or a second end time. Exemplarily, the two sets of service information also include third and fourth sets of service information, etc., the specific meanings of which are similar to those of the first and second sets of service information and are not further described. For example, a communication plan includes five sets of service information. The i-th set of service information includes communication location information i and communication time information i. Communication location information i indicates the location i at which the terminal device is expected to use satellite communication. Communication time information i indicates the time i at which the terminal device is expected to use satellite communication at location i, where i = 1, 2, 3, 4, 5. Location 1, location 2, location 3, location 4, and location 5 are consecutive locations on the movement trajectory, or two or more adjacent locations may be the same location. Time 1, time 2, time 3, time 4, and time 5 are continuous in time sequence.

[0115] If the communication plan includes at least two sets of service information, the identities of at least two satellites expected to be used can be determined based on the two sets of service information.

[0116] Among them, the embodiments of the present application do not limit the specific implementation method of determining the communication plan based on satellite coverage information, feeder link information and communication requirements of the terminal device.

[0117] For example, the information of the candidate satellite can be determined first based on the communication needs of the terminal device and the satellite coverage information, and then the communication plan can be determined based on the information of the candidate satellite and the feeder link information, where the information of the candidate satellite includes at least one of the following information: the identification of the candidate satellite, the coverage time of the candidate satellite, and the coverage area of ​​the candidate satellite.

[0118] For another example, the information of the candidate satellite can be determined based on the feeder link information and the satellite coverage information, and then the communication plan can be determined based on the information of the candidate satellite and the communication needs of the terminal device, wherein the information of the candidate satellite includes at least one of the following information: the identification of the candidate satellite, the coverage time of the candidate satellite, and the coverage area of ​​the candidate satellite.

[0119] In the embodiment of the present application, the service information may also be referred to as expected satellite usage information, expected satellite demand information, or expected communication demand information, etc.

[0120] In the embodiment of the present application, the satellite identifier may be the satellite ID or the data network access identifier (DNAI) corresponding to the satellite.

[0121] In the embodiment of the present application, the communication plan is also referred to as a connection plan, a contact plan, or a delay interruption tolerant communication plan.

[0122] In one implementation method, the AMF may receive the communication plan of the terminal device from the terminal device, a ground application server, or a network management device, wherein the network management device may be an operation, administration, and maintenance (OAM) device.

[0123] Step 402a: The AMF sends the identifier of the first satellite to the SMF.

[0124] Accordingly, the SMF receives the identification of the first satellite.

[0125] Furthermore, after receiving the identifier of the first satellite, the SMF can select the onboard UPF on the satellite according to the identifier of the first satellite.

[0126] In the above solution, in the scenario where the satellite cannot be connected to the terminal device and the core network at the same time, the AMF selects the first satellite to provide services for the terminal device according to the communication plan of the terminal device, and sends the identifier of the first satellite to the SMF. The SMF selects the onboard UPF to provide services for the terminal device based on the identifier of the first satellite, thereby realizing correct communication of the terminal device.

[0127] In one implementation method, the AMF may further send an indication message to the SMF, where the indication message is used to trigger the selection of the satellite-borne UPF that provides services to the terminal device. Therefore, after the SMF receives the indication message, it triggers the SMF to select the satellite-borne UPF according to the identifier of the first satellite.

[0128] In one implementation method, the SMF also receives session management subscription information of the first session of the terminal device from the UDM, where the session management subscription information includes a DNN. The data network corresponding to the DNN is used to provide on-board storage and forwarding services. The SMF then selects the onboard UPF based on the identifiers of the DNN and the first satellite. Exemplarily, the session management subscription information also includes a storage and forwarding indication, which is used to indicate that the data network corresponding to the DNN is used to provide on-board storage and forwarding services. The storage and forwarding indication is used to trigger the SMF to select the onboard UPF. Specifically, the SMF is triggered to select the onboard UPF based on the identifiers of the DNN and the first satellite.

[0129] In one implementation method, the SMF also receives traffic description information from the ground application server, and then the SMF generates a forwarding rule and sends the forwarding rule to the onboard UPF. The forwarding rule is used by the onboard UPF to forward the uplink service flow that matches the traffic description information to the onboard application server. Exemplarily, the traffic description information includes a DNAI, and the SMF can also refer to the DNAI when selecting the onboard UPF. For example, the SMF selects the onboard UPF based on the identifier and DNAI of the first satellite, or selects the onboard UPF based on the identifier, DNAI and DNN of the first satellite, and so on.

[0130] In one implementation method, the AMF receives the store-and-forward contract data of the terminal device from the UDM, which is used to indicate that the terminal device has subscribed to the store-and-forward service. The AMF then sends the above-mentioned indication information to the SMF based on the store-and-forward contract data. That is, after the AMF determines that the terminal device has subscribed to the store-and-forward service, it sends the indication information to the SMF to trigger the selection of the onboard UPF to provide services for the terminal device.

[0131] In another implementation method, the AMF receives a session establishment request from a terminal device and a data network name (DNN) DNN requested by the terminal device. The session establishment request is used to request the establishment of a session. The data network corresponding to the DNN is used to provide on-board storage and forwarding services. The AMF then sends indication information to the SMF based on the DNN. That is, when the AMF determines that the session requested by the terminal device requires the use of the on-board storage and forwarding service, it sends the above-mentioned indication information to the SMF to trigger the selection of the onboard UPF that provides services for the terminal device.

[0132] In one implementation, the AMF may also send the access stratum context of the terminal device to the first satellite. This access stratum context is used to establish a connection between the first satellite and the terminal device. This allows the first satellite to quickly establish a connection with the terminal device based on the access stratum context, improving communication efficiency.

[0133] Figure 4(b) is a flow chart of a communication method provided in an embodiment of the present application. The method is applied to scenarios where satellite coverage is discontinuous and the satellite cannot establish a connection with the terminal device and 5GC at the same time. The method includes the following steps:

[0134] Step 401b: The ground application server sends the downlink service flow of the terminal device to the satellite application server.

[0135] The downlink service flow is also called downlink service data or downlink data.

[0136] Figure 5 is an example diagram of satellite communication. A satellite-borne application server is deployed on the satellite, which may be, for example, an edge application server (EAS), an N6 local area network service function entity, or other service function entity. The satellite-borne application server may be connected to the satellite-borne UPF through the N6 interface. The ground application server is connected to the ground UPF of the ground 5GC through the N6 interface. The ground application server and the satellite-borne application server are interconnected through a data network external to 3GPP, wherein the data network after the N6 interface on the satellite and the data network after the ground N6 interface are interconnected when the satellite and the ground gateway can establish a connection. Due to the movement of the satellite, the satellite cannot establish a connection with the terminal device and the ground 5GC at the same time, so the satellite is required to store and forward the data. In an embodiment of the present application, the communication data between the terminal device and the ground application server is stored and forwarded by the satellite-borne application server on the satellite.

[0137] The onboard application server is also referred to as an onboard application server, an application server on a satellite, or an onboard AF, etc. The terrestrial application server is also referred to as an application server, a terrestrial AF, or an AF, etc.

[0138] Step 402b: The onboard application server stores the downlink service flow.

[0139] Step 403b: After receiving the uplink service flow from the terminal device or within the satellite communication time of the terminal device, the onboard application server sends the stored downlink service flow to the onboard UPF.

[0140] Among them, the onboard application server receives the uplink business flow from the terminal device, indicating that a communication connection is established between the terminal device and the satellite. Therefore, after receiving the uplink business flow from the terminal device, the onboard application server can send the stored downlink business flow to the onboard UPF, and then the onboard UPF sends the downlink business flow to the terminal device.

[0141] Among them, the satellite communication time of the terminal device can be understood as the time when the terminal device can establish communication with the satellite. During this satellite communication time, the onboard application server sends the stored downlink business flow to the onboard UPF, and then the onboard UPF sends the downlink business flow to the terminal device.

[0142] Specifically, the satellite communication time may be used to indicate the time when the terminal device communicates with the satellite where the satellite-borne application server is located. Exemplarily, the satellite communication time may include at least two of the start time, the communication duration, or the end time.

[0143] It should be noted that the onboard UPF can send downlink service flows to the terminal device according to the forwarding rules. For example, the onboard UPF receives the forwarding rules from the SMF, and the forwarding rules are used by the onboard UPF to send the downlink service flows of the terminal device to the terminal device.

[0144] In the above solution, in a scenario where the satellite cannot be connected to the terminal device and the core network at the same time, the onboard application server in the 3GPP external network stores and forwards the downlink service flow that needs to be sent to the terminal device, thereby achieving correct communication of the terminal device. In addition, since the 3GPP network does not need to store the downlink service flow, the pressure on the 3GPP network can be reduced.

[0145] Figure 4(c) is a flow chart of a communication method provided in an embodiment of the present application. This method is applied to scenarios where satellite coverage is discontinuous and the satellite cannot establish a connection with the terminal device and 5GC at the same time. The method includes the following steps:

[0146] In step 401c, the onboard UPF sends the uplink service flow of the terminal device to the onboard application server. Correspondingly, the onboard application server receives the uplink service flow of the terminal device.

[0147] The uplink service flow is also called uplink service data or uplink data.

[0148] In one implementation method, the onboard application server receives the uplink service flow of the terminal device, which can be specifically: the terminal device sends the uplink service flow of the terminal device to the onboard access network device, the onboard access network device sends the uplink service flow to the onboard UPF, and then the onboard UPF sends the uplink service flow to the onboard application server.

[0149] In one implementation method, before receiving the uplink service flow of the terminal device, the onboard UPF can receive a forwarding rule from the SMF. The forwarding rule is used by the onboard UPF to send the uplink service flow of the terminal device to the onboard application server. After receiving the uplink service flow, the onboard UPF sends the uplink service flow to the onboard application server according to the forwarding rule.

[0150] Step 402c: The onboard application server stores the uplink service flow.

[0151] Step 403c: When the satellite-borne application server successfully establishes a connection with the ground application server, the satellite-borne application server sends the stored uplink service flow to the ground application server. Correspondingly, the ground application server receives the uplink service flow.

[0152] In the above method, in a scenario where the satellite cannot be connected to the terminal device and the core network at the same time, the onboard application server in the 3GPP external network stores and forwards the uplink service flow to be sent to the terminal device, thereby achieving normal communication of the terminal device. In addition, since the 3GPP network does not need to store the uplink service flow, the pressure on the 3GPP network is greatly reduced.

[0153] It should be noted that any two or three of the above embodiments in FIG. 4( a ) to FIG. 4 ( c ) can be implemented in combination with each other, and this application does not limit this.

[0154] FIG6 is a flow chart of a communication method provided by an embodiment of the present application. The embodiment of FIG6 is a specific example of combining the embodiments of FIG4(a) to FIG4(c) above. In the implementation of FIG6, a base station and a UE are used as an example of an access network device and a terminal device, respectively. The method includes the following steps:

[0155] Phase 1: The UE accesses the 5GC using base station 1 on land, completes registration and session establishment, and the UE and AF complete the negotiation of the communication plan and send the communication plan to the 5GC.

[0156] This phase 1 involves the following steps 601 to 605 .

[0157] Step 601: The UE and the AF complete the negotiation of the communication plan.

[0158] The AF here refers to a third-party application server on the ground, which can be called a ground application server.

[0159] The base station 1 shown in the figure can be a ground base station or a base station on a satellite.

[0160] Regarding the meaning and implementation method of the communication plan, reference may be made to the description of the aforementioned embodiment.

[0161] Step 602: AMF obtains the communication plan.

[0162] In one implementation method, the UE sends a communication plan to the AMF. Optionally, the UE also sends the identifier of the UE corresponding to the communication plan to the AMF. The UE may be the UE that negotiates the communication plan with the AF or another UE. That is, the aforementioned UE can negotiate a communication plan for itself or for one or more other UEs.

[0163] In another implementation method, the AF sends the communication plan to the AMF. Specifically, the AF can send the communication plan directly to the AMF, or the AF can send the communication plan to the PCF and then the PCF sends the communication plan to the AMF, or the AF can send the communication plan to the AMF through the NEF and PCF. The AF also sends the UE identifier to the AMF. The UE can be the UE that negotiates the communication plan with the AF or another UE. That is, the aforementioned UE can negotiate the communication plan for itself or for other UEs. In addition, when the AF sends the communication plan to the AMF, it can also send a store-and-forward requirement indication to the AMF to indicate that the UE corresponding to the communication plan has a store-and-forward requirement.

[0164] In another implementation method, the AMF can obtain satellite coverage information, feeder link information and UE communication requirements from the OAM device, UE or AF, and determine the communication plan based on the satellite coverage information, feeder link information and UE communication requirements.

[0165] In another implementation method, the AMF obtains the communication plan from the OAM system.

[0166] Step 603: AMF determines to provide a store-and-forward service for the terminal device.

[0167] In one implementation method, when the UE registers, the AMF obtains the UE's store-and-forward contract information from the UDM, and the AMF determines to provide the store-and-forward service for the terminal device based on the store-and-forward contract information.

[0168] In another implementation method, when the UE establishes a PDU session, the SMF obtains the session management contract information from the UDM, and the session management contract information includes a store-and-forward indication. The SMF sends the session management contract information to the AMF, and the AMF stores the session management contract information in the session context of the UE. The AMF determines to provide store-and-forward service for the terminal device based on the store-and-forward indication in the session management contract information.

[0169] Step 604: SMF obtains traffic description information.

[0170] The traffic description information may include the IP address of the AF, the port number of the AF, and the protocol number. Exemplarily, the traffic description information also includes the IP address of the UE and the port number of the UE.

[0171] Alternatively, the traffic description information may include an application identifier.

[0172] In one implementation, the SMF can obtain traffic description information from the AF. For example, the AF sends the traffic description information to the NEF, the NEF sends the traffic description information to the PCF, and then the PCF sends the traffic description information to the SMF. Another example is that the AF sends the traffic description information to the PCF, and then the PCF sends the traffic description information to the SMF.

[0173] In a specific implementation, the AF can send other information to the SMF while sending traffic description information to the SMF. The following describes different situations.

[0174] In scenario 1, the AF sends the UE's identifier, DNAI, and traffic description information to the PCF. The PCF determines the SMF corresponding to the UE's identifier, and then sends the DNAI and traffic description information to the SMF. The SMF determines the packet detection rule (PDR) based on the traffic description information, and determines the forwarding action rule (FAR) based on the DNAI, and then sends the N4 rule to the UPF. The N4 rule includes the PDR and FAR. The PDR is used to identify the service flow, and the FAR indicates how to handle the service flow, such as discarding or forwarding.

[0175] In scenario 2, the AF sends the UE's identifier, DNAI, traffic description information, and N6 traffic routing request to the PCF. The PCF maps the N6 traffic routing request to a traffic steering path (TSP) ID and determines the SMF corresponding to the UE's identifier. The PCF then sends the DNAI, traffic description information, and TSP ID to the SMF. The SMF determines the PDR based on the traffic description information and the FAR based on the TSP ID and DNAI. For example, the FAR includes the forwarding policy ID corresponding to the TSP ID. The SMF then sends the N4 rule to the UPF. The N4 rule includes the PDR and FAR. The PDR is used to identify the service flow, and the FAR indicates how to handle the service flow, such as discarding or forwarding.

[0176] Scenario 3: AF sends the UE's identifier, DNAI, traffic description information, and service function chain (SFC) ID to PCF. PCF maps the SFC ID to an uplink TSP ID and a downlink TSP ID, and determines the SMF corresponding to the UE's identifier. Then, it sends DNAI, traffic description information, uplink TSP ID, and downlink TSP ID to SMF. SMF determines the PDR based on the traffic description information, and determines the FAR based on the DNAI, uplink TSP ID, and downlink TSP ID. For example, the FAR includes a forwarding policy ID corresponding to the uplink TSP ID or downlink TSP ID. Then, SMF sends the N4 rule to UPF. The N4 rule includes the PDR and FAR. The PDR is used to identify the service flow, and the FAR indicates how to handle the service flow, such as discarding or forwarding.

[0177] For scenarios 1 to 3 above, in one implementation method, the source address in the uplink PDR is the UE's IP address, and the destination address is a wildcard. The source address in the downlink PDR is a wildcard, and the destination address is the UE's IP address. In another implementation method, the source address in the uplink PDR is the UE's IP address, and the destination address is the address in the traffic description information. The source address in the downlink PDR is the address in the traffic description information, and the destination address is the UE's IP address. In another implementation method, the uplink PDR contains an application identifier.

[0178] For the specific content of the N4 rule, please refer to the description in the aforementioned 604.

[0179] It should be noted that the embodiments of the present application are described using the N4 rule as an example. The N4 rule may also be called a forwarding rule, for example, without limitation.

[0180] Step 605: AMF obtains the access layer context of the UE from base station 1.

[0181] The AMF may also associate the UE's access layer context with the UE's identity.

[0182] In one implementation method, the AMF obtains and stores the access stratum context of the UE from base station 1 based on the identification or communication location information of the satellite in the communication plan. For example, if the AMF determines that the UE is about to use satellite communication services based on the identification or communication location information of the satellite in the communication plan, the AMF obtains and stores the access stratum context of the UE from base station 1. This allows the AMF to provide the satellite with the access stratum context of the UE when the UE uses the satellite communication services, thereby enabling a rapid connection between the satellite and the UE.

[0183] In another implementation method, after determining to provide storage and forwarding services for the terminal device, the AMF obtains the access layer context of the UE from base station 1 and stores it, so that when the UE uses the satellite's communication service, the satellite can provide the UE's access layer context to quickly establish a connection between the satellite and the UE.

[0184] Phase 2: The UE moves, for example, enters the RRC inactive state, enters areas such as the ocean or remote areas where satellites cannot establish feeds, and Satellite 1 can cover the UE's location. There is no feed link between Satellite 1 and the terrestrial 5GC. The 5GC waits to establish a feed link with Satellite 1 based on information such as the communication plan, completes the configuration related to enabling on-board storage and forwarding, and may store downlink data that the ground data network needs to send to the UE.

[0185] This phase 2 involves the following steps 606 to 611 .

[0186] In step 606, the AMF waits for establishing a feeder link with the satellite to be used according to the communication plan.

[0187] In one implementation method, when the communication plan includes the identification of one or more satellites to be used, the AMF waits in sequence to establish a feeder link with the one or more satellites to be used.

[0188] In another implementation method, when the communication plan includes one or more groups of service information, the AMF determines one or more satellites to be used based on the one or more groups of service information and satellite ephemeris information, and then waits in sequence to establish a feeder link with the one or more satellites to be used.

[0189] Among them, if a feed link is established between the AMF and the onboard base station on the satellite, an N2 connection can be further established with the onboard base station.

[0190] In one implementation method, after the AMF determines to provide a store-and-forward service for the UE, it determines to establish a feeder link with the satellite to be used.

[0191] Step 607: AMF sends the UE's access layer context to the onboard base station on satellite 1.

[0192] At a certain moment, AMF establishes a feeder link with satellite 1, and an N2 connection is established between the onboard base station on satellite 1 and AMF. AMF obtains the identifier of the onboard base station on satellite 1 according to the identifier mapping of satellite 1, and sends the access layer context of the UE stored in AMF to the onboard base station.

[0193] In one implementation method, when the communication plan includes the communication time of the UE, the AMF can determine the timing of sending the access layer context of the UE to the onboard base station on satellite 1 based on the communication time. For example, while satellite 1 is flying in the air, it may establish a feeder link with the ground AMF multiple times. However, the AMF does not send the access layer context of the UE to the onboard base station of the satellite 1 every time a feeder link is established with the onboard base station of the satellite 1. Instead, after the AMF establishes a feeder link with the onboard base station of the satellite 1, if it is determined that satellite 1 will cover the UE within the communication time of the UE, the AMF sends the access layer context of the UF to the onboard base station on satellite 1. This method can reduce the number of times the AMF sends the access layer context of the UE and save signaling overhead.

[0194] Step 608: AMF sends a store-and-forward indication, the identifier of the session management context, and the identification information of satellite 1 to SMF.

[0195] Furthermore, the AMF can determine the SMF providing services for the UE based on the UE identifier.

[0196] Step 609: The SMF determines the onboard UPF on satellite 1 that provides services for the UE.

[0197] Specifically, the SMF may determine, based on the store-and-forward indication, the selection and insertion of the onboard UPF on satellite 1, and determine the onboard UPF corresponding to the DNAI on satellite 1. The SMF may obtain the DNAI from the AF, or determine the DNAI based on identification information of satellite 1.

[0198] The onboard UPF may be an uplink classifier (UL CL), a local PDU session anchor (L-PSA), or a combined functional unit of UL CL and L-PSA.

[0199] Step 610: The SMF sends the N4 rule to the onboard UPF.

[0200] The N4 rule can be used to trigger the UPF to forward the UE's uplink service flow to the onboard application server for storage, and to send the stored downlink service flow to the UE. The onboard application server can be an edge application server (EAS) deployed on satellite 1 or other service function entity (such as an N6 local area network service function entity). The onboard application server can communicate with the ground application server (i.e., AF) via a non-3GPP network.

[0201] Step 611: SMF sends instruction information to AF.

[0202] The indication information may be used to indicate the onboard application server that has been deployed on the satellite 1. For example, the indication information may be a DNAI corresponding to the onboard application server that has been deployed.

[0203] Furthermore, after receiving the indication information, if there is downlink data to be sent to the terminal device, the AF can send the downlink data to the onboard application server through a network outside the 3GPP network, and the onboard application server stores the downlink data.

[0204] Phase 3: The UE accesses the satellite 1 selected in Phase 2 in a remote area or ocean. At this time, the UE may send uplink data to the satellite for storage and / or receive downlink data stored on the satellite.

[0205] This stage involves the following steps 612 to 615.

[0206] Step 612: Satellite 1 moves, the feeder link is disconnected, and the satellite base station sends an N2 release or suspension request to the AMF.

[0207] Furthermore, the AMF can trigger the SMF to release or suspend the N9 resources of the satellite UPF and the ground PSA UPF. The AMF determines to provide (or deploy) satellite storage and forwarding services for the UE without releasing the UE context.

[0208] Step 613: The satellite-borne base station pages the UE and establishes an RRC connection with the UE.

[0209] After establishing an RRC connection with the UE, the satellite-borne base station sends downlink data to the UE.

[0210] Specifically, the onboard application server sends the cached downlink data of the UE to the onboard UPF, and the onboard UPF sends the downlink data to the onboard base station. The onboard base station then pages the UE and sends the downlink data to the UE after establishing a connection with the UE.

[0211] In another implementation method, the UE may actively establish an RRC connection with the onboard base station of satellite 1 based on the communication plan.

[0212] Step 614: The UE sends a registration update message to the satellite-borne base station.

[0213] The registration update message may include a new communication plan, and the new communication plan may be used to indicate an updated manner of providing satellite communication services to the terminal device.

[0214] This step is optional. When the UE updates the communication plan, it can send a new communication plan to the satellite base station by initiating a registration update process. The specific implementation method of the new communication plan is similar to the implementation method of the communication plan in the embodiment of Figure 4(a) above, and will not be repeated here.

[0215] Step 615: The satellite-borne base station stores the registration update message.

[0216] After the UE establishes an RRC connection with the onboard base station of satellite 1, the UE can also send uplink data to the onboard base station, and then the onboard base station sends the uplink data to the onboard application server through the onboard UPF for storage.

[0217] Phase 4: Satellite 1 re-establishes feeding. At this time, the uplink data stored on Satellite 1 is sent to the terrestrial data network, or downlink data to be sent to the UE is received from the terrestrial data network.

[0218] This stage involves the following steps 616 .

[0219] Step 616: After satellite 1 establishes power feeding, the onboard base station on satellite 1 sends a registration update message to the AMF.

[0220] The AMF can select a satellite that provides communication services for the UE based on the new communication plan. The specific implementation process is similar to the above process and will not be repeated here.

[0221] The onboard application server sends the stored uplink data to the AF.

[0222] It should be noted that in the next satellite selection process of AMF, satellite 1 may still be selected to provide communication services for the UE, or other satellites, such as satellite 2, may be selected to provide communication services for the UE.

[0223] In scenarios where the satellite cannot simultaneously connect to both the terminal device and the core network, the onboard application server in the 3GPP external network stores and forwards the uplink / downlink traffic flows destined for the terminal device. This ensures proper communication for the terminal device and reduces pressure on the 3GPP network by eliminating the need for the 3GPP network to store these traffic flows. Furthermore, this solution can select communication plans for multiple UEs and send them to the core network, effectively completing onboard configuration.

[0224] It is understandable that, in order to implement the functions in the above embodiments, the mobility management network element, session management network element, onboard application server, or onboard user plane network element includes hardware structures and / or software modules corresponding to executing each function. Those skilled in the art should readily appreciate that, in combination with the units and method steps of the various examples described in the embodiments disclosed in this application, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a manner driven by computer software depends on the specific application scenario and design constraints of the technical solution.

[0225] Figures 7 and 8 are schematic diagrams of the structures of possible communication devices provided in embodiments of the present application. These communication devices can be used to implement the functions of the mobility management network element, session management network element, onboard application server, or onboard user plane network element in the above-mentioned method embodiments, and thus can also achieve the beneficial effects possessed by the above-mentioned method embodiments. In the embodiments of the present application, the communication device can be a mobility management network element, a session management network element, an onboard application server, or an onboard user plane network element, or can be a module (such as a chip) applied to the mobility management network element, the session management network element, the onboard application server, or the onboard user plane network element.

[0226] The communication device 700 shown in Figure 7 includes a processing unit 710 and a transceiver unit 720. The communication device 700 is used to implement the functions of the mobility management network element, session management network element, onboard application server, or onboard user plane network element in any of the method embodiments shown in Figures 4(a) to 4(c) and Figure 6.

[0227] When the communication device 700 is used to implement the function of the mobility management network element in the above method embodiment, the processing unit 710 is configured to determine, based on a communication plan of a terminal device, a first satellite that is expected to provide communication services for the terminal device; and the transceiver unit 720 is configured to send an identifier of the first satellite to the session management network element. The communication plan includes an identifier of at least one satellite expected to be used; or the communication plan includes at least two sets of service information, the at least two sets of service information including a first set of service information and a second set of service information, the first set of service information including first communication location information and first communication time information, the first communication location information being used to indicate a first location at which the terminal device is expected to use satellite communication, the first communication time information being used to indicate a first time at which the terminal device is expected to use satellite communication at the first location, and the second set of service information including second communication location information and second communication time information, the second communication location information being used to indicate a second location at which the terminal device is expected to use satellite communication, and the second communication time information being used to indicate a second time at which the terminal device is expected to use satellite communication at the second location, the second time being different from the first time.

[0228] In one possible implementation method, the first communication time information includes at least two of a first start time, a first communication duration, or a first end time; the second communication time information includes at least two of a second start time, a second communication duration, or a second end time.

[0229] In a possible implementation method, the first position is different from the second position.

[0230] In one possible implementation method, when the communication plan includes the identifier of the at least one satellite expected to be used, the communication plan also includes communication time information corresponding to the at least one satellite expected to be used, and the communication time information corresponding to the first satellite is used to indicate the time when the terminal device expects to use the first satellite to communicate.

[0231] In a possible implementation method, the transceiver unit 720 is further configured to receive the communication plan from the terminal device, the ground application server, or the network management device.

[0232] In a possible implementation method, the transceiver unit 720 is further configured to send an access layer context of the terminal device to the first satellite, where the access layer context is used to establish a connection between the first satellite and the terminal device.

[0233] In a possible implementation method, the transceiver unit 720 is further configured to send indication information to the session management network element, where the indication information is used to trigger selection of a satellite-based user plane network element that provides services for the terminal device.

[0234] In one possible implementation method, the transceiver unit 720 is also used to receive the storage and forwarding contract data of the terminal device from the unified data management network element, and the storage and forwarding contract data is used to indicate that the terminal device has signed a contract for the storage and forwarding service; the transceiver unit 720 is used to send indication information to the session management network element, specifically including: sending the indication information to the session management network element based on the storage and forwarding contract data.

[0235] In one possible implementation method, the transceiver unit 720 is also used to receive a session establishment request from the terminal device and the data network name DNN requested by the terminal device, the session establishment request is used to request to establish a session, and the data network corresponding to the DNN is used to provide on-board storage and forwarding services; the transceiver unit 720 is used to send indication information to the session management network element, specifically including: sending the indication information to the session management network element according to the DNN.

[0236] When the communication device 700 is used to implement the function of the session management network element in the above method embodiment, the transceiver unit 720 is used to receive the session management subscription information of the first session of the terminal device from the unified data management network element, where the session management subscription information includes the data network name DNN, and the data network corresponding to the DNN is used to provide on-board storage and forwarding services; the processing unit 710 is used to select the on-board user plane network element according to the DNN.

[0237] In one possible implementation method, the session management subscription information also includes a store-and-forward indication, which is used to indicate that the data network corresponding to the DNN is used to provide on-board store-and-forward services; the processing unit 710 is used to select an on-board user plane network element according to the DNN, specifically including: selecting an on-board user plane network element according to the DNN and the store-and-forward indication.

[0238] In one possible implementation method, the transceiver unit 720 is also used to receive traffic description information from a ground application server; and send forwarding rules to the selected onboard user plane network element, wherein the forwarding rules are used by the onboard user plane network element to forward the uplink service flow that matches the traffic description information to the onboard application server.

[0239] In a possible implementation method, the traffic description information includes a DNAI; the processing unit 710 is further configured to select a satellite-based user plane network element according to the DNAI.

[0240] When the communication device 700 is used to implement the function of the satellite-borne application server in the above-mentioned method embodiment, the transceiver unit 720 is used to receive the downlink business flow of the terminal device from the ground application server; the processing unit 710 is used to store the downlink business flow; the transceiver unit 720 is also used to send the stored downlink business flow to the satellite-borne user plane network element after receiving the uplink business flow from the terminal device or during the satellite communication time of the terminal device, and the satellite communication time is used to indicate the time when the terminal device uses satellite communication.

[0241] In a possible implementation method, the transceiver unit 720 is further configured to receive the satellite communication time of the terminal device.

[0242] In a possible implementation method, the satellite communication time information includes at least two of a start time, a communication duration, or an end time.

[0243] When the communication device 700 is used to implement the function of the satellite-borne application server in the above-mentioned method embodiment, the transceiver unit 720 is used to receive the uplink service flow from the terminal device of the satellite-borne user plane network element; the processing unit 710 is used to store the uplink service flow; the transceiver unit 720 is also used to send the stored uplink service flow to the ground application server when the satellite-borne application server successfully establishes a connection with the ground application server.

[0244] In one possible implementation method, the transceiver unit 720 is also used to receive the downlink service flow of the terminal device from the ground application server when the satellite-borne application server successfully establishes a connection with the ground application server; the processing unit 710 is also used to store the downlink service flow; the transceiver unit 720 is also used to send the stored downlink service flow to the satellite-borne user plane network element after receiving the uplink service flow from the terminal device or within the satellite communication time of the terminal device, and the satellite communication time is used to indicate the time when the terminal device uses satellite communication.

[0245] In a possible implementation method, the transceiver unit 720 is further configured to receive the satellite communication time of the terminal device.

[0246] In a possible implementation method, the satellite communication time information includes at least two of a start time, a communication duration, or an end time.

[0247] When the communication device 700 is used to implement the functions of the satellite user plane network element in the above-mentioned method embodiment, the transceiver unit 720 is used to receive forwarding rules from the session management network element, and the forwarding rules are used by the satellite user plane network element to forward the uplink service flow of the terminal device to the satellite application server; receive the uplink service flow from the terminal device; and the processing unit 710 is used to send the uplink service flow of the terminal device to the satellite application server through the transceiver unit 720 according to the forwarding rules.

[0248] In one possible implementation method, the forwarding rule is also used by the onboard user plane network element to send a downlink service flow to the terminal device; the transceiver unit 720 is also used to receive the downlink service flow of the terminal device from the onboard application server; the processing unit 710 is also used to send the downlink service flow to the terminal device through the transceiver unit 720 according to the forwarding rule.

[0249] A more detailed description of the processing unit 710 and the transceiver unit 720 can be directly obtained by referring to the relevant descriptions in the method embodiment of Figures 4(a) to 4(c) and Figure 6, and will not be repeated here.

[0250] The communication device 800 shown in FIG8 includes a processor 810. It may further include an interface circuit 820. The processor 810 and the interface circuit 820 are coupled to each other. It is understood that the interface circuit 820 may be a transceiver or an input / output interface.

[0251] Optionally, the communication device 800 further includes a memory 830 for storing instructions or input data.

[0252] The processor 810 may be configured to execute instructions in the memory 830 to implement actions of the relevant network elements in the method embodiments shown in Figures 4(a) to 4(c) and 6. For example, the processor 810 may read instructions in the memory 830 via the interface circuit 820, without limitation.

[0253] It should be noted that the communication device 800 can be a device in any of the methods shown in Figures 4(a) to 4(c) and Figure 6, for example, a satellite-borne UPF, a satellite-borne application server, a ground application server, a UE, an AMF, a PSA UPF, an SMF, or an AF, etc., and can also be located in the above-mentioned devices, for example, a chip in the device, or a system on a chip, etc., without limitation.

[0254] When the communication device 800 is used to implement the relevant network element functions in any of the methods shown in Figures 4(a) to 4(c) and Figure 6, the processor 810 is used to implement the functions of the above-mentioned processing unit 710, and the interface circuit 820 is used to implement the functions of the above-mentioned transceiver unit 720.

[0255] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0256] In one implementation method, an embodiment of the present application also provides a communication system, which includes an AMF and an SMF, and the AMF and SMF can be used to implement the operations performed by the AMF and the SMF in the method embodiment shown in Figure 4(a) or Figure 6.

[0257] In one implementation method, an embodiment of the present application also provides a communication system, which includes a UDM and an SMF. The UDM and SMF can be used to implement the operations performed by the UDM and SMF in the method embodiment shown in Figure 4(a) or Figure 6.

[0258] In one implementation method, an embodiment of the present application further provides a communication system, comprising an onboard application server and a ground application server. The onboard application server and the ground application server can be used to implement the operations performed by the onboard application server and the ground application server (or AF) in the method embodiments shown in Figures 4(b), 4(c), or 6. Furthermore, the communication system also includes an onboard UPF, which is used to implement the operations performed by the onboard UPF in the method embodiments shown in Figures 4(b), 4(c), or 6.

[0259] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in an access network device or a terminal device. Of course, the processor and storage medium can also exist in the access network device or the terminal device as discrete components.

[0260] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, an access network device, a terminal device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0261] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0262] In this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the previous and next related objects are in an "or" relationship; in the formulas of this application, the character " / " indicates that the previous and next related objects are in a "division" relationship.

[0263] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

Claims

1. A communication method, characterized in that: include: Determining, according to a communication plan of the terminal device, a first satellite expected to provide communication services for the terminal device; Sending the identifier of the first satellite to a session management network element; wherein the communication plan includes an identification of at least one satellite to be used; or, The communication plan includes at least two groups of service information, and the at least two groups of service information include a first group of service information and a second group of service information. The first group of service information includes first communication position information and first communication time information, the first communication position information is used to indicate a first position where the terminal device is expected to use satellite communication, and the first communication time information is used to indicate a first time when the terminal device is expected to use satellite communication at the first position. The second group of service information includes second communication position information and second communication time information, the second communication position information is used to indicate a second position where the terminal device is expected to use satellite communication, and the second communication time information is used to indicate a second time when the terminal device is expected to use satellite communication at the second position, and the second time is different from the first time.

2. The method according to claim 1, characterized in that The first communication time information includes at least two of a first start time, a first communication duration, or a first end time; The second communication time information includes at least two of a second start time, a second communication duration, or a second end time.

3. The method according to claim 1 or 2, characterized in that The first position is different from the second position.

4. The method according to any one of claims 1 to 3, characterized in that When the communication plan includes the identifier of the at least one satellite expected to be used, the communication plan also includes communication time information corresponding to the at least one satellite expected to be used, and the communication time information corresponding to the first satellite is used to indicate the time when the terminal device is expected to use the first satellite for communication.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: Receive the communication plan from the terminal device, ground application server or network management device.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: An access layer context of the terminal device is sent to the first satellite, where the access layer context is used to establish a connection between the first satellite and the terminal device.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: Send indication information to the session management network element, where the indication information is used to trigger selection of a satellite-based user plane network element that provides services for the terminal device.

8. The method according to claim 7, characterized in that The method further comprises: Receiving store-and-forward contract data of the terminal device from a unified data management network element, wherein the store-and-forward contract data is used to indicate that the terminal device has signed a contract for a store-and-forward service; The sending the indication information to the session management network element includes: The indication information is sent to the session management network element according to the store-and-forward subscription data.

9. The method according to claim 7, characterized in that The method further comprises: Receiving a session establishment request from the terminal device and a data network name DNN requested by the terminal device, wherein the session establishment request is used to request to establish a session, and the data network corresponding to the DNN is used to provide an on-board storage and forwarding service; The sending the indication information to the session management network element includes: According to the DNN, the indication information is sent to the session management network element.

10. A communication method, characterized in that: include: Receiving session management subscription information of a first session of a terminal device from a unified data management network element, wherein the session management subscription information includes a data network name DNN, and the data network corresponding to the DNN is used to provide an on-board storage and forwarding service; According to the DNN, a satellite-based user plane network element is selected.

11. The method according to claim 10, characterized in that The session management subscription information also includes a store-and-forward instruction, where the store-and-forward instruction is used to instruct the data network corresponding to the DNN to provide an on-board store-and-forward service; The selecting, according to the DNN, a satellite-borne user plane network element comprises: According to the DNN and the store-and-forward indication, a satellite user plane network element is selected.

12. The method according to claim 10 or 11, characterized in that The method further comprises: Receive traffic description information from a ground application server; A forwarding rule is sent to the selected onboard user plane network element, where the forwarding rule is used by the onboard user plane network element to forward an uplink service flow matching the traffic description information to the onboard application server.

13. The method according to claim 12, characterized in that The traffic description information includes a data network access identifier DNAI; The method further comprises: Select a satellite-borne user plane network element according to the DNAI.

14. A communication method, characterized in that: include: Receiving downlink service flow of terminal equipment from ground application server; storing the downlink service flow; After receiving the uplink service flow from the terminal device or during the satellite communication time of the terminal device, the stored downlink service flow is sent to the onboard user plane network element, and the satellite communication time is used to indicate the time when the terminal device uses satellite communication.

15. The method according to claim 14, characterized in that The method further comprises: Receive the satellite communication time of the terminal device.

16. The method according to claim 14 or 15, characterized in that The satellite communication time information includes at least two of a start time, a communication duration or an end time.

17. A communication method, characterized in that: include: Receiving uplink service flows from terminal equipment of satellite-borne user plane network elements; storing the uplink service flow; When the satellite-borne application server successfully establishes a connection with the ground application server, the stored uplink service flow is sent to the ground application server.

18. The method according to claim 17, characterized in that The method further comprises: When the satellite-borne application server successfully establishes a connection with the ground application server, receiving a downlink service flow of the terminal device from the ground application server; storing the downlink service flow; After receiving the uplink service flow from the terminal device or during the satellite communication time of the terminal device, the stored downlink service flow is sent to the onboard user plane network element, and the satellite communication time is used to indicate the time when the terminal device uses satellite communication.

19. The method according to claim 18, characterized in that The method further comprises: Receive the satellite communication time of the terminal device.

20. The method according to claim 18 or 19, characterized in that The satellite communication time information includes at least two of a start time, a communication duration or an end time.

21. A communication device, characterized in that: The invention comprises a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and execute the method described in any one of claims 1 to 9, or execute the method described in any one of claims 10 to 13, or execute the method described in any one of claims 14 to 16, or execute the method described in any one of claims 17 to 20.

22. A communication device, characterized in that: Comprising a module for executing the method of any one of claims 1 to 9, or the method of any one of claims 10 to 13, or the method of any one of claims 14 to 16, or the method of any one of claims 17 to 20.

23. A communication device, characterized in that: The method comprises a processor coupled to a memory, wherein the processor is used to call a program stored in the memory to execute the method described in any one of claims 1 to 9, or the method described in any one of claims 10 to 13, or the method described in any one of claims 14 to 16, or the method described in any one of claims 17 to 20.

24. A communication device, characterized in that: The communication device comprises a processor and a memory; the memory is used to store computer instructions, and when the communication device is running, the processor executes the computer instructions stored in the memory to execute the method described in any one of claims 1 to 9, or execute the method described in any one of claims 10 to 13, or execute the method described in any one of claims 14 to 16, or execute the method described in any one of claims 17 to 20.

25. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, it implements the method as described in any one of claims 1 to 9, or implements the method as described in any one of claims 10 to 13, or implements the method as described in any one of claims 14 to 16, or implements the method as described in any one of claims 17 to 20.

26. A communication system, characterized in that: comprising a session management network element, and a mobility management network element for executing the method according to any one of claims 1 to 9; The session management network element is used to receive the identifier of the first satellite.

27. A communication system, characterized in that: comprising a unified data management network element, and a session management network element for executing the method according to any one of claims 10 to 13; The unified data management network element is used to send the session management subscription information of the first session of the terminal device to the session management network element.

28. A communication system, characterized in that: comprising a ground application server, and a spaceborne application server for executing the method according to any one of claims 14 to 16; The ground application server is used to send the downlink service flow of the terminal equipment to the satellite application server.

29. A communication system, characterized in that: comprising a ground application server, and a spaceborne application server for executing the method according to any one of claims 17 to 20; The ground application server is used to receive the uplink service flow of the terminal device from the satellite-borne application server.

Citation Information

Patent Citations

  • Communication method and device of satellite communication system

    CN114024594A

  • System and method for authorizing access in satellite communications

    CN114270728A

  • Satellite UPF discovery method and device

    CN115706600A

  • Data processing method, network equipment and storage medium

    CN115708329A

  • Polar relay system for satellite communication

    US5666648A