Communication method and device

Abstract

Provided are a communication method and device, the method comprising: a session management network element receiving first information from a first anchor point user plane network element anchored by a first session established by a first terminal device, the first information comprising address information of data transmitted between the first terminal device and a second terminal device; and the session management network element determines whether the first terminal equipment and the second terminal equipment use the same access network or the same backhaul network according to the first information, and determines a first network element for forwarding the data of the first session under the condition of using the same access network or the same backhaul network. According to information reported by a session-anchored anchor point user plane network element, when a point-to-point communication terminal device uses the same access network or the same backhaul network, a new network element is determined to provide a forwarding service for session data so as to avoid point-to-point data transmission only based on the session-anchored anchor point user plane network element. And the performance of point-to-point data transmission is improved.

Description

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

[0002] This application relates to the field of communications, and more specifically, to a communication method and apparatus. Background Technology

[0003] In current 5G communication systems, point-to-point communication between two terminal devices can be divided into two modes: one mode is where the terminal device has a peer-to-peer application, and the terminal devices need to directly transmit user plane data based on the peer's Internet Protocol (IP) address; the other mode is where the two terminal devices belong to the same 5G Virtual Network (5G VN) group, and the two terminal devices communicate within the 5G VN group.

[0004] The two point-to-point communication methods described above achieve point-to-point data transmission based on ground anchor user plane network elements anchored to the session. However, in certain scenarios (such as when the two terminal devices in point-to-point communication use the same satellite access network or the same satellite backhaul link), still using ground anchor user plane network elements for point-to-point data transmission may increase data transmission latency. Therefore, how to adjust the network elements that provide forwarding services for session data to improve the performance of point-to-point communication between terminal devices has become an urgent problem to be solved. Summary of the Invention

[0005] This application provides a communication method that determines a new network element to provide forwarding services for session data based on information reported by the user plane network element anchored to the session, thereby improving the performance of point-to-point data transmission.

[0006] Firstly, a communication method is provided, which can be executed by a session management network element, or by a component of the session management network element (such as a chip or circuit). There is no limitation on this. For ease of description, the following explanation will take execution by the session management network element as an example.

[0007] The method includes: a session management network element receiving first information from a first anchor user plane network element, the first anchor user plane network element being the user plane network element anchored to the first session established by the first terminal device, wherein the first information includes the source address and / or the destination address of the first data, and the first data includes data of the first session sent by the first terminal device to a second terminal device and / or data sent by the second terminal device to the first terminal device; the session management network element determining, based on the first information, whether the first terminal device and the second terminal device use the same access network or the same backhaul network, and if the first terminal device and the second terminal device use the same access network or the same backhaul network, the session management network element determining a first network element for forwarding the data of the first session.

[0008] Based on the above technical solution, the session management network element determines whether the two terminal devices (e.g., the first terminal device and the second terminal device) in point-to-point communication use the same access network or the same backhaul network according to the information reported by the anchor user plane network element to which the session is anchored. If the two terminal devices in point-to-point communication use the same access network or the same backhaul network, a new network element is determined to provide forwarding services for the session data, in order to avoid data transmission only based on the anchor user plane network element to which the session is anchored and improve the performance of point-to-point data transmission.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the first information includes the address of the second terminal device, and the session management network element determines whether the first terminal device and the second terminal device use the same access network or the same backhaul network based on the first information, including: the session management network element determines the location information of the second terminal device based on the address of the second terminal device; the session management network element determines whether the first terminal device and the second terminal device use the same access network or the same backhaul network based on the location information of the first terminal device and the location information of the second terminal device.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the first information includes the address of the second terminal device. The session management network element determines whether the first terminal device and the second terminal device use the same access network or the same backhaul network based on the first information, including: the session management network element determines the second data network access identifier corresponding to the session of the second terminal device based on the address of the second terminal device; the session management network element determines whether the first terminal device and the second terminal device use the same access network or the same backhaul network based on the first data network access identifier corresponding to the first session and the second data network access identifier.

[0011] Based on the above technical solution, when the first information includes the address of the second terminal device, the session management network element can determine whether the terminal devices in point-to-point communication use the same access network or the same backhaul network based on the location information of the terminal devices in point-to-point communication or the data network access identifier corresponding to the session of the terminal devices. In other words, the session management network element can determine whether the terminal devices in point-to-point communication use the same access network or the same backhaul network in different ways, thereby improving the flexibility of the solution.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, the access network includes the satellite or satellite constellation where the access network equipment is located; the backhaul network includes the satellite, the backhaul link, and the satellite constellation in the backhaul link.

[0013] For example, when two terminal devices performing point-to-point communication use the same satellite access network or the same satellite backhaul link, the session management network element can determine that the onboard network element provides forwarding services for the terminal device's data in order to reduce data transmission latency.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the first network element includes a second anchor user plane network element or an intermediate user plane network element, wherein the second anchor user plane network element is a user plane network element other than the first anchor user plane network element anchored to the first session, and the intermediate user plane network element is used to provide forwarding services for communication between the first terminal device and the second terminal device through the first session.

[0015] Based on the above technical solution, the first network element determined by the session management network element can be either an anchor user plane network element or an intermediate user plane network element (such as an enhanced ULCL that can provide forwarding services after being enhanced from a regular ULCL, or a regular ULCL and a local anchor user plane network element). It is not limited to being an anchor user plane network element, thus improving the flexibility of the solution.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, if the first network element is the intermediate user plane network element, then when the first terminal device and the second terminal device use the same access network or the same backhaul network, determining the first network element for forwarding the data of the first session includes: when the first terminal device and the second terminal device use the same access network or the same backhaul network, the session management network element determines to insert the first network element or use the already inserted first network element.

[0017] When the first network element is an intermediate user plane network element, the first network element can be inserted by the session management network element.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, if the first network element is the second anchor user plane network element, the method further includes: the session management network element migrating the first session from being anchored to the first anchor user plane network element to being anchored to the second anchor user plane network element.

[0019] When the first network element is the second anchor point user plane network element, the first network element can be understood as the anchor point user plane network element that the first session re-anchors.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, the first network element is located on a satellite.

[0021] Based on the above technical solution, the first network element determined by the session management network element can be the satellite-borne first network element, in order to reduce the data transmission latency when two terminal devices performing point-to-point communication use the same satellite access network or the same satellite backhaul link.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the session management network element sending first indication information to the first anchor user plane network element, the first indication information being used to instruct the first anchor user plane network element to report the first information when a first condition is met; the first condition includes receiving data from the first terminal device sent to other terminal devices and / or receiving data from other terminal devices sent to the first terminal device.

[0023] Based on the above technical solution, the first anchor point user plane network element can report the first information based on the instructions of the session management network element, so as to clarify the timing of reporting the first information.

[0024] In conjunction with the first aspect, in some implementations of the first aspect, before the session management network element sends the first indication information to the first anchor user plane network element, the method further includes: the session management network element determining to send the first indication information to the first anchor user plane network element based on second information, wherein the second information includes at least one of the following: access type RAT information corresponding to the first session, backhaul link type information corresponding to the first session, or location information of the first terminal device.

[0025] Based on the above technical solution, the session management network element can determine whether to send the first instruction information according to the second information, instead of blindly sending the first instruction information, thereby improving the accuracy of the solution.

[0026] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the session management network element determining the first anchor user plane network element based on the fourth information, wherein the fourth information includes at least one of the following: access type RAT information corresponding to the first session, backhaul link type information corresponding to the first session, location information of the first terminal device, or indication information allowing the first session to perform point-to-point communication based on the first network element.

[0027] In conjunction with the first aspect, in some implementations of the first aspect, before the session management network element receives the first information from the first anchor user plane network element, the method further includes: the session management network element inserting the first network element according to the third information; wherein the third information includes at least one of the following: the first information, satellite operation and control information, access type RAT information corresponding to the first session, location information of the first terminal device, or location information of the second terminal device.

[0028] Based on the above technical solution, the session management network element can pre-insert the first network element according to the third information, which can be of various types, thus improving the flexibility of the solution.

[0029] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the session management network element sending a packet detection rule (PDR) and a packet forwarding rule (FAR) to the first network element, wherein the PDR and the FAR are used to instruct the first network element to forward the data of the first session.

[0030] Based on the above technical solution, the session management network element can enable the first network element to forward data by configuring PDR and FAR for the first network element.

[0031] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the session management network element establishing a first forwarding tunnel between the first network element and the second network element, the first forwarding tunnel being used to transmit data between the first network element and the second network element, wherein the second network element is a network element that forwards data of the second session established by the second terminal device.

[0032] Based on the above technical solution, the first network element can forward the data of the first session based on the first forwarding tunnel, so as to enable point-to-point communication between the first terminal device and the second terminal device even when the first network element forwarding the data of the first session established by the first terminal device is different from the second network element forwarding the data of the second session established by the second terminal device.

[0033] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the session management network element establishing a second forwarding tunnel between the first anchor user plane network element and the first network element, the second forwarding tunnel being used to transmit data between the first anchor user plane network element and the first network element.

[0034] Based on the above technical solution, the session management network element can also establish a tunnel between the determined first network element and the first anchor user plane network element, so as to realize point-to-point communication between the first terminal device and the other terminal device when the session of other terminal devices is anchored to the first anchor user plane network element.

[0035] In conjunction with the first aspect, in some implementations of the first aspect, when the first access network device accessed by the first terminal device is switched to the second access network device, the method further includes: the session management network element determining whether the session set to be switched includes the first session based on the session set to be switched; if the session set includes the first session, the session management network element determining the third network element to forward the data of the first session based on the first information.

[0036] Based on the above technical solution, when the access network equipment accessed by the first terminal device is switched, the session management network element can re-determine the network element that provides data forwarding services for the migrated session.

[0037] In conjunction with the first aspect, in some implementations of the first aspect, the first information further includes at least one of the following: the source interface identifier of the first data, the identifier information of the local area network group to which the first terminal device belongs, the network instance information used by the first anchor user plane network element to receive the first data, or the network instance information used by the first anchor user plane network element to send the first data.

[0038] Secondly, a communication method is provided, which can be executed by a first anchor user plane network element, or by a component of the first anchor user plane network element (such as a chip or circuit), without limitation. For ease of description, the following description takes execution by the first anchor user plane network element as an example.

[0039] The method includes: a first anchor user plane network element determining first information, the first anchor user plane network element being the anchor user plane network element to which a first session established by a first terminal device is anchored; the first anchor user plane network element sending the first information to a session management network element, wherein the first information includes the source address of the first data and / or the destination address of the first data, the first data including the data of the first session to be sent by the first terminal device to a second terminal device and / or the data sent by the second terminal device to the first terminal device, and the first information being used to determine whether the first terminal device and the second terminal device use the same access network or the same backhaul network.

[0040] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: The first anchor user plane network element receives first indication information from the session management network element. The first indication information is used to instruct the first anchor user plane network element to report the first information when a first condition is met. The first anchor user plane network element determines whether the first condition is met. If the first condition is met, the first anchor user plane network element sends the first information to the session management network element. The first condition includes receiving data from the first terminal device sent to other terminal devices and / or receiving data from other terminal devices sent to the first terminal device.

[0041] In conjunction with the second aspect, in some implementations of the second aspect, the first information further includes at least one of the following: the source interface identifier of the first data, the identifier information of the local area network group to which the first terminal device belongs, the network instance information used by the first anchor user plane network element to receive the first data, the network instance information used by the first anchor user plane network element to send the first data, the N3 or N9 tunnel information used by the first anchor user plane network element to receive the first data, or the N3 or N9 tunnel information used by the first anchor user plane network element to send the first data.

[0042] The beneficial effects of the methods shown in the second aspect and its possible designs above can be referred to the beneficial effects in the first aspect and its possible designs.

[0043] Thirdly, a communication method is provided, which can be executed by a first network element or by a component of the first network element (such as a chip or circuit). There is no limitation on this. For ease of description, the following explanation will take execution by the first network element as an example.

[0044] The method includes: a first network element receiving a packet detection rule (PDR) and a packet forwarding rule (FAR) from a session management network element; the first network element forwarding data of a first session according to the PDR and FAR, wherein the first network element is a network element that forwards data of a first session established by a first terminal device.

[0045] In conjunction with the third aspect, in some implementations of the third aspect, the first network element includes a second anchor user plane network element or an intermediate user plane network element, wherein the second anchor user plane network element is a user plane network element other than the first anchor user plane network element anchored to the first session, and the intermediate user plane network element is used to provide forwarding services for communication between the first terminal device and the second terminal device through the first session.

[0046] In conjunction with the third aspect, in some implementations of the third aspect, the first network element is located on a satellite.

[0047] In conjunction with the third aspect, in some implementations of the third aspect, the first network element forwards the data of the first session according to the PDR and FAR, including: the first network element sending the data of the first session to the second network element through the first forwarding tunnel according to the PDR and FAR, wherein the second network element is a network element that forwards the data of the second session established by the second terminal device, and the first forwarding tunnel is used to transmit data between the first network element and the second network element.

[0048] In conjunction with the third aspect, in some implementations of the third aspect, the first network element forwards the data of the first session according to the PDR and FAR, including: the first network element sends the data of the first session to the third access network device according to the PDR and FAR, wherein the third access network device is the network device accessed by the second terminal device.

[0049] The beneficial effects of the methods shown in the third aspect and its possible designs above can be referred to the beneficial effects in the first aspect and its possible designs.

[0050] Fourthly, a communication device is provided for performing the method provided in the first aspect.

[0051] The apparatus includes: a receiving unit, configured to receive first information from a first anchor user plane network element, the first anchor user plane network element being the anchored user plane network element for a first session established by a first terminal device, wherein the first information includes the source address and / or the destination address of the first data, and the first data includes data of the first session sent by the first terminal device to a second terminal device and / or data sent by the second terminal device to the first terminal device; and a processing unit, configured to determine, based on the first information, whether the first terminal device and the second terminal device use the same access network or the same backhaul network; if the first terminal device and the second terminal device use the same access network or the same backhaul network, the processing unit is further configured to determine a first network element for forwarding the data of the first session.

[0052] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first information includes the address of the second terminal device, and the processing unit determines whether the first terminal device and the second terminal device use the same access network or the same backhaul network based on the first information, including: the processing unit determines the location information of the second terminal device based on the address of the second terminal device; the processing unit determines whether the first terminal device and the second terminal device use the same access network or the same backhaul network based on the location information of the first terminal device and the location information of the second terminal device.

[0053] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first information includes the address of the second terminal device. The processing unit determines whether the first terminal device and the second terminal device use the same access network or the same backhaul network based on the first information, including: the processing unit determines a second data network access identifier corresponding to the session of the second terminal device based on the address of the second terminal device; the processing unit determines whether the first terminal device and the second terminal device use the same access network or the same backhaul network based on the first data network access identifier corresponding to the first session and the second data network access identifier.

[0054] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the access network includes the satellite or satellite constellation where the access network equipment is located; the backhaul network includes the satellite, the backhaul link, and the satellite constellation in the backhaul link.

[0055] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first network element includes a second anchor user plane network element or an intermediate user plane network element, wherein the second anchor user plane network element is a user plane network element other than the first anchor user plane network element anchored to the first session, and the intermediate user plane network element is used to provide forwarding services for communication between the first terminal device and the second terminal device through the first session.

[0056] In conjunction with the fourth aspect, in some implementations of the fourth aspect, if the first network element is the intermediate user plane network element, then when the first terminal device and the second terminal device use the same access network or the same backhaul network, determining the first network element for forwarding the data of the first session includes: when the first terminal device and the second terminal device use the same access network or the same backhaul network, the processing unit determines to insert the first network element or use the already inserted first network element.

[0057] In conjunction with the fourth aspect, in some implementations of the fourth aspect, if the first network element is the second anchor user plane network element, the method further includes: the session management network element migrating the first session from being anchored to the first anchor user plane network element to being anchored to the second anchor user plane network element.

[0058] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first network element is located on a satellite.

[0059] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the apparatus further includes: a transmitting unit, configured to transmit first indication information to the first anchor user plane network element, the first indication information being configured to instruct the first anchor user plane network element to report the first information if a first condition is met; the first condition includes receiving data from the first terminal device sent to other terminal devices and / or receiving data from other terminal devices sent to the first terminal device.

[0060] In conjunction with the fourth aspect, in some implementations of the fourth aspect, before the sending unit sends the first indication information to the first anchor user plane network element, the processing unit is further configured to determine, based on the second information, to send the first indication information to the first anchor user plane network element, wherein the second information includes at least one of the following: access type RAT information corresponding to the first session, backhaul link type information corresponding to the first session, or location information of the first terminal device.

[0061] In conjunction with the fourth aspect, in some implementations of the fourth aspect, before the session management network element receives the first information from the first anchor user plane network element, the processing unit is further configured to insert the first network element according to the third information; wherein the third information includes at least one of the following: the first information, satellite operation and control information, access type RAT information corresponding to the first session, location information of the first terminal device, or location information of the second terminal device.

[0062] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the apparatus further includes: a sending unit, configured to send a packet detection rule (PDR) and a packet forwarding rule (FAR) to the first network element, wherein the PDR and the FAR are used to instruct the first network element to forward the data of the first session.

