A method of data transmission and a communication device

Abstract

The embodiment of the present application provides a data transmission method and communication device, the method comprises the following steps: a first terminal device acquires first information, the first information is used for a first network device to transmit first data to the first terminal device through a first communication path, and the first information comprises a first packet detection rule (PDR); the first terminal device sends a first message to a second network device through a second communication path, wherein the first message comprises the first information and first indication information, and the first indication information is used for indicating that the first data is transmitted through the first communication path and / or the second communication path. In the method, the transmission of the data through the direct connection path and the non-direct connection path can be realized at the same time, so that the transmission path between the remote terminal device and the data network has diversity, and the service demand can be dynamically met.

Description

[0001] The present application claims priority to the Chinese patent application No. 202111476011.3, filed on December 6, 2021, and entitled "A data transmission method", the whole content of which is incorporated herein by reference. TECHNICAL FIELD

[0002] Embodiments of the present application relate to the field of communication, and more particularly, to a data transmission method and a communication device. BACKGROUND

[0003] A remote user equipment (UE) can communicate with a data network (DN) through two paths. One is to communicate based on a Uu interface, that is, the remote UE accesses an operator network (for example, a base station) directly, and communicates with the DN through the operator network, which can be referred to as a direct path. The other is to communicate based on a proximity-based services communication 5 (PC5) interface, that is, the remote UE accesses the operator network through a relay, and then communicates with the DN through the operator network, which can be referred to as an indirect path.

[0004] In the prior art, the remote UE uses a single path (direct path or indirect path) for data transmission, which cannot dynamically meet the transmission requirements of services, such as latency or quality, etc.

[0005] Therefore, there is an urgent need for a data transmission method that uses two paths for data transmission to meet the transmission requirements of user services. SUMMARY

[0006] Embodiments of the present application provide a data transmission method and a communication device, which can indicate the path of a quality of service (QoS) flow, so that the transmission path between the remote terminal device and the data network has diversity, and can dynamically meet the service requirements.

[0007] In a first aspect, a data transmission method is provided, which can be executed by a first terminal device, or can also be executed by a chip or circuit configured in the first terminal device, and the present application does not limit this. The following is described by taking the execution by the first terminal device as an example.

[0008] The method comprises: a first terminal device obtaining first information, the first information being used for a first network device to transmit first data to the first terminal device through the first communication path, the first information comprising a first packet detection rule (PDR); and the first terminal device sending a first message to a second network device through a second communication path, the first message comprising the first information and first indication information, the first indication information being used for indicating that the first data is transmitted through the first communication path and / or the second communication path.

[0009] According to the above scheme, the first terminal device can obtain the first information and send the first information to the first network device through the second communication path, so as to enable the first network device to transmit the first data to the first terminal device through the first communication path and / or the second communication path, to realize data transmission through the direct connection path and the non-direct connection path at the same time, and to make the transmission path between the remote terminal device and the data network have diversity, thereby dynamically meeting the service requirement.

[0010] With reference to the first aspect, in some implementations of the first aspect, the first terminal device sends a first request message to the second terminal device, the first request message being used for requesting to establish a first QoS flow on the first communication path, the first request message comprising second indication information, the second indication information being used for obtaining the first information; and the first terminal device receives the first information from the second terminal device.

[0011] In the present application, the first communication path in the above scheme is a non-direct connection path.

[0012] It can be understood that the first information is QoS flow information of the first QoS flow established on the non-direct connection path.

[0013] With reference to the first aspect, in some implementations of the first aspect, the first information is obtained by the first terminal device in establishing a first QoS flow on the first communication path.

[0014] In this scheme, the first communication path is a direct connection path.

[0015] It can be understood that the first information is QoS flow information obtained in establishing a first QoS flow on the direct connection path.

[0016] With reference to the first aspect, in some implementations of the first aspect, the first information further comprises first QoS flow information on the first communication path, the first QoS flow information comprising an identifier of the second terminal device, an identifier QFI of the first QoS flow, and an identifier of a PDU session corresponding to the first QoS flow.

[0017] With reference to the first aspect, in some implementations of the first aspect, the first information further includes third indication information, the third indication information being used to indicate performing reliability transmission or load balancing transmission.

[0018] With reference to the first aspect, in some implementations of the first aspect, the first communication path is a communication path in which the first terminal device connects the first network device through the second terminal device, or the first communication path is a communication path in which the first terminal device directly connects the first network device.

[0019] With reference to the first aspect, in some implementations of the first aspect, the first communication path includes at least one QoS flow, the first QoS flow information includes a PDR corresponding to the first QoS flow, and the first QoS flow is one of the at least one QoS flow.

[0020] The second aspect provides a data transmission method, which can be executed by a first network device or a chip or circuit configured in the first network device, and the present application does not limit this. Hereinafter, the execution by the first network device is taken as an example for description.

[0021] The method includes the following steps: the first network device receives first information and second information, the first information being used for the first network device to transmit data to a first terminal device through a first communication path, and the second information being used for the first network device to transmit data to the first terminal device through a second communication path; and the first network device receives first data and transmits the first data to the first terminal device through the first communication path and / or the second communication path.

[0022] According to the above scheme, the first network device can receive the first information and the second information, transmit data to the first terminal device through the first communication path according to the first information, and transmit data to the first terminal device through the second communication path according to the second information, so as to realize the transmission of data through the direct connection path and the non-direct connection path at the same time, and make the transmission path between the remote terminal device and the data network have diversity, and dynamically meet the service requirement.

[0023] With reference to the second aspect, in some implementations of the second aspect, the first network device transmits the first data to the first terminal device through the first communication path and / or the second communication path, including: the first network device determines a destination address and a source address according to the first information; and the first network device processes the first data according to the destination address and the source address, and transmits the processed first data.

[0024] With reference to the second aspect, in some implementations of the second aspect, the first communication path is a communication path through which the first terminal device receives data transmitted by the first network device via a second terminal device.

[0025] With reference to the second aspect, in some implementations of the second aspect, the first network device receives third indication information, the third indication information being used to indicate reliability transmission or load balancing transmission.

[0026] With reference to the second aspect, in some implementations of the second aspect, when the third indication information indicates reliability transmission, the first network device replicates IP packets of the first data and transmits the IP packets of the first data to the first terminal device via the first communication path and the second communication path respectively; or when the second indication information indicates load balancing transmission, the first network device splits the IP packets of the first data and transmits the IP packets of the first data to the first terminal device via the first communication path and the second communication path respectively.

[0027] With reference to the second aspect, in some implementations of the second aspect, the first network device determines to transmit the first data to the first terminal device via the first communication path and / or the second communication path according to the third indication information; or the first network device determines to transmit the first data to the first terminal device via the first communication path and / or the second communication path according to the first information and the second information.

[0028] With reference to the second aspect, in some implementations of the second aspect, the first network device transmits the first data to a third network device, and the third network device transmits the first data to the first terminal device via the first communication path.

[0029] With reference to the second aspect, in some implementations of the second aspect, the first communication path includes at least one QoS flow, the first QoS flow information includes a PDR corresponding to the first QoS flow, the first QoS flow is one of the at least one QoS flow, the second communication path includes at least one QoS flow, the second QoS flow information includes a PDR corresponding to the second QoS flow, and the second QoS flow is one of the at least one QoS flow.

[0030] With reference to the second aspect, in some implementations of the second aspect, the first network device encapsulates the first data into a GTP message, and transmits the GTP message to the third network device via a first tunnel, the GTP message including an identifier QFI of the first QoS flow, and the first tunnel being used for data transmission between the first network device and the third network device.

[0031] In a third aspect, a data transmission system is provided, comprising: a first UPF, a first AMF, a second UPF, a second AMF, a first SMF, and a second SMF, the first AMF and the first SMF being network devices serving a first terminal device, the second AMF and the second SMF being network devices serving a second terminal device, the first UPF transmitting first data to the first terminal device through a first communication path and / or a second communication path, the second UPF transmitting the first data to the first terminal device through the second communication path; wherein the first AMF is configured to: receive, from the first terminal device and send, to the second AMF, a first message comprising first information and first indication information; receive, from the second AMF, an address of the second UPF and a first packet detection rule (PDR), the first PDR being a PDR corresponding to a first QoS flow on the first communication path; send, to the first SMF, the address of the second UPF, an identifier of the first QoS flow, and the first indication information; the second AMF is configured to: receive the first message; determine the address of the second UPF and the first PDR according to the first message; the first SMF is configured to: receive the address of the second UPF, the identifier of the first QoS flow, and the first indication information; send, to the first UPF, the first PDR, a second PDR, and the identifier of the first QoS flow according to the first indication information, the second PDR being a PDR corresponding to a second QoS flow on the second communication path; the first UPF is configured to: receive the first PDR, the second PDR, and the identifier of the first QoS flow; transmit first data to the first terminal device through the first communication path and / or the second communication path; the second UPF is configured to: transmit the first data to the first terminal device through the second communication path.

[0032] With reference to the third aspect, in some implementations of the third aspect, the first SMF is further configured to establish a first tunnel according to the address of the second UPF, the first tunnel being used for data transmission between the first UPF and the second UPF.

[0033] With reference to the third aspect, in some implementations of the third aspect, the first information comprises first QoS flow information on the first communication path, the first QoS flow information comprising an identifier of the second terminal device, an identifier of the first QoS flow (QFI), and an identifier of a PDU session corresponding to the first QoS flow.

[0034] With reference to the third aspect, in some implementations of the third aspect, the first AMF is further configured to determine the second AMF according to the identifier of the second terminal device.

[0035] In some implementations of the third aspect, the first message further includes third indication information, the third indication information being used to instruct the first UPF to perform reliability transmission or load balancing transmission.

[0036] In a fourth aspect, a device for data transmission is provided. The device can be a first terminal device, or a chip or circuit configured in the first terminal device, which is not limited in the present application.

[0037] The device includes: a processing unit configured to obtain first information, the first information being used for a first network device to transmit first data to the first terminal device through a first communication path, the first information including a first packet detection rule (PDR); and a transceiver configured to send a first message to a second network device through a second communication path, the first message including the first information and first indication information, the first indication information being used to instruct to transmit the first data through the first communication path and / or the second communication path.

[0038] In some implementations of the fourth aspect, the transceiver is specifically configured to send a first request message to a second terminal device, the first request message being used to request to establish a first QoS flow on the first communication path, the first request message including second indication information, the second indication information being used to obtain the first information; and receive the first information from the second terminal device.

[0039] In some implementations of the fourth aspect, the first information is obtained by the first terminal device in establishing the first QoS flow on the first communication path.

[0040] In some implementations of the fourth aspect, the first information further includes first QoS flow information on the first communication path, the first QoS flow information including an identifier of the second terminal device, an identifier QFI of the first QoS flow, and an identifier of a PDU session corresponding to the first QoS flow.

[0041] In some implementations of the fourth aspect, the first information further includes third indication information, the third indication information being used to instruct to perform reliability transmission or load balancing transmission.

[0042] In some implementations of the fourth aspect, the first communication path is a communication path through which the first terminal device connects the first network device through the second terminal device, or the first communication path is a communication path through which the first terminal device directly connects the first network device.

[0043] In some embodiments of the fourth aspect, the first communication path comprises at least one QoS flow, and the first QoS flow information comprises a PDR corresponding to the first QoS flow, and the first QoS flow is one of the at least one QoS flow.

[0044] In a fifth aspect, a device for data transmission is provided. The device can be a first network device, or a chip or circuit configured in the first network device, which is not limited in the present application.

[0045] The device comprises a transceiver configured to receive first information and second information, the first information being used for the first network device to transmit data to a first terminal device via a first communication path, and the second information being used for the first network device to transmit data to the first terminal device via a second communication path; and the transceiver is further configured to receive first data and transmit the first data to the first terminal device via the first communication path and / or the second communication path.

[0046] In some embodiments of the fifth aspect, the device further comprises a processing unit configured to determine a destination address and a source address according to the first information, process the first data according to the destination address and the source address, and transmit the processed first data.

[0047] In some embodiments of the fifth aspect, the first communication path is a communication path via which the first terminal device receives data transmitted by the first network device through a second terminal device.

[0048] In some embodiments of the fifth aspect, the transceiver is further configured to receive third indication information, the third indication information being used to indicate reliability transmission or load balancing transmission.

[0049] In some embodiments of the fifth aspect, when the third indication information indicates reliability transmission, the processing unit is specifically configured to copy IP packets of the first data, and the transceiver is specifically configured to transmit the IP packets of the first data to the first terminal device via the first communication path and the second communication path respectively; or when the second indication information indicates load balancing transmission, the processing unit is specifically configured to split the IP packets of the first data, and the transceiver is specifically configured to transmit the IP packets of the first data to the first terminal device via the first communication path and the second communication path respectively.

[0050] In some implementations of the fifth aspect, the processing unit is further configured to: determine, according to the third indication information, to send the first data to the first terminal device via the first communication path and / or the second communication path; or determine, according to the first information and the second information, to send the first data to the first terminal device via the first communication path and / or the second communication path.

[0051] In some implementations of the fifth aspect, the transceiver is further configured to send the first data to a third network device, and send, by the third network device, the first data to the first terminal device via the first communication path.

[0052] In some implementations of the fifth aspect, the first communication path includes at least one QoS flow, the first QoS flow information includes a PDR corresponding to the first QoS flow, the first QoS flow is one of the at least one QoS flow, the second communication path includes at least one QoS flow, the second QoS flow information includes a PDR corresponding to the second QoS flow, and the second QoS flow is one of the at least one QoS flow.

[0053] In some implementations of the fifth aspect, the transceiver is further configured to: receive an identifier QFI of the first QoS flow, and send the first data to a third network device, specifically including: encapsulating, by the transceiver, the first data into a GTP message, and sending, by the transceiver, the GTP message to the third network device via a first tunnel, the GTP message including the identifier QFI of the first QoS flow, and the first tunnel being used for data transmission between the first network device and the third network device.

