Communication method and apparatus

Abstract

The application provides a satellite communication method and device. The method can include: a session management network element obtaining first service information, the service information being used to indicate one or more services supported by a satellite; the session management network element determining whether to allow a terminal device to access the services supported by the satellite according to the first 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, the session management network element inserting a user plane network element on the satellite into a user plane path of the terminal device. Based on the above scheme, the time delay of satellite communication of the terminal device can be reduced, and the user experience can be improved.

Description

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

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

[0003] Currently, a key application scenario for the convergence of satellite communication and 5G (5G mobile communications system) technologies is satellite backhaul (SATB), where the satellite link serves as the backhaul link, allowing access network equipment to communicate with core network equipment. In this scenario, user plane function (UPF) network elements can be deployed on the satellite to provide various service support. For example, an on-board UPF can be inserted into the user plane path to enable satellite edge computing or satellite local switching. However, current solutions that insert UPFs into the user plane path suffer from high user plane transmission latency and poor user experience. Summary of the Invention

[0004] This application provides a communication method and apparatus that determines whether to insert user plane network elements on the satellite into the user plane path of the terminal device based on whether the terminal device is allowed to access services on the satellite, thereby improving the user experience.

[0005] Firstly, a communication method is provided, which can be executed by a session management network element, or by a component of the session management network element (such as a chip or circuit), without limitation. For ease of description, the following explanation uses execution by a session management network element as an example.

[0006] The communication method includes: a session management network element acquiring service information, the service information indicating one or more services supported by the satellite; the session management network element determining, based on the service information, whether to allow a terminal device to access the services supported by the satellite; and, if it is determined that the terminal device is allowed to access at least one of the services supported by the satellite, the session management network element inserts a user plane network element on the satellite into the user plane path of the terminal device.

[0007] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: if it is determined that the terminal device is not allowed to access any of the services supported by the satellite, the session management network element does not insert the user plane network element on the satellite into the user plane path of the terminal device.

[0008] Based on the above scheme, when it is determined that the terminal device is allowed to access at least one of the satellite-supported services, the session management network element inserts the satellite user plane network element into the user plane path of the terminal device; when it is determined that the terminal device is not allowed to access any of the satellite-supported services, the satellite user plane network element is not inserted into the user plane path of the terminal device. Therefore, satellite user plane network elements can be inserted into the user plane path of terminal devices that require services from satellite user plane network elements, thus supporting these terminal devices' access to satellite services; while satellite user plane network elements are not inserted into the user plane path of terminal devices that do not require services from satellite user plane network elements, thereby shortening the length of the user plane path for these terminal devices, reducing transmission latency, and improving user experience.

[0009] In conjunction with the first aspect, in certain implementations of the first aspect, the session management network element obtains service information by: the session management network element determining a first data network access identifier based on the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device; and the session management network element determining the service information based on the first data network access identifier and first configuration information, wherein the first configuration information includes the correspondence between the first data network access identifier and the service information.

[0010] Based on the above scheme, the session management network element can first determine the first data network access identifier, and then determine the service information, i.e., determine the services supported by the satellite, according to the first data network access identifier and the first configuration information. Specifically, the session management network element can combine the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device to determine the first data network access identifier, so as to accurately determine the first data network access identifier corresponding to the satellite.

[0011] In conjunction with the first aspect, in certain implementations of the first aspect, the session management network element determines the first data network access identifier based on the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device, including: the session management network element determines one or more second data network access identifiers based on the location information of the terminal device; the session management network element determines the first data network access identifier from the one or more second data network access identifiers based on the satellite backhaul type information.

[0012] Based on the above scheme, the session management network element determines the first data network access identifier by combining the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device. Specifically, when the location information of the terminal device corresponds to one or more second data network access identifiers, the session management network element can further combine the satellite backhaul type information to determine the first data network access identifier corresponding to that satellite.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, the session management network element determines the data network access identifier based on the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device, including: the session management network element determines the data network access identifier based on the location information of the terminal device, the satellite backhaul type information and the constellation information of the satellite.

[0014] Based on the above scheme, the session management network element can determine the data network access identifier by combining the location information of the terminal device, the satellite backhaul type information, and the satellite constellation information. For example, when a terminal device has multiple backhaul links, there may be multiple data network access identifiers corresponding to the terminal device's location information and satellite backhaul type information. In this case, the data network access identifier corresponding to the satellite can be determined by combining the satellite constellation information, in order to determine the services supported by the satellite.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the session management network element determines the data network access identifier based on the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device, including: the session management network element determines the data network access identifier based on the location information of the terminal device, the satellite backhaul type information and the satellite identification information.

[0016] Based on the above scheme, the session management network element can determine the data network access identifier by combining the location information of the terminal device, the satellite backhaul type information, and the satellite identification information. For example, when a terminal device has multiple backhaul links, there may be multiple data network access identifiers corresponding to the terminal device's location information and satellite backhaul type information. In this case, the data network access identifier corresponding to the satellite can be determined by combining the satellite identification information, in order to determine the services supported by the satellite.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the session management network element obtains service information, including: the session management network element obtains the identification information of the satellite; the session management network element determines the service information based on the identification information of the satellite and second configuration information, wherein the second configuration information includes the correspondence between the identification information of the satellite and the service information.

[0018] Based on the above scheme, the session management network element can first obtain the satellite's identification information, and then determine the service information based on the satellite's identification information and the second configuration information, that is, determine the services supported by the satellite.

[0019] In conjunction with the first aspect, in certain implementations of the first aspect, the session management network element obtains the identification information of the satellite, including: the session management network element receives the identification information of the satellite from the mobility management network element.

[0020] Based on the above scheme, the session management network element can obtain the satellite's identification information through the mobility management network element, so that the session management network element can determine the service information based on the satellite's identification information.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, the session management network element obtains the identification information of the satellite, including: the session management network element determines the identification information of the satellite based on the location information of the terminal device and the constellation information of the satellite.

[0022] Based on the above scheme, the session management network element can determine the satellite identification information according to the location information and constellation information of the terminal device, so that the session management network element can determine the service information according to the satellite identification information.

[0023] In conjunction with the first aspect, in some implementations of the first aspect, the session management network element obtains service information, including: the session management network element obtains the constellation information of the satellite; the session management network element determines the service information based on the constellation information of the satellite and third configuration information, wherein the third configuration information includes the correspondence between the constellation information of the satellite and the service information.

[0024] Based on the above scheme, the session management network element can first determine the satellite constellation information, and then determine the service information based on the constellation information, that is, determine the services supported by the satellite. For example, when satellites within a constellation have the same capabilities, that is, support the same services, the services supported by the satellite can be determined based on the satellite constellation information.

[0025] In conjunction with the first aspect, in certain implementations of the first aspect, the session management network element determines whether to allow the terminal device to access the satellite-supported service based on the service information, including: the session management network element receiving subscription data from the data management network element of the terminal device; and the session management network element determining whether to allow the terminal device to access the satellite-supported service based on the subscription data and the service information.

[0026] Based on the above scheme, the session management network element can determine whether to allow the terminal device to access satellite-supported services based on the subscription data and service information. In this way, the session management network element can decide whether to insert the user plane network element on the satellite into the user plane path of the terminal device based on the judgment result.

[0027] In conjunction with the first aspect, in some implementations of the first aspect, the subscription data includes an identifier of a service that the terminal device is allowed to access; the session management network element determines whether to allow the terminal device to access the satellite-supported service based on the service information, including: if the service that the terminal device is allowed to access includes at least one service indicated by the service information, then the session management network element determines that the terminal device is allowed to access the satellite-supported service.

[0028] Based on the above scheme, if the services allowed for terminal device access indicated by the subscription data include at least one of the satellite-supported services, then the session management network element determines that the terminal device is allowed to access the satellite-supported services. In other words, in this case, the session management network element can insert the user plane network element on the satellite into the user plane path of the terminal device.

[0029] In conjunction with the first aspect, in certain implementations of the first aspect, the session management network element determines whether to allow the terminal device to access the satellite-supported service based on the service information, including: the session management network element receiving policy information of the terminal device from the policy control network element, the policy information including an identifier of the service that the terminal device is allowed to access; and the session management network element determining whether to allow the terminal device to access the satellite-supported service based on the policy information and the service information.

[0030] Based on the above scheme, the session management network element can determine whether to allow the terminal device to access satellite-supported services according to policies and service information, so that the session management network element can decide whether to insert the user plane network element on the satellite into the user plane path of the terminal device based on the judgment result.

[0031] In conjunction with the first aspect, in some implementations of the first aspect, the satellite backhaul type information indicates that the terminal device accesses the satellite via a geostationary orbit satellite backhaul.

[0032] Secondly, a communication method is provided, which can be executed by a mobility management network element, or by a component of the mobility management network element (such as a chip or circuit), without limitation. For ease of description, the following explanation uses execution by a mobility management network element as an example.

[0033] The communication method includes: the mobility management network element determining a first data network access identifier based on the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device; and the mobility management network element sending the first data network access identifier to the session management network element.

[0034] Based on the above scheme, the mobility management network element can provide the session management network element with a first data network access identifier, so that the session management network element can determine the services supported by the satellite accessed by the terminal device based on the first data network access identifier, and further decide whether to insert the user plane network element on the satellite into the user plane path of the terminal device based on the judgment of whether the terminal device is allowed to access the services on the satellite.

[0035] In conjunction with the second aspect, in some implementations of the second aspect, the mobility management network element determines the first data network access identifier based on the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device, including: the mobility management network element determines one or more second data network access identifiers based on the location information of the terminal device; the mobility management network element determines the first data network access identifier from the one or more second data network access identifiers based on the satellite backhaul type information.

[0036] Based on the above scheme, the mobility management network element determines the first data network access identifier by combining the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device. Specifically, when the location information of the terminal device corresponds to one or more second data network access identifiers, the mobility management network element can further combine the satellite backhaul type information to determine the first data network access identifier corresponding to that satellite.

[0037] In conjunction with the second aspect, in some implementations of the second aspect, the mobility management network element determines the first data network access identifier based on the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device, including: the mobility management network element determines the first data network access identifier based on the location information of the terminal device, the satellite backhaul type information corresponding to the terminal device, and the constellation information of the satellite.

[0038] Based on the above scheme, the mobility management network element can determine the data network access identifier by combining the location information of the terminal device, the satellite backhaul type information, and the satellite constellation information. For example, when a terminal device has multiple backhaul links, there may be multiple data network access identifiers corresponding to the terminal device's location information and satellite backhaul type information. In this case, the data network access identifier corresponding to the satellite can be determined by combining the satellite constellation information, in order to determine the services supported by the satellite.

[0039] In conjunction with the second aspect, in some implementations of the second aspect, the satellite backhaul type information indicates that the terminal device accesses the satellite via a geostationary orbit satellite backhaul.