[0063] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the processing unit is further configured to establish a first forwarding tunnel between the first network element and the second network element, the first forwarding tunnel being used to transmit data between the first network element and the second network element, wherein the second network element is a network element that forwards data of the second session established by the second terminal device.

[0064] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the processing unit is further configured to establish a second forwarding tunnel between the first anchor user plane network element and the first network element, the second forwarding tunnel being used to transmit data between the first anchor user plane network element and the first network element.

[0065] In conjunction with the fourth aspect, in some implementations of the fourth aspect, when the first access network device accessed by the first terminal device is switched to the second access network device, the processing unit is further configured to determine whether the session set to be switched includes the first session based on the session set to be switched. If the session set includes the first session, the processing unit is further configured to determine whether the third network element forwards the data of the first session based on the first information.

[0066] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first information further includes at least one of the following: the source interface identifier of the first data, the identifier information of the local area network group to which the first terminal device belongs, the network instance information used by the first anchor user plane network element to receive the first data, the network instance information used by the first anchor user plane network element to send the first data, the N3 or N9 tunnel information used by the first anchor user plane network element to receive the first data, or the N3 or N9 tunnel information used by the first anchor user plane network element to send the first data.

[0067] The beneficial effects of the methods shown in the fourth aspect and its possible designs above can be referred to the beneficial effects in the first aspect and its possible designs.

[0068] Fifthly, a communication device is provided for performing the method provided in the second aspect above.

[0069] The device includes: a processing unit for determining first information, wherein the first anchor user plane network element is the anchor user plane network element to which the first session established by the first terminal device is anchored; and a sending unit for sending the first information to a session management network element, wherein the first information includes the source address of the first data and / or the destination address of the first data, the first data includes data of the first session sent by the first terminal device to the second terminal device and / or data sent by the second terminal device to the first terminal device, and the first information is used to determine whether the first terminal device and the second terminal device use the same access network or the same backhaul network.

[0070] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the apparatus further includes: a receiving unit, configured to receive first indication information from the session management network element, the first indication information being configured to instruct the first anchor user plane network element to report the first information if a first condition is met; the processing unit determining whether the first condition is met, and if the first condition is met, the sending unit sending the first information to the session management network element; the first condition including receiving data from the first terminal device sent to other terminal devices and / or receiving data from other terminal devices sent to the first terminal device.

[0071] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first information further includes at least one of the following: the source interface identifier of the first data, the identifier information of the local area network group to which the first terminal device belongs, the network instance information used by the first anchor user plane network element to receive the first data, the network instance information used by the first anchor user plane network element to send the first data, the N3 or N9 tunnel information used by the first anchor user plane network element to receive the first data, or the N3 or N9 tunnel information used by the first anchor user plane network element to send the first data.

[0072] The beneficial effects of the methods shown in the fifth aspect above and its possible designs can be referred to the beneficial effects in the second aspect and its possible designs.

[0073] In a sixth aspect, a communication device is provided for performing the method provided in the third aspect above.

[0074] The device includes: a receiving unit for receiving packet detection rules (PDR) and packet forwarding rules (FAR) from a session management network element; and a processing unit for forwarding data of a first session according to the PDR and FAR, wherein the first network element is a network element that forwards data of a first session established by a first terminal device.

[0075] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the first network element includes a second anchor user plane network element or an intermediate user plane network element, wherein the second anchor user plane network element is a user plane network element other than the first anchor user plane network element anchored to the first session, and the intermediate user plane network element is used to provide forwarding services for communication between the first terminal device and the second terminal device through the first session.

[0076] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the first network element is located on a satellite.

[0077] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the processing unit forwards the data of the first session according to the PDR and FAR, including: the processing unit sends the data of the first session to the second network element through the first forwarding tunnel according to the PDR and FAR, wherein the second network element is the network element that forwards the data of the second session established by the second terminal device.

[0078] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the processing unit forwards the data of the first session according to the PDR and FAR, including: the processing unit sends the data of the first session to a third access network device according to the PDR and FAR, wherein the third access network device is a network device accessed by the second terminal device.

[0079] The beneficial effects of the methods shown in the sixth aspect above and its possible designs can be referred to the beneficial effects in the third aspect and its possible designs.

[0080] In a seventh aspect, a communication apparatus is provided for performing the method provided in the first aspect. Specifically, the communication apparatus may include units and / or modules for performing the method provided in any of the above implementations of the first aspect, such as a processing unit and an acquisition unit.

[0081] In one implementation, the transceiver unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0082] In another implementation, the transceiver unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0083] In an eighth aspect, a communication apparatus is provided for performing the method provided in the second aspect. Specifically, the communication apparatus may include units and / or modules for performing the method provided in the second aspect, such as a processing unit and an acquisition unit.

[0084] In one implementation, the transceiver unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0085] In another implementation, the transceiver unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0086] A ninth aspect provides a communication apparatus for performing the method provided in the third aspect. Specifically, the communication apparatus may include units and / or modules for performing the method provided in the third aspect, such as a processing unit and an acquisition unit.

[0087] In one implementation, the transceiver unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0088] In another implementation, the transceiver unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0089] In a tenth aspect, this application provides a processor for performing the methods provided in the foregoing aspects.

[0090] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0091] Eleventhly, a computer-readable storage medium is provided that stores program code for execution by a device, the program code including a method for performing any of the implementations of the first to third aspects described above.

[0092] In a twelfth aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method provided by any of the implementations of the first to third aspects described above.

[0093] In a thirteenth aspect, a chip is provided, the chip including a processor and a communication interface, wherein the processor reads instructions stored in a memory through the communication interface and executes the method provided by any of the implementations of the first to third aspects described above.

[0094] Optionally, as one implementation, the chip also includes a memory storing computer programs or instructions, and a processor for executing the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the processor is used to execute the method provided by any of the first to third aspects described above.

[0095] Fourteenth aspect, a communication system is provided, comprising any plurality of the communication devices of the fourth to sixth aspects. Attached Figure Description

[0096] Figure 1 A schematic diagram of the architecture of a 5G system to which embodiments of this application are applicable is shown.

[0097] Figure 2 This is a schematic diagram of 5G VN communication user plane data forwarding based on N19 provided in an embodiment of this application.

[0098] Figure 3 This is a schematic diagram of local forwarding of 5G VN communication user plane data provided in an embodiment of this application.

[0099] Figure 4 This is a schematic diagram illustrating a satellite access provision provided in an embodiment of this application.

[0100] Figure 5 This is a schematic diagram of a satellite providing backhaul according to an embodiment of this application.

[0101] Figure 6 This is a two-dimensional unfolded diagram of a polar orbital constellation.

[0102] Figure 7 This is a schematic flowchart of a communication method provided in this application.

[0103] Figure 8 This is a schematic flowchart illustrating another communication method provided in an embodiment of this application.

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

[0105] Figure 10 This is a schematic block diagram of the device 1000 provided in the embodiments of this application.

[0106] Figure 11 This is a schematic block diagram of the device 1100 provided in the embodiments of this application. Detailed Implementation

[0107] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

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

[0109] To facilitate understanding of the embodiments of this application, firstly, in conjunction with Figure 1 This paper briefly introduces the communication system to which the embodiments of this application are applicable.

[0110] As an example, Figure 1 A schematic diagram of the architecture of a 5G system to which embodiments of this application are applicable is shown. Figure 1 This is a schematic diagram of a 5G network architecture based on service-oriented interfaces. Figure 1 As shown, the network architecture may include, but is not limited to, the following network elements (or functional network elements, functional entities, nodes, devices, etc.): User equipment (UE), radio access network (R)AN, access and mobility management function (AMF) network elements, session management function (SMF) network elements, user plane function (UPF) network elements, policy control function (PCF) network elements, unified data management (UDM) network elements, application function (AF) network elements, data network (DN), network slice selection function (NSSF), authentication server function (AUSF), network exposure function (NEF) network elements, binding support function (BSF) network elements, unified data repository (UDR), etc.

[0111] The following is about Figure 1 A brief introduction to each network element shown in the image: 1. UE: This can include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, as well as various forms of terminals, mobile stations (MS), terminals, or soft terminals, etc. For example, water meters, electricity meters, sensors, etc.

[0112] For example, the user equipment in the embodiments of this application may refer to an access terminal, user unit, user station, mobile station, mobile station, relay station, remote station, remote terminal, mobile device, user terminal, terminal equipment, wireless communication equipment, user agent, or user device. The user equipment may also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, user equipment in a 5G network, or user equipment in a future evolved public land mobile network (PLMN) or user equipment in a future vehicle network, etc. The embodiments of this application are not limited in this respect.

[0113] As an example and not a limitation, in this application embodiment, wearable devices can also be called wearable smart devices. This is a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices; they achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functionality without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific application function and require use with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0114] Furthermore, in this embodiment, the user equipment can also be a user equipment within an Internet of Things (IoT) system. IoT is an important component of future information technology development, and its main technical characteristic is connecting objects to networks via communication technologies, thereby realizing an intelligent network that enables human-machine interconnection and machine-to-machine interconnection. In this embodiment, IoT technology can achieve massive connectivity, deep coverage, and low terminal power consumption through technologies such as narrowband (NB).

[0115] In addition, in the embodiments of this application, the user equipment may also include sensors, whose main functions include collecting data (for some user equipment), receiving control information and downlink data from the access network equipment, and sending electromagnetic waves to transmit uplink data to the access network equipment.

[0116] In this application embodiment, the device for implementing the function of the user equipment can be the user equipment itself, or it can be a device that supports the user equipment in implementing the function, such as a chip system or a combination device or component that can implement the function of the user equipment. The device can be installed in the user equipment.

[0117] In this application embodiment, the chip system may be composed of chips, or it may include chips and other discrete devices. In the technical solutions provided in this application embodiment, the user equipment itself is used as an example to illustrate the technical solutions provided in this application embodiment.

[0118] 2. (R)AN: Used to provide network access functionality for authorized user equipment in a specific area, and can use transmission tunnels with different service qualities according to the user equipment level, service requirements, etc.

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

[0120] For example, the access network device in this application embodiment can be any communication device with wireless transceiver function for communicating with user equipment. The access network equipment includes, but is not limited to: evolved NodeB (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved Node B (HeNB, or home Node B (HNB), baseband unit (BBU), access point (AP), wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP) in a wireless fidelity (WIFI) system. It can also be a gNB in ​​a 5G system, such as NR, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or transmission point, such as a baseband unit (BBU) or a distributed unit (DU).

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

[0122] 3. UPF network element: mainly includes the following functions: data packet routing and transmission, data packet detection, service usage reporting, quality of service (QoS) processing, uplink data packet detection, downlink data packet storage and other user plane related functions.

[0123] In 5G communication systems, this user plane network element can be a UPF network element. In future communication systems, the user plane network element can still be a UPF network element, or it can have other names; this application does not limit this.

[0124] For example, a UPF may include a packet data unit session anchor UPF (PSA UPF) and an intermediate UPF (I-UPF).

[0125] Among them, the PSA UPF is a UPF that supports the PDU session anchor point function. It is a UPF that connects to the DN through the N6 interface and is responsible for data transmission between the core network and the data network; all UPFs between (R)AN and PSA UPF are called I-UPF.

[0126] For example, the uplink classifier functionality UPF (UL CL UPF) involved in the embodiments of this application is a UPF that can implement the uplink classifier function, which is inserted into the session of the terminal device by the SMF. Specifically, the UL CL UPF is connected to the PSA UPF through the N9 interface. For uplink data (which can also be called traffic, data packets, etc.), after identification according to the forwarding rules, it distinguishes the data that needs to be sent to the PSA UPF and forwards it. For downlink data, the data from the PSA UPF is forwarded to the RAN through the N3 interface. In this application, the UL CL UPF can be understood as a specific I-UPF. In addition, the UL CL UPF can also be co-located with the PSA UPF. For example, the UL CL UPF and the Local PSA UPF are co-located. That is to say, the UL CL UPF involved in the embodiments of this application can be understood as implementing part of the functions of the network element that implements the co-location of the UL CL UPF and the Local PSA UPF (e.g., the data offloading function and the data forwarding function are implemented by the Local PSA UPF).

[0127] It should be noted that the specific form of the I-UPF is not limited in the embodiments of this application. The UL CLUPF mentioned above is just an example and does not constitute any limitation on the scope of protection of this application. For example, the I-UPF can also be a branch point (BP) UPF (such as the I-UPF in the Internet Protocol Version 6 Multi-home (IPv6 Multi-home) scenario); or, the I-UPF can be a network element that combines UL CL UPF and LocalPSA UPF; or, the I-UPF can be called an on-board UPF, etc.

[0128] 4. DN: A network used to provide data transmission.

[0129] In 5G communication systems, this data network element can be a DN (Digital Network Element). In future communication systems, the data network element can still be a DN element, or it can have other names; this application does not limit this.

[0130] 5. AMF network element: mainly includes the following functions: connection management, mobility management, registration management, access authentication and authorization, reachability management, security context management and other access and mobility-related functions.

[0131] In 5G communication systems, the access management network element can be an AMF network element. In future communication systems, the access management network element can still be an AMF network element, or it can have other names; this application does not limit this.

[0132] 6. SMF: Primarily used for session management, allocation and management of Internet Protocol (IP) addresses for terminal devices, selection of manageable user plane functions, endpoints for policy control and billing function interfaces, and downlink data notification, etc.

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

[0134] 7. PCF: A unified policy framework used to guide network behavior, providing policy rule information for control plane functional network elements (such as AMF, SMF, etc.).

[0135] 8. UDM: This can be understood as the naming of the Unified Data Management Network Element in the 5G architecture. The Unified Data Management Network Element mainly includes the following functions: unified data management, supporting authentication trust processing in 3GPP authentication and key negotiation mechanisms, user identity processing, access authorization, registration and mobility management, subscription management, and SMS management.

[0136] 9. AF: Used to provide application layer information. It can interact with the policy framework or directly interact with the policy framework to make policy decision requests, etc., through network open function elements.

[0137] 10. NSSF: Main functions include: selecting a set of network slice instances for the UE, determining the allowed network slice selection assistance information (NSSAI), and determining the AMF set that can serve the UE.

[0138] 11. AUSF: Mainly includes the following functions: authentication server function, interacts with unified data management network elements to obtain user information, and performs authentication-related functions, such as generating intermediate keys.

[0139] 12. BSF: Implements session binding. Specifically, it is used for AF addressing PCF.

[0140] When the SMF requests policy control from the PCF for a session established for the UE, it provides the PCF with information such as the UE's identifier and user IP address. The PCF then registers the binding information (including but not limited to the UE's identifier, user IP address, and the identifier of the selected PCF) with the BSF. Subsequently, when the UE accesses services on the AF through this session, the AF may need to request policy authorization from the PCF for the services accessed by the UE. The PCF selected by the AF for this policy authorization must be consistent with the PCF selected by the SMF for this session, because this policy authorization generally triggers the PCF to adjust the policy control for the associated sessions of the SMF. The AF can query the corresponding PCF from the BSF based on the user IP address or the UE's identifier, and then directly request policy authorization from the AF through the N5 interface defined by 5G.

[0141] 13. UDR: Primarily used for storing and retrieving data types such as contract data, strategy data, and application data.

[0142] It is understood that the aforementioned network elements or functional network elements can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0143] 14. NEF: This can be understood as the naming of Open Capability Network Elements in the 5G architecture. Open Capability Network Elements mainly include the following functions: securely opening services and capabilities provided by 3GPP network functions, which can be internally opened or opened to third parties; converting or translating information interacting with AF and information interacting with internal network functions, such as AF service identifiers and internal 5G core network information such as data network name (DNN) and single network slice selection assistance information (S-NSSAI), etc.

[0144] from Figure 1 It can be seen from this that Figure 1 The interfaces between the various control plane network elements are service-oriented interfaces.

[0145] exist Figure 1 In the architecture shown, the interface names and functions between the various network elements are as follows: 1) N1: The interface between AMF and the terminal, which can be used to transmit QoS control rules to the terminal.

[0146] 2) N2: The interface between AMF and RAN, which can be used to transmit radio bearer control information from the core network side to the RAN.

[0147] 3) N3: The interface between RAN and UPF, mainly used to transmit uplink and downlink user plane data between RAN and UPF.

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

[0149] 5) N9: User plane interface between UPFs, used to transmit uplink and downlink user data streams between UPFs.

[0150] 6) The service-oriented interfaces Nnssf, Nudr, Nausf, Nbsf, Namf, Npcf, Nsmf, Nudm, Nnef, and Naf are the service-oriented interfaces provided by NSSF, UDR, AUSF, BSF, AMF, PCF, SMF, UDM, NEF, and AF, respectively, and are used to call the corresponding service-oriented operations.

[0151] 7) N6: The interface between UPF and DN, used to transmit uplink and downlink user data streams between UPF and DN.

[0152] N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers can be found in the definitions of the 3rd Generation Partnership Project (3GPP) standard protocol, and are not limited here.

[0153] It should be noted that the interfaces between various control plane network elements can also be point-to-point interfaces, which will not be elaborated here.

[0154] It should be understood that the network architecture applicable to the above embodiments of this application is merely an illustrative example, and the network architecture applicable to the embodiments of this application is not limited thereto. Any network architecture that includes the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0155] It should also be understood that Figure 1 The AMF, SMF, UPF, PCF, UDM, etc. shown can be understood as network elements used to implement different functions, such as network slices that can be combined as needed. These network elements can be independent devices or integrated into the same device to implement different functions. They can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., cloud platform). This application does not limit the specific form of the above network elements.