[0054] In a sixth aspect, a processor is provided, configured to execute the method in any of the above aspects.

[0055] For the sending and obtaining / receiving operations of the processor, if no special description is provided, or if it does not contradict the actual role or inherent logic in the related description, it can be understood as the processor output and receive, input operations, or can be understood as the sending and receiving operations performed by the radio frequency circuit and the antenna, which is not limited in the present application.

[0056] In a seventh aspect, a communication apparatus is provided, including: a memory configured to store a program; and at least one processor configured to execute the computer program or instructions stored in the memory to perform the method in any of the above aspects or the implementation manner thereof.

[0057] In an implementation form, the apparatus is a first terminal device, a second terminal device, a first network device, or a second network device.

[0058] In another implementation form, the apparatus is a chip, a chip system, or a circuit for the first terminal device, the second terminal device, the first network device, or the second network device.

[0059] In an eighth aspect, a computer readable storage medium storing program codes for execution by an apparatus is provided. The program codes include codes for performing the method provided in any of the aspects or implementation forms.

[0060] In a ninth aspect, a computer program product containing instructions which, when the computer program product is executed on a computer, cause the computer to carry out the method provided in any of the aspects or implementation forms.

[0061] In a tenth aspect, a chip is provided. The chip includes a processor and a communication interface. The processor reads instructions stored on a memory through the communication interface and performs the method provided in any of the aspects or implementation forms.

[0062] Optionally, as an implementation form, the chip further includes a memory. The memory stores a computer program or instructions. The processor is configured to execute the computer program or instructions stored on the memory. When the computer program or instructions are executed, the processor is configured to perform the method provided in any of the aspects or implementation forms.

[0063] In an eleventh aspect, a communication system is provided. The communication system includes the first terminal device, the second terminal device, the first network device, and the second network device described above. BRIEF DESCRIPTION OF DRAWINGS

[0064] Figure 1 A schematic diagram of a communication system architecture suitable for embodiments of the application is shown.

[0065] Figure 2 A schematic diagram of an application architecture of a communication system suitable for embodiments of the application is shown.

[0066] Figure 3 A protocol stack architecture for user plane data transmission by a remote UE through a non-direct path is shown.

[0067] Figure 4 A schematic flow diagram of user plane data transmission by a remote UE using a non-direct path transmission mode is shown.

[0068] Figure 5 A schematic diagram of a data transmission method 500 provided by embodiments of the application is shown.

[0069] Figure 6 A variation diagram of a transmission path of data of a remote UE provided by an embodiment of the application is shown.

[0070] Figure 7 A diagram of a data transmission method 700 provided by an embodiment of the application is shown.

[0071] Figure 8 A diagram of a method for performing multiplexing by a UPF provided by an embodiment of the application is shown.

[0072] Figure 9 A diagram of a data transmission method 900 provided by an embodiment of the application is shown.

[0073] Figure 10 A diagram of a data transmission method 1000 provided by an embodiment of the application is shown.

[0074] Figure 11 A diagram of a data transmission method 1100 provided by an embodiment of the application is shown.

[0075] Figure 12 A diagram of a data transmission apparatus 1200 provided by an embodiment of the application is shown.

[0076] Figure 13 A diagram of a data transmission apparatus 1300 provided by an embodiment of the application is shown. DETAILED DESCRIPTION

[0077] The technical solutions in the application will be described below with reference to the drawings.

[0078] The technical solutions provided in the present application can be applied to various communication systems, for example, a 5th generation (5G) or new radio (NR) system, a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, and the like. The technical solutions provided in the present application can also be applied to future communication systems, such as a 6th generation mobile communication system. The technical solutions provided in the present application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and an internet of things (IoT) communication system or other communication systems.

[0079] First, a network architecture suitable for the present application is briefly introduced as follows.

[0080] As an example, Figure 1 A schematic diagram of a network architecture is shown.

[0081] As Figure 1As shown, the network architecture takes the 5th generation system (5GS) as an example. The network architecture can include but is not limited to: a network slice selection function (NSSF), an authentication server function (AUSF), a unified data management (UDM), a network exposure function (NEF), a network repository function (NRF), a policy control function (PCF), an application function (AF), an access and mobility management function (AMF), a session management function (SMF), a user equipment (UE), a wireless access network device, a user plane function (UPF), and a data network (DN).

[0082] Among them, the DN can be the Internet; the NSSF, AUSF, UDM, NEF, NRF, PCF, AF, AMF, SMF, and UPF belong to network elements in the core network, and since Figure 1 Taking the 5th generation system as an example, the core network can be referred to as a 5G core network (5GC or 5GCN).

[0083] The following briefly introduces each network element shown in Figure 1

[0084] 1. UE (including UE1 and UE2 in Figure 1 ): can be referred to as a terminal device, an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device.

[0085] ​The terminal device can be a device providing voice / data to a user, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc. At present, some examples of terminals are: mobile phone, tablet computer, notebook computer, palm computer, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, wearable device, terminal device in a 5G network, or terminal device in a future evolved public land mobile network (PLMN), etc. The embodiments of the present application are not limited thereto.

[0086] By way of example and not limitation, in the embodiments of the present application, the terminal device can also be a wearable device. The wearable device can also be referred to as a wearable smart device, which is a general term for devices that are designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing, and shoes. The wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. The wearable device is not only a hardware device, but also a device that realizes powerful functions through software support and data interaction and cloud interaction. The general wearable smart device includes a device with full functions and large size, which can realize complete or partial functions without relying on a smart phone, such as a smart watch or smart glasses, and a device that focuses on a certain application function and needs to cooperate with other devices such as a smart phone, such as various smart wristbands and smart jewelry for monitoring vital signs.

[0087] In addition, in the embodiments of the present application, the terminal device can also be a terminal device in an IoT system. IoT is an important part of future information technology development, and its main technical feature is to connect objects through communication technology and network, so as to realize the intelligent network of man-machine interconnection and object-object interconnection.

[0088] It should be noted that the terminal device and the access network device can communicate with each other by using a certain air interface technology (such as NR or LTE technology, etc.). The terminal device and the terminal device can also communicate with each other by using a certain air interface technology (such as NR or LTE technology, etc.).

[0089] In the embodiments of the present application, the device for implementing the function of the terminal device can be a terminal device, or a device capable of supporting the terminal device to implement the function, such as a chip system or a chip, which can be installed in the terminal device. In the embodiments of the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices.

[0090] 2, (wireless) access network ((radio) access network, (R) AN) device: can provide access to a communication network for authorized users in a specific area, which can specifically include a wireless network device in a third generation partnership project (3rd generation partnership project, 3GPP) network, and can also include an access point in a non-3GPP (non-3GPP) network. The following is for convenience. AN device is used to represent.

[0091] AN devices can employ different radio access technologies. There are currently two types of radio access technologies: 3GPP radio access technologies (e.g., radio access technologies employed in third generation (3G), fourth generation (4G), or 5G systems) and non-3GPP radio access technologies. 3GPP radio access technologies refer to radio access technologies that conform to 3GPP standard specifications, for example, access network devices in 5G systems are referred to as next generation Node Base stations (gNBs) or RAN devices. Non-3GPP radio access technologies can include air interface technologies represented by access points (APs) in wireless fidelity (WiFi), worldwide interoperability for microwave access (WiMAX), code division multiple access (CDMA), etc. AN devices can allow terminal devices and 3GPP core networks to be interconnected and communicate with each other using non-3GPP technologies.

[0092] AN devices can be responsible for functions such as radio resource management on the air interface side, quality of service (QoS) management, data compression, and encryption. AN devices provide access services for terminal devices, and thus complete the forwarding of control signals and user data between terminal devices and core networks.

[0093] The AN device may include, but is not limited to, a macro base station, a micro base station (also referred to as a small station), a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (for example, a home evolved NodeB or home Node B, HNB), a baseband unit (BBU), an AP in a WiFi system, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), and the like, and can also be a gNB or a transmission point (TRP or TP) in a 5G (for example, NR) system, 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 a transmission point, such as a distributed unit (DU), or a base station in a next-generation communication 6G system, and the like. The embodiments of the present application do not limit the specific technology and specific device form adopted by the AN device.

[0094] 3. AMF: mainly used for access control, mobility management, attachment and detachment, and the like.

[0095] 4. SMF: mainly used for user plane network element selection, user plane network element redirection, internet protocol (IP) address allocation of a terminal device, and session establishment, modification and release, and QoS control.

[0096] 5. UPF: mainly used for receiving and forwarding of user plane data. For example, the UPF can receive user plane data from a DN and send the user plane data to a terminal device through an AN device. The UPF can also receive user plane data from a terminal device through an AN device and forward the user plane data to a DN.

[0097] 6. NEF: mainly used for securely exposing services and capabilities provided by 3GPP network functions to the outside.

[0098] 7. PCF: mainly used for a unified policy framework for guiding network behavior, and providing policy rule information for control plane network elements (for example, AMF, SMF, and the like).

[0099] 8. AF: mainly used for providing services to a 3GPP network, such as interacting with a PCF for policy control, and the like.

[0100] 9. Network slice selection function (NSSF): mainly used for network slice selection.

[0101] 10. UDM: Primarily used for UE subscription data management, including UE identifier storage and management, UE access authorization, etc.

[0102] 11. DN: Primarily used by operators to provide data services to UEs. Examples include the Internet, third-party service networks, and IP Multimedia Service (IMS) networks.

[0103] 12. AUSF: Primarily used for user authentication, etc.

[0104] 13. NRF: Primarily used to store network functional entities and their descriptions of the services they provide.

[0105] exist Figure 1 In the network architecture shown, network elements can communicate via interfaces. For example, UE2 connects to the AN device via the Radio Resource Control (RRC) protocol, and the UE and AN device communicate using the Uu interface. UE1 and UE2 communicate via the PC5 interface, which can be used for UE discovery and data and signaling transmission between UEs. Furthermore, in... Figure 1 In the diagram, N1 is the interface between UE2 and AMF; N2 is the interface between (R)AN and AMF, used for sending NAS messages, etc.; N3 is the interface between RAN and UPF, used for transmitting user plane data, etc.; N4 is the interface between SMF and UPF, used for transmitting information such as tunnel identification information for N3 connection, data buffer indication information, and downlink data notification messages, etc.; N6 is the interface between UPF and DN, used for transmitting user plane data, etc.; and N11 is the interface between AMF and SMF.

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

[0107] It should also be understood that Figure 1The AMF, SMF, UPF, PCF, UDM, NSSF, AUSF, and the like functions or network elements shown in the middle can be understood as network elements for implementing different functions, for example, can be combined into a network slice on demand. These network elements can be independent devices, can be integrated into the same device to implement different functions, or can be network elements in a hardware device, or can be software functions running on a dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform), and the specific form of the network elements is not limited in the present application.

[0108] It should also be understood that the above naming is only defined for the convenience of distinguishing different functions and should not constitute any limitation on the present application. The present application does not exclude the possibility of using other names in 6G networks and other future networks. For example, in 6G networks, some or all of the above network elements can use the terms in 5G, or other names, etc. For the convenience of understanding the embodiments of the present application, the terms involved in the present application are briefly explained.

[0109] 1. Direct path: the terminal device directly accesses the access network device, that is, in the direct path, the terminal device and the access network device directly establish a connection and communicate, without passing through other devices (for example, relay devices).

[0110] It should be understood that after the terminal device directly accesses the access network device in the direct path, data transmission is performed with the data network through the access network device and the core network device.

[0111] The direct path can also be referred to as a direct link.

[0112] 2. Indirect path: the terminal device accesses the access network device through a relay device, that is, in the indirect path, the terminal device and the access network device establish a connection and communicate through one or more relay devices. For example, the relay device is a relay UE, and the terminal device is a remote UE, in which case the remote UE establishes a connection with the relay UE, and the relay UE establishes a connection with the RAN, so that the remote UE can establish a connection with the RAN through the relay UE.

[0113] It should be understood that after the terminal device accesses the access network device through the relay device in the indirect path, data transmission is performed with the data network through the relay device, the access network device, and the core network device.

[0114] It should be noted that in the non-direct path, the connection mode between the terminal device and the relay device can be a connection mode in 3GPP, for example, a proximity-based services communication 5 (PC5) connection, or a connection mode in a short-distance communication technology, for example, a Bluetooth connection, a WiFi connection, and the like. In addition, when multiple relay devices are included on the non-direct path, the connection method between the terminal device and the relay device and the connection mode between any two relay devices can be the same or different.

[0115] The non-direct path can also be referred to as a non-direct link.

[0116] 3、Protocol data unit (PDU) session: The 5G core network (5GC) supports a PDU connection service. The PDU connection service can refer to a service of exchanging PDU data packets between a terminal device and a DN. The PDU connection service is implemented by the terminal device initiating establishment of a PDU session. After a PDU session is established, a data transmission channel between the terminal device and the DN is established. In other words, the PDU session is at the UE level. Each terminal device can establish one or more PDU sessions.

[0117] As described above, the SMF is mainly used to be responsible for session management in a mobile network. A PDU session can be established, modified, or released between a terminal device and an SMF through NAS session management (SM) signaling.

[0118] In an embodiment of the present application, one PDU session can be identified by one PDU session identifier (PDU session ID).

[0119] 4、Quality of service (QoS) flow: QoS granularity in a PDU session. A QoS flow identifier (QFI) can be used to identify a QoS flow. A PDU session can include multiple QoS flows, and the QFI of each QoS flow is different. In other words, one QFI can be unique in one PDU session.

[0120] Furthermore, the QoS stream corresponding to a service can refer to the QoS stream used to transmit the data for that service. For example, when the data for that service is transmitted through the QoS stream in a PDU, that QoS stream can be called the QoS stream corresponding to that service. The service carried by the QoS stream can refer to the service transmitted through that QoS stream.

