Communication method and device

Abstract

The invention provides a satellite communication method and device, and the method can comprise the steps that a session management network element obtains first service information, and the service information is used for indicating one or more services supported by a satellite; the session management network element determines whether to allow the terminal device to access services supported by the satellite according to the first service information; and when 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 a user plane path of the terminal device. Based on the scheme, the time delay of satellite communication of the terminal equipment can be reduced, and the user experience is improved.

Description

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

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

[0003] Currently, an important scenario where the satellite communication and 5G communication system (the 5th-generation mobile communications system, 5GS) fusion technology can be applied is satellite backhaul (SATB), that is, the satellite link serves as the satellite backhaul link, and the access network device communicates with the core network device through the satellite backhaul link. In this scenario, a user plane function (UPF) network element can be deployed on the satellite to provide various service supports. For example, an on-satellite UPF can be inserted into the user plane path to enable satellite edge computing or satellite local switching, etc. However, in the current solution of inserting an on-satellite UPF into the user plane path, the user plane transmission delay is large and the user experience is poor. Summary of the Invention

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

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

[0006] The communication method includes: the session management network element obtains service information, where the service information is used to indicate one or more services supported by the satellite; the session management network element determines whether to allow the terminal device to access the services supported by the satellite according to the service information; in the case of determining 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 on-satellite user plane network element into the user plane path of the terminal device.

[0007] In combination with the first aspect, in some implementation manners of the first aspect, the method further includes: in the case of determining 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 on-satellite user plane network element into the user plane path of the terminal device.

[0008] Based on the above solution, 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 user plane network element on the satellite 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 user plane network element on the satellite is not inserted into the user plane path of the terminal device. Based on this, the user plane network element on the satellite can be inserted into the user plane path of the terminal device that requires the user plane network element on the satellite to provide services, so as to support these terminal devices to access the services on the satellite; and the user plane network element on the satellite is not inserted into the user plane path of the terminal device that does not require the user plane network element on the satellite to provide services, so as to shorten the length of the user plane path of these terminal devices, reduce the transmission delay, and improve the user experience.

[0009] Combined with the first aspect, in some implementation manners of the first aspect, the session management network element obtains service information, including: the session management network element determines a first data network access identifier according to the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device; the session management network element determines the service information according to the first data network access identifier and the first configuration information, and the first configuration information includes the correspondence between the first data network access identifier and the service information.

[0010] Based on the above solution, the session management network element can first determine the first data network access identifier, and then determine the service information according to the first data network access identifier and the first configuration information, that is, determine the satellite-supported services. Among them, the session management network element can determine the first data network access identifier in combination with the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device, so as to accurately determine the first data network access identifier corresponding to the satellite.

[0011] Combined with the first aspect, in some implementation manners of the first aspect, the session management network element determines the first data network access identifier according to 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 according to 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 according to the satellite backhaul type information.

[0012] Based on the above solution, the session management network element determines the first data network access identifier in combination with 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 determine the first data network access identifier corresponding to the satellite in combination with the satellite backhaul type information.

[0013] In combination with the first aspect, in some implementations of the first aspect, the session management network element determines a 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 constellation information.

[0014] Based on the above solution, 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. Exemplarily, when the terminal device has multiple backhaul links, there may be multiple data network access identifiers corresponding to the location information of the terminal device and the satellite backhaul type information. In this case, the satellite constellation information can be combined to determine the data network access identifier corresponding to the satellite, so as to determine the services supported by the satellite.

[0015] In combination with the first aspect, in some implementations of the first aspect, the session management network element determines a 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 solution, 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. Exemplarily, when the terminal device has multiple backhaul links, there may be multiple data network access identifiers corresponding to the location information of the terminal device and the satellite backhaul type information. In this case, the satellite identification information can be combined to determine the data network access identifier corresponding to the satellite, so as to determine the services supported by the satellite.

[0017] In combination 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 satellite identification information; the session management network element determines the service information based on the satellite identification information and the second configuration information, and the second configuration information includes the correspondence between the satellite identification information and the service information.

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

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

[0020] Based on the above solution, the session management network element can obtain the identification information of the satellite through the mobility management network element, so that the session management network element can determine the service information according to the identification information of the satellite.

[0021] Combined with the first aspect, in some implementation manners 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 according to the location information of the terminal device and the constellation information of the satellite.

[0022] Based on the above solution, the session management network element can determine the identification information of the satellite by itself 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 identification information of the satellite.

[0023] Combined with the first aspect, in some implementation manners of the first aspect, the session management network element obtains the service information, including: the session management network element obtains the constellation information of the satellite; the session management network element determines the service information according to the constellation information of the satellite and the third configuration information, and the third configuration information includes the corresponding relationship between the constellation information of the satellite and the service information.

[0024] Based on the above solution, the session management network element can first determine the constellation information of the satellite, and then determine the service information according to the constellation information, that is, determine the services supported by the satellite. Exemplarily, when the satellites in a constellation have the same capabilities, that is, support the same services, the services supported by the satellite can be determined according to the constellation information of the satellite.

[0025] Combined with the first aspect, in some implementation manners of the first aspect, the session management network element determines whether to allow the terminal device to access the services supported by the satellite according to the service information, including: the session management network element receives the subscription data of the terminal device from the data management network element; the session management network element determines whether to allow the terminal device to access the services supported by the satellite according to the subscription data and the service information.

[0026] Based on the above solution, the session management network element can determine whether to allow the terminal device to access the services supported by the satellite according to the subscription data and the 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 according to the judgment result.

[0027] Combined with the first aspect, in some implementation manners of the first aspect, the subscription data includes the identification of the services allowed for the terminal device to access; the session management network element determines whether to allow the terminal device to access the services supported by the satellite according to the service information, including: if the services allowed for the terminal device to access include at least one service indicated by the service information, the session management network element determines to allow the terminal device to access the services supported by the satellite.

[0028] Based on the above solution, if the services allowed for the terminal device to access indicated by the subscription data include at least one of the satellite-supported services, the session management network element determines to allow the terminal device to access the satellite-supported services. That is to say, in this case, the session management network element may insert the user plane network element on the satellite into the user plane path of the terminal device.

[0029] Combined with the first aspect, in some implementation manners of the first aspect, the session management network element determines whether to allow the terminal device to access the satellite-supported services according to the service information, including: the session management network element receives the policy information of the terminal device from the policy control network element, and the policy information includes the identifiers of the services allowed for the terminal device to access; the session management network element determines whether to allow the terminal device to access the satellite-supported services according to the policy information and the service information.

[0030] Based on the above solution, the session management network element can determine whether to allow the terminal device to access the satellite-supported services according to the policy 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 according to the judgment result.

[0031] Combined with the first aspect, in some implementation manners of the first aspect, the satellite backhaul type information indicates that the terminal device accesses the satellite through geostationary orbit satellite backhaul.

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

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

