Satellite communication method and device

Abstract

The invention provides a satellite communication method and device, and the method can comprise the steps that a session management network element obtains an identification list, and the identification list comprises one or more pieces of identification information of terminal equipment which accesses a satellite in a satellite return mode; and the session management network element configures a forwarding rule to a user plane network element on the satellite, wherein the forwarding rule is used for distributing a data packet of which the destination address is included in the address of the terminal equipment corresponding to the identification list to the access network equipment corresponding to the terminal equipment. According to the scheme, the terminal equipment supporting the local data exchange under the satellite can communicate through the local data exchange under the satellite, so that the time delay can be reduced, and the user experience is improved.

Description

[0001] This application is a divisional application. The application number of the original application is 202210309468.3, and the original application date is March 27, 2022. The entire content of the original application is incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technologies, and in particular, to a satellite communication method and apparatus. Background Art

[0003] Currently, an important scenario where satellite communication and 5G communication system (the 5th-generation mobile communications system, 5GS) fusion technology can be applied is satellite backhaul (SATB), that is, the satellite link serves as the satellite backhaul link, and the access network device communicates with the core network device through the satellite backhaul link. However, in this scenario, when two UEs accessing the network through satellite backhaul communicate, the latency is often relatively large, resulting in a poor user experience. How to reduce the end-to-end transmission latency in the satellite communication scenario is a problem that needs to be considered. Summary of the Invention

[0004] This application provides a satellite communication method and apparatus, which can reduce the transmission latency between terminal devices in the satellite communication scenario.

[0005] In a first aspect, a satellite communication method is provided. This method can be executed by a session management network element, or can also be executed by a component (such as a chip or a circuit) of the session management network element, and this is not limited. For the sake of description, the following takes the execution by the session management network element as an example for illustration.

[0006] The communication method includes: the session management network element obtains an identifier list, and the identifier list includes identifier information of one or more terminal devices accessing the satellite through satellite backhaul; the session management network element configures a forwarding rule for the user plane network element on the satellite, and the forwarding rule is used to divert data packets whose destination address includes the address of the terminal device corresponding to the identifier list to the access network device corresponding to the terminal device.

[0007] Based on the above solution, the session management network element can configure a forwarding rule for the user plane network element on the satellite, so that the user plane network element sends data packets whose destination address includes the address of the terminal device corresponding to the identifier list to the access network device corresponding to the terminal device. That is to say, for the terminal devices in the identifier list, the data packets sent to them can be directly sent by the user plane network element on the satellite to the corresponding access network device, without passing through the ground anchor access network device. Therefore, the data transmission path can be shortened and the transmission latency can be reduced.

[0008] In combination with the first aspect, in some implementations of the first aspect, the session management network element obtains an identifier list, including: the session management network element receives the identifier list from the data management network element or the mobility management network element.

[0009] Based on the above solution, the session management network element can obtain the identifier list through the data management network element or the mobility management network element, so as to configure a forwarding rule for the user plane network element on the satellite according to the identifier list.

[0010] In combination with the first aspect, in some implementations of the first aspect, before the session management network element receives the identifier list from the data management network element, the method further includes: the session management network element sends a request message to the data management network element, and the request message includes relevant information of the satellite, and the request message is used to request to obtain the identifier list.

[0011] Based on the above solution, the session management network element can send a request message carrying relevant information of the satellite to the data management network element, so that the data management network element can send the identifier list corresponding to the relevant information of the satellite to the session management network element.

[0012] In combination with the first aspect, in some implementations of the first aspect, the method further includes: the session management network element receives a session context establishment request message from the mobility management network element, and the session context establishment request message includes the identifier information of the first terminal device, and the first terminal device accesses the satellite through a satellite backhaul mode; the session management network element obtains relevant information of the satellite; the session management network element sends a registration message to the data management network element, and the registration message includes the identifier information of the first terminal device and the relevant information of the satellite.

[0013] Based on the above solution, when the first terminal device establishes a session through the session management network element, if the session management network element determines that the first terminal device accesses the satellite through a satellite backhaul mode, the session management network element can register the identifier information of the first terminal device and the relevant information of the satellite to the data management network element, so that the data management network element can save the above identifier list.

[0014] In combination with the first aspect, in some implementations of the first aspect, the method further includes: the session management network element determines to allow the first terminal device to perform local data exchange under the satellite.

[0015] Based on the above solution, when the session management network element determines that the first terminal device supports local data exchange under the satellite, it can register the identification information of the first terminal device and the relevant information of the satellite with the data management network element, so that the identification list can include the identification information of one or more terminal devices allowed to perform local data exchange under the satellite, enabling the session management network element to configure forwarding rules for the user plane network element on the satellite to implement local data exchange under the satellite for these terminal devices.

[0016] In combination with the first aspect, in some implementation manners of the first aspect, the session management network element obtains the relevant information of the satellite, including: the session management network element receives the relevant information of the satellite from the mobility management network element.

[0017] In combination with the first aspect, in some implementation manners of the first aspect, the session management network element obtains the relevant information of the satellite, including: the session management network element determines the relevant information of the satellite according to the location information of the terminal device.

[0018] Based on the above solution, the session management network element can obtain the identification information of the satellite through the mobility management network element, or can also determine the relevant information of the satellite by itself according to the identification information of the terminal device, so as to obtain an identification list corresponding to the relevant information of the satellite.

[0019] In combination with the first aspect, in some implementation manners of the first aspect, the method further includes: the session management network element sends a subscription message to the data management network element, where the subscription message includes the relevant information of the satellite, and the subscription message is used to subscribe to the change notification of the identification list.

[0020] Based on the above solution, the session management network element can subscribe to the change notification of the identification list from the data management network element. That is to say, when a new terminal device registers to the identification list, or an original terminal device is deregistered from the identification list, the group management network element needs to notify the session management network element. Based on this, the session management network element can update the forwarding rules for the user plane network element on the satellite according to the updated session identification list, so that the terminal device that accesses the satellite through the satellite backhaul method and supports local data exchange under the satellite can communicate through local data exchange under the satellite, thereby reducing the transmission delay and improving the user experience.

[0021] In combination with the first aspect, in some implementation manners of the first aspect, the relevant information of the satellite can be any one of the following information: the data network access identifier corresponding to the satellite, the identifier of the satellite, the Internet protocol address of the satellite.

[0022] Second aspect, a satellite communication method is provided. This method can be executed by a mobility management network element, or can also be executed by components (such as chips or circuits) of the mobility management network element, and there is no limitation in this regard. For the sake of convenience in description, the following takes the execution by the mobility management network element as an example for illustration.

[0023] This communication method includes: the mobility management network element receives an identity list from the data management network element, and this identity list includes identity information of one or more terminal devices accessing the satellite through the satellite backhaul mode; the mobility management network element sends this identity list to the session management network element.

[0024] Based on the above solution, the mobility management network element can provide the session management network element with an identity list corresponding to the relevant information of the satellite, so that the session management network element can configure a forwarding rule for the user plane network element on the satellite according to this identity list, so that the user plane network element sends a data packet whose destination address includes the address of the terminal device corresponding to the identity list to the access network device corresponding to this terminal device, thereby shortening the data transmission path and reducing the transmission delay.

[0025] Combined with the second aspect, in some implementation manners of the second aspect, before the mobility management network element receives the identity list from the data management network element, this method further includes: the mobility management network element sends a request message to the data management network element, and this request message includes the relevant information of the satellite, and this request message is used to request to obtain this identity list.

[0026] Based on the above solution, the mobility management network element can request the data management network element for an identity list corresponding to the relevant information of the satellite, so as to provide this identity list to the session management network element.

[0027] Combined with the second aspect, in some implementation manners of the second aspect, this method further includes: the mobility management network element receives a session establishment request message from a first terminal device, and this session establishment request message includes the identity information of the first terminal device, and the first terminal device accesses the satellite through the satellite backhaul mode; the mobility management network element determines the relevant information of the satellite according to the location information of the first terminal device; the mobility management network element sends a registration message to the data management network element, and this registration message includes the identity information of the first terminal device and the relevant information of the satellite.

[0028] Based on the above solution, the mobility management network element can register the identity information of the first terminal device and the relevant information of the satellite to the data management network element during the session establishment process of the first terminal device, so that the data management network element can generate and save an identity list corresponding to the relevant information of the satellite.

[0029] In combination with the second aspect, in some implementations of the second aspect, the method further includes: the session management network element determines to allow the first terminal device to perform local data exchange under the satellite.

[0030] Based on the above solution, the mobility management network element can, when determining to allow the first terminal device to perform local data exchange under the satellite, register the identification information of the first terminal device with the data management network element, so that the terminal devices corresponding to the identification list itself support local data exchange under the satellite.

[0031] In combination with the second aspect, in some implementations of the second aspect, the method further includes: the mobility management network element sends a subscription message to the data management network element, the subscription message includes relevant information about the satellite, and the subscription message is used to subscribe to change notifications of the identification list.

[0032] Based on the above solution, the mobility management network element can subscribe to change notifications of the identification list from the data management network element. That is to say, when a new terminal device registers with the identification list, or an original terminal device is deregistered from the identification list, the group management network element needs to notify the mobility management network element. Based on this, the mobility management network element can send the updated identification list to the session management network element, so that the session management network element can update the forwarding rules to the user plane network element on the satellite according to the updated session identification list, enabling terminal devices that access the satellite through satellite backhaul and support local data exchange under the satellite to communicate through local data exchange under the satellite, thereby reducing transmission latency and improving the user experience.

[0033] In a third aspect, a satellite communication method is provided. This method can be executed by the data management network element, or can also be executed by components (such as chips or circuits) of the data management network element, and this is not limited. For the sake of description, the following takes the execution by the data management network element as an example for illustration.

[0034] The satellite communication method includes: the data management network element receives a request message from a first network element, the request message includes relevant information about the satellite; the data management network element determines an identification list corresponding to the identification information of the satellite according to the relevant information about the satellite, and the identification list includes the identification information of one or more terminal devices that access the satellite through satellite backhaul; in response to the request message, the data management network element sends the identification list to the first network element.

[0035] Based on the above solution, the data management network element can send the identification list corresponding to the satellite to the first network element according to the request of the first network element, so that the session management network element can configure forwarding rules for the user plane network element on the satellite according to the identification list, so that the user plane network element can send the data packet whose destination address includes the address of the terminal device corresponding to the identification list to the access network device corresponding to the terminal device, thereby shortening the data transmission path and reducing the transmission delay.

[0036] Among them, the first network element here can be a session management network element or a mobility management network element.

[0037] Combined with the third aspect, in some implementation manners of the third aspect, the method further includes: the data management network element receives a registration message from the first network element, and the registration message includes the identification information of the first terminal device and the related information of the satellite; the data management network element saves the identification information of the first terminal device in the identification list.

[0038] Based on the above solution, the first session management network element can register the identification information of the first terminal device and the related information of the satellite to the data management network element, so that the data management network element can update the identification list, thereby enabling the first terminal device to perform local data exchange under the satellite to reduce the transmission delay.

