WO2021219044A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2021219044A1
WO2021219044A1 PCT/CN2021/090782 CN2021090782W WO2021219044A1 WO 2021219044 A1 WO2021219044 A1 WO 2021219044A1 CN 2021090782 W CN2021090782 W CN 2021090782W WO 2021219044 A1 WO2021219044 A1 WO 2021219044A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
request
network element
creation
forwarding rule
Prior art date
Application number
PCT/CN2021/090782
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 WO2021219044A1 publication Critical patent/WO2021219044A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and device.
  • data forwarding between terminal equipment can be locally forwarded through user plane network elements, and between UE1 and UE2
  • UE1 sends a data message carrying the media access control address (MAC) of UE2 to the user plane network element.
  • the user plane network element After receiving the data message, the user plane network element recognizes The destination address of the data message, the data message is sent to UE2 through the UE2 session.
  • MAC media access control address
  • the Ethernet control automation technology (EtherCAT) system is an Ethernet-based communication system.
  • the EtherCAT network includes a master device and multiple slave devices, and the network interfaces of the master device and the slave device have sending and receiving functions.
  • the master device and the slave device implement different physical topologies through wired connections.
  • the transmission path of the data message in the EtherCAT network is a circular loop that passes through the master device and each slave device.
  • the EtherCAT device when the EtherCAT device is connected through the 5G system, the data message must be transmitted by EtherCAT The mechanism, that is, the same data message needs to pass through each EtherCAT device in turn, that is, the data message needs to be transmitted through the 5G system multiple times; and the data message does not reach the user plane network element in the 5G system multiple times. Change the message characteristics.
  • the data message cannot be forwarded according to the characteristics of the data message text itself after entering the user plane network element in the 5G system
  • the device in the EtherCAT network of the message causes the communication system that combines the EtherCAT network and the 5G system to form a loop loop for data message transmission between the master device and multiple slave devices, and the user plane network element cannot pass the data message through the session Transmit to each slave device in the EtherCAT network.
  • the present application provides a communication method and device, which are used to implement the user plane network element to transmit data messages to each slave device in the EtherCAT network through a session.
  • an embodiment of the present application provides a communication method.
  • the method includes: a user plane network element may receive a first uplink data packet through a first session, and the first session is a session of a first terminal device; The plane network element forwards the first uplink data packet through the second session according to the first forwarding rule instructing to forward the uplink data packet from the first session through the second session, where the second session is a session of the second terminal device, That is, the user plane network element may send the first uplink data packet to the second terminal device through the second session.
  • the user plane network element when the user plane network element forwards the uplink data message from the first terminal device (that is, the first uplink data message), it can be based on the difference between the session of the first terminal device and the session of the second terminal device.
  • the association relationship is to forward the first uplink data message through the session associated with the session of the first terminal device, so that when the first terminal device is associated with the slave device or the master device in the EtherCAT network, the user plane network element can pass through the first terminal device.
  • the session of the terminal device receives the first uplink data message from the slave device or master device associated with the first terminal device; when the second terminal device is associated with the slave device or master device in the EtherCAT network, the user plane network element
  • the first uplink data message may be sent to the slave device or the master device associated with the second terminal device through the session of the second terminal device.
  • the user plane network element may also receive the second uplink data packet through the second session; after that, the user plane network element forwards the second uplink data packet through the first session according to the second forwarding rule, Wherein, the second forwarding rule instructs to forward the uplink data packet from the second session through the first session.
  • the user plane network element when the user plane network element forwards the uplink data packet from the second terminal device (that is, the second uplink data packet), it can be based on the difference between the session of the first terminal device and the session of the second terminal device.
  • the association relationship is to forward the second uplink data message through the session associated with the session of the second terminal device, so that when the second terminal device is associated with the slave device or the master device in the EtherCAT network, the user plane network element can pass through the second terminal device.
  • the session of the terminal device receives the second uplink data message from the slave device or master device associated with the second terminal device; when the first terminal device is associated with the slave device or master device in the EtherCAT network, the user plane network element
  • the second uplink data message may be sent to the slave device or the master device associated with the second terminal device through the session of the first terminal device.
  • the user plane network element may also pre-configure the first forwarding rule. For example, the user plane network element may receive the first forwarding rule from the session management network element.
  • the first forwarding rule is pre-configured in the user plane network element, which can ensure that the first uplink data message can be forwarded through the second session.
  • the user plane network element may also pre-configure the second forwarding rule. For example, the user plane network element may receive the second forwarding rule from the session management network element.
  • the second forwarding rule is pre-configured in the user plane network element, which can ensure that the second uplink data packet can be forwarded through the second session.
  • the first forwarding rule is a forwarding rule of the first session, and the first forwarding rule includes some or all of the following:
  • the first forwarding rule can flexibly indicate to forward the uplink data message from the first session through the second session by carrying the identifier of the second session, the session association identifier, etc., which is suitable for a variety of different application scenarios.
  • the second forwarding rule is the forwarding rule of the second session, and the second forwarding rule includes some or all of the following:
  • the second forwarding rule can flexibly indicate the forwarding of the uplink data message from the second session through the first session by carrying the identifier of the first session, the session association identifier, etc., which is suitable for a variety of different application scenarios.
  • an embodiment of the present application provides a communication method, which is applied to a first terminal device.
  • the method includes: first.
  • the first terminal device may send a first session creation (or modification) request to the session management network element, the first session creation (or modification) request is used to request the creation (or modification) of the first session, and the first session creation (or modification)
  • the request is also used to indicate that the uplink of the first session is associated with the second session or the first session is associated with the second session; afterwards, after the first terminal device receives the first session creation (or modification) response from the session management network element, it may The first uplink data packet is sent through the first session, and the first session creation (or modification) response indicates that the first session creation (or modification) is successful.
  • the first terminal device when the first terminal device initiates the session creation or modification process, it can indicate that the upstream of the first session is associated with the second session, so that the session management network element can configure the first forwarding rule on the user plane network element.
  • the first session creation (or modification) request includes the identifier of the second session or the session association identifier, and the session association identifier indicates that the first session is associated with the second session.
  • the first session creation (or modification) request may also carry upstream indication information, such as session flow direction information.
  • the first session creation (or modification) request can flexibly indicate that the uplink of the first session is associated with the second session by carrying the identifier of the first session and the session association identifier, which is suitable for a variety of different application scenarios. .
  • an embodiment of the present application provides a communication method, which is applied to a second terminal device, and the method includes: first, the second terminal device sends a second session creation (or modification) request to the session management network element, and first 2.
  • the session creation (or modification) request is used to request the creation (or modification) of the second session and to indicate that the downstream flow of the second session is associated with the first session;
  • the second terminal device After receiving the second session creation (or modification) response from the session management network element, the second terminal device receives the first uplink data packet through the second session, and the second session creation (or modification) response indicates the second session creation ( Or modify) success.
  • the second terminal device when the second terminal device initiates the session creation or modification process, it can instruct the first session to associate with the downstream of the second session, so that the session management network element can configure the first forwarding rule on the user plane network element.
  • the second session creation (or modification) request includes an identifier of the first session or a session association identifier, and the session association identifier indicates that the first session is associated with the second session.
  • the second session creation (or modification) request can flexibly indicate the downstream association between the first session and the second session (that is, the upstream flow of the first session) by carrying the identifier of the first session and the session association identifier.
  • the second session Associated with the second session, applicable to a variety of different application scenarios.
  • the embodiments of the present application provide a communication method, which is applied to a second terminal device.
  • the method includes: first, the second terminal device sends a third session creation (or modification) request to the session management network element, and third The session creation (or modification) request is used to request the creation (or modification) of the second session, and the third session creation (or modification) request is also used to indicate that the upstream flow of the second session is associated with the first session or the first session is associated with the second session. Session association; afterwards, after receiving the third session creation (or modification) response from the session management network element, the second terminal device sends a second uplink data packet through the second session, and the third session creation (or modification) response indicates the first Second, the session is successfully created (or modified).
  • the second terminal device when the second terminal device initiates the session creation or modification process, it can instruct the upstream association of the first session with the second session, which is convenient for the session management network element to configure the second forwarding rule on the user plane network element.
  • the third session creation (or modification) request includes an identifier of the first session or a session association identifier, and the session association identifier indicates that the first session is associated with the second session.
  • the third session creation (or modification) request may also carry upstream indication information, such as session flow direction information.
  • the third session creation (or modification) request can flexibly indicate that the uplink of the second session is associated with the first session by carrying the identifier of the first session and the session association identifier, which is suitable for a variety of different applications. Scenes.
  • an embodiment of the present application provides a communication method, the method includes: a session management network element may receive a first request, the first request is used to indicate that the upstream of the first session is associated with the second session; the first request It may be sent by the first terminal device, the second terminal device, or the application function network element. After that, the session management network element configures a first forwarding rule in the user plane network element, and the first forwarding rule instructs to forward the uplink data message from the first session through the second session.
  • the session management network element can configure the first forwarding rule in time after learning the association relationship between the upstream of the first session and the second session, so as to facilitate the subsequent forwarding of the upstream data packets from the first session through the second session.
  • the session management network element receives the first request, including the following situations:
  • Case 1 The session management network element receives the first session creation (or modification) request from the first terminal device.
  • the first session creation (or modification) request is used to request the creation of the first session and to indicate the upstream and the second session of the first session. Session association.
  • Case 2 The session management network element receives the first session creation (or modification) request from the first terminal device, and the second session creation (or modification) request is used to request the creation of the first session and indicate that the first session is associated with the second session.
  • Case 3 The session management network element receives a second session creation (or modification) request from the second terminal device, and the third session creation request is used to request the creation of the second session and indicate the downstream association between the first session and the second session.
  • Case 4 The session management network element receives the first configuration request from the application function network element, the first configuration request is used to configure the first session, and the first configuration request is also used to indicate that the upstream of the first session is associated with the second session or the first One session is associated with the second session.
  • the first request can come from a terminal device or other network elements, that is, different devices can inform the session management network element through different messages that the upstream flow of the first session (upstream) is associated with the second session, which is suitable for Different scenarios expand the scope of application.
  • the session management network element may also receive a second request, which is used to request the creation of the second session and to indicate that the upstream flow of the second session is associated with the first session; after that, the session management network element A second forwarding rule is configured in the user plane network element, and the second forwarding rule instructs to forward the uplink data packet from the second session through the first session.
  • the session management network element can configure the second forwarding rule in time after learning the association relationship between the upstream of the second session and the first session, so as to facilitate the subsequent forwarding of uplink data packets from the second session through the first session.
  • the session management network element receives the second request, including the following situations:
  • Case 1 The session management network element receives a third session creation (or modification) request from the second terminal device, and the third session creation (or modification) request is used to request the creation (or modification) of the second session and to indicate the uplink of the second session
  • the flow is associated with the first session.
  • Case 2 The session management network element receives a third session creation (or modification) request from the second terminal device, and the third session creation (or modification) request is used to request the creation (or modification) of the second session and to indicate that the second session and the first session One session association.
  • Case 3 The session management network element receives a second configuration request from the application function network element, the second configuration request is used to configure the second session, and the second configuration request is also used to indicate that the upstream of the second session is associated with the first session or the second One session is associated with the second session.
  • the second request can come from a terminal device or other network elements, that is, different devices can inform the session management network element through different messages that the upstream flow of the second session (upstream) is associated with the first session, which is suitable for Different scenarios expand the scope of application.
  • the first session creation (or modification) request and the first configuration request include some or all of the following: the identifier of the second session or the session association identifier, and the session association identifier indicates that the first session is connected to the second session. Session association.
  • the first session creation (or modification) request may also include upstream indication information.
  • the first configuration request indicates that the uplink of the first session is associated with the second session, it may also carry indication information of the uplink.
  • the second session creation (or modification) request includes some or all of the following: the identifier of the first session or the session association identifier.
  • the first session creation (or modification) request may also include upstream indication information.
  • the third session creation (or modification) request may also include downstream indication information.
  • the first request can flexibly indicate that the second session is associated with the first session by carrying the session identifier, the session association identifier, etc., which is suitable for a variety of different application scenarios.
  • the third session creation (or modification) request and the second configuration request include some or all of the following: the identifier of the first session or the session association identifier, and the session association identifier indicates the first session and the second session. Session association.
  • the third session creation (or modification) request may also include upstream indication information.
  • the second configuration request indicates that the uplink of the second session is associated with the first session, it may also carry indication information of the uplink.
  • the second request can flexibly indicate that the second session is associated with the first session by carrying the session identifier, the session association identifier, etc., which is suitable for a variety of different application scenarios.
  • the first forwarding rule is the forwarding rule of the first session, and the first forwarding rule includes some or all of the following: the identifier of the second session, the session association identifier, or the GTP-U identifier of the second session , Where the session association identifier indicates that the first session is associated with the second session.
  • the first forwarding rule can flexibly indicate to forward the uplink data message from the first session through the second session by carrying the identifier of the second session, the session association identifier, etc., which is suitable for a variety of different application scenarios.
  • the second forwarding rule is the forwarding rule of the second session, and the second forwarding rule includes some or all of the following:
  • the second forwarding rule can flexibly indicate the forwarding of the uplink data message from the second session through the first session by carrying the identifier of the first session, the session association identifier, etc., which is suitable for a variety of different application scenarios.
  • an embodiment of the present application provides a communication method, which is applied to an application function network element, and the method includes: first.
  • the application function network element sends a first configuration request to the session management network element, the first configuration request is used to configure the first session, and the first configuration request is also used to indicate that the uplink of the first session is associated with the second session or the first session is associated with the second session.
  • the second session is associated.
  • the first configuration request includes some or all of the following: the identifier of the second session or the session association identifier, the session association identifier indicates that the first session is associated with the second session, and the first configuration request indicates that the upstream of the first session is associated with the second session.
  • the session can also carry upstream indication information.
  • the application function network element when configuring the first session, can indicate that the first session is associated with the second session, so that the session management network element can configure the first forwarding rule on the user plane network element.
  • the application function network element sends a second configuration request to the session management network element, the second configuration request is used to configure the second session, and the second configuration request is also used to indicate the upstream and first configuration of the second session.
  • a session is associated or the first session is associated with the second session.
  • the second configuration request includes some or all of the following: the identifier of the second session or the session association identifier, the session association identifier indicates that the first session is associated with the second session, and the first configuration request indicates that the upstream of the second session is associated with the first session.
  • the session can also carry upstream indication information.
  • the application function network element can indicate that the first session is associated with the second session when configuring the second session, so that the session management network element can configure the second forwarding rule on the user plane network element.
  • the embodiments of the present application also provide a communication system.
  • the communication system includes a session management network element and a user plane network element;
  • the session management network element is configured to receive a first request, the first request is used to indicate that the upstream of the first session is associated with the second session; and the first forwarding rule is sent to the user plane network element, and the first forwarding rule indicates that the second The session forwards the uplink data message from the first session.
  • the user plane network element is configured to receive the first forwarding rule; and receive the first uplink data packet through the first session; and forward the first uplink data packet through the second session according to the first forwarding rule.
  • the session management network element may also receive a second request, the second request is used to request the creation of the second session and to indicate that the uplink of the second session is associated with the first session; and send to the user plane network element A second forwarding rule, where the second forwarding rule instructs to forward the uplink data message from the second session through the first session;
  • the user plane network element may receive the second forwarding rule; and receive the second uplink data packet through the second session; and forward the second uplink data packet through the first session according to the second forwarding rule.
  • the first request is a first session creation (or modification) request;
  • the communication system further includes a first terminal device;
  • the first terminal device is configured to send a first session creation (or modification) request to the session management network element, the first session creation (or modification) request is used to request the creation (or modification) of the first session, and the first session creation (or modification) The modification) request is also used to indicate that the uplink of the first session is associated with the second session or the first session is associated with the second session.
  • the first request is a second session creation (or modification) request;
  • the communication system also includes a second terminal device;
  • the second terminal device may send a second session creation (or modification) request to the session management network element, and the third session creation (or modification) request is used to request the creation (or modification) of the second session and to indicate the downstream connection of the second session.
  • the first session is associated.
  • the first request is a first configuration request
  • the communication system further includes an application function network element
  • the application function network element may send a first configuration request to the session management network element, the first configuration request is used to configure the first session, and the first configuration request is also used to indicate that the uplink of the first session is associated with the second session or the first session Associated with the second conversation.
  • the second request is a third session creation (or modification) request;
  • the communication system includes a second terminal device;
  • the second terminal device may send a third session creation (or modification) request to the session management network element, the third session creation (or modification) request is used to request the creation (or modification) of the second session, and the third session creation (or modification) The request is also used to indicate that the uplink of the second session is associated with the first session or the first session is associated with the second session.
  • the second request is a second configuration request
  • the communication system further includes an application function network element
  • the application function network element may send a quick search second configuration request to the session management network element, the second configuration request is used to configure the second session, and the second configuration request is also used to indicate that the upstream of the second session is associated with the first session or the first session.
  • One session is associated with the second session.
  • the first session creation (or modification) request includes some or all of the following:
  • the identifier of the second session or the session association identifier, and the session association identifier indicates that the first session is associated with the second session.
  • the second session creation (or modification) request includes some or all of the following:
  • the identifier of the first session or the session association identifier is a registered trademark of the first session or the session association identifier.
  • the first configuration request includes some or all of the following:
  • the identifier of the second session or the session association identifier, and the session association identifier indicates that the first session is associated with the second session.
  • the third session creation (or modification) request includes some or all of the following:
  • the identifier of the first session or the session association identifier, and the session association identifier indicates that the first session is associated with the second session.
  • the second configuration request includes some or all of the following:
  • the identifier of the first session or the session association identifier, and the session association identifier indicates that the first session is associated with the second session.
  • the first forwarding rule is a forwarding rule of the first session, and the first forwarding rule includes some or all of the following:
  • the second forwarding rule is the forwarding rule of the second session, and the second forwarding rule includes some or all of the following:
  • an embodiment of the present application also provides a communication device, which is applied to a user plane network element, and the beneficial effects can be referred to the description of the first aspect and will not be repeated here.
  • the device has the function of realizing the behavior in the method example of the first aspect described above.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the device includes a receiving unit and a sending unit, and these units can perform the corresponding functions in the above-mentioned method example of the first aspect. For details, please refer to the detailed description in the method example, which will not be repeated here.
  • an embodiment of the present application also provides a communication device, the communication device is applied to a first terminal device, and the beneficial effects can be referred to the description of the second aspect and will not be repeated here.
  • the device has the function of realizing the behavior in the method example of the second aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the device includes a receiving unit and a sending unit, and these units can perform the corresponding functions in the method example of the second aspect. For details, refer to the detailed description in the method example, which is not repeated here.
  • an embodiment of the present application also provides a communication device, the communication device is applied to a second terminal device, and the beneficial effects can be referred to the description of the third aspect and will not be repeated here.
  • the device has the function of realizing the behavior in the method example of the third aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the device includes a receiving unit and a sending unit, and these units can perform corresponding functions in the method example of the third aspect. For details, please refer to the detailed description in the method example, which will not be repeated here.
  • an embodiment of the present application also provides a communication device, the communication device is applied to a second terminal device, and the beneficial effects can be referred to the description of the fourth aspect and will not be repeated here.
  • the device has the function of realizing the behavior in the method example of the fourth aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the device includes a receiving unit and a sending unit, and these units can perform the corresponding functions in the foregoing method example of the fourth aspect. For details, please refer to the detailed description in the method example, which will not be repeated here.
  • an embodiment of the present application also provides a communication device, which is applied to a session management network element, and the beneficial effects can be referred to the description of the fifth aspect and will not be repeated here.
  • the device has the function of realizing the behavior in the method example of the fifth aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the device includes a receiving unit and a processing unit, and these units can perform the corresponding functions in the method example of the fifth aspect. For details, please refer to the detailed description in the method example, which will not be repeated here.
  • an embodiment of the present application also provides a communication device, which is applied to an application function network element, and the beneficial effects can be referred to the description of the sixth aspect and will not be repeated here.
  • the device has the function of realizing the behavior in the method example of the sixth aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the device includes sending units, and these units can perform corresponding functions in the method examples of the sixth aspect described above. For details, please refer to the detailed description in the method examples, which will not be repeated here.
  • an embodiment of the present application also provides a communication device, which is applied to a user plane network element, and the beneficial effects can be referred to the description of the first aspect and will not be repeated here.
  • the structure of the communication device includes a processor and a memory, and the processor is configured to support the user plane network element to perform the corresponding function in the above-mentioned first aspect method.
  • the memory is coupled with the processor, and it stores program instructions and data necessary for the communication device.
  • the structure of the communication device also includes a communication interface for communicating with other devices.
  • the embodiments of the present application also provide a communication device, the communication device is applied to the first terminal device, and the beneficial effects can be referred to the description of the second aspect and will not be repeated here.
  • the structure of the communication device includes a processor and a memory, and the processor is configured to support the first terminal device to perform the corresponding function in the method of the second aspect described above.
  • the memory is coupled with the processor, and it stores program instructions and data necessary for the communication device.
  • the structure of the communication device also includes a transceiver for communicating with other devices.
  • an embodiment of the present application also provides a communication device, which is applied to a second terminal device, and the beneficial effects can be referred to the description of the third aspect, which will not be repeated here.
  • the structure of the communication device includes a processor and a memory, and the processor is configured to support the second terminal device to perform the corresponding function in the method of the third aspect described above.
  • the memory is coupled with the processor, and it stores program instructions and data necessary for the communication device.
  • the structure of the communication device also includes a transceiver for communicating with other devices.
  • an embodiment of the present application also provides a communication device, which is applied to a second terminal device, and the beneficial effects can be referred to the description of the fourth aspect and will not be repeated here.
  • the structure of the communication device includes a processor and a memory, and the processor is configured to support the second terminal device to perform the corresponding function in the above-mentioned fourth aspect method.
  • the memory is coupled with the processor, and it stores program instructions and data necessary for the communication device.
  • the structure of the communication device also includes a transceiver for communicating with other devices.
  • an embodiment of the present application also provides a communication device, which is applied to a session management network element, and the beneficial effects can be referred to the description of the fifth aspect and will not be repeated here.
  • the structure of the communication device includes a processor and a memory, and the processor is configured to support the base station to perform the corresponding functions in the above-mentioned fifth aspect method.
  • the memory is coupled with the processor, and it stores program instructions and data necessary for the communication device.
  • the structure of the communication device also includes a communication interface for communicating with other devices.
  • an embodiment of the present application also provides a communication device, which is applied to an application function network element, and the beneficial effects can be referred to the description of the sixth aspect and will not be repeated here.
  • the structure of the communication device includes a processor and a memory, and the processor is configured to support the base station to perform the corresponding function in the method of the sixth aspect described above.
  • the memory is coupled with the processor, and it stores program instructions and data necessary for the communication device.
  • the structure of the communication device also includes a communication interface for communicating with other devices.
  • this application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium, which when run on a computer, causes the computer to execute the methods described in the above aspects.
  • the present application also provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the methods described in the foregoing aspects.
  • the present application also provides a computer chip connected to a memory, and the chip is used to read and execute a software program stored in the memory, and execute the methods described in the foregoing aspects.
  • Figure 1 is a schematic diagram of the network architecture of the 5G system
  • FIG. 2 is a schematic diagram of the network topology of EtherCAT
  • FIG. 3 is a schematic diagram of the structure of an EtherCAT message
  • 4a to 4c are schematic diagrams of a network architecture provided by an embodiment of this application.
  • 5 to 12 are schematic diagrams of a communication method provided by embodiments of this application.
  • Figures 13 to 19 are schematic structural diagrams of a communication device provided by embodiments of this application.
  • the present application provides a communication method and device to implement the user plane network element to transmit data messages to each slave device in the EtherCAT network through a session.
  • the embodiment of the application relates to the combination of a 5G system and an EtherCAT network.
  • the 5G system, the EtherCAT network and the network architecture to which the embodiment of the application is applicable will be described below first.
  • the network architecture is a 5G network architecture.
  • the network elements in the 5G architecture include terminal equipment.
  • the terminal equipment is the UE as an example.
  • the network architecture also includes radio access network (RAN), access and mobility management function (access and mobility management function, AMF) network elements, session management function (session management function, SMF) network elements, user plane Function (user plane function, UPF) network element, policy control function (policy control function, PCF) network element, application function (AF) network element, data network (data network, DN), etc.
  • RAN radio access network
  • AMF access and mobility management function
  • SMF session management function
  • user plane Function user plane function
  • policy control function policy control function
  • PCF application function
  • AF application function
  • RAN The main function of RAN is to control users to access the mobile communication network through wireless.
  • RAN is a part of the mobile communication system. It implements a wireless access technology. Conceptually, it resides between a certain device (such as a mobile phone, a computer, or any remote control machine) and provides a connection to its core network.
  • the AMF network element is responsible for the terminal's access management and mobility management. In practical applications, it includes the mobility management function in the MME in the LTE network framework, and adds the access management function.
  • the SMF network element is responsible for session management, such as user session establishment.
  • the UPF network element is a functional network element of the user plane, which is mainly responsible for connecting to external networks. It includes the related functions of the LTE service gateway (serving gateway, SGW) and the public data network gateway (public data network GateWay, PDN-GW).
  • SGW serving gateway
  • PDN-GW public data network GateWay
  • the DN is responsible for the network that provides services for the terminal. For example, some DNs provide the terminal with Internet access, and some other DNs provide the terminal with short message functions, and so on.
  • PCF policy and charging rules function
  • the AF network element can be a third-party application control platform or the operator’s own equipment.
  • the AF network element can provide services for multiple application servers.
  • the AF network element is a functional network element that can provide various business services.
  • NEF network elements interact with the core network and can interact with the policy management framework for policy management.
  • the core network control plane function network elements also include network exposure function (NEF), unified data management (unified data management, UDM), and unified data repository (UDR) for network elements.
  • Network element, NEF network element is used to provide the framework, authentication and interface related to network capability opening, and transfer information between 5G system network functions and other network functions;
  • UDR network element is mainly used to store user-related contract data and policy data , Used for open structured data and application data;
  • UDM network elements can store the user's subscription information to achieve a backend similar to the HSS in 4G.
  • the terminal equipment in this application also known as user equipment (UE), is a device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; and can also be deployed on water. (Such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, satellites, etc.).
  • UE user equipment
  • Terminal devices can be mobile phones, tablets, computers with wireless transceiver functions, virtual reality (VR) terminals, augmented reality (AR) terminals, industrial control (industrial control)
  • EtherCAT is a real-time Ethernet technology developed and promoted by ETG (EtherCAT Technology Association) under the German Beckoff Company. It is an open network protocol that can communicate between master and slave devices. It uses cluster frames and network topology. Always constitute a logical ring, in each cycle, the master device (also known as the master station, or master node) to some or all of the slave devices (also known as slave stations or slave nodes) send data messages, from a slave The device transmits along the ring topology. When the data message sent by the master device passes through the slave device, the slave device only receives the data sent for it, and at the same time adds its own output data to the message.
  • EtherCAT For ease of understanding, take an example of a high-speed train.
  • the principle of EtherCAT is similar to a high-speed train.
  • the "train” (EtherCAT message) will not stop. We can see the whole train by staring at the train through the window on the platform. When our "acquaintances" are sitting by the window of the train, the people on the platform can greet acquaintances through the window (that is, each slave device can extract or insert data into the data frame sent by the master device, corresponding to each slave device. Part of the address of the device).
  • FIG. 2 it is a schematic diagram of an EtherCAT ring topology in the prior art.
  • the master device and the slave device are connected by wired transmission, and the slave devices are also connected by wired transmission.
  • An EtherCAT message includes a frame header (for example, Ethernet header), data (for example, Ethernet data), and a frame check sequence (for example, Frame Check Sequence, FCS).
  • a frame header for example, Ethernet header
  • data for example, Ethernet data
  • a frame check sequence for example, Frame Check Sequence, FCS
  • the frame header can also be called a standard Ethernet frame header, which mainly includes a source address, a destination address, and an Ethernet frame type.
  • the data mainly includes two parts: data header (for example, EtherCAT Header) and message (for example, EtherCAT Datagrams):
  • EtherCAT Header including: data length (Length) indication field, reserved bit (R), data type (Type) indication field; among them, the data length indication field is used to indicate the data length, and the data type indication field is used to indicate the data type .
  • EtherCAT Datagrams including multiple sub-messages, with a total length of 44-1486 bytes.
  • Each sub-message includes a 10-byte sub-message header (Datagram Header), 0-1486 bytes of data (Data), and a 2-byte working counter (WKC).
  • the sub-message header indicates the address segment of the slave device that needs to receive the sub-message.
  • FCS The frame check sequence
  • FCS also known as the end of the frame
  • FCS is a cyclic redundancy check code.
  • the FCS is calculated from the frame header and data part of the frame.
  • the destination device After the destination device receives it, it calculates the FCS again in the same way. If it is different from the received FCS, the frame is considered to be in the process of transmission. An error occurred, and the frame was chosen to be discarded.
  • FCS provides an error detection mechanism to verify the integrity of the frame during transmission.
  • the FCS in the Ethernet frame occupies a fixed length, generally 4 bytes.
  • the slave device When the slave device receives an EtherCAT message, it determines whether to process the sub-message according to the address segment in the word header of the sub-message in the EtherCAT message (this determination process can also be called addressing), Processing includes reading data in sub-messages or inserting data in sub-messages.
  • the slave device can be addressed in the following two ways:
  • Each slave device corresponds to a negative self-incremental address according to its position in the EtherCAT network.
  • Each sub-message (sub-message header of the sub-message) in the EtherCAT message sent by the master device includes the corresponding self-incremental address of a slave device.
  • the slave device processes The sub-message whose self-increment address is 0, and after adding 1 to the self-incrementing address in each sub-message in the EtherCAT message, it is transmitted to the next slave device.
  • Self-incremental addressing is usually used to scan hardware configuration information or determine the relative position between slave devices.
  • Each slave device has a fixed address (or logical address), which has nothing to do with the position of the slave device in the EtherCAT network.
  • the fixed address is generally allocated during the scanning hardware configuration process, and is suitable for use when a large amount of data is exchanged between the master device and the slave device.
  • the logical address is the address corresponding to the slave device in the virtual data space, and is used to perform read and write operations on the virtual data space.
  • Each sub-message (sub-message header of the sub-message) in the EtherCAT message sent by the master device includes a fixed address (or logical address) of a corresponding slave device.
  • the slave device processes the sub-message whose address is the fixed address of the slave device in the sub-message. After processing the sub-message, it will include the processed EtherCAT message of the sub-message. The file is transmitted to the next slave device.
  • FIG. 4a a schematic diagram of a network architecture applicable to this application, in which a 5G system and an EtherCAT network architecture are combined.
  • the master device (master) in the EtherCAT network in Figure 4a is deployed in the DN and is connected to the UPF network element in the 5G system, and the slave device (salve) in the EtherCAT network is connected to the UE in the 5G system.
  • the number of slave devices connected to the UE in the 5G system is not limited here, nor the number of UEs in the 5G system.
  • one or more slave devices in the EtherCAT network can access the 5G system through one UE in the 5G system, and other slave devices in the EtherCAT network can access the 5G system through another UE in the 5G system.
  • one or more slave devices in the EtherCAT network can be bound to a session of the UE in the 5G system, and then access the 5G system through the UE, that is, the one or more slave devices can pass through the session Send the data message to the 5G system, and other slave devices in the EtherCAT network can be bound to another session of the UE in the 5G system, and then access the 5G system through the UE. That is, the one or more slave devices can send data packets to the 5G system through the session.
  • the master device in the EtherCAT network can send data messages to each slave device connected to the UE of the 5G system through the 5G system.
  • SMF The network element is triggered by the UE or other network elements (AF network element), configures the forwarding rules of the session in the UPF network element, and establishes the association relationship between the session and the session.
  • AF network element network elements
  • the following takes the EtherCAT network including four slave devices, the master device is deployed in the DN, and the four slave devices are located on the UE side as an example to introduce two different types of applications applicable to the embodiments of this application.
  • Network architecture the EtherCAT network including four slave devices, the master device is deployed in the DN, and the four slave devices are located on the UE side as an example to introduce two different types of applications applicable to the embodiments of this application.
  • Figures 4b and 4c only show the connection between the UPF network element, the master device and the slave device, and the connection mode and deployment of other network elements. The location can be seen in Figure 4a.
  • slave device 1 is connected to two UEs respectively, UE1 and UE2, and slave device 4 is connected to UE3.
  • the data transmission path between the master device and the slave device 1, the slave device 2, the slave device 3, and the slave device 4 is marked with a black solid line with an arrow.
  • the data message sent by the master device passes through the UPF network element, and the UPF network element transmits the data message to the slave device 1 through the session of UE1.
  • the data message is returned to the slave device 1, the slave device 2, and the slave device 3 after being transmitted.
  • slave device 1 sends the data message to UE2
  • UE2 sends the data message to the UPF network element through the session of UE2
  • the UPF network element transmits the data message to UE3 through the session of UE3, and UE3 the data message
  • the data message is transmitted to the slave device 4, and then the slave device 4 returns the data message to UE3.
  • UE3 sends the data message to the UPF network element through the session of UE3, and the UPF network element transmits the data message to the UPF network element through the session of UE2. From device 1, slave device 1 returns the data message to UE1, and UE1 returns the data message to the master device through the session of UE1.
  • the slave device 1 is connected to two different UEs as an example.
  • the slave device 1 may also be bound to two different sessions of the same UE, and the transmission path is similar to the foregoing description.
  • slave device 1 is connected to UE1
  • slave device 4 is connected to UE3.
  • the data transmission path between the master device and the slave device 1, the slave device 2, the slave device 3, and the slave device 4 is marked with a black solid line with an arrow.
  • the data message sent by the master device passes through the UPF network element, and the UPF network element transmits the data message to the slave device 1 through the session of UE1.
  • the data message is returned to the slave device 1, the slave device 2, and the slave device 3 after being transmitted.
  • slave device 1 sends the data message to UE1
  • UE1 sends the data message to the UPF network element through the session of UE1
  • the UPF network element transmits the data message to UE3 through the session of UE3, and UE3 the data message
  • the data message is transmitted to the slave device 4, and the slave device 4 then returns the data message to the UE3.
  • the UE3 sends the data message to the UPF network element through the session of the UE3, and the UPF network element returns the data message to the master device.
  • the data message fed back from the device 4 does not need to be sent back to the slave device 1.
  • the transmission path is shorter, and the slave device 1 does not need to communicate with multiple devices. UE or multiple sessions are bound.
  • the communication method provided by the embodiment of the present application includes two parts, namely a forwarding rule configuration method and a data transmission method, which are respectively introduced below:
  • the session management network element can receive a first request from a terminal device or an application function network element.
  • the first request is used to indicate that the upstream of the first session is associated with the second session.
  • the first request may be
  • the newly added request information may also be an existing request message, such as a session creation request or a session modification request.
  • the first request comes from the terminal device and the application function network element as examples.
  • the first request comes from the first terminal device, and the first request is a first session creation request, and the first session creation request indicates that the upstream of the first session is associated with the second session.
  • a forwarding rule configuration method provided in an embodiment of the application is shown, and the method includes:
  • Step 501 The first terminal device sends a first session creation request to the session management network element, where the first session request is used to request the creation of the first session and to indicate that the uplink of the first session is associated with the second session.
  • the first terminal device may be pre-configured with the association relationship between the first session and the second session.
  • the first session creation request sent by the first terminal device to the session management network element is in addition to the request Creating the first session also indicates that the uplink of the first session is associated with the second session, where the uplink of the first session is associated with the second session means that the uplink data received through the first session can be forwarded through the second session.
  • the first session creation request indicates that the uplink of the first session is associated with the second session.
  • the first session creation request carries the identifier of the second session, such as the MAC address or IP of the second session.
  • the address for another example, carries a session association identifier in the first session creation request, and the session association identifier can indicate that the uplink of the first session is associated with the second session.
  • the first session creation request may also include flow direction information of the first session, that is, upstream flow indication information.
  • the session association identifier may be a group identifier.
  • the first terminal device When the first terminal device is requesting to create the first session, that is, when sending the first session creation request, it may carry the group identifier, and the second terminal device is sending the user data to the session management network element.
  • the session creation request When a session creation request for creating a second session is requested, the session creation request may also carry the same group identifier.
  • the session management network element When the session management network element receives the session creation request (the first session creation request from the first terminal device and the session creation request from the second terminal device) carrying the same group identifier, it can determine that the first terminal device and The session of the second terminal device has an association relationship.
  • the session association identifier can be a pre-appointed identifier.
  • the session management network element receives a session creation request carrying the same identifier (the first session creation request from the first terminal device and the session creation request from the second terminal device ), it can also be determined according to the identifier that there is an association relationship between the session between the first terminal device and the second terminal device, and then it can be determined that the uplink of the first session is associated with the second session.
  • Step 502 After receiving the first session creation request, the session management network element configures a first forwarding rule in the user plane network element, where the first forwarding rule instructs to forward the uplink data packet from the first session through the second session.
  • the session management network element When the session management network element configures the first forwarding rule in the user plane network element, it may send an N4 session creation request carrying the first forwarding rule to the user plane network element to create the first forwarding rule of the first session. After receiving the N4 session creation request, the user plane network element locally configures the first forwarding rule.
  • the first forwarding rule indicates that there are many ways to forward the uplink data message from the first session through the second session, several of which are listed below:
  • the identifier of the second session may be the N4 session identifier of the second session.
  • the user plane network element may determine that the upstream flow of the first session is associated with the second session according to the identifier of the second session.
  • the first forwarding rule that the user plane network element can configure is that after receiving the upstream data (also referred to as an upstream data packet) through the first session, the upstream data is sent through the second session.
  • the session association identifier For the session association identifier, please refer to the foregoing description, which will not be repeated here.
  • the first forwarding rule that the user plane network element can configure is to receive the upstream data from the first session and send the upstream data to the local forwarding module.
  • the user plane network element can configure the first forwarding rule according to the existing group management method, that is, the first forwarding rule configured by the user plane network element for the first session Specifically, it is receiving uplink data from the first session and sending the uplink data to the local forwarding module.
  • GTP-U General Radio Packet Service Tunneling Protocol User Plane
  • the first forwarding rule that the user plane network element can configure is to receive the upstream data from the first session, and add the GTP-U identifier of the second session to the upstream data, and add this
  • the uplink data identified by the GTP-U of the second session is sent to the local forwarding module.
  • the session management network element may send a first session creation response to the first terminal to indicate that the first session is successfully created, that is, the first session uplink is established The association of the stream with the second session.
  • the first session creation request requests the association between the upstream of the first session and the second session.
  • the first terminal device can also request the downstream of the first session.
  • the downstream of the first session receives data from the data network, that is, the downstream of the first session is associated with the N6 interface of the user plane network element.
  • the upstream and downstream flows of the first session are both bound to the second session, that is, the first session and the second session are associated, the following manner may also be used, see FIG. 6 for details.
  • FIG. 6 is a forwarding rule configuration method provided by an embodiment of the application, and the method includes:
  • Step 601 The first terminal device sends a first session creation request to the session management network element, where the first session request is used to request the creation of a first session and indicate that the first session is associated with the second session.
  • association between the first session and the second session includes that the uplink data received through the first session is forwarded through the second session, and the uplink data received through the second session is forwarded through the first session. That is to say, the relationship between the first session and the second session includes the association between the upstream of the first session and the second session, and the downstream of the first session and the second session (that is, the downstream of the first session and the second session). Session association) association.
  • the manner of indicating the association between the first session and the second session is the same as the manner of associating the upstream of the first session with the second session.
  • the foregoing content please refer to the foregoing content, which will not be repeated here.
  • Step 602 After the session management network element receives the first session creation request, it configures a forwarding rule in the user plane network element.
  • the forwarding rule instructs to forward the uplink data packet from the first session through the second session (that is, the first forwarding Rules) and receiving uplink data packets from the second session through the first session (may be referred to as the second forwarding rule). It is the same as step 502. For details, please refer to the related description of step 502, which will not be repeated here.
  • the identifier of the second session may be the N4 session identifier of the second session.
  • the user plane network element may determine that the upstream flow of the first session is associated with the second session according to the identifier of the second session.
  • the forwarding rule that is, the first forwarding rule that the user plane network element can configure is that after receiving the upstream data (also referred to as the upstream data packet) through the first session, through the second session Send the uplink data.
  • the forwarding rule (that is, the second forwarding rule) that the user plane network element can configure is that after receiving the uplink data through the second session, the uplink data is sent through the first session.
  • the forwarding rule may be configured as the forwarding rule of the second session.
  • the session association identifier For the session association identifier, please refer to the foregoing description, which will not be repeated here.
  • the forwarding rule (that is, the first forwarding rule) that can be configured by the user plane network element is to receive the upstream data from the first session and send the upstream data to the local forwarding module.
  • the data packet from the second session is matched from the local forwarding module, and the matched packet is sent through the first session.
  • the user plane network element can configure the forwarding rule according to the existing group management method, that is, the forwarding rule configured by the user plane network element for the upstream of the first session is specific
  • the forwarding rule configured for the downstream flow of the first session is specifically to match the second terminal device belonging to the same group from the local forwarding module
  • the matched packet is sent through the first session of the first terminal device located in the same group.
  • GTP-U General Radio Packet Service Tunneling Protocol User Plane
  • the forwarding rule that is, the first forwarding rule that the user plane network element can configure is to receive the upstream data from the first session, and add the GTP-U identifier of the second session to the upstream data , And send the uplink data with the GTP-U identifier of the second session added to the local forwarding module.
  • the forwarding rule that is, the second forwarding rule that can be configured by the user plane network element is to match the data packet that includes the GTP-U identifier of the first session from the forwarding module, and pass the second session Send the message.
  • the session management network element may send a second session creation response to the first terminal, which is used to indicate that the first session is successfully created, that is, the first session upstream and Association of the second session.
  • FIG. 7 is a forwarding rule configuration method provided by an embodiment of the application, and the method includes:
  • Step 701 The second terminal device sends a second session creation request to the session management network element, where the second session request is used to request the creation of the second session and to indicate the downstream association of the first session and the second session.
  • Step 702 After the session management network element receives the second session creation request, the session management network element can create a second session, configure the first forwarding rule in the user plane network element, and the first forwarding rule indicates that the second session is forwarded from the second session Upstream data packets of a session. It is the same as step 502. For details, please refer to the related description of step 502, which will not be repeated here.
  • the session management network element can trigger the user plane network element to create the first forwarding rule of the first session.
  • the session management network element can also trigger the user plane network element to create the third forwarding rule of the second session.
  • the session management network element may send a second session creation response to the second terminal to indicate that the second session is successfully created, that is, the first session uplink is established The association of the stream with the second session.
  • the second terminal device can send an instruction to the session management network element to indicate that the first session and the The third session creation request for the uplink association of the second session (or the association of the first session and the second session).
  • the session management network element may configure the second session of the second session on the user plane network element.
  • a second forwarding rule where the second forwarding rule instructs to forward the uplink data packet from the second session through the first session.
  • the manner in which the first session is associated with the uplink of the second session and the manner in which the first session is associated with the second session is indicated are the same as the manner in which the first session is associated with the second session in the embodiment shown in FIG. 5 or FIG.
  • the method and the method of indicating the association between the first session and the second session are similar, except that the information related to the first session (such as the identifier of the first session, the GTP-U identifier, etc.) is carried here.
  • the manner in which the session management network element configures the second forwarding rule of the second session on the user plane network element is similar to the manner in which the session management network element configures the first forwarding rule of the first session on the user plane network element.
  • the foregoing content please refer to the foregoing content. I won't repeat it here.
  • the first terminal device may send a fourth session creation request to the session management network element, and the fourth session creation request is used to request the creation of the first session and to indicate that the second session is associated with the downstream flow of the first session, so that the session management network element can
  • the user plane network element creates the second forwarding rule for the second session.
  • the session management network element may also trigger the user plane network element to create a fourth forwarding rule for the first session.
  • One session receives uplink data packets from the second session.
  • the terminal devices are used to send the session creation request (the first session creation request, the second session creation request, the third session creation request, or the fourth session creation request ) Take an example for description.
  • the terminal device may also send a session modification request, and inform the session management network element of the association relationship between the first session and the second session through the session modification request.
  • the specific process is similar to sending a session creation request, and will not be repeated here.
  • the first request comes from an application function network element, and the first request is a first configuration request for configuring the first session.
  • Step 801 The application function network element sends a first configuration request to the session management network element, where the first configuration request is used to indicate that the uplink of the first session is associated with the second session or the first session is associated with the second session.
  • the application network element can trigger the creation of a data stream in the first session, send a first configuration request, and further configure the first session.
  • the first configuration request indicates that the uplink of the first session is associated with the second session or the manner in which the first session is associated with the second session is associated with the first session creation request indicates that the uplink of the first session is associated with the second session or the first session is associated with the second session.
  • the second session association method is similar. For details, please refer to the foregoing content, which will not be repeated here.
  • Step 802 After receiving the first configuration request, the session management network element configures a first forwarding rule in the user plane network element, where the first forwarding rule instructs to forward the uplink data packet from the first session through the second session. It is the same as step 501. For details, please refer to the related description of step 501, which will not be repeated here.
  • the application function network element may also send a second configuration request.
  • Step 803 The application function network element sends a second configuration request to the session management network element, where the second configuration request is used to indicate that the uplink of the first session is associated with the first session or the first session is associated with the second session.
  • the application network element can trigger the creation of a data stream in the second session, send a second configuration request, and further configure the second session.
  • the second configuration request indicates that the uplink of the second session is associated with the first session or the manner in which the first session is associated with the second session is associated with the third session creation request indicating that the uplink of the second session is associated with the first session or the first session is associated with the first session.
  • the second session association method is similar. For details, please refer to the foregoing content, which will not be repeated here.
  • Step 804 After receiving the second configuration request, the session management network element configures a second forwarding rule in the user plane network element, the second forwarding rule instructing to forward the uplink data packet from the second session through the first session.
  • the session management network element configures a second forwarding rule in the user plane network element, the second forwarding rule instructing to forward the uplink data packet from the second session through the first session.
  • step 803 to step 804 may not be performed.
  • the first forwarding rule is configured on the user plane network element, and the user plane network element can forward data according to the first forwarding rule or the second forwarding rule.
  • FIG. 9 is a data transmission method provided by an embodiment of the application. The method includes:
  • Step 901 The first terminal device sends a first uplink data packet through the first session.
  • Step 902 After receiving the first uplink data packet through the first session, the user plane network element may forward the first uplink data packet through the second session according to the first forwarding rule.
  • Step 903 The second terminal device receives the first uplink data packet through the second session.
  • the following steps 904 to 906 may also be performed.
  • Step 904 The second terminal device sends a second uplink data packet through the second session.
  • Step 905 After receiving the second uplink data packet through the second session, the user plane network element may forward the second uplink data packet through the first session according to the second forwarding rule.
  • Step 906 The first terminal device receives the second uplink data packet through the first session.
  • the user plane network element can determine the required data based on the source of the first uplink data message (the first session).
  • the session for forwarding the uplink data message that is, the terminal device (the second terminal device) that receives the uplink data message is determined.
  • the following further describes a forwarding rule configuration method and data transmission method provided in the embodiments of the present application based on the network architecture shown in FIG. 4b.
  • an embodiment of the present application provides a forwarding rule configuration method and a data transmission method, wherein steps 1001 to 1005 are forwarding rule configuration methods, and steps 1006 to 1017 are data transmission methods.
  • Step 1001 The UPF network element configures the session corresponding to the N6 interface as the session of the UE1, so that the UPF network element can directly forward the data message through the session between the N6 interface and the UE1.
  • the correspondence between the N6 interface and the session may be pre-configured in the UPF network element, and the UPF network element may configure the session corresponding to the N6 interface according to the correspondence.
  • UE1 may also send a fifth session creation/modification request to the SMF network element.
  • the fifth session creation/modification request is used to request the creation of a session of UE1.
  • the fifth session creation/modification request may also indicate the session location of UE1.
  • the associated data network name (data network name, DNN), and the DN indicated by the DNN is associated with the N6 interface of the UPF network element.
  • the SMF network element After receiving the fifth session creation/modification request, the SMF network element notifies the UPF network element to create the session of UE1, and configures the session corresponding to the N6 interface as the session of UE1.
  • Step 1001 essentially configures the data packet forwarding rules between the slave device 1 and the master device, that is, the master device sends the data packet to UE1 through the session of UE1, so that the slave device 1 can obtain the data packet from UE1. Arts.
  • Step 1002 UE2 sends a sixth session creation/modification request to the SMF network element.
  • the sixth session creation/modification request is used to request the creation of a session of UE2.
  • the sixth session creation/modification request may also indicate the session of UE2 and UE3. Associated.
  • the embodiment of this application does not limit the manner in which the sixth session creation/modification request indicates that the session of UE2 is associated with the session of UE3.
  • the sixth session creation/modification request may indicate the session between UE2 and UE3 by carrying the session identifier of UE3.
  • the association may also indicate that the session of UE2 is associated with the session of UE3 by carrying the group identifier of the group where UE2 and UE3 are located, and may also indicate that the session of UE2 is associated with the session of UE3 by carrying a pre-appointed session association identifier.
  • Step 1003 After receiving the sixth session creation/modification request, the SMF network element may send the first N4 session creation/modification request to the UPF network element to create/modify the forwarding rule of the UE2 session.
  • the forwarding rule indicates to forward the uplink data message from the session of UE2 through the session of UE3.
  • the forwarding rule can be expressed as any of the following:
  • the uplink of the UE2 session send the uplink data (also called uplink data message) received through the session of UE2 to the session of UE3; for the downlink of the UE2 session, when configuring the forwarding rule of the UE3 session , Configure to send the uplink data received through the session of UE3 to the session of UE2.
  • This configuration process can be performed when creating/modifying the forwarding rule of the UE3 session.
  • the uplink data is sent to the local forwarding module.
  • the data packet is matched from the local forwarding module, that is, the session association identifier or the session identifier of the UE3 is matched, and the matched data packet is sent through the session of UE2.
  • the GTP-U identifier of the session of the UE3 is added to the uplink data, and then sent to the local forwarding module.
  • the data packet is matched from the local forwarding module, that is, the GTP-U identifier of the session of UE2 is matched, and the matched data packet is sent through the session of UE2.
  • forwarding rules can be configured in the way of existing group management. That is, after the uplink data is received through the session of UE2, the uplink data is sent to the local forwarding module; and the data packet of UE3 belonging to the same group is matched from the local forwarding module, and the matched data packet is passed through UE2 The conversation is sent.
  • step 1002 to step 1003 the forwarding rule for the session of UE1 connected to slave device 1 is essentially configured, that is, slave device 1 can send data packets to UE3 (that is, slave device 4) through the session of UE2, and The data message from UE3 can be received through the session of UE2.
  • Step 1004 UE3 sends a seventh session creation/modification request.
  • the seventh session creation/modification request is used to request creation/modification of the session of UE3.
  • the sixth session creation/modification request may also indicate that the session of UE2 is associated with the session of UE3.
  • the instruction method is the same as step 1002.
  • Step 1005 The SMF network element sends a second N4 session creation/modification request to the UPF network element to create/modify the forwarding rule of the UE3 session.
  • the forwarding rule indicates to forward the data message from the session of UE3 through the session of UE2.
  • the uplink data (also referred to as an uplink data packet) received through the UE3 session is sent to the UE2 session.
  • the uplink data is sent to the local forwarding module.
  • the data packet is matched from the local forwarding module, that is, the session association identifier or the session identifier of UE2 is matched, and the matched data packet is sent through the session of UE3.
  • the GTP-U identifier of the session of UE2 is added to the uplink data, and then sent to the local forwarding module.
  • the data packet is matched from the local forwarding module, that is, the GTP-U identifier of the UE3 session is matched, and the matched data packet is sent through the UE3 session.
  • forwarding rules can be configured in the way of existing group management. That is, after the uplink data is received through the session of UE3, the uplink data is sent to the local forwarding module; and the data packet of UE2 belonging to the same group is matched from the local forwarding module, and the matched data packet is passed through UE3 The conversation is sent.
  • Steps 1004 to 1005 essentially configure the forwarding rules for the session of UE3 connected to slave device 4, that is, slave device 4 can send data packets to UE2 (that is, slave device 1) through the session of UE3, or Receive data packets from UE2 through the session of UE3.
  • UE1 to UE3 send a session creation/modification request to the SMF network element to indicate the association between sessions.
  • the associated message (that is, the first request) between the session and the session of the UE3 may also be sent by the AF network element to the SMF network element.
  • the AF network element may send the first request to the PCF through the NEF network element (or the AF network element may also directly send the first request to the PCF network element), and then the PCF network element sends the first request to the SMF network element.
  • the AF network element sends the first request to the SMF network element through NEF transmission (or the AF network element may also directly send the first request to the SMF network element).
  • Step 1006 The master device sends the first message to the UPF network element.
  • Step 1007 After receiving the first packet, the UPF network element forwards the first packet to the session of UE1 according to the correspondence between the N6 side interface and the session.
  • Step 1008 After receiving the first message, the UE1 sends the first message to the slave device 1.
  • Step 1009 After the slave device 1 receives the first message, it sends it to the slave device 2 and the slave device 3, and then the first message is sent back to the slave device 1.
  • the first message may be processed.
  • Step 1010 The slave device 1 sends the first packet to the UPF network element through the session of the UE2. That is, the slave device 1 sends the first message to the UE2, and the UE2 sends the first message to the UPF network element through the session of the UE2.
  • Step 1011 The UPF network element sends the first packet to UE3 through the session of UE3 associated with the session of UE2 according to the forwarding rule of the session of UE2.
  • Step 1012 After receiving the first message, the UE3 sends the first message to the slave device 4.
  • Step 1013 After receiving the first message from the device 4, the first message is read, and the first message is sent back to the UPF network element through the session of the UE3. That is, the slave device 4 sends the first message to the UE3, and the UE3 sends the first message to the UPF network element through the session of the UE3.
  • Step 1014 The UPF network element sends the first packet to the session of UE2 associated with the session of UE3 according to the forwarding rule of the session of UE3. That is, the UPF network element sends the first message to UE2 through the session of UE2.
  • Step 1015 UE2 is sending the first message to slave device 1.
  • Step 1016 After receiving the first message from UE2, slave device 1 sends the first message back to the UPF network element through the session of UE1.
  • Step 1017 The UPF network element forwards the first packet to the master device according to the correspondence between the session of UE1 and the N6 interface.
  • an embodiment of the present application provides a forwarding rule configuration method and a data transmission method, wherein steps 1101 to 1105 are forwarding rule configuration methods, and steps 1106 to 1114 are data transmission methods.
  • Step 1101 The UPF network element configures the session corresponding to the N6 interface. Specifically, the UPF configures the session corresponding to the uplink of the N6 interface as the session of UE1, and the session corresponding to the downlink of the N6 interface is the session of UE3.
  • Step 1101 essentially configures the data packet forwarding rules between the slave device 1 and the master device and between the slave device 4 and the master device, that is, the master device sends the data packet to UE1 through the session of UE1.
  • Slave 1 can obtain the data message from UE1.
  • the master device receives the data message from the slave device 4 through the session of the UE3.
  • Step 1102 UE1 sends an eighth session creation/modification request to the SMF network element.
  • the eighth session creation/modification request is used to request the creation/modification of the session of UE1.
  • the eighth session creation/modification request may also indicate the uplink of the session of UE1.
  • the DNN associated with the flow and the downstream flow of the session of UE1 are associated with the session of UE3, where the DN indicated by the DNN is associated with the N6 interface of the UPF network element.
  • the eighth session creation/modification request indicates that the downlink flow of the session of UE1 is associated with the session of UE3 and the sixth session creation/modification request may also indicate that the manner in which the session of UE2 is associated with the session of UE3 is similar, that is, the eighth session is created.
  • The/modification request may indicate that the downlink of the session of UE1 is associated with the session of UE3 by carrying the identifier of the session of UE3, the group identifier of the group where UE1 and UE3 are located, or the pre-appointed session association identifier.
  • Step 1103 After receiving the eighth session creation/modification request, the SMF network element may send a third N4 session creation/modification request to the UPF network element, which is used to create/modify the uplink forwarding rule of the session of UE1 and the downlink forwarding rule.
  • the forwarding rule indicates to forward the data message from the session of UE2 through the session of UE3.
  • the forwarding rule of the session uplink of UE1 indicates to send the uplink data received through the session of UE1 to the session of UE3.
  • the configuration method of the forwarding rule of the session upstream of the UE1 is similar to the forwarding rule of the session upstream of the UE2 in FIG.
  • the forwarding rule of the session downstream of the UE1 indicates that the data packet is received from the N6 interface corresponding to the DNN.
  • Step 1104 UE3 sends a ninth session creation/modification request to the SMF network element.
  • the ninth session creation/modification request is used to request the creation/modification of the session of UE3.
  • the ninth session creation/modification request may also indicate the uplink of UE3’s session.
  • the DNN associated with the flow and the downstream flow of the session of UE3 are associated with the session of UE1, where the DN indicated by the DNN is associated with the N6 interface of the UPF network element.
  • the ninth session creation/modification request UE3's session downlink can be associated with the session of UE1 by carrying the session identifier of UE1, carrying the group identifier of the group where UE1 and UE3 are located, or the pre-agreed session association identifier indicating the session of UE1.
  • Downstream is associated with the session of UE3.
  • Step 1105 After receiving the ninth session creation/modification request, the SMF network element can send a fourth N4 session creation/modification request to the UPF network element, which is used to create/modify the UE3 session upstream forwarding rule and downstream forwarding rule.
  • the forwarding rule for the downlink of the session of UE3 indicates to send the uplink data received through the session of UE1 to the session of UE3.
  • the configuration method of the forwarding rule of the session downlink of UE3 is similar to the forwarding rule of the session downlink of UE2 in FIG.
  • the forwarding rule of the session upstream of UE3 indicates to send a data packet to the N6 interface corresponding to the DNN.
  • Steps 1102 to 1105 essentially configure the data packet forwarding rules between the slave device 1 and the master device, and between the slave device 1 and the slave device 4, that is, the master device sends data packets through the session of UE1 To UE1, so that slave device 1 can obtain the data packet from UE1.
  • the slave device 1 sends a data message to the UE3 through the session of the UE1, and the slave device 4 receives the data message, and sends the data message to the residential device through the session of the UE3.
  • Step 1101 may not be executed.
  • Step 1106 The master device sends a second message to the UPF network element.
  • Step 1107 After receiving the second packet, the UPF network element forwards the second packet to the session of UE1 according to the correspondence between the N6 side interface and the downlink of the UE1 session. That is, the second message is sent to UE1.
  • Step 1108 After receiving the second message, the UE1 sends the second message to the slave device 1.
  • Step 1109 After the slave device 1 receives the second message, it sends it to the subsequent slave device 2 and the slave device 3 to process the second message, and then the processed second message is sent back to the slave device 1.
  • Step 1110 The slave device 1 sends the processed second packet to the UPF network element through the session of the UE1.
  • Step 1111 The UPF network element sends the processed second packet to the session of UE3 according to the forwarding rule of the session upstream of UE1. That is, the second message is sent to UE3.
  • Step 1112 After receiving the processed second message, the UE3 sends the processed second message to the slave device 4.
  • Step 1113 After receiving the processed second message from the device 4, process the processed second message again (for the convenience of description, the second processed message is used here to represent the second message processed by the slave 4 ), sending the processed second processed message back to the UPF network element through the session of UE3.
  • Step 1114 The UPF forwards the second processed packet to the master device according to the correspondence between the session upstream of UE3 and the N6 interface.
  • an embodiment of the present application provides a forwarding rule configuration method and a data transmission method, wherein steps 1201 to 1205 are forwarding rule configuration methods, and steps 1206 to 1224 are data transmission methods.
  • Step 1201 It is the same as step 1101. For details, please refer to the foregoing description, which will not be repeated here.
  • Step 1202 It is the same as step 1102. For details, please refer to the foregoing description, which will not be repeated here.
  • the eighth session creation/modification request may also indicate the address of the slave device associated with UE1.
  • the embodiment of this application does not limit the way of indicating the address of the slave device 1. Two ways are listed below:
  • the first way is to use the self-increment address addressing method for the slave device.
  • the eighth session creation/modification request includes the starting sequence number of the self-increment address of the slave device associated with UE1.
  • it can also indicate the slave device associated with UE1 (slave device 1, slave device 2, and slave device 3). )quantity.
  • the number of slave devices associated with UE1 is 3.
  • the starting sequence number of the self-increment address of the slave device associated with UE1 is the sequence number of the sub-increment address of the slave device 1. Since the slave device 1 is the first slave device to receive the EtherCAT message among the slave devices, so The starting sequence number carried in the eighth session creation/modification request is 0.
  • the second way is to use a fixed address or a logical address for the slave device.
  • the eighth session creation/modification request includes the fixed address or logical address of the slave device associated with UE1.
  • Step 1203 It is the same as step 1103.
  • Step 1203 It is the same as step 1103.
  • the SMF network element may also send the starting sequence number, fixed address or logical address of the self-incremental address of the slave device associated with UE1 to the UPF network element. That is to say, the third N4 session creation/modification request may also carry the starting sequence number, fixed address or logical address of the self-incremental address of the slave device associated with UE1 sent by the UPF network element.
  • Step 1204 It is the same as step 1104. For details, please refer to the foregoing description, which will not be repeated here.
  • the ninth session creation/modification request may also indicate the address of the slave device associated with UE3.
  • the embodiment of the present application does not limit the way of indicating the address of the slave device 4. Two ways are listed below:
  • the first way is to use the self-increment address addressing method for the slave device.
  • the ninth session creation/modification request includes the starting sequence number of the self-increment address of the slave device associated with UE3, and optionally, it can also indicate the number of slave devices (slave device 4) associated with UE3. In this embodiment of the application, the number of slave devices associated with UE3 is one.
  • the starting sequence number of the self-increment address of the slave device associated with UE3 is the sequence number of the sub-increment address of the slave device 4. Since the slave device 4 is the fourth slave device that receives the EtherCAT message in each slave device, so The starting sequence number carried in the ninth session creation/modification request is 3.
  • the second way is to use a fixed address or a logical address for the slave device.
  • the ninth session creation/modification request includes the fixed address or logical address of the slave device associated with UE3.
  • Step 1205 It is the same as step 1105.
  • Step 1205 It is the same as step 1105.
  • the SMF network element may also send the starting sequence number, fixed address or logical address of the self-incremental address of the slave device associated with UE3 to the UPF network element. That is to say, the fourth N4 session creation/modification request may also carry the starting sequence number, fixed address or logical address of the self-incremental address of the slave device associated with UE3 sent by the UPF network element.
  • the UPF network element forwards the data message.
  • Step 1206 The UPF network element receives the third message from the master device from the N6 interface corresponding to the DNN.
  • Step 1207 The UPF network element determines the first sub-message in the third message according to the starting sequence number of the self-incremental address of the slave device associated with UE1, and forwards the determined first sub-message to the session of UE1.
  • the number of first sub-messages is not limited here, it can be one or more.
  • the UPF network element can extract the sub-messages in the third message that the self-increment address of the slave device is sorted after 0 and after 0, and will extract
  • the sub-message is encapsulated, and the encapsulated sub-message is forwarded through the session of UE1.
  • the advanced sub-message here may also include all the sub-messages in the third message, and the third message may be directly forwarded.
  • the UPF extracts three sub-messages corresponding to slave device 1, slave device 2, and slave device 3 in the third message according to the number of slave devices associated with UE1 and the starting sequence number of the self-incremental address, and encapsulates the three sub-messages.
  • a sub-message forwards the encapsulated word-message to the session of UE1.
  • the EtherCAT network can assign a fixed address to each slave device when the slave device is performing self-increment address addressing, and the UPF network element can record the fixed address of each slave device for subsequent data message forwarding .
  • the fixed address of each slave device saved by the UPF network element can also be that after UE1 and UE3 (or AF network element) send the fixed address of the associated slave device to the SMF network element, SMF The network element is sent to the UPF network element.
  • Step 1208 The UPF network element sends the first sub-message to UE1 through the session of UE1.
  • Step 1209 After receiving the first sub-message, UE1 sends the first sub-message to slave device 1.
  • Step 1210 After receiving the first sub-message from device 1, it processes the first sub-message, and sends the processed first sub-message to the subsequent slave device 2 and slave device 3.
  • the first processed sub-message is used to represent the first sub-message processed by the slave device 3), and then the first processed sub-message is sent back to the slave device 1.
  • Step 1211 The slave device 1 sends the first processed sub-message to the UPF network element through the session of the UE1.
  • Step 1212 The UPF network element determines the second sub-message corresponding to the slave device associated with UE3 according to the starting sequence number of the sub-incremental address of the slave device associated with UE3, encapsulates the extracted second sub-message, and passes The session of UE3 sends the encapsulated second sub-message.
  • the UPF network element adds 3 to the address of the self-incremental address in each sub-message in the third message and sends it to session 3, and sends it to the session of UE3.
  • Step 1213 After receiving the encapsulated second sub-message, the UE3 sends the second sub-message to the slave device 4.
  • Step 1214 After the second sub-message is received from the device 4, the processed second sub-message (for convenience of explanation, the second processed sub-message is used here to represent the second message processed by the slave 4), The processed second processed sub-message is sent back to the UPF network element through the session of UE3.
  • Step 1215 After receiving the first processing sub-message and the second processing sub-message, the UPF network element merges the first processing sub-messages and the second processing sub-messages into the same message, and then through the uplink of the UE3 session The N6 interface associated with the flow sends the message to the master device.
  • the UPF network element can identify whether the sub-message has been processed, so that the processed sub-message can be sent to the slave device. Two ways of identification are listed below.
  • UPF saves the third message, and then after receiving the first processing sub-message and the second processing sub-message, it compares the first sub-message and the second sub-message of the third message with the first processing sub-message. Message and the second processing sub-message, according to the comparison result, it is determined whether the first sub-message and the second sub-message are modified, the modified sub-message is replaced with the corresponding word message in the third message, and the The third message that replaces the sub-message is sent to the master device.
  • Each sub-message in the third message includes a read-write identifier. If the slave device modifies the sub-message, the read-write identifier can be changed. The changed read-write identifier can indicate that the sub-message has been modified. .
  • the UPF network element can determine whether the sub-message has been modified according to the read-write identifier in the sub-message, and further merge the modified sub-messages into In a message, send the message to the master device.
  • the UPF network element forwards the data message.
  • Step 1216 The UPF network element receives the fourth message from the master device from the N6 interface corresponding to the DNN.
  • Step 1217 The UPF network element sends a fourth packet according to the session of UE1 associated with the N6 side interface.
  • the UPF network element may extract the third sub-message according to the fixed address (or logical address) of the slave device associated with UE1, and forward the third sub-message to the session of UE1.
  • the number of third sub-messages is not limited here, it can be one or multiple.
  • Step 1218 After receiving the third sub-message, UE1 sends the third sub-message to slave device 1.
  • Step 1219 After receiving the third sub-message from device 1, it processes the third sub-message, and sends the processed third sub-message to the subsequent slave device 2 and slave device 3.
  • the third processing sub-message is used to represent the third sub-message processed by the slave device 3), and then the third-processing sub-message is sent back to the slave device 1.
  • Step 1220 The slave device 1 sends the third processed sub-message to the UPF network element through the session of the UE1.
  • Step 1221 The UPF network element sends a fourth packet according to the session of UE4 associated with the N6 side interface.
  • the UPF extracts the fourth sub-message according to the fixed address (or logical address) of the slave device associated with UE3, and forwards the determined fourth sub-message to the session of UE3.
  • the number of fourth sub-messages is not limited here, it can be one or more.
  • Step 1222 After receiving the encapsulated fourth sub-message, the UE3 sends the fourth sub-message to the slave device 4.
  • Step 1223 After receiving the fourth sub-message from the device 4, the processed fourth sub-message (for the convenience of description, the fourth processed sub-message is used here to represent the fourth sub-message processed by the slave 4) , Send the processed fourth processing sub-message back to the UPF network element through the session of UE3.
  • Step 1224 After receiving the first processing sub-message and the fourth processing sub-message, the UPF network element merges the first processing sub-messages and the fourth processing sub-messages into the same message, and then through the uplink of the UE3 session The N6 interface associated with the flow sends the message to the master device.
  • an embodiment of the application also provides a communication device for executing the method executed by the UPF network element described in the method embodiment shown in FIG. 5 to FIG. 12, and the related features can be Refer to the foregoing method embodiment, which will not be repeated here.
  • a communication device provided for this application includes a receiving unit 1301 and a sending unit 1302.
  • the receiving unit 1301 is configured to receive the first uplink data packet through the first session;
  • the sending unit 1302 is configured to forward the first uplink data packet through the second session according to the first forwarding rule, where the first forwarding rule instructs to forward the uplink data packet from the first session through the second session.
  • the receiving unit 1301 is further configured to receive the second uplink data packet through the second session;
  • the sending unit 1302 is further configured to forward the second uplink data packet through the first session according to the second forwarding rule, where the second forwarding rule instructs to forward the uplink data packet from the second session through the first session.
  • the receiving unit 1301 receives the first forwarding rule from the session management network element before the sending unit 1302 receives the first uplink data packet through the first session.
  • the receiving unit 1301 receives the second forwarding rule from the session management network element before the sending unit receives the second uplink data packet through the second session.
  • the first forwarding rule is a forwarding rule of the first session, and the first forwarding rule includes some or all of the following:
  • the second forwarding rule is a forwarding rule of the second session, and the second forwarding rule includes some or all of the following:
  • an embodiment of the present application also provides a communication device for executing the method performed by the SMF network element in the method embodiment shown in FIG. 5 to FIG. 12.
  • a communication device provided for this application includes a receiving unit 1401 and a processing unit 1402.
  • the receiving unit 1401 is configured to receive a first request, where the first request is used to indicate that the uplink of the first session is associated with the second session;
  • the processing unit 1402 is configured to configure a first forwarding rule in the user plane network element, the first forwarding rule instructing to forward the uplink data packet from the first session through the second session.
  • the receiving unit 1401 receives the first request and the types of the first request are as follows:
  • the first session creation (or modification) request is used to request the creation (or modification) of the first session, and to indicate that the upstream of the first session is associated with the second session .
  • the first session creation (or modification) request is received from the first terminal device, and the first session creation (or modification) request is also used to indicate that the uplink of the first session is associated with the second session or the first session is associated with the second session.
  • a second session creation (or modification) request is received from the second terminal device, where the second session creation request is used to request the creation of the second session and to indicate the downstream association between the first session and the second session.
  • a first configuration request is received from an application function network element, the first configuration request is used to configure the first session, and the first configuration request is also used to indicate that the uplink of the first session is associated with the second session or the first session is associated with the second session .
  • the receiving unit 1401 may also receive a second request, the second request being used to request the creation of the second session and to indicate that the uplink of the second session is associated with the first session;
  • the processing unit 1402 may configure a second forwarding rule in the user plane network element, the second forwarding rule instructing to forward the uplink data packet from the second session through the first session.
  • the receiving unit 1401 receives the second request and the types of the second request are as follows:
  • a third session creation (or modification) request is received from the second terminal device.
  • the third session creation (or modification) request is used to request the creation of the second session and indicate that the upstream flow of the second session is associated with the first session, and the third session is created
  • the request is also used to indicate that the uplink of the second session is associated with the first session or the first session is associated with the second session.
  • a second configuration request is received from the application function network element, the second configuration request is used to configure the second session, and the second configuration request is also used to indicate that the uplink of the second session is associated with the first session or the first session is associated with the second session .
  • the first session creation (or modification) request and the first configuration request include some or all of the following: the identifier of the second session or the session association identifier, and the session association identifier indicates that the first session is connected to the first session.
  • the second session creation (or modification) request includes some or all of the following:
  • the identifier of the first session or the session association identifier is a registered trademark of the first session or the session association identifier.
  • the third session creation (or modification) request and the second configuration request include some or all of the following: the identifier of the first session or the session association identifier, and the session association identifier indicates that the first session and the second session Second, session association.
  • the first forwarding rule is a forwarding rule of the first session, and the first forwarding rule includes some or all of the following:
  • the second forwarding rule is a forwarding rule of the second session, and the second forwarding rule includes some or all of the following:
  • an embodiment of the application also provides a communication device for executing the method executed by the first terminal device or UE2 in the method embodiment shown in FIG. 5 to FIG. 12, related features Please refer to the foregoing method embodiment, which will not be repeated here.
  • a communication device provided for this application includes a sending unit 1501 and a receiving unit 1502.
  • the sending unit 1501 is configured to send a first session creation (or modification) request to the session management network element, the first session creation (or modification) request is used to request the creation (or modification) of the first session, and the first session creation (or modification) )
  • the request is also used to indicate that the uplink of the first session is associated with the second session or the first session is associated with the second session;
  • the receiving unit 1502 is configured to receive a first session creation (or modification) response from the session management network element, where the first session creation (or modification) response indicates that the first session creation (or modification) is successful;
  • the sending unit 1501 is further configured to send the first uplink data packet through the first session after the receiving unit receives the first session creation (or modification) response.
  • the first session creation request includes an identifier or a session association identifier of the second session, and the session association identifier indicates that the first session is associated with the second session.
  • an embodiment of the present application also provides a communication device for executing the method executed by the second terminal device in the method embodiment shown in FIG. 7 to FIG. 12.
  • a communication device provided for this application includes a sending unit 1601 and a receiving unit 1602.
  • the sending unit 1601 is configured to send a second session creation (or modification) request to the session management network element, where the second session creation request is used to request the creation of the second session and indicate that the downstream flow of the second session is associated with the first session;
  • the receiving unit 1602 is configured to receive a second session creation (or modification) response from the session management network element, where the third session creation response indicates that the second session is successfully created;
  • the sending unit 1601 is further configured to receive the first uplink data packet through the second session after the receiving unit receives the second session creation (or modification) response.
  • the second session request includes an identifier of the first session or a session association identifier, and the session association identifier indicates that the first session is associated with the second session.
  • a communication device for executing the method executed by the second terminal device in the above-mentioned method embodiment.
  • a communication device provided by this application includes a sending unit 1701 and a receiving unit 1702:
  • the sending unit 1701 is configured to send a third session creation (or modification) request to the session management network element, the third session request is used to request the creation (or modification) of the second session, and the third session creation request is also used to indicate the second session
  • the upstream flow of is associated with the first session or the first session is associated with the second session;
  • the receiving unit 1702 is configured to receive a third session creation (or modification) response from the session management network element, and the third session creation (or modification) response indicates that the second session creation (or modification) is successful;
  • the sending unit 1701 is further configured to send the second uplink data packet through the second session after the receiving unit receives the third session creation (or modification) response.
  • the third session creation (or modification) request includes an identifier of the first session or a session association identifier, and the session association identifier indicates that the first session is associated with the second session.
  • the third session creation (or modification) request may also carry upstream indication information, such as session flow direction information.
  • an embodiment of the application also provides a communication device for executing the method executed by the second terminal device or UE3 in the method embodiment shown in FIG. 8 to FIG. 12, and related features Please refer to the foregoing method embodiment, which will not be repeated here.
  • a communication device provided for this application includes a sending unit 1701 and a receiving unit 1702.
  • the sending unit 1701 is configured to send a third session creation (or modification) request to the session management network element, and the third session creation (or modification) request is used to request the creation (or modification) of the second session and the third session creation (or modification) The request is also used to indicate that the uplink of the second session is associated with the first session or the first session is associated with the second session;
  • the receiving unit 1702 is configured to receive a third session creation (or modification) response from the session management network element, and the third session creation (or modification) response indicates that the second session creation (or modification) is successful;
  • the sending unit 1701 is configured to send the second uplink data packet through the second session after the receiving unit receives the third session creation (or modification) response.
  • the third session creation (or modification) request includes an identifier of the first session or a session association identifier, and the session association identifier indicates that the first session is associated with the second session.
  • the division of units in the embodiments of this application is illustrative, and is only a logical function division. In actual implementation, there may be other division methods.
  • the functional units in the various embodiments of this application can be integrated into one processing unit. In the device, it can also exist alone physically, or two or more units can be integrated into one module.
  • the above-mentioned integrated unit can be realized in the form of hardware or software function module.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to enable a terminal device (which may be a personal computer, a mobile phone, or a network device, etc.) or a processor to execute all or part of the steps of the method in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks and other media that can store program codes. .
  • the session management network element and the user plane network element, the first terminal device, and the second terminal device may all be presented in the form of dividing various functional modules in an integrated manner.
  • the "module” here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the communication device 1800 shown in FIG. 18 includes at least one processor 1801, a memory 1802, and optionally, a communication interface 1803.
  • the processor 1801 may be a central processing unit, and the memory 1802 may be a volatile memory, such as random access memory; the memory may also be a non-volatile memory, such as read-only memory, flash memory, hard disk drive (HDD) Or solid-state drive (SSD) or memory 1802 is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory 1802 may be a combination of the above-mentioned memories.
  • the specific connection medium between the foregoing processor 1801 and the memory 1802 is not limited in the embodiment of the present application.
  • the memory 1802 and the processor 1801 are connected through a bus 1804 in the figure.
  • the bus 1804 is represented by a thick line in the figure. Is limited.
  • the bus 1804 can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is used in FIG. 18 to represent it, but it does not mean that there is only one bus or one type of bus.
  • the processor 1801 can have data transceiver functions and can communicate with other devices.
  • an independent data transceiver module such as a communication interface 1803, can be used to send and receive data; the processor 1801 is communicating with other devices. During communication, data transmission can be performed through the communication interface 1803.
  • the processor 1801 in FIG. 18 can call the computer execution instructions stored in the memory 1802, so that the user plane network element can execute any of the foregoing method embodiments The method executed by the user plane network element in.
  • the functions/implementation processes of the receiving unit and the sending unit in FIG. 13 may be implemented by the processor 1801 in FIG. 18 calling a computer execution instruction stored in the memory 1802.
  • the functions/implementation process of the receiving unit and the sending unit in FIG. 14 can be implemented through the communication interface 1803 in FIG. 18.
  • the processor 1801 in FIG. 18 can call the computer execution instructions stored in the memory 1802, so that the session management network element can execute any of the foregoing method embodiments. The method performed by the session management network element in.
  • the functions/implementation processes of the receiving unit and the processing unit in FIG. 14 may be implemented by the processor 1801 in FIG. 18 calling a computer execution instruction stored in the memory 1802.
  • the function/implementation process of the processing unit in FIG. 14 may be implemented by the processor 1801 in FIG. 18 calling computer execution instructions stored in the memory 1802
  • the function/implementation process of the receiving unit in FIG. 14 may be implemented by The communication interface 1803 is implemented.
  • the communication device 1900 shown in FIG. 19 includes at least one processor 1901, a memory 1902, and optionally, a transceiver 1903.
  • the processor 1901 and the memory 1902 are similar to the processor 1801 and the memory 1802. For details, please refer to the foregoing description, which will not be repeated here.
  • the specific connection medium between the foregoing processor 1901 and the memory 1902 is not limited in the embodiment of the present application.
  • the memory 1902 and the processor 1901 are connected by a bus 1904 in the figure, and the bus 1904 is indicated by a thick line in the figure. Is limited.
  • the bus 1904 can be divided into an address bus, a data bus, a control bus, and so on. For ease of presentation, only one thick line is used to represent in FIG. 19, but it does not mean that there is only one bus or one type of bus.
  • the processor 1901 can have data transceiver functions and can communicate with other devices.
  • an independent data transceiver module such as a transceiver 1903, can be set to send and receive data; the processor 1901 is communicating with other devices.
  • the transceiver 1903 can be used for data transmission.
  • the processor 1901 in FIG. 19 can call the computer execution instructions stored in the memory 1902, so that the first terminal device can execute any of the foregoing method embodiments. The method executed by the first terminal device in.
  • the functions/implementation processes of the sending unit and the receiving unit in FIG. 15 can be implemented by the processor 1901 in FIG. 19 calling a computer execution instruction stored in the memory 1902.
  • the functions/implementation process of the transmitting unit and the receiving unit of FIG. 15 and FIG. 16 can be implemented by the transceiver 1903 in FIG. 19.
  • the processor 1901 in FIG. 19 can call the computer execution instructions stored in the memory 1902, so that the second terminal device can execute any of the foregoing method embodiments. The method executed by the second terminal device in.
  • the functions/implementation processes of the sending unit and the receiving unit in FIG. 16 and FIG. 17 can all be implemented by the processor 1901 in FIG. 19 calling a computer execution instruction stored in the memory 1902.
  • the functions/implementation processes of the transmitting unit and the receiving unit in FIG. 16 and FIG. 17 can be implemented by the transceiver 1903 in FIG. 19.
  • this application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种通信方法及装置，用以实现用户面网元将数据报文通过会话传输至EtherCAT网络中的各个从设备。本申请中，用户面网元可以通过第一会话接收第一上行数据报文，该第一会话为第一终端设备的会话；之后，所述用户面网元根据指示通过第二会话转发来自所述第一会话的上行数据报文的第一转发规则，通过第二会话转发所述第一上行数据报文，用户面网元在转发来自第一上行数据报文时，根据第一会话与第二会话之间的关联关系，通过与第一会话关联的会话，转发第一上行数据报文，当第二终端设备与从设备或主设备关联时，用户面网元可以通过第二会话，将第一上行数据报文发送给与第二终端设备与关联的从设备或主设备。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2020年04月29日提交中国专利局、申请号为202010356026.5、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