[0121] Furthermore, the QoS requirements of a QoS flow refer to the conditions that the QoS parameters corresponding to the QoS flow must meet. QoS parameters can include, but are not limited to, rate, latency, packet loss rate, priority, reliability, etc. For example, the QoS requirement for a QoS flow is that the rate in the QoS parameters corresponding to the QoS flow must meet 7 megabits per second (Mbps), that is, greater than or equal to 7 Mbps.

[0122] 5. Reliable transmission: When terminal devices and network devices transmit data simultaneously via direct and indirect paths, the network device copies the downlink data and transmits it via both the direct and indirect paths to ensure that the terminal device receives the data. This is called reliable transmission.

[0123] 6. Load-balanced transmission: When terminal devices and network devices transmit data simultaneously via direct and indirect paths, the network device divides the downlink data into two data packets and transmits them via the direct and indirect paths respectively, thereby balancing the load on the two paths. This is called load-balanced transmission.

[0124] Figure 2 A schematic diagram of the application architecture of a communication system according to an embodiment of this application is shown. Figure 2 As shown, this network architecture is... Figure 1 On the infrastructure shown, the 3GPP standard provides a scheme for one UE (e.g., a remote UE) to access the network through another UE (e.g., a relay UE). Figure 2 In this configuration, a remote UE can directly access the network. Specifically, this includes first directly accessing the AN (Access Provider Interface), then accessing the core network (5GC includes the remote UE's AMF, SMF, and UPF), and performing signaling and data transmission with the core network and DN. This transmission method can be called the direct path transmission method. Alternatively, a remote UE can also access the network through a relay UE. Specifically, this includes first accessing the AN through the relay UE, then accessing the core network through the AN, and finally performing signaling and data transmission with the remote UE's core network and DN. This transmission method can be called the indirect path transmission method.

[0125] It should be understood that Figure 2The relay UE in this context is a layer-3 UE-to-network relay.

[0126] Figure 3 This illustrates a protocol stack architecture for user plane data transmission when a remote UE uses a non-direct path transmission method. For example... Figure 3 As shown, the Protocol Data Unit (PDU) layer is used to transmit data generated by the application software (APP) between the remote UE and UPF. The Service Data Adaptation Protocol (SDAP) layer is used for mapping between Quality of Service (QoS) flows and Data Radio Bearers (DRBs). It should be understood that a QoS flow is a data transmission channel with QoS guarantees between the UE and UPF. A QoS flow consists of two parts: the DRB between the UE and the NG-RAN, and the N3 connection between the NG-RAN and the UPF. One or more QoS flows can share a single DRB connection, and SDAP is used to map QoS flows to the DRB. The DRB consists of two layers: the Packet Data Convergence Protocol (PDCP) layer and the Radio Link Control (RLC) layer. The PDCP layer is used for functions such as header compression, decompression, encryption / decryption, integrity protection, and integrity verification of user plane data. The PDCP layer is configured by RRC messages.

[0127] Media access control (MAC) is used to map logical channels and transport channels, and to combine MAC data from different logical channels into a single transport block. PHY stands for Physical Layer. The adaptation layer is used by the relay UE or NG-RAN to indicate to which remote UE a data packet contained in the relay UE's RLC belongs to, and which radio bearer it belongs to.

[0128] General packet radio service (GPRS) tunneling protocol-user (GTP-U) is a set of IP-based high-layer protocols located above the transmission control protocol / internet protocol (TCP / IP) and user data protocol / internet protocol (UDP / IP). The GTP-U message is used to carry user data between GTP-U bodies. L2 represents layer 2, and L1 represents layer 1.

[0129] As shown in FIG. 1, from the perspective of the NG-RAN, the DRB of the remote UE is composed of two parts: the PDCP layer between the NG-RAN and the remote UE, and the RLC layer between the NG-RAN and the relay UE. From the perspective of the remote UE, the DRB of the remote UE is composed of two parts: the PDCP layer between the NG-RAN and the remote UE, and the RLC layer between the NG-RAN and the relay UE. Figure 3

[0130] Specifically, the transmission process of uplink data is as follows: the APP layer of the remote UE generates data, the remote UE maps the data to a QoS flow at the PDU layer and sends the data to the Uu-SDAP layer, the data including a QoS flow identifier, the remote UE maps the QoS flow to a DRB according to the QoS flow identifier at the Uu SDAP layer, and sends the data of the QoS flow to the Uu PDCP layer corresponding to the DRB. The remote UE sends the data of the Uu PDCP layer to the protocol stack of the PC5 interface for processing, and sends the data to the relay UE through the PC5 interface. The relay UE parses the data of the Uu PDCP of the remote UE. The relay UE sends the data to the NG-RAN through the Uu interface with the NG-RAN. After receiving the data, the NG-RAN parses the data of the remote UE using the context of the remote UE, and sends the data of the remote UE to the UPF through the N3 interface with the UPF.

[0131] Similarly, the transmission process of downlink data is as follows: the NG-RAN receives data sent by the UPF to the remote UE, determines that the remote UE uses the relay UE for data transmission according to the context of the remote UE. After parsing the data, the relay UE sends the data to the remote UE through the PC5 interface between the relay UE and the remote UE, and the remote UE performs data parsing.

[0132] Figure 4 An illustrative flowchart of the remote UE using a non-direct path transmission mode for user plane data transmission is shown. As shown in FIG. 2, the remote UE receives data from the NG-RAN through the Uu interface, and the data is parsed by the remote UE. Figure 4 ​As shown, the method 400 includes the following steps.

[0133] S410, the operator network distributes authorization authentication and information provision of relay related services for the relay UE and the remote UE.

[0134] S420, optionally, the relay UE establishes a PDU session.

[0135] S430, the APP on the remote UE starts, determines that the APP can use layer 2 relay service through URSP, and then the remote UE performs a relay UE discovery procedure and selects a relay UE.

[0136] S440, the remote UE selects a relay UE and establishes a connection with the relay UE, and the relay UE determines whether a new PDU session needs to be established according to the correspondence between the RSC and the PDU session parameters.

[0137] S450, the relay UE performs an IP router function and allocates an IP address for the remote UE.

[0138] S460, if the remote UE has special QoS requirements, the remote UE can request to establish / modify a QoS flow; the remote UE sends a modification request message to the relay UE, carrying PC5 QoS parameters, the relay UE locally maps the PC5 QoS parameters into Uu QoS parameters, and judges whether a new QoS flow needs to be established, and if so, initiates a process of establishing a new QoS flow.

[0139] S470, the relay UE reports the information of the remote UE to the SMF, including Remote User ID and Remote UE info.

[0140] After the connection establishment is completed, the data of the remote UE is forwarded through the UPF, the NG-RAN and the relay UE.

[0141] In the current data transmission, the remote UE uses a certain fixed path (direct connection path or indirect connection path) to transmit the data of the service, for example, if the terminal device determines that the transmission path is a direct connection path, the terminal device initiates a PDU session request to the access network device, establishes a PDU session and a QoS flow of the direct connection path, and thereafter, the terminal device transmits data with the data network through the QoS flow of the direct connection path. Or, if the terminal device determines that the transmission path is an indirect connection path, the terminal device initiates a PDU session request to the access network device through the relay device, establishes a PDU session and a QoS flow of the indirect connection path, and thereafter, the terminal device transmits data with the data network through the QoS flow of the indirect connection path. This transmission method cannot dynamically meet the transmission requirements of the service, such as delay, communication quality or communication capacity, etc.

[0142] The application provides a data transmission method and device, so that the data transmission path between the terminal device and the data network has diversity, for example, data can be transmitted through a direct connection path and a non-direct connection path at the same time, and the service demand can be dynamically met, for example, the transmission rate is improved or the reliability of data transmission is guaranteed.

[0143] Figure 5 FIG. 5 is a schematic diagram of a data transmission method 500 provided by an embodiment of the application. The method 500 can include the following steps.

[0144] S510, the first terminal device acquires first information.

[0145] Specifically, the first terminal device can be an example of a remote UE.

[0146] The first information includes first QoS flow information of a first communication path, and the first information is used for the first network device to transmit first data to the first terminal device through the first communication path.

[0147] Specifically, the first network device can be a UPF, and the first data can be downlink transmission data received by the UPF.

[0148] As an example, the first communication path is a non-direct connection path, and the second communication path is a direct connection path. The first terminal device acquires the first QoS flow information of the non-direct connection path, and the first QoS flow information is used for the first network device to transmit the first data to the first terminal device through the non-direct connection path.

[0149] In a possible implementation, the first terminal device acquires the first QoS flow information of the non-direct connection path through the non-direct connection path. The non-direct connection path can be understood as that the first terminal device accesses the network device through a second terminal device. The second terminal device can be an example of a relay UE.

[0150] For example, the first terminal device sends a first request message to the second terminal device through a PC5 interface, the first request message is used to request to establish a first QoS flow on a non-direct connection path, the first request message includes second indication information, the second indication information is used to acquire the first information, and correspondingly, the second terminal device establishes the first QoS flow on the non-direct connection path and sends the first information to the first terminal device through the PC5 interface according to the second indication information. That is, the first terminal device receives the first information from the second terminal device.

[0151] For example, the first request message can be a "linkmodificationrequest (connection modification request) message".

[0152] For example, the first request message can also be an independent request message.

[0153] It can be understood that the second communication path is a direct connection path, which can be understood as a path in which the first terminal device directly accesses the network device, and the first terminal device establishes a second QoS flow on the direct connection path and obtains second information including information of the second QoS flow. However, it should be understood that the first terminal device directly accesses the network device, which means that data transmission with the network device does not need to be forwarded through a relay UE. In fact, there may be a relay of other network elements, which is not limited in the embodiments of the present application.

[0154] The first request message can also include, for example, “request PC5 QoS rule” and “request PC5 QoS parameter”. The destination address of the “packet filter” in the “request PC5 QoS rule” is the destination address of the packet filter of the QoS rule of the second QoS flow. The “request PC5 QoS parameter” is the same as the QoS parameter of the second QoS flow.

[0155] For example, the first information can include a packet detection rule PDR corresponding to the first QoS flow, and can also include the PC5 QoS parameter and the PC5 QoS rule of the newly created first QoS flow.

[0156] It should be understood that the packet detection rule PDR corresponding to the first QoS flow can also be understood as the packet filter corresponding to the PDR, or the destination address (IP address and port number) of the packet filter corresponding to the PDR.

[0157] For example, the first information can include an identifier of the second terminal device, an identifier QFI-1 of the first QoS flow, and an identifier of a PDU session corresponding to the first QoS flow.

[0158] The identifier (Relay UE ID) of the second terminal device can be a GUTI (Globally Unique Temporary UE Identity) or an S-TMSI (Serving-Temporary Mobile Subscriber Identity).

[0159] For example, the second terminal device can send the first information through a “linkmodificationaccept” message.

[0160] Exemplarily, the second indication information can be a "paired QoS flow indication", and the first terminal device can send the related information of the newly established first QoS flow to the first terminal device according to the "paired QoS flow indication".

[0161] As another example, the first communication path is a direct connection path, and the second communication path is a non-direct connection path. The first terminal device obtains the first QoS flow information of the direct connection path, and the first QoS flow information is used for the first network device to transmit the first data to the first terminal device through the direct connection path.

[0162] In a possible implementation, the first terminal device establishes a direct connection path and obtains the first QoS flow information of the direct connection path in the establishment process. The direct connection path can be understood as a path in which the first terminal device directly accesses the network device, but it should be understood that the direct connection of the first terminal device to the network device means that data transmission with the network device does not need to be forwarded through a relay UE, and in fact, there can be a relay of other network elements, which is not limited in the embodiments of the present application.

[0163] For example, the first terminal device triggers the establishment of the direct connection path, establishes the first QoS flow on the direct connection path, and obtains the first information.

[0164] Exemplarily, the first information includes a packet detection rule PDR corresponding to the first QoS flow on the direct connection path, and can also include PC5 QoS parameters and PC5 QoS rules of the newly established first QoS flow.

[0165] Exemplarily, the first information can include the identifier of the second terminal device, the identifier QFI-1 of the first QoS flow, and the identifier of the PDU session corresponding to the first QoS flow, and can also include PC5 QoS parameters and PC5 QoS rules of the newly established first QoS flow.

[0166] S520, the first terminal device sends a first message to the second network device.

[0167] Specifically, the first terminal device sends the first message to the second network device through the second communication path. The first message includes the first information and first indication information, and the first indication information is used to indicate that the first data is transmitted through the first communication path and / or the second communication path.

[0168] The second network device is an example of a core network element. For example, it can be an AMF or an SMF.

[0169] Correspondingly, the second network device receives the first message from the first terminal device.

[0170] As an example, the first communication path is a non-direct connection path, and the second communication path is a direct connection path. After the first terminal device obtains the information of the first QoS flow of the non-direct connection path, the first terminal device sends a first message to the first AMF (the AMF of the first terminal device) through the direct connection path, and carries the first information and first indication information in the first message, where the first indication information is used to indicate that the first data is transmitted through the first communication path and / or the second communication path.

[0171] As an example, the first message can also be an independent notification message.

[0172] As an example, the first message can be a PDU session modification request message or a PDU session establishment request message, or a non-access stratum (NAS) message.

[0173] For example, the first terminal device sends a PDU session modification request message to the first AMF through the uu interface of the direct connection path, and carries the first information and the first indication information in the request message, where the PDU session modification request message is used to request to modify the second QoS flow of the direct connection path.

[0174] As an example, the first information includes a packet detection rule (PDR) corresponding to the first QoS flow, and can also include a PC5 QoS parameter and a PC5 QoS rule of the newly created first QoS flow.

[0175] As an example, the first information includes an identifier of the second terminal device, an identifier QFI-1 of the first QoS flow, and an identifier of a PDU session corresponding to the first QoS flow.

[0176] The identifier (Relay UE ID) of the second terminal device can be a GUTI or an S-TMSI.

[0177] As an example, the first indication information can be a “paired QoS flow indication”.

[0178] It should be noted that the first indication information and the second indication information can both be “paired QoS flow indications”, but the second indication information is information of the PC5 interface, and the first indication information is information sent through the Uu interface, so the forms of the communication interfaces can be different, and the embodiments of the present application do not limit this.

[0179] Optionally, the first message can also carry third indication information, where the third indication information is used to indicate to perform reliability transmission or load balancing transmission.

[0180] As an example, the third indication information can be a “multi path rule”.

[0181] For example, the reliability transmission indication or the load balancing transmission indication is included in a "multi path rule".

[0182] The first indication information is used to indicate that the first data is transmitted through the first communication path and the second communication path. It can be understood that the downlink data can be transmitted to the remote UE through the direct connection path and the indirect connection path at the same time, so as to improve the efficiency of data transmission and ensure the reliability of data transmission.

[0183] When the first data is transmitted through only the first communication path or the second communication path, it can be understood that there are two paths, i.e., the direct connection path and the indirect connection path, between the remote UE and the DN, which can be used to transmit the downlink data. The direct connection path or the indirect connection path can be selected at will or according to the transmission requirement to transmit the downlink data, thereby improving the flexibility of data transmission.

[0184] As another example, the first communication path is a direct connection path, and the second communication path is an indirect connection path. After the first terminal device obtains the information of the first QoS flow of the direct connection path, the first terminal device sends a first message to the second AMF (the AMF of the second terminal device) through the indirect connection path, and carries the first information and the first indication information in the first message. The first indication information is used to indicate that the first data is transmitted through the first communication path and / or the second communication path.

[0185] For example, the first message can also be an independent notification message.

[0186] For example, the first message can be a PDU session modification request message or a PDU session establishment request message, etc. non-access stratum (NAS) message.

[0187] For example, the first terminal device sends a connection modification request message to the second terminal device through the PC5 interface of the indirect connection path. The first information and the first indication information are carried in the request message. The connection modification request message is used to request to modify the second QoS flow of the indirect connection path. The second terminal device sends a PDU session modification request message to the second AMF. The first information and the first indication information are carried in the request message. The PDU session modification request message is used to request to modify the second QoS flow of the indirect connection path.

[0188] For example, the first information includes a packet detection rule (PDR) corresponding to the first QoS flow, and can also include PC5 QoS parameters and PC5 QoS rules of the newly created first QoS flow.

[0189] Exemplarily, the first information comprises an identifier of the second terminal device, an identifier QFI-1 of the first QoS flow, and an identifier of a PDU session corresponding to the first QoS flow.

[0190] The identifier (Relay UE ID) of the second terminal device can be a GUTI or an S-TMSI.

[0191] Exemplarily, the first indication information can be a "paired QoS flow indication".

[0192] It should be noted that the first indication information and the second indication information can both be "paired QoS flow indications", but the second indication information is information for the PC5 interface, and the first indication information is information sent by the Uu interface, so the forms of the communication interfaces can be different, and the embodiments of the present application do not limit this.

[0193] Optionally, the first message can further carry third indication information, which is used to indicate reliability transmission or load balancing transmission.

[0194] Exemplarily, the third indication information can be a "multi path rule".

[0195] For example, the "multi path rule" comprises a reliability transmission indication or a load balancing transmission indication.

[0196] S530, the second network device sends the first information and the second information to the first network device.

[0197] Specifically, the second network device sends the first information and the second information to the first network device through the second communication path. The first information comprises first QoS flow information of the first communication path, and the second information comprises second QoS flow information of the second communication path. The first QoS flow information is used for the first network device to transmit downlink data to the first terminal device through the first communication path, and the second QoS flow information is used for the first network device to transmit downlink data to the first terminal device through the second communication path.

[0198] The first network device can be a first UPF of the first communication path, or a second UPF of the second communication path. The first UPF and the second UPF can be the same UPF, or can be different UPFs.

[0199] As an example, the first communication path is a non-direct connection path, and the second communication path is a direct connection path. After the first AMF receives the first message (a PDU session modification request message) from the first terminal device, the first AMF sends the first message to a first SMF (an SMF of the first terminal device). The first SMF modifies the second QoS flow of the direct connection path according to the first information and the first indication information carried in the PDU session modification request message, and sends the first information and second information to the first UPF.

[0200] For example, the first information includes a packet detection rule (PDR) corresponding to the first QoS flow on the non-direct connection path, and the second information includes a PDR corresponding to the second QoS flow on the direct connection path.

[0201] Optionally, the first message can also carry third indication information. The first terminal device can send the third indication information to the first network device through the second network device. The third indication information is used to instruct the first network device to perform reliable transmission or load balancing transmission.

[0202] Optionally, the third indication information can also be carried in the PDR corresponding to the second QoS flow. Embodiments of the present application are not limited in this regard.

[0203] In a possible implementation, a Multi-Path Rule ID field can be added to the packet detection rule (PDR) corresponding to the second QoS flow. Specifically, the Multi-Path Rule corresponding to the field includes a multi-path cooperative transmission indication and an outer IP header creation indication.

[0204] As another example, the first communication path is a direct connection path, and the second communication path is a non-direct connection path. After the second AMF receives the first message (a PDU session modification request message) from the first terminal device through the second terminal device, the second AMF sends the first message to a second SMF (an SMF of the second terminal device). The second SMF modifies the second QoS flow according to the first information and the first indication information carried in the PDU session modification request message, and sends the first information and second information to the first UPF.

[0205] For example, the first information includes a packet detection rule (PDR) corresponding to the first QoS flow on the direct connection path, and the second information includes a PDR corresponding to the second QoS flow on the non-direct connection path.

[0206] Optionally, the first message can also carry third indication information. The first terminal device can send the third indication information to the first network device through the second network device. The third indication information is used to instruct the first network device to perform reliable transmission or load balancing transmission.

[0207] Optionally, the third indication information can also be carried in the PDR corresponding to the second QoS flow, and embodiments of the present application do not limit this.

[0208] In a possible implementation, the PDR corresponding to the second QoS flow can be added with a Multi-PathRule ID field, and specifically, the Multi-Path Rule corresponding to the field includes the multi-path cooperative transmission indication and the Outer IP header creation indication.

[0209] As another example, the first communication path is a non-direct connection path, and the second communication path is a direct connection path. The first AMF sends a first message to the second AMF, obtains the address of the second UPF and the PDR corresponding to the first QoS flow through the second AMF, and sends them to the first SMF (the SMF of the first terminal device). The first SMF modifies the second QoS flow according to the first information and the first indication information carried in the first message, and sends the first information and the second information to the first UPF.

[0210] For example, the first information includes the PDR corresponding to the first QoS flow on the non-direct connection path, and the second information includes the PDR corresponding to the second QoS flow on the direct connection path.

[0211] Optionally, the first SMF can also send third indication information to the first UPF, and the third indication information is used to instruct the first network device to perform reliable transmission or load balancing transmission.

[0212] In a possible implementation, the PDR corresponding to the second QoS flow can be added with a Multi-PathRule ID field, and specifically, the Multi-Path Rule corresponding to the field includes the multi-path cooperative transmission indication, the Outer IP header creation indication, and the CN tunnel info.

[0213] As another example, the first communication path is a direct connection path, and the second communication path is a non-direct connection path. The second AMF receives a first message through the second terminal device, and sends the first message to the first AMF. The first UPF and the PDR corresponding to the first QoS flow of the direct connection path are obtained through the first AMF, and are sent to the second SMF (the SMF of the second terminal device). The second SMF modifies the second QoS flow on the non-direct connection path according to the first information and the first indication information carried in the first message, and sends the first information and the second information to the second UPF.

[0214] For example, the first information includes a packet detection rule (PDR) corresponding to a first QoS flow on a direct connection path, and the second information includes a PDR corresponding to a second QoS flow on a non-direct connection path.

[0215] Optionally, the second SMF can further send third indication information to the second UPF, where the third indication information is used to instruct the first network device to perform reliability transmission or load balancing transmission.

[0216] In a possible implementation, a Multi-Path Rule ID field can be added to a packet detection rule (PDR) corresponding to a second QoS flow, and specifically, the Multi-Path Rule ID field includes multi-path cooperative transmission indication, outer IP header creation indication, and CN tunnel info in the Multi-Path Rule corresponding to the Multi-Path Rule ID field.

[0217] S540, the first network device determines to perform multi-path transmission.

[0218] Specifically, the first network device receives first information and second information, the first network device receives first data, and determines to perform multi-path transmission on the first data according to the first information and the second information.

[0219] The process of performing multi-path transmission is specifically shown in the following embodiments.

[0220] Optionally, the first network device receives third indication information, determines to perform multi-path transmission on the first data according to the third indication information, and determines to specifically perform reliability transmission or load balancing transmission.

[0221] It should be noted that when the first UPF and the second UPF are different, the first network device needs to transmit data to a third network device when performing reliability transmission or load balancing transmission, and the third network device transmits the data to the terminal device through a non-direct connection path. The third network device can be the first UPF or the second UPF.

[0222] Figure 6 A variation diagram of a transmission path of data of a remote UE is shown. Wherein, Figure 6 (a) is a schematic diagram of a non-direct connection path and a direct connection path of a remote UE connected to the same UPF, and (b) is a schematic diagram of a non-direct connection path and a direct connection path of a remote UE connected to different UPFs. The following takes the first network device as the first UPF and the third network device as the second UPF as an example.

[0223] Wherein, Figure 6 (a) is a schematic diagram of a transmission path of data of a remote UE after S510 to S540, and (b) is a schematic diagram of a transmission path of data of a remote UE after S510 to S540.Figure 6 (a) is a schematic diagram of a data transmission path of the remote UE after S510 to S540, as shown in

[0224] wherein, Figure 6 (b) is a schematic diagram of a data transmission path of the remote UE after S510 to S540, as shown in Figure 6 (b) is a schematic diagram of a data transmission path of the remote UE after S510 to S540, as shown in

[0225] It should be noted that each implementation scenario of the embodiment shown in method 500 can be implemented alone or in combination with each other, and is not limited.

[0226] Figure 7 is a schematic diagram of a data transmission method 700 provided by an embodiment of the present application. The method 700 can be regarded as a specific implementation manner of the method 500, and the method 700 can include the following steps.

[0227] S710, the remote UE establishes a PDU session #1 and a QoS flow #1 on a direct connection path.

[0228] Specifically, the remote UE initiates establishment of the PDU session #1 on the direct connection path, so that data transmission between the remote UE and the DN can be realized. Wherein, the PDU session #1 includes the QoS flow #1 (an example of a second QoS flow).

[0229] The identifier of the QoS flow #1 can be QFI-1.

[0230] It can be understood that the remote UE can obtain QoS flow information #2 in the process of establishing the QoS flow #1, and the QoS flow information #2 includes identifier information QFI-1 of the QoS flow #1 and a PDR corresponding to the QFI-1.

[0231] S720, the remote UE sends a request message #1 (an example of a first request message) to the relay UE through a non-direct connection path.

[0232] Specifically, the remote UE determines that a non-direct connection path needs to be established according to the data transmission requirement, so as to simultaneously use the non-direct connection path and the direct connection path for multi-path transmission, for example, to perform reliable transmission or load balancing transmission.

[0233] Specifically, the remote UE sends a request message #1 (an example of a first request message) to the relay UE through a PC5 interface, the request message #1 being used to request establishment of a QoS flow #2 (an example of a first QoS flow) on a non-direct connection path.

[0234] The identifier of the QoS flow #2 can be QFI-2.

[0235] The request message #1 includes indication information #1 (an example of second indication information), the indication information #1 being used to acquire QoS flow information #1 (an example of first information), the QoS flow information #1 including identifier information QFI-2 of the QoS flow #2 and a PDR corresponding to the QFI-2.

[0236] The request message #1 also includes “request PC5 QoS rule” and “request PC5 QoS parameter”. In the “request PC5 QoS rule”, a destination address of packet filtering is the same as a destination address of packet filtering of a QoS rule of the QFI-1; the “request PC5 QoS parameter” is the same as a QoS parameter of the QoS flow #1.

[0237] It can be understood that the remote UE can acquire QoS flow information #2 (an example of second information) of the QoS flow #1 on the direct connection path. The QoS flow information #2 includes a QoS rule and a QoS parameter of the QFI-1.

[0238] Exemplarily, the request message #1 can be a link modification request message.

[0239] Exemplarily, the indication information #1 can be paired QoS flow indication information.

[0240] S730, the relay UE sends a request message #2 to the SMF #2.

[0241] Specifically, the relay UE sends the request message #2 to the AMF #2, and the AMF #2 sends the request message #2 to the SMF #2 (an example of a second network device), the request message #2 including the above-mentioned indication information #1, the request message #2 also including “request QoS rule” and “request QoS parameter”. Correspondingly, the SMF #2 establishes the QoS flow #2 on the non-direct connection path according to the request message #2.

[0242] The "request QoS rule" and the "request QoS parameter" in the request message #2 are determined by the relay UE according to the "request PC5 QoS rule" and the "request PC5 QoS parameter" of the remote UE.

[0243] Exemplarily, the request message #2 can be a PDU session establish request message.

[0244] Exemplarily, the relay UE can send the request message #2 to the AMF #2 through an UL NAS message.

[0245] Exemplarily, the AMF #2 can send the request message #2 to the SMF #2 through an N11 message, which can be a PDU session create SM context request message, etc.

[0246] The AMF #2 and the SMF #2 are network devices serving the relay UE.

[0247] S740, the SMF #2 sends a response message #1 to the relay UE.

[0248] Specifically, the SMF #2 sends the response message #1 to the relay UE through the AMF #2.

[0249] Specifically, the response message #1 is used to respond to the request message #2.

[0250] Exemplarily, the response message #1 can be a PDU session establish accept message.

[0251] Exemplarily, specifically, the SMF #2 can first send an N11 message to the AMF #2, the N11 message including an N1 SM container and an N2 SM container, the N1 SM container including the response message #1, and the N2 SM container including QoS flow information #1, QoS rule and QoS parameter, wherein the N11 message can be a Namf_communication_N1N2MessageTransfer message.

[0252] The QoS flow information #1 includes identification information QFI-2 of the QoS flow #2 and a PDR corresponding to the QFI-2.

[0253] It should be understood that the SMF#2 sends the PDR corresponding to the QFI-2 to the relay UE according to the indication information#1.

[0254] S750, the relay UE sends a response message#2 to the remote UE through the non-direct connection path.

[0255] Specifically, the relay UE sends the response message#2 to the remote UE through the PC5 interface, and the response message#2 includes the QoS flow information#1 (an example of the first information), the PC5 QoS rule and the PC5 QoS parameter.

[0256] The QoS flow information#1 includes the identification information QFI-2 of the QoS flow#2 and the PDR corresponding to the QFI-2.

[0257] Exemplarily, the response message#2 can be a link modification accept message.

[0258] It can be understood that the relay UE generates the PC5 QoS rule according to the QoS rule included in the response message#1, and generates the PC5 QoS parameter according to the QoS parameter included in the response message#1.

[0259] S760, the remote UE sends a request message#3 (an example of the first message) to the SMF#1 through the direct connection path.

[0260] Specifically, the remote UE carries the QoS flow information#1 and the indication information#2 in the request message#3.

[0261] The request message#3 is used to request the SMF#1 to modify the QoS flow#1, and the modification here can be understood as modifying the QoS parameter corresponding to the QoS flow#1, that is, adding the QoS parameter of the QoS flow#2 included in the QoS flow information#1, specifically, adding the PDR corresponding to the QFI-2.

[0262] Exemplarily, the request message#3 can be a PDU session modification request message.

[0263] Optionally, the request message#3 can also carry indication information#3 (an example of the third indication information).

[0264] The indication information#3 is used to instruct the network device (UPF#1) to perform reliable transmission or load balancing transmission.

[0265] S770, the SMF#1 sends a request message#4 to the UPF#1.

[0266] Specifically, SMF#1 carries QoS flow information #1 and QoS flow information #2 in the request message #4.

[0267] Optionally, the request message #4 may also carry instruction information #3 (an example of a third instruction message).

[0268] This instruction #3 is used to instruct the network device (UPF#1) to perform reliable transmission or load-balanced transmission.

[0269] For example, the request message #4 could be an N4 modification request message.

[0270] S780, UPF#1 determines to perform multiplexing based on request message #4.

[0271] Specifically, UPF#1 determines the PDR corresponding to QFI-2 and the PDR corresponding to QFI-1 based on request message #4, and further determines to perform multiplexing.

[0272] Optionally, when the request message #4 includes indication information #3, UPF #1 can determine whether to perform reliable transmission or load-balanced transmission based on the indication information #3.

[0273] Figure 8 This is a schematic diagram of a method for performing multiplexing by a UPF according to an embodiment of this application. Method 800 is a specific description of how UPF#1 performs multiplexing to a remote UE after step S780 in method 700.

[0274] like Figure 8 As shown, Figure 8 (a) shows a schematic diagram of a remote UE's non-directly connected path and directly connected path connected to different UPFs. As shown in 8(b), this is a schematic diagram of a remote UE's non-directly connected path and directly connected path connected to the same UPF. In this case, QoS flow #1 is established on the directly connected path, and QoS flow #2 is established on the non-directly connected path.

[0275] Specifically, such as Figure 8 As shown in (a), the direct path of the remote UE is connected to UPF#1 (an example of the first UPF), and the non-direct path of the remote UE is connected to UPF#2. The specific execution of multiplexing includes the following steps:

[0276] a: When UPF#1 receives downlink data from the APP server, it determines, based on indication information #3, that if reliable transmission is to be performed, the downlink IP packet needs to be copied; if load balancing transmission is to be performed, the IP packet needs to be split. This downlink data packet includes the external IP address (IP-5) of the destination address (QoS flow #1) and the IP address (IP-6) of the source address (APP server).

[0277] b: On the direct path, UPF#1 needs to translate IP-5 into the inner network address IP1 corresponding to QoS flow#1, so the data packet sent by UPF#1 to the remote UE includes the destination address IP-1 and the source address IP6.

[0278] c: On the non-direct path, UPF#1 needs to add an IP header to the existing IP packet, the destination address is the destination address of the packet filter of the PDR corresponding to QoS flow#2, and the source address remains unchanged, so the IP header to be added includes the outer network IP corresponding to QoS flow#2 and the source address, and the data packet routed by UPF#1 to UPF#2 includes IP-4 and IP6, IP-1 and IP6.

[0279] d: UPF#2 translates the outer network IP corresponding to QoS flow#2 into the inner network address IP-3 corresponding to QoS flow#2, and routes the data packet to the relay UE according to the inner network address, the data packet includes IP-3 and IP-6, IP-1 and IP-6.

[0280] e: The relay UE routes to the remote UE according to the PC5 QoS rule.

[0281] f: The remote UE determines that it is a multi-path cooperative transmission according to the record of step S720 in method 700, and needs to remove the outer IP header, and the obtained IP packet includes the destination address IP-1 and the source address IP6. Further, the IP packet is sent to the APP client, and the APP client performs IP layer processing such as deduplication and reordering to ensure reliability.

[0282] Specifically, as shown in Figure 8 (b), the direct path and the non-direct path of the remote UE connect UPF#1, which is different from Figure 8 (a) in that, when performing multi-path transmission, UPF#1 does not need to route the data packet to UPF#2, but directly routes it to the relay UE, and the other steps are basically the same as those of Figure 9 (a) and will not be described here.

[0283] Table 1(a) and Table 1(b) respectively show the English and corresponding Chinese interpretation of the multi-path transmission method related feature information provided by the embodiments of the application.

[0284] Table 1(a)

[0285]

[0286]

[0287] Table 1(b)

[0288]

[0289]

[0290] Table 2(a) and Table 2(b) respectively show the English and corresponding Chinese interpretation of the characteristic information of the "Multi-Path Rule" multi-path transmission rule.

[0291] Table 2(a)

[0292]

[0293] Table 2(b)

[0294]

[0295]

[0296] Figure 10 Fig. 9 is a schematic diagram of a method 900 of data transmission provided by an embodiment of the present application. The method 900 can be regarded as a specific implementation of the method 500, and the method 900 can comprise the following steps.

[0297] S910, the remote UE triggers the relay UE to establish a PDU session #2 and a QoS flow #2 on a non-direct connection path.

[0298] Specifically, the remote UE triggers the relay UE to establish the PDU session #2 on the non-direct connection path through the PC5 interface, so that data transmission between the remote UE and the DN can be realized. The PDU session #2 includes the QoS flow #2 (an example of a second QoS flow).

[0299] The identifier of the QoS flow #2 can be QFI-2.

[0300] It can be understood that the remote UE can obtain QoS flow information #1 in the process of triggering the establishment of the QoS flow #2, and the QoS flow information #1 includes the identifier information QFI-2 of the QoS flow #2 and the PDR corresponding to the QFI-2.

[0301] S920, the remote UE sends a request message #5 to the SMF #1.

[0302] Specifically, the remote UE determines that the direct connection path needs to be established according to the data transmission requirement, so as to simultaneously use the non-direct connection path and the direct connection path for multi-path transmission, for example, to perform reliable transmission or load balancing transmission.

[0303] Specifically, the remote UE sends the request message #5 to the AMF #1, and the AMF #1 sends the request message #5 to the SMF #1, and the request message #5 is used to request to establish a QoS flow #1 (an example of a first QoS flow) on the direct connection path.

[0304] The identifier of the QoS flow #1 can be QFI-1.

[0305] The request message #5 includes indication information #1 (an example of second indication information), which is used to acquire QoS flow information #2 (an example of first information), the QoS flow information #2 including identifier information QFI-1 of the QoS flow #1 and PDR corresponding to QFI-1.

[0306] The request message #5 also includes "request QoS rule" and "request QoS parameter". Wherein, the destination address of the packet filter in the "request QoS rule" is the same as the destination address of the packet filter of the QoS rule of QFI-2; the "request QoS parameter" is the same as the QoS parameter of the QoS flow #2.

[0307] Exemplarily, the request message #5 can be a PDU session modification request message.

[0308] Exemplarily, the indication information #1 can be paired QoS flow indication information.

[0309] Exemplarily, the remote UE can send the request message #5 to the AMF #1 through an UL NAS message.

[0310] Exemplarily, the AMF #1 can send the request message #5 to the SMF #1 through an N11 message, which can be a PDU session creation context request message, etc.

[0311] The AMF #1 and the SMF #1 are network devices serving the remote UE.

[0312] S930, the SMF #1 sends a response message #3 to the remote UE.

[0313] Specifically, the SMF #1 sends the response message #3 to the remote UE through the AMF #1. Correspondingly, the remote UE receives the response message #3.

[0314] Specifically, the response message #3 is used to respond to the above-mentioned request message #5.

[0315] The response message #3 includes QoS flow information #2 (an example of first information), QoS rule and QoS parameter.

[0316] The QoS flow information #2 includes identification information QFI-1 of the QoS flow #1 and a PDR corresponding to the QFI-1.

[0317] It should be understood that the SMF #1 sends the PDR corresponding to the QFI-1 to the remote UE according to the indication information #1.

[0318] Exemplarily, the response message #3 can be a PDU session modification accept message.

[0319] The SMF #1 can send the response message #3 to the AMF #1 through an N11 message, which can be a Namf_communication_N1N2MessageTransfer message.

[0320] S940, the remote UE sends a request message #6 to the relay UE through a non-direct connection path.

[0321] Specifically, the remote UE sends the request message #6 (an example of the first message) to the relay UE through a PC5 interface.

[0322] The request message #3 includes QoS flow information #2 and indication information #2 (an example of the first indication information).

[0323] Optionally, the request message #6 can also carry indication information #3 (an example of the third indication information).

[0324] The indication information #3 is used to instruct the network device (UPF #2) to perform reliability transmission or load balancing transmission.

[0325] Exemplarily, the request message #6 can be a link modification request message.

[0326] Exemplarily, the indication information #2 can be paired QoS flow indication information.

[0327] S950, the relay UE sends a request message #7 to the SMF #2.

[0328] Specifically, the relay UE sends the request message #7 to the AMF #2, and the AMF #2 sends the request message #7 to the SMF #2 (an example of the second network device).

[0329] Specifically, the relay UE carries the QoS flow information #2 and the indication information #2 in the request message #7.

[0330] The request message 7 is used to request the SMF 2 to modify the QoS flow 2, and the modification can be understood as modifying the QoS parameter corresponding to the QoS flow 2, that is, adding the QoS parameter of the QoS flow 1 included in the QoS flow information 2, and specifically, can be understood as adding the PDR corresponding to the QFI-1.

[0331] The request message 7 can be a PDU session modification request message.

[0332] Optionally, the request message 7 can also carry indication information 3 (an example of third indication information).

[0333] The indication information 3 is used to instruct the network device (the UPF 2) to perform reliability transmission or load balancing transmission.

[0334] S960, the SMF 2 sends a request message 8 to the UPF 2.

[0335] Specifically, the SMF 1 carries the QoS flow information 1 and the QoS flow information 2 in the request message 8.

[0336] Optionally, the request message 8 can also carry indication information 3 (an example of third indication information).

[0337] The indication information 3 is used to instruct the network device (the UPF 2) to perform reliability transmission or load balancing transmission.

[0338] Exemplarily, the request message 8 can be an N4 modification request message.

[0339] S970, the SMF 2 sends a response message 4 to the relay UE.

[0340] Specifically, the SMF 2 sends the response message 4 to the relay UE through the AMF 2.

[0341] The response message 4 is used to respond to the request message 7, and the SMF 2 completes the modification of the QoS flow 2.

[0342] Exemplarily, the response message 4 can be a PDU session modification accept message.

[0343] S980, the relay UE sends a response message 5 to the remote UE.

[0344] Specifically, the relay UE sends the response message 5 to the remote UE through the PC5 interface.

[0345] The response message #5 is used to respond to the request message #6.

[0346] Exemplarily, the response message #5 can be a link modification accept message.

[0347] S990, the UPF #2 determines to perform multiplexing according to the request message #8.

[0348] Specifically, the UPF #2 determines the PDR corresponding to QFI-2 and the PDR corresponding to QFI-1 according to the request message #48, and further determines to perform multiplexing.

[0349] Optionally, when the indication information #3 is included in the request message #8, the UPF #2 can determine to specifically perform reliable transmission or perform load balancing transmission according to the indication information #3.

[0350] It can be understood that the UPF specifically performs the method of multiplexing, which is the same as method 800, and the embodiments of the present application will not be described here.

[0351] According to the technical solutions provided by the embodiments of the present application, in the layer three relay scenario, the UE performs downlink data packet transmission through direct and indirect paths at the same time, thereby improving the data transmission rate or increasing the reliability.

[0352] Figure 11 is a schematic diagram of a data transmission method 1000 provided by an embodiment of the present application. The method 1000 can be regarded as a specific implementation of the method 500, and the method 1000 can include the following steps.

[0353] S1010, the remote UE establishes a PDU session #1 and a QoS flow #1 on a direct path.

[0354] Specifically, the remote UE initiates establishment of the PDU session #1 on the direct path, so that data transmission between the remote UE and the DN can be realized. The PDU session #1 includes the QoS flow #1 (an example of the second QoS flow).

[0355] The identifier of the QoS flow #1 can be QFI-1.

[0356] It can be understood that the remote UE can obtain the QoS flow information #2 in the process of establishing the QoS flow #1, and the QoS flow information #2 includes the identifier information QFI-1 of the QoS flow #1 and the PDR corresponding to the QFI-1.

[0357] S1020, the remote UE sends a request message #1 (an example of the first request message) to the relay UE through a non-direct path.

[0358] Specifically, the remote UE determines that the non-direct connection path needs to be established according to the data transmission requirement, so as to simultaneously use the non-direct connection path and the direct connection path for multiplexing, for example, for reliable transmission or load balancing transmission.

[0359] Specifically, the remote UE sends a request message #1 (an example of a first request message) to the relay UE through the PC5 interface, and the request message #1 is used to request to establish a QoS flow #2 (an example of a first QoS flow) on the non-direct connection path.

[0360] The identifier of the QoS flow #2 can be QFI-2.

[0361] The request message #1 includes indication information #1 (an example of second indication information), and the indication information #1 is used to obtain QoS flow information #1 (an example of first information), and the QoS flow information #1 includes the identifier information QFI-2 of the QoS flow #2.

[0362] The request message #1 also includes “request PC5 QoS rule” and “request PC5 QoS parameter”. Wherein, the destination address of the packet filter in “request PC5 QoS rule” and the destination address of the packet filter of the QoS rule of QFI-1 are the same; “request PC5 QoS parameter” and the QoS parameter of the QoS flow #1 are the same.

[0363] It can be understood that the remote UE can obtain the QoS flow information #2 (an example of second information) of the QoS flow #1 on the direct connection path. Wherein, the QoS flow information #2 includes the QoS rule and the QoS parameter of QFI-1.

[0364] The request message #1 can be a link modification request message.

[0365] The indication information #1 can be paired QoS flow indication information.

[0366] S1030, the relay UE sends a request message #9 to the SMF #2.

[0367] Specifically, the relay UE sends the request message #9 to the AMF #2, and the AMF #2 sends the request message #9 to the SMF #2, and the request message #9 includes “request QoS rule” and “request QoS parameter”. Correspondingly, the SMF #2 establishes the QoS flow #2 on the non-direct connection path according to the request message #9.

[0368] The "request QoS rule" and "request QoS parameter" in the request message #9 are determined by the relay UE according to the "request PC5 QoS rule" and "request PC5 QoS parameter" of the remote UE.

[0369] The request message #9 can be a PDU session modification request message.

[0370] The relay UE can send the request message #9 to the AMF #2 through an UL NAS message.

[0371] The AMF #2 can send the request message #9 to the SMF #2 through an N11 message, which can be a PDU session creation context request message, etc.

[0372] The AMF #2 and the SMF #2 are network devices serving the relay UE.

[0373] S1040, the SMF #2 sends a response message #6 to the relay UE.

[0374] Specifically, the SMF #2 sends the response message #6 to the relay UE through the AMF #2.

[0375] Specifically, the response message #6 is used to respond to the request message #9.

[0376] The response message #6 can be a PDU session modification accept message.

[0377] The response message #6 includes the identification information QFI-2 of the QoS flow #2.

[0378] The response message #6 also includes the QoS rule and the QoS parameter, and the "QoS rule" and "QoS parameter" in the response message #6 are determined by the SMF #2 according to the "request QoS rule" and "request QoS parameter" sent by the relay UE.

[0379] S1050, the relay UE sends a response message #7 to the remote UE through a non-direct connection path.

[0380] Specifically, the relay UE sends a response message #7 to the remote UE through the PC5 interface, where the response message #7 includes the QFI-2 (an example of the first information) of the QoS flow information #1, the ID of the PDU session #2, the ID of the relay UE, the PC5 QoS rule and the PC5 QoS parameter.

[0381] The response message #7 can be a link modification accept message.

[0382] It can be understood that the relay UE generates the PC5 QoS rule according to the QoS rule included in the response message #6, and generates the PC5 QoS parameter according to the QoS parameter included in the response message #6.

[0383] It should be noted that the relay UE sends the QFI-2, the ID of the PDU session #2 and the ID of the relay UE to the remote UE according to the indication information #1.

[0384] In an optional manner, the relay UE ID can be a GUTI or an S-TMSI.

[0385] S1060, the remote UE sends a request message #10 to the AMF #1 through the direct connection path.

[0386] Specifically, the remote UE carries the QFI-2, the ID of the PDU session #2, the ID of the relay UE and the modification request of the PDU session #1 of the QoS flow #1 in the request message #10.

[0387] Optionally, the request message #10 can further include the indication information #2.

[0388] The request message #10 can be a NAS message, used to request to modify the parameters of the QoS flow #1. Here, the modification can be understood as modifying the QoS parameter corresponding to the QoS flow #1, that is, adding the QoS parameter of the QoS flow #2 included in the QoS flow information #1.

[0389] S1070, the AMF #1 sends a request message #11 to the AMF #2.

[0390] Specifically, the AMF #1 determines the address of the AMF #2 serving the relay UE according to the ID of the relay UE included in the request message #10, and further sends the request message #11 to the AMF #2.

[0391] In this application, the request message #11 includes the QFI-2, the ID of the PDU session #2 and the ID of the relay UE.

[0392] Optionally, the request message #11 can further include the indication information #2.

[0393] The indication information #2 is used to indicate the PDR corresponding to the QFI-2 sent by the AMF #2.

[0394] As an example, the AMF #1 can send a request message #11 to the AMF #2 through an N11 message, which can be a (Namf_communication_UEContextTransfer request) message.

[0395] S1080, the AMF #2 sends a response message #8 to the AMF #1.

[0396] Specifically, the AMF #2 determines the address of the UPF #2 providing services for the relay UE QFI-2 and the PDR corresponding to the QFI-2 according to the QFI-2, the ID of the PDU session #2 and the ID of the relay UE. Further, the AMF #2 sends the response message #8 to the AMF #1.

[0397] Specifically, the response message #8 is used to respond to the above-mentioned request message #11.

[0398] In this application, the response message #8 carries the address of the UPF #2 and the PDR corresponding to the QFI-2.

[0399] As an example, the address of the UPF #2 can be the fully qualified domain name (FQDN) or IP address of the UPF-2.

[0400] It should be understood that the AMF #2 sends the PDR corresponding to the QFI-2 to the AMF #1 according to the indication information.

[0401] As an example, the AMF #2 can send the response message #8 to the AMF #1 through an N11 message, which can be a (Namf_communication_UEContextTransfer response) message.

[0402] S1090, the AMF #1 sends a request message #12 to the SMF #1.

[0403] Wherein, the request message #12 includes the address of the UPF #2, the PDR corresponding to the QFI-2, and the modification request of the PDU session #1 of the QoS flow #1.

[0404] Optionally, the indication information #2 can also be included.

[0405] It can be understood that the request message 12 is used to request the SMF 1 to modify the QoS parameter of the PDU session 1 of the QoS flow 1, and the modification can be understood as modifying the QoS parameter corresponding to the QoS flow 1, that is, adding the QoS parameter of the QoS flow 2 included in the QoS flow information 1, which can be specifically adding the PDR corresponding to QFI-2.

[0406] As an example, the AMF 1 can send the request message 12 to the SMF 1 through an N11 message, which can be a (Namf_PDUSession_UpdateSMContext request) message.

[0407] S1091, the SMF 1 sends a request message 13 to the UPF 1.

[0408] The request message 13 includes the PDR corresponding to QFI-2, the PDR corresponding to QFI-1, and QFI-2.

[0409] Optionally, the indication information 3 (an example of third indication information) can also be included.

[0410] The indication information 3 is used for the UPF 1 to determine to perform multiplexing, and specifically, to determine to perform reliability transmission or load balancing transmission.

[0411] Optionally, the PDR corresponding to QFI-2, QFI-2, and the indication information 3 can be carried in the PDR corresponding to QFI-1.

[0412] As an example, the SMF 1 can send the request message 13 to the UPF 1 through an N4 modification request message.

[0413] Further, the SMF 1 determines whether the UPF 1 and the UPF 2 are the same UPF according to the address of the UPF 2 included in the request message 12.

[0414] Specifically, when the UPF 1 is the same as the UPF 2, the transmission of the downlink data can be directly performed according to the method 800(b).

[0415] Specifically, when the UPF 1 is different from the UPF 2, in one possible implementation, the SMF 1 can perform the transmission of the downlink data according to the method 800(a).

[0416] In another possible implementation, the SMF 1 can initiate the establishment of a tunnel between the UPF 1 and the UPF 2.

[0417] It can be understood that the tunnel between the UPF#1 and the UPF#2 can be used to transmit data, and the scheme can also be used in the method 700 and the method 900, and the implementation among the embodiments can be combined with each other, and the application embodiments are not limited in this regard.

[0418] S1092, a tunnel is established between the UPF#1 and the UPF#2.

[0419] Specifically, the UPF#1 allocates tunnel related information, and the tunnel related information is sent to the UPF#2 through the SMF#1, the AMF#1, the AMF#2 and the SMF#2.

[0420] In the application, the tunnel related information of the UPF#1 includes an address of the UPF#1 and a tunnel ID (tunnel ID).

[0421] For example, the tunnel ID can be a full qualified tunnel endpoint ID (F-TEID).

[0422] As an example, the signaling in the process that the UPF#1 allocates the tunnel related information and sends the tunnel related information to the UPF#2 through the SMF#1, the AMF#1, the AMF#2 and the SMF#2 can be sent through an N1 message.

[0423] For example, the UPF#1 can send the tunnel related information to the SMF#1 through an N4 modification response message.

[0424] It can be understood that the response message is used to respond to the request message #13.

[0425] For example, the SMF#1 can send the tunnel related information to the AMF#1 through a Namf_PDUSession_UpdateSMContext response message.

[0426] For example, the AMF#1 can send the tunnel related information to the AMF#2 through a Namf_communication_UEContextTransfer request message.

[0427] For example, the AMF#2 can send the tunnel related information to the SMF#2 through a Namf_PDUSession_UpdateSMContext request message.

[0428] For example, the SMF#2 can send the tunnel related information to the UPF#2 through an N4 modification response message.

[0429] Similarly, UPF#2 allocates tunnel related information, which is sent to UPF#1 via SMF#2, AMF#2, AMF#1 and SMF#1.

[0430] In the present application, the tunnel related information of UPF#2 includes the address of UPF#2 and a tunnel ID.

[0431] For example, the tunnel ID can be a full qualified tunnel endpoint ID (F-TEID).

[0432] The signaling interaction process is similar to the process of UPF#1 allocating tunnel related information described above, and will not be described here.

[0433] After UPF#1 and UPF#2 complete the interaction of tunnel information, the tunnel is established. That is, the UPF#1 and UPF#2 can transmit data through the tunnel.

[0434] S1093, UPF#1 determines to perform multiplexing according to the request message #13.

[0435] Specifically, UPF#1 determines the PDR corresponding to QFI-2 and the PDR corresponding to QFI-1 according to the request message #13, and further determines to perform multiplexing.

[0436] Optionally, when the request message #13 includes the indication information #3, the UPF#1 can determine to perform reliable transmission or perform load balancing transmission according to the indication information #3.

[0437] In the present application, the method for UPF to perform multiplexing and method 800 are basically the same, the difference is that in the present embodiment, when the non-direct connection path and the direct connection path of the remote UE are connected to different UPFs, steps a and b are the same as method 800, when UPF#1 performs step c, UPF#1 QFI-1 corresponding PDR determines the tunnel between UPF#1 and UPF#2, adds a new GTP-U message header to the new IP packet (including IP-4 and IP6, IP-1 and IP6), and sends it to UPF#2 through the tunnel. The information of QFI-2 is contained in the GTP-U message header, step d: UPF#2 receives the GTP-U message in the tunnel, and according to the direct mapping relationship of the tunnel identifier, transfers the GTP-U to Gnb#2; step e: gNB sends the new IP packet to the relay UE according to the QFI-2 in the GTP-U, and the relay UE routes to the remote UE according to the PC5 QoS rule. The subsequent process is the same as method 800, and the present embodiment will not be described here.

[0438] Figures 5 to 11FIG. 11 is a schematic diagram of a method 1100 for data transmission provided by an embodiment of the present application. The method 1100 can be regarded as a specific implementation of the method 500, and the method 1100 can include the following steps.

[0439] S1110, the remote UE triggers the relay UE to establish a PDU session #2 and a QoS flow #2 on the non-direct connection path.

[0440] Specifically, the remote UE triggers the relay UE to establish the PDU session #2 on the non-direct connection path through the PC5 interface, so that data transmission between the remote UE and the DN can be realized. The PDU session #2 includes the QoS flow #2 (an example of a second QoS flow).

[0441] The identifier of the QoS flow #2 can be QFI-2.

[0442] It can be understood that the remote UE can obtain the QoS flow information #1 in the process of triggering the establishment of the QoS flow #2, and the QoS flow information #1 includes the identifier information QFI-2 of the QoS flow #2 and the PDR corresponding to the QFI-2.

[0443] S1120, the remote UE sends a request message #14 to the SMF #1.

[0444] Specifically, the remote UE determines that the direct connection path needs to be established according to the data transmission requirement, so as to simultaneously use the non-direct connection path and the direct connection path for multi-path transmission, for example, to perform reliable transmission or load balancing transmission.

[0445] Specifically, the remote UE sends the request message #14 to the AMF #1, and the AMF #1 sends the request message #14 to the SMF #1. The request message #14 is used to request the establishment of a QoS flow #1 (an example of a first QoS flow) on the direct connection path.

[0446] The identifier of the QoS flow #1 can be QFI-1.

[0447] The request message #14 includes the indication information #1 (an example of second indication information), and the indication information #1 is used to obtain the QoS flow information #2 (an example of first information). The QoS flow information #2 includes the identifier information QFI-1 of the QoS flow #1.

[0448] The request message #14 further includes "request QoS rule" and "request QoS parameter". In the "request QoS rule", the destination address of the packet filter is the same as the destination address of the packet filter of the QoS rule of the QFI-2; and the "request QoS parameter" is the same as the QoS parameter of the QoS flow #2.

[0449] The request message 14 can be a PDU session modification request message.

[0450] The indication information 1 can be paired QoS flow indication information.

[0451] The remote UE can send the request message 14 to the AMF 1 through an UL NAS message.

[0452] The AMF 1 can send the request message 14 to the SMF 1 through an N11 message, which can be a PDU session creation context request (Nsmf_PDUsession_createSMcontext request) message, etc.

[0453] The AMF 1 and the SMF 1 are network devices serving the remote UE.

[0454] S1130, the SMF 1 sends a response message 9 to the remote UE.

[0455] Specifically, the SMF 1 sends the response message 9 to the remote UE through the AMF 1. Correspondingly, the remote UE receives the response message 9.

[0456] Specifically, the response message 9 is used to respond to the request message 14.

[0457] The response message 9 includes identification information QFI-1 (an example of the first information) of the QoS flow 1 and an ID of the PDU session 1.

[0458] The response message 9 can also include QoS rules and QoS parameters.

[0459] It should be understood that the SMF 1 sends the QFI-1 and the ID of the PDU session 1 to the remote UE according to the indication information 1.

[0460] The response message 9 can be a PDU session modification accept message.

[0461] The SMF 1 can send the response message 9 to the AMF 1 through an N11 message, which can be a N1N2 message transfer (Namf_communication_N1N2MessageTransfer) message.

[0462] S1140, the remote UE sends a request message 15 to the relay UE through a non-direct connection path.

[0463] Specifically, the remote UE sends a request message #15 (an example of the first message) to the relay UE through the PC5 interface.

[0464] The request message #15 includes the QFI-1, the ID of the PDU session #1, the ID of the remote UE, and a modification request of the PDU session #2 of the QoS flow #2 (an example of the first indication information).

[0465] Optionally, the request message #15 can also carry the indication information #2 (an example of the first indication information).

[0466] The request message #15 can be a link modification request message.

[0467] The indication information #2 can be paired QoS flow indication information.

[0468] The request message #15 is used to request to modify the parameters of the QoS flow #2. The modification here can be understood as modifying the QoS parameters corresponding to the QoS flow #2, that is, adding the QoS parameters of the QoS flow #2 included in the QoS flow information #1.

[0469] S1150, the AMF #2 sends a request message #16 to the AMF #1.

[0470] Specifically, the AMF #2 determines the address of the AMF #1 serving the remote UE according to the ID of the remote UE included in the request message #15, and further sends the request message #16 to the AMF #1.

[0471] In this application, the request message #16 includes the QFI-1, the ID of the PDU session #1, and the ID of the remote UE.

[0472] Optionally, the request message #16 can also include the indication information #2.

[0473] The indication information #2 is used to indicate that the AMF #2 sends the PDR corresponding to the QFI-1.

[0474] As an example, the AMF #2 can send the request message #16 to the AMF #1 through an N11 message, which can be a (Namf_communication_UEContextTransfer request) message.

[0475] S1160, the AMF #1 sends a response message #10 to the AMF #2.

[0476] Specifically, the AMF#1 determines the address of the UPF#1 providing service for the remote UE QFI-1 and the PDR corresponding to the QFI-1 according to the QFI-1, the ID of the PDU session#1 and the ID of the remote UE. Further, the AMF#1 sends the response message#10 to the AMF#2.

[0477] Specifically, the response message#10 is used to respond to the above-mentioned request message#16.

[0478] In this application, the response message#10 carries the address of the UPF#1 and the PDR corresponding to the QFI-1.

[0479] As an example, the address of the UPF#1 can be the fully qualified domain name (FQDN) or IP address of the UPF-1.

[0480] It should be understood that the AMF#1 sends the PDR corresponding to the QFI-1 to the AMF#2 according to the indication information.

[0481] As an example, the AMF#1 can send the response message#10 to the AMF#2 through an N11 message, which can be a (Namf_communication_UEContextTransfer response) message.

[0482] S1170, the AMF#2 sends the request message#17 to the SMF#2.

[0483] Wherein, the request message#17 includes the address of the UPF#1, the PDR corresponding to the QFI-1, and the modification request of the PDU session#1 of the QoS flow#2.

[0484] Optionally, the indication information#2 can also be included.

[0485] It can be understood that the request message#17 is used to request the SMF#2 to modify the QoS parameter of the PDU session#2 of the QoS flow#2, and the modification here can be understood as modifying the QoS parameter corresponding to the QoS flow#2, that is, adding the QoS parameter of the QoS flow#1 included in the QoS flow information#2, which can be specifically adding the PDR corresponding to the QFI-1.

[0486] As an example, the AMF#2 can send the request message#17 to the SMF#2 through an N11 message, which can be a (Namf_PDUSession_UpdateSMContext request) message.

[0487] S1180, the SMF#2 sends the request message#18 to the UPF#2.

[0488] The request message #18 includes a PDR corresponding to QFI-1, a PDR corresponding to QFI-2, and an indication information #3.

[0489] Optionally, the indication information #3 (an example of the third indication information) can be further included.

[0490] The indication information #3 is used for the UPF #2 to determine to perform multiplexing, and specifically, to determine to perform reliability transmission or load balancing transmission.

[0491] Optionally, the PDR corresponding to QFI-1, QFI-1, and the indication information #3 can be carried in the PDR corresponding to QFI-2.

[0492] As an example, the SMF #2 can send the request message #18 to the UPF #2 through an N4 modification request message.

[0493] Further, the SMF #2 determines whether the UPF #1 and the UPF #2 are the same UPF according to the address of the UPF #1 included in the request message 18.

[0494] Specifically, when the UPF #1 is the same as the UPF #2, the transmission of the downlink data can be directly performed according to the method 800 (b).

[0495] Specifically, when the UPF #1 is different from the UPF #2, in a possible implementation, the SMF #1 can perform the transmission of the downlink data according to the method 800 (a).

[0496] In another possible implementation, the SMF #2 can initiate the establishment of a tunnel between the UPF #1 and the UPF #2.

[0497] It can be understood that the tunnel between the UPF #1 and the UPF #2 can be used to transmit data, and this scheme can also be used in the method 700 and the method 900. The implementations among the embodiments can be combined with each other, and the embodiments of the present application are not limited thereto.

[0498] S1190, a tunnel is established between the UPF #1 and the UPF #2.

[0499] Specifically, the UPF #2 allocates tunnel related information, and the tunnel related information is sent to the UPF #1 through the SMF #2, the AMF #2, the AMF #1, and the SMF #1.

[0500] In the present application, the tunnel related information of the UPF #2 includes an address of the UPF #2 and a tunnel ID.

[0501] Exemplarily, the tunnel ID can be a full qualified tunnel endpoint ID (F-TEID).

[0502] As an example, the UPF#2 allocates the tunnel related information, and the signaling in the process of sending the tunnel related information from the UPF#2 to the UPF#1 via the SMF#2, the AMF#2, the AMF#1 and the SMF#1 can be sent through the N1 message.

[0503] Exemplarily, the UPF#2 can send the tunnel related information to the SMF#2 through the N4 modification response message.

[0504] It can be understood that the response message is used to respond to the request message #18.

[0505] Exemplarily, the SMF#2 can send the tunnel related information to the AMF#2 through the Namf_PDUSession_UpdateSMContext response message.

[0506] Exemplarily, the AMF#2 can send the tunnel related information to the AMF#1 through the Namf_communication_UEContextTransfer request message.

[0507] Exemplarily, the AMF#1 can send the tunnel related information to the SMF#1 through the Namf_PDUSession_UpdateSMContext request message.

[0508] Exemplarily, the SMF#1 can send the tunnel related information to the UPF#1 through the N4 modification response message.

[0509] Similarly, the UPF#1 allocates the tunnel related information, and the tunnel related information is sent to the UPF#1 via the SMF#1, the AMF#1, the AMF#2 and the SMF#2.

[0510] In the present application, the tunnel related information of the UPF#1 includes an address and a tunnel ID of the UPF#1.

[0511] Exemplarily, the tunnel ID can be a full qualified tunnel endpoint ID (F-TEID).

[0512] The interaction process of the signaling is similar to the process of allocating the tunnel related information by the UPF#2, which will not be described herein.

[0513] After UPF#1 and UPF#2 complete the exchange of tunnel information, the tunnel is established. That is, UPF#1 and UPF#2 can transmit data through this tunnel.

[0514] S1191, UPF#2 determines to perform multiplexing based on request message #18.

[0515] Specifically, UPF#2 determines the PDR corresponding to QFI-2 and the PDR corresponding to QFI-1 based on request message #18, and further determines to perform multiplexing.

[0516] Optionally, when the request message #18 includes indication information #3, UPF #2 can determine whether to perform reliable transmission or load-balanced transmission based on the indication information #3.

[0517] In this application, the method for performing multiplexing by the UPF is the same as the method for performing transmission after step S1093, and will not be described in detail here.

[0518] According to the technical solution provided in the embodiments of this application, in the three-layer relay scenario, the UE transmits downlink data packets simultaneously through direct and indirect paths, thereby improving the data transmission rate or increasing reliability.

[0519] The above, combined with Figures 12 to 13 The methods provided in the embodiments of this application are described in detail below. Figure 12 The apparatus provided in the embodiments of this application is described in detail. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, for content not described in detail, please refer to the method embodiments above. For the sake of brevity, it will not be repeated here.

[0520] This device is used to implement the above embodiments and related implementation methods, and details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0521] Figure 5 A schematic diagram of a data transmission apparatus 1200 provided in an embodiment of this application is shown.