[0039] Combined with the third aspect, in some implementation manners of the third aspect, the method further includes: the data management network element receives a subscription message from the first network element, and the subscription message includes the related information of the satellite, and the subscription message is used to subscribe to the change notification of the related information of the satellite.

[0040] Based on the above solution, the first network element can subscribe to the change notification of the identification list from the data management network element. In this case, after the identification list is updated, the data management network element can send the updated identification list to the first network element, so that the session management network element can configure new forwarding rules for the user plane network element on the satellite according to the updated identification list.

[0041] Combined with the third aspect, in some implementation manners of the third aspect, the first network element is a session management network element or a mobility management network element.

[0042] Fourthly, a communication device is provided, which is used to execute any of the methods provided in the first to third aspects above. Specifically, the device may include units and / or modules for executing the methods provided in the first to third aspects, such as a processing module and / or a transceiver module (which may also be referred to as a communication module). In one implementation, the device is a network device. For example, the device is a session management network element, or a mobility management network element, or a data management network element. When the device is a network device, the communication module may be a transceiver, or an input / output interface; the processing module may be a processor.

[0043] In one implementation, the device is a chip, a chip system or a circuit used in a network device. When the device is a chip, a chip system or a circuit used in a communication device, the communication module may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc. on the chip, the chip system or the circuit; the processing module may be a processor, a processing circuit or a logic circuit, etc.

[0044] In a possible case, the device is a session management network element, or a chip, a chip system or a circuit in a session management network element. In this case, the device may include units and / or modules for executing the method provided in the first aspect, such as a processing unit and / or a communication unit.

[0045] In another possible case, the device is a mobility management network element, or a chip, a chip system or a circuit in a mobility management network element. In this case, the device may include units and / or modules for executing the method provided in the second aspect, such as a processing module and / or a transceiver module.

[0046] In yet another possible case, the device is a data management network element, or a chip, a chip system or a circuit in a data management network element. In this case, the device may include units and / or modules for executing the method provided in the third aspect, such as a processing module and / or a transceiver module.

[0047] Fifthly, a communication device is provided, which includes: a memory for storing a program; a processor for executing the program stored in the memory, and when the program stored in the memory is executed, the processor is used to execute any of the methods provided in the first to third aspects above.

[0048] Sixth aspect, the present application provides a processor for executing the methods provided in the above aspects. During the execution of these methods, the processes of sending the above information and obtaining / receiving the above information in the above methods can be understood as the process of the processor outputting the above information and the process of the processor receiving the input above information. When outputting the above information, the processor outputs the above information to the transceiver for transmission by the transceiver. After the above information is output by the processor, other processing may be required before reaching the transceiver. Similarly, when the processor receives the input above information, the transceiver obtains / receives the above information and inputs it to the processor. Further, after the transceiver receives the above information, the above information may require other processing before being input to the processor.

[0049] Based on the above principle, for example, the reception of the request message mentioned in the foregoing method can be understood as the processor receiving the input information.

[0050] For operations such as transmission, sending, and obtaining / receiving involved in the processor, if there is no special description, or if it does not conflict with its actual role or internal logic in the relevant description, they can all be more generally understood as operations of the processor outputting, receiving, and inputting, rather than the transmission, sending, and receiving operations directly performed by the radio frequency circuit and the antenna.

[0051] During implementation, the above processor can be a processor specifically for executing these methods, or a processor that executes computer instructions in a memory to execute these methods, such as a general-purpose processor. The above memory can be a non-transitory memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip or separately provided on different chips. The embodiments of the present application do not limit the type of the memory and the setting manner of the memory and the processor.

[0052] Seventh aspect, a computer-readable storage medium is provided. The computer-readable medium stores program code for a device to execute, and the program code includes any of the methods provided in the first aspect to the third aspect above.

[0053] Eighth aspect, a computer program product containing instructions is provided. When the computer program product runs on a computer, it causes the computer to execute any of the methods provided in the first aspect to the third aspect above.

[0054] Ninth aspect, a chip is provided. The chip includes a processor and a communication interface. The processor reads instructions stored on a memory through the communication interface and executes any of the methods provided in the first aspect to the third aspect above.

[0055] Optionally, as an implementation, the chip may further include a memory in which instructions are stored, and the processor is configured to execute the instructions stored on the memory. When the instructions are executed, the processor is configured to execute any of the methods provided in the first to third aspects above.

[0056] In a tenth aspect, a communication system is provided, including one or more of the foregoing session management network element, mobility management network element, and data management network element. Description of the Drawings

[0057] Figure 1 is a schematic diagram of a network architecture applicable to the embodiments of the present application;

[0058] Figure 2 is a schematic diagram of a communication architecture of a satellite backhaul link;

[0059] Figure 3 is a schematic diagram of a communication architecture of satellite local data exchange;

[0060] Figure 4 is a schematic flowchart of a communication method provided by an embodiment of the present application;

[0061] Figure 5 is a schematic flowchart of another communication method provided by an embodiment of the present application;

[0062] Figure 6 is a schematic flowchart of yet another communication method provided by an embodiment of the present application;

[0063] Figure 7 is a schematic block diagram of a communication device provided by an embodiment of the present application;

[0064] Figure 8 is a schematic block diagram of a communication device provided by another embodiment of the present application;

[0065] Figure 9 is a schematic block diagram of a communication device provided by yet another embodiment of the present application. Detailed Embodiments

[0066] To make the objectives, technical solutions, and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings. The specific operation methods in the method embodiments can also be applied to the device embodiments or system embodiments. Among them, in the description of the present application, unless otherwise specified, the meaning of "a plurality of" is two or more.

[0067] In various embodiments of the present application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be cross-referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0068] It can be understood that the various numerical numbers involved in the present application are only for the convenience of description and are not used to limit the scope of the present application. The magnitudes of the serial numbers of the above processes do not mean the order of execution, and the execution order of each process should be determined by its function and inherent logic.

[0069] The terms "first", "second", "third", "fourth" and other various term numbers (if any) in the description and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and do not necessarily describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances so that the embodiments described here can be implemented in an order other than that shown or described here. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0070] The technical solutions provided by the present application can be applied to various communication systems, such as: the fifth generation (5G) or new radio (NR) system, the long term evolution (LTE) system, the LTE frequency division duplex (FDD) system, the LTE time division duplex (TDD) system, etc. The technical solutions provided by the present application can also be applied to future communication systems. The technical solutions provided by the present application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine type communication (MTC), and the Internet of Things (IoT) communication system or other communication systems.

[0071] The following will be combined with Figure 1An example is given to illustrate the 5G system applicable to the embodiments of the present application. It should be understood that the 5G system described herein is only an example and should not constitute any limitation to the present application.

[0072] It should also be understood that service-based interfaces or point-to-point interfaces can be adopted for communication between some network elements in the 5G system. The 5G system frameworks based on point-to-point interfaces and service-based interfaces are respectively introduced below in combination with Figure 1 (a) of Figure 1 and (b) of

[0073] As an exemplary illustration, Figure 1 (a) of Figure 1 shows a schematic diagram of the architecture of the 5G system 100 applicable to the embodiments of the present application. Figure 1 It is a schematic diagram of the 5G network architecture based on point-to-point interfaces. As shown in

[0074] (a) of

[0075] This network architecture may include, but is not limited to, the following network elements (or referred to as functional network elements, functional entities, nodes, devices, etc.): Figure 1 (Radio) access network equipment (radio access network, (R)AN), access and mobility management function (access and mobility management function, AMF) network element, session management function (session management function, SMF) network element, user plane function (user plane function, UPF) network element, policy control function (policy control function, PCF) network element, unified data management (unified data management, UDM) network element, AF network element, data network (data network, DN), network slice selection function (network slice selection function, NSSF), authentication server function (authentication server function, AUSF), unified data management (unified data management, UDM), BSF network element, unified data repository (unified data repository, UDR), etc.

[0076] 1. User Equipment (UE): It can be referred to as terminal equipment, terminal device, access terminal, user unit, user station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. A terminal device can be a device that provides voice / data connectivity to users. For example, it can be a handheld device with wireless connection capabilities, a vehicle-mounted device, etc. Currently, some examples of terminals can be: mobile phone, tablet (pad), computer with wireless transceiver function (such as laptop, handheld computer, etc.), mobile internet device (MID), virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in a 5G network or terminal device in a future evolved public land mobile network (PLMN), etc.

[0077] In addition, the terminal device can also be a terminal device in the Internet of Things (IoT) system. The IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, so as to achieve an intelligent network of human-machine interconnection and object-object interconnection. IoT technology can achieve massive connection, deep coverage, and power saving of terminals through, for example, narrowband (NB) technology.

[0078] In addition, the terminal device may further include an intelligent printer, a train detector, etc. Its main functions include collecting data (for some terminal devices), receiving control information and downlink data from the network device, and transmitting electromagnetic waves to transmit uplink data to the network device.

[0079] It should be understood that the user equipment may be any device that can access the network. A certain air interface technology may be adopted between the terminal device and the access network device for mutual communication.

[0080] Optionally, the user equipment can be used as a base station. For example, the user equipment can act as a scheduling entity that provides sidelink signals between user equipments in V2X or D2D, etc. For instance, a cellular phone and a vehicle communicate with each other using sidelink signals. The cellular phone and the smart home device communicate without relaying the communication signal through a base station.

[0081] 2. (Radio) Access Network ((R)AN) Equipment: It is used to provide network access functions for authorized user equipments in a specific area and can use transmission tunnels with different service qualities according to the level of the user equipment, service requirements, etc.

[0082] (R)AN can manage radio resources, provide access services for user equipments, and then complete the forwarding of control signals and user equipment data between the user equipment and the core network. (R)AN can also be understood as a base station in a traditional network.

[0083] Exemplarily, the access network equipment in the embodiments of the present application may be any communication device with wireless transceiver functions for communicating with user equipments. The access network equipment includes but is not limited to an evolved NodeB (eNB) or a gNB in a 5G, such as an NR, system, or a transmission point (TRP or TP), one or a group (including multiple antenna panels) of antenna panels of a base station in a 5G system, or may also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), etc.

[0084] In some deployments, the gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers. The AAU implements some physical layer processing functions, radio frequency processing, and related functions of the active antenna. Since the information in the RRC layer will ultimately become the information in the PHY layer, or is transformed from the information in the PHY layer, therefore, in this architecture, high-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or sent by the DU + AAU. It can be understood that the access network device can be a device including one or more of the CU node, DU node, and AAU node. In addition, the CU can be classified as an access network device in the radio access network (RAN), or the CU can be classified as an access network device in the core network (CN), and this application does not make a limitation on this.