[0156] It should also be understood that the above naming is defined solely for the purpose of distinguishing different functions and should not constitute any limitation on this application. This application does not preclude the possibility of using other naming conventions in 5G networks and other future networks. For example, in 6G networks, some or all of the above-mentioned network elements may use the terminology from 5G, or may use other names, etc.

[0157] It should also be understood that Figure 1 The interface names between the various network elements are merely examples; in actual implementations, the interface names may differ, and this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0158] Currently, 5G networks (e.g., Figure 1 In the communication system shown, terminal devices can communicate point-to-point. However, the current method of point-to-point communication between terminal devices requires the implementation of ground anchor user plane network elements based on session anchoring. In some scenarios (such as when two terminal devices communicating point-to-point use the same satellite access network or the same satellite backhaul link), point-to-point data transmission through ground anchor user plane network elements may increase the latency of data transmission.

[0159] For example, if the terminal device is a terminal device within a 5G Virtual Network (5G VN) group, and the data between the terminal devices is forwarded via terrestrial PSA UPF, even if the two communicating terminal devices access the network through the same satellite constellation or achieve backhaul through the same satellite backhaul link, the data will still be forwarded based on terrestrial PSA UPF, which will result in a large latency.

[0160] This application provides a communication method that, based on information reported by the anchor point user plane network element of the session, determines a new network element to provide forwarding services for the session's data when the terminal devices of point-to-point communication use the same access network or the same backhaul network, thereby improving the performance of point-to-point data transmission.

[0161] It should be understood that the methods provided in the embodiments of this application can be applied to 5G communication systems, for example, Figure 1 The communication system shown is illustrated. However, the embodiments of this application do not limit the scenarios in which this method can be applied; for example, it is also applicable to other network architectures that include network elements capable of implementing the corresponding functions.

[0162] To facilitate understanding of the technical solutions of the embodiments of this application, before introducing the solutions of the embodiments of this application, some terms or concepts that may be involved in the embodiments of this application will be briefly described first.

[0163] 1. 5G VN.

[0164] Currently, 5G networks offer 5G VN services, also known as 5G Local Area Network (5GLAN) services. 5G VN services can be used for home communication, enterprise offices, factory manufacturing, vehicle-to-everything (V2X) communication, and power grid upgrades. 5G VN services can provide private communication via Internet Protocol (IP) or non-IP methods (such as Ethernet) for two or more terminal devices within a group of devices.

[0165] For example, equipment in a factory can form a 5G VN group, allowing different devices to send Ethernet data packets to each other; similarly, employees' office equipment (such as mobile phones, computers, or laptops) in a department of an enterprise can form a 5G VN group, enabling different office devices to send IP data packets to each other. If two terminal devices are not in the same 5G VN group, they cannot communicate with each other.

[0166] 2. 5G VN communication data forwarding method.

[0167] There are three data forwarding methods in the user plane of 5G VN communication: 1) N6-based forwarding: Uplink data of 5G VN communication is forwarded to DN via PSA UPF, or downlink data from DN is received by PSA UPF.

[0168] 2) N19-based forwarding: Uplink and downlink data in 5G VN communication are forwarded between different PSA UPFs via N19. N19 can be understood as a user plane tunnel connecting different PSA UPFs within a 5G VN group. The implementation of N19-based forwarding can be that the SMF establishes N19 between different PSA UPFs.

[0169] For ease of understanding, combined with Figure 2 Explain how 5G VN communication user plane data is forwarded based on N19. Figure 2 This is a schematic diagram of 5G VN communication user plane data forwarding based on N19 provided in an embodiment of this application.

[0170] from Figure 2 As can be seen, different devices (such as...) in a 5G VN group Figure 2 UE#1 and UE#2 shown can send data packets to each other. The specific data packet transmission process includes: Data packet #1 of UE#1 is forwarded to the corresponding PSA UPF#1 through the access RAN#1. The transmission between UE#1 and RAN#1 is over the air interface, and the transmission between RAN#1 and PSA UPF#1 is through the N3 interface.

[0171] Optionally, when UE#1 cannot directly access PSA UPF#1 (e.g., due to network deployment limitations or geographical restrictions), it needs to be bridged to I-UPF (e.g., Figure 2 The I-UPF#1 shown in the figure is then forwarded to PSA UPF#1.

[0172] Data packet #2 of UE#2 is forwarded to the corresponding PSA UPF#2 through the access RAN#2. The transmission between UE#2 and RAN#2 is over the air interface, and the transmission between RAN#2 and PSA UPF#2 is through the N3 interface.

[0173] Optionally, when UE#2 cannot directly access PSA UPF#2 (e.g., due to network deployment limitations or geographical restrictions), it needs to be bridged to I-UPF (e.g., Figure 2 The I-UPF#2 shown in the figure is then forwarded to PSA UPF#2.

[0174] In the case where data packet #1 of UE#1 is transmitted to PSA UPF#1 and data packet #2 of UE#2 is transmitted to PSA UPF#2, PSA UPF#1 and PSA UPF#2 communicate via N19. For example, PSA UPF#1 transmits data packet #1 to PSA UPF#2 via the N19 interface, and PSA UPF#2 transmits data packet #2 to PSA UPF#1 via the N19 interface.

[0175] After receiving data packet #2, PSA UPF#1 can transmit data packet #2 to UE#1. After receiving data packet #1, PSA UPF#2 can transmit data packet #1 to UE#2, thus realizing data packet transmission between UE#1 and UE#2.

[0176] 3) Local forwarding: Different PDU sessions in a 5G VN group are anchored on the same PSA UPF, and the data of the PDU session (or the data carried by the PDU session) is locally forwarded on this PSA UPF. Specifically, in order to achieve local forwarding, the SMF can anchor as many PDU sessions as possible within the 5G VN group on the same PSA UPF.

[0177] For ease of understanding, combined with Figure 3 Explain how 5G VN communication user plane data is forwarded locally. Figure 3 This is a schematic diagram of local forwarding of 5G VN communication user plane data provided in an embodiment of this application.

[0178] from Figure 3 As can be seen, different devices (such as...) in a 5G VN group Figure 3UE#1 and UE#2 shown can send data packets to each other. The specific data packet transmission process includes: Data packet #1 of UE#1 is forwarded to the corresponding PSA UPF#1 through the access RAN#1. The transmission between UE#1 and RAN#1 is over the air interface, and the transmission between RAN#1 and PSA UPF#1 is through the N3 interface.

[0179] Optionally, when UE#1 cannot directly access PSA UPF#1 (e.g., due to network deployment limitations or geographical restrictions), it needs to be bridged to I-UPF (e.g., Figure 3 The I-UPF#1 shown in the figure is then forwarded to PSA UPF#1.

[0180] Data packet #2 of UE#2 is forwarded to the corresponding PSA UPF#1 through the access RAN#2. The transmission between UE#2 and RAN#2 is over the air interface, while the transmission between RAN#2 and PSA UPF#1 is through the N3 interface.

[0181] Optionally, when UE#2 cannot directly access PSA UPF#1 (e.g., due to network deployment limitations or geographical restrictions), it needs to be bridged to I-UPF (e.g., Figure 2 The I-UPF#2 shown in the figure is then forwarded to PSA UPF#1.

[0182] When data packet #1 of UE#1 is transmitted to PSA UPF#1 and data packet #2 of UE#2 is transmitted to PSA UPF#1, PSA UPF#1 can transmit data packet #2 to UE#1 and data packet #1 to UE#2, thus realizing data packet transmission between UE#1 and UE#2.

[0183] 3. Packet Detection Rule (PDR) and Forwarding Action Rule (FAR) configuration.

[0184] For each UE (or member) within the 5G VN group, the SMF configures the following PDR and FAR (or N4 rules) for the session-anchored PSA UPF to enable the processing of packets initiated by that UE: 1) To detect data, set the PDR source interface to "access side" and set the CN tunnel information to the PDU session tunnel header (e.g., N3 or N9 GTP-U F-TEID). 2) In order to forward data, set the destination interface of FAR to "5G VN internal".

[0185] For each UE within the 5G VN group, the SMF configures the following N4 rule for the session-anchored PSA UPF to enable processing of packets sent to that UE: 1) To detect data, set the PDR source interface to "5G VN internal" and set the destination address to the IP / MAC address of the 5G VN group member; 2) In order to forward data, the FAR must include an external header construction identifier that indicates N3 / N9 tunnel information, and the destination interface must be set to "access side".

[0186] If forwarding is based on N19, the SMF needs to configure the following N4 rules for the PSA UPF anchored to the session to process packets received on each N19 tunnel: 1) To detect data, set the PDR source interface to "core side" and the CN tunnel information to N19 tunnel head (i.e., N19 GTP-U F-TEID). 2) In order to forward data, the destination interface in FAR needs to be set to "5G VN internal".

[0187] If forwarding is based on N19, the SMF needs to configure the following N4 rules for the PSA UPF anchored to the session in order to process data sent to sessions within the group anchored to other PSA UPFs: 1) To detect data, set the PDR source interface to "5G VN internal" and set the target address to the IP / MAC address of the UE anchored to the UPF at the other end of the N19 tunnel; 2) In order to forward data to 5G VN group members anchored to other UPFs via the N19 tunnel, it is necessary to set the external header construction identifier of FAR containing N19 tunnel information, and at the same time, set the destination interface to "core side".

[0188] SMF configures the following N4 rule for the PSA UPF anchored to the session to process packets sent by group members through the N6 connection: 1) To detect data, set the PDR source interface to "core side" and the source address to the IP / MAC address of the group member; 2) In order to forward data, set the destination interface of FAR to "5G VN internal".

[0189] SMF configures the following N4 rules for the PSA UPF anchored to the session to process packets destined for group members or devices within the DN: 1) To detect data, set the PDR source interface to "5G VN internal" and set the destination address to the IP / MAC address of the 5G VN group member; 2) In order to forward data, the destination interface is set to "core side" in FAR.

[0190] When the PSA UPF anchored to a UE changes but the UE's address remains unchanged, the SMF should update the N4 rules configured for that UE so that packets destined for that UE can be forwarded correctly.

[0191] 4. Satellite communication and 5G integration technology.

[0192] Currently, the integration of satellite communication and 5GS can be divided into two scenarios. The first scenario is that the satellite is used as a 3GPP access point, and the UE accesses 5GS through the satellite. The second scenario is that the satellite link is used as a backhaul link, and the RAN communicates with the 5G core network (5G core, 5GC) through the backhaul link (e.g., the backhaul link provides bearer for N3 or N9).

[0193] When using satellites for 3GPP access, they can be considered as radio frequency modules of the RAN, providing transparent forwarding capabilities; while during satellite backhaul, the satellite only acts as a bearer node, and its data is transparent to the UE.

[0194] Alternatively, satellite-supported data processing could be considered, that is, satellites could provide non-transparent forwarding capabilities or regenerative capabilities, specifically by deploying RAN and UPF on satellites.

[0195] Regarding the concept of satellite regeneration capabilities, two scenarios are considered. The first scenario is: the satellite is equipped with an onboard RAN and an onboard UPF, and the UE accesses the 5GC network through the onboard RAN and onboard UPF. For example... Figure 4 As shown, Figure 4 This is a schematic diagram illustrating a satellite access provision provided in an embodiment of this application.

[0196] The second scenario is: RAN is deployed on the ground, and onboard UPF is deployed on the satellite, with the satellite link serving as the backhaul. Figure 5 As shown, Figure 5 This is a schematic diagram of a satellite providing backhaul according to an embodiment of this application.

[0197] In both of the above scenarios, UPFs are deployed on the satellites, and the satellites may be networked through inter-satellite links.

[0198] 5. Satellite constellation.

[0199] A satellite constellation is a collection of satellites launched into orbit and capable of normal operation. It is usually a satellite network composed of satellites configured in a certain way. Major communication satellite constellations include the Iridium system, the European Data Relay System (EDRS), Tianlian-1, Starlink, and OneWeb, as well as navigation-related constellations such as the Global Position System (GPS), GLONASS, Galileo, and BeiDou.

[0200] The main constellation types involved in this application include: Low Earth Orbit (LEO) satellite constellations, Medium Earth Orbit (MEO) satellite constellations, LEO inclined orbit constellations, and MEO inclined orbit constellations, etc.

[0201] LEO (Leo-Orbital) and MEO (Medium-Orbital) tilted constellations do not involve the concept of a reverse seam. This means that when a constellation is classified as a LEO or MEO tilted constellation, there is no need to consider whether it supports a reverse seam. LEO (Leo-Orbital) and MEO (Medium-Orbital) polar constellations do involve the concept of a reverse seam. This means that when a constellation is classified as a LEO or MEO polar constellation, it is necessary to consider whether it supports a reverse seam.

[0202] 6. Satellite networking.

[0203] Satellite networking refers to a network model based on satellite technology. In this model, the network consists of multiple types of satellite systems in different orbits, using a satellite constellation as the basic physical framework. It fully leverages the wide coverage and multi-level, full-spectrum acquisition of multi-source target information by satellite systems, providing users with highly reliable information that incorporates precise time and space references and multi-element fusion processing. The development of terrestrial computer networks has enabled spacecraft to join the network as servers, terminals, nodes, or transmission lines, which can be considered the technological foundation for proposing the concept of satellite networking.

[0204] 7. Satellite type.

[0205] Different types of satellites may have different coverage areas, motion characteristics, and the resulting propagation delays and jitter due to their different orbital altitudes.

[0206] For example, satellites can be classified by orbit type into geostationary equatorial orbital (GEO), MEO, LEO, and other satellites (Other SAT).

[0207] 8. Polar orbits.

[0208] An artificial Earth satellite orbit with its orbital plane at a 90° angle to the equatorial plane. This type of orbit allows the satellite to reach the skies above the North and South Poles, meaning it can fly over the entire globe. Meteorological satellites, navigation satellites, and Earth resource satellites, which require global observation and application, all use this type of orbit.

[0209] 9. Reverse seam.

[0210] When satellites are in orbit, their direction of motion is mostly the same as that of satellites in adjacent orbits. Sometimes, however, two special orbits exist, adjacent to each other, but the satellites orbiting on these orbits move in opposite directions. Viewed from the South Pole, the satellite on the left orbit moves from south to north, while the satellite on the right orbit moves from north to south. Because of this phenomenon, the region between these two orbits is called the anti-gap.

[0211] 10. Inter-satellite links.

[0212] Non-geostationary satellites such as MEO and LEO often require multiple satellites to form a constellation to achieve continuous coverage of fixed areas such as the ground or sea, and use inter-satellite links for on-board relay, thus eliminating the need to build ground base stations around the world and enhancing coverage capabilities.

[0213] Inter-satellite links are divided into two categories: links between satellites in the same orbit, called intra-orbit inter-satellite links, and links between different orbits, called inter-satellite links. Inter-orbit inter-satellite links are further divided into in-orbit inter-links and out-of-orbit links. In-orbit inter-links are links between two adjacent satellites orbiting in the same direction. In-orbit inter-links may break down near the polar regions due to changes in the relative positions of the satellites. Out-of-orbit links are links between two satellites orbiting in opposite directions. Because the satellites orbit in opposite directions, out-of-orbit links are difficult to establish or can only be established for a short time.

[0214] For ease of understanding, combined with Figure 6 The inter-satellite links will be explained. Figure 6 It is a two-dimensional unfolded diagram of a polar orbit constellation, with each orbit having a fixed tilt angle of 90 degrees (the satellite orbits pass over the polar regions).

[0215] 11. Satellite operation and control information.

[0216] The topology of a non-geostationary satellite constellation (e.g., the connectivity between satellites) changes with satellite movement. As satellites move, ground terminals (e.g., in access scenarios where the ground terminal is a UE, and in backhaul scenarios where the ground terminal is a regular satellite terminal serving a base station) need to switch their access to different satellites. Because satellite operation is predictable, the positions and adjacency relationships of satellites at different times can be predicted. Therefore, the topology changes of the satellite constellation and the coverage area of ​​each satellite are also predictable. In this application, the predictable information related to satellites can be referred to as satellite operation information, constellation operation information, or satellite operation and control information. For ease of description, this application uses "satellite operation and control information" to refer to the predictable information related to satellites.

[0217] The satellite operation and control information involved in this application includes, but is not limited to, one or more types of information such as ephemeris information for each satellite, position information of each satellite at the current moment calculated based on ephemeris information, and stable constellation topology information (also known as satellite snapshot information) within each periodic time segment. Among them, the satellite ephemeris information includes orbital parameters, or parameters such as the satellite's azimuth calculated based on orbital parameters. It can be understood that the satellite ephemeris information can be used to calculate, predict, depict, or describe the time, position, velocity, and other states of satellite flight.

[0218] 12. Protocol Data Unit (PDU) Session.

[0219] A PDU session is an association between a terminal device and a DN, used to provide a PDU connection service. Each PDU session can establish (or configure) one or more Quality of Service (QoS) flows that carry service data streams. In this application, the service data streams carried by the QoS flows in a PDU session are referred to as the data of the PDU session.

[0220] 13. Data between terminal devices is transmitted in a point-to-point manner.

