A communication method and apparatus

Abstract

A communication method and apparatus are disclosed to reduce communication service latency and improve user experience in satellite communication scenarios. A session management function network element determines that the user plane function network element and access network equipment providing services for the PDU session of a terminal device are deployed on the same satellite. The session management function network element sends first session management information to the access network equipment or second session management information to the user plane function network element. The first session management information includes first session information, which indicates the context in which the user plane function network element processes the PDU session. The second session management information includes second session information and third session information; the second session information indicates the context in which the terminal device processes the PDU session, and the third session information indicates the context in which the access network equipment processes the PDU session. This reduces communication between the satellite and ground equipment, thereby reducing communication latency.

Description

Technical Field

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

[0002] Currently, satellite communication is gradually becoming a research hotspot. Satellite communication can supplement terrestrial communication in scenarios where coverage is difficult, such as deserts and oceans. Satellite communication scenarios may involve deploying network elements originally located on the ground to satellites. For example, one possible deployment method is to deploy access network equipment and user plane function network elements on satellites. In this deployment method, the equipment on the satellite and the equipment on the ground need to communicate frequently, which may cause significant communication service latency, thus affecting user experience. Summary of the Invention

[0003] This application provides a communication method and apparatus to reduce communication service latency and improve user experience in satellite communication scenarios.

[0004] In a first aspect, this application provides a communication method, which may include: a session management function network element determining that a user plane function network element and an access network device providing services for a protocol data unit (PDU) session of a terminal device are deployed on the same satellite; then, the session management function network element sends first session management information to the access network device, or the session management function network element sends second session management information to the user plane function network element; the first session management information includes first session information. The session management function network element is deployed on the ground side; the first session information is used to instruct the user plane function network element to process the context of the PDU session; the second session management information includes second session information and third session information, the second session information being used to instruct the terminal device to process the context of the PDU session, and the third session information being used to instruct the access network device to process the context of the PDU session.

[0005] Using the above method, the access network device sends the first session management information to the user plane function network element, and the access network device and the user plane function network element are deployed on the same satellite. Therefore, compared to existing technologies, the session management function network element does not need to send the first session management information to the user plane function network element, reducing the transmission between the session management function network element and the user plane function network element. Alternatively, the session management function network element sends the third session information of the access network device and the second session information of the terminal device through the second session management information. This eliminates the need for the access and mobility management function network element to send the third session information to the access network device and the second session information to the terminal device, further reducing the transmission between the access and mobility management function network element and the access network device compared to existing technologies. Thus, the transmission between satellite-based devices and ground-based devices can be reduced, thereby reducing service latency and improving user experience.

[0006] In one possible design, the session management function network element determines that the user plane function network element and the access network device providing services for the PDU session of the terminal device are deployed on the same satellite. The session management function network element can receive first information from the access and mobility management function network element, indicating that the user plane function network element and the access network device providing services for the PDU session of the terminal device are deployed on the same satellite. Then, based on the first information, the session management function network element determines that the user plane function network element and the access network device providing services for the PDU session of the terminal device are deployed on the same satellite. In this way, the session management function network element can accurately determine that the user plane function network element and the access network device are deployed on the same satellite, thereby reducing subsequent transmissions between devices on the satellite and devices on the ground.

[0007] In one possible design, the first information may include one or more of the following: indication information that the access network device and the user plane function network element are independently deployed on the same satellite; indication information that the access network device and the user plane function network element are co-deployed on the same satellite; information about the satellite where the access network device and the user plane function network element are located; information about the access network device; or information about the user plane function network element.

[0008] In one possible design, before the session management function (SMF) network element sends the first session management information to the access network device, the SMF network element may also receive first capability information from the user plane function (MPF) network element. This first capability information indicates that the MPF network element supports the ability to reduce interactions between the MPF network element and the SMF network element. In this way, the SMF network element can subsequently send the first session management information to the access network device to reduce transmission between the SMF network element and the MPF network element, thereby reducing communication latency.

[0009] In one possible design, the first session management information may further include information about the user plane function network element. This allows the access network device to accurately send the first session information to the user plane function network element based on the information of the user plane function network element.

[0010] In one possible design, the first session management information may further include reduced signaling indication information, which instructs the access network device to send the first session information to the user plane function element. This ensures that the access network device accurately sends the first session information to the user plane function element.

[0011] In one possible design, after the session management function (SMF) network element sends the first session management information to the access network device, the SMF network element can also receive second information from the access network device. This second information indicates that both the user plane function (MPF) network element and the access network device have completed the context processing of the PDU session. In this way, the information indicating that the MPF network element has completed the PDU session context processing can be transmitted from the access network device to the SMF network element, thereby reducing the transmission between the SMF network element and the MPF network element.

[0012] In one possible design, after the Session Management Function (SMF) element sends the second session management information to the User Plane Function (MPF) element, the SMF element can also receive notification information from the MPF element that the access network device has completed context processing of the PDU session. In this way, the information indicating that the access network device has completed context processing of the PDU session can be transmitted from the MPF element to the SMF element, eliminating the need for the Access and Mobility Management (AMO) element to obtain the information from the access network device and then send it to the SMF element, thereby reducing transmission between the AMO element and the access network device.

[0013] In one possible design, after the Session Management Function (SMF) network element sends the second session management information to the User Plane Function (MPF) network element, the SMF network element can also receive notification information from the MPF network element that the terminal device has completed the context processing of the PDU session. In this way, the information indicating that the terminal device has completed the context processing of the PDU session can be transmitted from the MPF network element to the SMF network element, without the Access and Mobility Management (AMO) network element needing to obtain it from the access network device and then send it to the SMF network element, thereby reducing the transmission between the AMO network element and the access network device.

[0014] Secondly, this application provides a communication method, which may include: an access network device receiving first session management information from a session management function network element, the first session management information including first session information, and sending the first session information to the user plane function network element; wherein the first session information is used to instruct the user plane function network element to process the context of the PDU session of the terminal device; wherein the user plane function network element and the access network device are deployed on the same satellite, and the session management function network element is deployed on the ground side.

[0015] Using the above method, the access network device sends the first session information to the user plane function network element. Compared with the prior art, it is not necessary for the session management function network element to send the first session information to the user plane function network element. This reduces the transmission between the session management function network element and the user plane function network element, thereby reducing the transmission between the satellite equipment and the ground equipment, thus reducing service latency and improving user experience.

[0016] In one possible design, the access network device can also send second capability information to the access and mobility management function (AMF) network element. This second capability information indicates that the access network device supports signaling interaction with the user plane function (MPF) network element. This allows the access network device to subsequently send the first session information to the MPF network element.

[0017] In one possible design, the first session management information may further include information about the user plane function network element. This allows the access network device to accurately send the first session information to the user plane function network element based on the information of the user plane function network element.

[0018] In one possible design, the first session management information may further include reduced signaling indication information, which instructs the access network device to send the first session information to the user plane function element. This ensures that the access network device accurately sends the first session information to the user plane function element.

[0019] In one possible design, the access network device can also receive third information from the user plane function element, the third information indicating that the user plane function element has completed the context processing of the PDU session; then, the access network device sends second information to the session management function element, the second information indicating that both the user plane function element and the access network device have completed the context processing of the PDU session. In this way, the information indicating that the user plane function element has completed the context processing of the PDU session can be transmitted from the access network device to the session management function element, thereby reducing the transmission between the session management function element and the user plane function element.

[0020] Thirdly, this application provides a communication method, which may include: a user plane function network element receiving second session management information from a session management function network element, the second session management information including second session information and third session information; the user plane function network element sending the second session information and the third session information to the access network device; wherein the second session information is used to indicate the context of a terminal device processing a PDU session, and the third session information is used to indicate the context of the access network device processing the PDU session; wherein the user plane function network element and the access network device are deployed on the same satellite, and the session management function network element is deployed on the ground side.

[0021] Using the above method, the session management function network element sends the third session information of the access network device and the second session information of the terminal device through the second session management information. This eliminates the need for the access and mobility management function network element to send the third session information to the access network device and the second session information to the terminal device. Compared to existing technologies, this reduces the transmission between the access and mobility management function network element and the access network device. Consequently, it reduces the transmission between satellite-based and ground-based devices, thereby reducing service latency and improving user experience.

[0022] In one possible design, before the user plane function element receives the second session management information from the session management function element, the user plane function element may also send first capability information to the session management function element. This first capability information indicates that the user plane function element supports the ability to reduce interactions between itself and the session management function element. This allows the session management function element to subsequently reduce transmissions between itself and the user plane function element, thereby reducing communication latency.

[0023] In one possible design, the user plane function network element can also send a notification to the session management function network element that the access network device has completed the context processing of the PDU session. In this way, the information indicating that the access network device has completed the context processing of the PDU session can be transmitted from the user plane function network element to the session management function network element, without the access and mobility management function network element needing to obtain it from the access network device and then send it to the session management function network element, thereby reducing the transmission between the access and mobility management function network element and the access network device.

[0024] In one possible design, the user plane function network element can also send a notification to the session management function network element that the terminal device has completed the context processing of the PDU session. In this way, the information indicating that the terminal device has completed the context processing of the PDU session can be transmitted from the user plane function network element to the session management function network element, without the access and mobility management function network element needing to obtain it from the access network device and then send it to the session management function network element, thereby reducing the transmission between the access and mobility management function network element and the access network device.

[0025] Fourthly, this application provides a communication method, which may include: an access and mobility management function (AMU) network element sending first information to a session management function (SMF) network element, wherein the first information is used to indicate that a user plane function network element and an access network device providing services for a Protocol Data Unit (PDU) session of a terminal device are deployed on the same satellite. This allows the SMF network element to accurately determine, based on the first information, that the user plane function network element and the access network device are deployed on the same satellite, thereby reducing subsequent transmissions between the SMF network element and the user plane function network element, or between the AMU network element and the access network device.

[0026] In one possible design, the first information may include one or more of the following: indication information that the access network device and the user plane function network element are independently deployed on the same satellite; indication information that the access network device and the user plane function network element are co-deployed on the same satellite; information about the satellite where the access network device and the user plane function network element are located; information about the access network device; or information about the user plane function network element.

[0027] In one possible design, before the access and mobility management function network element sends the first information to the session management function network element, it can also receive second capability information from the access network device. This second capability information indicates that the access network device supports signaling interaction with the user plane function network element. This allows subsequent signaling interaction between the access network device and the user plane function network element.

[0028] Fifthly, this application also provides a communication device, which may be a session management function network element. This communication device has the functionality to implement the methods described in the first aspect or various possible design examples of the first aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functionality.

[0029] In one possible design, the communication device includes a transceiver unit and a processing unit, which can perform the corresponding functions in the first aspect or various possible design examples of the first aspect, as detailed in the method examples, which will not be repeated here.

[0030] In one possible design, the communication device includes a communication interface and a processor, and optionally a memory. The communication interface is used to send and receive data, messages, or information, and to communicate and interact with other devices in the communication system. The processor is configured to support the communication device in performing the corresponding functions described in the first aspect or various possible design examples of the first aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device.

[0031] Sixthly, this application also provides a communication device, which may be an access network device, having the functionality to implement the methods described in the second aspect or various possible design examples of the second aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functionality.

[0032] In one possible design, the communication device includes a transceiver unit and a processing unit, which can perform the corresponding functions in the second aspect or various possible design examples of the second aspect, as detailed in the method examples, which will not be repeated here.

[0033] In one possible design, the communication device includes a communication interface and a processor, and optionally a memory. The communication interface is used to send and receive data, messages, or information, and to communicate and interact with other devices in the communication system. The processor is configured to support the communication device in performing the corresponding functions in the second aspect or various possible design examples of the second aspect described above. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device.

[0034] Seventhly, this application also provides a communication device, which may be a user plane function network element. This communication device has the functionality to implement the methods described in the third aspect or various possible design examples of the third aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the described functionality.

[0035] In one possible design, the communication device includes a transceiver unit and a processing unit, which can perform the corresponding functions in the third aspect or various possible design examples of the third aspect, as detailed in the method examples, which will not be repeated here.

[0036] In one possible design, the communication device includes a communication interface and a processor, and optionally a memory. The communication interface is used to send and receive data, messages, or information, and to communicate and interact with other devices in the communication system. The processor is configured to support the communication device in performing the corresponding functions in the third aspect or various possible design examples of the third aspect described above. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device.

[0037] Eighthly, this application also provides a communication device, which may be an access and mobility management function network element. This communication device has the functionality to implement the methods described in the fourth aspect or various possible design examples of the fourth aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functionality.

[0038] In one possible design, the communication device includes a transceiver unit and a processing unit, which can perform the corresponding functions in the fourth aspect or various possible design examples of the fourth aspect, as detailed in the method examples, which will not be repeated here.