[0522] The device 1200 includes a transceiver unit 1210, which can be used to implement corresponding communication functions. The transceiver unit 12210 can also be called a communication interface or a communication unit.

[0523] The device 1200 may also include a processing unit 1220, which can be used for data processing.

[0524] Optionally, the apparatus 1200 further includes a storage unit, which can be used to store instructions and / or data. The processing unit 1220 can read the instructions and / or data in the storage unit, so as to make the apparatus realize the actions of different devices in the foregoing various method embodiments, for example, the actions of the first terminal device, the second terminal device, the first network device, or the second network device.

[0525] As a design, the apparatus 1200 is used to execute the actions performed by the terminal device in the various method embodiments.

[0526] Specifically, the processing unit 1220 is configured to obtain first information, the first information being used for a first network device to transmit first data to a first terminal device through a first communication path, the first information including a first packet detection rule (PDR); and the transceiver 1210 is configured to send, to a second network device through a second communication path, a first message including the first information and first indication information, the first indication information being used to indicate that the first data is transmitted through the first communication path and / or the second communication path.

[0527] Optionally, the transceiver 1210 is further configured to send, to a second terminal device, a first request message used to request to establish a first QoS flow on the first communication path, the first request message including second indication information used to obtain the first information; and the first terminal device receives the first information from the second terminal device.

