Satellite communication method and apparatus

Abstract

The application provides a satellite communication method and device, the method can include: a session management network element acquires an identification list, the identification list includes identification information of one or more terminal devices accessing the satellite through a satellite backhaul mode; the session management network element configures a forwarding rule to a user plane network element on the satellite, the forwarding rule is used for shunting a data packet whose destination address contains an address of a terminal device corresponding to the identification list to an access network device corresponding to the terminal device. Through the above scheme, the terminal device supporting local data exchange under the satellite can communicate through the local data exchange under the satellite, thereby reducing the time delay and improving the user experience.

Description

[0001] This application is a divisional application, the original application's application number is 202210309468.3, the original application's original date is 2022-03-27, and the original application's entire content is incorporated by reference in this application. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, in particular to a satellite communication method and device. BACKGROUND

[0003] At present, an important scene in which satellite communication and 5G communication system (5th-generation mobile communication system, 5GS) fusion technology can be applied is satellite backhaul (satellite backhaul, SATB), that is, the satellite link is used as a 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 time delay is usually large, resulting in poor user experience. How to reduce the end-to-end transmission delay in the satellite communication scenario is a problem that needs to be considered. SUMMARY

[0004] The present application provides a satellite communication method and device, which can reduce the transmission delay between terminal devices in a satellite communication scenario.

[0005] In a first aspect, a satellite communication method is provided, which can be executed by a session management network element, or also can be executed by a component (such as a chip or circuit) of the session management network element, and no limitation is made in this regard. For ease of description, the following will be described by taking the execution by the session management network element as an example.

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

[0007] Based on the above scheme, the session management network element can configure a forwarding rule to the user plane network element on the satellite, so that the user plane network element sends data packets whose destination address contains an address of a terminal device corresponding to the identifier list to an access network device corresponding to the terminal device. That is, 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 going through the ground anchor access network device, so that the data transmission path can be shortened and the transmission delay can be reduced.

[0008] With reference to the first aspect, in some implementations of the first aspect, the session management network element obtaining the identifier list comprises: the session management network element receiving the identifier list from a data management network element or a mobility management network element.

[0009] Based on the above scheme, 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 to a user plane network element on the satellite according to the identifier list.

[0010] With reference to 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 comprises: the session management network element sending a request message to the data management network element, the request message comprising relevant information of the satellite, the request message being used for requesting to obtain the identifier list.

[0011] Based on the above scheme, 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 sends an identifier list corresponding to the relevant information of the satellite to the session management network element.

[0012] With reference to the first aspect, in some implementations of the first aspect, the method further comprises: the session management network element receiving a session context establishment request message from a mobility management network element, the session context establishment request message comprising identifier information of a first terminal device, the first terminal device accessing the satellite in a satellite backhaul manner; the session management network element obtaining relevant information of the satellite; the session management network element sending a registration message to the data management network element, the registration message comprising the identifier information of the first terminal device and the relevant information of the satellite.

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

[0014] With reference to the first aspect, in some implementations of the first aspect, the method further comprises: the session management network element determining that the first terminal device is allowed to perform local data exchange under the satellite.

[0015] Based on the above scheme, the session management network element can register the identifier information of the first terminal device and the related information of the satellite to the data management network element in a case where it is determined that the first terminal device supports local data exchange under the satellite, so that the identifier list can include identifier information of one or more terminal devices allowed to perform local data exchange under the satellite, thereby enabling the session management network element to configure a forwarding rule to the user plane network element on the satellite to implement local data exchange under the satellite for these terminal devices.

[0016] With reference to the first aspect, in some implementations of the first aspect, the session management network element obtains the related information of the satellite, including: the session management network element receiving the related information of the satellite from the mobility management network element.

[0017] With reference to the first aspect, in some implementations of the first aspect, the session management network element obtains the related information of the satellite, including: the session management network element determining the related information of the satellite according to the location information of the terminal device.

[0018] Based on the above scheme, the session management network element can obtain the identifier information of the satellite through the mobility management network element, or determine the related information of the satellite according to the identifier information of the terminal device, so as to obtain the identifier list corresponding to the related information of the satellite.

[0019] With reference to the first aspect, in some implementations of the first aspect, the method further includes: the session management network element sending a subscription message to the data management network element, the subscription message including the related information of the satellite, and the subscription message being used to subscribe to a change notification of the identifier list.

[0020] Based on the above scheme, the session management network element can subscribe to the change notification of the identifier list from the data management network element. That is, when a new terminal device is registered to the identifier list or the original terminal device is unregistered from the identifier 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 rule to the user plane network element on the satellite according to the updated session identifier list, so that the terminal device accessing the satellite through the satellite backhaul mode and supporting 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] With reference to the first aspect, in some implementations of the first aspect, the related information of the satellite can be any one of the following information: a data network access identifier corresponding to the satellite, an identifier of the satellite, and an Internet protocol address of the satellite.

[0022] In a second aspect, a satellite communication method is provided. The method can be performed by a mobile management network element, or can be performed by a component (e.g., a chip or a circuit) of the mobile management network element, without limitation. For ease of description, the method performed by the mobile management network element is described below.

[0023] The communication method includes: receiving, by the mobile management network element, an identifier list from a data management network element, the identifier list including identifier information of one or more terminal devices accessing the satellite via satellite backhaul; and sending, by the mobile management network element, the identifier list to a session management network element.

[0024] Based on the above scheme, the mobile management network element can provide the session management network element with an identifier list corresponding to the information related to the satellite, so that the session management network element can configure a forwarding rule to a user plane network element on the satellite according to the identifier list, so that the user plane network element sends a data packet whose destination address is included in the address of the terminal device corresponding to the identifier list to an access network device corresponding to the terminal device, thereby shortening the data transmission path and reducing the transmission delay.

[0025] In some implementations of the second aspect, before the mobile management network element receives the identifier list from the data management network element, the method further includes: sending, by the mobile management network element, a request message to the data management network element, the request message including information related to the satellite, the request message being used to request the identifier list.

[0026] Based on the above scheme, the mobile management network element can request the data management network element for an identifier list corresponding to the information related to the satellite, so as to provide the session management network element with the identifier list.

[0027] In some implementations of the second aspect, the method further includes: receiving, by the mobile management network element, a session establishment request message from a first terminal device, the session establishment request message including identifier information of the first terminal device, the first terminal device accessing the satellite via satellite backhaul; determining, by the mobile management network element, information related to the satellite according to location information of the first terminal device; and sending, by the mobile management network element, a registration message to the data management network element, the registration message including the identifier information of the first terminal device and the information related to the satellite.

[0028] Based on the above scheme, the mobile management network element can register the identifier information of the first terminal device and the information related to 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 identifier list corresponding to the information related to the satellite.

[0029] With reference to the second aspect, in some implementations of the second aspect, the method further includes: determining, by the session management network element, to allow the first terminal device to perform local data exchange under the satellite.

[0030] Based on the above scheme, the mobile management network element can register the identification information of the first terminal device to the data management network element in the case of determining to allow the first terminal device to perform local data exchange under the satellite, so that the terminal device corresponding to the identification list itself supports local data exchange under the satellite.

[0031] With reference to the second aspect, in some implementations of the second aspect, the method further includes: sending, by the mobile management network element, a subscription message to the data management network element, the subscription message including the related information of the satellite, the subscription message being used to subscribe to a change notification of the identification list.

[0032] Based on the above scheme, the mobile management network element can subscribe to the change notification of the identification list from the data management network element. That is, when a new terminal device is registered to the identification list or the original terminal device is unregistered from the identification list, the group management network element needs to notify the mobile management network element. Based on this, the mobile 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 rule to the user plane network element on the satellite according to the updated session identification list, so that the terminal device accessing the satellite through the satellite backhaul mode and supporting 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.