[0039] In one possible design, the communication device includes a communication interface and a processor, and optionally a memory. The communication interface is used to send and receive data, messages, or information, and to communicate and interact with other devices in the communication system. The processor is configured to support the communication device in performing the corresponding functions in the fourth aspect or various possible design examples of the fourth aspect described above. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device.

[0040] Ninthly, embodiments of this application provide a communication system that may include the terminal equipment, access network equipment, user plane function network elements, session management function network elements, and access and mobility management function network elements mentioned above.

[0041] Tenthly, embodiments of this application provide a computer-readable storage medium storing program instructions that, when executed on a computer, cause the computer to perform the methods described in the first aspect and any possible design of the embodiments of this application, or in the second aspect and any possible design of the second aspect, or in the third aspect and any possible design of the third aspect, or in the fourth aspect and any possible design of the fourth aspect. Exemplarily, the computer-readable storage medium can be any available medium accessible to a computer. For example, but not limited to, the computer-readable medium can include non-transient computer-readable media, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disk storage, magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible to a computer.

[0042] Eleventhly, embodiments of this application provide a computer program product, including instructions that, when executed on a computer, cause the methods described in the first aspect or any possible design of the first aspect, or in the second aspect or any possible design of the second aspect, or in the third aspect and any possible design of the third aspect, or in the fourth aspect and any possible design of the fourth aspect to be executed.

[0043] In a twelfth aspect, this application also provides a chip including a processor coupled to a memory for reading and executing program instructions stored in the memory to enable the chip to implement the methods described in the first aspect or any possible design of the first aspect, or in the second aspect or any possible design of the second aspect, or in the third aspect and any possible design thereof, or in the fourth aspect and any possible design thereof.

[0044] For the various aspects of the above-mentioned fifth to twelfth aspects and the technical effects that may be achieved by each aspect, please refer to the above description of the technical effects that may be achieved by the various possible solutions of the first aspect or the first aspect, or the various possible solutions of the second aspect or the second aspect, or the third aspect and the third aspect, or the fourth aspect and the fourth aspect. It will not be repeated here. Attached Figure Description

[0045] Figure 1 A schematic diagram of the architecture of a communication system provided in this application;

[0046] Figure 2 A schematic diagram illustrating a satellite communication deployment method provided in this application;

[0047] Figure 3 A flowchart of a communication method provided in this application;

[0048] Figure 4 A flowchart of another communication method provided in this application;

[0049] Figure 5 A flowchart illustrating an example of a communication method provided in this application;

[0050] Figure 6 A flowchart illustrating another communication method provided in this application;

[0051] Figure 7 A flowchart illustrating an example of a communication method provided in this application;

[0052] Figure 8 A flowchart illustrating another communication method provided in this application;

[0053] Figure 9 A flowchart illustrating an example of a communication method provided in this application;

[0054] Figure 10 A flowchart illustrating another communication method provided in this application;

[0055] Figure 11 A flowchart illustrating an example of a communication method provided in this application;

[0056] Figure 12 A flowchart illustrating another communication method provided in this application;

[0057] Figure 13 A flowchart illustrating another communication method provided in this application;

[0058] Figure 14 A schematic diagram of the structure of a communication device provided in this application;

[0059] Figure 15 A structural diagram of a communication device provided in this application. Detailed Implementation

[0060] The present application will now be described in further detail with reference to the accompanying drawings.

[0061] This application provides a communication method and apparatus to reduce communication service latency in satellite communication scenarios, thereby improving user experience. The method and apparatus described in this application are based on the same technical concept. Since the principles by which the method and apparatus solve the problem are similar, their implementations can be mutually referenced, and repeated details will not be elaborated further.

[0062] In the description of this application, the terms "first," "second," etc., are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance or order.

[0063] In the description of this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0064] In the description of this application, "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone, where A and B can be singular or plural. " / " means "or", for example, a / b means a or b.

[0065] To more clearly describe the technical solutions of the embodiments of this application, the communication methods and devices provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0066] Figure 1This paper illustrates a possible communication system architecture to which the communication method provided in this application is applicable. The architecture of this communication system may include a radio access network, terminal equipment, and a core network. For example, in this communication system architecture, the radio access network may include access network equipment. The core network may include: network exposure function (NEF) network elements, policy control function (PCF) network elements, unified data management (UDM) network elements, application function (AF) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, and user plane function (UPF) network elements. Specifically, the AMF network element can be connected to the access network equipment via the N2 interface, the access network equipment can be connected to the UPF via the N3 interface, the SMF and UPF can be connected via the N4 interface, and the AMF network element can be connected to the UE via the N1 interface. The interface names are merely illustrative and are not specifically limited in this application. It should be understood that the embodiments of this application are not limited to... Figure 1 The communication system shown Figure 1 The names of the network elements shown here are merely illustrative and are not intended to limit the network elements included in the communication system architecture to which the method of this application applies. The functions of each network element or device in the communication system are described in detail below:

[0067] Terminal equipment, also known as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., is a device that provides voice and / or data connectivity to users. For example, terminal equipment can include handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, terminal equipment can include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, etc. Figure 1 The terminal device shown is a UE, which is only an example and does not limit the terminal device.

[0068] (R)AN equipment: Equipment that provides access for terminal devices, including radio access network (RAN) equipment and access network (AN) equipment. RAN equipment is mainly 3GPP network radio network equipment, while AN can be access network equipment defined outside of 3GPP. RAN equipment is mainly responsible for functions such as radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. The access network equipment can include various forms of base stations, such as macro base stations, micro base stations (also known as small stations), relay stations, and access points. In systems using different radio access technologies, the names of equipment with base station functions may differ; for example, in the 5th generation (5G) system, it is called RAN or gNB (5G NodeB).

[0069] Access and mobility management (AM) network elements are used to manage the access control and mobility of terminal devices. In practical applications, they include the mobility management functions of the Mobility Management Entity (MME) in the Long Term Evolution (LTE) network framework, and also incorporate access management functions. Specifically, they can be responsible for terminal device registration, mobility management, tracking area update procedures, reachability detection, selection of session management network elements, and mobility state transition management. For example, in 5G, the AMMF network element can be an AMF network element, such as... Figure 1 As shown; in future communications, such as 6G, the access and mobility management function network element can still be an AMF network element, or have other names, which is not limited in this application. When the access and mobility management function network element is an AMF network element, the AMF can provide Namf services.

[0070] Session management function (SMF) network elements are responsible for session management of terminal devices (including session establishment, modification, and release; maintaining the tunnel between user plane function network elements and access network devices), selection and reselection of user plane function network elements, allocation of Internet Protocol (IP) addresses for terminal devices (including optional authorization), configuration of traffic routing in user plane function network elements, and quality of service (QoS) control. SMF network elements are the endpoints for the session management portion of non-access stratum (NAS) messages. For example, in 5G, the SMF network element could be an SMF network element, such as... Figure 1 As shown; in future communications, such as 6G, the session management function network element can still be an SMF network element, or have other names, which is not limited in this application. When the session management function network element is an SMF network element, the SMF can provide Nsmf services.

[0071] User Plane Function (UPF) network elements are responsible for forwarding and receiving user data in terminal devices. They can receive user data from the data network and transmit it to the terminal device via the access network equipment. UPF network elements can also receive user data from the terminal device via the access network equipment and forward it to the data network. The transmission resources and scheduling functions providing services to the terminal device within the UPF network element are managed and controlled by the SMF network element. For example, in 5G, the User Plane Function (UPF) network element can be a UPF network element, such as... Figure 1 As shown; in future communications, such as 6G, user plane function network elements may still be UPF network elements, or may have other names, which are not limited in this application.

[0072] Policy control function network elements: These primarily support providing a unified policy framework to control network behavior, providing policy rules to the control layer network functions, and are also responsible for acquiring user subscription information related to policy decisions. For example, in 5G, the policy control function network element can be a PCF network element, such as... Figure 1 As shown; in future communications, such as 6G, the policy control function network element can still be a PCF network element, or have other names, which is not limited in this application. When the policy control function network element is a PCF network element, the PCF network element can provide NPCF services.

[0073] Network Open Functions (NEF) elements primarily support secure interaction between 3GPP networks and third-party applications. For example, in 5G, a NEF element could be a network open functions (e.g., NEF network elements). Figure 1 As shown; in future communications, such as 6G, the Network Open Functions (NEF) element may still be a NEF element, or may have other names, which are not limited in this application. When the Network Open Functions (NEF) element is a NEF, the NEF can provide Nnef services to other Network Functions (NNF) elements.

[0074] Application function network elements: These primarily support interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side. For example, in 5G, an application function network element could be an AF (Active Front-End) network element, such as... Figure 1 As shown; in future communications, such as 6G, the application function network element may still be an AF network element, or may have other names, which is not limited in this application. When the application function network element is an AF network element, the AF network element can provide NAF services.

[0075] Unified data management function network elements are used for generating authentication credentials, processing user identifiers (such as storing and managing permanent user identities), controlling access authorization, and managing subscription data. For example, in 5G, the unified data management function network element can be a UDM network element, such as... Figure 1 As shown; in future communications, such as 6G, the unified data management function network element can still be a UDM network element, or have other names, which is not limited in this application. When the unified data management function network element is a UDM network element, the UDM network element can provide Nudm services.

[0076] A data network (DN) refers to a service network that provides data transmission services to users, such as IP multi-media service (IMS) and the Internet.

[0077] The UE accesses the DN through a protocol data unit (PDU) session established between the UE and the DN.

[0078] In the core network, each network element can also be called a functional entity or device. It can be a network element implemented on dedicated hardware, a software instance running on dedicated hardware, or an instance of virtualized function on an appropriate platform. For example, the virtualization platform mentioned above can be a cloud platform.

[0079] It should be noted that, Figure 1 The communication system shown does not constitute a limitation on the communication systems applicable to the embodiments of this application. Figure 1 The communication system architecture shown is a 5G system architecture. Optionally, the method of this application embodiment is also applicable to various future communication systems, such as 6G or other communication networks.

[0080] It should be noted that, Figure 1 The architecture of the communication system shown is not limited to the network elements shown in the figure, but may also include other devices not shown in the figure. These will not be listed here.

[0081] It should be noted that the embodiments of this application do not limit the distribution form of each network element. Figure 1 The distribution shown is merely exemplary and is not intended to limit the scope of this application.

[0082] For ease of explanation, all subsequent references to this application will be made to it. Figure 1 The network element shown is used as an example for illustration, and network element XX is directly abbreviated as XX. For example, SMF network element is abbreviated as SMF. It should be understood that all network element names in this application are merely examples and may be referred to by other names in future communications, or the network element involved in this application may be replaced by other entities or devices with the same function in future communications. This application does not limit these possibilities. This is a unified explanation here and will not be repeated later.

[0083] It should be noted that all names of messages or information in this application are merely examples and may be other names. A message can be information, and information can be a message; this application does not limit either. It should be understood that a message or information from network element 1 to network element 2 can be sent directly from network element 1 to network element 2, or it can be sent indirectly. For example, network element 1 first sends a message or information to network element 3, and then network element 3 sends a message or information to network element 2. Ultimately, the message or information is sent to network element 2 through one or more network elements.

[0084] Currently, satellite communication technology can supplement terrestrial communication in scenarios where coverage is difficult, such as deserts and oceans. In satellite communication scenarios, it may involve deploying network elements originally located on the ground onto satellites. For example, one possible deployment method for satellite communication could be as follows: Figure 2 As shown. In Figure 2In this scenario, user plane network elements providing services for PDU sessions executed by terminal devices, such as RAN and UPF, can be deployed on satellites. Terminal devices access the 5G core network via satellite, and ground stations are responsible for forwarding signaling and service data between the satellite and the 5G core network. It should be noted that in the above scenario, UPF may also be deployed on the ground, for example... Figure 2 UPF1 and UPF2 are shown in the 5G core network located on the ground. It should be understood that... Figure 2 The network elements or devices shown are merely examples and are not intended to limit this application.

[0085] In this deployment method, devices on the satellite and on the ground need to communicate frequently. Due to the large distance between the satellite and the ground, this may cause significant communication latency, thus affecting the user's communication experience. Therefore, this application proposes a communication method to reduce the number of information exchanges between devices on the satellite and on the ground, thereby reducing communication latency and improving the user experience.

[0086] Based on the above description, such as Figure 3 As shown in the illustration, this application provides a communication method applicable to scenarios where access network equipment and user plane function network elements are simultaneously deployed on the same satellite, while session management function network elements are deployed on the ground side. The specific process may include:

[0087] Step 301: The session management function network element determines that the user plane function network element and access network equipment that provide services for the PDU session of the terminal equipment are deployed on the same satellite.