[0040] Thirdly, a communication method is provided, characterized in that the method includes: the mobility management network element determining the identification information of the satellite accessed by the terminal device based on the location information of the terminal device; and the mobility management network element sending the identification information of the satellite to the session management network element.

[0041] Based on the above scheme, the mobility management network element can provide the satellite identification information to the session management network element, so that the session management network element can determine the services supported by the satellite accessed by the terminal device based on the satellite identification information, and further decide whether to insert the user plane network element on the satellite into the user plane path of the terminal device based on the judgment of whether the terminal device is allowed to access the services on the satellite.

[0042] Fourthly, a communication method is provided, characterized in that the method includes: a session management network element determining whether to allow a terminal device to perform local data exchange under satellite; if it is determined that the terminal device is allowed to perform local data exchange under satellite, the session management network element inserts a user plane network element on the satellite into the user plane path of the terminal device.

[0043] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: when it is determined that the terminal device is not allowed to perform local data exchange under satellite, the session management network element inserts the user plane network element on the satellite into the user plane path of the terminal device.

[0044] Based on the above scheme, when the terminal device needs to perform local data exchange under satellite, a user plane network element on the satellite can be inserted into the user plane path of the terminal device, thereby supporting the terminal device to perform local data exchange under satellite; when the terminal device does not need to perform local data exchange under satellite, a user plane network element on the satellite is not inserted into the user plane path of the terminal device, thereby shortening the length of the user plane path of these terminal devices, reducing transmission latency, and improving user experience.

[0045] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the session management network element determines whether to allow the terminal device to perform local data exchange under satellite, including: the session management network element receiving subscription data of the terminal device from the data management network element; and the session management network element determining whether to allow the terminal device to perform local data exchange under satellite based on the subscription data.

[0046] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the session management network element determines whether to allow the terminal device to perform local data exchange under satellite, including: the session management network element receiving policy information of the terminal device from the policy control network element; and the session management network element determining whether to allow the terminal device to perform local data exchange under satellite based on the policy information.

[0047] Fifthly, a communication apparatus is provided for performing any of the methods provided in the first to fourth aspects. Specifically, the apparatus may include units and / or modules for performing the methods provided in the first to fourth aspects, such as processing modules and / or transceiver modules (also referred to as communication modules). In one implementation, the apparatus is a network device, for example, a session management network element or a mobility management network element. When the apparatus is a network device, the communication module may be a transceiver, or an input / output interface; the processing module may be a processor.

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

[0049] In one possibility, the device is a session management network element, or a chip, chip system, or circuit within a session management network element. In this case, the device may include units and / or modules for performing the methods provided in the first or fourth aspect, such as processing units and / or communication units.

[0050] In another possibility, the device is a mobility management network element, or a chip, chip system, or circuit within a mobility management network element. In this case, the device may include units and / or modules for performing the methods provided in the second or third aspect, such as processing modules and / or transceiver modules.

[0051] A sixth aspect provides a communication device comprising: a memory for storing a program; and a processor for executing the program stored in the memory, wherein when the program stored in the memory is executed, the processor performs any of the methods provided in the first to fourth aspects.

[0052] Seventhly, this application provides a processor for executing the methods provided in the foregoing aspects. In executing these methods, the processes of sending and receiving the aforementioned information can be understood as the processor outputting the aforementioned information and the processor receiving the input information. When outputting the aforementioned information, the processor outputs the information to a transceiver for transmission. After being output by the processor, the information may require further processing before reaching the transceiver. Similarly, when the processor receives the input information, the transceiver acquires / receives the information and inputs it into the processor. Furthermore, after the transceiver receives the information, the information may require further processing before being input into the processor.

[0053] Based on the above principles, for example, the receiving request message mentioned in the aforementioned method can be understood as the processor receiving input information.

[0054] Unless otherwise specified, or unless it contradicts its actual function or internal logic in the relevant description, the operations of the processor, such as transmitting, sending, and receiving, can be more generally understood as processor output and receiving, input, etc., rather than transmission, sending, and receiving operations performed directly by radio frequency circuits and antennas.

[0055] In implementation, the processor can be a dedicated processor for executing these methods, or it can be a processor that executes computer instructions stored in memory to execute these methods, such as a general-purpose processor. The memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or disposed on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.

[0056] Eighthly, a computer-readable storage medium is provided that stores program code for execution by a device, the program code including methods for performing any of the methods provided in the first to fourth aspects above.

[0057] Ninth aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform any of the methods provided in the first to fourth aspects.

[0058] In a tenth aspect, a chip is provided, the chip including a processor and a communication interface, the processor reading instructions stored in a memory through the communication interface and executing any of the methods provided in the first to fourth aspects.

[0059] Optionally, as one implementation, the chip may further include a memory storing instructions, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to perform any of the methods provided in the first to fourth aspects described above.

[0060] Eleventhly, a communication system is provided, including one or more of the aforementioned session management network element and mobility management network element. Attached Figure Description

[0061] Figure 1 This is a schematic diagram of a network architecture applicable to embodiments of this application;

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

[0063] Figure 3 This is a schematic diagram of a communication architecture for satellite edge computing;

[0064] Figure 4 This is a schematic diagram of a communication architecture for satellite local data exchange;

[0065] Figure 5 This is a schematic block diagram illustrating a communication method provided in an embodiment of this application;

[0066] Figure 6 This is a schematic flowchart illustrating another communication method provided in an embodiment of this application;

[0067] Figure 7 This is a schematic flowchart illustrating another communication method provided in the embodiments of this application;

[0068] Figure 8 This is a schematic flowchart illustrating another communication method provided in the embodiments of this application;

[0069] Figure 9 This is a schematic flowchart illustrating another communication method provided in the embodiments of this application;

[0070] Figure 10 This is a schematic flowchart illustrating another communication method provided in the embodiments of this application;

[0071] Figure 11 This is a schematic block diagram of a communication device provided in one embodiment of this application;

[0072] Figure 12 This is a schematic block diagram of a communication device provided in another embodiment of this application;

[0073] Figure 13 This is a schematic block diagram of a communication device provided in another embodiment of this application. Detailed Implementation

[0074] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The specific operating methods in the method embodiments can also be applied to the device embodiments or system embodiments. In the description of this application, unless otherwise stated, "multiple" means two or more.

[0075] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0076] It is understood that the various numerical designations used in this application are merely for descriptive convenience and are not intended to limit the scope of this application. The order of the process numbers does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0077] The terms "first," "second," "third," "fourth," and other various terminology (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0078] The technical solutions provided in this application can be applied to various communication systems, such as 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems. Furthermore, the technical solutions provided in this 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 systems or other communication systems.

[0079] The following will combine Figure 1 Examples of 5G systems applicable to embodiments of this application are provided. It should be understood that the 5G systems described herein are merely examples and should not be construed as limiting this application in any way.

[0080] It should also be understood that some network elements in a 5G system can communicate using service-oriented interfaces or point-to-point interfaces. The following section will discuss this further. Figure 1 (a) and Figure 1 (b) introduces the 5G system framework based on point-to-point interface and the 5G system framework based on service interface, respectively.

[0081] As an example, Figure 1 Figure 1 (a) shows a schematic diagram of the architecture of a 5G system 100 to which embodiments of this application apply. Figure 1 This is a schematic diagram of a 5G network architecture based on a point-to-point interface. Figure 1 As shown in (a), the network architecture may include, but is not limited to, the following network elements (or functional network elements, functional entities, nodes, devices, etc.):

[0082] The network includes radio access network (R)AN, access and mobility management function (AMF) network elements, session management function (SMF) network elements, user plane function (UPF) network elements, policy control function (PCF) network elements, unified data management (UDM) network elements, AF network elements, data network (DN), network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM), BSF network elements, unified data repository (UDR), etc.

[0083] The following is about Figure 1 A brief introduction to each network element shown in (a):

[0084] 1. User Equipment (UE): This can also be called terminal equipment, terminal device, access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device. Terminal equipment can be a device that provides voice / data connectivity to users, such as a handheld device with wireless connectivity, vehicle-mounted equipment, etc. Currently, examples of terminals include: mobile phones, tablets, computers with wireless transceiver capabilities (such as laptops and PDAs), mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a mobile network (PLMN), etc.

[0085] Furthermore, terminal devices can also be terminal devices in Internet of Things (IoT) systems. IoT is an important component of future information technology development. Its main technical characteristic is connecting objects to networks through communication technologies, thereby realizing an intelligent network that enables human-machine interconnection and machine-to-machine interconnection. IoT technology can achieve massive connectivity, deep coverage, and low power consumption at the terminal level through technologies such as narrowband (NB).

[0086] In addition, terminal devices may also include smart printers, train detectors, etc. Their main functions include collecting data (for some terminal devices), receiving control information and downlink data from network devices, and sending electromagnetic waves to transmit uplink data to network devices.

[0087] It should be understood that a user equipment can be any device capable of accessing a network. Terminal devices and access network devices can communicate with each other using some form of air interface technology.

[0088] Alternatively, the user equipment (UE) can be used to act as a base station. For example, the UE can act as a scheduling entity, providing sidelink signaling between UEs in V2X or D2D, etc. For instance, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices can communicate without relaying communication signals through a base station.

[0089] 2. Radio access network (RAN) equipment: used to provide network access functionality for authorized user equipment in a specific area, and can use transmission tunnels with different service quality according to the user equipment level, service requirements, etc.

[0090] (R)AN can manage radio resources, 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. (R)AN can also be understood as a base station in a traditional network.

[0091] For example, the access network device in this application embodiment can be any kind of communication device with wireless transceiver function for communicating with user equipment. The access network device includes, but is not limited to, an evolved NodeB (eNB) or 5G, such as NR, a gNB in ​​the system, or a transport point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or it can also be a network node constituting a gNB or transport point, such as a baseband unit (BBU) or a distributed unit (DU), etc.

