A communication method and apparatus

Abstract

A communication method and apparatus for enabling a user plane network element to transmit data packets to each slave device in an EtherCAT network through a session. In this application, the user plane network element can receive a first uplink data packet through a first session, and the first session is a session of a first terminal device. Then, the user plane network element forwards the first uplink data packet from the first session according to a first forwarding rule indicating to forward the uplink data packet from the first session through a second session. When the user plane network element forwards the first uplink data packet, according to the association relationship between the first session and the second session, it forwards the first uplink data packet through the session associated with the first session. When a second terminal device is associated with a slave device or a master device, the user plane network element can send the first uplink data packet to the slave device or the master device associated with the second terminal device through the second session.

Description

Technical Field

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

[0002] Currently, in a fifth-generation mobile networks (5G) system, data forwarding between user equipment (UE) can be implemented through a user plane network element for local forwarding. Taking the data forwarding between UE1 and UE2 as an example, UE1 sends a data packet carrying a media access control address (MAC) with the destination address being UE2 to the user plane network element. After receiving the data packet, the user plane network element identifies the destination address of the data packet and sends the data packet to UE2 through the UE2 session.

[0003] An ether control automation technology (EtherCAT) system is a communication system based on Ethernet. The EtherCAT network includes a master device and multiple slave devices, and the network interfaces of the master device and the slave devices have sending and receiving functions. Different physical topologies are realized through wired connections between the master device and the slave devices. The transmission path of data packets in the EtherCAT network is a ring loop passing through the master device and each slave device.

[0004] In view that data forwarding between terminal devices in the 5G system is implemented by the user plane network element according to the characteristics of the data packet (such as the destination address in the packet), when EtherCAT devices are accessed through the 5G system, for the data packet to implement the EtherCAT transmission mechanism, that is, the same data packet needs to pass through each EtherCAT device in sequence. That is to say, the data packet needs to pass through the 5G system multiple times for transmission; and the characteristics of the data packet do not change when it reaches the user plane network element in the 5G system multiple times. Therefore, due to the existing data forwarding mechanism limitations of the user plane network element in the 5G system, after the data packet enters the user plane network element in the 5G system, it is impossible to determine the device in the EtherCAT network for forwarding the packet based on the characteristics of the data packet itself, resulting in the inability to form a ring loop for data packet transmission between the master device and multiple slave devices in the communication system combining the EtherCAT network and the 5G system, and the user plane network element cannot send the data packet to each slave device in the EtherCAT network through the session. Summary of the Invention

[0005] The present application provides a communication method and apparatus for enabling a user plane network element to transmit data packets to each slave device in an EtherCAT network through a session.

[0006] In a first aspect, an embodiment of the present application provides a communication method, the method including: the user plane network element may receive a first uplink data packet through a first session, where the first session is a session of a first terminal device; then, the user plane network element forwards the first uplink data packet from the first session according to an indication through a second session, a first forwarding rule for forwarding the uplink data packet from the first session through the second session, where the second session is a session of a 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.

[0007] Through the above method, when the user plane network element forwards the uplink data packet from the first terminal device (i.e., the first uplink data packet), it may forward the first uplink data packet through a session associated with the session of the first terminal device according to the association relationship between the session of the first terminal device and the session of the second terminal device. In this way, when the first terminal device is associated with a slave device or a master device in the EtherCAT network, the user plane network element may receive the first uplink data packet from the slave device or the master device associated with the first terminal device through the session of the first terminal device; when the second terminal device is associated with a slave device or a master device in the EtherCAT network, the user plane network element may send the first uplink data packet to the slave device or the master device associated with the second terminal device through the session of the second terminal device.

[0008] In a possible design, the user plane network element may further receive a second uplink data packet through the second session; then, the user plane network element forwards the second uplink data packet through the first session according to a second forwarding rule, where the second forwarding rule indicates forwarding the uplink data packet from the second session through the first session.

[0009] Through the above method, when the user plane network element forwards the uplink data packet from the second terminal device (i.e., the second uplink data packet), it may forward the second uplink data packet through a session associated with the session of the second terminal device according to the association relationship between the session of the first terminal device and the session of the second terminal device. In this way, when the second terminal device is associated with a slave device or a master device in the EtherCAT network, the user plane network element may receive the second uplink data packet from the slave device or the master device associated with the second terminal device through the session of the second terminal device; when the first terminal device is associated with a slave device or a master device in the EtherCAT network, the user plane network element may send the second uplink data packet to the slave device or the master device associated with the second terminal device through the session of the first terminal device.

[0010] In a possible design, before the user plane network element receives the first uplink data packet through the first session, a first forwarding rule may also be pre-configured in the user plane network element. For example, the user plane network element may receive the first forwarding rule from the session management network element.

[0011] Through the above method, since the first forwarding rule is pre-configured in the user plane network element, it can be ensured that the first uplink data packet can be forwarded through the second session.

[0012] In a possible design, before the user plane network element receives the second uplink data packet through the second session, a second forwarding rule may also be pre-configured in the user plane network element. For example, the user plane network element may receive the second forwarding rule from the session management network element.

[0013] Through the above method, since the second forwarding rule is pre-configured in the user plane network element, it can be ensured that the second uplink data packet can be forwarded through the second session.

[0014] In a possible design, the first forwarding rule is the forwarding rule of the first session, and the first forwarding rule includes some or all of the following:

[0015] 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 the association between the first session and the second session.

[0016] Through the above method, the first forwarding rule can flexibly indicate to forward the uplink data packet from the first session through the second session by carrying the identifier of the second session, the session association identifier, etc., and is applicable to a variety of different application scenarios.

[0017] In a possible design, the second forwarding rule is the forwarding rule of the second session, and the second forwarding rule includes some or all of the following:

[0018] The identifier of the first session, the session association identifier, or the General Packet Radio Service Tunneling Protocol User Plane (GTP-U) identifier of the first session, where the session association identifier indicates the association between the first session and the second session.

[0019] Through the above method, the second forwarding rule can flexibly indicate to forward the uplink data packet from the second session through the first session by carrying the identifier of the first session, the session association identifier, etc., and is applicable to a variety of different application scenarios.

[0020] Second aspect, embodiments of the present application provide 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 a session management network element. The first session creation (or modification) request is used to request the creation (or modification) of a first session, and the first session creation (or modification) request is further used to indicate that the uplink flow of the first session is associated with a second session or the first session is associated with the second session; After that, after the first terminal device receives a first session creation (or modification) response from the session management network element, it may send a first uplink data packet through the first session. The first session creation (or modification) response indicates that the creation (or modification) of the first session is successful.

[0021] Through the above method, when the first terminal device initiates a session creation or modification process, it may indicate that the uplink flow of the first session is associated with the second session, which is convenient for the session management network element to configure a first forwarding rule in the user plane network element.

[0022] In a possible design, the first session creation (or modification) request includes an identifier of the second session or a session association identifier, and the session association identifier indicates that the first session is associated with the second session. Optionally, the first session creation (or modification) request may further carry indication information of the uplink flow, such as the flow direction information of the session.

[0023] Through the above method, the first session creation (or modification) request can flexibly indicate that the uplink flow of the first session is associated with the second session by carrying the identifier of the first session and the session association identifier, and is applicable to a variety of different application scenarios.

[0024] Third aspect, 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 second session creation (or modification) request to a session management network element. The second session creation (or modification) request is used to request the creation (or modification) of a second session and indicate that the downlink flow of the second session is associated with the first session;

[0025] After the second terminal device receives a second session creation (or modification) response from the session management network element, it receives a first uplink data packet through the second session. The second session creation (or modification) response indicates that the creation (or modification) of the second session is successful.

[0026] Through the above method, when the second terminal device initiates a session creation or modification process, it may indicate that the first session is associated with the downlink flow of the second session, which is convenient for the session management network element to configure a first forwarding rule in the user plane network element.

[0027] In a possible design, 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.

[0028] Through the above method, the second session creation (or modification) request can flexibly indicate the association between the downlink flow of the first session and the second session (that is, the uplink flow of the first session is associated with the second session) by carrying the identifier of the first session and the session association identifier, and is applicable to a variety of different application scenarios.

[0029] In a fourth aspect, an embodiment of the present application provides 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 a session management network element. The third session creation (or modification) request is used to request the creation (or modification) of a second session, and the third session creation (or modification) request is further used to indicate that the uplink flow of the second session is associated with the first session or the first session is associated with the second session; After that, after the second terminal device receives a 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 that the creation (or modification) of the second session is successful.

[0030] Through the above method, when the second terminal device initiates a session creation or modification process, it can indicate the association between the uplink flow of the first session and the second session, which is convenient for the session management network element to configure a second forwarding rule in the user plane network element.

[0031] In a possible design, the third session creation (or modification) request includes the identifier of the first session or the session association identifier, and the session association identifier indicates the association between the first session and the second session. Optionally, the third session creation (or modification) request may further carry indication information of the uplink flow, such as the flow direction information of the session.

[0032] Through the above method, the third session creation (or modification) request can flexibly indicate the association between the uplink flow of the second session and the first session by carrying the identifier of the first session and the session association identifier, and is applicable to a variety of different application scenarios.

[0033] In a fifth aspect, an embodiment of the present application provides a communication method. The method includes: The session management network element may receive a first request, and the first request is used to indicate the association between the uplink flow of the first session and the second session; The first request may be sent by a first terminal device, a second terminal device, or an 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 indicates to forward the uplink data packet from the first session through the second session.

[0034] Through the above method, after the session management network element learns the association relationship between the uplink flow of the first session and the second session, it can configure the first forwarding rule in a timely manner, which is convenient for forwarding the uplink data packet from the first session through the second session subsequently.

[0035] In a possible design, the session management network element receives a first request, including the following cases:

[0036] Case 1: The session management network element receives a first session creation (or modification) request from a first terminal device. The first session creation (or modification) request is used to request the creation of a first session and indicate that the uplink flow of the first session is associated with a second session.

[0037] Case 2: The session management network element receives a first session creation (or modification) request from a first terminal device. The second session creation (or modification) request is used to request the creation of a first session and indicate that the first session is associated with a second session.

[0038] Case 3: The session management network element receives a second session creation (or modification) request from a second terminal device. The third session creation request is used to request the creation of a second session and indicate that the downlink flow of the first session is associated with the second session.

[0039] Case 4: The session management network element receives a first configuration request from an application function network element. The first configuration request is used to configure a first session, and the first configuration request is also used to indicate that the uplink flow of the first session is associated with a second session or the first session is associated with a second session.

[0040] Through the above method, the first request can come from a terminal device or other network elements, that is, different devices can inform the session management network element of the association between the uplink flow of the first session (the uplink flow) and the second session through different messages, which is applicable to different scenarios and expands the application scope.

[0041] In a possible design, the session management network element can also receive a second request. The second request is used to request the creation of a second session and indicate that the uplink flow of the second session is associated with the first session; afterwards, the session management network element configures a second forwarding rule in the user plane network element, and the second forwarding rule indicates forwarding the uplink data packet from the second session through the first session.

[0042] Through the above method, after the session management network element learns the association relationship between the uplink flow of the second session and the first session, it can timely configure the second forwarding rule to facilitate subsequent forwarding of the uplink data packet from the second session through the first session.

[0043] In a possible design, the session management network element receives a second request, including the following cases:

[0044] Case 1: The session management network element receives a third session creation (or modification) request from a second terminal device. The third session creation (or modification) request is used to request the creation (or modification) of a second session and indicate that the uplink flow of the second session is associated with the first session.

[0045] Scenario 2: The session management network element receives a third session creation (or modification) request from a second terminal device. The third session creation (or modification) request is used to request the creation (or modification) of a second session and indicates that the second session is associated with the first session.

[0046] Scenario 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 further used to indicate that the uplink flow of the second session is associated with the first session or the first session is associated with the second session.

[0047] Through the above method, the second request can come from a terminal device or other network elements, that is, different devices can inform the session management network element that the uplink flow of the second session (or the uplink flow) is associated with the first session through different messages, which is applicable to different scenarios and expands the application scope.

[0048] In a possible design, 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 the association between the first session and the second session. The first session creation (or modification) request may further include indication information of the uplink flow. When the first configuration request indicates that the uplink flow of the first session is associated with the second session, it may also carry the indication information of the uplink flow.