[0034] Based on the above solution, the mobility management network element can provide the first data network access identifier 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 according to the first data network access identifier, and further can decide whether to insert the user plane network element on the satellite into the user plane path of the terminal device according to the judgment of whether the terminal device is allowed to access the services on the satellite.

[0035] In combination with the second aspect, in some implementations of the second aspect, the mobility management network element determines the first data network access identifier according to 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 according to 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 according to the satellite backhaul type information.

[0036] Based on the above solution, the mobility management network element determines the first data network access identifier in combination with 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 determine the first data network access identifier corresponding to the satellite in combination with the satellite backhaul type information.

[0037] In combination with the second aspect, in some implementations of the second aspect, the mobility management network element determines the first data network access identifier according to 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 according to 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 solution, the mobility management network element can determine the data network access identifier in combination with the location information of the terminal device, the satellite backhaul type information, and the constellation information of the satellite. Exemplarily, when the terminal device has multiple backhaul links, there may be multiple data network access identifiers corresponding to the location information of the terminal device and the satellite backhaul type information. In this case, the constellation information of the satellite can be combined to determine the data network access identifier corresponding to the satellite, so as to determine the services supported by the satellite.

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

[0040] In a third aspect, a communication method is provided, characterized in that the method includes: the mobility management network element determines the identification information of the satellite accessed by the terminal device according to the location information of the terminal device; the mobility management network element sends the identification information of the satellite to the session management network element.

[0041] Based on the above solution, the mobility management network element can provide the identification information of the satellite 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 according to the identification information of the satellite, and further determine whether to insert the user plane network element on the satellite into the user plane path of the terminal device according to the judgment of whether the terminal device is allowed to access the services on the satellite.

[0042] In a fourth aspect, a communication method is provided, characterized in that the method includes: the session management network element determines whether to allow the terminal device to perform local data exchange under the satellite; in the case of determining to allow the terminal device to perform local data exchange under 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.

[0043] In combination with the fourth aspect, in some implementation manners of the fourth aspect, the method further includes: in the case of determining not to allow the terminal device to perform local data exchange under 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.

[0044] Based on the above solution, in the case where the terminal device needs to perform local data exchange under the satellite, the user plane network element on the satellite can be inserted into the user plane path of the terminal device, so as to support the terminal device to perform local data exchange under the satellite; while in the case where the terminal device does not need to perform local data exchange under the satellite, the user plane network element on the satellite is not inserted into the user plane path of the terminal device, so as to shorten the length of the user plane paths of these terminal devices, reduce the transmission delay, and improve the user experience.

[0045] In combination with the fourth aspect, in some implementation manners of the fourth aspect, the session management network element determines whether to allow the terminal device to perform local data exchange under the satellite, including: the session management network element receives the subscription data of the terminal device from the data management network element; the session management network element determines whether to allow the terminal device to perform local data exchange under the satellite according to the subscription data.

[0046] In combination with the fourth aspect, in some implementation manners of the fourth aspect, the session management network element determines whether to allow the terminal device to perform local data exchange under the satellite, including: the session management network element receives the policy information of the terminal device from the policy control network element; the session management network element determines whether to allow the terminal device to perform local data exchange under the satellite according to the policy information.

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

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

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

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

[0051] Sixth aspect, a communication device is provided, which includes: a memory for storing a program; a processor for executing the program stored in the memory. When the program stored in the memory is executed, the processor is used to execute any of the methods provided in the first aspect to the fourth aspect above.

[0052] Seventh aspect, the present application provides a processor for executing the methods provided in the above aspects. In the process of executing these methods, the processes of sending the above information and obtaining / receiving the above information in the above methods can be understood as the process of the processor outputting the above information and the process of the processor receiving the input above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After the above information is output by the processor, other processing may be required before it reaches the transceiver. Similarly, when the processor receives the input above information, the transceiver obtains / receives the above information and inputs it to the processor. Further, after the transceiver receives the above information, the above information may need to be processed further before being input to the processor.

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

[0054] For operations such as transmitting, sending, and obtaining / receiving involved by the processor, if there is no special description, or if it does not conflict with its actual role or internal logic in the relevant description, they can all be more generally understood as the processor's output and reception, input, etc. operations, rather than the transmitting, sending, and receiving operations directly performed by the radio frequency circuit and the antenna.

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

[0056] In an eighth aspect, there is provided a computer-readable storage medium storing program code for a device to execute, and the program code includes any method provided in the first aspect to the fourth aspect above.

[0057] In a ninth aspect, there is provided a computer program product containing instructions, and when the computer program product runs on a computer, it causes the computer to execute any method provided in the first aspect to the fourth aspect above.

[0058] In a tenth aspect, there is provided a chip including a processor and a communication interface, and the processor reads the instructions stored on the memory through the communication interface and executes any method provided in the first aspect to the fourth aspect above.

[0059] Optionally, as an implementation manner, the chip may further include a memory, and instructions are stored in the memory, and the processor is used to execute the instructions stored on the memory. When the instructions are executed, the processor is used to execute any method provided in the first aspect to the fourth aspect above.

[0060] In an eleventh aspect, there is provided a communication system including one or more of the foregoing session management network elements and mobility management network elements. Description of the Drawings

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

[0062] Figure 2It is a schematic diagram of the communication architecture of a satellite return link;

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

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

[0065] Figure 5 It is a schematic block diagram of a communication method provided by an embodiment of the present application;

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

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

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

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

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

[0071] Figure 11 It is a schematic block diagram of a communication device provided by an embodiment of the present application;

[0072] Figure 12 It is a schematic block diagram of a communication device provided by another embodiment of the present application;

[0073] Figure 13 It is a schematic block diagram of a communication device provided by yet another embodiment of the present application. Detailed implementation manners

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

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

[0076] It should be understood that the various numerical numbers involved in this application are only for the convenience of description and are not used to limit the scope of this application. The magnitudes of the serial numbers of the above processes do not imply the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic.

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

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

[0079] Next, it will be combined with Figure 1 to illustrate the 5G system applicable to the embodiments of this application. It should be understood that the 5G system described herein is only an example and should not constitute any limitation to this application.

[0080] It should also be understood that some network elements in the 5G system can communicate using a service-based interface or a point-to-point interface. Next, it will be combined with Figure 1 of (a) andFigure 1 (b) respectively introduce the 5G system framework based on the peer-to-peer interface and the 5G system framework based on the service-based interface.

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

[0082] (Radio) access network device (radio access network, (R)AN), access and mobility management function (accessand mobility management function, AMF) network element, session management function (sessionmanagement function, SMF) network element, user plane function (user plane function, UPF) network element, policy control function (policy controlfunction, PCF) network element, unified data management (unified data management, UDM) network element, AF network element, data network (data network, DN), network slice selection function (network sliceselection function, NSSF), authentication server function (authentication server function, AUSF), unified data management (unified datamanagement, UDM), BSF network element, unified data repository (unified datarepository, UDR), etc.