[0085] In a satellite communication scenario, the radio access network device may also be referred to as a radio satellite access network site (or radio satellite access network device, radio satellite access network), satellite access network site (or satellite access network device, satellite access network), or satellite network site (or satellite network device, satellite network). The embodiments of this application do not make any limitations in this regard. There are various deployment methods for the satellite access network. For example, the same PLMN simultaneously has a terrestrial 3GPP access network and a satellite 3GPP access network, and there are independent interfaces between the two access networks and the core network respectively. Another example is that different core networks share the same satellite access network, and the shared satellite access network will include available PLMNs in the broadcast system information. Another example is that the terrestrial access network and the satellite access network are independent, that is, the terrestrial access network and the satellite access network correspond to independent PLMNs. Another example is that the satellites in the sky are only responsible for signal transmission and do not have the function of an access network. In this scenario, the satellite access can also be referred to as satellite backhaul. In the above non-satellite backhaul scenarios, the satellite may include all or part of the functions of the access network. This application does not make any limitations in this regard. When all the functions of the base station are integrated on the satellite, the satellite access network device can be understood as a device with some functions of the base station on the satellite, and all the relevant signaling and data processing of the access network are carried out on the satellite. When some functions of the base station are integrated on the satellite and some functions are located on the ground, the satellite access network device can be understood as a device with some functions of the base station on the satellite and a device with some functions of the base station on the ground, and the relevant signaling and data processing of the access network are carried out partly on the satellite and partly on the ground. During satellite backhaul, the satellite access network device can be understood as a base station on the ground, and all the relevant signaling and data processing of the access network are carried out on the ground, and the satellite transparently transmits signaling and data between the terminal device and the satellite access network.

[0086] 3. User plane function (UPF) network element: It is used for packet routing and forwarding, as well as quality of service (QoS) processing of user plane data, etc.

[0087] In a 5G communication system, this user plane network element may be a user plane function (UPF) network element. In future communication systems, the user plane network element may still be a UPF network element, or there may be other names. This application does not make any limitations.

[0088] 4. Access and mobility management function (AMF) network element: The access and mobility management function network element is mainly used for mobility management and access management, etc., and can be used to implement other functions except session management in the MME function. For example, functions such as access authorization / authentication, etc.

[0089] In a future communication system, the access and mobility management device can still be the AMF, or it can have other names, which are not limited in this application.

[0090] 5. Session Management Function (SMF) network element: mainly used for session management, allocation and management of the Internet Protocol (IP) address of the user equipment, selection of manageable user plane functions, termination of the policy control and charging function interfaces, and downlink data notification, etc.

[0091] In a future communication system, the session management network element can still be the SMF network element, or it can have other names, which are not limited in this application.

[0092] 6. Policy Control Function (PCF) network element: used for the unified policy framework to guide network behavior, and provide policy rule information for control plane function network elements (such as AMF, SMF, etc.).

[0093] In a future communication system, the policy control network element can still be the PCF network element, or it can have other names, which are not limited in this application.

[0094] 7. Application Function (AF): used for data routing that affects applications, a radio access network open function network element, and interacts with the policy framework for policy control, etc.

[0095] In a future communication system, the application network element can still be the AF network element, or it can have other names, which are not limited in this application.

[0096] 8. Unified Data Management (UDM) network element: used for processing UE identifiers, access authentication, registration, and mobility management, etc.

[0097] In a future communication system, the unified data management can still be the UDM network element, or it can have other names, which are not limited in this application.

[0098] 9. Authentication Server Function (AUSF) network element: used for authentication services, generating keys to implement mutual authentication of user equipment, and supporting a unified authentication framework.

[0099] In a future communication system, the authentication server function network element can still be the AUSF network element, or it can have other names, which are not limited in this application.

[0100] 10. Network Data Analytics Function (NWDAF) network element: It is used to identify network slice instances and load the load level information of network slice instances. The Network Data Analytics Function enables NF consumers to subscribe to or unsubscribe from periodic notifications and, in the case of exceeding a threshold, notify the consumers.

[0101] In future communication systems, the network element of the Network Data Analytics Function can still be the NWDAF network element, or it can also have other names, which are not limited in this application.

[0102] 11. Data Network (DN): The DN is a network outside the operator's network. The operator's network can access multiple DNs. Multiple services can be deployed on the DN, providing services such as data and / or voice for terminal devices. For example, the DN is a private network of a smart factory. The sensors installed in the workshop of the smart factory can be terminal devices. A control server for the sensors is deployed in the DN, and the control server can provide services for the sensors. The sensors can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions. Another example is that the DN is the internal office network of a company. The mobile phones or computers of the company's employees can be terminal devices, and the mobile phones or computers of the employees can access information and data resources on the company's internal office network.

[0103] Figure 1 In (a), Nausf, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers can be referred to the meanings defined in the 3GPP standard protocol and are not restricted here.

[0104] In Figure 1In the network architecture shown in (a) below, each network element can communicate through the interfaces shown in the figure. As shown in the figure, the UE and the AMF can interact through the N1 interface, and the interaction messages can be called N1 messages (N1Message) for example. The RAN and the AMF can interact through the N2 interface, and the N2 interface can be used for sending non-access stratum (NAS) messages, etc. The RAN and the UPF can interact through the N3 interface, and the N3 interface can be used for transmitting user plane data, etc. The SMF and the UPF can interact through the N4 interface, and the N4 interface can be used for transmitting information such as tunnel identification information of the N3 connection, data caching indication information, and downlink data notification messages. The UPF and the DN can interact through the N6 interface, and the N6 interface can be used for transmitting user plane data, etc. The relationships between other interfaces and each network element are as shown in Figure 1 shown in (a) below. For the sake of brevity, they will not be elaborated one by one here.

[0105] As Figure 1 shown in (b) below, it is a schematic diagram of the 5G network architecture based on point-to-point interfaces. The introduction of the functions of the network elements therein can refer to Figure 1 the introduction of the functions of the corresponding network elements in (a) below, and will not be elaborated here. Figure 1 The main difference between (b) below and Figure 1 (a) below is that: Figure 1 the interfaces between the network elements in (b) below are point-to-point interfaces, rather than service-based interfaces.

[0106] In Figure 1 the architecture shown in (b) below, the interface names and functions between each network element are as follows:

[0107] 1) N7: The interface between the PCF and the SMF, used for issuing protocol data unit (PDU) session granularity and service data flow granularity control policies.

[0108] 2) N15: The interface between the PCF and the AMF, used for issuing UE policy and access control related policies.

[0109] 3) N5: The interface between the AF and the PCF, used for issuing application service requests and reporting network events.

[0110] 4) N4: The interface between the SMF and the UPF, used for transmitting information between the control plane and the user plane, including issuing forwarding rules from the control plane to the user plane, QoS control rules, traffic statistics rules, etc., and reporting user plane information.

[0111] 5) N11: The interface between the SMF and the AMF, which is used to transfer PDU session tunnel information between the RAN and the UPF, transfer control messages sent to the UE, transfer radio resource control information sent to the RAN, etc.

[0112] 6) N2: The interface between the AMF and the RAN, which is used to transfer radio bearer control information from the core network side to the RAN, etc.

[0113] 7) N1: The interface between the AMF and the UE, which is access-independent and used to transfer QoS control rules to the UE, etc.

[0114] 8) N8: The interface between the AMF and the UDM, which is used for the AMF to obtain subscription data and authentication data related to access and mobility management from the UDM, and for the AMF to register the current mobility management related information of the UE with the UDM, etc.

[0115] 9) N10: The interface between the SMF and the UDM, which is used for the SMF to obtain subscription data related to session management from the UDM, and for the SMF to register the current session related information of the UE with the UDM, etc.

[0116] 10) N35: The interface between the UDM and the UDR, which is used for the UDM to obtain user subscription data information from the UDR.

[0117] 11) N36: The interface between the PCF and the UDR, which is used for the PCF to obtain policy related subscription data and application data related information from the UDR.

[0118] 12) N12: The interface between the AMF and the AUSF, which is used for the AMF to initiate an authentication process to the AUSF, and the SUCI can be carried as a subscription identifier;

[0119] 13) N13: The interface between the UDM and the AUSF, which is used for the AUSF to obtain user authentication vectors from the UDM to execute the authentication process.

[0120] It should be understood that the above naming is only defined for the convenience of distinguishing different functions and should not impose any limitations on this application. This application does not exclude the possibility of using other naming in 5G networks and future other networks. For example, in future networks, some or all of the above network elements may continue to use the terms in 5G, or other names may also be used, etc. Figure 1 The interface names between the network elements in (a) are just an example. In specific implementations, the interface names may be other names, and this application does not make specific limitations on this. In addition, the names of the messages (or signaling) transmitted between the above network elements are also just an example and do not impose any limitations on the functions of the messages themselves.

[0121] It can be understood that the above network element or function can be either a network element in a hardware device, or a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). For the convenience of description, in the following of this application, a network device is taken as an access and mobility management function (AMF), and a base station is taken as a radio access network (RAN) as an example for description.

[0122] It should be understood that the above network architecture applied to the embodiments of this application is only an example, and the network architecture applicable to the embodiments of this application is not limited thereto. Any network architecture capable of implementing the functions of the above network elements is applicable to the embodiments of this application.

[0123] The network architecture and service scenarios described in the embodiments of this application are for more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those of ordinary skill in the art know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of this application are equally applicable to similar technical problems.

[0124] Each aspect or feature of the embodiments of this application can be implemented as a method, or implemented by a device or a standard programming and / or engineering technology product. The term "product" used in this application covers a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media can include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes, etc.), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks, or key drives, etc.). Additionally, the various storage media described herein can represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable media" can include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0125] To facilitate the understanding of the technical solutions of the embodiments of this application, before introducing the solutions of the embodiments of this application based on the 5G architecture, some terms or concepts in 5G that may be involved in the embodiments of this application, as well as network elements that may be involved in this application but not shown in the above network architecture, are briefly described first.

[0126] 1. Satellite communication

[0127] Satellite communication technology refers to the technology in which wireless communication devices on the ground access the network through satellites, or refers to the technology in which wireless communication devices on the ground communicate with each other through satellites as relays. Compared with traditional mobile communication systems, satellite communication has a wider coverage range and can overcome natural geographical barriers such as oceans, deserts, and mountains.

[0128] Based on Figure 1 the shown communication system architecture, satellite communication can be integrated with the 5th-generation mobile communications system (5GS). Currently, the integration of satellite communication and 5GS can be divided into two scenarios. The first scenario is that the satellite serves as a 3GPP access and the UE accesses 5GS through the satellite. The second scenario is that the satellite link serves as a backhaul link and the RAN communicates with the 5G core network (5GC) through the backhaul link (for example, the backhaul link provides a bearer for N3 or N9).

[0129] This application mainly focuses on the scenario where Figure 2 the satellite link serves as a 5G backhaul link as shown, Figure 2 which is a schematic diagram of the scenario of the integration of satellite communication and 5GS. It can be seen from Figure 2 that the satellite link serves as a 5G backhaul link and the RAN is connected to the 5GC through the 5G backhaul link. Among them, the 5GC may include core network network elements such as AMF, AF, and UPF shown in Figure 1 .

[0130] It should be noted that Figure 2 only one satellite is shown in. In actual communication scenarios, there may be multiple satellites, and the types of these multiple satellites can be the same or different. There are wireless links between different satellites, which can complete signaling interaction and user data transmission between access network devices.

[0131] Due to different orbital heights, the coverage area, motion characteristics, propagation delay, jitter, etc. of different types of satellites may also be different. Exemplarily, satellites can be divided into geostationary equatorial orbit (GEO), low earth orbit (LEO) polar orbit constellations, mid earth orbit (MEO), and other satellites (Other SAT) according to orbital types.