[0049] 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 further include indication information of the uplink flow. The third session creation (or modification) request may further include indication information of the downlink flow.

[0050] Through the above method, the first request can flexibly indicate the association between the second session and the first session by carrying the identifier of the session, the session association identifier, etc., which is applicable to a variety of different application scenarios.

[0051] In a possible design, 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 association between the first session and the second session. The third session creation (or modification) request may further include indication information of the uplink flow. When the second configuration request indicates that the uplink flow of the second session is associated with the first session, it may also carry the indication information of the uplink flow.

[0052] Through the above method, the second request can flexibly indicate the association between the second session and the first session by carrying the identifier of the session, the session association identifier, etc., which is applicable to a variety of different application scenarios.

[0053] In a possible design, the first forwarding rule is the forwarding rule for the first session. 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. The session association identifier indicates the association between the first session and the second session.

[0054] Through the above method, the first forwarding rule can flexibly indicate forwarding the uplink data packet from the first session through the second session by carrying the identifier of the second session, the session association identifier, etc., and is applicable to a variety of different application scenarios.

[0055] In a possible design, the second forwarding rule is the forwarding rule for the second session. The second forwarding rule includes some or all of the following:

[0056] The identifier of the first session, the session association identifier, or the General Packet Radio Service Tunneling Protocol User Plane (GTP-U) identifier of the first session. The session association identifier indicates the association between the first session and the second session.

[0057] Through the above method, the second forwarding rule can flexibly indicate forwarding the uplink data packet from the second session through the first session by carrying the identifier of the first session, the session association identifier, etc., and is applicable to a variety of different application scenarios.

[0058] In a sixth aspect, an embodiment of the present application provides a communication method, which is applied to an Application Function (AF) network element. The method includes: First, the AF network element sends a first configuration request to the Session Management Function (SMF) 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 flow of the first session is associated with the second session or the first session is associated with the second session. 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 the association between the first session and the second session. When the first configuration request indicates that the uplink flow of the first session is associated with the second session, it may also carry the indication information of the uplink flow.

[0059] Through the above method, when configuring the first session, the AF network element can indicate the association between the first session and the second session, which is convenient for the SMF network element to configure the first forwarding rule in the User Plane Function (UPF) network element.

[0060] In a possible design, the AF network element sends a second configuration request to the SMF 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 flow of the second session is associated with the first session 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 the association between the first session and the second session. When the first configuration request indicates that the uplink flow of the second session is associated with the first session, it may also carry the indication information of the uplink flow.

[0061] Through the above method, when the application function network element configures the second session, it can indicate the association between the first session and the second session, facilitating the session management network element to configure the second forwarding rule in the user plane network element.

[0062] In a seventh aspect, an embodiment of the present application further provides a communication system. The beneficial effects can be referred to the descriptions in the first aspect and the second aspect, which will not be elaborated here. The communication system includes a session management network element and a user plane network element;

[0063] The session management network element is configured to receive a first request, where the first request is used to indicate the association between the uplink flow of the first session and the second session; and send a first forwarding rule to the user plane network element, where the first forwarding rule indicates forwarding the uplink data packet from the first session through the second session.

[0064] The user plane network element is configured to receive the first forwarding rule; 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.

[0065] In a possible design, the session management network element may further receive a second request, where the second request is used to request the creation of the second session and indicate the association between the uplink flow of the second session and the first session; and send a second forwarding rule to the user plane network element, where the second forwarding rule indicates forwarding the uplink data packet from the second session through the first session;

[0066] The user plane network element may receive the second forwarding rule; 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.

[0067] In a possible design, the first request is a first session creation (or modification) request; the communication system further includes a first terminal device;

[0068] 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) request is further used to indicate the association between the uplink flow of the first session and the second session or the association between the first session and the second session.

[0069] In a possible design, the first request is a second session creation (or modification) request; the communication system further includes a second terminal device;

[0070] The second terminal device may send a second 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 indicate the association between the downlink flow of the second session and the first session.

[0071] In a possible design, the first request is a first configuration request, and the communication system further includes an application function network element;

[0072] 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 a first session, and the first configuration request is further used to indicate that the uplink flow of the first session is associated with a second session or the first session is associated with the second session.

[0073] In a possible design, the second request is a third session creation (or modification) request; the communication system includes a second terminal device;

[0074] 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 a second session, and the third session creation (or modification) request is further used to indicate that the uplink flow of the second session is associated with the first session or the first session is associated with the second session.

[0075] In a possible design, the second request is a second configuration request, and the communication system further includes an application function network element;

[0076] The application function network element may send a second configuration request to the session management network element. The second configuration request is used to configure a second session, and the second configuration request is further used to indicate that the uplink flow of the second session is associated with the first session or the first session is associated with the second session.

[0077] In a possible design, the first session creation (or modification) request includes some or all of the following:

[0078] The identifier of the second session or a session association identifier, where the session association identifier indicates that the first session is associated with the second session.

[0079] In a possible design, the second session creation (or modification) request includes some or all of the following:

[0080] The identifier of the first session or a session association identifier.

[0081] In a possible design, the first configuration request includes some or all of the following:

[0082] The identifier of the second session or a session association identifier, where the session association identifier indicates that the first session is associated with the second session.

[0083] In a possible design, the third session creation (or modification) request includes some or all of the following:

[0084] The identifier of the first session or a session association identifier, where the session association identifier indicates that the first session is associated with the second session.

[0085] In a possible design, the second configuration request includes some or all of the following:

[0086] An identifier of the first session or a session association identifier, where the session association identifier indicates that the first session is associated with the second session.

[0087] In a possible design, the first forwarding rule is the forwarding rule of the first session, and the first forwarding rule includes some or all of the following:

[0088] An identifier of the second session, a session association identifier, or a General Packet Radio Service Tunneling Protocol User Plane (GTP-U) identifier of the second session, where the session association identifier indicates that the first session is associated with the second session.

[0089] In a possible design, the second forwarding rule is the forwarding rule of the second session, and the second forwarding rule includes some or all of the following:

[0090] An identifier of the first session, a session association identifier, or a GTP-U identifier of the first session, where the session association identifier indicates that the first session is associated with the second session.

[0091] In a ninth aspect, an embodiment of the present application further provides a communication device, which is applied to a user plane network element. The beneficial effects can be referred to the description in the first aspect and will not be elaborated here. The device has the functions of implementing the behaviors in the method example of the first aspect. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the structure of the device includes a receiving unit and a sending unit, and these units can execute the corresponding functions in the method example of the first aspect. For specific reference, see the detailed description in the method example and will not be elaborated here.

[0092] In a tenth aspect, an embodiment of the present application further provides a communication device, which is applied to a first terminal device. The beneficial effects can be referred to the description in the second aspect and will not be elaborated here. The device has the functions of implementing the behaviors in the method example of the second aspect. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the structure of the device includes a receiving unit and a sending unit, and these units can execute the corresponding functions in the method example of the second aspect. For specific reference, see the detailed description in the method example and will not be elaborated here.

[0093] In a tenth aspect, an embodiment of the present application further provides a communication device, which is applied to a second terminal device. For the beneficial effects, reference may be made to the description in the third aspect and will not be elaborated here. The device has the function of implementing the actions in the method example of the above-mentioned third aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the structure of the device includes a receiving unit and a transmitting unit, and these units can execute the corresponding functions in the method example of the above-mentioned third aspect. For details, refer to the detailed description in the method example and will not be elaborated here.

[0094] In an eleventh aspect, an embodiment of the present application further provides a communication device, which is applied to a second terminal device. For the beneficial effects, reference may be made to the description in the fourth aspect and will not be elaborated here. The device has the function of implementing the actions in the method example of the above-mentioned fourth aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the structure of the device includes a receiving unit and a transmitting unit, and these units can execute the corresponding functions in the method example of the above-mentioned fourth aspect. For details, refer to the detailed description in the method example and will not be elaborated here.

[0095] In a twelfth aspect, an embodiment of the present application further provides a communication device, which is applied to a session management network element. For the beneficial effects, reference may be made to the description in the fifth aspect and will not be elaborated here. The device has the function of implementing the actions in the method example of the above-mentioned fifth aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the structure of the device includes a receiving unit and a processing unit, and these units can execute the corresponding functions in the method example of the above-mentioned fifth aspect. For details, refer to the detailed description in the method example and will not be elaborated here.

[0096] In a thirteenth aspect, an embodiment of the present application further provides a communication device, which is applied to an application function network element. For the beneficial effects, reference may be made to the description in the sixth aspect and will not be elaborated here. The device has the function of implementing the actions in the method example of the above-mentioned sixth aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the structure of the device includes a transmitting unit, and these units can execute the corresponding functions in the method example of the above-mentioned sixth aspect. For details, refer to the detailed description in the method example and will not be elaborated here.

[0097] In a fourteenth aspect, an embodiment of the present application further provides a communication device, which is applied to a user plane network element. The beneficial effects can be referred to the description in the first aspect and will not be elaborated here. The structure of the communication device includes a processor and a memory. The processor is configured to support the user plane network element to execute the corresponding functions in the method of the first aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device. The structure of the communication device further includes a communication interface for communicating with other devices.

[0098] In a fifteenth aspect, an embodiment of the present application further provides a communication device, which is applied to a first terminal device. The beneficial effects can be referred to the description in the second aspect and will not be elaborated here. The structure of the communication device includes a processor and a memory. The processor is configured to support the first terminal device to execute the corresponding functions in the method of the second aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device. The structure of the communication device further includes a transceiver for communicating with other devices.

[0099] In a sixteenth aspect, an embodiment of the present application further provides a communication device, which is applied to a second terminal device. The beneficial effects can be referred to the description in the third aspect and will not be elaborated here. The structure of the communication device includes a processor and a memory. The processor is configured to support the second terminal device to execute the corresponding functions in the method of the third aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device. The structure of the communication device further includes a transceiver for communicating with other devices.

[0100] In a seventeenth aspect, an embodiment of the present application further provides a communication device, which is applied to a second terminal device. The beneficial effects can be referred to the description in the fourth aspect and will not be elaborated here. The structure of the communication device includes a processor and a memory. The processor is configured to support the second terminal device to execute the corresponding functions in the method of the fourth aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device. The structure of the communication device further includes a transceiver for communicating with other devices.

[0101] In an eighteenth aspect, an embodiment of the present application further provides a communication device, which is applied to a session management network element. The beneficial effects can be referred to the description in the fifth aspect and will not be elaborated here. The structure of the communication device includes a processor and a memory. The processor is configured to support the base station to execute the corresponding functions in the method of the fifth aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device. The structure of the communication device further includes a communication interface for communicating with other devices.

[0102] In a nineteenth aspect, an embodiment of the present application further provides a communication device, which is applied to an application function network element. The beneficial effects can be referred to the description in the sixth aspect and will not be elaborated here. The structure of the communication device includes a processor and a memory. The processor is configured to support the base station to execute the corresponding functions in the method of the sixth aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device. The structure of the communication device further includes a communication interface for communicating with other devices.

[0103] In a twentieth aspect, the present application further provides a computer-readable storage medium, in which instructions are stored. When the instructions are run on a computer, the computer is caused to execute the methods described in the above aspects.

[0104] In a twenty-first aspect, the present application further provides a computer program product containing instructions. When the computer program product is run on a computer, the computer is caused to execute the methods described in the above aspects.

[0105] In a twenty-second aspect, the present application further provides a computer chip. The chip is connected to a memory, and the chip is used to read and execute the software program stored in the memory and execute the methods described in the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0106] Figure 1 It is a schematic diagram of the network architecture of a 5G system;

[0107] Figure 2 It is a schematic diagram of the network topology of EtherCAT;

[0108] Figure 3 It is a schematic diagram of the structure of an EtherCAT message;

[0109] Figures 4a to 4c It is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0110] Figures 5 to 12 It is a schematic diagram of a communication method provided by an embodiment of the present application;

[0111] Figures 13 to 19 It is a schematic diagram of the structure of a communication device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0112] The present application provides a communication method and device for enabling a user plane network element to transmit data packets to each slave device in an EtherCAT network through a session.