[0088] For example, the session management function network element can receive first information from the access and mobility management function network element, the first information being used to indicate that the user plane function network element providing services for the PDU session of the terminal device and the access network device are deployed on the same satellite; the session management function network element can then determine, based on the first information, that the user plane function network element providing services for the PDU session of the terminal device and the access network device are deployed on the same satellite.

[0089] For example, the first information may include one or more of the following: indication information that the access network device and the user plane function network element are independently deployed on the same satellite; indication information that the access network device and the user plane function network element are co-deployed on the same satellite; information about the satellite where the access network device and the user plane function network element are located; information about the access network device; or information about the user plane function network element.

[0090] The first information may also be referred to as co-located user face information, etc. This application does not limit the name of the first information.

[0091] It should be noted that the indication information for access network equipment and user plane function network elements independently deployed on the same satellite and the indication information for access network equipment and user plane function network elements jointly deployed on the same satellite will not be included in the first information simultaneously. Specifically, in the scenario where the access network equipment and user plane function network elements are independently deployed on the same satellite, the access network equipment and user plane function network elements can use the current N3 interface for signaling exchange (currently, the N3 interface can only be used for data packet transmission between access network equipment and user plane function network elements, not for signaling transmission). In the scenario where the access network equipment and user plane function network elements are jointly deployed on the same satellite, the interaction between the access network equipment and user plane function network elements is implemented internally.

[0092] The information of the satellites where the access network equipment and the user plane function network element are located may include the identifiers of the satellites where the access network equipment and the user plane function network element are located, the orbital information of the satellites, etc.

[0093] The information of the access network device may include the device's identifier, etc.

[0094] The information of the user plane function network element can be its identifier, address, etc.

[0095] In one exemplary implementation, the session management function network element, based on the first information, can determine, using the following methods, whether the user plane function network element providing services for the PDU session of the terminal device and the access network device are deployed on the same satellite:

[0096] Method 1: The session management function network element can be directly determined based on the indication information included in the first information that the access network device and the user plane function network element are independently deployed on the same satellite, or the indication information that the access network device and the user plane function network element are co-deployed on the same satellite.

[0097] Method 2: When the first information includes the information of the user plane function network element, the session management function network element, in combination with its local configuration and the information of the user plane function network element, determines that the user plane function network element and the access network device are deployed on the same satellite.

[0098] Method 3: When the first information includes the information of the access network device, the session management function network element, in conjunction with the information of the user plane function network element jointly deployed with the access network device obtained from local configuration or from other network elements (such as AMF or UDM), determines that the user plane function network element and the access network device are deployed on the same satellite.

[0099] Method 4: When the first information includes information about the satellite where the access network device and the user plane function network element are located, the session management function network element can determine that the information of the satellite where the access network device and the user plane function network element are located are the same, thereby determining that the user plane function network element and the access network device are deployed on the same satellite.

[0100] It should be understood that, in addition to the methods described above, the session management function network element can also determine that the user plane function network element and the access network device are deployed on the same satellite using other methods. For example, the access network device serving the terminal device provides the session management function network element with information about user plane function network elements deployed on the same satellite as the access network device, so that the session management function network element determines that the access network device and the user plane function network element are deployed on the same satellite based on the information about user plane function network elements deployed on the same satellite provided by the access network device, and the information of the access network device itself. This application does not limit the method for determining that the user plane function network element and the access network device are deployed on the same satellite.

[0101] In one optional implementation, when the Access and Mobility Management Function (AMS) network element sends the first information to the Session Management Function (SMS) network element, it can be done during the session establishment process, after the AMS network element receives an uplink NAS message containing a PDU session establishment request message from the terminal device, and then sends a session management context creation request message to the SMS network element, the session management context creation request message containing the first information and the PDU session establishment request message; alternatively, it can be done during the PDU session modification process, when the terminal device initiates PDU session modification, the AMS network element sends the first information to the SMS network element; or it can be done during the PDU session release process. Alternatively, if the AMS network element sends the first information during the session establishment process, it can also send the first information again during the subsequent PDU session modification process and / or PDU session release process; this application does not limit this to any particular method.

[0102] It should be noted that, in this application, when the access network equipment is located on a satellite, it does not limit whether some or all of the modules included in the access network equipment are located on the satellite, nor does it limit whether some or all of the functional modules included in the user plane function network element are located on the satellite where the access network equipment is located.

[0103] Optionally, before step 301, when selecting a user plane function network element to provide services for the PDU session of the terminal device, the session management function network element may select a user plane function network element deployed on the same satellite as the access network device providing services for the PDU session of the terminal device.

[0104] Step 302: The session management function network element sends first session management information to the access network device. The first session management information includes first session information, which is used to instruct the user plane function network element to process the context of the PDU session.

[0105] Optionally, the first session management information can be transmitted to the access network device via the N2 interface, and thus the first session management information can be referred to as the first N2 session management information. For ease of description, the first session management information will be described as the first N2 session management information in the following description.

[0106] Optionally, session information sent to the user plane function network element can reach the user plane function network element through the N4 interface. Generally, session information sent to the user plane function network element is referred to as N4 session management information. Therefore, the first session information in this application can be referred to as first N4 session management information. For ease of description, the first session information will be described as first N4 session management information in the following description.

[0107] However, the embodiments of this application do not limit the first session management information and the first session information to other message names. As long as they have the notification function of the first session management information and the first session information, they are all within the protection scope of this application.

[0108] The context of the PDU session can also be referred to as the context of the N4 session. The context that instructs the user plane function network element to process the PDU session can be a context that instructs the user plane function network element to create (configure), update, and remove (release) the N4 session. In addition, it can also instruct the user plane function network element to process resources such as tunnels.

[0109] In one optional implementation, the first N4 session management information can be referred to as an N4 transparent transmission container. That is, the first N4 session management information is sent by the session management function network element to the user plane function network element. During the transmission process, network elements such as access and mobility management function network elements and access network equipment transparently transmit this information. In the session establishment process, the first N4 session management information can be an N4 session establishment request message, used by the user plane function network element to create an N4 session context, such as configuring various N4 rules. In the PDU session modification process, the first N4 session management information can be an N4 session modification request message, used by the user plane function network element to update the N4 session context, such as updating various N4 rules. In the PDU session release process, the first N4 session management information can be an N4 session release request message, used by the user plane function network element to remove the N4 session context, such as removing various N4 rules.

[0110] In one optional implementation, before the session management function network element sends the first session management information to the access network device, it may also receive first capability information from the user plane function network element. The first capability information is used to indicate that the user plane function network element supports the ability to reduce the interaction between the user plane function network element and the session management function network element.

[0111] Optionally, the user plane function network element may send the first capability information to the session management function network element during the N4 association establishment process. The first capability information may also be referred to as signaling optimization support indication information, user plane signaling support indication information, or other names, which are not limited in this application. For example, when the user plane function network element sends the first capability information, if the access network device and the user plane function network element are independently deployed on the same satellite, it indicates that the user plane function network element supports signaling interaction with the access network; if the access network device and the user plane function network element are co-deployed on the same satellite, it indicates that the user plane function network element supports internal interaction with the access network.

[0112] This ensures that the session management function network element accurately sends the first session management information to the access network device, avoiding the situation where the session management function network element blindly sends the first session management information to the access network device when the user plane function network element does not support the ability to reduce the interaction between the user plane function network element and the session management function network element. This would not only fail to reduce the communication overhead between the satellite device and the ground device, but also waste transmission resources caused by sending invalid messages.

[0113] In another optional implementation, before the session management function network element sends the first session management information to the access network device, the access network device may also send the second capability information to the access and mobility management function network element. The second capability information is used to indicate that the access network device supports signaling interaction with the user plane function network element.

[0114] Optionally, the access network device may send the second capability information to the access and mobility management function network element during the next-generation (NG) interface establishment process. The second capability information may also be referred to as user plane signaling support indication information, etc. For example, when the access network device sends the second capability information, if the access network device and the user plane function network element are independently deployed on the same satellite, it indicates that the user plane function network element supports signaling interaction with the access network; if the access network device and the user plane function network element are co-deployed on the same satellite, it indicates that the user plane function network element supports internal interaction with the access network.

[0115] This also enables the session management function network element to accurately send the first session management information to the access network device, avoiding the situation where the session management function network element blindly sends the first session management information to the access network device when the access network device and the user plane function network element on the same satellite do not support interaction capabilities. This would not only fail to reduce the communication overhead between the satellite device and the ground device, but also waste transmission resources caused by sending invalid messages.

[0116] Step 303: The access network device sends the first N4 session management information to the user plane function network element.

[0117] In an optional implementation, the first N2 session management information may further include reduced signaling indication information, which is used to instruct the access network device to send the first N4 session management information to the user plane function network element.

[0118] In an optional implementation, the first N2 session management information may further include information about the user plane function network element. In this way, the access network device can accurately send the first N4 session management information to the user plane function network element based on the information of the user plane function network element.

[0119] In one possible implementation, when the access network device serving the PDU session of the terminal device and the user plane function network element are deployed on the same satellite, the user plane function network element may not allocate a core network tunnel during the PDU session establishment process. Furthermore, during the session establishment process or the PDU session modification process, the first N2 session management information may also not include core network tunnel information. Additionally, during the PDU session establishment process, when the first N2 session management information does not include core network tunnel information, the access network device may also not allocate an access network tunnel.

[0120] In another alternative approach, during the PDU session establishment process, when the access network device determines that it and the user plane function element are deployed on the same satellite, the access network device may not allocate an access network tunnel. For example, if the first N2 session management information includes information about the user plane function element, the access network device can determine that the user plane function element corresponding to the PDU session is deployed on the same satellite as the access network device.

[0121] In another alternative approach, when the first N2 session management information also includes reduction signaling indication information, the access network device may also not allocate an access network tunnel.

[0122] After the user plane function network element completes the context processing of the PDU session of the terminal device, the access network device can receive third information from the user plane function network element. This third information indicates that the user plane function network element has completed the context processing of the PDU session. Subsequently, after the access network device also completes the context processing of the terminal device's PDU session, the access network device can then send second information to the session management function network element. This second information indicates that both the user plane function network element and the access network device have completed the context processing of the PDU session. For example, the second information may indicate the establishment, modification, or release of the PDU session by the access network device and the user plane function network element. This includes the completion of tunnel processing, establishment, or release between the access network device and the user plane function network element.

[0123] For example, in the PDU session establishment process, if the access network device and the user plane function network element are co-deployed on the same satellite, the access network device and the user plane function network element can complete the configuration of the user plane path through internal implementation. If the access network device and the user plane function network element are independently deployed on the same satellite, the access network device can send the allocated access network tunnel information to the user plane function network element, and the user plane function network element can update forwarding rules, etc. When the access network device and the user plane function network element are independently deployed on the same satellite, this application does not limit the interfaces and messages used for signaling interaction between the access network device and the user plane function network element; for example, custom data packets can be used.

[0124] In one optional implementation, the third information may be a first N4 session response message sent by the user plane function network element to the access network device, used to respond to the first N4 session management information; that is, the first N4 session response message is sent by the user plane function network element to the session management function network element. The second information may be a first N2 session response message sent by the access network device to the session management function network element, used to respond to the first N2 session management information.

[0125] In one possible approach, since the third information is used to indicate that the user plane function network element has completed the context processing of the PDU session, and the second information is used to indicate that the user plane function network element and the access network device have completed the context processing of the PDU session, it can be understood that the second information includes the third information. For example, the first N2 session response information includes the first N4 session response information.

[0126] In another optional implementation, the third information may be the result of the PDU session context processing sent by the user plane function network element to the access network device, indicating that the user plane function network element has completed the PDU session context processing, and the result of the PDU session context processing is sent by the user plane function network element to the access network device. The second information may be a first N2 session response information sent by the access network device to the session management function network element, used to respond that the first N2 session management information includes the above-mentioned result information. It should be noted that the result information sent by the access network device to the session management function network element is based on the result information received from the user plane function network element, and the two can be represented in the same or different ways.

[0127] Using the communication method provided in this application embodiment, the access network device sends the first N4 session management information to the user plane function network element, and the access network device and the user plane function network element are deployed on the same satellite. In this way, compared with the prior art, it is not necessary for the session management function network element to send the first N4 session management information to the user plane function network element, which can reduce the transmission between the session management function network element and the user plane function network element, thereby reducing the transmission between the equipment on the satellite and the equipment on the ground, thereby reducing service latency and improving user experience.

[0128] like Figure 4 As shown in the embodiment of this application, another communication method is provided. This method can also be applied in scenarios where access network equipment and user plane function network elements are simultaneously deployed on the same satellite equipment, while session management function network elements are deployed on the ground side. The specific process of this method may include:

[0129] Step 401: The session management function network element determines the user plane function network element and access network equipment that provide services for the PDU session of the terminal equipment and are deployed on the same satellite.

[0130] For details on the implementation process of step 401, please refer to [link / reference]. Figure 3 The relevant descriptions in step 301 of the illustrated embodiment will not be repeated here.

[0131] Step 402: The session management function network element sends second session management information to the user plane function network element. The second session management information includes second session information and third session information. The second session information is used to instruct the terminal device to process the context of the PDU session, and the third session information is used to instruct the access network device to process the context of the PDU session.

[0132] Optionally, the second session management information can reach the user plane function network element through the N4 interface; therefore, the second session management information can also be referred to as the second N4 session management information. For ease of description, the second session management information will be described as the second N4 session management information in the following description.

[0133] Optionally, session information sent to the access network device can reach the access network device through the N2 interface. This session information is generally referred to as N2 session management information; therefore, the third session information in this application can also be referred to as second N2 session management information. For ease of description, the third session information will be described as second N2 session management information in the following description. Similarly, currently, sessions sent to the terminal device can reach the terminal device through the N1 interface. This session information is generally referred to as N1 session management information; therefore, the second session information in this application can be referred to as N1 session management information. For ease of description, the second session information will be described as N1 session management information in the following description.

[0134] However, the embodiments of this application do not limit the second session management information, the second session information and the third session information to other message names. As long as they have the notification function of the second session management information, the second session information and the third session information, they are all within the protection scope of this application.

[0135] The N1 session management information may include PDU session-related messages / information, or the N1 session management information may be PDU session-related messages / information, such as PDU session establishment acceptance messages, PDU session modification command messages, PDU session release command messages, etc. Furthermore, one example of the terminal device processing the PDU session context is that after receiving the PDU session establishment acceptance message, it determines that the network has accepted the establishment of the session and processes the PDU session according to the parameters in the PDU session establishment acceptance message, such as sending data packets according to the network-authorized quality of service (QoS) parameters.

[0136] The second N2 session management information may also include PDU session-related messages / information, or the second N2 session management information may be PDU session-related messages / information, such as tunnel information, QoS information, etc. For example, one example of the access network device processing the context of the PDU session is that after receiving the tunnel information, the access network device uses it as the uplink endpoint of the user plane data of the PDU session.

[0137] Optionally, the N1 session management information can be referred to as the N1 transparent transmission container. This means that the N1 session management information is sent from the session management function network element to the terminal device, and all network elements traversed during the transmission process, such as access and mobility management function network elements and access network devices, will transparently transmit this information. Similarly, the second N2 session management information can be referred to as the N2 transparent transmission container. This means that the second N2 session management information can be sent from the session management function network element to the access network device, and all network elements traversed during the transmission process, such as access and mobility management function network elements, will also transparently transmit this information.

[0138] In an optional implementation, before the Session Management Function (SMF) element sends the second Session Management Information to the User Plane Function (MPF) element, the Access Network Device (ANF) may first send second Capability Information to the Access and Mobility Management (AMM) element. This second Capability Information indicates that the ANF device supports signaling interaction with the MPF element. Optionally, the ANF device may send the second Capability Information to the MPF element during the NG establishment process. The second Capability Information may also be referred to as User Plane Signaling Support Indication Information, etc. For example, when the ANF device sends the second Capability Information, if the ANF device and the MPF element are independently deployed on the same satellite, it indicates that the MPF element supports signaling interaction with the ANF; if the ANF device and the MPF element are co-deployed on the same satellite, it indicates that the MPF element supports internal interaction with the ANF. Furthermore, optionally, the ANF element may send the second Capability Information to the Session Management Function (SMF) element.

[0139] In another optional approach, before the session management function network element sends the second session management information to the user plane function network element, the access network device may send the second capability information to the access and mobility management function network element when forwarding the PDU session establishment request message of the terminal device to the access and mobility management function network element. When the access and mobility management function network element receives the second capability information from the access network device, it may transparently transmit the second capability information to the session management function network element when forwarding the PDU session establishment request message to the session management function network element.

[0140] This allows the session management function network element to accurately send the second session management information to the user plane function network element, avoiding the situation where the session management function network element blindly sends the first session management information to the user plane function network element when the user plane function network element does not support the ability to interact with the access network equipment. This would not only fail to reduce the communication overhead between the equipment on the satellite and the equipment on the ground, but would also cause a waste of transmission resources due to the sending of invalid messages.

[0141] Step 403: The user plane function network element sends the N1 session management information and the second N2 session management information to the access network device.

[0142] Subsequently, the access network device sends the N1 session management information to the terminal device.

[0143] In one possible scenario, where the access network device and the user plane function network element are co-located and deployed on the same satellite, the user plane function network element can internally send the N1 session management information and the second N2 session management information to the access network device.

[0144] In another possible approach, where the access network device and the user plane function network element are independently deployed on the same satellite, the user plane function network element can send the N1 session management information and the second N2 session management information to the access network device via signaling.

[0145] In one alternative implementation, the second N2 session management information may not include core network tunnel information.

[0146] In one optional implementation, after the access network device completes the context processing of the PDU session, it can send an indication to the user plane function network element that the context processing of the PDU session has been completed. For example, the access network device completing the context processing of the PDU session includes completing resource allocation, resource updates, and resource release. Then, the user plane function network element sends a notification to the session management function network element that the access network device has completed the context processing of the PDU session.

[0147] In one optional implementation, after the terminal device completes the context processing of the PDU session, it can send a context processing indication of the PDU session to the access network device through the access network device. Then, the user plane function network element sends a notification message to the session management function network element that the terminal device has completed the context processing of the PDU session.

[0148] Using the communication method provided in this application embodiment, the session management function network element sends the N2 session management information of the access network device and the N1 session management information of the terminal device through N4 session management information. This eliminates the need for the access and mobility management function network element to send N2 session management information and N1 session management information of the terminal device to the access network device. Compared to existing technologies, this reduces the transmission between the access and mobility management function network element and the access network device, thereby reducing the transmission between satellite-based devices and ground-based devices, ultimately reducing service latency and improving user experience.

[0149] Based on the above embodiments, the communication method provided in this application will be described in detail below through specific examples. In the following examples, the terminal device is UE, the session management function network element is SMF, the user plane function network element is UPF, the access network device is RAN, and the access and mobility management function network element is AMF, which will be used as examples for detailed explanation.

[0150] In one scenario, if the SMF determines that the UPF and RAN serving the UE's PDU session are deployed on the same satellite, the SMF will not configure, update, or delete rules and resources on the UPF. The following will illustrate... Figures 5-7 The example shown below illustrates this. Figures 5-7 The examples shown all illustrate the situation by having the UPF and RAN, which provide services for the UE's PDU session, deployed on the same satellite, while the SMF is deployed on the ground.

[0151] Figure 5 An example of a communication method is shown, which describes in detail the communication method provided in the embodiments of this application in conjunction with a session establishment process. The specific process of this example may include:

[0152] Step 501: The UE sends a PDU session establishment request message to the AMF. The UE may include the PDU session establishment request message in an uplink NAS transmission message before sending it to the AMF.

[0153] Step 502: The AMF selects an SMF for the PDU session.

[0154] Step 503: The AMF forwards the PDU session establishment request message to the SMF. The AMF may include the PDU session establishment request message in the session management context creation request message. Optionally, the session management context creation request message may include co-located user plane information (i.e., the first information mentioned above).

[0155] The content of the user face information at the same location can be found in the relevant description of the first information mentioned above, and will not be described in detail here.

[0156] The SMF can determine whether the RAN and UPF of the serving UE are deployed on the same satellite based on the user plane information of the same location provided by the AMF. The specific method for determining the SMF can be found in the relevant description in step 301 of the above embodiment, and will not be described in detail here.

[0157] Step 504: Optionally, if the SMF needs to obtain contract data information, the SMF queries the UDM for contract data information.

[0158] Step 505: If the SMF can process the PDU session establishment request message, the SMF sends a Create Session Management Context Response message to the AMF, which contains the session context identifier.

[0159] Step 506: If the SMF needs to perform a secondary authentication and authorization process, the SMF triggers the secondary authentication and authorization process of the PDU session.

[0160] Step 507: If the PDU session requires the use of dynamic policies, the SMF performs a PCF selection operation. Optionally, the SMF initiates a session management policy establishment process.

[0161] Step 508: The SMF selects a UPF for the PDU session. Optionally, when selecting a UPF, the SMF considers user plane information for the same location provided by the AMF, i.e., it prioritizes selecting a UPF whose RAN is deployed on the same satellite as the serving UE.

[0162] Step 509: Optional, SMF initiates a session management policy association modification process.

[0163] Step 510: If the PDU session is being established for the first time, the SMF initiates the N4 session establishment procedure, sending a PDU session establishment request message to the UPF. Otherwise, if the PDU session is a re-establishment of an existing PDU session, the SMF initiates the N4 session modification procedure, sending a PDU session modification request message to the UPF. The SMF includes packet inspection rules, QoS enforcement rules, and reporting rules in the aforementioned request message.

[0164] Step 511: In the N4 session establishment process or N4 session modification process, the UPF allocates a core network tunnel (CN tunnel) for the PDU session and provides the core network tunnel information to the SMF in the response message of the PDU session establishment request message or the PDU session modification request message.

[0165] The initial configuration may include an N4 association establishment process. The functions supported by the interaction between the SMF and UPF in this process are not shown in the example diagram. Optionally, in the N4 association establishment process, the UPF sends signaling optimization support indication information (i.e., the first capability information mentioned above) to the SMF. This signaling optimization support indication information instructs the UPF to support reducing signaling between the SMF and the UPF. For scenarios where the RAN and UPF are independently deployed on the same satellite, this signaling optimization support indication information indicates that the UPF supports signaling interaction with the RAN; for scenarios where the RAN and UPF are jointly deployed on the same satellite, this indication information indicates that there is internal signaling interaction between the UPF and the RAN. This application does not limit the name of this signaling optimization support indication information; for example, it could also be called user plane signaling support indication information, etc.

[0166] Another process may exist in the initial configuration, namely the NG establishment process. The functions supported by the interaction between the AMF and RAN in this process are not shown in the example diagram. Optionally, in the NG establishment process, the RAN sends user plane signaling support indication information (i.e., the second capability information mentioned above) to the AMF. This user plane signaling support indication information indicates that the RAN and UPF support user plane signaling interaction. For scenarios where the RAN and UPF are independently deployed on the same satellite, this user plane signaling support indication information indicates that the RAN supports signaling interaction with the UPF; for scenarios where the RAN and UPF are jointly deployed on the same satellite, this user plane signaling support indication information indicates that there is internal signaling interaction between the UPF and the RAN. Optionally, if the AMF receives this user plane signaling support indication information, the AMF can send it to the SMF in step 502 above.

[0167] In an alternative approach, when the RAN forwards the UE's PDU session establishment request message to the AMF in step 501, it sends the user plane signaling support indication information to the SMF. After receiving the user plane signaling support indication information from the RAN, the AMF transparently transmits the user plane signaling support indication information to the SMF in step 503.

[0168] In one possible implementation, if the user plane information provided by the AMF for the same location includes co-deployment indication information on the same satellite (i.e., the RAN and UPF are co-deployed on the same satellite), and the UPF selected by the SMF is the same UPF deployed on the same satellite as the serving UE's RAN, then the SMF will not initiate the aforementioned N4 session establishment or modification procedure; that is, steps 510 and 511 will not be executed. Optionally, if the user plane information provided by the AMF for the same location includes co-deployment indication information on the same satellite, and the UPF selected by the SMF is the same UPF deployed on the same satellite as the serving UE's RAN, and if the UPF provides signaling optimization support indication information to the SMF, then steps 510 and 511 will not be executed.

[0169] In another possible implementation, if the user plane information provided by the AMF for the same location includes co-deployment indication information on the same satellite, and the UPF selected by the SMF is a UPF deployed on the same satellite as the RAN serving the UE, then in step 511, the UPF is not allocated a core network tunnel. Optionally, in this scheme, the SMF instructs the UPF not to allocate a core network tunnel.

[0170] Step 512: The SMF sends a transmission message to the AMF. This transmission message includes N2 session management information and N1 session management information, etc. The N2 session management information is sent by the SMF to the RAN, and the N1 session management information is sent by the SMF to the UE. The N2 session management information includes the PDU session identifier, QoS-related information, slice-related information, core network tunnel information, etc. The N1 session management information includes the PDU session acceptance message, etc.

[0171] If steps 510 and 511 are not executed, or if steps 510 and 511 are executed but the UPF does not allocate a core network tunnel in step 511, then the N2 session management information will not contain core network tunnel information. Optionally, the N2 session management information may contain the UPF's identification information or address information.