[0528] Optionally, the first information is obtained by the first terminal device in establishing the first QoS flow on the first communication path.

[0529] Optionally, the first information further includes first QoS flow information on the first communication path, the first QoS flow information including an identifier of the second terminal device, an identifier QFI of the first QoS flow, and an identifier of a PDU session corresponding to the first QoS flow.

[0530] Optionally, the first information further includes third indication information used to indicate to perform reliability transmission or load balancing transmission.

[0531] Optionally, the first communication path is a communication path through which the first terminal device connects the first network device via the second terminal device, or the first communication path is a communication path through which the first terminal device directly connects the first network device.

[0532] Optionally, the first communication path comprises at least one QoS flow, the first QoS flow information comprises a PDR corresponding to the first QoS flow, and the first QoS flow is one of the at least one QoS flow.

[0533] The apparatus 1200 can implement the steps or procedures performed by the terminal device in the method embodiments according to the embodiments of the present application. The apparatus 1200 can include units for performing the steps of the methods. Figure 7 The apparatus 1200 can implement the steps or procedures performed by the terminal device in the method embodiments according to the embodiments of the present application. The apparatus 1200 can include units for performing the steps of the methods. Figure 9 、 Figure 10 、 Figure 11 and Figure 5 The apparatus 1200 can implement the steps or procedures performed by the terminal device in the method embodiments according to the embodiments of the present application. The apparatus 1200 can include units for performing the steps of the methods.