[0113] To make the objectives, technical solutions, and advantages of this application clearer, the following will further describe this application in detail in conjunction with the accompanying drawings. In the description of this application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship. For example, A / B may represent A or B. The "and / or" in this application is merely a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. Here, A and B may be singular or plural. Also, in the description of this application, unless otherwise specified, "a plurality of" means two or more than two.

[0114] The embodiments of this application relate to the combination of a 5G system and an EtherCAT network. First, the 5G system, EtherCAT network, and network architecture applicable to the embodiments of this application will be described below.

[0115] Please refer to Figure 1 , which is a schematic diagram of the network architecture of the 5G system. This network architecture is a 5G network architecture. The network elements in this 5G architecture include terminal devices. Figure 1 In, the terminal device is taken as the UE as an example. The network architecture also includes a radio access network (RAN), an access and mobility management function (AMF) network element, a session management function (SMF) network element, a user plane function (UPF) network element, a policy control function (PCF) network element, an application function (AF) network element, a data network (DN), etc.

[0116] The main function of the RAN is to control users to access the mobile communication network wirelessly. The RAN is a part of the mobile communication system. It implements a wireless access technology. Conceptually, it resides between certain devices (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 access management and mobility management of the terminal. In practical applications, it includes the mobility management function in the MME in the LTE network framework and adds an access management function.

[0117] The SMF network element is responsible for session management, such as the establishment of a user's session, etc.

[0118] The UPF network element is a user plane functional network element, mainly responsible for connecting to the external network, which includes the relevant functions of the serving gateway (SGW) and the public data network gateway (PDN-GW) of LTE.

[0119] The DN is the network that provides services for the terminal. For example, some DNs provide Internet access functions for the terminal, and some other DNs provide SMS functions for the terminal, etc.

[0120] The main function of the PCF network element is to perform policy control, similar to the policy and charging rules function (PCRF) network element in LTE. It is mainly responsible for policy authorization, service quality, and the generation of charging rules, and sends the corresponding rules to the UPF network element through the SMF network element to complete the installation of the corresponding policies and rules.

[0121] The AF network element can be a third-party application control platform or the operator's own device. 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, can interact with the core network through the NEF network element, and can also interact with the policy management framework for policy management.

[0122] In addition, although not shown, the core network control plane functional network elements also include the network exposure function (NEF), unified data management (UDM), and unified data repository (UDR) network elements. The NEF network element is used to provide a framework, authentication, and interfaces related to network capability exposure, and transfer information between the 5G system network functions and other network functions; the UDR network element is mainly used to store user-related subscription data, policy data, structured data for exposure, and application data; the UDM network element can store the user's subscription information and implement a backend similar to the HSS in 4G.

[0123] The terminal device in this application, also known as user equipment (UE), is a device with wireless transceiver functions. It can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, satellites, etc.). The terminal device can be a mobile phone, a tablet (pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc.

[0124] The EtherCAT network and its principle are introduced below.

[0125] EtherCAT is a real-time Ethernet technology developed and promoted by ETG (EtherCAT Technology Group) under Beckhoff in Germany. It is an open network protocol that can communicate between master and slave devices. It uses a cluster frame, and the network topology always forms a logical ring. In each cycle, the master device (also called the master station or master node) sends data packets to some or all of the slave devices (also called the slave stations or slave nodes). The data packets are transmitted along the ring topology from one slave device. When the data packets sent by the master device pass through a slave device, the slave device only receives the data sent for it and adds its own output data to the packets at the same time.

[0126] For easy understanding, take the example of a high-speed train. The principle of EtherCAT is similar to that of a high-speed train. The "train" (EtherCAT packet) keeps running. Standing on the platform and staring at the train through the window, we can see the whole train. When someone we know is sitting by the window of the train, the people on the platform can say hello to the acquaintance through the window (that is, each slave device can extract or insert data into the part of the data frame sent by the master device corresponding to the address of each slave device).

[0127] Such as Figure 2As shown in the figure, it is a schematic diagram of the EtherCAT ring topology structure in the prior art. The master device and the slave devices are connected by means of wired transmission, and the slave devices are also connected by means of wired transmission. There is one master device and at least one slave device in a ring topology structure.

[0128] As Figure 3 shown in the figure, it is a schematic diagram of the structure of an EtherCAT message in the prior art. An EtherCAT message includes a frame header (e.g., Ethernet header), data (e.g., Ethernet data), and a frame check sequence (e.g., Frame Check Sequence, FCS).

[0129] Among them, the frame header can also be called a standard Ethernet frame header, which mainly includes a source address, a destination address, an Ethernet frame type, etc.

[0130] The data mainly includes two parts: a data header (e.g., EtherCAT Header) and messages (e.g., EtherCAT Datagrams):

[0131] 1) EtherCAT Header, which contains: a data length (Length) indication field, a reserved bit (R), and a 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.

[0132] 2) EtherCAT Datagrams, which contain multiple sub-messages, and the total length is between 44 and 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). Among them, the address segment of the slave device that needs to receive this sub-message is indicated in the sub-message header.

[0133] The frame check sequence (FCS), also known as the frame tail, is a cyclic redundancy check code. When the source device sends a data frame, the FCS is calculated from the frame header and the data part of the frame. When the destination device receives it, the FCS is calculated again in the same way. If it is different from the received FCS, it is considered that an error has occurred during the transmission of the frame, and thus this frame is selected to be discarded. The FCS provides an error detection mechanism to verify the integrity of the frame during transmission. The length occupied by the FCS in the Ethernet frame is fixed, generally 4 bytes.

[0134] When an EtherCAT message is received from a device, that is, it is determined 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), and the processing includes reading the data in the sub-message or inserting data into the sub-message.

[0135] For the address segment in the sub-message of the EtherCAT message, the slave device can perform addressing in the following two ways:

[0136] 1). Incremental addressing.

[0137] Each slave device corresponds to a negative incremental address according to its position in the EtherCAT network. Each sub-message (sub-message header) in the EtherCAT message sent by the master device includes the incremental address of a corresponding slave device. When the EtherCAT message passes through a slave device, the slave device processes the sub-message with an incremental address of 0, and after adding 1 to the incremental addresses in each sub-message of the EtherCAT message, it transmits the message to the next slave device. Incremental addressing is usually used to scan hardware configuration information or determine the relative positions between slave devices.

[0138] 2). Fixed address or logical address:

[0139] Each slave device has a fixed address (or logical address), which is independent of its position in the EtherCAT network. The fixed address is generally assigned during the process of scanning the hardware configuration and is applicable 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 for reading and writing operations on the virtual data space.

[0140] Each sub-message (sub-message header) in the EtherCAT message sent by the master device includes the fixed address (or logical address) of a corresponding slave device. When the EtherCAT message passes through a slave device, the slave device processes the sub-message with an address that is the fixed address of the slave device. After processing the sub-message, it transmits the EtherCAT message including the processed sub-message to the next slave device.

[0141] As Figure 4a shown, it is a schematic diagram of a network architecture applicable to this application, in which a network architecture combining a 5G system and EtherCAT is shown. Figure 4a In the EtherCAT network, the master device is deployed in the DN and is connected to the UPF network element in the 5G system. The slave devices in the EtherCAT network are connected to the UEs in the 5G system. Here, the number of slave devices connected to the UEs in the 5G system is not limited, nor is the number of UEs in the 5G system limited.

[0142] For example, one or more slave devices in the EtherCAT network can access the 5G system through a 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. For another example, one or more slave devices in the EtherCAT network can be bound to a session of a 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 this session. 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 this session.

[0143] In the network architecture as Figure 4a shown, the master device in the EtherCAT network can send data packets to each slave device connected to the UE of the 5G system through the 5G system. To ensure the loop of data packet transmission in the EtherCAT network, under the trigger of the UE or other network elements (AF network elements), the SMF network element configures the forwarding rules of the session in the UPF network element and establishes the association relationship between sessions. After that, when the UPF network element receives the data packet that needs to be transmitted in the EtherCAT network through the session, it can forward the data packet through the session associated with this session based on the forwarding rules of the session, so that the data packet can be forwarded to the session associated with this session, and then transmitted to the slave device bound to the session associated with this session.

[0144] It should be noted that in the network architecture as Figure 4a shown, it is only illustrated that the master device in the EtherCAT network is deployed in the DN and the slave devices are deployed on the UE side. The embodiments of the present application do not limit the deployment locations of the master device and the slave devices. For example, the master device and the slave devices can both be deployed on the UE side or in the DN.

[0145] Based on the network architecture as Figure 4a shown, taking the EtherCAT network including four slave devices, with the master device deployed in the DN and the four slave devices located on the UE side as an example, two different network architectures applicable to the embodiments of the present application are introduced.

[0146] To clearly show the transmission path of data packets between the master device and the slave devices, Figure 4b and 4c only the connections between the UPF network element, the master device, and the slave devices are shown. The connection methods and deployment locations between other network elements can be referred to as Figure 4a .

[0147] See Figure 4b , there are connections between slave device 1, slave device 2 and slave device 3. Slave device 1 is respectively connected to two UEs, namely UE1 and UE2, and slave device 4 is connected to UE3.

[0148] The data transmission paths between the master device and slave device 1, slave device 2, slave device 3 and slave device 4 are marked with solid black arrows.

[0149] The data packet sent by the master device passes through the UPF network element. The UPF network element transmits the data packet to slave device 1 through the session of UE1. After being transmitted among slave device 1, slave device 2 and slave device 3, the data packet returns to slave device 1. Slave device 1 sends the data packet to UE2, and UE2 sends it to the UPF network element through the session of UE2. The UPF network element transmits the data packet to UE3 through the session of UE3. UE3 transmits the data packet to slave device 4, and then slave device 4 returns the data packet to UE3. UE3 sends the data packet to the UPF network element through the session of UE3. The UPF network element transmits the data packet to slave device 1 through the session of UE2. Slave device 1 returns the data packet to UE1, and UE1 returns the data packet to the master device through the session of UE1.

[0150] It should be noted that in the foregoing description, slave device 1 connecting two different UEs is taken as an example. In fact, slave device 1 can also be bound to two different sessions of the same UE, and the transmission path is similar to the foregoing description.

[0151] See Figure 4c , there are connections between slave device 1, slave device 2 and slave device 3. Slave device 1 is respectively connected to UE1, and slave device 4 is connected to UE3.

[0152] The data transmission paths between the master device and slave device 1, slave device 2, slave device 3 and slave device 4 are marked with solid black arrows.

[0153] The data packet sent by the master device passes through the UPF network element. The UPF network element transmits the data packet to slave device 1 through the session of UE1. After being transmitted among slave device 1, slave device 2 and slave device 3, the data packet returns to slave device 1. Slave device 1 sends the data packet to UE1, and UE1 sends it to the UPF network element through the session of UE1. The UPF network element transmits the data packet to UE3 through the session of UE3. UE3 transmits the data packet to slave device 4, and then slave device 4 returns the data packet to UE3. UE3 sends the data packet to the UPF network element through the session of UE3. The UPF network element returns the data packet to the master device.

[0154] Differentiated from the transmission path as Figure 4b shown, such asFigure 4c In the transmission path, the data packet fed back by the slave 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 be bound to multiple UEs or multiple sessions either.

[0155] Based on the network structure as Figure 4a shown, the communication method provided by the embodiments of the present application includes two parts, namely a forwarding rule configuration method and a data transmission method, which are introduced separately below:

[0156] (1). Forwarding rule configuration method.

[0157] In the embodiments of the present application, the session management network element can receive a first request from a terminal device or an application function network element, where the first request is used to indicate that the uplink flow of a first session is associated with a second session. The first request can be newly added request information or an existing request message, such as a session creation request or a session modification request. The following uses the first request from a terminal device and an application function network element as examples for illustration respectively.

[0158] (1). The first request comes from a first terminal device, and the first request is a first session creation request, and the first session creation request indicates that the uplink flow of the first session is associated with the second session.

[0159] As Figure 5 shown, a forwarding rule configuration method provided by the embodiments of the present application includes:

[0160] Step 501: The first terminal device sends a first session creation request to the session management network element. The first session request is used to request the creation of the first session and indicate that the uplink flow of the first session is associated with the second session.