[0092] In some deployments, a gNB may include a centralized unit (CU) and a dedicated unit (DU). The gNB may also include an active antenna unit (AAU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions. The DU handles physical layer protocols and real-time services, implementing radio link control (RLC), media access control (MAC), and physical (PHY) layer functions. The AAU implements some physical layer processing functions, radio frequency processing, and active antenna-related functions. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can be considered to be sent by the DU, or by the DU+AAU. It is understood that access network equipment can be one or more of the following: CU nodes, DU nodes, and AAU nodes. In addition, the CU can be classified as an access network device in the radio access network (RAN) or as an access network device in the core network (CN), and this application does not limit this.

[0093] In satellite communication scenarios, wireless access network equipment can also be referred to as a wireless satellite access network site (or wireless satellite access network equipment, wireless satellite access network), a satellite access network site (or satellite access network equipment, satellite access network), or a satellite network site (or satellite network equipment, satellite network). This application does not limit this specific terminology. Satellite access networks can be deployed in various ways. For example, a single PLMN may simultaneously possess both a terrestrial 3GPP access network and a satellite 3GPP access network, with each access network having independent interfaces with the core network. Another example is that different core networks share the same satellite access network, and the shared satellite access network includes available PLMNs in the broadcast system information. Yet another example is that the terrestrial access network and satellite access network are independent, meaning that the terrestrial access network and satellite access network correspond to independent PLMNs. Yet another example is that satellites in the sky are only responsible for signal transmission and do not have access network functionality; in this scenario, satellite access can also be referred to as satellite backhaul. In the aforementioned non-satellite backhaul scenarios, satellites may include all or part of the access network functionality, and this application does not limit this specific terminology. When all base station functions are integrated on a satellite, the satellite access network equipment can be understood as equipment that performs some of the base station functions on the satellite; all signaling and data processing related to accessing the network is performed on the satellite. When some base station functions are integrated on the satellite and others are located on the ground, the satellite access network equipment can be understood as equipment that performs some of the base station functions on both the satellite and the ground; some signaling and data processing related to accessing the network is performed on the satellite, and some is performed on the ground. During satellite backhaul, the satellite access network equipment can be understood as a ground-based base station; all signaling and data processing related to accessing the network is performed on the ground, and the satellite transmits signaling and data between the terminal equipment and the satellite access network.

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

[0095] In 5G communication systems, this 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 have other names; this application does not limit this.

[0096] 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. It can be used to implement other functions in the MME besides session management, such as access authorization / authentication.

[0097] In future communication systems, the access and mobility management equipment may still be an AMF, or may have other names; this application does not limit this.

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

[0099] In future communication systems, the session management network element can still be an SMF network element, or it can have other names; this application does not limit this.

[0100] 6. Policy control function (PCF) network element: A unified policy framework used to guide network behavior, providing policy rule information to control plane function network elements (such as AMF, SMF, etc.).

[0101] In future communication systems, the policy control network element can still be a PCF network element, or it can have other names; this application does not limit this.

[0102] 7. Application Function (AF): Used for data routing affected by applications, opening up functional network elements in wireless access networks, and interacting with the policy framework for policy control, etc.

[0103] In future communication systems, the application network element can still be an AF network element, or it can have other names; this application does not limit this.

[0104] 8. Unified Data Management (UDM) network element: used to handle UE identification, access authentication, registration, and mobility management, etc.

[0105] In future communication systems, unified data management can still be a UDM network element, or it can have other names; this application does not limit this.

[0106] 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.

[0107] In future communication systems, the authentication server function network element can still be an AUSF network element, or it can have other names; this application does not limit this.

[0108] 10. Network Data Analytics Function (NWDAF): This network element is used to identify network slice instances and load their load level information. The NWDAF allows NF consumers to subscribe to or unsubscribe from periodic notifications and to receive notifications when thresholds are exceeded.

[0109] In future communication systems, the network data analysis function network element can still be an NWDAF network element, or it can have other names; this application does not limit this.

[0110] 11. Data Network (DN): A DN is a network located outside the carrier's network. Multiple DNs can be connected to the carrier's network, and various services can be deployed on a DN, providing data and / or voice services to terminal devices. For example, a DN might be the private network of a smart factory. Sensors installed in the workshop can act as terminal devices, and a control server for these sensors is deployed within the DN. The control server provides services to the sensors. Sensors can communicate with the control server, receive instructions from it, and transmit the collected sensor data back to the control server accordingly. Another example is a DN serving as an internal office network for a company. Employees' mobile phones or computers can act as terminal devices, accessing information and data resources on the company's internal office network.

[0111] Figure 1 In (a), Nausf, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers can be found in the definitions in the 3GPP standard protocols, and are not limited here.

[0112] exist Figure 1In the network architecture shown in (a), network elements can communicate with each other through the interfaces shown in the figure. As shown, the UE and AMF can interact through the N1 interface, and the interaction message can be called an N1 message. The RAN and AMF can interact through the N2 interface, which can be used to send non-access stratum (NAS) messages. The RAN and UPF can interact through the N3 interface, which can be used to transmit user plane data. The SMF and UPF can interact through the N4 interface, which can be used to transmit information such as tunnel identification information for N3 connections, data buffer indication information, and downlink data notification messages. The UPF and DN can interact through the N6 interface, which can be used to transmit user plane data. The relationships between other interfaces and network elements are as follows: Figure 1 As shown in (a), for the sake of brevity, not all details are provided here.

[0113] like Figure 1 As shown in (b), this is a schematic diagram of a 5G network architecture based on a point-to-point interface. For a description of the functions of the network elements, please refer to [reference needed]. Figure 1 The functions of the network elements corresponding to (a) will not be described in detail here. Figure 1 (b) and Figure 1 The main difference between (a) and (b) is: Figure 1 The interfaces between the network elements in (b) are point-to-point interfaces, not service-oriented interfaces.

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

[0115] 1) N7: The interface between PCF and SMF, used to issue protocol data unit (PDU) session granularity and business data stream granularity control strategies.

[0116] 2) N15: The interface between PCF and AMF, used to issue UE policies and access control related policies.

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

[0118] 4) N4: The interface between SMF and UPF, used to transmit information between the control plane and the user plane, including the distribution of forwarding rules, QoS control rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.

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

[0120] 6) N2: The interface between AMF and RAN, used to transmit radio bearer control information from the core network side to the RAN.

[0121] 7) N1: The interface between AMF and UE, access-independent, used to transmit QoS control rules to UE, etc.

[0122] 8) N8: The interface between AMF and UDM, used by AMF to obtain access and mobility management related subscription data and authentication data from UDM, and by AMF to register UE's current mobility management related information with UDM.

[0123] 9) N10: The interface between SMF and UDM, used by SMF to obtain session management-related subscription data from UDM, and by SMF to register UE current session-related information with UDM.

[0124] 10) N35: The interface between UDM and UDR, used by UDM to obtain user subscription data information from UDR.

[0125] 11) N36: The interface between PCF and UDR, used by PCF to obtain policy-related contract data and application data related information from UDR.

[0126] 12) N12: The interface between AMF and AUSF, used by AMF to initiate the authentication process to AUSF, which can carry SUCI as the signing identifier;

[0127] 13) N13: The interface between UDM and AUSF, used by AUSF to obtain the user authentication vector from UDM in order to execute the authentication process.

[0128] It should be understood that the above naming is defined solely for the purpose of distinguishing different functions and should not constitute any limitation on this application. This application does not preclude the possibility of using other naming conventions in 5G networks and other future networks. For example, in 6G networks, some or all of the above-mentioned network elements may use the terminology from 5G, or they may use other names, etc. Figure 1 The interface names between the network elements in (a) are merely examples; in actual implementations, the interface names may be different, and this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0129] It is understood that the aforementioned network elements or functions can be network components in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). For ease of explanation, this application will subsequently use the network device as the Access and Mobility Management (AMF) network element and the base station as the Radio Access Network (RAN) as an example.

[0130] It should be understood that the network architecture described above for the embodiments of this application is merely an example, and the network architecture applicable to the embodiments of this application is not limited thereto. Any network architecture capable of realizing the functions of the above-described network elements is applicable to the embodiments of this application.

[0131] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

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

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

[0134] 1. Satellite communication

[0135] Satellite communication technology refers to the technology by which terrestrial wireless communication devices access networks via satellite, or the technology by which terrestrial wireless communication devices communicate with each other using satellites as relays. Compared to traditional mobile communication systems, satellite communication has advantages such as wider coverage and the ability to overcome natural geographical obstacles such as oceans, deserts, and mountains.

[0136] based on Figure 1 The communication system architecture shown can integrate satellite communication with the 5G 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 a 3GPP access point, 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 network (5G core, 5GC) through the backhaul link (e.g., the backhaul link provides bearer for N3 or N9).

[0137] This application is primarily aimed at... Figure 2 The scenario shown illustrates a satellite link used as a 5G backhaul link. Figure 2 This is a schematic diagram illustrating a scenario where satellite communication and 5GS are integrated. From Figure 2 As can be seen, the satellite link serves as the 5G backhaul link, and the RAN connects to the 5GC via the 5G backhaul link. The 5GC can include, for example, Figure 1 The core network elements shown are AMF, AF, UPF, etc.

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

[0139] Different types of satellites, due to their varying orbital altitudes, may differ in coverage area, motion characteristics, and the resulting propagation delays and jitter. For example, satellites can be categorized by orbital type into geostationary equatorial orbit (GEO), low earth orbit (LEO) polar orbit constellations, medium earth orbit (MEO) satellites, and other satellites (SAT).

[0140] 2. Zodiac information.

[0141] 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.

[0142] Common constellation types include: low Earth orbit (LEO) polar orbit constellations, medium Earth orbit (MEO) polar orbit constellations, LEO inclined orbit constellations, and MEO inclined orbit constellations.

[0143] Constellation information refers to information related to satellite constellations, primarily including orbital plane parameters and satellite level parameters. In some contexts, constellation information can also be referred to as ephemeris information.

[0144] 3. Satellite edge computing

[0145] Deploying edge services on satellites enables satellite edge computing. For example... Figure 3 As shown, the UE establishes a PDU session, with the user plane path being UE, RAN, GEO UPF (i.e., L-PSA in the diagram), and terrestrial PSA (the user plane path is shown by the dotted line in the diagram). The UPF deployed on the satellite enables satellite edge computing (EC). This allows data packets from the UE accessing onboard EC services to be directly routed to the edge computing platform via the onboard UPF. This avoids the previous method of sending packets to the terrestrial PSA first, and then from the terrestrial PSA to the edge computing platform, thus reducing the user plane path, reducing service communication latency, and improving user experience.

[0146] 4. Satellite local switching

[0147] By deploying a UPF on a satellite, local switching, or local data exchange under the satellite, can be enabled. For example... Figure 4As shown, UE1 establishes PDU session-1 via satellite backhaul, with the user plane path being UE, RAN1, GEO UPF-1, and (optional) terrestrial PSA-1 (as shown by the dashed line in the figure); UE2 establishes PDU session-2 via satellite backhaul, with the user plane path being UE, RAN2, GEO UPF-2, and (optional) terrestrial PSA-2 (as shown by the dashed line in the figure). GEO UPF-1 and GEO UPF-2 can be the same or different. Enabling direct communication between UE1 and UE2 through the onboard UPFs (i.e., GEO UPF-1 and GEO UPF-2), i.e., local switching, shortens the communication path between UE1 and UE2, improving the user experience.

[0148] The above text combined Figure 1 The application has introduced the scenarios in which the embodiments of this application can be applied, and also briefly introduced the basic concepts involved in this application. The communication method and device provided by this application will be described in detail below with reference to the accompanying drawings.

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

[0150] To facilitate understanding of the embodiments of this application, the following points are provided.

[0151] First, in this application, "for instruction" can be understood as "enabling," and "enabling" can include direct enabling and indirect enabling. When describing information for enabling A, it can include whether the information directly enables A or indirectly enables A, but it does not necessarily mean that the information carries A.