[0534] It should be understood that the specific processes by which the units perform the corresponding steps have been described in detail in the above method embodiments, and for the sake of brevity, will not be repeated here.

[0535] As a design, the apparatus 1200 is configured to perform the actions performed by the first network device in the various method embodiments.

[0536] Specifically, the transceiver 1210 is configured to receive first information and second information, the first information being used for the first network device to transmit data to a first terminal device through a first communication path, and the second information being used for the first network device to transmit data to the first terminal device through a second communication path; and further configured to receive first data and send the first data to the first terminal device through the first communication path and / or the second communication path.

[0537] Optionally, the processing unit 1220 is configured to determine a destination address and a source address according to the first information; and the first network device processes the first data according to the destination address and the source address, and sends the processed first data.

[0538] Optionally, the first communication path is a communication path through which the first terminal device receives data sent by the first network device through a second terminal device.

[0539] Optionally, the transceiver 1210 is further configured to receive third indication information, the third indication information being used to indicate reliability transmission or load balancing transmission.

[0540] Optionally, when the third indication information indicates reliable transmission, the processing unit 1220 is configured to duplicate IP packets of the first data, and the transceiver unit 1210 is configured to transmit the IP packets of the first data to the first terminal device through the first communication path and the second communication path respectively; or, when the second indication information indicates load balancing transmission, the processing unit 1220 is configured to split the IP packets of the first data, and the transceiver unit 1210 is configured to transmit the IP packets of the first data to the first terminal device through the first communication path and the second communication path respectively.