[0132] 2. Satellite constellation.

[0133] A satellite constellation is a collection of satellites that are launched into orbit and can operate normally. Usually, it is a satellite network composed of a number of satellites configured in a certain way. The main satellite constellations include the Global Positioning System (GPS) satellite constellation, the GLONASS satellite constellation, the Galileo satellite constellation, and the Beidou satellite constellation, etc.

[0134] The constellation types mainly involved in this application include:

[0135] Low Earth Orbit (LEO) polar orbit constellations, Medium Earth Orbit (MEO) polar orbit constellations, LEO inclined orbit constellations, and MEO inclined orbit constellations, etc.

[0136] Among them, the LEO inclined orbit constellation and the MEO inclined orbit constellation do not involve the concept of reverse seam. That is to say, in the case of the constellation type being LEO inclined orbit constellation and MEO inclined orbit constellation, there is no need to consider whether reverse seam is supported. The LEO polar orbit constellation and the MEO polar orbit constellation involve the concept of reverse seam. That is to say, in the case of the constellation type being LEO polar orbit constellation and MEO polar orbit constellation, it is necessary to consider whether reverse seam is supported.

[0137] 3. Ephemeris

[0138] Ephemeris, which can also be called ephemeris table, almanac, ephemeris book, etc., is information used to locate the position of celestial bodies at any moment. The terminal device can search the network according to the satellite ephemeris data, thereby improving the user experience. The satellite ephemeris mainly includes orbital plane parameters and satellite level parameters.

[0139] It should be understood that in the embodiments of this application, the satellite ephemeris can also be called ephemeris parameters, the ephemeris parameters of a satellite, the ephemeris parameters of a satellite accessing the network, the ephemeris parameters of a satellite in the satellite backhaul, or other possible names. This application does not make any limitations in this regard.

[0140] 4. Satellite backhaul

[0141] When Figure 1 a satellite is used as the transmission path between the RAN and the UPF in the network architecture shown, it is called satellite backhaul. Figure 3 Fig. shows a schematic diagram of a satellite backhaul scenario. As Figure 3As shown in the figure, UE1 establishes PDU session - 1 through satellite backhaul. The user plane path is UE, RAN1, GEO UPF - 1, (optional) terrestrial PSA - 1 (shown as a dotted line in the figure); UE2 establishes PDU session - 2 through satellite backhaul. The user plane path is UE, RAN2, GEO UPF - 2, (optional) terrestrial PSA - 2 (shown as a dashed line in the figure). GEO UPF - 1 and GEO UPF - 2 can be the same or different.

[0142] The above combines Figure 1 introduced the scenarios where the embodiments of this application can be applied, and also briefly introduced the basic concepts involved in this application. In the following, the communication methods and devices provided by this application will be described in detail with reference to the accompanying drawings.

[0143] The embodiments shown below do not particularly limit the specific structure of the execution entity of the method provided by the embodiments of this application. As long as it can communicate according to the method provided by the embodiments of this application by running a program that records the code of the method provided by the embodiments of this application. For example, the execution entity of the method provided by the embodiments of this application can be a core network device and a terminal device, or a functional module in the core network device or the terminal device that can call and execute the program.

[0144] For the convenience of understanding the embodiments of this application, the following points are explained.

[0145] First, in this application, "for indicating" can be understood as "enabling", and "enabling" can include direct enabling and indirect enabling. When describing that a certain piece of information is used to enable A, it can include that this information directly enables A or indirectly enables A, and it does not necessarily mean that A is carried in this information.

[0146] The information enabled by the information is called the information to be enabled. Then, in the specific implementation process, there are many ways to enable the information to be enabled. For example, but not limited to, the information to be enabled can be directly enabled, such as the information to be enabled itself or the index of the information to be enabled, etc. It can also indirectly enable the information to be enabled by enabling other information, where there is an association relationship between the other information and the information to be enabled. It can also only enable a part of the information to be enabled, while the other parts of the information to be enabled are known or pre - agreed. For example, it can also rely on the pre - agreed (such as protocol - specified) arrangement order of each piece of information to achieve the enabling of specific information, thereby reducing the enabling overhead to a certain extent. At the same time, the common parts of each piece of information can be identified and enabled uniformly to reduce the enabling overhead caused by enabling the same information separately.

[0147] Second, the first, second, and various numerical numbers (e.g., "#1", "#2", etc.) shown in this application are only for convenience of description and are used to distinguish objects, and do not limit the scope of the embodiments of this application. For example, to distinguish different messages, etc., rather than to describe a specific order or sequence. It should be understood that the objects described in this way can be interchanged under appropriate circumstances so as to be able to describe solutions other than the embodiments of this application.

[0148] Third, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that comprises a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products, or devices.

[0149] Fourth, in this application, "pre-configuration" may include pre-definition. For example, protocol definition. Among them, "pre-definition" can be implemented by pre-saving corresponding codes, tables, or other means that can be used to indicate relevant information in a device (e.g., including each network element). This application does not limit its specific implementation manner.

[0150] Fifth, the "storage" involved in the embodiments of this application may refer to storage in one or more memories. The one or more memories may be separately provided or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories may also have a part separately provided and a part integrated in a decoder, a processor, or a communication device. The type of memory may be any form of storage medium, and this application does not limit this.

[0151] Sixth, the "protocol" involved in the embodiments of this application may refer to standard protocols in the communication field. For example, it may include 5G protocols, new radio (NR) protocols, and related protocols applied to future communication systems. This application does not limit this.

[0152] Seventh, the dashed boxes in the method flowcharts in the accompanying drawings of this application specification indicate optional steps.

[0153] Hereinafter, taking the interaction between network elements as an example, the communication method provided by the embodiments of this application will be described in detail. It should be understood that the terms and steps in the embodiments of this application can refer to each other.

[0154] Figure 4 An exemplary flowchart of method 400 provided by the embodiments of this application is shown. Method 400 will be described exemplarily in combination with each step below.

[0155] S401, the session management network element obtains an identity list.

[0156] Exemplarily, the identifier list includes the identifier information of one or more terminal devices accessing the satellite through satellite backhaul, or in other words, the identifier list includes the identifier information of one or more terminal devices accessing the network through satellite backhaul. The identifier list corresponds to the relevant information of the satellite. The identifier information of the terminal device may be the Internet Protocol (IP) address of the terminal device, that is, the identifier list may be the IP list of the terminal device, or the identifier information of the terminal device may also be other types of identifiers, such as the Subscription Permanent Identifier (SUPI) of the terminal device, which is not limited in this application. In one implementation, the one or more terminal devices support local data exchange under the satellite. In this case, the identifier list can also be described as: the identifier list includes the identifier information of one or more terminal devices that support local data exchange under the satellite and access the satellite through satellite backhaul.

[0157] The relevant information of the satellite may refer to any information associated with the satellite. For example, the relevant information of the satellite may be any one of the following information: the data network access identifier corresponding to the satellite, the identifier of the satellite, the Internet Protocol address of the satellite, which is not limited in this application.

[0158] The following gives an exemplary description of the specific implementation of the session management network element to obtain the identifier list.

[0159] As a possible implementation, the session management network element sends a request message to the data management network element. The request message includes the relevant information of the satellite, and the request message is used to request to obtain the identifier list. Correspondingly, the data management network element receives the request message from the session management network element, then obtains the identifier list stored locally corresponding to the relevant information of the satellite according to the relevant information of the satellite, and then the data management network element sends the identifier list to the session management network element.

[0160] As another possible implementation, it can also be that the mobility management network element requests the data management network element to obtain the identifier list, and then sends the obtained identifier list to the session management network element.

[0161] As yet another possible implementation, if all the terminal devices corresponding to the identifier list are served by the session management network element, the session management network element can determine the identifier list by itself. That is to say, the session management network element may also determine by itself the identifier list of the terminal devices accessing the satellite through satellite backhaul.

[0162] As another possible implementation, the session management network element determines the identification list according to the identification list of the terminal devices that need to communicate (denoted as the first identification list) and the identification list of the terminal devices that access the satellite through satellite backhaul (denoted as the second identification list). For example, before S401, the session management network element receives the first identification list from the application function network element; wherein, the first identification list includes the identification information corresponding to the terminal devices that need to communicate. The terminal devices that need to communicate are, for example, the terminal devices that need to participate in an online meeting.

[0163] Then, the session management network element can obtain the second identification list of the terminal devices that access the satellite through satellite backhaul from the mobility management network element or the data management network element, or the second identification list of the terminal devices that access the satellite through satellite backhaul determined by the session management network element itself. The specific implementation method can refer to the above example (i.e., the identification list in the above example corresponds to the second identification list here).

[0164] Furthermore, the session management network element determines the identification list according to the first identification list and the second identification list. Exemplarily, the identification list includes the identification information of the terminal devices that are common to the first identification list and the second identification list, that is, the identification list includes the identification information of one or more terminal devices that need to communicate and access the satellite through satellite backhaul.

[0165] For example, the session management function (SMF) receives the first identification list {UE1 - UE10} from the application function (AF); the second identification list of the terminal devices that access the satellite through satellite backhaul obtained by the SMF is {UE5 - UE100}. Then the SMF determines the identification list as {UE5 - UE10} according to the first identification list and the second identification list. That is to say, the communication of UE5 - UE10 can be realized through the local data exchange under the satellite in this application, and the communication of UE1 - UE4 can be realized by using the existing technology, which will not be elaborated in this application.

[0166] It should be understood that the data management network element has pre - saved the corresponding relationship between the relevant information of the satellite and the identification list, where the terminal devices in the identification list can be registered (or saved) by the session management network element to the data management network element. The following will give an exemplary description in combination with S403 - S405.

[0167] S402, the session management network element receives a session context establishment request message from the mobility management network element.

[0168] Exemplarily, the session context establishment request message includes the identification information of the first terminal device, wherein the first terminal device accesses the satellite through satellite backhaul. The identification information of the terminal device can be the IP of the terminal device or the SUPI of the terminal device, which is not limited in this application.

[0169] In one implementation, the first terminal device accesses the satellite through the way of backhaul via a geostationary orbit satellite. That is to say, the satellite backhaul mode of the first terminal device is backhaul via a geostationary orbit satellite. In this implementation, the identification list can also be described as: the identification list includes the identification information of one or more terminal devices that access the geostationary orbit satellite through the way of backhaul via a geostationary orbit satellite.

[0170] S403, the session management network element determines whether to allow the first terminal device to perform local data exchange under the satellite.

[0171] Exemplarily, the session management network element can determine whether to allow the first terminal device to perform local data exchange under the satellite according to the subscription information or policy information of the first terminal device. For example, the subscription information or policy information indicates that the terminal can perform local data exchange, and this application does not limit this. If the session management network element determines to allow the first terminal device to perform local data exchange under the satellite, the session management network element executes S404.

[0172] S404, the session management network element sends a registration message to the data management network element. Correspondingly, the data management network element receives the registration message from the session management network element.

[0173] Exemplarily, the registration message includes the identification information of the first terminal device and the relevant information of the satellite. Correspondingly, after receiving the registration message, the data management network element saves the identification information of the first terminal device and the relevant information of the satellite, or rather, the data management network element saves the identification information of the first terminal device into the identification list corresponding to the relevant information of the satellite.