[0083] Next, a brief introduction to each network element shown in Figure 1 (a) will be given:

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

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

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

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

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

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

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

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

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

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

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

[0095] In a 5G communication system, this user plane network element may be a user plane function (UPF) network element. In future communication systems, the user plane network element may still be a UPF network element, or there may be other names, which are not limited by the present application.

[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, etc., and can be used to implement other functions except session management in the MME function. For example, functions such as access authorization / authentication.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0110] 11. Data Network (DN): The DN is a network outside the operator's network. The operator's network can access multiple DNs. Multiple services can be deployed on the DN, which can provide services such as data and / or voice for terminal devices. For example, the DN is a private network of a smart factory. The sensors installed in the workshop of the smart factory can be terminal devices. A control server for the sensors is deployed in the DN, and the control server can provide services for the sensors. The sensors can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions, etc. Another example is that the DN is the internal office network of a company. The mobile phones or computers of the company's employees can be terminal devices, and the mobile phones or computers of the employees can access information, data resources, etc. 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 referred to the meanings defined in the 3GPP standard protocol and are not restricted here.

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

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

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

[0115] 1) N7: The interface between the PCF and the SMF, which is used to issue protocol data unit (PDU) session granularity and service data flow granularity control policies.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0134] 1. Satellite communication

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

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

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

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

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

[0140] 2. Constellation information.

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