[0152] The information that enables the information is called the information to be enabled. In the specific implementation process, there are many ways to enable the information to be enabled, such as, but not limited to, directly enabling the information to be enabled, such as the information to be enabled itself or its index. It can also be indirectly enabled by enabling other information, where there is a relationship between the other information and the information to be enabled. It can also enable only a part of the information to be enabled, while the other parts are known or pre-agreed upon. For example, enabling specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing enabling overhead to some extent. Simultaneously, common parts of various pieces of information can be identified and enabled uniformly to reduce the enabling overhead caused by individually enabling the same information.

[0153] Second, the first, second, and various numerical designations (e.g., "#1", "#2", etc.) shown in this application are merely for descriptive convenience and to distinguish objects, and are not intended to limit the scope of the embodiments of this application. For example, to distinguish different messages, etc., rather than to describe a specific order or sequence. It should be understood that such described objects can be interchanged where appropriate to describe solutions other than those in the embodiments of this application.

[0154] Third, the terms “comprising” and “having” and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such process, method, product or device.

[0155] Fourth, in this application, "pre-configuration" may include pre-defined terms, such as protocol definitions. These "pre-defined terms" can be implemented by pre-storing corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including various network elements). This application does not limit the specific implementation method.

[0156] Fifth, the term "storage" in the embodiments of this application can refer to storage in one or more memories. These memories can be separate installations or integrated into an encoder, decoder, processor, or communication device. Alternatively, some memories can be separately installed, while others can be integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0157] Sixth, the “protocol” involved in the embodiments of this application may refer to standard protocols in the field of communication, such as 5G protocols, new radio (NR) protocols, and related protocols applied in future communication systems. This application does not limit this.

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

[0159] The following describes in detail the communication method provided in the embodiments of this application, taking the interaction between network elements as an example. It should be understood that the terms and steps in the various embodiments of this application can be referenced to each other.

[0160] Figure 5Figure (a) shows an exemplary block diagram of method 500(a) provided in an embodiment of this application. It should be understood that method 500(a) can be executed by a session management network element or by a component (e.g., a chip or circuit) configured in the session management network element, and this application does not limit it. For convenience, the following description uses the execution of method 500(a) by a session management network element as an example.

[0161] S501, the session management network element obtains service information.

[0162] For example, this service information is used to indicate one or more services supported by the satellite, or in other words, the service information includes information about one or more services supported by the satellite. Services can be represented by service identifiers. Service identifiers can be represented by at least one of the following: application identifier (App ID), fully qualified domain name (FQDN), internet protocol (IP) 5-tuple, IP triplet, data network network (DNN), single network slice selection assistance information (S-NSSAI), etc. As a specific example, the service information can be described as one or more FQDNs supported by the satellite; as another specific example, the service information can be described as one or more App IDs supported by the satellite; and yet another specific example, the service information can be described as one or more (DNN, S-NSSAI) supported by the satellite.

[0163] The satellite here can refer to the satellite that the terminal device accesses, or in other words, the terminal device accesses the satellite through satellite backhaul.

[0164] The following is an exemplary description of the specific implementation method for the session management network element to obtain service information. In one implementation, the session management network element determines a first data network access identifier based on the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device. Alternatively, the session management network element determines a first data network access identifier corresponding to the location information of the terminal device and the satellite backhaul type information, or, based on the location information of the terminal device, determines the first data network access identifier of the terminal device accessing the core network via satellite backhaul. For example, the session management network element determines one or more second data network access identifiers based on the location information of the terminal device, and then determines the first data network access identifier from among these one or more second data network access identifiers based on the satellite backhaul type information corresponding to the terminal device. This first data network access identifier corresponds to the satellite. That is, the session management network element may determine multiple second data network access identifiers based on the location information of the terminal device, and then, based on the satellite backhaul type information of the terminal device, determines the first data network access identifier corresponding to the satellite from among these multiple second data network access identifiers. The satellite backhaul type information is used to indicate which satellite backhaul type the terminal device uses to access the satellite. For example, the satellite backhaul type information is used to instruct the terminal device to access the satellite via geostationary orbit satellite backhaul. It should be understood that the session management network element can obtain the location information of the terminal device and the corresponding satellite backhaul type information from the mobility management network element. For example, the session management network element receives a Create Session Management Context Request message from the mobility management network element, which includes the terminal device's identification information, location information, and corresponding satellite backhaul type information. The session management network element obtains the terminal device's location information and corresponding satellite backhaul type information from this Create Session Management Context Request message.

[0165] Furthermore, the session management network element determines the service information based on the first data network access identifier and the first configuration information. The first configuration information includes the correspondence between the first data network access identifier and the service information.

[0166] It should be understood that the session management network element pre-stores the first configuration information before S501. For example, prior to the above scheme, the session management network element receives the first configuration information from the application function network element and then stores the first configuration information.

[0167] Optionally, in this implementation, the session management network element may also require other factors to determine the first data network access identifier. For example, the session management network element determines the first data network access identifier based on the location information of the terminal device, the satellite backhaul type information corresponding to the terminal device, and the constellation information of the satellite. As another example, the session management network element determines the first data network access identifier based on the location information of the terminal device, the satellite backhaul type information corresponding to the terminal device, and the identification information of the satellite. It should be noted that when the terminal device has multiple backhaul links, there may be multiple data network access identifiers corresponding to the location information and satellite backhaul type information of the terminal device. In this case, combining the satellite constellation information or the satellite identification information can determine the data network access identifier corresponding to that satellite.

[0168] It should be understood that in this example, the constellation information of the satellite can be determined by the session management network element, or the constellation information of the satellite can be determined by the mobility management network element and then sent to the session management network element; this application does not impose any limitation on this. For example, when access network devices use different identification information when accessing different constellations, the session management network element can determine the constellation information of the satellite based on the identification information of the access network device corresponding to the terminal device. The identification information of the access network device can refer to the transport layer identification information of the access network device, or it can be the identification of the access network device itself. As another example, when different constellations use different frequency bands, the session management network element can determine the constellation information of the satellite based on the frequency used by the satellite. Alternatively, the mobility management network element can determine the constellation information using the above scheme and then send it to the session management network element; this application does not impose any limitation on this.

[0169] Similarly, in the above example, the satellite identification information can be determined by the session management network element, or the satellite identification information can be determined by the mobility management network element and then sent to the session management network element; this application does not limit this. For example, the session management network element can determine the satellite identification information corresponding to the location information of the terminal device based on the location information of the terminal device. It should be understood that, in one implementation, the session management network element pre-sets the correspondence between the location information of the terminal device and the satellite identification information. Alternatively, the mobility management network element can determine the satellite identification information through the above scheme and then send it to the session management network element; this application does not limit this.

[0170] In another implementation, the session management network element obtains the satellite's identification information and then determines the service information based on the satellite's identification information and the second configuration information, wherein the second configuration information includes the correspondence between the satellite's identification information and the service information.

[0171] It should be understood that in this implementation, the satellite's identification information can be determined by the session management network element, or it can be determined by the mobility management network element and then sent to the session management network element; this application does not limit this. For specific implementation methods, please refer to the examples above.

[0172] In another implementation, the session management network element obtains the satellite constellation information and then determines the service information based on the satellite constellation information and third configuration information. The third configuration information includes the correspondence between the satellite constellation information and the service information. For example, in a scenario where any satellite within a constellation corresponds to the same service, the session management network element can determine the service information supported by the satellite based on its constellation information.

[0173] It should be understood that in this implementation, the satellite constellation information can be determined by the session management network element, or the satellite constellation information can be determined by the mobility management network element and then sent to the session management network element; this application does not limit this. For specific implementation methods, please refer to the examples above.

[0174] S502, the session management network element determines whether to allow terminal devices to access satellite-supported services based on service information.

[0175] For example, in one implementation, the session management network element receives subscription data from the data management network element for the terminal device, and then determines whether to allow the terminal device to access satellite-supported services based on the subscription data and service information. For instance, the subscription data includes identifiers of services that the terminal device is allowed to access; if the services that the terminal device is allowed to access include at least one service indicated by the service information, then the session management network element determines that the terminal device is allowed to access satellite-supported services.

[0176] Therefore, based on the above scheme, the session management network element determines whether to allow the terminal device to access satellite-supported services according to the service information. This can include: the session management network element determining whether to insert the user plane network element on the satellite into the user plane path of the terminal device based on the first data network access identifier, the first configuration information, and the subscription data of the terminal device.

[0177] In another implementation, the session management network element receives policy information from the policy control network element for the terminal device, and then determines whether to allow the terminal device to access satellite-supported services based on the policy information and the service information. For example, the policy information includes identifiers of services that the terminal device is allowed to access; if the services that the terminal device is allowed to access include at least one service indicated by the service information, the session management network element determines that the terminal device is allowed to access satellite-supported services.

[0178] Therefore, based on the above scheme, the session management network element determines whether to allow the terminal device to access satellite-supported services according to the service information. This may include: the session management network element determining whether to insert the user plane network element on the satellite into the user plane path of the terminal device according to the first data network access identifier, the first configuration information and the policy information of the terminal device.

[0179] S503, if it is determined that the terminal device is allowed to access at least one of the services supported by the satellite, the session management network element inserts the user plane network element on the satellite into the user plane path of the terminal device.

[0180] For example, in one scenario (denoted as Scenario 1), when it is determined that the terminal device is allowed to access at least one of the satellite-supported services, or when it is determined that the services allowed for the terminal device to access include at least one of the satellite-supported services, or when it is determined that the services allowed for the terminal device to access overlap with at least one of the satellite-supported services, the session management network element inserts a user plane network element on the satellite into the user plane path of the terminal device. This user plane network element on the satellite can serve as a routing point, a local anchor user plane network element, or a session anchor user plane network element; this application does not limit this. Wherein, when the user plane network element on the satellite serves as a local anchor user plane network element, the terminal device's session is established, and there are two user plane paths: terminal device - access network device - user plane network element on the satellite - service platform, and terminal device - access network device - user plane network element on the satellite - ground anchor user plane network element; when the user plane network element on the satellite serves as a session anchor user plane network element, the terminal device's session is established, and there is one user plane path: terminal device - access network device - user plane network element on the satellite - service platform. It should be understood that when a session management network element inserts a user plane network element from the satellite into the user plane path of a terminal device, it can mean that the session management network element inserts a user plane network element from the satellite into the user plane path of the terminal device as a splitting point and / or a local anchor point. Alternatively, it can mean that the session management network element uses a user plane network element from the satellite as a session anchor point.

[0181] Furthermore, if the user plane network element on the satellite serves as a splitter and / or a local anchor user plane network element, the session management network element selects a ground anchor user plane network element for the terminal device's session. That is, in Case 1, if the session management network element determines that the terminal device is allowed to access at least one of the services supported by the satellite, the session management network element inserts the user plane network element on the satellite into the terminal device's user plane path, and then selects a ground anchor user plane network element for the terminal device's session.