[0174] Optionally, before S404, the session management network element obtains the relevant information of the satellite.

[0175] Exemplarily, the session management network element can obtain the relevant information of the satellite from the mobility management network element, or can also determine the relevant information of the satellite by itself.

[0176] As an example, the mobility management network element can carry the relevant information of the satellite in the session context establishment request message, and the session management network element obtains the relevant information of the satellite from the session context establishment request message.

[0177] As another example, the session management network element determines the relevant information of the satellite according to the location information of the terminal device. Optionally, the session management network element may also determine the relevant information of the satellite in combination with other information. For example, the session management network element determines the relevant information of the satellite according to the location information of the terminal device and the satellite backhaul type information. Another example is that the session management network element may determine the relevant information of the satellite according to the location information of the terminal device, the satellite backhaul type information, and the constellation information of the satellite.

[0178] Similarly, if there is another terminal device (such as a second terminal device) that can perform local data exchange under the satellite and access the satellite through satellite backhaul and establish a session through the session management network element, the session management network element registers the identification information of the second terminal device and the relevant information of the satellite with the data management network element. The data management network element receives and stores the corresponding relationship between the location information of the second terminal device and the relevant information of the satellite. Or rather, the data management network element stores the location information of the second terminal device in the identification list corresponding to the relevant information of the satellite. In this way, a list of identifications including the identifications of one or more terminal devices that access the satellite through satellite backhaul and support local data exchange under the satellite can be maintained on the data management network element side.

[0179] Optionally, in S405, the session management network element sends a subscription message to the data management network element. The subscription message includes the relevant information of the satellite, and the subscription message is used to subscribe to the change notification of the identification list. That is to say, when the identification list corresponding to the relevant information of the satellite is updated, the data management network element sends a notification message to the session management network element. For example, when a certain terminal device registers to the satellite (that is, a certain terminal device accesses the network through satellite backhaul), or a certain terminal device is deregistered from the satellite (that is, a certain terminal device no longer accesses the network through satellite backhaul), the data management network element sends a notification message to the session management network element and carries the updated identification list in the notification message.

[0180] It should be understood that S405 is described by taking explicit subscription as an example, but the session management network element may also subscribe to the data management network element in a way of implicit subscription, that is, step 405 is not executed, and this application does not make any limitation. It should be understood that the identification list may also be registered by the session management network element to the data management network element, and the specific implementation manner is similar to S402 - S405, which will be briefly described below.

[0181] Exemplarily, the mobility management network element receives a message from a first terminal device, which includes a session establishment request message and also includes the identification information of the first terminal device. The first terminal device accesses the satellite through satellite backhaul. Then, optionally, the mobility management network element determines whether to allow the first terminal device to perform local data exchange under the satellite (similar to S403). If allowed, the mobility management network element sends a registration message to the data management network element. The registration message includes the identification information of the first terminal device and the relevant information of the satellite (similar to S404). The data management network element receives and saves the correspondence between the identification information of the first terminal device and the relevant information of the satellite. Optionally, the mobility management network element may also send a subscription message to the data management network element to subscribe to the change notification of the identification list (similar to S405), which will not be elaborated here.

[0182] S406. The session management network element configures a forwarding rule for the user plane network element on the satellite.

[0183] Exemplarily, the forwarding rule is used to divert (or forward) a data packet whose destination address contains the address of the terminal device corresponding to the identification list to the access network device corresponding to the terminal device. Or it can also be described as that the forwarding rule is used to divert a data packet to be sent to the terminal device corresponding to the identification list to the access network device corresponding to the terminal device. Or it can also be described as that the forwarding rule is used to divert a data packet whose destination address points to the terminal device in the identification list to the access network device corresponding to the terminal device. Or it can also be described as that the forwarding rule is used to divert a data packet whose destination address contains the address of the terminal device in the identification list to the internal interface. For example, UE1 accesses the network through satellite backhaul. Assume that the identification list corresponding to the relevant information of the satellite at this time includes UE2 and UE3. UE1 sends a data packet to UE2, and the destination address of the data packet is the UE2 IP. When the user plane network element on the satellite receives the data packet, according to the forwarding rule, it determines that the destination address of the data packet is included in the address of the terminal device corresponding to UE2 or UE3, then the user plane network element on the satellite sends the data packet to the access network device corresponding to UE2.

[0184] Furthermore, the forwarding rule is also used to divert a data packet sent to the terminal device to the access network device corresponding to the terminal device. Taking the above example for illustration, UE3 sends a data packet to UE1, and the destination address of the data packet is the UE1 IP. When the user plane network element on the satellite receives the data packet, according to the forwarding rule, it determines that the destination address of the data packet is UE1, then the user plane network element on the satellite sends the data packet to the access network device corresponding to UE1.

[0185] It should be noted that the specific manifestation form of the forwarding rule may include two parts: the detection rule part and the forwarding rule part. Among them, the detection rule part is used to detect data packets that meet the conditions, that is, to detect data packets whose destination address is the address of the terminal device in the identification list; the forwarding rule part is used to forward the data packets that meet the conditions to the internal interface or to the access network device corresponding to the terminal device corresponding to the destination address.

[0186] Based on the above solution, the session management network element can configure the forwarding rule for the user plane network element on the satellite, so that the user plane network element can send the data packet whose destination address contains the address of the terminal device corresponding to the identification list to the access network device corresponding to the terminal device. That is to say, for the terminal devices in the identification list, the data packets sent to them can be directly sent by the user plane network element on the satellite to the corresponding access network device, without passing through the ground anchor access network device. Therefore, the data transmission path can be shortened and the transmission delay can be reduced.

[0187] Taking the 5G system as the basis, the communication method provided by the embodiments of the present application will be introduced below. It should be understood that SMF1 in method 500 and method 600 may correspond to the session management network element in method 400, AMF1 in method 500 and method 600 may correspond to the mobility management network element in method 400, UDM / NRF in method 500 and method 600 may correspond to the data management network element in method 400, and UE ID list in method 500 and method 600 may correspond to the identification list in method 400. Therefore, the descriptions between different embodiments can be referred to and supplemented with each other.

[0188] Figure 5 An exemplary flowchart of method 500 provided by the embodiments of the present application is shown. Method 500 will be described exemplarily below in combination with each step.

[0189] S501, UE1 sends a PDU session establishment request message to AMF1. Correspondingly, AMF1 receives the PDU session establishment request message from UE1.

[0190] Exemplarily, UE1 sends a PDU session establishment request message to AMF1 via a NAS message. Specifically, for example, UE1 sends an AN message to gNB1, and the AN message carries a NAS message, which includes a PDU session ID and a PDU session establishment request. After receiving the AN message from UE1, gNB sends an N2 message to AMF1, and the N2 message includes a PDU session ID, UE location information (ULI), and a PDU session establishment request, etc. The UE location information is used to identify the current location of UE1. For example, the UE location information can be a tracking area identity (TAI), a cell identity, or a geographical location identity, etc.

[0191] Optionally, at S502, AMF1 determines the GEO SAT ID according to the UE location information.

[0192] Exemplarily, when AMF1 determines that UE1 accesses the access network through a GEO satellite for backhaul, AMF1 determines the GEO SAT ID according to the UE location information. The GEO SAT ID is used to identify the GEO satellite accessed by UE1. The GEO SAT ID can be the identification information of the GEO satellite itself, or the identification information of the UPF on the GEO satellite (i.e., GEO UPF ID), which is not limited in this application. It can be understood that, as described in method 400, the GEO SAT ID can also be represented by DNAI, that is, represented by the DNAI corresponding to the GEO satellite. The specific meaning of DNAI can also be described as the identification corresponding to the user plane function network element on the GEO satellite, or the identification corresponding to the user plane connection where the GEO UPF is located. Alternatively, the GEO SAT ID can also be represented by GEOSAT IP, and the GEO SAT IP can be understood as the IP address of the GEO SAT.

[0193] In one implementation, AMF1 can also determine the satellite backhaul type of UE1. For example, if AMF1 determines that UE1 accesses the network through a GEO satellite based on the gNB 1 ID, then AMF1 determines that the satellite backhaul type of UE1 is GEO SATB. In another implementation, AMF1 can obtain the satellite backhaul type corresponding to UE from gNB1. For example, gNB1 sends satellite backhaul type information to AMF1, and the satellite backhaul type information indicates that UE1 accesses the network through a GEO satellite for backhaul.

[0194] Optionally, AMF1 can also determine the constellation information of the satellite. For example, in one implementation, when different gNB IDs / gNB IPs are used when the gNB accesses different constellations, AMF1 can determine the constellation information of UE1 based on the gNB1 ID / gNB1 IP; in another implementation, when different frequency bands are used for different constellations, AMF1 can determine the constellation information of UE1 based on the frequency used by the satellite.

[0195] S503. AMF1 sends a Create Session Management Context Request message to SMF1. Correspondingly, SMF1 receives the Create Session Management Context Request message from AMF1.

[0196] Exemplarily, after receiving the PDU session establishment request from UE1, AMF1 sends a Create Session Management Context (Nsmf_PDUSession_CreateSMContext request) message to SMF1. The Create Session Management Context request message includes parameters such as SUPI, PDU session ID, and the location information of the UE.

[0197] It should be understood that if AMF executes S502, AMF1 can carry the GEO SAT ID in the Create Session Management Context request message.

[0198] Optionally, in S504, SMF1 selects a terrestrial PSA.

[0199] Exemplarily, SMF1 can select a terrestrial PSA for the session of UE1. Optionally, SMF1 can also allocate an IP address (denoted as UE1 IP) for UE1.

[0200] It should be understood that SMF1 may also not select a terrestrial PSA, that is, SMF1 may not execute S504. In this case, SMF1 can still allocate UE1 IP for UE1, but at this time UE1 IP is not anchored at the UPF.

[0201] Optionally, in S505, SMF1 determines whether to allow the UE to perform local data exchange under the satellite.

[0202] In one implementation, SMF1 obtains the subscription data of UE1 through the UDM and determines whether to allow UE1 to perform local data exchange (local switch) based on the subscription data.

[0203] In another implementation, SMF1 obtains the policy information for the UE through the PCF and determines whether to allow the UE to perform local data exchange under the satellite based on the policy information.

[0204] S506. The SMF1 sends a query request message to the UDM / NRF. Correspondingly, the UDM / NRF receives the query request message from the SMF1.

[0205] Exemplarily, when the SMF1 determines that the UE1 is allowed to perform local data exchange under the satellite, the SMF1 sends a query request message to the UDM / NRF. The query request message includes the GEO SAT ID. The query request message is used to request a query of the UE identification list corresponding to the GEO SAT ID. Or rather, the query request message is used to request a query of the UE identification list of the UEs connected to the GEO satellite corresponding to the GEO SAT ID. Or rather, the query request message is used to request a query of the identification list of the UEs that are connected to the GEO satellite corresponding to the GEO SAT ID and can perform local switch under the satellite. Or rather, the query request message is used to request a query of the UE identification list corresponding to the GEO SAT ID saved by the UDM / NRF. The UE ID list includes the identifications of one or more UEs that are connected to the GEO satellite and can perform local switch under the satellite. Herein, the identification of the UE may refer to the ID of the UE, or the IP of the UE, or other types of identifications, which are not limited in this application. That is to say, the UE identification list may be a UE ID list, or a UE IP list, or other types of lists, which are not limited in this application. For the convenience of description, the UE identification list is taken as the UE ID list as an example for subsequent description.