[0033] The third aspect provides a satellite communication method, which can be executed by a data management network element, or can also be executed by a component (such as a chip or a circuit) of the data management network element, and the implementation is not limited. For ease of description, the following takes the execution by the data management network element as an example for description.

[0034] The satellite communication method includes: receiving, by the data management network element, a request message from a first network element, the request message including related information of the satellite; determining, by the data management network element, an identification list corresponding to the identification information of the satellite according to the related information of the satellite, the identification list including identification information of one or more terminal devices accessing the satellite through a satellite backhaul mode; and in response to the request message, sending, by the data management network element, the identification list to the first network element.

[0035] Based on the above scheme, the data management network element can send the identifier 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 a forwarding rule to the user plane network element on the satellite according to the identifier list, so that the user plane network element sends the data packet containing the destination address to the access network device corresponding to the terminal device, thereby shortening the data transmission path and reducing the transmission delay.

[0036] Here, the first network element can be a session management network element or a mobile management network element.

[0037] In combination with the third aspect, in some implementations of the third aspect, the method further includes: the data management network element receives a registration message from the first network element, the registration message including the identifier information of the first terminal device and the related information of the satellite; and the data management network element saves the identifier information of the first terminal device in the identifier list.

[0038] Based on the above scheme, the first session management network element can register the identifier 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 updates the identifier list, thereby enabling the first terminal device to perform local data exchange under the satellite to reduce the transmission delay.

[0039] In combination with the third aspect, in some implementations of the third aspect, the method further includes: the data management network element receives a subscription message from the first network element, the subscription message including 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 scheme, the first network element can subscribe to the change notification of the identifier list from the data management network element. In this case, when the identifier list is updated, the data management network element can send the updated identifier list to the first network element, so that the session management network element can configure a new forwarding rule to the user plane network element on the satellite according to the updated identifier list.

[0041] In combination with the third aspect, in some implementations of the third aspect, the first network element is a session management network element or a mobile management network element.

[0042] In a fourth aspect, a communication apparatus is provided. The apparatus is configured to perform any of the methods provided in the first aspect to the third aspect. Specifically, the apparatus can include units and / or modules configured to perform the methods provided in the first aspect to the third aspect, such as a processing module and / or a transceiver module (also referred to as a communication module). In one implementation, the apparatus is a network device, e.g., the apparatus is a session management network element, or a mobility management network element, or a data management network element. When the apparatus is a network device, the communication module can be a transceiver, or an input / output interface; and the processing module can be a processor.

[0043] In one implementation, the apparatus is a chip, chip system, or circuitry for use in a network device. When the apparatus is a chip, chip system, or circuitry for use in a communication device, the communication module can be an input / output interface, interface circuitry, output circuitry, input circuitry, pin, or related circuitry, etc. on the chip, chip system, or circuitry; and the processing module can be a processor, processing circuitry, or logic circuitry, etc.

[0044] In one possible implementation, the apparatus is a session management network element, or a chip, chip system, or circuitry for use in a session management network element. In this case, the apparatus can include units and / or modules configured to perform the method provided in the first aspect, such as a processing unit and / or a communication unit.

[0045] In another possible implementation, the apparatus is a mobility management network element, or a chip, chip system, or circuitry for use in a mobility management network element. In this case, the apparatus can include units and / or modules configured to perform the method provided in the second aspect, such as a processing module and / or a transceiver module.

[0046] In yet another possible implementation, the apparatus is a data management network element, or a chip, chip system, or circuitry for use in a data management network element. In this case, the apparatus can include units and / or modules configured to perform the method provided in the third aspect, such as a processing module and / or a transceiver module.

[0047] In a fifth aspect, a communication apparatus is provided. The apparatus includes a memory configured to store a program, and a processor configured to execute the program stored in the memory. When the program stored in the memory is executed, the processor is configured to perform any of the methods provided in the first aspect to the third aspect.

[0048] In a sixth aspect, the present application provides a processor configured to perform the method of any of the above aspects. In performing the method, the processor outputs the information and receives the information as described above. In outputting the information, the processor outputs the information to a transceiver for transmission by the transceiver. The information can be further processed after being outputted by the processor and before being received by the transceiver. Similarly, in receiving the information, the processor receives the information from a transceiver. The information can be further processed after being received by the transceiver and before being inputted to the processor.

[0049] For example, the processor receives the information as described above.

[0050] For the transmission, sending, and receiving operations of the processor, if not specifically stated, or if not contrary to the actual role or inherent logic in the description, the processor can be more generally understood as outputting and receiving the information, rather than directly transmitting and receiving the information by the radio frequency circuit and the antenna.

[0051] In implementation, the processor can be a processor specially configured to perform the method, or a processor configured to execute computer instructions in a memory to perform the method, such as a general-purpose processor. The memory can be a non-transitory memory, such as a read only memory (ROM), which can be integrated on the same chip as the processor, or separately arranged on different chips. The type of the memory and the arrangement of the memory and the processor are not limited in the embodiments of the present application.

[0052] In a seventh aspect, a computer readable storage medium is provided, which stores program codes for execution by an apparatus. The program codes include codes for performing any of the methods of the first aspect to the third aspect.

[0053] In an eighth aspect, a computer program product including instructions is provided, which, when executed on a computer, causes the computer to perform any of the methods of the first aspect to the third aspect.

[0054] In a ninth aspect, a chip is provided, which includes a processor and a communication interface. The processor reads instructions stored on a memory through the communication interface, and performs any of the methods of the first aspect to the third aspect.

[0055] Optionally, as an implementation form, the chip can further include a memory in which instructions are stored, and the processor is configured to execute the instructions stored in the memory, and when the instructions are executed, the processor is configured to execute any method provided in the first aspect to the third aspect.

[0056] In a tenth aspect, a communication system is provided, including one or more of the session management network element, the mobility management network element, and the data management network element described above. BRIEF DESCRIPTION OF DRAWINGS

[0057] Figure 1 FIG. 1 is a schematic diagram of a network architecture suitable for embodiments of the present application;

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

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

[0060] Figure 4 FIG. 4 is a schematic flow diagram of a communication method provided by embodiments of the present application;

[0061] Figure 5 FIG. 5 is a schematic flow diagram of another communication method provided by embodiments of the present application;

[0062] Figure 6 FIG. 6 is a schematic flow diagram of still another communication method provided by embodiments of the present application;

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

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

[0065] Figure 9 FIG. 9 is a schematic block diagram of a communication device provided by still another embodiment of the present application. DETAILED DESCRIPTION

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

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

[0068] It can be understood that the various numerical numbers involved in the present application are only for the convenience of differentiation, and are not used to limit the scope of the present application. The size of the serial number of the above processes does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic.