[0172] Optionally, if the UPF selected by the SMF is a UPF deployed on the same satellite as the RAN of the serving UE, the SMF includes signaling optimization instruction information in the N2 session management information, which instructs the RAN to perform signaling optimization.

[0173] Step 513: The AMF sends an N2 session request message to the RAN. The N2 session request message contains N2 session management information and a NAS message. The N2 session management information is sent by the SMF to the RAN. The NAS message contains the PDU session identifier and N1 session management information. The N1 session management information is sent by the SMF to the UE.

[0174] Step 514: The RAN interacts with the UE to exchange session-related information, such as the RAN sending N1 session management information to the UE, the RAN establishing relevant resources for the PDU session, and allocating access network tunnels (AN tunnels) for the PDU session.

[0175] In one possible implementation, if the RAN and UPF are co-deployed on the same satellite, the RAN does not allocate an access network tunnel. Optionally, if the RAN determines that the UPF corresponding to the PDU session is a co-deployed UPF, the RAN does not allocate an access network tunnel. Optionally, if the SMF provides a UPF identifier or UPF address in the N2 session management information, the RAN determines that the UPF corresponding to the PDU session is a co-deployed UPF. Of course, there are other ways for the RAN to determine the co-deployed UPF, and this application does not limit this.

[0176] In another possible implementation, if the RAN and UPF are co-located on the same satellite and the RAN receives signaling optimization instructions from the SMF, then the RAN will not allocate access network tunnels.

[0177] In another possible implementation, if the N2 session management information received by the RAN does not contain core network tunnel information, then the RAN will not allocate an access network tunnel.

[0178] Step 515: The RAN and UPF exchange session management information, such as access network tunnel information.

[0179] Optionally, if the RAN receives signaling optimization instruction information from the SMF, the RAN determines that it needs to interact with the UPF for session management information.

[0180] In one possible implementation, if the RAN and UPF are co-deployed on the same satellite, the RAN and UPF complete the configuration of the user plane path through their internal implementations. This application does not limit the internal processing of the co-deployed RAN and UPF.

[0181] In another possible implementation, if the RAN and UPF are independently deployed on the same satellite, the RAN sends the allocated access network tunnel information to the UPF, and the UPF updates its forwarding rules, etc. This application does not limit the interfaces and messages used for signaling interaction between the RAN and UPF; for example, special data packets can be used.

[0182] After steps 514 and 515, the UE can send uplink data packets, and the UPF can send the received downlink data packets to the UE.

[0183] Step 516: The RAN sends an N2 session response message to the AMF. The N2 session response message contains the PDU session identifier, N2 session management response information, etc. The N2 session management response information is sent by the RAN to the SMF. It includes the PDU session identifier, access network tunnel information, and QoS information for acceptance / rejection.

[0184] In one possible implementation, when the RAN receives signaling optimization instruction information from the SMF, the N2 session management response information does not include access network tunnel information.

[0185] Optionally, if the RAN receives signaling optimization indication information from the SMF and has completed the interaction with the UPF, the N2 session response message includes UPF configuration completion indication information to indicate that the UPF configuration is complete.

[0186] Step 517: The AMF sends a Session Management Context Update message to the SMF. The Session Management Context message contains the N2 Session Management Response information sent by the RAN to the SMF.

[0187] Currently, in the standard procedure, the SMF provides the access network tunnel information to the UPF after receiving it from the RAN. However, in this application, if the SMF receives user plane information from the AMF at the same location, and the UPF selected by the SMF is deployed on the same satellite as the RAN serving the UE, then upon receiving the N2 session management information from the RAN, it does not perform the operation in the standard procedure; that is, it does not provide the access network tunnel information to the UPF. Therefore, in... Figure 5 This step will not be shown again.

[0188] In one possible implementation, if the SMF receives a UPF configuration completion indication from the RAN, the operation in the standard procedure will not be executed.

[0189] It should be noted that the above standard procedure still applies even when the RAN and UPF are not on the same satellite.

[0190] Step 518: Optionally, the SMF registers the PDU session information with the UDM.

[0191] Step 519: SMF sends a Session Management Context Update Response Message to AMF.

[0192] Step 520: If the session establishment fails, the SMF sends a session context notification message to the AMF and instructs the session to be released.

[0193] It should be noted that step 520 can occur at any time after step 505.

[0194] Step 521: In scenarios where the PDU session is Internet protocol version 6 (IPv6) or IPv4v6, the SMF generates an IPv6 route advertisement and sends it to the UE.

[0195] Step 522: For certain special scenarios, SMF may need to initiate a policy association update process.

[0196] Step 523: SMF may subscribe to session management subscription data from UDM.

[0197] It should be noted that if a PDU session establishment fails after step 504, step 523 will be executed.

[0198] Figure 6 An example of another communication method is shown, which describes in detail the communication method provided in the embodiments of this application in conjunction with the PDU session modification process. The specific process of this example may include:

[0199] Several possible ways to trigger PDU session modification can be found in steps 601a-601g:

[0200] Step 601a: The UE sends a PDU session modification request message to the SMF.

[0201] Specifically, the UE sends a PDU session modification request message to the SMF through the AMF. Optionally, during this process, the AMF sends user plane information at the same location (i.e., the first information mentioned above) to the SMF. The content of the user plane information at the same location can be found in the relevant description of the first information mentioned above, and will not be described in detail here.

[0202] Step 601b: PCF initiates the session management policy association modification process.

[0203] Step 601c: Due to changes in the contracted data, SMF initiates a PDU session modification.

[0204] Step 601d: Due to local configuration policies and RAN triggering, the SMF may decide to initiate a PDU session modification.

[0205] Step 601e: The RAN indicates to the SMF that the access network resources of the PDU session have changed, such as being released.

[0206] Step 601f: In an IoT energy-saving scenario, the AMF may trigger the SMF to initiate a PDU session modification.

[0207] Step 601g: AMF may notify SMF to update information related to big data analytics.

[0208] Step 602: Optionally, the SMF may need to notify the PCF of some events, and the SMF may initiate a session management policy association modification process.

[0209] After step 602, if the UPF used for the PDU session is deployed on the same satellite as the RAN of the serving UE, then proceed directly to steps 603a-603d below.

[0210] In one possible implementation, the SMF determines, based on user plane information from the same location sent by the AMF, that the UPF used for the PDU session is the same UPF deployed on the same satellite as the RAN serving the UE.

[0211] In another possible implementation, the SMF determines during the session establishment process that the UPF used for the PDU session is a UPF deployed on the same satellite as the RAN serving the UE, and saves this information.

[0212] If the UPF used for the PDU session is not deployed on the same satellite as the RAN serving the UE, the following steps are performed when a modification to the PDU session is determined: The SMF may update the N4 rules related to the new or modified QoS (primarily modifying rules related to uplink data) and send an N4 session modification request message to the UPF. Upon receiving the N4 session modification request message, the UPF updates the corresponding rules. That is, with the method of this application, the above two steps are no longer performed. These two steps are... Figure 6 It will no longer be shown in the text.

[0213] For different methods in steps 601a-601g above, the corresponding operations in steps 603a-603d will be performed:

[0214] Step 603a: For a PDU session modification initiated by the UE or RAN, the SMF sends a Session Management Context Update Response Message to the AMF. This message contains N2 session management information and N1 session management information. The N2 session management information includes the PDU session identifier, QoS information, core network tunnel information, etc. The N1 session management information includes a PDU session modification command message, which contains the PDU session identifier, QoS information, etc.

[0215] Optionally, if the UPF does not allocate a core network tunnel during the session establishment process, the N2 session management information will not include core network tunnel information.

[0216] Optionally, if the UPF selected by the SMF is a UPF deployed on the same satellite as the RAN of the serving UE, the SMF includes signaling optimization instruction information in the N2 session management information, which instructs the RAN to perform signaling optimization.

[0217] Step 603b: For the PDU session modification requested by the SMF, the SMF sends a transport message to the AMF. The content of the transport message is the same as that of the session management context update response message in step 603a, and they can be referred to each other.

[0218] Step 603c: For scenarios where the parameters associated with SMF in UDM change, i.e., not following the scenario in 601c where the contract data changes, SMF provides AMF with CN-assisted RAN parameter adjustments derived by SMF.

[0219] Step 603d: For scenarios involving big data analytics-related information updates, SMF notifies AMF that the relevant information has been updated.

[0220] Step 604: The AMF sends an N2 message to the RAN. The N2 message contains N2 session management information and N1 session management information from the SMF.

[0221] Step 605: The RAN may initiate access network-related signaling interactions with the UE. During this process, the RAN sends N1 session management information to the UE.

[0222] Step 606: The RAN and UPF exchange information such as QoS updates, such as the UPF updating QoS-related N4 rules, which include uplink and downlink rules.

[0223] Optionally, if the RAN receives signaling optimization indication information from the SMF, the RAN determines that it needs to exchange QoS and other information with the UPF.

[0224] In one possible implementation, if the RAN and UPF are co-deployed on the same satellite, the RAN and UPF complete the configuration of the user plane path through internal implementation.

[0225] In another possible implementation, if the RAN and UPF are deployed independently on the same satellite, the RAN instructs the UPF to update forwarding rules, etc.

[0226] Step 607: The RAN sends an N2 session acknowledgment message to the AMF. The N2 session acknowledgment message contains N2 session management response information, which includes QoS information such as acceptance / rejection.

[0227] Optionally, if the RAN receives signaling optimization indication information from the SMF and has completed the interaction with the UPF, the N2 session confirmation message will include UPF configuration completion indication information to indicate that the UPF configuration is complete.

[0228] Step 608: The AMF sends a Session Management Context Update Request message to the SMF. The Session Management Context Update Request message contains the RAN's N2 Session Management Response Information.

[0229] Step 609: SMF sends a Session Management Context Update Response Message to AMF.

[0230] In one approach, if the UPF used for the PDU session is deployed on the same satellite as the RAN serving the UE, then after the AMF receives the N2 session management response information from the RAN, it continues to execute step 610 below.

[0231] In one possible implementation, the SMF determines, based on user plane information from the same location sent by the AMF, that the UPF used for the PDU session is the same UPF deployed on the same satellite as the RAN serving the UE.

[0232] In another possible implementation, the SMF determines during the session establishment process that the UPF used for the PDU session is a UPF deployed on the same satellite as the RAN serving the UE, and saves this information.

[0233] In another approach, if the SMF receives a UPF configuration completion indication from the RAN, it continues with step 610 below.

[0234] When the UPF used for the PDU session is not deployed on the same satellite as the RAN serving the UE, according to existing standard procedures, the SMF sends an N4 session modification request message to the UPF. The N4 session modification request message is used to update rules related to new, modified, or deleted QoS. The rules modified here are mainly those related to downlink data. In other words, the communication method provided in this application does not perform the steps in the aforementioned existing procedures. Figure 6 It will no longer be shown in the text.

[0235] It should be noted that when the UPF used for the PDU session is not deployed on the same satellite as the RAN serving the UE, according to the existing standard procedure, the above-mentioned SMF rule update step can also be performed after step 612, but the above-mentioned step is still not performed using the method of this application.

[0236] Step 610: If the UE receives a PDU session modification command from the SMF, the UE sends a PDU session modification command confirmation message to the SMF. Specifically, the UE first sends a PDU session modification command confirmation message to the RAN.

[0237] Step 611: The RAN forwards the PDU session modification command confirmation message to the AMF.

[0238] Step 612: The AMF forwards the PDU session modification command confirmation message to the SMF via the session management context request message.

[0239] Step 613: SMF may initiate a session association policy modification process to notify the execution status of policy rules, etc.

[0240] Figure 7 An example of another communication method is shown, which describes in detail the communication method provided in the embodiments of this application in conjunction with the PDU session release process. The specific process of this example may include:

[0241] Several possible ways to trigger PDU session release can be found in steps 701a-701f:

[0242] Step 701a: The UE sends a PDU session release request message to the SMF.

[0243] Specifically, the UE sends a PDU session release request message to the SMF through the AMF. Optionally, during this process, the AMF sends user plane information at the same location (i.e., the first information mentioned above) to the SMF. The content of the user plane information at the same location can be found in the relevant description of the first information mentioned above, and will not be described in detail here.

[0244] Step 701b: PCF may invoke session management policies to manage the termination process.

[0245] Step 701c: If the PDU session state between the UE and AMF does not match, or if N1 or N2 session management information is not required before releasing the session management context, the AMF may send a session management context release request message to the SMF to request the SMF to release the PDU session.

[0246] Optionally, during this process, the AMF sends user plane information at the same location to the SMF (i.e., the first information mentioned above). The content of the user plane information at the same location can be found in the relevant description of the first information mentioned above, and will not be described in detail here.