[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, etc.

[0143] Constellation information refers to some information related to the satellite constellation, mainly including Orbital Plane Parameters and Satellite Level Parameters, etc. In some scenarios, constellation information can also be called ephemeris information.

[0144] 3. Satellite Edge Computing

[0145] Deploying edge services on satellites can enable satellite edge computing. As Figure 3 shown, the UE establishes a PDU session, and the user plane path is UE, RAN, GEO UPF (i.e., L-PSA in the figure), and terrestrial PSA (the user plane path is shown as the dotted line in the figure). By deploying UPF on the satellite, satellite edge computing (EC) can be enabled. In this way, the data packets of the UE accessing the on-board EC service can be directly split by the on-board UPF to the edge computing platform. It avoids the packets being first sent to the terrestrial PSA and then sent by the terrestrial PSA to the edge computing platform, thereby reducing the user plane path, reducing the service communication delay, and enhancing the user experience.

[0146] 4. Satellite Local Switching

[0147] By deploying UPF on the satellite, satellite local switching can be enabled, or it can also be called local data switching under the satellite. As Figure 4As shown in the figure, UE1 establishes a PDU session-1 through satellite backhaul. The user plane path is UE, RAN1, GEO UPF-1, (optional) terrestrial PSA-1 (as shown by the dotted line in the figure); UE2 establishes a PDU session-2 through satellite backhaul. The user plane path is UE, RAN2, GEO UPF-2, (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. By enabling direct communication between UE1 and UE2 through the on-board UPF (i.e., GEO UPF-1 and GEO UPF-2), that is, local switch, the communication path between UE1 and UE2 can be shortened, improving the user experience.

[0148] As described above in connection with Figure 1 the scenarios to which the embodiments of the present application can be applied are introduced, and the basic concepts involved in the present application are also briefly introduced. In the following, the communication methods and devices provided by the present application will be described in detail with reference to the accompanying drawings.

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

[0150] To facilitate understanding of the embodiments of the present application, the following points are explained.

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

[0152] The information enabled by 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. For example, but not limited to, the information to be enabled can be directly enabled, such as the information to be enabled itself or the index of the information to be enabled, etc. It is also possible to indirectly enable the information to be enabled by enabling other information, where there is an association relationship between the other information and the information to be enabled. It is also possible to only enable a part of the information to be enabled, while the other parts of the information to be enabled are known or pre-agreed. For example, it is also possible to achieve the enabling of specific information by relying on the pre-agreed (such as protocol-defined) arrangement order of each piece of information, thereby reducing the enabling overhead to a certain extent. At the same time, it is also possible to identify the common parts of each piece of information and enable them uniformly to reduce the enabling overhead caused by enabling the same information separately.

[0153] Second, the first, second, and various numerical numbers (e.g., "#1", "#2", etc.) shown in this application are only for convenience of description and are used to distinguish objects, and are not used 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 the objects described in this way can be interchanged under appropriate circumstances so as to be able to describe solutions other than the embodiments of this application.

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

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

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

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

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

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

[0160] Figure 5The (a) of [Figure 0] shows an exemplary block diagram of the method 500(a) provided by the embodiments of the present application. It should be understood that the method 500(a) can be executed by a session management network element, or by components (such as chips or circuits) configured in the session management network element. The present application does not make a limitation. For convenience, the following takes the session management network element executing the method 500(a) as an example for illustration.

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

[0162] Exemplarily, the service information is used to indicate one or more services supported by the satellite, or in other words, the service information includes information on one or more services supported by the satellite. Services can be represented by service identifiers. The service identifier can be represented by at least one of the following: application identifier (App ID), fully qualified domain name (FQDN), internet protocol (IP) quintuple, IP triple, data network name (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; as 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 accessed by the terminal device, or in other words, the terminal device accesses the satellite through the satellite backhaul method.

[0164] The following makes 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. Or rather, the session management network element determines the first data network access identifier corresponding to the location information of the terminal device and the satellite backhaul type information. Or rather, the session management network element determines the first data network access identifier of the terminal device that accesses the core network through satellite backhaul based on the location information of the terminal device. For example, the session management network element determines one or more second data network access identifiers according to the location information of the terminal device, and then the session management network element determines the first data network access identifier from the one or more second data network access identifiers according to the satellite backhaul type information corresponding to the terminal device. The first data network access identifier corresponds to the satellite. That is to say, the session management network element may determine multiple second data network access identifiers according to the location information of the terminal device, and then the session management network element may determine the first data network access identifier corresponding to the satellite from the multiple second data network access identifiers according to the satellite backhaul type information of the terminal device. The satellite backhaul type information is used to indicate the type of satellite backhaul through which the terminal device accesses the satellite. For example, the satellite backhaul type information is used to indicate that the terminal device accesses the satellite through geostationary orbit satellite backhaul. It should be understood that the session management network element may obtain the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device 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, and the create session management context request message includes the identification information of the terminal device, the location information of the terminal device, and the satellite backhaul type information corresponding to the terminal device. The session management network element obtains the location information of the terminal device and the satellite backhaul type information corresponding to the terminal device from the create session management context request message.

[0165] Furthermore, the session management network element determines the service information according to the first data network access identifier and the first configuration information. Wherein, 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 has pre-saved the first configuration information before S501. For example, before the above solution, the session management network element receives the first configuration information from the application function network element, and then further saves 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 according to the location information of the terminal device, the satellite backhaul type information corresponding to the terminal device, and the constellation information of the satellite. Another example is that the session management network element determines the first data network access identifier according to 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 here that when the terminal device has multiple backhaul links, there may be multiple data network access identifiers corresponding to the location information of the terminal device and the satellite backhaul type information. In this case, combining the constellation information of the satellite or the identification information of the satellite can determine the data network access identifier corresponding to the 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 after the mobility management network element determines the constellation information of the satellite, it is sent to the session management network element, which is not limited in this application. For example, when the access network device uses different identification information when accessing different constellations, the session management network element can determine the constellation information of the satellite according to the identification information of the access network device corresponding to the terminal device, where the identification information of the access network device can refer to the transport layer identification information of the access network device or the identification of the access network device itself; another example is that when different constellations use different frequency bands, the session management network element can determine the constellation information of the satellite according to the frequency used by the satellite. Or, after the mobility management network element determines the constellation information through the above solution and sends it to the session management network element, which is not limited in this application.

[0169] Similarly, in the above example, the identification information of the satellite can be determined by the session management network element, or after the mobility management network element determines the identification information of the satellite, it is sent to the session management network element, which is not limited in this application. For example, the session management network element can determine the identification information of the satellite corresponding to the location information of the terminal device according to 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 identification information of the satellite. Or, after the mobility management network element determines the identification information of the satellite through the above solution and sends it to the session management network element, which is not limited in this application.

[0170] In another implementation, the session management network element obtains the identification information of the satellite, and then determines the service information according to the identification information of the satellite and the second configuration information, where the second configuration information includes the correspondence between the identification information of the satellite and the service information.

[0171] It should be understood that in this implementation manner, the identity information of the satellite can be determined by the session management network element, or can be sent to the session management network element after the mobility management network element determines the identity information of the satellite. This application does not make any limitations. For the specific implementation manner, reference can be made to the above examples.

[0172] In yet another implementation manner, the session management network element obtains the constellation information of the satellite, and then determines the service information according to the constellation information of the satellite and the third configuration information, where the third configuration information includes the corresponding relationship between the constellation information of the satellite and the service information. For example, in a scenario where any satellite in a constellation corresponds to the same service, in this case, the session management network element can determine the service information supported by the satellite according to the constellation information of the satellite.

[0173] It should be understood that in this implementation manner, the constellation information of the satellite can be determined by the session management network element, or can be sent to the session management network element after the mobility management network element determines the constellation information of the satellite. This application does not make any limitations. For the specific implementation manner, reference can be made to the above examples.

[0174] S502, the session management network element determines whether to allow the terminal device to access the services supported by the satellite according to the service information.

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

[0176] Therefore, based on the above solution, the session management network element determines whether to allow the terminal device to access the services supported by the satellite, which may include: the session management network element determines 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 subscription data of the terminal device.

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

[0178] Therefore, based on the above solution, the session management network element determines whether to allow the terminal device to access the satellite-supported services, which may include: the session management network element determines 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. 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 user plane network element on the satellite into the user plane path of the terminal device.

[0180] Exemplarily, in one case (denoted as Case 1), when it is determined that the terminal device is allowed to access at least one of the satellite-supported services, or in other words, when it is determined that at least one of the services allowed for the terminal device to access includes the satellite-supported services, or in other words, when it is determined that at least one of the services allowed for the terminal device to access overlaps with the satellite-supported services, the session management network element inserts the user plane network element on the satellite into the user plane path of the terminal device. The user plane network element on the satellite can be used as a traffic splitting point, or as a local anchor user plane network element, or as a session anchor user plane network element, which is not limited in this application. Among them, when the user plane network element on the satellite is used as the local anchor user plane network element, the session establishment of the terminal device is completed, 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 is used as the session anchor user plane network element, the session establishment of the terminal device is completed, 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 the session management network element inserts the user plane network element on the satellite into the user plane path of the terminal device, which may mean that the session management network element inserts the user plane network element on the satellite into the user plane path of the terminal device as a traffic splitting point and / or a local anchor session management network element, or it may mean that the session management network element uses the user plane network element on the satellite as the session anchor user plane network element.

[0181] Furthermore, if the user plane network element on the satellite is used as a traffic splitting point and / or a local anchor user plane network element, the session management network element selects a ground anchor user plane network element for the session of the terminal device. That is to say, in Case 1, 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 user plane network element on the satellite into the user plane path of the terminal device, and then selects a ground anchor user plane network element for the session of the terminal device.

[0182] Optionally, this case further includes S504, where the session management network element sends a traffic steering rule to the user plane network element on the satellite.

[0183] Exemplarily, 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, a routing rule, etc., which is not limited in this application. This traffic steering rule is used to instruct the user plane network element on the satellite to directly send the data packets for the services on the satellite to the corresponding service platform. For example, this steering rule is used to instruct the user plane network element on the satellite to directly send the data packets for the edge computing service on the satellite to the corresponding edge computing platform. Correspondingly, based on this traffic steering rule, after the user plane network element on the satellite receives the data packets for the edge computing service on the satellite, it directly sends the data packets to the corresponding service platform, without first sending the data packets to the core network device on the ground and then having the core network device on the ground send them to the corresponding service platform, thereby reducing latency and improving the user experience.

[0184] In another case (denoted as case 2), when it is determined that the terminal device is not allowed to access any of the services supported by the satellite, or in other words, when it is determined that none of the services allowed for the terminal device to access include any of the services supported by the satellite, or when it is determined that there is no overlap between the services allowed for the terminal device to access and 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.

[0185] Furthermore, the session management network element selects a ground anchor user plane network element for the session of the terminal device. That is, in case 2, when 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 user plane path of the terminal device, but directly selects a ground anchor user plane network element for the session of the terminal device.

[0186] It should be understood that the above case 1 and case 2 are two parallel solutions, or in other words, two branches of a complete solution. That is, for a terminal device, both case 1 and case 2 may occur. Specifically, when 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 executes the solution corresponding to case 1; when 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 executes the solution corresponding to case 2.

[0187] Based on the above solution, 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 user plane network element on the satellite 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 user plane network element on the satellite is not inserted into the user plane path of the terminal device. Based on this, the user plane network element on the satellite can be inserted into the user plane path of the terminal device that requires the service provided by the user plane network element on the satellite, so as to support these terminal devices to access the services on the satellite; and the user plane network element on the satellite is not inserted into the user plane path of the terminal device that does not require the service provided by the user plane network element on the satellite, so as to shorten the length of the user plane path of these terminal devices, reduce the transmission delay, and improve the user experience.

[0188] Figure 5 Figure (b) of shows an exemplary block diagram of method 500(b) provided by an embodiment of the present application. It should be understood that method 500(b) can be executed by the session management network element, or by components (such as chips or circuits) configured in the session management network element, which is not limited in the present application. For convenience, the following takes the session management network element executing method 500(b) as an example for description.

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

[0190] As a possible implementation, the session management network element determines whether to allow the terminal device to perform local data exchange under the satellite according to the subscription data or policy information of the terminal device. Among them, the subscription data or policy information may include local data exchange indication information. For example, the session management network element obtains the subscription data of the terminal device through the data management network element, and then determines whether to allow the terminal device to perform local data exchange under the satellite according to the local data exchange indication information in the subscription data. Among them, the local data exchange indication information is used to indicate whether to allow the terminal device to perform local data exchange under the satellite. As a possible implementation, the local data exchange indication information can adopt different values to indicate different situations. For example, when the value of the local data exchange indication information is 1, it means that the terminal device is allowed to perform local data exchange under the satellite, and when the local data exchange indication information is 0 (or empty), it means that the terminal device is not allowed to perform local data exchange under the satellite.

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

[0192] Exemplarily, in one case (denoted as case a), when it is determined that the terminal device is allowed to access local data exchange under the satellite, or in other words, when it is determined that the terminal device supports local data exchange under 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. The user plane network element on the satellite can be used as a shunt point, or as a local anchor user plane network element, or as a session anchor user plane network element, which is not limited in this application.

[0193] Furthermore, the session management network element selects a ground anchor user plane network element for the session of the terminal device. That is to say, in case a, when the session management network element determines that the terminal device is allowed to perform local data exchange under 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, and then selects a ground anchor user plane network element for the session of the terminal device.

[0194] Optionally, in this case, it further includes S530, where the session management network element sends a traffic steering rule to the user plane network element on the satellite.

[0195] Exemplarily, 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 is used to instruct the user plane network element on the satellite to send the data packet destined for the terminal device on the satellite to the corresponding terminal device through the local data exchange of the satellite. Or in other words, this traffic steering rule is used to instruct the user plane network element on the satellite to send the data packet with the destination address pointing to the terminal device on the satellite to the access network device corresponding to the terminal device. Or in other words, this traffic steering rule is used to instruct the user plane network element on the satellite to send the data packet matching the terminal device on the satellite through the local data exchange. Correspondingly, based on this traffic steering rule, when the user plane network element on the satellite receives a data packet destined for a terminal device connected to the satellite, the user plane network element on the satellite directly sends this data packet to the corresponding access network device, thereby shortening the data transmission path and improving the user experience. In another case (denoted as case b), when it is determined that the terminal device is not allowed to access local data exchange under the satellite, or in other words, when it is determined that the terminal device does not support local data exchange under 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.

[0196] Furthermore, the session management network element selects a ground anchor user plane network element for the session of the terminal device. That is to say, in case b, when the session management network element determines that the terminal device is not allowed to perform local data exchange under 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, but directly selects a ground anchor user plane network element for the session of the terminal device.

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

[0198] Based on the above solution, when the terminal device needs to perform local data exchange under the satellite, the user plane network element on the satellite can be inserted into the user plane path of the terminal device, so as to support the terminal device to perform local data exchange under the satellite; when the terminal device does not need to perform local data exchange under the satellite, the user plane network element on the satellite is not inserted into the user plane path of the terminal device, so as to shorten the length of the user plane path of these terminal devices, reduce the transmission delay, and improve the user experience.

[0199] Based on the 5G system, the communication method provided in the embodiments of the present application will be introduced below. In one implementation, the SMF in method 600 to method 1000 may correspond to the session management network element in method 500, the AMF in method 600 to method 1000 may correspond to the mobility management network element in method 500, the UE in method 600 to method 1000 may correspond to the terminal device in method 500, and the DNAI in method 600 to method 1000 may correspond to the data network access identifier in method 500. Method 500 to method 1000 can be applied to Figure 1 or Figure 2 the network architecture shown.

[0200] Figure 6 The exemplary flowchart of method 600 provided in the embodiments of the present application is shown. Method 600 will be described below with reference to each step.

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

[0202] Exemplarily, the correspondence between the DNAI and the service information can be understood as the service deployment information corresponding to the satellite. The service information is used to indicate one or more services supported by the satellite. In one implementation, the service information may include FQDNs corresponding to different services. That is to say, the correspondence between the DNAI and the service information here can be the correspondence between the DNAI and one or more FQDNs. The DNAI is used to identify the user plane connection for accessing the services supported by the satellite. For example, in the satellite edge computing scenario, the service may refer to the EC service. At this time, the DNAI can be understood as the location information of the EC platform or the identifier of the user plane connection corresponding to accessing the EC platform.

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

[0204] In one implementation, the SMF obtains the correspondence between the DNAI and the service information through the AF. For example, the AF sends an AF request message to the SMF through the NEF / PCF. The AF request message includes the correspondence between the DNAI and the service information. After receiving the AF request message, the SMF saves the correspondence between the DNAI and the service information locally. In another implementation, the SMF obtains the correspondence between the DNAI and the service information through local configuration information.

[0205] It should be understood that the present application does not limit the specific timing of the execution of S601, 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] Exemplarily, the UE sends a PDU session establishment request to the AMF through a NAS message. Specifically, for example, the UE sends an AN message to the gNB. The AN message carries a NAS message, and the NAS message includes a PDU session ID and a session establishment request. After receiving the AN message from the UE, the gNB sends an N2 message to the AMF. The N2 message includes the PDU session ID, the UE location information (ULI), and the session establishment request. The UE location information is used to identify the geographical location where the UE is currently located.

[0208] It should be understood that the above PDU session establishment request can also be replaced by a PDU session modification request, a PDU session release request, etc., which are not limited in this application. That is to say, the solution provided in the embodiments of this application can be applied to the PDU session establishment process, or the PDU session modification process, or the PDU session release process of the UE.

[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] Exemplarily, after receiving the PDU session establishment request from the UE, the AMF sends a create session management context request (Nsmf_PDUSession_CreateSMContext request) message to the SMF, and the create session management context request message includes the location information of the UE.

[0211] If the AMF determines that the UE accesses the network through satellite backhaul (SATB), the AMF carries the satellite backhaul type information in the create session management context request message, and the satellite backhaul type information is used to indicate the backhaul type of the UE accessing the satellite. For example, the satellite backhaul type information is used to indicate that the UE accesses the GEO satellite through the GEO satellite backhaul type.

[0212] S604. The SMF determines the DNAI corresponding to the location information of the UE and the satellite backhaul type information.

[0213] Exemplarily, after obtaining the location information of the UE and the satellite backhaul type information from the create session management context request message, the SMF determines the corresponding DNAI according to the location information of the UE and the satellite backhaul type information.

[0214] As a possible implementation manner, the SMF locally stores configuration information, which can be pre-configured for the SMF in advance or obtained by the SMF from other network elements. The configuration information includes the correspondence between the location information of the UE, the satellite backhaul type information, and the DNAI. The SMF determines the DNAI according to the obtained location information of the UE, the satellite backhaul type information, and the 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 for the SMF to obtain 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 constellation information of the satellite based on the gNB ID / gNB IP; in another implementation, different constellations use different frequency bands, and the SMF can determine the constellation information of the satellite 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, which is not limited in this application.

[0216] S605. The SMF obtains the service information supported by the satellite.

[0217] Exemplarily, after the SMF determines the DNAI, based on the DNAI and the correspondence between the DNAI and the service information obtained in S601, the SMF determines the service information supported by the satellite.

[0218] S606. The SMF determines whether to allow the UE to access the services supported by the satellite.

[0219] Exemplarily, the SMF can first determine the service information allowed for the UE to access through the UDM or PCF.

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

[0221] For another example, the SMF obtains the policy information for the UE through the PCF, and the policy information includes the identifiers of the services allowed for the UE to access. Specifically, for example, the SMF sends a policy information request message to the PCF, and the policy information request message includes the identifier information of the UE. After receiving the policy information request message from the SMF, the PCF sends a policy information response message to the SMF, and the policy information response message includes the policy information for the UE. The SMF obtains the identifiers of the services allowed for the UE to access from the policy information for the UE.

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

[0223] It should be understood that the services allowed for the UE to access can also be referred to as the services that the UE has the right to access, or the services subscribed by the UE, or the services that the UE can use, or the services supported by the UE, etc., and this application does not make any limitations.

[0224] Furthermore, the SMF determines whether to allow the UE to access the services supported by the satellite based on the identifiers of the services allowed for the UE to access and the service information supported by the satellite.

[0225] When at least one of the identifiers of the services allowed for the UE to access matches the service information supported by the satellite, or in other words, when the service information supported by the satellite includes at least one of the identifiers of the services allowed for the UE to access, the SMF determines to allow the UE to access at least one of the services supported by the satellite. In this case, the session management network element inserts the UPF on the satellite (denoted as GEO UPF) into the user plane path of the UE.

[0226] When none of the identifiers of the services allowed for the UE to access match the service information supported by the satellite, or in other words, when the service information supported by the satellite does not include any of the identifiers of the services allowed for the UE to access, the SMF determines not to allow the UE to access any of the services supported by the satellite. In this case, the session management network element does not insert the GEO UPF into the user plane path of the UE.

[0227] The following gives an exemplary description of these two cases respectively.

[0228] Case A:

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

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

[0231] Exemplarily, in the case where the SMF determines to allow the UE to access at least one of the satellite-supported services, the SMF selects the GEO UPF as the UL CL / BP, and then sends an N4 session modification request message to the GEO UPF. The N4 session modification request message includes a traffic steering rule, which is used to instruct the GEO UPF to directly send the data packets for the services on the GEO satellite to the edge computing platform. Or, the traffic steering rule is used to instruct to divert the services that allow the UE to access and are also supported by the satellite to the edge computing platform (SAT EC) on the satellite. Alternatively, the SMF can also instruct the GEO UPF to act as the local PSA through the N4 session modification request message.

[0232] Furthermore, the SMF selects the 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 - terrestrial PSA.

[0234] That is to say, in the case where the UE is allowed to access at least one of the satellite-supported services, the SMF first selects the GEO UPF 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 to say, in the case where the UE is allowed to access at least one of the satellite-supported services, the SMF selects the GEO UPF as the session anchor UPF.

[0236] Case B:

[0237] S609, the SMF selects the terrestrial PSA.

[0238] Exemplarily, after the SMF determines not to insert the UPF corresponding to the DNAI as the diversion 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 - terrestrial PSA.

[0240] That is to say, when the UE is not allowed to access any of the satellite - supported services, the SMF does not select the GEO UPF but directly selects the terrestrial PSA.

[0241] In the above - mentioned solution, according to whether the UE is allowed to access the services on the satellite, it is determined whether to insert the UPF on the satellite into the user plane path of the UE, thereby reducing the latency and improving the user experience.

[0242] On the one hand, the solution of the embodiment of the present application can pre - insert the UPF on the satellite into the user plane path of the UE. In this case, when the UE initiates a certain service on the satellite, it can be directly supported by the UPF on the satellite. For example, by pre - inserting the UPF on the satellite as a shunt point, when the UE initiates the EC service on the satellite, the UPF on the satellite can directly shunt the packets to the on - satellite EC platform. This solution can save latency compared with the method of dynamically inserting the UPF on the satellite. Specifically, if the SMF decides whether to insert the UPF on the satellite into the user plane path of the UE according to the service that the UE will access when the UE initiates a service. When insertion is required, the SMF selects the UPF on the satellite and sends the corresponding policy to it. Since the interaction between the SMF and the UPF on the satellite is satellite - terrestrial interaction and the latency is very long, this will lead to a long time for establishing the user plane connection, resulting in excessive latency. In contrast, the solution provided by the embodiment of the present application can reduce the duration of establishing the user plane connection by pre - inserting the UPF on the satellite and improve the user experience.

[0243] On the other hand, in the solution of the embodiment of the present application, a satellite UPF is not inserted into the user plane path of a UE that cannot access services on the satellite. Compared with the solution in which the SMF uniformly inserts the satellite UPF into the user plane path, this solution can shorten the length of the user plane path of some UEs (i.e., UEs that do not support accessing services on the satellite), reduce the latency of data transmission, and improve the user experience. For example, during the session establishment process of the UE, the SMF uniformly pre-inserts the satellite UPF into the user plane path of the UE. However, if the UE is not allowed to access any services on the satellite, it is unnecessary to pre-insert the satellite UPF into the user plane path of the UE, which will add an extra UPF to the path between the base station and the terrestrial PSA, thereby increasing the message processing process and resulting in an increase in the latency of message transmission, affecting the user experience. In contrast, in the solution provided by the embodiment of the present application, the satellite UPF is inserted into the user plane path of the UE only when the UE is allowed to access at least one service on the satellite, and when the UE is not allowed to access any service on the satellite, the satellite UPF is not inserted into the user plane path of the UE, which not only does not affect the services of the UE but also reduces the latency of data transmission, thereby improving the user experience.

[0244] Figure 7 FIG. 4 shows an exemplary flowchart of method 700 provided by an embodiment of the present application. Method 700 will be described exemplarily below in conjunction with each step.

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

[0246] Exemplarily, the correspondence between the SAT ID and service information can be understood as the service deployment information corresponding to the satellite, and the service information is used to indicate one or more services supported by the satellite. The description of the service information can refer to S601 in method 600 and will not be elaborated here. The SAT ID is used to identify the satellite, and the SAT ID can be the identification information of the satellite itself or the identification information of the UPF on the satellite (SAT UPF ID), which is not limited in the present application.

[0247] In one implementation, the SMF can obtain the correspondence between the SAT ID and service information through the AF; in another implementation, the SMF can obtain the correspondence between the SAT ID and service 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. For the sake of brevity, they will not be elaborated here.

[0251] S704. The SMF determines the SAT ID corresponding to the location information of the UE.

[0252] Exemplarily, the SMF obtains the location information of the UE from the Create Session Management Context Request message, and then determines the corresponding SAT ID according to the location information of the UE.

[0253] As a possible implementation, the SMF locally stores configuration information, which can be pre-configured for the SMF in advance or obtained from other network elements. The configuration information includes the correspondence between the location information of the UE and the SAT ID. The SMF determines the SAT ID according to the obtained location information of the UE and the configuration information.

[0254] S705. The SMF determines the service information corresponding to the SAT ID.

[0255] Exemplarily, after the SMF determines the SAT ID, according to the SAT ID and the correspondence between the SAT ID and the service information obtained in S701, the SMF determines the service information supported by the satellite.

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

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

[0258] Figure 8 FIG. shows an exemplary flowchart of method 800 provided by an embodiment of the present application. Method 800 will be exemplarily described below in conjunction with each step.

[0259] S801. The SMF obtains the correspondence between the DNAI and the service information.

[0260] 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. For the sake of brevity, they will not be elaborated here.

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

[0263] Exemplarily, after the AMF obtains the location information of the UE and the satellite backhaul type information, it determines the corresponding DNAI according to the location information of the UE and the satellite backhaul type information.

[0264] As a possible implementation, the AMF locally stores configuration information, which can be pre-configured for the AMF in advance or obtained from other network elements. The configuration information includes the correspondence between the location information of the UE, the satellite backhaul type information, and the DNAI. The AMF determines the DNAI according to the location information of the UE, the satellite backhaul type information, and the configuration information.

[0265] For the specific implementation method, reference can be made to S604 in method 600. The difference is that S604 in method 600 is executed by the SMF, and S803 in method 800 is executed by the 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] Exemplarily, after the AMF determines the DNAI corresponding to the location information of the UE and the satellite backhaul type information, it sends a create session management context request message to the SMF, and the create session management context request message includes the DNAI.

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

[0269] S806, the SMF determines whether to allow the UE to access the services supported by the satellite.

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

[0271] Figure 9 The exemplary flowchart of method 900 provided by the embodiments of the present application is shown. The method 900 will be described exemplarily below in combination with each step.

[0272] S901, the SMF obtains the correspondence between the SAT ID and the service 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 elaborated here.

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

[0276] Exemplarily, after receiving the PDU session establishment request message from the UE, the AMF determines the location information of the UE, and then determines the SAT ID corresponding to the location information of the UE according to the location information of the UE.

[0277] As a possible implementation, the AMF locally stores configuration information, which can be pre-configured for the SMF or obtained from other network elements. The configuration information includes the correspondence between the location information of the UE and the SAT ID. The AMF determines the SAT ID according to the location information of the UE and the configuration information.

[0278] For the specific implementation method, reference can be made to S704 in method 700, the difference being that S704 in method 700 is executed by the SMF, and S903 in method 900 is executed by the 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] Exemplarily, after receiving the PDU session establishment request from the UE, the AMF sends a create session management context request message to the SMF, and the create session management context request message includes the SAT ID.

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