[0221] When two UEs communicate directly using each other's IP addresses, there are two communication modes: one is when there is a peer-to-peer application on the UE, and the UEs need to directly transmit user plane data based on each other's IP addresses; the other is when the UEs belong to the same 5G VN group and the UEs communicate with each other using 5G VN.

[0222] In the first scenario: the PSA UPF forwards data destined for the target UE to the DN via N6, and then the DN routes the data packets to the PSA UPF corresponding to the target UE. In this case, the UE typically establishes a connection with the device / application in the DN (e.g., a point-to-point application server), and with the help of the device / application in the DN, obtains the IP address of the other UE. Therefore, UEs can directly initiate data communication using the other end's IP address as the destination address of the data packets. Since the DN is usually deployed on the ground, even if the UE uses the same satellite for 3GPP access or backhaul, the data communication between UEs still needs to pass through the ground-based PSA UPF and DN, resulting in a relatively large round-trip delay for communication between UEs.

[0223] For the second scenario: Based on the 5G VN communication described above, UEs need to be assigned to the same 5G VN group. Communication data between UEs is forwarded locally or via N19 based on the anchor point UPF (e.g., PSA UPF). The data is delivered to the target UE by the same PSA UPF or another PSA UPF. Currently, the PSA UPF is a ground-based PSA UPF. Even if two UEs using point-to-point communication use the same satellite as the 3GPP access or backhaul link, the data between UEs still needs to pass through the ground PSA UPF, resulting in a relatively large round-trip delay for communication between UEs.

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

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

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

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

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

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

[0230] Fifth, the term "and / or" in this article is merely a description of 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. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

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

[0232] Without loss of generality, the communication method provided in the embodiments of this application will be described in detail below using the interaction between network elements as an example.

[0233] For ease of description, the following explanation uses the following example: Session Management Function (SMF) network element, UE terminal equipment, RAN access network equipment, UDM unified data management network element, AMF access and mobility management function network element, UPF user plane function network element, PSA UPF anchor UPF, I-UPF intermediate UPF, and DN data network.

[0234] It should be noted that this application does not impose any restrictions on the names of network devices.

[0235] For example, the access and mobility management function network element can be an AMF, or other network elements capable of implementing access and mobility management functions.

[0236] For example, the network element for session management functions can be an SMF, or other network elements capable of implementing session management functions.

[0237] For example, the user plane function network element can be a UPF, or other network elements that can implement user plane functions.

[0238] For example, the unified data management network element can be a UDM, or other network elements that can perform data management functions.

[0239] For example, the anchor UPF can be a PSA UPF, or other network elements that can implement anchor sessions.

[0240] For example, the intermediate UPF can be an I-UPF, or another UPF between a RAN and a PSA UPF, such as a UL CLUPF.

[0241] As mentioned above, current point-to-point data transmission between UEs, when both UEs use the same satellite for 3GPP access or backhaul, still requires data to pass through the ground-based PSA UPF, resulting in relatively high round-trip latency. To address this latency issue, this application proposes a communication method that uses the onboard UPF (e.g., onboard PSA UPF or I-UPF) as a PSA UPF or an extended I-UPF to support local forwarding, N19 forwarding, and other functions. Data forwarding rules are configured directly for the onboard UPF during session establishment to enable it to provide data forwarding services. Alternatively, another communication method is provided: the SMF detects and reports communication based on the onboard UPF before issuing data forwarding rules. However, both of these methods may consume limited satellite resources. For example, configuring data forwarding rules during session establishment consumes satellite resources if no subsequent data forwarding occurs. Furthermore, detection and reporting based on the onboard UPF may increase its resource consumption.

[0242] To reduce satellite resource consumption, this application provides an alternative communication method. This method involves detecting and reporting communication via a ground-based UPF, then enabling the onboard UPF to forward data. This reduces round-trip latency between UEs and avoids unnecessary data forwarding configuration for the onboard UPF and / or prevents the onboard UPF from performing detection and reporting. The communication method will be described in detail below with reference to the accompanying drawings.

[0243] Figure 7 This is a schematic flowchart illustrating a communication method provided in this application. It includes the following steps: S710, the first PSA UPF sends the first information to the SMF, or in other words, the SMF receives the first information from the first PSA UPF.

[0244] The first PSA UPF is the PSA UPF anchored to the first session (e.g., the first PDU session) established by the first UE. For example, the first PSA UPF can be the terrestrial PSA UPF that is defaulted to during the establishment of the first session. For instance, during the establishment of the first session, the SMF can determine this first PSA UPF as the PSA UPF anchored to the first session, so that the first PSA UPF is responsible for transmitting the data of the first session between the core network and the data network. The following will combine... Figure 8 The details of how SMF determines the PSA UPF anchored for the session during the session establishment process will not be elaborated here.

[0245] It should be noted that this embodiment uses the first PSA UPF anchored to the first session of the first UE as an example to introduce the signaling interaction between the first PSA UPF and the SMF. The signaling interaction between the PSA UPF and the SMF anchored to the sessions of other UEs is similar to the signaling interaction between the first PSA UPF and the SMF, and will not be repeated in this embodiment.

[0246] The first information is used by the SMF to determine whether the two terminal devices in point-to-point communication (e.g., the first terminal device and the second terminal device) use the same access network or the same backhaul network. If the two terminal devices in point-to-point communication use the same access network or the same backhaul network, the SMF determines a new network element (e.g., the first network element) to provide forwarding services for the session's data. In other words, after receiving the first information, the SMF can determine a first network element to provide forwarding services for the data of the first session, and the first PSA UPF anchored to the first session may no longer provide forwarding services for the data of the first session.

[0247] In this embodiment, the SMF can determine the first network element to provide forwarding services for the data of the first session based on the first information reported by the first PSA UPF, in order to avoid point-to-point data transmission only based on the first PSA UPF and improve the performance of point-to-point data transmission.

[0248] Specifically, the first information mentioned above includes the source address of the first data and / or the destination address of the first data, wherein the first data is data from the first UE, or the first data is data sent to the first UE.

[0249] For example, the first data is the data transmitted between the first UE and the second UE, and the first data includes the data of the first session sent by the first UE to the second UE and / or the data sent by the second UE to the first UE.

[0250] For example, the first data is data from a first session sent by a first UE to a second UE. The source address of the first data is the address of the first UE, and the destination address of the first data is the address of the second UE. Exemplarily, the source address of the first data includes, but is not limited to, the IP address or MAC address of the first UE, and the destination address of the first data is not limited to, the IP address or MAC address of the second UE.

[0251] For example, the first data is data sent from the second UE to the first UE, where the source address of the first data is the address of the second UE, and the destination address of the first data is the address of the first UE. Exemplarily, the source address of the first data includes, but is not limited to, the IP address or MAC address of the second UE, and the destination address of the first data is not limited to, the IP address or MAC address of the first UE.

[0252] As one possible implementation, the first UE and the second UE are two different terminal devices in a local area network group; for example, the first UE and the second UE are two UEs within a certain 5G VN group. In this implementation, the first information may optionally include at least one of the following: The network instance information includes the identifier of the local area network group to which the first UE belongs, the network instance information used by the first anchor user plane network element to receive the first data, or the network instance information used by the first anchor user plane network element to send the first data. The network instance information indicates a specific network instance. Specifically, a network instance is defined to isolate different IP domains, such as isolating access networks connected to different IP domains by the UPF, isolating UE IP addresses allocated by multiple data networks, or isolating transport networks within the same PLMN. For example, when the SMF issues PDR and FAR to the UPF, it may also provide network instance information so that when the UPF receives or sends a data packet, it can determine the network instance from which the data packet originates or is destined for based on the network instance information.

[0253] In this embodiment, the first UE and the second UE are the two ends of point-to-point communication. Point-to-point communication can also be understood as: (on-board or local) 5G VN group communication, (on-board or local) forwarding, (on-board or local) data forwarding, (on-board or local) loopback, (on-board or local) routing, etc. For ease of description, it will be referred to as point-to-point communication below.