[0069] The terms "first", "second", "third", "fourth" and other various terms labels in the specification and claims of the present application and the above drawings (if any) are used to distinguish similar objects, and do not necessarily mean a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not necessarily limit to those steps or units clearly listed, but can 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: 5th generation (5G) or new radio (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, 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 internet of things (IoT) communication system or other communication systems.

[0071] The technical solutions provided by the present application will be described below in conjunction with Figure 1The 5G system to which the embodiments of the present application are applicable is exemplified. It should be understood that the 5G system described herein is only an example and should not constitute any limitation on the present application.

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

[0073] As an exemplary illustration, Figure 1 (a) shows an architecture diagram of the 5G system 100 to which the embodiments of the present application are applicable. Figure 1 is a 5G network architecture diagram based on point-to-point interfaces. As shown in Figure 1 (a), the network architecture can include, but is not limited to, the following network elements (or referred to as functional network elements, functional entities, nodes, devices, etc.):

[0074] a (wireless) access network device (radio access network, (R)AN), an access and mobility management function (access and mobility management function, AMF) network element, a session management function (session management function, SMF) network element, a user plane function (user plane function, UPF) network element, a policy control function (policy control function, PCF) network element, a unified data management (unified data management, UDM) network element, an AF network element, a data network (data network, DN), a network slice selection function (network slice selection function, NSSF), an authentication server function (authentication server function, AUSF), a unified data management (unified data management, UDM), a BSF network element, a unified data repository (unified data repository, UDR), etc.

[0075] The network elements shown in Figure 1 (a) are briefly introduced as follows:

[0076] 1、User Equipment (UE): can be referred to as terminal equipment, terminal device, access terminal, subscriber unit, subscriber station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal equipment can be a device that provides voice / data connectivity to a user, such as a handheld device with wireless connection function, vehicle-mounted equipment, etc. At present, some examples of terminals can be: mobile phone, tablet computer, computer with wireless transceiver function (such as notebook computer, palm 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 wireless modem, vehicle-mounted device, wearable device, terminal device in 5G network or terminal device in future evolved public land mobile network (PLMN), etc.

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

[0078] In addition, the terminal device can also include a smart printer, a train detector, etc., and the 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 can be any device that can access the network. The terminal device and the access network device can communicate with each other using a certain air interface technology.

[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 equipment in V2X or D2D, etc. For example, a cell phone and a car communicate with each other using sidelink signals. The cell phone and the smart home device communicate without relaying the communication signal through the base station.

[0081] 2, (radio) access network ((R)AN) device: used to provide network access functions for authorized user equipment in a certain area, and can use different quality of service transmission tunnels according to the level of the user equipment, the demand of the service, etc.

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

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

[0084] In some deployments, a gNB can include a centralized unit (CU) and a DU. The gNB can also include an active antenna unit (AAU). The CU implements part of the functions of the gNB, and the DU implements part of the functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, implements the radio resource control (RRC), and the functions of the packet data convergence protocol (PDCP) layer. The DU is responsible for processing the physical layer protocol and real-time services, and implements the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. The AAU implements part of the physical layer processing functions, radio frequency processing, and related functions of the active antenna. Since the information of the RRC layer eventually becomes the information of the PHY layer, or is transformed from the information of the PHY layer, under this architecture, high-layer signaling, such as RRC layer signaling, can also be considered as being sent by the DU, or 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, the DU node, and the AAU node. In addition, the CU can be divided into an access network device in the radio access network (RAN), or can be divided into an access network device in the core network (CN), which is not limited in the present application.

[0085] In a satellite communication scenario, the wireless access network device can also be referred to as a wireless satellite access network site (or wireless satellite access network device, wireless satellite access network), a satellite access network site (or satellite access network device, satellite access network), or a satellite network site (or satellite network device, satellite network). The embodiments of the present application do not limit this. The satellite access network can have multiple deployment modes, for example: a PLMN has both a terrestrial 3GPP access network and a satellite 3GPP access network, and the two access networks have independent interfaces with the core network; for example: different core networks share the same satellite access network, and the shared satellite access network will contain the available PLMN in the broadcast system information; for example: 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; for example: the satellite in the sky is only responsible for signal transmission and does not have the function of an access network. In the above non-satellite backhaul scenario, the satellite can contain all or part of the function of the access network, and the present application does not limit this. 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 part of the function of the base station on the satellite, and all the related signaling and data processing of the access network is performed on the satellite. When part of the function of the base station is integrated on the satellite and part of the function is located on the ground, the satellite access network device can be understood as a device with part of the function of the base station on the satellite and a device with part of the function of the base station on the ground, and part of the related signaling and data processing of the access network is performed on the satellite and part of it is performed on the ground. In the satellite backhaul scenario, the satellite access network device can be understood as a base station on the ground, and all the related signaling and data processing of the access network is performed on the ground. The satellite transmits signaling and data between the terminal device and the satellite access network.

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

[0087] In the 5G communication system, the user plane network element can be a user plane function (UPF) network element. In future communication systems, the user plane network element can still be a UPF network element, or it can also have other names, which are not limited by the present application.

[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 in the MME function except for session management, such as access authorization / authentication functions, etc.

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

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

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

[0092] 6. Policy control function (PCF) network element: a unified policy framework for guiding network behavior, providing policy rule information for control plane function network elements (such as AMF, SMF, etc.).

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

[0094] 7. Application function (AF): used for data routing affected by applications, wireless access network exposure function network element, and policy framework interaction for policy control, etc.

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

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

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

[0098] 9. Authentication server function (AUSF) network element: used for authentication services, generating keys to achieve two-way authentication of user equipment, and supporting a unified authentication framework.

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

[0100] 10、network data analytics function (NWDAF) network element: used to identify network slice instances, load network slice instance load level information. Network data analysis function can make NF consumer subscribe or unsubscribe regular notification, and notify the consumer in case of exceeding the threshold.

[0101] In future communication systems, the network data analysis function network element 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): DN is a network outside the operator network, and the operator network can access multiple DNs. Multiple services can be deployed on the DN, and data and / or voice services can be provided for terminal devices. For example, the DN is a private network of a smart factory, and the sensors installed in the workshop of the smart factory can be terminal devices. The control server of 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 to obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions. For another example, the DN is an internal office network of a company, and the mobile phones or computers of the employees of the company can be terminal devices. The mobile phones or computers of the employees can access information and data resources on the internal office network of the company.

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

[0104] In Figure 1In the network architecture shown in (a), each network element can communicate with each other through the interface shown in the figure. As shown in the figure, the UE and the AMF can interact through the N1 interface, and the interaction message can be referred to as the N1 message (N1 Message) for example. The RAN and the AMF can interact through the N2 interface, which can be used for sending non-access stratum (NAS) messages and the like. The RAN and the UPF can interact through the N3 interface, which can be used for transmitting user plane data and the like. The SMF and the UPF can interact through the N4 interface, which can be used for transmitting information such as tunnel identification information of the N3 connection, data buffering indication information, and downlink data notification messages. The UPF and the DN can interact through the N6 interface, which can be used for transmitting user plane data and the like. The relationship between other interfaces and network elements is as follows Figure 1 In (a) of the foregoing, for brevity, the details are not described one by one.

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

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

[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 policies and access control related policies.

[0109] 3) N5: the interface between the AF and the PCF, used for application service request issuance and network event reporting.

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

[0111] ​​​​5) N11: interface between SMF and AMF, used for transferring PDU session tunnel information between RAN and UPF, transferring control message sent to UE, transferring radio resource control information sent to RAN, etc.

[0112] 6) N2: interface between AMF and RAN, used for transferring radio bearer control information from core network side to RAN, etc.

[0113] 7) N1: interface between AMF and UE, access independent, used for transferring QoS control rule to UE, etc.

[0114] 8) N8: interface between AMF and UDM, used for AMF to acquire access and mobility management related subscription data and authentication data from UDM, and AMF to register UE current mobility management related information to UDM, etc.

[0115] 9) N10: interface between SMF and UDM, used for SMF to acquire session management related subscription data from UDM, and SMF to register UE current session related information to UDM, etc.

[0116] 10) N35: interface between UDM and UDR, used for UDM to acquire user subscription data information from UDR.

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

[0118] 12) N12: interface between AMF and AUSF, used for AMF to initiate authentication procedure to AUSF, wherein SUCI can be carried as subscription identifier;

[0119] 13) N13: interface between UDM and AUSF, used for AUSF to acquire user authentication vector from UDM to perform authentication procedure.