[0161] The association relationship between the first session and the second session can be pre-configured in the first terminal device. When the first terminal device needs to create the first session, the first session creation request sent by the first terminal device to the session management network element not only requests the creation of the first session, but also indicates that the uplink flow of the first session is associated with the second session. The association between the uplink flow of the first session and the second session means that the uplink data received through the first session can be forwarded through the second session.

[0162] The present application does not limit the manner in which the first session creation request indicates the association between the uplink flow of the first session and the second session. For example, the identifier of the second session, such as the MAC address or IP address of the second session, is carried in the first session creation request. Another example is that a session association identifier is carried in the first session creation request, and the session association identifier can indicate the association between the uplink flow of the first session and the second session. Optionally, the first session creation request may further include the flow direction information of the first session, that is, the indication information of the uplink flow.

[0163] The session association identifier may be a group identifier. When the first terminal device requests to create a first session, that is, when sending a first session creation request, it may carry the group identifier. When the second terminal device sends a session creation request to the session management network element for requesting to create a second session, the session creation request may also carry the same group identifier.

[0164] When the session management network element receives session creation requests (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 may determine that there is an association relationship between the sessions of the first terminal device and the second terminal device.

[0165] Of course, the session association identifier may be a pre-agreed identifier. When the session management network element receives session creation requests (the first session creation request from the first terminal device and the session creation request from the second terminal device) carrying the same identifier, it may also determine that there is an association relationship between the sessions of the first terminal device and the second terminal device based on this identifier, and then determine that the uplink flow of the first session is associated with the second session.

[0166] 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. The first forwarding rule indicates that the uplink data packets from the first session are forwarded through the second session.

[0167] 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 for creating the first forwarding rule of the first session. After receiving the N4 session creation request, the user plane network element configures the first forwarding rule locally.

[0168] There are many ways for the first forwarding rule to indicate that the uplink data packets from the first session are forwarded through the second session. Several of them are listed below:

[0169] 1. The identifier of the second session. The identifier of the second session may be the N4 session identifier of the second session. After receiving the first forwarding rule including the identifier of the second session, the user plane network element may determine that the uplink flow of the first session is associated with the second session according to the identifier of the second session.

[0170] For the uplink flow of the first session, the first forwarding rule that the user plane network element may configure is that after receiving the uplink data (which may also be called uplink data packets) from the first session, the uplink data is sent through the second session.

[0171] 2. The session association identifier. For the session association identifier, refer to the foregoing description and it will not be elaborated here.

[0172] For the uplink of the first session, the first forwarding rule that the user plane network element can configure is to receive the uplink data from the first session and send the uplink data to the local forwarding module.

[0173] It should be noted that when the session association identifier is a group identifier, 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 is specifically to receive the uplink data from the first session and send the uplink data to the local forwarding module.

[0174] 3. General Packet Radio Service Tunnelling Protocol User Plane (GTP-U) identifier of the second session.

[0175] For the uplink of the first session, the first forwarding rule that the user plane network element can configure is to receive the uplink data from the first session, add the GTP-U identifier of the second session to the uplink data, and send the uplink data with the GTP-U identifier of the second session added to the local forwarding module.

[0176] After the session management network element configures the first forwarding rule in the user plane network element, the session management network element can send a first session creation response to the first terminal to indicate that the first session is successfully created, that is, the association between the first session uplink and the second session is established.

[0177] In the Figure 5 illustrated embodiment, the first session creation request requests the association between the first session uplink and the second session. In the same way, the first terminal device can also request the association between the first session downlink and other sessions. The first session downlink receives data from the data network, that is, the first session downlink is associated with the N6 interface of the user plane network element.

[0178] However, if both the uplink and downlink of the first session are bound to the second session, that is, the first session and the second session are associated, the following method can also be adopted. For details, see Figure 6 .

[0179] As Figure 6 shown in the embodiment provided by the present application, a forwarding rule configuration method includes:

[0180] Step 601: The first terminal device sends a first session creation request to the session management network element. The first session request is used to request the creation of the first session and indicate the association between the first session and the second session.

[0181] It should be noted that the association relationship 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 association relationship between the first session and the second session includes the association between the uplink flow of the first session and the second session, and the association between the downlink flow of the first session and the second session (i.e., the association between the downlink flow of the first session and the second session).

[0182] The indication method of the association between the first session and the second session is the same as the method of the association between the uplink flow of the first session and the second session. For specific details, please refer to the foregoing content and will not be elaborated here.

[0183] Step 602: After receiving the first session creation request, the session management network element configures a forwarding rule in the user plane network element. This forwarding rule indicates forwarding the uplink data packets from the first session through the second session (i.e., the first forwarding rule) and receiving the uplink data packets from the second session through the first session (which can be called the second forwarding rule). Similar to step 502, for specific details, please refer to the relevant description of step 502 and will not be elaborated here.

[0184] There are many ways to indicate the forwarding rule of the first session. Several of them are listed below:

[0185] 1. The identifier of the second session. The identifier of the second session can be the N4 session identifier of the second session. After receiving the first forwarding rule including the identifier of the second session, the user plane network element can determine the association between the uplink flow of the first session and the second session according to the identifier of the second session.

[0186] For the uplink flow of the first session, the forwarding rule (i.e., the first forwarding rule) that the user plane network element can configure is that after receiving the uplink data (which can also be called the uplink data packet) from the first session, the uplink data is sent through the second session.

[0187] For the downlink flow of the first session, the forwarding rule (i.e., the second forwarding rule) that the user plane network element can configure is that after receiving the uplink data from the second session, the uplink data is sent through the first session. For the configuration of the forwarding rule of the downlink flow of the first session, when creating the second session, this forwarding rule can be configured as the forwarding rule of the second session.

[0188] 2. Session association identifier. For the session association identifier, please refer to the foregoing description and will not be elaborated here.

[0189] For the uplink flow of the first session, the forwarding rule (i.e., the first forwarding rule) that the user plane network element can configure is to receive the uplink data from the first session and send the uplink data to the local forwarding module.

[0190] For the downlink of the first session, the local forwarding module matches data packets from the second session and sends the matched packets through the first session.

[0191] It should be noted that when the session association identifier is a group identifier, the user plane network element can configure the forwarding rules according to the existing group management method. That is, the forwarding rules configured by the user plane network element for the uplink of the first session are specifically to receive the uplink data from the first session and send the uplink data to the local forwarding module. The forwarding rules configured by the user plane network element for the downlink of the first session are specifically to match the data packets of the second terminal device belonging to the same group from the local forwarding module and send the matched packets through the first session of the first terminal device located in the same group.

[0192] 3. General Packet Radio Service Tunnelling Protocol User Plane (GTP-U) identifier of the second session.

[0193] For the uplink of the first session, the forwarding rules (i.e., the first forwarding rules) that the user plane network element can configure are to receive the uplink data from the first session, add the GTP-U identifier of the second session to the uplink data, and send the uplink data with the GTP-U identifier of the second session added to the local forwarding module.

[0194] For the downlink of the first session, the forwarding rules (i.e., the second forwarding rules) that the user plane network element can configure are to match the data packets including the GTP-U identifier of the first session from the forwarding module and send the packets through the second session.

[0195] After the session management network element configures the forwarding rules in the user plane network element, the session management network element can send a second session creation response to the first terminal to indicate that the creation of the first session is successful, that is, the association between the uplink of the first session and the second session is established.

[0196] Another expression for the association between the uplink of the first session and the second session is the association between the first session and the downlink of the second session. Therefore, it can also be in the way of indicating the downlink of the first session and the second session. For details, please refer to Figure 7 .

[0197] As Figure 7 shown is a forwarding rule configuration method provided by an embodiment of the present application. The method includes:

[0198] Step 701: The second terminal device sends a second session creation request to the session management network element. The second session request is used to request the creation of the second session and indicate the association between the first session and the downlink of the second session.

[0199] Step 702: After the session management network element receives the second session creation request, the session management network element may create a second session and configure a first forwarding rule in the user plane network element. The first forwarding rule indicates that the uplink data packets from the first session are forwarded through the second session. Similar to step 502, for specific details, please refer to the relevant description of step 502, which will not be elaborated here.

[0200] That is to say, the session management network element may trigger the user plane network element to create a first forwarding rule for the first session. As a possible implementation manner, the session management network element may also trigger the user plane network element to create a third forwarding rule for the second session. The third forwarding rule indicates that the uplink data packets from the first session are received through the second session.

[0201] After the session management network element configures the first forwarding rule in the user plane network element, the session management network element may send a second session creation response to the second terminal, which is used to indicate that the second session is successfully created, that is, the association between the first session uplink flow and the second session is established.

[0202] If, during data forwarding, the uplink data received from the second session needs to be forwarded through the first session, similar to the method shown in Figure 5 Figure 6, the second terminal device may send a third session creation request indicating the association between the first session and the second session uplink flow (or the association between the first session and the second session) to the session management network element. After receiving the third session creation request, the session management network element may configure a second forwarding rule for the second session in the user plane network element. The second forwarding rule indicates that the uplink data packets from the second session are forwarded through the first session.

[0203] The method of indicating the association between the first session and the second session uplink flow and the method of indicating the association between the first session and the second session are similar to the method of indicating the association between the first session uplink flow and the second session and the method of indicating the association between the first session and the second session in the embodiment shown in Figure 5 Figure 6. The difference is that the relevant information of the first session (such as the identifier of the first session, the GTP-U identifier, etc.) is carried here.

[0204] The method by which the session management network element configures the second forwarding rule for the second session in the user plane network element is similar to the method by which the session management network element configures the first forwarding rule for the first session in the user plane network element. For specific details, please refer to the foregoing content, which will not be elaborated here.

[0205] Of course, another way of expressing the association between the uplink of the first session and the second session is that the downlink of the first session is associated with the second session. Therefore, it is also possible to use the method of indicating the downlink of the first session and the second session, that is, the first terminal device can send a fourth session creation request to the session management network element. The fourth session creation request is used to request the creation of the first session and indicate the association between the second session and the downlink of the first session, so that the session management network element can create a second forwarding rule for the second session in the user plane network element. As a possible implementation, the session management network element can also trigger the user plane network element to create a fourth forwarding rule for the first session, and the fourth forwarding rule indicates receiving the uplink data packet from the second session through the first session.

[0206] In the above embodiments, only the case where the terminal device (the first terminal device and the second terminal device) sends a session creation request (the first session creation request, the second session creation request, the third session creation request or the fourth session creation request) is taken as an example for illustration. In fact, the terminal device can also send a session modification request to inform the session management network element of the association relationship between the first session and the second session. The specific process is similar to that of sending a session creation request and will not be elaborated here.

[0207] (2) The first request comes from the application function network element, and the first request is a first configuration request for configuring the first session.

[0208] Step 801: The application function network element sends a first configuration request to the session management network element. 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.

[0209] After the sessions of the first terminal device and the second terminal device are both created, the application network element can trigger the creation of the data stream in the first session, send a first configuration request, and further configure the first session.

[0210] The way that the first configuration 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 is similar to the way that 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. For specific details, please refer to the foregoing content and will not be elaborated here.

[0211] Step 802: After receiving the first configuration request, the session management network element configures a first forwarding rule in the user plane network element. The first forwarding rule indicates forwarding the uplink data packet from the first session through the second session. The same as step 501, for specific details, please refer to the relevant description of step 501 and will not be elaborated here.

[0212] In order to configure a second forwarding rule in the user plane network element, the application function network element can also send a second configuration request.

[0213] Step 803: The application function network element sends a second configuration request to the session management network element. The second configuration request is used to indicate that the uplink flow of the second session is associated with the first session or the first session is associated with the second session.

[0214] After the sessions of the first terminal device and the second terminal device are both created, the application network element can trigger the creation of data streams in the second session, send a second configuration request, and perform further configuration on the second session.

[0215] The manner in which the second configuration request indicates that the uplink flow of the second session is associated with the first session or the first session is associated with the second session is similar to the manner in which the third session creation request indicates that the uplink flow of the second session is associated with the first session or the first session is associated with the second session. For specific details, please refer to the foregoing content and will not be elaborated here.

[0216] 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 indicates that the uplink data packets from the second session are forwarded through the first session. For specific details, please refer to the foregoing description and will not be elaborated here.

[0217] It should be noted that if the first configuration request has indicated the association between the first session and the second session, steps 803 to 804 may not be executed either.

[0218] (2) Data transmission method.

[0219] After the first forwarding rule is configured in the user plane network element, the user plane network element can forward data according to the first forwarding rule or the second forwarding rule. As Figure 9 shown in the data transmission method provided by an embodiment of the present application, the method includes:

[0220] Step 901: The first terminal device sends a first uplink data packet through the first session.

[0221] Step 902: After receiving the first uplink data packet through the first session, the user plane network element can forward the first uplink data packet through the second session according to the first forwarding rule.

[0222] Step 903: The second terminal device receives the first uplink data packet through the second session.

[0223] If the uplink flow of the second session is associated with the second session, that is, the user plane network element configures a second forwarding rule, steps 904 to 906 can also be executed.

[0224] Step 904: The second terminal device sends a second uplink data packet through the second session.

[0225] Step 905: After receiving the second uplink data packet through the second session, the user plane network element can forward the second uplink data packet through the first session according to the second forwarding rule.

[0226] Step 906: The first terminal device receives the second uplink data packet through the first session.

[0227] From the above transmission process of the first uplink data packet, it can be seen that after receiving the first uplink data packet, the user plane network element can determine the session required to forward the uplink data packet based on the source of the first uplink data packet (the first session), that is, determine the terminal device (the second terminal device) that receives the first uplink data packet.

[0228] Next, based on the Figure 4b network architecture shown below, a forwarding rule configuration method and a data transmission method provided by an embodiment of the present application will be further described.

[0229] As Figure 10 shown, a forwarding rule configuration method and a data transmission method provided by an embodiment of the present application, where steps 1001 to 1005 are the forwarding rule configuration method, and steps 1006 to 1017 are the data transmission method.

[0230] Step 1001: The UPF network element configures the session corresponding to the N6 interface as the session of UE1, so that the UPF network element can directly forward data packets through the N6 interface and the session of UE1. The corresponding relationship between the N6 interface and the session can be pre-configured in the UPF network element, and the UPF network element can configure the session corresponding to the N6 interface according to this corresponding relationship.

[0231] Optionally, UE1 can 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 the session of UE1, and the fifth session creation / modification request can also indicate the data network name (DNN) associated with the session of UE1. The DN indicated by the DNN is associated with the N6 interface of the UPF network element.

[0232] 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.

[0233] Substantially, step 1001 configures the forwarding rule for data packets 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.

[0234] Step 1002: UE2 sends a sixth session creation / modification request to the SMF network element. This sixth session creation / modification request is used to request the creation of a session for UE2, and it can also indicate the association between the session of UE2 and the session of UE3.

[0235] The embodiments of this application do not limit the manner in which the sixth session creation / modification request indicates the association between the session of UE2 and the session of UE3. For example, the sixth session creation / modification request can indicate the association between the session of UE2 and the session of UE3 by carrying the identifier of the session of UE3, or by carrying the group identifier of the group where UE2 and UE3 are located, or by carrying a pre-agreed session association identifier to indicate the association between the session of UE2 and the session of UE3.

[0236] Step 1003: After receiving the sixth session creation / modification request, the SMF network element can send a first N4 session creation / modification request to the UPF network element to create / modify the forwarding rules for the session of UE2. This forwarding rule indicates that the uplink data packets of the session of UE2 are forwarded through the session of UE3.

[0237] This forwarding rule can be manifested in any of the following:

[0238] 1. For the uplink flow of the UE2 session, the uplink data (which can also be referred to as uplink data packets) received through the session of UE2 is sent to the session of UE3; for the downlink flow of the UE2 session, when configuring the forwarding rules for the session of UE3, it is configured to send the uplink data received through the session of UE3 to the session of UE2. This configuration process can be executed when creating / modifying the forwarding rules for the session of UE3.

[0239] 2. For the uplink flow of the UE2 session, after receiving the uplink data through the session of UE2, the uplink data is sent to the local forwarding module.

[0240] For the downlink flow of the UE2 session, data packets are matched from the local forwarding module, that is, the session association identifier or the identifier of the session of UE3 is matched, and the matched data packets are sent through the session of UE2.

[0241] 3. For the uplink flow of the UE2 session, after receiving the uplink data through the session of UE2, the GTP-U identifier of the session of UE3 is added to the uplink data, and then it is sent to the local forwarding module.

[0242] For the downlink flow of the UE2 session, data packets are matched from the local forwarding module, that is, the GTP-U identifier of the session of UE2 is matched, and the matched data packets are sent through the session of UE2.

[0243] 4. For the method of indicating the sessions of UE3 and the session association of UE2 through the group identifier, the forwarding rules can be configured in the existing group management manner. That is, after receiving the uplink data through the session of UE2, the uplink data is sent to the local forwarding module; and the data packets belonging to the same group as UE3 are matched from the local forwarding module, and the matched data packets are sent through the session of UE2.

[0244] In steps 1002 - 1003, the forwarding rules for the session of UE1 connected to the slave device 1 are essentially configured. That is, the slave device 1 can send data packets to UE3 (i.e., the slave device 4) through the session of UE2, and can also receive data packets from UE3 through the session of UE2.

[0245] Step 1004: UE3 sends a seventh session creation / modification request, which is used to request the creation / modification of the session of UE3. The sixth session creation / modification request can also indicate the association between the session of UE2 and the session of UE3. The indication method is the same as step 1002.

[0246] Step 1005: The SMF network element sends a second N4 session creation / modification request to the UPF network element to create / modify the forwarding rules for the session of UE3. The forwarding rules indicate that the data packets from the session of UE3 are forwarded through the session of UE2.

[0247] 1. For the uplink flow of the UE3 session, the uplink data (which can also be called uplink data packets) received through the session of UE3 is sent to the session of UE2.

[0248] 2. For the uplink flow of the UE3 session, after receiving the uplink data through the session of UE3, the uplink data is sent to the local forwarding module.

[0249] For the downlink flow of the UE3 session, data packets are matched from the local forwarding module, that is, the session association identifier or the identifier of the session of UE2 is matched, and the matched data packets are sent through the session of UE3.

[0250] 3. For the uplink flow of the UE3 session, after receiving the uplink data through the session of UE3, the GTP-U identifier of the session of UE2 is added to the uplink data, and then it is sent to the local forwarding module.

[0251] For the downlink flow of the UE3 session, data packets are matched from the local forwarding module, that is, the GTP-U identifier of the session of UE3 is matched, and the matched data packets are sent through the session of UE3.

[0252] 4. For the method of indicating the sessions of UE3 and the session association of UE2 through the group identifier, the forwarding rules can be configured in the existing group management manner. That is, after receiving the uplink data through the session of UE3, the uplink data is sent to the local forwarding module; and the data packets belonging to the same group as UE2 are matched from the local forwarding module, and the matched data packets are sent through the session of UE3.

[0253] In steps 1004 to 1005, the forwarding rules for the session of UE3 connected to the slave device 4 are substantially configured. That is, the slave device 4 can send data packets to UE2 (i.e., the slave device 1) through the session of UE3, and can also receive data packets from UE2 through the session of UE3.

[0254] It should be noted that in steps 1001 to 1005, UE1 to UE3 send session creation / modification requests to the SMF network element to indicate the association between sessions. As a possible implementation, the message indicating the association between sessions (i.e., the first request) between the session of UE2 and the session of UE3 can also be sent by the AF network element to the SMF network element. For example, the AF network element can send the first request to the PCF through the NEF network element (or the AF network element can 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. Another example is that the AF network element sends the first request to the SMF network element through the NEF (or the AF network element can also directly send the first request to the SMF network element).

[0255] The foregoing steps implement the configuration method of the forwarding rules. The data packet transmission process will be described below.

[0256] Step 1006: The master device sends the first packet to the UPF network element.

[0257] 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 interface and the session.

[0258] Step 1008: After receiving the first packet, UE1 sends the first packet to the slave device 1.

[0259] Step 1009: After receiving the first packet, the slave device 1 sends it to the slave device 2 and the slave device 3, and then the first packet is sent back to the slave device 1.

[0260] After receiving the first packet, the slave device 1, the slave device 2, and the slave device 3 can process the first packet.

[0261] Step 1010: Send the first message to the UPF network element through the session of UE2 from Device 1. That is, send the first message from Device 1 to UE2, and UE2 sends the first message to the UPF network element through the session of UE2.

[0262] Step 1011: The UPF network element sends the first message to UE3 through the session of UE3 associated with the session of UE2 according to the forwarding rule of the session of UE2.

[0263] Step 1012: After receiving the first message, UE3 sends the first message to Slave Device 4.

[0264] Step 1013: After receiving the first message, Slave Device 4 reads the first message and sends the first message back to the UPF network element through the session of UE3. That is, Slave Device 4 sends the first message to UE3, and UE3 sends the first message to the UPF network element through the session of UE3.

[0265] Step 1014: The UPF network element sends the first message 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.

[0266] Step 1015: UE2 sends the first message to Device 1.

[0267] Step 1016: After receiving the first message from UE2, Device 1 sends the first message back to the UPF network element through the session of UE1.

[0268] Step 1017: The UPF network element forwards the first message to the master device according to the correspondence between the session of UE1 and the N6 interface.

[0269] Next, based on the Figure 4c network architecture shown below, a forwarding rule configuration method and a data transmission method provided by an embodiment of the present application are further described.

[0270] As Figure 11 shown, a forwarding rule configuration method and a data transmission method provided by an embodiment of the present application, where steps 1101 to 1105 are the forwarding rule configuration method, and steps 1106 to 1114 are the data transmission method.

[0271] Step 1101: The UPF network element configures the session corresponding to the N6 interface. Specifically, the UPF configures the session corresponding to the upstream of the N6 interface as the session of UE1, and the session corresponding to the downstream of the N6 interface as the session of UE3.

[0272] In step 1101, the forwarding rules of data packets between the slave device 1 and the master device, and between the slave device 4 and the master device are essentially configured. That is, the master device sends data packets to UE1 through the session of UE1, so that the slave device 1 can obtain the data packets from UE1. The master device receives data packets from the slave device 4 through the session of UE3.

[0273] 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 can also indicate the DNN associated with the upstream flow of the session of UE1 and the association between the downstream flow of the session of UE1 and the session of UE3. Among them, the DN indicated by the DNN is associated with the N6 interface of the UPF network element.

[0274] The way that the eighth session creation / modification request indicates the association between the downstream flow of the session of UE1 and the session of UE3 is similar to the way that the sixth session creation / modification request can also indicate the association between the session of UE2 and the session of UE3. That is, the eighth session creation / modification request can indicate the association between the downstream flow of the session of UE1 and the session of UE3 by carrying the identifier of the session of UE3, carrying the group identifier of the group where UE1 and UE3 are located, or a pre-agreed session association identifier.

[0275] Step 1103: After receiving the eighth session creation / modification request, the SMF network element can send a third N4 session creation / modification request to the UPF network element to create / modify the forwarding rules for the upstream flow and the downstream flow of the session of UE1. The forwarding rule indicates that data packets from the session of UE2 are forwarded through the session of UE3.

[0276] The forwarding rule for the upstream flow of the session of UE1 indicates that the upstream data received through the session of UE1 is sent to the session of UE3. The configuration method of the forwarding rule for the upstream flow of the session of UE1 is similar to that of Figure 10 the forwarding rule for the upstream flow of the session of UE2 in, and specific details can be referred to the foregoing content and will not be elaborated here.

[0277] The forwarding rule for the downstream flow of the session of UE1 indicates that data packets are received from the N6 interface corresponding to the DNN.

[0278] 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 can also indicate the DNN associated with the upstream flow of the session of UE3 and the association between the downstream flow of the session of UE3 and the session of UE1. Among them, the DN indicated by the DNN is associated with the N6 interface of the UPF network element.

[0279] For the downlink of the session of UE3 in the ninth session creation / modification request, the association with the session of UE1 can be indicated by carrying the identifier of the session of UE1, carrying the group identifier of the group where UE1 and UE3 are located, or a pre-agreed session association identifier to indicate the association between the downlink of the session of UE1 and the session of UE3.

[0280] Step 1105: After receiving the ninth session creation / modification request, the SMF network element may send a fourth N4 session creation / modification request to the UPF network element to create / modify the forwarding rules for the uplink and downlink of the session of UE3.

[0281] The forwarding rule for the downlink of the session of UE3 indicates that the uplink data received through the session of UE1 is sent to the session of UE3. The configuration method of the forwarding rule for the downlink of the session of UE3 is similar to that of the forwarding rule for the downlink of the session of UE2 in Figure 10 and can specifically refer to the foregoing content, which will not be elaborated here.

[0282] The forwarding rule for the uplink of the session of UE3 indicates sending data packets to the N6 interface corresponding to the DNN.

[0283] In steps 1102 to 1105, essentially, the forwarding rules for data packets between the slave device 1 and the master device, and between the slave device 1 and the slave device 4 are configured. That is, the master device sends data packets to UE1 through the session of UE1, so that the slave device 1 can obtain the data packets from UE1. The slave device 1 sends data packets to UE3 through the session of UE1, and the slave device 4 receives the data packets and sends the data packets to the master device through the session of UE3.

[0284] It should be noted that if the eighth session creation / modification request in step 1102 indicates the DNN associated with the downlink of the session of UE1 and the ninth session creation / modification request in step 1104 indicates the DNN associated with the uplink of the session of UE3, step 1101 may not be executed.

[0285] The foregoing steps implement the configuration method of the forwarding rules. The following describes the data packet transmission process.

[0286] Step 1106: The master device sends a second packet to the UPF network element.

[0287] 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 session of UE1. That is, the second packet is sent to UE1.

[0288] Step 1108: After receiving the second packet, UE1 sends the second packet to the slave device 1.

[0289] Step 1109: After receiving the second message from Device 1, it is sent to subsequent Slave Device 2 and Slave Device 3 for processing the second message. After that, the processed second message is sent back to Slave Device 1.

[0290] Step 1110: Slave Device 1 sends the processed second message to the UPF network element through the session of UE1.

[0291] Step 1111: The UPF network element sends the processed second message to the session of UE3 according to the forwarding rule of the uplink flow of the session of UE1. That is, the second message is sent to UE3.

[0292] Step 1112: After receiving the processed second message, UE3 sends the processed second message to Slave Device 4.

[0293] Step 1113: After receiving the processed second message, Slave Device 4 processes the processed second message again (for convenience of description, the second processed message is used to represent the second message processed by Slave Device 4 here), and sends the processed second processed message back to the UPF network element through the session of UE3.

[0294] Step 1114: The UPF forwards the second processed message to the master device according to the correspondence between the uplink flow of the session of UE3 and the N6 interface.

[0295] Next, based on the network architecture as Figure 4c shown, a forwarding rule configuration method and a data transmission method provided by an embodiment of the present application are further described.

[0296] As Figure 12 shown, a forwarding rule configuration method and a data transmission method provided by an embodiment of the present application, where Steps 1201 to 1205 are the forwarding rule configuration method, and Steps 1206 to 1224 are the data transmission method.

[0297] Step 1201: It is the same as Step 1101. For specific details, please refer to the foregoing description and will not be elaborated here.

[0298] Step 1202: It is the same as Step 1102. For specific details, please refer to the foregoing description and will not be elaborated here.

[0299] It should be noted that the eighth session creation / modification request may also indicate the address of the slave device associated with UE1. The embodiment of the present application does not limit the manner of indicating the address of Slave Device 1. The following lists two ways:

[0300] Way 1: For the way that the slave device uses the self-incrementing address for addressing.

[0301] The eighth session creation / modification request includes the starting serial number of the incremental address of the slave devices associated with UE1. Optionally, it can also indicate the number of slave devices (slave device 1, slave device 2, and slave device 3) associated with UE1. In the embodiment of this application, the number of slave devices associated with UE1 is 3.

[0302] The starting serial number of the incremental address of the slave devices associated with UE1 is the serial number of the sub-incremental address of slave device 1. Since slave device 1 is the first slave device to receive the EtherCAT message among all slave devices, the starting serial number carried in the eighth session creation / modification request is 0.

[0303] Method 2: For the slave devices using fixed addresses or logical addresses.

[0304] The eighth session creation / modification request includes the fixed address or logical address of the slave devices associated with UE1.

[0305] Step 1203: The same as step 1103. For specific details, please refer to the foregoing description and will not be elaborated here.

[0306] It should be noted that in this step, the SMF network element can also send the starting serial number, fixed address, or logical address of the incremental address of the slave devices associated with UE1 to the UPF network element. That is to say, the third N4 session creation / modification request can also carry the starting serial number, fixed address, or logical address of the incremental address of the slave devices associated with UE1 sent by the UPF network element.

[0307] Step 1204: The same as step 1104. For specific details, please refer to the foregoing description and will not be elaborated here.

[0308] It should be noted that the ninth session creation / modification request can also indicate the addresses of the slave devices associated with UE3. The embodiment of this application does not limit the method of indicating the address of slave device 4. Two methods are listed below:

[0309] Method 1: For the slave devices using incremental addresses for addressing.

[0310] The ninth session creation / modification request includes the starting serial number of the incremental address of the slave devices associated with UE3. Optionally, it can also indicate the number of slave devices (slave device 4) associated with UE3. In the embodiment of this application, the number of slave devices associated with UE3 is 1.

[0311] The starting serial number of the incremental address of the slave devices associated with UE3 is the serial number of the sub-incremental address of slave device 4. Since slave device 4 is the fourth slave device to receive the EtherCAT message among all slave devices, the starting serial number carried in the ninth session creation / modification request is 3.

[0312] Method 2: The method for the slave device to use a fixed address or a logical address.

[0313] The ninth session creation / modification request includes the fixed address or the logical address of the slave device associated with UE3.

[0314] Step 1205: The same as Step 1105. For specific details, please refer to the foregoing description and will not be elaborated here.

[0315] It should be noted that in this step, the SMF network element can also send the starting sequence number, fixed address or logical address of the 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 can also carry the starting sequence number, fixed address or logical address of the incremental address of the slave device associated with UE3 sent by the UPF network element.

[0316] Next, the forwarding process of the data packet by the UPF network element when the slave device uses the incremental address addressing method to determine the sub-packet.

[0317] Step 1206: The UPF network element receives the third packet from the master device through the N6 interface corresponding to the DNN.

[0318] Step 1207: The UPF network element determines the first sub-packet in the third packet according to the starting sequence number of the incremental address of the slave device associated with UE1, and forwards the determined first sub-packet to the session of UE1. The number of the first sub-packets is not limited here, and it can be one or multiple.

[0319] Since the starting sequence number of the incremental address of the slave device associated with UE1 is 0, the UPF network element can extract the sub-packets in the third packet whose incremental addresses of the slave device are sorted after 0 and 0, encapsulate the extracted sub-packets, and forward the encapsulated sub-packets through the session of UE1. The sub-packets extracted here can also include all the sub-packets in the third packet, that is, the third packet can be directly forwarded.

[0320] Optionally, the UPF extracts three sub-packets corresponding to slave device 1, slave device 2, and slave device 3 in the third packet according to the number of slave devices associated with UE1 and the starting sequence number of the incremental address, encapsulates the three sub-packets, and forwards the encapsulated sub-packets to the session of UE1.

[0321] It should be noted that when the slave device performs self-increment address addressing, the EtherCAT network can assign fixed addresses to each slave device, and the UPF network element can record the fixed addresses of each slave device for subsequent forwarding of data packets. As a possible implementation, the fixed addresses of each slave device saved by the UPF network element can also be sent by the SMF network element to the UPF network element after the UE1 and UE3 (or AF network element) send the fixed addresses of the associated slave devices to the SMF network element.

[0322] Step 1208: The UPF network element sends the first sub-packet to UE1 through the session of UE1.

[0323] Step 1209: After receiving the first sub-packet, UE1 sends the first sub-packet to slave device 1.

[0324] Step 1210: After receiving the first sub-packet, slave device 1 processes the first sub-packet and sends the processed first sub-packet to subsequent slave device 2 and slave device 3. For the convenience of explanation, here the first processed sub-packet is used to represent the first sub-packet after being processed by slave device 3), and then the first processed sub-packet is sent back to slave device 1.

[0325] Step 1211: Slave device 1 sends the first processed sub-packet to the UPF network element through the session of UE1.

[0326] Step 1212: The UPF network element determines the second sub-packet corresponding to the slave device associated with UE3 according to the starting serial number of the sub-increment address of the slave device associated with UE3, encapsulates the extracted second sub-packet, and sends the encapsulated second sub-packet through the session of UE3.

[0327] Optionally, the UPF network element adds 3 to the address of the self-increment address in each sub-packet of the third packet and sends it to session 3, the session sent to UE3.

[0328] Step 1213: After receiving the encapsulated second sub-packet, UE3 sends the second sub-packet to slave device 4.

[0329] Step 1214: After receiving the second sub-packet, the processed second sub-packet (for the convenience of explanation, here the second processed sub-packet is used to represent the second packet after being processed by slave device 4) sends the processed second processed sub-packet back to the UPF network element through the session of UE3.

[0330] Step 1215: After receiving the first processed sub-packet and the second processed sub-packet, the UPF network element merges the first processed sub-packet and the second processed sub-packet into the same packet and sends the packet to the master device through the N6 interface associated with the upstream flow of the session of UE3.

[0331] The UPF network element can identify whether a sub - message has been processed so that it can send the processed sub - message to the slave device. The following lists two identification methods.

[0332] 1. The UPF saves the third message. After receiving the first processed sub - message and the second processed sub - message, it compares the first sub - message and the second sub - message in the third message with the first processed sub - message and the second processed sub - message. According to the comparison result, it determines whether the first sub - message and the second sub - message have been modified, replaces the corresponding sub - messages in the third message with the modified sub - messages, and sends the third message with the replaced sub - messages to the master device.

[0333] 2. Each sub - message in the third message includes a read - write flag. If the slave device modifies a sub - message, it can change this read - write flag, and the changed read - write flag can indicate that the sub - message has been modified.

[0334] After receiving the first processed sub - message and the second processed sub - message, the UPF network element can determine whether a sub - message has been modified according to the read - write flag in the sub - message. Further, it combines the modified sub - messages into one message and sends this message to the master device.

[0335] The following describes the forwarding process of data messages by the UPF network element when the slave device determines sub - messages by using the fixed - address or logical - address addressing method.

[0336] Step 1216: The UPF network element receives the fourth message from the master device through the N6 interface corresponding to the DNN.

[0337] Step 1217: The UPF network element sends the fourth message according to the session of UE1 associated with the N6 - side interface.

[0338] Optionally, the UPF network element can extract the third sub - message according to the fixed address (or logical address) of the slave device associated with UE1, and forward the determined third sub - message to the session of UE1. There is no limit to the number of third sub - messages, which can be one or multiple.

[0339] Step 1218: After receiving the third sub - message, UE1 sends the third sub - message to slave device 1.

[0340] Step 1219: After receiving the third sub - message, slave device 1 processes the third sub - message and sends the processed third sub - message to subsequent slave device 2 and slave device 3. For the convenience of explanation, here the third processed sub - message is used to represent the third sub - message processed by slave device 3. After that, the third processed sub - message is sent back to slave device 1.

[0341] Step 1220: Slave device 1 sends the third processed sub - message to the UPF network element through the session of UE1.

[0342] Step 1221: The UPF network element sends a fourth message according to the session of UE4 associated with the N6 interface.

[0343] Optionally, the UPF extracts a 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. There is no limit to the number of fourth sub-messages, which can be one or multiple.

[0344] Step 1222: After receiving the encapsulated fourth sub-message, UE3 sends the fourth sub-message to the slave device 4.

[0345] Step 1223: After receiving the fourth sub-message, the slave device 4 sends the processed fourth sub-message (for ease of explanation, here the fourth processed sub-message is used to represent the fourth sub-message processed by the slave device 4) back to the UPF network element through the session of UE3.

[0346] Step 1224: After receiving the first processed sub-message and the fourth processed sub-message, the UPF network element merges the first processed sub-message and the fourth processed sub-message into the same message, and sends the message to the master device through the N6 interface associated with the upstream flow of the session of UE3.

[0347] Based on the same inventive concept as the method embodiment, the embodiment of the present application also provides a communication device for executing the method executed by the UPF network element in the method embodiment as described above Figures 5 to 12 shown. For related features, reference can be made to the above method embodiment, which will not be elaborated here. As Figure 13 shown, a communication device provided by the present application includes a receiving unit 1301 and a sending unit 1302:

[0348] The receiving unit 1301 is configured to receive a first uplink data message through a first session;

[0349] The sending unit 1302 is configured to forward the first uplink data message through a second session according to a first forwarding rule, where the first forwarding rule indicates forwarding the uplink data message from the first session through the second session.

[0350] In a possible implementation manner, the receiving unit 1301 is further configured to receive a second uplink data message through the second session;

[0351] The sending unit 1302 is further configured to forward the second uplink data message through the first session according to a second forwarding rule, where the second forwarding rule indicates forwarding the uplink data message from the second session through the first session.

[0352] In a possible implementation, before the sending unit 1302 receives the first uplink data packet through the first session, the receiving unit 1301 receives the first forwarding rule from the session management network element.

[0353] In a possible implementation, before the sending unit receives the second uplink data packet through the second session, the receiving unit 1301 receives the second forwarding rule from the session management network element.

[0354] In a possible implementation, the first forwarding rule is the forwarding rule of the first session, and the first forwarding rule includes some or all of the following:

[0355] 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.

[0356] In a possible implementation, the second forwarding rule is the forwarding rule of the second session, and the second forwarding rule includes some or all of the following:

[0357] The identifier of the first session, the session association identifier, or the GTP-U identifier of the first session, where the session association identifier indicates that the first session is associated with the second session.

[0358] Based on the same inventive concept as the method embodiment, an embodiment of the present application further provides a communication device for executing the method executed by the SMF network element in the method embodiment as shown above Figures 5 to 12 The relevant features can be referred to the above method embodiment and will not be elaborated here. As shown in Figure 14 A communication device provided by the present application includes a receiving unit 1401 and a processing unit 1402:

[0359] The receiving unit 1401 is configured to receive a first request, where the first request is used to indicate that the uplink flow of the first session is associated with the second session;

[0360] The processing unit 1402 is configured to configure a first forwarding rule in the user plane network element, where the first forwarding rule indicates forwarding the uplink data packet from the first session through the second session.

[0361] In a possible implementation, the receiving unit 1401 receives the first request and the types of the first request are as follows:

[0362] Receive a first session creation (or modification) request from the first terminal device, where the first session creation (or modification) request is used to request to create (or modify) the first session and indicate that the uplink flow of the first session is associated with the second session.

[0363] Receive a first session creation (or modification) request from a first terminal device, where the first session creation (or modification) request is further used to indicate that the uplink flow of the first session is associated with a second session or the first session is associated with the second session.

[0364] Receive a second session creation (or modification) request from a second terminal device, where the second session creation request is used to request the creation of a second session and indicate that the downlink flow of the first session is associated with the second session.

[0365] Receive a first configuration request from an application function network element, where the first configuration request is used to configure the first session, and the first configuration request is further used to indicate that the uplink flow of the first session is associated with a second session or the first session is associated with the second session.

[0366] In a possible implementation, the receiving unit 1401 may further receive a second request, where the second request is used to request the creation of a second session and indicate that the uplink flow of the second session is associated with the first session;

[0367] The processing unit 1402 may configure a second forwarding rule in the user plane network element, where the second forwarding rule indicates forwarding the uplink data packets from the second session through the first session.

[0368] In a possible implementation, the receiving unit 1401 receives the second request and the types of the second request are as follows:

[0369] Receive a third session creation (or modification) request from a second terminal device, where the third session creation (or modification) request is used to request the creation of a second session and indicate that the uplink flow of the second session is associated with the first session, and the third session creation request is further used to indicate that the uplink flow of the second session is associated with the first session or the first session is associated with the second session.

[0370] Receive a second configuration request from an application function network element, where the second configuration request is used to configure the second session, and the second configuration request is further used to indicate that the uplink flow of the second session is associated with the first session or the first session is associated with the second session.

[0371] In a possible implementation, 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 a session association identifier, where the session association identifier indicates that the first session is associated with the second session;

[0372] The second session creation (or modification) request includes some or all of the following:

[0373] The identifier of the first session or a session association identifier.

[0374] In a possible implementation, 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, where the session association identifier indicates that the first session is associated with the second session.

[0375] In a possible implementation, the first forwarding rule is the forwarding rule for the first session, and the first forwarding rule includes some or all of the following:

[0376] 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.

[0377] In a possible implementation, the second forwarding rule is the forwarding rule for the second session, and the second forwarding rule includes some or all of the following:

[0378] The identifier of the first session, the session association identifier, or the GTP-U identifier of the first session, where the session association identifier indicates that the first session is associated with the second session.

[0379] Based on the same inventive concept as the method embodiment, an embodiment of the present application further provides a communication device for executing the method performed by the first terminal device or UE2 in the method embodiment as described above. For related features, reference can be made to the above method embodiment, which will not be elaborated here. As Figures 5 to 12 shown, a communication device provided by the present application includes a sending unit 1501 and a receiving unit 1502. Figure 15 The sending unit 1501 is configured to send a first session creation (or modification) request to a 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) request is further used to indicate that the uplink flow of the first session is associated with the second session or the first session is associated with the second session;