[0206] It should be understood that the SMF1 may receive the GEO SAT ID from the AMF1, or may determine the GEO SAT ID by itself. For example, the SMF1 determines the GEO SAT ID according to the location information of the UE1, which is not limited in this application.

[0207] S507. The UDM / NRF sends a query response message to the SMF1. Correspondingly, the SMF1 receives the query response message from the UDM / NRF.

[0208] Exemplarily, after receiving the query request message from the SMF1, the UDM / NRF determines the UE ID list corresponding to the GEO SAT ID according to the GEO SAT ID, and then the UDM / NRF sends a query response message to the SMF1. The query response message includes the UE ID list. It should be understood that the UDM / NRF has pre-saved the corresponding relationship between the GEO SAT ID and the UE ID list.

[0209] It should be noted that the above query process, i.e., S506 - S507, can also be enhanced as follows:

[0210] Optionally, after the UDM / NRF receives a query request message from the SMF1, it determines whether the query request message is the first query request. That is, the UDM / NRF determines whether there is any other SMF that has queried it for the UE ID list corresponding to the GEOSAT ID before S506;

[0211] When the UDM / NRF determines that the query request is not the first query, the query response message (i.e., S507) returned by the UDM / NRF to the SMF does not include the UE ID list corresponding to the GEO SAT ID. Further, the query response message includes an indication information for indicating to the SMF1 that this query request is not the first query request. That is, at this time, the UDM / NRF does not return the UE ID list corresponding to the GEO SAT ID to the SMF1.

[0212] S508, the SMF1 sends a registration request message to the UDM / NRF. Correspondingly, the UDM / NRF receives the registration request message from the SMF1.

[0213] Exemplarily, when the SMF1 determines that the UE is allowed to perform local data exchange under the satellite, the SMF1 sends a registration request message to the UDM / NRF, and the registration request message includes the GEO SAT ID and the UE1 ID. That is, if a certain UE can perform local data exchange under the satellite, the SMF1 sends the identifier of the UE and the identifier of the satellite corresponding to the UE to the UDM / NRF.

[0214] It should be understood that the registration request message may also have other names. For example, the registration request message may also be referred to as a storage request message, which is not limited in this application.

[0215] It should also be understood that S508 may be executed before S506 or after S506, which is not limited in this application.

[0216] It should also be understood that S508 may also be executed simultaneously with S506. For example, S508 and S506 may be combined into one message. For example, the SMF1 sends a registration and query request message to the UDM / NRF, and the registration and query request message includes the GEO SAT ID and the UE1 ID. After receiving the registration and query request message, the UDM / NRF sends a registration and query response message to the SMF1, and the registration and query response message includes the UE ID list.

[0217] S509, the UDM / NRF saves the GEO SAT ID and the UE1 ID.

[0218] Exemplarily, after the UDM / NRF receives a registration request message from the SMF1, it saves the GEO SAT ID and the UE1 ID, or, in other words, saves the correspondence between the GEO SAT ID and the UE1 ID, or, in other words, saves the UE1 ID into the UE ID list corresponding to the GEO SAT ID.

[0219] S510, the SMF1 sends a subscription message to the UDM / NRF. Correspondingly, the UDM / NRF receives this subscription message from the SMF1.

[0220] Exemplarily, the SMF1 can also send a subscription message to the UDM / NRF. This subscription message includes the GEO SAT ID and is used to subscribe to the change notification of the UE ID list corresponding to this GEO SAT ID. That is to say, when the UE ID list corresponding to this GEO SAT ID is updated, the UDM / NRF sends a notification message to the SMF1. For example, when a certain UE registers to this GEO SAT or a certain UE logs off from this GEO SAT, the UDM / NRF sends a notification message to the SMF1 and carries the updated UE ID list in this notification message.

[0221] It should be understood that S510 is described by taking explicit subscription as an example, but the SMF1 can also subscribe to the UDM / NRF in an implicit subscription manner. For example, S510 is not executed, and implicit subscription is indicated through S506 or S508. This application does not make any limitations.

[0222] S511, the SMF1 sends an N4 session establishment request message to the GEO UPF. Correspondingly, the GEO UPF receives the N4 session establishment request message from the SMF.

[0223] Exemplarily, when the UE is allowed to perform local switch under the satellite, the SMF selects the GEO UPF, or, in other words, the SMF inserts the GEO UPF as the I-UPF / shunting point. This GEO UPF corresponds to the GEO SAT ID.

[0224] Furthermore, the SMF1 sends an N4 session establishment request message to the GEO UPF. This N4 session establishment request message may include the UE ID list corresponding to the GEO SAT ID to instruct the GEO UPF to perform local switch on the packets that match the UE ID list, or, in other words, to instruct the GEO UPF to perform local switch on the packets whose destination address indicates the UE in the UE ID list.

[0225] S512, The GEO UPF sends an N4 session establishment response message to SMF1. Correspondingly, SMF1 receives the N4 session establishment response message from the GEO UPF.

[0226] Exemplarily, after the GEO UPF receives the N4 session establishment request message from SMF1, it returns an N4 session establishment response message, which carries the GEO UPF tunnel info for N3 (i.e., the N3 tunnel information of the GEO UPF) to establish the N3 connection between gNB1 and the GEO UPF. Optionally, it can also carry the GEO UPF tunnel info for N9 (i.e., the N9 tunnel information of the GEO UPF) to establish the N9 tunnel between the GEO UPF and the terrestrial PSA.

[0227] S513, SMF1 sends an N1N2 message transfer request message to AMF1. Correspondingly, AMF1 receives the N1N2 message transfer request message from SMF1.

[0228] Exemplarily, the N1N2 message transfer request message includes the PDU session ID, the N2 SM info sent to the gNB, and the N1 SM container sent to the UE.

[0229] S514, AMF1 sends an N2 PDU session request message to gNB1. Correspondingly, gNB1 receives the N2 PDU session request message from AMF1.

[0230] Exemplarily, the N2 PDU session request message includes the N2 SM info and the N1 SM container.

[0231] S515, gNB1 initiates the radio interface configuration for the UE.

[0232] S516, gNB1 sends an N2 PDU session confirmation message to AMF1. Correspondingly, AMF1 receives the N2 PDU session confirmation message from gNB1.

[0233] Exemplarily, the N2 PDU session ACK message includes the gNB tunnel info (i.e., the gNB tunnel information). Further, the AMF sends the gNB tunnel info to the SMF.

[0234] S517. The SMF1 sends an N4 session modification request message to the GEO UPF. Correspondingly, the GEO UPF receives the N4 session modification request message from the SMF.

[0235] Exemplarily, after receiving the gNB tunnel info, the SMF1 sends an N4 session modification request message to the GEO UPF. The N4 session modification request message includes configuration information, which is used to instruct the GEO UPF to send the received packets that need to be sent to the UEs corresponding to the UE ID list to the gNB corresponding to the UE. Or rather, the configuration information is used to instruct the GEO UPF to send the packets whose destination address points to the UEs in the UE ID list to the gNB corresponding to the UE.

[0236] It should be understood that the GEO UPF can determine the gNB corresponding to the UE according to the saved context. For example, the GEO UPF saves the information as shown in Table 1. Among them, the N4 session ID corresponds to the PDU session ID.

[0237] Table 1

[0238] UE IP gNB tunnel info GEO UPF tunnel info N4 session ID UE1 IP gNB-1 tunnel info GEO UPF tunnel info-1 N4 session-1 UE2 IP gNB-2 tunnel info GEO UPF tunnel info-2 N4 session-2

[0239] Suppose the UE ID list includes the identifiers of UE1 and UE2. UE1 sends a packet to the GEO UPF through gNB1, and the destination address is the UE2 IP. The GEO UPF determines that the tunnel information of gNB2 corresponding to UE2 is gNB2 tunnel info according to the saved context. Then, the GEO UPF sends the packet to gNB2 according to the gNB2 tunnel info.

[0240] Through the above solution, a data forwarding rule for the UEs within the UE ID list can be configured for the GEO UPF, so that the data packets whose destination address points to any UE within the UE ID list can be directly sent to the corresponding gNB, thereby realizing the local data exchange of the UEs within the UE ID list under the satellite, reducing the latency and improving the user experience.

[0241] On the other hand, when a new UE accesses the GEO UPF, the UE ID list can also be updated. This will be described below with examples.

[0242] After the above process, UE2 also initiates a PDU session establishment process. The specific process is similar to the session establishment process of UE1. The parts not described in detail can refer to the description of the above S501 - S517 part. It should be noted that the network elements providing services for UE2 are gNB2, AMF2, and SMF2.

[0243] UE2 sends a PDU session establishment request message to AMF2. After AMF2 receives this PDU session establishment request message, it sends a create session management context establishment request message to SMF2. If SMF2 determines that UE2 accesses the network through GEO SAT backhaul, SMF2 requests UDM / NRF to obtain the UE ID list corresponding to this GEO SAT ID according to this GEO SAT ID (similar to S506). UDM / NRF returns the UE ID list to SMF2 according to the request of SMF2, and the UE ID list includes the identifier of UE1. It should be understood that the identifier of this UE1 is saved by UDM / NRF in S509. On the other hand, SMF2 registers the GEO SAT ID and UE2 ID with UDM / NRF (similar to S508), and subscribes to the change notification of the UE ID list from UDM / NRF (similar to S510).

[0244] Further, SMF2 sends an N4 session establishment request message to GEO UPF. The N4 session establishment request message includes this UE ID list to instruct GEO UPF to send the packets with the destination address pointing to the UE in the UE ID list to the gNB corresponding to this UE. Taking this UE ID list as an example, GEO UPF sends the packet with the destination address of UE1 IP to gNB1.

[0245] On the other hand, UDM / NRF also sends a notification message to SMF1. The notification message carries the updated UE ID list corresponding to GEO SAT, and the updated UE ID list includes UE2 ID. Then, SMF-1 initiates an N4 session modification to GEO UPF, carrying the updated UE ID list.

[0246] Based on the above solution, SMF1 can configure a forwarding rule for GEO UPF so that GEO UPF sends the packets with the destination address included in the address of the UE corresponding to the UE ID list to the gNB corresponding to this UE. That is to say, for the UEs in the UE ID list, the packets sent to them can be directly sent by GEO UPF to the corresponding gNB without passing through the terrestrial PSA. Therefore, the data transmission path can be shortened and the transmission delay can be reduced.

[0247] Figure 6 Fig. shows an exemplary flowchart of method 600 provided by an embodiment of the present application. The method 600 will be described exemplarily in combination with each step below.

[0248] It should be understood that S601 - S602 is similar to S501 - S502 in method 500. For the sake of brevity, it will not be elaborated here.

[0249] Optionally, in S603, AMF1 determines whether to allow the UE to perform local data exchange under the satellite.