目前，在第五代移动通信技术(5th generation mobile networks，5G)***中，终端设备(user equipment，UE)之间的数据转发，可以通过用户面网元实现本地转发，以UE1和UE2之间的数据转发为例，UE1向用户面网元发送携带目的地址为UE2的媒体存取控制地址(media access control address，MAC)的数据报文，用户面网元接收到该数据报文后，识别该数据报文的目的地址，将该数据报文通过UE2会话发送至UE2。
以太网控制自动化技术(ether control automation technology，EtherCAT)***是以以太网为基础的通信***，EtherCAT网络包括一个主设备和多个从设备，主设备和从设备的网络接口具备发送和接收功能。主设备和从设备间通过有线连接实现不同的物理拓扑结构。EtherCAT网络中的数据报文的传输路径为一个经过主设备以及各个从设备的环形回路。
鉴于5G***中终端设备间数据转发是通过用户面网元根据数据报文的特征(例如报文中的目的地址)实现的，当EtherCAT设备通过5G***接入，数据报文要实现EtherCAT的传输机制，即同一数据报文需要依次经过各个EtherCAT设备，也就是说，该数据报文需要多次经过5G***进行传输；而该数据报文在多次到达5G***中的用户面网元时不改变报文特征，因此由于5G***中的用户面网元现有的数据转发机制限制，使得该数据报文在进入5G***中的用户面网元后，无法根据数据报文本身的特征确定转发报文的EtherCAT网络中的设备，导致EtherCAT网络与5G***结合的通信***中无法形成主设备和多个从设备之间数据报文传输的环形回路，用户面网元不能将数据报文通过会话传输至EtherCAT网络中的各个从设备。
发明内容
本申请提供一种通信方法及装置，用以实现用户面网元将数据报文通过会话传输至EtherCAT网络中的各个从设备。
第一方面，本申请实施例提供了一种通信方法，方法包括：用户面网元可以通过第一会话接收第一上行数据报文，该第一会话为第一终端设备的会话；之后，用户面网元根据指示通过第二会话转发来自第一会话的上行数据报文的第一转发规则，通过第二会话转发第一上行数据报文，其中，第二会话为第二终端设备的会话，也就是说，用户面网元可以通过第二会话将第一上行数据报文发送给第二终端设备。
通过上述方法，用户面网元在转发来自第一终端设备的上行数据报文(也即第一上行数据报文)时，可以根据第一终端设备的会话与第二终端设备的会话之间的关联关系，通过与第一终端设备的会话关联的会话，转发第一上行数据报文，这样当第一终端设备与EtherCAT网络中的从设备或主设备关联时，用户面网元可以通过第一终端设备的会话，接收来自与第一终端设备与关联的从设备或主设备的第一上行数据报文；当第二终端设备与EtherCAT网络中的从设备或主设备关联时，用户面网元可以通过第二终端设备的会话，将第一上行数据报文发送给与第二终端设备与关联的从设备或主设备。
在一种可能的设计中，用户面网元还可以通过第二会话接收第二上行数据报文；之后，用户面网元根据第二转发规则，通过第一会话转发第二上行数据报文，其中，第二转发规则指示通过第一会话转发来自第二会话的上行数据报文。
通过上述方法，用户面网元在转发来自第二终端设备的上行数据报文(也即第二上行数据报文)时，可以根据第一终端设备的会话与第二终端设备的会话之间的关联关系，通过与第二终端设备的会话关联的会话，转发第二上行数据报文，这样当第二终端设备与EtherCAT网络中的从设备或主设备关联时，用户面网元可以通过第二终端设备的会话，接收来自与第二终端设备与关联的从设备或主设备的第二上行数据报文；当第一终端设备与EtherCAT网络中的从设备或主设备关联时，用户面网元可以通过第一终端设备的会话，将第二上行数据报文发送给与第二终端设备与关联的从设备或主设备。
在一种可能的设计中，用户面网元通过第一会话接收第一上行数据报文之前，用户面网元中还可以预先配置第一转发规则。例如，用户面网元可以从会话管理网元接收第一转发规则。
通过上述方法，用户面网元中预先配置有第一转发规则，可以保证第一上行数据报文可以通过第二会话转发。
在一种可能的设计中，用户面网元通过第二会话接收第二上行数据报文之前，用户面网元中还可以预先配置第二转发规则。例如，用户面网元可以从会话管理网元接收第二转发规则。
通过上述方法，用户面网元中预先配置有第二转发规则，可以保证第二上行数据报文可以通过第二会话转发。
在一种可能的设计中，第一转发规则为第一会话的转发规则，第一转发规则包括下列的部分或全部：
第二会话的标识、会话关联标识、或第二会话的GTP-U标识，其中，会话关联标识指示第一会话与第二会话关联。
通过上述方法，第一转发规则可以通过携带第二会话的标识、会话关联标识等方式灵活的指示通过第二会话转发来自第一会话的上行数据报文，适用于多种不同的应用场景。
在一种可能的设计中，第二转发规则为第二会话的转发规则，第二转发规则包括下列的部分或全部：
第一会话的标识、会话关联标识、或第一会话的通用无线分组业务隧道协议用户面GTP-U标识，其中，会话关联标识指示第一会话与第二会话关联。
通过上述方法，第二转发规则可以通过携带第一会话的标识、会话关联标识等方式灵活的指示通过第一会话转发来自第二会话的上行数据报文，适用于多种不同的应用场景。
第二方面，本申请实施例提供了一种通信方法，该方法应用于第一终端设备，方法包 括：首先。第一终端设备可以向会话管理网元发送第一会话创建(或修改)请求，第一会话创建(或修改)请求用于请求创建(或修改)第一会话，第一会话创建(或修改)请求还用于指示第一会话的上行流与第二会话关联或第一会话与第二会话关联；之后，第一终端设备从会话管理网元接收第一会话创建(或修改)响应后，可以通过第一会话发送第一上行数据报文，第一会话创建(或修改)响应指示第一会话创建(或修改)成功。
通过上述方法，第一终端设备在发起会话创建或修改流程时，可以指示第一会话的上行流与第二会话关联，便于会话管理网元在用户面网元配置第一转发规则。
在一种可能的设计中，第一会话创建(或修改)请求包括第二会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联。可选的，第一会话创建(或修改)请求还可以携带的上行流的指示信息，如会话的流向信息。
通过上述方法，第一会话创建(或修改)请求可以通过携带第一会话的标识、会话关联标识的方式灵活的指示第一会话的上行流与第二会话关联，适用于多种不同的应用场景。
第三方面，本申请实施例提供了一种通信方法，该方法应用于第二终端设备，方法包括：首先，第二终端设备向会话管理网元发送第二会话创建(或修改)请求，第二会话创建(或修改)请求用于请求创建(或修改)第二会话以及指示第二会话的下行流与第一会话关联；
第二终端设备在从会话管理网元接收到第二会话创建(或修改)响应后，通过第二会话接收第一上行数据报文，第二会话创建(或修改)响应指示第二会话创建(或修改)成功。
通过上述方法，第二终端设备在发起会话创建或修改流程时，可以指示第一会话与第二会话的下行流关联，便于会话管理网元在用户面网元配置第一转发规则。
在一种可能的设计中，第二会话创建(或修改)请求包括第一会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联。
通过上述方法，第二会话创建(或修改)请求可以通过携带第一会话的标识、会话关联标识的方式灵活的指示第一会话与第二会话的下行流关联(也即第一会话的上行流与第二会话关联)，适用于多种不同的应用场景。
第四方面，本申请实施例提供了一种通信方法，方法应用于第二终端设备，方法包括：首先，第二终端设备向会话管理网元发送第三会话创建(或修改)请求，第三会话创建(或修改)请求用于请求创建(或修改)第二会话，第三会话创建(或修改)请求还用于指示第二会话的上行流与第一会话关联或第一会话与第二会话关联；之后，第二终端设备在从会话管理网元接收第三会话创建(或修改)响应后，通过第二会话发送第二上行数据报文，第三会话创建(或修改)响应指示第二会话创建(或修改)成功。
通过上述方法，第二终端设备在发起会话创建或修改流程时，可以指示第一会话与第二会话的上行流关联，便于会话管理网元在用户面网元配置第二转发规则。
在一种可能的设计中，第三会话创建(或修改)请求包括第一会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联。可选的，第三会话创建(或修改)请求还可以携带的上行流的指示信息，如会话的流向信息。
通过上述方法，第三会话创建(或修改)请求可以通过携带第一会话的标识、会话关联标识的方式灵活的指示通第二会话的上行流与第一会话关联，适用于多种不同的应用场景。
第五方面，本申请实施例提供了一种通信方法，方法包括：会话管理网元可以接收第一请求，第一请求用于指示第一会话的上行流与第二会话关联；该第一请求可以是第一终端设备、第二终端设备或应用功能网元发送的。之后，会话管理网元在用户面网元中配置第一转发规则，第一转发规则指示通过第二会话转发来自第一会话的上行数据报文。
通过上述方法，会话管理网元在获知第一会话的上行流与第二会话的关联关系后，可以及时的配置第一转发规则，便于后续通过第二会话转发来自第一会话的上行数据报文。
在一种可能的设计中，会话管理网元接收第一请求，包括如下几种情况：
情况一、会话管理网元从第一终端设备接收第一会话创建(或修改)请求，第一会话创建(或修改)请求用于请求创建第一会话以及指示第一会话的上行流与第二会话关联。
情况二、会话管理网元从第一终端设备接收第一会话创建(或修改)请求，第二会话创建(或修改)请求用于请求创建第一会话以及指示第一会话与第二会话关联。
情况三、会话管理网元从第二终端设备接收第二会话创建(或修改)请求，第三会话创建请求用于请求创建第二会话以及指示第一会话与第二会话的下行流关联。
情况四、会话管理网元从应用功能网元接收第一配置请求，第一配置请求用于配置第一会话，第一配置请求还用于指示第一会话的上行流与第二会话关联或第一会话与第二会话关联。
通过上述方法，第一请求可以来自终端设备或其他网元，也即不同的设备可以通过不同的消息告知会话管理网元第一会话(的上行流)的上行流与第二会话关联，适用于不同场景，扩展了应用范围。
在一种可能的设计中，会话管理网元还可以接收第二请求，第二请求用于请求创建第二会话以及指示第二会话的上行流与第一会话关联；之后，会话管理网元在用户面网元中配置第二转发规则，第二转发规则指示通过第一会话转发来自第二会话的上行数据报文。
通过上述方法，会话管理网元在获知第二会话的上行流与第一会话的关联关系后，可以及时的配置第二转发规则，便于后续通过第一会话转发来自第二会话的上行数据报文。
在一种可能的设计中，会话管理网元接收第二请求，包括如下几种情况：
情况一、会话管理网元从第二终端设备接收第三会话创建(或修改)请求，第三会话创建(或修改)请求用于请求创建(或修改)第二会话以及指示第二会话的上行流与第一会话关联。
情况二、会话管理网元从第二终端设备接收第三会话创建(或修改)请求，第三会话创建(或修改)请求用于请求创建(或修改)第二会话以及指示第二会话与第一会话关联。
情况三、会话管理网元从应用功能网元接收第二配置请求，第二配置请求用于配置第二会话，第二配置请求还用于指示第二会话的上行流与第一会话关联或第一会话与第二会话关联。
通过上述方法，第二请求可以来自终端设备或其他网元，也即不同的设备可以通过不同的消息告知会话管理网元第二会话(的上行流)的上行流与第一会话关联，适用于不同场景，扩展了应用范围。
在一种可能的设计中，第一会话创建(或修改)请求以及第一配置请求包括下列中的部分或全部：第二会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联。第一会话创建(或修改)请求中还可以包括上行流的指示信息。第一配置请求在指示第一会话的上行流与第二会话关联时，还可以携带上行流的指示信息。
第二会话创建(或修改)请求包括下列中的部分或全部：第一会话的标识或会话关联标识。第一会话创建(或修改)请求中还可以包括上行流的指示信息。第三会话创建(或修改)请求中还可以包括下行流的指示信息。
通过上述方法，第一请求可以通过携带会话的标识、会话关联标识等方式灵活的指示通第二会话与第一会话关联，适用于多种不同的应用场景。
在一种可能的设计中，第三会话创建(或修改)请求以及第二配置请求包括下列中的部分或全部：第一会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联。第三会话创建(或修改)请求中还可以包括上行流的指示信息。第二配置请求在指示第二会话的上行流与第一会话关联时，还可以携带上行流的指示信息。
通过上述方法，第二请求可以通过携带会话的标识、会话关联标识等方式灵活的指示通第二会话与第一会话关联，适用于多种不同的应用场景。
在一种可能的设计中，第一转发规则为第一会话的转发规则，第一转发规则包括下列的部分或全部：第二会话的标识、会话关联标识、或第二会话的GTP-U标识，其中，会话关联标识指示第一会话与第二会话关联。
通过上述方法，第一转发规则可以通过携带第二会话的标识、会话关联标识等方式灵活的指示通过第二会话转发来自第一会话的上行数据报文，适用于多种不同的应用场景。
在一种可能的设计中，第二转发规则为第二会话的转发规则，第二转发规则包括下列的部分或全部：
第一会话的标识、会话关联标识、或第一会话的通用无线分组业务隧道协议用户面GTP-U标识，其中，会话关联标识指示第一会话与第二会话关联。
通过上述方法，第二转发规则可以通过携带第一会话的标识、会话关联标识等方式灵活的指示通过第一会话转发来自第二会话的上行数据报文，适用于多种不同的应用场景。
第六方面，本申请实施例提供了一种通信方法，该方法应用于应用功能网元，方法包括：首先。应用功能网元向会话管理网元发送第一配置请求，第一配置请求用于配置第一会话，第一配置请求还用于指示第一会话的上行流与第二会话关联或第一会话与第二会话关联。第一配置请求包括下列中的部分或全部：第二会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联，第一配置请求在指示第一会话的上行流与第二会话关联时，还可以携带上行流的指示信息。
通过上述方法，应用功能网元可以在配置第一会话时，可以指示第一会话与第二会话关联，便于会话管理网元在用户面网元配置第一转发规则。
在一种可能的设计中，应用功能网元向会话管理网元发送第二配置请求，第二配置请求用于配置第二会话，第二配置请求还用于指示第二会话的上行流与第一会话关联或第一会话与第二会话关联。第二配置请求包括下列中的部分或全部：第二会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联，第一配置请求在指示第二会话的上行流与第一会话关联时，还可以携带上行流的指示信息。
通过上述方法，应用功能网元可以在配置第二会话时，可以指示第一会话与第二会话关联，便于会话管理网元在用户面网元配置第二转发规则。
第七方面，本申请实施例还提供了一种通信***，有益效果可以参见第一方面和第二方面的描述此处不再赘述，该通信***包括会话管理网元和用户面网元；
会话管理网元，用于接收第一请求，第一请求用于指示第一会话的上行流与第二会话 关联；以及向用户面网元发送第一转发规则，第一转发规则指示通过第二会话转发来自第一会话的上行数据报文。
用户面网元，用于接收第一转发规则；以及通过第一会话接收第一上行数据报文；以及根据第一转发规则，通过第二会话转发第一上行数据报文。
在一种可能的设计中，会话管理网元还可以接收第二请求，第二请求用于请求创建第二会话以及指示第二会话的上行流与第一会话关联；以及向用户面网元发送第二转发规则，第二转发规则指示通过第一会话转发来自第二会话的上行数据报文；
用户面网元可以接收第二转发规则；以及通过第二会话接收第二上行数据报文；以及根据第二转发规则，通过第一会话转发第二上行数据报文。
在一种可能的设计中，第一请求为第一会话创建(或修改)请求；通信***还包括第一终端设备；
第一终端设备，用于向会话管理网元发送第一会话创建(或修改)请求，第一会话创建(或修改)请求用于请求创建(或修改)第一会话，第一会话创建(或修改)请求还用于指示第一会话的上行流与第二会话关联或第一会话与第二会话关联。
在一种可能的设计中，第一请求为第二会话创建(或修改)请求；通信***还包括第二终端设备；
第二终端设备可以向会话管理网元发送第二会话创建(或修改)请求，第三会话创建(或修改)请求用于请求创建(或修改)第二会话以及指示第二会话的下行流与第一会话关联。
在一种可能的设计中，第一请求为第一配置请求，通信***还包括应用功能网元；
应用功能网元可以向会话管理网元发送第一配置请求，第一配置请求用于配置第一会话，第一配置请求还用于指示第一会话的上行流与第二会话关联或第一会话与第二会话关联。
在一种可能的设计中，第二请求为第三会话创建(或修改)请求；通信***包括第二终端设备；
第二终端设备可以向会话管理网元发送第三会话创建(或修改)请求，第三会话创建(或修改)请求用于请求创建(或修改)第二会话，第三会话创建(或修改)请求还用于指示第二会话的上行流与第一会话关联或第一会话与第二会话关联。
在一种可能的设计中，第二请求为第二配置请求，通信***还包括应用功能网元；
应用功能网元可以向会话管理网元发送速搜第二配置请求，第二配置请求用于配置第二会话，第二配置请求还用于指示第二会话的上行流与第一会话关联或第一会话与第二会话关联。
在一种可能的设计中，第一会话创建(或修改)请求包括下列中的部分或全部：
第二会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联。
在一种可能的设计中，第二会话创建(或修改)请求包括下列中的部分或全部：
第一会话的标识或会话关联标识。
在一种可能的设计中，第一配置请求包括下列中的部分或全部：
第二会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联。
在一种可能的设计中，第三会话创建(或修改)请求包括下列中的部分或全部：
第一会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联。
在一种可能的设计中，第二配置请求包括下列中的部分或全部：
第一会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联。
在一种可能的设计中，第一转发规则为第一会话的转发规则，第一转发规则包括下列的部分或全部：
第二会话的标识、会话关联标识、或第二会话的通用无线分组业务隧道协议用户面GTP-U标识，其中，会话关联标识指示第一会话与第二会话关联。
在一种可能的设计中，第二转发规则为第二会话的转发规则，第二转发规则包括下列的部分或全部：
第一会话的标识、会话关联标识、或第一会话的GTP-U标识，其中，会话关联标识指示第一会话与第二会话关联。
第八方面，本申请实施例还提供了一种通信装置，所述通信装置应用于用户面网元，有益效果可以参见第一方面的描述此处不再赘述。该装置具有实现上述第一方面的方法实例中行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，所述装置的结构中包括接收单元和发送单元，这些单元可以执行上述第一方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
第九方面，本申请实施例还提供了一种通信装置，所述通信装置应用于第一终端设备，有益效果可以参见第二方面的描述此处不再赘述。该装置具有实现上述第二方面的方法实例中行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，所述装置的结构中包括接收单元和发送单元，这些单元可以执行上述第二方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
第十方面，本申请实施例还提供了一种通信装置，所述通信装置应用于第二终端设备，有益效果可以参见第三方面的描述此处不再赘述。该装置具有实现上述第三方面的方法实例中行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，所述装置的结构中包括接收单元和发送单元，这些单元可以执行上述第三方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
第十一方面，本申请实施例还提供了一种通信装置，所述通信装置应用于第二终端设备，有益效果可以参见第四方面的描述此处不再赘述。该装置具有实现上述第四方面的方法实例中行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，所述装置的结构中包括接收单元和发送单元，这些单元可以执行上述第四方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
第十二方面，本申请实施例还提供了一种通信装置，所述通信装置应用于会话管理网元，有益效果可以参见第五方面的描述此处不再赘述。该装置具有实现上述第五方面的方法实例中行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，所述装置的结构中包括接收单元和处理单元，这些单元可以执行上述第五方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
第十三方面，本申请实施例还提供了一种通信装置，所述通信装置应用于应用功能网元，有益效果可以参见第六方面的描述此处不再赘述。该装置具有实现上述第六方面的方法实例中行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，所述装置的结构中包括发送单元，这些单元可以执行上述第六方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
第十四方面，本申请实施例还提供了一种通信装置，所述通信装置应用于用户面网元，有益效果可以参见第一方面的描述此处不再赘述。所述通信装置的结构中包括处理器和存储器，所述处理器被配置为支持所述用户面网元执行上述第一方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。所述通信装置的结构中还包括通信接口，用于与其他设备进行通信。
第十五方面，本申请实施例还提供了一种通信装置，所述通信装置应用于第一终端设备，有益效果可以参见第二方面的描述此处不再赘述。所述通信装置的结构中包括处理器和存储器，所述处理器被配置为支持所述第一终端设备执行上述第二方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。所述通信装置的结构中还包括收发器，用于与其他设备进行通信。
第十六方面，本申请实施例还提供了一种通信装置，所述通信装置应用于第二终端设备，有益效果可以参见第三方面的描述此处不再赘述。所述通信装置的结构中包括处理器和存储器，所述处理器被配置为支持所述第二终端设备执行上述第三方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。所述通信装置的结构中还包括收发器，用于与其他设备进行通信。
第十七方面，本申请实施例还提供了一种通信装置，所述通信装置应用于第二终端设备，有益效果可以参见第四方面的描述此处不再赘述。所述通信装置的结构中包括处理器和存储器，所述处理器被配置为支持所述第二终端设备执行上述第四方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。所述通信装置的结构中还包括收发器，用于与其他设备进行通信。
第十八方面，本申请实施例还提供了一种通信装置，所述通信装置应用于会话管理网元，有益效果可以参见第五方面的描述此处不再赘述。所述通信装置的结构中包括处理器和存储器，所述处理器被配置为支持所述基站执行上述第五方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。所述通信装置的结构中还包括通信接口，用于与其他设备进行通信。
第十九方面，本申请实施例还提供了一种通信装置，所述通信装置应用于应用功能网元，有益效果可以参见第六方面的描述此处不再赘述。所述通信装置的结构中包括处理器和存储器，所述处理器被配置为支持所述基站执行上述第六方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。所述通信装置的结构中还包括通信接口，用于与其他设备进行通信。
第二十方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第二十一方面，本申请还提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第二十二方面，本申请还提供一种计算机芯片，所述芯片与存储器相连，所述芯片用于读取并执行所述存储器中存储的软件程序，执行上述各方面所述的方法。
附图说明
图1为5G***的网络架构示意图；
图2为EtherCAT的网络拓扑示意图；
图3为EtherCAT报文的结构示意图；
图4a～图4c为本申请实施例提供的一种网络架构示意图；
图5～图12为本申请实施例提供的一种通信方法的示意图；
图13～图19为本申请实施例提供的一种通信装置的结构示意图。
具体实施方式
本申请提供了一种通信方法及装置，用以实现用户面网元将数据报文通过会话传输至EtherCAT网络中的各个从设备。
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。
本申请实施例涉及到5G***与EtherCAT网络结合，下面先对本申请实施例所涉及的5G***、EtherCAT网络及本申请实施例适用的网络架构进行说明。
请参见图1，为5G***的网络架构示意图，该网络架构为5G网络架构。该5G架构中的网元包括终端设备，图1中以终端设备为UE为例。网络架构还包括无线接入网(radio access network，RAN)、接入和移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、用户面功能(user plane function，UPF)网元、策略控制功能(policy control function，PCF)网元、应用功能(application function，AF)网元、数据网络(data network，DN)等。
RAN的主要功能是控制用户通过无线接入到移动通信网络。RAN是移动通信***的一部分。它实现了一种无线接入技术。从概念上讲，它驻留某个设备之间(如移动电话、一台计算机，或任何远程控制机)，并提供与其核心网的连接。AMF网元负责终端的接入管理和移动性管理，在实际应用中，其包括了LTE中网络框架中MME里的移动性管理功能，并加入了接入管理功能。
SMF网元负责会话管理，如用户的会话建立等。
UPF网元是用户面的功能网元，主要负责连接外部网络，其包括了LTE的服务网关(serving gateway，SGW)和公用数据网网关(public data network GateWay，PDN-GW)的相关功能。
DN负责为终端提供服务的网络，如一些DN为终端提供上网功能，另一些DN为终端提供短信功能等等。
PCF网元的主要功能是执行策略控制，类似于LTE中的策略与计费规则功能(policy and charging rules function，PCRF)网元，主要负责策略授权，服务质量以及计费规则的生成，并将相应规则通过SMF网元下发至UPF网元，完成相应策略及规则的安装。
AF网元可以是第三方的应用控制平台，也可以是运营商自己的设备，AF网元可以为多个应用服务器提供服务，AF网元是可以提供各种业务服务的功能网元，能够通过NEF网元与核心网交互，以及能够和策略管理框架交互进行策略管理。
此外，尽管未示出，核心网控制面功能网元还包括网络开放功能(network exposure function，NEF)、统一数据管理(unified data management，UDM)、网元统一数据仓储(unified data repository，UDR)网元，NEF网元用于提供网络能力开放相关的框架、鉴权和接口，在5G***网络功能和其他网络功能之间传递信息；UDR网元主要用来存储用户相关的签约数据、策略数据、用于开放的结构化数据、应用数据；UDM网元可存储用户的签约信息，实现类似于4G中的HSS的后端。
本申请中的终端设备，又称之为用户设备(user equipment，UE)，是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。终端设备可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
下面对EtherCAT网络及原理进行介绍。
EtherCAT是德国Beckoff公司旗下的ETG(EtherCAT技术协会)负责研发并推广的一种实时以太网技术，它是一种开放的网络协议，可以进行主从设备之间的通信，采用集束帧，网络拓扑总是构成一个逻辑环，在每个周期，主设备(也称为主站、或主节点)向一部分或全部从设备(也称为从站、或从节点)发送数据报文，从一个从设备沿环形拓扑结构进行传输，当主设备发送的数据报文传输经过从设备时，从设备仅接收为其发送的数据，同时添加自己的输出数据到报文中。
为了便于理解，举一个高速列车的例子。EtherCAT的原理类似于高速列车，“火车”(EtherCAT报文)的行驶不会停，在站台上通过窗口一直盯着火车看，我们可以看到整个火车。当火车的窗户边坐的是我们的“熟人”时，站台上的人通过窗口可以跟熟人打招呼(即，每个从设备可以提取或者***数据到主设备发出的数据帧中对应于每个从设备的地址的部分)。
如图2所示，为现有技术中的EtherCAT环形拓扑结构示意图。主设备与从设备之间通过有线传输的方式进行连接，从设备之间也通过有线传输的方式进行连接。一个环形拓扑结构中有一个主设备和至少一个从设备。
如图3所示，为现有技术中的EtherCAT报文的结构示意图。一个EtherCAT报文包括帧头(例如,Ethernet header)、数据(例如,Ethernet data)和帧校验序列(例如,Frame Check Sequence，FCS)。
其中，帧头也可以称为标准以太网帧头，主要包括源地址、目的地址、以太帧类型等。
数据主要包括两个部分：数据头(例如,EtherCAT Header)和报文(例如,EtherCAT  Datagrams)：
1)EtherCAT Header，包含：数据长度(Length)指示域、保留位(R)、数据类型(Type)指示域；其中，数据长度指示域用于指示数据长度，数据类型指示域用于指示数据类型。
2)EtherCAT Datagrams，包含多个子报文，总长度在44-1486字节之间。每个子报文包括10字节的子报文头(Datagram Header)、0-1486字节数据(Data)和2字节工作计数器(working counter，WKC)。其中，子报文头中指示需要接收该子报文的从设备的地址段。
帧校验序列(FCS)，也称为帧尾，是一段循环冗余校验码。源设备发送数据帧时，由帧的帧头和数据部分计算得出FCS，目的设备接收到后，用同样的方式再计算一遍FCS，如果与接收到的FCS不同，则认为帧在传输过程中发生了错误，从而选择丢弃这个帧。FCS提供了一种错误检测机制，用来验证帧在传输过程中的完整性。以太帧中的FCS占用的长度固定，一般为4字节。
当从设备接收到EtherCAT报文时，也即根据EtherCAT报文中子报文的字报文头中的地址段确定是否对该子报文进行处理(该确定过程也可以称为寻址)，处理包括读取子报文中的数据或在子报文中***数据。
针对EtherCAT报文中子报文中的地址段，从设备可以通过如下两种方式进行寻址：
1)、自增量寻址。
每个从设备根据在EtherCAT网络中的位置对应有一个负的自增量地址。主设备发出的EtherCAT报文中的每个子报文(子报文的子报文头)中包括对应的一个从设备的自增量地址，EtherCAT报文在经过一个从设备时，该从设备处理自增量地址为0的子报文，并将EtherCAT报文中各个子报文中的自增量地址加1后，传输给下一个从设备。自增量寻址通常用于扫描硬件配置信息或确定从设备之间的相对位置。
2)、固定地址或逻辑地址：
每个从设备具备一个固定地址(或逻辑地址)，与从设备在EtherCAT网络中的位置无关。固定地址一般为扫描硬件配置过程中分配的，适用于主设备和从设备之间交换大量的数据时使用。逻辑地址为虚拟数据空间中从设备对应的地址，用于对虚拟数据空间进行读写操作。
主设备发出的EtherCAT报文中的每个子报文(子报文的子报文头)包括对应的一个从设备的固定地址(或逻辑地址)。EtherCAT报文在经过一个从设备时，该从设备处理子报文中地址为该从设备固定地址的子报文，在对该子报文处理后，将包括处理后的子报文的EtherCAT报文传输给下一个从设备。
如图4a所示，为本申请适用的一种网络架构示意图，其中，结合了5G***和EtherCAT的网络架构。图4a中EtherCAT网络中的主设备(master)部署在DN中，连接5G***中的UPF网元，EtherCAT网络中的从设备(salve)连接5G***中的UE。这里不限定5G***中的UE上连接的从设备的数量，也不限定5G***中的UE的数量。
例如，EtherCAT网络中的一个或多个从设备可以通过5G***中的一个UE接入5G***，EtherCAT网络中的其他从设备可以通过5G***中的另一个UE接入5G***。又例如，EtherCAT网络中的一个或多个从设备可以与5G***中的UE的一个会话绑定，进而通过该UE接入5G***，也即，所述一个或多个从设备可以通过该会话将数据报文发送至5G***，EtherCAT网络中的其他从设备可以与5G***中的该UE的另一个会话绑定，进而通过该UE接入5G***。也即，所述一个或多个从设备可以通过该会话将数据 报文发送至5G***。
在如图4a所示的网络架构，EtherCAT网络中的主设备可以通过5G***将数据报文发送至于5G***的UE连接的各个从设备，为了保证EtherCAT网络中数据报文传输的环形回路，SMF网元在UE或其他网元(AF网元)的触发下，在UPF网元中配置会话的转发规则，建立会话与会话之间的关联关系，之后，当UPF网元通过会话接收到需要在EtherCAT网络传输的数据报文后，可以基于会话的转发规则，通过与该会话关联的会话转发给数据报文，以使得该数据报文可以转发至与该会话关联的会话，进而传输至与所述与该会话关联的会话绑定的从设备。
需要说明的是，在如图4a所示的网络架构中，仅是以EtherCAT网络中的主设备部署在DN中，从设备部署在UE侧仅说明，本申请实施例并不限定主设备以及从设备部署的位置。例如，主设备以及从设备可以均部署在UE侧或DN中。
基于如图4a所示的网络架构，下面以EtherCAT网络中的包括四个从设备，且主设备部署在DN中，四个从设备位于UE侧为例，介绍本申请实施例适用的两种不同的网络架构。
为了清晰的展示主设备与从设备之间数据报文的传输路径，图4b与4c仅示出了UPF网元、主设备以及从设备之间的连接，其他网元之间的连接方式以及部署位置可参见如图4a。
参见图4b，从设备1、从设备2与从设备3之间连接，从设备1分别连接两个UE，分别为UE1和UE2，从设备4连接UE3。
主设备与从设备1、从设备2、从设备3以及从设备4之间的数据传输路径用黑色带箭头的实线标注。
主设备发出的数据报文经过UPF网元，UPF网元将该数据报文通过UE1的会话传输给从设备1，该数据报文在从设备1、从设备2以及从设备3传输后返回至从设备1，从设备1将该数据报文发送给UE2，UE2通过UE2的会话发送给UPF网元，UPF网元将该数据报文传输通过UE3的会话传输给UE3，UE3将该数据报文传输给从设备4，从设备4之后再将该数据报文返回至UE3，UE3通过UE3的会话将该数据报文发送至UPF网元，UPF网元将该数据报文通过UE2的会话传输给从设备1，从设备1将该数据报文返回至UE1，UE1将该数据报文通过UE1的会话返回至主设备。
需要说明的是，前述说明中以从设备1连接两个不同的UE为例，事实上，从设备1也可以与同一个UE的两个不同的会话绑定，传输路径与前述说明类似。
参见图4c，从设备1、从设备2与从设备3之间连接，从设备1分别连接UE1，从设备4连接UE3。
主设备与从设备1、从设备2、从设备3以及从设备4之间的数据传输路径用黑色带箭头的实线标注。
主设备发出的数据报文经过UPF网元，UPF网元将该数据报文通过UE1的会话传输给从设备1，该数据报文在从设备1、从设备2以及从设备3传输后返回至从设备1，从设备1将该数据报文发送给UE1，UE1通过UE1的会话发送给UPF网元，UPF网元将该数据报文传输通过UE3的会话传输给UE3，UE3将该数据报文传输给从设备4，从设备4之后再将该数据报文返回至UE3，UE3通过UE3的会话将该数据报文发送至UPF网元，UPF网元将该数据报文返回至主设备。
区别与如图4b所示的传输路径，如图4c的传输路径中，从设备4反馈的数据报文不需要在发回至从设备1，传输路径更短，从设备1也无需与多个UE或多个会话绑定。
基于如图4a所示的网络结构，本申请实施例所提供通信方法包括两部分，分别为转发规则配置方法以及数据传输方法，下面分别进行介绍：
(一)、转发规则配置方法。
在本申请实施例中，会话管理网元能够接收来自终端设备或应用功能网元的第一请求，该第一请求用于指示第一会话的上行流与第二会话关联，第一请求可以是新增的请求信息，也可以是已有的请求消息，如会话创建请求或会话修改请求。下面分别以第一请求来自终端设备和应用功能网元为例进行说明。
(1)、第一请求来自第一终端设备，且第一请求为第一会话创建请求，第一会话创建请求指示第一会话的上行流与第二会话关联。
如图5所示为本申请实施例提供的一种转发规则配置方法，该方法包括：
步骤501：第一终端设备向会话管理网元发送第一会话创建请求，第一会话请求用于请求创建第一会话以及指示第一会话的上行流与第二会话关联。
第一终端设备中可以预先配置有第一会话与第二会话的关联关系，当第一终端设备需要创建第一会话时，第一终端设备向会话管理网元发送的第一会话创建请求除了请求创建第一会话，还指示第一会话的上行流与第二会话关联，其中第一会话的上行流与第二会话关联是指通过第一会话接收的上行数据可以通过第二会话进行转发。
本申请并不限定第一会话创建请求指示第一会话的上行流与第二会话关联的方式，例如，在第一会话创建请求中携带第二会话的标识，如第二会话的MAC地址或IP地址，又例如，在第一会话创建请求中携带会话关联标识，该会话关联标识能够指示第一会话的上行流与第二会话关联。可选的，第一会话创建请求中还可以包括第一会话的流向信息，也即上行流的指示信息。
该会话关联标识可以是群组标识，当第一终端设备在请求创建第一会话，也即发送第一会话创建请求时，可以携带群组标识，第二终端设备在向会话管理网元发送用于请求创建第二会话的会话创建请求时，该会话创建请求也可以携带相同的群组标识。
当会话管理网元接收到携带有相同的群组标识的会话创建请求(来自第一终端设备的第一会话创建请求以及来自第二终端设备的会话创建请求)后，可以确定第一终端设备与第二终端设备的会话存在关联关系。
当然，会话关联标识可以是预先约定的标识，当会话管理网元接收到携带有相同的标识的会话创建请求(来自第一终端设备的第一会话创建请求以及来自第二终端设备的会话创建请求)后，也可以根据该标识可以确定第一终端设备与第二终端设备的会话存在关联关系，进而确定第一会话的上行流与第二会话关联。
步骤502：会话管理网元接收到第一会话创建请求后，在用户面网元中配置第一转发规则，第一转发规则指示通过第二会话转发来自第一会话的上行数据报文。
会话管理网元在用户面网元中配置第一转发规则时，可以向用户面网元发送携带有第一转发规则的N4会话创建请求，用于创建第一会话的第一转发规则。用户面网元接收到该N4会话创建请求后，在本地配置第一转发规则。
第一转发规则指示通过第二会话转发来自第一会话的上行数据报文的方式有许多种，下面列举其中几种：
1、第二会话的标识，第二会话的标识可以是第二会话的N4会话标识。用户面网元在接收到包括第二会话的标识的第一转发规则后，可以根据第二会话的标识确定第一会话的上行流与第二会话关联。
对于第一会话的上行流，用户面网元可以配置的第一转发规则为通过第一会话接收来自上行数据(也可以称为上行数据报文)后，通过第二会话发送该上行数据。
2、会话关联标识，关于会话关联标识可参见前述说明，此处不再赘述。
对于第一会话的上行流，用户面网元可以配置的第一转发规则为接收来自第一会话的上行数据，并将该上行数据发送到本地转发模块。
需要说明的是，当会话关联标识为群组标识时，用户面网元可以按照现有的群组管理方式配置第一转发规则，也即用户面网元为第一会话配置的第一转发规则具体为接收来自第一会话的上行数据，并将该上行数据发送到本地转发模块。
3、第二会话的通用无线分组业务隧道协议用户面(GRPS Tunnelling Protocol User Plane，GTP-U)标识。
对于第一会话的上行流，用户面网元可以配置的第一转发规则为接收来自第一会话的上行数据，并在该上行数据中添加第二会话的GTP-U标识，并将该添加了第二会话的GTP-U标识的上行数据发送到本地转发模块。
会话管理网元在用户面网元中配置第一转发规则之后，会话管理网元可以向第一终端发送第一会话创建响应，用于指示第一会话创建成功，也即建立了第一会话上行流与第二会话的关联。
在如图5所示的实施例中，第一会话创建请求请求的是第一会话的上行流与第二会话的关联，采用相同的方式，第一终端设备也可以请求第一会话的下行流与其他会话，第一会话的下行流接收来自数据网络的数据，也即第一会话的下行流与用户面网元的N6接口关联。
但若第一会话的上行流与下行流均与第二会话绑定，也即第一会话和第二会话关联，也可以采用下述方式，具体参见图6。
如图6所示为本申请实施例提供的一种转发规则配置方法，该方法包括：
步骤601：第一终端设备向会话管理网元发送第一会话创建请求，第一会话请求用于请求创建第一会话以及指示第一会话与第二会话关联。
需要说明的是，第一会话与第二会话存在关联关系包括通过第一会话接收的上行数据通过第二会话进行转发、以及通过第二会话接收的上行数据通过第一会话进行转发。也就是说，第一会话与第二会话存在关联关系包括第一会话的上行流与第二会话关联、以及第一会话与第二会话的下行流(也即第一会话的下行流与第二会话关联)关联。
第一会话与第二会话关联的指示方式与第一会话的上行流与第二会话关联的方式相同，具体可参见前述内容，此处不再赘述。
步骤602：会话管理网元接收到第一会话创建请求后，在用户面网元中配置转发规则，该转发规则指示通过第二会话转发来自第一会话的上行数据报文(也即第一转发规则)以及通过第一会话接收来自第二会话的上行数据报文(可以称为第二转发规则)。与步骤502相同，具体可以参见步骤502的相关说明，此处不再赘述。
第一会话的转发规则的指示方式有许多种，下面列举其中几种：
1、第二会话的标识，第二会话的标识可以是第二会话的N4会话标识。用户面网元在 接收到包括第二会话的标识的第一转发规则后，可以根据第二会话的标识确定第一会话的上行流与第二会话关联。
对于第一会话的上行流，用户面网元可以配置的转发规则(也即第一转发规则)为通过第一会话接收来自上行数据(也可以称为上行数据报文)后，通过第二会话发送该上行数据。
对于第一会话的下行流，用户面网元可以配置的转发规则(也即第二转发规则)为通过第二会话接收来自上行数据后，通过第一会话发送该上行数据，对于第一会话的下行流的转发规则的配置，可以在创建第二会话时，将该转发规则配置为第二会话的转发规则。
2、会话关联标识，关于会话关联标识可参见前述说明，此处不再赘述。
对于第一会话的上行流，用户面网元可以配置的转发规则(也即第一转发规则)为接收来自第一会话的上行数据，并将该上行数据发送到本地转发模块。
对于第一会话的下行流，从该本地转发模块匹配来自第二会话的数据报文，通过第一会话发送匹配到的报文。
需要说明的是，当会话关联标识为群组标识时，用户面网元可以按照现有的群组管理方式配置转发规则，也即用户面网元为第一会话的上行流配置的转发规则具体为接收来自第一会话的上行数据，并将该上行数据发送到本地转发模块，为第一会话的下行流配置的转发规则具体为从该本地转发模块匹配属于同一群组的第二终端设备的数据报文，通过位于同一群组的第一终端设备的第一会话发送匹配到的报文。
3、第二会话的通用无线分组业务隧道协议用户面(GRPS Tunnelling Protocol User Plane，GTP-U)标识。
对于第一会话的上行流，用户面网元可以配置的转发规则(也即第一转发规则)为接收来自第一会话的上行数据，并在该上行数据中添加第二会话的GTP-U标识，并将该添加了第二会话的GTP-U标识的上行数据发送到本地转发模块。
对于第一会话的下行流，用户面网元可以配置的转发规则(也即第二转发规则)为从该转发模块匹配包括第一会话的GTP-U标识的数据报文，通过的第二会话发送该报文。
会话管理网元在用户面网元中配置转发规则之后，会话管理网元可以向第一终端发送第二会话创建响应，用于指示第一会话创建成功，也即建立了第一会话上行流与第二会话的关联。
第一会话的上行流与第二会话关联的另一种表述为第一会话与第二会话的下行流关联，故而也可以才采用指示第一会话与第二会话的下行流的方式，具体可参见图7。
如图7所示为本申请实施例提供的一种转发规则配置方法，该方法包括：
步骤701：第二终端设备向会话管理网元发送第二会话创建请求，第二会话请求用于请求创建第二会话以及指示第一会话与第二会话的下行流关联。
步骤702：会话管理网元接收到第二会话创建请求后，会话管理网元可以创建第二会话，在用户面网元中配置第一转发规则，第一转发规则指示通过第二会话转发来自第一会话的上行数据报文。与步骤502相同，具体可以参见步骤502的相关说明，此处不再赘述。
也就是说，会话管理网元可以触发用户面网元创建第一会话的第一转发规则，作为一种可能的实施方式，会话管理网元也可以触发用户面网元创建第二会话的第三转发规则，第三转发规则指示通过第二会话接收来自第一会话的上行数据报文。
会话管理网元在用户面网元中配置第一转发规则之后，会话管理网元可以向第二终端 发送第二会话创建响应，用于指示第二会话创建成功，也即建立了第一会话上行流与第二会话的关联。
若在数据转发时，从第二会话接收的上行数据需要通过第一会话转发，与如图5或图6所示的方式类似，第二终端设备可以向会话管理网元发送指示第一会话与第二会话上行流关联(或第一会话与第二会话关联)的第三会话创建请求，会话管理网元在接收到第三会话创建请求后，可以在用户面网元配置第二会话的第二转发规则，该第二转发规则指示通过第一会话转发来自所述第二会话的上行数据报文。
指示第一会话与第二会话上行流关联的方式以及指示第一会话与第二会话关联的方式与如图5或图6所示的实施例中指示第一会话上行流与第二会话关联的方式以及指示第一会话与第二会话关联的方式类似，区别在于此处携带的是第一会话的相关信息(如第一会话的标识、GTP-U标识等)。
会话管理网元在用户面网元配置第二会话的第二转发规则的方式与会话管理网元在用户面网元配置第一会话的第一转发规则的方式类似，具体可参见前述内容，此处不再赘述。
当然，第一会话与第二会话的上行流关联的另一种表述为第一会话的下行流与第二会话关联，故而也可以采用指示第一会话的下行流与第二会话的方式，也即第一终端设备可以向会话管理网元发送第四会话创建请求，第四会话创建请求用于请求创建第一会话以及指示第二会话与第一会话的下行流关联，以便会话管理网元在用户面网元创建第二会话的第二转发规则，作为一种可能的实施方式，会话管理网元也可以触发用户面网元创建第一会话的第四转发规则，第四转发规则指示通过第一会话接收来自第二会话的上行数据报文。
在上述实施例中，仅是以终端设备(第一终端设备和第二终端设备)发送会话创建请求(第一会话创建请求、第二会话创建请求、第三会话创建请求或第四会话创建请求)为例进行说明，事实上，终端设备也可以发送会话修改请求，通过会话修改请求告知会话管理网元第一会话与第二会话的关联关系。具体过程，与发送会话创建请求类似，此处不再赘述。
(2)、第一请求来自应用功能网元，第一请求为第一配置请求，用于配置第一会话。
步骤801：应用功能网元向会话管理网元发送第一配置请求，第一配置请求用于指示第一会话的上行流与第二会话关联或第一会话与第二会话关联。
第一终端设备和第二终端设备的会话均创建完成后，应用网元可以触发创建第一会话中的数据流，发送第一配置请求，对第一会话进行进一步配置。
第一配置请求指示第一会话的上行流与第二会话关联或第一会话与第二会话关联的方式与第一会话创建请求指示第一会话的上行流与第二会话关联或第一会话与第二会话关联的方式类似，具体可参见前述内容，此处不再赘述。
步骤802：会话管理网元接收到第一配置请求后，在用户面网元中配置第一转发规则，第一转发规则指示通过第二会话转发来自第一会话的上行数据报文。与步骤501相同，具体可以参见步骤501的相关说明，此处不再赘述。
为了在用户面网元配置第二转发规则，应用功能网元还可以发送第二配置请求。
步骤803：应用功能网元向会话管理网元发送第二配置请求，第二配置请求用于指示第为会话的上行流与第一会话关联或第一会话与第二会话关联。
第一终端设备和第二终端设备的会话均创建完成后，应用网元可以触发创建第二会话 中的数据流，发送第二配置请求，对第二会话进行进一步配置。
第二配置请求指示第二会话的上行流与第一会话关联或第一会话与第二会话关联的方式与第三会话创建请求指示第二会话的上行流与第一会话关联或第一会话与第二会话关联的方式类似，具体可参见前述内容，此处不再赘述。
步骤804：会话管理网元接收到第二配置请求后，在用户面网元中配置第二转发规则，第二转发规则指示通过第一会话转发来自第二会话的上行数据报文。具体可参见前述说明，此处不再赘述。
需要说明的是，若第一配置请求已指示第一会话与第二会话关联，也可以不执行步骤803～步骤804。
(二)、数据传输方法。
在用户面网元配置了第一转发规则，用户面网元可以根据第一转发规则或第二转发规则对进行数据转发，如图9所示为本申请实施例提供的一种数据传输方法，该方法包括：
步骤901：第一终端设备通过第一会话发送第一上行数据报文。
步骤902：用户面网元通过第一会话接收第一上行数据报文后，可以根据第一转发规则，通过第二会话转发第一上行数据报文。
步骤903：第二终端设备通过第二会话接收第一上行数据报文。
若第二会话的上行流与第二会话关联，也即用户面网元配置了第二转发规则，还可以执行如下步骤904～步骤906。
步骤904：第二终端设备通过第二会话发送第二上行数据报文。
步骤905：用户面网元通过第二会话接收第二上行数据报文后，可以根据第二转发规则，通过第一会话转发第二上行数据报文。
步骤906：第一终端设备通过第一会话接收第二上行数据报文。
通过上述第一上行数据报文的传输过程可以看出，用户面网元在接收到第一上行数据报文后，可以基于第一上行数据报文的来源(第一会话)，来确定所需转发该上行数据报文的会话，也即确定接收该上行数据报文的终端设备(第二终端设备)。
下面基于如图4b所示的网络架构对本申请实施例提供的一种转发规则配置方法以及数据传输方法进行进一步说明。
如图10所示，本申请实施例提供的一种转发规则配置方法以及数据传输方法，其中步骤1001～步骤1005为转发规则配置方法，步骤1006～步骤1017为数据传输方法。
步骤1001：UPF网元配置N6接口对应的会话为UE1的会话，以便UPF网元可以通过N6接口和UE1的会话直接进行数据报文的转发。N6接口与会话的对应关系可以是预先配置在UPF网元中的，UPF网元可以根据该对应关系配置N6接口对应的会话。
可选的，UE1也可以向SMF网元发送第五会话创建/修改请求，该第五会话创建/修改请求用于请求创建UE1的会话，第五会话创建/修改请求还可以指示UE1的会话所关联的数据网络名称(data network name，DNN)，该DNN所指示的DN与UPF网元的N6接口关联。
SMF网元在接收到第五会话创建/修改请求后，通知UPF网元创建UE1的会话，并配置N6接口对应的会话为UE1的会话。
步骤1001中实质上是配置从设备1与主设备之间的数据报文的转发规则，也即主设备通过UE1的会话将数据报文发送至UE1，这样从设备1可以从UE1获取该数据报文。
步骤1002：UE2向SMF网元发送第六会话创建/修改请求，该第六会话创建/修改请求用于请求创建UE2的会话，第六会话创建/修改请求还可以指示UE2的会话与UE3的会话关联。
本申请实施例并不限定第六会话创建/修改请求指示UE2的会话与UE3的会话关联的方式，例如第六会话创建/修改请求可以通过携带UE3的会话的标识指示UE2的会话与UE3的会话关联，也可以通过携带UE2和UE3所在群组的群组标识指示UE2的会话与UE3的会话关联，还可以通过携带预先约定的会话关联标识指示UE2的会话与UE3的会话关联。
步骤1003：SMF网元接收到第六会话创建/修改请求后，可以向UPF网元发送第一N4会话创建/修改请求，用于创建/修改UE2的会话的转发规则。该转发规则指示通过UE3的会话转发来自UE2的会话的上行数据报文。
该转发规则可以表现为如下中的任一种：
1、对于UE2会话的上行流，将通过UE2的会话接收的上行数据(也可以称为上行数据报文)发送到UE3的会话；对于UE2会话的下行流，在配置UE3的会话的转发规则时，配置将通过UE3的会话接收的上行数据发送到UE2的会话。该配置过程可以在创建/修改UE3的会话的转发规则时执行。
2、对于UE2会话的上行流，通过UE2的会话接收的上行数据后，将该上行数据发送到本地转发模块。
对于UE2会话的下行流，从本地转发模块匹配数据报文，也即匹配会话关联标识或UE3的会话的标识，并将匹配到的数据报文通过UE2的会话发送。
3、对于UE2会话的上行流，通过UE2的会话接收的上行数据后，在该上行数据中添加UE3的会话的GTP-U标识，之后发送到本地转发模块。
对于UE2会话的下行流，从本地转发模块匹配数据报文，也即匹配UE2的会话的GTP-U标识，并将匹配到的数据报文通过UE2的会话发送。
4、对应通过群组标识指示UE3的会话以及UE2的会话关联的方式，可以按现有群组管理的方式配置转发规则。也即通过UE2的会话接收的上行数据后，并将该上行数据发送到本地转发模块；以及从本地转发模块匹配属于同一群组的UE3的数据报文，并将匹配到的数据报文通过UE2的会话发送。
步骤1002～步骤1003中实质上是配置了与从设备1连接的UE1的会话的转发规则，也即从设备1可以通过UE2的会话将数据报文发送至UE3(也即从设备4)，还可以通过UE2的会话接收来自UE3的数据报文。
步骤1004：UE3发送第七会话创建/修改请求，该第七会话创建/修改请求用于请求创建/修改UE3的会话，第六会话创建/修改请求还可以指示UE2的会话与UE3的会话关联。指示的方法同步骤1002。
步骤1005：SMF网元向UPF网元发送第二N4会话创建/修改请求，用于创建/修改UE3的会话的转发规则。该转发规则指示通过UE2的会话转发来自UE3的会话的数据报文。
1、对于UE3会话的上行流，将通过UE3的会话接收的上行数据(也可以称为上行数据报文)发送到UE2的会话。
2、对于UE3会话的上行流，通过UE3的会话接收的上行数据后，将该上行数据发送 到本地转发模块。
对于UE3会话的下行流，从本地转发模块匹配数据报文，也即匹配会话关联标识或UE2的会话的标识，并将匹配到的数据报文通过UE3的会话发送。
3、对于UE3会话的上行流，通过UE3的会话接收的上行数据后，在该上行数据中添加UE2的会话的GTP-U标识，之后发送到本地转发模块。
对于UE3会话的下行流，从本地转发模块匹配数据报文，也即匹配UE3的会话的GTP-U标识，并将匹配到的数据报文通过UE3的会话发送。
4、对应通过群组标识指示UE3的会话以及UE2的会话关联的方式，可以按现有群组管理的方式配置转发规则。也即通过UE3的会话接收的上行数据后，并将该上行数据发送到本地转发模块；以及从本地转发模块匹配属于同一群组的UE2的数据报文，并将匹配到的数据报文通过UE3的会话发送。
步骤1004～1005中实质上是配置了与从设备4连接的UE3的会话的转发规则，也即从设备4可以通过UE3的会话将数据报文发送至UE2(也即从设备1)，还可以通过UE3的会话接收来自UE2的数据报文。
需要说明的是，在步骤1001～步骤1005中，是UE1～UE3向SMF网元发送会话创建/修改请求，指示会话之间的关联，作为一种可能的实施方式，指示会话之间(UE2的会话与UE3的会话)的关联的消息(也即第一请求)也可以是由AF网元发送给SMF网元的。例如，AF网元可以通过NEF网元将第一请求发送给PCF(或者AF网元也可以直接将第一请求发送到PCF网元)，之后PCF网元向SMF网元发送第一请求。又例如，AF网元通过NEF发送将第一请求发送给SMF网元(或者AF网元也可以直接将第一请求发送到SMF网元)。
前述步骤实现了转发规则的配置方式，下面对数据报文传输过程进行说明。
步骤1006：主设备向UPF网元发送第一报文。
步骤1007：UPF网元接收到第一报文后，根据N6侧接口和会话的对应关系，将第一报文转发到UE1的会话。
步骤1008：UE1接收第一报文后，将第一报文发送给从设备1。
步骤1009：从设备1接收到第一报文后，发送到从设备2、从设备3，之后第一报文被发回到从设备1。
从设备1、从设备2以及从设备3在接收到第一报文后，可以对第一报文进行处理。
步骤1010：从设备1通过UE2的会话将第一报文发送给UPF网元。也即从设备1将第一报文发送给UE2，UE2通过UE2的会话将第一报文发送给UPF网元。
步骤1011：UPF网元根据UE2的会话的转发规则，通过与UE2的会话关联的UE3的会话将第一报文发送到UE3。
步骤1012：UE3接收第一报文后，将第一报文发送给从设备4。
步骤1013：从设备4接收到第一报文后，读取该第一报文，通过UE3的会话将第一报文发回到UPF网元。也即从设备4将第一报文发送给UE3，UE3通过UE3的会话将第一报文发送给UPF网元。
步骤1014：UPF网元根据UE3的会话的转发规则，将第一报文发送到与UE3的会话关联的UE2的会话。也即UPF网元通过UE2的会话将第一报文发送给UE2。
步骤1015：UE2在将第一报文发送给从设备1。
步骤1016：从设备1从UE2接收到第一报文后，通过UE1的会话将第一报文发回到UPF网元。
步骤1017：UPF网元根据UE1的会话和N6接口的对应关系，将第一报文转发到主设备。
下面基于如图4c所示的网络架构对本申请实施例提供的一种转发规则配置方法以及数据传输方法进行进一步说明。
如图11所示，本申请实施例提供的一种转发规则配置方法以及数据传输方法，其中步骤1101～步骤1105为转发规则配置方法，步骤1106～步骤1114为数据传输方法。
步骤1101：UPF网元配置N6接口对应的会话，具体的，UPF配置N6接口的上行对应的会话为UE1的会话，N6接口的下行对应的会话为UE3的会话。
步骤1101中实质上是配置从设备1与主设备之间、以及从设备4与主设备之间的数据报文的转发规则，也即主设备通过UE1的会话将数据报文发送至UE1，这样从设备1可以从UE1获取该数据报文。主设备通过UE3的会话接收来自从设备4的数据报文。
步骤1102：UE1向SMF网元发送第八会话创建/修改请求，该第八会话创建/修改请求用于请求创建/修改UE1的会话，第八会话创建/修改请求还可以指示UE1的会话的上行流所关联的DNN以及UE1的会话的下行流与UE3的会话关联，其中，DNN所指示的DN与UPF网元的N6接口关联。
第八会话创建/修改请求指示UE1的会话的下行流与UE3的会话关联的方式与第六会话创建/修改请求还可以指示UE2的会话与UE3的会话关联的方式类似，也即第八会话创建/修改请求可以通过携带UE3的会话的标识、携带UE1和UE3所在群组的群组标识或预先约定的会话关联标识指示UE1的会话的下行流与UE3的会话关联。
步骤1103：SMF网元接收到第八会话创建/修改请求后，可以向UPF网元发送第三N4会话创建/修改请求，用于创建/修改UE1的会话上行流的转发规则以及下行流的转发规则。该转发规则指示通过UE3的会话转发来自UE2的会话的数据报文。
UE1的会话上行流的转发规则指示将通过UE1的会话接收的上行数据发送到UE3的会话。UE1的会话上行流的转发规则的配置方式与如图10中UE2的会话上行流的转发规则类似，具体可以参见前述内容，此处不再赘述。
UE1的会话下行流的转发规则指示从DNN对应的N6接口接收数据报文。
步骤1104：UE3向SMF网元发送第九会话创建/修改请求，该第九会话创建/修改请求用于请求创建/修改UE3的会话，第九会话创建/修改请求还可以指示UE3的会话的上行流所关联的DNN以及UE3的会话的下行流与UE1的会话关联，其中，DNN所指示的DN与UPF网元的N6接口关联。
第九会话创建/修改请求UE3的会话的下行流与UE1的会话关联可以通过携带UE1的会话的标识、携带UE1和UE3所在群组的群组标识或预先约定的会话关联标识指示UE1的会话的下行流与UE3的会话关联。
步骤1105：SMF网元接收到第九会话创建/修改请求后，可以向UPF网元发送第四N4会话创建/修改请求，用于创建/修改UE3的会话上行流的转发规则以及下行流的转发规则。
UE3的会话下行流的转发规则指示将通过UE1的会话接收的上行数据发送到UE3的会话。UE3的会话下行流的转发规则的配置方式与如图10中UE2的会话下行流的转发规 则类似，具体可以参见前述内容，此处不再赘述。
UE3的会话上行流的转发规则指示向DNN对应的N6接口发送数据报文。
步骤1102～步骤1105中实质上是配置从设备1与主设备之间、以及从设备1与从设备4之间的数据报文的转发规则，也即主设备通过UE1的会话将数据报文发送至UE1，这样从设备1可以从UE1获取该数据报文。从设备1通过UE1的会话将数据报文发送至UE3，从设备4接收到该数据报文，将该数据报文通过UE3的会话发送至住设备。
需要说明的是，若步骤1102中第八会话创建/修改请求指示了UE1会话的下行流所关联的DNN以及步骤1104中第九会话创建/修改请求指示了UE3会话的上行流所关联的DNN，也可以不执行步骤1101。
前述步骤实现了转发规则的配置方式，下面对数据报文传输过程进行说明。
步骤1106：主设备向UPF网元发送第二报文。
步骤1107：UPF网元接收到第二报文后，根据N6侧接口和UE1会话下行流的对应关系，将第二报文转发到UE1的会话。也即将第二报文发送给UE1。
步骤1108：UE1接收第二报文后，将第二报文发送给从设备1。
步骤1109：从设备1接收到第二报文后，发送到后续从设备2、从设备3对第二报文进行处理，之后处理后的第二报文被发回到从设备1。
步骤1110：从设备1通过UE1的会话将处理后的第二报文发送给UPF网元。
步骤1111：UPF网元根据UE1的会话上行流的转发规则，将处理后的第二报文发送到UE3的会话。也即将第二报文发送给UE3。
步骤1112：UE3接收处理后的第二报文后，将处理后的第二报文发送给从设备4。
步骤1113：从设备4接收到处理后的第二报文后，再次处理该处理后的第二报文(为方便说明，这里用第二处理报文表示从设备4处理后的第二报文)，通过UE3的会话将处理后的第二处理报文发回到UPF网元。
步骤1114：UPF根据UE3的会话上行流和N6接口的对应关系，将第二处理报文转发到主设备。
下面基于如图4c所示的网络架构对本申请实施例提供的一种转发规则配置方法以及数据传输方法进行进一步说明。
如图12所示，本申请实施例提供的一种转发规则配置方法以及数据传输方法，其中步骤1201～步骤1205为转发规则配置方法，步骤1206～步骤1224为数据传输方法。
步骤1201：与步骤1101相同，具体可参见前述说明，此处不再赘述。
步骤1202：与步骤1102相同，具体可参见前述说明，此处不再赘述。
需要说明的是，第八会话创建/修改请求还可以指示与UE1关联的从设备的地址。本申请实施例并不限定指示从设备1的地址的方式，下面列举两种方式：
方式一、对于从设备利用自增量地址寻址的方式。
第八会话创建/修改请求中包括与UE1关联的从设备的自增量地址的起始序号，可选的，还可以指示与UE1关联的从设备(从设备1、从设备2以及从设备3)的数量。在本申请实施例中与UE1关联的从设备的数量为3。
与UE1关联的从设备的自增量地址的起始序号为从设备1的子增量地址的序号，由于从设备1在各个从设备中为第一个接收到EtherCAT报文的从设备，故而第八会话创建/修改请求携带的起始序号为0。
方式二、对于从设备利用固定地址或逻辑地址的方式。
第八会话创建/修改请求中包括与UE1关联的从设备的固定地址或逻辑地址。
步骤1203：与步骤1103相同，具体可参见前述说明，此处不再赘述。
需要说明的是，在该步骤中SMF网元还可以向UPF网元发送与UE1关联的从设备的自增量地址的起始序号、固定地址或逻辑地址。也就是说第三N4会话创建/修改请求中还可以携带UPF网元发送与UE1关联的从设备的自增量地址的起始序号、固定地址或逻辑地址。
步骤1204：与步骤1104相同，具体可参见前述说明，此处不再赘述。
需要说明的是，第九会话创建/修改请求还可以指示与UE3关联的从设备的地址。本申请实施例并不限定指示从设备4的地址的方式，下面列举两种方式：
方式一、对于从设备利用自增量地址寻址的方式。
第九会话创建/修改请求中包括与UE3关联的从设备的自增量地址的起始序号，可选的，还可以指示与UE3关联的从设备(从设备4)的数量。在本申请实施例中与UE3关联的从设备的数量为1。
与UE3关联的从设备的自增量地址的起始序号为从设备4的子增量地址的序号，由于从设备4在各个从设备中为第四个接收到EtherCAT报文的从设备，故而第九会话创建/修改请求携带的起始序号为3。
方式二、对于从设备利用固定地址或逻辑地址的方式。
第九会话创建/修改请求中包括与UE3关联的从设备的固定地址或逻辑地址。
步骤1205：与步骤1105相同，具体可参见前述说明，此处不再赘述。
需要说明的是，在该步骤中SMF网元还可以向UPF网元发送与UE3关联的从设备的自增量地址的起始序号、固定地址或逻辑地址。也就是说第四N4会话创建/修改请求中还可以携带UPF网元发送与UE3关联的从设备的自增量地址的起始序号、固定地址或逻辑地址。
下面对从设备采用自增量地址寻址的方式确定子报文时，UPF网元对数据报文的转发过程。
步骤1206：UPF网元从DNN所对应的N6接口接收来自主设备的第三报文。
步骤1207：UPF网元根据与UE1关联的从设备的自增量地址的起始序号，确定第三报文中的第一子报文，将确定第一子报文转发到UE1的会话。这里不限定第一子报文的数量，可以是一个，也可以是多个。
由于与UE1关联的从设备的自增量地址的起始序号为0，UPF网元可以提取第三报文中将从设备的自增量地址排序在0以及0之后的子报文，将提取的子报文封装，通过UE1的会话转发封装后的子报文。这里提前的子报文也可以包括第三报文中所有子报文，也就可以直接转发该第三报文。
可选的，UPF根据与UE1关联的从设备的数量以及自增量地址的起始序号提取第三报文中从设备1、从设备2以及从设备3对应的三个子报文，封装该三个子报文，将封装后的字报文转发到UE1的会话。
需要说明的是，通过在从设备在进行自增量地址寻址时，EtherCAT网络可以为各个从设备分配固定地址，UPF网元可以记录各个从设备的固定地址，以便后续进行数据报文的转发。作为一种可能的实施方式，UPF网元所保存的各个从设备的固定地址，也可以是 UE1以及UE3(或AF网元)将所关联的从设备的固定地址发送给SMF网元后，SMF网元发送给UPF网元。
步骤1208：UPF网元通过UE1的会话将第一子报文发送给UE1。
步骤1209：UE1接收第一子报文后，将第一子报文发送给从设备1。
步骤1210：从设备1接收到第一子报文后，对第一子报文进行处理，并将处理后的第一子报文发送到后续从设备2、从设备3，为方便说明，这里用第一处理子报文表示从设备3处理后的第一子报文)，之后第一处理子报文被发回到从设备1。
步骤1211：从设备1通过UE1的会话将第一处理子报文发送给UPF网元。
步骤1212：UPF网元根据与UE3关联的从设备的子增量地址的起始序号，确定与UE3关联的从设备对应的第二子报文，将提取的第二子报文封装后，通过UE3的会话发送封装后的第二子报文。
可选的，UPF网元将第三报文中各子报文中的自增量地址的地址加3后发送到会话3，发送到UE3的会话。
步骤1213：UE3接收封装后的第二子报文后，将第二子报文发送给从设备4。
步骤1214：从设备4接收到第二子报文后，该处理后的第二子报文(为方便说明，这里用第二处理子报文表示从设备4处理后的第二报文)，通过UE3的会话将处理后的第二处理子报文发回到UPF网元。
步骤1215：UPF网元接收到第一处理子报文以及第二处理子报文后，将第一处理子报文以及第二处理子报文合并到同一报文后，通过UE3的会话的上行流关联的N6接口将该报文发送到主设备。
UPF网元可以识别子报文是否经过处理，以便可以将处理后的子报文发送给从设备。下面列举两种识别方式。
1.UPF保存第三报文，之后在接收到第一处理子报文以及第二处理子报文后，比对第三报文第一子报文和第二子报文与第一处理子报文以及第二处理子报文，根据比对结果确定第一子报文和第二子报文是否发生修改，将发生修改的子报文替换第三报文中对应的字报文，将替换了子报文的第三报文发送给主设备。
2.第三报文中的各个子报文包括读写标识，若从设备对子报文进行修改，则可以变更该读写标识，变更后的读写标识可以指示该子报文发生了修改。
UPF网元可以在接收到第一处理子报文以及第二处理子报文后，根据子报文中的读写标识确定子报文是否发生修改，进一步的将发生修改的子报文合并在一个报文中，将该报文发送给主设备。
下面对从设备采用固定地址或逻辑地址寻址的方式确定子报文时，UPF网元对数据报文的转发过程。
步骤1216：UPF网元从DNN所对应的N6接口接收来自主设备的第四报文。
步骤1217：UPF网元根据N6侧接口所关联的UE1的会话发送第四报文。
可选的，UPF网元可以根据与UE1所关联的从设备的固定地址(或逻辑地址)提取第三子报文，将确定第三子报文转发到UE1的会话。这里不限定第三子报文的数量，可以是一个，也可以是多个。
步骤1218：UE1接收第三子报文后，将第三子报文发送给从设备1。
步骤1219：从设备1接收到第三子报文后，对第三子报文进行处理，并将处理后的第 三子报文发送到后续从设备2、从设备3，为方便说明，这里用第三处理子报文表示从设备3处理后的第三子报文)，之后第三处理子报文被发回到从设备1。
步骤1220：从设备1通过UE1的会话将第三处理子报文发送给UPF网元。
步骤1221：UPF网元根据N6侧接口所关联的UE4的会话发送第四报文。
可选的，UPF根据与UE3所关联的从设备的固定地址(或逻辑地址)提取第四子报文，将确定第四子报文转发到UE3的会话。这里不限定第四子报文的数量，可以是一个，也可以是多个。
步骤1222：UE3接收封装后的第四子报文后，将第四子报文发送给从设备4。
步骤1223：从设备4接收到第四子报文后，该处理后的第四子报文(为方便说明，这里用第四处理子报文表示从设备4处理后的第四子报文)，通过UE3的会话将处理后的第四处理子报文发回到UPF网元。
步骤1224：UPF网元接收到第一处理子报文以及第四处理子报文后，将第一处理子报文以及第四处理子报文合并到同一报文后，通过UE3的会话的上行流关联的N6接口将该报文发送到主设备。
基于与方法实施例同一发明构思，本申请实施例还提供了一种通信装置，用于执行上述如图5～图12所示的方法实施例中所述UPF网元执行的方法，相关特征可参见上述方法实施例，此处不再赘述，如图13所示，为本申请提供的一种通信装置，所述装置包括接收单元1301以及发送单元1302。
接收单元1301，用于通过第一会话接收第一上行数据报文；
发送单元1302，用于根据第一转发规则，通过第二会话转发第一上行数据报文，其中，第一转发规则指示通过第二会话转发来自第一会话的上行数据报文。
在一种可能的实施方式中，接收单元1301，还用于通过第二会话接收第二上行数据报文；
发送单元1302，还用于根据第二转发规则，通过第一会话转发第二上行数据报文，其中，第二转发规则指示通过第一会话转发来自第二会话的上行数据报文。
在一种可能的实施方式中，接收单元1301在发送单元1302通过第一会话接收第一上行数据报文之前，从会话管理网元接收第一转发规则。
在一种可能的实施方式中，接收单元1301在发送单元通过第二会话接收第二上行数据报文之前，从会话管理网元接收第二转发规则。
在一种可能的实施方式中，第一转发规则为第一会话的转发规则，第一转发规则包括下列的部分或全部：
第二会话的标识、会话关联标识、或第二会话的GTP-U标识，其中，会话关联标识指示第一会话与第二会话关联。
在一种可能的实施方式中，第二转发规则为第二会话的转发规则，第二转发规则包括下列的部分或全部：
第一会话的标识、会话关联标识、或第一会话的GTP-U标识，其中，会话关联标识指示第一会话与第二会话关联。
基于与方法实施例同一发明构思，本申请实施例还提供了一种通信装置，用于执行上述如图5～图12所示的方法实施例中SMF网元执行的方法，相关特征可参见上述方法实施例，此处不再赘述，如图14所示，为本申请提供的一种通信装置，装置包括接收单元1401 以及处理单元1402。
接收单元1401，用于接收第一请求，第一请求用于指示第一会话的上行流与第二会话关联；
处理单元1402，用于在用户面网元中配置第一转发规则，第一转发规则指示通过第二会话转发来自第一会话的上行数据报文。
在一种可能的实施方式中，接收单元1401接收第一请求以及第一请求的类型有如下几种：
从第一终端设备接收第一会话创建(或修改)请求，第一会话创建(或修改)请求用于请求创建(或修改)第一会话，以及指示第一会话的上行流与第二会话关联。
从第一终端设备接收第一会话创建(或修改)请求，第一会话创建(或修改)请求还用于指示第一会话的上行流与第二会话关联或第一会话与第二会话关联。
从第二终端设备接收第二会话创建(或修改)请求，第二会话创建请求用于请求创建第二会话以及指示第一会话与第二会话的下行流关联。
从应用功能网元接收第一配置请求，第一配置请求用于配置第一会话，第一配置请求还用于指示第一会话的上行流与第二会话关联或第一会话与第二会话关联。
在一种可能的实施方式中，接收单元1401还可以于接收第二请求，第二请求用于请求创建第二会话以及指示第二会话的上行流与第一会话关联；
处理单元1402可以在用户面网元中配置第二转发规则，第二转发规则指示通过第一会话转发来自第二会话的上行数据报文。
在一种可能的实施方式中，接收单元1401接收第二请求以及第二请求的类型有如下几种：
从第二终端设备接收第三会话创建(或修改)请求，第三会话创建(或修改)请求用于请求创建第二会话以及指示第二会话的上行流与第一会话关联，第三会话创建请求还用于指示第二会话的上行流与第一会话关联或第一会话与第二会话关联。
从应用功能网元接收第二配置请求，第二配置请求用于配置第二会话，第二配置请求还用于指示第二会话的上行流与第一会话关联或第一会话与第二会话关联。
在一种可能的实施方式中，第一会话创建(或修改)请求以及第一配置请求包括下列中的部分或全部：第二会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联；
第二会话创建(或修改)请求包括下列中的部分或全部：
第一会话的标识或会话关联标识。
在一种可能的实施方式中，第三会话创建(或修改)请求以及第二配置请求包括下列中的部分或全部：第一会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联。
在一种可能的实施方式中，第一转发规则为第一会话的转发规则，第一转发规则包括下列的部分或全部：
第二会话的标识、会话关联标识、或第二会话的GTP-U标识，其中，会话关联标识指示第一会话与第二会话关联。
在一种可能的实施方式中，第二转发规则为第二会话的转发规则，第二转发规则包括下列的部分或全部：
第一会话的标识、会话关联标识、或第一会话的GTP-U标识，其中，会话关联标识指示第一会话与第二会话关联。
基于与方法实施例同一发明构思，本申请实施例还提供了一种通信装置，用于执行上述如图5～图12所示的方法实施例中第一终端设备或UE2执行的方法，相关特征可参见上述方法实施例，此处不再赘述，如图15所示，为本申请提供的一种通信装置，装置包括发送单元1501以及接收单元1502。
发送单元1501，用于向会话管理网元发送第一会话创建(或修改)请求，第一会话创建(或修改)请求用于请求创建(或修改)第一会话，第一会话创建(或修改)请求还用于指示第一会话的上行流与第二会话关联或第一会话与第二会话关联；
接收单元1502，用于从会话管理网元接收第一会话创建(或修改)响应，第一会话创建(或修改)响应指示第一会话创建(或修改)成功；
发送单元1501，还用于在接收单元接收到第一会话创建(或修改)响应后，通过第一会话发送第一上行数据报文。
在一种可能的实施方式中，第一会话创建请求包括第二会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联。
基于与方法实施例同一发明构思，本申请实施例还提供了一种通信装置，用于执行上述如图7～图12所示的方法实施例中第二终端设备执行的方法，相关特征可参见上述方法实施例，此处不再赘述，如图16所示，为本申请提供的一种通信装置，装置包括发送单元1601以及接收单元1602。
发送单元1601，用于向会话管理网元发送第二会话创建(或修改)请求，第二会话创建请求用于请求创建第二会话以及指示第二会话的下行流与第一会话关联；
接收单元1602，用于从会话管理网元接收第二会话创建(或修改)响应，第三会话创建响应指示第二会话创建成功；
发送单元1601，还用于在接收单元接收到第二会话创建(或修改)响应后，通过第二会话接收第一上行数据报文。
在一种可能的实施方式中，第二会话请求包括第一会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联。
基于与方法实施例同一发明构思，本申请实施例还提供了一种通信装置，用于执行上述法实施例中第二终端设备执行的方法，相关特征可参见上述方法实施例，此处不再赘述，如图17所示，为本申请提供的一种通信装置，装置包括发送单元1701以及接收单元1702：
发送单元1701，用于向会话管理网元发送第三会话创建(或修改)请求，第三会话请求用于请求创建(或修改)第二会话，第三会话创建请求还用于指示第二会话的上行流与第一会话关联或第一会话与第二会话关联；
接收单元1702，用于从会话管理网元接收第三会话创建(或修改)响应，第三会话创建(或修改)响应指示第二会话创建(或修改)成功；
发送单元1701，还用于在接收单元接收到第三会话创建(或修改)响应后，通过第二会话发送第二上行数据报文。
在一种可能的实施方式中，第三会话创建(或修改)请求包括第一会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联。可选的，第三会话创建(或修改)请求还可以携带的上行流的指示信息，如会话的流向信息。
基于与方法实施例同一发明构思，本申请实施例还提供了一种通信装置，用于执行上述如图8～图12所示的方法实施例中第二终端设备或UE3执行的方法，相关特征可参见上述方法实施例，此处不再赘述，如图17所示，为本申请提供的一种通信装置，装置包括发送单元1701以及接收单元1702。
发送单元1701，用于向会话管理网元发送第三会话创建(或修改)请求，第三会话创建(或修改)请求用于请求创建(或修改)第二会话第三会话创建(或修改)请求还用于指示第二会话的上行流与第一会话关联或第一会话与第二会话关联；
接收单元1702，用于从会话管理网元接收第三会话创建(或修改)响应，第三会话创建(或修改)响应指示第二会话创建(或修改)成功；
发送单元1701，用于在接收单元接收到第三会话创建(或修改)响应后，通过第二会话发送第二上行数据报文。
在一种可能的实施方式中，第三会话创建(或修改)请求包括第一会话的标识或会话关联标识，会话关联标识指示第一会话与第二会话关联。
本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能单元可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个模块中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
该集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台终端设备(可以是个人计算机，手机，或者网络设备等)或处理器(processor)执行本申请各个实施例该方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
在本申请实施例中，所述会话管理网元以及用户面网元、所述第一终端设备以及第二终端设备均可以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
在一个简单的实施例中，本领域的技术人员可以想到所述会话管理网元以及用户面网元功能可采用图18所示的形式。
如图18所示的通信装置1800，包括至少一个处理器1801、存储器1802，可选的，还可以包括通信接口1803。
处理器1801可以为中央处理器，存储器1802可以是易失性存储器，例如随机存取存储器；存储器也可以是非易失性存储器，例如只读存储器，快闪存储器，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)、或者存储器1802是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器1802可以是上述存储器的组合。
本申请实施例中不限定上述处理器1801以及存储器1802之间的具体连接介质。本申请实施例在图中以存储器1802和处理器1801之间通过总线1804连接，总线1804在图中 以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。该总线1804可以分为地址总线、数据总线、控制总线等。为便于表示，图18中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
处理器1801可以具有数据收发功能，能够与其他设备进行通信，在如图18装置中，也可以设置独立的数据收发模块，例如通信接口1803，用于收发数据；处理器1801在与其他设备进行通信时，可以通过通信接口1803进行数据传输。
当所述用户面网元采用图18所示的形式时，图18中的处理器1801可以通过调用存储器1802中存储的计算机执行指令，使得所述用户面网元可以执行上述任一方法实施例中的所述用户面网元执行的方法。
具体的，图13中的接收单元和发送单元的功能/实现过程均可以通过图18中的处理器1801调用存储器1802中存储的计算机执行指令来实现。图14的接收单元和发送单元的功能/实现过程可以通过图18中的通信接口1803来实现。
当所述会话管理网元采用图18所示的形式时，图18中的处理器1801可以通过调用存储器1802中存储的计算机执行指令，使得所述会话管理网元可以执行上述任一方法实施例中的所述会话管理网元执行的方法。
具体的，图14中的接收单元和处理单元的功能/实现过程均可以通过图18中的处理器1801调用存储器1802中存储的计算机执行指令来实现。或者，图14中的处理单元的功能/实现过程可以通过图18中的处理器1801调用存储器1802中存储的计算机执行指令来实现，图14的接收单元的功能/实现过程可以通过图18中的通信接口1803来实现。
在一个简单的实施例中，本领域的技术人员可以想到所述第一终端设备、以及第二终端设备功能可采用图19所示的形式。
如图19所示的通信装置1900，包括至少一个处理器1901、存储器1902，可选的，还可以包括收发器1903。
处理器1901和存储器1902与处理器1801和存储器1802类似，具体可以参见前述说明，此处不再赘述。
本申请实施例中不限定上述处理器1901以及存储器1902之间的具体连接介质。本申请实施例在图中以存储器1902和处理器1901之间通过总线1904连接，总线1904在图中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。该总线1904可以分为地址总线、数据总线、控制总线等。为便于表示，图19中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
处理器1901可以具有数据收发功能，能够与其他设备进行通信，在如图19装置中，也可以设置独立的数据收发模块，例如收发器1903，用于收发数据；处理器1901在与其他设备进行通信时，可以通过收发器1903进行数据传输。
当所述第一终端设备采用图19所示的形式时，图19中的处理器1901可以通过调用存储器1902中存储的计算机执行指令，使得所述第一终端设备可以执行上述任一方法实施例中的所述第一终端设备执行的方法。
具体的，图15中的发送单元、接收单元的功能/实现过程均可以通过图19中的处理器1901调用存储器1902中存储的计算机执行指令来实现。图15、图16的发送单元和接收单元的功能/实现过程可以通过图19中的收发器1903来实现。
当所述第二终端设备采用图19所示的形式时，图19中的处理器1901可以通过调用 存储器1902中存储的计算机执行指令，使得所述第二终端设备可以执行上述任一方法实施例中的所述第二终端设备执行的方法。
具体的，图16、图17中的发送单元、接收单元的功能/实现过程均可以通过图19中的处理器1901调用存储器1902中存储的计算机执行指令来实现。图16、图17以及的发送单元和接收单元的功能/实现过程可以通过图19中的收发器1903来实现。
本领域内的技术人员应明白，本申请的实施例可提供为方法、***、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (53)

  1. 一种通信方法，其特征在于，所述方法包括：
    用户面网元通过第一会话接收第一上行数据报文；
    所述用户面网元根据第一转发规则，通过第二会话转发所述第一上行数据报文，其中，所述第一转发规则指示通过第二会话转发来自所述第一会话的上行数据报文。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    用户面网元通过所述第二会话接收第二上行数据报文；
    所述用户面网元根据第二转发规则，通过所述第一会话转发所述第二上行数据报文，其中，所述第二转发规则指示通过第一会话转发来自所述第二会话的上行数据报文。
  3. 如权利要求1或2所述的方法，其特征在于，所述用户面网元通过第一会话接收第一上行数据报文之前，还包括：
    所述用户面网元从会话管理网元接收所述第一转发规则。
  4. 如权利要求1或2所述的方法，其特征在于，所述用户面网元通过第二会话接收第二上行数据报文之前，还包括：
    所述用户面网元从会话管理网元接收所述第二转发规则。
  5. 如权利要求1～3任一所述的方法，其特征在于，所述第一转发规则为所述第一会话的转发规则，所述第一转发规则包括下列的部分或全部：
    所述第二会话的标识、会话关联标识、或所述第二会话的通用无线分组业务隧道协议用户面GTP-U标识，其中，所述会话关联标识指示所述第一会话与所述第二会话关联。
  6. 如权利要求2～5任一所述的方法，其特征在于，所述第二转发规则为所述第二会话的转发规则，所述第二转发规则包括下列的部分或全部：
    所述第一会话的标识、会话关联标识、或所述第一会话的通用无线分组业务隧道协议用户面GTP-U标识，其中，所述会话关联标识指示所述第一会话与所述第二会话关联。
  7. 一种通信方法，其特征在于，所述方法包括：
    向会话管理网元发送第一会话创建请求，所述第一会话创建请求用于请求创建第一会话，所述第一会话创建请求还用于指示所述第一会话的上行流与第二会话关联或所述第一会话与第二会话关联；
    在从所述会话管理网元接收第一会话创建响应后，通过所述第一会话发送第一上行数据报文，所述第一会话创建响应指示所述第一会话创建成功。
  8. 如权利要求7所述的方法，其特征在于，所述第一会话创建请求包括所述第二会话的标识或会话关联标识，所述会话关联标识指示所述第一会话与所述第二会话关联。
  9. 一种通信方法，其特征在于，所述方法包括：
    向会话管理网元发送第二会话创建请求，所述第二会话创建请求用于请求创建第二会话以及指示所述第二会话的下行流与第一会话关联；
    在从所述会话管理网元接收到第二会话创建响应后，通过所述第二会话接收第一上行数据报文，所述第二会话创建响应指示所述第二会话创建成功。
  10. 如权利要求9所述的方法，其特征在于，所述第二会话创建请求包括所述第一会话的标识或会话关联标识，所述会话关联标识指示所述第一会话与所述第二会话关联。
  11. 一种通信方法，其特征在于，所述方法包括：
    向会话管理网元发送第三会话创建请求，所述第三会话创建请求用于请求创建第二会话，所述第三会话创建请求还用于指示所述第二会话的上行流与第一会话关联或所述第一会话与所述第二会话关联；
    从所述会话管理网元接收第三会话创建响应，所述第三会话创建响应指示所述第二会话创建成功。
  12. 如权利要求11所述的方法，其特征在于，所述第三会话创建请求包括所述第一会话的标识或会话关联标识，所述会话关联标识指示所述第一会话与所述第二会话关联。
  13. 一种通信方法，其特征在于，所述方法包括：
    会话管理网元接收第一请求，所述第一请求用于指示所述第一会话的上行流与第二会话关联；
    所述会话管理网元在用户面网元中配置第一转发规则，所述第一转发规则指示通过第二会话转发来自所述第一会话的上行数据报文。
  14. 如权利要求13所述的方法，其特征在于，所述会话管理网元接收第一请求，包括：
    所述会话管理网元从第一终端设备接收第一会话创建请求，所述第一会话创建请求用于请求创建第一会话，所述第一会话创建请求还用于指示所述第一会话的上行流与第二会话关联或所述第一会话与第二会话关联；或
    所述会话管理网元从第二终端设备接收第二会话创建请求，所述第二会话创建请求用于请求创建第二会话以及指示所述第一会话与第二会话的下行流关联；或
    所述会话管理网元从应用功能网元接收第一配置请求，所述第一配置请求用于配置所述第一会话，所述第一配置请求还用于指示所述第一会话的上行流与第二会话关联或所述第一会话与第二会话关联。
  15. 如权利要求13或14所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元接收第二请求，所述第二请求用于请求创建第二会话以及指示所述第二会话的上行流与第一会话关联；
    所述会话管理网元在所述用户面网元中配置第二转发规则，所述第二转发规则指示通过第一会话转发来自所述第二会话的上行数据报文。
  16. 如权利要求15所述的方法，其特征在于，所述会话管理网元接收第二请求，包括：
    所述会话管理网元从第二终端设备接收第三会话创建请求，所述第三会话创建请求用于请求创建第二会话，所述第三会话创建请求还用于指示所述第二会话的上行流与第一会话关联或所述第一会话与第二会话关联；或
    所述会话管理网元从应用功能网元接收第二配置请求，所述第二配置请求用于配置所述第二会话，所述第二配置请求还用于指示所述第二会话的上行流与第一会话关联或所述第一会话与第二会话关联。
  17. 如权利要求13或14所述的方法，其特征在于，所述第一会话创建请求以及所述第一配置请求包括下列中的部分或全部：
    所述第二会话的标识或会话关联标识，所述会话关联标识指示所述第一会话与所述第二会话关联；
    所述第二会话创建请求包括下列中的部分或全部：
    所述第一会话的标识或所述会话关联标识。
  18. 如权利要求15或16所述的方法，其特征在于，所述第三会话创建请求以及所述第 二配置请求包括下列中的部分或全部：
    所述第一会话的标识或会话关联标识，所述会话关联标识指示所述第一会话与所述第二会话关联。
  19. 如权利要求13～17任一所述的方法，其特征在于，所述第一转发规则为所述第一会话的转发规则，所述第一转发规则包括下列的部分或全部：
    所述第二会话的标识、会话关联标识、或所述第二会话的通用无线分组业务隧道协议用户面GTP-U标识，其中，所述会话关联标识指示所述第一会话与所述第二会话关联。
  20. 如权利要求14～18任一所述的方法，其特征在于，所述第二转发规则为所述第二会话的转发规则，所述第二转发规则包括下列的部分或全部：
    所述第一会话的标识、会话关联标识、或所述第一会话的通用无线分组业务隧道协议用户面GTP-U标识，其中，所述会话关联标识指示所述第一会话与所述第二会话关联。
  21. 一种通信装置，其特征在于，所述装置包括接收单元以及发送单元：
    所述接收单元，用于通过第一会话接收第一上行数据报文；
    所述发送单元，用于根据第一转发规则，通过第二会话转发所述第一上行数据报文，其中，所述第一转发规则指示通过第二会话转发来自所述第一会话的上行数据报文。
  22. 如权利要求21所述的装置，其特征在于，
    所述接收单元，还用于通过所述第二会话接收第二上行数据报文；
    所述发送单元，还用于根据第二转发规则，通过所述第一会话转发所述第二上行数据报文，其中，所述第二转发规则指示通过第一会话转发来自所述第二会话的上行数据报文。
  23. 如权利要求21或22所述的装置，其特征在于，所述接收单元在所述发送单元通过第一会话接收第一上行数据报文之前，还用于：
    从会话管理网元接收所述第一转发规则。
  24. 如权利要求21或22所述的装置，其特征在于，所述接收单元在所述发送单元通过第二会话接收第二上行数据报文之前，还用于：
    从会话管理网元接收所述第二转发规则。
  25. 如权利要求21～24任一所述的装置，其特征在于，所述第一转发规则为所述第一会话的转发规则，所述第一转发规则包括下列的部分或全部：
    所述第二会话的标识、会话关联标识、或所述第二会话的通用无线分组业务隧道协议用户面GTP-U标识，其中，所述会话关联标识指示所述第一会话与所述第二会话关联。
  26. 如权利要求21～24任一所述的装置，其特征在于，所述第二转发规则为所述第二会话的转发规则，所述第二转发规则包括下列的部分或全部：
    所述第一会话的标识、会话关联标识、或所述第一会话的通用无线分组业务隧道协议用户面GTP-U标识，其中，所述会话关联标识指示所述第一会话与所述第二会话关联。
  27. 一种通信装置，其特征在于，所述装置包括发送单元以及接收单元：
    所述发送单元，用于向会话管理网元发送第一会话创建请求，所述第一会话创建请求用于请求创建第一会话，所述第一会话创建请求还用于指示所述第一会话的上行流与第二会话关联或所述第一会话与第二会话关联；
    所述接收单元，用于从所述会话管理网元接收第一会话创建响应，所述第一会话创建响应指示所述第一会话创建成功；
    所述发送单元，还用于在所述接收单元接收到第一会话创建响应后，通过所述第一会 话发送第一上行数据报文。
  28. 如权利要求27所述的装置，其特征在于，所述第一会话创建请求包括所述第二会话的标识或会话关联标识，所述会话关联标识指示所述第一会话与所述第二会话关联。
  29. 一种通信装置，其特征在于，所述装置包括发送单元以及接收单元：
    所述发送单元，用于向会话管理网元发送第二会话创建请求，所述第二会话创建请求用于请求创建第二会话以及指示所述第二会话的下行流与第一会话关联；
    所述接收单元，用于从所述会话管理网元接收第二会话创建响应，所述第二会话创建响应指示所述第二会话创建成功；
    所述发送单元，还用于在所述接收单元接收到所述第二会话创建响应后，通过所述第二会话接收第一上行数据报文。
  30. 如权利要求29所述的装置，其特征在于，所述第二会话创建请求包括所述第一会话的标识或会话关联标识，所述会话关联标识指示所述第一会话与所述第二会话关联。
  31. 一种通信装置，其特征在于，所述装置包括发送单元以及接收单元：
    所述发送单元，用于向会话管理网元发送第三会话创建请求，所述第三会话创建请求用于请求创建第二会话，所述第三会话创建请求还用于指示所述第二会话的上行流与第一会话关联或所述第一会话与所述第二会话关联；
    所述接收单元，用于从所述会话管理网元接收第三会话创建响应，所述第三会话创建响应指示所述第二会话创建成功。
  32. 如权利要求31所述的装置，其特征在于，所述第三会话创建请求包括所述第一会话的标识或会话关联标识，所述会话关联标识指示所述第一会话与所述第二会话关联。
  33. 一种通信装置，其特征在于，所述装置包括接收单元以及处理单元：
    所述接收单元，用于接收第一请求，所述第一请求用于指示所述第一会话的上行流与第二会话关联；
    所述处理单元，用于在用户面网元中配置第一转发规则，所述第一转发规则指示通过第二会话转发来自所述第一会话的上行数据报文。
  34. 如权利要求33所述的装置，其特征在于，所述接收单元在接收第一请求时，具体用于：
    从第一终端设备接收第一会话创建请求，所述第一会话创建请求用于请求创建第一会话以及指示所述第一会话的上行流与第二会话关联，所述第一会话创建请求还用于指示所述第一会话的上行流与第二会话关联或所述第一会话与第二会话关联；或
    从第二终端设备接收第二会话创建请求，所述第二会话创建请求用于请求创建第二会话以及指示所述第一会话与第二会话的下行流关联；或
    从应用功能网元接收第一配置请求，所述第一配置请求用于配置所述第一会话，所述第一配置请求还用于指示所述第一会话的上行流与第二会话关联或所述第一会话与第二会话关联。
  35. 如权利要求33或34所述的装置，其特征在于，
    所述接收单元，还用于接收第二请求，所述第二请求用于请求创建第二会话以及指示所述第二会话的上行流与第一会话关联；
    所述处理单元，还在所述用户面网元中配置第二转发规则，所述第二转发规则指示通过第一会话转发来自所述第二会话的上行数据报文。
  36. 如权利要求34所述的装置，其特征在于，所述接收单元在接收第二请求时，具体用于：
    从第二终端设备接收第三会话创建请求，所述第三会话创建请求用于请求创建第二会话，所述第三会话创建请求还用于指示所述第二会话的上行流与第一会话关联或所述第一会话与第二会话关联；或
    从应用功能网元接收第二配置请求，所述第二配置请求用于配置所述第二会话，所述第二配置请求还用于指示所述第二会话的上行流与第一会话关联或所述第一会话与第二会话关联。
  37. 如权利要求34所述的装置，其特征在于，所述第一会话创建请求以及所述第一配置请求包括下列中的部分或全部：
    所述第二会话的标识或会话关联标识，所述会话关联标识指示所述第一会话与所述第二会话关联；
    所述第二会话创建请求包括下列中的部分或全部：
    所述第一会话的标识或所述会话关联标识。
  38. 如权利要求35或36所述的装置，其特征在于，所述第三会话创建请求以及所述第二配置请求包括下列中的部分或全部：
    所述第一会话的标识或会话关联标识，所述会话关联标识指示所述第一会话与所述第二会话关联。
  39. 如权利要求33～38任一所述的装置，其特征在于，所述第一转发规则为所述第一会话的转发规则，所述第一转发规则包括下列的部分或全部：
    所述第二会话的标识、会话关联标识、或所述第二会话的通用无线分组业务隧道协议用户面GTP-U标识，其中，所述会话关联标识指示所述第一会话与所述第二会话关联。
  40. 如权利要求33～38任一所述的装置，其特征在于，所述第二转发规则为所述第二会话的转发规则，所述第二转发规则包括下列的部分或全部：
    所述第一会话的标识、会话关联标识、或所述第一会话的通用无线分组业务隧道协议用户面GTP-U标识，其中，所述会话关联标识指示所述第一会话与所述第二会话关联。
  41. 一种通信装置，其特征在于，用于实现如权利要求1至6任一项所述的方法。
  42. 一种通信装置，其特征在于，用于实现如权利要求7至8任一项所述的方法。
  43. 一种通信装置，其特征在于，用于实现如权利要求9至10任一项所述的方法。
  44. 一种通信装置，其特征在于，用于实现如权利要求11至12任一项所述的方法。
  45. 一种通信装置，其特征在于，用于实现如权利要求13至20任一项所述的方法。
  46. 一种通信装置，其特征在于，包括处理器和存储器，所述存储器中存储有指令，所述处理器执行所述指令时，使得所述装置执行权利要求1至6任一项所述的方法。
  47. 一种通信装置，其特征在于，包括处理器和存储器，所述存储器中存储有指令，所述处理器执行所述指令时，使得所述装置执行权利要求7至8任一项所述的方法。
  48. 一种通信装置，其特征在于，包括处理器和存储器，所述存储器中存储有指令，所述处理器执行所述指令时，使得所述装置执行权利要求9至10任一项所述的方法。
  49. 一种通信装置，其特征在于，包括处理器和存储器，所述存储器中存储有指令，所述处理器执行所述指令时，使得所述装置执行权利要求11至12任一项所述的方法。
  50. 一种通信装置，其特征在于，包括处理器和存储器，所述存储器中存储有指令，所 述处理器执行所述指令时，使得所述装置执行权利要求13至20任一项所述的方法。
  51. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得所述计算机执行如权利要求1～20任一项所述的方法。
  52. 一种计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得所述计算机执行如权利要求1～20任一项所述的方法。
  53. 一种计算机芯片，其特征在于，所述芯片与存储器相连，所述芯片用于读取并执行所述存储器中存储的软件程序，执行如权利要求1～20任一项所述的方法。