[0380] 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 creation (or modification) of the first session is successful;

[0381] The sending unit 1501 is further configured to send a first uplink data packet through the first session after the receiving unit receives the first session creation (or modification) response.

[0382]

[0383] In a possible implementation, the first session creation request includes the identifier of the second session or the session association identifier, where the session association identifier indicates that the first session is associated with the second session.

[0384] ​Based on the same inventive concept as the method embodiment, the embodiment of the present application also provides a communication device for executing the above-mentioned Figures 7 to 12 The method executed by the second terminal device in the method embodiment shown, the relevant features can be found in the above method embodiment, and will not be repeated here, such as Figure 16 As shown, a communication device provided by the present application includes a sending unit 1601 and a receiving unit 1602.

[0385] The sending unit 1601 is used 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 to create a second session and indicate that a downlink flow of the second session is associated with the first session;

[0386] The receiving unit 1602 is configured to receive a second session creation (or modification) response from the session management network element, wherein the third session creation response indicates that the second session is successfully created;

[0387] The sending unit 1601 is further configured to receive a first uplink data message through the second session after the receiving unit receives a second session creation (or modification) response.

[0388] In a possible implementation, 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.

[0389] Based on the same inventive concept as the method embodiment, the embodiment of the present application further provides a communication device for executing the method executed by the second terminal device in the above method embodiment. The relevant features can be found in the above method embodiment and will not be repeated here. Figure 17 As shown, a communication device provided by the present application includes a sending unit 1701 and a receiving unit 1702:

[0390] A sending unit 1601 is configured to send a third session creation (or modification) request to a session management network element, where the third session request is used to request creation (or modification) of a second session, and the third session creation request is further used to indicate that an upstream of the second session is associated with the first session or that the first session is associated with the second session;

[0391] The receiving unit 1602 is configured to receive a third session creation (or modification) response from the session management network element, where the third session creation (or modification) response indicates that the second session is successfully created (or modified);

[0392] The sending unit 1601 is further configured to send a second uplink data message through the second session after the receiving unit receives a third session creation (or modification) response.

[0393] In a possible implementation, the third session creation (or modification) request includes an identifier of the first session or a session association identifier, where the session association identifier indicates that the first session is associated with the second session. Optionally, the third session creation (or modification) request may further carry indication information of the uplink flow, such as the flow direction information of the session.

[0394] Based on the same inventive concept as the method embodiment, an embodiment of the present application further provides a communication device for executing the method performed by the second terminal device or UE3 in the method embodiment as Figures 8 to 12 shown. For related features, reference may be made to the above method embodiment, which will not be elaborated here. As Figure 17 shown, a communication device provided in the present application includes a sending unit 1701 and a receiving unit 1702.

[0395] The sending unit 1701 is configured to send a third session creation (or modification) request to a session management network element, where the third session creation (or modification) request is used to request the creation (or modification) of a second session. The third session creation (or modification) request is further used to indicate that the uplink flow of the second session is associated with the first session or the first session is associated with the second session;