[0541] Optionally, the processing unit 1220 is further configured to determine, according to the third indication information, to transmit the first data to the first terminal device through the first communication path and / or the second communication path; or determine, according to the first information and the second information, to transmit the first data to the first terminal device through the first communication path and / or the second communication path.

[0542] Optionally, the transceiver unit 1210 is further configured to transmit the first data to a third network device, and transmit, by the third network device, the first data to the first terminal device through the first communication path.

[0543] Optionally, the first communication path includes at least one QoS flow, the first QoS flow information includes a PDR corresponding to the first QoS flow, the first QoS flow is one of the at least one QoS flow, the second communication path includes at least one QoS flow, the second QoS flow information includes a PDR corresponding to the second QoS flow, and the second QoS flow is one of the at least one QoS flow.

[0544] Optionally, the transceiver unit 1210 is further configured to receive an identifier QFI of the first QoS flow, and transmit the first data to a third network device, and the transceiver unit 1210 is specifically configured to encapsulate the first data into a GTP message, and transmit the GTP message to the third network device through a first tunnel, the GTP message including the identifier QFI of the first QoS flow, and the first tunnel being used for data transmission between the first network device and the third network device.

[0545] The apparatus 1200 can implement steps or procedures performed by the first network device in the method embodiments according to the embodiments of the present application. The apparatus 1200 can include units for performing the methods of the first network device in the embodiments shown in the specification, or include units for performing the methods of the UPF#1 or UPF#2 in the embodiments shown in the specification. Figure 7 The apparatus 1200 can implement steps or procedures performed by the first network device in the method embodiments according to the embodiments of the present application. The apparatus 1200 can include units for performing the methods of the first network device in the embodiments shown in the specification, or include units for performing the methods of the UPF#1 or UPF#2 in the embodiments shown in the specification. Figure 9 、 Figure 10 、 Figure 11 and Figure 13 The apparatus 1200 can implement steps or procedures performed by the first network device in the method embodiments according to the embodiments of the present application. The apparatus 1200 can include units for performing the methods of the first network device in the embodiments shown in the specification, or include units for performing the methods of the UPF#1 or UPF#2 in the embodiments shown in the specification.

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