PCT/CN2021/090782 2020-04-29 2021-04-28 一种通信方法及装置 WO2021219044A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010356026.5A CN113573330A (zh) 2020-04-29 2020-04-29 一种通信方法及装置
CN202010356026.5 2020-04-29

Publications (1)

Publication Number Publication Date
WO2021219044A1 true WO2021219044A1 (zh) 2021-11-04

Family

ID=78157710

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/090782 WO2021219044A1 (zh) 2020-04-29 2021-04-28 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN113573330A (zh)
WO (1) WO2021219044A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019157873A1 (zh) * 2018-02-13 2019-08-22 中兴通讯股份有限公司 计费方法、装置及会话管理实体
CN110324246A (zh) * 2018-03-31 2019-10-11 华为技术有限公司 一种通信方法及装置
CN111010744A (zh) * 2018-10-08 2020-04-14 华为技术有限公司 建立会话的方法和装置以及发送报文的方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019157873A1 (zh) * 2018-02-13 2019-08-22 中兴通讯股份有限公司 计费方法、装置及会话管理实体
CN110324246A (zh) * 2018-03-31 2019-10-11 华为技术有限公司 一种通信方法及装置
CN111010744A (zh) * 2018-10-08 2020-04-14 华为技术有限公司 建立会话的方法和装置以及发送报文的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
TENCENT: "Support for Groupcast Traffic Forwarding of a 5G VN", 3GPP DRAFT; S2-1907545 TS23.501 R16 TSN MC TRAFFIC FORWARDING OF A 5G VN GROUP, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Sapporo, Japan; 20190624 - 20190628, 18 June 2019 (2019-06-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 4, XP051752504 *

Also Published As

Publication number Publication date
CN113573330A (zh) 2021-10-29

Similar Documents

Publication Publication Date Title
US20220060416A1 (en) Routing Rule Management Method and Communications Apparatus
US10397012B2 (en) Evolved multimedia broadcast/multicast service (EMBMS) system and EMBMS system management method
US9173244B2 (en) Methods for establishing and using public path, M2M communication method, and systems thereof
CN112105088B (zh) 多播通信方法、装置及***
CN114124618B (zh) 一种报文传输方法及电子设备
CN110703817A (zh) 一种统计流量的控制方法、装置和***
WO2021135650A1 (zh) 通信方法及装置
EP3949468A1 (en) Apparatus, method and computer program for group communication
EP4138439A1 (en) Communication method, apparatus, and system
US11722883B2 (en) Transmission method and apparatus
WO2021089018A1 (zh) 一种通信方法、装置及***
WO2022143395A1 (zh) 一种冗余路径创建方法、装置及***
WO2020200207A1 (zh) 一种获取终端设备互联网协议ip地址方法、设备及***
WO2020169039A1 (zh) 一种策略管理的方法及装置
US20220182304A1 (en) Communication method, apparatus, and system
KR20130116343A (ko) 일시적 가입 레코드
CN109120657B (zh) 一种业务配置方法和节点
WO2021184271A1 (zh) 一种消息转发方法及装置
WO2021219044A1 (zh) 一种通信方法及装置
WO2021004393A1 (zh) 支持端口控制的方法及设备
WO2021174376A1 (zh) 一种通信方法及装置
WO2021057020A1 (zh) 一种网络切片的计费方法及装置
JP7472279B2 (ja) 通信方法、装置、およびシステム
WO2022037097A1 (zh) 通信方法、装置及***
CN104811386A (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: 21797261

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21797261

Country of ref document: EP

Kind code of ref document: A1