[0247] Step 701d: The RAN may instruct the SMF to release the PDU session.

[0248] Step 701e: SMF decides to release the PDU session.

[0249] Step 701f: In scenarios where N1 or N2 session management information is required before releasing the session management context, the AMF may send a session management context update request message to the SMF to request the SMF to release the PDU session.

[0250] Optionally, during this process, the AMF sends user plane information at the same location to the SMF (i.e., the first information mentioned above). The content of the user plane information at the same location can be found in the relevant description of the first information mentioned above, and will not be described in detail here.

[0251] If the UPF used for the PDU session is deployed on the same satellite as the RAN of the serving UE, then when the SMF determines that the PDU session needs to be released, continue to execute the corresponding steps in steps 702a-702d below.

[0252] In one possible implementation, the SMF determines, based on user plane information from the same location sent by the AMF, that the UPF used for the PDU session is the same UPF deployed on the same satellite as the RAN serving the UE.

[0253] In another possible implementation, the SMF determines during the session establishment process that the UPF used for the PDU session is a UPF deployed on the same satellite as the RAN serving the UE, and saves this information.

[0254] In other words, if the UPF used for the PDU session is not deployed on the same satellite as the RAN serving the UE, then when the SMF determines that the PDU session needs to be released, the following steps are performed according to the existing standard procedure: The SMF sends an N4 session release request message to the UPF. The UPF sends an N4 session release response message to the SMF. After receiving the request, the UPF discards the PDU session data packets and releases the tunnel resources and the N4 session-related context. That is to say, with the method provided in this application, the above steps are no longer performed. These two steps are... Figure 7 It will no longer be shown in the text.

[0255] For different methods in steps 701a-701f above, the corresponding operations in steps 702a-702c will be performed:

[0256] Step 702a: For scenarios 701a, 701d, and 701f, the SMF sends a Session Management Context Update Response Message to the AMF. This message contains an N1 Session Management Container (N1 Session Management Information) and optionally an N2 Resource Release Request. The N1 Session Management Container is information sent by the SMF to the UE, containing a PDU session release command. If the user plane of the PDU session is active, the N1 Session Management Container contains an N2 Resource Release Request, which is information sent by the SMF to the RAN.

[0257] Optionally, if the UPF selected by the SMF is a UPF deployed on the same satellite as the RAN serving the UE, the SMF includes signaling optimization indication information in the N2 resource release request to instruct the RAN to perform signaling optimization.

[0258] Step 702b: For the scenarios in steps 701b and 701e, the SMF sends a transmission message to the AMF. The transmission message contains the N1 session management container and optionally includes an N2 resource release request. For details regarding the N1 session management container, please refer to the content in step 702a; it will not be described in detail here.

[0259] Step 702c: For the scenario in step 701c, the SMF sends a session management context release response message to the AMF, and the AMF and SMF remove the context of all PDU sessions. In this case, steps 703 to 712 below are not executed.

[0260] Step 703: The AMF forwards the information received from the SMF to the RAN via the N2 resource release request message.

[0261] Step 704: RAN and UE interact to release access network resources. During this process, the RAN forwards the received PDU session release command to the UE.

[0262] Step 705: The RAN and UPF exchange information to release the PDU session (i.e., the N4 session).

[0263] Optionally, if the RAN receives a signaling optimization instruction from the SMF, the RAN determines that it needs to interact with the UPF to release the N4 session.

[0264] In one possible implementation, if the RAN and UPF are co-deployed on the same satellite, the RAN and UPF release the N4 session through internal implementation.

[0265] In another possible implementation, if the RAN and UPF are deployed independently on the same satellite, the RAN instructs the UPF to release the N4 session, etc.

[0266] Step 706: The RAN sends an N2 resource release confirmation message to the AMF. The N2 resource release confirmation message includes N2 session management resource release confirmation information. This N2 session management resource release confirmation information is the information sent by the RAN to the SMF.

[0267] Optionally, if the RAN receives signaling optimization indication information from the SMF and has completed the interaction with the UPF, the N2 resource release confirmation message includes N4 session release indication information to indicate that the N4 session release is complete.

[0268] Step 707: The AMF sends a Session Management Context Update Request message to the SMF. The Session Management Context Update Request message contains confirmation information from the RAN regarding the release of N2 session management resources.

[0269] Step 708: SMF sends a Session Management Context Update Response Message to AMF.

[0270] Step 709: The UE sends a NAS message to the RAN. The NAS message contains the PDU session identifier and the N1 session management response container (N1 session management response information). The N1 session management response container contains the PDU session release confirmation.

[0271] Step 710: The RAN forwards the received NAS message to the AMF.

[0272] Step 711: The AMF sends the received N1 session management response container to the SMF via the session management context update message.

[0273] Optionally, steps 709-711 may occur before steps 706-708.

[0274] Step 712: For scenarios 702a or 702b, after the SMF waits for the AMF's response regarding the information related to N1 and N2, the SMF notifies the AMF that the corresponding PDU session context has been released.

[0275] Step 713: SMF may invoke session management policies to associate with the termination process.

[0276] Step 714: SMF notifies entities that have subscribed to PDU session changes.

[0277] Step 715: SMF may subscribe to changes in session management subscription data.

[0278] Step 716: SMF registers a PDU session.

[0279] Through the above Figures 5-7 The example shown can eliminate some communication processes between the SMF and UPF, which means reducing communication between equipment on the satellite and equipment on the ground, thereby reducing service latency and improving user experience.

[0280] In another scenario, if the SMF determines that the UPF serving the UE's PDU session and the RAN serving the UE are deployed on the same satellite, the SMF will send signaling (i.e., N4 interface signaling) for configuring, updating, and deleting rules and resources on the UPF to the UPF via the N2 interface. The following will illustrate... Figures 8-10 The example shown below illustrates this. Figures 8 to 10 The examples used are as follows: the UPF that provides services for the UE's PDU session and the RAN that provides services for the UE are deployed on the same satellite, while the SMF is deployed on the ground.

[0281] Figure 8 An example of a communication method is shown, which describes in detail the communication method provided in the embodiments of this application in conjunction with a session establishment process. The specific process of this example may include:

[0282] Steps 801-809 and Figure 5 Steps 501-509 in the example shown are similar and can be referred to each other, so they will not be repeated here.

[0283] If the user plane information provided by the AMF for the same location includes instructions for co-deployment on the same satellite, and the UPF selected by the SMF is a UPF deployed on the same satellite as the RAN serving the UE, then the SMF will not initiate the aforementioned N4 session establishment or N4 session modification procedure. Figure 5In the example shown, steps 510 and 511 do not execute. That is, the above process does not execute after using the method of this application. Specifically, in... Figure 8 The steps mentioned above that are not performed are not shown in the text.

[0284] Step 810: The SMF sends the first N2 session management information to the AMF. The first N2 session management information includes the N4 pass-through container 1 (i.e., the first N4 session management information mentioned above). The N4 pass-through container 1 contains an N4 session request message, which is used to configure various N4 rules to the UPF.

[0285] Step 811: The AMF forwards the received N4 transparent container 1 to the RAN.

[0286] Step 812 and Figure 5 Step 514 in the example shown is similar and can be referred to in relation to each other, so it will not be repeated here.

[0287] Step 813: The RAN sends the received N4 pass-through container 1 to the UPF.

[0288] Step 814: The UPF generates an N4 session establishment response message, includes the N4 session establishment response message in N4 transparent container 2 (i.e., the second information), and sends it to the RAN. N4 transparent container 2 indicates that the N4 session has been established and the tunnel information has been set. Optionally, the RAN provides access network tunnel information to the UPF at the same time as providing N4 transparent container 1.

[0289] In one possible implementation, if the RAN and UPF are co-deployed on the same satellite, the RAN sends N4 transparent container 1 to the UPF through its internal implementation, and the UPF sends N4 transparent container 2 to the RAN in response through its internal implementation.

[0290] In another possible implementation, if the RAN and UPF are deployed independently on the same satellite, the RAN will send the allocated access network tunnel information and the received N4 pass-through container 1 to the UPF, and the UPF will send the N4 pass-through container 2 back to the RAN in response.

[0291] Step 815: RAN transmits N4 transparent container 2 (i.e., the second information mentioned above) to AMF.

[0292] Step 816: The AMF sends the received N4 transparent container 2 to the SMF.

[0293] Currently, in the standard procedure, after receiving the access network tunnel information from the RAN, the SMF provides the core network tunnel information to the UPF. However, in this application, if the SMF receives N4 transparent container 2 from the UPF, and N4 transparent container 2 indicates that the N4 session has been established and the tunnel information has been set, the SMF does not perform the operation in the standard procedure, that is, it does not provide the core network tunnel information to the UPF. Therefore, in Figure 8 This step will not be shown again.

[0294] Steps 817-822 and Figure 5 Steps 518-523 in the example shown are similar and can be referred to each other, so they will not be repeated here.

[0295] Figure 9 An example of another communication method is shown, which describes in detail the communication method provided in the embodiments of this application in conjunction with the PDU session modification process. The specific process of this example may include:

[0296] Steps 901a-902 and Figure 6 Steps 601a-602 in the example shown are similar and can be referred to each other, so they will not be repeated here.

[0297] After step 902, if the UPF used for the PDU session is deployed on the same satellite as the RAN of the serving UE, then proceed directly to step 903 below.

[0298] In one possible implementation, the SMF determines, based on user plane information from the same location sent by the AMF, that the UPF used for the PDU session is the same UPF deployed on the same satellite as the RAN serving the UE.

[0299] In another possible implementation, the SMF determines during the session establishment process that the UPF used for the PDU session is a UPF deployed on the same satellite as the RAN serving the UE, and saves this information.

[0300] If the UPF used for the PDU session is not deployed on the same satellite as the RAN serving the UE, the following steps are performed when a modification to the PDU session is determined: The SMF may update the N4 rules related to the new or modified QoS (primarily modifying rules related to uplink data) and send an N4 session modification request message to the UPF. Upon receiving the N4 session modification request message, the UPF updates the corresponding rules. That is, with the method of this application, the above two steps are no longer performed. These two steps are... Figure 9 It will no longer be shown in the text.

[0301] Step 903: The SMF sends the first N2 session management information to the AMF. The first N2 session management information includes the N4 pass-through container 1 (i.e., the first N4 session management information mentioned above). The N4 pass-through container 1 contains N4 session modification request messages, which are used to update various N4 rules to the UPF.

[0302] Step 904: The AMF forwards the received N4 pass-through container 1 to the RAN.

[0303] Step 905 and Figure 6 Step 605 in the example shown is similar and can be referred to in relation to each other, so it will not be repeated here.

[0304] Step 906: The RAN sends the received N4 pass-through container 1 to the UPF.

[0305] Step 907: The UPF generates an N4 session modification response message and includes the N4 session modification response message in the N4 pass-through container 2 and sends it to the RAN. The N4 pass-through container 2 indicates that the N4 session has been updated.

[0306] In one possible implementation, if the RAN and UPF are co-deployed on the same satellite, the RAN sends N4 transparent container 1 to the UPF through its internal implementation, and the UPF sends N4 transparent container 2 to the RAN in response through its internal implementation.

[0307] In another possible implementation, if the RAN and UPF are deployed independently on the same satellite, the RAN will send the received N4 pass-through container 1 to the UPF, and the UPF will send the N4 pass-through container 2 to the RAN in response.

[0308] Step 908: The RAN sends the N4 transparent container 2 (i.e., the second information mentioned above) to the AMF.

[0309] Step 909: AMF sends N4 transparent container 2 to SMF.

[0310] Currently, in the standard procedure, after receiving the access network tunnel information from the RAN, the SMF provides the core network tunnel information to the UPF. However, in this application, if the SMF receives N4 transparent container 2 from the UPF, and N4 transparent container 2 indicates that the N4 session has been updated, the SMF does not perform the operation in the standard procedure, that is, it does not provide the core network tunnel information to the UPF. Therefore, in... Figure 9 This step will not be shown again.

[0311] Steps 910-913 and Figure 6 Steps 610-613 in the example shown are similar and can be referred to each other, so they will not be repeated here.

[0312] Figure 10 An example of another communication method is shown, which describes in detail the communication method provided in the embodiments of this application in conjunction with the PDU session release process. The specific process of this example may include:

[0313] Steps 1001a-1001f and Figure 7 Steps 701a-701f in the example shown are similar and can be referred to in relation to each other, so they will not be repeated here.

[0314] If the UPF used for the PDU session is deployed on the same satellite as the RAN of the serving UE, then when the SMF determines that the PDU session needs to be released, continue to perform step 1002 below.