[0396] The receiving unit 1702 is configured to receive a third session creation (or modification) response from the session management network element, where the third session creation (or modification) response indicates that the creation (or modification) of the second session is successful;

[0397] The sending unit 1701 is configured to send a second uplink data packet through the second session after the receiving unit receives the third session creation (or modification) response.

[0398] In a possible implementation, the third session creation (or modification) request includes an identifier of the first session or a session association identifier, where the session association identifier indicates that the first session is associated with the second session.

[0399] The division of units in the embodiments of the present application is illustrative. It is only a logical function division. In actual implementation, there may be other division methods. In addition, in each embodiment of the present application, each functional unit may be integrated in one processor, may exist separately physically, or two or more units may be integrated in one module. The above integrated units may be implemented in the form of hardware or in the form of software functional modules.

[0400] When 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. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a terminal device (which can 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 various embodiments of this application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs.

[0401] In the embodiments of this application, the session management network element, the user plane network element, the first terminal device, and the second terminal device can all be presented in the form of dividing each functional module in an integrated manner. Here, a "module" can refer to a specific ASIC, circuit, a processor and a memory that execute one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions.

[0402] In a simple embodiment, those skilled in the art can conceive that the functions of the session management network element and the user plane network element can be adopted Figure 18 in the form shown.

[0403] Such as Figure 18 the communication device 1800 shown, which includes at least one processor 1801, a memory 1802, and optionally, a communication interface 1803 can also be included.

[0404] The processor 1801 can be a central processing unit, and the memory 1802 can be a volatile memory, such as a random access memory; the memory can also be a non-volatile memory, such as a read-only memory, a flash memory, a hard disk drive (HDD), or a solid-state drive (SSD), or the memory 1802 is any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1802 can be a combination of the above memories.

[0405] In the embodiments of the present application, the specific connection medium between the above-mentioned processor 1801 and the memory 1802 is not limited. In the embodiments of the present application, in the figure, the memory 1802 and the processor 1801 are connected through a bus 1804. The bus 1804 is represented by a thick line in the figure. The connection manners between other components are only for illustrative purposes and are not limiting. The bus 1804 can be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, Figure 18 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0406] The processor 1801 may have a data transceiver function and be able to communicate with other devices. In a device such as Figure 18 , an independent data transceiver module may also be provided, such as a communication interface 1803, for receiving and transmitting data. When the processor 1801 communicates with other devices, data transmission can be performed through the communication interface 1803.

[0407] When the user plane network element adopts the Figure 18 shown form, Figure 18 the processor 1801 in it can call the computer-executable instructions stored in the memory 1802, so that the user plane network element can execute the method executed by the user plane network element in any of the above method embodiments.

[0408] Specifically, Figure 13 the functions / implementation processes of the receiving unit and the sending unit in it can all be implemented by the processor 1801 in Figure 18 calling the computer-executable instructions stored in the memory 1802. Figure 14 The functions / implementation processes of the receiving unit and the sending unit of Figure 18 can be implemented through the communication interface 1803 in

[0409] When the session management network element adopts the Figure 18 shown form, Figure 18 the processor 1801 in it can call the computer-executable instructions stored in the memory 1802, so that the session management network element can execute the method executed by the session management network element in any of the above method embodiments.

[0410] Specifically, Figure 14 the functions / implementation processes of the receiving unit and the processing unit in it can all be implemented by the processor 1801 in Figure 18 calling the computer-executable instructions stored in the memory 1802. Or, Figure 14 the function / implementation process of the processing unit in Figure 18 can be implemented by the processor 1801 inFigure 14 The function / implementation process of the receiving unit can be achieved through Figure 18 the communication interface 1803 in

[0411] In a simple embodiment, those skilled in the art can conceive that the functions of the first terminal device and the second terminal device can adopt Figure 19 the form shown.

[0412] Such as Figure 19 the communication device 1900 shown, which includes at least one processor 1901, a memory 1902. Optionally, a transceiver 1903 may also be included.

[0413] The processor 1901 and the memory 1902 are similar to the processor 1801 and the memory 1802. For details, reference can be made to the foregoing description and will not be elaborated here.