[0547] Figure 13 A schematic diagram of a device 1300 for data transmission is shown. The device 1300 includes a processor 1310, the processor 1310 is coupled with a memory 1320, the memory 1320 is configured to store computer programs or instructions and / or data, and the processor 1310 is configured to execute the computer programs or instructions stored in the memory 1320, or read the data stored in the memory 1320, to perform the methods in the above method embodiments. As shown, the device 1300 further includes a transceiver 1330, the transceiver 1330 is configured to receive and / or send signals. For example, the processor 1310 is configured to control the transceiver 1330 to receive and / or send signals. Figure 5

[0548] Optionally, the processor 1310 is one or more.

[0549] Optionally, the memory 1320 is one or more.

[0550] Optionally, the memory 1320 is integrated with the processor 1310, or is separately arranged.

[0551] As an option, the device 1300 is configured to implement the operations performed by the first terminal device, the second terminal device, the first network device, or the second network device in the above method embodiments.

[0552] For example, the processor 1310 is configured to execute the computer programs or instructions stored in the memory 1320 to implement the related operations of the first access network device in the above method embodiments. For example, the processor 1310 is configured to execute the computer programs or instructions stored in the memory 1320 to implement the method performed by the first network device in the embodiment shown in any one of Figure 7 Figure 9 、 Figure 10 、 Figure 11 and the method performed by the UPF#1 in the embodiment shown in any one of Figure 5

[0553] For another example, the processor 1310 is configured to execute the computer programs or instructions stored in the memory 1320 to implement the related operations of the terminal device in the above method embodiments. For example, the processor 1310 is configured to execute the computer programs or instructions stored in the memory 1320 to implement the method performed by the first terminal device in the embodiment shown in any one of Figure 7 Figure 9 、 Figure 10 、 Figure 11 and the method performed by the remote UE in the embodiment shown in any one of ​ ​​​​​

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

[0555] It should also be understood that the memory mentioned in the embodiments of the present application can be a volatile memory and / or a non-volatile memory. The non-volatile memory can be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM). For example, the RAM can be used as an external cache. As an example but not limitation, the RAM includes the following various forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM) and direct rambus RAM (DR RAM).

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

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

[0558] The application further provides a computer readable medium, having stored thereon a computer program, which, when executed by a computer, implements the functions of any of the method embodiments described above.

[0559] The application further provides a computer program product, which, when executed by a computer, implements the functions of any of the method embodiments described above.

[0560] The application further provides a system, comprising the first access network device, the second access network device, the access and mobility management function device and the first session management function device described above.

[0561] In the embodiments described above, all or some of the embodiments can be implemented through software, hardware, firmware or any combination thereof. When implemented by software, all or some of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed by a computer, all or some of the processes or functions according to the embodiments described in the application are generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website site, computer, server or data center to another website site, computer, server or data center through a wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media sets. The available media can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (such as a solid state disk (solid state disk, SSD)), etc.

[0562] In the embodiments of the present application, the words "example", "for example", etc. are used to mean serving as an example, instance, or illustration. Any embodiment or design presented as an example in the present application should not be interpreted as being more preferred or advantageous than other embodiments or design schemes. Rather, the word "example" is used to present the concept in a specific manner.

[0563] It should be understood that the term "embodiment" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, the various embodiments throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner.

[0564] It should be understood that the size of the sequence number of each process described above in various embodiments of the present application does not mean the order of execution, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The names of all nodes and messages in the present application are only names set by the present application for convenience of description, and the names in the actual network can be different, and the present application should not be understood as limiting the names of various nodes and messages. On the contrary, any name with the same or similar function as the node or message used in the present application is regarded as a method or equivalent replacement of the present application, and is within the protection scope of the present application.

[0565] It should also be understood that in the present application, "when", "if" and "if" all refer to the corresponding processing of the UE or the base station under certain objective circumstances, not the time limit, and it is not required that the UE or the base station has a judgment action when implementing, nor does it mean that there are other limitations.

[0566] It should be noted that in the embodiments of the present application, "pre-setting", "pre-configuration" and the like can be realized by pre-saving corresponding codes, tables or other means for indicating related information in the device (for example, terminal equipment), and the specific implementation manner is not limited in the present application, for example, the rules and constants preset in the embodiments of the present application.

[0567] In addition, the terms "system" and "network" are often used interchangeably in this paper. The term "and / or" in this paper is only a description of the association relationship between the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent the following three cases: A exists alone, A and B exist together, B exists alone.

[0568] The term "at least one" or "at least one" in this paper means all or any combination of the listed items, for example, "at least one of A, B and C" can mean that A exists alone, B exists alone, C exists alone, A and B exist together, B and C exist together, A, B and C exist together. This paper means one or more. "Multiple" means two or more.

[0569] It should be understood that, in the embodiments of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that the determination of B according to A does not mean that B is determined only according to A, but B can also be determined according to A and / or other information. The terms "comprise", "contain", "have" and their variants mean "comprise but not limited to", unless otherwise specifically emphasized.

[0570] It should be understood that, in various embodiments of the present application, the first, second and various numerical numbers are only for the convenience of differentiation in description, and are not used to limit the scope of the embodiments of the present application. For example, different information is distinguished.

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

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

[0573] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be realized by other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0574] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiments of the present application.

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

[0576] If the functions are realized in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the parts of the present application that essentially contribute to the prior art or the parts of the technical solutions can be embodied in the form of software products. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage medium includes a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0577] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for data transmission, characterized in that, include: The first terminal device acquires first information, which is used by the first network device to transmit first data to the first terminal device through a first communication path. The first information includes a first packet detection rule (PDR). The first terminal device sends a first message to the second network device through a second communication path. The first message includes the first information and the first indication information. The first indication information is used to indicate that the first data is transmitted through the first communication path and / or the second communication path.

2. The method according to claim 1, characterized in that, The method further includes: The first terminal device sends a first request message to the second terminal device. The first request message is used to request the establishment of a first QoS flow on the first communication path. The first request message includes second indication information, which is used to obtain the first information. The first terminal device acquires first information, including: The first terminal device receives the first information from the second terminal device.

3. The method according to claim 1, characterized in that, The first information is obtained by the first terminal device when establishing the first QoS stream on the first communication path.

4. The method according to claim 1, characterized in that, The first information also includes first QoS flow information on the first communication path, the first QoS flow information including the identifier of the second terminal device, the identifier QFI of the first QoS flow, and the identifier of the PDU session corresponding to the first QoS flow.

5. The method according to any one of claims 1-4, characterized in that, The first information also includes third indication information, which is used to indicate whether to perform reliable transmission or load-balanced transmission.

6. The method according to any one of claims 1-4, characterized in that, The first communication path is the communication path through which the first terminal device connects to the first network device via the second terminal device, or the first communication path is the communication path through which the first terminal device directly connects to the first network device.

7. The method according to claim 4, characterized in that, The first communication path includes at least one QoS stream, the first QoS stream information includes the PDR corresponding to the first QoS stream, and the first QoS stream is one of the at least one QoS stream.

8. A method for data transmission, characterized in that, include: The first network device receives first information and second information from the second network device. The first information is used by the first network device to transmit data to the first terminal device through a first communication path. The first information is received by the second network device from the first terminal device through a second communication path. The second information is used by the first network device to transmit data to the first terminal device through the second communication path. The first network device receives the first data and sends the first data to the first terminal device through the first communication path and / or the second communication path.

9. The method according to claim 8, characterized in that, The first network device sends the first data to the first terminal device through the first communication path and / or the second communication path, including: The first network device determines the destination address and source address based on the first information; The first network device processes the first data according to the destination address and the source address, and then sends the processed first data.

10. The method according to claim 9, characterized in that, The first communication path is the communication path through which the first terminal device receives data sent by the first network device via the second terminal device.

11. The method according to any one of claims 8-10, characterized in that, The method further includes: The first network device receives a third indication information, which is used to indicate whether to perform reliable transmission or load-balanced transmission.

12. The method according to claim 11, characterized in that, The method further includes: When the third indication information indicates reliable transmission, the first network device copies the IP packets of the first data and sends the IP packets of the first data to the first terminal device through both the first communication path and the second communication path; or... When the second indication information indicates load balancing transmission, the first network device will split the IP packets of the first data and send the IP packets of the first data to the first terminal device through the first communication path and the second communication path respectively.

13. The method according to claim 11, characterized in that, The method further includes: The first network device determines, based on the third indication information, to send the first data to the first terminal device through the first communication path and / or the second communication path; or The first network device determines, based on the first information and the second information, to send the first data to the first terminal device through the first communication path and / or the second communication path.

14. The method according to any one of claims 8-10, characterized in that, The method further includes: The first network device sends the first data to the third network device, which then sends it to the first terminal device through the first communication path.

15. The method according to any one of claims 8-10, characterized in that, The first communication path includes at least one QoS stream, and the first QoS stream information includes the PDR corresponding to the first QoS stream, wherein the first QoS stream is one of the at least one QoS stream. The second communication path includes at least one QoS stream, and the second QoS stream information includes the PDR corresponding to the second QoS stream, wherein the second QoS stream is one of the at least one QoS stream.

16. The method according to claim 14, characterized in that, The first network device also receives the identifier (QFI) of the first QoS stream, and the first network device sends the first data to the third network device, including: The first network device encapsulates the first data into a GTP message and sends the GTP message to the third network device through a first tunnel. The GTP message includes the identifier QFI of the first QoS flow. The first tunnel is used for data transmission between the first network device and the third network device.

17. A data transmission system, characterized in that, The system includes: a first UPF, a first AMF, a second UPF, a second AMF, a first SMF, and a second SMF. The first AMF and the first SMF are network devices that provide services to a first terminal device, and the second AMF and the second SMF are network devices that provide services to a second terminal device. The first UPF transmits first data to the first terminal device through a first communication path and / or a second communication path, and the second UPF transmits the first data to the first terminal device through the second communication path. The first AMF is configured to: receive from the first terminal device and send a first message to the second AMF, the first message including first information and first indication information; receive from the second AMF the address of the second UPF and a first packet detection rule (PDR), the first PDR being the PDR corresponding to the first QoS flow on the first communication path; and send the address of the second UPF, the identifier of the first QoS flow, and the first indication information to the first SMF. The second AMF is configured to: receive the first message; determine the address of the second UPF and the first PDR based on the first message; the first SMF is configured to: receive the address of the second UPF, the identifier of the first QoS flow, and the first indication information; and send the first PDR, the second PDR, and the identifier of the first QoS flow to the first UPF based on the first indication information, the second PDR being the PDR corresponding to the second QoS flow on the second communication path; the first UPF is configured to: receive the first PDR, the second PDR, and the identifier of the first QoS flow; and transmit first data to the first terminal device through the first communication path and / or the second communication path; the second UPF is configured to: transmit the first data to the first terminal device through the second communication path.

18. The system according to claim 17, characterized in that, The first SMF is also used to establish a first tunnel based on the address of the second UPF, and the first tunnel is used for data transmission between the first UPF and the second UPF.

19. The system according to claim 17 or 18, characterized in that, The first information includes the first QoS flow information on the first communication path, the identifier of the second terminal device, the identifier QFI of the first QoS flow, and the identifier of the PDU session corresponding to the first QoS flow.

20. The system according to claim 19, characterized in that, The first AMF is also used to determine the second AMF based on the identifier of the second terminal device.

21. The system according to claim 17 or 18, characterized in that, The first message also includes a third indication, which is used to instruct the first UPF to perform reliable transmission or load-balanced transmission.

22. A data transmission apparatus, characterized in that, include: A unit for performing the method according to any one of claims 1 to 16.

23. A data transmission apparatus, characterized in that, include: A processor for executing a computer program stored in memory to cause the apparatus to perform the method as described in any one of claims 1 to 16.

24. The apparatus according to claim 23, characterized in that, The device also includes the memory.

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

26. A computer program product, characterized in that, The computer program product includes instructions for performing the method as described in any one of claims 1 to 16.

Images