[0315] In one possible implementation, the SMF determines, based on user plane information from the same location sent by the AMF, that the UPF used for the PDU session is the same UPF deployed on the same satellite as the RAN serving the UE.

[0316] In another possible implementation, the SMF determines during the session establishment process that the UPF used for the PDU session is a UPF deployed on the same satellite as the RAN serving the UE, and saves this information.

[0317] In other words, if the UPF used for the PDU session is not deployed on the same satellite as the RAN serving the UE, then when the SMF determines that the PDU session needs to be released, the following steps are performed according to the existing standard procedure: The SMF sends an N4 session release request message to the UPF. The UPF sends an N4 session release response message to the SMF. After receiving the request, the UPF discards the PDU session data packets and releases the tunnel resources and the N4 session-related context. That is to say, with the method provided in this application, the above steps are no longer performed. These two steps are... Figure 10 It will no longer be shown in the text.

[0318] Step 1002: The SMF sends the first N2 session management information to the AMF. The first N2 session management information includes the N4 pass-through container 1 (i.e., the first N4 session management information mentioned above). The N4 pass-through container 1 contains an N4 session release request message, which is used to release the N4 rule.

[0319] Step 1003: The AMF forwards the received N4 transparent container 1 to the RAN.

[0320] Step 1004 and Figure 7 Step 704 in the example shown is similar and can be referred to in relation to each other, so it will not be repeated here.

[0321] Step 1005: The RAN sends the received N4 transparent container 1 to the UPF.

[0322] Step 1006: The UPF generates an N4 session release response message, includes the N4 session release response message in the N4 pass-through container 2, and sends it to the RAN. The N4 pass-through container 2 indicates that the N4 session has been released.

[0323] In one possible implementation, if the RAN and UPF are co-deployed on the same satellite, the RAN sends N4 transparent container 1 to the UPF through its internal implementation, and the UPF sends N4 transparent container 2 to the RAN in response through its internal implementation.

[0324] In another possible implementation, if the RAN and UPF are deployed independently on the same satellite, the RAN will send the received N4 pass-through container 1 to the UPF, and the UPF will send the N4 pass-through container 2 to the RAN in response.

[0325] Step 1007: RAN sends N4 transparent container 2 to AMF.

[0326] Step 1008: AMF sends N4 transparent container 2 to SMF.

[0327] Steps 1009-1016 and Figure 7 Steps 709-716 in the example shown are similar and can be referred to each other, so they will not be repeated here.

[0328] Through the above Figures 8-10 The example shown can eliminate some communication processes between the SMF and UPF, which reduces communication between equipment on the satellite and equipment on the ground, thereby reducing service latency and improving user experience.

[0329] In another scenario, if the SMF determines that the UPF serving the UE's PDU session and the RAN serving the UE are deployed on the same satellite, then the SMF will send the signaling (i.e., N1 and N2 interface signaling) to the RAN and UE through the N4 interface. The following will illustrate... Figures 11-13 The example shown below illustrates this. Figures 11 to 13 This example illustrates the situation by having the UPF serving the UE's PDU session and the RAN serving the UE deployed on the same satellite, while the SMF is deployed on the ground.

[0330] Figure 11 An example of a communication method is shown, which describes in detail the communication method provided in the embodiments of this application in conjunction with a session establishment process. The specific process of this example may include:

[0331] Steps 1101-1109 and Figure 5 Steps 501-509 in the example shown are similar and can be referred to one another; they will not be repeated here.

[0332] Step 1110: The SMF sends the second N4 session management information to the UPF. The second N4 session management information contains the N1 session management container (i.e., the N1 session management information mentioned above) and the N2 session management container (i.e., the second N2 session management information mentioned above). The N2 session management container does not contain core network tunnel information.

[0333] Step 1111: The UPF forwards the received N1 session management container and N2 session management container to the RAN. Optionally, the UPF provides the RAN with core network tunnel information.

[0334] In one possible implementation, if the RAN and UPF are co-deployed on the same satellite, the UPF sends the N1 session management container and the N2 session management container to the RAN through its internal implementation.

[0335] In another possible implementation, if the RAN and UPF are deployed independently on the same satellite, the UPF will send the received N1 session management container and N2 session management container to the RAN.

[0336] Step 1112: The RAN sends the received N1 session management container to the UE and establishes the corresponding resources.

[0337] Step 1113: After the resources are allocated, the RAN sends a message to the UPF indicating that the resource allocation has been completed.

[0338] In one possible implementation, if the RAN and UPF are co-deployed on the same satellite, the RAN sends the information to the UPF through an internal implementation.

[0339] In another possible implementation, if the RAN and UPF are deployed independently on the same satellite, the RAN sends the information through the interface with the UPF.

[0340] Step 1114: UPF sends a notification message to SMF indicating that the user plane configuration is complete.

[0341] Steps 1115-1120 and Figure 5 Steps 518-523 in the example shown are similar and can be referred to each other, so they will not be repeated here.

[0342] Figure 12 An example of another communication method is shown, which describes in detail the communication method provided in the embodiments of this application in conjunction with the PDU session modification process. The specific process of this example may include:

[0343] Steps 1201a-1202 and Figure 6 Steps 601a-602 in the example shown are similar and can be referred to each other, so they will not be repeated here.

[0344] Step 1203: SMF sends the second N4 session management information to UPF. The second N4 session management information includes the N1 session management container (i.e., the N1 session management information mentioned above) and the N2 session management container (i.e., the second N2 session management information mentioned above).

[0345] In other words, instead of sending N1 session management information and N2 session management information to AMF in the existing manner, this application sends them to UPF through SMF.

[0346] Step 1204: SMF sends a Session Management Context Update Response Message to AMF.

[0347] It should be noted that the session management context update response message does not contain N1 session management information or N2 session management information.

[0348] Step 1205: The UPF interacts with the RAN to update QoS information, etc. Specifically, the UPF sends the received N1 session management container and N2 session management container to the RAN. For details on the interaction between the UPF and the RAN, please refer to the relevant descriptions in the preceding embodiments; they will not be described in detail here.

[0349] Step 1206: RAN updates session resources. During this process, the RAN sends the received N1 session management container to the UE.

[0350] Step 1207: After completing the resource update, the RAN notifies the UPF that the resources have been updated.

[0351] Step 1208: The UPF notifies the SMF that the session-related resources have been updated (that is, the UPF sends a notification to the SMF that the RAN has completed the context processing of the PDU session).

[0352] Step 1209 and Figure 6 Step 610 in the example shown is similar and can be referred to in relation to each other, so it will not be repeated here.

[0353] Step 1210: The RAN sends a notification message to the UPF confirming the UE's session modification.

[0354] Step 1211: The UPF sends a notification message to the SMF confirming the UE's confirmation of the session modification (that is, the UPF sends a notification message to the SMF that the UE has completed the context processing of the PDU session).

[0355] Step 1212 and Figure 6 Step 613 in the example shown is similar and can be referred to in relation to each other, so it will not be repeated here.

[0356] Figure 13 An example of another communication method is shown, which describes in detail the communication method provided in the embodiments of this application in conjunction with the PDU session release process. The specific process of this example may include:

[0357] Steps 1301a-1301f and Figure 7 Steps 701a-701f in the example shown are similar and can be referred to in relation to each other, so they will not be repeated here.

[0358] Step 1302: SMF sends an N4 session release request (i.e., the second N4 session management information mentioned above) to UPF. The N4 session release request includes an N1 session management container (i.e., the N1 session management information mentioned above) and an N2 session management container (i.e., the second N2 session management information mentioned above).

[0359] Step 1303: The SMF sends a Session Management Context Update Request Response Message to the AMF. It should be noted that the Session Management Context Update Request Response Message does not contain the N1 Session Management Container and the N2 Session Management Container.

[0360] Step 1304: The UPF sends the received N1 session management container and N2 session management container to the RAN.

[0361] Step 1305: RAN releases the relevant access network resources.

[0362] Step 1306: The RAN sends a notification to the UPF that the RAN-related PDU session resources have been released.

[0363] Step 1307: The UPF sends a notification to the SMF that the PDU session resources have been released (that is, the UPF sends a notification to the SMF that the RAN has completed the context processing of the PDU session).

[0364] Step 1308 and Figure 7 Step 709 in the example shown is similar and can be referred to in relation to each other, so it will not be repeated here.

[0365] Step 1309: The RAN sends a notification message to the UPF confirming the release of the UE's PDU session.

[0366] Step 1310: The UPF sends a notification message to the SMF confirming the release of the UE's PDU session (that is, the UPF sends a notification message to the SMF that the UE has completed the context processing of the PDU session).

[0367] Steps 1311-1314 and Figure 7 Steps 713-716 in the example shown are similar and can be referred to each other, so they will not be repeated here.

[0368] Through the above Figures 11-13 The example shown can eliminate some communication processes between the AMF and RAN, and can also effectively reduce communication between equipment on the satellite and equipment on the ground, thereby reducing service latency and improving user experience.

[0369] Based on the above embodiments, this application also provides a communication device, see below. Figure 14 As shown, the communication device 1400 may include a transceiver unit 1401 (also referred to as a communication unit 1401) and a processing unit 1402. The transceiver unit 1401 is used for receiving or sending messages (information or data) to the communication device 1400, and the processing unit 1402 is used for controlling and managing the operations of the communication device 1400. The processing unit 1402 can also control the steps performed by the transceiver unit 1401.

[0370] For example, the communication device 1400 may specifically be a session management function network element, a processor, chip, chip system, or a functional module in the session management function network element as described in the above embodiments; or, the communication device 1400 may specifically be a user plane function network element, a processor, chip, chip system, or a functional module in the user plane function network element as described in the above embodiments; or, the communication device 1400 may specifically be an access network device, a processor, chip, chip system, or a functional module in the access network device as described in the above embodiments.

[0371] In one embodiment, when the communication device 1400 is used to implement the function of the session management function network element in the above embodiment, the processing unit 1402 can be used to determine that the user plane function network element and the access network device providing services for the Protocol Data Unit (PDU) session of the terminal device are deployed on the same satellite; wherein, the session management function network element is deployed on the ground side; the transceiver unit 1401 can be used to send first session management information to the access network device, or, the transceiver unit 1401 can be used to send second session management information to the user plane function network element; the first session management information includes first session information, which is used to indicate the context in which the user plane function network element processes the PDU session; the second session management information includes second session information and third session information; wherein, the second session information is used to indicate the context in which the terminal device processes the PDU session, and the third session information is used to indicate the context in which the access network device processes the PDU session.

[0372] In an optional implementation, when the processing unit 1402 determines that the user plane function network element and the access network device providing services for the PDU session of the terminal device are deployed on the same satellite, it can be used to: control the transceiver unit 1401 to receive first information from the access and mobility management function network element, the first information indicating that the user plane function network element and the access network device providing services for the PDU session of the terminal device are deployed on the same satellite; and determine, based on the first information, that the user plane function network element and the access network device providing services for the PDU session of the terminal device are deployed on the same satellite.

[0373] For example, the first information may include one or more of the following: indication information that the access network device and the user plane function network element are independently deployed on the same satellite; indication information that the access network device and the user plane function network element are co-deployed on the same satellite; information about the satellite where the access network device and the user plane function network element are located; information about the access network device; or information about the user plane function network element.

[0374] In one possible approach, the transceiver unit 1401 may also be used to: receive first capability information from the user plane function network element before sending the first session management information to the access network device, wherein the first capability information is used to indicate that the user plane function network element supports the ability to reduce the interaction between the user plane function network element and the session management function network element.

[0375] The first session management information may further include information about the user plane function network element. Further, the first session management information may also include reduced signaling indication information, which is used to instruct the access network device to send the first session information to the user plane function network element.

[0376] In an alternative embodiment, the transceiver unit 1401 may further be used to: after sending the first session management information to the access network device, receive second information from the access network device, the second information being used to indicate that the user plane function element has completed the context processing of the PDU session and that the access network device has completed the context processing of the PDU session.

[0377] Optionally, the transceiver unit 1401 can also be used to: after sending the second session management information to the user plane function network element, receive from the user plane function network element a notification that the access network device has completed the context processing of the PDU session.

[0378] In one example, the transceiver unit 1401 can also be used to: after sending the second session management information to the user plane function network element, receive notification information from the user plane function network element that the terminal device has completed the context processing of the PDU session.

[0379] In another embodiment, when the communication device 1400 is used to implement the functions of the access network device in the above embodiments, the transceiver unit 1401 can be used to receive first session management information from the session management function network element, the first session management information including first session information, the first session information being used to instruct the user plane function network element to process the context of the PDU session of the terminal device; and to send the first N4 session management information to the user plane function network element. The processing unit 1402 can be used to control the transceiver unit 1401 to perform the above operations. Wherein, the user plane function network element and the access network device are deployed on the same satellite, and the session management function network element is deployed on the ground side.