[0182] Optionally, this case also includes S504, where the session management network element sends traffic redirection rules to the user plane network element on the satellite.

[0183] For example, after the session management network element inserts the user plane network element on the satellite into the user plane path of the terminal device, it sends a traffic steering rule to the user plane network element on the satellite. This traffic steering rule can also be called a data forwarding rule, routing rule, etc., and is not limited thereto in this application. This traffic steering rule instructs the user plane network element on the satellite to directly send data packets for services on the satellite to the corresponding service platform. For example, this steering rule instructs the user plane network element on the satellite to directly send data packets for edge computing services on the satellite to the corresponding edge computing platform. Correspondingly, based on this traffic steering rule, after receiving data packets for edge computing services on the satellite, the user plane network element on the satellite directly sends the data packets to the corresponding service platform, without first sending the data packets to the ground core network equipment, which then sends them to the corresponding service platform. This reduces latency and improves user experience.

[0184] In another case (referred to as Case 2), if it is determined that the terminal device is not allowed to access any of the satellite-supported services, or if it is determined that the services that the terminal device is allowed to access do not include any of the satellite-supported services, or if it is determined that the services that the terminal device is allowed to access do not overlap with any of the satellite-supported services, the session management network element will not insert the user plane network element on the satellite into the terminal device's user plane path.

[0185] Furthermore, the session management network element selects a ground anchor user plane network element for the terminal device's session. That is, in case 2, if the session management network element determines that the terminal device is not allowed to access any of the services supported by the satellite, the session management network element does not insert the user plane network element on the satellite into the terminal device's user plane path, but directly selects a ground anchor user plane network element for the terminal device's session.

[0186] It should be understood that Situation 1 and Situation 2 above are two parallel solutions, or rather, two branches of a complete solution. That is, for a given terminal device, both Situation 1 and Situation 2 may occur. Specifically, if the session management network element determines that the terminal device is allowed to access at least one of the satellite-supported services, the session management network element executes the solution corresponding to Situation 1; if the session management network element determines that the terminal device is not allowed to access any of the satellite-supported services, the session management network element executes the solution corresponding to Situation 2.

[0187] Based on the above scheme, when it is determined that the terminal device is allowed to access at least one of the satellite-supported services, the session management network element inserts the satellite user plane network element into the terminal device's user plane path; when it is determined that the terminal device is not allowed to access any of the satellite-supported services, the satellite user plane network element is not inserted into the terminal device's user plane path. Therefore, satellite user plane network elements can be inserted into the user plane paths of terminal devices that require satellite user plane network element services, thus supporting these terminal devices' access to satellite services; while satellite user plane network elements are not inserted into the user plane paths of terminal devices that do not require satellite user plane network element services, thereby shortening the length of the user plane paths of these terminal devices, reducing transmission latency, and improving user experience.

[0188] Figure 5 Figure (b) shows an exemplary block diagram of method 500(b) provided in an embodiment of this application. It should be understood that method 500(b) can be executed by a session management network element or by a component (e.g., a chip or circuit) configured in the session management network element, and this application does not limit it. For convenience, the following description uses the execution of method 500(b) by a session management network element as an example.

[0189] S510, the session management network element determines whether to allow terminal devices to conduct local data exchange under satellite.

[0190] As one possible implementation, the session management network element determines whether to allow the terminal device to perform local data exchange under satellite based on the terminal device's subscription data or policy information. The subscription data or policy information may include local data exchange indication information. For example, the session management network element obtains the terminal device's subscription data through the data management network element, and then determines whether to allow the terminal device to perform local data exchange under satellite based on the local data exchange indication information in the subscription data. This local data exchange indication information is used to indicate whether the terminal device is allowed to perform local data exchange under satellite. As one possible implementation, this local data exchange indication information can take different values ​​to indicate different situations. For example, when the local data exchange indication information is 1, it indicates that the terminal device is allowed to perform local data exchange under satellite; when the local data exchange indication information is 0 (or empty), it indicates that the terminal device is not allowed to perform local data exchange under satellite.

[0191] S520: When the session management network element determines that the terminal device is allowed to conduct local data exchange under satellite, it inserts the user plane network element on the satellite into the user plane path of the terminal device.

[0192] For example, in one scenario (denoted as scenario a), if it is determined that the terminal device is allowed to access local data exchange under the satellite, or in other words, if it is determined that the terminal device supports local data exchange under the satellite, the session management network element inserts the user plane network on the satellite into the user plane path of the terminal device. This user plane network element on the satellite can serve as a routing point, a local anchor user plane network element, or a session anchor user plane network element; this application does not limit the scope of the application.

[0193] Furthermore, the session management network element selects a ground anchor user plane network element for the terminal device's session. That is, in case a, if the session management network element determines that the terminal device is allowed to perform local data exchange under satellite, the session management network element inserts the user plane network element on the satellite into the terminal device's user plane path, and then selects a ground anchor user plane network element for the terminal device's session.

[0194] Optionally, in this case, it also includes S530, whereby the session management network element sends traffic redirection rules to the user plane network element on the satellite.

[0195] For example, after the session management network element inserts the satellite-based user plane network element into the user plane path of the terminal device, it sends a traffic redirection rule to the satellite-based user plane network element. This traffic redirection rule instructs the satellite-based user plane network element to send data packets destined for the satellite-based terminal device to the corresponding terminal device via satellite local data exchange. Alternatively, it instructs the satellite-based user plane network element to send data packets with destination addresses pointing to the satellite-based terminal device to the access network device corresponding to the terminal device. Correspondingly, based on this traffic redirection rule, when the satellite-based user plane network element receives a data packet destined for a terminal device connected to the satellite, it directly sends the data packet to the corresponding access network device, thereby shortening the data transmission path and improving user experience. In another case (denoted as case b), if it is determined that the terminal device is not allowed to access satellite-based local data exchange, or if it is determined that the terminal device does not support satellite-based local data exchange, the session management network element does not insert the satellite-based user plane network element into the user plane path of the terminal device.

[0196] Furthermore, the session management network element selects a ground anchor user plane network element for the terminal device's session. That is, in case b, if the session management network element determines that the terminal device is not allowed to perform local data exchange under satellite, the session management network element does not insert the satellite user plane network element into the terminal device's user plane path, but directly selects a ground anchor user plane network element for the terminal device's session.

[0197] It should be understood that scenarios a and b above are two parallel solutions. That is, for a given terminal device, either scenario a or scenario b may occur. Specifically, if the session management network element determines that the terminal device is allowed to perform local data exchange under satellite, the session management network element executes the solution corresponding to scenario a; if the session management network element determines that the terminal device is not allowed to perform local data exchange under satellite, the session management network element executes the solution corresponding to scenario b.

[0198] Based on the above scheme, when the terminal device needs to perform local data exchange under satellite, a user plane network element on the satellite can be inserted into the user plane path of the terminal device, thereby supporting the terminal device to perform local data exchange under satellite; when the terminal device does not need to perform local data exchange under satellite, a user plane network element on the satellite is not inserted into the user plane path of the terminal device, thereby shortening the length of the user plane path of these terminal devices, reducing transmission latency, and improving user experience.

[0199] The following describes the communication method provided in the embodiments of this application, based on a 5G system. In one implementation, the SMF in methods 600 to 1000 can correspond to the Session Management Network element in method 500, the AMF in methods 600 to 1000 can correspond to the Mobility Management Network element in method 500, the UE in methods 600 to 1000 can correspond to the terminal device in method 500, and the DNAI in methods 600 to 1000 can correspond to the Data Network Access Identifier in method 500. Methods 500 to 1000 can be applied to... Figure 1 or Figure 2 In the network architecture shown.

[0200] Figure 6 An exemplary flowchart of a method 600 provided in an embodiment of this application is shown. The method 600 is described below with reference to each step.

[0201] S601, SMF obtains the correspondence between DNAI and business information.

[0202] For example, the correspondence between the DNAI and service information can be understood as the service deployment information corresponding to the satellite. This service information indicates one or more services supported by the satellite. In one implementation, the service information may include FQDNs corresponding to different services; that is, the correspondence between the DNAI and service information can be a correspondence between the DNAI and one or more FQDNs. The DNAI is used to identify the user plane connection used to access the services supported by the satellite. For example, in a satellite edge computing scenario, the service may refer to the EC service. In this case, the DNAI can be understood as the location information of the EC platform, or as an identifier for accessing the user plane connection corresponding to the EC platform.

[0203] For ease of explanation, the satellite involved in the embodiments of this application is a GEO satellite as an example.

[0204] In one implementation, the SMF obtains the mapping between the DNAI and the service information through the AF (Active Request). For example, the AF sends an AF request message to the SMF via the NEF / PCF, which includes the mapping between the DNAI and the service information. After receiving the AF request message, the SMF stores the mapping between the DNAI and the service information locally. In another implementation, the SMF obtains the mapping between the DNAI and the service information through local configuration information.

[0205] It should be understood that this application does not limit the specific timing of S601 execution, but S601 should be executed before S602.

[0206] S602, the UE sends a PDU session establishment request to the AMF. Correspondingly, the AMF receives the PDU session establishment request from the UE.

[0207] For example, the UE sends a PDU session establishment request to the AMF via a NAS message. Specifically, the UE sends an AN message to the gNB, which carries a NAS message including the PDU session ID and a PDU session establishment request. After receiving the AN message from the UE, the gNB sends an N2 message to the AMF, which includes the PDU session ID, the UE location information (ULI), and the session establishment request. The UE location information identifies the UE's current geographical location.

[0208] It should be understood that the aforementioned PDU session establishment request can also be replaced by a PDU session modification request or a PDU session release request, etc., and this application does not limit it. That is to say, the solution provided in the embodiments of this application can be applied to the UE's PDU session establishment process, or PDU session modification process, or PDU session release process.

[0209] S603, the AMF sends a Create Session Management Context Request message to the SMF. Correspondingly, the SMF receives the Create Session Management Context Request message from the AMF.

[0210] For example, after the AMF receives a PDU session establishment request from the UE, it sends a Create Session Management Context Request (Nsmf_PDUSession_CreateSMContext request) message to the SMF. This Create Session Management Context Request message includes the UE's location information.

[0211] If the AMF determines that the UE accesses the network via satellite backhaul (SATB), the AMF will include satellite backhaul type information in the Create Session Management Context Request message. This satellite backhaul type information is used to indicate the backhaul type of the satellite the UE accesses. For example, this satellite backhaul type information is used to indicate that the UE accesses the GEO satellite via the GEO satellite backhaul type.

[0212] S604, SMF determines the DNAI corresponding to the UE's location information and satellite backhaul type information.