[0282] S906, the SMF determines whether to allow the UE to access the services supported by the satellite.

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

[0284] Figure 10 The exemplary flowchart of method 1100 provided by the embodiment of the present application is shown. The method 1100 will be described exemplarily below in combination with each step.

[0285] S1001, 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.

[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 elaborated here.

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

[0289] Exemplarily, the SMF may determine whether to allow the UE to perform local data exchange under the satellite according to the UE's subscription data or policy information. Among them, the subscription data or policy information may include local data exchange indication information. For example, 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 the satellite according to the local data exchange indication information in the subscription data. The local data exchange indication information is used to indicate whether to allow the UE to perform local data exchange under the satellite. As a possible implementation, the local data exchange indication information may adopt different values to indicate different situations. For example, when the value of the local data exchange indication information is 1, it means that the UE is allowed to perform local data exchange under the satellite, and when the local data exchange indication information is 0 (or empty), it means that the UE is not allowed to perform local data exchange under the satellite.

[0290] In the case of allowing the UE to perform local data exchange under the satellite, the session management network element inserts the UPF on the satellite (denoted as GEO UPF) into the user plane path of the UE.

[0291] In the case of not allowing the UE to perform local data exchange under the satellite, the session management network element does not insert the UPF on the satellite (denoted as GEO UPF) into the user plane path of the UE.

[0292] The following gives exemplary descriptions of these two cases respectively.

[0293] Case A:

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

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

[0296] Exemplarily, when the SMF determines that the UE is allowed to perform local data exchange under the 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 steering rule, and the traffic steering rule is used to instruct the GEO UPF to send data packets directed to the UE on the satellite to the corresponding UE through satellite local data exchange. In other words, the traffic steering rule is used to instruct the GEO UPF to send data packets with a destination address directed to the UE on the satellite to the gNB corresponding to the UE. In other words, the traffic steering rule is used to instruct the GEO UPF to send data packets matching the UE on the satellite through local data exchange.

[0297] Case B:

[0298] S1006, SMF selects ground PSA.

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

[0300] Based on the above solution, when the UE needs to perform local data exchange under the satellite, the GEO UPF can be inserted into the user plane path of the UE, thereby supporting the UE to perform local data exchange under the satellite; and when the UE does not need to perform local data exchange under the satellite, the GEO UPF is not inserted into the user plane path of the UE, thereby shortening the length of the user plane path of the UE, reducing the transmission delay, and improving the 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 UPF of the satellite. Specifically, the SMF determines whether the UE is allowed to access the services supported by the satellite and whether the UE is allowed to perform local data exchange under the satellite. In the case where the UE is allowed to access at least one of the services supported by the satellite, or the UE is allowed to perform local data exchange under the satellite, the SMF inserts the UPF on the satellite, otherwise, the SMF does not insert the UPF on the satellite.

[0302] Corresponding to the methods given in the above-mentioned method embodiments, the embodiments of the present application also provide corresponding devices, which include modules for executing the corresponding methods in the above-mentioned method embodiments. The module can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the above-mentioned method embodiments are also applicable to the following device embodiments. Therefore, the contents not described in detail can be referred to the above method embodiments, and for the sake of brevity, they will not be repeated here.

[0303] Figure 11 It is a schematic block diagram of a communication device 10 provided by an embodiment of the present application. The device 10 includes a processing module 11. Optionally, the device 10 may further include a transceiver module 11. The processing module 11 is used for data processing, and the transceiver module 12 can implement corresponding communication functions, or rather, the transceiver module 12 is used for performing operations related to reception and transmission, and the processing module 11 is used for performing other operations except reception and transmission. 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), and the storage module can be used to store instructions and / or data. The processing module 11 can read the instructions and / or data in the storage module so that the device can implement the actions of the device or network element in the foregoing various method embodiments.

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