[0414] In the embodiments of the present application, the specific connection medium between the above-mentioned processor 1901 and the memory 1902 is not limited. In the embodiments of the present application, in the figure, the memory 1902 and the processor 1901 are connected through a bus 1904. The bus 1904 is represented by a thick line in the figure. The connection manners between other components are only for illustrative purposes and are not restrictive. This bus 1904 can be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience of representation, Figure 19 only one thick line is used in

[0415] The processor 1901 may have a data transceiver function and be capable of communicating with other devices. In a device such as Figure 19 a separate data transceiver module, such as the transceiver 1903, may also be provided for data transmission and reception; when the processor 1901 communicates with other devices, data transmission can be performed through the transceiver 1903.

[0416] When the first terminal device adopts Figure 19 the form shown, Figure 19 the processor 1901 in

[0417] Specifically, Figure 15 the functions / implementation processes of the sending unit and the receiving unit in Figure 19 can all be achieved by the processor 1901 in Figure 15 calling the computer-executable instructions stored in the memory 1902. Figure 16 The functions / implementation processes of the sending unit and the receiving unit of Figure 19It is implemented by the transceiver 1903 in

[0418] When the second terminal device adopts Figure 19 the form shown, Figure 19 the processor 1901 in

[0419] Specifically, Figure 16 and Figure 17 the functions / implementation processes of the sending unit and receiving unit in Figure 19 can all be implemented by the processor 1901 in Figure 16 and Figure 17 The functions / implementation processes of the sending unit and receiving unit of Figure 19 can be implemented by the transceiver 1903 in

[0420] Those skilled in the art should understand that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program code.

[0421] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram can be implemented by computer program instructions, and the combination of the flows and / or blocks in the flowchart and / or block diagram can also be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the specified functions in Figure 1 one or more of the flows Figure 1 or multiple flows and / or blocks

[0422] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including instruction means, and the instruction means implements the specified functions in Figure 1 one or more of the flows Figure 1 or multiple flows and / or blocks

[0423] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus, so that a series of operation steps are executed on the computer or other programmable apparatus to produce a computer-implemented process, thereby the instructions executed on the computer or other programmable apparatus provide steps for realizing the functions specified in one process or a plurality of processes and / or one block or a plurality of blocks. Figure 1 one process or a plurality of processes and / or Figure 1 one block or a plurality of blocks.

[0424] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to cover these changes and modifications.

Claims

1. A communication method, characterized in that, the method includes: The user plane network element receives a first uplink data packet through a first session; the first uplink data packet is an EtherCAT data packet of Ethernet Control Automation Technology; The user plane network element forwards the first uplink data packet through a second session according to a first forwarding rule, wherein the first forwarding rule indicates to forward the uplink EtherCAT data packet from the first session through the second session; Wherein, the first forwarding rule is the forwarding rule of the first session, and the first forwarding rule includes part or all of the following: The identifier of the second session or the GTP-U identifier of the General Packet Radio Service Tunnel Protocol user plane of the second session.

2. The method according to claim 1, characterized in that, the method further includes: The user plane network element receives a second uplink data packet through the second session; The user plane network element forwards the second uplink data packet through the first session according to a second forwarding rule, wherein the second forwarding rule indicates to forward the uplink data packet from the second session through the first session.

3. The method according to claim 1 or 2, characterized in that, before the user plane network element receives the first uplink data packet through the first session, it further includes: The user plane network element receives the first forwarding rule from the session management network element.

4. The method according to claim 2, characterized in that, before the user plane network element receives the second uplink data packet through the second session, it further includes: The user plane network element receives the second forwarding rule from the session management network element.

5. The method according to claim 2 or 4, characterized in that, the second forwarding rule is the forwarding rule of the second session, and the second forwarding rule includes part or all of the following: The identifier of the first session or the GTP-U identifier of the General Packet Radio Service Tunnel Protocol user plane of the first session.

6. A communication method, characterized in that, the method includes: Sending a first session creation request to the session management network element, the first session creation request is used to request the creation of a first session, and the first session creation request is also used to indicate that the uplink flow of the first session is associated with a second session; After receiving a first session creation response from the session management network element, sending a first uplink data packet through the first session, the first session creation response indicates that the first session is successfully created; Wherein, the first session creation request includes the identifier of the second session; the first uplink data packet is an EtherCAT data packet of Ethernet Control Automation Technology.

7. A communication method, characterized in that, the method includes: Sending a second session creation request to the session management network element, the second session creation request is used to request the creation of a second session and indicate that the downlink flow of the second session is associated with the first session; After receiving a second session creation response from the session management network element, receiving a first uplink data packet through the second session, the second session creation response indicates that the second session is successfully created; Wherein, the second session creation request includes the identifier of the first session; the first uplink data packet is an EtherCAT (Ethernet Control Automation Technology) data packet.

8. A communication method, characterized in that the method includes: A session management network element receives a first request, where the first request is used to indicate that the uplink flow of a first session is associated with a second session; The session management network element configures a first forwarding rule in a user plane network element, where the first forwarding rule indicates that uplink data packets from the first session are forwarded through the second session; the uplink data packet is an EtherCAT data packet; Wherein, 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 or the GTP-U (General Packet Radio Service Tunneling Protocol User Plane) identifier of the second session.

9. The method according to claim 8, characterized in that the session management network element receiving the first request includes: The session management network element receives a first session creation request from a first terminal device, where the first session creation request is used to request the creation of a first session, and the first session creation request is further used to indicate that the uplink flow of the first session is associated with a second session; or the session management network element receives a second session creation request from a second terminal device, where the second session creation request is used to request the creation of a second session and to indicate the association between the downlink flow of the first session and the second session; or the session management network element receives a first configuration request from an application function network element, where the first configuration request is used to configure the first session, and the first configuration request is further used to indicate that the uplink flow of the first session is associated with a second session.

10. The method according to claim 8 or 9, characterized in that the method further includes: The session management network element receives a second request, where the second request is used to request the creation of a second session and to indicate that the uplink flow of the second session is associated with the first session; The session management network element configures a second forwarding rule in the user plane network element, where the second forwarding rule indicates that uplink data packets from the second session are forwarded through the first session.

11. The method according to claim 10, characterized in that the session management network element receiving the second request includes: The session management network element receives a third session creation request from a second terminal device, where the third session creation request is used to request the creation of a second session, and the third session creation request is further used to indicate that the uplink flow of the second session is associated with the first session; or the session management network element receives a second configuration request from an application function network element, where the second configuration request is used to configure the second session, and the second configuration request is further used to indicate that the uplink flow of the second session is associated with the first session.

12. The method according to claim 9, characterized in that the first session creation request and the first configuration request include: the identifier of the second session; the second session creation request includes: the identifier of the first session.

13. The method according to claim 11, characterized in that The third session creation request and the second configuration request include: The identifier of the first session.

14. The method according to claim 10, characterized in that 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 identifier of the first session or the General Packet Radio Service Tunneling Protocol User Plane (GTP-U) identifier of the first session.

15. A communication device, characterized in that The device includes a receiving unit and a transmitting unit: The receiving unit is used to receive a first uplink data packet through a first session; the first uplink data packet is an EtherCAT data packet of Ethernet Control Automation Technology; The transmitting unit is used to forward the first uplink data packet through a second session according to a first forwarding rule, wherein the first forwarding rule indicates to forward the uplink EtherCAT data packet from the first session through the second session; Wherein, 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 or the General Packet Radio Service Tunneling Protocol User Plane (GTP-U) identifier of the second session.

16. The device according to claim 15, characterized in that The receiving unit is further used to receive a second uplink data packet through the second session; The transmitting unit is further used to forward the second uplink data packet through the first session according to a second forwarding rule, wherein the second forwarding rule indicates to forward the uplink data packet from the second session through the first session.

17. The device according to claim 15 or 16, characterized in that Before the transmitting unit receives the first uplink data packet through the first session, the receiving unit is further used to: Receive the first forwarding rule from the session management network element.

18. The device according to claim 16, characterized in that Before the transmitting unit receives the second uplink data packet through the second session, the receiving unit is further used to: Receive the second forwarding rule from the session management network element.

19. The device according to claim 16 or 18, characterized in that 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 identifier of the first session or the General Packet Radio Service Tunneling Protocol User Plane (GTP-U) identifier of the first session.

20. A communication device, characterized in that The device includes a transmitting unit and a receiving unit: The transmitting unit is used to send a first session creation request to the session management network element, the first session creation request is used to request the creation of a first session, and the first session creation request is further used to indicate that the uplink flow of the first session is associated with a second session; The receiving unit is used to receive a first session creation response from the session management network element, and the first session creation response indicates that the first session is successfully created; The transmitting unit is further used to send a first uplink data packet through the first session after the receiving unit receives the first session creation response. Wherein, the first session creation request includes the identifier of the second session; The first uplink data packet is an EtherCAT data packet of Ethernet Control Automation Technology.

21. A communication device, characterized in that the device includes a sending unit and a receiving unit: The sending unit is configured to send a second session creation request to a session management network element, where the second session creation request is used to request the creation of a second session and indicate that the downlink flow of the second session is associated with a first session; The receiving unit is configured to receive a second session creation response from the session management network element, where the second session creation response indicates that the second session is successfully created; The sending unit is further configured to, after the receiving unit receives the second session creation response, receive a first uplink data packet through the second session; Wherein, the second session creation request includes the identifier of the first session; The first uplink data packet is an EtherCAT data packet of Ethernet Control Automation Technology.

22. A communication device, characterized in that the device includes a receiving unit and a processing unit: The receiving unit is configured to receive a first request, where the first request is used to indicate that the uplink flow of a first session is associated with a second session; The processing unit is configured to configure a first forwarding rule in a user plane network element, where the first forwarding rule indicates forwarding the uplink data packet from the first session through the second session; the uplink data packet is an EtherCAT data packet of Ethernet Control Automation Technology; Wherein, 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 or the GTP-U identifier of the General Packet Radio Service Tunnel Protocol User Plane of the second session.

23. The device according to claim 22, characterized in that when receiving the first request, the receiving unit is specifically configured to: receive a first session creation request from a first terminal device, where the first session creation request is used to request the creation of a first session and indicate that the uplink flow of the first session is associated with a second session, and the first session creation request is further used to indicate that the uplink flow of the first session is associated with the second session; or receive a second session creation request from a second terminal device, where the second session creation request is used to request the creation of a second session and indicate that the downlink flow of the first session is associated with the second session; or receive a first configuration request from an application function network element, where the first configuration request is used to configure the first session, and the first configuration request is further used to indicate that the uplink flow of the first session is associated with the second session.

24. The device according to claim 22 or 23, characterized in that the receiving unit is further configured to receive a second request, where the second request is used to request the creation of a second session and indicate that the uplink flow of the second session is associated with the first session; the processing unit is further configured to configure a second forwarding rule in the user plane network element, where the second forwarding rule indicates forwarding the uplink data packet from the second session through the first session.

25. The device according to claim 24, characterized in that When receiving the second request, the receiving unit is specifically configured to: Receive a third session creation request from a second terminal device, where the third session creation request is used to request the creation of a second session, and the third session creation request is further used to indicate that the uplink flow of the second session is associated with the first session; Or receive a second configuration request from an application function network element, where the second configuration request is used to configure the second session, and the second configuration request is further used to indicate that the uplink flow of the second session is associated with the first session.

26. The apparatus according to claim 23, wherein the first session creation request and the first configuration request include: the identifier of the second session; the second session creation request includes: the identifier of the first session.

27. The apparatus according to claim 25, wherein the third session creation request and the second configuration request include: the identifier of the first session.

28. The apparatus according to claim 24, wherein 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 identifier of the first session or the General Packet Radio Service Tunneling Protocol User Plane (GTP-U) identifier of the first session.

29. A communication apparatus, wherein it includes a processor and a memory, and instructions are stored in the memory. When the processor executes the instructions, the apparatus executes the method according to any one of claims 1 to 5.

30. A communication apparatus, wherein it includes a processor and a memory, and instructions are stored in the memory. When the processor executes the instructions, the apparatus executes the method according to claim 6.

31. A communication apparatus, wherein it includes a processor and a memory, and instructions are stored in the memory. When the processor executes the instructions, the apparatus executes the method according to claim 7.

32. A communication apparatus, wherein it includes a processor and a memory, and instructions are stored in the memory. When the processor executes the instructions, the apparatus executes the method according to any one of claims 8 to 14.

Images