[0213] For example, after obtaining the UE's location information and satellite backhaul type information from the Create Session Management Context Request message, the SMF determines the corresponding DNAI based on the UE's location information and satellite backhaul type information.

[0214] As one possible implementation, the SMF locally stores configuration information, which can be pre-configured to the SMF or obtained by the SMF from other network elements. This configuration information includes the correspondence between the UE's location information, satellite backhaul type information, and DNAI. The SMF determines the DNAI based on the obtained UE location information, satellite backhaul type information, and this configuration information.

[0215] Optionally, the SMF determines the DNAI based on the UE's location information, satellite backhaul type information, and constellation information. For example, in one scenario, the UE's location information may correspond to multiple constellations. In this case, the SMF needs to first obtain the UE's constellation information, and then determine the corresponding DNAI based on the UE's location information, satellite backhaul type information, and constellation information. This application does not limit the implementation method of the SMF obtaining the UE's constellation information. Two possible examples are given below: In one implementation, when the gNB accesses different constellations and uses different gNB IDs / gNB IPs, the SMF can determine the satellite constellation information based on the gNB ID / gNB IP; in another implementation, different constellations use different frequency bands, and the SMF can determine the satellite constellation information based on the frequency used by the satellite. It should be understood that the AMF can also determine the UE's constellation information and then send it to the SMF; this application does not limit this.

[0216] S605, SMF obtains satellite-supported service information.

[0217] For example, after the SMF determines the DNAI, it determines the satellite-supported service information based on the DNAI and the correspondence between the DNAI and service information obtained in S601.

[0218] S606, SMF determines whether the UE is allowed to access satellite-supported services.

[0219] For example, the SMF can first determine the service information that the UE is allowed to access through the UDM or PCF.

[0220] For example, the SMF obtains the UE's subscription data through the UDM, which includes identifiers of services the UE is allowed to access. This subscription data could refer to Session Management Subscription Data. Specifically, the SMF sends a subscription data request message to the UDM, which includes the UE's identification information. After receiving the subscription data request message from the SMF, the UDM retrieves the UE's subscription data based on the UE's identification information and then sends a subscription data response message to the SMF, which includes the UE's subscription data. The SMF then obtains the identifiers of services the UE is allowed to access from the UE's subscription data.

[0221] For example, the SMF obtains policy information for the UE through the PCF, which includes identifiers of services the UE is allowed to access. Specifically, the SMF sends a policy information request message to the PCF, which includes the UE's identification information. After receiving the policy information request message from the SMF, the PCF sends a policy information response message to the SMF, which includes policy information for the UE. The SMF then obtains the identifiers of the services the UE is allowed to access from the policy information for the UE.

[0222] It should be noted that in the above example, the subscription data or policy information obtained by the SMF may include identifiers of services that the UE is not allowed to access. In this case, the SMF can determine the identifiers of services that the UE is allowed to access based on the identifiers of the services that are not allowed to the UE.

[0223] It should be understood that the services that the UE is allowed to access can also be called services that the UE has permission to access, services that the UE has subscribed to, services that the UE can use, or services that the UE supports, etc., and this application does not limit them.

[0224] Furthermore, the SMF determines whether to allow the UE to access satellite-supported services based on the identifier of the services that the UE is allowed to access and the information on services supported by the satellite.

[0225] If at least one of the identifiers of services that the UE is allowed to access matches the satellite-supported service information, or in other words, if the satellite-supported service information includes at least one of the identifiers of services that the UE is allowed to access, the SMF determines that the UE is allowed to access at least one of the satellite-supported services. In this case, the session management network element inserts the UPF on the satellite (denoted as GEO UPF) into the UE's user plane path.

[0226] If none of the identifiers of the services allowed for UE access match the satellite-supported service information, or if the satellite-supported service information does not include any of the identifiers of the services allowed for UE access, the SMF determines that UE access to any of the satellite-supported services is not permitted. In this case, the session management network element does not insert the GEO UPF into the UE's user plane path.

[0227] The following examples illustrate these two scenarios.

[0228] Situation A:

[0229] S607, SMF selects GEO UPF as UL CL / BP. Here, GEO UPF refers to the GEO UPF corresponding to DNAI in step S604, or it can be described as the GEO UPF corresponding to the satellite backhaul network used by the UE.

[0230] S608, SMF sends an N4 session establishment or modification request message to GEO UPF.

[0231] For example, if the SMF determines that the UE is allowed to access at least one of the satellite-supported services, the SMF selects a GEO UPF as the UL CL / BP and then sends an N4 Session Modification Request message to the GEO UPF. This N4 Session Modification Request message includes a traffic redirection rule instructing the GEO UPF to send data packets for services on the GEO satellite directly to the edge computing platform. Alternatively, the traffic redirection rule instructs the offloading of services that are allowed to the UE and are also supported by the satellite to the satellite-based edge computing platform (SAT EC). Alternatively, the SMF can also instruct the GEO UPF to act as a local PSA via the N4 Session Modification Request message.

[0232] Furthermore, the SMF selects a terrestrial PSA. Then, the network side completes the establishment of the PDU session.

[0233] Based on this, two user plane paths can be established: UE-RAN-GEO UPF-SAT EC; UE-RAN-GEO UPF-Ground PSA.

[0234] In other words, if the UE is allowed to access at least one of the satellite-supported services, the SMF first selects GEOUPF as the UL CL / BP or the local PSA, and then selects the terrestrial PSA.

[0235] Case A can also be described as the SMF selecting the GEO UPF as the session anchor UPF. That is, the SMF selects the GEO UPF as the session anchor UPF if the UE is allowed to access at least one of the satellite-supported services.

[0236] Situation B:

[0237] S609, SMF selects ground-based PSA.

[0238] For example, after the SMF determines that the UPF corresponding to the DNAI will not be inserted as the splitting point, the SMF does not select the GEO UPF corresponding to the DNAI, but directly selects the terrestrial PSA. Then the network side completes the establishment of the PDU session.

[0239] Based on this, a user plane path can be established: UE-RAN-Ground PSA.

[0240] In other words, if the UE is not allowed to access any of the satellite-supported services, the SMF will not choose the GEO UPF, but will directly choose the terrestrial PSA.

[0241] In the above scheme, the decision to insert a UPF on the satellite into the user plane path of the UE is based on whether the UE is allowed to access services on the satellite, thereby reducing latency and improving user experience.

[0242] On one hand, the solution in this application embodiment can pre-insert a UPF on the satellite into the UE's user plane path. In this case, when the UE initiates a satellite service, it can be directly supported by the satellite UPF. For example, by pre-inserting a satellite UPF as a routing point, when the UE initiates an EC service on the satellite, the satellite UPF can directly route the packet to the onboard EC platform. This solution can save latency compared to dynamically inserting satellite UPFs. Specifically, if the SMF decides whether to insert a satellite UPF into the UE's user plane path based on the service the UE will access when the UE initiates a service, and when insertion is required, the SMF selects the satellite UPF and applies the corresponding policy. Since the interaction between the SMF and the satellite UPF is a satellite-to-ground interaction, the latency is very long, which leads to a long user plane connection establishment time, resulting in excessive latency. In contrast, the solution provided in this application embodiment, by pre-inserting a satellite UPF, can reduce the user plane connection establishment time and improve the user experience.

[0243] On the other hand, the solution in this application does not insert a satellite-based UPF into the user plane path of UEs that cannot access services on the satellite. Compared to the solution where the SMF uniformly inserts the satellite-based UPF into the user plane path, this solution can shorten the length of the user plane path for some UEs (i.e., UEs that do not support accessing services on the satellite), reduce data transmission latency, and improve user experience. For example, during the UE session establishment process, the SMF uniformly inserts the satellite-based UPF into the UE's user plane path in advance. However, if the UE is not allowed to access any services on the satellite, it is unnecessary to insert the satellite-based UPF into the UE's user plane path in advance. This would result in an extra UPF on the path between the base station and the ground PSA, thereby increasing the packet processing process, leading to increased packet transmission latency, and affecting user experience. In contrast, the solution provided in this application inserts the satellite UPF into the UE's user plane path only when the UE is allowed to access at least one service on the satellite. When access to any service on the satellite is not allowed, the satellite UPF is not inserted into the UE's user plane path. This does not affect the UE's services and reduces data transmission latency, thereby improving user experience.

[0244] Figure 7 An exemplary flowchart of a method 700 provided in an embodiment of this application is shown. The method 700 is described below with reference to each step.

[0245] S701, SMF obtains the correspondence between SAT ID and business information.

[0246] For example, the correspondence between the SAT ID and service information can be understood as the service deployment information corresponding to the satellite, which is used to indicate one or more services supported by the satellite. A description of this service information can be found in S601 of method 600, and will not be repeated here. The SAT ID is used to identify the satellite; the SAT ID can be the satellite's own identification information or the identification information of the UPF on the satellite (SAT UPF ID), which is not limited in this application.

[0247] In one implementation, the SMF can obtain the correspondence between the SAT ID and the business information through AF; in another implementation, the SMF can obtain the correspondence between the SAT ID and the business information through local configuration information.

[0248] S702, the UE sends a PDU session request message to the AMF. Correspondingly, the AMF receives the PDU session request message from the UE.

[0249] S703, the AMF sends a Create Session Management Context Request message to the SMF. Correspondingly, the SMF receives the Create Session Management Context Request message from the AMF.

[0250] It should be understood that S702 and S703 are similar to S602 and S603 in method 600, and will not be described again here for the sake of brevity.

[0251] S704, SMF determines the SAT ID corresponding to the UE's location information.

[0252] For example, the SMF obtains the UE's location information from the Create Session Management Context Request message, and then determines the corresponding SAT ID based on the UE's location information.

[0253] As one possible implementation, the SMF locally stores configuration information, which can be pre-configured to the SMF or obtained from other network elements. This configuration information includes the mapping between the UE's location information and the SAT ID. The SMF determines the SAT ID based on the obtained UE location information and this configuration information.

[0254] S705, SMF determines the business information corresponding to the SAT ID.

[0255] For example, after determining the SAT ID, the SMF determines the satellite-supported service information based on the SAT ID and the correspondence between the SAT ID and service information obtained by S701.

[0256] S706, SMF determines whether to allow the UE to access satellite-supported services.

[0257] It should be understood that S706 is similar to S606 in method 600, and for the sake of brevity, it will not be described again here. Figure 7 S707-S09 in method 600 are similar to S608-S610 in method 600, and will not be described again here.

[0258] Figure 8 An exemplary flowchart of a method 800 provided in an embodiment of this application is shown. The method 800 is described below with reference to each step.

[0259] S801, SMF obtains the correspondence between DNAI and business information.

[0260] In step S802, the UE sends a PDU session establishment request message to the AMF. Correspondingly, the AMF receives the PDU session establishment request message from the UE.

[0261] S801-S802 are similar to S601-S602 in method 600, and will not be described again here for the sake of brevity.