[0306] The device 10 can implement the steps or processes corresponding to the session management network element (such as an SMF) in the foregoing method embodiment. Among them, the processing module 11 can be used to perform operations related to the processing of the application session management network element (such as an SMF) in the foregoing method embodiment, and the transceiver module 12 can be used to perform operations related to the reception and transmission of the session management network element (such as an SMF) in the foregoing method embodiment.

[0307] Exemplarily, the device 10 may correspond to the session management network element in method 500 of the embodiment of the present application, or the SMF in methods 600 to 1000. The device 10 may include a module for executing the method executed by the session management network element (or SMF) in Figures 5 to 10 And each module in the device 10 and the above other operations and / or functions respectively are for implementing the corresponding processes of the method shown in Figures 5 to 10 shown method.

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

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

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

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

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

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

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

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

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

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

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

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

[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. Among them, the receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they may be collectively referred to as a transceiver.

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

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

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

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

[0325] Figure 13 Fig. shows a schematic structural diagram of a simplified network device 30. The network device includes a part 31 and a part 32. The part 31 is mainly used for receiving and transmitting radio frequency signals and converting radio frequency signals into baseband signals; the part 32 is mainly used for baseband processing and controlling the network device, etc. The part 31 may usually be referred to as a transceiver module, a transceiver, a transceiver circuit, or a transceiver, etc. The part 32 is usually the control center of the network device and may usually be referred to as a processing module, which is used to control the network device to execute the processing operations on the network device side in the above method embodiment.

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

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

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

[0329] The transceiver module of part 31 is used to execute Figures 5 to 10 the steps related to the transceiver of any network device in the method shown; part 32 is used to execute 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 only for example and not for limitation, the above network device including a transceiver module and a processing module may not depend on Figure 10 the structure shown.

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

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

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

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

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

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

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

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

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

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

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

[0342] It should also be understood that the memory mentioned in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM). For example, the RAM can be used as an external cache. By way of example and not limitation, the RAM can include the following various forms: 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 SDRAM (ESDRAM), synchlink DRAM (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 in the processor.

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

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

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

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

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

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

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

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

Claims

1. A communication method, characterized in that, Including: The session management function network element obtains service information, where the service information is used to indicate one or more services supported by the satellite; When the session management function network element determines, according to 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 according to claim 1, wherein The session management function network element obtaining service information includes: The session management function network element determines the data network access identifier DNAI corresponding to the satellite; The session management function network element obtains the service information according to the DNAI and the first configuration information, where the first configuration information includes the correspondence between the DNAI and the service information.

3. The method according to claim 2, wherein The method further includes: The session management function network element receives the first configuration information from the application function network element AF.

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, and the DNAI is used to identify the user plane connection for accessing the service supported by the satellite.

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

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 identification information of the satellite.

7. The method according to claim 5 or 6, characterized in that The satellite backhaul type information indicates that the terminal device accesses the satellite through a geostationary orbit satellite backhaul.

8. The method according to claim 6, wherein Also including: The session management function network element receives the identification of the satellite from the mobility management network element.

9. The method according to claim 1, characterized in that, The service is represented by at least one of the following identifications: application identification, fully qualified domain name FQDN.

10. The method according to any one of claims 1 to 9, characterized in that The user plane network element on the satellite is the user plane function network element UPF on the satellite.

11. The method according to any one of claims 1 to 10, characterized in that, The session management function network element determining that the terminal device is allowed to access at least one of the services supported by the satellite includes: The session management function network element determines that the terminal device is allowed to access at least one of the services supported by the satellite according to the service information and the policy information, where the policy information includes the identification of the services that the terminal device is allowed to access; The method further includes: The session management function network element receives the policy information from the policy control network element.

12. The method according to any one of claims 1 to 11, characterized in that, The session management network element inserting the user plane network element on the satellite into the user plane path of the terminal device includes: the session management network element selects the user plane network element on the satellite as a shunt point and inserts it into the user plane path of the terminal device.

13. The method according to any one of claims 1 to 12, characterized in that, Also including: The session management network element sends a traffic steering rule to the user plane network element on the satellite, where the traffic steering rule is used to instruct the user plane network element on the satellite to send the data packet for the service on the satellite to the service platform corresponding to the satellite.

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

15. The device according to claim 14, characterized in that, The processing module is configured to obtain service information, including: The processing module is configured to determine the data network access identifier (DNAI) corresponding to the satellite; The processing module is configured to obtain the service information according to the DNAI and the first configuration information, where the first configuration information includes the correspondence between the DNAI and the service information.

16. The device according to claim 15, characterized in that, The apparatus further includes: A transceiver module, configured to receive the first configuration information from an application function network element (AF).

17. The device according to any one of claims 14 to 16, characterized in that, The user plane network element on the satellite is the user plane network element on the satellite corresponding to the DNAI, and the DNAI is used to identify the user plane connection for accessing the service supported by the satellite.

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

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

20. The device according to claim 18 or 19, characterized in that The satellite backhaul type information indicates that the terminal device accesses the satellite through a geostationary orbit satellite backhaul.

21. The device according to claim 19, characterized in that, The apparatus further includes: a transceiver module, configured to receive the identification of the satellite from a mobility management network element.

22. The device according to claim 14, wherein, The service is represented by at least one of the following: an application identifier, a fully qualified domain name (FQDN).

23. The device according to any one of claims 14 to 22, characterized in that, The user plane network element on the satellite is the user plane function network element (UPF) on the satellite.

24. The device according to any one of claims 14 to 23, characterized in that, The processing module is specifically configured to receive, through the transceiver module, policy information from a policy control network element, where the policy information includes the identification of the service that the terminal device is allowed to access; and determine, according to the policy information and the service information, that the terminal device is allowed to access at least one of the services supported by the satellite.

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

26. The device according to any one of claims 14 to 25, characterized in that, The processing module is further configured to send, through the transceiver module, a traffic steering rule to the user plane network element on the satellite, where the traffic steering rule is used to instruct the user plane network element on the satellite to send the data packet for the service on the satellite to the service platform corresponding to the satellite.

27. A communication device, characterized in that, It includes at least one processor, and the at least one processor is coupled to at least one memory. The at least one processor is configured to execute computer programs or instructions stored in the at least one memory, so that the communication apparatus executes the method according to any one of claims 1 to 13.

28. A chip, characterized in that, It includes a processor and a communication interface. The communication interface is configured to receive data and / or information, and transmit the received data and / or information to the processor. The processor processes the data and / or information to execute the method according to any one of claims 1 to 13.

29. A computer-readable storage medium, characterized in that, A computer program is stored thereon, and when the computer program is executed, it causes the method according to any one of claims 1 to 13 to be executed.

30. A computer program product comprising instructions, characterized in that, When it runs on a computer, it causes the computer to execute the method according to any one of claims 1 to 13.

Images