[0120] It should be understood that the above naming is only defined for the purpose of distinguishing different functions, and should not constitute any limitation to the present application. The present application does not exclude the possibility of using other naming in 5G network and future other networks. For example, in future network, part or all of the above network elements can use the terms in 5G, or other names, etc. Figure 2 The interface names between the network elements in (a) are only an example, and the names of the interfaces in the specific implementation can be other names, which are not limited in the present application. In addition, the names of the messages (or signaling) transmitted between the above network elements are also only an example, and the functions of the messages themselves are not limited.

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

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

[0123] The network architecture and service scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. It can be known by those skilled in the art that, with the evolution of network architecture and the appearance of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0124] The various aspects or features of the embodiments of the present application can be implemented as a method, or by an apparatus or an article of manufacture of standard programming and / or engineering techniques. The term "article of manufacture" used in the present application encompasses a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, or magnetic tape), optical storage devices (e.g., compact disk (CD), digital versatile disk (DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card, stick, or key drive). In addition, 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 medium" 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] In order to facilitate the understanding of the technical solutions of the embodiments of the present application, before introducing the solutions of the embodiments of the present application based on the 5G architecture, first, some terms or concepts in 5G that may be involved in the embodiments of the present application, and network elements that may be involved in the present application but not shown in the above network architecture are described briefly.

[0126] 1. Satellite communication

[0127] Satellite communication technology refers to a technology that a wireless communication device on the ground accesses a network through a satellite, or a technology that wireless communication devices on the ground communicate through a satellite as a relay. Compared with a traditional mobile communication system, satellite communication has a wider coverage and can overcome natural geographical obstacles such as oceans, deserts, and mountains.

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

[0129] The present application mainly aims at the scenario in which the satellite link is used as a 5G backhaul link, as shown in FIG. 2, Figure 2 is a schematic diagram of a scenario in which satellite communication is integrated with a 5GS. As can be seen from Figure 1 , the satellite link is used as a 5G backhaul link, and the RAN is connected to the 5GC through the 5G backhaul link. The 5GC can include core network elements such as AMF, AF, and UPF, as shown in Figure 2 Figure 1

[0130] It should be noted that Figure 3 only one satellite is shown in FIG. 1, and in an actual communication scenario, there can be multiple satellites, and the types of the multiple satellites can be the same or different. There is a wireless link between different satellites, and the wireless link can complete signaling interaction and user data transmission between access network devices.

[0131] Different types of satellites have different orbit altitudes, and the coverage area, motion characteristics, and resulting propagation delay and jitter of the satellites can also be different. By way of example, satellites can be divided into geostationary equatorial orbit (GEO), low earth orbit (LEO) polar orbit constellation, mid earth orbit (MEO), and other satellites (Other SAT) according to orbit types.

[0132] 2. Satellite constellation

[0133] ​​A satellite constellation is a collection of satellites launched into orbit and capable of normal operation. It is usually a satellite network composed of satellites configured in a certain way. Major satellite constellations include the Global Positioning System (GPS) constellation, the GLONASS constellation, the Galileo constellation, and the BeiDou constellation.

[0134] The main constellation types 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] LEO (Leo-Orbital) and MEO (Medium-Orbital) tilted constellations do not involve the concept of a reverse seam. This means that when a constellation is classified as a LEO or MEO tilted constellation, there is no need to consider whether it supports a reverse seam. LEO (Leo-Orbital) and MEO (Medium-Orbital) polar constellations do involve the concept of a reverse seam. This means that when a constellation is classified as a LEO or MEO polar constellation, it is necessary to consider whether it supports a reverse seam.

[0137] 3. Astrological Calendar

[0138] Ephemeris, also known as ephemeris tables, almanacs, or calendars, is information used to determine the position of celestial bodies at any given time. Terminal devices can use satellite ephemeris data to search the network, thereby improving the user experience. Satellite ephemeris mainly includes orbital plane parameters and satellite level parameters.

[0139] It should be understood that in the embodiments of this application, satellite ephemeris may also be referred to as ephemeris parameter, satellite ephemeris parameter, satellite ephemeris parameter in satellite access network, satellite ephemeris parameter in satellite return, or other possible names, and this application does not limit it in this way.

[0140] 4. Satellite backhaul

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

[0142] The above Figure 5 The scenario to which the embodiments of the present application can be applied is introduced, and the basic concepts involved in the present application are also briefly introduced. The communication method and device provided by the present application will be described in detail below with reference to the drawings.

[0143] The embodiments shown below do not particularly limit the specific structure of the execution subject of the method provided by the embodiments of the present application, as long as the execution subject can communicate according to the method provided by the embodiments of the present application by running the program in which the code of the method provided by the embodiments of the present application is recorded. For example, the execution subject of the method provided by the embodiments of the present 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] In order to facilitate understanding of the embodiments of the present application, the following points are explained.

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

[0146] The information enabled by the information is referred to as to-be-enabled information. In the specific implementation process, there are many ways to enable the to-be-enabled information, for example, but not limited to, the to-be-enabled information can be directly enabled, such as the to-be-enabled information itself or the index of the to-be-enabled information. The to-be-enabled information can also be indirectly enabled by enabling other information, wherein the other information and the to-be-enabled information have an association relationship. The to-be-enabled information can also be enabled only in part, and the other part of the to-be-enabled information is known or agreed in advance. For example, the enabling of a specific information can also be realized by means of the arrangement order of each information agreed in advance (for example, the protocol stipulates), thereby reducing the enabling cost to a certain extent. At the same time, the common part of each information can be identified and uniformly enabled to reduce the enabling cost caused by separately enabling the same information.

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

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

[0149] Fourth, in the present application, "pre-configuration" can include pre-definition, for example, protocol definition. Wherein, "pre-definition" can be realized by pre-saving corresponding code, table or other means that can be used to indicate related information in the device (for example, including various network elements), the specific implementation of the present application is not limited.

[0150] Fifth, "save" involved in the embodiments of the present application can refer to saving in one or more memories. The one or more memories can be separately set or integrated in the encoder or decoder, processor or communication device. The one or more memories can be part of the separately set and part of the integrated in the decoder, processor or communication device. The type of memory can be any form of storage medium, which is not limited in the present application.

[0151] Sixth, the "protocol" involved in the embodiments of the present application can refer to the standard protocol in the communication field, which can include 5G protocol, new radio (NR) protocol and related protocols applied in future communication systems, which is not limited in the present application.

[0152] Seventh, the dashed box in the method flowchart of the drawing part of the present application specification represents an optional step.

[0153] The following will be described in detail with the interaction between network elements as an example. It should be understood that the terms and steps in the embodiments of the present application can be mutually referenced.

[0154] UE IP An exemplary flowchart of the method 400 provided by the embodiments of the present application is shown. The method 400 will be described exemplarily in combination with each step.

[0155] S401, the session management network element acquires an identification list.

[0156] Exemplarily, the identification list includes identification information of one or more terminal devices accessing a satellite through satellite backhaul, or in other words, the identification list includes identification information of one or more terminal devices accessing a network through satellite backhaul. The identification list corresponds to the related information of the satellite. The identification information of the terminal device can be an internet protocol (IP) address of the terminal device, that is, the identification list can be an IP list of the terminal device, or the identification information of the terminal device can also be other types of identification, such as a subscription permanent identifier (SUPI) of the terminal device, which is not limited in the present application. In an implementation manner, the one or more terminal devices support local data exchange under a satellite, in which case the identification list can also be described as: the identification list includes identification information of one or more terminal devices supporting local data exchange under a satellite and accessing the satellite through satellite backhaul.

[0157] The related information of the satellite can refer to any information associated with the satellite, for example, the related information of the satellite can be any one of the following information: a data network access identifier corresponding to the satellite, an identifier of the satellite, an internet protocol address of the satellite, which is not limited in the present application.

[0158] The specific implementation manner of the session management network element obtaining the identification list is exemplarily described below.

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