[0262] S803, AMF determines the DNAI corresponding to the UE's location information and satellite backhaul type.

[0263] For example, after the AMF obtains the UE's location information and satellite backhaul type information, it determines the corresponding DNAI based on the UE's location information and satellite backhaul type information.

[0264] As one possible implementation, the AMF locally stores configuration information, which can be pre-configured to the AMF or obtained from other network elements. This configuration information includes the correspondence between the UE's location information, satellite backhaul type information, and DNAI. The AMF determines the DNAI based on the UE's location information, satellite backhaul type information, and this configuration information.

[0265] For specific implementation details, please refer to S604 in method 600. The difference is that S604 in method 600 is executed by SMF, while S803 in method 800 is executed by SMF.

[0266] S804, the AMF sends a Create Session Management Context Request message to the SMF. Correspondingly, the SMF receives the Create Session Management Context Request message from the AMF.

[0267] For example, after the AMF determines the DNAI corresponding to the UE's location information and satellite backhaul type information, it sends a Create Session Management Context Request message to the SMF, which includes the DNAI.

[0268] S805, SMF obtains service information supported by the satellite.

[0269] S806, SMF determines whether the UE is allowed to access satellite-supported services.

[0270] It should be understood that S805 and S806 are similar to S605 and S606 in method 600, and will not be described again here. Furthermore, S807 to S809 are similar to S607-S609 in method 600, and will not be described again here.

[0271] Figure 9 An exemplary flowchart of a method 900 provided in an embodiment of this application is shown. The method 900 is described below with reference to each step.

[0272] S901, SMF obtains the correspondence between SAT ID and business information.

[0273] S902, the UE sends a PDU session establishment request message to the AMF. Correspondingly, the AMF receives the PDU session establishment request message from the UE.

[0274] It should be understood that S901 and S902 are similar to S701 and S702 in method 700, and will not be described again here.

[0275] S903, AMF determines the SAT ID corresponding to the UE's location information.

[0276] For example, after the AMF receives a PDU session establishment request message from the UE, it determines the UE's location information and then determines the SAT ID corresponding to the UE's location information.

[0277] As one possible implementation, the AMF locally stores configuration information, which can be pre-configured for the SMF or obtained from other network elements. This configuration information includes the correspondence between the UE's location information and the SAT ID. The AMF determines the SAT ID based on the UE's location and this configuration information.

[0278] For specific implementation details, please refer to S704 in method 700. The difference is that S704 in method 700 is executed by SMF, while S903 in method 900 is executed by AMF.

[0279] S904, the AMF sends a Create Session Management Context Request message to the SMF. Correspondingly, the SMF receives the Create Session Management Context Request message from the AMF.

[0280] For example, after the AMF receives a PDU session establishment request from the UE, it sends a Create Session Management Context Request message to the SMF, which includes the SAT ID.

[0281] S905, SMF obtains service information supported by the satellite.

[0282] S906, SMF determines whether the UE is allowed to access satellite-supported services.

[0283] It should be understood that S905 and S906 are similar to S605 and S606 in method 600, and will not be described again here. Furthermore, S907 to S909 are similar to S607-S609 in method 600, and will not be described again here.

[0284] Figure 10 An exemplary flowchart of a method 1100 provided in an embodiment of this application is shown. The method 1100 is described below with reference to each step.

[0285] S1001, the UE sends a PDU session establishment request message to the AMF, and correspondingly, the AMF receives the PDU session establishment request message from the UE.

[0286] S1002, the AMF sends a Create Session Management Context Request message to the SMF. Correspondingly, the SMF receives the Create Session Management Context Request message from the AMF.

[0287] It should be understood that S1001 and S1002 are similar to S602 and S603 in method 600, and will not be described again here.

[0288] S1003, SMF determines whether to allow UE to perform local data exchange under satellite.

[0289] For example, the SMF can determine whether to allow the UE to perform local data exchange under satellite based on the UE's subscription data or policy information. The subscription data or policy information may include local data exchange indication information. For instance, the SMF obtains the UE's subscription data through the UDM, and then determines whether to allow the UE to perform local data exchange under satellite based on the local data exchange indication information in the subscription data. This local data exchange indication information is used to indicate whether the UE is allowed to perform local data exchange under satellite. As one possible implementation, the local data exchange indication information can take different values ​​to indicate different situations. For example, when the local data exchange indication information is 1, it indicates that the UE is allowed to perform local data exchange under satellite; when the local data exchange indication information is 0 (or empty), it indicates that the UE is not allowed to perform local data exchange under satellite.

[0290] When the UE is allowed to perform local data exchange under satellite, the session management network element inserts the UPF on the satellite (denoted as GEO UPF) into the UE's user plane path.

[0291] If the UE is not allowed to perform local data exchange under satellite, the session management network element will not insert the UPF on the satellite (denoted as GEO UPF) into the UE's user plane path.

[0292] The following examples illustrate these two scenarios.

[0293] Situation A:

[0294] S1004, SMF selects GEO UPF as UL CL / BP or local PSA.

[0295] S1005, SMF sends an N4 session establishment or modification request message to GEO UPF.

[0296] For example, when the SMF determines that the UE is allowed to perform local data exchange under satellite, the SMF selects the GEO UPF and then sends an N4 session modification request message to the GEO UPF. The N4 session modification request message includes a traffic redirection rule, which instructs the GEO UPF to send data packets destined for the UE on the satellite to the corresponding UE via satellite local data exchange. Alternatively, the traffic redirection rule instructs the GEO UPF to send data packets with destination addresses pointing to the UE on the satellite to the UE's corresponding gNB. Or, the traffic redirection rule instructs the GEO UPF to send data packets matched to the UE on the satellite via local data exchange.

[0297] Situation B:

[0298] S1006, SMF selects ground-based PSA.

[0299] S1006 is similar to S609, so it will not be described in detail here.

[0300] Based on the above scheme, when the UE needs to perform local data exchange under satellite, a GEO UPF can be inserted into the UE's user plane path to support the UE to perform local data exchange under satellite; when the UE does not need to perform local data exchange under satellite, a GEO UPF is not inserted into the UE's user plane path, thereby shortening the length of the UE's user plane path, reducing transmission latency, and improving user experience.

[0301] It should be understood that method 100 can be implemented alone or in combination with the aforementioned methods 600 to 900. For example, when method 1100 is implemented in combination with method 600, the SMF can comprehensively consider the situations given in S605 and S1003 to determine whether to insert the satellite's UPF. Specifically, the SMF determines whether the UE is allowed to access satellite-supported services and whether the UE is allowed to perform local data exchange under the satellite. If the UE is allowed to access at least one of the satellite-supported services, or if the UE is allowed to perform local data exchange under the satellite, then the SMF inserts the satellite's UPF; otherwise, the SMF does not insert the satellite's UPF.

[0302] Corresponding to the methods given in the above method embodiments, this application also provides a corresponding apparatus, which includes a module for executing the corresponding methods in the above method embodiments. This module can be software, hardware, or a combination of software and hardware. It is understood that the technical features described in the above method embodiments are also applicable to the following apparatus embodiments. Therefore, details not described in detail can be found in the above method embodiments, and for brevity, will not be repeated here.

[0303] Figure 11 This is a schematic block diagram of a communication device 10 provided in an embodiment of this application. The device 10 includes a processing module 11. Optionally, the device 10 may further include a transceiver module 11. The processing module 11 is used for data processing, and the transceiver module 12 can implement corresponding communication functions; that is, the transceiver module 12 is used to perform receiving and sending related operations, while the processing module 11 is used to perform other operations besides receiving and sending. The transceiver module 12 may also be referred to as a communication interface or a communication unit.

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

[0305] In the first design, the device 10 may correspond to the network device in the above method embodiment, or a component of the network device (such as a chip), such as a session management network element (such as SMF) or a mobility management network element (such as AMF).

[0306] The device 10 can implement the steps or processes corresponding to the session management network element (such as SMF) in the above method embodiments. The processing module 11 can be used to perform processing-related operations of the session management network element (such as SMF) in the above method embodiments, and the transceiver module 12 can be used to perform transceiver-related operations of the session management network element (such as SMF) in the above method embodiments.

[0307] For example, the device 10 may correspond to the session management network element in method 500 of the embodiments of this application, or the SMF in methods 600 to 1000. The device 10 may include tools for performing... Figures 5 to 10 The module is the one that executes the method of the session management network element (or SMF) in the device. Furthermore, each module in the device 10 and the other operations and / or functions described above are respectively for implementing... Figures 5 to 10 The corresponding flow of the method shown.

[0308] In one possible design, the processing module 11 is configured to acquire service information indicating one or more services supported by the satellite; and determine, based on the service information, whether to allow a terminal device to access the services supported by the satellite; and, if it is determined that the terminal device is allowed to access at least one of the services supported by the satellite, insert a user plane network element on the satellite into the user plane path of the terminal device.

[0309] The device 10 can implement the steps or processes corresponding to the Mobility Management Network Element (or AMF) in the above method embodiments. The transceiver module 12 can be used 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 used to perform processing-related operations of applying the Mobility Management Network Element (or AMF) in the above method embodiments.

[0310] For example, the device 10 may correspond to the mobility management network element in method 500 of the embodiments of this application, or the AMF in methods 600 to 1000. The device 10 may include tools for performing Figures 5 to 10 The module is the one that executes the method by the mobility management network element (or AMF) in the device. Furthermore, each module in the device 10 and the other operations and / or functions described above are respectively for implementing... Figures 5 to 10 The corresponding flow of the method shown.

[0311] In one possible implementation, the processing module 11 is used to determine a first data network access identifier based on the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device; the transceiver module 12 is used to send the first data network access identifier to the session management network element.

[0312] It should be understood that the specific process of each module performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments, and will not be repeated here for the sake of brevity.

[0313] It should also be understood that the device 10 here is embodied in the form of a functional module. The term "module" here can refer to application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors, etc.) and memories for executing one or more software or firmware programs, integrated logic circuits, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that device 10 may specifically be a mobility management network element in the above embodiments, and may be used to execute the various processes and / or steps corresponding to the mobility management network element in the above method embodiments; or, device 10 may specifically be a terminal device in the above embodiments, and may be used to execute the various processes and / or steps corresponding to the terminal device in the above method embodiments. To avoid repetition, further details are omitted here.

[0314] The apparatus 10 of each of the above-described schemes has the function of implementing the corresponding steps performed by the network device (such as a mobility management network element or a data management network element) or terminal device in the above-described methods. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described 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 processing modules, can be replaced by processors, which respectively execute the transceiver operations and related processing operations in each method embodiment.

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

[0316] It should be pointed out that, Figure 12 The device mentioned can be the network element or equipment in the foregoing embodiments, or it can be 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; the processing module is a processor, microprocessor, or integrated circuit integrated on the chip. No limitations are imposed here.

