WO2023103417A1 - 一种数据传输的方法和通信装置 - Google Patents

一种数据传输的方法和通信装置 Download PDF

Info

Publication number
WO2023103417A1
WO2023103417A1 PCT/CN2022/109557 CN2022109557W WO2023103417A1 WO 2023103417 A1 WO2023103417 A1 WO 2023103417A1 CN 2022109557 W CN2022109557 W CN 2022109557W WO 2023103417 A1 WO2023103417 A1 WO 2023103417A1
Authority
WO
WIPO (PCT)
Prior art keywords
functional entity
user plane
plane functional
session
entity
Prior art date
Application number
PCT/CN2022/109557
Other languages
English (en)
French (fr)
Inventor
金辉
窦凤辉
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023103417A1 publication Critical patent/WO2023103417A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/12—Communication route or path selection, e.g. power-based or shortest path routing based on transmission quality or channel quality

Definitions

  • the embodiments of the present application relate to the communication field, and more specifically, to a data transmission method and a communication device.
  • a remote (remote) user equipment can communicate with a data network (data network, DN) through two paths.
  • One is to communicate based on the Uu interface, that is, the remote UE directly accesses the operator network (for example, a base station), and communicates with the DN through the operator network.
  • This path can be called a direct path (direct path); the other is Communication based on the proximity-based services communication 5 (PC5) interface, that is, the remote UE accesses the operator network through the relay (relay), and then communicates with the DN through the operator network.
  • PC5 proximity-based services communication 5
  • the remote UE uses a single path (direct path or indirect path) for data transmission, which cannot dynamically meet service transmission requirements, such as delay or quality.
  • the embodiments of the present application provide a data transmission method and a communication device, which can indicate the path of the QoS flow, so that the transmission path between the remote terminal device and the data network has diversity, and can dynamically meet service requirements.
  • a data transmission method is provided, and the method may be executed by a terminal device, or may also be executed by a chip or a circuit configured in the terminal device, which is not limited in the present application.
  • the execution by the first terminal device is taken as an example for description below.
  • the method includes: the first terminal device acquires first information, where the first information includes an identifier of a first session of the first communication path, an identifier of a second session of the second communication path, and the The first identifier of the relay device; the first terminal device sends a first request message including the first information to the first mobility management entity, and the first request message is used to request to pass the first session and the The second session jointly transmits the first data.
  • the first terminal device can obtain the identifier of the first session of the direct path, and can also obtain the identifier of the second session of the non-direct path and the identifier of the relay device from the relay device, and according to the The identifier of the first session may also obtain the identifier of the second session of the non-direct path from the relay device and the identifier of the relay device may initiate a request to the first mobility management entity on the direct path, and the request is passed through the first session and The second session jointly transmits the first data, so that data can be jointly transmitted on the direct path and the non-direct path.
  • the first UPF of the direct path can establish a transmission channel with the second UPF of the non-direct path, so that the first terminal device can transmit part or all of the first QoS flow of the direct path through the direct path and the non-direct path
  • the data or part or all of the data of the second QoS flow of the non-direct path is transmitted to realize redundant transmission, load balancing transmission or switching transmission of data.
  • the first communication path is a direct path connecting the first terminal device to the network
  • the second communication path is an indirect path connecting the first terminal device to the network through a relay device.
  • the first information further includes an identifier of a first quality of service flow and/or an identifier of a second quality of service flow, and the first quality of service flow is the second quality of service flow.
  • the first request message further includes a first indication, and the first indication is used to indicate that the first session and the second session are used to jointly transmit the The first data, or, the first request message further includes the first indication and a second indication, where the second indication is used to describe the first data.
  • the first data includes all or part of the data streamed through the first quality of service, or the first data includes All or part of the data transmitted by a quality stream;
  • the first quality of service stream is a quality of service stream corresponding to the first session, and the second quality of service stream is a quality of service stream corresponding to the second session.
  • the identifier of the second session and the first identifier of the relay device are obtained by the first terminal device from the relay device.
  • the first request message further includes a third indication, and the third indication is used to indicate that the first communication path is an anchor path, or, the first Three indications are used to indicate that the second communication path is an anchor path, and the first communication path and the second communication path communicate with the application server through a user plane functional entity serving the anchor path. .
  • the first request message further includes an identifier of the first terminal device, and the identifier of the first terminal device corresponds to the second communication path.
  • a data transmission method is provided, and the method may be executed by a terminal device, or may also be executed by a chip or a circuit configured in the terminal device, which is not limited in the present application.
  • the following takes the implementation of the relay device as an example for description.
  • the method includes: the relay device acquiring third information, where the third information includes an identifier of a first session of the first communication path, an identifier of a second session of the second communication path, and the first The first identification of the terminal device;
  • the relay device sends a second request message including the third information to a second mobility management function entity, where the second request message is used to request that the first session and the second session jointly transmit the second request message. a data.
  • the relay device can obtain the identifier of the second session of the non-direct path, and can also obtain the identifier of the first session of the direct path and the identifier of the first terminal device from the first terminal device.
  • the identifier of the second session of the direct connection path may also be obtained from the first terminal device, and the identifier of the first session of the direct connection path and the identifier of the first terminal device may initiate a request to the second mobility management entity on the non-direct connection path, It is requested to jointly transmit the first data through the first session and the second session, so that data can be jointly transmitted on the direct path and the non-direct path.
  • the third information further includes an identifier of a second quality of service flow and/or an identifier of a first quality of service flow, and the first quality of service flow is the identifier of the first quality of service flow.
  • the second request message further includes a first indication, and the first indication is used to indicate that the first session and the second session are used to jointly transmit the The first data, or, the second request message further includes the first indication and a second indication, and the second indication is used to describe the first data.
  • the first data includes all or part of the data streamed through the first quality of service, or the first data includes All or part of the data transmitted by a quality stream;
  • the first quality of service stream is a quality of service stream corresponding to the first session, and the second quality of service stream is a quality of service stream corresponding to the second session.
  • the identifier of the first session and the first identifier of the first terminal device are acquired by the relay device from the first terminal device.
  • the first request message further includes a third indication
  • the third indication information is used to indicate that the first communication path is an anchor path
  • the The third indication information is used to indicate that the second communication path is an anchor path
  • the first communication path and the second communication path communicate with an application server through a user plane functional entity serving the anchor path.
  • a data transmission method is provided, and the method may be executed by a core network device, or may also be executed by a chip or a circuit configured in the core network device, which is not limited in this application.
  • the following takes execution by a core network device as an example for description.
  • the method comprises: a first mobility management entity receiving a first request message from said first terminal device, said first request message being used to request a first session and said second communication path over said first communication path
  • the second session of the second session jointly transmits the first data
  • the first request message includes first information
  • the first information includes the identifier of the first session, the identifier of the second session, and the first information of the relay device an identification
  • the first user plane functional entity and the second user plane functional entity transmit the first data
  • the first user plane functional entity serves the first communication path
  • the second user plane functional entity serves the second communication path; wherein, the first data is transmitted between one of the first user plane functional entity and the second user plane functional entity and an application server .
  • the first terminal device requests to jointly transmit the first data through the first session and the second session, and the first data can be transmitted between the first user plane functional entity and the second user plane functional entity, so that Realize the common transmission of data on the directly connected path and the non-directly connected path.
  • the first information further includes an identifier of a first quality of service flow and/or an identifier of a second quality of service flow, and the first quality of service flow is the second quality of service flow.
  • the first request message further includes a first indication, and the first indication is used to indicate that the first session and the second session are used to jointly transmit the First data; or, the first request message further includes the first indication and a second indication, where the second indication is used to describe the first data.
  • the first data includes all or part of the data streamed through the first quality of service, or the first data includes All or part of the data transmitted by a quality stream;
  • the first quality of service stream is a quality of service stream corresponding to the first session, and the second quality of service stream is a quality of service stream corresponding to the second session.
  • the first request message further includes a third indication, and the third indication is used to indicate that the first communication path is an anchor path, or, the first The three indications are used to indicate that the second communication path is an anchor path, and the first communication path and the second communication path communicate with the application server through a user plane functional entity serving the anchor path.
  • the first request message further includes an identifier of the first terminal device, and the identifier of the first terminal device corresponds to the second communication path.
  • the first mobility management entity determines a second mobility management entity according to the first identifier of the relay device, or, the first mobility management entity Determine a second session management function entity according to the first identifier of the relay device and the identifier of the second session; the second mobility management entity serves the relay device; the second session management function entity Serving the second session.
  • connection between the first user plane functional entity and the second user plane functional entity is established through the first session management functional entity and the second session management functional entity.
  • the first user plane functional entity and the second user plane functional entity transmit the first data through the first channel.
  • the establishment of the first user plane functional entity and the second user plane functional entity through the first session management functional entity and the second session management functional entity The first channel between, including: the first session management functional entity obtains first channel information from the first user plane functional entity and sends the first channel information to the second session management functional entity through the second session management functional entity
  • the second user plane functional entity the first channel information is used by the second user plane functional entity to send data to the first user plane functional entity through the first channel
  • the second session management function The entity obtains second channel information from the second user plane functional entity and sends the second channel information to the first user plane functional entity through the first session management functional entity, and the second channel information uses sending data from the first user plane functional entity to the second user plane functional entity through the first channel.
  • the first channel includes: the first mobility management entity determines the second mobility management entity according to the first identifier of the relay device; the first mobility management entity determines the second mobility management entity from the second mobility The management entity obtains the address of the second session management function entity; the first mobility management entity sends the address of the second session management function entity to the first session management function entity; the first session management function The entity acquires first channel information from the first user plane functional entity; the first session management functional entity sends the first channel information to the second session management functional entity according to the address of the second session management functional entity channel information; the second session management functional entity acquires second channel information from the second user plane functional entity; the second session management functional entity sends the second channel information to the first session management functional entity .
  • the first channel includes: the first mobility management entity determines the second mobility management entity according to the first identifier of the relay device; the first mobility management entity manages the The functional entity acquires first channel information from the first user plane functional entity; the second mobility management entity acquires second channel information from the second user plane functional entity through the second session management functional entity; The first mobility management entity sends the second channel information to the first user plane functional entity through the first session management functional entity; the second mobility management entity transmits the second channel information through the second session management functional entity sending the first channel information to the second user plane functional entity.
  • the first user plane functional entity is an anchor user plane functional entity
  • the first session management functional entity sends a first a rule
  • the first rule is used to instruct the first user plane functional entity to send part or all of the first data to the second user plane functional entity, so that the second user plane functional entity passes the
  • the second communication path sends the data received from the first user plane functional entity to the first terminal device; or, the first user plane functional entity is an anchor user plane functional entity, and the first session management function
  • the entity sends a second rule to the first user plane functional entity, where the second rule is used to instruct the first user plane functional entity to send data received from the second user plane functional entity to the application server or, the first user plane functional entity is an anchor user plane functional entity, the second session management functional entity sends a third rule to the second user plane functional entity, and the third rule is used to indicate that the The second user plane functional entity sends the first data received from the first terminal device to the first user plane functional entity; or, the first user plane functional entity is an anchor user
  • the second user plane functional entity is an anchor user plane functional entity
  • the first session management functional entity sends the first session management functional entity to the first user plane functional entity a rule
  • the first rule is used to instruct the first user plane functional entity to send the first data received from the first terminal device to the second user plane functional entity; or
  • the second user The functional entity of the user plane is an anchor user plane functional entity
  • the first session management functional entity sends a second rule to the first user plane functional entity
  • the second rule is used to instruct the first user plane functional entity to send a second rule to the first user plane functional entity.
  • the first terminal device sends the data received from the second user plane functional entity; or, the second user plane functional entity is an anchor user plane functional entity, and the second session management functional entity sends the data to the second user plane functional entity
  • the second user plane functional entity sends a third rule, where the third rule is used to instruct the second user plane functional entity to send part or all of the first data to the first user plane functional entity, so that the first user plane functional entity sends
  • a user plane functional entity sends the data received from the second user plane functional entity to the first terminal device through the first communication path; or, the second user plane functional entity is an anchor user plane functional entity , the second session management functional entity sends a fourth rule to the second user plane functional entity, the fourth rule is used to indicate that the second user plane functional entity will receive from the first user plane functional entity
  • the data is sent to the application server.
  • the first session management function entity receives the first information from the first mobility management entity, and the first session management function entity receives the first information according to the first session management function entity A message generates the first rule and the second rule; the second session management function entity receives second information from the first session management function entity or the second mobility management entity, and the second The session management function entity generates the third rule and the fourth rule according to the second information, where the second information includes: a first indication, an identifier of the second session, and a second An identifier, the second identifier of the relay device is determined by the first mobility management entity according to the first identifier of the relay device.
  • the second information further includes at least one of the following: the identifier of the second quality of service flow; the second indication; the identifier of the first terminal device ; or said third instruction.
  • a data transmission method is provided, and the method may be executed by a core network device, or may also be executed by a chip or a circuit configured in the core network device, which is not limited in the present application.
  • the following takes execution by a core network device as an example for description.
  • the method includes: a second mobility management function entity receives a second request message from the relay device, the second request message is used to request the first session and the second communication path through the first communication path
  • the second session of the second session jointly transmits the first data
  • the second request message includes third information
  • the third information includes the identifier of the first session, the identifier of the second session, and the ID of the first terminal device first identifier
  • after receiving the second request message the first user plane functional entity and the second user plane functional entity transmit the first data
  • the first user plane functional entity serves the first communication path
  • the second user plane functional entity serves the second communication path, wherein one of the first user plane functional entity and the second user plane functional entity transmits the first data.
  • the relay device requests to jointly transmit the first data through the first session and the second session, and the first data can be transmitted between the first user plane functional entity and the second user plane functional entity, thereby realizing Data is co-transmitted on both direct and non-direct paths.
  • the third information further includes the identifier of the second quality of service flow and/or the identifier of the first quality of service flow, and the second quality of service flow is the identifier of the first quality of service flow.
  • the second request message further includes a first indication, and the first indication is used to indicate that the first session and the second session are used to jointly transmit the The first data; or, the second request message further includes the first indication and a second indication, and the second indication is used to describe the first data.
  • the first data includes all or part of the data streamed through the first quality of service, or the first data includes All or part of the data transmitted by a quality stream;
  • the first quality of service stream is a quality of service stream corresponding to the first session, and the second quality of service stream is a quality of service stream corresponding to the second session.
  • the second request message further includes a third indication
  • the third indication is used to indicate that the first communication path is an anchor path, or, the first communication path
  • the three indications are used to indicate that the second communication path is an anchor path, and the first communication path and the second communication path communicate with the application server through a user plane functional entity serving the anchor path.
  • the second mobility management entity determines the first mobility management entity according to the first identifier of the first terminal device, or, the second mobility management entity The entity determines a first session management function entity according to the first identifier of the first terminal device and the identifier of the first session; the first mobility management entity serves the first terminal device, and the first session A management functional entity serves the first session.
  • the transmission of the first data by the first user plane functional entity and the second user plane functional entity includes: using the first session management functional entity and the The second session management functional entity establishes a first channel between the first user plane functional entity and the second user plane functional entity; the first user plane functional entity and the second user plane functional entity pass the The first channel transmits the first data.
  • the establishment of the first user plane functional entity and the second user plane functional entity through the first session management functional entity and the second session management functional entity The first channel between, including: the first session management functional entity obtains first channel information from the first user plane functional entity and sends the first channel information to the second session management functional entity through the second session management functional entity
  • the second user plane functional entity the first channel information is used by the second user plane functional entity to send data to the first user plane functional entity through the first channel
  • the second session management function The entity acquires second channel information from the second user plane functional entity and sends the second channel information to the first user plane functional entity through the first session management functional entity, and the first channel information uses sending data from the first user plane functional entity to the second user plane functional entity through the first channel.
  • the first channel includes: the second mobility management entity determines the first mobility management entity according to the first identifier of the first terminal device; the second mobility management entity The mobility management entity obtains the address of the first session management function entity; the second mobility management entity sends the address of the first session management function entity to the second session management function entity; the second session management The functional entity obtains the second channel information from the second user plane functional entity; the second session management functional entity sends the first session management functional entity to the first session management functional entity according to the address of the first session management functional entity Two channel information; the first session management functional entity obtains the first channel information from the first user plane functional entity; the first session management functional entity sends the first channel to the second session management functional entity information.
  • the first channel includes: the second mobility management entity determines the first mobility management entity according to the first identifier of the first terminal device; the second mobility management entity determines the first mobility management entity through the second session
  • the management functional entity acquires second channel information from the second user plane functional entity; the first mobility management entity acquires first channel information from the first user plane functional entity through the first session management functional entity;
  • the second mobility management entity sends the first channel information to the second user plane functional entity through the second session management functional entity; the first mobility management entity transmits the first channel information through the first session management functional entity
  • the entity sends the second channel information to the first user plane function entity.
  • the first user plane functional entity is an anchor user plane functional entity
  • the first session management functional entity sends a first a rule
  • the first rule is used to instruct the first user plane functional entity to send part or all of the first data to the second user plane functional entity, so that the second user plane functional entity passes the
  • the second communication path sends the data received from the first user plane functional entity to the first terminal device; or, the first user plane functional entity is an anchor user plane functional entity, and the first session management function
  • the entity sends a second rule to the first user plane functional entity, where the second rule is used to instruct the first user plane functional entity to send data received from the second user plane functional entity to the application server or, the first user plane functional entity is an anchor user plane functional entity, the second session management functional entity sends a third rule to the second user plane functional entity, and the third rule is used to indicate that the The second user plane functional entity sends the first data received from the first terminal device to the first user plane functional entity; or, the first user plane functional entity is an anchor user
  • the second user plane functional entity is an anchor user plane functional entity
  • the first session management functional entity sends the first session management functional entity to the first user plane functional entity a rule
  • the first rule is used to instruct the first user plane functional entity to send the first data received from the first terminal device to the second user plane functional entity; or
  • the second user The functional entity of the user plane is an anchor user plane functional entity
  • the first session management functional entity sends a second rule to the first user plane functional entity
  • the second rule is used to instruct the first user plane functional entity to send a second rule to the first user plane functional entity.
  • the first terminal device sends the data received from the second user plane functional entity; or, the second user plane functional entity is an anchor user plane functional entity, and the second session management functional entity sends the data to the second user plane functional entity
  • the second user plane functional entity sends a third rule, where the third rule is used to instruct the second user plane functional entity to send part or all of the first data to the first user plane functional entity, so that the first user plane functional entity sends
  • a user plane functional entity sends the data received from the second user plane functional entity to the first terminal device through the first communication path; or, the second user plane functional entity is an anchor user plane functional entity , the second session management functional entity sends a fourth rule to the second user plane functional entity, the fourth rule is used to indicate that the second user plane functional entity will receive from the first user plane functional entity
  • the data is sent to the application server.
  • the second session management function entity receives the third information from the second mobility management entity, and the second session management function entity receives the third information according to the first session management function entity
  • the third information generates the first rule and the second rule
  • the first session management function entity receives fourth information from the second session management function entity or the first mobility management entity
  • the first session management function entity receives fourth information
  • the first The session management function entity generates the third rule and the fourth rule according to the fourth information, where the fourth information includes: the first indication, the identifier of the first session, and the first terminal device's first Two identifiers, where the second identifier of the first terminal device is determined by the second mobility management entity according to the first identifier of the first terminal device.
  • the fourth information further includes at least one of the following: an identifier of the first quality of service flow; the second indication; an identifier of the relay device; Or, the third indication.
  • a data transmission device may be a terminal device, or may also be a chip or a circuit configured in the terminal device, which is not limited in the present application.
  • the following uses the first terminal device as an example for description.
  • the device includes: a transceiver unit, configured to acquire first information, where the first information includes an identifier of a first session of the first communication path, an identifier of a second session of the second communication path, and the relay The first identifier of the device; the transceiving unit is further configured to send a first request message including the first information to the first mobility management entity, where the first request message is used to request to pass the first session and the The second session jointly transmits the first data.
  • the first terminal device can obtain the identifier of the first session of the direct path, and can also obtain the identifier of the second session of the non-direct path and the identifier of the relay device from the relay device, and according to the The identifier of the first session may also obtain the identifier of the second session of the non-direct path from the relay device and the identifier of the relay device may initiate a request to the first mobility management entity on the direct path, and the request is passed through the first session and The second session jointly transmits the first data, so that data can be jointly transmitted on the direct path and the non-direct path.
  • the first communication path is a direct path connecting the first terminal device to the network
  • the second communication path is an indirect path connecting the first terminal device to the network through a relay device.
  • the first information further includes an identifier of a first quality of service flow and/or an identifier of a second quality of service flow, and the first quality of service flow is the second quality of service flow.
  • the first request message further includes a first indication, and the first indication is used to indicate that the first session and the second session are used to jointly transmit the The first data, or, the first request message further includes the first indication and a second indication, where the second indication is used to describe the first data.
  • the first data includes all or part of the data streamed through the first quality of service, or the first data includes All or part of the data transmitted by a quality stream;
  • the first quality of service stream is a quality of service stream corresponding to the first session, and the second quality of service stream is a quality of service stream corresponding to the second session.
  • the identifier of the second session, the identifier of the second quality of service flow, and the first identifier of the relay device are Obtained by the above relay device.
  • the first request message further includes a third indication, and the third indication is used to indicate that the first communication path is an anchor path, or, the first communication path Three indications are used to indicate that the second communication path is an anchor path, and the first communication path and the second communication path communicate with the application server through a user plane functional entity serving the anchor path. .
  • the first request message further includes an identifier of the first terminal device, and the identifier of the first terminal device corresponds to the second communication path.
  • a data transmission device may be a terminal device, or may also be a chip or a circuit configured in the terminal device, which is not limited in the present application.
  • the following takes the implementation of the relay device as an example for description.
  • the device includes: a transceiver unit, configured to acquire third information, where the third information includes an identifier of a first session of the first communication path, an identifier of a second session of the second communication path, and the first The first identifier of the terminal device; the transceiving unit is further configured for the relay device to send a second request message including the third information to the second mobility management functional entity, and the second request message is used to request to pass The first session and the second session jointly transmit first data.
  • the relay device can obtain the identifier of the second session of the non-direct path, and can also obtain the identifier of the first session of the direct path and the identifier of the first terminal device from the first terminal device.
  • the identifier of the second session of the direct connection path may also be obtained from the first terminal device, and the identifier of the first session of the direct connection path and the identifier of the first terminal device may initiate a request to the second mobility management entity on the non-direct connection path, It is requested to jointly transmit the first data through the first session and the second session, so that data can be jointly transmitted on the direct path and the non-direct path.
  • the third information further includes an identifier of a second quality of service flow and/or an identifier of a first quality of service flow, and the first quality of service flow is the identifier of the first quality of service flow.
  • the second request message further includes a first indication, and the first indication is used to indicate that the first session and the second session are used to jointly transmit the The first data, or, the second request message further includes the first indication and a second indication, and the second indication is used to describe the first data.
  • the first data includes all or part of the data streamed through the first quality of service, or the first data includes All or part of the data transmitted by a quality stream;
  • the first quality of service stream is a quality of service stream corresponding to the first session, and the second quality of service stream is a quality of service stream corresponding to the second session.
  • the identifier of the first session, the identifier of the first quality of service flow, and the first identifier of the first terminal device are obtained from the relay device. acquired by the first terminal device.
  • the first request message further includes a third indication
  • the third indication information is used to indicate that the first communication path is an anchor path
  • the The third indication information is used to indicate that the second communication path is an anchor path
  • the first communication path and the second communication path communicate with the application server through a user plane functional entity serving the anchor path.
  • a data transmission device may be a core network device, or may also be a chip or a circuit configured in the core network device, which is not limited in this application.
  • the core network equipment is taken as an example for description below.
  • the apparatus includes: a transceiving unit, configured to receive a first request message from the first terminal device, the first request message being used to request a first session via the first communication path and a session of the second communication path
  • the second session jointly transmits the first data
  • the first request message includes first information
  • the first information includes an identifier of the first session, an identifier of the second session, and the first information of the relay device.
  • the transceiver unit is further configured to transmit the first data to the first user plane functional entity and the second user plane functional entity, where the first user plane functional entity serves the The first communication path, the second user plane functional entity serves the second communication path; wherein, between the first user plane functional entity and the second user plane functional entity and the application server transmit the first data.
  • the first terminal device requests to jointly transmit the first data through the first session and the second session, and the first data can be transmitted between the first user plane functional entity and the second user plane functional entity, so that Realize the common transmission of data on the directly connected path and the non-directly connected path.
  • the first information further includes an identifier of a first quality of service flow and/or an identifier of a second quality of service flow, and the first quality of service flow is the second quality of service flow.
  • the first request message further includes a first indication, and the first indication is used to indicate that the first session and the second session are used to jointly transmit the First data; or, the first request message further includes the first indication and a second indication, where the second indication is used to describe the first data.
  • the first data includes all or part of the data streamed through the first quality of service, or the first data includes All or part of the data transmitted by a quality stream;
  • the first quality of service stream is a quality of service stream corresponding to the first session, and the second quality of service stream is a quality of service stream corresponding to the second session.
  • the first request message further includes a third indication, and the third indication is used to indicate that the first communication path is an anchor path, or, the first communication path
  • the three indications are used to indicate that the second communication path is an anchor path, and the first communication path and the second communication path communicate with the application server through a user plane functional entity serving the anchor path.
  • the first request message further includes an identifier of the first terminal device, and the identifier of the first terminal device corresponds to the second communication path.
  • the apparatus includes: a processing unit configured to determine a second mobility management entity according to the first identifier of the relay device, or the processing unit is configured to determine a second mobility management entity according to the The first identifier of the relay device and the identifier of the second session determine a second session management function entity; the second mobility management entity serves the relay device, and the second session management function entity serves in the second session.
  • the processing unit is specifically configured to establish the first user plane function entity and the second session management function entity through the first session management function entity and the second session management function entity.
  • a first channel between two user plane functional entities; the first user plane functional entity and the second user plane functional entity transmit the first data through the first channel.
  • the processing unit is configured to instruct the transceiver unit to acquire first channel information from the first user plane functional entity and pass the first channel information through the second
  • the session management function entity sends the information to the second user plane function entity, and the first channel information is used for the second user plane function entity to send data to the first user plane function entity through the first channel
  • the processing unit is configured to instruct the transceiver unit to acquire second channel information from the second user plane functional entity and send the second channel information to the first user plane functional entity through the first session management functional entity, The second channel information is used for the first user plane functional entity to send data to the second user plane functional entity through the first channel.
  • the processing unit is specifically configured to determine the second mobility management entity according to the first identifier of the relay device;
  • the property management entity acquires the address of the second session management function entity;
  • the transceiver unit is further configured to send the address of the second session management function entity to the first session management function entity;
  • the transceiver unit is further configured to receive from the first session management function entity
  • a user plane functional entity acquires first channel information;
  • the processing unit is further configured to instruct the transceiver unit to send the first channel information to the second session management functional entity according to the address of the second session management functional entity;
  • the transceiver unit It is further configured to acquire second channel information from the second user plane functional entity;
  • the transceiver unit is further configured to send the second channel information to the first session management functional entity.
  • the transceiver unit is further configured to determine the second mobility management entity according to the first identifier of the relay device;
  • the plane functional entity acquires the first channel information;
  • the transceiver unit is further configured to acquire the second channel information from the second user plane functional entity;
  • the transceiver unit is further configured to send the first user plane information to the first user plane
  • the functional entity sends the second channel information;
  • the transceiver unit is further configured to send the first channel information to the second user plane functional entity through the second session management functional entity.
  • the first user plane functional entity is an anchor user plane functional entity
  • the transceiver unit is further configured to send the first rule to the first user plane functional entity, so The first rule is used to instruct the first user plane functional entity to send part or all of the first data to the second user plane functional entity, so that the second user plane functional entity passes the second communication
  • the path sends the data received from the first user plane functional entity to the first terminal device; or, the first user plane functional entity is an anchor user plane functional entity, and the transceiver unit is further configured to send data to the first user plane functional entity
  • the user plane functional entity sends a second rule, where the second rule is used to instruct the first user plane functional entity to send the data received from the second user plane functional entity to the application server; or, the first user plane functional entity sends the data received from the second user plane functional entity to the application server;
  • a user plane functional entity is an anchor user plane functional entity
  • the transceiver unit is further configured to send a third rule to the second user plane functional entity, and
  • the second user plane functional entity is an anchor user plane functional entity
  • the transceiver unit is further configured to send the first rule to the first user plane functional entity, so The first rule is used to instruct the first user plane functional entity to send the first data received from the first terminal device to the second user plane functional entity; or, the second user plane functional entity is an anchor user plane functional entity, the transceiver unit is further configured to send a second rule to the first user plane functional entity, and the second rule is used to instruct the first user plane functional entity to send the first terminal device sending the data received from the second user plane functional entity; or, the second user plane functional entity is an anchor user plane functional entity, and the transceiver unit is further configured to send a third rule to the second user plane functional entity , the third rule is used to instruct the second user plane functional entity to send part or all of the first data to the first user plane functional entity, so that the first user plane functional entity passes the first user plane functional entity A communication path sends the data received from the second user plane functional entity
  • the transceiver unit is further configured to receive the first information from the first mobility management entity, and the processing unit is further configured to generate the first information according to the first information.
  • a rule and the second rule; the transceiver unit is further configured to receive second information from the first session management function entity or the second mobility management entity, and the processing unit is further configured to generate the second information according to the second information.
  • the third rule and the fourth rule, the second information includes: a first indication, an identifier of the second session, and a second identifier of the relay device, and the second identifier of the relay device is Determined by the first mobility management entity according to the first identifier of the relay device.
  • the second information further includes at least one of the following: the identifier of the second quality of service flow; the second indication; the identifier of the first terminal device ; or said third instruction.
  • a data transmission device may be a core network device, or may also be a chip or a circuit configured in the core network device, which is not limited in the present application.
  • the core network device is taken as an example for description below.
  • the apparatus includes: a transceiving unit, configured to receive a second request message from the relay device, the second request message is used to request the first session through the first communication path and the second session of the second communication path
  • the two sessions jointly transmit the first data
  • the second request message includes third information
  • the third information includes an identifier of the first session, an identifier of the second session, and a first identification
  • the transceiver unit is further configured to transmit the first data between the first user plane functional entity and the second user plane functional entity, where the first user plane functional entity serves The first communication path, the second user plane functional entity serving the second communication path, wherein, one of the first user plane functional entity and the second user plane functional entity and an application server transmit the first data between.
  • the relay device requests to jointly transmit the first data through the first session and the second session, and the first data can be transmitted between the first user plane functional entity and the second user plane functional entity, thereby realizing Data is co-transmitted on both direct and non-direct paths.
  • the third information further includes an identifier of a second quality of service flow and/or an identifier of a first quality of service flow, and the second quality of service flow is the identifier of the first quality of service flow.
  • the second request message further includes a first indication, and the first indication is used to indicate that the first session and the second session are used to jointly transmit the The first data; or, the second request message further includes the first indication and a second indication, and the second indication is used to describe the first data.
  • the first data includes all or part of the data streamed through the first quality of service, or the first data includes All or part of the data transmitted by a quality stream;
  • the first quality of service stream is a quality of service stream corresponding to the first session, and the second quality of service stream is a quality of service stream corresponding to the second session.
  • the second request message further includes a third indication, and the third indication is used to indicate that the first communication path is an anchor path, or, the first communication path
  • the three indications are used to indicate that the second communication path is an anchor path, and the first communication path and the second communication path communicate with the application server through a user plane functional entity serving the anchor path.
  • the apparatus further includes: a processing unit configured to determine the first mobility management entity according to the first identifier of the first terminal device, or the processing unit is further configured to Determine the first session management function entity according to the first identifier of the first terminal device and the identifier of the first session; the first mobility management entity serves the first terminal device, and the first session management A functional entity serves the first session.
  • the processing unit is specifically configured to establish the first user plane functional entity and the second user plane functional entity through the first session management functional entity and the second session management functional entity.
  • a first channel between functional entities of the user plane; the first data is transmitted by the first functional entity of the user plane and the functional entity of the second user plane through the first channel.
  • the transceiver unit is specifically configured to obtain first channel information from the first user plane functional entity and pass the first channel information through the second session management functional entity sending to the second user plane functional entity, the first channel information is used for the second user plane functional entity to send data to the first user plane functional entity through the first channel; the transceiver unit is also used for Obtaining second channel information from the second user plane functional entity and sending the second channel information to the first user plane functional entity through the first session management functional entity, where the first channel information is used for The first user plane functional entity sends data to the second user plane functional entity through the first channel.
  • the processing unit is further configured to determine the first mobility management entity according to the first identifier of the first terminal device;
  • the mobility management entity acquires the address of the first session management function entity;
  • the transceiver unit is further configured to send the address of the first session management function entity to the second session management function entity;
  • the transceiver unit is further configured to receive from the The second user plane functional entity acquires the second channel information;
  • the processing unit is further configured to instruct the transceiving unit to send the second channel information to the first session management functional entity according to the address of the first session management functional entity;
  • the unit is further configured to acquire first channel information from the first user plane functional entity;
  • the transceiver unit is further configured to send the first channel information to the second session management functional entity.
  • the processing unit is further configured to determine the first mobility management entity according to the first identifier of the first terminal device; the transceiver unit is further configured to pass the second The session management functional entity acquires second channel information from the second user plane functional entity; the transceiver unit is further configured to acquire first channel information from the first user plane functional entity through the first session management functional entity; the transceiver unit is further configured to send the first channel information to the second user plane functional entity through the second session management functional entity; the transceiver unit is further configured to send the first channel information to the first user plane functional entity through the first session management functional entity The functional entity sends the second channel information.
  • the first user plane functional entity is an anchor user plane functional entity
  • the transceiver unit is further configured to send the first rule to the first user plane functional entity, so The first rule is used to instruct the first user plane functional entity to send part or all of the first data to the second user plane functional entity, so that the second user plane functional entity passes the second communication
  • the path sends the data received from the first user plane functional entity to the first terminal device; or, the first user plane functional entity is an anchor user plane functional entity, and the transceiver unit is further configured to send data to the first user plane functional entity
  • the user plane functional entity sends a second rule, where the second rule is used to instruct the first user plane functional entity to send the data received from the second user plane functional entity to the application server; or, the first user plane functional entity sends the data received from the second user plane functional entity to the application server;
  • a user plane functional entity is an anchor user plane functional entity
  • the transceiver unit is further configured to send a third rule to the second user plane functional entity, and
  • the second user plane functional entity is an anchor user plane functional entity
  • the transceiver unit is further configured to send the first rule to the first user plane functional entity, so The first rule is used to instruct the first user plane functional entity to send the first data received from the first terminal device to the second user plane functional entity; or, the second user plane functional entity is an anchor user plane functional entity, the transceiver unit is further configured to send a second rule to the first user plane functional entity, and the second rule is used to instruct the first user plane functional entity to send the first terminal device sending the data received from the second user plane functional entity; or, the second user plane functional entity is an anchor user plane functional entity, and the transceiver unit is further configured to send a third rule to the second user plane functional entity , the third rule is used to instruct the second user plane functional entity to send part or all of the first data to the first user plane functional entity, so that the first user plane functional entity passes the first user plane functional entity A communication path sends the data received from the second user plane functional entity
  • the transceiver unit is further configured to receive the third information from the second mobility management entity, and the processing unit is further configured to generate the third information according to the third information A rule and the second rule; the transceiver unit is further configured to receive fourth information from the second session management function entity or the first mobility management entity, and the processing unit is further configured to generate the fourth information according to the fourth information
  • the third rule and the fourth rule, the fourth information includes: the first indication, the identifier of the first session, and the second identifier of the first terminal device, and the second identifier of the first terminal device
  • the identity is determined by the second mobility management entity according to the first identity of the first terminal device.
  • the fourth information further includes at least one of the following: the identifier of the first quality of service flow; the second indication; the identifier of the relay device; Or, the third indication.
  • a data transmission method is provided, and the method may be executed by a first terminal device, or may also be executed by a chip or a circuit configured in the first terminal device, which is not limited in the present application.
  • the following takes execution by the first terminal device as an example for description.
  • the method includes: the first terminal device acquires first information, the first information is used for the first network device to transmit first data to the first terminal device through the first communication path, and the first information includes the first A packet detection rule PDR; the first terminal device sends a first message to a second network device through a second communication path, the first message includes the first information and first indication information, and the first indication information It is used to indicate to transmit the first data through the first communication path and/or the second communication path.
  • 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 that the first network device can send the first information to the first network device through the first communication path and/or the second communication path.
  • the transmission of the first data by the first terminal device can realize simultaneous data transmission on the direct connection path and the non-direct connection path, so that the transmission paths between the remote terminal device and the data network are diversified and can dynamically meet service requirements.
  • the first terminal device sends a first request message to the second terminal device, and the first request message is used to request Establishing a first QoS flow, the first request message includes second indication information, and the second indication information is used to acquire the first information; the first terminal device receives the first QoS flow from the second terminal device a message.
  • the first communication path in the above solution is an indirect path.
  • the first information is QoS flow information of the first QoS flow established on the indirect path.
  • the first information is obtained when the first terminal device establishes a first QoS flow on the first communication path.
  • the first communication path is a direct connection path.
  • the first information is the QoS flow information obtained when establishing the first QoS flow on the direct path.
  • the first information further includes first QoS flow information on the first communication path, and the first QoS flow information includes the second terminal device's ID, the ID QFI of the first QoS flow, and the ID of the PDU session corresponding to the first QoS flow.
  • the first information further includes third indication information, where the third indication information is used to indicate reliable transmission or load balancing transmission.
  • the first communication path is a communication path through which the first terminal device connects to the first network device through the second terminal device, or, the The first communication path is a communication path through which the first terminal device is directly connected to the first network device.
  • 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 The QoS flow is one of the at least one QoS flow.
  • a data transmission method is provided, and the method may be executed by a first network device, or may also be executed by a chip or a circuit configured in the first network device, which is not limited in this application.
  • the following takes execution by the first network device as an example for description.
  • the method includes: the first network device receives first information and second information, the first information is used for the first network device to transmit data to the first terminal device through a first communication path, and the second information is used for The first network device transmits data to the first terminal device through the second communication path; the first network device receives the first data, and transmits data to the first terminal device through the first communication path and/or the second communication path A terminal device sends the first data.
  • the first network device can receive the first information and the second information, and can transmit data to the first terminal device through the first communication path according to the first information, and can transmit data to the first terminal device through the second communication path according to the second information.
  • the data transmission of the device can realize the simultaneous data transmission on the direct connection path and the non-direct connection path, so that the transmission paths between the remote terminal equipment and the data network are diversified and can dynamically meet business needs.
  • 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 according to the first information; the first network device processes the first data according to the destination address and source address, and sends the processed first data.
  • the first communication path is a communication path for the first terminal device to receive data sent by the first network device through the second terminal device.
  • the first network device receives third indication information, where the third indication information is used to indicate reliable transmission or load balancing transmission.
  • the first network device when the third indication information indicates reliable transmission, copies the IP packet of the first data, and passes the The first communication path and the second communication path send the IP packet of the first data to the first terminal device; or, when the second indication information indicates load balancing transmission, the first network device sends the IP packet of the first data splitting the IP packets of the first data, and sending the IP packets of the first data to the first terminal device through the first communication path and the second communication path respectively.
  • the first network device determines, according to the third indication information, to send a message to the first terminal through the first communication path and/or the second communication path The device sends the first data; or the first network device determines to send the first data to the first terminal device through the first communication path and/or the second communication path according to the first information and the second information the first data.
  • the first network device sends the first data to a third network device, and the third network device sends the first data through the first communication path. to the first terminal device.
  • 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 The 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
  • the second QoS flow is One of the at least one QoS flow.
  • the first network device encapsulates the first data into a GTP message, and sends the GTP message to the third network device through the first channel , the GTP message includes an identifier QFI of the first QoS flow, and the first channel is used for data transmission between the first network device and the third network device.
  • a data transmission system includes: a first UPF, a first AMF, a second UPF, a second AMF, a first SMF, a second SMF, the first AMF and the first AMF
  • An SMF is a network device that provides services for the first terminal device
  • the second AMF and the second SMF are network devices that provide services for the second terminal device
  • the first UPF passes the first communication path and/or
  • the second communication path transmits the first data to the first terminal device
  • the second UPF transmits the first data to the first terminal device through the second communication path
  • the first AMF uses Therefore, receiving from the first terminal device and sending a first message to the second AMF, the first message including first information and first indication information; receiving the address of the second UPF and the first message from the second AMF Packet detection rule PDR, the first PDR is the PDR corresponding to the first QoS flow on the first communication path; send the address of the second UPF, the identifier of the first Q
  • the first SMF is further configured to establish a first channel according to the address of the second UPF, and the first channel is used for the second UPF A UPF performs data transmission with the second UPF.
  • the first information includes first QoS flow information on the first communication path, and the first QoS flow information of the second terminal The identifier of the device, the identifier QFI of the first QoS flow, and the identifier of the PDU session corresponding to the first QoS flow.
  • the first AMF is further configured to determine the second AMF according to the identifier of the second terminal device.
  • the first message further includes third indication information, and the third indication information is used to instruct the first UPF to perform reliable transmission or load transmission. Balanced transmission.
  • a device for data transmission may be a first terminal device, or may also be a chip or a circuit configured in the first terminal device, which is not limited in this application.
  • the apparatus includes: a processing unit, configured to acquire first information, the first information is used for a first network device to transmit first data to the first terminal device through the first communication path, and the first information includes The first packet detection rule PDR; a transceiver unit, configured to send a first message to a second network device through a second communication path, the first message includes the first information and first indication information, and the first indication information It is used to indicate to transmit the first data through the first communication path and/or the second communication path.
  • the above-mentioned transceiving unit is specifically configured to send a first request message to the second terminal device, and the first request message is used to request that the first communication A first QoS flow is established on a path, the first request message includes second indication information, and the second indication information is used to obtain the first information; and the first information is received from the second terminal device.
  • the first information is obtained when the first terminal device establishes a first QoS flow on the first communication path.
  • the first information further includes first QoS flow information on the first communication path, and the first QoS flow information includes the second terminal The identifier of the device, the identifier QFI of the first QoS flow, and the identifier of the PDU session corresponding to the first QoS flow.
  • the first information further includes third indication information, where the third indication information is used to indicate reliable transmission or load balancing transmission.
  • the first communication path is a communication path through which the first terminal device connects to the first network device through the second terminal device, or , the first communication path is a communication path through which the first terminal device is directly connected to the first network device.
  • 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 The first QoS flow is one of the at least one QoS flow.
  • a device for data transmission may be a first network device, or may also be a chip or a circuit configured in the first network device, which is not limited in this application.
  • the device includes: a transceiver unit, configured to receive first information and second information, the first information is used by the first network device to transmit data to the first terminal device through a first communication path, and the second information is used The first network device transmits data to the first terminal device through the second communication path; the transceiver unit is further configured to: receive the first data, and transmit data to the first terminal device through the first communication path and/or the second communication path The first terminal device sends the first data.
  • the apparatus further includes a processing unit configured to determine a destination address and a source address according to the first information; The first data is processed, and the processed first data is sent.
  • the first communication path is a communication path through which the first terminal device receives data sent by the first network device through the second terminal device.
  • the transceiver unit is further configured to receive third indication information, where the third indication information is used to indicate reliable transmission or load balancing transmission.
  • the processing unit when the third indication information indicates reliable transmission, the processing unit is specifically configured to: copy the IP packet of the first data, The transceiver unit is specifically configured to: send the IP packet 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 For load balancing transmission, the processing unit is specifically configured to: offload the IP packets of the first data, and the transceiver unit is specifically configured to: transmit data to the The first terminal device sends the IP packet of the first data.
  • the processing unit is further configured to: determine, according to the third indication information, whether to communicate with the user through the first communication path and/or the second communication path.
  • the first terminal device sends the first data; or, according to the first information and the second information, it is determined to send the first data to the first terminal device through the first communication path and/or the second communication path Describe the first data.
  • the transceiver unit is further configured to send the first data to a third network device, and the third network device transmits the first data through the first The communication path is sent to the first terminal device.
  • 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 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 the PDR corresponding to the second QoS flow
  • the first QoS flow The flow is one of the at least one QoS flow.
  • the transceiver unit 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 : the transceiver unit encapsulates the first data into a GTP message, and sends the GTP message to the third network device through a first channel, where the GTP message includes the identifier QFI of the first QoS flow, so The first channel is used for data transmission between the first network device and the third network device.
  • the present application provides a processor configured to execute the methods provided in the foregoing aspects.
  • the processor's output and reception, input and other operations can also be understood as the sending and receiving operations performed by the radio frequency circuit and the antenna, which is not limited in this application.
  • the present application provides a communication device, which includes: a memory for storing programs; at least one processor for executing the computer programs or instructions stored in the memory to perform any of the above aspects or its implementation method provided.
  • the apparatus is a first terminal device, a second terminal device, a first network device, and a second network device.
  • the apparatus is a chip, a chip system, or a circuit used in the first terminal device, the second terminal device, the first network device, or the second network device.
  • the present application provides a computer-readable storage medium, where the computer-readable medium stores program code for execution by a device, and the program code includes a method for executing any one of the above aspects or its implementation.
  • the present application provides a computer program product containing instructions.
  • the computer program product When the computer program product is run on a computer, it causes the computer to execute the method provided by any one of the above aspects or its implementation.
  • the present application provides a chip.
  • the chip includes a processor and a communication interface.
  • the processor reads the instructions stored in the memory through the communication interface, and executes the method provided by any one of the above aspects or its implementation.
  • the chip further includes a memory, in which computer programs or instructions are stored, and the processor is used to execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, the processor is used to execute The method provided by any one of the above aspects or its implementation.
  • the present application provides a communication system, including the above-mentioned first terminal device, relay device, first mobility management entity, second mobility management entity, first session management functional entity, and second session management entity A functional entity, a first user plane functional entity and a second user plane functional entity.
  • Fig. 1 shows a schematic diagram of a communication system architecture applicable to the embodiment of the present application.
  • Fig. 2 shows a schematic diagram of an application architecture of a communication system applicable to the embodiment of the present application.
  • FIG. 3 shows a protocol stack architecture in which a remote UE performs user plane data transmission through a non-direct path.
  • FIG. 4 shows a schematic flowchart of user plane data transmission performed by a remote UE in a non-direct path transmission manner.
  • FIG. 5 shows a schematic diagram of a data transmission method 500 provided by an embodiment of the present application.
  • FIG. 6 shows a schematic diagram of changes in a data transmission path of a remote UE provided by an embodiment of the present application.
  • FIG. 7 shows a schematic diagram of a data transmission method 700 provided by an embodiment of the present application.
  • FIG. 8 shows a schematic diagram of a method for performing multiple transmission by a UPF provided by an embodiment of the present application.
  • FIG. 9 shows a schematic diagram of a data transmission method 900 provided by an embodiment of the present application.
  • FIG. 10 shows a schematic diagram of a data transmission method 1000 provided by an embodiment of the present application.
  • FIG. 11 shows a schematic diagram of a data transmission method 1100 provided by an embodiment of the present application.
  • FIG. 12 shows a schematic flowchart of a data transmission method 1200 provided by an embodiment of the present application.
  • FIG. 13 shows a schematic flowchart of a data transmission method 1300 provided by an embodiment of the present application.
  • FIG. 14 shows a schematic diagram of a data transmission method 1400 provided by an embodiment of the present application.
  • FIG. 15 shows a flow chart of a method for associating a direct path and a non-direct path and creating a transmission channel provided by an embodiment of the present application.
  • FIG. 16 shows a schematic diagram of an apparatus 1600 for data transmission provided by an embodiment of the present application.
  • FIG. 17 shows a schematic diagram of a data transmission device 1700 provided by an embodiment of the present application.
  • the technical solution provided by this application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) or new radio (new radio, NR) system, long term evolution (long term evolution, LTE) system, LTE frequency division Duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, etc.
  • 5G fifth generation
  • NR new radio
  • long term evolution long term evolution
  • LTE long term evolution
  • LTE frequency division Duplex frequency division duplex
  • FDD frequency division duplex
  • TDD time division duplex
  • the technical solution provided by this application can also be applied to device to device (device to device, D2D) communication, vehicle to everything (vehicle-to-everything, V2X) communication, machine to machine (machine to machine, M2M) communication, machine type Communication (machine type communication, MTC), and Internet of things (internet of things, IoT) communication system or other communication systems.
  • D2D device to device
  • V2X vehicle-to-everything
  • M2M machine to machine
  • M2M machine type Communication
  • MTC machine type communication
  • IoT Internet of things
  • Fig. 1 shows a schematic diagram of a network architecture.
  • the network architecture takes the 5G system (the 5th generation system, 5GS) as an example.
  • the network architecture may include but not limited to: network slice selection function (network slice selection function, NSSF), authentication server function (authentication server function, AUSF), unified data management (unified data management, UDM), network exposure function (network exposure function, NEF), network storage function (NF repository function, NRF), policy control function (policy control function, PCF), application function (application function, AF), access and mobility management function (access and mobility management function, AMF), session management function (session management function, SMF), user equipment (user equipment, UE), radio access network equipment, user plane function (user plane function, UPF), data network (data network, DN).
  • network slice selection function network slice selection function
  • authentication server function authentication server function
  • unified data management unified data management
  • UDM network exposure function
  • NEF network exposure function
  • NRF network storage function
  • policy control function policy control function
  • PCF policy control function
  • application function application function, AF
  • DN can be the Internet
  • NSSF, AUSF, UDM, NEF, NRF, PCF, AF, AMF, SMF, and UPF belong to the network elements in the core network.
  • the core network can be called 5G core network (5G core network, 5GC or 5GCN).
  • Each network element shown in FIG. 1 is briefly introduced below.
  • UE can be called terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless Communication Device, User Agent, or User Device.
  • a terminal device may be a device that provides voice/data to a user, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • some terminals are: mobile phone (mobile phone), tablet computer, notebook computer, palmtop computer, mobile internet device (mobile internet device, MID), wearable device, virtual reality (virtual reality, VR) device, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, smart grid Wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocol , SIP) phones, wireless local loop (wireless local loop, WLL) stations, personal digital assistants (personal digital assistant, PDA), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, Wearable devices, terminal devices in a 5G network, or terminal devices in a future evolving public land mobile network (PLMN), etc., are not limited in this
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.
  • the terminal device can also be the terminal device in the IoT system.
  • IoT is an important part of the development of information technology in the future. Its main technical feature is to connect items to the network through communication technology, so as to realize Interconnection, an intelligent network that interconnects things.
  • a certain air interface technology such as NR or LTE technology
  • a certain air interface technology may also be used to communicate with each other between terminal devices.
  • the device for realizing the function of the terminal device may be the terminal device, or may be a device capable of supporting the terminal device to realize the function, such as a chip system or a chip, and the device may be installed in the terminal device.
  • the system-on-a-chip may be composed of chips, or may include chips and other discrete devices.
  • (wireless) access network ((radio) access network, (R) AN) equipment it can provide authorized users in a specific area with the function of accessing the communication network, specifically including the third generation partnership project (3rd generation partnership)
  • the wireless network device in the project, 3GPP) network may also include an access point in a non-3GPP (non-3GPP) network.
  • non-3GPP non-3GPP
  • AN devices may use different wireless access technologies.
  • 3GPP access technologies for example, wireless access technologies used in third generation (3rd generation, 3G), fourth generation (4th generation, 4G) or 5G systems
  • non- 3GPP (non-3GPP) access technology refers to the access technology that complies with the 3GPP standard specifications.
  • the access network equipment in the 5G system is called the next generation Node Base station (gNB) or RAN equipment.
  • Non-3GPP access technologies may include air interface technology represented by access point (AP) in wireless fidelity (WiFi), worldwide interoperability for microwave access (WiMAX), code Multiple access (code division multiple access, CDMA), etc.
  • the AN device may allow non-3GPP technology interconnection and intercommunication between the terminal device and the 3GPP core network.
  • the AN device can be responsible for functions such as wireless resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • QoS quality of service
  • the AN equipment provides access services for the terminal equipment, and then completes the forwarding of control signals and user data between the terminal equipment and the core network.
  • AN equipment may include, but not limited to, for example: a macro base station, a micro base station (also called a small station), a radio network controller (radio network controller, RNC), a node B (Node B, NB), a base station controller (base station controller) , BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), AP in WiFi system, wireless relay Node, wireless backhaul node, transmission point (transmission point, TP) or transmission and reception point (transmission and reception point, TRP), etc., can also be gNB or transmission point (TRP or TP) in the 5G (eg, NR) system , one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or it can also be a network node that constitutes a gNB or a transmission point, such as a
  • AMF mainly used for functions such as access control, mobility management, attachment and detachment.
  • SMF It is mainly used for user plane network element selection, user plane network element redirection, Internet protocol (internet protocol, IP) address allocation for terminal equipment, session establishment, modification and release, and QoS control.
  • IP Internet protocol
  • UPF mainly used for receiving and forwarding user plane data.
  • the UPF can receive user plane data from the DN, and send the user plane data to the terminal device through the AN device.
  • UPF can also receive user plane data from terminal equipment through AN equipment and forward it to DN.
  • NEF It is mainly used to safely open services and capabilities provided by 3GPP network functions to the outside.
  • PCF A unified policy framework mainly used to guide network behavior, and provide policy rule information for control plane network elements (such as AMF, SMF, etc.).
  • AF It is mainly used to provide services to the 3GPP network, such as interacting with the PCF for policy control.
  • Network slice selection function (network slice selection function, NSSF): mainly used for network slice selection.
  • UDM mainly used for UE subscription data management, including storage and management of UE ID, UE access authorization, etc.
  • DN mainly used for the operator network that provides data services for the UE.
  • the Internet Internet
  • a third-party service network IP multimedia service (IP multi-media service, IMS) network, and the like.
  • IP multimedia service IP multi-media service, IMS
  • AUSF mainly used for user authentication, etc.
  • NRF It is mainly used to save the description information of network functional entities and the services they provide.
  • various network elements can communicate through interfaces.
  • UE2 is connected to the AN device through a radio resource control (radio resource control, RRC) protocol, and a Uu interface is used for communication between the UE and the AN device.
  • RRC radio resource control
  • the PC5 interface is used for communication between UE1 and UE2, and the PC5 interface can be used for mutual discovery between UEs and data and signaling transmission between UEs.
  • 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
  • N4 is the interface between SMF and UPF, which is used to transmit such information as the channel identification information of N3 connection, data cache indication information, and downlink data notification messages
  • N6 interface is the interface between UPF and DN, Used to transmit user plane data, etc.
  • the N11 interface is the interface between the AMF and the SMF.
  • network architecture shown above is only an example, and the network architecture applicable to the embodiment of the present application is not limited thereto, and any network architecture capable of realizing the functions of the foregoing network elements is applicable to the embodiment of the present application.
  • the functions or network elements such as AMF, SMF, UPF, PCF, UDM, NSSF, and AUSF shown in Figure 1 can be understood as network elements for implementing different functions, for example, they can be combined into network slices as required.
  • These network elements can be independent devices, or can be integrated in the same device to achieve different functions, or can be network elements in hardware devices, or software functions running on dedicated hardware, or platforms (for example, cloud The virtualization function instantiated on the platform), this application does not limit the specific form of the above network elements.
  • Direct path The terminal device is directly connected to the access network device, that is, in the direct connection path, the terminal device and the access network device directly establish a connection and communicate without passing through other devices (such as , relay device).
  • the direct path may also be called a direct link (link).
  • the terminal device accesses the access network device through the relay device, that is, in the indirect path, the terminal device and the access network device pass through one or more relay devices Establish a connection and communicate.
  • the relay device is a relay (relay) UE
  • the terminal device is a remote (remote) UE.
  • the remote UE establishes a connection with the relay UE
  • the relay UE establishes a connection with the RAN, so that the remote The UE can establish a connection with the RAN through the relay UE.
  • the connection mode between the terminal device and the relay device may be the connection mode in 3GPP, for example, proximity-based services communication 5 (proximity-based services communication 5, PC5) connection, also It may be a connection mode in a short-distance communication technology, for example, a Bluetooth connection, a WiFi connection, and the like.
  • the connection method between the terminal device and the relay device may be the same as or different from the connection method between any two relay devices.
  • An indirect path may also be called an indirect link (link).
  • Protocol data unit (protocol data unit, PDU) session (PDU session): 5G core network (5G core network, 5GC) supports PDU connection business.
  • the PDU connection service may refer to a service of exchanging PDU data packets between the terminal device and the DN.
  • the PDU connection service is realized by the establishment of the PDU session initiated by the terminal device. After a PDU session is established, a data transmission channel between the terminal device and the DN is established. In other words, PDU sessions are at UE level. Each end device can establish one or more PDU sessions.
  • SMF is mainly responsible for session management in mobile networks.
  • the PDU session can be established, modified or released between the terminal device and the SMF through NAS session management (session management, SM) signaling.
  • NAS session management session management, SM
  • a PDU session can be identified by a PDU session identifier (PDU session identifier, PDU session ID).
  • PDU session identifier PDU session ID
  • QoS flow The QoS distinction granularity in the PDU session.
  • QoS flow identifier QoS flow identifier
  • QFI QoS flow identifier
  • 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 within one PDU session.
  • the QoS flow corresponding to the service may refer to the QoS flow used to transmit the data of the service.
  • the QoS flow may be called the QoS flow corresponding to the service.
  • the service carried by the QoS flow may refer to the service transmitted through the QoS flow.
  • the QoS requirements of the QoS flow may refer to the conditions that the QoS parameters corresponding to the QoS flow need to meet.
  • QoS parameters may include but not limited to: rate, delay, packet loss rate, priority, reliability, and so on.
  • the QoS requirement corresponding to the QoS flow is: the rate in the QoS parameter corresponding to the QoS flow needs to meet 7 megabits per second (Mbps), that is, greater than or equal to 7 Mbps.
  • Reliable transmission When the terminal device and the network device transmit data through the direct path and the non-direct path at the same time, the network device will copy the downlink data and transmit them through the direct path and the non-direct path respectively, so that To ensure that the terminal device receives the data is reliable transmission.
  • Load balancing transmission When data transmission is performed between the terminal device and the network device through the direct path and the non-direct path at the same time, the network device divides the downlink data into two data packets, which are respectively passed through the direct path and the non-direct path. Transmission is performed to balance the load of the two paths, that is, load-balanced transmission.
  • Fig. 2 shows a schematic diagram of an application architecture of a communication system according to an embodiment of the present application.
  • the network architecture is based on the infrastructure shown in Figure 1, a UE (for example, a remote (remote) UE) provided by the 3GPP standard passes another UE (for example, a relay (relay) UE) Access to the network scheme.
  • the remote UE can directly access the network. Specifically, it includes first directly accessing the AN, and then accessing the core network through the AN (5GC includes the AMF of the remote UE, the SMF of the remote UE, and the core network of the remote UE. UPF), and perform signaling and data transmission with the core network and DN.
  • a UE for example, a remote (remote) UE
  • the remote UE can directly access the network. Specifically, it includes first directly accessing the AN, and then accessing the core network through the AN (5GC includes the AMF of the remote UE, the SMF of the remote UE, and
  • This transmission mode can be called a direct path (direct path) transmission mode.
  • the remote UE can also access the network through the relay UE. Specifically, it includes: first accessing the AN through the relay UE, and then accessing the core network through the AN, and then performing signaling and communication with the core network and DN of the remote UE. Data transmission, this transmission method can be called an indirect path (indirect path) transmission method.
  • the relay UE in FIG. 2 is a layer-3 UE-to-network relay (layer-3 UE-to-network relay).
  • FIG. 3 shows a protocol stack architecture when a remote UE uses a non-direct path transmission mode to transmit user plane data.
  • a protocol data unit protocol data unit, PDU
  • layer is used to transfer data generated by an application software (applicable soft, APP) between the remote UE and the UPF.
  • the service data adaptation protocol service data adaptation protocol, SDAP
  • QoS quality of service
  • DRB data radio bearer
  • the QoS flow consists of two parts: DRB between UE and NG-RAN, N3 connection between NG-RAN and UPF.
  • DRB is composed of two layers: packet data convergence protocol (PDCP) layer and radio link control (radio link control, RLC) layer.
  • PDCP packet data convergence protocol
  • RLC radio link control
  • the PDCP layer is used to perform functions such as header compression, decompression, encryption/decryption, integrity protection, and integrity verification of user plane data
  • the PDCP layer is configured by an RRC message.
  • Media access control (mediu access control, MAC) is used to perform mapping between logical channels and transport channels, and to combine MAC data from different logical channels into one transport block.
  • PHY is the physical layer (physical layer, PHY).
  • the adaptation (adaptation) layer is used for the relay UE or the NG-RAN to indicate which remote UE the data packet contained in the RLC of the relay UE belongs to, and which radio bearer of the remote UE belongs to.
  • GTP-U General packet radio service
  • TCP/IP transmission control protocol/internet protocol
  • UDP/IP User Datagram Protocol/Internet Protocol
  • GTP-U messages are used to carry user data between GTP-U entities.
  • L2 means layer 2 (layer 2)
  • L2 means layer 1 (layer 1).
  • the DRB of the remote UE consists 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 .
  • the DRB of the remote UE consists 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.
  • the transmission process of uplink data is: the APP layer of the remote UE generates data, the remote UE maps the data to the QoS flow at the PDU layer, and sends the data to the Uu-SDAP layer, the data includes the QoS flow identifier, and the remote UE At the Uu SDAP layer, the UE maps the QoS flow to the DRB according to the QoS flow identifier, 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 it to the relay UE through the PC5 interface.
  • the relay UE analyzes and obtains the Uu PDCP data of the remote UE.
  • the relay UE sends data to the NG-RAN through the Uu interface with the NG-RAN.
  • NG-RAN uses the context of the remote UE to parse out the data of the remote UE, and NG-RAN sends the data of the remote UE to the UPF through the N3 interface with the UPF.
  • the process of downlink data transmission is: NG-RAN receives the data sent by UPF to the remote UE, and determines that the remote UE uses the relay UE for data transmission according to the context of the remote UE. After analyzing 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 analysis.
  • Fig. 4 shows a schematic flowchart of user plane data transmission performed by a remote UE in an indirect path transmission manner. As shown in Fig. 4, the method 400 includes the following steps.
  • the operator's network distributes the authorization authentication and information provision of relay-related services to the relay UE and the remote UE.
  • the relay UE establishes a PDU session.
  • the APP on the remote UE starts, and it is determined through the URSP that the APP can use the layer 2 relay service, then the remote UE executes a relay UE discovery procedure, and selects a relay UE.
  • 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.
  • the relay UE performs an IP router function, and assigns an IP address to the remote UE.
  • the remote UE can request to create/modify the QoS flow; the remote UE sends a modification request message to the relay UE, carrying the PC5 QoS parameter, and the relay UE locally maps the PC5 QoS parameter to Uu QoS parameters, and judge whether to create a new QoS flow, and initiate the process of creating a new QoS flow if necessary.
  • the relay UE reports the information of the remote UE to the SMF, including Remote User ID and Remote UE info.
  • the data of the remote UE is forwarded through the UPF, NG-RAN and the relay UE.
  • the remote UE uses a certain fixed path (direct path or non-direct path) to transmit service data. For example, if the terminal device determines that the transmission path is a direct path, the terminal device sends The network access device initiates a PDU session request, establishes the PDU session and QoS flow of the direct path, and then, the terminal device transmits data with the data network through the QoS flow of the direct path. Or, if the terminal device determines that the transmission path is a non-direct path, the terminal device initiates a PDU session request to the access network device through the relay device, and establishes a PDU session and QoS flow for the non-direct path. The QoS flow of the connection path and the data network transmit data. This transmission mode cannot dynamically meet service transmission requirements, for example, time delay, communication quality, or communication capacity.
  • the present application provides a method and device for data transmission, so that the data transmission paths between the terminal equipment and the data network are diversified, for example, data can be transmitted through direct paths and non-direct paths at the same time, and business needs can be dynamically met. For example, to increase the transmission rate or to ensure the reliability of data transmission.
  • FIG. 5 is a schematic diagram of a data transmission method 500 provided by an embodiment of the present application.
  • Method 500 may include the following steps.
  • the first terminal device acquires first information.
  • the first terminal device may be an example of a remote UE.
  • the first information includes first QoS flow information of the first communication path, and the first information is used for the first network device to transmit the first data to the first terminal device through the first communication path.
  • the first network device may be a UPF
  • the first data may be downlink transmission data received by the UPF.
  • the first communication path is a non-direct connection path
  • the second communication path is a direct connection path.
  • the first terminal device acquires first QoS flow information of the non-direct path, where the first QoS flow information is used by the first network device to transmit the first data to the first terminal device through the non-direct path.
  • the first terminal device acquires the first QoS flow information of the indirect path through the indirect path.
  • the indirect path can be understood as the first terminal device accessing the network device through the second terminal device.
  • the second terminal device may be an example of a relay UE.
  • the first terminal device sends a first request message to the second terminal device through the PC5 interface, the first request message is used to request the establishment of the first QoS flow on the indirect path; the first request message includes the second indication information , the second indication information is used to obtain the first information; correspondingly, the second terminal device establishes the first QoS flow on the indirect path, and sends the first QoS flow to the first terminal device through the PC5 interface according to the second indication information first information. That is, the first terminal device receives the first information from the second terminal device.
  • the first request message may be a "link modification request (connection modification request) message".
  • the first request message may also be an independent request message.
  • the second communication path is a direct connection path, which can be understood as a path through 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 to obtain the second information, the second information includes information about the second QoS flow.
  • the first terminal device directly accesses the network device, which means that data transmission with the network device does not need to be forwarded by the relay UE. limited.
  • the first request message can also include "request PC5 QoS rule (PC5 QoS rule request)” and "request PC5 QoS parameter (PC5 QoS parameter request)", the "packet filter ( Packet filtering) " destination address is the destination address of the packet filtering of the QoS rule of the second QoS flow, and this " request PC5 QoS parameter (PC5 QoS parameter request) is identical with the QoS parameter of the second QoS flow.
  • the first information may include the packet detection rule PDR corresponding to the first QoS flow, and may also include the newly created PC5 QoS parameters and PC5 QoS rule of the first QoS flow.
  • the packet detection rule PDR corresponding to the first QoS flow can also be understood as the data packet filtering corresponding to the PDR, or the destination address (IP address and port number) of the data packet filtering corresponding to the PDR.
  • the first information may 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.
  • the identifier (Relay UE ID) of the second terminal device may be GUTI (Globally Unique Temporary UE Identity, Globally Unique Temporary UE Identity) or S-TMSI (Serving-Temporary Mobile Subscriber Identity, Temporary Mobile Subscriber Identity).
  • GUTI Globally Unique Temporary UE Identity, Globally Unique Temporary UE Identity
  • S-TMSI Server-Temporary Mobile Subscriber Identity, Temporary Mobile Subscriber Identity
  • the second terminal device may send the first information through a "link modification accept (connection modification accept) message".
  • the second indication information may be "paired QoS flow (associated QoS flow) indication"
  • the second terminal device may send related information of the newly created first QoS flow according to the paired QoS flow (associated QoS flow) indication" to the first terminal device.
  • the first communication path is a direct connection path
  • the second communication path is a non-direct connection path.
  • the first terminal device acquires first QoS flow information of the direct path, where the first QoS flow information is used by the first network device to transmit the first data to the first terminal device through the direct path.
  • the first terminal device establishes the direct path and acquires the first QoS flow information of the direct path during the establishment process.
  • the direct connection path can be understood as a path through which the first terminal device directly accesses the network device, but it should be understood that the first terminal device directly accesses the network device, which means that data transmission between the network device and the forwarding of the UE is not required. , in fact, there may be a transfer of other network elements, which is not limited in this embodiment of the present application.
  • the first terminal device triggers the establishment of the direct path, establishes the first QoS flow on the direct path, and acquires the first information.
  • the first information includes the packet detection rule PDR corresponding to the first QoS flow on the direct path, and may also include the PC5 QoS parameter and PC5 QoS rule of the newly created first QoS flow.
  • the first information may include the identifier of the second terminal device, the identifier QFI-1 of the first QoS flow, the identifier of the PDU session corresponding to the first QoS flow, and may also include the newly created first QoS PC5 QoS parameters and PC5 QoS rule for the flow.
  • the first terminal device sends the first message to the second network device.
  • the first terminal device sends the first message to the second network device through the second communication path.
  • the first message includes first information and first indication information, where the first indication information is used to indicate to transmit the first data through the first communication path and/or the second communication path.
  • the second network device is an example of a core network element.
  • it could be AMF, SMF.
  • the second network device receives the first message from the first terminal device.
  • the first communication path is a non-direct connection path
  • the second communication path is a direct connection path.
  • the first terminal device After the first terminal device acquires the information of the first QoS flow of the non-direct path, it sends a first message to the first AMF (the AMF of the first terminal device) through the direct path, and carries the first information in the first message and first indication information, where the first indication information is used to indicate to transmit the first data through the first communication path and/or the second communication path.
  • the first message may also be an independent notification message.
  • the first message may be a non-access stratum (non-access stratum, NAS) message such as a PDU session modification request message or a PDU session establishment request message.
  • NAS non-access stratum
  • the first terminal device sends a PDU session modification request message to the first AMF through the uu interface of the direct path, the request message carries the first information and the first indication information, and the PDU session modification request message is used to request the direct Modify the second QoS flow of the link path.
  • the first information includes the packet detection rule PDR corresponding to the first QoS flow, and may also include the newly created PC5 QoS parameters and PC5 QoS rule of the first QoS flow.
  • 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.
  • the identifier (Relay UE ID) of the second terminal equipment may be GUTI or S-TMSI.
  • the first indication information may be "paired QoS flow (associated QoS flow) indication".
  • both the first indication information and the second indication information can be "paired QoS flow (associated QoS flow) indication", but the second indication information is the information of the PC5 interface, and the first indication information is the information sent by the Uu interface , so the expression form of the communication interface may be different, which is not limited in this embodiment of the present application.
  • the first message may also carry third indication information, where the third indication information is used to indicate reliable transmission or load balancing transmission.
  • the third indication information may be "multi path rule (multipath rule)”.
  • a reliable transmission indication or a load balancing transmission indication is included in a "multi path rule".
  • the first indication information is used to indicate the transmission of the first data through the first communication path and the second communication path. It can be understood that the data for downlink transmission can be simultaneously transmitted to the remote UE through the direct path and the non-direct path, so that It can improve the efficiency of data transmission and ensure the reliability of data transmission.
  • a direct path or an indirect path which can be used to transmit downlink data, which can be arbitrarily Selecting or selecting a direct connection path or a non-direct connection path for downlink data transmission according to transmission requirements improves the flexibility of data transmission.
  • the first communication path is a direct connection path
  • the second communication path is a non-direct connection path.
  • the first terminal device obtains the information of the first QoS flow of the direct path, it sends the first message to the second AMF (the AMF of the second terminal device) through the non-direct path, and carries the first information and First indication information, where the first indication information is used to indicate to transmit the first data through the first communication path and/or the second communication path.
  • the first message may also be an independent notification message.
  • the first message may be a non-access stratum (non-access stratum, NAS) message such as a PDU session modification request message or a PDU session establishment request message.
  • NAS non-access stratum
  • the first terminal device sends a connection modification request message to the second terminal device through the PC5 interface of the non-direct path, the request message carries the first information and the first indication information, and the connection modification request message is used to request the The second QoS flow of the direct path is modified.
  • the second terminal device sends a PDU session modification request message to the second AMF, the request message carries the first information and the first indication information, and the PDU session modification request message is used to request the second QoS flow for the non-direct path to modify.
  • the first information includes the packet detection rule PDR corresponding to the first QoS flow, and may also include the newly created PC5 QoS parameters and PC5 QoS rule of the first QoS flow.
  • 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.
  • the identifier (Relay UE ID) of the second terminal equipment may be GUTI or S-TMSI.
  • the first indication information may be "paired QoS flow (associated QoS flow) indication".
  • both the first indication information and the second indication information can be "paired QoS flow (associated QoS flow) indication", but the second indication information is the information of the PC5 interface, and the first indication information is the information sent by the Uu interface , so the expression form of the communication interface may be different, which is not limited in this embodiment of the present application.
  • the first message may also carry third indication information, where the third indication information is used to indicate reliable transmission or load balancing transmission.
  • the third indication information may be "multi path rule (multipath rule)”.
  • a reliable transmission indication or a load balancing transmission indication is included in a "multi path rule".
  • the second network device sends the first information and the second information to the first network device.
  • 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 includes first QoS flow information of the first communication path
  • the second information includes second QoS flow information of the second communication path
  • the first QoS flow information is used by the first network device to communicate with the second communication path through the first communication path.
  • a terminal device transmits downlink data
  • the second QoS flow information is used by the first network device to transmit downlink data to the first terminal device through the second communication path.
  • the first network device may be a first UPF of the first communication path, or may be a second UPF of the second communication path, and the first UPF and the second UPF may be the same UPF or different UPFs.
  • the first communication path is a non-direct connection path
  • the second communication path is a direct connection path.
  • the first AMF receives the first message (PDU session modification request message) from the first terminal device, it sends it to the first SMF (the SMF of the first terminal device), and the first SMF according to the first information carried in the PDU session modification request message modify the second QoS flow of the direct path together with the first indication information, and send the first information and the second information to the first UPF.
  • the first information includes the packet detection rule PDR corresponding to the first QoS flow on the non-direct path
  • the second information includes the PDR corresponding to the second QoS flow on the direct path.
  • the first message may also carry third indication information
  • the first terminal device may send the third indication information to the first network device through the second network device, where the third indication information is used to instruct the first network device to perform reliable sexual transmission or load balancing transmission.
  • the third indication information may also be carried in the PDR corresponding to the second QoS flow, which is not limited in this embodiment of the present application.
  • a Multi-Path Rule ID field can be added to the packet detection rule PDR corresponding to the second QoS flow.
  • the Multi-Path Rule corresponding to this field includes a multi-path coordinated transmission indication and a creation Outer IP header creation indication.
  • the first communication path is a direct connection path
  • the second communication path is a non-direct connection path.
  • the second AMF receives the first message (PDU session modification request message) from the first terminal device through the second terminal device, it sends it to the second SMF (the SMF of the second terminal device), and the second SMF sends the message according to the PDU session modification request message.
  • the carried first information and first indication information modify the second QoS flow, and send the first information and the second information to the first UPF.
  • the first information includes the packet detection rule PDR corresponding to the first QoS flow on the direct path
  • the second information includes the PDR corresponding to the second QoS flow on the non-direct path.
  • the first message may also carry third indication information
  • the first terminal device may send the third indication information to the first network device through the second network device, where the third indication information is used to instruct the first network device to perform reliable sexual transmission or load balancing transmission.
  • the third indication information may also be carried in the PDR corresponding to the second QoS flow, which is not limited in this embodiment of the present application.
  • a Multi-Path Rule ID field can be added to the packet detection rule PDR corresponding to the second QoS flow.
  • the Multi-Path Rule corresponding to this field includes a multi-path coordinated transmission indication and a creation Outer IP header creation indication.
  • the first communication path is a non-direct connection path
  • the second communication path is a direct connection path.
  • the first AMF sends the 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 it to the first SMF (the SMF of the first terminal device), and the first SMF according to
  • the first information and the first indication information carried in the first message modify the second QoS flow, and send the first information and the second information to the first UPF.
  • the first information includes the packet detection rule PDR corresponding to the first QoS flow on the non-direct path
  • the second information includes the PDR corresponding to the second QoS flow on the direct path.
  • the first SMF may also send third indication information to the first UPF, where the third indication information is used to instruct the first network device to perform reliable transmission or load balancing transmission.
  • a Multi-Path Rule ID field can be added to the packet detection rule PDR corresponding to the second QoS flow.
  • the Multi-Path Rule corresponding to this field includes a multi-path coordinated transmission indication, creation Outer IP header creation indication and CN tunnel info.
  • the first communication path is a direct connection path
  • the second communication path is a non-direct connection path.
  • the second AMF receives the first message through the second terminal device, and sends the first message to the first AMF, obtains the address of the first UPF and the PDR corresponding to the first QoS flow of the direct path through the first AMF, and sends it to the second SMF (SMF of the second terminal device), the second SMF modifies the second QoS flow of the non-direct path according to the first information carried in the first message and the first indication information, and sends the first information and second information.
  • SMF SMF of the second terminal device
  • the first information includes the packet detection rule PDR corresponding to the first QoS flow on the direct path
  • the second information includes the PDR corresponding to the second QoS flow on the non-direct path.
  • the second SMF may also send third indication information to the second UPF, where the third indication information is used to instruct the first network device to perform reliable transmission or load balancing transmission.
  • a Multi-Path Rule ID field can be added to the packet detection rule PDR corresponding to the second QoS flow.
  • the Multi-Path Rule corresponding to this field includes a multi-path coordinated transmission indication, creation Outer IP header creation indication and CN tunnel info.
  • the first network device determines to perform multiplex transmission.
  • the first network device receives the first information and the second information, the first network device receives the first data, and determines to perform multiplex transmission on the first data according to the first information and the second information.
  • the first network device receives the third indication information, determines to perform multiplex transmission on the first data according to the third indication information, and determines to specifically perform reliable transmission or load balancing transmission.
  • the first network device needs to transmit data to the third network device when performing reliable transmission or load balancing transmission, and the third network device passes the indirect path Data transmission to end devices.
  • the third network device may be the first UPF or the second UPF.
  • FIG. 6 shows a schematic diagram of changes in a data transmission path of a remote UE provided by an embodiment of the present application.
  • Figure 6(a) is a schematic diagram of the non-direct path and direct path of the remote UE connected to the same UPF
  • Figure 6(b) is the non-direct path and direct path of the remote UE connected to different UPFs
  • the following takes the first UPF as an example of the first network device, and the second UPF as an example of the third network device.
  • FIG. 6(a) is a schematic diagram of the data transmission path of the remote UE after S510 to S540. As shown in FIG. 6(a), the direct path and the indirect path of the remote UE are connected to UPF #1 ( An example of the first UPF), that is, the first network device and the third network device are the same network device.
  • UPF #1 An example of the first UPF
  • FIG. 6(b) is a schematic diagram of the data transmission path of the remote UE after S510 to S540.
  • the direct connection path of the remote UE is connected to UPF #1 (an example of the first UPF )
  • the indirect path of the remote UE connects UPF#2 (an example of the second UPF), that is, the first network device and the third network device are two different network devices.
  • FIG. 7 is a schematic diagram of a data transmission method 700 provided by an embodiment of the present application.
  • the method 700 may be regarded as a specific implementation manner of the method 500, and the method 700 may include the following steps.
  • the remote UE establishes a PDU session #1 and a QoS flow #1 on the direct path.
  • PDU session #1 includes QoS flow #1 (an example of the second QoS flow).
  • the identifier of the QoS flow #1 may be QFI-1.
  • the remote UE can acquire QoS flow information #2 during the process of establishing the QoS flow #1, and the QoS flow information #2 includes the identification information QFI-1 of the QoS flow #1 and the PDR corresponding to the QFI-1.
  • the remote UE sends a request message #1 (an example of a first request message) to the relay UE through an indirect path.
  • the remote UE determines that an indirect path needs to be established according to the data transmission requirement, so as to simultaneously use the indirect path and the direct path for multiple transmissions, for example, reliable transmission or load balancing transmission is required.
  • the remote UE sends a request message #1 (an example of the 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 (first QoS flow #2) on the non-direct path.
  • a request message #1 an example of the first request message
  • the request message #1 is used to request to establish a QoS flow #2 (first QoS flow #2) on the non-direct path.
  • QoS flow #2 first QoS flow #2
  • the identifier of the QoS flow #2 may be QFI-2.
  • the request message #1 includes indication information #1 (an example of the second indication information), the indication information #1 is used to obtain the QoS flow information #1 (an example of the first information), and the QoS flow information #1 includes the QoS flow # 2 identification information QFI-2 and the PDR corresponding to QFI-2.
  • the request message #1 also includes "request PC5 QoS rule” and "request PC5 QoS parameter".
  • the destination address of packet filtering in "request PC5 QoS rule” is the same as the destination address of packet filtering in QoS rule of QFI-1;
  • “request PC5 QoS parameter” is the same as the QoS parameter of QoS flow #1.
  • the remote UE may acquire QoS flow information #2 (an example of the third information) of the QoS flow #1 on the direct path.
  • the QoS flow information #2 includes QoS rule and QoS parameters of QFI-1.
  • the request message #1 may be a link modification request (link modification request) message.
  • the indication information #1 may be associated QoS flow (paired QoS flow) indication information.
  • the relay UE sends a request message #2 to the SMF #2.
  • the relay UE sends a request message #2 to AMF#2, and AMF#2 sends a request message #2 to SMF#2 (an example of a second network device), the request message #2 includes the above indication information #1, the Request message #2 also includes "request QoS rule" and "request QoS parameter".
  • SMF#2 establishes QoS flow #2 on the indirect path according to the request message #2.
  • the "request QoS rule” and “request QoS parameter" in the request message #2 are determined by the relay UE according to the "request PC5 QoS rule” and "request PC5 QoS parameter" of the remote UE.
  • the request message #2 may be a PDU session establish request (PDU session establish request) message.
  • the relay UE may send the request message #2 to the AMF #2 through the UL NAS message.
  • AMF#2 may send a request message #2 to SMF#2 through an N11 message, and the N11 message may be a PDU session creation context request (Nsmf_PDUsession_createSMcontext request) message or the like.
  • Nsmf_PDUsession_createSMcontext request PDU session creation context request
  • AMF#2 and SMF#2 are network devices serving the relay UE.
  • SMF#2 sends a response message #1 to the relay UE.
  • SMF#2 sends a response message #1 to the relay UE through AMF#2.
  • the response message #1 is used to respond to the above request message #2.
  • the response message #1 may be a PDU session establish accept (PDU session establish accept) message.
  • SMF#2 may first send an N11 message to AMF#2, the N11 message includes N1 SM container and N2 SM container, the N1 SM container includes response message #1, and the N2 SM container includes QoS flow information #1, QoS rule and QoS parameters, wherein, the N11 message may be a N1N2 message delivery (Namf_communication_N1N2MessageTransfer) message.
  • N11 message may be a N1N2 message delivery (Namf_communication_N1N2MessageTransfer) message.
  • the QoS flow information #1 includes the identification information QFI-2 of the QoS flow #2 and the PDR corresponding to the QFI-2.
  • the SMF#2 sends the PDR corresponding to the QFI-2 to the relay UE according to the indication information#1.
  • the relay UE sends a response message #2 to the remote UE through the indirect path.
  • the relay UE sends a response message #2 to the remote UE through the PC5 interface, and the response message #2 includes QoS flow information #1 (an example of the first information), PC5 QoS rule and PC5 QoS parameter.
  • the QoS flow information #1 includes the identification information QFI-2 of the QoS flow #2 and the PDR corresponding to the QFI-2.
  • the response message #2 may be a link modification accept (link modification accept) message.
  • 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.
  • the remote UE sends a request message #3 (an example of the first message) to the SMF #1 through the direct path.
  • the remote UE carries QoS flow information #1 and indication information #2 in the request message #3.
  • the request message #3 is used to request SMF#1 to modify the QoS flow #1.
  • the modification here can be understood as modifying the QoS parameters corresponding to the QoS flow #1, that is, increasing the QoS parameter included in the QoS flow information #1.
  • the QoS parameter of flow #2 specifically, can be understood as adding the PDR corresponding to QFI-2.
  • the request message #3 may be a PDU session modification request (PDU session modification request) message.
  • the request message #3 may also carry indication information #3 (an example of third indication information).
  • the instruction information #3 is used to instruct the network device (UPF#1) to perform reliable transmission or load balancing transmission.
  • S770, SMF#1 sends request message #4 to UPF#1.
  • SMF#1 carries QoS flow information #1 and QoS flow information #2 in the request message #4.
  • the request message #4 may also carry indication information #3 (an example of third indication information).
  • the instruction information #3 is used to instruct the network device (UPF#1) to perform reliable transmission or load balancing transmission.
  • the request message #4 may be an N4 modification request message.
  • UPF#1 determines to perform multiplex transmission according to the request message #4.
  • UPF#1 determines the PDR corresponding to QFI-2 and the PDR corresponding to QFI-1 according to the request message #4, and further determines to perform multiplex transmission.
  • UPF #1 may determine to specifically perform reliable transmission or load balancing transmission according to the indication information #3.
  • FIG. 8 is a schematic diagram of a method for performing multiple transmission by a UPF provided by an embodiment of the present application.
  • the method 800 is a specific description of the method for UPF#1 performing multiplex transmission to the remote UE after step S780 is executed in the method 700.
  • Figure 8(a) shows a schematic diagram of the remote UE's non-direct path and direct path connected to different UPFs, such as 8(b) for the remote UE's non-direct path and direct path Schematic diagram of paths connected to the same UPF.
  • QoS flow #1 is established on the direct path
  • QoS flow #2 is established on the non-direct path.
  • 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.
  • UPF#1 an example of the first UPF
  • UPF#2 an example of the first UPF
  • UPF#1 When UPF#1 receives the downlink data sent by the APP server, UPF#1 needs to copy the downlink IP packet when it determines to perform reliable transmission according to the instruction information #3; when it determines to perform load balancing transmission, it needs to copy the IP packet for diversion.
  • the downlink data packet includes the external network address IP-5 of the destination address QoS flow #1 and the address IP-6 of the source address APP server.
  • UPF#1 On the direct connection path, UPF#1 needs to translate IP-5 into the internal network address IP1 corresponding to QoS flow #1, so the data packet sent by UPF#1 to the remote UE includes destination address IP-1 and source address IP6 .
  • 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.
  • the source address remains unchanged. Therefore, the IP that needs to be added
  • the header includes the external network IP and source address corresponding to QoS flow #2, and the data packet routed from UPF#1 to UPF#2 includes IP-4 and IP6, IP-1 and IP6.
  • the data packet sent by UPF#1 to UPF#2 may not add IP headers (IP-4 and IP6), and UPF#2 adds the IP headers by itself.
  • UPF#2 translates the external network IP corresponding to QoS flow #2 into the internal network address IP-3 corresponding to QoS flow #2, UPF#2 routes the data packet to the relay UE according to the internal network address, the data packet Including IP-3 and IP-6, IP-1 and IP-6.
  • the relay UE is routed to the remote UE according to the PC5 QoS rule.
  • the remote UE determines that the multi-channel coordinated transmission needs to remove the outer IP header, and the obtained IP packet includes the destination address IP-1 and the source address IP6. Then the IP packet is sent to the APP client, and the APP client performs IP layer processing such as deduplication and reordering, so as to ensure reliability.
  • the direct path and the non-direct path of the remote UE are connected to UPF#1.
  • UPF#1 does not need to route the data packet to UPF#2, but directly routes the data packet to the relay UE.
  • Other steps are basically the same as those described in FIG. 8(a), and will not be repeated here.
  • Table 1(a) and Table 1(b) respectively show the English and corresponding Chinese interpretations of the feature information related to the multiplex transmission method provided by the embodiment of the present application.
  • Table 2(a) and Table 2(b) respectively show the English and corresponding Chinese interpretations of the feature information of the "Multi-Path Rule" multi-path transmission rule.
  • FIG. 9 is a schematic diagram of a data transmission method 900 provided by an embodiment of the present application.
  • the method 900 may be regarded as a specific implementation manner of the method 500, and the method 900 may include the following steps.
  • the remote UE triggers the relay UE to establish PDU session #2 and QoS flow #2 on the indirect path.
  • the remote UE triggers the relay UE to establish PDU session #2 on the indirect path through the PC5 interface, so that data transmission between the remote UE and the DN can be realized.
  • PDU session #2 includes QoS flow #2 (an example of the second QoS flow).
  • the identifier of the QoS flow #2 may be QFI-2.
  • the remote UE may acquire QoS flow information #1 during the process of triggering the establishment of the QoS flow #2, and the QoS flow information #1 includes the identification information QFI-2 of the QoS flow #2 and the PDR corresponding to the QFI-2.
  • the remote UE sends a request message #5 to the SMF#1.
  • the remote UE determines that a direct path needs to be established according to the data transmission requirement, so as to simultaneously use the non-direct path and the direct path to perform multiple transmissions, for example, reliable transmission or load balancing transmission is required.
  • the remote UE sends a request message #5 to AMF#1, and AMF#1 sends a request message #5 to SMF#1, and the request message #5 is used to request to establish a QoS flow #1 (first An example of a QoS flow).
  • the identifier of the QoS flow #1 may be QFI-1.
  • the request message #5 includes indication information #1 (an example of the third indication), and the indication information #1 is used to obtain QoS flow information #2 (an example of the first information), and the QoS flow information #2 includes the QoS flow #1 The identification information QFI-1 and the PDR corresponding to QFI-1.
  • the request message #5 also includes "request QoS rule” and "request QoS parameter".
  • the destination address of the packet filtering in "request QoS rule” is the same as the destination address of the packet filtering of the QoS rule of QFI-2; the "request QoS parameter” is the same as the QoS parameter of QoS flow #2.
  • the request message #5 may be a PDU session modification request (PDU session modification request) message.
  • the indication information #1 may be associated QoS flow (paired QoS flow) indication information.
  • the remote UE may send a request message #5 to AMF #1 through a UL NAS message.
  • AMF#1 may send a request message #5 to SMF#1 through an N11 message, and the N11 message may be a PDU session creation context request (Nsmf_PDUsession_createSMcontext request) message or the like.
  • Nsmf_PDUsession_createSMcontext request PDU session creation context request
  • AMF#1 and SMF#1 are network devices serving remote UEs.
  • SMF#1 sends a response message #3 to the remote UE.
  • SMF#1 sends a response message #3 to the remote UE through AMF#1.
  • the remote UE receives the response message #3.
  • response message #3 is used to respond to the above request message #5.
  • This response message #3 includes QoS flow information #2 (an example of the first information), QoS rule and QoS parameters.
  • the QoS flow information #2 includes the identification information QFI-1 of the QoS flow #1 and the PDR corresponding to the QFI-1.
  • the SMF#1 sends the PDR corresponding to the QFI-1 to the remote UE according to the indication information#1.
  • the response message #3 may be a PDU session modification accept (PDU session modification accept) message.
  • SMF#1 may send the response message #3 to AMF#1 through an N11 message, and the N11 message may be a N1N2 message transfer (Namf_communication_N1N2MessageTransfer) message.
  • N11 message may be a N1N2 message transfer (Namf_communication_N1N2MessageTransfer) message.
  • the remote UE sends a request message #6 to the relay UE through the indirect path.
  • the remote UE sends a request message #6 (an example of the first message) to the relay UE through the PC5 interface.
  • This request message #3 includes QoS flow information #2 and instruction information #2 (an example of the first instruction).
  • the request message #6 may also carry indication information #4.
  • the instruction information #3 is used to instruct the network device (UPF#2) to perform reliable transmission or load balancing transmission.
  • the request message #6 may be a link modification request (link modification request) message.
  • the indication information #2 may be associated QoS flow (paired QoS flow) indication information.
  • the relay UE sends a request message #7 to the SMF #2.
  • 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).
  • the relay UE carries QoS flow information #2 and indication information #2 in the request message #7.
  • the request message #7 is used to request SMF#2 to modify the QoS flow #2.
  • the modification here can be understood as modifying the QoS parameters corresponding to the QoS flow #2, that is, increasing the QoS parameter included in the QoS flow information #2.
  • the QoS parameter of flow #1 can be understood as adding the PDR corresponding to QFI-1.
  • the request message #7 may be a PDU session modification request (PDU session modification request) message.
  • the request message #7 may also carry indication information #3 (an example of third indication information).
  • the instruction information #3 is used to instruct the network device (UPF#2) to perform reliable transmission or load balancing transmission.
  • S960, SMF#2 sends request message #8 to UPF#2.
  • SMF#1 carries QoS flow information #1 and QoS flow information #2 in the request message #8.
  • the request message #8 may also carry indication information #3 (an example of third indication information).
  • the instruction information #3 is used to instruct the network device (UPF#2) to perform reliable transmission or load balancing transmission.
  • the request message #8 may be an N4 modification request message.
  • SMF#2 sends a response message #4 to the relay UE.
  • SMF#2 sends a response message #4 to the relay UE through AMF#2.
  • the response message #4 is used to respond to the request message #7, and the SMF #2 finishes modifying the QoS flow #2.
  • the response message #4 may be a PDU session modification accept (PDU session modification accept) message.
  • the relay UE sends a response message #5 to the remote UE.
  • the relay UE sends a response message #5 to the remote UE through the PC5 interface.
  • This response message #5 is used to respond to the request message #6.
  • the response message #5 may be a link modification accept (link modification accept) message.
  • UPF #2 determines to perform multiplex transmission according to the request message #8.
  • 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 multiplex transmission.
  • the UPF #2 may determine to specifically perform reliable transmission or load balancing transmission according to the indication information #3.
  • the UE simultaneously transmits downlink data packets through the direct and indirect paths, thereby increasing the data transmission rate or increasing the reliability.
  • FIG. 10 is a schematic diagram of a data transmission method 1000 provided by an embodiment of the present application.
  • the method 1000 may be regarded as a specific implementation manner of the method 500, and the method 1000 may include the following steps.
  • the remote UE establishes a PDU session #1 and a QoS flow #1 on the direct path.
  • PDU session #1 includes QoS flow #1 (an example of the second QoS flow).
  • the identifier of the QoS flow #1 may be QFI-1.
  • the remote UE can acquire QoS flow information #2 during the process of establishing the QoS flow #1, and the QoS flow information #2 includes the identification information QFI-1 of the QoS flow #1 and the PDR corresponding to the QFI-1.
  • the remote UE sends a request message #1 (an example of a first request message) to the relay UE through an indirect path.
  • the remote UE determines that an indirect path needs to be established according to the data transmission requirement, so as to simultaneously use the indirect path and the direct path for multiple transmissions, for example, reliable transmission or load balancing transmission is required.
  • the remote UE sends a request message #1 (an example of the 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 (first QoS flow #2) on the non-direct path.
  • a request message #1 an example of the first request message
  • the request message #1 is used to request to establish a QoS flow #2 (first QoS flow #2) on the non-direct path.
  • QoS flow #2 first QoS flow #2
  • the identifier of the QoS flow #2 may be QFI-2.
  • the request message #1 includes indication information #1 (an example of the second indication information), the indication information #1 is used to obtain the QoS flow information #1 (an example of the first information), and the QoS flow information #1 includes the QoS flow # 2 identification information QFI-2.
  • the request message #1 also includes "request PC5 QoS rule” and "request PC5 QoS parameter".
  • the destination address of the data packet filtering in "request PC5 QoS rule” is the same as the destination address of the data packet filtering of the QoS rule of QFI-1; the "request PC5 QoS parameter” is the same as the QoS parameter of QoS flow #1.
  • the remote UE may acquire QoS flow information #2 (an example of the second information) of the QoS flow #1 on the direct path.
  • the QoS flow information #2 includes QoS rule and QoS parameters of QFI-1.
  • the request message #1 may be a link modification request (link modification request) message.
  • the indication information #1 may be associated QoS flow (paired QoS flow) indication information.
  • the relay UE sends a request message #9 to the SMF#2.
  • the relay UE sends a request message #9 to AMF#2, and AMF#2 sends a request message #9 to SMF#2, and the request message #9 includes "request QoS rule" and "request QoS parameter".
  • SMF#2 establishes QoS flow #2 on the indirect path according to the request message #9.
  • 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.
  • the request message #9 may be a PDU session modification request (PDU session modification request) message.
  • the relay UE can send request message #9 to AMF #2 through UL NAS message.
  • AMF#2 can send a request message #9 to SMF#2 through an N11 message, and the N11 message can be a PDU session creation context request (Nsmf_PDUsession_createSMcontext request) message or the like.
  • Nsmf_PDUsession_createSMcontext request PDU session creation context request
  • AMF#2 and SMF#2 are network devices serving the relay UE.
  • SMF#2 sends a response message #6 to the relay UE.
  • SMF#2 sends a response message #6 to the relay UE through AMF#2.
  • response message #6 is used to respond to the above request message #9.
  • the response message #6 may be a PDU session modification accept (PDU session modification accept) message.
  • the response message #6 includes the identification information QFI-2 of the QoS flow #2.
  • the response message #6 also includes QoS rule and QoS parameters.
  • the "QoS rule” and “QoS parameter” in the response message #6 are the "request QoS rule” and "request QoS parameter” sent by SMF#2 according to the relay UE. "definite.
  • the relay UE sends a response message #7 to the remote UE through the indirect path.
  • the relay UE sends a response message #7 to the remote UE through the PC5 interface, and the response message #7 includes the QFI-2 of the QoS flow information #1 (an example of the first information), the ID of the PDU session #2, the Following UE's ID, PC5 QoS rule and PC5 QoS parameters.
  • the response message #7 may be a link modification accept (link modification accept) message.
  • 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.
  • 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.
  • the relay UE ID can be GUTI or S-TMSI.
  • the remote UE sends a request message #10 to the AMF #1 through the direct path.
  • 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.
  • the request message #10 may also include indication information #2.
  • the request message #10 may be a NAS message, and is used to request to modify the parameters of the QoS flow #1.
  • the modification here can be understood as modifying the QoS parameters corresponding to the QoS flow #1, that is, adding the QoS parameters of the QoS flow #2 included in the QoS flow information #1.
  • AMF#1 sends a request message #11 to AMF#2.
  • AMF#1 determines the address of AMF#2 serving the relay UE according to the ID of the relay UE included in the request message #10, and further, sends a request message #11 to AMF#2.
  • the request message #11 includes QFI-2, the ID of the PDU session #2 and the ID of the relay UE.
  • the request message #11 may also include indication information #2.
  • the indication information #2 is used to instruct the AMF #2 to send the PDR corresponding to the QFI-2.
  • AMF#1 may send a request message #11 to AMF#2 through an N11 message, and the N11 message may be a (Namf_communication_UEContextTransfer request) message.
  • AMF#2 sends a response message #8 to AMF#1.
  • the AMF#2 determines the address of the UPF#2 serving 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, AMF#2 sends a response message #8 to AMF#1.
  • response message #8 is used to respond to the above request message #11.
  • the response message #8 carries the address of UPF #2 and the PDR corresponding to QFI-2.
  • AMF#2 acquires the address of UPF#2 from SMF#2.
  • the address of UPF#2 can be a fully qualified domain name (fully qualified domain name, FQDN) or an IP address of UPF-2.
  • AMF#2 sends the PDR corresponding to QFI-2 to AMF#1 according to the indication information.
  • AMF#2 may send a response message #8 to AMF#1 through an N11 message, and the N11 message may be a (Namf_communication_UEContextTransfer response) message.
  • AMF#1 sends a request message #12 to SMF#1.
  • 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.
  • indication information #2 may also be included.
  • the request message #12 is used to request SMF#1 to modify the QoS parameters of the PDU session #1 of the QoS flow #1.
  • the modification here can be understood as modifying the QoS parameters corresponding to the QoS flow #1, namely , adding the QoS parameters of the QoS flow #2 included in the QoS flow information #1, specifically, adding the PDR corresponding to QFI-2.
  • AMF#1 may send a request message #12 to SMF#1 through an N11 message, and the N11 message may be a (Namf_PDUSession_UpdateSMContext request) message.
  • S1091 SMF#1 sends request message #13 to UPF#1.
  • the request message #13 includes the PDR corresponding to QFI-2, the PDR corresponding to QFI-1, and QFI-2.
  • indication information #3 (an example of third indication information) may also be included.
  • the instruction information #3 is used for UPF#1 to determine to perform multiplex transmission, and specifically, to determine to perform reliable transmission or load-balanced transmission.
  • the PDR corresponding to QFI-2, QFI-2 and indication information #3 may be carried in the PDR corresponding to QFI-1.
  • SMF#1 may send a request message #13 to UPF#1 through the N4 modification request message.
  • SMF#1 determines whether UPF#1 and UPF#2 are the same UPF according to the address of UPF#2 included in the request message 12.
  • downlink data transmission can be performed directly according to method 800(b).
  • SMF#1 may transmit downlink data according to method 800(a).
  • SMF#1 may initiate channel establishment between UPF#1 and UPF#2.
  • the channel between UPF#1 and UPF#2 can be used to transmit data, and this solution can also be used in method 700 and method 900, and the implementation methods of the various embodiments can be combined with each other. This is not limited.
  • UPF#1 allocates channel-related information, and the channel-related information is sent to UPF#2 through SMF#1, AMF#1, AMF#2 and SMF#2.
  • the tunnel-related information of UPF#1 includes the address and tunnel (tunnel) ID of UPF#1.
  • the tunnelID may be a full qualified tunnel endpoint ID (full qualified tunnel endpoint ID, F-TEID).
  • UPF#1 allocates channel-related information
  • the signaling sent to UPF#2 through SMF#1, AMF#1, AMF#2 and SMF#2 can be sent through N1 message.
  • UPF#1 may send channel-related information to SMF#1 through the N4 modification response message.
  • response message is used to respond to the request message #13.
  • SMF#1 may send channel-related information to AMF#1 through the Namf_PDUSession_UpdateSMContext response message.
  • AMF#1 may send channel-related information to AMF#2 through a Namf_communication_UEContextTransfer request message.
  • AMF#2 can send channel-related information to SMF#2 through the Namf_PDUSession_UpdateSMContext request message.
  • SMF#2 may send channel-related information to UPF#2 through the N4 modification response message.
  • UPF#2 allocates channel-related information, and the channel-related information is sent to UPF#1 through SMF#2, AMF#2, AMF#1 and SMF#1.
  • the tunnel-related information of UPF#2 includes the address and tunnel (tunnel) ID of UPF#2.
  • the tunnelID may be a full qualified tunnel endpoint ID (full qualified tunnel endpoint ID, F-TEID).
  • the signaling interaction process is similar to the above-mentioned process of UPF#1 allocating channel-related information, and will not be repeated here.
  • UPF #1 determines to perform multiplex transmission according to the request message #13.
  • 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 multiplex transmission.
  • UPF #1 may determine to specifically perform reliable transmission or load balancing transmission according to the indication information #3.
  • the method for UPF to perform multiple transmission is basically the same as method 800, the difference is that in this embodiment, when the non-direct path and the direct path of the remote UE are connected to different UPFs, step a and step b Exactly the same as method 800, when UPF#1 executes step c, the PDR corresponding to UPF#1QFI-1 determines the channel between UPF#1 and UPF#2, and sends new IP packets (including IP-4 and IP6, IP- 1 and IP6) add a new GTP-U message header, and send it to UPF#2 through this channel, and include the information of QFI-2 in the GTP-U message header, step d: UPF#2 receives GTP-U in this channel After the message, transfer the GTP-U to Gnb#2 according to the direct mapping relationship of the channel identifier; 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 sends the IP packet to the relay
  • FIG. 11 is a schematic diagram of a data transmission method 1100 provided by an embodiment of the present application.
  • the method 1100 may be regarded as a specific implementation manner of the method 500, and the method 1100 may include the following steps.
  • the remote UE triggers the relay UE to establish PDU session #2 and QoS flow #2 on the indirect path.
  • the remote UE triggers the relay UE to establish PDU session #2 on the indirect path through the PC5 interface, so that data transmission between the remote UE and the DN can be realized.
  • PDU session #2 includes QoS flow #2 (an example of the second QoS flow).
  • the identifier of the QoS flow #2 may be QFI-2.
  • the remote UE may acquire QoS flow information #1 during the process of triggering the establishment of the QoS flow #2, and the QoS flow information #1 includes the identification information QFI-2 of the QoS flow #2 and the PDR corresponding to the QFI-2.
  • the remote UE sends a request message #14 to SMF#1.
  • the remote UE determines that a direct path needs to be established according to the data transmission requirement, so as to simultaneously use the non-direct path and the direct path to perform multiple transmissions, for example, reliable transmission or load balancing transmission is required.
  • the remote UE sends a request message #14 to AMF#1, and AMF#1 sends a request message #14 to SMF#1, and the request message #14 is used to request to establish a QoS flow #1 (first An example of a QoS flow).
  • the identifier of the QoS flow #1 may be QFI-1.
  • the request message #14 includes indication information #1 (an example of the second indication information), and the indication information #1 is used to obtain the QoS flow information #2 (an example of the first information), and the QoS flow information #2 includes the QoS flow # 1 identification information QFI-1.
  • the request message #14 also includes "request QoS rule” and "request QoS parameter".
  • the destination address of the data packet filtering in "request QoS rule” is the same as the destination address of the data packet filtering of the QoS rule of QFI-2; the "request QoS parameter” is the same as the QoS parameter of QoS flow #2.
  • the request message #14 may be a PDU session modification request (PDU session modification request) message.
  • the indication information #1 may be associated QoS flow (paired QoS flow) indication information.
  • the remote UE can send request message #14 to AMF #1 through UL NAS message.
  • AMF#1 can send a request message #14 to SMF#1 through an N11 message, and the N11 message can be a PDU session creation context request (Nsmf_PDUsession_createSMcontext request) message or the like.
  • Nsmf_PDUsession_createSMcontext request PDU session creation context request
  • AMF#1 and SMF#1 are network devices serving remote UEs.
  • SMF#1 sends a response message #9 to the remote UE.
  • SMF#1 sends a response message #9 to the remote UE through AMF#1.
  • the remote UE receives the response message #9.
  • response message #9 is used to respond to the above request message #14.
  • the response message #9 includes the identification information QFI-1 (an example of the first information) of the QoS flow #1 and the ID of the PDU session #1.
  • the response message #9 may also include QoS rule and QoS parameters.
  • 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.
  • the response message #9 may be a PDU session modification accept (PDU session modification accept) message.
  • SMF#1 may send the response message #9 to AMF#1 through an N11 message, and the N11 message may be a N1N2 message transfer (Namf_communication_N1N2MessageTransfer) message.
  • N11 message may be a N1N2 message transfer (Namf_communication_N1N2MessageTransfer) message.
  • the remote UE sends a request message #15 to the relay UE through an indirect path.
  • the remote UE sends a request message #15 (an example of the first message) to the relay UE through the PC5 interface.
  • the request message #15 includes QFI-1, the ID of the PDU session #1, the ID of the remote UE, and a modification request for the PDU session #2 of the QoS flow #2. (An example of the first instruction information).
  • the request message #15 may also carry indication information #2 (an example of the first indication information).
  • the request message #15 may be a link modification request (link modification request) message.
  • the indication information #2 may be associated QoS flow (paired QoS flow) indication information.
  • 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.
  • AMF#2 sends a request message #16 to AMF#1.
  • AMF#2 determines the address of AMF#1 serving the remote UE according to the ID of the remote UE included in the request message #15, and further sends a request message #16 to AMF#1.
  • the request message #16 includes QFI-1, the ID of the PDU session #1 and the ID of the remote UE.
  • the request message #16 may also include indication information #2.
  • the indication information #2 is used to instruct the AMF #2 to send the PDR corresponding to the QFI-1.
  • AMF#2 may send a request message #16 to AMF#1 through an N11 message, and the N11 message may be a (Namf_communication_UEContextTransfer request) message.
  • AMF#1 sends a response message #10 to AMF#2.
  • AMF#1 determines the address of UPF#1 serving the remote UE QFI-1 and the PDR corresponding to QFI-1 according to QFI-1, the ID of PDU session #1 and the ID of the remote UE. Further, AMF#1 sends a response message #10 to AMF#2.
  • the response message #10 is used to respond to the above request message #16.
  • the response message #10 carries the address of UPF #1 and the PDR corresponding to QFI-1.
  • the address of UPF#1 can be a fully qualified domain name (fully qualified domain name, FQDN) or an IP address of UPF-1.
  • AMF#1 sends the PDR corresponding to QFI-1 to AMF#2 according to the indication information.
  • AMF#1 may send a response message #10 to AMF#2 through an N11 message, and the N11 message may be a (Namf_communication_UEContextTransfer response) message.
  • AMF#2 sends a request message #17 to SMF#2.
  • 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.
  • indication information #2 may also be included.
  • the request message #17 is used to request SMF#2 to modify the QoS parameters of the PDU session #2 of the QoS flow #2.
  • the modification here can be understood as modifying the QoS parameters corresponding to the QoS flow #2, namely , adding the QoS parameters of the QoS flow #1 included in the QoS flow information #2, which specifically may be adding the PDR corresponding to QFI-1.
  • AMF#2 may send a request message #17 to SMF#2 through an N11 message, and the N11 message may be a (Namf_PDUSession_UpdateSMContext request) message.
  • SMF#2 sends request message #18 to UPF#2.
  • the request message #18 includes the PDR corresponding to QFI-1, the PDR corresponding to QFI-2, and QFI-1.
  • indication information #3 (an example of third indication information) may also be included.
  • the instruction information #3 is used for UPF#2 to determine to perform multiplex transmission, and specifically, to determine to perform reliable transmission or load-balanced transmission.
  • the PDR corresponding to QFI-1, QFI-1 and indication information #3 may be carried in the PDR corresponding to QFI-2.
  • SMF#2 may send a request message #18 to UPF#2 through the N4 modification request message.
  • SMF#2 determines whether UPF#1 and UPF#2 are the same UPF according to the address of UPF#1 included in the request message 18 .
  • downlink data transmission can be performed directly according to method 800(b).
  • SMF#1 may transmit downlink data according to method 800(a).
  • SMF#2 may initiate channel establishment between UPF#1 and UPF#2.
  • the channel between UPF#1 and UPF#2 can be used to transmit data, and this solution can also be used in method 700 and method 900, and the implementation methods of the various embodiments can be combined with each other. This is not limited.
  • UPF#2 allocates channel-related information, and the channel-related information is sent to UPF#1 through SMF#2, AMF#2, AMF#1 and SMF#1.
  • the tunnel-related information of UPF#2 includes the address and tunnel (tunnel) ID of UPF#2.
  • the tunnelID may be a full qualified tunnel endpoint ID (full qualified tunnel endpoint ID, F-TEID).
  • UPF#2 allocates channel-related information, and the signaling sent to UPF#1 through SMF#2, AMF#2, AMF#1 and SMF#1 can be sent through N1 message.
  • UPF#2 may send channel-related information to SMF#2 through the N4 modification response message.
  • response message is used to respond to the request message #18.
  • SMF#2 can send channel-related information to AMF#2 through the Namf_PDUSession_UpdateSMContext response message.
  • AMF#2 may send channel-related information to AMF#1 through a Namf_communication_UEContextTransfer request message.
  • AMF#1 may send channel-related information to SMF#1 through the Namf_PDUSession_UpdateSMContext request message.
  • SMF#1 may send channel-related information to UPF#1 through the N4 modification response message.
  • UPF#1 allocates channel-related information, and the channel-related information is sent to UPF#1 through SMF#1, AMF#1, AMF#2 and SMF#2.
  • the tunnel-related information of UPF#1 includes the address and tunnel (tunnel) ID of UPF#1.
  • the tunnelID may be a full qualified tunnel endpoint ID (full qualified tunnel endpoint ID, F-TEID).
  • the signaling interaction process is similar to the above-mentioned process of UPF#2 allocating channel-related information, and will not be repeated here.
  • UPF #2 determines to perform multiplex transmission according to the request message #18.
  • UPF#2 determines the PDR corresponding to QFI-2 and the PDR corresponding to QFI-1 according to the request message #18, and further determines to perform multiplex transmission.
  • UPF #2 may determine to specifically perform reliable transmission or load balancing transmission according to the indication information #3.
  • the method for the UPF to perform multiplex transmission is the same as the transmission method performed after step S1093 is performed, and details are not described here in this embodiment of the application.
  • the UE simultaneously transmits downlink data packets through the direct and indirect paths, thereby increasing the data transmission rate or increasing the reliability.
  • the remote UE after the remote UE establishes PDU session #1 and QoS flow #1 on the direct path, the remote UE triggers the relay UE to establish the PDU session # on the non-direct path. 2 and QoS flow #2, and the remote UE triggers the modification process of PDU session #1, and executes the session association between the remote UE and the relay UE.
  • the two paths of the directly connected path perform multiplex transmission, wherein the UPF on the directly connected path and the UPF on the non-directly connected path can be used for data transmission.
  • the remote UE after the remote UE triggers the relay UE to establish PDU session #2 and QoS flow #2 on the non-direct path, the remote UE establishes the PDU session # on the direct path. 1 and QoS flow #1, and the relay UE triggers the modification process of PDU session #2, and executes the session association between the remote UE and the relay UE.
  • the relay UE may also trigger the modification process of the PDU session #2, and perform the association of the PDU session #1 and the PDU session #2; in the method 1100, It is also possible for the remote UE to trigger the modification process of the PDU session #1, and perform the association between the PDU session #1 and the PDU session #2.
  • This embodiment of the present application does not limit it.
  • Fig. 12 shows a flow chart of a data communication method 1200 provided by an embodiment of the present application.
  • the method 1200 includes a first communication path and a second communication path, wherein the first communication path is a connection between the first terminal device and the network A direct connection path for connection, and the second communication path is an indirect connection path for the first terminal device to connect to the network through a relay device.
  • the first terminal device may trigger modification of the first session and the first QoS flow through the direct path, where the first session and the first QoS flow are established by the first terminal device on the direct path.
  • the first session may be, for example, a first protocol data unit (protocol data unit, PDU) session
  • the second session may be, for example, a second PDU session
  • the first quality of service flow may be a first quality of service (quality of service, QoS) flow
  • the second quality of service flow may be a second QoS flow
  • the first mobility management entity may be a first AMF (access and mobility management function)
  • the second mobility management entity may be a second AMF
  • the first session function management entity may be a first SMF (session management function)
  • the second session function management entity may be, for example, a second SMF
  • the first user plane function management entity may be a first UPF (user plane function)
  • the second The user plane function management entity may be the second UPF.
  • the method includes the following steps.
  • the first terminal device acquires first information.
  • the first information includes an identifier of the first PDU session of the first communication path, an identifier of the second PDU session of the second communication path, and an identifier of the relay device.
  • the identifier of the second PDU session of the second communication path and the identifier of the relay device in the first information are obtained by the first terminal device from the relay device.
  • the first terminal device sends a connection establishment request message to the relay device to trigger the relay device to establish the second QoS flow and the second PDU session, and the relay device establishes the second QoS flow and the second PDU session Then the identifier of the second PDU session and/or the identifier of the second QoS flow may be sent to the first terminal device.
  • the first terminal device sends a connection establishment request message, which is used to trigger the relay device to establish the second QoS flow and the second PDU session.
  • the first The terminal device sends a connection modification request message, and the relay UE sends the identifier of the second PDU session and/or the identifier of the second QoS flow to the first terminal device through a response message of the connection modification request message.
  • the first terminal device first triggers the relay device to establish the second PDU session and the second QoS flow, and obtains the identifier of the second PDU session of the second communication path, and the ID of the second QoS flow corresponding to the second PDU session. ID and the ID of the relay device, and then when requesting to establish the first PDU session and the first QoS flow on the direct path, the first terminal device can request multiplex transmission in the request message, which includes the first PDU session The identifier of the second PDU session of the second communication path, the identifier of the second QoS flow corresponding to the second PDU session, and the identifier of the relay device.
  • the first information may also include the identifier of the first QoS flow and/or the identifier of the second QoS flow, the first QoS flow is the QoS flow corresponding to the first PDU session, and the second QoS flow is the second PDU session Corresponding QoS flow.
  • the first terminal device first establishes the first PDU session and the first QoS flow on the direct path, and then triggers the relay device to establish the second PDU session and the second QoS flow.
  • the first information can be Include the identifier of the first QoS flow.
  • the first terminal device sends a first request message to the first AMF.
  • the first request message includes first information, and the first request message is used to request to transmit the first data jointly through the first PDU session and the second PDU session.
  • the first request message further includes a first indication, where the indication is used to indicate that the first data is transmitted jointly through the first PDU session and the second PDU session.
  • the first request message further includes a first indication and a second indication, where the second indication is used to describe the first data.
  • the specific distinction granularity of the first data is not emphasized.
  • the granularity of the QoS flow may be used.
  • data originally transmitted through a specific QoS flow needs to be multiplexed.
  • the second indication can be limited to the granularity of service data flow, such as the granularity of Service data flow (SDF), and it can also be understood that the second indication further describes the type of data that needs to be multiplexed in the first data, for example, The type may be the business type of the data.
  • SDF granularity of Service data flow
  • the first PDU session includes the first QoS flow
  • the first request message is used to request to jointly transmit all or part of the data transmitted by the first QoS flow through the first PDU session and the second PDU session, or, the second PDU session
  • the second QoS flow is included, and the first request message is used to request to transmit all or part of the data transmitted by the second QoS flow through the first PDU session and the second PDU session.
  • the first data includes all or part of the data transmitted through the first QoS flow, or the first data includes all or part of the data transmitted through the second QoS flow.
  • the data originally transmitted on the directly connected path may be jointly transmitted on the two paths, and the data originally transmitted on the non-directly connected path may be jointly transmitted on the two paths.
  • the first request message further includes a third indication, where the third indication is used to indicate that the first communication path is an anchor path, or the third indication is used to indicate that the second communication path is an anchor path,
  • the first communication path and the second communication path communicate with the application server through the user plane functional entity serving the anchor path.
  • the first SMF and the second SMF may determine that the first UPF or the second UPF is the anchor UPF based on the third indication information.
  • the first request message further includes an identifier of the first terminal device, and the identifier of the first terminal device corresponds to the second communication path.
  • the identifier of the first terminal device is the identifier used when the first terminal device discovers or establishes a connection with the second terminal device, and the identifier of the first terminal device may be assigned by the relay device for the first terminal device, or It can be assigned by the first terminal device itself.
  • the identifier of the first terminal device is used by the second SMF to configure identification rules for the second UPF.
  • the identification rules are used by the second UPF to determine the data to be multiplexed.
  • the second The SMF can determine the IP address and port number information used by the relay device when relaying the data of the first terminal device according to the identifier of the first terminal device, so as to configure the identification rule for the second UPF, and the identification rule is used for the second UPF
  • the data passing through the multiplexed first terminal device is determined according to the IP address and port number information.
  • the first UPF and the second UPF After receiving the first request message, the first UPF and the second UPF transmit the first data.
  • the first AMF can determine the second AMF through the identifier of the relay device, or determine the second SMF according to the identifier of the relay device and the identifier of the second PDU session, wherein , the second AMF serves the relay device, and the second SMF serves the second PDU session.
  • a first channel between the first UPF and the second UPF is established through the first SMF and the second SMF, and the first UPF and the second UPF can transmit the first data through the first channel.
  • the first SMF obtains the first channel information from the first UPF and sends the first channel information to the second UPF through the second SMF, and the first channel information is used for the first UPF to send the first channel information to the second UPF through the first channel.
  • the second UPF sends data;
  • the second SMF obtains the second channel information from the second UPF and sends the second channel information to the first UPF through the first SMF, and the first channel information is used for the second UPF to send data to the first UPF through the first channel.
  • UPF sends data.
  • the first AMF determines the second AMF according to the first identifier of the relay device; the first AMF obtains the address of the second SMF from the second AMF; the first AMF sends the address of the second SMF to the first SMF; The first SMF obtains the first channel information from the first UPF; the first SMF sends the first channel information to the second SMF according to the address of the second SMF; the second SMF obtains the second channel information from the second UPF; the second SMF sends The first SMF sends the second channel information.
  • the steps of sending channel information between the first SMF and the second SMF are not limited in sequence.
  • the first AMF determines the second AMF according to the first identifier of the relay device; the first AMF acquires first channel information from the first UPF through the first SMF The second AMF acquires second channel information from the second UPF through the second SMF; the first AMF sends the second channel information to the first UPF through the first SMF; The second AMF sends the first channel information to the second UPF through the second SMF.
  • the steps of sending channel information between the first SMF and the second SMF are not limited in sequence.
  • the first UPF and the second UPF transmit the first data according to rules configured by the first SMF and the second SMF.
  • the first UPF is an anchor UPF
  • the first SMF sends a first rule to the first UPF
  • the first rule is used to instruct the first UPF to send part or all of the first data to the second UPF
  • the second UPF is made to send the data received from the first UPF to the first terminal device through the second communication path.
  • the first UPF is an anchor UPF
  • the first SMF sends a second rule to the first UPF
  • the second rule is used to instruct the first UPF to send the data received from the second UPF to the application server.
  • the first UPF is an anchor UPF
  • the second SMF sends a third rule to the second UPF
  • the third rule is used to instruct the second UPF to send the first UPF received from the first terminal device to the first UPF.
  • the data to be multiplexed that the first terminal device sends to the second UPF through the second communication path may be all or part of the first data, depending on the distribution rule of the first terminal device.
  • the splitting rule can be understood as the granularity of multiplex transmission by the first terminal device. For example, if the granularity of QoS flow is used as the granularity, the data to be multiplexed may be all of the first data; if the granularity of service data flow is used, then The data to be multiplexed may be part of the first data. For the second UPF, all the data to be multiplexed and sent by the first terminal device received from the second communication path must be sent to the first UPF.
  • the first UPF is an anchor UPF
  • the second SMF sends a fourth rule to the second UPF
  • the fourth rule is used to instruct the second UPF to send the first UPF received from the first UPF to the first terminal device.
  • the second UPF is an anchor UPF
  • the first SMF sends a first rule to the first UPF
  • the first rule is used to instruct the first UPF to send the second UPF received from the first terminal device to the second UPF.
  • the second UPF is an anchor UPF
  • the first SMF sends a second rule to the first UPF
  • the second rule is used to instruct the first UPF to send the data received from the second UPF to the first terminal device .
  • the second UPF is an anchor UPF
  • the second SMF sends a third rule to the second UPF
  • the third rule is used to instruct the second UPF to send part or all of the first data to the first UPF
  • the first UPF is made to send the data received from the second UPF to the first terminal device through the first communication path.
  • the second UPF is an anchor UPF
  • the second SMF sends a fourth rule to the second UPF, where the fourth rule is used to instruct the second UPF to send the data received from the first UPF to the application server.
  • the first SMF receives first information from the first AMF, and the first SMF generates the first rule and the second rule according to the first information.
  • the second SMF receives the second information from the first SMF or the second AMF, and the second SMF generates the third rule and the fourth rule according to the second information.
  • the second information includes: the first indication, the identifier of the second PDU session, and the second identifier of the relay device, and the second identifier of the relay device is determined by the first AMF according to the first identifier of the relay device.
  • the second information further includes at least one of the following: an identifier of the second QoS flow, a second indication, an identifier of the first terminal device, or a third indication.
  • the second SMF receives the identifier of the second PDU session, the identifier of the second QoS flow corresponding to the second PDU session, and the second identifier of the relay device from the first SMF, and the second SMF receives the identifier of the second PDU session according to the second
  • the identifier of the PDU session, the identifier of the second QoS flow corresponding to the second PDU session, and the second identifier of the relay device generate a third rule and a fourth rule.
  • the first UPF of the direct path of the first terminal device can establish a transmission channel with the second UPF of the non-direct path, so that the first terminal device can transmit the direct path through the direct path and the non-direct path Part or all of the data of the first QoS flow or part or all of the data of the second QoS flow of the non-direct path is transmitted to realize redundant transmission, load balancing transmission or switching transmission of data.
  • FIG. 13 shows a flow chart of a data communication method 1300 provided by an embodiment of the present application.
  • the method 1300 includes a first communication path and a second communication path, wherein the first communication path is a connection between the first terminal device and the network A direct connection path for connection, and the second communication path is an indirect connection path for the first terminal device to connect to the network through a relay device.
  • the relay device may trigger modification of the second PDU session and the second QoS flow, where the second PDU session and the second QoS flow are established by the relay device on the indirect path.
  • the method includes the following steps.
  • the relay device acquires third information.
  • the third information includes the identifier of the second PDU session of the second communication path, the identifier of the first PDU session of the first communication path, and the identifier of the first terminal device.
  • the identifier of the first PDU session of the first communication path and the identifier of the first terminal device in the third information are acquired by the relay device from the first terminal device.
  • the first terminal device may send the identifier of the first PDU session and the identifier of the first QoS flow to the relay device.
  • the relay device sends a connection modification request message, and the first terminal device can send the first PDU to the relay device through the connection modification request message
  • the identifier of the session and the identifier of the first QoS flow are identifiers of the first QoS flow.
  • the third information may also include the identifier of the second QoS flow and/or the identifier of the first QoS flow, the first QoS flow is the QoS flow corresponding to the first PDU session, and the second QoS flow is the second PDU The QoS flow corresponding to the session.
  • the relay device first establishes the second PDU session and the second QoS flow on the non-direct path, and then the first terminal device establishes the first PDU session and the first QoS flow.
  • the third information can be Including the identifier of the second QoS flow.
  • the relay device sends a second request message to the second AMF.
  • the second request message includes third information, and the second request message is used to request to transmit the first data jointly through the first PDU session and the second PDU session.
  • the second request message further includes a first indication, where the first indication is used to indicate that the first data is jointly transmitted through the first PDU session and the second PDU session.
  • the first request message further includes a first indication and a second indication, where the second indication is used to describe the first data.
  • the specific transmission granularity is not emphasized, for example, the QoS flow may be used as the granularity; when the first request message includes the first indication and the second indication, the second indication may be Multiplexing at a defined granularity.
  • the second indication can be limited to the granularity of service data flow, such as the granularity of SDF. It can also be understood that the second indication further describes the type of data that needs to be multiplexed in the first data. For example, the type can be data type of business.
  • the first PDU session includes the first QoS flow
  • the second request message is used to request to jointly transmit all or part of the data transmitted by the first QoS flow through the first PDU session and the second PDU session, or, the second PDU session
  • the second QoS flow is included, and the second request message is used to request to transmit all or part of the data transmitted by the second QoS flow through the first PDU session and the second PDU session.
  • the first data includes all or part of the data transmitted through the first QoS flow, or the first data includes all or part of the data transmitted through the second QoS flow.
  • the data originally transmitted on the directly connected path may be jointly transmitted on the two paths, and the data originally transmitted on the non-directly connected path may be jointly transmitted on the two paths.
  • the second request message further includes a third indication, where the third indication is used to indicate that the first communication path is an anchor path, or the third indication is used to indicate that the second communication path is an anchor path,
  • the first communication path and the second communication path communicate with the application server through the user plane functional entity serving the anchor path.
  • the first UPF and the second UPF After receiving the second request message, the first UPF and the second UPF transmit the first data.
  • the second AMF can determine the first AMF through the identifier of the first terminal device, or determine the first SMF according to the identifier of the first terminal device and the identifier of the first PDU session , wherein the first AMF serves the first remote device, and the first SMF serves the first PDU session.
  • a first channel between the first UPF and the second UPF is established through the first SMF and the second SMF, and the first UPF and the second UPF can transmit the first data through the first channel.
  • the first SMF obtains the first channel information from the first UPF and sends the first channel information to the second UPF through the second SMF, and the first channel information is used for the first UPF to send the first channel information to the second UPF through the first channel.
  • the second UPF sends data;
  • the second SMF obtains the second channel information from the second UPF and sends the second channel information to the first UPF through the first SMF, and the first channel information is used for the second UPF to send data to the first UPF through the first channel.
  • UPF sends data.
  • the second mobility management entity obtains the address of the first session management function entity from the first mobility management entity;
  • the functional entity sends the address of the first session management functional entity;
  • the second session management functional entity acquires second channel information from the second user plane functional entity;
  • the second session management functional entity obtains the second channel information according to the first The address of the session management function entity, sending the second channel information to the first session management function entity;
  • the first session management function entity acquires the first channel information from the first user plane function entity;
  • the second channel management function entity A session management function entity sends the first channel information to the second session management function entity.
  • the steps of sending channel information between the first SMF and the second SMF are not limited in sequence.
  • the second mobility management entity determines the first mobility management entity according to the first identifier of the first terminal device; the second mobility management entity manages the The functional entity acquires second channel information from the second user plane functional entity; the first mobility management entity acquires first channel information from the first user plane functional entity through the first session management functional entity; The second mobility management entity sends the first channel information to the second user plane functional entity through the second session management functional entity; the first mobility management entity transmits the first channel information through the first session management functional entity sending the second channel information to the first user plane functional entity.
  • the steps of sending channel information between the first SMF and the second SMF are not limited in sequence.
  • the first UPF and the second UPF transmit the first data according to rules configured by the first SMF and the second SMF.
  • the first UPF is an anchor UPF
  • the first SMF sends a first rule to the first UPF
  • the first rule is used to instruct the first UPF to send part or all of the first data to the second UPF
  • the second UPF is made to send the data received from the first UPF to the first terminal device through the second communication path.
  • the first UPF is an anchor UPF
  • the first SMF sends a second rule to the first UPF
  • the second rule is used to instruct the first UPF to send the data received from the second UPF to the application server.
  • the first UPF is an anchor UPF
  • the second SMF sends a third rule to the second UPF
  • the third rule is used to instruct the second UPF to send the first UPF received from the first terminal device to the first UPF.
  • the data to be multiplexed that the first terminal device sends to the second UPF through the second communication path may be all or part of the first data, depending on the distribution rule of the first terminal device.
  • the splitting rule can be understood as the granularity of multiplex transmission by the first terminal device. For example, if the granularity of QoS flow is used as the granularity, the data to be multiplexed may be all of the first data; if the granularity of service data flow is used, then The data to be multiplexed may be part of the first data. For the second UPF, all the data to be multiplexed and sent by the first terminal device received from the second communication path must be sent to the first UPF.
  • the first UPF is an anchor UPF
  • the second SMF sends a fourth rule to the second UPF
  • the fourth rule is used to instruct the second UPF to send the first UPF received from the first UPF to the first terminal device.
  • the second UPF is an anchor UPF
  • the first SMF sends the first rule to the first UPF, where the first rule is used to instruct the first UPF to send the first data received from the first terminal device to the second UPF.
  • the second UPF is an anchor UPF
  • the first SMF sends a second rule to the first UPF
  • the second rule is used to instruct the first UPF to send the data received from the second UPF to the first terminal device .
  • the second UPF is an anchor UPF
  • the second SMF sends a third rule to the second UPF
  • the third rule is used to instruct the second UPF to send part or all of the first data to the first UPF
  • the first UPF is made to send the data received from the second UPF to the first terminal device through the first communication path.
  • the second UPF is an anchor UPF
  • the second SMF sends a fourth rule to the second UPF, where the fourth rule is used to instruct the second UPF to send the data received from the first UPF to the application server.
  • the first SMF receives first information from the first AMF, and the first SMF generates the first rule and the second rule according to the first information.
  • the first SMF receives the second information from the second SMF or the second AMF, and the second SMF generates the third rule and the fourth rule according to the second information.
  • the second information includes: the first indication, the identifier of the second PDU session, and the second identifier of the relay device, and the second identifier of the relay device is determined by the first AMF according to the first identifier of the relay device.
  • the second information further includes at least one of the following: an identifier of the second QoS flow, a second indication, an identifier of the first terminal device, or a third indication.
  • the first SMF receives the identifier of the first PDU session, the identifier of the first QoS flow corresponding to the first PDU session, and the second identifier of the first terminal device from the second SMF, and the first SMF according to the first SMF
  • the identifier of a PDU session, the identifier of the first QoS flow corresponding to the first PDU session, and the second identifier of the first terminal device generate a third rule and a fourth rule.
  • the first UPF of the direct path of the first terminal device can establish a transmission channel with the second UPF of the non-direct path, so that the first terminal device can transmit the direct path through the direct path and the non-direct path Part or all of the data of the first QoS flow or part or all of the data of the second QoS flow of the non-direct path is transmitted to realize redundant transmission, load balancing transmission or switching transmission of data.
  • FIG. 14 shows a schematic diagram of a data transmission method 1400 provided by an embodiment of the present application.
  • the method 1400 is applicable to the above method 1200 and method 1300, wherein the remote UE is an example of a first terminal device, and the relay UE is an example of a relay device.
  • the method 1400 may include the following steps.
  • the remote UE and the relay UE perform an authorization process for multiplex transmission.
  • the remote UE and the relay UE are authorized by the network side to perform multiplex transmission.
  • the remote UE acquires authorization information #a, where the authorization information #a includes: the network side authorizes the remote UE to perform multiplex transmission through the direct path and the non-direct path.
  • the relay UE acquires authorization information #b, and the authorization information #b includes: the network side authorizes the indirect path of the relay UE to be used by the remote UE to perform multiplex transmission.
  • the remote UE and the relay UE respectively establish a PDU session and a QoS flow on the direct path and the non-direct path.
  • the remote UE establishes PDU session #1 (as an example of the first PDU session) and QoS flow #1 (as an example of the first QoS flow) on the direct path
  • the relay UE establishes a PDU on the non-direct path Session #2 (an example of a second PDU session) and QoS flow #2 (an example of a second QoS flow).
  • the remote UE first establishes a direct path, establishes PDU session #1 and QoS flow #1 on the direct path, then triggers the relay UE to establish a non-direct path, and establishes PDU session #2 and QoS flow on the non-direct path #2.
  • UPF1 on the direct path acts as an anchor point for UPF#2 on the non-direct path to communicate with the server.
  • the remote UE first establishes PDU session #1 and QoS flow #1 on the direct path, and the remote UE establishes PDU session #2 and QoS flow #2 on the non-direct path through the relay UE, specifically including Step S1420a1-step S1420a5, the specific steps are as follows:
  • the remote UE establishes PDU session #1 and QoS flow #1 on the direct path.
  • the remote UE initiates the establishment of PDU session #1 on the direct path, so that data transmission between the remote UE and the DN can be realized.
  • PDU session #1 includes QoS flow #1, and the identifier of the QoS flow #1 may be QFI-1.
  • the remote UE performs a discovery process of the relay UE.
  • the remote UE sends a discovery message.
  • the relay UE sends an announcement message according to the discovery message, and the announcement message may include indication information #2, where the indication information #2 is used to indicate that multiplex transmission is supported. That is, the relay UE supports simultaneous transmission with the remote UE on the direct path and the non-direct path. In other words, if the remote UE needs to perform multiple transmission, it can select a relay UE that supports multiple transmission.
  • the remote UE if the remote UE needs to perform multiplex transmission, the remote UE sends a request message #1, in which request message #1 supports multiplex transmission, and correspondingly, the response sent by the relay UE
  • the message may include indication information #2 indicating that multiplex transmission is supported.
  • the remote UE sends a request message #1 to the relay UE through the PC5 interface.
  • the remote UE sends a request message #1 to the relay UE through the PC5 interface, and the request message #1 is used for the relay UE to establish a QoS flow #2 and a PDU session #2 on a non-direct path, and the QoS flow #
  • the identification of 2 may be QFI-2.
  • the request message #1 may include at least one of the identifier of the PC5 QoS flow, the PC5 QoS rule, and the destination address of the packet filter.
  • the remote UE indicates that the data transmitted by the PC5 QoS flow identified by the PC5 QoS flow to the relay UE can be multiplexed, or the IP data packet can match the data of the PC5 QoS rule and Packet filter Multiplexing can be performed.
  • the request message #1 also includes "request PC5 QoS rule” and "request PC5 QoS parameter".
  • the destination address of packet filtering in "request PC5 QoS rule” is the same as the destination address of packet filtering in QoS rule of QFI-1;
  • “request PC5 QoS parameter” is the same as the QoS parameter of QoS flow #1.
  • the remote UE can obtain the QFI-1 identifier of the QoS flow #1 and the ID of the PDU session #1 on the direct path.
  • the request message #1 may be a connection establishment request (link establishment request) message, or a connection modification request (link modification request) message.
  • the request message #1 may also include indication information #1 (as an example of the first indication), the indication information #1 is used to indicate that the data is jointly transmitted through the PDU session #1 and the PDU session #2, so that the PDU session #2 can be obtained. ID of #2 and the identity QFI-2 of QoS flow #2.
  • the remote UE sends a connection establishment request message to the relay UE to request the relay UE to establish QoS flow #2 and PDU session #2, and the connection establishment request message includes indication information #1
  • the relay UE can send the identifier of PDU session #2 and the identifier QFI-2 of QoS flow #2 to the remote UE through the indication information #1.
  • the remote UE sends a connection establishment request message to request the relay UE to establish QoS flow #2 and PDU session #2, and the relay UE completes the establishment of QoS flow #2 and PDU session #2 Afterwards, the remote UE sends a connection modification request message, and the connection modification request message includes indication information #1, and the relay UE can send the identifier of the PDU session #2 and the QoS flow #2 to the remote UE through the indication information #1 The logo QFI-2.
  • the indication information #1 may be associated QoS flow (paired QoS flow) indication information (also called L3 U2N relay multipath indication information).
  • QoS flow paired QoS flow
  • L3 U2N relay multipath indication information also called L3 U2N relay multipath indication information
  • the relay UE establishes or modifies PDU session #2 and QoS flow #2.
  • the relay UE sends a response message #1 to the remote UE through the indirect path.
  • the relay UE sends a response message #1 to the remote UE through the PC5 interface, and the response message #1 includes QFI-2, the ID of the PDU session #2, and the ID #1 of the relay UE (the first An example of identification), PC5 QoS rule and PC5 QoS parameters.
  • the response message #1 may be a link modification accept (link modification accept) message, or a connection establishment accept (link establishment accept) message.
  • the response message #1 when the remote UE sends the indication information #1 in the connection establishment request message, the response message #1 may be a connection establishment reception message; the remote UE sends the indication information #1 in the connection modification request message , the response message #1 may be a connection modification reception message.
  • 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 #6.
  • the relay UE sends the QFI-2, the ID of the PDU session #2 and the ID #1 of the relay UE to the remote UE according to the indication information #1.
  • the relay UE ID may be GUTI, SUCI or S-TMSI.
  • Case 2 The remote UE first establishes a non-direct path through the relay UE, which triggers the relay UE to establish PDU session #2 and QoS flow #2 on the non-direct path, and the remote UE then establishes a direct path. Establish PDU session #1 and QoS flow #1 on the path.
  • UPF2 on the non-direct path acts as an anchor point for communication between UPF#1 on the direct path and the server side.
  • the remote UE first establishes PDU session #2 and QoS flow #2 on the non-direct path through the relay UE, and the remote UE establishes PDU session #1 and QoS flow #1 on the direct path, specifically including Step S1420b1-step S1420b4, the specific steps are as follows:
  • the remote UE performs a discovery process of the relay UE.
  • the remote UE sends a discovery message.
  • the relay UE sends an announcement message according to the discovery message, and the announcement message may include indication information #2, where the indication information #2 is used to indicate that multiplex transmission is supported. That is, the relay UE supports simultaneous transmission with the remote UE on the direct path and the non-direct path. In other words, if the remote UE needs to perform multiple transmission, it can select a relay UE that supports multiple transmission.
  • the remote UE if the remote UE needs to perform multiplex transmission, the remote UE sends a request message #1, in which request message #1 supports multiplex transmission, and correspondingly, the response sent by the relay UE
  • the message may include indication information #2 indicating that multiplex transmission is supported.
  • the remote UE triggers the relay UE to establish PDU session #2 and QoS flow #2.
  • the remote UE sends a request message #1 to the relay UE through the PC5 interface.
  • the request message #1 is used for the relay UE to establish a QoS flow #2 and a PDU session #2 on the non-direct path.
  • the identification of the QoS flow #2 Can be QFI-2.
  • the request message #1 may include at least one of the identifier of the PC5 QoS flow, the PC5 QoS rule, and the destination address of the packet filter.
  • the remote UE indicates that the data transmitted by the PC5 QoS flow identified by the PC5 QoS flow to the relay UE can be multiplexed, or the IP data packet can match the data of the PC5 QoS rule and Packet filter Multiplexing can be performed.
  • the request message #1 also includes "request PC5 QoS rule” and "request PC5 QoS parameter”.
  • the remote UE establishes PDU session #1 and QoS flow #1 on the direct path.
  • the remote UE sends a request message #1' to AMF#1 (as an example of the first AMF) through the direct path, and the request message #1' is used to request SMF#1 to establish a QoS flow# on the direct path 1 and PDU session #1, the identifier of the QoS flow #1 may be QFI-1.
  • the request message #1' may include indication information #1, and the indication information #1 is used to indicate that the remote The terminal UE performs multiplex transmission through the QoS flow #1 and the QoS flow #2 at the same time.
  • the remote UE before sending the request message #1', can obtain the identifier of the PDU session #2 and the identifier QFI-2 of the QoS flow #2 from the relay UE, and ' includes the identifier of the PDU session #2 and the identifier QFI-2 of the QoS flow #2.
  • the remote UE can first establish the direct connection PDU session #1 and QoS flow #1, and then obtain the identifier of the PDU session #2 and the identifier QFI-2 of the QoS flow #2 from the relay UE for subsequent multiple Instruction of road transmission (step S1430).
  • the request message #1' may be a link modification request (link modification request) message, or a connection establishment request (link establishment request) message.
  • the indication information #1 may be associated QoS flow (paired QoS flow) indication information.
  • the remote UE can send request message #1' to AMF#1 through UL NAS message.
  • AMF#1 can send request message #1' to SMF#1 through N11 message, and this N11 message can be PDU session establishment context request (Nsmf_PDUsession_createSMcontext request) message etc.
  • Nsmf_PDUsession_createSMcontext request PDU session establishment context request
  • AMF#1 and SMF#1 are network devices serving remote UEs.
  • SMF#1 sends a response message #1' to the remote UE.
  • SMF#1 sends a response message #1' to the remote UE through AMF#1.
  • the remote UE receives the response message #1'.
  • the response message #1' is used to respond to the above request message #1'.
  • the response message #1' includes the identification information QFI-1 of the QoS flow #1 and the ID of the PDU session #1.
  • the response message #1' may also include QoS rule and QoS parameters.
  • 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.
  • the response message #1' may be a PDU session modification accept (PDU session modification accept) message.
  • SMF#1 may send the response message #1' to AMF#1 through an N11 message, and the N11 message may be a N1N2 message transfer (Namf_communication_N1N2MessageTransfer) message.
  • N11 message may be a N1N2 message transfer (Namf_communication_N1N2MessageTransfer) message.
  • the above steps realize the establishment process of the direct path and the non-direct path.
  • the following steps introduce the association of the direct path and the non-direct path and the method of creating the transmission channel between UPF#1 and UPF#2.
  • the remote UE can trigger the modification of PDU session #1 and QoS #1 through the direct connection path.
  • the remote UE can also trigger the relay UE to modify the modification of PDU session #2 and QoS #2
  • the method 1300 is described below by taking the remote UE triggering the modification of PDU session #1 and QoS #1 through the direct path as an example.
  • the remote UE sends a request message #2 to the AMF #1 through the direct path.
  • the remote UE carries information #1 (as an example of the first information) in the request message #2 (as an example of the first request message), and the first information may include the ID of QFI-2 and PDU session #2 , QFI-1, ID of PDU session #1, ID #1 of relay UE, indication information #3 (as an example of the third indication), indication information #1 (as an example of the first indication) and PDU session modification request (PDU session modification request).
  • the first information may include the ID of QFI-2 and PDU session #2 , QFI-1, ID of PDU session #1, ID #1 of relay UE, indication information #3 (as an example of the third indication), indication information #1 (as an example of the first indication) and PDU session modification request (PDU session modification request).
  • step S1420b3 the remote UE includes the indication information #1 in the sending request message #1' to instruct the remote UE to perform multiplex transmission through the QoS flow #1 and the QoS flow #2 at the same time, And if the request message #1' also includes the identifier of PDU session #2 and the identifier QFI-2 of QoS flow #2, then step S1430 may not be executed.
  • the indication information #3 is used to indicate that the anchor path is a direct path or a non-direct path, that is, UPF#1 of the direct path serves as the anchor UPF to communicate with the external application server, or the non-direct path
  • UPF#1 of the direct path serves as the anchor UPF to communicate with the external application server, or the non-direct path
  • the UPF#2 serves as the anchor UPF to communicate with the external application server.
  • indication information #3 may be an anchor path (anchor path) parameter.
  • the above-mentioned ID of QFI-1 and PDU session #1 can be included in the PDU session modification request, and the PDU session modification request can be directly encapsulated in the N1 SM container, invisible to AMF1, and directly transparently transmitted from AMF1 to SMF1.
  • the above-mentioned QFI-2, ID of PDU session #2, ID #1 of relay UE, indication information #3, indication information #1 and remote User ID parameters may include QFI-1, PDU session #1 ID's PDU Session Modification Request is included in parallel in Request Message #2.
  • the above QFI-1, ID of PDU session #1, QFI-2, ID of PDU session #2, ID #1 of relay UE, indication information #3, indication information #1 and remote User ID parameters can be It is included in the request message #2 in parallel with the PDU session modification request including QFI-1 and the ID of the PDU session #1.
  • the request message #2 may be a NAS message.
  • the transmission channel between UPF#1 and UPF#2 can be established in various ways, for example, the method for establishing the transmission channel between UPF#1 and UPF#2 is shown in Figure 15(a) below 1.
  • Figure 15(b) below shows Method 2 for establishing a transmission channel between UPF#1 and UPF#2, where Method 1 includes Step S1440-Step S1447, and Method 2 includes Step S1450a-Step S1470b.
  • the specific method is as follows.
  • AMF#1 obtains the address of SMF#2 according to the request message #2.
  • AMF#1 (an example of the first AMF) obtains the address information of the corresponding SMF#2 (an example of the second SMF) according to the ID of the relay UE in the request message #2.
  • AMF#1 sends the ID#1 of the relay UE (for example, the SUCI of the relay UE) to the AUSF, obtains the SUPI (Subscription Permanent Identifier) sent by the AUSF, and then AMF#1 sends the SUPI to the UDM , PDU session ID, get the SMF address sent by UDM.
  • the ID#1 of the relay UE for example, the SUCI of the relay UE
  • SUPI Subscribescription Permanent Identifier
  • AMF#1 calls Nausf_UEAuthentication_authenticate provided by AUSF to obtain the SUPI (Subscription Permanent Identifier) of the relay UE, and then calls the Nudm_UECM_Get service provided by UDM to obtain the address information of the SMF serving the PDU session #2 of the relay UE.
  • SUPI Subscriber Identifier
  • Nudm_UECM_Get service provided by UDM to obtain the address information of the SMF serving the PDU session #2 of the relay UE.
  • AMF-1 determines the AMF (AMF#2) serving the relay UE according to the ID of the relay UE (for example, the GUTI of the relay UE), and then calls the Namf_Communication_UEContextTransfer service from AMF# 2 Obtain the address information (SMF#2) of the SMF serving the PDU session #2 of the relay UE.
  • AMF#1 can also obtain the address of UPF#2 (an example of the second UPF), and the address of UPF#2 is used for SMF#1 to determine whether the UPF#2 is the same as UPF#1 .
  • AMF#1 obtains the address of UPF#2 from SMF#2.
  • AMF#1 sends request message #3 to SMF#1.
  • the request message #3 includes the address information of SMF#2, QFI-1, the ID of PDU session #1, QFI-2, the ID of PDU session #2, and the ID #2 of the relay UE (the first ID of the relay device) An example of two identifiers), indication information #3, indication information #1, and a PDU session modification request.
  • the ID#2 of the relay UE is determined by the AMF#1 according to the ID#1 of the relay UE.
  • request message #3 may also include the address of UPF #2.
  • SMF#1 determines whether UPF#2 is the same as UPF#1 according to the address of UPF#2.
  • downlink data transmission can be performed directly according to method 800(b).
  • SMF#1 may instruct data to perform multiplex transmission, for example, perform downlink data transmission according to method 800(a) for performing multiplex transmission transmission.
  • AMF#1 may send a request message #3 to SMF#1 through an N11 message, and the N11 message may be a (Namf_PDUSession_UpdateSMContext request) message.
  • SMF#1 sends request message #4 to UPF#1.
  • request message #4 includes QFI-2, ID of PDU session #2, ID #2 of relay UE, indication information #3, indication information #1 and PDU session modification request.
  • the request message #4 is used to instruct UPF #1 (an example of the first UPF) to create a transmission channel with UPF #2, and the transmission channel is used to transmit data suitable for multiplexing.
  • SMF#1 instructs UPF#1 to allocate channel information #1 (an example of first channel information) of a transmission channel, and the channel information #1 is used for UPF#2 to send data suitable for multiplex transmission to UPF#1.
  • channel information #1 an example of first channel information
  • channel information #1 may be a channel (tunnel) ID, for example, the tunnel ID may be a full qualified tunnel endpoint ID (full qualified tunnel endpoint ID, F-TEID).
  • SMF#1 determines rule information applicable to UPF#1 for multiplex transmission, and according to the rules, UPF#1 can determine which data is suitable for multiplex transmission.
  • SMF#1 generates the first rule and the second rule according to QFI-1, the ID of PDU session #1, QFI-2, the ID of PDU session #2, and the ID #2 of the relay UE.
  • UPF#1 is the anchor UPF
  • SMF#1 sends the first rule to UPF#1
  • the first rule is used to instruct UPF#1 to send part or all of the data to UPF#2, so that UPF#2 passes the second
  • a communication path transmits data received from said first UPF to a remote UE.
  • UPF#1 is an anchor UPF
  • SMF#1 sends a second rule to UPF#1, and the second rule is used to instruct UPF#1 to send the data received from UPF#2 to the application server.
  • UPF#2 is an anchor UPF
  • SMF#1 sends a first rule to the UPF#1, and the first rule is used to instruct UPF#1 to send to UPF#2 the first data received from the remote UE;
  • UPF#2 is an anchor UPF
  • SMF#1 sends a second rule to the UPF#1, where the second rule is used to instruct UPF#1 to send the data received from UPF#2 to the remote UE.
  • SMF#1 instructs UPF#1 to transmit the determined data suitable for multiplex transmission to the remote UE through the direct path, and pass The transmission channel between UPF#1 and UPF#2 is sent to UPF#2, and UPF#2 sends it to the remote UE through a non-direct path; for uplink data, SMF#1 instructs UPF#1 to transmit data from the transmission channel The received data (data from UPF#2 on the non-direct path) and the data received from the direct path are sent to the Internet network; if the indication information #3 indicates that the anchor path is a non-direct path, for For uplink data, SMF#1 instructs UPF#1 to send the determined data suitable for multiplex transmission (remote UE data received through the direct connection path) to UPF#2 through the transmission channel, and UPF#2 sends the data The remote UE data received from the non-direct path is sent to the internet network; for downlink data, SMF#1 instructs UPF#1 to transmit the determined data suitable for multiplex transmission to the remote UE
  • the request message #3 further includes the indication information #1 and the indication information #5 (an example of the second indication), and the indication information #5 is used to describe the first data.
  • the transmission granularity can be Indicates that the granularity defined by message #5 is multiplexed.
  • the indication information #5 can be limited to the service data flow as the granularity, such as the granularity of Service data flow (SDF), and it can also be understood that the indication information #5 further describes the data types that need to be multiplexed in the first data, For example, the type may be the business type of the data.
  • the remote UE transmits data of multiple applications in the same QoS flow at the same time, but the remote UE may only need to multiplex the data of one or part of the applications.
  • the remote UE can include the first QoS rule in the request message #2, the first QoS rule identifies the data of a specific application that needs to be multiplexed, and the first QoS rule is used for SMF#1 Indicates to UPF#1 that data for this particular application needs to be multiplexed.
  • the remote UE can indicate the first PC5 QoS rule to the relay UE when obtaining the identifier of the PDU session #2 and the identifier QFI-2 of the QoS flow #2 from the relay UE.
  • the first PC5 The QoS rule identifies application data that needs to be multiplexed.
  • the relay UE sends the first UU QoS flow to SMF#2 according to the first PC5 QoSrule, and SMF#2 instructs the first PDR corresponding to UPF#2 according to the first UU QoS flow, specifically indicating that the data corresponding to the PDR can only be transmitted to UPF#1, otherwise it needs to be directly transmitted to the network through UPF#2.
  • the request message #4 may be an N4 session modification request (N4 session modification request) message.
  • SMF#1 receives response message #2 from UPF#1.
  • the response message #2 includes tunnel information #1 (tunnel info-1).
  • the response message #2 may be an N4 session modification response (N4 session modification response) message.
  • SMF#1 sends request message #5 to SMF#2.
  • SMF#1 sends request message #5 to SMF#2 according to the address of SMF#2.
  • the request message #5 includes channel information #1 (tunnel info-1), QFI-1, QFI-2, ID of PDU session #2, ID of PDU session #2, ID #2 of relay UE, indication information #3. Instruction information #1 and PDU session modification request (PDU session modification request).
  • SMF#1 may send a request message #5 to SMF#2 through an N11 message, and the N11 message may be a (Namf_PDUSession_UpdateSMContext request) message.
  • SMF#2 sends request message #6 to UPF#2.
  • request message #6 includes (tunnel info-1), QFI-1, QFI-2, ID of PDU session #2, ID #2 of relay UE, indication information #3, indication information #1 and PDU session modification Request (PDU session modification request).
  • the request message #6 is used to instruct UPF #2 to create a transmission channel with UPF #1, and the transmission channel is used to transmit data suitable for multiplex transmission.
  • SMF#2 instructs UPF#2 to allocate channel information #2 of the transmission channel, and the channel information #2 is used for UPF#1 to send data suitable for multiplex transmission to UPF#2.
  • channel information #2 may be a channel (tunnel) ID, for example, the tunnel ID may be a full qualified tunnel endpoint ID (full qualified tunnel endpoint ID, F-TEID).
  • SMF#2 instructs UPF#2 to determine the rule information applicable to multiplexed data, and according to this rule, UPF#2 can determine the data applicable to multiplexed transmission.
  • SMF#2 generates the third rule and the fourth rule according to the QFI-2 received from SMF#1, the ID of PDU session #2, the ID#2 of the relay UE, and the ID of the remote UE .
  • SMF#2 generates the third rule and the fourth rule according to the QFI-2 received from SMF#1, the ID of PDU session #2, and the ID#2 of the relay UE.
  • UPF#1 is the anchor UPF
  • SMF#2 sends the third rule to UPF#2
  • the third rule is used to instruct UPF#2 to send data received from the remote UE to UPF#1;
  • UPF#1 is the anchor UPF
  • SMF#2 sends a fourth rule to UPF#2, where the fourth rule is used to instruct UPF#2 to send data received from UPF#1 to the remote UE.
  • UPF#2 is an anchor UPF
  • SMF#2 sends a third rule to the UPF#2, where the third rule is used to instruct the UPF#2 to send part or all of the first data to UPF#1, causing the first UPF#1 to send the data received from UPF#2 to the remote UE through the first communication path; or
  • UPF#2 is an anchor UPF
  • SMF#2 sends a fourth rule to UPF#2, where the fourth rule is used to instruct UPF#2 to send the data received from UPF#1 to the application server.
  • SMF#2 instructs UPF#2 to send the determined data suitable for multiplex transmission to UPF#1 through the transmission channel
  • SMF#2 instructs UPF#2 to send the data received from the transmission channel (data from UPF#1) to the Internet network
  • the instruction information #3 indicates that the anchor path is a direct path, for the uplink
  • SMF#2 instructs UPF#2 to send the determined data suitable for multiplex transmission (UE data received through QoS flow#2) to UPF#1 through the transmission channel.
  • SMF#2 instructs UPF The data received by #2 from the transmission channel (data from UPF#1) is sent to the UE through the indirect path QoS flow #2.
  • the request message #6 may be an N4 session modification request (N4 session modification request) message.
  • SMF#2 receives response message #3 from UPF#2.
  • the response message #3 includes tunnel information #2 (tunnel info-2).
  • the response message #3 may be an N4 session modification response (N4 session modification response) message.
  • SMF#1 receives response message #4 from SMF#2.
  • the response message #4 includes tunnel information #2 (tunnel info-2).
  • SMF#2 may send a response message #4 to SMF#1 through an N11 message, and the N11 message may be a (Namf_PDUSession_UpdateSMContext response) message.
  • SMF#1 sends request message #7 to UPF#1.
  • the request message #7 includes tunnel information #2 (tunnel info-2).
  • the request message #7 may be an N4 session modification request (N4 session modification request) message.
  • UPF#1 sends a response message #5 to SMF#1.
  • step S1451-step S1457 is a process in which SMF#1 and SMF#2 instruct UPF#1 and UPF#2 to establish a channel and exchange channel information.
  • UPF#1 passes the tunnel info allocated by UPF#2 -2 sends data to UPF#2, and UPF#2 sends data to UPF#1 through the tunnel info-1 allocated by UPF#1.
  • AMF#1 After AMF#1 receives the request message #2 from the remote UE, AMF#1 can simultaneously request AMF#2 and SMF#1 to execute the modification procedures of PDU session #2 and PDU session #1 respectively, and at the same time request to create UPF# The transmission channel between 1 and UPF#2.
  • AMF#1 sends a request message #8 to AMF#2.
  • AMF#1 determines the address of AMF#2 serving the relay UE according to ID#2 of the relay UE included in the request message #2, and further, sends a request message #8 to AMF#2.
  • the request message #8 includes QFI-2, the ID of the PDU session #2, the ID #2 of the relay UE, the indication information #3, the indication information #1, and the modification request of the PDU session #2 (PDU session modification request).
  • request message #8 may also include the address of UPF #2.
  • AMF#1 may send a request message #8 to AMF#2 through an N11 message, and the N11 message may be a (Namf_communication_UEContextTransfer request) message.
  • AMF#2 sends a request message #9 to SMF#2.
  • the request message #9 includes QFI-2, the ID of the PDU session #2, the ID #2 of the relay UE, the indication information #3, the indication information #1, and the modification request of the PDU session #2 (PDU session modification request).
  • request message #9 may also include the address of UPF #2.
  • AMF#1 may send a request message #9 to AMF#2 through an N11 message, and the N11 message may be a (Namf_communication_UEContextTransfer request) message.
  • SMF#2 sends request message #10 to UPF#2.
  • the request message #10 includes QFI-2, the ID of the PDU session #2, the ID #2 of the relay UE, the indication information #3, the indication information #1 and the PDU session #2 modification request (PDU session modification request).
  • the request message #10 is used to instruct UPF #2 to create a transmission channel with UPF #1, and the transmission channel is used to transmit data suitable for multiplex transmission.
  • SMF#2 instructs UPF#2 to determine the rule information applicable to the multiplexed data, and according to this rule, UPF#2 can determine which data is applicable to the multiplexed transmission.
  • step S1444a which will not be repeated here.
  • SMF#2 instructs UPF#2 to allocate channel information #2 of the transmission channel, and the channel information #2 is used for UPF#1 to send data suitable for multiplex transmission to UPF#2.
  • channel information #2 may be a channel (tunnel) ID, for example, the tunnel ID may be a full qualified tunnel endpoint ID (full qualified tunnel endpoint ID, F-TEID).
  • the request message #10 may be an N4 session modification request (N4 session modification request) message.
  • SMF#2 receives response message #6 from UPF#2.
  • the response message #6 includes tunnel information #2 (tunnel info-2).
  • the response message #6 may be an N4 session modification response (N4 session modification response) message.
  • SMF#2 sends a response message #7 to AMF#1 through AMF#2.
  • the response message #7 includes tunnel information #2 (tunnel info-2).
  • the response message #7 may be an N4 session modification response (N4 session modification response) message.
  • step S1450a-step S1454a is the modification process of PDU session #2 and the creation process of channel information #2.
  • AMF#1 sends request message #11 to SMF#1.
  • the request message #11 includes QFI-1, ID of PDU session #1, QFI-2, ID of PDU session #2, ID #2 of relay UE, indication information #3, indication information #1 and PDU session #1 modification request (PDU session modification request).
  • the request message #11 may also include the address of UPF #2.
  • SMF#1 determines whether UPF#2 is the same as UPF#1 according to the address of UPF#2.
  • downlink data transmission can be performed directly according to method 800(b).
  • SMF#1 may instruct data to perform multiplex transmission, for example, perform downlink data transmission according to method 800(a) for performing multiplex transmission transmission.
  • AMF#1 may send a request message #11 to SMF#1 through an N11 message, and the N11 message may be a (Namf_PDUSession_UpdateSMContext request) message.
  • SMF#1 sends request message #14 to UPF#1.
  • the request message #14 includes QFI-2, the ID of the PDU session #2, the ID #2 of the relay UE, the indication information #3, the indication information #1 and the modification request of the PDU session #1 (PDU session modification request).
  • the request message #14 is used to instruct UPF #2 to create a transmission channel with UPF #1, and the transmission channel is used to transmit data suitable for multiplex transmission.
  • SMF#1 instructs UPF#1 to determine rule information applicable to multiplexed data, and according to the rule, UPF#1 can determine which data is applicable to multiplexed transmission.
  • step S1442a which will not be repeated here.
  • SMF#1 instructs UPF#1 to allocate channel information #1 of a transmission channel, and the channel information #1 is used for UPF#2 to send data suitable for multiplex transmission to UPF#1.
  • channel information #1 may be a channel (tunnel) ID, for example, the tunnel ID may be a full qualified tunnel endpoint ID (full qualified tunnel endpoint ID, F-TEID).
  • the request message #14 may be an N4 session modification request (N4 session modification request) message.
  • SMF#1 receives response message #8 from UPF#1.
  • the response message #8 includes tunnel information #1 (tunnel info-1).
  • the response message #8 may be an N4 session modification response (N4 session modification response) message.
  • SMF#1 sends a response message #9 to AMF#1.
  • the response message #9 includes tunnel information #1 (tunnel info-1).
  • the response message #9 may be an N4 session modification response (N4 session modification response) message.
  • step S1450b-step S1453b is the modification process of PDU session #1 and the creation process of channel information #1.
  • AMF#1 and AMF#2 exchange tunnel information #1 (tunnel info-1) and tunnel information #2 (tunnel info-2).
  • AMF#1 sends channel information #2 to UPF#1 through SMF#1.
  • AMF#2 sends channel information #1 to UPF#2 through SMF#2.
  • step S1450a-step S1454a and step S1450b-step S1453b may be executed simultaneously.
  • step S1470a and step S1470b can be executed at the same time.
  • modification process of the PDU session and the creation process of the channel information in method 1000 and method 1100 are also applicable to the method 1400, which is not limited in this embodiment of the present application.
  • the remote UE notifies the relay UE to start multiplex transmission.
  • the remote UE generates an uplink IP data packet #1 based on the IP address and port number of the direct link and sends an uplink transmission on the direct link;
  • the remote UE Based on the IP data packet generated on the direct link, the remote UE generates the uplink data packet #2 sent on the non-direct link based on the IP address and port number of the non-direct link, that is, there are two layers of IP headers , and send the data packet #2 with the two-layer IP header on the indirect link for uplink transmission.
  • UPF#1 receives data packet #2 from UPF#2, removes a layer of IP packet header and performs IP packet sorting together with data packet #1 received from the direct link, deduplicates and other operations, and then transmits it to the application server.
  • the relay UE may serve multiple remote UEs, so the QoS flow #2 established or modified by the relay UE may transmit the data of multiple remote UEs, so for the anchor UPF, it is indistinguishable Which remote UE the data transmitted through the same QoS flow belongs to.
  • the relay UE can allocate or establish a dedicated QoS flow for transmitting the data that the remote UE needs to perform multiplex transmission.
  • SMF#2 on the non-direct path can use the dedicated QoS flow according to the dedicated QoS flow configures identification rules to UPF#2. This identification rule is used for UPF#2 to determine that the data corresponding to the dedicated QoS flow needs to be multiplexed.
  • the QoS flow #2 can be a dedicated QoS flow allocated or established by the relay UE, which only transmits the data of the remote UE.
  • UPF #2 for uplink data, from the QoS flow # 2
  • the transmitted data can be transmitted through the transmission channel.
  • UPF#2 can send the data received from this dedicated QoS flow to UPF-1, while the data received from other QoS flows can be sent directly through the N6 interface to the Internet.
  • the remote UE may send remote UE identity (remote User ID) information to AMF#1.
  • remote UE identity (remote User ID) User ID) information is used by SMF#2 to determine the IP address and/or TDP/UDP of the remote UE on the indirect path.
  • UPF#2 can determine the uplink data for multiplex transmission according to the IP address and/or TDP/UDP of the remote UE; when UPF#2 is the anchor UPF, SMF#2 can instruct UPF#2 according to the remote
  • the IP address and/or TDP/UDP of the terminal UE determine the downlink data transmitted to UPF#1, that is, for UPF#2, the downlink data includes the data of multiple remote UEs, according to the IP address indicated by SMF#2
  • the address and/or TDP/UDP can determine the data of the remote UE that needs to be multiplexed, that is, UPF#2 sends the data of the remote UE corresponding to the IP address indicated by SMF#2 and/or TDP/UDP
  • To UPF#1 is sent through the direct path and at the same time through the non-direct path, and the rest of the data can only be sent through the non-direct path, in other words, the rest of the data does not need to be multiplexed.
  • the remote UE can send the remote UE identity (remote User ID) information to the AMF#1 through the request message #2.
  • the relay UE sets identification information #a for the data to be multiplexed, and the identification information #a is used by UPF #2 to determine the QoS flow for multiplexed transmission.
  • the relay UE may obtain the QoS rule #x for multiplex transmission from the remote UE.
  • the QoS rule #x is used by the SMF#2 to determine the QoS flow for the remote UE to multiplex, thereby instructing the UPF#2 to determine the uplink multiplex transmission of the data of the QoS flow.
  • UPF#1 sends data packet #1 to UPF#2, and UPF#2 adds another layer of IP packet header based on the IP address and port number of the relay UE to generate downlink data packet #2, which is sent to Remote UE; or, UPF#1 adds another layer of IP packet header to data packet #1 based on the IP address and port number of the relay UE to generate data packet #2, and then sends it to UPF#2. sent to the remote UE.
  • UPF#1 obtains the IP address and port number of the relay UE from UPF#2.
  • UPF#2 transmits CN Tunnel Info-2 to UPF#1 in method 1400.
  • UPF#1 obtains the IP address and port number of the relay UE from UPF#2.
  • the specific method can refer to the method of obtaining PDR in steps S1070-1091 in method 1000 in FIG. 10.
  • UPF#1 obtains the non-direct connection The PDR corresponding to the QoS flow #2 of the path, according to which the IP address and port number of the relay UE can be determined.
  • the remote UE can choose a path from the direct path and the non-direct path to receive the downlink data packet. For example, the remote UE can receive the data packet #1 on the direct path and perform IP packet sorting, deduplication and other operations. Pass it to the application layer. In this case, the downlink data packet #2 on the non-direct path is discarded by default; as another example, the remote UE can receive the data packet #2 on the non-direct path, and perform IP Packet sorting, deduplication and other operations are passed to the application layer. In this case, the downlink data packet #1 on the direct connection path is discarded by default.
  • the above-mentioned scheme b2 when the remote UE determines that the multi-channel transmission is specifically used for reliability transmission, the above-mentioned scheme b2 may be implemented, and when the remote UE determines that the multiple-channel transmission is specifically used for load balancing transmission, the above-mentioned scheme b1 may be implemented.
  • the remote UE generates an uplink IP data packet #3 based on the IP address and port number of the non-direct link and sends an uplink transmission on the non-direct link;
  • the remote UE Based on the IP data packet #3 generated on the non-direct link, the remote UE generates the uplink data packet #4 sent on the direct link based on the IP address and port number of the direct link, that is, there are two layers of IP packet header, and send the data packet #4 with two layers of IP headers on the direct link for uplink transmission.
  • UPF#2 receives data packet #4 from UPF#1, removes a layer of IP packet header and performs IP packet sorting together with data packet #3 received from the non-direct link, deduplicates and other operations, and then transmits it to the application server .
  • the relay UE when the relay UE receives the IP data packet #3 from the remote UE, it can add identification information #a, and the identification information #a is used for UPF #2 to determine the QoS flow for multiplex transmission , so as to perform operations such as IP de-reordering on the data together with the data packet #4 received from UPF#1.
  • UPF#2 sends data packet #3 to UPF#1, and UPF#1 generates downlink data packet #4 based on the IP address and port number of the direct connection path, and sends it to the remote UE on the direct connection link; or, UPF #2 adds another layer of IP header to data packet #3 based on the IP address and port number of the direct connection path to generate data packet #4, then sends it to UPF#1, and sends it to the remote UE on the direct connection link.
  • the downlink data packet #4 received by the remote UE from the direct connection path removes a layer of IP packet header and the data packet #3 received from the non-direct connection path performs IP packet sorting, deduplication and other operations to the application layer transfer.
  • UPF#2 obtains the IP address and port number of the direct connection path from UPF#1.
  • UPF#1 transferring CN Tunnel Info-1 to UPF#2 in method 1400.
  • UPF#2 obtains the IP address and port number of the relay UE from UPF#1.
  • UPF#1 For a specific method, refer to the method of obtaining the PDR corresponding to QFI1 in steps S1160-1180 in method 1100 in FIG. 10 .
  • the remote UE For the downlink data packet #4 received by the remote UE from the direct link, after removing a layer of IP packet header and the data packet #3 received from the non-direct link, perform IP packet sorting, deduplication and other operations passed to the application layer.
  • UPF#1 on the direct path of the remote UE can establish a transmission channel with UPF#2 on the non-direct path, so that the remote UE can transmit the direct path through the direct path and the non-direct path Part or all of the data of QoS flow #1, or part or all of the data of QoS flow #2 through non-direct paths, to achieve data redundancy transmission or load balancing transmission or switching transmission.
  • module may be a combination of software and/or hardware that realizes a predetermined function.
  • devices described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.
  • FIG. 16 shows a schematic diagram of an apparatus 1600 for data transmission provided by an embodiment of the present application.
  • the device 1600 includes a transceiver unit 1610, which can be used to implement corresponding communication functions, and the transceiver unit 16210 can also be called a communication interface or a communication unit.
  • the apparatus 1600 may further include a processing unit 1620, and the processing unit 1620 may be used for data processing.
  • the device 1600 further includes a storage unit, which can be used to store instructions and/or data, and the processing unit 1620 can read the instructions and/or data in the storage unit, so that the device implements the foregoing method embodiments actions of different devices.
  • a storage unit which can be used to store instructions and/or data
  • the processing unit 1620 can read the instructions and/or data in the storage unit, so that the device implements the foregoing method embodiments actions of different devices.
  • the apparatus 1600 is configured to perform the actions performed by the first terminal device (remote UE) in each method embodiment above.
  • the transceiver unit 1610 is configured to obtain first information, where the first information includes the identifier of the first session of the first communication path, the identifier of the second session of the second communication path, and the relay The first identifier of the device; the transceiving unit 1610 is further configured to send a first request message including the first information to the first mobility management entity, where the first request message is used to request to pass the first session and The second session jointly transmits the first data.
  • the apparatus 1600 is used to perform the actions performed by the relay device (relay UE) in each method embodiment above.
  • the transceiver unit 1610 is configured to obtain third information, where the third information includes the identifier of the first session of the first communication path, the identifier of the second session of the second communication path, and the first The first identifier of the terminal device; the transceiving unit 1610 is further configured for the relay device to send a second request message including the third information to a second mobility management function entity, where the second request message is used to request The first data is jointly transmitted through the first session and the second session.
  • the apparatus 1600 is configured to perform the actions performed by the core network device in each method embodiment above.
  • the transceiver unit 1610 is configured to receive a first request message from the first terminal device, where the first request message is used to request the first session through the first communication path and the session of the second communication path
  • the second session jointly transmits the first data
  • the first request message includes first information
  • the first information includes an identifier of the first session, an identifier of the second session, and the first information of the relay device.
  • the transceiver unit 1610 is further configured to transmit the first data to the first user plane functional entity and the second user plane functional entity, where the first user plane functional entity serves The first communication path, the second user plane functional entity serving the second communication path; wherein, one of the first user plane functional entity and the second user plane functional entity and an application server transmit the first data between.
  • the apparatus 1600 is configured to perform the actions performed by the relay device in each method embodiment above.
  • the transceiver unit 1610 is configured to receive a second request message from the relay device, where the second request message is used to request the first session through the first communication path and the second session of the second communication path.
  • the two sessions jointly transmit the first data
  • the second request message includes third information
  • the third information includes an identifier of the first session, an identifier of the second session, and a first identification
  • the transceiver unit 1610 is further configured to transmit the first data between the first user plane functional entity and the second user plane functional entity, and the first user plane functional entity serves On the first communication path, the second user plane functional entity serves the second communication path, wherein one of the first user plane functional entity and the second user plane functional entity communicates with an application server transmit the first data between.
  • the apparatus 1600 can implement the steps or processes corresponding to the execution of the terminal equipment or the core network equipment in the method embodiment according to the embodiment of the present application, and the apparatus 1600 can include an The unit of the method executed by the first terminal device (remote EU) or core network device (first AMF, second AMF, first SMF, second SMF, first UPF, second UPF) in the device.
  • first terminal device remote EU
  • core network device first AMF, second AMF, first SMF, second SMF, first UPF, second UPF
  • the apparatus 1600 is configured to perform the actions performed by the terminal device in each method embodiment above.
  • the processing unit 1620 is configured to obtain first information, the first information is used by the first network device to transmit the first data to the first terminal device through the first communication path, and the first information includes The first packet detection rule PDR; the transceiver unit 1610, configured to send a first message to a second network device through a second communication path, the first message includes the first information and first indication information, and the first indication The information is used to indicate that the first data is transmitted through the first communication path and/or the second communication path.
  • the transceiver unit 1610 is further configured to send a first request message to the second terminal device, where the first request message is used to request establishment of a first QoS flow on the first communication path, and the first request The message includes second indication information, where the second indication information is used to acquire the first information; the first terminal device receives the first information from the second terminal device.
  • the first information is obtained by the first terminal device when establishing the first QoS flow on the first communication path.
  • the first information further includes first QoS flow information on the first communication path, and the first QoS flow information includes the identifier of the second terminal device, the identifier QFI of the first QoS flow, the The identifier of the PDU session corresponding to the first QoS flow.
  • the first information further includes third indication information, where the third indication information is used to indicate reliable transmission or load balancing transmission.
  • the above-mentioned first communication path is a communication path through which the first terminal device connects to the first network device through the second terminal device, or, the first communication path is a direct connection between the first terminal device and the first network device.
  • 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 apparatus 1600 can implement the steps or processes corresponding to the execution of the terminal device in the method embodiment according to the embodiment of the present application, and the apparatus 1600 can include the method for executing the method executed by the first terminal device in the embodiment shown in FIG. 5 unit, or a unit including the method executed by the remote UE in the embodiments shown in FIG. 7 , FIG. 9 , FIG. 10 and FIG. 11 .
  • the apparatus 1600 is configured to perform the actions performed by the first network device in each method embodiment above.
  • the transceiver unit 1610 is configured to receive first information and second information, the first information is used by the first network device to transmit data to the first terminal device through the first communication path, and the second information is used For the first network device to transmit data to the first terminal device through the second communication path; and for receiving the first data, to the first terminal device through the first communication path and/or the second communication path The device sends the first data.
  • the processing unit 1620 is configured to determine a destination address and a source address according to the first information; the first network device processes the first data according to the destination address and source address, and sends the processed Describe the first data.
  • the first communication path is a communication path for the first terminal device to receive data sent by the first network device through the second terminal device.
  • the transceiving unit 1610 is further configured to receive third indication information, where the third indication information is used to indicate reliable transmission or load balancing transmission.
  • the processing unit 1620 when the third indication information indicates reliable transmission, the processing unit 1620 is configured to copy the IP packet of the first data, and the transceiver unit 1610 is configured to pass through the first communication path and the second communication path respectively.
  • the second communication path sends the IP packet of the first data to the first terminal device; or, when the second indication information indicates load balancing transmission, the processing unit 1620 is configured to split the IP packet of the first data
  • the transceiving unit 1610 is configured to send the IP packet of the first data to the first terminal device through the first communication path and the second communication path respectively.
  • the processing unit 1620 is further configured to determine, according to 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, according to The first information and the second information determine to send the first data to the first terminal device through the first communication path and/or the second communication path.
  • the transceiving unit 1610 is further configured to send the first data to a third network device, and the third network device sends the data to the first terminal device through the first communication path.
  • 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
  • the first QoS flow is one of the at least one QoS flow.
  • the transceiver unit 1610 is further configured to receive the identifier QFI of the first QoS flow, and send the first data to the third network device, and the transceiver unit 1610 is specifically configured to encapsulate the first data into a GTP message, through The first channel sends the GTP message to the third network device, the GTP message includes the identifier QFI of the first QoS flow, and the first channel is used for the first network device and the third network device Network equipment for data transmission.
  • the apparatus 1600 can implement the steps or processes corresponding to the execution of the first network device in the method embodiment according to the embodiment of the present application, and the apparatus 1600 can include a method for executing the execution of the first network device in the embodiment shown in FIG. 5
  • FIG. 17 shows a schematic diagram of a data transmission device 1700 provided by an embodiment of the present application.
  • the device 1700 includes a processor 1710, the processor 1710 is coupled with a memory 1720, the memory 1720 is used for storing computer programs or instructions and/or data, and the processor 1710 is used for executing the computer programs or instructions stored in the memory 1720, or reading the memory 1720 The stored data is used to execute the methods in the above method embodiments.
  • the device 1700 further includes a transceiver 1730 for receiving and/or sending signals.
  • the processor 1710 is configured to control the transceiver 1730 to receive and/or send signals.
  • processors 1710 there are one or more processors 1710 .
  • the memory 1720 is integrated with the processor 1710, or is set separately.
  • the apparatus 1700 is used to implement the operations performed by the first terminal device, the second terminal device, the first network device, or the second network device in each of the above method embodiments.
  • the processor 1710 is configured to execute the computer programs or instructions stored in the memory 1720, so as to implement related operations of the network device in each method embodiment above.
  • the processor 1710 is configured to execute the computer program or instruction stored in the memory 1720, so as to implement related operations of the terminal device in each of the above method embodiments.
  • processors mentioned in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general-purpose processors, digital signal processors (digital signal processors, DSPs), application-specific integrated circuits ( application specific integrated circuit (ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the memory mentioned in the embodiments of the present application may be a volatile memory and/or a nonvolatile memory.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM).
  • RAM random access memory
  • RAM can be used as an external cache.
  • RAM includes the following multiple forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), Double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and direct Memory bus random access memory (direct rambus RAM, DR RAM).
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components
  • the memory storage module may be integrated in the processor.
  • memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • the present application also provides a computer-readable medium on which a computer program is stored, and when the computer program is executed by a computer, the functions of any one of the above method embodiments are realized.
  • the present application also provides a computer program product, which implements the functions of any one of the above method embodiments when executed by a computer.
  • the present application also provides a system, which includes the aforementioned first access network device, second access network device, access and mobility management functional device, and first session management functional device.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请实施例提供了一种数据传输的方法和通信装置，该方法包括：第一终端设备获取第一信息，所述第一信息包括所述第一通信路径的第一会话的标识、所述第二通信路径的第二会话的标识以及所述中继设备的第一标识；所述第一终端设备向第一移动性管理实体发送包括所述第一信息的第一请求消息，所述第一请求消息用于请求通过所述第一会话和所述第二会话共同传输第一数据。在该方法中，能够实现在直连路径和非直连路径共同进行数据的传输，使得远端终端设备和数据网络之间的传输路径具有多样性，可以动态地满足业务需求。

Description

一种数据传输的方法和通信装置
本申请要求于2021年12月6日提交国家知识产权局、申请号为202111476011.3、申请名称为“一种数据传输的方法”的中国专利申请和2022年2月25日提交国家知识产权局、申请号为202210180880.X、申请名称为“一种数据传输的方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种数据传输的方法和通信装置。
背景技术
远端(remote)用户设备(user equipment，UE)可以通过两种路径与数据网络(data network，DN)通信。一种是基于Uu接口进行通信，即远端UE直接接入运营商网络(例如，基站)，通过运营商网络与DN通信，这种路径可以称为直接路径(direct path)；另一种是基于邻近服务通信5(proximity-based services communication 5，PC5)接口进行通信，即远端UE通过中继(relay)接入运营商网络，再通过运营商网络与DN通信，这中路径可以称为间接路径(indirect path)。
现有技术中，远端UE使用单一路径(直接路径或间接路径)进行数据传输，无法动态地满足业务的传输需求，例如，时延或质量等。
因此亟需一种数据传输方法，通过两条路径来进行数据传输，满足用户业务的传输需求。
发明内容
本申请实施例提供一种数据传输的方法和通信装置，能够指示服务质量QoS流的路径，使得远端终端设备和数据网络之间的传输路径具有多样性，可以动态地满足业务需求。
第一方面，提供了一种数据传输的方法，该方法可以由终端设备执行，或者，也可以由配置于终端设备中的芯片或电路执行，本申请对此不作限定。以下以第一终端设备执行为例进行说明。
该方法包括：所述第一终端设备获取第一信息，所述第一信息包括所述第一通信路径的第一会话的标识、所述第二通信路径的第二会话的标识以及所述中继设备的第一标识；所述第一终端设备向第一移动性管理实体发送包括所述第一信息的第一请求消息，所述第一请求消息用于请求通过所述第一会话和所述第二会话共同传输第一数据。
根据上述技术方案，第一终端设备可以获取直连路径的第一会话的标识，也可以从中继设备获取非直连路径的第二会话的标识和中继设备的标识，根据该直连路径的第一会话的标识，也可以从中继设备获取非直连路径的第二会话的标识和中继设备的标识可以在直连路径上向第一移动性管理实体发起请求，请求通过第一会话和所述第二会话共同传输第一数据，从而可以实现在直连路径上和非直连路径上共同传输数据。
直连路径的第一UPF可以和非直连路径的第二UPF建立传输通道，使得第一终端设备可以通过该直连路径和非直连路径传输直连路径的第一QoS流的部分或全部数据或传输非直连路径的第二QoS流的部分或全部数据，实现数据的冗余传输或负载均衡传输或切换传输。
本申请中，第一通信路径是所述第一终端设备与网络连接的直连路径，所述第二通信路径是所述第一终端设备通过中继设备与网络连接的非直连路径。
结合第一方面，可选的一种实施方式中，所述第一信息还包括第一服务质量流的标识和/或第二服务质量流的标识，所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
结合第一方面，可选的一种实施方式中，所述第一请求消息还包括第一指示，所述第一指示用于指示通过所述第一会话和所述第二会话共同传输所述第一数据，或者，所述第一请求消息还包括所述第一指示和第二指示，所述第二指示用于描述所述第一数据。
结合第一方面，可选的一种实施方式中，所述第一数据包括通过所述第一服务质量流传输的全部数据或部分数据，或者，所述第一数据包括通过所述第二服务质量流传输的全部数据或部分数据；所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
结合第一方面，可选的一种实施方式中，所述第二会话的标识以及所述中继设备的第一标识是所述第一终端设备从所述中继设备获取的。
结合第一方面，可选的一种实施方式中，所述第一请求消息还包括第三指示，所述第三指示用于指示所述第一通信路径为锚点路径，或者，所述第三指示用于指示所述第二通信路径为锚点路径，所述第一通信路径和所述第二通信路径通过服务于所述锚点路径的用户面功能实体用户面功能实体与应用服务器通信。
结合第一方面，可选的一种实施方式中，所述第一请求消息还包括所述第一终端设备的标识，所述第一终端设备的标识对应所述第二通信路径。
第二方面，提供了一种数据传输的方法，该方法可以由终端设备执行，或者，也可以由配置于终端设备中的芯片或电路执行，本申请对此不作限定。以下以中继设备执行为例进行说明。
该方法包括：所述中继设备获取第三信息，所述第三信息包括所述第一通信路径的第一会话的标识、所述第二通信路径的第二会话的标识以及所述第一终端设备的第一标识；
所述中继设备向第二移动性管理功能实体发送包括所述第三信息的第二请求消息，所述第二请求消息用于请求通过所述第一会话和所述第二会话共同传输第一数据。
根据上述技术方案，中继设备可以获取非直连路径的第二会话的标识，也可以从第一终端设备获取直连路径的第一会话的标识和第一终端设备的标识，根据该非直连路径的第二会话的标识，也可以从第一终端设备获取直连路径的第一会话的标识和第一终端设备的标识可以在非直连路径上向第二移动性管理实体发起请求，请求通过第一会话和所述第二会话共同传输第一数据，从而可以实现在直连路径上和非直连路径上共同传输数据。
结合第二方面，可选的一种实施方式中，所述第三信息还包括第二服务质量流的标识和/或第一服务质量流的标识，所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
结合第二方面，可选的一种实施方式中，所述第二请求消息还包括第一指示，所述第一指示用于指示通过所述第一会话和所述第二会话共同传输所述第一数据，或者，所述第二请求消息还包括所述第一指示和第二指示，所述第二指示用于描述所述第一数据。
结合第二方面，可选的一种实施方式中，所述第一数据包括通过所述第一服务质量流传输的全部数据或部分数据，或者，所述第一数据包括通过所述第二服务质量流传输的全部数据或部分数据；所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
结合第二方面，可选的一种实施方式中，所述第一会话的标识以及所述第一终端设备的第一标识是所述中继设备从所述第一终端设备获取的。
结合第二方面，可选的一种实施方式中，所述第一请求消息还包括第三指示，所述第三指示信息用于指示所述第一通信路径为锚点路径，或者，所述第三指示信息用于指示所述第二通信路径为锚点路径，
所述第一通信路径和所述第二通信路径通过服务于所述锚点路径的用户面功能实体与应用服务器通信。
第三方面，提供了一种数据传输的方法，该方法可以由核心网设备执行，或者，也可以由配置于核心网设备中的芯片或电路执行，本申请对此不作限定。以下以由核心网设备执行为例进行说明。
该方法包括：第一移动性管理实体从所述第一终端设备接收第一请求消息，所述第一请求消息用于请求通过所述第一通信路径的第一会话和所述第二通信路径的第二会话共同传输第一数据，所述第一请求消息包括第一信息，所述第一信息包括所述第一会话的标识、所述第二会话的标识以及所述中继设备的第一标识；在接收所述第一请求消息之后，第一用户面功能实体和第二用户面功能实体传输所述第一数据，所述第一用户面功能实体服务于所述第一通信路径，所述第二用户面功能实体服务于所述第二通信路径；其中，所述第一用户面功能实体和所述第二用户面功能实体中的一个与应用服务器之间传输所述第一数据。
根据上述技术方案，第一终端设备请求通过第一会话和所述第二会话共同传输第一数据，可以通过第一用户面功能实体和第二用户面功能实体之间传输第一数据，从而可以实现在直连路径上和非直连路径上共同传输数据。
结合第三方面，可选的一种实施方式中，所述第一信息还包括第一服务质量流的标识和/或第二服务质量流的标识，所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
结合第三方面，可选的一种实施方式中，所述第一请求消息还包括第一指示，所述第一指示用于指示通过所述第一会话和所述第二会话共同传输所述第一数据；或者，所述第一请求消息还包括所述第一指示和第二指示，所述第二指示用于描述所述第一数据。
结合第三方面，可选的一种实施方式中，所述第一数据包括通过所述第一服务质量流传输的全部数据或部分数据，或者，所述第一数据包括通过所述第二服务质量流传输的全部数据或部分数据；所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
结合第三方面，可选的一种实施方式中，所述第一请求消息还包括第三指示，所述第 三指示用于指示所述第一通信路径为锚点路径，或者，所述第三指示用于指示所述第二通信路径为锚点路径，所述第一通信路径和所述第二通信路径通过服务于所述锚点路径的用户面功能实体与应用服务器通信。
结合第三方面，可选的一种实施方式中，所述第一请求消息还包括所述第一终端设备的标识，所述第一终端设备的标识对应所述第二通信路径。
结合第三方面，可选的一种实施方式中，所述第一移动性管理实体根据所述中继设备的第一标识确定第二移动性管理实体，或者，所述第一移动性管理实体根据所述中继设备的第一标识和所述第二会话的标识确定第二会话管理功能实体；所述第二移动性管理实体服务于所述中继设备；所述第二会话管理功能实体服务于所述第二会话。
结合第三方面，可选的一种实施方式中，通过第一会话管理功能实体和所述第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道；
所述第一用户面功能实体和所述第二用户面功能实体通过所述第一通道传输所述第一数据。
结合第三方面，可选的一种实施方式中，所述通过第一会话管理功能实体和所述第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道，包括：所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息并将所述第一通道信息通过所述第二会话管理功能实体发送至所述第二用户面功能实体，所述第一通道信息用于所述第二用户面功能实体通过所述第一通道向所述第一用户面功能实体发送数据；所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息并将所述第二通道信息通过所述第一会话管理功能实体发送至所述第一用户面功能实体，所述第二通道信息用于所述第一用户面功能实体通过所述第一通道向所述第二用户面功能实体发送数据。
结合第三方面，可选的一种实施方式中，所述通过第一会话管理功能实体和第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道，包括：所述第一移动性管理实体根据所述中继设备的第一标识确定所述第二移动性管理实体；所述第一移动性管理实体从所述第二移动性管理实体获取所述第二会话管理功能实体的地址；所述第一移动性管理实体向所述第一会话管理功能实体发送所述第二会话管理功能实体的地址；所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息；所述第一会话管理功能实体根据所述第二会话管理功能实体的地址，向所述第二会话管理功能实体发送所述第一通道信息；所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息；所述第二会话管理功能实体向所述第一会话管理功能实体发送所述第二通道信息。
结合第三方面，可选的一种实施方式中，所述通过第一会话管理功能实体和第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道，包括：所述第一移动性管理实体根据所述中继设备的第一标识确定所述第二移动性管理实体；所述第一移动性管理实体通过所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息；所述第二移动性管理实体通过所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息；所述第一移动性管理实体通过所述第一会话管理功能实体向所述第一用户面功能实体发送所述第二通道信息；所述第二移动性管理实体通过所 述第二会话管理功能实体向所述第二用户面功能实体发送所述第一通道信息。
结合第三方面，可选的一种实施方式中，所述第一用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第一规则，所述第一规则用于指示所述第一用户面功能实体向所述第二用户面功能实体发送所述第一数据的部分或全部，使得所述第二用户面功能实体通过所述第二通信路径向所述第一终端设备发送从所述第一用户面功能实体接收的数据；或者，所述第一用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第二规则，所述第二规则用于指示所述第一用户面功能实体将从所述第二用户面功能实体接收的数据发送至所述应用服务器；或者，所述第一用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第三规则，所述第三规则用于指示所述第二用户面功能实体向所述第一用户面功能实体发送从所述第一终端设备接收的所述第一数据；或者，所述第一用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第四规则，所述第四规则用于指示所述第二用户面功能实体向所述第一终端设备发送从所述第一用户面功能实体接收的数据。
结合第三方面，可选的一种实施方式中，所述第二用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第一规则，所述第一规则用于指示所述第一用户面功能实体向所述第二用户面功能实体发送从所述第一终端设备接收的所述第一数据；或者，所述第二用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第二规则，所述第二规则用于指示所述第一用户面功能实体向所述第一终端设备发送从所述第二用户面功能实体接收的数据；或者，所述第二用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第三规则，所述第三规则用于指示所述第二用户面功能实体向所述第一用户面功能实体发送所述第一数据的部分或全部，使得所述第一用户面功能实体通过所述第一通信路径向所述第一终端设备发送从所述第二用户面功能实体接收的数据；或者，所述第二用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第四规则，所述第四规则用于指示所述第二用户面功能实体将从所述第一用户面功能实体接收的数据发送至所述应用服务器。
结合第三方面，可选的一种实施方式中，所述第一会话管理功能实体从所述第一移动性管理实体接收所述第一信息，所述第一会话管理功能实体根据所述第一信息生成所述第一规则和所述第二规则；所述第二会话管理功能实体从所述第一会话管理功能实体或所述第二移动性管理实体接收第二信息，所述第二会话管理功能实体根据所述第二信息生成所述第三规则和所述第四规则，所述第二信息包括：第一指示、所述第二会话的标识以及所述中继设备的第二标识，所述中继设备的第二标识是由所述第一移动性管理实体根据所述中继设备的第一标识确定的。
结合第三方面，可选的一种实施方式中，所述第二信息还包括以下至少一项：所述第二服务质量流的标识；所述第二指示；所述第一终端设备的标识；或所述第三指示。
第四方面，提供了一种数据传输的方法，该方法可以由核心网设备执行，或者，也可以由配置于核心网设备中的芯片或电路执行，本申请对此不作限定。以下以由核心网设备执行为例进行说明。
该方法包括：第二移动性管理功能实体从所述中继设备接收第二请求消息，所述第二请求消息用于请求通过所述第一通信路径的第一会话和所述第二通信路径的第二会话共同传输第一数据，所述第二请求消息包括第三信息，所述第三信息包括所述第一会话的标识、所述第二会话的标识以及所述第一终端设备的第一标识；在接收所述第二请求消息之后，第一用户面功能实体和第二用户面功能实体传输所述第一数据，所述第一用户面功能实体服务于所述第一通信路径，所述第二用户面功能实体服务于所述第二通信路径，其中，所述第一用户面功能实体和所述第二用户面功能实体中的一个与应用服务器之间传输所述第一数据。
根据上述技术方案，中继设备请求通过第一会话和所述第二会话共同传输第一数据，可以通过第一用户面功能实体和第二用户面功能实体之间传输第一数据，从而可以实现在直连路径上和非直连路径上共同传输数据。
结合第四方面，可选的一种实施方式中，所述第三信息还包括第二服务质量流的标识和/或第一服务质量流的标识，所述第二服务质量流为所述第二会话对应的服务质量流，所述第一服务质量流为所述第一会话对应的服务质量流。
结合第四方面，可选的一种实施方式中，所述第二请求消息还包括第一指示，所述第一指示用于指示通过所述第一会话和所述第二会话共同传输所述第一数据；或者，所述第二请求消息还包括所述第一指示和第二指示，所述第二指示用于描述所述第一数据。
结合第四方面，可选的一种实施方式中，所述第一数据包括通过所述第一服务质量流传输的全部数据或部分数据，或者，所述第一数据包括通过所述第二服务质量流传输的全部数据或部分数据；所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
结合第四方面，可选的一种实施方式中，所述第二请求消息还包括第三指示，所述第三指示用于指示所述第一通信路径为锚点路径，或者，所述第三指示用于指示所述第二通信路径为锚点路径，所述第一通信路径和所述第二通信路径通过服务于所述锚点路径的用户面功能实体与应用服务器通信。
结合第四方面，可选的一种实施方式中，所述第二移动性管理实体根据所述第一终端设备的第一标识确定第一移动性管理实体，或者，所述第二移动性管理实体根据所述第一终端设备的第一标识和所述第一会话的标识确定第一会话管理功能实体；所述第一移动性管理实体服务于所述第一终端设备，所述第一会话管理功能实体服务所述第一会话。
结合第四方面，可选的一种实施方式中，所述第一用户面功能实体和所述第二用户面功能实体传输所述第一数据，包括：通过第一会话管理功能实体和所述第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道；所述第一用户面功能实体和所述第二用户面功能实体通过所述第一通道传输所述第一数据。
结合第四方面，可选的一种实施方式中，所述通过第一会话管理功能实体和所述第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道，包括：所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息并将所述第一通道信息通过所述第二会话管理功能实体发送至所述第二用户面功能实体，所述第一通道信息用于所述第二用户面功能实体通过所述第一通道向所述第一用户面功能实体发送数据；所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息 并将所述第二通道信息通过所述第一会话管理功能实体发送至所述第一用户面功能实体，所述第一通道信息用于所述第一用户面功能实体通过所述第一通道向所述第二用户面功能实体发送数据。
结合第四方面，可选的一种实施方式中，所述通过第一会话管理功能实体和第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道，包括：所述第二移动性管理实体根据所述第一终端设备的第一标识确定所述第一移动性管理实体；所述第二移动性管理实体从所述第一移动性管理实体获取所述第一会话管理功能实体的地址；所述第二移动性管理实体向所述第二会话管理功能实体发送所述第一会话管理功能实体的地址；所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息；所述第二会话管理功能实体根据所述第一会话管理功能实体的地址，向所述第一会话管理功能实体发送所述第二通道信息；所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息；所述第一会话管理功能实体向所述第二会话管理功能实体发送所述第一通道信息。
结合第四方面，可选的一种实施方式中，所述通过第一会话管理功能实体和第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道，包括：所述第二移动性管理实体根据所述第一终端设备的第一标识确定所述第一移动性管理实体；所述第二移动性管理实体通过所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息；所述第一移动性管理实体通过所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息；所述第二移动性管理实体通过所述第二会话管理功能实体向所述第二用户面功能实体发送所述第一通道信息；所述第一移动性管理实体通过所述第一会话管理功能实体向所述第一用户面功能实体发送所述第二通道信息。
结合第四方面，可选的一种实施方式中，所述第一用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第一规则，所述第一规则用于指示所述第一用户面功能实体向所述第二用户面功能实体发送所述第一数据的部分或全部，使得所述第二用户面功能实体通过所述第二通信路径向所述第一终端设备发送从所述第一用户面功能实体接收的数据；或者，所述第一用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第二规则，所述第二规则用于指示所述第一用户面功能实体将从所述第二用户面功能实体接收的数据发送至所述应用服务器；或者，所述第一用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第三规则，所述第三规则用于指示所述第二用户面功能实体向所述第一用户面功能实体发送从所述第一终端设备接收的所述第一数据；或者，所述第一用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第四规则，所述第四规则用于指示所述第二用户面功能实体向所述第一终端设备发送从所述第一用户面功能实体接收的数据。
结合第四方面，可选的一种实施方式中，所述第二用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第一规则，所述第一规则用于指示所述第一用户面功能实体向所述第二用户面功能实体发送从所述第一终端设备接收的所述第一数据；或者，所述第二用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第二规则，所述第二规则用于指示所 述第一用户面功能实体向所述第一终端设备发送从所述第二用户面功能实体接收的数据；或者，所述第二用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第三规则，所述第三规则用于指示所述第二用户面功能实体向所述第一用户面功能实体发送所述第一数据的部分或全部，使得所述第一用户面功能实体通过所述第一通信路径向所述第一终端设备发送从所述第二用户面功能实体接收的数据；或者，所述第二用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第四规则，所述第四规则用于指示所述第二用户面功能实体将从所述第一用户面功能实体接收的数据发送至所述应用服务器。
结合第四方面，可选的一种实施方式中，所述第二会话管理功能实体从所述第二移动性管理实体接收所述第三信息，所述第二会话管理功能实体根据所述第三信息生成所述第一规则和所述第二规则；所述第一会话管理功能实体从所述第二会话管理功能实体或所述第一移动性管理实体接收第四信息，所述第一会话管理功能实体根据所述第四信息生成所述第三规则和所述第四规则，所述第四信息包括：第一指示、所述第一会话的标识以及所述第一终端设备的第二标识，所述第一终端设备的第二标识是由所述第二移动性管理实体根据所述第一终端设备的第一标识确定的。
结合第四方面，可选的一种实施方式中，所述第四信息还包括以下至少一项：所述第一服务质量流的标识；所述第二指示；所述中继设备的标识；或，所述第三指示。
第五方面，提供了一种数据传输的装置，该装置可以是终端设备，或者，也可以由配置于终端设备中的芯片或电路，本申请对此不作限定。以下以第一终端设备为例进行说明。
该装置包括：收发单元，用于获取第一信息，所述第一信息包括所述第一通信路径的第一会话的标识、所述第二通信路径的第二会话的标识以及所述中继设备的第一标识；所述收发单元还用于向第一移动性管理实体发送包括所述第一信息的第一请求消息，所述第一请求消息用于请求通过所述第一会话和所述第二会话共同传输第一数据。
根据上述技术方案，第一终端设备可以获取直连路径的第一会话的标识，也可以从中继设备获取非直连路径的第二会话的标识和中继设备的标识，根据该直连路径的第一会话的标识，也可以从中继设备获取非直连路径的第二会话的标识和中继设备的标识可以在直连路径上向第一移动性管理实体发起请求，请求通过第一会话和所述第二会话共同传输第一数据，从而可以实现在直连路径上和非直连路径上共同传输数据。
本申请中，第一通信路径是所述第一终端设备与网络连接的直连路径，所述第二通信路径是所述第一终端设备通过中继设备与网络连接的非直连路径。
结合第五方面，可选的一种实施方式中，所述第一信息还包括第一服务质量流的标识和/或第二服务质量流的标识，所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
结合第五方面，可选的一种实施方式中，所述第一请求消息还包括第一指示，所述第一指示用于指示通过所述第一会话和所述第二会话共同传输所述第一数据，或者，所述第一请求消息还包括所述第一指示和第二指示，所述第二指示用于描述所述第一数据。
结合第五方面，可选的一种实施方式中，所述第一数据包括通过所述第一服务质量流传输的全部数据或部分数据，或者，所述第一数据包括通过所述第二服务质量流传输的全部数据或部分数据；所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服 务质量流为所述第二会话对应的服务质量流。
结合第五方面，可选的一种实施方式中，所述第二会话的标识、所述第二服务质量流的标识以及所述中继设备的第一标识是所述第一终端设备从所述中继设备获取的。
结合第五方面，可选的一种实施方式中，所述第一请求消息还包括第三指示，所述第三指示用于指示所述第一通信路径为锚点路径，或者，所述第三指示用于指示所述第二通信路径为锚点路径，所述第一通信路径和所述第二通信路径通过服务于所述锚点路径的用户面功能实体用户面功能实体与应用服务器通信。
结合第五方面，可选的一种实施方式中，所述第一请求消息还包括所述第一终端设备的标识，所述第一终端设备的标识对应所述第二通信路径。
第六方面，提供了一种数据传输的装置，该装置可以为终端设备，或者，也可以为配置于终端设备中的芯片或电路，本申请对此不作限定。以下以中继设备执行为例进行说明。
该装置包括：收发单元，用于获取第三信息，所述第三信息包括所述第一通信路径的第一会话的标识、所述第二通信路径的第二会话的标识以及所述第一终端设备的第一标识；所述收发单元还用于所述中继设备向第二移动性管理功能实体发送包括所述第三信息的第二请求消息，所述第二请求消息用于请求通过所述第一会话和所述第二会话共同传输第一数据。
根据上述技术方案，中继设备可以获取非直连路径的第二会话的标识，也可以从第一终端设备获取直连路径的第一会话的标识和第一终端设备的标识，根据该非直连路径的第二会话的标识，也可以从第一终端设备获取直连路径的第一会话的标识和第一终端设备的标识可以在非直连路径上向第二移动性管理实体发起请求，请求通过第一会话和所述第二会话共同传输第一数据，从而可以实现在直连路径上和非直连路径上共同传输数据。
结合第六方面，可选的一种实施方式中，所述第三信息还包括第二服务质量流的标识和/或第一服务质量流的标识，所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
结合第六方面，可选的一种实施方式中，所述第二请求消息还包括第一指示，所述第一指示用于指示通过所述第一会话和所述第二会话共同传输所述第一数据，或者，所述第二请求消息还包括所述第一指示和第二指示，所述第二指示用于描述所述第一数据。
结合第六方面，可选的一种实施方式中，所述第一数据包括通过所述第一服务质量流传输的全部数据或部分数据，或者，所述第一数据包括通过所述第二服务质量流传输的全部数据或部分数据；所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
结合第六方面，可选的一种实施方式中，所述第一会话的标识、所述第一服务质量流的标识以及所述第一终端设备的第一标识是所述中继设备从所述第一终端设备获取的。
结合第六方面，可选的一种实施方式中，所述第一请求消息还包括第三指示，所述第三指示信息用于指示所述第一通信路径为锚点路径，或者，所述第三指示信息用于指示所述第二通信路径为锚点路径，所述第一通信路径和所述第二通信路径通过服务于所述锚点路径的用户面功能实体与应用服务器通信。
第七方面，提供了一种数据传输的装置，该装置可以是核心网设备，或者，也可以由配置于核心网设备中的芯片或电路，本申请对此不作限定。以下以核心网设备为例进行说 明。
该装置包括：收发单元，用于从所述第一终端设备接收第一请求消息，所述第一请求消息用于请求通过所述第一通信路径的第一会话和所述第二通信路径的第二会话共同传输第一数据，所述第一请求消息包括第一信息，所述第一信息包括所述第一会话的标识、所述第二会话的标识以及所述中继设备的第一标识；在接收所述第一请求消息之后，收发单元还用于用于第一用户面功能实体和第二用户面功能实体传输所述第一数据，所述第一用户面功能实体服务于所述第一通信路径，所述第二用户面功能实体服务于所述第二通信路径；其中，所述第一用户面功能实体和所述第二用户面功能实体中的一个与应用服务器之间传输所述第一数据。
根据上述技术方案，第一终端设备请求通过第一会话和所述第二会话共同传输第一数据，可以通过第一用户面功能实体和第二用户面功能实体之间传输第一数据，从而可以实现在直连路径上和非直连路径上共同传输数据。
结合第七方面，可选的一种实施方式中，所述第一信息还包括第一服务质量流的标识和/或第二服务质量流的标识，所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
结合第七方面，可选的一种实施方式中，所述第一请求消息还包括第一指示，所述第一指示用于指示通过所述第一会话和所述第二会话共同传输所述第一数据；或者，所述第一请求消息还包括所述第一指示和第二指示，所述第二指示用于描述所述第一数据。
结合第七方面，可选的一种实施方式中，所述第一数据包括通过所述第一服务质量流传输的全部数据或部分数据，或者，所述第一数据包括通过所述第二服务质量流传输的全部数据或部分数据；所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
结合第七方面，可选的一种实施方式中，所述第一请求消息还包括第三指示，所述第三指示用于指示所述第一通信路径为锚点路径，或者，所述第三指示用于指示所述第二通信路径为锚点路径，所述第一通信路径和所述第二通信路径通过服务于所述锚点路径的用户面功能实体与应用服务器通信。
结合第七方面，可选的一种实施方式中，所述第一请求消息还包括所述第一终端设备的标识，所述第一终端设备的标识对应所述第二通信路径。
结合第七方面，可选的一种实施方式中，所述装置包括：处理单元，用于根据所述中继设备的第一标识确定第二移动性管理实体，或者，该处理单元用于根据所述中继设备的第一标识和所述第二会话的标识确定第二会话管理功能实体；所述第二移动性管理实体服务于所述中继设备，所述第二会话管理功能实体服务于所述第二会话。
结合第七方面，可选的一种实施方式中，所述处理单元具体用于通过第一会话管理功能实体和所述第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道；所述第一用户面功能实体和所述第二用户面功能实体通过所述第一通道传输所述第一数据。
结合第七方面，可选的一种实施方式中，所述处理单元用于指示收发单元从所述第一用户面功能实体获取第一通道信息并将所述第一通道信息通过所述第二会话管理功能实体发送至所述第二用户面功能实体，所述第一通道信息用于所述第二用户面功能实体通过 所述第一通道向所述第一用户面功能实体发送数据；所述处理单元用于指示收发单元从所述第二用户面功能实体获取第二通道信息并将所述第二通道信息通过所述第一会话管理功能实体发送至所述第一用户面功能实体，所述第二通道信息用于所述第一用户面功能实体通过所述第一通道向所述第二用户面功能实体发送数据。
结合第七方面，可选的一种实施方式中，处理单元具体用于根据所述中继设备的第一标识确定所述第二移动性管理实体；收发单元具体用于从所述第二移动性管理实体获取所述第二会话管理功能实体的地址；收发单元还用于向所述第一会话管理功能实体发送所述第二会话管理功能实体的地址；收发单元还用于从所述第一用户面功能实体获取第一通道信息；处理单元进一步用于指示收发单元根据所述第二会话管理功能实体的地址，向所述第二会话管理功能实体发送所述第一通道信息；收发单元进一步用于从所述第二用户面功能实体获取第二通道信息；收发单元进一步还用于向所述第一会话管理功能实体发送所述第二通道信息。
结合第七方面，可选的一种实施方式中，收发单元还用于根据所述中继设备的第一标识确定所述第二移动性管理实体；收发单元还用于从所述第一用户面功能实体获取第一通道信息；收发单元还用于从所述第二用户面功能实体获取第二通道信息；收发单元还用于通过所述第一会话管理功能实体向所述第一用户面功能实体发送所述第二通道信息；收发单元还用于通过所述第二会话管理功能实体向所述第二用户面功能实体发送所述第一通道信息。
结合第七方面，可选的一种实施方式中，所述第一用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第一用户面功能实体发送第一规则，所述第一规则用于指示所述第一用户面功能实体向所述第二用户面功能实体发送所述第一数据的部分或全部，使得所述第二用户面功能实体通过所述第二通信路径向所述第一终端设备发送从所述第一用户面功能实体接收的数据；或者，所述第一用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第一用户面功能实体发送第二规则，所述第二规则用于指示所述第一用户面功能实体将从所述第二用户面功能实体接收的数据发送至所述应用服务器；或者，所述第一用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第二用户面功能实体发送第三规则，所述第三规则用于指示所述第二用户面功能实体向所述第一用户面功能实体发送从所述第一终端设备接收的所述第一数据；或者，所述第一用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第二用户面功能实体发送第四规则，所述第四规则用于指示所述第二用户面功能实体向所述第一终端设备发送从所述第一用户面功能实体接收的数据。
结合第七方面，可选的一种实施方式中，所述第二用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第一用户面功能实体发送第一规则，所述第一规则用于指示所述第一用户面功能实体向所述第二用户面功能实体发送从所述第一终端设备接收的所述第一数据；或者，所述第二用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第一用户面功能实体发送第二规则，所述第二规则用于指示所述第一用户面功能实体向所述第一终端设备发送从所述第二用户面功能实体接收的数据；或者，所述第二用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第二用户面功能实体发送第三规则，所述第三规则用于指示所述第二用户面功能实体向所述第一用户面功能实体发送所述 第一数据的部分或全部，使得所述第一用户面功能实体通过所述第一通信路径向所述第一终端设备发送从所述第二用户面功能实体接收的数据；或者，所述第二用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第二用户面功能实体发送第四规则，所述第四规则用于指示所述第二用户面功能实体将从所述第一用户面功能实体接收的数据发送至所述应用服务器。
结合第七方面，可选的一种实施方式中，收发单元还用于从所述第一移动性管理实体接收所述第一信息，处理单元还用于根据所述第一信息生成所述第一规则和所述第二规则；收发单元进一步用于从所述第一会话管理功能实体或所述第二移动性管理实体接收第二信息，处理单元进一步用于根据所述第二信息生成所述第三规则和所述第四规则，所述第二信息包括：第一指示、所述第二会话的标识以及所述中继设备的第二标识，所述中继设备的第二标识是由所述第一移动性管理实体根据所述中继设备的第一标识确定的。
结合第七方面，可选的一种实施方式中，所述第二信息还包括以下至少一项：所述第二服务质量流的标识；所述第二指示；所述第一终端设备的标识；或所述第三指示。
第八方面，提供了一种数据传输的装置，该装置可以为核心网设备，或者，也可以为配置于核心网设备中的芯片或电路，本申请对此不作限定。以下以核心网设备为例进行说明。
该装置包括：收发单元，用于从所述中继设备接收第二请求消息，所述第二请求消息用于请求通过所述第一通信路径的第一会话和所述第二通信路径的第二会话共同传输第一数据，所述第二请求消息包括第三信息，所述第三信息包括所述第一会话的标识、所述第二会话的标识以及所述第一终端设备的第一标识；在接收所述第二请求消息之后，收发单元还用于在第一用户面功能实体和第二用户面功能实体之间传输所述第一数据，所述第一用户面功能实体服务于所述第一通信路径，所述第二用户面功能实体服务于所述第二通信路径，其中，所述第一用户面功能实体和所述第二用户面功能实体中的一个与应用服务器之间传输所述第一数据。
根据上述技术方案，中继设备请求通过第一会话和所述第二会话共同传输第一数据，可以通过第一用户面功能实体和第二用户面功能实体之间传输第一数据，从而可以实现在直连路径上和非直连路径上共同传输数据。
结合第八方面，可选的一种实施方式中，所述第三信息还包括第二服务质量流的标识和/或第一服务质量流的标识，所述第二服务质量流为所述第二会话对应的服务质量流，所述第一服务质量流为所述第一会话对应的服务质量流。
结合第八方面，可选的一种实施方式中，所述第二请求消息还包括第一指示，所述第一指示用于指示通过所述第一会话和所述第二会话共同传输所述第一数据；或者，所述第二请求消息还包括所述第一指示和第二指示，所述第二指示用于描述所述第一数据。
结合第八方面，可选的一种实施方式中，所述第一数据包括通过所述第一服务质量流传输的全部数据或部分数据，或者，所述第一数据包括通过所述第二服务质量流传输的全部数据或部分数据；所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
结合第八方面，可选的一种实施方式中，所述第二请求消息还包括第三指示，所述第三指示用于指示所述第一通信路径为锚点路径，或者，所述第三指示用于指示所述第二通 信路径为锚点路径，所述第一通信路径和所述第二通信路径通过服务于所述锚点路径的用户面功能实体与应用服务器通信。
结合第八方面，可选的一种实施方式中，该装置还包括：处理单元，用于根据所述第一终端设备的第一标识确定第一移动性管理实体，或者，处理单元还用于根据所述第一终端设备的第一标识和所述第一会话的标识确定第一会话管理功能实体；所述第一移动性管理实体服务于所述第一终端设备，所述第一会话管理功能实体服务所述第一会话。
结合第八方面，可选的一种实施方式中，处理单元具体用于通过第一会话管理功能实体和所述第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道；所述第一用户面功能实体和所述第二用户面功能实体通过所述第一通道传输所述第一数据。
结合第八方面，可选的一种实施方式中，收发单元具体用于从所述第一用户面功能实体获取第一通道信息并将所述第一通道信息通过所述第二会话管理功能实体发送至所述第二用户面功能实体，所述第一通道信息用于所述第二用户面功能实体通过所述第一通道向所述第一用户面功能实体发送数据；收发单元还用于从所述第二用户面功能实体获取第二通道信息并将所述第二通道信息通过所述第一会话管理功能实体发送至所述第一用户面功能实体，所述第一通道信息用于所述第一用户面功能实体通过所述第一通道向所述第二用户面功能实体发送数据。
结合第八方面，可选的一种实施方式中，处理单元还用于根据所述第一终端设备的第一标识确定所述第一移动性管理实体；收发单元还用于从所述第一移动性管理实体获取所述第一会话管理功能实体的地址；收发单元还用于向所述第二会话管理功能实体发送所述第一会话管理功能实体的地址；收发单元还用于从所述第二用户面功能实体获取第二通道信息；处理单元还用于指示收发单元根据所述第一会话管理功能实体的地址，向所述第一会话管理功能实体发送所述第二通道信息；收发单元进一步用于从所述第一用户面功能实体获取第一通道信息；收发单元进一步还用于向所述第二会话管理功能实体发送所述第一通道信息。
结合第八方面，可选的一种实施方式中，处理单元还用于根据所述第一终端设备的第一标识确定所述第一移动性管理实体；收发单元还用于通过所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息；收发单元还用于通过所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息；收发单元还用于通过所述第二会话管理功能实体向所述第二用户面功能实体发送所述第一通道信息；收发单元还用于通过所述第一会话管理功能实体向所述第一用户面功能实体发送所述第二通道信息。
结合第八方面，可选的一种实施方式中，所述第一用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第一用户面功能实体发送第一规则，所述第一规则用于指示所述第一用户面功能实体向所述第二用户面功能实体发送所述第一数据的部分或全部，使得所述第二用户面功能实体通过所述第二通信路径向所述第一终端设备发送从所述第一用户面功能实体接收的数据；或者，所述第一用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第一用户面功能实体发送第二规则，所述第二规则用于指示所述第一用户面功能实体将从所述第二用户面功能实体接收的数据发送至所述应用服务器；或者，所述第一用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第二用户面功能 实体发送第三规则，所述第三规则用于指示所述第二用户面功能实体向所述第一用户面功能实体发送从所述第一终端设备接收的所述第一数据；或者，所述第一用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第二用户面功能实体发送第四规则，所述第四规则用于指示所述第二用户面功能实体向所述第一终端设备发送从所述第一用户面功能实体接收的数据。
结合第八方面，可选的一种实施方式中，所述第二用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第一用户面功能实体发送第一规则，所述第一规则用于指示所述第一用户面功能实体向所述第二用户面功能实体发送从所述第一终端设备接收的所述第一数据；或者，所述第二用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第一用户面功能实体发送第二规则，所述第二规则用于指示所述第一用户面功能实体向所述第一终端设备发送从所述第二用户面功能实体接收的数据；或者，所述第二用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第二用户面功能实体发送第三规则，所述第三规则用于指示所述第二用户面功能实体向所述第一用户面功能实体发送所述第一数据的部分或全部，使得所述第一用户面功能实体通过所述第一通信路径向所述第一终端设备发送从所述第二用户面功能实体接收的数据；或者，所述第二用户面功能实体为锚点用户面功能实体，收发单元还用于向所述第二用户面功能实体发送第四规则，所述第四规则用于指示所述第二用户面功能实体将从所述第一用户面功能实体接收的数据发送至所述应用服务器。
结合第八方面，可选的一种实施方式中，收发单元还用于从所述第二移动性管理实体接收所述第三信息，处理单元还用于根据所述第三信息生成所述第一规则和所述第二规则；收发单元进一步用于从所述第二会话管理功能实体或所述第一移动性管理实体接收第四信息，处理单元进一步用于根据所述第四信息生成所述第三规则和所述第四规则，所述第四信息包括：第一指示、所述第一会话的标识以及所述第一终端设备的第二标识，所述第一终端设备的第二标识是由所述第二移动性管理实体根据所述第一终端设备的第一标识确定的。
结合第八方面，可选的一种实施方式中，所述第四信息还包括以下至少一项：所述第一服务质量流的标识；所述第二指示；所述中继设备的标识；或，所述第三指示。
第九方面，提供了一种数据传输的方法，该方法可以由第一终端设备执行，或者，也可以由配置于第一终端设备中的芯片或电路执行，本申请对此不作限定。以下以由第一终端设备执行为例进行说明。
该方法包括：第一终端设备获取第一信息，所述第一信息用于第一网络设备通过所述第一通信路径向所述第一终端设备传输第一数据，所述第一信息包括第一包检测规则PDR；所述第一终端设备通过第二通信路径向第二网络设备发送第一消息，所述第一消息包括所述第一信息和第一指示信息，所述第一指示信息用于指示通过所述第一通信路径和/或所述第二通信路径传输所述第一数据。
根据上述方案，第一终端设备可以获取第一信息，并通过第二通信路径向第一网络设备发送该第一信息，用于第一网络设备通过第一通信路径和/或第二通信路径向第一终端设备传输第一数据，能够实现在直连路径和非直连路径同时进行数据的传输，使得远端终端设备和数据网络之间的传输路径具有多样性，可以动态地满足业务需求。
结合第九方面，在第九方面的某些实现方式中，所述第一终端设备向第二终端设备发送第一请求消息，所述第一请求消息用于请求在所述第一通信路径上建立第一QoS流，所述第一请求消息包括第二指示信息，所述第二指示信息用于获取所述第一信息；所述第一终端设备从所述第二终端设备接收所述第一信息。
本申请中，上述方案中第一通信路径为非直连路径。
可以理解，该第一信息是在非直连路径上建立的第一QoS流的QoS流信息。
结合第九方面，在第九方面的某些实现方式中，所述第一信息是所述第一终端设备在所述第一通信路径上建立第一QoS流中获取的。
在该方案中，第一通信路径为直连路径。
可以理解，该第一信息是在直连路径上建立第一QoS流中获取的QoS流信息。
结合第九方面，在第九方面的某些实现方式中，所述第一信息还包括所述第一通信路径上的第一QoS流信息，所述第一QoS流信息包括第二终端设备的标识、所述第一QoS流的标识QFI、所述第一QoS流对应的PDU会话的标识。
结合第九方面，在第九方面的某些实现方式中，所述第一信息还包括第三指示信息，所述第三指示信息用于指示进行可靠性传输或负载均衡传输。
结合第九方面，在第九方面的某些实现方式中，所述第一通信路径为所述第一终端设备通过所述第二终端设备连接所述第一网络设备的通信路径，或者，所述第一通信路径为所述第一终端设备直接连接所述第一网络设备的通信路径。
结合第九方面，在第九方面的某些实现方式中，所述第一通信路径包括至少一个QoS流，所述第一QoS流信息包括所述第一QoS流对应的PDR，所述第一QoS流为所述至少一个QoS流中的一个。
第十方面，提供了一种数据传输的方法，该方法可以由第一网络设备执行，或者，也可以由配置于第一网络设备中的芯片或电路执行，本申请对此不作限定。以下以由第一网络设备执行为例进行说明。
该方法包括：第一网络设备接收第一信息和第二信息，所述第一信息用于所述第一网络设备通过第一通信路径向第一终端设备传输数据，所述第二信息用于所述第一网络设备通过第二通信路径向所述第一终端设备传输数据；所述第一网络设备接收第一数据，通过所述第一通信路径和/或第二通信路径向所述第一终端设备发送所述第一数据。
根据上述方案，第一网络设备可以接收第一信息和第二信息，根据第一信息可以通过第一通信路径向第一终端设备传输数据，根据第二信息可以通过第二通信路径向第一终端设备传输数据，能够实现在直连路径和非直连路径同时进行数据的传输，使得远端终端设备和数据网络之间的传输路径具有多样性，可以动态地满足业务需求。
结合第十方面，在第十方面的某些实现方式中，所述第一网络设备通过所述第一通信路径和/或第二通信路径向所述第一终端设备发送所述第一数据，包括：所述第一网络设备根据所述第一信息确定目的地址和源地址；所述第一网络设备根据所述目的地址和源地址对所述第一数据进行处理，发送处理后的所述第一数据。
结合第十方面，在第十方面的某些实现方式中，所述第一通信路径为所述第一终端设备通过第二终端设备接收所述第一网络设备发送的数据的通信路径。
结合第十方面，在第十方面的某些实现方式中，所述第一网络设备接收第三指示信息， 所述第三指示信息用于指示进行可靠性传输或负载均衡传输。
结合第十方面，在第十方面的某些实现方式中，当所述第三指示信息指示可靠性传输，所述第一网络设备将所述第一数据的IP包进行复制，分别通过所述第一通信路径和所述第二通信路径向所述第一终端设备发送所述第一数据的IP包；或者，当所述第二指示信息指示负载均衡传输，所述第一网络设备将所述第一数据的IP包进行分流，分别通过所述第一通信路径和所述第二通信路径向所述第一终端设备发送所述第一数据的IP包。
结合第十方面，在第十方面的某些实现方式中，所述第一网络设备根据所述第三指示信息确定通过所述第一通信路径和/或第二通信路径向所述第一终端设备发送所述第一数据；或者所述第一网络设备根据所述第一信息和所述第二信息确定通过所述第一通信路径和/或第二通信路径向所述第一终端设备发送所述第一数据。
结合第十方面，在第十方面的某些实现方式中，所述第一网络设备将所述第一数据发送给第三网络设备，由所述第三网络设备通过所述第一通信路径发向所述第一终端设备。
结合第十方面，在第十方面的某些实现方式中，所述第一通信路径包括至少一个QoS流，所述第一QoS流信息包括所述第一QoS流对应的PDR，所述第一QoS流为所述至少一个QoS流中的一个，所述第二通信路径包括至少一个QoS流，所述第二QoS流信息包括所述第二QoS流对应的PDR，所述第二QoS流为所述至少一个QoS流中的一个。
结合第十方面，在第十方面的某些实现方式中，所述第一网络设备将所述第一数据封装到GTP消息，通过第一通道将所述GTP消息发送至所述第三网络设备，所述GTP消息包括所述第一QoS流的标识QFI，所述第一通道用于所述第一网络设备和所述第三网络设备进行数据传输。
第十一方面，提供了一种数据传输系统，该系统包括：第一UPF、第一AMF、第二UPF、第二AMF、第一SMF，第二SMF，所述第一AMF和所述第一SMF是为第一终端设备提供服务的网络设备，所述第二AMF和所述第二SMF是为第二终端设备提供服务的网络设备，所述第一UPF通过第一通信路径和/或第二通信路径向所述第一终端设备传输第一数据，所述第二UPF通过所述第二通信路径向所述第一终端设备传输所述第一数据；其中，所述第一AMF用于，从所述第一终端设备接收并向第二AMF发送第一消息，所述第一消息包括第一信息和第一指示信息；从所述第二AMF接收第二UPF的地址和第一包检测规则PDR，所述第一PDR为所述第一通信路径上的第一QoS流对应的PDR；向第一SMF发送所述第二UPF的地址、所述第一QoS流的标识及所述第一指示信息；所述第二AMF用于，接收所述第一消息；根据所述第一消息确定所述第二UPF的地址和所述第一PDR；所述第一SMF用于，接收所述第二UPF的地址、所述第一QoS流的标识及所述第一指示信息；根据所述第一指示信息向所述第一UPF发送所述第一PDR、第二PDR及所述第一QoS流的标识，所述第二PDR为所述第二通信路径上的第二QoS流对应的PDR；所述第一UPF用于，接收所述第一PDR、第二PDR及所述第一QoS流的标识；通过所述第一通信路径和/或所述第二通信路径向所述第一终端设备传输第一数据；所述第二UPF用于，通过第二通信路径向所述第一终端设备传输所述第一数据。
结合第十一方面，在第十一方面的某些实现方式中，所述第一SMF还用于，根据所述第二UPF的地址建立第一通道，所述第一通道用于所述第一UPF和所述第二UPF进行数据传输。
结合第十一方面，在第十一方面的某些实现方式中，所述第一信息包括所述第一通信路径上的第一QoS流信息，所述第一QoS流信息所述第二终端设备的标识、所述第一QoS流的标识QFI、所述第一QoS流对应的PDU会话的标识。
结合第十一方面，在第十一方面的某些实现方式中，所述第一AMF还用于，根据所述第二终端设备的标识确定所述第二AMF。
结合第十一方面，在第十一方面的某些实现方式中，所述第一消息还包括第三指示信息，所述第三指示信息用于指示所述第一UPF进行可靠性传输或负载均衡传输。
第十二方面，提供了一种数据传输的装置，该装置可以为第一终端设备，或者，也可以为配置于第一终端设备中的芯片或电路，本申请对此不作限定。
该装置包括：处理单元，用于获取第一信息，所述第一信息用于第一网络设备通过所述第一通信路径向所述第一终端设备传输第一数据，所述第一信息包括第一包检测规则PDR；收发单元，用于通过第二通信路径向第二网络设备发送第一消息，所述第一消息包括所述第一信息和第一指示信息，所述第一指示信息用于指示通过所述第一通信路径和/或所述第二通信路径传输所述第一数据。
结合第十二方面，在第十二方面的某些实现方式中，上述收发单元具体用于向第二终端设备发送第一请求消息，所述第一请求消息用于请求在所述第一通信路径上建立第一QoS流，所述第一请求消息包括第二指示信息，所述第二指示信息用于获取所述第一信息；从所述第二终端设备接收所述第一信息。
结合第十二方面，在第十二方面的某些实现方式中，所述第一信息是所述第一终端设备在所述第一通信路径上建立第一QoS流中获取的。
结合第十二方面，在第十二方面的某些实现方式中，所述第一信息还包括所述第一通信路径上的第一QoS流信息，所述第一QoS流信息包括第二终端设备的标识、所述第一QoS流的标识QFI、所述第一QoS流对应的PDU会话的标识。
结合第十二方面，在第十二方面的某些实现方式中，所述第一信息还包括第三指示信息，所述第三指示信息用于指示进行可靠性传输或负载均衡传输。
结合第十二方面，在第十二方面的某些实现方式中，所述第一通信路径为所述第一终端设备通过所述第二终端设备连接所述第一网络设备的通信路径，或者，所述第一通信路径为所述第一终端设备直接连接所述第一网络设备的通信路径。
结合第十二方面，在第十二方面的某些实现方式中，所述第一通信路径包括至少一个QoS流，所述第一QoS流信息包括所述第一QoS流对应的PDR，所述第一QoS流为所述至少一个QoS流中的一个。
第十三方面，提供了一种数据传输的装置，该装置可以为第一网络设备，或者，也可以为配置于第一网络设备中的芯片或电路，本申请对此不作限定。
该装置包括：收发单元，用于接收第一信息和第二信息，所述第一信息用于所述第一网络设备通过第一通信路径向第一终端设备传输数据，所述第二信息用于所述第一网络设备通过第二通信路径向所述第一终端设备传输数据；该收发单元还用于：接收第一数据，通过所述第一通信路径和/或第二通信路径向所述第一终端设备发送所述第一数据。
结合第十三方面，在第十三方面的某些实现方式中，所述装置还包括处理单元，用于根据所述第一信息确定目的地址和源地址；根据所述目的地址和源地址对所述第一数据进 行处理，发送处理后的所述第一数据。
结合第十三方面，在第十三方面的某些实现方式中，所述第一通信路径为所述第一终端设备通过第二终端设备接收所述第一网络设备发送的数据的通信路径。
结合第十三方面，在第十三方面的某些实现方式中，所述收发单元还用于接收第三指示信息，所述第三指示信息用于指示进行可靠性传输或负载均衡传输。
结合第十三方面，在第十三方面的某些实现方式中，当所述第三指示信息指示可靠性传输，所述处理单元具体用于：将所述第一数据的IP包进行复制，所述收发单元具体用于：分别通过所述第一通信路径和所述第二通信路径向所述第一终端设备发送所述第一数据的IP包；或者，当所述第二指示信息指示负载均衡传输，所述处理单元具体用于：将所述第一数据的IP包进行分流，所述收发单元具体用于：分别通过所述第一通信路径和所述第二通信路径向所述第一终端设备发送所述第一数据的IP包。
结合第十三方面，在第十三方面的某些实现方式中，所述处理单元还用于：根据所述第三指示信息确定通过所述第一通信路径和/或第二通信路径向所述第一终端设备发送所述第一数据；或者，根据所述第一信息和所述第二信息确定通过所述第一通信路径和/或第二通信路径向所述第一终端设备发送所述第一数据。
结合第十三方面，在第十三方面的某些实现方式中，所述收发单元还用于将所述第一数据发送给第三网络设备，由所述第三网络设备通过所述第一通信路径发向所述第一终端设备。
结合第十三方面，在第十三方面的某些实现方式中，所述第一通信路径包括至少一个QoS流，所述第一QoS流信息包括所述第一QoS流对应的PDR，所述第一QoS流为所述至少一个QoS流中的一个，所述第二通信路径包括至少一个QoS流，所述第二QoS流信息包括所述第二QoS流对应的PDR，所述第人QoS流为所述至少一个QoS流中的一个。
结合第十三方面，在第十三方面的某些实现方式中，所述收发单元还用于：接收第一QoS流的标识QFI，将所述第一数据发送给第三网络设备，具体包括：所述收发单元将所述第一数据封装到GTP消息，通过第一通道将所述GTP消息发送至所述第三网络设备，所述GTP消息包括所述第一QoS流的标识QFI，所述第一通道用于所述第一网络设备和所述第三网络设备进行数据传输。
第十四方面，本申请提供了一种处理器，用于执行上述各方面提供的方法。
对于处理器所涉及的发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则可以理解为处理器输出和接收、输入等操作，也可以理解为由射频电路和天线所进行的发送和接收操作，本申请对此不做限定。
第十五方面，本申请提供了一种通信装置，该装置包括：存储器，用于存储程序；至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述任意一方面或其实现方式提供的方法。
在一种实现方式中，该装置为第一终端设备、第二终端设备、第一网络设备、第二网络设备。
在另一种实现方式中，该装置为用于第一终端设备、第二终端设备、第一网络设备或第二网络设备中的芯片、芯片系统或电路。
第十六方面，本申请提供了一种计算机可读存储介质，该计算机可读介质存储用于设 备执行的程序代码，该程序代码包括用于执行上述任意一方面或其实现方式提供的方法。
第十七方面，本申请提供了一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述任意一方面或其实现方式提供的方法。
第十八方面，本申请提供了一种芯片，芯片包括处理器与通信接口，处理器通过通信接口读取存储器上存储的指令，执行上述任意一方面或其实现方式提供的方法。
可选地，作为一种实现方式，芯片还包括存储器，存储器中存储有计算机程序或指令，处理器用于执行存储器上存储的计算机程序或指令，当计算机程序或指令被执行时，处理器用于执行上述任意一方面或其实现方式提供的方法。
第十九方面，本申请提供了通信系统，包括上文的第一终端设备、中继设备、第一移动性管理实体、第二移动性管理实体、第一会话管理功能实体、第二会话管理功能实体、第一用户面功能实体和第二用户面功能实体。
附图说明
图1示出了适用于本申请实施例的一种通信系统架构的示意图。
图2示出了适用于本申请实施例的一种通信系统的应用架构示意图。
图3示出了远端UE通过非直连路径进行用户面数据传输的一种协议栈架构。
图4示出了远端UE采用非直连路径传输方式进行用户面数据传输的示意性流程图。
图5示出了本申请实施例提供的一种数据传输的方法500的示意图。
图6示出了本申请实施例提供的远端UE的数据的传输路径的变化示意图。
图7示出了本申请实施例提供的一种数据传输的方法700的示意图。
图8示出了本申请实施例提供的UPF执行多路传输的方法的示意图。
图9示出了本申请实施例提供的一种数据传输的方法900的示意图。
图10示出了本申请实施例提供的一种数据传输的方法1000的示意图。
图11示出了本申请实施例提供的一种数据传输的方法1100的示意图。
图12示出了本申请实施例提供的一种数据传输的方法1200的示意流程图。
图13示出了本申请实施例提供的一种数据传输的方法1300的示意流程图。
图14示出了本申请实施例提供的一种数据传输的方法1400的示意图。
图15示出了本申请实施例提供的一种直连路径和非直连路径的关联及创建传输通道的方法流程图。
图16示出了本申请实施例提供的一种数据传输的装置1600的示意图。
图17示出了本申请实施例提供的一种数据传输的装置1700的示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请提供的技术方案可以应用于各种通信系统，例如：第五代(5th generation，5G)或新无线(new radio，NR)系统、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统。本申请提供的技术方案还可以应用于设备到设备(device to device，D2D)通信，车到万 物(vehicle-to-everything，V2X)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，以及物联网(internet of things，IoT)通信系统或者其他通信系统。
首先简单介绍适用于本申请的网络架构，如下。
作为示例，图1示出了一种网络架构的示意图。
如图1所示，该网络架构以5G系统(the 5th generation system，5GS)为例。该网络架构可以包括但不限于：网络切片选择功能(network slice selection function，NSSF)，认证服务器功能(authentication server function，AUSF)，统一数据管理(unified data management，UDM)，网络暴露功能(network exposure function，NEF)，网络存储功能(NF repository function，NRF)，策略控制功能(policy control function，PCF)，应用功能(application function，AF)，接入和移动性管理功能(access and mobility management function，AMF)，会话管理功能(session management function，SMF)，用户设备(user equipment，UE)，无线接入网设备，用户面功能(user plane function，UPF)，数据网络(data network，DN)。
其中，DN可以是互联网；NSSF、AUSF、UDM、NEF、NRF、PCF、AF、AMF、SMF、UPF属于核心网中的网元，由于图1以5G系统为例，那么该核心网可以称为5G核心网(5G core network，5GC或5GCN)。
下面对图1中示出的各网元做简单介绍。
1、UE(包括图1中的UE1和UE2)：可以称终端设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。
终端设备可以是一种向用户提供语音/数据的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜 等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，终端设备还可以是IoT系统中的终端设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。
需要指出的是，终端设备与接入网设备之间可以采用某种空口技术(如NR或LTE技术等)相互通信。终端设备与终端设备之间也可以采用某种空口技术(如NR或LTE技术等)相互通信。
本申请实施例中，用于实现终端设备的功能的装置可以是终端设备，也可以是能够支持终端设备实现该功能的装置，例如芯片系统或芯片，该装置可以被安装在终端设备中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
2、(无线)接入网((radio)access network，(R)AN)设备：可以为特定区域的授权用户提供接入通信网络的功能，具体可以包括第三代合作伙伴计划(3rd generation partnership project，3GPP)网络中无线网络设备也可以包括非3GPP(non-3GPP)网络中的接入点。下文为方便描述采用AN设备表示。
AN设备可以为采用不同的无线接入技术。目前的无线接入技术有两种类型：3GPP接入技术(例如，第三代(3rd generation，3G)、第四代(4th generation，4G)或5G系统中采用的无线接入技术)和非3GPP(non-3GPP)接入技术。3GPP接入技术是指符合3GPP标准规范的接入技术，例如，5G系统中的接入网设备称为下一代基站节点(next generation Node Base station，gNB)或者RAN设备。非3GPP接入技术可以包括以无线保真(wireless fidelity，WiFi)中的接入点(access point，AP)为代表的空口技术、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)、码分多址(code division multiple access，CDMA)等。AN设备可以允许终端设备和3GPP核心网之间采用非3GPP技术互连互通。
AN设备能够负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。AN设备为终端设备提供接入服务，进而完成控制信号和用户数据在终端设备和核心网之间的转发。
AN设备例如可以包括但不限于：宏基站、微基站(也称为小站)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(baseband unit，BBU)，WiFi系统中的AP、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G(如，NR)系统中的gNB或传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如分布式单元(distributed unit，DU)，或者下一代通信6G系统中的基站等。本申请实施例对AN设备所采用的具体技术和具体设备形态不做限定。
3、AMF：主要用于接入控制、移动性管理、附着与去附着等功能。
4、SMF：主要用于用户面网元选择，用户面网元重定向，终端设备的因特网协议 (internet protocol，IP)地址分配，以及会话的建立、修改和释放及QoS控制。
5、UPF：主要用于用户面数据的接收和转发。例如，UPF可以从DN接收用户面数据，并通过AN设备将用户面数据发送给终端设备。UPF还可以通过AN设备从终端设备接收用户面数据，并转发到DN。
6、NEF：主要用于安全地向外部开放由3GPP网络功能提供的业务和能力等。
7、PCF：主要用于指导网络行为的统一策略框架，为控制面网元(例如AMF，SMF等)提供策略规则信息等。
8、AF：主要用于向3GPP网络提供业务，如与PCF之间交互以进行策略控制等。
9、网络切片选择功能(network slice selection function，NSSF)：主要用于网络切片选择。
10、UDM：主要用于UE的签约数据管理，包括UE标识的存储和管理，UE的接入授权等。
11、DN：主要用于为UE提供数据服务的运营商网络。例如，因特网(Internet)、第三方的业务网络、IP多媒体服务业务(IP multi-media service，IMS)网络等。
12、AUSF：主要用于用户鉴权等。
13、NRF：主要用于保存网络功能实体以及其提供服务的描述信息等。
在图1所示的网络架构中，各网元之间可以接口通信。例如，UE2通过无线资源控制(radio resource control，RRC)协议与AN设备连接，UE和AN设备之间采用Uu接口进行通信。UE1和UE2之间采用PC5接口通信，PC5接口可以用于UE间互相发现、UE间进行数据和信令的传输。此外，在图1中，N1为UE2和AMF之间的接口，N2为(R)AN和AMF的接口，用于NAS消息的发送等；N3为RAN和UPF之间的接口，用于传输用户面的数据等；N4为SMF和UPF之间的接口，用于传输例如N3连接的通道标识信息，数据缓存指示信息，以及下行数据通知消息等信息；N6接口为UPF和DN之间的接口，用于传输用户面的数据等，N11接口为AMF和SMF之间的接口。
应理解，上述所示的网络架构仅是示例性说明，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
还应理解，图1中所示的AMF、SMF、UPF、PCF、UDM、NSSF、AUSF等功能或者网元，可以理解为用于实现不同功能的网元，例如可以按需组合成网络切片。这些网元可以各自独立的设备，也可以集成于同一设备中实现不同的功能，或者可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能，本申请对于上述网元的具体形态不作限定。
还应理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在6G网络以及未来其它的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。为便于理解本申请实施例，对本申请中涉及到的术语做简单说明。
1、直连路径(direct path)：终端设备直接接入接入网设备，即在该直连路径中，终端设备与接入网设备之间直接建立连接并进行通信，不经过其他设备(例如，中继设备)。
应理解，在直连路径中，终端设备直接接入接入网设备之后，经过接入网设备和核心网设备与数据网络进行数据传输。
直连路径，也可以称为直连链路(link)。
2、非直连路径(indirect path)：终端设备通过中继设备接入接入网设备，即在该非直连路径中，终端设备和接入网设备之间通过一个或多个中继设备建立连接并进行通信。例如，中继设备为中继(relay)UE，终端设备为远端(remote)UE，在这种情况下，远端UE与中继UE建立连接，中继UE与RAN建立连接，从而远端UE可以通过中继UE与RAN建立连接。
应理解，在非直连路径中，终端设备通过中继设备接入接入网设备之后，经过中继设备、接入网设备和核心网设备与数据网络进行数据传输。
需要说明的是，在非直连路径中，终端设备和中继设备之间的连接方式可以是3GPP中的连接方式，例如，邻近服务通信5(proximity-based services communication 5，PC5)连接，也可以是短距离通信技术中连接方式，例如，蓝牙连接、WiFi连接等。此外，当非直连路径上包括多个中继设备时，终端设备与中继设备之间的连接方法与任意两个中继设备之间的连接方式可以相同，也可以不同。
非直连路径，也可以称为非直连链路(link)。
3、协议数据单元(protocol data unit，PDU)会话(PDU session)：5G核心网(5G core network，5GC)支持PDU连接业务。PDU连接业务可以是指终端设备与DN之间交换PDU数据包的业务。PDU连接业务通过终端设备发起PDU会话的建立来实现。一个PDU会话建立后，也就是建立了一条终端设备和DN的数据传输通道。换句话说，PDU会话是UE级别的。每个终端设备可以建立一个或多个PDU会话。
如前所述，SMF主要用于负责移动网络中的会话管理。PDU会话在终端设备和SMF之间可以通过NAS会话管理(session management，SM)信令进行建立、修改或释放。
在本申请实施例中，一个PDU会话可以通过一个PDU会话标识(PDU session identifier，PDU session ID)来标识。
4、服务质量(quality of service，QoS)流(flow)：PDU会话中的QoS区分粒度。一个QoS流标识(QoS flow identifier，QFI)可用于标识一个QoS流。一个PDU会话中可以包括多个QoS流，每个QoS流的QFI是不同的。换言之，一个QFI在一个PDU会话中可以是唯一的。
进一步地，业务对应的QoS流：可以指的是用于传输该业务的数据的QoS流。例如，当通过PDU会中的QoS流传输该业务的数据时，该QoS流可以称之为是该业务对应的QoS流。QoS流承载的业务：可以指的是通过该QoS流传输的业务。
进一步地，QoS流的QoS需求：可以指的是QoS流所对应的QoS参数所需要满足的条件。QoS参数可以包括但不限于：速率、时延、丢包率、优先级、可靠性，等。举例来说，QoS流所对应的QoS需求是：QoS流所对应的QoS参数中的速率需要满足7兆比特每秒(Mbps)，即大于或等于7Mbps。
5、可靠性传输：终端设备和网络设备之间通过直连路径和非直连路径同时进行数据传输时，网络设备将下行数据进行复制，分别通过直连路径和非直连路径进行传输，从而保证终端设备接收到数据，即为可靠性传输。
6、负载均衡传输：终端设备和网络设备之间通过直连路径和非直连路径同时进行数据传输时，网络设备将下行数据分为两个数据包，分别通过直连路径和非直连路径进行传 输，从而均衡两条路径的负载，即为负载均衡传输。
图2示出了本申请实施例的一种通信系统的应用架构的示意图。如图2所示，该网络架构是在图1所示的基础架构上，3GPP标准提供的一个UE(例如，远端(remote)UE)通过另一个UE(例如，中继(relay)UE)接入网络的方案。在图2中，远端UE可以直接接入网络，具体来说，包括先直接接入AN，通过AN接入核心网(5GC包括远端UE的AMF、远端UE的SMF和远端UE的UPF)，并与核心网和DN进行信令和数据传输，这种传输方式可以称为直接路径(direct path)传输方式。远端UE还可以通过中继UE接入网络，具体来说，包括：先通过中继UE接入AN，再通过AN接入核心网，然后与远端UE的核心网和DN进行信令和数据传输，这种传输方式可以称为间接路径(indirect path)传输方式。
应理解，图2中的中继UE为层3用户设备到网络中继(layer-3 UE-to-network relay)。
图3示出了远端UE采用非直连路径传输方式进行用户面数据传输时的一种协议栈架构。如图3所示，协议数据单元(protocol data unit，PDU)层(layer)用于在远端UE和UPF之间传递应用软件(applicable soft，APP)产生的数据。业务数据适配协议(service data adaptation protocol，SDAP)层用于进行服务质量(quality of service，QoS)流(flow)和数据无线承载(data radio bearer，DRB)之间的映射。应理解，QoS流是UE与UPF间具有QoS保证的数据传输通道。QoS流由UE与NG-RAN之间的DRB、NG-RAN与UPF间的N3连接2部分组成。一个或多个QoS流可以共用一个DRB连接，SDAP用于将QoS流映射到DRB。DRB由分组数据汇聚层协议(packet data convergence protocol，PDCP)层和无线链路控制(radio link control，RLC)层这2层组成。其中，PDCP层用于进行用户面数据的报头压缩、解压缩、加密/解密、完整性保护、完整性验证等功能，PDCP层由RRC消息进行配置。
媒体接入控制(mediu access control，MAC)用于进行逻辑信道和传输信道之间的映射，并将来自不同逻辑信道的MAC数据复合到一个传输块。PHY为物理层(physical layer，PHY)。适配(adaptation)层用于中继UE或NG-RAN指示包含在中继UE的RLC中的数据包是属于哪个remote UE的，以及是属于远端UE的哪个无线承载的。
通用分组无线业务(general packet radio service，GPRS)通道传输协议-用户面(tunnel protocol-user，GTP-U)是一组基于IP的高层协议，位于传输控制协议/网际协议(transmission control protocol/internet protocol，TCP/IP)、用户数据报协议/网际协议(user data protocol，UDP/IP)之上。GTP-U消息用于在GTP-U体之间承载用户数据。L2表示层2(layer 2)，L2表示层1(layer 1)。
如图3所示，从NG-RAN的角度来看，远端UE的DRB由2部分组成：NG-RAN与远端UE之间的PDCP层，以及NG-RAN与中继UE间的RLC层。从远端UE的角度来看，远端UE的DRB由2部分组成：NG-RAN与远端UE之间的PDCP层，以及NG-RAN与中继UE间的RLC层。
具体地，上行数据的传输过程为：远端UE的APP层产生数据，远端UE在PDU层将数据映射到QoS流，并向Uu-SDAP层发送数据，该数据包括QoS流标识，远端UE在Uu SDAP层根据QoS流标识将QoS流映射到DRB，并将QoS流的数据发送给DRB对应的Uu PDCP层。远端UE将Uu PDCP层的数据发送给PC5接口的协议栈进行处理，并通 过PC5接口发送给中继UE。中继UE解析得到远端UE的Uu PDCP的数据。中继UE通过与NG-RAN的Uu接口将数据发送给NG-RAN。NG-RAN接收到数据后，使用远端UE的上下文解析出远端UE的数据，NG-RAN通过与UPF间的N3接口将远端UE的数据发送给UPF。
类似地，下行数据的传输过程为：NG-RAN接收到UPF发送给远端UE的数据，根据远端UE的上下文确定远端UE使用中继UE进行数据传输。中继UE解析出数据后，通过中继UE与远端UE的PC5接口将数据发送给远端UE，远端UE进行数据解析。
图4示出了远端UE采用非直接路径传输方式进行用户面数据传输的示意性流程图。如图4所示，该方法400包括以下步骤。
S410，运营商网络分布对中继UE和远端UE进行中继相关业务的授权认证和信息提供。
S420，可选地，中继UE建立PDU会话。
S430，远端UE上的APP启动，通过URSP确定该APP可使用layer 2 relay业务，则远端UE执行中继UE发现程序，并选定中继UE。
S440，远端UE选择中继UE并与中继UE建立连接，中继UE根据RSC和PDU会话参数的对应关系，确定是否需要新建PDU会话。
S450，中继UE执行IP router功能，并为远端UE分配IP地址。
S460，远端UE若有特殊QoS需求，则远端UE可请求新建/修改QoS flow；远端UE向中继UE发送修改请求消息，携带PC5 QoS参数，中继UE本地将PC5 QoS参数映射成Uu QoS参数，并判断是否需新建QoS flow，若需要则发起新建QoS flow的过程。
S470，中继UE向SMF报告远端UE的信息，包括Remote User ID,Remote UE info。
连接建立完成之后，远端UE的数据经过UPF、NG-RAN和中继UE进行转发。
在目前的数据传输中，远端UE使用某种固定的路径(直连路径或非直连路径)来传输业务的数据，例如，若终端设备确定传输路径为直连路径，则终端设备向接入网设备发起PDU会话请求，建立直连路径的PDU会话和QoS流，此后，终端设备通过直连路径的QoS流与数据网络传输数据。或者，若终端设备确定传输路径为非直连路径，则终端设备通过中继设备向接入网设备发起PDU会话请求，建立非直连路径的PDU会话和QoS流，此后，终端设备通过非直连路径的QoS流与数据网络传输数据。这种传输方式无法动态地满足业务的传输需求，例如，时延或通信质量或通信容量等。
本申请提供一种数据传输的方法和装置，使得终端设备和数据网络之间的数据传输路径具有多样性，例如可以同时通过直连路径和非直连路径传输数据，能够动态地满足业务需求，例如，提升传输速率或保证数据传输的可靠性。
图5是本申请实施例提供的一种数据传输的方法500的示意图。方法500可以包括如下步骤。
S510，第一终端设备获取第一信息。
具体地，第一终端设备可以是远端UE的一例。
其中，第一信息包括第一通信路径的第一QoS流信息，该第一信息用于第一网络设备通过第一通信路径向第一终端设备传输第一数据。
具体地，第一网络设备可以是UPF，第一数据可以是UPF接收的下行传输数据。
作为一种示例，第一通信路径为非直连路径，第二通信路径为直连路径。第一终端设备获取该非直连路径的第一QoS流信息，该第一QoS流信息用于第一网络设备通过非直连路径向第一终端设备传输第一数据。
一种可能的实施方式中，第一终端设备通过非直连路径获取该非直连路径的第一QoS流信息。该非直连路路径可以理解为第一终端设备通过第二终端设备接入网络设备。该第二终端设备可以是中继UE的一例。
例如，第一终端设备通过PC5接口向第二终端设备发送第一请求消息，第一请求消息用于请求在非直连路径上建立第一QoS流；所述第一请求消息包括第二指示信息，所述第二指示信息用于获取所述第一信息；相应地，第二终端设备在非直连路径上建立第一QoS流，并根据第二指示信息通过PC5接口向第一终端设备发送第一信息。也即，第一终端设备从第二终端设备接收第一信息。
示例性的，该第一请求消息可以是“link modification request(连接修改请求)消息”。
示例性的，该第一请求消息也可以是独立的请求消息。
可以理解，第二通信路径为直连路径，该直连路径可以理解为第一终端设备直接接入网络设备的路径，第一终端设备在该直连路径上建立第二QoS流，获取第二信息，第二信息包括第二QoS流的信息。但应理解，第一终端设备直接接入网络设备，指的是不需要通过中继UE的转发，与网络设备进行数据传输，实际上可能存在其他网元的中转，本申请实施例在此不作限定。
其中，该第一请求消息还可以包括如“request PC5 QoS rule(PC5 QoS规则请求)”和“request PC5 QoS参数(PC5 QoS参数请求)”，该“request PC5 QoS rule”中的“packet filter(数据包过滤)”的目的地址为第二QoS流的QoS规则的数据包过滤的目的地地址，该“request PC5 QoS参数(PC5 QoS参数请求)与第二QoS流的QoS参数相同。
示例性的，该第一信息可以包括第一QoS流对应的包检测规则PDR，还可以包括新建的第一QoS流的PC5 QoS参数和PC5 QoS rule。
应理解，第一QoS流对应的包检测规则PDR也可以理解为PDR对应的数据包过滤，或者是PDR对应的数据包过滤的目的地址(IP地址和端口号)。
示例性的，该第一信息可以包括第二终端设备的标识、所述第一QoS流的标识QFI-1、所述第一QoS流对应的PDU会话的标识。
其中，第二终端设备的标识(Relay UE ID)可以是GUTI(Globally Unique Temporary UE Identity，全球唯一临时UE标识)或S-TMSI(Serving-Temporary Mobile Subscriber Identity，临时移动用户标识)。
示例性的，第二终端设备可以通过“link modification accept(连接修改接收)消息”发送该第一信息。
示例性的，第二指示信息可以是“paired QoS flow(关联QoS流)指示”，第二终端设备根据该paired QoS flow(关联QoS流)指示”可以将新建的第一QoS流的相关信息发送给第一终端设备。
作为又一种示例，第一通信路径为直连路径，第二通信路径为非直连路径。第一终端设备获取该直连路径的第一QoS流信息，该第一QoS流信息用于第一网络设备通过直连路径向第一终端设备传输第一数据。
一种可能的实施方式中，第一终端设备通过建立直连路径并在建立过程中获取该直连路径的第一QoS流信息。该直连路径可以理解为第一终端设备直接接入网络设备的路径，但应该理解，第一终端设备直接接入网络设备，指的是不需要通过中继UE的转发与网络设备进行数据传输，实际上可能存在其他网元的中转，本申请实施例在此不作限定。
例如，第一终端设备触发直连路径的建立，并在直连路径上建立第一QoS流，获取第一信息。
示例性的，该第一信息包括直连路径上的第一QoS流对应的包检测规则PDR，还可以包括新建的第一QoS流的PC5 QoS参数和PC5 QoS rule。
示例性的，该第一信息可以包括第二终端设备的标识、所述第一QoS流的标识QFI-1、所述第一QoS流对应的PDU会话的标识，还可以包括新建的第一QoS流的PC5 QoS参数和PC5 QoS rule。
S520，第一终端设备向第二网络设备发送第一消息。
具体的，第一终端设备通过第二通信路径向第二网络设备发送第一消息。该第一消息包括第一信息和第一指示信息，第一指示信息用于指示通过第一通信路径和/或第二通信路径传输所述第一数据。
其中，第二网络设备是核心网网元的一例。例如，可以是AMF，SMF。
相应地，第二网络设备从第一终端设备接收该第一消息。
作为一种示例，第一通信路径为非直连路径，第二通信路径为直连路径。第一终端设备获取了非直连路径的第一QoS流的信息后，通过直连路径向第一AMF(第一终端设备的AMF)发送第一消息，并在第一消息中携带第一信息和第一指示信息，第一指示信息用于指示通过第一通信路径和/或第二通信路径传输所述第一数据。
示例性的，该第一消息也可以是独立的通知消息。
示例性的，该第一消息可以是PDU会话修改请求消息或PDU会话建立请求消息等非接入层(non-access stratum，NAS)消息。
例如，第一终端设备通过直连路径的uu接口向第一AMF发送PDU会话修改请求消息，在该请求消息中携带第一信息和第一指示信息，该PDU会话修改请求消息用于请求对直连路径的第二QoS流进行修改。
示例性的，该第一信息包括第一QoS流对应的包检测规则PDR，还可以包括新建的第一QoS流的PC5 QoS参数和PC5 QoS rule。
示例性的，该第一信息包括第二终端设备的标识、所述第一QoS流的标识QFI-1、所述第一QoS流对应的PDU会话的标识。
其中，第二终端设备的标识(Relay UE ID)可以是GUTI或S-TMSI。
示例性的，该第一指示信息可以是“paired QoS flow(关联QoS流)指示”。
需要说明的是，第一指示信息和第二指示信息都可以是“paired QoS flow(关联QoS流)指示”，但第二指示信息为PC5接口的信息，第一指示信息为Uu接口发送的信息，因此通信接口的表现形式可能不同，本申请实施例对此不作限定。
可选的，第一消息还可以携带第三指示信息，该第三指示信息用于指示进行可靠性传输或负载均衡传输。
示例性的，该第三指示信息可以是“multi path rule(多路径规则)”。
例如，在“multi path rule(多路径规则)”中包括可靠性传输指示或负载均衡传输指示。
其中，第一指示信息用于指示通过第一通信路径和第二通信路径传输第一数据，可以理解为，下行传输的数据可以通过直连路径和非直连路径同时向远端UE传输，从而可以提高数据传输的效率，保证数据传输的可靠性。
其中，当仅通过第一通信路径或第二通信路径传输第一数据，可以理解为，远端UE和DN间有直连路径或非直连路径两条路径可以用来传输下行数据，可以任意选择或者根据传输需求选择直连路径或非直连路径进行下行数据的传输，提高了数据传输的灵活性。
作为又一种示例，第一通信路径为直连路径，第二通信路径为非直连路径。第一终端设备获取直连路径的第一QoS流的信息后，通过非直连路径向第二AMF(第二终端设备的AMF)发送第一消息，并在第一消息中携带第一信息和第一指示信息，第一指示信息用于指示通过第一通信路径和/或第二通信路径传输所述第一数据。
示例性的，该第一消息也可以是独立的通知消息。
示例性的，该第一消息可以是PDU会话修改请求消息或PDU会话建立请求消息等非接入层(non-access stratum，NAS)消息。
例如，第一终端设备通过非直连路径的PC5接口发送连接修改请求消息给第二终端设备，在该请求消息中携带第一信息和第一指示信息，该连接修改请求消息用于请求对非直连路径的第二QoS流进行修改。通过第二终端设备向第二AMF发送PDU会话修改请求消息，在该请求消息中携带第一信息和第一指示信息，该PDU会话修改请求消息用于请求对非直连路径的第二QoS流进行修改。
示例性的，该第一信息包括第一QoS流对应的包检测规则PDR，还可以包括新建的第一QoS流的PC5 QoS参数和PC5 QoS rule。
示例性的，该第一信息包括第二终端设备的标识、所述第一QoS流的标识QFI-1、所述第一QoS流对应的PDU会话的标识。
其中，第二终端设备的标识(Relay UE ID)可以是GUTI或S-TMSI。
示例性的，该第一指示信息可以是“paired QoS flow(关联QoS流)指示”。
需要说明的是，第一指示信息和第二指示信息都可以是“paired QoS flow(关联QoS流)指示”，但第二指示信息为PC5接口的信息，第一指示信息为Uu接口发送的信息，因此通信接口的表现形式可能不同，本申请实施例对此不作限定。
可选的，第一消息还可以携带第三指示信息，该第三指示信息用于指示进行可靠性传输或负载均衡传输。
示例性的，该第三指示信息可以是“multi path rule(多路径规则)”。
例如，在“multi path rule(多路径规则)”中包括可靠性传输指示或负载均衡传输指示。
S530，第二网络设备向第一网络设备发送第一信息和第二信息。
具体地，第二网络设备通过第二通信路径向第一网络设备发送第一信息和第二信息。该第一信息包括第一通信路径的第一QoS流信息，该第二信息包括第二通信路径的第二QoS流信息，第一QoS流信息用于第一网络设备通过第一通信路径向第一终端设备传输下行数据，第二QoS流信息用于第一网络设备通过第二通信路径向第一终端设备传输下 行数据。
其中，第一网络设备可以是第一通信路径的第一UPF，也可以是第二通信路径的第二UPF，第一UPF和第二UPF可以是同一个UPF，也可以是不同的UPF。
作为一种示例，第一通信路径为非直连路径，第二通信路径为直连路径。第一AMF从第一终端设备接收第一消息(PDU会话修改请求消息)后，发送给第一SMF(第一终端设备的SMF)，该第一SMF根据PDU会话修改请求消息携带的第一信息和第一指示信息对直连路径的第二QoS流进行修改，向第一UPF发送第一信息和第二信息。
示例性的，该第一信息包括非直连路径上的第一QoS流对应的包检测规则PDR，第二信息包括直连路径上的第二QoS流对应的PDR。
可选的，第一消息还可以携带第三指示信息，第一终端设备可以通过第二网络设备向第一网络设备发送第三指示信息，该第三指示信息用于指示第一网络设备进行可靠性传输或负载均衡传输。
可选的，第三指示信息也可以携带在第二QoS流对应的PDR中，本申请实施例对此不作限定。
一种可能的实施方式中，对第二QoS流对应的包检测规则PDR可以新增Multi-Path Rule ID字段，具体的，在该字段对应的Multi-Path Rule中包含多路协同传输指示以及创建外部IP报头(Outer IP header creation)指示。
作为又一种示例，第一通信路径为直连路径，第二通信路径为非直连路径。第二AMF通过第二终端设备从第一终端设备接收第一消息(PDU会话修改请求消息)后，发送给第二SMF(第二终端设备的SMF)，该第二SMF根据PDU会话修改请求消息携带的第一信息和第一指示信息对第二QoS流进行修改，向第一UPF发送第一信息和第二信息。
示例性的，该第一信息包括直连路径上的第一QoS流对应的包检测规则PDR，第二信息包括非直连路径上的第二QoS流对应的PDR。
可选的，第一消息还可以携带第三指示信息，第一终端设备可以通过第二网络设备向第一网络设备发送第三指示信息，该第三指示信息用于指示第一网络设备进行可靠性传输或负载均衡传输。
可选的，第三指示信息也可以携带在第二QoS流对应的PDR中，本申请实施例对此不作限定。
一种可能的实施方式中，对第二QoS流对应的包检测规则PDR可以新增Multi-Path Rule ID字段，具体的，在该字段对应的Multi-Path Rule中包含多路协同传输指示以及创建外部IP报头(Outer IP header creation)指示。
作为又一种示例，第一通信路径为非直连路径，第二通信路径为直连路径。第一AMF向第二AMF发送第一消息，通过第二AMF获取第二UPF的地址和第一QoS流对应的PDR，发送给第一SMF(第一终端设备的SMF)，该第一SMF根据第一消息携带的第一信息和第一指示信息对第二QoS流进行修改，向第一UPF发送第一信息和第二信息。
示例性的，该第一信息包括非直连路径上的第一QoS流对应的包检测规则PDR，第二信息包括直连路径上的第二QoS流对应的PDR。
可选的，第一SMF还可以向第一UPF发送第三指示信息，该第三指示信息用于指示第一网络设备进行可靠性传输或负载均衡传输。
一种可能的实施方式中，对第二QoS流对应的包检测规则PDR可以新增Multi-Path Rule ID字段，具体的，在该字段对应的Multi-Path Rule中包含多路协同传输指示、创建外部IP报头(Outer IP header creation)指示以及CN通道信息(CN tunnel info)。
作为又一种示例，第一通信路径为直连路径，第二通信路径为非直连路径。第二AMF通过第二终端设备接收第一消息，并向第一AMF发送第一消息，通过第一AMF获取第一UPF的地址和直连路径的第一QoS流对应的PDR，发送给第二SMF(第二终端设备的SMF)，该第二SMF根据第一消息携带的第一信息和第一指示信息对非直连路径的第二QoS流进行修改，向第二UPF发送第一信息和第二信息。
示例性的，该第一信息包括直连路径上的第一QoS流对应的包检测规则PDR，第二信息包括非直连路径上的第二QoS流对应的PDR。
可选的，第二SMF还可以向第二UPF发送第三指示信息，该第三指示信息用于指示第一网络设备进行可靠性传输或负载均衡传输。
一种可能的实施方式中，对第二QoS流对应的包检测规则PDR可以新增Multi-Path Rule ID字段，具体的，在该字段对应的Multi-Path Rule中包含多路协同传输指示、创建外部IP报头(Outer IP header creation)指示以及CN通道信息(CN tunnel info)。
S540，第一网络设备确定执行多路传输。
具体地，第一网络设备接收第一信息和第二信息，第一网络设备接收第一数据，根据第一信息和第二信息确定对第一数据执行多路传输。
具体进行多路传输的过程见下文具体实施例。
可选的，第一网络设备接收第三指示信息，根据第三指示信息确定对第一数据执行多路传输，并且确定具体执行可靠性传输或负载均衡传输。
需要注意的是，当第一UPF和第二UPF不同时，第一网络设备在进行可靠性传输或负载均衡传输时需要将数据传输给第三网络设备，由第三网络设备通过非直连路径将数据传输给终端设备。其中，第三网络设备可以是第一UPF，也可以是第二UPF。
图6示出了本申请实施例提供的远端UE的数据的传输路径的变化示意图。其中，图6(a)为远端UE的非直连路径和直连路径连接到同一个UPF的示意图，图6(b)为远端UE的非直连路径和直连路径连接到不同UPF的示意图，以下以第一网络设备为第一UPF为例，第三网络设备为第二UPF为例。
其中，图6(a)是经过S510至S540之后远端UE的数据的传输路径的示意图，如图6(a)所示，远端UE的直连路径和非直连路径连接UPF#1(第一UPF的一例)，即，第一网络设备和第三网络设备是同一个网络设备。
其中，图6(b)是经过S510至S540之后远端UE的数据的传输路径的示意图，如图6(b)所示，远端UE的直连路径连接UPF#1(第一UPF的一例)，远端UE的非直连路径连接UPF#2(第二UPF的一例)，即，第一网络设备和第三网络设备两个不同的网络设备。
需要说明的是，方法500所示实施例的各个实施场景可以单独实施，也可以相互结合，不予限制。
图7是本申请实施例提供的一种数据传输的方法700的示意图。方法700可以视为方法500的一种具体实现方式，该方法700可以包括如下步骤。
S710，远端UE在直连路径上建立PDU会话#1和QoS流#1。
具体地，远端UE在直连路径上发起建立PDU会话#1的建立，从而可以实现远端UE和DN之间的数据传输。其中，PDU会话#1包括QoS流#1(第二QoS流的一例)。
该QoS流#1的标识可以是QFI-1。
可以理解，远端UE在建立该QoS流#1过程中可以获取QoS流信息#2，该QoS流信息#2包括QoS流#1的标识信息QFI-1及QFI-1对应的PDR。
S720，远端UE通过非直连路径向中继UE发送请求消息#1(第一请求消息的一例)。
具体地，远端UE根据数据传输需求确定需要建立非直连路径，从而同时使用非直连路径和直连路径进行多路传输，例如需要进行可靠性传输或负载均衡传输。
具体地，远端UE通过PC5接口向中继UE发送请求消息#1(第一请求消息的一例)，该请求消息#1用于请求在非直连路径上建立QoS流#2(第一QoS流的一例)。
该QoS流#2的标识可以是QFI-2。
该请求消息#1包括指示信息#1(第二指示信息的一例)，该指示信息#1用于获取QoS流信息#1(第一信息的一例)，该QoS流信息#1包括QoS流#2的标识信息QFI-2及QFI-2对应的PDR。
该请求消息#1还包括“request PC5 QoS rule”和“request PC5 QoS参数”。其中，request PC5 QoS rule”中的数据包过滤的目的地址和QFI-1的QoS rule的数据包过滤的目的地址相同；“request PC5 QoS参数”和QoS流#1的QoS参数相同。
可以理解，远端UE可以在直连路径上获取QoS流#1的QoS流信息#2(第三信息的一例)。其中，该QoS流信息#2包括QFI-1的QoS rule和QoS参数。
示例性的，该请求消息#1可以是连接修改请求(link modification request)消息。
示例性的，该指示信息#1可以是关联QoS流(paired QoS flow)指示信息。
S730，中继UE向SMF#2发送请求消息#2。
具体地，中继UE向AMF#2发送请求消息#2，AMF#2向SMF#2(第二网络设备的一例)发送请求消息#2，该请求消息#2包括上述指示信息#1，该请求消息#2还包括“request QoS rule”和“request QoS参数”。相应的，SMF#2根据该请求消息#2在非直连路径上建立QoS流#2。
其中，请求消息#2中的“request QoS rule”和“request QoS参数”是中继UE根据远端UE的“request PC5 QoS rule”和“request PC5 QoS参数”确定的。
示例性的，该请求消息#2可以是PDU会话建立请求(PDU session establish request)消息。
示例性的，该中继UE可以通过UL NAS消息发送请求消息#2给AMF#2。
示例性的，AMF#2可以通过N11消息向SMF#2发送请求消息#2，该N11消息可以是PDU会话创建上下文请求(Nsmf_PDUsession_createSMcontext request)消息等。
AMF#2和SMF#2是为中继UE服务的网络设备。
S740，SMF#2向中继UE发送响应消息#1。
具体地，SMF#2通过AMF#2向中继UE发送响应消息#1。
具体地，该响应消息#1用于响应上述请求消息#2。
示例性的，该响应消息#1可以是PDU会话建立接收(PDU session establish accept) 消息。
示例性的，具体地，SMF#2可以先向AMF#2发送N11消息，该N11消息包括N1 SM container和N2 SM container，该N1 SM container包括响应消息#1，该N2 SM container包括QoS流信息#1、QoS rule和QoS参数，其中，该N11消息可以是N1N2消息传递(Namf_communication_N1N2MessageTransfer)消息。
该QoS流信息#1包括QoS流#2的标识信息QFI-2及QFI-2对应的PDR。
应理解，SMF#2根据指示信息#1向中继UE发送所述QFI-2对应的PDR。
S750，中继UE通过非直连路径向远端UE发送响应消息#2。
具体地，中继UE通过PC5接口向远端UE发送响应消息#2，该响应消息#2包括QoS流信息#1(第一信息的一例)、PC5 QoS rule和PC5 QoS参数。
该QoS流信息#1包括QoS流#2的标识信息QFI-2及QFI-2对应的PDR。
示例性的，该响应消息#2可以是连接修改接收(link modification accept)消息。
可以理解，中继UE根据响应消息#1中包括的QoS rule生成PC5 QoS rule，根据响应消息#1中包括的QoS参数生成PC5 QoS参数。
S760，远端UE通过直连路径向SMF#1发送请求消息#3(第一消息的一例)。
具体地，远端UE在请求消息#3中携带QoS流信息#1和指示信息#2。
该请求消息#3用于请求SMF#1对QoS流#1进行修改，这里的修改可以理解为，对QoS流#1对应的QoS参数进行修改，即，增加QoS流信息#1中包括的QoS流#2的QoS参数，具体地，可以理解为增加QFI-2对应的PDR。
示例性的，该请求消息#3可以是PDU会话修改请求(PDU session modification request)消息。
可选的，该请求消息#3还可以携带指示信息#3(第三指示信息的一例)。
该指示信息#3用于指示网络设备(UPF#1)进行可靠性传输或负载均衡传输。
S770，SMF#1向UPF#1发送请求消息#4。
具体地，SMF#1在该请求消息#4中携带QoS流信息#1和QoS流信息#2。
可选的，该请求消息#4还可以携带指示信息#3(第三指示信息的一例)。
该指示信息#3用于指示网络设备(UPF#1)进行可靠性传输或负载均衡传输。
示例性的，该请求消息#4可以是N4修改请求消息。
S780，UPF#1根据请求消息#4确定执行多路传输。
具体地，UPF#1根据请求消息#4确定QFI-2对应的PDR和QFI-1对应的PDR，进一步确定执行多路传输。
可选的，当请求消息#4中包括指示信息#3，UPF#1可以根据该指示信息#3确定具体执行可靠性传输或执行负载均衡传输。
图8是本申请实施例提供的UPF执行多路传输的方法的示意图。该方法800是方法700中执行步骤S780后UPF#1向远端UE执行多路传输的具体方法说明。
如图8所示，图8(a)示出了远端UE的非直连路径和直连路径连接到不同UPF的示意图，如8(b)为远端UE的非直连路径和直连路径连接到同一个UPF的示意图。其中，直连路径上建立QoS流#1，非直连路径上建立QoS流#2。
具体的，如图8(a)所示，远端UE的直连路径连接UPF#1(第一UPF的一例)， 远端UE的非直连路径连接UPF#2。具体执行多路传输包括以下步骤：
a：UPF#1接收到APP服务器发送的下行数据时，UPF#1根据指示信息#3确定执行可靠性传输时，需要将下行IP包进行复制；当确定执行负载均衡传输时，需要将IP包进行分流。该下行数据包包括目的地址QoS流#1的外网地址IP-5和源地址APP服务器的地址IP-6。
b：在直连路径上，UPF#1需要IP-5翻译成QoS流#1对应的内网地址IP1，因此UPF#1向远端UE发送的数据包包括目的地址IP-1和源地址IP6。
c：在非直连路径上，UPF#1需要在现有IP包添加IP头，目的地址为QoS流#2对应的PDR的packet filter的目的地址，源地址不变，因此，需要添加的IP头包括QoS流#2对应的外网IP和源地址，UPF#1向UPF#2路由的数据包包括IP-4和IP6，IP-1和IP6。
需要说明的是，UPF#1向UPF#2发送的数据包也可以不添加IP头(IP-4和IP6)，由UPF#2自己添加该IP头。
d：UPF#2将QoS流#2对应的外网IP翻译成QoS流#2对应的内网地址IP-3，UPF#2根据该内网地址将数据包路由给中继UE，该数据包包括IP-3和IP-6，IP-1和IP-6。
e：中继UE根据PC5 QoS rule路由给远端UE。
f：远端UE根据方法700中的步骤S720的记录，确定为多路协同传输，则需要去掉外层IP头，得到的IP包包括目的地址IP-1和源地址IP6。进而将该IP包发给APP客户端，由APP客户端进行去重、重排序等IP层处理，从而保证可靠性。
具体的，如图8(b)所示，远端UE的直连路径和非直连路径连接UPF#1，与图8(a)所述的方法不同之处在于，具体执行多路传输时，UPF#1无需将数据包路由给UPF#2，直接路由给中继UE，其他步骤与图8(a)所述的步骤基本相同，在此不进行赘述。
表1(a)和表1(b)分别示出了本申请实施例提供的多路传输方法相关特征信息的英文和对应的中文释义。
表1(a)
Figure PCTCN2022109557-appb-000001
Figure PCTCN2022109557-appb-000002
表1(b)
Figure PCTCN2022109557-appb-000003
Figure PCTCN2022109557-appb-000004
表2(a)和表2(b)分别示出了“Multi-Path Rule”多路径传输规则的特征信息的英文和对应的中文释义。
表2(a)
Figure PCTCN2022109557-appb-000005
Figure PCTCN2022109557-appb-000006
表2(b)
Figure PCTCN2022109557-appb-000007
图9是本申请实施例提供的一种数据传输的方法900的示意图。方法900可以视为方法500的一种具体实现方式，该方法900可以包括如下步骤。
S910，远端UE触发中继UE在非直连路径上建立PDU会话#2和QoS流#2。
具体地，远端UE通过PC5接口在非直连路径上触发中继UE建立PDU会话#2，从而可以实现远端UE和DN之间的数据传输。其中，PDU会话#2包括QoS流#2(第二QoS流的一例)。
该QoS流#2的标识可以是QFI-2。
可以理解，远端UE在触发建立该QoS流#2过程中可以获取QoS流信息#1，该QoS流信息#1包括QoS流#2的标识信息QFI-2及QFI-2对应的PDR。
S920，远端UE向SMF#1发送请求消息#5。
具体地，远端UE根据数据传输需求确定需要建立直连路径，从而同时使用非直连路径和直连路径进行多路传输，例如需要进行可靠性传输或负载均衡传输。
具体地，远端UE向AMF#1发送请求消息#5，AMF#1向SMF#1发送请求消息#5，该请求消息#5用于请求在直连路径上建立QoS流#1(第一QoS流的一例)。
该QoS流#1的标识可以是QFI-1。
该请求消息#5包括指示信息#1(第三指示的一例)，该指示信息#1用于获取QoS流信息#2(第一信息的一例)，该QoS流信息#2包括QoS流#1的标识信息QFI-1及QFI-1对应的PDR。
该请求消息#5还包括“request QoS rule”和“request QoS参数”。其中，request QoS  rule”中的数据包过滤的目的地址和QFI-2的QoS rule的数据包过滤的目的地址相同；“request QoS参数”和QoS流#2的QoS参数相同。
示例性的，该请求消息#5可以是PDU会话修改请求(PDU session modification request)消息。
示例性的，该指示信息#1可以是关联QoS流(paired QoS flow)指示信息。
示例性的，该远端UE可以通过UL NAS消息发送请求消息#5给AMF#1。
示例性的，AMF#1可以通过N11消息向SMF#1发送请求消息#5，该N11消息可以是PDU会话创建上下文请求(Nsmf_PDUsession_createSMcontext request)消息等。
AMF#1和SMF#1是为远端UE服务的网络设备。
S930，SMF#1向远端UE发送响应消息#3。
具体地，SMF#1通过AMF#1向远端UE发送响应消息#3。相应的，远端UE接收该响应消息#3。
具体地，该响应消息#3用于响应上述请求消息#5。
该响应消息#3包括QoS流信息#2(第一信息的一例)、QoS rule和QoS参数。
该QoS流信息#2包括QoS流#1的标识信息QFI-1及QFI-1对应的PDR。
应理解，SMF#1根据指示信息#1向远端UE发送所述QFI-1对应的PDR。
示例性的，该响应消息#3可以是PDU会话修改接收(PDU session modification accept)消息。
其中，SMF#1可以通过N11消息向AMF#1发送该响应消息#3，该N11消息可以是N1N2消息传递(Namf_communication_N1N2MessageTransfer)消息。
S940，远端UE通过非直连路径向中继UE发送请求消息#6。
具体地，远端UE通过PC5接口向中继UE发送请求消息#6(第一消息的一例)。
该请求消息#3包括QoS流信息#2和指示信息#2(第一指示的一例)。
可选的，该请求消息#6还可以携带指示信息#4。
该指示信息#3用于指示网络设备(UPF#2)进行可靠性传输或负载均衡传输。
示例性的，该请求消息#6可以是连接修改请求(link modification request)消息。
示例性的，该指示信息#2可以是关联QoS流(paired QoS flow)指示信息。
S950，中继UE向SMF#2发送请求消息#7。
具体地，中继UE向AMF#2发送请求消息#7，AMF#2向SMF#2(第二网络设备的一例)发送请求消息#7。
具体地，中继UE在请求消息#7中携带QoS流信息#2和指示信息#2。
该请求消息#7用于请求SMF#2对QoS流#2进行修改，这里的修改可以理解为，对QoS流#2对应的QoS参数进行修改，即，增加QoS流信息#2中包括的QoS流#1的QoS参数，具体地，可以理解为增加QFI-1对应的PDR。
该请求消息#7可以是PDU会话修改请求(PDU session modification request)消息。
可选的，该请求消息#7还可以携带指示信息#3(第三指示信息的一例)。
该指示信息#3用于指示网络设备(UPF#2)进行可靠性传输或负载均衡传输。
S960，SMF#2向UPF#2发送请求消息#8。
具体地，SMF#1在该请求消息#8中携带QoS流信息#1和QoS流信息#2。
可选的，该请求消息#8还可以携带指示信息#3(第三指示信息的一例)。
该指示信息#3用于指示网络设备(UPF#2)进行可靠性传输或负载均衡传输。
示例性的，该请求消息#8可以是N4修改请求消息。
S970，SMF#2向中继UE发送响应消息#4。
具体地，SMF#2通过AMF#2向中继UE发送响应消息#4。
该响应消息#4用于响应请求消息#7，SMF#2完成对QoS流#2的修改。
示例性的，该响应消息#4可以是PDU会话修改接收(PDU session modification accept)消息。
S980，中继UE向远端UE发送响应消息#5。
具体地，中继UE通过PC5接口向远端UE发送响应消息#5。
该响应消息#5用于响应请求消息#6。
示例性的，该响应消息#5可以是连接修改接收(link modification accept)消息。
S990，UPF#2根据请求消息#8确定执行多路传输。
具体地，UPF#2根据请求消息#48确定QFI-2对应的PDR和QFI-1对应的PDR，进一步确定执行多路传输。
可选的，当请求消息#8中包括指示信息#3，UPF#2可以根据该指示信息#3确定具体执行可靠性传输或执行负载均衡传输。
可以理解，UPF具体执行多路传输的方法与方法800相同，本申请实施例在此不进行赘述。
根据本申请实施例提供的技术方案，在层三relay场景下，UE通过direct和indirect path同时进行下行数据包传输，从而提升数据传输速率或增加可靠性。
图10是本申请实施例提供的一种数据传输的方法1000的示意图。方法1000可以视为方法500的一种具体实现方式，该方法1000可以包括如下步骤。
S1010，远端UE在直连路径上建立PDU会话#1和QoS流#1。
具体地，远端UE在直连路径上发起建立PDU会话#1的建立，从而可以实现远端UE和DN之间的数据传输。其中，PDU会话#1包括QoS流#1(第二QoS流的一例)。
该QoS流#1的标识可以是QFI-1。
可以理解，远端UE在建立该QoS流#1过程中可以获取QoS流信息#2，该QoS流信息#2包括QoS流#1的标识信息QFI-1及QFI-1对应的PDR。
S1020，远端UE通过非直连路径向中继UE发送请求消息#1(第一请求消息的一例)。
具体地，远端UE根据数据传输需求确定需要建立非直连路径，从而同时使用非直连路径和直连路径进行多路传输，例如需要进行可靠性传输或负载均衡传输。
具体地，远端UE通过PC5接口向中继UE发送请求消息#1(第一请求消息的一例)，该请求消息#1用于请求在非直连路径上建立QoS流#2(第一QoS流的一例)。
该QoS流#2的标识可以是QFI-2。
该请求消息#1包括指示信息#1(第二指示信息的一例)，该指示信息#1用于获取QoS流信息#1(第一信息的一例)，该QoS流信息#1包括QoS流#2的标识信息QFI-2。
该请求消息#1还包括“request PC5 QoS rule”和“request PC5 QoS参数”。其中，request PC5 QoS rule”中的数据包过滤的目的地址和QFI-1的QoS rule的数据包过滤的目的地址 相同；“request PC5 QoS参数”和QoS流#1的QoS参数相同。
可以理解，远端UE可以在直连路径上获取QoS流#1的QoS流信息#2(第二信息的一例)。其中，该QoS流信息#2包括QFI-1的QoS rule和QoS参数。
该请求消息#1可以是连接修改请求(link modification request)消息。
该指示信息#1可以是关联QoS流(paired QoS flow)指示信息。
S1030，中继UE向SMF#2发送请求消息#9。
具体地，中继UE向AMF#2发送请求消息#9，AMF#2向SMF#2发送请求消息#9，该请求消息#9包括“request QoS rule”和“request QoS参数”。相应的，SMF#2根据该请求消息#9在非直连路径上建立QoS流#2。
其中，请求消息#9中的“request QoS rule”和“request QoS参数”是中继UE根据远端UE的“request PC5 QoS rule”和“request PC5 QoS参数”确定的。
该请求消息#9可以是PDU会话修改请求(PDU session modification request)消息。
该中继UE可以通过UL NAS消息发送请求消息#9给AMF#2。
AMF#2可以通过N11消息向SMF#2发送请求消息#9，该N11消息可以是PDU会话创建上下文请求(Nsmf_PDUsession_createSMcontext request)消息等。
AMF#2和SMF#2是为中继UE服务的网络设备。
S1040，SMF#2向中继UE发送响应消息#6。
具体地，SMF#2通过AMF#2向中继UE发送响应消息#6。
具体地，该响应消息#6用于响应上述请求消息#9。
该响应消息#6可以是PDU会话修改接收(PDU session modification accept)消息。
该响应消息#6包括QoS流#2的标识信息QFI-2。
该响应消息#6中还包括QoS rule和QoS参数，该响应消息#6中的“QoS rule”和“QoS参数”是SMF#2根据中继UE发送的“request QoS rule”和“request QoS参数”确定的。
S1050，中继UE通过非直连路径向远端UE发送响应消息#7。
具体地，中继UE通过PC5接口向远端UE发送响应消息#7，该响应消息#7包括QoS流信息#1的QFI-2(第一信息的一例)、PDU会话#2的ID、中继UE的ID，PC5 QoS rule和PC5 QoS参数。
该响应消息#7可以是连接修改接收(link modification accept)消息。
可以理解，中继UE根据响应消息#6中包括的QoS rule生成PC5 QoS rule，根据响应消息#6中包括的QoS参数生成PC5 QoS参数。
需要说明的是，中继UE根据指示信息#1向远端UE发送QFI-2、PDU会话#2的ID以及中继UE的ID。
可选的一种方式中，中继UE ID可以是GUTI或S-TMSI。
S1060，远端UE通过直连路径向AMF#1发送请求消息#10。
具体地，远端UE在该请求消息#10中携带QFI-2、PDU会话#2的ID、中继UE的ID以及QoS流#1的PDU会话#1的修改请求。
可选的，该请求消息#10还可以包括指示信息#2。
该请求消息#10可以是NAS消息，用于请求对QoS流#1的参数进行修改。这里的修改可以理解为，对QoS流#1对应的QoS参数进行修改，即，增加QoS流信息#1中包括 的QoS流#2的QoS参数。
S1070，AMF#1向AMF#2发送请求消息#11。
具体地，AMF#1根据请求消息#10中包括的中继UE的ID确定为该中继UE提供服务的AMF#2的地址，进一步的，向AMF#2发送请求消息#11。
本申请中，该请求消息#11包括QFI-2、PDU会话#2的ID以及中继UE的ID。
可选的，该请求消息#11还可以包括指示信息#2。
该指示信息#2用于指示AMF#2发送QFI-2对应的PDR。
作为一个示例，AMF#1可以通过N11消息向AMF#2发送请求消息#11，该N11消息可以是(Namf_communication_UEContextTransfer request)消息。
S1080，AMF#2向AMF#1发送响应消息#8。
具体地，AMF#2根据QFI-2、PDU会话#2的ID以及中继UE的ID确定为该中继UE QFI-2提供服务的UPF#2的地址和QFI-2对应的PDR。进一步的，AMF#2向AMF#1发送响应消息#8。
具体地，该响应消息#8用于响应上述请求消息#11。
本申请中，该响应消息#8中携带UPF#2的地址和QFI-2对应的PDR。
作为一个示例，AMF#2从SMF#2获取UPF#2的地址。
作为一个示例，UPF#2的地址可以是UPF-2的全限定域名(fully qualified domain name，FQDN)或IP地址。
应理解，AMF#2根据指示信息向AMF#1发送QFI-2对应的PDR。
作为一个示例，AMF#2可以通过N11消息向AMF#1发送响应消息#8，该N11消息可以是(Namf_communication_UEContextTransfer response)消息。
S1090，AMF#1向SMF#1发送请求消息#12。
其中，请求消息#12中包括UPF#2的地址、QFI-2对应的PDR，以及QoS流#1的PDU会话#1的修改请求。
可选的，还可以包括指示信息#2。
可以理解，该请求消息#12用于请求SMF#1对QoS流#1的PDU会话#1的QoS参数进行修改，这里的修改可以理解为，对QoS流#1对应的QoS参数进行修改，即，增加QoS流信息#1中包括的QoS流#2的QoS参数，这里具体可以是增加QFI-2对应的PDR。
作为一个示例，AMF#1可以通过N11消息向SMF#1发送请求消息#12，该N11消息可以是(Namf_PDUSession_UpdateSMContext request)消息。
S1091，SMF#1向UPF#1发送请求消息#13。
其中，请求消息#13包括QFI-2对应的PDR，QFI-1对应的PDR，QFI-2。
可选的，还可以包括指示信息#3(第三指示信息的一例)。
该指示信息#3用于UPF#1确定执行多路传输，并且具体的，确定进行可靠性传输或者进行负载均衡传输。
可选的，QFI-2对应的PDR，QFI-2以及指示信息#3可以携带在QFI-1对应的PDR中。
作为一个示例，SMF#1可以通过N4修改请求消息向UPF#1发送请求消息#13。
进一步的，SMF#1根据请求消息12中包括的UPF#2的地址确定UPF#1和UPF#2是 否为同一个UPF。
具体地，当UPF#1与UPF#2相同时，可以直接按照方法800(b)进行下行数据的传输。
具体地，当UPF#1与UPF#2不同时,在一种可能的实施方式中，SMF#1可以按照方法800(a)进行下行数据的传输。
在另一种可能的实施方式中，SMF#1可以发起UPF#1与UPF#2间的通道建立。
可以理解，UPF#1与UPF#2之间的通道可以用来传输数据，该方案也可以用于方法700和方法900中，各实施例间的实施方式可以互相结合实现，本申请实施例对此不作限定。
S1092，UPF#1和UPF#2之间建立通道。
具体地，UPF#1分配通道相关信息，该通道相关信息经过SMF#1，AMF#1，AMF#2和SMF#2发送给UPF#2。
本申请中，UPF#1的通道相关信息包括UPF#1的地址和通道(tunnel)ID。
示例性的，该tunnelID可以是全量通道端点标识(full qualified tunnel endpoint ID，F-TEID)。
作为一种示例，UPF#1分配通道相关信息，经过SMF#1，AMF#1，AMF#2和SMF#2发送给UPF#2过程中的信令可以通过N1消息发送。
示例性的，UPF#1可以通过N4修改响应消息向SMF#1发送通道相关信息。
可以理解，该响应消息用于响应请求消息#13。
示例性的，SMF#1可以通过Namf_PDUSession_UpdateSMContext response消息向AMF#1发送通道相关信息。
示例性的，AMF#1可以通过Namf_communication_UEContextTransfer request消息向AMF#2发送通道相关信息。
示例性的，AMF#2可以通过Namf_PDUSession_UpdateSMContext request消息向SMF#2发送通道相关信息。
示例性的，SMF#2可以通过N4修改响应消息向UPF#2发送通道相关信息。
类似的，UPF#2分配通道相关信息，该通道相关信息经过SMF#2，AMF#2，AMF#1和SMF#1发送给UPF#1。
本申请中，UPF#2的通道相关信息包括UPF#2的地址和通道(tunnel)ID。
示例性的，该tunnelID可以是全量通道端点标识(full qualified tunnel endpoint ID，F-TEID)。
信令的交互过程与上述UPF#1分配通道相关信息的过程类似，此处不再赘述。
UPF#1和UPF#2完成通道信息的交互后，完成通道的建立。即，UPF#1和UPF#2之间可以通过该通道传输数据。
S1093，UPF#1根据请求消息#13确定执行多路传输。
具体地，UPF#1根据请求消息#13确定QFI-2对应的PDR和QFI-1对应的PDR，进一步确定执行多路传输。
可选的，当请求消息#13中包括指示信息#3，UPF#1可以根据该指示信息#3确定具体执行可靠性传输或执行负载均衡传输。
本申请中，UPF执行多路传输的方法和方法800基本相同，不同之处在于：本实施例中，远端UE的非直连路径和直连路径连接到不同UPF时，步骤a和步骤b与方法800完全相同，UPF#1执行步骤c时，UPF#1QFI-1对应的PDR确定UPF#1与UPF#2之间的通道，并将新IP包(括IP-4和IP6，IP-1和IP6)新增GTP-U消息头，并通过该通道发送给UPF#2，在GTP-U消息头中包含QFI-2的信息，步骤d：UPF#2在该通道收到GTP-U消息后，根据通道标识直接的映射关系，将该GTP-U转给Gnb#2；步骤e：gNB根据GTP-U中的QFI-2将新IP包发送给中继UE，中继UE根据PC5 QoS rule路由给远端UE。后续流程与方法800完全相同，本申请实施例在此不进行赘述。
图11是本申请实施例提供的一种数据传输的方法1100的示意图。方法1100可以视为方法500的一种具体实现方式，该方法1100可以包括如下步骤。
S1110，远端UE触发中继UE在非直连路径上建立PDU会话#2和QoS流#2。
具体地，远端UE通过PC5接口在非直连路径上触发中继UE建立PDU会话#2，从而可以实现远端UE和DN之间的数据传输。其中，PDU会话#2包括QoS流#2(第二QoS流的一例)。
该QoS流#2的标识可以是QFI-2。
可以理解，远端UE在触发建立该QoS流#2过程中可以获取QoS流信息#1，该QoS流信息#1包括QoS流#2的标识信息QFI-2及QFI-2对应的PDR。
S1120，远端UE向SMF#1发送请求消息#14。
具体地，远端UE根据数据传输需求确定需要建立直连路径，从而同时使用非直连路径和直连路径进行多路传输，例如需要进行可靠性传输或负载均衡传输。
具体地，远端UE向AMF#1发送请求消息#14，AMF#1向SMF#1发送请求消息#14，该请求消息#14用于请求在直连路径上建立QoS流#1(第一QoS流的一例)。
该QoS流#1的标识可以是QFI-1。
该请求消息#14包括指示信息#1(第二指示信息的一例)，该指示信息#1用于获取QoS流信息#2(第一信息的一例)，该QoS流信息#2包括QoS流#1的标识信息QFI-1。
该请求消息#14还包括“request QoS rule”和“request QoS参数”。其中，request QoS rule”中的数据包过滤的目的地址和QFI-2的QoS rule的数据包过滤的目的地址相同；“request QoS参数”和QoS流#2的QoS参数相同。
该请求消息#14可以是PDU会话修改请求(PDU session modification request)消息。
该指示信息#1可以是关联QoS流(paired QoS flow)指示信息。
该远端UE可以通过UL NAS消息发送请求消息#14给AMF#1。
AMF#1可以通过N11消息向SMF#1发送请求消息#14，该N11消息可以是PDU会话创建上下文请求(Nsmf_PDUsession_createSMcontext request)消息等。
AMF#1和SMF#1是为远端UE服务的网络设备。
S1130，SMF#1向远端UE发送响应消息#9。
具体地，SMF#1通过AMF#1向远端UE发送响应消息#9。相应的，远端UE接收该响应消息#9。
具体地，该响应消息#9用于响应上述请求消息#14。
该响应消息#9包括QoS流#1的标识信息QFI-1(第一信息的一例)和PDU会话#1 的ID.
该响应消息#9还可以包括QoS rule和QoS参数。
应理解，SMF#1根据指示信息#1向远端UE发送所述QFI-1和PDU会话#1的ID。
该响应消息#9可以是PDU会话修改接收(PDU session modification accept)消息。
其中，SMF#1可以通过N11消息向AMF#1发送该响应消息#9，该N11消息可以是N1N2消息传递(Namf_communication_N1N2MessageTransfer)消息。
S1140，远端UE通过非直连路径向中继UE发送请求消息#15。
具体地，远端UE通过PC5接口向中继UE发送请求消息#15(第一消息的一例)。
该请求消息#15包括QFI-1、PDU会话#1的ID，远端UE的ID，以及QoS流#2的PDU会话#2的修改请求。(第一指示信息的一例)。
可选的，该请求消息#15还可以携带指示信息#2(第一指示信息的一例)。
该请求消息#15可以是连接修改请求(link modification request)消息。
该指示信息#2可以是关联QoS流(paired QoS flow)指示信息。
该请求消息#15用于请求对QoS流#2的参数进行修改。这里的修改可以理解为，对QoS流#2对应的QoS参数进行修改，即，增加QoS流信息#1中包括的QoS流#2的QoS参数。
S1150，AMF#2向AMF#1发送请求消息#16。
具体地，AMF#2根据请求消息#15中包括的远端UE的ID确定为该远端继UE提供服务的AMF#1的地址，进一步的，向AMF#1发送请求消息#16。
本申请中，该请求消息#16包括QFI-1、PDU会话#1的ID以及远端UE的ID。
可选的，该请求消息#16还可以包括指示信息#2。
该指示信息#2用于指示AMF#2发送QFI-1对应的PDR。
作为一个示例，AMF#2可以通过N11消息向AMF#1发送请求消息#16，该N11消息可以是(Namf_communication_UEContextTransfer request)消息。
S1160，AMF#1向AMF#2发送响应消息#10。
具体地，AMF#1根据QFI-1、PDU会话#1的ID以及远端UE的ID确定为该远端UE QFI-1提供服务的UPF#1的地址和QFI-1对应的PDR。进一步的，AMF#1向AMF#2发送响应消息#10。
具体地，该响应消息#10用于响应上述请求消息#16。
本申请中，该响应消息#10中携带UPF#1的地址和QFI-1对应的PDR。
作为一个示例，UPF#1的地址可以是UPF-1的全限定域名(fully qualified domain name，FQDN)或IP地址。
应理解，AMF#1根据指示信息向AMF#2发送QFI-1对应的PDR。
作为一个示例，AMF#1可以通过N11消息向AMF#2发送响应消息#10，该N11消息可以是(Namf_communication_UEContextTransfer response)消息。
S1170，AMF#2向SMF#2发送请求消息#17。
其中，请求消息#17中包括UPF#1的地址、QFI-1对应的PDR，以及QoS流#2的PDU会话#1的修改请求。
可选的，还可以包括指示信息#2。
可以理解，该请求消息#17用于请求SMF#2对QoS流#2的PDU会话#2的QoS参数进行修改，这里的修改可以理解为，对QoS流#2对应的QoS参数进行修改，即，增加QoS流信息#2中包括的QoS流#1的QoS参数，这里具体可以是增加QFI-1对应的PDR。
作为一个示例，AMF#2可以通过N11消息向SMF#2发送请求消息#17，该N11消息可以是(Namf_PDUSession_UpdateSMContext request)消息。
S1180，SMF#2向UPF#2发送请求消息#18。
其中，请求消息#18包括QFI-1对应的PDR，QFI-2对应的PDR，QFI-1。
可选的，还可以包括指示信息#3(第三指示信息的一例)。
该指示信息#3用于UPF#2确定执行多路传输，并且具体的，确定进行可靠性传输或者进行负载均衡传输。
可选的，QFI-1对应的PDR，QFI-1以及指示信息#3可以携带在QFI-2对应的PDR中。
作为一个示例，SMF#2可以通过N4修改请求消息向UPF#2发送请求消息#18。
进一步的，SMF#2根据请求消息18中包括的UPF#1的地址确定UPF#1和UPF#2是否为同一个UPF。
具体地，当UPF#1与UPF#2相同时，可以直接按照方法800(b)进行下行数据的传输。
具体地，当UPF#1与UPF#2不同时,在一种可能的实施方式中，SMF#1可以按照方法800(a)进行下行数据的传输。
在另一种可能的实施方式中，SMF#2可以发起UPF#1与UPF#2间的通道建立。
可以理解，UPF#1与UPF#2之间的通道可以用来传输数据，该方案也可以用于方法700和方法900中，各实施例间的实施方式可以互相结合实现，本申请实施例对此不作限定。
S1190，UPF#1和UPF#2之间建立通道。
具体地，UPF#2分配通道相关信息，该通道相关信息经过SMF#2，AMF#2，AMF#1和SMF#1发送给UPF#1。
本申请中，UPF#2的通道相关信息包括UPF#2的地址和通道(tunnel)ID。
示例性的，该tunnelID可以是全量通道端点标识(full qualified tunnel endpoint ID，F-TEID)。
作为一种示例，UPF#2分配通道相关信息，经过SMF#2，AMF#2，AMF#1和SMF#1发送给UPF#1过程中的信令可以通过N1消息发送。
示例性的，UPF#2可以通过N4修改响应消息向SMF#2发送通道相关信息。
可以理解，该响应消息用于响应请求消息#18。
示例性的，SMF#2可以通过Namf_PDUSession_UpdateSMContext response消息向AMF#2发送通道相关信息。
示例性的，AMF#2可以通过Namf_communication_UEContextTransfer request消息向AMF#1发送通道相关信息。
示例性的，AMF#1可以通过Namf_PDUSession_UpdateSMContext request消息向SMF#1发送通道相关信息。
示例性的，SMF#1可以通过N4修改响应消息向UPF#1发送通道相关信息。
类似的，UPF#1分配通道相关信息，该通道相关信息经过SMF#1，AMF#1，AMF#2和SMF#2发送给UPF#1。
本申请中，UPF#1的通道相关信息包括UPF#1的地址和通道(tunnel)ID。
示例性的，该tunnelID可以是全量通道端点标识(full qualified tunnel endpoint ID，F-TEID)。
信令的交互过程与上述UPF#2分配通道相关信息的过程类似，此处不再赘述。
UPF#1和UPF#2完成通道信息的交互后，完成通道的建立。即，UPF#1和UPF#2之间可以通过该通道传输数据。
S1191，UPF#2根据请求消息#18确定执行多路传输。
具体地，UPF#2根据请求消息#18确定QFI-2对应的PDR和QFI-1对应的PDR，进一步确定执行多路传输。
可选的，当请求消息#18中包括指示信息#3，UPF#2可以根据该指示信息#3确定具体执行可靠性传输或执行负载均衡传输。
本申请中，UPF执行多路传输的方法和执行步骤S1093后的执行的传输方法相同，本申请实施例在此不进行赘述。
根据本申请实施例提供的技术方案，在层三relay场景下，UE通过direct和indirect path同时进行下行数据包传输，从而提升数据传输速率或增加可靠性。
本申请中，图10所示的方法1000中，远端UE在直连路径上建立PDU会话#1和QoS流#1之后，远端UE触发中继UE在非直连路径上建立PDU会话#2和QoS流#2，并由远端UE触发对PDU会话#1的修改流程，执行远端UE与中继UE的会话关联，该会话关联可以理解为远端UE可以通过直连路径和非直连路径两个路径进行多路传输，其中可以通过直连路径上的UPF和非直连路径上的UPF进行数据传输。
本申请中，图11所示的方法1100中，远端UE触发中继UE在非直连路径上建立PDU会话#2和QoS流#2之后，远端UE在直连路径上建立PDU会话#1和QoS流#1，并由中继UE触发对PDU会话#2的修改流程，执行远端UE与中继UE的会话关联。
应理解，以上仅为示例性说明，在方法1000中，也可以由中继UE触发对PDU会话#2的修改流程，并执行PDU会话#1和PDU会话#2的关联；在方法1100中，也可以由远端UE触发对PDU会话#1的修改流程，并执行PDU会话#1和PDU会话#2的关联。本申请实施例对此不作限定。
图12示出了本申请实施例提供的一种数据通信的方法1200的流程图，该方法1200中包括第一通信路径和第二通信路径，其中，第一通信路径是第一终端设备与网络连接的直连路径，第二通信路径是第一终端设备通过中继设备与网络连接的非直连路径。第一终端设备可以通过直连路径触发第一会话和第一服务质量流的修改，其中，第一会话和第一服务质量QoS流是第一终端设备在直连路径上建立的。
本申请实施例中，第一会话例如可以是第一协议数据单元(protocol data unit，PDU)会话，第二会话例如可以是第二PDU会话，第一服务质量流可以是第一服务质量(quality of service，QoS)流，第二服务质量流可以是第二QoS流，第一移动性管理实体可以是第一AMF(access and mobility management function)，第二移动性管理实体可以是第二AMF， 第一会话功能管理实体可以是第一SMF(session management function)，第二会话功能管理实体例如可以是第二SMF，第一用户面功能管理实体可以是第一UPF(user plane function)，第二用户面功能管理实体可以是第二UPF。以上仅为本申请实施例中的示例性说明，本申请实施例对此不作限定。
该方法包括如下步骤。
S1210，第一终端设备获取第一信息。
具体的，第一信息包括第一通信路径的第一PDU会话的标识、第二通信路径的第二PDU会话的标识以及中继设备的标识。
一种可能的实施方式中，该第一信息中的第二通信路径的第二PDU会话的标识以及中继设备的标识是第一终端设备从中继设备获取的。
示例性的，第一终端设备向中继设备发送连接建立请求消息，用于触发中继设备建立第二QoS流和第二PDU会话，中继设备在建立完第二QoS流和第二PDU会话之后可以向第一终端设备发送第二PDU会话的标识和/或第二QoS流的标识。
示例性的，第一终端设备发送连接建立请求消息，用于触发中继设备建立第二QoS流和第二PDU会话，中继设备在第二QoS流和第二PDU会话建立完成后，第一终端设备发送连接修改请求消息，中继UE通过该连接修改请求消息的响应消息向第一终端设备发送第二PDU会话的标识和/或第二QoS流的标识。
示例性的，第一终端设备先触发中继设备建立了第二PDU会话和第二QoS流并获取了第二通信路径的第二PDU会话的标识、第二PDU会话对应的第二QoS流的标识以及中继设备的标识，然后在直连路径上请求建立第一PDU会话和第一QoS流时，第一终端设备可以在请求消息中请求多路传输，该请求消息中包括第一PDU会话的标识、第二通信路径的第二PDU会话的标识、第二PDU会话对应的第二QoS流的标识以及中继设备的标识。
可选的，第一信息还可以包括第一QoS流的标识和/或第二QoS流的标识，该第一QoS流是第一PDU会话对应的QoS流，第二QoS流是第二PDU会话对应的QoS流。
示例性的，第一终端设备先在直连路径上建立了第一PDU会话和第一QoS流，然后触发中继设备建立第二PDU会话和第二QoS流，该情况下，第一信息可以包括第一QoS流的标识。
S1220，第一终端设备向第一AMF发送第一请求消息。
其中，第一请求消息包括第一信息，第一请求消息用于请求通过第一PDU会话和第二PDU会话共同传输第一数据。
一种可能的实施方式中，第一请求消息还包括第一指示，所一指示用于指示通过所述第一PDU会话和所述第二PDU会话共同传输所述第一数据。
一种可能的实施方式中，第一请求消息还包括第一指示和第二指示，所述第二指示用于描述所述第一数据。
需要说明的是，第一请求消息只包括第一指示时，不强调具体的所述第一数据的区分粒度，例如可以以QoS流为粒度，例如，原本通过特定QoS流传输的数据需要多路传输；第一请求消息包括第一指示和第二指示时，可以以第二指示限定的粒度进行多路传输。例如，第二指示可以限定以业务数据流为粒度，例如Service data flow(SDF)的粒度，也可以 理解为，第二指示进一步描述了第一数据中的需要多路传输的数据类型，例如，该类型可以是数据的业务类型。
可以理解，第一PDU会话包括第一QoS流，第一请求消息用于请求通过第一PDU会话和第二PDU会话共同传输第一QoS流传输的全部数据或部分数据，或者，第二PDU会话包括第二QoS流，第一请求消息用于请求通过第一PDU会话和第二PDU会话共同传输第二QoS流传输的全部数据或部分数据。
一种可选的理解，第一数据包括通过所述第一QoS流传输的全部数据或部分数据，或者，第一数据包括通过所述第二QoS流传输的全部数据或部分数据。换句话说，可以在两条路径上共同传输原来直连路径上传输的数据，也可以在两条路径上共同传输原来非直连路径上传输的数据。
一种可能的实施方式中，第一请求消息还包括第三指示，第三指示用于指示第一通信路径为锚点路径，或者，第三指示用于指示第二通信路径为锚点路径，第一通信路径和第二通信路径通过服务于锚点路径的用户面功能实体与应用服务器通信。第一SMF和第二SMF可基于第三指示信息确定第一UPF或者第二UPF为锚点UPF。
一种可能的实施方式中，第一请求消息还包括第一终端设备的标识，第一终端设备的标识对应第二通信路径。可以理解，第一终端设备的标识为第一终端设备与第二终端设备执行发现或者建立连接时使用的标识，第一终端设备的标识可以由中继设备为第一终端设备分配的标识，也可以由第一终端设备自己分配，第一终端设备的标识用于第二SMF给第二UPF配置识别规则，该识别规则用于第二UPF确定通过进行多路传输的数据，具体地，第二SMF可以根据第一终端设备的标识确定中继设备在中继第一终端设备的数据的时使用的IP地址及端口号信息，从而向第二UPF配置识别规则，该识别规则用于第二UPF根据IP地址及端口号信息确定通过进行多路传输的第一终端设备的数据。
S1230，在接收第一请求消息之后，第一UPF和第二UPF传输第一数据。
本申请中，第一AMF接收第一请求消息后，第一AMF通过中继设备的标识可以确定第二AMF，或者，根据中继设备的标识和第二PDU会话的标识确定第二SMF，其中，第二AMF服务于中继设备，第二SMF服务于第二PDU会话。
进一步的，通过第一SMF和第二SMF建立第一UPF和第二UPF之间的第一通道，第一UPF和第二UPF通过该第一通道可以传输第一数据。
一种可能的实施方式中，第一SMF从第一UPF获取第一通道信息并将第一通道信息通过第二SMF发送至第二UPF，第一通道信息用于第一UPF通过第一通道向第二UPF发送数据；第二SMF从第二UPF获取第二通道信息并将第二通道信息通过第一SMF发送至第一UPF，第一通道信息用于第二UPF通过第一通道向第一UPF发送数据。
作为示例而非限定，第一AMF根据中继设备的第一标识确定第二AMF；第一AMF从第二AMF获取第二SMF的地址；第一AMF向第一SMF发送第二SMF的地址；第一SMF从第一UPF获取第一通道信息；第一SMF根据第二SMF的地址，向第二SMF发送第一通道信息；第二SMF从第二UPF获取第二通道信息；第二SMF向第一SMF发送第二通道信息。
其中，第一SMF和第二SMF之间互相发送通道信息的步骤没有顺序限定。
作为示例而非限定，所述第一AMF根据所述中继设备的第一标识确定所述第二AMF； 所述第一AMF通过所述第一SMF从所述第一UPF获取第一通道信息；所述第二AMF通过所述第二SMF从所述第二UPF获取第二通道信息；所述第一AMF通过所述第一SMF向所述第一UPF发送所述第二通道信息；所述第二AMF通过所述第二SMF向所述第二UPF发送所述第一通道信息。
其中，第一SMF和第二SMF之间互相发送通道信息的步骤没有顺序限定。
本申请中，第一UPF和第二UPF通过第一SMF和第二SMF配置的规则传输第一数据。
一种可能的实施方式中，第一UPF为锚点UPF，第一SMF向第一UPF发送第一规则，第一规则用于指示第一UPF向第二UPF发送第一数据的部分或全部，使得第二UPF通过第二通信路径向第一终端设备发送从所述第一UPF接收的数据。
一种可能的实施方式中，第一UPF为锚点UPF，第一SMF向第一UPF发送第二规则，第二规则用于指示第一UPF将从第二UPF接收的数据发送至应用服务器。
一种可能的实施方式中，第一UPF为锚点UPF，第二SMF向第二UPF发送第三规则，第三规则用于指示第二UPF向第一UPF发送从第一终端设备接收的第一数据。
该情况下，第一终端设备通过第二通信路径发送给第二UPF的待多路传输的数据，可能是第一数据的全部或部分，这取决于第一终端设备的分流规则。该分流规则可以理解为第一终端设备进行多路传输的粒度，例如，如果以QoS流为粒度，则待多路传输的数据可能是第一数据的全部，若以业务数据流为粒度，则待多路传输的数据可能是第一数据的部分。而对于第二UPF而言，所有从第二通信路径接收的第一终端设备发送的待多路传输的数据，都要发送给第一UPF。
一种可能的实施方式中，第一UPF为锚点UPF，第二SMF向第二UPF发送第四规则，第四规则用于指示第二UPF向第一终端设备发送从第一UPF接收的第一数据。
一种可能的实施方式中，第二UPF为锚点UPF，第一SMF向第一UPF发送第一规则，第一规则用于指示第一UPF向第二UPF发送从第一终端设备接收的第一数据。
一种可能的实施方式中，第二UPF为锚点UPF，第一SMF向第一UPF发送第二规则，第二规则用于指示第一UPF向第一终端设备发送从第二UPF接收的数据。
一种可能的实施方式中，第二UPF为锚点UPF，第二SMF向第二UPF发送第三规则，第三规则用于指示第二UPF向第一UPF发送第一数据的部分或全部，使得第一UPF通过第一通信路径向第一终端设备发送从第二UPF接收的数据。
一种可能的实施方式中，第二UPF为锚点UPF，第二SMF向第二UPF发送第四规则，第四规则用于指示第二UPF将从第一UPF接收的数据发送至应用服务器。
一种可能的实施方式中，第一SMF从第一AMF接收第一信息，第一SMF根据第一信息生成第一规则和第二规则。
一种可能的实施方式中，第二SMF从第一SMF接收或第二AMF接收第二信息，第二SMF根据第二信息生成第三规则和第四规则。
其中，第二信息包括：第一指示、第二PDU会话的标识以及中继设备的第二标识，中继设备的第二标识是由第一AMF根据中继设备的第一标识确定的。
可选的，第二信息还包括以下至少一项：第二QoS流的标识、第二指示、第一终端设备的标识、或第三指示。
一种可能的实施方式中，第二SMF从第一SMF接收第二PDU会话的标识、第二PDU会话对应的第二QoS流的标识以及中继设备的第二标识，第二SMF根据第二PDU会话的标识、第二PDU会话对应的第二QoS流的标识以及中继设备的第二标识生成第三规则和第四规则。
根据上述技术方案，第一终端设备直连路径的第一UPF可以和非直连路径的第二UPF建立传输通道，使得第一终端设备可以通过该直连路径和非直连路径传输直连路径的第一QoS流的部分或全部数据或传输非直连路径的第二QoS流的部分或全部数据，实现数据的冗余传输或负载均衡传输或切换传输。
图13示出了本申请实施例提供的一种数据通信的方法1300的流程图，该方法1300中包括第一通信路径和第二通信路径，其中，第一通信路径是第一终端设备与网络连接的直连路径，第二通信路径是第一终端设备通过中继设备与网络连接的非直连路径。中继设备可以触发第二PDU会话和第二QoS流的修改，其中，第二PDU会话和第二QoS流是中继设备在非直连路径上建立的。
该方法包括如下步骤。
S1310，中继设备获取第三信息。
具体的，第三信息包括第二通信路径的第二PDU会话的标识、第一通信路径的第一PDU会话的标识以及第一终端设备的标识。
一种可能的实施方式中，该第三信息中的第一通信路径的第一PDU会话的标识以及第一终端设备的标识是中继设备从第一终端设备获取的。
示例性的，第一终端设备建立完第一QoS流和第一PDU会话之后可以向中继设备发送第一PDU会话的标识和第一QoS流的标识。
示例性的，第一终端设备在第一QoS流和第一PDU会话建立完成后，中继设备发送连接修改请求消息，第一终端设备通过该连接修改请求消息可以向中继设备发送第一PDU会话的标识和第一QoS流的标识。
可选的，第三信息还可以包括第二QoS流的标识和/或第一QoS流的标识，该第一QoS流是第一PDU会话对应的QoS流，该第二QoS流是第二PDU会话对应的QoS流。
示例性的，中继设备先在非直连路径上建立了第二PDU会话和第二QoS流，然后第一终端设备建立第一PDU会话和第一QoS流，该情况下，第三信息可以包括第二QoS流的标识。
S1320，中继设备向第二AMF发送第二请求消息。
其中，第二请求消息包括第三信息，第二请求消息用于请求通过第一PDU会话和第二PDU会话共同传输第一数据。
一种可能的实施方式中，第二请求消息还包括第一指示，第一指示用于指示通过第一PDU会话和第二PDU会话共同传输第一数据。
一种可能的实施方式中，第一请求消息还包括第一指示和第二指示，所述第二指示用于描述所述第一数据。
需要说明的是，第一请求消息只包括第一指示时，不强调具体的传输粒度，例如可以以QoS流为粒度；第一请求消息包括第一指示和第二指示时，可以以第二指示限定的粒度进行多路传输。例如，第二指示可以限定以业务数据流为粒度，例如SDF的粒度，也 可以理解为，第二指示进一步描述了第一数据中的需要多路传输的数据类型，例如，该类型可以是数据的业务类型。
可以理解，第一PDU会话包括第一QoS流，第二请求消息用于请求通过第一PDU会话和第二PDU会话共同传输第一QoS流传输的全部数据或部分数据，或者，第二PDU会话包括第二QoS流，第二请求消息用于请求通过第一PDU会话和第二PDU会话共同传输第二QoS流传输的全部数据或部分数据。
一种可选的理解，第一数据包括通过所述第一QoS流传输的全部数据或部分数据，或者，第一数据包括通过所述第二QoS流传输的全部数据或部分数据。换句话说，可以在两条路径上共同传输原来直连路径上传输的数据，也可以在两条路径上共同传输原来非直连路径上传输的数据。
一种可能的实施方式中，第二请求消息还包括第三指示，第三指示用于指示第一通信路径为锚点路径，或者，第三指示用于指示第二通信路径为锚点路径，第一通信路径和第二通信路径通过服务于锚点路径的用户面功能实体与应用服务器通信。
S1330，在接收第二请求消息之后，第一UPF和第二UPF传输第一数据。
本申请中，第二AMF接收第二请求消息后，第二AMF通过第一终端设备的标识可以确定第一AMF，或者，根据第一终端设备的标识和第一PDU会话的标识确定第一SMF，其中，第一AMF服务于第一远端设备，第一SMF服务于第一PDU会话。
进一步的，通过第一SMF和第二SMF建立第一UPF和第二UPF之间的第一通道，第一UPF和第二UPF通过该第一通道可以传输第一数据。
一种可能的实施方式中，第一SMF从第一UPF获取第一通道信息并将第一通道信息通过第二SMF发送至第二UPF，第一通道信息用于第一UPF通过第一通道向第二UPF发送数据；第二SMF从第二UPF获取第二通道信息并将第二通道信息通过第一SMF发送至第一UPF，第一通道信息用于第二UPF通过第一通道向第一UPF发送数据。
作为示例而非限定，所述第二移动性管理实体从所述第一移动性管理实体获取所述第一会话管理功能实体的地址；所述第二移动性管理实体向所述第二会话管理功能实体发送所述第一会话管理功能实体的地址；所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息；所述第二会话管理功能实体根据所述第一会话管理功能实体的地址，向所述第一会话管理功能实体发送所述第二通道信息；所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息；所述第一会话管理功能实体向所述第二会话管理功能实体发送所述第一通道信息。
其中，第一SMF和第二SMF之间互相发送通道信息的步骤没有顺序限定。
作为示例而非限定，所述第二移动性管理实体根据所述第一终端设备的第一标识确定所述第一移动性管理实体；所述第二移动性管理实体通过所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息；所述第一移动性管理实体通过所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息；所述第二移动性管理实体通过所述第二会话管理功能实体向所述第二用户面功能实体发送所述第一通道信息；所述第一移动性管理实体通过所述第一会话管理功能实体向所述第一用户面功能实体发送所述第二通道信息。
其中，第一SMF和第二SMF之间互相发送通道信息的步骤没有顺序限定。
本申请中，第一UPF和第二UPF通过第一SMF和第二SMF配置的规则传输第一数据。
一种可能的实施方式中，第一UPF为锚点UPF，第一SMF向第一UPF发送第一规则，第一规则用于指示第一UPF向第二UPF发送第一数据的部分或全部，使得第二UPF通过第二通信路径向第一终端设备发送从所述第一UPF接收的数据。
一种可能的实施方式中，第一UPF为锚点UPF，第一SMF向第一UPF发送第二规则，第二规则用于指示第一UPF将从第二UPF接收的数据发送至应用服务器。
一种可能的实施方式中，第一UPF为锚点UPF，第二SMF向第二UPF发送第三规则，第三规则用于指示第二UPF向第一UPF发送从第一终端设备接收的第一数据。
该情况下，第一终端设备通过第二通信路径发送给第二UPF的待多路传输的数据，可能是第一数据的全部或部分，这取决于第一终端设备的分流规则。该分流规则可以理解为第一终端设备进行多路传输的粒度，例如，如果以QoS流为粒度，则待多路传输的数据可能是第一数据的全部，若以业务数据流为粒度，则待多路传输的数据可能是第一数据的部分。而对于第二UPF而言，所有从第二通信路径接收的第一终端设备发送的待多路传输的数据，都要发送给第一UPF。
一种可能的实施方式中，第一UPF为锚点UPF，第二SMF向第二UPF发送第四规则，第四规则用于指示第二UPF向第一终端设备发送从第一UPF接收的第一数据。
一种可能的实施方式中，第二UPF为锚点UPF，
第一SMF向第一UPF发送第一规则，第一规则用于指示第一UPF向第二UPF发送从第一终端设备接收的第一数据。
一种可能的实施方式中，第二UPF为锚点UPF，第一SMF向第一UPF发送第二规则，第二规则用于指示第一UPF向第一终端设备发送从第二UPF接收的数据。
一种可能的实施方式中，第二UPF为锚点UPF，第二SMF向第二UPF发送第三规则，第三规则用于指示第二UPF向第一UPF发送第一数据的部分或全部，使得第一UPF通过第一通信路径向第一终端设备发送从第二UPF接收的数据。
一种可能的实施方式中，第二UPF为锚点UPF，第二SMF向第二UPF发送第四规则，第四规则用于指示第二UPF将从第一UPF接收的数据发送至应用服务器。
一种可能的实施方式中，第一SMF从第一AMF接收第一信息，第一SMF根据第一信息生成第一规则和第二规则。
一种可能的实施方式中第一SMF从第二SMF接收或第二AMF接收第二信息，第二SMF根据第二信息生成第三规则和第四规则。
其中，第二信息包括：第一指示、第二PDU会话的标识以及中继设备的第二标识，中继设备的第二标识是由第一AMF根据中继设备的第一标识确定的。
可选的，第二信息还包括以下至少一项：第二QoS流的标识、第二指示、第一终端设备的标识、或第三指示。
一种可能的实施方式中，第一SMF从第二SMF接收第一PDU会话的标识、第一PDU会话对应的第一QoS流的标识以及第一终端设备的第二标识，第一SMF根据第一PDU会话的标识、第一PDU会话对应的第一QoS流的标识以及第一终端设备的第二标识生成第三规则和第四规则。
根据上述技术方案，第一终端设备直连路径的第一UPF可以和非直连路径的第二UPF建立传输通道，使得第一终端设备可以通过该直连路径和非直连路径传输直连路径的第一QoS流的部分或全部数据或传输非直连路径的第二QoS流的部分或全部数据，实现数据的冗余传输或负载均衡传输或切换传输。
图14示出了本申请实施例提供的一种数据传输的方法1400的示意图。该方法1400适用于上述方法1200和方法1300，其中，远端UE作为第一终端设备的一例，中继UE作为中继设备的一例。
该方法1400可以包括如下步骤。
S1410，远端UE和中继UE执行多路传输的授权过程。
本申请中，远端UE和中继UE被网络侧授权可以执行多路传输。
具体的，远端UE获取授权信息#a，该授权信息#a包括：网络侧授权该远端UE可以通过直连路径和非直连路径执行多路传输。
具体的，中继UE获取授权信息#b，该授权信息#b包括：网络侧授权该中继UE的非直连路径可以用于远端UE执行多路传输。
S1420，远端UE和中继UE分别在直连路径上和非直连路径上建立PDU会话和QoS流。
其中，远端UE在直连路径上建立PDU会话#1(作为第一PDU会话的一例)和QoS流#1(作为第一QoS流的一例)，中继UE在非直连路径上建立PDU会话#2(作为第二PDU会话的一例)和QoS流#2(作为第二QoS流的一例)。
需要说明的是，建立直连路径和非直连路径包括两种情况。
情况一：
远端UE先建立直连路径，在直连路径上建立PDU会话#1和QoS流#1，再触发中继UE建立非直连路径，在非直连路径上建立PDU会话#2和QoS流#2。
该情况下，直连路径上的UPF1作为非直连路径上的UPF#2与服务器通信的锚点。
示例性的，远端UE先在直连路径上建立PDU会话#1和QoS流#1，远端UE通过中继UE在非直连路径上建立PDU会话#2和QoS流#2，具体包括步骤S1420a1-步骤S1420a5，具体步骤如下：
S1420a1，远端UE在直连路径建立PDU会话#1和QoS流#1。
具体地，远端UE在直连路径上发起建立PDU会话#1的建立，从而可以实现远端UE和DN之间的数据传输。其中，PDU会话#1包括QoS流#1，该QoS流#1的标识可以是QFI-1。
S1420a2，远端UE执行中继UE的发现过程。
具体的，远端UE发送发现消息。
一种可能的实施方式中，中继UE根据发现消息发送宣称消息，在该宣称消息中可以包括指示信息#2，该指示信息#2用于指示支持多路传输。也即，该中继UE支持与远端UE在直连路径上和非直连路径上同时进行传输。换句话说，如果远端UE需要执行多路传输，可以选择支持多路传输的中继UE。
一种可能的实施方式中，如果远端UE需要执行多路传输，则远端UE发送请求消息#1，在该请求消息#1中请求支持多路传输，相应的，中继UE发送的响应消息中可以包括 指示信息#2指示支持多路传输。
S1420a3，远端UE通过PC5接口向中继UE发送请求消息#1。
具体地，远端UE通过PC5接口向中继UE发送请求消息#1，该请求消息#1用于中继UE在非直连路径上建立QoS流#2和PDU会话#2，该QoS流#2的标识可以是QFI-2。
该请求消息#1可以包括PC5 QoS flow的标识、PC5 QoS rule、数据包过滤的目的地址中的至少一个。
一种可选的理解，远端UE指示中继UE通过该PC5 QoS flow的标识的PC5 QoS flow上传输的数据可以执行多路传输，或者IP数据包能够匹配该PC5 QoS rule、Packet filter的数据可以执行多路传输。
该请求消息#1还包括“request PC5 QoS rule”和“request PC5 QoS参数”。其中，request PC5 QoS rule”中的数据包过滤的目的地址和QFI-1的QoS rule的数据包过滤的目的地址相同；“request PC5 QoS参数”和QoS流#1的QoS参数相同。
可以理解，远端UE可以在直连路径上获取QoS流#1的标识QFI-1和PDU会话#1的ID。
该请求消息#1可以是连接建立请求(link establishment request)消息，也可以是连接修改请求(link modification request)消息。
该请求消息#1还可以包括指示信息#1(作为第一指示的一例)，该指示信息#1用于指示通过PDU会话#1和PDU会话#2共同传输所述数据，从而可以获取PDU会话#2的ID和QoS流#2的标识QFI-2。
一种可能的实施方式中，远端UE向中继UE发送连接建立请求消息，用于请求中继UE建立QoS流#2和PDU会话#2，在该连接建立请求消息中包括指示信息#1，中继UE通过该指示信息#1在建立完QoS流#2和PDU会话#2之后可以向远端UE发送PDU会话#2的标识和QoS流#2的标识QFI-2。
另一种可能的实施方式中，远端UE发送连接建立请求消息，用于请求中继UE建立QoS流#2和PDU会话#2，中继UE在QoS流#2和PDU会话#2建立完成后，远端UE发送连接修改请求消息，在该连接修改请求消息中包括指示信息#1，中继UE通过该指示信息#1可以向远端UE发送PDU会话#2的标识和QoS流#2的标识QFI-2。
该指示信息#1可以是关联QoS流(paired QoS flow)指示信息(也可以称为L3 U2N relay multipath指示信息)。
S1420a4，中继UE建立或修改PDU会话#2和QoS流#2。
详细描述可参考方法1000中的步骤S1030-S1040，在此不再赘述。
S1420a5，中继UE通过非直连路径向远端UE发送响应消息#1。
具体地，中继UE通过PC5接口向远端UE发送响应消息#1，该响应消息#1包括QFI-2、PDU会话#2的ID、中继UE的ID#1(中继设备的第一标识的一例)，PC5 QoS rule和PC5 QoS参数。
该响应消息#1可以是连接修改接收(link modification accept)消息，也可以是连接建立接收(link establishment accept)消息。
可以理解，上述步骤S1420a2中，远端UE在连接建立请求消息中发送指示信息#1时，该响应消息#1可以是连接建立接收消息；远端UE在连接修改请求消息中发送指示信息#1 时，该响应消息#1可以是连接修改接收消息。
可以理解，中继UE根据响应消息#1中包括的QoS rule生成PC5 QoS rule，根据响应消息#6中包括的QoS参数生成PC5 QoS参数。
需要说明的是，中继UE根据指示信息#1向远端UE发送QFI-2、PDU会话#2的ID以及中继UE的ID#1。
可选的一种方式中，中继UE ID可以是GUTI、SUCI或S-TMSI。
情况二：远端UE先通过中继UE建立非直连路径，触发中继UE在非直连路径上建立PDU会话#2和QoS流#2，远端UE再建立直连路径，在直连路径上建立PDU会话#1和QoS流#1。
该情况下，非直连路径上的UPF2作为直连路径上的UPF#1与服务器侧通信的锚点。
示例性的，远端UE先通过中继UE在非直连路径上建立PDU会话#2和QoS流#2，远端UE在直连路径上建立PDU会话#1和QoS流#1，具体包括步骤S1420b1-步骤S1420b4，具体步骤如下：
S1420b1，远端UE执行中继UE的发现过程。
具体的，远端UE发送发现消息。
一种可能的实施方式中，中继UE根据发现消息发送宣称消息，在该宣称消息中可以包括指示信息#2，该指示信息#2用于指示支持多路传输。也即，该中继UE支持与远端UE在直连路径上和非直连路径上同时进行传输。换句话说，如果远端UE需要执行多路传输，可以选择支持多路传输的中继UE。
一种可能的实施方式中，如果远端UE需要执行多路传输，则远端UE发送请求消息#1，在该请求消息#1中请求支持多路传输，相应的，中继UE发送的响应消息中可以包括指示信息#2指示支持多路传输。
S1420b2，远端UE触发中继UE建立PDU会话#2和QoS流#2。
远端UE通过PC5接口向中继UE发送请求消息#1，该请求消息#1用于中继UE在非直连路径上建立QoS流#2和PDU会话#2，该QoS流#2的标识可以是QFI-2。
该请求消息#1可以包括PC5 QoS flow的标识、PC5 QoS rule、数据包过滤的目的地址中的至少一个。
一种可选的理解，远端UE指示中继UE通过该PC5 QoS flow的标识的PC5 QoS flow上传输的数据可以执行多路传输，或者IP数据包能够匹配该PC5 QoS rule、Packet filter的数据可以执行多路传输。
该请求消息#1还包括“request PC5 QoS rule”和“request PC5 QoS参数”。
S1420b3，远端UE在直连路径上建立PDU会话#1和QoS流#1。
具体地，远端UE通过直连路径向AMF#1(作为第一AMF的一例)发送请求消息#1’，该请求消息#1’用于请求SMF#1在直连路径上建立QoS流#1和PDU会话#1，该QoS流#1的标识可以是QFI-1。
可选的，远端UE在发送请求消息#1’请求建立QoS流#1和PDU会话#1过程中，该请求消息#1’可以包括指示信息#1，该指示信息#1用于指示远端UE同时通过该QoS流#1和QoS流#2进多路传输。
需要说明的是，该情况下，远端UE可以在发送请求消息#1’之前，从中继UE获取 PDU会话#2的标识和QoS流#2的标识QFI-2，并在该请求消息#1’中包括该PDU会话#2的标识和QoS流#2的标识QFI-2。
可选的，远端UE可以先建立直连PDU会话#1和QoS流#1之后，再去从中继UE获取PDU会话#2的标识和QoS流#2的标识QFI-2，用于后续多路传输的指示(步骤S1430)。
该请求消息#1’可以是连接修改请求(link modification request)消息，也可以是连接建立请求(link establishment request)消息。
该指示信息#1可以是关联QoS流(paired QoS flow)指示信息。
该远端UE可以通过UL NAS消息发送请求消息#1’给AMF#1。
AMF#1可以通过N11消息向SMF#1发送请求消息#1’，该N11消息可以是PDU会话创建上下文请求(Nsmf_PDUsession_createSMcontext request)消息等。
AMF#1和SMF#1是为远端UE服务的网络设备。
S1420b4，SMF#1向远端UE发送响应消息#1’。
具体地，SMF#1通过AMF#1向远端UE发送响应消息#1’。相应的，远端UE接收该响应消息#1’。
具体地，该响应消息#1’用于响应上述请求消息#1’。
该响应消息#1’包括QoS流#1的标识信息QFI-1和PDU会话#1的ID。
该响应消息#1’还可以包括QoS rule和QoS参数。
应理解，SMF#1根据指示信息#1向远端UE发送所述QFI-1和PDU会话#1的ID。
该响应消息#1’可以是PDU会话修改接收(PDU session modification accept)消息。
其中，SMF#1可以通过N11消息向AMF#1发送该响应消息#1’，该N11消息可以是N1N2消息传递(Namf_communication_N1N2MessageTransfer)消息。
上述步骤实现了直连路径和非直连路径的建立过程，以下步骤介绍直连路径和非直连路径的关联及创建UPF#1与UPF#2之间的传输通道的方法。
需要说明的是，远端UE可以通过直连路径触发PDU会话#1和QoS#1的修改，例如方法1200，远端UE也可以触发中继UE去修改PDU会话#2和QoS#2的修改，例如，方法1300，以下以远端UE触发通过直连路径触发PDU会话#1和QoS#1的修改为例进行说明。
S1430，远端UE通过直连路径向AMF#1发送请求消息#2。
具体地，远端UE在该请求消息#2(作为第一请求消息的一例)中携带信息#1(作为第一信息的一例)，第一信息可以包括QFI-2、PDU会话#2的ID、QFI-1、PDU会话#1的ID、中继UE的ID#1、指示信息#3(作为第三指示的一例)、指示信息#1(作为第一指示的一例)以及PDU会话修改请求(PDU session modification request)。
需要说明的是，上述步骤S1420b3中，远端UE在发送请求消息#1’中，包括指示信息#1用于指示远端UE同时通过该QoS流#1和QoS流#2进多路传输，并在请求消息#1’中还包括了PDU会话#2的标识和QoS流#2的标识QFI-2，则该步骤S1430可以不执行。
其中，指示信息#3用于指示锚点路径为直连路径或非直连路径，也即，直连路径的UPF#1作为锚点UPF与外部应用服务器进行通信，或者是，非直连路径的UPF#2作为锚点UPF与外部应用服务器进行通信。
示例性的，指示信息#3可以是锚点路径(anchor path)参数。
示例性的，上述QFI-1、PDU会话#1的ID可以包括至PDU会话修改请求中，该PDU会话修改请求可以直接封装在N1 SM container中对于AMF1不可见，由AMF1直接透传至SMF1。
示例性的，上述QFI-2、PDU会话#2的ID、中继UE的ID#1、指示信息#3、指示信息#1以及remote User ID参数可以和包括QFI-1、PDU会话#1的ID的PDU会话修改请求并列包括在请求消息#2中。
示例性的，上述QFI-1、PDU会话#1的ID、QFI-2、PDU会话#2的ID、中继UE的ID#1、指示信息#3、指示信息#1以及remote User ID参数可以和包括QFI-1、PDU会话#1的ID的PDU会话修改请求并列包括在请求消息#2中。
示例性的，该请求消息#2可以是NAS消息。
在步骤S1430之后，可以采用多种方式建立UPF#1和UPF#2之间的传输通道，例如，下图15(a)中示出了建立UPF#1和UPF#2之间传输通道的方法一，下图15(b)中示出了建立UPF#1和UPF#2之间传输通道的方法二，其中方法一包括步骤S1440-步骤S1447，方法二包括步骤S1450a-步骤S1470b。具体方法如下。
方法一：
S1440，AMF#1根据请求消息#2获取SMF#2的地址。
具体的，AMF#1(第一AMF的一例)根据请求消息#2中的中继UE的ID获取对应的SMF#2(第二SMF的一例)的地址信息。
一种可能的实施方式中，AMF#1向AUSF发送中继UE的ID#1(例如，中继UE的SUCI)，获取AUSF发送的SUPI(Subscription Permanent Identifier)，AMF#1再向UDM发送SUPI，PDU session ID，得到UDM发送的SMF地址。
例如，AMF#1调用AUSF提供的Nausf_UEAuthentication_authenticate获取中继UE的SUPI(Subscription Permanent Identifier)，然后调用UDM提供的Nudm_UECM_Get service获得服务于relay UE的PDU会话#2的SMF的地址信息。
另一种可能的实施方式中，AMF-1根据中继UE的ID(例如，中继UE的GUTI)，确定服务于中继UE的AMF(AMF#2)，再通过调用Namf_Communication_UEContextTransfer服务从AMF#2获取服务于中继UE的PDU会话#2的SMF的地址信息(SMF#2)。
可选的，在该步骤中，AMF#1还可以获取UPF#2(第二UPF的一例)的地址，该UPF#2的地址用于SMF#1确定该UPF#2与UPF#1是否相同。
一种可能的实施方式中，AMF#1从SMF#2获取UPF#2的地址。
S1441，AMF#1向SMF#1发送请求消息#3。
其中，请求消息#3中包括SMF#2的地址信息、QFI-1、PDU会话#1的ID、QFI-2、PDU会话#2的ID、中继UE的ID#2(中继设备的第二标识的一例)、指示信息#3、指示信息#1以及PDU会话修改请求。
其中，中继UE的ID#2是AMF#1根据中继UE的ID#1确定的。
可选的，请求消息#3还可以包括UPF#2的地址。
可选的一种理解，SMF#1根据UPF#2的地址确定UPF#2与UPF#1是否相同。
例如，当UPF#1与UPF#2相同时，可以直接按照方法800(b)进行下行数据的传输。
具体地，当UPF#1与UPF#2不同时,在一种可能的实施方式中，SMF#1可以指示数据进行多路传输，例如，按照多路传输进行方法800(a)进行下行数据的传输。
作为一个示例，AMF#1可以通过N11消息向SMF#1发送请求消息#3，该N11消息可以是(Namf_PDUSession_UpdateSMContext request)消息。
S1442a，SMF#1向UPF#1发送请求消息#4。
其中，请求消息#4包括QFI-2、PDU会话#2的ID、中继UE的ID#2、指示信息#3、指示信息#1以及PDU会话修改请求。
该请求消息#4用于指示UPF#1(第一UPF的一例)创建与UPF#2之间的传输通道，该传输通道用于传输适用于多路传输的数据。
具体的，SMF#1指示UPF#1分配传输通道的通道信息#1(第一通道信息的一例)，该通道信息#1用于UPF#2向UPF#1发送适用于多路传输的数据。
本申请中，通道信息#1可以是通道(tunnel)ID，例如，该tunnelID可以是全量通道端点标识(full qualified tunnel endpoint ID，F-TEID)。
具体的，SMF#1确定适用于UPF#1进行多路传输的规则信息，依据规则，UPF#1可以确定哪些数据适用于多路传输。
一种可能的实施方式中，SMF#1根据QFI-1、PDU会话#1的ID、QFI-2、PDU会话#2的ID、中继UE的ID#2生成第一规则和第二规则。
具体的，UPF#1为锚点UPF，SMF#1向UPF#1发送第一规则，第一规则用于指示UPF#1向UPF#2发送数据的部分或全部，使得UPF#2通过第二通信路径向远端UE发送从所述第一UPF接收的数据。
或者，UPF#1为锚点UPF，SMF#1向UPF#1发送第二规则，第二规则用于指示UPF#1将从UPF#2接收的数据发送至应用服务器。
或者，UPF#2为锚点UPF，SMF#1向所述UPF#1发送第一规则，第一规则用于指示UPF#1向UPF#2发送从远端UE接收的第一数据；或者
或者，UPF#2为锚点UPF，SMF#1向所述UPF#1发送第二规则，所述第二规则用于指示UPF#1向所述远端UE发送从UPF#2接收的数据。
一种可选的理解，若锚点路径为直连路径，针对下行数据，SMF#1指示UPF#1将确定的适用于多路传输的数据，通过直连路径传输至远端UE，并通过UPF#1和UPF#2之间的传输通道发送给UPF#2，由UPF#2通过非直连路径发送至远端UE；针对上行数据，SMF#1指示UPF#1将从该传输通道上收到的数据(来自于非直连路径上UPF#2的数据)和从直连路径上收到的数据，发往internet网络；若指示信息#3指示锚点路径为非直连路径，针对上行数据，SMF#1指示UPF#1将确定的适用于多路传输的数据(通过直连路径接收的远端UE数据)，通过该传输通道发送给UPF#2，由UPF#2将该数据与从非直连路径上收到的远端UE数据发送至internet网络；针对下行数据，SMF#1指示UPF#1从该传输通道上收到的数据(来自于UPF#2的数据)，通过直连路径发往远端UE。
可选的一种实施方式中，请求消息#3还包括所述指示信息#1和指示信息#5(第二指示的一例)，所述指示信息#5用于描述第一数据。
需要说明的是，请求消息#2只包括指示信息#1时，不强调具体的传输粒度，例如可以以QoS流为粒度；请求消息#2包括指示信息#1和指示信息#5时，可以以指示信息#5 限定的粒度进行多路传输。例如，指示信息#5可以限定以业务数据流为粒度，例如Service data flow(SDF)的粒度，也可以理解为，指示信息#5进一步描述了第一数据中的需要多路传输的数据类型，例如，该类型可以是数据的业务类型。
可选的一种理解，远端UE在同一个QoS流中同时传输多个应用的数据，但远端UE可能只需要对其中一个或部分应用的数据进行多路传输，该情况下，针对UPF#1为锚点，远端UE可以在请求消息#2中包括第一QoS rule，该第一QoS rule标识了需要进行多路传输的特定应用的数据，该第一QoS rule用于SMF#1向UPF#1指示该特定应用的数据需要进行多路传输。针对UPF#2为锚点，远端UE可以在从中继UE获取PDU会话#2的标识和QoS流#2的标识QFI-2时，向中继UE指示第一PC5 QoS rule，该第一PC5 QoS rule标识了需要进行多路传输的应用的数据。中继UE根据该第一PC5 QoSrule向SMF#2发送第一UU QoS流，SMF#2根据该第一UU QoS流指示UPF#2对应的第一PDR，具体指示与该PDR对应的数据才能传输至UPF#1，否则需要通过UPF#2直接传输至网络。
示例性的，该请求消息#4可以是N4会话修改请求(N4 sessionmodification request)消息。
S1442b，SMF#1从UPF#1接收响应消息#2。
具体的，响应消息#2包括通道信息#1(tunnel info-1)。
示例性的，该响应消息#2可以是N4会话修改响应(N4 sessionmodification response)消息。
S1443，SMF#1向SMF#2发送请求消息#5。
具体的，SMF#1根据SMF#2的地址向SMF#2发送请求消息#5。
其中，请求消息#5包括通道信息#1(tunnel info-1)、QFI-1、QFI-2、PDU会话#2的ID、PDU会话#2的ID、中继UE的ID#2、指示信息#3、指示信息#1以及PDU会话修改请求(PDU session modification request)。
作为一个示例，SMF#1可以通过N11消息向SMF#2发送请求消息#5，该N11消息可以是(Namf_PDUSession_UpdateSMContext request)消息。
S1444a，SMF#2向UPF#2发送请求消息#6。
其中，请求消息#6包括(tunnel info-1)、QFI-1、QFI-2、PDU会话#2的ID、中继UE的ID#2、指示信息#3、指示信息#1以及PDU会话修改请求(PDU session modification request)。
该请求消息#6用于指示UPF#2创建与UPF#1之间的传输通道，该传输通道用于传输适用于多路传输的数据。
具体的，SMF#2指示UPF#2分配传输通道的通道信息#2，该通道信息#2用于UPF#1向UPF#2发送适用于多路传输的数据。
本申请中，通道信息#2可以是通道(tunnel)ID，例如，该tunnelID可以是全量通道端点标识(full qualified tunnel endpoint ID，F-TEID)。
具体的，SMF#2指示UPF#2确定适用于多路传输的数据的规则信息，依据此规则，UPF#2可确定适用于多路传输的数据。
一种可能的实施方式中，SMF#2根据从SMF#1接收的QFI-2、PDU会话#2的ID、中继UE的ID#2和远端UE的ID生成第三规则和第四规则。
一种可能的实施方式中，SMF#2根据从SMF#1接收的QFI-2、PDU会话#2的ID、中继UE的ID#2生成第三规则和第四规则。
具体的，UPF#1为锚点UPF，SMF#2向UPF#2发送第三规则，第三规则用于指示UPF#2向UPF#1发送从远端UE接收数据；
或者，UPF#1为锚点UPF，SMF#2向UPF#2发送第四规则，第四规则用于指示UPF#2向远端UE发送从UPF#1接收数据。
或者，UPF#2为锚点UPF，SMF#2向所述UPF#2发送第三规则，所述第三规则用于指示所述UPF#2向UPF#1发送第一数据的部分或全部，使得第一UPF#1通过第一通信路径向远端UE发送从UPF#2接收的数据；或者
或者，UPF#2为锚点UPF，SMF#2向UPF#2发送第四规则，所述第四规则用于指示UPF#2将从UPF#1接收的数据发送至所述应用服务器。
一种可选的理解，若锚点路径为非直连路径，针对下行数据，SMF#2指示UPF#2将确定的适用于多路传输的数据，通过该传输通道发送给UPF#1，针对上行数据，SMF#2指示UPF#2从该传输通道上收到的数据(来自于UPF#1的数据)，发往internet网络；若指示信息#3指示锚点路径为直连路径，针对上行数据，SMF#2指示UPF#2将确定的适用于多路传输的数据(通过QoS流#2接收的UE数据)，通过该传输通道发送给UPF#1，针对下行数据，SMF#2指示UPF#2从该传输通道上收到的数据(来自于UPF#1的数据)，通过非直连路径QoS流#2发往UE。
示例性的，该请求消息#6可以是N4会话修改请求(N4 sessionmodification request)消息。
S1444b，SMF#2从UPF#2接收响应消息#3。
具体的，响应消息#3包括通道信息#2(tunnel info-2)。
示例性的，该响应消息#3可以是N4会话修改响应(N4 sessionmodification response)消息。
S1445，SMF#1从SMF#2接收响应消息#4。
具体的，响应消息#4包括通道信息#2(tunnel info-2)。
作为一个示例，SMF#2可以通过N11消息向SMF#1发送响应消息#4，该N11消息可以是(Namf_PDUSession_UpdateSMContext response)消息。
S1446，SMF#1向UPF#1发送请求消息#7。
其中，请求消息#7中包括通道信息#2(tunnel info-2)。
示例性的，该请求消息#7可以是N4会话修改请求(N4 sessionmodification request)消息。
S1447，UPF#1向SMF#1发送响应消息#5。
可以理解，步骤S1451-步骤S1457为SMF#1和SMF#2指示UPF#1与UPF#2建立通道并交换通道信息的过程，交换完通道信息后，UPF#1通过UPF#2分配的tunnel info-2向UPF#2发送数据，UPF#2通过UPF#1分配的tunnel info-1向UPF#1发送数据。
方法二：
AMF#1接收到远端UE的请求消息#2后，AMF#1可以同时向AMF#2和SMF#1请求分别执行PDU会话#2和PDU会话#1的修改流程，并同时请求创建UPF#1和UPF#2之间 的传输通道。
S1450a，AMF#1向AMF#2发送请求消息#8。
具体地，AMF#1根据请求消息#2中包括的中继UE的ID#2确定为该中继UE提供服务的AMF#2的地址，进一步的，向AMF#2发送请求消息#8。
本申请中，该请求消息#8包括QFI-2、PDU会话#2的ID、中继UE的ID#2、指示信息#3、指示信息#1以及PDU会话#2的修改请求(PDU session modification request)。
可选的，请求消息#8还可以包括UPF#2的地址。
作为一个示例，AMF#1可以通过N11消息向AMF#2发送请求消息#8，该N11消息可以是(Namf_communication_UEContextTransfer request)消息。
S1451a，AMF#2向SMF#2发送请求消息#9。
本申请中，该请求消息#9包括QFI-2、PDU会话#2的ID、中继UE的ID#2、指示信息#3、指示信息#1以及PDU会话#2的修改请求(PDU session modification request)。
可选的，请求消息#9还可以包括UPF#2的地址。
作为一个示例，AMF#1可以通过N11消息向AMF#2发送请求消息#9，该N11消息可以是(Namf_communication_UEContextTransfer request)消息。
S1452a，SMF#2向UPF#2发送请求消息#10。
其中，请求消息#10包括QFI-2、PDU会话#2的ID、中继UE的ID#2、指示信息#3、指示信息#1以及PDU会话#2修改请求(PDU session modification request)。
该请求消息#10用于指示UPF#2创建与UPF#1之间的传输通道，该传输通道用于传输适用于多路传输的数据。
具体的，SMF#2指示UPF#2确定适用于多路传输的数据的规则信息，依据此规则，UPF#2可确定哪些数据适用于多路传输。
其中，具体的规则信息可以参考步骤S1444a，不再赘述。
具体的，SMF#2指示UPF#2分配传输通道的通道信息#2，该通道信息#2用于UPF#1向UPF#2发送适用于多路传输的数据。
本申请中，通道信息#2可以是通道(tunnel)ID，例如，该tunnelID可以是全量通道端点标识(full qualified tunnel endpoint ID，F-TEID)。
示例性的，该请求消息#10可以是N4会话修改请求(N4 sessionmodification request)消息。
S1453a，SMF#2从UPF#2接收响应消息#6。
具体的，响应消息#6包括通道信息#2(tunnel info-2)。
示例性的，该响应消息#6可以是N4会话修改响应(N4 sessionmodification response)消息。
S1454a，SMF#2通过AMF#2向AMF#1发送响应消息#7。
具体的，响应消息#7包括通道信息#2(tunnel info-2)。
示例性的，该响应消息#7可以是N4会话修改响应(N4 sessionmodification response)消息。
以上步骤S1450a-步骤S1454a为PDU会话#2的修改流程和通道信息#2的创建过程。
以下介绍PDU会话#1的修改流程和通道信息#1的创建过程。
S1450b，AMF#1向SMF#1发送请求消息#11。
其中，请求消息#11中包括QFI-1、PDU会话#1的ID、QFI-2、PDU会话#2的ID、中继UE的ID#2、指示信息#3、指示信息#1以及PDU会话#1的修改请求(PDU session modification request)。
可选的，请求消息#11还可以包括UPF#2的地址。
可选的一种理解，SMF#1根据UPF#2的地址确定UPF#2与UPF#1是否相同。
例如，当UPF#1与UPF#2相同时，可以直接按照方法800(b)进行下行数据的传输。
具体地，当UPF#1与UPF#2不同时,在一种可能的实施方式中，SMF#1可以指示数据进行多路传输，例如，按照多路传输进行方法800(a)进行下行数据的传输。
作为一个示例，AMF#1可以通过N11消息向SMF#1发送请求消息#11，该N11消息可以是(Namf_PDUSession_UpdateSMContext request)消息。
S1451b，SMF#1向UPF#1发送请求消息#14。
其中，请求消息#14包括QFI-2、PDU会话#2的ID、中继UE的ID#2、指示信息#3、指示信息#1以及PDU会话#1的修改请求(PDU session modification request)。
该请求消息#14用于指示UPF#2创建与UPF#1之间的传输通道，该传输通道用于传输适用于多路传输的数据。
具体的，SMF#1指示UPF#1确定适用于多路传输的数据的规则信息，依据此规则，UPF#1可确定哪些数据适用于多路传输。
其中，具体的规则信息可以参考步骤S1442a，不再赘述。
具体的，SMF#1指示UPF#1分配传输通道的通道信息#1，该通道信息#1用于UPF#2向UPF#1发送适用于多路传输的数据。
本申请中，通道信息#1可以是通道(tunnel)ID，例如，该tunnelID可以是全量通道端点标识(full qualified tunnel endpoint ID，F-TEID)。
示例性的，该请求消息#14可以是N4会话修改请求(N4 sessionmodification request)消息。
S1452b，SMF#1从UPF#1接收响应消息#8。
具体的，响应消息#8包括通道信息#1(tunnel info-1)。
示例性的，该响应消息#8可以是N4会话修改响应(N4 sessionmodification response)消息。
S1453b，SMF#1向AMF#1发送响应消息#9。
具体的，响应消息#9包括通道信息#1(tunnel info-1)。
示例性的，该响应消息#9可以是N4会话修改响应(N4 sessionmodification response)消息。
以上步骤S1450b-步骤S1453b为PDU会话#1的修改流程和通道信息#1的创建过程。
S1460，AMF#1与AMF#2交互通道信息#1(tunnel info-1)和通道信息#2(tunnel info-2)。
S1470a，AMF#1通过SMF#1向UPF#1发送通道信息#2。
S1470b，AMF#2通过SMF#2向UPF#2发送通道信息#1。
可以理解，上述步骤S1450a-步骤S1454a和步骤S1450b-步骤S1453b可以同时执行。
可以理解，上述步骤S1470a和步骤S1470b可以同时执行。
需要说明的是，方法1000和方法1100中PDU会话的修改流程和通道信息的创建过程也适用于该方法1400，本申请实施例对此不作限定。
S1480，远端UE通知中继UE启动多路传输。
应理解，上述两种方式仅为示例性说明，实际实施中PDU会话的修改流程和通道信息的创建过程可能存在多种方式，例如，本实施例中的方法1000和方法1100，可以实现PDU会话的修改和通道信息的创建均可适用于本申请实施例，本申请对此不作限定。
以下介绍适用于方法1400的数据传输过程。
以图15所示架构为例，当直连路径为锚点路径时，即，UPF#1为锚点UPF，与应用服务器进行通信，该架构下，具体传输方式如下。
对于上行数据：
a.远端UE基于直连链路的IP地址及端口号生成上行IP数据包#1并在直连链路上发送上行传输；
远端UE基于在直连链路上生成的IP数据包，基于非直连链路的IP地址及端口号生成在非直连链路上发送的上行数据包#2，即有两层IP包头，并将该具有两层IP包头的数据包#2在非直连链路上发送上行传输。
b.UPF#1从UPF#2接收数据包#2，去除一层IP包头后与从直连链路接收到的数据包#1一起执行IP包排序，去重等操作后向应用服务器传递。
需要说明的是，中继UE可能会服务于多个远端UE，因此中继UE建立或修改的QoS流#2可能传输多个远端UE的数据，因此对于锚点UPF来说，无法区分通过同一QoS流传输的数据属于哪一个远端UE。
一种可能的实施方式中，中继UE可以分配或建立专用的QoS flow用于传输远端UE要执行多路传输的数据，进一步的，非直连路径上的SMF#2可以根据该专用的QoS flow向UPF#2配置识别规则。该识别规则用于UPF#2确定该该专用的QoS flow对应的数据需要进行多路传输。
一种可选的理解，该QoS流#2可以是中继UE分配或建立的专用QoS flow，只传输该远端UE的数据，对于UPF#2来说，针对上行数据，从该QoS流#2传输的数据都可以通过传输通道进行传输。例如，以UPF#1为锚点为例，UPF#2可以将从该专用QoS flow上收到的数据发送到UPF-1，而从其他QoS flow上收到的数据，则直接通过N6接口发送到Internet。
另一种可能的实施方式中，远端UE可以向AMF#1发送远端UE身份(remote User ID)信息，针对上行数据，当UPF#1为锚点UPF时，该远端UE身份(remote User ID)信息用于SMF#2确定远端UE在非直连路径上的IP地址和/或TDP/UDP。从而指示UPF#2可以根据该远端UE的IP地址和/或TDP/UDP确定进行多路传输的上行数据；当UPF#2为锚点UPF时，SMF#2可以指示UPF#2根据该远端UE的IP地址和/或TDP/UDP确定传输至UPF#1的下行数据，即，对于UPF#2来说，下行数据中包括了多个远端UE的数据，根据SMF#2指示的IP地址和/或TDP/UDP可以确定需要进行多路传输的远端UE的数据，也就是说，UPF#2将SMF#2指示的IP地址和/或TDP/UDP对应的远端UE的数据发送至UPF#1通过直连路径发送，并同时通过非直连路径发送，其余的数据可以只通过非直连路径发送，换句话说，其余的数据不需要进行多路传输。
可选的一种理解，远端UE可以通过请求消息#2向AMF#1发送远端UE身份(remote User ID)信息。
另一种可能的实施方式中，中继UE对进行多路传输的数据设置标识信息#a，该标识信息#a用于UPF#2确定进行多路传输的QoS流。
另一种可能的实施方式中，中继UE可以从远端UE获取进行多路传输的QoS规则#x。该QoS规则#x用于SMF#2确定远端UE进行多路传输的QoS流，从而指示UPF#2可以确定对该QoS流的数据进行上行多路传输。
对于下行数据：
a.UPF#1向UPF#2发送数据包#1，UPF#2基于中继UE的IP地址及端口号再增加一层IP包头生成下行数据包#2，在非直连链路上发送给远端UE；或者，UPF#1基于中继UE的IP地址及端口号在数据包#1上再增加一层IP包头生成数据包#2，再发送给UPF#2，在非直连链路上发送给远端UE。
可选的，UPF#1从UPF#2获取中继UE的IP地址及端口号，具体流程可参考方法1400中UPF#2向UPF#1传递CN Tunnel Info-2的过程。
可选的，UPF#1从UPF#2获取中继UE的IP地址及端口号，具体方法可以参考图10方法1000中的步骤S1070-1091中获取PDR的方式，UPF#1获取了非直连路径的QoS流#2对应的PDR，根据该PDR可以确定中继UE的IP地址及端口号。
b1.远端UE从非直连链路上收到的下行数据包#2，去除一层IP包头后和从直连路径上收到的数据包#1执行IP包排序，去重等操作后向应用层传递。
b2.远端UE可以从直连路径和非直连路径上选择一个路径接收下行数据包，例如，远端UE可以接收直连路径上的数据包#1执行IP包排序，去重等操作后向应用层传递，该情况下默认非直连路径上的下行数据包#2被丢弃；再例如，远端UE可以接收非直连路径上的数据包#2，去除一层IP报头后执行IP包排序，去重等操作后向应用层传递，该情况下默认直连路径上的下行数据包#1被丢弃。
可以理解，上述b1和b2为两种可选的实施方案。
示例性的，当远端UE确定多路传输具体用于可靠性传输时，可以执行上述方案b2，当远端UE确定多路传输具体用于负载均衡传输时，可以执行上述方案b1。
以图15所示架构为例，当非直连路径为锚点路径时，即，UPF#2为锚点UPF，与应用服务器进行通信，该架构下，具体传输方式如下。
对于上行数据：
a.远端UE基于非直连链路的IP地址及端口号生成上行IP数据包#3并在非直连链路上发送上行传输；
远端UE基于在非直连链路上生成的IP数据包#3，基于直连链路的IP地址及端口号生成在直连链路上发送的上行数据包#4，即有两层IP包头，并将该具有两层IP包头的数据包#4在直连链路上发送上行传输。
b.UPF#2从UPF#1接收数据包#4，去除一层IP包头后与从非直连链路接收到的数据包#3一起执行IP包排序，去重等操作后向应用服务器传递。
可选的一种实施方式中，中继UE从远端UE接收到IP数据包#3时，可以添加标识信息#a，该标识信息#a用于UPF#2确定进行多路传输的QoS流，从而将该数据与从UPF#1 收到的数据包#4共同执行IP去重排序等操作。
对于下行数据：
a.UPF#2向UPF#1发送数据包#3，UPF#1基于直连路径的IP地址及端口号生成下行数据包#4，在直连链路上发送给远端UE；或者，UPF#2基于直连路径的IP地址及端口号在数据包#3上再增加一层IP包头生成数据包#4，再发送给UPF#1，在直连链路上发送给远端UE。
远端UE从直连路径上收到的下行数据包#4，去除一层IP包头后和从非直连路径上收到的数据包#3执行IP包排序，去重等操作后向应用层传递。
可选的，UPF#2从UPF#1获取直连路径的IP地址及端口号，具体流程可参考方法1400中UPF#1向UPF#2传递CN Tunnel Info-1的过程。
可选的，UPF#2从UPF#1获取中继UE的IP地址及端口号，具体方法可以参考图10方法1100中的步骤S1160-1180中获取QFI1对应的PDR的方式。
b.远端UE从直连链路上收到的下行数据包#4，去除一层IP包头后和从非直连路径上收到的数据包#3执行IP包排序，去重等操作后向应用层传递。
根据上述技术方案，远端UE的直连路径上的UPF#1可以和非直连路径的UPF#2建立传输通道，使得远端UE可以通过该直连路径和非直连路径传输直连路径的QoS流#1的部分或全部数据，或传输非直连路径,QoS流#2的部分或全部数据，实现数据的冗余传输或负载均衡传输或切换传输。
以上，结合图5至图15详细说明了本申请实施例提供的方法。以下，结合图16至图17详细说明本申请实施例提供的装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
该装置用于实现上述实施例及相关实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图16示出了本申请实施例提供的一种数据传输的装置1600的示意图。
该装置1600包括收发单元1610，收发单元1610可以用于实现相应的通信功能，收发单元16210还可以称为通信接口或通信单元。
该装置1600还可以包括处理单元1620，处理单元1620可以用于进行数据处理。
可选地，该装置1600还包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元1620可以读取存储单元中的指令和/或数据，以使得装置实现前述各个方法实施例中不同设备的动作。
作为一种设计，该装置1600用于执行上文各个方法实施例中第一终端设备(远端UE)所执行的动作。
具体地，收发单元1610，用于获取第一信息，所述第一信息包括所述第一通信路径的第一会话的标识、所述第二通信路径的第二会话的标识以及所述中继设备的第一标识；所述收发单元1610还用于向第一移动性管理实体发送包括所述第一信息的第一请求消息，所述第一请求消息用于请求通过所述第一会话和所述第二会话共同传输第一数据。
作为一种设计，该装置1600用于执行上文各个方法实施例中中继设备(中继UE)所 执行的动作。
具体地，收发单元1610，用于获取第三信息，所述第三信息包括所述第一通信路径的第一会话的标识、所述第二通信路径的第二会话的标识以及所述第一终端设备的第一标识；所述收发单元1610还用于所述中继设备向第二移动性管理功能实体发送包括所述第三信息的第二请求消息，所述第二请求消息用于请求通过所述第一会话和所述第二会话共同传输第一数据。
作为一种设计，该装置1600用于执行上文各个方法实施例中核心网设备所执行的动作。
具体地，收发单元1610，用于从所述第一终端设备接收第一请求消息，所述第一请求消息用于请求通过所述第一通信路径的第一会话和所述第二通信路径的第二会话共同传输第一数据，所述第一请求消息包括第一信息，所述第一信息包括所述第一会话的标识、所述第二会话的标识以及所述中继设备的第一标识；在接收所述第一请求消息之后，收发单元1610还用于用于第一用户面功能实体和第二用户面功能实体传输所述第一数据，所述第一用户面功能实体服务于所述第一通信路径，所述第二用户面功能实体服务于所述第二通信路径；其中，所述第一用户面功能实体和所述第二用户面功能实体中的一个与应用服务器之间传输所述第一数据。
作为一种设计，该装置1600用于执行上文各个方法实施例中中继设备所执行的动作。
具体地，收发单元1610，用于从所述中继设备接收第二请求消息，所述第二请求消息用于请求通过所述第一通信路径的第一会话和所述第二通信路径的第二会话共同传输第一数据，所述第二请求消息包括第三信息，所述第三信息包括所述第一会话的标识、所述第二会话的标识以及所述第一终端设备的第一标识；在接收所述第二请求消息之后，收发单元1610还用于在第一用户面功能实体和第二用户面功能实体之间传输所述第一数据，所述第一用户面功能实体服务于所述第一通信路径，所述第二用户面功能实体服务于所述第二通信路径，其中，所述第一用户面功能实体和所述第二用户面功能实体中的一个与应用服务器之间传输所述第一数据。
该装置1600可实现对应于根据本申请实施例的方法实施例中的终端设备或核心网设备执行的步骤或者流程，该装置1600可以包括用于执行图12、图13、图14所示实施例中的第一终端设备(远端EU)或核心网设备(第一AMF，第二AMF，第一SMF，第二SMF，第一UPF，第二UPF)执行的方法的单元。
应理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为一种设计，该装置1600用于执行上文各个方法实施例中终端设备所执行的动作。
具体地，处理单元1620，用于获取第一信息，所述第一信息用于第一网络设备通过所述第一通信路径向所述第一终端设备传输第一数据，所述第一信息包括第一包检测规则PDR；收发单元1610，用于通过第二通信路径向第二网络设备发送第一消息，所述第一消息包括所述第一信息和第一指示信息，所述第一指示信息用于指示通过所述第一通信路径和/或所述第二通信路径传输所述第一数据。
可选地，该收发单元1610还用于向第二终端设备发送第一请求消息，所述第一请求消息用于请求在所述第一通信路径上建立第一QoS流，所述第一请求消息包括第二指示 信息，所述第二指示信息用于获取所述第一信息；所述第一终端设备从所述第二终端设备接收所述第一信息。
可选地，该第一信息是所述第一终端设备在所述第一通信路径上建立第一QoS流中获取的。
可选地，该第一信息还包括所述第一通信路径上的第一QoS流信息，所述第一QoS流信息包括第二终端设备的标识、所述第一QoS流的标识QFI、所述第一QoS流对应的PDU会话的标识。
可选地，该第一信息还包括第三指示信息，所述第三指示信息用于指示进行可靠性传输或负载均衡传输。
可选地，上述第一通信路径为所述第一终端设备通过所述第二终端设备连接所述第一网络设备的通信路径，或者，所述第一通信路径为所述第一终端设备直接连接所述第一网络设备的通信路径。
可选地，上述第一通信路径包括至少一个QoS流，所述第一QoS流信息包括所述第一QoS流对应的PDR，所述第一QoS流为所述至少一个QoS流中的一个。
该装置1600可实现对应于根据本申请实施例的方法实施例中的终端设备执行的步骤或者流程，该装置1600可以包括用于执行图5所示实施例中的第一终端设备执行的方法的单元，或包括图7、图9、图10和图11所示实施例中的远端UE执行的方法的单元。
应理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为一种设计，该装置1600用于执行上文各个方法实施例中第一网络设备所执行的动作。
具体地，收发单元1610，用于接收第一信息和第二信息，所述第一信息用于所述第一网络设备通过第一通信路径向第一终端设备传输数据，所述第二信息用于所述第一网络设备通过第二通信路径向所述第一终端设备传输数据；还用于接收第一数据，通过所述第一通信路径和/或第二通信路径向所述第一终端设备发送所述第一数据。
可选地，处理单元1620用于根据所述第一信息确定目的地址和源地址；所述第一网络设备根据所述目的地址和源地址对所述第一数据进行处理，发送处理后的所述第一数据。
可选地，所述第一通信路径为所述第一终端设备通过第二终端设备接收所述第一网络设备发送的数据的通信路径。
可选地，收发单元1610，还用于接收第三指示信息，所述第三指示信息用于指示进行可靠性传输或负载均衡传输。
可选地，当所述第三指示信息指示可靠性传输，处理单元1620用于将所述第一数据的IP包进行复制，收发单元1610用于分别通过所述第一通信路径和所述第二通信路径向所述第一终端设备发送所述第一数据的IP包；或者，当所述第二指示信息指示负载均衡传输，处理单元1620用于将所述第一数据的IP包进行分流，收发单元1610用于分别通过所述第一通信路径和所述第二通信路径向所述第一终端设备发送所述第一数据的IP包。
可选地，处理单元1620，还用于根据所述第三指示信息确定通过所述第一通信路径和/或第二通信路径向所述第一终端设备发送所述第一数据；或者，根据所述第一信息和 所述第二信息确定通过所述第一通信路径和/或第二通信路径向所述第一终端设备发送所述第一数据。
可选地，收发单元1610，还用于将所述第一数据发送给第三网络设备，由所述第三网络设备通过所述第一通信路径发向所述第一终端设备。
可选地，所述第一通信路径包括至少一个QoS流，所述第一QoS流信息包括所述第一QoS流对应的PDR，所述第一QoS流为所述至少一个QoS流中的一个，所述第二通信路径包括至少一个QoS流，所述第二QoS流信息包括所述第二QoS流对应的PDR，所述第人QoS流为所述至少一个QoS流中的一个。
可选地，收发单元1610还用于接收第一QoS流的标识QFI，将所述第一数据发送给第三网络设备，收发单元1610具体用于将所述第一数据封装到GTP消息，通过第一通道将所述GTP消息发送至所述第三网络设备，所述GTP消息包括所述第一QoS流的标识QFI，所述第一通道用于所述第一网络设备和所述第三网络设备进行数据传输。
该装置1600可实现对应于根据本申请实施例的方法实施例中的第一网络设备执行的步骤或者流程，该装置1600可以包括用于执行图5所示实施例中的第一网络设备执行的方法的单元，或包括图7、图9、图10和图11所示实施例中的UPF#1或UPF#2执行的方法的单元。
应理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
图17示出了本申请实施例提供的一种数据传输的装置1700的示意图。该装置1700包括处理器1710，处理器1710与存储器1720耦合，存储器1720用于存储计算机程序或指令和/或数据，处理器1710用于执行存储器1720存储的计算机程序或指令，或读取存储器1720存储的数据，以执行上文各方法实施例中的方法。如图17所示，该装置1700还包括收发器1730，收发器1730用于信号的接收和/或发送。例如，处理器1710用于控制收发器1730进行信号的接收和/或发送。
可选地，处理器1710为一个或多个。
可选地，存储器1720为一个或多个。
可选地，该存储器1720与该处理器1710集成在一起，或者分离设置。
作为一种方案，该装置1700用于实现上文各个方法实施例中由第一终端设备、第二终端设备、第一网络设备或第二网络设备执行的操作。
例如，处理器1710用于执行存储器1720存储的计算机程序或指令，以实现上文各个方法实施例中网络设备的相关操作。例如，图12、图13、图14所示实施例中的第一AMF、第二AMF、第一UPF、第二UPF、第一SMF和第二SMF执行的方法；例如，图5所示实施例中的第一网络设备执行的方法，或图7、图9、图10和图11中任一个所示实施例中的UPF#1执行的方法。
又如，处理器1710用于执行存储器1720存储的计算机程序或指令，以实现上文各个方法实施例中终端设备的相关操作。例如，图12、图13、图14所示实施例中的第一终端设备和中继设备执行的方法；例如，图5所示实施例中的第一终端设备执行的方法，或图7、图9、图10和图11中任一个所示实施例中的远端UE执行的方法。
应理解，本申请实施例中提及的处理器可以是中央处理单元(central processing unit， CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器和/或非易失性存储器。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。例如，RAM可以用作外部高速缓存。作为示例而非限定，RAM包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请还提供了一种计算机可读介质，其上存储有计算机程序，该计算机程序被计算机执行时实现上述任一方法实施例的功能。
本申请还提供了一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
本申请还提供一种系统，其包括前述的第一接入网设备、第二接入网设备、接入与移动性管理功能设备和第一会话管理功能设备。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬 盘(solid state disk，SSD))等。
在本申请实施例中，“示例的”、“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
应理解，说明书通篇中提到的“实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各个实施例未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。本申请中所有节点、消息的名称仅仅是本申请为描述方便而设定的名称，在实际网络中的名称可能不同，不应理解本申请限定各种节点、消息的名称，相反，任何具有和本申请中用到的节点或消息具有相同或类似功能的名称都视作本申请的方法或等效替换，都在本申请的保护范围之内。
还应理解，在本申请中，“当…时”、“若”以及“如果”均指在某种客观情况下UE或者基站会做出相应的处理，并非是限定时间，且也不要求UE或基站实现时一定要有判断的动作，也不意味着存在其它限定。
需要说明的是，本申请实施例中，“预先设定”、“预先配置”等可以通过在设备(例如，终端设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定，例如本申请实施例中预设的规则、预设的常数等。
另外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
本文中术语“……中的至少一个”或“……中的至少一种”，表示所列出的各项的全部或任意组合，例如，“A、B和C中的至少一种”，可以表示：单独存在A，单独存在B，单独存在C，同时存在A和B，同时存在B和C，同时存在A、B和C这六种情况。本文中的“至少一个”表示一个或者多个。“多个”表示两个或者两个以上。
应理解，在本申请各实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。术语“包括”、“包含”、“具有”及它们的变形都意味着“包括但不限于”，除非是以其他方式另外特别强调。
应理解，在本申请的各种实施例中，第一、第二以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围。例如，区分不同的信息等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装 置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (47)

  1. 一种数据传输的方法，其特征在于，应用于包括第一终端设备的第一通信路径和第二通信路径的系统中，所述第一通信路径是所述第一终端设备与网络连接的直连路径，所述第二通信路径是所述第一终端设备通过中继设备与网络连接的非直连路径，所述方法包括：
    所述第一终端设备获取第一信息，所述第一信息包括所述第一通信路径的第一会话的标识、所述第二通信路径的第二会话的标识以及所述中继设备的第一标识；
    所述第一终端设备向第一移动性管理实体发送包括所述第一信息的第一请求消息，所述第一请求消息用于请求通过所述第一会话和所述第二会话共同传输第一数据。
  2. 根据权利要求1所述的方法，其特征在于，所述第一信息还包括第一服务质量流的标识和/或第二服务质量流的标识，所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一请求消息还包括第一指示，所述第一指示用于指示通过所述第一会话和所述第二会话共同传输所述第一数据，或者
    所述第一请求消息还包括所述第一指示和第二指示，所述第二指示用于描述所述第一数据。
  4. 根据权利要求1-3项中任一项所述的方法，其特征在于，
    所述第一数据包括通过第一服务质量流传输的全部数据或部分数据，或者，
    所述第一数据包括通过第二服务质量流传输的全部数据或部分数据；
    所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
  5. 根据权利要求1-4项中任一项所述的方法，其特征在于，所述第二会话的标识以及所述中继设备的第一标识是所述第一终端设备从所述中继设备获取的。
  6. 根据权利要求1-5项中任一项所述的方法，其特征在于，所述第一请求消息还包括第三指示，所述第三指示用于指示所述第一通信路径为锚点路径，或者，所述第三指示用于指示所述第二通信路径为锚点路径，
    所述第一通信路径和所述第二通信路径通过服务于所述锚点路径的用户面功能实体用户面功能实体与应用服务器通信。
  7. 根据权利要求1-6项中任一项所述的方法，其特征在于，所述第一请求消息还包括所述第一终端设备的标识，所述第一终端设备的标识对应所述第二通信路径。
  8. 一种数据传输的方法，其特征在于，应用于包括第一终端设备的第一通信路径和第二通信路径的系统中，所述第一通信路径是所述第一终端设备与网络连接的直连路径，所述第二通信路径是所述第一终端设备通过中继设备与网络连接的非直连路径，所述方法包括：
    所述中继设备获取第三信息，所述第三信息包括所述第一通信路径的第一会话的标识、所述第二通信路径的第二会话的标识以及所述第一终端设备的第一标识；
    所述中继设备向第二移动性管理功能实体发送包括所述第三信息的第二请求消息，所 述第二请求消息用于请求通过所述第一会话和所述第二会话共同传输第一数据。
  9. 根据权利要求8所述的方法，其特征在于，所述第三信息还包括第二服务质量流的标识和/或第一服务质量流的标识，所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
  10. 根据权利要求8或9所述的方法，其特征在于，所述第二请求消息还包括第一指示，所述第一指示用于指示通过所述第一会话和所述第二会话共同传输所述第一数据，或者
    所述第二请求消息还包括所述第一指示和第二指示，所述第二指示用于描述所述第一数据。
  11. 根据权利要求8-10项中任一项所述的方法，其特征在于，
    所述第一数据包括通过第一服务质量流传输的全部数据或部分数据，或者，
    所述第一数据包括通过第二服务质量流传输的全部数据或部分数据；
    所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
  12. 根据权利要求8-11项中任一项所述的方法，其特征在于，所述第一会话的标识以及所述第一终端设备的第一标识是所述中继设备从所述第一终端设备获取的。
  13. 根据权利要求8-12项中任一项所述的方法，其特征在于，所述第一请求消息还包括第三指示，所述第三指示信息用于指示所述第一通信路径为锚点路径，或者，所述第三指示信息用于指示所述第二通信路径为锚点路径，
    所述第一通信路径和所述第二通信路径通过服务于所述锚点路径的用户面功能实体与应用服务器通信。
  14. 一种数据传输的方法，其特征在于，该方法应用于包括第一终端设备的第一通信路径和第二通信路径的系统中，所述第一通信路径是所述第一终端设备与网络连接的直连路径，所述第二通信路径是所述第一终端设备通过中继设备与网络连接的非直连路径，所述方法包括：
    第一移动性管理实体从所述第一终端设备接收第一请求消息，所述第一请求消息用于请求通过所述第一通信路径的第一会话和所述第二通信路径的第二会话共同传输第一数据，所述第一请求消息包括第一信息，所述第一信息包括所述第一会话的标识、所述第二会话的标识以及所述中继设备的第一标识；
    在接收所述第一请求消息之后，第一用户面功能实体和第二用户面功能实体传输所述第一数据，所述第一用户面功能实体服务于所述第一通信路径，所述第二用户面功能实体服务于所述第二通信路径；
    其中，所述第一用户面功能实体和所述第二用户面功能实体中的一个与应用服务器之间传输所述第一数据。
  15. 根据权利要求14所述的方法，其特征在于，所述第一信息还包括第一服务质量流的标识和/或第二服务质量流的标识，所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
  16. 根据权利要求14或15所述的方法，其特征在于，
    所述第一请求消息还包括第一指示，所述第一指示用于指示通过所述第一会话和所述 第二会话共同传输所述第一数据；或者
    所述第一请求消息还包括所述第一指示和第二指示，所述第二指示用于描述所述第一数据。
  17. 根据权利要求14-16项中任一项所述的方法，其特征在于，
    所述第一数据包括通过第一服务质量流传输的全部数据或部分数据，或者，
    所述第一数据包括通过第二服务质量流传输的全部数据或部分数据；
    所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
  18. 根据权利要求14-17项中任一项所述的方法，其特征在于，所述第一请求消息还包括第三指示，所述第三指示用于指示所述第一通信路径为锚点路径，或者，所述第三指示用于指示所述第二通信路径为锚点路径，
    所述第一通信路径和所述第二通信路径通过服务于所述锚点路径的用户面功能实体与应用服务器通信。
  19. 根据权利要求14-18项中任一项所述的方法，其特征在于，所述第一请求消息还包括所述第一终端设备的标识，所述第一终端设备的标识对应所述第二通信路径。
  20. 根据权利要求14-19项中所述的方法，其特征在于，
    所述第一移动性管理实体根据所述中继设备的第一标识确定第二移动性管理实体，或者，
    所述第一移动性管理实体根据所述中继设备的第一标识和所述第二会话的标识确定第二会话管理功能实体；
    所述第二移动性管理实体服务于所述中继设备；所述第二会话管理功能实体服务于所述第二会话。
  21. 根据权利要求20所述的方法，其特征在于，所述第一用户面功能实体和所述第二用户面功能实体传输所述第一数据，包括：
    通过第一会话管理功能实体和所述第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道；
    所述第一用户面功能实体和所述第二用户面功能实体通过所述第一通道传输所述第一数据。
  22. 根据权利要求21所述的方法，其特征在于，所述通过第一会话管理功能实体和所述第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道，包括：
    所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息并将所述第一通道信息通过所述第二会话管理功能实体发送至所述第二用户面功能实体，所述第一通道信息用于所述第二用户面功能实体通过所述第一通道向所述第一用户面功能实体发送数据；
    所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息并将所述第二通道信息通过所述第一会话管理功能实体发送至所述第一用户面功能实体，所述第二通道信息用于所述第一用户面功能实体通过所述第一通道向所述第二用户面功能实体发送数据。
  23. 根据权利要求21或22所述的方法，其特征在于，所述通过第一会话管理功能实体和第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道，包括：
    所述第一移动性管理实体根据所述中继设备的第一标识确定所述第二移动性管理实体；
    所述第一移动性管理实体从所述第二移动性管理实体获取所述第二会话管理功能实体的地址；
    所述第一移动性管理实体向所述第一会话管理功能实体发送所述第二会话管理功能实体的地址；
    所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息；
    所述第一会话管理功能实体根据所述第二会话管理功能实体的地址，向所述第二会话管理功能实体发送所述第一通道信息；
    所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息；
    所述第二会话管理功能实体向所述第一会话管理功能实体发送所述第二通道信息。
  24. 根据权利要求21或22所述的方法，其特征在于，所述通过第一会话管理功能实体和第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道，包括：
    所述第一移动性管理实体根据所述中继设备的第一标识确定所述第二移动性管理实体；
    所述第一移动性管理实体通过所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息；
    所述第二移动性管理实体通过所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息；
    所述第一移动性管理实体通过所述第一会话管理功能实体向所述第一用户面功能实体发送所述第二通道信息；
    所述第二移动性管理实体通过所述第二会话管理功能实体向所述第二用户面功能实体发送所述第一通道信息。
  25. 根据权利要求14-24项中任一项所述的方法，其特征在于，
    所述第一用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第一规则，所述第一规则用于指示所述第一用户面功能实体向所述第二用户面功能实体发送所述第一数据的部分或全部，使得所述第二用户面功能实体通过所述第二通信路径向所述第一终端设备发送从所述第一用户面功能实体接收的数据；
    或者，所述第一用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第二规则，所述第二规则用于指示所述第一用户面功能实体将从所述第二用户面功能实体接收的数据发送至所述应用服务器；
    或者，所述第一用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第三规则，所述第三规则用于指示所述第二用户面功能实体向所述第一用户面功能实体发送从所述第一终端设备接收的所述第一数据；
    或者，所述第一用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体 向所述第二用户面功能实体发送第四规则，所述第四规则用于指示所述第二用户面功能实体向所述第一终端设备发送从所述第一用户面功能实体接收的数据。
  26. 根据权利要求14-24项中任一项所述的方法，其特征在于，
    所述第二用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第一规则，所述第一规则用于指示所述第一用户面功能实体向所述第二用户面功能实体发送从所述第一终端设备接收的所述第一数据；或者
    所述第二用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第二规则，所述第二规则用于指示所述第一用户面功能实体向所述第一终端设备发送从所述第二用户面功能实体接收的数据；或者
    所述第二用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第三规则，所述第三规则用于指示所述第二用户面功能实体向所述第一用户面功能实体发送所述第一数据的部分或全部，使得所述第一用户面功能实体通过所述第一通信路径向所述第一终端设备发送从所述第二用户面功能实体接收的数据；或者
    所述第二用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第四规则，所述第四规则用于指示所述第二用户面功能实体将从所述第一用户面功能实体接收的数据发送至所述应用服务器。
  27. 根据权利要求25或26所述的方法，其特征在于，还包括：
    所述第一会话管理功能实体从所述第一移动性管理实体接收所述第一信息，所述第一会话管理功能实体根据所述第一信息生成所述第一规则和所述第二规则；
    所述第二会话管理功能实体从所述第一会话管理功能实体或所述第二移动性管理实体接收第二信息，所述第二会话管理功能实体根据所述第二信息生成所述第三规则和所述第四规则，所述第二信息包括：第一指示、所述第二会话的标识以及所述中继设备的第二标识，所述中继设备的第二标识是由所述第一移动性管理实体根据所述中继设备的第一标识确定的。
  28. 根据权利要求27所述的方法，其特征在于，所述第二信息还包括以下至少一项：
    所述第二服务质量流的标识；
    所述第二指示；
    所述第一终端设备的标识；或
    所述第三指示。
  29. 一种数据传输的方法，其特征在于，该方法应用于包括第一终端设备的第一通信路径和第二通信路径的系统中，所述第一通信路径是所述第一终端设备与网络连接的直连路径，所述第二通信路径是所述第一终端设备通过中继设备与网络连接的非直连路径，所述方法包括：
    第二移动性管理功能实体从所述中继设备接收第二请求消息，所述第二请求消息用于请求通过所述第一通信路径的第一会话和所述第二通信路径的第二会话共同传输第一数据，所述第二请求消息包括第三信息，所述第三信息包括所述第一会话的标识、所述第二会话的标识以及所述第一终端设备的第一标识；
    在接收所述第二请求消息之后，第一用户面功能实体和第二用户面功能实体传输所述 第一数据，所述第一用户面功能实体服务于所述第一通信路径，所述第二用户面功能实体服务于所述第二通信路径，
    其中，所述第一用户面功能实体和所述第二用户面功能实体中的一个与应用服务器之间传输所述第一数据。
  30. 根据权利要求29所述的方法，其特征在于，所述第三信息还包括第二服务质量流的标识和/或第一服务质量流的标识，所述第二服务质量流为所述第二会话对应的服务质量流，所述第一服务质量流为所述第一会话对应的服务质量流。
  31. 根据权利要求29或30所述的方法，其特征在于，
    所述第二请求消息还包括第一指示，所述第一指示用于指示通过所述第一会话和所述第二会话共同传输所述第一数据；或者
    所述第二请求消息还包括所述第一指示和第二指示，所述第二指示用于描述所述第一数据。
  32. 根据权利要求29-31项中任一项所述的方法，其特征在于，
    所述第一数据包括通过第一服务质量流传输的全部数据或部分数据，或者，
    所述第一数据包括通过第二服务质量流传输的全部数据或部分数据；
    所述第一服务质量流为所述第一会话对应的服务质量流，所述第二服务质量流为所述第二会话对应的服务质量流。
  33. 根据权利要求29-32项中任一项所述的方法，其特征在于，所述第二请求消息还包括第三指示，所述第三指示用于指示所述第一通信路径为锚点路径，或者，所述第三指示用于指示所述第二通信路径为锚点路径，
    所述第一通信路径和所述第二通信路径通过服务于所述锚点路径的用户面功能实体与应用服务器通信。
  34. 根据权利要求29-33项中任一项所述的方法，其特征在于，
    所述第二移动性管理实体根据所述第一终端设备的第一标识确定第一移动性管理实体，或者，
    所述第二移动性管理实体根据所述第一终端设备的第一标识和所述第一会话的标识确定第一会话管理功能实体；
    所述第一移动性管理实体服务于所述第一终端设备，所述第一会话管理功能实体服务所述第一会话。
  35. 根据权利要求34所述的方法，其特征在于，所述第一用户面功能实体和所述第二用户面功能实体传输所述第一数据，包括：
    通过第一会话管理功能实体和所述第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道；
    所述第一用户面功能实体和所述第二用户面功能实体通过所述第一通道传输所述第一数据。
  36. 根据权利要求35所述的方法，其特征在于，所述通过第一会话管理功能实体和所述第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道，包括：
    所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息并将所述 第一通道信息通过所述第二会话管理功能实体发送至所述第二用户面功能实体，所述第一通道信息用于所述第二用户面功能实体通过所述第一通道向所述第一用户面功能实体发送数据；
    所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息并将所述第二通道信息通过所述第一会话管理功能实体发送至所述第一用户面功能实体，所述第一通道信息用于所述第一用户面功能实体通过所述第一通道向所述第二用户面功能实体发送数据。
  37. 根据权利要求35或36所述的方法，其特征在于，所述通过第一会话管理功能实体和第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道，包括：
    所述第二移动性管理实体根据所述第一终端设备的第一标识确定所述第一移动性管理实体；
    所述第二移动性管理实体从所述第一移动性管理实体获取所述第一会话管理功能实体的地址；
    所述第二移动性管理实体向所述第二会话管理功能实体发送所述第一会话管理功能实体的地址；
    所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息；
    所述第二会话管理功能实体根据所述第一会话管理功能实体的地址，向所述第一会话管理功能实体发送所述第二通道信息；
    所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息；
    所述第一会话管理功能实体向所述第二会话管理功能实体发送所述第一通道信息。
  38. 根据权利要求35或36所述的方法，其特征在于，所述通过第一会话管理功能实体和第二会话管理功能实体建立所述第一用户面功能实体和所述第二用户面功能实体之间的第一通道，包括：
    所述第二移动性管理实体根据所述第一终端设备的第一标识确定所述第一移动性管理实体；
    所述第二移动性管理实体通过所述第二会话管理功能实体从所述第二用户面功能实体获取第二通道信息；
    所述第一移动性管理实体通过所述第一会话管理功能实体从所述第一用户面功能实体获取第一通道信息；
    所述第二移动性管理实体通过所述第二会话管理功能实体向所述第二用户面功能实体发送所述第一通道信息；
    所述第一移动性管理实体通过所述第一会话管理功能实体向所述第一用户面功能实体发送所述第二通道信息。
  39. 根据权利要求29-38项中任一项所述的方法，其特征在于，
    所述第一用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第一规则，所述第一规则用于指示所述第一用户面功能实体向所述第二用户面功能实体发送所述第一数据的部分或全部，使得所述第二用户面功能实体通过所述第二通信路径向所述第一终端设备发送从所述第一用户面功能实体接收的数据；
    或者，所述第一用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第二规则，所述第二规则用于指示所述第一用户面功能实体将从所述第二用户面功能实体接收的数据发送至所述应用服务器；
    或者，所述第一用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第三规则，所述第三规则用于指示所述第二用户面功能实体向所述第一用户面功能实体发送从所述第一终端设备接收的所述第一数据；
    或者，所述第一用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第四规则，所述第四规则用于指示所述第二用户面功能实体向所述第一终端设备发送从所述第一用户面功能实体接收的数据。
  40. 根据权利要求29-38项中任一项所述的方法，其特征在于，
    所述第二用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第一规则，所述第一规则用于指示所述第一用户面功能实体向所述第二用户面功能实体发送从所述第一终端设备接收的所述第一数据；或者
    所述第二用户面功能实体为锚点用户面功能实体，所述第一会话管理功能实体向所述第一用户面功能实体发送第二规则，所述第二规则用于指示所述第一用户面功能实体向所述第一终端设备发送从所述第二用户面功能实体接收的数据；或者
    所述第二用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第三规则，所述第三规则用于指示所述第二用户面功能实体向所述第一用户面功能实体发送所述第一数据的部分或全部，使得所述第一用户面功能实体通过所述第一通信路径向所述第一终端设备发送从所述第二用户面功能实体接收的数据；或者
    所述第二用户面功能实体为锚点用户面功能实体，所述第二会话管理功能实体向所述第二用户面功能实体发送第四规则，所述第四规则用于指示所述第二用户面功能实体将从所述第一用户面功能实体接收的数据发送至所述应用服务器。
  41. 根据权利要求39或40所述的方法，其特征在于，
    所述第二会话管理功能实体从所述第二移动性管理实体接收所述第三信息，所述第二会话管理功能实体根据所述第三信息生成所述第一规则和所述第二规则；
    所述第一会话管理功能实体从所述第二会话管理功能实体或所述第一移动性管理实体接收第四信息，所述第一会话管理功能实体根据所述第四信息生成所述第三规则和所述第四规则，所述第四信息包括：第一指示、所述第一会话的标识以及所述第一终端设备的第二标识，所述第一终端设备的第二标识是由所述第二移动性管理实体根据所述第一终端设备的第一标识确定的。
  42. 根据权利要求41所述的方法，其特征在于，所述第四信息还包括以下至少一项：
    所述第一服务质量流的标识；
    所述第二指示；
    所述中继设备的标识；或
    所述第三指示。
  43. 一种数据传输的装置，其特征在于，包括：用于执行权利要求1至13中任一项所述的方法的单元，或14至42中任一项所述的方法的单元。
  44. 一种数据传输的装置，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求1至13，或14至42中任一项所述的方法。
  45. 根据权利要求44所述的装置，其特征在于，所述装置还包括所述存储器。
  46. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至13，或14至42中任意一项所述的方法。
  47. 一种计算机程序产品，其特征在于，所述计算机程序产品包括用于执行如权利要求1至13，或14至42中任一项所述的方法的指令。
PCT/CN2022/109557 2021-12-06 2022-08-01 一种数据传输的方法和通信装置 WO2023103417A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202111476011.3 2021-12-06
CN202111476011 2021-12-06
CN202210180880.X 2022-02-25
CN202210180880.XA CN116233957A (zh) 2021-12-06 2022-02-25 一种数据传输的方法和通信装置

Publications (1)

Publication Number Publication Date
WO2023103417A1 true WO2023103417A1 (zh) 2023-06-15

Family

ID=86570264

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/109557 WO2023103417A1 (zh) 2021-12-06 2022-08-01 一种数据传输的方法和通信装置

Country Status (2)

Country Link
CN (1) CN116233957A (zh)
WO (1) WO2023103417A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109328483A (zh) * 2016-07-04 2019-02-12 华为技术有限公司 一种无线链路失败处理方法、相关设备及通信系统
CN109417695A (zh) * 2017-01-10 2019-03-01 华为技术有限公司 一种通信路径转换方法及设备
CN112313991A (zh) * 2018-06-26 2021-02-02 诺基亚技术有限公司 用于通信系统中的增强型数据分组流处理的方法和装置
WO2021032605A1 (en) * 2019-08-20 2021-02-25 Telefonaktiebolaget Lm Ericsson (Publ) Maintaining sidelink (sl) operation under radio link failure (rlf) using ue-to-ue relay
CN113079547A (zh) * 2020-01-03 2021-07-06 大唐移动通信设备有限公司 一种提供中继业务的方法、设备、装置及可读存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109328483A (zh) * 2016-07-04 2019-02-12 华为技术有限公司 一种无线链路失败处理方法、相关设备及通信系统
CN109417695A (zh) * 2017-01-10 2019-03-01 华为技术有限公司 一种通信路径转换方法及设备
CN112313991A (zh) * 2018-06-26 2021-02-02 诺基亚技术有限公司 用于通信系统中的增强型数据分组流处理的方法和装置
WO2021032605A1 (en) * 2019-08-20 2021-02-25 Telefonaktiebolaget Lm Ericsson (Publ) Maintaining sidelink (sl) operation under radio link failure (rlf) using ue-to-ue relay
CN113079547A (zh) * 2020-01-03 2021-07-06 大唐移动通信设备有限公司 一种提供中继业务的方法、设备、装置及可读存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CATT, OPPO: "New WID on Study on System enhancement for Proximity based Services in 5GS - Phase 2", 3GPP DRAFT; S2-2108162, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Electronic meeting; 20211018 - 20211022, 26 October 2021 (2021-10-26), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052070930 *

Also Published As

Publication number Publication date
CN116233957A (zh) 2023-06-06

Similar Documents

Publication Publication Date Title
US10911984B2 (en) Apparatus, system and method of providing offloadability information to a user-equipment (UE)
WO2021164564A1 (zh) 传输组播业务的方法和装置
US20230067851A1 (en) Communication method and apparatus
WO2022048394A1 (zh) 网络连接方法、网络去连接方法及通信装置
US20230164640A1 (en) Communication method and communication apparatus
US20230199550A1 (en) Relay Management Method and Communication Apparatus
US20240172084A1 (en) Data transmission method and apparatus
WO2022052851A1 (zh) 一种服务质量QoS的监测方法
US20230189054A1 (en) Relay communication method, and communication apparatus
WO2021174377A1 (zh) 切换方法和通信装置
WO2020199034A1 (zh) 用于中继通信的方法和装置
WO2023103417A1 (zh) 一种数据传输的方法和通信装置
US11985652B2 (en) P-BSR enhancements for IAB networks to improve E2E latency
WO2023088165A1 (zh) 一种数据传输的方法和装置
WO2022170798A1 (zh) 确定策略的方法和通信装置
WO2024067194A1 (zh) 通信方法、通信装置、以及通信系统
WO2023134516A1 (zh) 一种广播通信方法和装置
WO2023150944A1 (zh) 切换方法、终端设备和网络设备
WO2023197737A1 (zh) 报文发送方法、pin管理方法、通信装置及通信系统
WO2022141025A1 (zh) 用于传输数据的方法与装置
WO2023179331A1 (zh) 一种发送数据包的方法、通信装置及通信系统
WO2023124932A1 (zh) 建立连接的方法和通信装置
WO2023185657A1 (zh) 通信方法和通信装置
WO2024001897A1 (zh) 通信方法和装置
WO2022205453A1 (zh) 网络选择的方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22902851

Country of ref document: EP

Kind code of ref document: A1