[0160] As another possible implementation manner, the mobile management network element can also request the data management network element to obtain the identification list, and then send the obtained identification list to the session management network element.

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

[0162] As a further possible implementation, the session management network element determines the list of identities of terminal devices that need to communicate (denoted as a first list of identities) and a list of identities of terminal devices that access the satellite via satellite backhauling (denoted as a second list of identities) as needed. For example, before S401, the session management network element receives the first list of identities from the application function network element; wherein the first list of identities comprises identity information of terminal devices that need to communicate. The terminal devices that need to communicate are, for example, terminal devices that need to participate in an online conference.

[0163] Then, the session management network element can obtain the second list of identities of terminal devices that access the satellite via satellite backhauling from the mobility management network element or the data management network element, or the second list of identities of terminal devices that access the satellite via satellite backhauling determined by the session management network element itself. The specific implementation manner can be referred to the above examples (i.e., the list of identities in the above examples corresponds to the second list of identities here).

[0164] Further, the session management network element determines the list of identities according to the first list of identities and the second list of identities. Exemplarily, the list of identities comprises identity information of terminal devices that are common in the first list of identities and the second list of identities, i.e., the list of identities comprises identity information of one or more terminal devices that need to communicate and access the satellite via satellite backhauling.

[0165] For example, the session management network element SMF receives the first list of identities {UE1-UE10} from the application function network element AF; the SMF obtains the second list of identities of terminal devices that access the satellite via satellite backhauling as {UE5-UE100}. Then, the SMF determines the list of identities as {UE5-UE10} according to the first list of identities and the second list of identities. That is, the communication of UE5-UE10 can be realized by local data exchange under the satellite in the present application, and the communication of UE1-UE4 can be realized by using the prior art, which is not described herein.

[0166] It should be understood that the data management network element pre-stores a correspondence between the relevant information of the satellite and the list of identities, wherein the terminal devices in the list of identities can be registered (or said to be saved) to the data management network element by the session management network element. The following is exemplarily described 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 comprises identity information of a first terminal device, wherein the first terminal device accesses the satellite via satellite backhauling. Wherein, the identity 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 the present application.

[0169] In an implementation, the first terminal device accesses the satellite in a geostationary orbit satellite backhaul mode, that is, the satellite backhaul mode of the first terminal device is a geostationary orbit satellite backhaul. In this implementation, the identity list can also be described as: the identity list includes identity information of one or more terminal devices accessing a geostationary orbit satellite in a geostationary orbit satellite backhaul mode.

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

[0171] For example, the session management network element can determine whether to allow the first terminal device to perform local data exchange under the satellite according to 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, which is not limited in the present application. 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 performs 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] For example, the registration message includes identity information of the first terminal device and related information of the satellite. Correspondingly, after receiving the registration message, the data management network element saves the identity information of the first terminal device and the related information of the satellite, or in other words, the data management network element saves the identity information of the first terminal device into an identity list corresponding to the related information of the satellite.

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

[0175] For example, the session management network element can obtain the related information of the satellite from the mobility management network element, or determine the related information of the satellite by itself.

[0176] As an example, the mobility management network element can carry the related information of the satellite in the session context establishment request message, and the session management network element obtains the related 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 can 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. For another example, the session management network element can determine the relevant information of the satellite according to the location information of the terminal device, the satellite backhaul type information, and constellation information of the satellite.

[0178] Similarly, if there is another terminal device (for example, a second terminal device) that can perform local data exchange under the satellite and accesses the satellite through the satellite backhaul, the session management network element establishes a session for the second terminal device 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 to the data management network element. The data management network element receives and saves the correspondence between the location information of the second terminal device and the relevant information of the satellite, or in other words, the data management network element saves the location information of the second terminal device to an identification list corresponding to the relevant information of the satellite. In this way, an identification list including the identification of one or more terminal devices that access the satellite through the satellite backhaul and support local data exchange under the satellite can be maintained at the data management network element.

[0179] Optionally, at S405, the session management network element sends a subscription message to the data management network element, the subscription message including the relevant information of the satellite, and the subscription message being used to subscribe to a change notification of the identification list. That is, 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 terminal device is registered to the satellite (i.e., a terminal device accesses the network through the satellite backhaul) or a terminal device is unregistered from the satellite (i.e., a terminal device no longer accesses the network through the 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 can also subscribe to the data management network element in an implicit manner, i.e., step 405 is not performed, which is not limited by the present application. It should be understood that the identification list can also be registered to the data management network element by the session management network element, and the specific implementation manner is similar to S402-S405, which is briefly described below.

[0181] Exemplarily, the mobile management network element receives a message including a session establishment request message from a first terminal device, the message further including identification information of the first terminal device, the first terminal device accessing the satellite through satellite backhaul. Then, the mobile management network element can optionally determine whether to allow the first terminal device to perform local data exchange under the satellite (similar to S403), and if so, the mobile management network element sends a registration message to the data management network element, the registration message including the identification information of the first terminal device and the related 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 related information of the satellite. Optionally, the mobile management network element can also send a subscription message to the data management network element to subscribe to the notification of changes in the identification list (similar to S405), which will not be described here.

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

[0183] Exemplarily, the forwarding rule is used to offload (or forward) data packets 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 the forwarding rule is used to offload data packets 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 the forwarding rule is used to offload data packets 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 the forwarding rule is used to offload data packets 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, and it is assumed that the identification list corresponding to the related 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 UE2 IP. When the user plane network element on the satellite receives the data packet, according to the forwarding rule, it is determined that the destination address of the data packet contains 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] Further, the forwarding rule is also used to offload data packets sent to the terminal device to the access network device corresponding to the terminal device. The above example is used for illustration, UE3 sends a data packet to UE1, and the destination address of the data packet is UE1 IP. When the user plane network element on the satellite receives the data packet, according to the forwarding rule, it is determined 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 embodiment of the forwarding rule can include two parts: a detection rule part and a forwarding rule part. The detection rule part is used to detect data packets that meet the conditions, that is, data packets whose destination addresses are addresses of terminal devices 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 scheme, the session management network element can configure the forwarding rule to the user plane network element on the satellite, so that the user plane network element sends data packets whose destination addresses contain addresses of terminal devices corresponding to the identification list to the access network device corresponding to the terminal device. That is, for the terminal devices in the identification list, the data packets sent to them can be directly sent to the corresponding access network device by the user plane network element on the satellite, without going through the ground anchor access network device, so that the data transmission path can be shortened and the transmission delay can be reduced.

[0187] The following describes the communication method provided by the embodiments of the present application based on the 5G system. It should be understood that the SMF1 in the method 500 and the method 600 can correspond to the session management network element in the method 400, the AMF1 in the method 500 and the method 600 can correspond to the mobility management network element in the method 400, the UDM / NRF in the method 500 and the method 600 can correspond to the data management network element in the method 400, and the UE ID list in the method 500 and the method 600 can correspond to the identification list in the method 400, so the descriptions in different embodiments can be referred to and supplemented.

[0188] gNB tunnel info An exemplary flowchart of the method 500 provided by the embodiments of the present application is shown. The method 500 is exemplarily described in combination with each step.

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

[0190] Exemplarily, UE1 sends a PDU session establishment (PDU session establishment request) request message to AMF1 through a NAS message. Specifically, for example, UE1 sends an AN message to gNB1, and the AN message carries a NAS message, and the NAS message includes a PDU session ID and a PDU session establishment request. After receiving the AN message from UE1, gNB1 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, S502, AMF1 determines a GEO SAT ID according to the UE location information.

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