[0250] In one implementation, AMF1 obtains the subscription data of UE1 through UDM, and determines whether to allow UE1 to perform local data exchange according to the subscription data.

[0251] In another implementation, AMF1 obtains the policy information for the UE through PCF, and determines whether to allow UE1 to perform local data exchange according to the policy information.

[0252] In S604, AMF1 sends a query request message to UDM / NRF, and the query request message includes the GEO SAT ID. Correspondingly, UDM / NRF receives the query request message from AMF1.

[0253] In S605, UDM / NRF sends a query response message to AMF1, and the query response message includes the UE ID list. Correspondingly, AMF1 receives the query response message from UDM / NRF.

[0254] Optionally, AMF1 also executes S606 - S608, which are described as follows:

[0255] In S606, AMF1 sends a registration request message to UDM / NRF, and the registration request message includes the GEO SAT ID and the UE1 ID. Correspondingly, UDM / NRF receives the registration request message from AMF1.

[0256] In S607, UDM / NRF saves the GEO SAT ID and the UE1 ID.

[0257] In S608, AMF1 sends a subscription message to UDM / NRF, and the subscription message includes the GEO SAT ID.

[0258] It should be understood that S604 - S608 is similar to S506 - S510 in method 500, except that S506 - S510 in method 500 is executed by SMF1, and S604 - S608 is executed by AMF1. For the sake of brevity, the detailed process will not be elaborated.

[0259] In S609, AMF1 sends a create session management context request message to SMF1. Correspondingly, SMF1 receives the create session management context request message from AMF1.

[0260] Exemplarily, the create session management context request message includes a UE ID list.

[0261] It can be understood that in method 600, the registration process can also be performed by the SMF. That is to say, when S606 - S607 are not executed, the SMF1 performs the registration process to the UDM / NRF after S610, that is, registers the corresponding relationship between the GEO SAT ID and the UE1 ID to the UDM / NRF. For specific descriptions, reference can be made to S508 - S509, which are briefly described as follows:

[0262] The SMF1 sends a registration request message to the UDM / NRF. Correspondingly, the UDM / NRF receives the registration request message from the SMF1. Among them, the registration request message contains the GEO SAT ID and the UE1 ID.

[0263] After receiving the registration request message from the SMF1, the UDM / NRF saves the GEO SAT ID and the UE1 ID.

[0264] Furthermore, S610 - S617 are similar to S504, S511 - S517 in method 500. For the sake of brevity, they will not be elaborated here.

[0265] Corresponding to the methods given in the above method embodiments, the embodiments of the present application also provide corresponding devices. The device includes modules for performing the corresponding operations of the above - mentioned method embodiments. The module can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the above - mentioned method embodiments also apply to the following device embodiments. Therefore, the content not described in detail can be referred to the above - mentioned method embodiments. For the sake of brevity, it will not be elaborated here.

[0266] Figure 7 It is a schematic block diagram of a communication device 10 provided by an embodiment of the present application. The device 10 includes a processing module 11. Optionally, the device 10 may further include a transceiver module 12. The processing module 11 is used for data processing. The transceiver module 12 can implement corresponding communication functions, or it can be said that the transceiver module 12 is used to perform operations related to reception and transmission. The processing module 11 is used to perform other operations except reception and transmission. The transceiver module 12 can also be referred to as a communication interface or a communication unit.

[0267] Optionally, the device 10 may further include a storage module ( Figure 7 not shown in the figure), which can be used to store instructions and / or data. The processing module 11 can read the instructions and / or data in the storage module so that the device can implement the actions of the device or network element in the foregoing method embodiments.

[0268] In a first design, the device 10 may correspond to the network device in the above method embodiments, or a component of the network device (such as a chip), for example, a session management network element (such as an SMF), or a mobility management network element (such as an AMF), or a data management network element (such as a DUM or an NRF).

[0269] The device 10 may implement the steps or processes corresponding to those performed by the session management network element (such as an SMF) in the above method embodiments. Among them, the processing module 11 may be used to perform the operations related to the processing of the application session management network element (such as an SMF) in the above method embodiments, and the transceiver module 12 may be used to perform the operations related to the transceiver of the session management network element (such as an SMF) in the above method embodiments.

[0270] Exemplarily, the device 10 may correspond to the session management network element in the method 400 of the embodiments of the present application, or the SMF in the methods 500 to 600. The device 10 may include modules for performing Figures 4 to 6 the methods performed by the session management network element (or SMF) therein. Moreover, each module in the device 10 and the above other operations and / or functions respectively serve to implement Figures 4 to 6 the corresponding processes of the methods shown.

[0271] In a possible design, the processing module 11 is configured to obtain service information, where the service information is used to indicate one or more services supported by the satellite; and, determine whether to allow the terminal device to access the services supported by the satellite according to the service information; and, in the case of determining to allow the terminal device to access at least one of the services supported by the satellite, insert the user plane network element on the satellite into the user plane path of the terminal device.

[0272] The processing module 11 is configured to obtain an identification list, where the identification list includes identification information of one or more terminal devices accessing the satellite through satellite backhaul; the processing module 11 is configured to configure a forwarding rule for the user plane network element on the satellite, and the forwarding rule is used to divert data packets whose destination address includes the address of the terminal device corresponding to the identification list to the access network device corresponding to the terminal device.

[0273] Optionally, the transceiver module 12 is specifically configured to receive the identification list from the data management network element or the mobility management network element.

[0274] Optionally, the transceiver module 12 is further configured to send a request message to the data management network element, where the request message includes relevant information of the satellite, and the request message is used to request to obtain the identification list.

[0275] Optionally, the transceiver module 12 is further configured to receive a session context establishment request message from a mobility management network element, where the session context establishment request message includes identification information of a first terminal device, and the first terminal device accesses the satellite through a satellite backhaul mode; the processing module 11 is further configured to obtain relevant information of the satellite; the transceiver module 12 is further configured to send a registration message to the data management network element, where the registration message includes the identification information of the first terminal device and the relevant information of the satellite.

[0276] Optionally, the processing module 11 is further configured to determine to allow the first terminal device to perform local data exchange under the satellite.

[0277] Optionally, the processing module 11 is specifically configured to obtain relevant information of the satellite, including: the session management network element receives the relevant information of the satellite from the mobility management network element.

[0278] Optionally, the processing module 11 is specifically configured to determine the relevant information of the satellite according to the location information of the terminal device.

[0279] Optionally, the transceiver module 12 is further configured to send a subscription message to the data management network element, where the subscription message includes the relevant information of the satellite, and the subscription message is used to subscribe to change notifications of the identification list.

[0280] Optionally, the relevant information of the satellite may be any one of the following information: the data network access identifier corresponding to the satellite, the identifier of the satellite, the Internet protocol address of the satellite.

[0281] The apparatus 10 can implement the steps or processes corresponding to those performed by the mobility management network element (or AMF) in the above method embodiments. Among them, the transceiver module 12 can be used to perform the operations related to sending and receiving of the mobility management network element (or AMF) in the above method embodiments, and the processing module 11 can be used to perform the processing-related operations of applying the mobility management network element (or AMF) in the above method embodiments.

[0282] Exemplarily, the apparatus 10 can correspond to the mobility management network element in method 400 of the embodiments of the present application, or the AMF in methods 500 to 600. The apparatus 10 may include modules for performing the methods performed by the mobility management network element (or AMF) in Figures 4 to 6 And each module in the apparatus 10 and the above other operations and / or functions respectively correspond to the corresponding processes of the methods shown in Figures 4 to 6 the methods shown.

[0283] In a possible implementation, the transceiver module 12 is configured to receive an identifier list corresponding to the relevant information of the satellite from the data management network element, where the identifier list includes identifier information of one or more terminal devices accessing the satellite through the satellite backhaul mode; and send the identifier list to the session management network element.

[0284] Optionally, the transceiver module 12 is further configured to send a request message to the data management network element, where the request message includes the relevant information of the satellite, and the request message is used to request to obtain the identifier list.

[0285] Optionally, the transceiver module 12 is further configured to receive a session establishment request message from a first terminal device, where the session establishment request message includes the identifier information of the first terminal device, and the first terminal device accesses the satellite through the satellite backhaul mode; the processing module 11 is further configured to determine the relevant information of the satellite according to the location information of the first terminal device; the transceiver module 12 is further configured to send a registration message to the data management network element, where the registration message includes the identifier information of the first terminal device and the relevant information of the satellite.

[0286] Optionally, the processing module 11 is further configured to determine to allow the first terminal device to perform local data exchange under the satellite.

[0287] Optionally, the transceiver module 12 is further configured to send a subscription message to the data management network element, where the subscription message includes the relevant information of the satellite, and the subscription message is used to subscribe to the change notification of the identifier list.

[0288] The apparatus 10 can implement the steps or processes corresponding to the group management network element (or UDM / NRF) in the above method embodiments. Among them, the transceiver module 12 can be used to perform the operations related to sending and receiving of the group management network element (or UDM / NRF) in the above method embodiments, and the processing module 11 can be used to perform the operations related to processing of the application group management network element (or UDM / NRF) in the above method embodiments.

[0289] Exemplarily, the apparatus 10 can correspond to the group management network element in the method 400 of the embodiments of the present application, or the UDM / NRF in the methods 500 to 600. The apparatus 10 can include modules for performing Figures 4 to 6 the methods performed by the group management network element (or UDM / NRF) therein. And, each module in the apparatus 10 and the above other operations and / or functions respectively are for implementing Figures 4 to 6 the corresponding processes of the methods shown.

[0290] In a possible implementation, a transceiver module 12 is configured to receive a request message from a first network element, where the request message includes information related to the satellite; a processing module 11 is configured to determine an identifier list corresponding to the information related to the satellite according to the information related to the satellite, where the identifier list includes identifier information of one or more terminal devices accessing the satellite through a satellite feedback method; the transceiver module 12 is further configured to send the identifier list to the first network element.

[0291] Optionally, the transceiver module 12 is further configured to receive a registration message from the first network element, where the registration message includes identifier information of a first terminal device and information related to the satellite; the processing module 11 is further configured to save the identifier information of the first terminal device in the identifier list.

[0292] Optionally, the transceiver module 12 is further configured to receive a subscription message from the first network element, where the subscription message includes information related to the satellite, and the subscription message is used to subscribe to change notifications of the information related to the satellite.

[0293] Optionally, the first network element is a session management network element or a mobility management network element.

[0294] It should be understood that the specific processes of each module executing the above corresponding steps have been described in detail in the above method embodiments. For the sake of brevity, they will not be elaborated here.

[0295] It should also be understood that the apparatus 10 here is embodied in the form of functional modules. The term "module" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor, or a group of processors, etc.) for executing one or more software or firmware programs, and a memory, a combined logic circuit, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art can understand that the apparatus 10 may specifically be the mobility management network element in the above embodiments, and may be used to execute each process and / or step corresponding to the mobility management network element in the above method embodiments; or, the apparatus 10 may specifically be the terminal device in the above embodiments, and may be used to execute each process and / or step corresponding to the terminal device in the above method embodiments. To avoid repetition, they will not be elaborated here.