[0380] In an optional implementation, the transceiver unit 1401 can also be used to send second capability information to the access and mobility management function network element, the second capability information being used to instruct the access network device to support signaling interaction with the user plane function network element.

[0381] For example, the first session management information may also include information about the user plane function network element.

[0382] Optionally, the first session management information may further include reduced signaling indication information, which is used to instruct the access network device to send the first session information to the user plane function network element.

[0383] In one possible embodiment, the transceiver unit 1401 may also be configured to receive third information from the user plane function network element, the third information being used to indicate that the user plane function network element has completed the context processing of the PDU session; and to send second information to the session management function network element, the second information being used to indicate that the user plane function network element has completed the context processing of the PDU session and that the access network device has completed the context processing of the PDU session.

[0384] In another embodiment, when the communication device 1400 is used to implement the functions of the user plane function network element in the above embodiments, the transceiver unit 1401 can be used to receive second session management information from the session management function network element, the second session management information including second session information and third session information; wherein, the second session information is used to instruct the terminal device to process the PDU session context, and the third session information is used to instruct the access network device to process the PDU session context; and, send the second session information and the third session information to the access network device. The processing unit 1402 can be used to control the transceiver unit 1401 to perform the above operations. The user plane function network element and the access network device are deployed on the same satellite, and the session management function network element is deployed on the ground side.

[0385] In an optional implementation, the transceiver unit 1401 may also be used to send first capability information to the session management function network element, the first capability information being used to instruct the user plane function network element to support the ability to reduce the interaction between the user plane function network element and the session management function network element.

[0386] In one possible approach, the transceiver unit 1401 can also be used to send a notification message to the session management function network element that the access network device has completed the context processing of the PDU session.

[0387] For example, the transceiver unit 1401 can also be used to send a notification message to the session management function network element that the terminal device has completed the context processing of the PDU session.

[0388] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The functional units in the embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0389] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0390] Based on the above embodiments, this application also provides a communication device, see below. Figure 15 As shown, the communication device 1500 may include a communication interface 1501 and a processor 1502. Optionally, the communication device 1500 may also include a memory 1503. The memory 1503 may be located inside or outside the communication device 1500. The processor 1502 can control the communication interface 1501 to receive and send messages, information, or data. The communication interface may be a transceiver or similar device.

[0391] Specifically, the processor 1502 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor 1502 may further include a hardware chip. This hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0392] The communication interface 1501, the processor 1502, and the memory 1503 are interconnected. Optionally, the communication interface 1501, the processor 1502, and the memory 1503 are interconnected via a bus 1504; the bus 1504 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 15 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0393] In one optional implementation, the memory 1503 is used to store programs, etc. Specifically, the program may include program code, which includes computer operation instructions. The memory 1503 may include RAM, and may also include non-volatile memory, such as one or more disk storage devices. The processor 1502 executes the application program stored in the memory 1503 to implement the above-mentioned functions, thereby realizing the functions of the communication device 1500.

[0394] For example, the communication device 1500 may be a session management function network element in the above embodiments, a user plane function network element in the above embodiments, or an access network device in the above embodiments.

[0395] In one embodiment, when the communication device 1500 implements the functions of the session management function network element in the above embodiments, the communication interface 1501 can implement the send / receive operations performed by the session management function network element in the above embodiments; the processor 1502 can implement other operations performed by the session management function network element in the above embodiments besides the send / receive operations. Specific details can be found in the relevant descriptions in the above embodiments, and will not be elaborated upon here.

[0396] In another embodiment, when the communication device 1500 implements the functions of the user plane function network element in the above embodiments, the communication interface 1501 can implement the transmit and receive operations performed by the user plane function network element in the above embodiments; the processor 1502 can implement other operations performed by the user plane function network element in the above embodiments besides the transmit and receive operations. Specific details can be found in the relevant descriptions in the above embodiments, and will not be elaborated further here.

[0397] In another embodiment, when the communication device 1500 implements the functions of the access network device in the above embodiments, the communication interface 1501 can implement the transmit and receive operations performed by the access network device in the above embodiments; the processor 1502 can implement other operations performed by the access network device in the above embodiments besides the transmit and receive operations. For specific details, please refer to the relevant descriptions in the above embodiments, which will not be described in detail here.

[0398] Based on the above embodiments, this application provides a communication system that may include the terminal equipment, session management function network element, access network equipment, user plane function network element, and access and mobility management function network element involved in the above embodiments.

[0399] This application also provides a computer-readable storage medium for storing a computer program. When the computer program is executed by a computer, the computer can perform the above-described functions. Figures 3 to 13 The embodiments described above involve the functions of the session management function network element (such as SMF), or implementing the above-mentioned functions. Figures 3 to 13 The embodiments described herein involve the functions of access network equipment (such as RAN), or the implementation of the above-mentioned functions. Figures 3 to 13 The embodiments described include the functions of user plane functional network elements (such as UPF).

[0400] This application also provides a computer program product for storing a computer program. When the computer program is executed by a computer, the computer can perform the above-described functions. Figures 3 to 13 The embodiments described above involve the functions of the session management function network element (such as SMF), or implementing the above-mentioned functions. Figures 3 to 13 The embodiments described herein involve the functions of access network equipment (such as RAN), or the implementation of the above-mentioned functions. Figures 3 to 13 The embodiments described include the functions of user plane functional network elements (such as UPF).

[0401] This application embodiment also provides a chip, including a processor, the processor being coupled to a memory, for calling a program in the memory to cause the chip to perform the above-described actions. Figures 3 to 13 The embodiments described above involve the functions of the session management function network element (such as SMF), or implementing the above-mentioned functions. Figures 3 to 13 The embodiments described herein involve the functions of access network equipment (such as RAN), or the implementation of the above-mentioned functions. Figures 3 to 13 The embodiments described include the functions of user plane functional network elements (such as UPF).

[0402] This application embodiment also provides a chip, the chip being coupled to a memory, the chip being used to implement the above... Figures 3 to 13 The embodiments described above involve the functions of the session management function network element (such as SMF), or implementing the above-mentioned functions. Figures 3 to 13The embodiments described herein involve the functions of access network equipment (such as RAN), or the implementation of the above-mentioned functions. Figures 3 to 13 The embodiments described include the functions of user plane functional network elements (such as UPF).

[0403] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0404] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0405] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0406] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0407] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method, characterized in that, include: The user plane function network element that provides services for the Protocol Data Unit (PDU) session of the terminal equipment and the access network equipment are deployed on the same satellite; The session management function network element is deployed on the ground side; The session management function network element sends the first session management information to the access network device, or the session management function network element sends the second session management information to the user plane function network element; The first session management information includes first session information, which is used to instruct the user plane function network element to process the context of the PDU session. The second session management information includes second session information and third session information. The second session information is used to instruct the terminal device to process the context of the PDU session, and the third session information is used to instruct the access network device to process the context of the PDU session.

2. The method as described in claim 1, characterized in that, The session management function network element determines that the user plane function network element and the access network equipment that provide services for the PDU session of the terminal device are deployed on the same satellite, including: The session management function network element receives first information from the access and mobility management function network element, the first information being used to indicate that the user plane function network element providing services for the PDU session of the terminal device and the access network device are deployed on the same satellite; Based on the first information, the session management function network element determines that the user plane function network element that provides services for the PDU session of the terminal device and the access network device are deployed on the same satellite.

3. The method as described in claim 2, characterized in that, The first information includes one or more of the following: The indication information that the access network equipment and the user plane function network elements are independently deployed on the same satellite; The indication information that the access network equipment and the user plane function network element are co-deployed on the same satellite; Information about the satellites where the access network equipment and the user plane function network elements are located; Information about the access network device or information about the user plane function network element.

4. The method according to any one of claims 1-3, characterized in that, Before the session management function network element sends the first session management information to the access network device, the method further includes: The session management function network element receives first capability information from the user plane function network element. The first capability information is used to indicate that the user plane function network element supports the ability to reduce the interaction between the user plane function network element and the session management function network element.

5. The method according to any one of claims 1-4, characterized in that, The first session management information also includes information about the user plane function network element.

6. The method according to any one of claims 1-5, characterized in that, The first session management information also includes reduced signaling indication information, which is used to instruct the access network device to send the first session information to the user plane function network element.

7. The method according to any one of claims 1-6, characterized in that, After the session management function network element sends the first session management information to the access network device, the method further includes: The session management function network element receives second information from the access network device, the second information being used to indicate that the user plane function network element has completed the context processing of the PDU session and that the access network device has completed the context processing of the PDU session.

8. The method according to any one of claims 1-3, characterized in that, After the session management function network element sends the second session management information to the user plane function network element, the method further includes: The session management function network element receives notification information from the user plane function network element that the access network device has completed the context processing of the PDU session.

9. The method according to any one of claims 1-3 and 8, characterized in that, After the session management function network element sends the second session management information to the user plane function network element, the method further includes: The session management function network element receives notification information from the user plane function network element that the terminal device has completed the context processing of the PDU session.

10. A communication method, characterized in that, include: The access network device receives first session management information from the session management function network element. The first session management information includes first session information, which is used to instruct the user plane function network element to process the context of the PDU session of the terminal device. The access network device sends the first session information to the user plane function network element; The user plane function network element and the access network equipment are deployed on the same satellite, while the session management function network element is deployed on the ground side.

11. The method as described in claim 10, characterized in that, The method further includes: The access network device sends second capability information to the access and mobility management function network element, the second capability information being used to instruct the access network device to support signaling interaction with the user plane function network element.

12. The method as described in claim 10 or 11, characterized in that, The first session management information also includes information about the user plane function network element.

13. The method according to any one of claims 10-12, characterized in that, The first session management information also includes reduced signaling indication information, which is used to instruct the access network device to send the first session information to the user plane function network element.

14. The method according to any one of claims 10-13, characterized in that, The method further includes: The access network device receives third information from the user plane function network element, the third information being used to indicate that the user plane function network element has completed the context processing of the PDU session; The access network device sends a second message to the session management function network element, the second message indicating that the user plane function network element has completed the context processing of the PDU session and that the access network device has completed the context processing of the PDU session.

15. A communication method, characterized in that, include: The user plane function network element receives second session management information from the session management function network element. The second session management information includes second session information and third session information. The second session information is used to indicate the context in which the terminal device processes the PDU session, and the third session information is used to indicate the context in which the access network device processes the PDU session. The user plane function network element sends the second session information and the third session information to the access network device; The user plane function network element and the access network equipment are deployed on the same satellite, while the session management function network element is deployed on the ground side.

16. The method as described in claim 15, characterized in that, Before the user plane function network element receives the second session management information from the session management function network element, the method further includes: The user plane function network element sends first capability information to the session management function network element. The first capability information is used to instruct the user plane function network element to support the ability to reduce the interaction between the user plane function network element and the session management function network element.

17. The method as described in claim 15 or 16, characterized in that, The method further includes: The user plane function network element sends a notification message to the session management function network element that the access network device has completed the context processing of the PDU session.

18. The method according to any one of claims 15-17, characterized in that, The method further includes: The user plane function network element sends a notification message to the session management function network element that the terminal device has completed the context processing of the PDU session.

19. A communication device, characterized in that, Includes memory, processor, and communication interface, wherein: The memory is used to store computer instructions; The communication interface is used to receive and send information or messages; The processor is coupled to the memory and is used to invoke the computer instructions in the memory to execute the method as described in any one of claims 1-9 via the communication interface.

20. A communication device, characterized in that, Includes memory, processor, and communication interface, wherein: The memory is used to store computer instructions; The communication interface is used to receive and send information or messages; The processor is coupled to the memory and is used to invoke the computer instructions in the memory to execute the method as described in any one of claims 10-14 via the communication interface.

21. A communication device, characterized in that, Includes memory, processor, and communication interface, wherein: The memory is used to store computer instructions; The communication interface is used to receive and send information or messages; The processor is coupled to the memory and is used to invoke the computer instructions in the memory to execute the method as described in any one of claims 15-18 via the communication interface.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when invoked by the computer, perform the method as described in any one of claims 1-9, or the method as described in any one of claims 10-14, or the method as described in any one of claims 15-18.

23. A computer program product, characterized in that, It includes instructions that, when executed on a computer, cause the method of any one of claims 1-9, or the method of any one of claims 10-14, or the method of any one of claims 15-18 to be performed.

24. A chip, characterized in that, The chip includes a processor coupled to a memory for reading and executing program instructions stored in the memory to implement the method as described in any one of claims 1-9, or the method as described in any one of claims 10-14, or the method as described in any one of claims 15-18.

Images