[0193] In an implementation manner, AMF1 can also determine the satellite backhaul type of UE1. For example, AMF1 determines that UE1 accesses a network through a GEO satellite according to the gNB1 ID, and then AMF1 determines that the satellite backhaul type of UE1 is GEO SAT B. In another implementation manner, 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 a network through a GEO satellite backhaul.

[0194] Optionally, the AMF1 can also determine the constellation information of the satellite. For example, in one implementation, when different gNBs access different constellations, different gNB IDs / gNB IPs are adopted, the AMF1 can determine the constellation information of the UE1 according to the gNB1 ID / gNB1 IP; in another implementation, when different constellations adopt different frequency bands, the AMF1 can determine the constellation information of the UE1 according to the frequency used by the satellite.

[0195] S503, the AMF1 sends a create session management context request message to the SMF1. Correspondingly, the SMF1 receives the create session management context request message from the AMF1.

[0196] For example, after the AMF1 receives the PDU session establishment request from the UE1, the AMF1 sends a create session management context request (Nsmf_PDUSession_CreateSMContext request) message to the SMF1, which includes the SUPI, the PDU session ID, the location information of the UE, and the like.

[0197] It should be understood that if the AMF performs S502, the AMF1 can carry the GEO SAT ID in the create session management context request message.

[0198] Optionally, S504, the SMF1 selects a ground PSA.

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

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

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

[0202] In one implementation, the SMF1 obtains the subscription data of the UE1 through the UDM, and determines whether the UE1 is allowed to perform local data exchange under the satellite according to the subscription data.

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

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

[0205] Exemplarily, in a case that the SMF 1 determines to allow the UE 1 to perform the local data exchange under the satellite, the SMF 1 sends a query request message to the UDM / NRF, the query request message including the GEO SAT ID, the query request message being used to request querying a UE identity list corresponding to the GEO SAT ID, or in other words, the query request message being used to request querying a UE identity list of the UE connected to the GEO satellite corresponding to the GEO SAT ID, or in other words, the query request message being used to request querying an identity list of the UE connected to the GEO satellite corresponding to the GEO SAT ID and capable of performing the local switch under the satellite, or in other words, the query request message being used to request querying an identity list of the UE saved by the UDM / NRF and corresponding to the GEO SAT ID. The UE ID list includes one or more identities of the UE connected to the GEO satellite and capable of performing the local switch under the satellite. Wherein, the identity of the UE here can refer to an ID of the UE, or an IP of the UE, or other types of identities, which are not limited in the present application. That is, the identity list of the UE can be a UE ID list, or a UE IP list, or other types of lists, which are not limited in the present application. For the convenience of description, the identity list of the UE is taken as the UE ID list in the following description.

[0206] It should be understood that the SMF 1 can receive the GEO SAT ID from the AMF 1, or determine the GEO SAT ID by itself, for example, the SMF 1 determines the GEO SAT ID according to the location information of the UE 1, which is not limited in the present application.

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

[0208] Exemplarily, after the UDM / NRF receives the query request message from the SMF 1, 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 SMF 1, the query response message including the UE ID list. It should be understood that the UDM / NRF pre-stores the correspondence 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 the query request message from the SMF1, the UDM / NRF determines whether the query request message is the first query request, that is, the UDM / NRF determines whether there is another SMF querying the UE ID list corresponding to the GEO SAT 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 indicating that the query request is not the first query request. That is, the UDM / NRF does not return the UE ID list corresponding to the GEO SAT ID to the SMF1 at this time.