[0254] Specifically, the aforementioned "on-board" refers to point-to-point communication implemented on onboard network elements, including but not limited to: In scenarios where networks are accessed via satellite constellations (e.g., Figure 4 In the scenario shown, where the onboard UPF performs local data forwarding or N19 forwarding, and the satellite backhaul link serves as the backhaul link (e.g., Figure 5 In the scenario shown, data is forwarded locally or via N19 by the onboard UPF.

[0255] Optionally, the first PSA UPF may send first information to the SMF based on the SMF's instruction. Figure 7 The method flow shown also includes: S720, the SMF sends the first instruction information to the first PSA UPF, or in other words, the first PSA UPF receives the first instruction information from the SMF.

[0256] Specifically, the first indication information is used to instruct the first PSA UPF to report first information when a first condition is met. The first condition includes receiving data from the first terminal device sent to other terminal devices and / or receiving data from other terminal devices sent to the first terminal device, wherein other terminal devices can be understood as terminal devices other than the first terminal device.

[0257] In other words, in this embodiment, the first PSA UPF can report the aforementioned first information based on the instructions of the SMF, rather than deciding to report the first information on its own, so as to clarify the timing of reporting the first information.

[0258] For example, receiving data from the first UE could mean receiving data sent by the first UE to the second UE; receiving data sent to the first UE could mean receiving data sent by the second UE to the first UE, which can be understood as a point-to-point communication requirement between the first UE and the second UE; or, For example, receiving data from the first UE and / or receiving data sent to the first UE can be understood as the first UE having a data transmission requirement, wherein data transmission can be sending data and / or receiving data.

[0259] If the first condition is met, the first PSA UPF sends the first message to the SMF.

[0260] For example, the first PSA UPF determines whether the first UE has a data transmission requirement, which may be based on the PDR configured locally by the first PSA UPF (e.g., the destination address indicated by the PDR is successfully matched).

[0261] As one possible implementation, the first instruction information can be a Usage Reporting Rule (URR), or other information that instructs the first PSA UPF to report the first information.

[0262] It should be understood that the above-mentioned first PSA UPF reporting the first information based on the SMF instruction is only an example and does not constitute any limitation on the scope of protection of this application. In this embodiment, the first PSA UPF may also actively report the first information, or may determine whether to report the first information based on the pre-configured first conditions.

[0263] Optionally, the SMF sending the first indication information to the first PSA UPF may be based on certain information determining that it needs to send the first indication information to the first PSA UPF. Figure 7 The method flow shown also includes: S730, SMF determines to send first instruction information based on second information.

[0264] Specifically, the second information includes at least one of the following: The access type RAT information corresponding to the first session, the backhaul link type information corresponding to the first session, or the location information of the first UE.

[0265] For example, if the RAT information indicates that the access type is satellite access, and the SMF infers from the UE's location information (such as the cell global identifier) ​​that the satellite or constellation corresponding to the onboard access network device accessed by the UE also has an onboard UPF deployed, then the SMF decides to send the first indication information. The information regarding whether the onboard access network device and its corresponding satellite or constellation have an onboard UPF deployed can be pre-configured within the SMF, or it can be obtained by the SMF from the NRF.

[0266] For example, if the backhaul link type information indicates that the backhaul link is satellite backhaul, and the SMF infers from the UE's location information (such as the cell global identifier) ​​that the satellite or constellation used by the satellite backhaul link accessed by the UE also has an onboard UPF deployed, then the SMF decides to issue the first indication information. The information regarding whether the satellite backhaul link and the corresponding satellite or constellation have an onboard UPF deployed can be pre-configured within the SMF, or it can be obtained by the SMF from the NRF.

[0267] For example, in the case where the first UE accesses the core network via satellite (e.g., Figure 4 (As shown in the scenario), the RAT information corresponding to the first session can be the satellite access type information corresponding to the first session.

[0268] For example, in the case where the backhaul link of the first UE is a satellite backhaul link (e.g., Figure 5(As shown in the scenario) The type information of the backhaul link corresponding to the first session can be the type information of the satellite backhaul link corresponding to the first session. For example, the location information of the first UE may be the user location information (ULI) of the first UE.

[0269] Specifically, after the SMF receives the aforementioned first information, Figure 7 The method flow shown also includes: S740, SMF determines whether the first UE and the second UE use the same access network or the same backhaul network based on the first information.

[0270] In this embodiment, the SMF can determine whether two UEs (e.g., the first UE and the second UE) communicating in point-to-point use the same access network or the same backhaul network based on the first information received from the first PSA UPF.

[0271] For example, the access network includes the satellite or satellite constellation where the access network equipment is located; the backhaul network includes the satellite, backhaul link, and satellite constellation in the backhaul link.

[0272] Alternatively, the first UE and the second UE may use the same access network equipment, which may be located on a satellite or on a satellite constellation.

[0273] Alternatively, the first UE and the second UE can use the same backhaul network, which means that the first UE and the second UE can use the same satellite backhaul link.

[0274] For example, the first information includes the source address of the first data and / or the destination address of the first data. Specifically, the SMF locally stores the context of the current session (such as the first session) containing the address of the first UE. When the first data is data sent from the first UE to the second UE, the first information may only contain the destination address of the first data; when the first data is a data packet sent from the second UE to the first UE, the first information may only contain the source address of the first data.

[0275] Specifically, the SMF or the first PSA UPF can pre-divide an IP address pool. When the UE uses satellite (or constellation) access or a satellite backhaul link, it assigns an IP address from the corresponding address pool to the UE. Therefore, when the addresses of the first UE and the second UE are addresses assigned by the SMF or the first PSA UPF, the SMF can determine whether the first UE and the second UE use the same access network or the same backhaul network based on the source address and / or destination address of the first data. For example, the SMF can obtain other information about the first UE from the context of the first session, such as location information and RAT information. The SMF can obtain the session context of the second UE based on the address information of the second UE. The principle by which the SMF can determine whether the first UE and the second UE use the same access network or the same backhaul network based on the source address and / or destination address of the first data is similar in the following examples and will not be elaborated further.

[0276] Optionally, the SMF determines whether the first UE and the second UE use the same access network or the same backhaul network based on the first information, including but not limited to the following possible methods: Method 1: The aforementioned first information includes the address of the second UE. Specifically, including the address of the second UE in the first information can be understood as either the source address of the first data or the destination address of the first data being the address of the second UE.

[0277] For example, the source address of the first data is the address of the first UE, and the destination address of the first data is the address of the second UE; or, the source address of the first data is the address of the second UE, and the destination address of the first data is the address of the first UE.

[0278] In this implementation, the SMF queries the session context of the second UE based on the address of the second UE to obtain the location information of the second UE. In this implementation, the first information received by the SMF corresponds to the session of the first UE. The SMF can directly query the session context and location information of the first UE without needing to query the session context based on the address of the first UE.

[0279] Specifically, in this implementation, the SMF determines whether the first UE and the second UE use the same access network or the same backhaul network based on the first information, including: The SMF obtains the location information of the first UE based on the session context of the first UE; the SMF obtains the location information of the second UE based on the address of the second UE; the SMF determines whether the first UE and the second UE use the same access network or the same backhaul network based on the location information of the first UE and the location information of the second UE.

[0280] For example, when a first UE sends data to a second UE, the SMF determines the second UE based on the destination address of the first data, and further determines the location information of the second UE and the first UE. Based on the location information, the SMF determines any one of the following: The first UE and the second UE use the same satellite access (e.g., the cell global identifier in the location information of the first UE and the second UE represents the same satellite base station), the first UE and the second UE use the same satellite constellation access (e.g., the cell global identifier in the location information of the first UE and the second UE represents different base stations belonging to the same satellite constellation), the first UE and the second UE use the same satellite backhaul link (e.g., the cell global identifier in the location information of the first UE and the second UE represents the same or different base stations using the same satellite backhaul link), or the first UE and the second UE use the same satellite constellation backhaul network (e.g., the cell global identifier in the location information of the first UE and the second UE represents the same or different base stations using the same satellite constellation backhaul network).

[0281] For example, the location information of the first UE includes the ULI of the first UE. The location information of the second UE includes the ULI of the second UE.

[0282] Optionally, there can be two SMFs: SMF#1 serves the first UE, and SMF#2 serves the second UE. The aforementioned SMF querying the session context of the second terminal device based on the second UE's address could be as follows: SMF#1 uses the second UE's address to query the UDM for the second UE's location information.

[0283] Optionally, the SMF can be a single entity. In the case where both the first UE and the second UE are served by the same SMF, the SMF obtains the ULI of the first UE from the session context of the first UE based on the first data corresponding to the first session, and then obtains the ULI of the second UE from the session context of the second UE based on the address (such as the IP address) of the second UE. The SMF then compares the ULI of UE1 with the ULI of the second UE. If they are the same, it determines whether the first UE and the second UE use the same access network or the same backhaul network.

[0284] Method 2: The aforementioned first information includes the address of the second UE. In this implementation, the SMF queries the session context of the second UE based on the address of the second UE to obtain the second data network access identifier (DNAI) corresponding to the session of the second UE. Furthermore, in this implementation, the first information received by the SMF corresponds to the session of the first UE, and the SMF can directly query the first data network access identifier corresponding to the session of the first UE in the session context of the first UE. The SMF does not need to query the session context of the first UE based on the address of the first UE.

[0285] Specifically, in this implementation, the SMF determines whether the first UE and the second UE use the same access network or the same backhaul network based on the first information, including: SMF determines the second data network access identifier corresponding to the session of the second UE based on the address of the second UE; Based on the first data network access identifier (DN) and the second data network access identifier (DN) corresponding to the first session, the SMF determines whether the first UE and the second UE use the same access network or the same backhaul network. The data network access identifier can identify the data network DN of the user plane access application (or service). If the DN is located on a satellite, the DNAI can be understood as having a corresponding relationship with the satellite (both one-to-one and many-to-one relationships are within the scope of protection of this application).

[0286] It should be noted that although this application relates to point-to-point communication between UEs, there may also be scenarios where the first UE and the second UE access services on the satellite at the same time. In this case, the SMF can check the first data network access identifier and the second data network access identifier to determine whether the first UE and the second UE are using the same access network or the same backhaul network.

[0287] Optionally, if the first data network access identifier (DNI) of the first UE is the first DNAI and the second data network access identifier (DNI) of the second UE is the second DNAI, the SMF can determine whether the first UE and the second UE use the same access network or the same backhaul network based on whether the first DNAI and the second DNAI are the same. For example, if the first DNAI and the second DNAI are the same, the SMF determines that the first UE and the second UE use the same access network or the same backhaul network; for instance, one GEO satellite corresponds to one fixed DNAI, or one constellation corresponds to one DNAI.

[0288] For example, when a first UE sends data to a second UE, the SMF determines the second UE based on the destination address of the first data, and further determines the second DNAI of the second UE and the first DNAI of the first UE. Based on the first DNAI and the second DNAI, the SMF determines any one of the following: The first UE and the second UE use the same satellite access (e.g., the first DNAI and the second DNAI represent the use of the same satellite), the first UE and the second UE use the same satellite constellation access (e.g., the first DNAI and the second DNAI represent different satellites belonging to the same satellite constellation), the first UE and the second UE use the same satellite backhaul link (e.g., the first DNAI and the second DNAI represent the use of the same satellite), or the first UE and the second UE use the same satellite constellation backhaul network (e.g., the first DNAI and the second DNAI represent the use of the same satellite constellation backhaul network).

[0289] Optionally, there can be two SMFs, namely SMF#1 serving the first UE and SMF#2 serving the second UE. In this case, the SMF can query the session context of the second terminal device based on the address of the second UE by: SMF#1 using the address of the second UE to query the DNAI corresponding to the session of the second UE from the UDM.

[0290] Optionally, the SMF can be a single entity. In the case where both the first UE and the second UE are served by the same SMF, the SMF obtains the DNAI of the first session from the session context of the first UE based on the first data corresponding to the first session, and then obtains the DNAI of the second UE from the session context of the second UE based on the address (such as the IP address) of the second UE. The SMF then compares the DNAI of UE1 with the DNAI of the second UE. If they are the same, it determines whether the first UE and the second UE use the same access network or the same backhaul network.

[0291] Method 3: The aforementioned first information includes the address of the second UE. In this implementation, the SMF queries the session context of the second UE based on the address of the second UE. Furthermore, in this implementation, the first information received by the SMF corresponds to the session of the first UE, and the SMF can directly query the session context of the first UE without needing to query the session context of the first UE based on its address.

[0292] Specifically, in this implementation, the SMF determines whether the first UE and the second UE use the same access network or the same backhaul network based on the first information, including: SMF determines the session context of the second UE based on the address of the second UE; Based on the session context of the first UE and the session context of the second UE, the SMF determines whether the first UE and the second UE are using the same access network or the same backhaul network.

[0293] For example, the session context of the first UE includes N3 tunnel information #1 or N9 tunnel information #1, etc. The session context of the second UE includes N3 tunnel information #2 or N9 tunnel information #2, etc.

[0294] Optionally, if the session context of the first UE is N3 tunnel information #1 and the session context of the second UE is N3 tunnel information #2, the SMF can determine whether the first UE and the second UE use the same access network or the same backhaul network based on whether N3 tunnel information #1 and N3 tunnel information #2 are the same. For example, if the IP addresses of N3 tunnel information #1 and N3 tunnel information #2 are the same, it indicates that they use the same RAN for backhaul from the same satellite (or satellite constellation); if the addresses of N3 tunnel information #1 and N3 tunnel information #2 are different, it may indicate that they use different RANs for backhaul from the same satellite (or satellite constellation).

[0295] Optionally, if the session context of the first UE is N9 tunnel information #1 and the session context of the second UE is N9 tunnel information #2, the SMF can determine whether the first UE and the second UE use the same access network or the same backhaul network based on whether N9 tunnel information #1 and N9 tunnel information #2 are the same. For example, if an on-board I-UPF has already been inserted, it can also be determined whether the same satellite or (or satellite constellation) is used based on the CN N9 tunnel information of the I-UPF.

[0296] For example, when a first UE sends data to a second UE, the SMF determines the second UE based on the destination address of the first data, and further determines the session context between the second UE and the first UE. The SMF determines any one of the following based on the session context: The first UE and the second UE use the same satellite access (e.g., the N3 tunnel information in the session context of the first UE and the second UE represents the same satellite base station), the first UE and the second UE use the same satellite constellation access (e.g., the N3 tunnel information in the session context of the first UE and the second UE represents different base stations belonging to the same satellite constellation), the first UE and the second UE use the same satellite backhaul link (e.g., the N3 tunnel information in the session context of the first UE and the second UE represents the same or different base stations using the same satellite backhaul link, or the N9 tunnel information represents that the first UE and the second UE have been inserted with the same I-UPF), or the first UE and the second UE use the same satellite constellation backhaul network (e.g., the N3 tunnel information in the session context of the first UE and the second UE represents the same or different base stations using the same satellite constellation backhaul network, or the N9 tunnel information represents that the first UE and the second UE have been inserted with different I-UPFs using the same satellite constellation backhaul network).

[0297] The SMF determines whether the first UE and the second UE use the same access network or the same backhaul network based on the first information, including: When the first terminal device and the second terminal device do not use the same access network and the same backhaul network, the SMF does not need to determine the first network element used to forward the data of the first session, that is, whether it is the network element that provides forwarding service for the data of the first session or the first anchor user plane network element.

[0298] When the first UE and the second UE use the same access network or the same backhaul network, the SMF needs to insert a first network element to provide forwarding services for the data of the first session. Figure 7 The method flow shown also includes: In the S750, the SMF determines the first network element used to forward data for the first session.

[0299] As one possible implementation, the first network element is a second anchor user plane network element. This second anchor user plane network element is a user plane network element other than the first anchor user plane network element that the first session is anchored to.

[0300] In this implementation, determining the first network element can be understood as: the first session established by the first UE is migrated (or relocated) from the user plane network element anchored at the first anchor point to the user plane network element anchored at the second anchor point.

[0301] As another possible implementation, the first network element is an intermediate user plane network element. This intermediate user plane network element is used to provide forwarding services for communication between the first terminal device and the second terminal device through the first session.

[0302] In this implementation, determining the first network element can be understood as: the SMF inserting a network element that provides forwarding services for the data of the first session established for the first UE. For example, the SMF determines to insert a first network element or uses an already inserted first network element.

[0303] It should be understood that, under this implementation, the anchor point UPF to which the first session is anchored is still the first PSA UPF mentioned above. However, the function of forwarding data is implemented by the inserted intermediate user plane network element, while other functions implemented by the anchor point UPF (such as address allocation) are still implemented by the first PSA UPF.

[0304] It should be noted that when the first network element is an intermediate user plane network element, the SMF can insert the first network element before receiving the first information, such as during the establishment of the first session. However, after receiving the first information, it determines whether to enable the inserted first network element to forward the data of the first session. For ease of understanding, the following will combine... Figure 8 The method and process of inserting the first network element during the session establishment process are introduced; or, the timing of SMF inserting the first network element can be after receiving the first information.

[0305] Optionally, if the SMF has already inserted the first network element before receiving the first information, the first information may include information indicating the transmission tunnel of the first PSA UPF (e.g., N19 tunnel information). This can be understood as follows: during the process of inserting the first network element before receiving the first information, the SMF can obtain the tunnel information of the first network element through signaling interaction with the first network element, and the SMF and the first PSA UPF will notify the first PSA UPF of the tunnel information of the first network element through signaling interaction. Specifically, the tunnel information interaction process will be... Figure 8 The details are explained in detail elsewhere, so I will not repeat them here.

[0306] Optionally, if the SMF inserts the first network element after receiving the first information, the first information may include information indicating the transmission tunnel (e.g., AN tunnel information) between the first PSA UPF and the access network device.

[0307] For example, the first network element being an intermediate user plane network element includes: the first network element being an I-UPF or a UL CL UPF. For instance, the functionality of the I-UPF or UL CL UPF is enhanced so that the I-UPF or UL CL UPF has the function of data forwarding. The aforementioned intermediate user plane network element providing forwarding services for the communication between the first UE and the second terminal device through the first session can be understood as: the I-UPF or UL CL UPF providing local forwarding or Nx forwarding services for the communication between the first UE and the second terminal device through the first session.

[0308] For example, the first network element, an intermediate user plane network element, includes: the first network element being a UL CL UPF and a local anchor user plane network element (local PSA UPF). For instance, the first network element is a network element combining a UL CL UPF and a local PSA UPF (which can be referred to as a UL CL UPF and a local PSA UPF). The UL CL UPF is a regular UL CL UPF used to offload data to the local PSA UPF. This local PSA UPF has the function of data forwarding. This local PSA UPF is not the anchor user plane network element to which the session is anchored; the local PSA UPF can be understood as a functional network element for forwarding session data. For example, the local PSA UPF is the UPF anchored to the session corresponding to the service on the satellite. The aforementioned intermediate user plane network element providing forwarding services for the communication between the first UE and the second terminal device through the first session can be understood as: the local PSA UPF providing local forwarding or Nx forwarding services for the communication between the first UE and the second terminal device through the first session.

[0309] As one possible implementation, the first network element mentioned above is located on the ground.

[0310] As another possible implementation, the first network element mentioned above is located on a satellite. That is, the first network element determined by the SMF can be the satellite-borne first network element, in order to reduce the data transmission latency when the first UE and the second UE performing point-to-point communication use the same satellite access network or the same satellite backhaul link.

[0311] For example, when the first UE and the second UE use the same satellite access network, the first PSA UPF anchored to the first session established by the first UE is migrated to the onboard PSA UPF#1, and similarly, the PSA UPF#2 anchored to the second session established by the second UE is migrated to the onboard PSA UPF#2. If the onboard PSA UPF#1 and the onboard PSA UPF#2 are the same onboard PSA UPF, data transmission between the first UE and the second UE is achieved through local forwarding by the onboard PSA UPF#1; if the onboard PSA UPF#1 and the onboard PSA UPF#2 are different onboard PSA UPFs, an N19 tunnel is established between the onboard PSA UPF#1 and the onboard PSA UPF#2, and data transmission between the first UE and the second UE is achieved through N19 forwarding between the onboard PSA UPF#1 and the onboard PSA UPF#2.

[0312] As one possible implementation, if it is determined that the first UE and the second UE use the same satellite, the SMF can directly determine to insert the first network element on that satellite / use the inserted first network element to provide forwarding services for the data of the first session.

[0313] For example, when a second UE sends first data to a first UE, the SMF identifies the second UE based on the source address of the first data, and further determines the location information of both the second and first UEs. Based on this location information, it is determined that they use the same satellite or satellite constellation to access or backhaul the network. The SMF then determines that a first network element provides forwarding services for the data of the first UE's first session. This first network element can be an onboard PSA UPF or an onboard I-UPF, for example, inserted into a satellite or satellite constellation.

[0314] As another possible implementation, if it is determined that the first UE and the second UE use the same access network or backhaul network, a first network element needs to be inserted to provide forwarding services for the data of the first session. However, if the satellite used by the first UE and the second UE is not determined, the first network element can be further determined based on third information.

[0315] For example, if the SMF determines the second UE based on the source or destination address of the first data, and further determines that the second UE and the first UE use the same access network based on their location information (such as the cell global identifier), then the SMF determines that the first network element provides forwarding services for the data of the first UE's first session. This first network element can be a locally deployed terrestrial PSA UPF or I-UPF.

[0316] For example, if the SMF determines that the first terminal device and the second terminal device use the same access network or the same backhaul network (e.g., the same satellite), it can insert a first network element on the same access network or the same backhaul network or select the inserted first network element for data forwarding.

[0317] For example, if the SMF determines that the first terminal device and the second terminal device use the same access network or the same backhaul network, it inserts the first network element based on the third information. It can also be understood that if the satellite where the first network element is located is uncertain, the SMF can determine the first network element based on the third information.

[0318] Specifically, the third information includes at least one of the following: The first information, satellite operation and control information, access type RAT information corresponding to the first session, access type RAT information corresponding to the second session, location information of the first terminal device, or location information of the second terminal device.

[0319] For example, the third information includes the access type RAT information corresponding to the first session, the access type RAT information corresponding to the second session, the location information of the first terminal device, and the location information of the second terminal device. Based on the location information of the first UE and the location information of the second UE (e.g., the cell global identifier of the first UE and the cell global identifier of the second UE), the SMF determines that the first terminal device and the second terminal device use the same onboard RAN, and then determines to insert an I-UPF or PSA UPF as the first network element on the satellite corresponding to the onboard RAN.

[0320] For example, the third information includes satellite operation and control information, the location information of the first terminal device, and the location information of the second terminal device. Based on the location information (such as the cell global identifier), the SMF determines that the base stations accessed by the first terminal device and the second terminal device use different satellites under the same satellite constellation. For example, if they use two different satellites in the same LEO satellite constellation, the SMF can select an I-UPF or PSA UPF on a certain LEO satellite that is adjacent to the satellites of the two RANs to which it belongs as the first network element.

[0321] For example, the third information includes the location information of the first terminal device and the location information of the second terminal device. Based on the location information (such as the cell global identifier), the SMF determines that the first terminal device and the second terminal device use the same satellite backhaul link, such as using the same GEO satellite. Then the SMF determines the I-UPF or PSA UPF on the GEO satellite as the first network element.

[0322] For example, the third information includes satellite operation and control information, the location information of the first terminal device, and the location information of the second terminal device. Based on the location information (such as the cell global identifier), the SMF determines that the base stations accessed by the first terminal device and the second terminal device use the same satellite backhaul network, such as the same LEO satellite constellation. Then, based on the satellite operation and control information, the SMF determines the I-UPF or PSA UPF on a certain LEO satellite that is serving the base station.

[0323] For example, the third information includes the first information. Based on the network instance information included in the first information, the SMF determines that the RAN accessed by the first terminal device and the second terminal device uses the same satellite backhaul link, such as the same GEO satellite. Then the SMF determines the I-UPF or PSA UPF on the GEO satellite as the first network element.

[0324] Furthermore, in order to enable the first network element to forward data from the first session, the SMF needs to configure PDR and FAR for the first network element. Figure 7 The method flow shown also includes: In S760, the SMF sends PDR and FAR to the first network element, or in other words, the first network element receives PDR and FAR from the SMF.

[0325] After the first network element is inserted, in order to enable the first network element to forward data locally or based on Nx, the SMF will send flow control rules (such as PDR and FAR) to instruct the first network element to forward the received data packets locally or based on Nx. Furthermore, the flow control rules can also instruct the first network element to send the received data packets to its internal interface, which will then perform the local forwarding or Nx-based forwarding.

[0326] Specifically, in order to enable data packets sent from the first UE to the second UE to be forwarded locally by the first network element, the PDR includes the destination address of the first data (when the first data is sent from the first UE to the second UE) or the source address of the first data (when the first data is sent from the second UE to the first UE); the FAR includes the N4 session corresponding to the second session whose destination interface is the second UE; Alternatively, based on the data plane forwarding mechanism of 5G VN group communication, PDR and FAR can be configured on the first network element to enable 5G VN group communication. For specific PDR and FAR configurations, please refer to the description of PDR and FAR above, which will not be repeated here.

[0327] It should be understood that the above steps S710 to S770 detail how the SMF determines the first network element for the first session established by the first UE. For the second UE, the SMF will also determine the second network element for the second session established by the second UE. For example, if the PSA UPF anchored to the second session established by the second UE is PSA UPF#2, the SMF can determine the second network element based on the information reported by PSA UPF#2. The specific process can be referred to the above steps S710 to S770, where the roles of the first UE and the second UE are reversed, that is, from the perspective of the second UE, it becomes the first UE in steps S710 to S770. This will not be elaborated here.

[0328] As one possible implementation, when the first network element and the second network element determined by the SMF are the same network element, point-to-point communication between the first UE and the second UE can be achieved by local forwarding by the first network element.

[0329] As another possible implementation, when the first network element and the second network element determined by the SMF are not the same network element, point-to-point communication between the first UE and the second UE can be achieved by forwarding between the first network element and the second network element based on Nx (e.g., N19).

[0330] In this implementation, a first forwarding tunnel (e.g., N19) needs to be established between the first network element and the second network element. This first forwarding tunnel is used to transmit data between the first network element and the second network element.

[0331] In addition, if there is a communication requirement between the first UE and other UEs (e.g., the third UE), and the third session established by the third UE is anchored on the first PSA UPF, a second forwarding tunnel can be established between the first PSA UPF and the first network element. The second forwarding tunnel is used to transmit data between the first PSA UPF and the first network element.

[0332] For ease of understanding, combined with Figure 8 This section details the point-to-point communication process between the first UE and the second UE. Figure 8 This is a schematic flowchart of another communication method provided in an embodiment of this application, including the following steps: S801, the first UE sends a session establishment request message #1 to the AMF, or in other words, the AMF receives a session establishment request message #1 from the first UE.

[0333] The session establishment request message #1 is used to request the establishment of the first PDU session. Specifically, the session establishment request message #1 includes, but is not limited to, information such as the DNN#1 and S-NSSAI#1 corresponding to the first UE.

[0334] It should be understood that the session establishment request message #1 is forwarded to the AMF through the first RAN, and the first RAN also sends the first UE's ULI and RAT information to the AMF. For ease of distinction, the first UE's ULI will be referred to as ULI#1 and RAT as RAT#1 in the following text.

[0335] For example, information such as ULI#1 and / or RAT #1 can be carried in the Session Establishment Request message #1 and sent to the AMF, or it can be sent to the AMF via other messages.

[0336] It should be noted that the first UE sends a session establishment request message #1 to the AMF through the first RAN. That is, although the AMF ultimately receives the session establishment request message #1, the first UE is unaware of who ultimately receives it; it only perceives that the session establishment request message #1 was sent to the first RAN. Furthermore, during transmission, the first RAN may modify the message's form / content. However, as long as the modified message can notify the AMF of the session establishment request message #1, it can be considered the session establishment request message #1 in this embodiment.

[0337] For S802, the AMF should be SMF.

[0338] Specifically, the AMF selects the SMF to establish the first PDU session based on the received information such as DNN#1, S-NSSAI#1, ULI#1, and RAT#1.

[0339] It should be noted that this application embodiment does not impose restrictions on how the AMF specifically selects the SMF. Reference can be made to the relevant descriptions regarding AMF selection of the SMF during the current PDU session establishment process. After the AMF selects the SMF to create the first PDU session, a first request can be made to request the SMF to create the session management (SM) context #1 corresponding to the first PDU session.

[0340] Figure 8 The method flow shown also includes: S803, AMF sends first request #1 to SMF, or in other words, SMF receives first request #1 from AMF.

[0341] The first request #1 is used to request the creation of SM context #1. Specifically, the first request #1 includes information such as the identifier of the first UE, DNN #1, S-NSSAI #1, ULI #1, and RAT #1, wherein the identifier of the first UE includes, but is not limited to, any of the following: The first UE has several identifiers, including a Subscription Permanent Identifier (SUPI), a Subscription Concealed Identifier (SUCI), a Generic Public Subscription Identifier (GPSI), a Permanent Equipment Identifier (PEI), or a Mobile Subscriber International ISDN / PSTN number (MSISDN). ISDN stands for Integrated Services Digital Network, and PSTN stands for Public Switched Telephone Network. MSISDN can be understood as a publicly disclosed identifier for the terminal, such as its telephone number. For ease of description, the following text uses SUPI#1 as an example.

[0342] For example, the first request #1 can be called the first PDU session create SM context request (Nsmf_PDUSession_CreateSMContext Request).

[0343] Furthermore, the SMF can obtain session management subscription information #1 from the UDM. Figure 8 The method flow shown may also include: S804, SMF obtains session management subscription information #1 from UDM.

[0344] As one possible implementation, the SMF can request session management subscription information #1 by sending a query request #1 to the UDM.

[0345] As another possible implementation, SMF can request session management subscription information #1 by sending a subscription request #1 to UDM.

[0346] It should be noted that this application does not restrict the way SMF obtains session management subscription information #1 from UDM; it can be either query or subscription, which will not be elaborated further in this application.

[0347] In this embodiment, the session management subscription information #1 obtained by the SMF also includes point-to-point transmission indication information #1, which is used to indicate that the data of the first PDU session is allowed to be transmitted in a point-to-point manner. For example, the point-to-point transmission indication information #1 indicates that the data of the first PDU session corresponding to DNN#1 and S-NSSAI#1 is transmitted in a point-to-point manner.

[0348] For example, the first UE can be a member of a 5G VN group. If the first UE is a member of a 5G VN group, the session management subscription information #1 mentioned above also includes information about the 5G VN group. For example, the session management subscription information #1 also includes the identification information of the 5G VN group.

[0349] S805, SMF sends first response #1 to AMF, or AMF receives first response #1 from SMF.

[0350] The first response #1 is used to respond to the first request #1 mentioned above, indicating that the first PDU session establishment request is accepted.

[0351] For example, the first response #1 can be called the first PDU session create SM context response (Nsmf_PDUSession_CreateSMContext Response).

[0352] S806, SMF determines the first PSA UPF.

[0353] Specifically, the SMF determines the first PSA UPF of a ground-based system as the PSA UPF anchored to the first PDU session based on at least one of the following information: RAT#1, ULI#1, DNN#1, S-NSSAI#1, and Session Management Subscription Information #1. For example, when RAT#1 represents satellite access, although a UPF is also deployed on the satellite, the SMF defaults to determining the ground-based UPF as the PSA UPF; or, when RAT#1 represents ground access and the base station corresponding to the cell global identifier contained in ULI#1 uses satellite backhaul, although a UPF is deployed on the satellite, the SMF defaults to determining the ground-based UPF as the PSA UPF; or the session subscription data associated with DNN#1 and S-NSSAI#1 requires that the ground-based UPF be determined as the PSA UPF by default.

[0354] For example, the SMF can assign IP address #1 to the first UE. For instance, the SMF can divide the aforementioned RAT#1 into an address pool so that the addresses obtained by UEs accessing the network based on the access method indicated by RAT#1 all belong to the IP range corresponding to the address pool.

[0355] Furthermore, after the SMF determines the first PSA UPF, Figure 8 The method flow shown also includes: S807, SMF sends second request #1 to first PSA UPF, or in other words, first PSA UPF receives second request #1 from SMF.

[0356] The second request #1 is used to obtain uplink N9 tunnel (N9 channel, N9 CN) information #1, which includes the address information of the first PSA UPF and the tunnel ID information allocated by the first PSA UPF, and is used to send to the first RAN to establish the uplink N9 tunnel.

[0357] S808, the first PSA UPF sends the second response #1 to the SMF, or in other words, the SMF receives the second response #1 from the first PSA UPF.

[0358] The second response #1 includes uplink N9 CN information #1.

[0359] Optionally, if the SMF does not assign IP address #1 to the first UE in step S806 above, the SMF may also request the first PSA UPF to assign IP address #1 to the first UE. In this case, the second response #1 may also include the IP address #1 of the first UE.

[0360] Optionally, during the establishment of the first PDU session, the SMF can also determine a first network element so that the network element providing forwarding services for the first PDU session can be transformed from the first PSA UPF into the first network element.

[0361] For example, the above Figure 7 The embodiments shown describe in detail the possible forms of the first network element, which will not be repeated here. For ease of description, this embodiment takes the example of point-to-point communication based on the first intermediate user plane network element on the satellite when point-to-point satellite communication occurs, that is, the first network element is the onboard I-UPF.

[0362] S809, SMF determines the first intermediate user plane network element.

[0363] Specifically, the SMF determines the first intermediate user plane network element based on the relevant information provided by the first RAN.

[0364] For example, the SMF determines the first intermediate user plane network element based on at least one of RAT#1, TAI information #1 in ULI#1, NGCI information #1 in ULI#1, or satellite operation and control information.

[0365] For example, RAT#1 represents satellite access, TAI information in ULI#1 and NGCI information represent the first RAN information currently used by the first UE. The SMF may determine the UPF that uses the same satellite as the first RAN as the first intermediate user plane network element. The SMF may further determine the UPF on the satellite adjacent to the satellite used by the first RAN as the first intermediate user plane network element based on the satellite operation and control information indication. For example, RAT#1 represents terrestrial access, and the TAI and NGCI information in ULI#1 represent the first RAN information currently used by the first UE. Based on this information, the SMF determines that the first RAN uses a satellite backhaul link, and the SMF determines the UPF on the corresponding satellite as the first intermediate user plane network element. For example, the SMF may also determine, based on the TAI and NGCI information in ULI#1, that the first RAN is currently using a satellite constellation as its backhaul link. Therefore, the SMF can further determine, based on satellite operation and control information, the UPF on the satellite serving the first RAN, or the UPF on a satellite over the first RAN, as the first intermediate user plane network element. After the SMF determines the first intermediate user plane network element, Figure 8 The method flow shown also includes: S810, the SMF sends the third request #1 to the first intermediate user plane network element, or in other words, the first intermediate user plane network element receives the third request #1 from the SMF.

[0366] The third request #1 is used to request the first intermediate user plane network element to allocate uplink N3 CN information #1. This uplink N3 CN information #1 includes the address information of the first intermediate user plane network element and the tunnel ID information allocated to it. This information is used to establish an N3 tunnel between the first RAN and the first intermediate user plane network element. Specifically, the third request #1 includes uplink N9 CN information #1, which is used to establish an N9 tunnel between the first PSA UPF and the first intermediate user plane network element. S811, the first intermediate user plane network element sends the third response #1 to the SMF, or in other words, the SMF receives the third response #1 from the first intermediate user plane network element.

[0367] The third response #1 is used in response to the aforementioned third request #1. Specifically, the third response #1 includes uplink N3CN information #1.

[0368] It should be understood that Figure 8 Steps S809-S811 can occur before steps S806-S808. In this application, there are no restrictions on the order of performing the steps of determining the first PSA UPF and determining the first intermediate user plane network element.

[0369] S812, SMF sends first message #1 to AMF, or AMF receives first message #1 from SMF.

[0370] The first message #1 includes information such as uplink N3 CN information #1, IP address #1, and the first PDU session establishment and acceptance message.

[0371] For example, the first message #1 can be referred to as the N1N2 message transfer (Namf_Communication_N1N2MessageTransfer).

[0372] S813, AMF sends fourth request #1 to the first RAN, or in other words, the first RAN receives fourth request #1 from AMF.

[0373] The fourth request #1 is used to request the establishment of an N2 PDU session. Specifically, the fourth request #1 includes uplink N3 CN information #1 and IP address #1.

[0374] S814, the first RAN and the first UE exchange signaling, requesting the first UE to establish a session, including a session establishment acceptance message.

[0375] S815, the first RAN sends the fourth response #1 to the AMF, or in other words, the AMF receives the fourth response #1 from the first RAN.

[0376] The fourth response #1 is used in response to the aforementioned fourth request #1. Specifically, the fourth response #1 includes downlink N3 AN information #1 allocated by the first RAN, etc.

[0377] S816, AMF sends Fifth Request #1 to SMF, or in other words, SMF receives Fifth Request #1 from AMF.

[0378] The fifth request #1 includes downlink N3 AN information #1, etc.

[0379] Optionally, the fifth request #1 can be a first PDU session SM context update (Nsmf_PDUSession_UpdateSMContext) request message.

[0380] S817, the SMF sends the sixth request #1 to the first intermediate user plane network element, or in other words, the first intermediate user plane network element receives the sixth request #1 from the SMF.

[0381] The sixth request #1 includes downlink N3 AN information #1.

[0382] Optionally, the sixth request #1 can be an N4 Session modification request.

[0383] S818, the first intermediate user plane network element sends the sixth response #1 to the SMF, or in other words, the SMF receives the sixth response #1 from the first intermediate user plane network element.

[0384] This sixth response #1 is used in response to the aforementioned sixth request #1. Specifically, the sixth response #1 includes downlink N9 CN information #1.

[0385] S819, SMF sends seventh request #1 to the first PSA UPF, or in other words, the first PSA UPF receives seventh request #1 from SMF.

[0386] The seventh request #1 includes downlink N9 CN information #1.

[0387] Optionally, the seventh request #1 can be an N4 Session modification request.

[0388] As one possible implementation, for non-5G VN communication, the seventh request #1 also includes a first PDR and first indication information (e.g., a first URR), the first PDR including at least one of the following: Information used to indicate whether data comes from satellite access network equipment, information used to indicate whether satellite backhaul is used access network source interface, information used to indicate whether satellite backhaul is used network instance, downlink N9 CN information #1, uplink N9 CN information #1, or destination address information #1, wherein destination address information #1 includes destination IP address range #1 or set #1.

[0389] Specifically, when using UPF to allocate addresses, the destination IP address range #1 corresponds to the address pool range governed by the first PSA UPF; when using SMF to allocate addresses, the destination IP address range #1 corresponds to the address pool range allocated by the SMF.

[0390] The first URR reporting trigger includes: the occurrence of a point-to-point communication request.

[0391] As another possible implementation, for 5G VN communication, the seventh request #1 also includes rules such as the first PDR and the first FAR, as well as the first URR. The reporting triggers for the first URR include: the occurrence of a point-to-point communication request, such as the successful matching of the destination IP or MAC corresponding to the first PDR.

[0392] S820, first PSA UPF installation first URR.

[0393] S821, the first PSA UPF sends the seventh response #1 to the SMF, or in other words, the SMF receives the seventh response #1 from the first PSA UPF.

[0394] S822, SMF sends fifth response #1 to AMF, or AMF receives fifth response #1 from SMF.

[0395] Fifth Response #1 is used to respond to the aforementioned Fifth Request #1.

[0396] Optionally, the fifth response #1 can be the first PDU session SM context update (Nsmf_PDUSession_UpdateSMContext) response message.

[0397] It should be understood that the PDU session establishment process for other UEs is similar to the first UE proposing the first PDU session described above. This embodiment also includes the following steps: S823, the second terminal device establishes a second PDU session.

[0398] Similar to the process described above for the first terminal device to establish a first PDU session, the process for the second terminal device to establish a second PDU session includes the following steps (not described in the original text). Figure 8 (shown in the middle) Step 1: The second terminal device sends a session establishment request message #2 to the AMF, or in other words, the AMF receives a session establishment request message #2 from the second terminal device.

[0399] The session establishment request message #2 is used to request the establishment of a second PDU session. Specifically, the session establishment request message #2 includes, but is not limited to, information such as the DNN#2 and S-NSSAI#2 corresponding to the second UE.

[0400] It should be understood that the session establishment request message #2 is forwarded to the AMF through the second RAN, and the second RAN also sends information such as the second UE's ULI#2 and RAT#2 to the AMF.

[0401] For example, information such as ULI#2 and / or RAT #2 can be carried in the Session Establishment Request message #2 and sent to the AMF, or it can be sent to the AMF via other messages.

[0402] It should be noted that the second UE sends a session establishment request message #2 to the AMF through the second RAN. That is, although the AMF ultimately receives the session establishment request message #2, the second UE is unaware of who ultimately receives it; it only perceives that the session establishment request message #2 was sent to the second RAN. Furthermore, during transmission, the second RAN may modify the message's form / content. However, as long as the modified message can notify the AMF of the session establishment request message #2, it can be considered as the session establishment request message #2 in this embodiment.

[0403] Step 2: Select SMF from AMF.

[0404] Specifically, the AMF selects the SMF to establish the second PDU session based on the received information such as DNN#2, S-NSSAI#2, ULI#2, and RAT#2.

[0405] Step 3: AMF sends first request #2 to SMF, or SMF receives first request #2 from AMF.

[0406] The first request #2 is used to request the creation of SM context #2. Specifically, the first request #2 includes information such as the identifier of the second UE, DNN #2, S-NSSAI #2, ULI #2, and RAT #2, wherein the identifier of the second UE includes, but is not limited to, any of the following: The second UE's SUPI, SUCI, GPSI, PEI, or MSISDN. For ease of description, the following description uses the second UE's identifier SUPI#2 as an example.

[0407] For example, the first request #2 can be called the second PDU session create SM context request (Nsmf_PDUSession_CreateSMContext Request).

[0408] Step 4: SMF obtains session management subscription information #2 from UDM.

[0409] As one possible implementation, the SMF can request session management subscription information #2 by sending a query request #2 to the UDM.

[0410] As another possible implementation, SMF can request session management subscription information by sending a subscription request #2 to UDM.

[0411] It should be noted that this application does not restrict the way SMF obtains session management subscription information #2 from UDM; it can be either query or subscription, which will not be elaborated further in this application.

[0412] In this embodiment, the session management subscription information #2 obtained by the SMF also includes point-to-point transmission indication information #2, which is used to indicate that the data of the second PDU session is allowed to be transmitted in a point-to-point manner. For example, point-to-point transmission indication information #2 indicates that the data of the second PDU session corresponding to DNN#2 and S-NSSAI#2 is transmitted in a point-to-point manner.

[0413] For example, the second UE can be a member of a 5G VN group. In the case that the second UE is a member of a 5G VN group, the session management subscription information #2 mentioned above also includes information about the 5G VN group. For example, the session management subscription information #2 also includes the identification information of the 5G VN group.

[0414] Step 5: The SMF sends the first response #2 to the AMF, or in other words, the AMF receives the first response #2 from the SMF.

[0415] The first response #2 is used to respond to the first request #2 mentioned above, indicating that the second PDU session establishment request is accepted.

[0416] For example, the first response #2 can be called the second PDU session creation SM context response (Nsmf_PDUSession_CreateSMContext Response).

[0417] Step 6: SMF determines the second PSA UPF.

[0418] Specifically, the SMF determines a second PSA UPF for a ground based on at least one of the following information: RAT#2, ULI#2, DNN#2, S-NSSAI#2, and Session Management Subscription Information #2.

[0419] For example, the SMF can assign IP address #2 to the second UE. For instance, the SMF can divide RAT#2 into an address pool so that the addresses obtained by UEs accessing the network based on the access method indicated by RAT#2 all belong to the IP range corresponding to the address pool.

[0420] Step 7: The SMF sends the second request #2 to the second PSA UPF, or in other words, the second PSA UPF receives the second request #2 from the SMF.

[0421] The second request #2 is used to obtain uplink N9 CN information #2.

[0422] Step 8: The second PSA UPF sends a second response #2 to the SMF, or in other words, the SMF receives a second response #2 from the second PSA UPF.

[0423] The second response #2 includes uplink N9 CN information #2.

[0424] Step 9: SMF determines the second I-UPF.

[0425] Specifically, the SMF infers how to determine the onboard second intermediate user plane network element based on the relevant information provided by the second RAN.

[0426] For example, the SMF determines the second intermediate user plane network element based on at least one of RAT#2, TAI information #2 in ULI#2, NGCI information #2 in ULI#2, or satellite operation and control information.

[0427] Step 10: The SMF sends the third request #2 to the second intermediate user plane network element, or in other words, the second intermediate user plane network element receives the third request #2 from the SMF.

[0428] The third request #2 is used to request the second intermediate user plane network element to allocate uplink N3 CN information #2. Specifically, the third request #2 includes uplink N9 CN information #2. Step 11: The second intermediate user plane network element sends a third response #2 to the SMF, or in other words, the SMF receives a third response #2 from the second intermediate user plane network element.

[0429] The third response #2 is used in response to the aforementioned third request #2. Specifically, the third response #2 includes uplink N3CN information #2.

[0430] Step 12: SMF sends the first message #2 to AMF, or AMF receives the first message #2 from SMF.

[0431] The first message #2 includes information such as uplink N3 CN information #2, IP address #2, and the second PDU session establishment and acceptance message.

[0432] For example, the second message #2 can be referred to as the N1N2 message transfer (Namf_Communication_N1N2MessageTransfer).

[0433] Step 13: The AMF sends the fourth request #2 to the second RAN, or in other words, the second RAN receives the fourth request #2 from the AMF.

[0434] The fourth request #2 is used to request the establishment of an N2 PDU session. Specifically, the fourth request #2 includes uplink N3 CN information #2 and IP address #2.

[0435] Step 14: The second RAN exchanges signaling with the second UE, requesting the second UE to establish a session, including a session establishment acceptance message.

[0436] Step 15: The second RAN sends the fourth response #2 to the AMF, or the AMF receives the fourth response #2 from the second RAN.

[0437] The fourth response #2 is used in response to the aforementioned fourth request #2. Specifically, the fourth response #2 includes downlink N3 AN information #2 allocated by the second RAN, etc.

[0438] Step 16: The AMF sends the fifth request #2 to the SMF, or in other words, the SMF receives the fifth request #2 from the AMF.

[0439] The fifth request #2 includes downlink N3 AN information #2, etc.

[0440] Optionally, the fifth request #2 can be a second PDU session SM context update (Nsmf_PDUSession_UpdateSMContext) request message.

[0441] Step 17: The SMF sends the sixth request #2 to the second intermediate user plane network element, or in other words, the second intermediate user plane network element receives the sixth request #2 from the SMF.

[0442] The sixth request #2 includes downlink N3 AN information #2.

[0443] Optionally, the sixth request #2 can be an N4 Session modification request.

[0444] Step 18: The second intermediate user plane network element sends the sixth response #2 to the SMF, or in other words, the SMF receives the sixth response #2 from the second intermediate user plane network element.

[0445] The sixth response #2 is used in response to the sixth request #2 mentioned above. Specifically, the sixth response #2 includes downlink N9 CN information #2.

[0446] Step 19: The SMF sends the seventh request #2 to the second PSA UPF, or in other words, the second PSA UPF receives the seventh request #2 from the SMF.

[0447] The seventh request #2 includes downlink N9 CN information #2.

[0448] Optionally, the seventh request #2 can be an N4 Session modification request.

[0449] As one possible implementation, for non-5G VN communication, the seventh request #2 also includes a second PDR and a second URR, wherein the second PDR includes at least one of the following information: Information used to indicate whether the second data comes from a satellite access network device, information used to indicate whether the access network source interface for satellite backhaul is used, information used to indicate whether the network instance for satellite backhaul is used, downlink N9 CN information #2, uplink N9 CN information #2, or destination address information #2, wherein the destination address information #2 includes a destination IP address range #2 or a set #2.

[0450] Specifically, when using UPF to allocate addresses, the destination IP address range #2 corresponds to the address pool range governed by the second PSA UPF; when using SMF to allocate addresses, the destination IP address range #2 corresponds to the address pool range allocated by SMF.

[0451] The reporting trigger for the second URR includes: the destination IP address range #2 corresponding to the second PDR is successfully matched.

[0452] As another possible implementation, for 5G VN communication, based on the existing mechanism, the corresponding second PDR and second FAR rules are issued, and the second URR for reporting point-to-point communication is also issued. The reporting trigger of the second URR includes the successful matching of the destination IP or MAC of the corresponding second PDR.

[0453] Step 20: Install the second PDR and the second URR on the second PSA UPF.

[0454] Step 21: The first PSA UPF sends the seventh response #2 to the SMF, or in other words, the SMF receives the seventh response #2 from the first PSA UPF.

[0455] Step 22: The SMF sends the fifth response #2 to the AMF, or the AMF receives the fifth response #2 from the SMF.

[0456] Fifth Response #2 is used in response to the aforementioned Fifth Request #1.

[0457] Optionally, the fifth response #2 can be a second PDU session SM context update (Nsmf_PDUSession_UpdateSMContext) response message.

[0458] As one possible implementation, the process of establishing a PDU session by the second terminal device can occur after the first terminal device establishes a first PDU session.

[0459] As another possible implementation, the process of establishing a PDU session by the second terminal device can occur before the first terminal device establishes a first PDU session.

[0460] As another possible implementation, the process of establishing a PDU session by the second terminal device can be carried out simultaneously with the process of establishing a first PDU session by the first terminal device.

[0461] In addition, as a possible implementation, the second PDU session and the first PDU session mentioned above are anchored to the same PSA UPF, that is, the first PSA UPF and the second PSA UPF mentioned above are the same PSA UPF.

[0462] In the case where the second PDU session and the first PDU session are anchored to the same PSA UPF, as a possible implementation, the second PDU session and the first PDU session use the same RAN and / or I-UPF, that is, the first RAN and the second RAN are the same RAN, and / or, the first intermediate user plane network element and the second intermediate user plane network element are the same I-UPF.

[0463] For example, the first terminal device and the second terminal device mentioned above use the same satellite access, and therefore use the same onboard RAN and I-UPF.

[0464] As another possible implementation, the second PDU session and the first PDU session described above use different RANs and I-UPFs.

[0465] For example, the first terminal device and the second terminal device mentioned above use different satellite access but belong to the same constellation, so they may have the same PSA UPF but different RAN and I-UPF.

[0466] As another possible implementation, the second PDU session and the first PDU session mentioned above use different RANs but use the same I-UPF.

[0467] For example, in a satellite backhaul scenario, different ground RANs use the same satellite backhaul, and therefore use the same I-UPF.

[0468] As another possible implementation, the second PDU session and the first PDU session mentioned above are anchored to different PSA UPFs, that is, the first PSA UPF and the second PSA UPF mentioned above are different PSA UPFs.

[0469] When the second PDU session and the first PDU session are anchored to different PSA UPFs, the second PDU session and the first PDU session use different RANs and I-UPFs, that is, the first RAN and the second RAN are different, and / or the first intermediate user plane network element and the second intermediate user plane network element are different.

[0470] For example, the first UE and the second UE mentioned above use different satellite access or backhaul, and may be anchored to different PSA UPFs due to their far distance from each other.

[0471] Furthermore, in this implementation, for non-5G VN communication, when the second PSA UPF allocates IP address #2, the SMF determines that the first PDU session established by the first UE for point-to-point communication is anchored to the first PSA UPF based on the information of the first PDU session. Therefore, when the SMF configures the second PDR for the second PSA UPF, the destination IP address range #2 included in the second PDR includes the IP address range corresponding to the address pool managed by the second PSA UPF and the IP address range corresponding to the address pool managed by the first PSA UPF. The SMF also updates the first PDR of the first PSA UPF and adds the IP address range corresponding to the address pool managed by the second PSA UPF.

[0472] For 5G VN group communication, the SMF establishes a 5G VN group granularity N4 session with the second PSA UPF, creates an N19 tunnel, and issues corresponding second PDR and second FAR rules to enable N19 forwarding. It also issues a second URR report for point-to-point communication, with the URR reporting trigger including successful matching of the destination IP / MAC for the corresponding N19 forwarding of the second PDR. Furthermore, the SMF establishes a 5G VN group granularity N4 session with the first PSA UPF, creates an N19 tunnel, and issues corresponding first PDR and first FAR rules to enable N19 forwarding. It also issues a first URR report for point-to-point communication, with the first URR reporting trigger including successful matching of the destination IP / MAC for the corresponding N19 forwarding of the first PDR.

[0473] The above describes the relevant configurations during the PDU session establishment process, in the case where there is a communication requirement between the first UE and the second UE: For example, in non-5G VN communication, when the first PSA UPF receives uplink data from the first UE destined for the second UE, and the destination address is within the address range of the second PDR and a match is found, the data packet is forwarded by the second FAR into the DN. The routing and forwarding equipment of the DN then returns the data packet to the first or second PSA UPF of the target second UE, and the first or second PSA UPF then sends the data packet to the target second UE.

[0474] For example, in 5G VN communication, when the first UE and the second UE use the same PSA UPF, the first PSA UPF performs local forwarding to achieve data transmission. The specific transmission method has been explained in detail when discussing local forwarding earlier (e.g., Figure 3 The transmission process shown will not be elaborated here.

[0475] For example, in 5G VN communication, when the first UE and the second UE use different PSA UPFs, the first PSA UPF and the second PSA UPF achieve data transmission based on N19 forwarding (e.g., Figure 2 The transmission process is shown below.

[0476] In other words, when there is a communication requirement between the first UE and the second UE, the first PSA UPF forwards the first received data packet to the target UE based on the existing 5G VN communication mechanism. For subsequent data packets to be transmitted between the first UE and the second UE, data transmission can be achieved by activating the inserted first and second intermediate user plane network elements, thereby reducing data transmission latency. Figure 8 The method flow shown also includes: S824, the first PSA UPF sends the first message to the SMF.

[0477] Since there is a communication requirement between the first UE and the second UE, the first PSA UPF reports a point-to-point communication report (e.g., first information). Refer to the description of step S710 above, which will not be repeated here.

[0478] S825, SMF determines the communication method.

[0479] Based on the first received message and the session information, SMF determines whether to perform point-to-point satellite communication, specifically as follows: Based on the destination address (e.g., destination IP address or destination MAC address) of the data included in the first information, the SMF determines the session of the target UE and determines whether the session of the target UE (e.g., the second PDU session mentioned above) has enabled point-to-point communication. In conjunction with at least one of the source interface identification information, network instance information, and N9 tunnel information included in the first information, it determines whether the current first PDU session and the second PDU session use the same I-UPF or different I-UPFs.

[0480] As a possible implementation, if S809 does not insert the first intermediate user plane network element, SMF can also insert the first intermediate user plane network element for the first PDU session of the first UE in this step (i.e. when it is determined that satellite point-to-point communication is required), and similarly insert the second I-UPF for the second PDU session of the second UE.

[0481] S826, SMF sends PDR and FAR to the first intermediate user plane network element.

[0482] For example, the SMF sends an N4 session modification request to the first intermediate user plane network element, the N4 session modification request including PDR and FAR.

[0483] As one possible implementation, the sessions of the first UE and the second UE use the same I-UPF.

[0484] In this implementation, an internal forwarding interface is created on the first intermediate user plane network element, and the corresponding PDR and FAR are issued to realize the local forwarding of data between the first UE and the second UE based on the first intermediate user plane network element.

[0485] As another possible implementation, the sessions of the first UE and the second UE use different I-UPFs.

[0486] In this implementation, the SMF establishes an Nx tunnel (e.g., N19) between the first intermediate user plane network element and the second intermediate user plane network element to facilitate data transmission between the first intermediate user plane network element and the second intermediate user plane network element through the tunnel. Establishing the Nx tunnel specifically includes: creating an Nx#1 interface in the first intermediate user plane network element to obtain downlink Nx#1 tunnel information, and creating an Nx#2 interface in the second intermediate user plane network element to obtain uplink Nx#2 tunnel information.

[0487] The above combination Figure 8 This application details embodiments of how to implement point-to-point communication. Furthermore, it provides a communication method that enables the SMF to re-determine the network element providing forwarding services for the affected session in scenarios where the UE's access network equipment undergoes a handover. For ease of understanding, the following description, in conjunction with... Figure 9 This communication method is described in detail.

[0488] Assume that before the handover, both the first UE and the second UE access the core network using the first RAN and the first intermediate user plane network element, and have a session with point-to-point communication enabled. During the access network equipment handover phase, the second UE switches from the first RAN to the second RAN.

[0489] Figure 9 This is a schematic flowchart illustrating another communication method provided in an embodiment of this application, including the following steps: S901, the second RAN sends a handover request to the AMF.

[0490] The handover request includes a list of sessions to be switched and downlink N3 tunnel information allocated by the second RAN.

[0491] Alternatively, the switching request may be an N2 PATH Switch Request.

[0492] S902, AMF sends message #1 to SMF.

[0493] Message #1 includes downlink N3 tunnel information and a list of sessions that need to be switched. Optionally, message #1 can be a PDU session context update request (Nsmf_PDUSession_UpdateSMContext Request).

[0494] S903, SMF determines whether data transmission is affected.

[0495] Specifically, based on the list of sessions to be switched and the point-to-point communication context maintained by the SMF, the SMF determines whether a switch of sessions in the context is involved.

[0496] For example, a session that implements point-to-point communication based on a first intermediate user plane network element includes a first PDU session, and the list of sessions that need to be switched includes the first PDU session.

[0497] In cases where the SMF determines that data transmission in point-to-point communication sessions may be affected, Figure 9 The method flow shown also includes the following steps: S904, SMF obtains uplink N9 tunnel information #1 from the first PSA UPF.

[0498] The uplink N9 tunnel information #1 is used by the SMF to send to the second intermediate user plane network element in subsequent steps, so as to establish an N9 tunnel between the first PSA UPF and the second intermediate user plane network element.

[0499] For example, the SMF sends an N4 session modification request to the first PSA UPF, requesting the first PSA UPF to allocate uplink N9 tunnel information #1.

[0500] As one possible implementation, in subsequent steps, an Nx interface and forwarding can be created on the second intermediate user plane network element to achieve the migration of point-to-point communication (e.g., the relevant configurations for forwarding data from the first PDU session are migrated from the first intermediate user plane network element to the second intermediate user plane network element). Figure 9 The method flow shown also includes the following steps: S905, SMF obtains Nx#1 tunnel information from the first intermediate user plane network element.

[0501] The Nx#1 tunnel information is used in subsequent steps by the SMF to send to the second intermediate user plane network element in order to establish an Nx tunnel between the first intermediate user plane network element and the second intermediate user plane network element.

[0502] For example, the SMF sends an N4 session modification request #1 to the first intermediate user plane network element to request the first intermediate user plane network element to allocate Nx#1 (e.g., N19) tunnel information; the first intermediate user plane network element returns a response carrying the Nx#1 tunnel information.

[0503] Specifically, the SMF can determine the second intermediate user plane network element as the handover target based on the N3 tunnel information carried in the handover request in step S901 above, such as the second intermediate user plane network element and the second RAN being deployed on the same satellite or the satellite where the second intermediate user plane network element is located providing a backhaul link for the second RAN.

[0504] S906, SMF obtains tunnel information #1 from the second intermediate user plane network element.

[0505] For example, the SMF sends an N4 session modification request #2 to the second intermediate user plane network element, requesting the second intermediate user plane network element to allocate tunnel information #1. Tunnel information #1 includes Nx#2 tunnel information, which is used by the SMF in subsequent steps to send to the first intermediate user plane network element to establish an Nx tunnel between the first and second intermediate user plane network elements. Tunnel information #1 also includes N3 tunnel information, which is used by the SMF in subsequent steps to send to the second RAN to establish an N3 tunnel between the second RAN and the second intermediate user plane network element. Tunnel information #1 also includes N9 tunnel information #2, which is used by the SMF to send to the first PSA UPF to establish an N9 tunnel between the first PSA UPF and the second intermediate user plane network element. The second intermediate user plane network element returns a response carrying tunnel information #1.

[0506] Specifically, the SMF configures PDR and FAR for the second intermediate user plane network element to implement data forwarding based on Nx (e.g., N19). For uplink data (e.g., data packets from the first UE to the second UE), PDR contains the IP address of the second UE as the destination address, and FAR contains the address information of the first intermediate user plane network element containing Nx#1 tunnel information. For downlink data (e.g., data packets from the second UE to the first UE), PDR contains the IP address of the first UE as the destination address, and FAR is set to contain the RAN address information in the N3 tunnel information obtained in step S901.

[0507] S907, SMF sends tunnel information #2 to the first PSA UPF.

[0508] This tunnel information #2 is used to establish an N9 tunnel between the first PSA UPF and the second intermediate user plane network element.

[0509] For example, the SMF sends an N4 Modify Session Request to the first PSA UPF. The N4 Modify Session Request carries the downlink N9 tunnel information of the second intermediate user plane network element obtained in step S906 and the N9 tunnel of the anchor PSA UPF (for non-local forwarding data packets sent to the anchor PSA UPF out of N6).

[0510] S908, SMF sends Nx#2 tunnel information to the first intermediate user plane network element.

[0511] For example, the SMF sends an N4 session modification request to the first intermediate user plane network element, carrying the Nx#2 tunnel information obtained in step S906, which is used by the first intermediate user plane network element to establish an Nx tunnel between the second intermediate user plane network element.

[0512] Specifically, the SMF configures PDR and FAR for the first intermediate user plane network element. For uplink data (e.g., data packets from the first UE to the second UE), the PDR contains the IP address of the second UE as the destination address, and the FAR contains the I-UPF address information of the Nx#1 tunnel information. For downlink data (e.g., data packets from the second UE to the first UE), the PDR contains the IP address of the first UE as the destination address, and the FAR is set to contain the RAN address information in the N3 tunnel information obtained in step S901.

[0513] S909, SMF sends N3 tunnel information to AMF.

[0514] S910, AMF sends N3 tunnel information to the second RAN2.

[0515] S911, the second RAN sends a resource release message to the first RAN.

[0516] As another possible implementation, the rules on the first intermediate user plane network element are modified first, redirecting data packets to the first PSA UPF via N9. Matching is then performed again on the first PSA UPF, and point-to-point communication is enabled on the second intermediate user plane network element. Compared to the above implementation, this approach ensures data transmission continuity while reusing the ground detection reporting and on-board forwarding process, reducing the operational complexity of the SMF (data packets can be forwarded by the first PSA UPF first, and then by the second intermediate user plane network element after configuration). Figure 9 The method flow shown also includes the following steps: Specifically, the SMF determines the second intermediate user plane network element as the handover target based on the N3 tunnel information carried in the handover request in step S901. For example, the second intermediate user plane network element and the second RAN are deployed on the same satellite or the satellite where the second intermediate user plane network element is located provides a backhaul link for the second RAN.

[0517] S912, SMF sends uplink N9 tunnel information and downlink N3 tunnel information to the second intermediate user plane network element.

[0518] The SMF sends an N4 session modification request to the second intermediate user plane network element, carrying uplink N9 tunnel information and downlink N3AN tunnel information, requesting the allocation of downlink N3 and N9 tunnel information; the second intermediate user plane network element returns the downlink N3 and N9 tunnel information.

[0519] S913, the SMF sends an N4 session modification request to the first PSA UPF, carrying the downlink N9 tunnel information allocated by the second intermediate user plane network element obtained in step S912; the first PSA UPF returns a response.

[0520] S914, the SMF sends an N4 session modification request to the first intermediate user plane network element to modify the PDR and FAR so that the data packets from the N3 interface can be forwarded to the first PSA UPF, and the first PSA UPF can process the forwarding of the data packets.

[0521] S915, SMF sends message #2 (e.g., Nsmf_PDUSession_UpdateSMContextResponse) to AMF, carrying the uplink N3 CN tunnel information obtained in step S912.

[0522] S916, AMF sends uplink N3 CN tunnel information to the second RAN.

[0523] S917, the second RAN sends a resource release message to the first RAN.

[0524] When the first UE and the second UE communicate again and generate data packets, the point-to-point communication is successfully re-matched, and the SMF creates an Nx-based forwarding mechanism. Figure 8 Steps S824 to S826 shown, for example, establishing an Nx tunnel between the first intermediate user plane network element and the second intermediate user plane network element to facilitate data forwarding, will not be described in detail here.

[0525] It should be understood that the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0526] It should also be understood that, in the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0527] For example, Figure 8 The illustrated embodiments and Figure 9 The illustrated embodiments can be combined to establish point-to-point communication and to switch the network element providing forwarding services when there is a handover requirement. For example, when the first access network device accessed by the first terminal device is switched to the second access network device, the session management network element determines whether the session set to be switched includes the first session based on the session set to be switched. If the session set includes the first session, the session management network element determines the third network element to forward the data of the first session based on the first information.

[0528] It should also be understood that in some of the above embodiments, the examples are mainly based on devices in existing network architectures (such as network devices, terminal devices, etc.). It should be understood that the specific form of the device is not limited in the embodiments of this application. For example, any device that can achieve the same function in the future is applicable to the embodiments of this application.

[0529] It is understood that in the above-described method embodiments, the methods and operations implemented by devices (such as the aforementioned network devices, terminal devices, etc.) can also be implemented by components of the devices (such as chips or circuits).

[0530] The above, combined with Figures 7 to 9 The communication method provided in the embodiments of this application is described in detail. The above communication method is mainly introduced from the perspective of interaction between various network elements. It is understood that each network element includes the corresponding hardware structure and / or software module to perform the above functions in order to achieve the above functions.

[0531] Those skilled in the art will recognize that, based on the units and algorithm steps described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0532] The following, combined with Figure 10 and Figure 11 This application provides a detailed description of the communication device provided in its embodiments. It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be found in the above method embodiments. For brevity, some content is omitted.

[0533] This application embodiment can divide the transmitting or receiving device into functional modules according to the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the division of functional modules according to each function as an example.

[0534] Figure 10 This is a schematic block diagram of the device 1000 provided in an embodiment of this application. The device 1000 includes a transceiver unit 1010 and a processing unit 1020. The transceiver unit 1010 can implement corresponding communication functions, and the processing unit 1020 is used for data processing. The transceiver unit 1010 can also be referred to as a communication interface or a communication unit. When the transceiver unit 1010 implements the function of acquiring information, it can also be referred to as an acquisition unit.

[0535] Optionally, the device 1000 may further include a storage unit, which can be used to store instructions and / or data, and the processing unit 1020 can read the instructions and / or data in the storage unit to enable the device to implement the aforementioned method embodiments.

[0536] The device 1000 can be used to perform the actions performed by the devices (such as the core network elements, access network devices, terminal devices, etc. mentioned above) in the above method embodiments. In this case, the device 1000 can be a device or a component that can be configured on the device. The transceiver unit 1010 is used to perform the transceiver-related operations of the device in the above method embodiments, and the processing unit 1020 is used to perform the processing-related operations of the device in the above method embodiments.

[0537] As a design feature, the device 1000 is used to perform the actions performed by the session management network element in the above method embodiments.

[0538] The transceiver unit 1010 is configured to receive first information from a first anchor user plane network element, wherein the first anchor user plane network element is the user plane network element anchored to the first session established by the first terminal device, wherein the first information includes the source address of the first data and / or the destination address of the first data, and the first data includes the data of the first session sent by the first terminal device to the second terminal device and / or the data sent by the second terminal device to the first terminal device; Processing unit 1020 is configured to determine, based on the first information, whether the first terminal device and the second terminal device use the same access network or the same backhaul network; When the first terminal device and the second terminal device use the same access network or the same backhaul network, the processing unit 1020 is further configured to determine a first network element for forwarding data of the first session.

[0539] The apparatus 1000 can implement the steps or processes corresponding to those executed by the session management network element in the method embodiment according to the embodiments of this application. The apparatus 1000 may include units for executing the methods executed by the session management network element in the method embodiment. Furthermore, each unit in the apparatus 1000 and the other operations and / or functions described above are respectively for implementing the corresponding processes of the method embodiment in the session management network element of the method embodiment.

[0540] Among them, when the device 1000 is used to perform Figure 7 When the method is in use, the transceiver unit 1010 can be used to execute the transceiver steps in the method, such as steps S710, S720 and S770; the processing unit 1020 can be used to execute the processing steps in the method, such as steps S740, S750 and S760.

[0541] When the device 1000 is used to perform Figure 8 When the method is executed, the transceiver unit 1010 can be used to execute the transceiver steps in the method, such as steps S803, S804, S805, S807, S808, S810, S811, S812, S816, S817, S818, S819, S821, S822, S824, and S826; the processing unit 1020 can be used to execute the processing steps in the method, such as steps S806, S809, and S825.

[0542] When the device 1000 is used to perform Figure 9When the method is in use, the transceiver unit 1010 can be used to execute the transceiver steps in the method, such as steps S902, S904, S906, S905, S907, S908, S909, S912, S913, S914, S915; the processing unit 1020 can be used to execute the processing steps in the method, such as step S903.

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

[0544] As an alternative design, the device 1000 is used to perform the actions performed by the first anchor point user plane network element in the above method embodiment.

[0545] The apparatus 1000 can implement the steps or processes corresponding to the first anchor user plane network element executed in the method embodiment according to the present application. The apparatus 1000 may include units for executing the method executed by the first anchor user plane network element in the method embodiment. Furthermore, each unit in the apparatus 1000 and the other operations and / or functions described above are respectively for implementing the corresponding processes of the method embodiment in the first anchor user plane network element of the method embodiment.

[0546] Processing unit 1020 is used to determine first information, wherein the first anchor user plane network element is the anchor user plane network element to which the first session established by the first terminal device is anchored; The transceiver unit 1010 is used to send the first information to the session management network element, wherein the first information includes the source address of the first data and / or the destination address of the first data, the first data includes the data of the first session sent by the first terminal device to the second terminal device and / or the data sent by the second terminal device to the first terminal device, and the first information is used to determine whether the first terminal device and the second terminal device use the same access network or the same backhaul network.

[0547] Among them, when the device 1000 is used to perform Figure 7 When the method is in use, the transceiver unit 1010 can be used to execute the transceiver steps in the method, such as steps S710 and S720; the processing unit 1020 can be used to execute the processing steps in the method, such as step S730.

[0548] When the device 1000 is used to perform Figure 8 When the method is in use, the transceiver unit 1010 can be used to execute the transceiver steps in the method, such as steps S807, S808, S819, S821, and S824; the processing unit 1020 can be used to execute the processing steps in the method, such as step S820.

[0549] When the device 1000 is used to perform Figure 9When the method is in use, the transceiver unit 1010 can be used to execute the transceiver steps in the method, such as steps S904, S907, and S913; the processing unit 1020 can be used to execute the processing steps in the method.

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

[0551] As another design, the device 1000 is used to perform the actions performed by the first network element in the above method embodiment.

[0552] The apparatus 1000 can implement steps or processes corresponding to those executed by the first network element in the method embodiment according to the present application. The apparatus 1000 may include units for executing the method executed by the first network element in the method embodiment. Furthermore, each unit in the apparatus 1000 and the other operations and / or functions described above are respectively for implementing the corresponding processes of the method embodiment in the first network element of the method embodiment.

[0553] Transceiver unit 1010 is used to receive packet detection rules (PDR) and packet forwarding rules (FAR) from session management network elements; The processing unit 1020 is used to forward the data of the first session according to the PDR and FAR, wherein the first network element is the network element that forwards the data of the first session established by the first terminal device.

[0554] Among them, when the device 1000 is used to perform Figure 7 When the method is in use, the transceiver unit 1010 can be used to execute the transceiver steps in the method, such as step S770; the processing unit 1020 can be used to execute the processing steps in the method.

[0555] When the device 1000 is used to perform Figure 8 When the method is in use, the transceiver unit 1010 can be used to execute the transceiver steps in the method, such as steps S810, S811, S817, S818, and S826; the processing unit 1020 can be used to execute the processing steps in the method.

[0556] When the device 1000 is used to perform Figure 9 When the method is in use, the transceiver unit 1010 can be used to execute the transceiver steps in the method, such as steps S905, S908, and S914; the processing unit 1020 can be used to execute the processing steps in the method.

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

[0558] The processing unit 1020 in the above embodiments can be implemented by at least one processor or processor-related circuitry. The transceiver unit 1010 can be implemented by a transceiver or transceiver-related circuitry. The storage unit can be implemented by at least one memory.

[0559] like Figure 11 As shown, this application embodiment also provides an apparatus 1100. The apparatus 1100 includes a processor 1110 and may further include one or more memories 1120. The processor 1110 is coupled to the memory 1120, which stores computer programs or instructions and / or data. The processor 1110 executes the computer programs or instructions and / or data stored in the memory 1120, causing the methods in the above method embodiments to be executed. Optionally, the apparatus 1100 includes one or more processors 1110.

[0560] Alternatively, the memory 1120 may be integrated with the processor 1110 or set separately.

[0561] Optionally, such as Figure 11 As shown, the device 1100 may further include a transceiver 1130 for receiving and / or transmitting signals. For example, a processor 1110 is used to control the transceiver 1130 to receive and / or transmit signals.

[0562] As one approach, the device 1100 is used to implement the operations performed by the devices (such as the aforementioned core network elements, access network devices, terminal devices, etc.) in the above method embodiments.

[0563] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by devices (such as the aforementioned core network elements, access network devices, terminal devices, etc.) in the above method embodiments.

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

[0565] This application also provides a computer program product containing instructions that, when executed by a computer, cause the computer to implement the methods described in the above method embodiments, which are executed by devices (such as the aforementioned core network elements, access network devices, terminal devices, etc.).

[0566] This application also provides a communication system, which includes the devices described in the above embodiments (such as the core network elements, access network devices, terminal devices, etc.).

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A communication method applied to a Session Management Function (SMF) network element, characterized in that, include: Receive first information from the first Protocol Data Unit Session Anchor Point User Plane Function (PSA UPF) network element, wherein the first PSA UPF network element is the UPF network element anchored to the first Protocol Data Unit (PDU) session established by the first terminal device, wherein the first PSA UPF network element is located on the ground, the first information includes the destination address of the first data, and the first data includes the data of the first PDU session sent by the first terminal device to the second terminal device. Based on the first information, it is determined that the first terminal device and the second terminal device use the same backhaul network; as well as A first network element is determined for forwarding data from the first PDU session, and the first network element is located on a satellite.

2. The method according to claim 1, characterized in that, The step of determining that the first terminal device and the second terminal device use the same backhaul network based on the first information includes: The second data network access identifier (DNAI) corresponding to the session of the second terminal device is determined based on the address of the second terminal device. Based on the first DNAI and the second DNAI corresponding to the first PDU session, it is determined that the first terminal device and the second terminal device use the same backhaul network.

3. The method according to claim 1 or 2, characterized in that, The first network element determined for forwarding data of the first PDU session includes: Determine whether to insert the first network element or use the first network element that has already been inserted.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: A Packet Detection Rule (PDR) and a Packet Forwarding Rule (FAR) are sent to the first network element. The PDR and FAR are used to instruct the first network element to forward the data of the first PDU session.

5. The method according to any one of claims 1-4, characterized in that, The first network element includes a second PSA UPF network element, which is a UPF network element other than the first PSA UPF network element to which the first PDU session is anchored.

6. The method according to any one of claims 1-4, characterized in that, The first network element includes an uplink classifier function UL CL UPF network element and a local PSA UPF network element. The UL CL UPF network element is used to send the data of the first PDU session to the local PSA UPF network element, and the local PSA UPF network element is used to send the data of the first PDU session to the second terminal device.

7. The method according to any one of claims 1-6, characterized in that, The first network element is used to implement local forwarding of data from the first PDU session or forwarding via the N19 interface.

8. The method according to any one of claims 1-7, characterized in that, The backhaul network includes satellite backhaul links.

9. The method according to claim 8, characterized in that, The satellites include geostationary GEO satellites.

10. The method according to any one of claims 1-9, characterized in that, The destination address of the first data includes the IP address of the second terminal device.

11. The method according to any one of claims 1-10, characterized in that, The first terminal device and the second terminal device belong to a fifth-generation virtual network (5G VN) group.

12. A communication method applied to a first Protocol Data Unit Session Anchor Point User Plane Function (PSA) UPF network element, characterized in that, include: First information is determined, the first information includes the destination address of the first data, the first data includes the data of the first protocol data unit (PDU) session sent by the first terminal device to the second terminal device; wherein, the first PSA UPF network element is the UPF network element anchored to the first protocol data unit (PDU) session established by the first terminal device, and the first PSA UPF network element is located on the ground; The first information is sent to the Session Management Function (SMF) network element, and the first information is used to determine that the first terminal device and the second terminal device use the same backhaul network.

13. The method according to claim 12, characterized in that, The backhaul network includes satellite backhaul links.

14. The method according to claim 13, characterized in that, The satellites include geostationary GEO satellites.

15. The method according to any one of claims 12-14, characterized in that, The destination address of the first data includes the IP address of the second terminal device.

16. The method according to any one of claims 12-15, characterized in that, The first terminal device and the second terminal device belong to a fifth-generation virtual network (5G VN) group.

17. A communication device, characterized in that, Used to perform the method according to any one of claims 1 to 16.

18. The communication device according to claim 17, characterized in that, The communication device includes a processor.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed, causes the device to perform the method as described in any one of claims 1 to 16.

20. A chip, characterized in that, include: A processor for retrieving and running a computer program from memory, causing a communication device on which the chip is mounted to perform the method as described in any one of claims 1 to 16.

21. The chip according to claim 20, characterized in that, The chip also includes the memory.

Images