[0296] The apparatus 10 of each of the above solutions has the function of implementing the corresponding steps performed by the network device (such as a session management network element, or a mobility management network element, or a data management network element) in the above method. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver module can be replaced by a transceiver (for example, the sending unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as the processing module, can be replaced by a processor to respectively perform the transceiver operations and related processing operations in each method embodiment.

[0297] In addition, the above transceiver module 12 can also be a transceiver circuit (for example, it can include a receiving circuit and a sending circuit), and the processing module can be a processing circuit.

[0298] It should be noted that Figure 8 the apparatus in can be the network element or device in the foregoing embodiments, or a chip or a chip system, for example: a system on chip (SoC). Among them, the transceiver module can be an input / output circuit, a communication interface; the processing module is a processor or a microprocessor or an integrated circuit integrated on the chip. This is not limited herein.

[0299] According to the foregoing method, Figure 8 FIG. is a schematic diagram of a communication apparatus 20 provided in an embodiment of the present application. In a possible design, the apparatus 20 can correspond to the session management network element (or SMF) in the foregoing method embodiment; in another possible design, the apparatus 10 can correspond to the mobility management network element (or AMF) in the foregoing method embodiment.

[0300] The apparatus 20 can include a processor 21 (i.e., an example of the processing module), and the processor 21 is used to execute Figures 4 to 6 the operations performed by the session management network element (such as SMF) or the mobility management network element (such as AMF) in the corresponding method in. Optionally, the apparatus 20 can include a memory 22, and the processor 21 can execute the instructions stored in the memory 22 to enable the apparatus 20 to implement the operations performed by the session management network element (such as SMF) or the mobility management network element (such as AMF) in the corresponding method in Figures 4 to 6 .

[0301] Further, the device 20 may further include a transceiver 23 (i.e., an example of a transceiver module). Further, the processor 21, the memory 22, and the transceiver 23 may communicate with each other through an internal connection path to transmit control and / or data signals. The memory 22 is used to store a computer program, and the processor 21 may be used to call and run the computer program from the memory 22 to control the transceiver 23 to receive signals and control the transceiver 23 to send signals, so as to complete the steps of the terminal device or the network device in the above method. The memory 22 may be integrated in the processor 21 or may be separately provided from the processor 21.

[0302] Optionally, if the communication device 20 is a communication equipment, the transceiver 23 may include an input port and an output port, that is, the transceiver 23 may be divided into a receiver and a transmitter. Among them, the receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they may be collectively referred to as a transceiver.

[0303] Optionally, if the communication device 20 is a chip or a circuit, the input port is an input interface, and the output port is an output interface.

[0304] As an implementation manner, the function of the transceiver 23 may be considered to be implemented by a transceiver circuit or a dedicated chip for transceiver. The processor 21 may be considered to be implemented by a dedicated processing chip, a processing circuit, a processor, or a general-purpose chip.

[0305] As another implementation manner, it may be considered to use a general-purpose computer to implement the communication device provided in the embodiments of the present application. That is, the program codes for implementing the functions of the processor 21 and the transceiver 23 are stored in the memory 22, and the general-purpose processor implements the functions of the processor 21 and the transceiver 23 by executing the codes in the memory 22.

[0306] For the concepts, explanations, detailed descriptions, and other steps related to the technical solution provided in the embodiments of the present application involved in the device 20, please refer to the descriptions of these contents in the foregoing method or other embodiments, and details are not described herein.

[0307] Figure 9 The structural schematic diagram of a simplified network device 30 is shown. The network device includes part 31 and part 32. Part 31 is mainly used for the transceiver of radio frequency signals and the conversion between radio frequency signals and baseband signals; part 32 is mainly used for baseband processing and controlling the network device, etc. Part 31 may usually be referred to as a transceiver module, a transceiver, a transceiver circuit, or a transceiver, etc. Part 32 is usually the control center of the network device and may usually be referred to as a processing module, which is used to control the network device to execute the processing operations on the network device side in the above method embodiments.

[0308] The transceiver module of part 31, which can also be referred to as a transceiver or a transceiver unit, etc., includes an antenna and a radio frequency circuit, where the radio frequency circuit is mainly used for radio frequency processing. For example, the devices used to implement the receiving function in part 31 can be regarded as a receiving module, and the devices used to implement the transmitting function can be regarded as a transmitting module, that is, part 31 includes a receiving module and a transmitting module. The receiving module can also be referred to as a receiver, a receptor, or a receiving circuit, etc., and the transmitting module can be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0309] Part 32 can include one or more single boards, and each single board can include one or more processors and one or more memories. The processor is used to read and execute the programs in the memory to implement baseband processing functions and the control of the network device. If there are multiple single boards, the single boards can be interconnected to enhance the processing ability. As an alternative implementation, it can also be that multiple single boards share one or more processors, or multiple single boards share one or more memories, or multiple single boards share one or more processors simultaneously.

[0310] For example, in one implementation Figure 9 the network device shown can be Figures 4 to 6 any network device shown in the method shown, such as a mobility management network element, etc.

[0311] The transceiver module of part 31 is used to execute Figures 4 to 6 the steps related to the transceiver of any network device in the method shown; part 32 is used to execute Figures 4 to 6 the steps related to the processing of any network device in the method shown.

[0312] It should be understood that Figure 9 only as an example and not a limitation, the above network device including a transceiver module and a processing module may not depend on Figure 9 the structure shown.

[0313] When the device 30 is a chip, the chip includes a transceiver module and a processing module. Among them, the transceiver module can be an input / output circuit, a communication interface; the processing module is a processor, a microprocessor, or an integrated circuit integrated on the chip.

[0314] This application embodiment also provides a computer-readable storage medium, on which computer instructions for implementing the method executed by the network device in the above method embodiment are stored.

[0315] For example, when the computer program is executed by the computer, it enables the computer to implement the method executed by the network device in the above method embodiment.

[0316] An embodiment of the present application further provides a computer program product including instructions, which, when executed by a computer, cause the computer to implement the method executed by the first device or the method executed by the second device in the above method embodiments.

[0317] An embodiment of the present application further provides a communication system, which includes the network device in the above embodiments.

[0318] For the explanations and beneficial effects of the relevant content in any of the above provided devices, reference can be made to the corresponding method embodiments provided above, and details are not described herein again.

[0319] In an embodiment of the present application, the network device may include a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. Among them, the hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also referred to as main memory). The operating system in the operating system layer may be any one or more computer operating systems that implement service processing through processes. For example, the Linux operating system, the Unix operating system, the Android operating system, the iOS operating system, or the windows operating system, etc. The application layer may include applications such as a browser, an address book, a word processing software, and an instant messaging software.

[0320] The embodiment of the present application does not particularly limit the specific structure of the execution subject of the method provided in the embodiment of the present application. As long as it can communicate according to the method provided in the embodiment of the present application by running a program recording the code of the method provided in the embodiment of the present application. For example, the execution subject of the method provided in the embodiment of the present application may be a network device, or a functional module in the network device that can call and execute the program.

[0321] Each aspect or feature of the present application may be implemented as a method, a device, or an article of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein may cover a computer program accessible from any computer-readable device, carrier, or medium. For example, the computer-readable medium may include, but is not limited to: magnetic storage devices (such as hard disks, floppy disks, or magnetic tapes, etc.), optical discs (such as compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (such as erasable programmable read-only memories (EPROMs), cards, sticks, or key drives, etc.).

[0322] The various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable media" may include, but is not limited to: wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0323] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0324] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, the RAM may be used as an external cache. By way of example and not limitation, the RAM may include the following various forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0325] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, the memory (storage module) can be integrated in the processor.

[0326] It should also be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0327] Those of ordinary skill in the art can realize that the units and steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the protection scope of this application.

[0328] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the above-described devices and units can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0329] In several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of the devices or units can be in electrical, mechanical or other forms.

[0330] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place, or distributed to multiple network units. Some or all of the units can be selected according to actual needs to implement the solution provided in this application.

[0331] In addition, the functional units in each embodiment of this application can be integrated into one unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0332] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that the computer can access or a data storage device such as a server or data center that includes one or more integrated available media. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD), etc.). For example, the foregoing available media can include, but are not limited to: USB flash drives, external hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs and other media that can store program code.

[0333] As described above, the foregoing are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed in the present application should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims and the specification.

Claims

1. A method for satellite communication, characterized in that, comprising: A session management network element obtains an identifier list, and the identifier list includes identifier information of one or more terminal devices accessing the network through satellite backhaul; The session management network element configures a forwarding rule for a user plane network element on the satellite, and the forwarding rule is used to forward data packets to an internal interface of the user plane network element, wherein the destination address of the data packet is included in the addresses of one or more terminal devices corresponding to the identifier list.

2. The method according to claim 1, characterized in that, the session management network element obtaining the identifier list includes: The session management network element determines the identifier list according to a first identifier list of terminal devices that need to communicate and a second identifier list of terminal devices accessing the network through satellite backhaul.

3. The method according to claim 2, characterized in that, further comprising: The session management network element receives the first identifier list from an application function network element.

4. The method according to claim 1, characterized in that, the session management network element obtaining the identifier list includes: The session management network element receives the identifier list from a data management network element or a mobility management network element.

5. The method according to claim 4, characterized in that, before the session management network element receives the identifier list from the data management network element, the method further includes: The session management network element sends a request message to the data management network element, and the request message includes information related to the satellite, and the request message is used to request to obtain the identifier list.

6. The method according to claim 5, characterized in that, the relevant information can be any one of the following information: The data network access identifier corresponding to the satellite, the identifier of the satellite, the Internet protocol address of the satellite.

7. The method according to any one of claims 1 to 6, characterized in that, the method further includes: The session management network element receives a session context establishment request message from a mobility management network element, and the session context establishment request message includes identifier information of a first terminal device, and the first terminal device accesses the satellite through satellite backhaul; The session management network element obtains relevant information; The session management network element sends a registration message to the data management network element, and the registration message includes the identifier information of the first terminal device and the relevant information.

8. The method according to any one of claims 1-6, characterized in that, the method further includes: The session management network element determines to allow the first terminal device to perform local data exchange under the satellite.

9. The method according to claim 1 or 8, characterized in that, the identifier list includes identifier information of one or more terminal devices that support local data exchange under the satellite and access the satellite through satellite backhaul.

10. The method according to any one of claims 1 to 9, characterized in that, the method further includes: The session management network element sends a subscription message to the data management network element, and the subscription message includes the relevant information, and the subscription message is used to subscribe to a change notification of the identifier list.

11. The method according to any one of claims 1 to 10, wherein, the satellite feedback mode is geostationary orbit satellite feedback.

12. A communication device, wherein, the device includes a module for executing the method according to any one of claims 1 to 11.

13. A communication device, wherein, it includes: a processor for executing a computer program stored in a memory, so that the device executes the method according to any one of claims 1 to 11.

14. A computer program product, wherein, the computer program product includes instructions for executing the method according to any one of claims 1 to 11.

15. A computer-readable storage medium, wherein, it includes: the computer-readable storage medium stores a computer program; when the computer program runs on a computer, the computer is caused to execute the method according to any one of claims 1 to 11.

Images