[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, in the case that the SMF1 determines to allow the UE to perform the 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 the local data exchange under the satellite, the SMF1 sends the identification of the UE and the identification of the satellite corresponding to the UE to the UDM / NRF.

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

[0215] It should also be understood that S508 can be performed before S506 or after S506, which is not limited in the present application.

[0216] It should also be understood that S508 can also be performed simultaneously with S506, for example, S508 and S506 can 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 the UDM / NRF receives 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 the registration request message from the SMF1, the GEO SAT ID and the UE1 ID are saved, or in other words, the correspondence between the GEO SAT ID and the UE1 ID is saved, or in other words, the UE1 ID is saved 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 the subscription message from the SMF1.

[0220] Exemplarily, the SMF1 can also send a subscription message to the UDM / NRF, the subscription message including the GEO SAT ID, and the subscription message being used to subscribe to the change notification of the UE ID list corresponding to the GEO SAT ID. That is, when the UE ID list corresponding to the GEO SAT ID is updated, the UDM / NRF sends a notification message to the SMF1. For example, when a certain UE is registered to the GEO SAT, or a certain UE is unregistered from the GEO SAT, the UDM / NRF sends a notification message to the SMF1, and carries the updated UE ID list in the 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 manner, for example, S510 is not performed, and the implicit subscription is indicated through S506 or S508, which is not limited in the present application.

[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 / diversion point. The GEO UPF corresponds to the GEO SAT ID.

[0224] Further, the SMF1 sends an N4 session establishment request message to the GEO UPF, and the N4 session establishment request message can include the UE ID list corresponding to the GEO SAT ID, so as to instruct the GEO UPF to perform local switch on the packet matched to the UE ID list, or in other words, instruct the GEO UPF to perform local switch on the packet whose destination address indicates the UE in the UE ID list.

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

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

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

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

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

[0230] Illustratively, the N2 PDU session request (N2 PDU session request) message includes N2 SM info, N1 SM container.

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

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

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

[0234] S517, the SMF 1 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 the SMF 1 receives the gNB tunnel info, the SMF 1 sends an N4 session modification request message to the GEO UPF, the N4 session modification request message including configuration information, the configuration information being used to instruct the GEO UPF to send the received packet, which needs to be sent to the UE corresponding to the UE ID list, to the gNB corresponding to the UE, or in other words, the configuration information being used to instruct the GEO UPF to send the packet, whose destination address points to the UE 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. Wherein, the N4 session ID corresponds to the PDU session ID.

[0237] Table 1

[0238] 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 Figure 6 Figure 7

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

[0240] Through the above scheme, the data forwarding rule for the UE in the UE ID list can be configured to the GEO UPF, so that the packet whose destination address points to any UE in the UE ID list can be directly sent to the corresponding gNB, thereby realizing the local data exchange of the UE in the UE ID list under the satellite, reducing the time delay 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. The following will be described in conjunction with an example.

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

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

[0244] Further, the SMF 2 sends an N4 session establishment request message to the GEO UPF, and the N4 session establishment request message includes the UE ID list to indicate that the GEO UPF sends the packet whose destination address is the UE in the UE ID list to the gNB corresponding to the UE. For example, the GEO UPF sends the data packet whose destination address is the IP of the UE 1 to the gNB 1.

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

[0246] Based on the above scheme, the SMF 1 can configure a forwarding rule to the GEO UPF, so that the GEO UPF sends the data packet whose destination address is the address of the UE corresponding to the UE ID list to the gNB corresponding to the UE. That is, for the UE in the UE ID list, the data packet sent to them can be directly sent to the corresponding gNB by the GEO UPF, without passing through the ground PSA, so that the data transmission path can be shortened and the transmission delay can be reduced.

[0247] Figure 7 An exemplary flowchart of the method 600 provided by the embodiments of the present application is shown. The method 600 is exemplarily described below in combination with each step.

[0248] It should be understood that S601-S602 are similar to S501-S502 in method 500, and for brevity, the detailed process is not described here.

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

[0250] In an implementation, AMF1 acquires subscription data of UE1 through UDM, and judges whether to allow UE1 to perform local data exchange under satellite according to the subscription data.

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

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

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

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

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

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

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

[0258] It should be understood that S604-S608 are similar to S506-S510 in method 500, and the difference is that S506-S510 in method 500 is performed by SMF1, and S604-S608 is performed by AMF1. For brevity, the detailed process is not described here.

[0259] 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 UE ID list is included in the create session management context request message.

[0261] It can be understood that in the method 600, the registration procedure can also be performed by the SMF. That is, after S606-S607 are not performed, the registration procedure to the UDM / NRF is performed by the SMF1 after S610, that is, the correspondence between the GEOSAT ID and the UE1 ID is registered to the UDM / NRF, and the specific description can be referred to S508-S509, and the simple description is 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. The registration request message contains the GEOSAT ID and the UE1 ID.

[0263] After the UDM / NRF receives the registration request message from the SMF1, the GEOSAT ID and the UE1 ID are saved.

[0264] Further, S610-S617 are similar to S504, S511-S517 in the method 500, and for brevity, the details are not described here.

[0265] Corresponding to the method provided in each of the above method embodiments, the embodiment of the present application also provides a corresponding device, which includes a module for executing the corresponding modules of each of the above 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 method embodiments are also applicable to the following device embodiments, and therefore, the details not described in detail can be referred to the above method embodiments, and for brevity, the details are not described here.

[0266] Figure 4 to Figure 6 is a schematic block diagram of a communication device 10 provided by the embodiment of the present application. The device 10 includes a processing module 11. Optionally, the device 10 can also include a transceiver module 12. The processing module 11 is used for data processing, and the transceiver module 12 can realize the corresponding communication function, or in other words, the transceiver module 12 is used for performing the receiving and transmitting related operations, and the processing module 11 is used for performing other operations in addition to receiving and transmitting. The transceiver module 12 can also be referred to as a communication interface or a communication unit.

[0267] Optionally, the device 10 can also include a storage module (not shown in the figure), which can be used to store instructions and / or data, and the processing module 11 can read the instructions and / or data in the storage module, so that the device realizes the actions of the equipment or network element in each of the above method embodiments. Figure 4 to Figure 6 Optionally, the device 10 can also include a storage module (not shown in the figure), which can be used to store instructions and / or data, and the processing module 11 can read the instructions and / or data in the storage module, so that the device realizes the actions of the equipment or network element in each of the above method embodiments.

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

[0269] The apparatus 10 can implement steps or procedures performed by a session management network element (e.g., an SMF) in the above method embodiments, where the processing module 11 can be configured to perform operations related to processing by the session management network element (e.g., an SMF) in the above method embodiments, and the transceiver module 12 can be configured to perform operations related to transmission and reception by the session management network element (e.g., an SMF) in the above method embodiments.

[0270] For example, the apparatus 10 can correspond to a session management network element in the method 400, or an SMF in the method 500 to the method 600. The apparatus 10 can include modules for performing the methods performed by the session management network element (or the SMF) in the above method embodiments. Also, the modules in the apparatus 10 and the other operations and / or functions described above are respectively configured to implement the corresponding procedures of the methods shown in the above method embodiments. Figure 4 to Figure 6 Figure 4 to Figure 6 For example, the apparatus 10 can correspond to a session management network element in the method 400, or an SMF in the method 500 to the method 600. The apparatus 10 can include modules for performing the methods performed by the session management network element (or the SMF) in the above method embodiments. Also, the modules in the apparatus 10 and the other operations and / or functions described above are respectively configured to implement the corresponding procedures of the methods shown in the above method embodiments.

[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 a satellite; and determine whether to allow a terminal device to access the services supported by the satellite according to the service information; and in a case where it is determined to allow the terminal device to access at least one of the services supported by the satellite, insert a user plane network element on the satellite into a user plane path of the terminal device.

[0272] The processing module 11 is configured to obtain an identifier list, where the identifier list includes identifier information of one or more terminal devices that access the satellite in a satellite backhaul manner; and configure a forwarding rule for a user plane network element on the satellite, where the forwarding rule is used to offload a data packet with a destination address included in an address of a terminal device corresponding to the identifier list to an access network device corresponding to the terminal device.

[0273] Optionally, the transceiver module 12 is specifically configured to receive the identifier list from a data management network element or a mobile 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 related information of the satellite, and the request message is used to request to obtain the identifier list.

[0275] ​Optionally, the transceiver 12 is further configured to receive a session context setup request message from a mobility management network element, the session context setup request message comprising identification information of a first terminal device, the first terminal device accessing the satellite through a satellite backhaul manner; the processing module 11 is further configured to obtain the related information of the satellite; and the transceiver 12 is further configured to send a registration message to the data management network element, the registration message comprising the identification information of the first terminal device and the related information of the satellite.

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

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

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

[0279] Optionally, the transceiver 12 is further configured to send a subscription message to the data management network element, the subscription message comprising the related information of the satellite, the subscription message being used to subscribe to a change notification of the identification list.

[0280] Optionally, the related information of the satellite can be any one of the following information: a data network access identifier corresponding to the satellite, an identification of the satellite, and an Internet protocol address of the satellite.

[0281] The apparatus 10 can implement steps or processes performed by a mobility management network element (or AMF) in the above method embodiments, wherein the transceiver 12 can be configured to perform transceiver-related operations of the mobility management network element (or AMF) in the above method embodiments, and the processing module 11 can be configured to perform processing-related operations of the mobility management network element (or AMF) in the above method embodiments.

[0282] For example, the apparatus 10 can correspond to a mobility management network element in the method 400 or an AMF in the method 500 to the method 600. The apparatus 10 can include modules for performing the method performed by the mobility management network element (or AMF) in the above method embodiments. Figure 4 to Figure 6 Figure 4 to Figure 6

[0283] ​​In a possible implementation, the transceiver 12 is configured to receive, from a data management network element, an identifier list corresponding to the relevant information of the satellite, the identifier list comprising one or more identifiers of terminal devices accessing the satellite via satellite backhauling; and send the identifier list to a session management network element.

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

[0285] Optionally, the transceiver 12 is further configured to receive, from a first terminal device, a session establishment request message comprising an identifier of the first terminal device, the first terminal device accessing the satellite via satellite backhauling; the processing module 11 is further configured to determine the relevant information of the satellite according to location information of the first terminal device; and the transceiver 12 is further configured to send, to the data management network element, a registration message comprising the identifier of the first terminal device and the relevant information of the satellite.

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

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

[0288] The apparatus 10 can implement steps or procedures performed by the group management network element (or UDM / NRF) in the above method embodiments, where the transceiver 12 can be configured to perform transceiver-related operations of the group management network element (or UDM / NRF) in the above method embodiments, and the processing module 11 can be configured to perform processing-related operations of the group management network element (or UDM / NRF) in the above method embodiments.

[0289] For example, the apparatus 10 can correspond to the group management network element in the method 400, or the UDM / NRF in the method 500 to the method 600. The apparatus 10 can include modules for performing the methods performed by the group management network element (or UDM / NRF) in the above method embodiments. Figure 8 For example, the apparatus 10 can correspond to the group management network element in the method 400, or the UDM / NRF in the method 500 to the method 600. The apparatus 10 can include modules for performing the methods performed by the group management network element (or UDM / NRF) in the above method embodiments. Figure 8 For example, the apparatus 10 can correspond to the group management network element in the method 400, or the UDM / NRF in the method 500 to the method 600. The apparatus 10 can include modules for performing the methods performed by the group management network element (or UDM / NRF) in the above method embodiments.

[0290] In a possible implementation, the transceiver 12 is configured to receive a request message from a first network element, the request message comprising satellite-related information; the processor 11 is configured to determine an identity list corresponding to the satellite-related information according to the satellite-related information, the identity list comprising one or more identity information of terminal devices accessing the satellite via satellite backhauling; and the transceiver 12 is further configured to send the identity list to the first network element.

[0291] Optionally, the transceiver 12 is further configured to receive a registration message from the first network element, the registration message comprising identity information of a first terminal device and the satellite-related information; and the processor 11 is further configured to save the identity information of the first terminal device in the identity list.

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

[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 performing the corresponding steps are described in detail in the above method embodiments, and thus will not be repeated here for brevity.

[0295] It should also be understood that the apparatus 10 is embodied in the form of functional modules. The term "module" herein can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and memory that execute one or more software or firmware programs, a combinational logic circuit, and / or other suitable components that provide the described functionality. In one optional example, those skilled in the art can understand that the apparatus 10 can be embodied as the mobility management network element in the above embodiments, and can be used to perform the processes and / or steps corresponding to the mobility management network element in the above method embodiments. Alternatively, the apparatus 10 can be embodied as the terminal device in the above embodiments, and can be used to perform the processes and / or steps corresponding to the terminal device in the above method embodiments. To avoid repetition, details are not repeated here.

[0296] The apparatus 10 of each of the above solutions has a 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. The 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, which respectively performs the transceiving operations and related processing operations in each method embodiment.

[0297] In addition, the transceiver module 12 can also be a transceiver circuit (for example, which 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 4 to Figure 6 The apparatus in the above solutions can be a network element or device in the foregoing embodiments, or a chip or chip system, such as a system on chip (SoC). The transceiver module can be an input / output circuit or a communication interface, and the processing module can be a processor or microprocessor integrated on the chip or an integrated circuit. In this regard, no limitation is made.

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

[0300] The apparatus 20 can include a processor 21 (which is an example of a processing module), which is configured to perform Figure 9 operations performed by a session management network element (such as an SMF) or a mobility management network element (such as an AMF) in the corresponding method in the above solutions. Optionally, the apparatus 20 can include a memory 22, and the processor 21 can execute instructions stored in the memory 22, so that the apparatus 20 implements operations performed by a session management network element (such as an SMF) or a mobility management network element (such as an AMF) in the corresponding method in the above solutions. Figure 9

[0301] ​Further, the apparatus 20 can further include a transceiver 23 (i.e., an example of a transceiving module). Further, the processor 21, the memory 22, and the transceiver 23 can communicate with each other through an internal connection path, and transfer control and / or data signals. The memory 22 is configured to store a computer program, and the processor 21 can be configured to invoke and execute the computer program stored in the memory 22, to control the transceiver 23 to receive signals, to control the transceiver 23 to send signals, and to complete the steps of the terminal device or the network device in the above method. The memory 22 can be integrated in the processor 21, or can be configured separately from the processor 21.

[0302] Optionally, if the communication apparatus 20 is a communication device, the transceiver 23 can include an input port and an output port, i.e., the transceiver 23 can be divided into a receiver and a transmitter. The receiver and the transmitter can be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as a transceiver.

[0303] Optionally, if the communication apparatus 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 functions of the transceiver 23 can be implemented by a transceiving circuit or a transceiving dedicated chip. The processor 21 can be implemented by a dedicated processing chip, a processing circuit, a processor, or a general-purpose chip.

[0305] As another implementation manner, a general-purpose computer can be used to implement the communication device provided in the embodiments of the present application. That is, 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] The concepts, explanations, detailed descriptions, and other steps related to the technical solutions provided in the embodiments of the present application involved in the apparatus 20 are described in the foregoing method or other embodiments, and are not repeated here.

[0307] Figure 4 to Figure 6 A simplified structural diagram of a network device 30 is shown. The network device includes a 31 part and a 32 part. The 31 part is mainly used for the transceiving of radio frequency signals and the conversion between radio frequency signals and baseband signals; the 32 part is mainly used for baseband processing, controlling the network device, etc. The 31 part can be commonly referred to as a transceiving module, a transceiver, a transceiving circuit, or a transceiver, etc. The 32 part is usually the control center of the network device, and can be commonly referred to as a processing module, which is configured to control the network device to perform the processing operations on the network device side in the foregoing method embodiments.

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

[0309] The 32 part 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 program in the memory to realize the baseband processing function and the control of the network device. If there are multiple single boards, the single boards can be interconnected to enhance the processing capability. As an optional implementation, multiple single boards can also share one or more processors, or multiple single boards can share one or more memories, or multiple single boards can share one or more processors at the same time.

[0310] For example, in an implementation, Figure 4 to Figure 6 The network device shown can be Figure 4 to Figure 6 Any network device in the method shown, such as a mobile management network element, etc.

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

[0312] It should be understood that ​ The network device described above, which includes a transceiver module and a processing module, can not depend on ​ The structure shown.

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

[0314] The embodiment of the application also provides a computer readable storage medium, which stores computer instructions for implementing the method executed by the network device in the method embodiment described above.

[0315] For example, when the computer program is executed by a computer, the computer can implement the method executed by the network device in the method embodiment described above.

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

[0317] The embodiment of the present application further provides a communication system comprising the network device in the above embodiment.

[0318] The explanations and beneficial effects of the related content in any of the above-provided devices can refer to the corresponding method embodiments provided above, and will not be repeated here.

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

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

[0321] Various aspects or features of the present application can be implemented as methods, apparatuses, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" used herein can encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, or magnetic strips), optical storage devices (e.g., compact disk (CD), digital versatile disk (DVD), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), card, stick, or key drive, etc.).

[0322] 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 medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and / or carrying instruction(s) and / or data.

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

[0324] It should also be understood that the memory mentioned in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically EPROM (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM). For example, the RAM can be used as an external cache. As an example but not limitation, the RAM can include the following various forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (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 processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated in the processor.

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

[0327] Those skilled in the art can appreciate that the units and steps of the examples described in combination with the embodiments disclosed herein can be realized by electronic hardware, or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software depends on the specific application and design constraints of the technical solution. The skilled person can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0328] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the above-described device and unit can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

[0329] In several embodiments provided in the present 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 only schematic. For example, the division of the units is only a logical function division, and actual implementation can have another division manner. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other form.

[0330] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or they can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to realize the scheme provided in the present application.

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

[0332] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented 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, all or part of the processes or functions described in the embodiments of the present application are generated. 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, a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media sets. The available media 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 not limited to: a variety of media that can store program codes such as a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0333] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within 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, include: The session management network element obtains an identifier list, which includes identifier information of one or more terminal devices that access the network via satellite backhaul. The session management network element configures forwarding rules to the user plane network element on the satellite. The forwarding rules are used to forward data packets to the internal interface of the user plane network element, wherein the destination address of the data packet is contained in the address 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 obtains an identifier list, including: The session management network element determines the identifier list based on a first identifier list of terminal devices that need to communicate and a second identifier list of terminal devices that access the network via satellite backhaul.

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

4. The method according to claim 1, characterized in that, 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.

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. The request message includes information related to the satellite and is used to request the identification list.

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

7. The method according to any one of claims 4 to 6, characterized in that, The method further includes: The session management network element receives a session context establishment request message from the mobility management network element. The session context establishment request message includes the identification information of the first terminal device, which accesses the satellite via 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. The registration message includes the identification 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 whether the one or more terminal devices are allowed to perform local data exchange under satellite.

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

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

11. The method according to any one of claims 1 to 10, characterized in that, The satellite backhaul method is geostationary orbit satellite backhaul.

12. A communication device, characterized in that, The apparatus includes a module for performing the method as described in any one of claims 1 to 11.

13. A communication device, characterized in that, include: A processor for executing a computer program stored in memory to cause the apparatus to perform the method as described in any one of claims 1 to 11.

14. A computer program product, characterized in that, The computer program product includes instructions for execution by a processor of the method as described in any one of claims 1 to 11.

15. A computer-readable storage medium, characterized in that, include: The computer-readable storage medium stores a computer program; when the computer program is run on a computer, it causes the computer to perform the method as described in any one of claims 1 to 11.

Images