[0317] According to the aforementioned method, Figure 12 This is a schematic diagram of the communication device 20 provided in an embodiment of this application. In one possible design, the device 20 may correspond to the Session Management Network Element (or SMF) in the above method embodiment; in another possible design, the device 10 may correspond to the Mobility Management Network Element (or AMF) in the above method embodiment.

[0318] The device 20 may include a processor 21 (i.e., an example of a processing module), which is used to perform... Figures 5 to 10 The operation performed by the Session Management Network Element (such as SMF) or Mobility Management Network Element (such as AMF) in the corresponding method. Optionally, the device 20 may include a memory 22, and the processor 21 may execute instructions stored in the memory 22 to cause the device 20 to implement, for example... Figures 5 to 10 The corresponding method is the operation performed by the session management network element (such as SMF) or the mobility management network element (such as AMF).

[0319] Furthermore, the device 20 may also include a transceiver 23 (i.e., an example of a transceiver module). Furthermore, the processor 21, memory 22, and transceiver 23 can communicate with each other via internal connections to transmit control and / or data signals. The memory 22 stores computer programs, and the processor 21 can retrieve and run these programs from the memory 22 to control the transceiver 23 to receive and transmit signals, thus completing the steps of the terminal device or network device described above. The memory 22 may be integrated into the processor 21 or disposed separately from it.

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

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

[0322] As one implementation method, the transceiver 23 can be implemented using a transceiver circuit or a dedicated transceiver chip. The processor 21 can be implemented using a dedicated processing chip, processing circuit, processor, or general-purpose chip.

[0323] As another implementation method, the communication device provided in this application embodiment can be implemented using a general-purpose computer. That is, the program code that implements the functions of processor 21 and transceiver 23 is stored in memory 22, and the general-purpose processor implements the functions of processor 21 and transceiver 23 by executing the code in memory 22.

[0324] For the concepts, explanations, detailed descriptions, and other steps related to the technical solutions provided in the embodiments of this application involved in the device 20, please refer to the descriptions of these contents in the foregoing methods or other embodiments, which will not be repeated here.

[0325] Figure 13 A simplified schematic diagram of a network device 30 is shown. The network device includes parts 31 and 32. Part 31 is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals to baseband signals; part 32 is mainly used for baseband processing and controlling the network device. Part 31 can generally be referred to as a transceiver module, transceiver, transceiver circuit, or transceiver unit. Part 32 is usually the control center of the network device, often referred to as a processing module, used to control the network device to perform the processing operations on the network device side in the above method embodiments.

[0326] The transceiver module in section 31, also known as a transceiver unit or transceiver, includes an antenna and radio frequency (RF) circuitry, with the RF circuitry primarily used for RF processing. For example, the device in section 31 that performs the receiving function can be considered a receiving module, and the device that performs the transmitting function can be considered a transmitting module; that is, section 31 includes both a receiving module and a transmitting module. The receiving module can also be called a receiver, receiver circuit, or receiving unit, while the transmitting module can be called a transmitter, transmitter, or transmitting circuit.

[0327] Part 32 may include one or more single boards, each single board may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement baseband processing functions and control network devices. If multiple single boards exist, they can be interconnected to enhance processing capabilities. As an optional implementation, multiple single boards may share one or more processors, or multiple single boards may share one or more memories, or multiple single boards may simultaneously share one or more processors.

[0328] For example, in one implementation, Figure 13 The network device shown can be Figures 5 to 10 The method shown can be any network device, such as a mobility management network element.

[0329] The transceiver module in section 31 is used for execution Figures 5 to 10 The method shown includes any network device's transmit / receive related steps; section 32 is used for execution. Figures 5 to 10 The steps related to the processing of any network device in the method shown.

[0330] It should be understood that Figure 10 This is merely an example and not a limitation; the network devices described above, including transceiver modules and processing modules, may not rely on... Figure 10 The structure shown.

[0331] 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 or a communication interface; the processing module is a processor, microprocessor, or integrated circuit integrated on the chip.

[0332] This application also provides a computer-readable storage medium storing computer instructions for implementing the method executed by the network device in the above method embodiments.

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

[0334] This application also provides a computer program product containing instructions that, when executed by a computer, cause the computer to implement the method executed by the first device or the method executed by the second device in the above method embodiments.

[0335] This application also provides a communication system, which includes the network device described in the above embodiments.

[0336] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0337] In this embodiment, the network device may include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system layer. The hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system layer may be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

[0338] This application does not impose any particular limitation on the specific structure of the execution subject of the method provided in this application embodiment. As long as it is possible to communicate according to the method provided in this application embodiment by running a program that records the code of the method provided in this application embodiment. For example, the execution subject of the method provided in this application embodiment can be a network device, or a functional module in a network device that can call and execute a program.

[0339] Various aspects or features of this application can be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. As used herein, the term "article of manufacture" can encompass a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media can include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.).

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

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

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

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

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

[0345] Those skilled in the art will recognize that the units and steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of protection of this application.

[0346] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the above-described apparatus and unit can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0347] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of apparatus or units may be electrical, mechanical, or other forms.

[0348] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to implement the solution provided in this application, depending on actual needs.

[0349] In addition, the functional units in the various embodiments of this application can be integrated into one unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0350] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially 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 this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks (SSDs)). For example, the aforementioned available media may include, but are not limited to, various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0351] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of protection of the claims and the specification.

Claims

1. A communication method characterized by comprising: include: The session management function network element acquires service information, which is used to indicate one or more services supported by the satellite; When the session management function network element determines, based on the service information, that the terminal device is allowed to access at least one of the services supported by the satellite, the session management function network element inserts the user plane network element on the satellite into the user plane path of the terminal device.

2. The method of claim 1, wherein, The session management function network element obtains service information, including: The session management function network element obtains the satellite's identification information; The session management function network element determines the service information based on the satellite's identification information and the second configuration information, wherein the second configuration information includes the correspondence between the satellite's identification information and the service information.

3. The method of claim 2, wherein, The session management function network element obtains the satellite's identification information, including: The session management function network element receives the satellite's identification information from the mobility management network element.

4. The method according to any one of claims 1 to 3, characterized in that, The user plane network element on the satellite is the user plane network element on the satellite corresponding to the data network access identifier (DNAI). The DNAI is used to identify the user plane connection used to access the services supported by the satellite.

5. The method of claim 4, wherein, The DNAI is determined by the location information and satellite backhaul type information of the terminal device.

6. The method according to claim 4, characterized in that, The DNAI is determined by the location information of the terminal device, the satellite backhaul type information, and the satellite's identification information.

7. The method according to claim 1, characterized in that, The service is represented by at least one of the following identifiers: application identifier, fully qualified domain name (FQDN).

8. The method according to any one of claims 1 to 3, characterized in that, The user plane network element on the satellite is the user plane functional network element (UPF) on the satellite.

9. The method according to any one of claims 1 to 3, characterized in that, The session management function network element determines, based on the service information, that the terminal device is allowed to access at least one of the services supported by the satellite, including: The session management function network element determines, based on the service information and policy information, that the terminal device is allowed to access at least one of the services supported by the satellite, wherein the policy information includes an identifier of the service that the terminal device is allowed to access; The method further includes: The session management function network element receives policy information from the policy control network element.

10. The method according to any one of claims 1 to 3, characterized in that, The session management function network element inserts the user plane network element on the satellite into the user plane path of the terminal device, including: the session management function network element selects the user plane network element on the satellite as a splitting point and inserts it into the user plane path of the terminal device.

11. The method according to any one of claims 1 to 3, characterized in that, Also includes: The session management function network element sends a traffic redirection rule to the user plane network element on the satellite. The traffic redirection rule is used to instruct the user plane network element on the satellite to send data packets for the services on the satellite to the corresponding service platform of the satellite.

12. A communication device, characterized in that, include: A processing module is used to acquire service information, which is used to indicate one or more services supported by the satellite; The processing module is further configured to insert a user plane network element on the satellite into the user plane path of the terminal device when it is determined, based on the service information, that the terminal device is allowed to access at least one of the services supported by the satellite.

13. The apparatus according to claim 12, characterized in that, The processing module is used to acquire business information, including: The processing module is used to obtain the satellite's identification information; The processing module is used to determine the service information based on the satellite's identification information and the second configuration information, wherein the second configuration information includes the correspondence between the satellite's identification information and the service information.

14. The apparatus according to claim 13, characterized in that, The processing module is used to obtain the satellite's identification information, including: The processing module is used to receive the satellite's identification information from the mobility management network element.

15. The apparatus according to any one of claims 12 to 14, characterized in that, The user plane network element on the satellite is the user plane network element on the satellite corresponding to the data network access identifier (DNAI). The DNAI is used to identify the user plane connection used to access the services supported by the satellite.

16. The apparatus according to claim 15, characterized in that, The DNAI is determined by the location information and satellite backhaul type information of the terminal device.

17. The apparatus according to claim 15, characterized in that, The DNAI is determined by the location information of the terminal device, the satellite backhaul type information, and the satellite's identification information.

18. The apparatus according to claim 12, characterized in that, The service is represented by at least one of the following identifiers: application identifier, fully qualified domain name (FQDN).

19. The apparatus according to any one of claims 12 to 14, characterized in that, The user plane network element on the satellite is the user plane functional network element (UPF) on the satellite.

20. The apparatus according to any one of claims 12 to 14, characterized in that, The processing module is specifically used to receive policy information from the policy control network element through the transceiver module. The policy information includes identifiers of services that the terminal device is allowed to access. And based on the policy information and the service information, determine at least one of the services supported by the satellite that the terminal device is allowed to access.

21. The apparatus according to any one of claims 12 to 14, characterized in that, The processing module is used to insert the user plane network element on the satellite into the user plane path of the terminal device, including: the processing module is used to select the user plane network element on the satellite as a split point and insert it into the user plane path of the terminal device.

22. The apparatus according to any one of claims 12 to 14, characterized in that, The processing module is also used to send traffic redirection rules to the user plane network elements on the satellite through the transceiver module. The traffic redirection rules are used to instruct the user plane network elements on the satellite to send data packets for the services on the satellite to the corresponding service platform of the satellite.

23. A communication device, characterized in that, The device includes at least one processor coupled to at least one memory, the at least one processor being configured to execute a computer program or instructions stored in the at least one memory to cause the communication device to perform the method as described in any one of claims 1 to 11.

24. A chip, characterized in that, The device includes a processor and a communication interface, the communication interface being used to receive data and / or information and transmit the received data and / or information to the processor, the processor processing the data and / or information to perform the method as described in any one of claims 1 to 11.

25. A computer-readable storage medium, characterized in that, It stores a computer program thereon, which, when executed, causes the method as described in any one of claims 1 to 11 to be performed.

26. A computer program product containing instructions, characterized in that, When it is run on a computer, it causes the computer to perform the method as described in any one of claims 1 to 11.

Images