Session establishment method, data transmission method and related device

Abstract

The embodiment of the present application discloses a method for establishing a session, a method for transmitting data, and related devices. A first device receives a first message sent by a second device, and the first device establishes a first session with a third device according to the first message, the first message carries a first identifier and a second identifier, the second identifier indicates information about a group to which the first identifier belongs, and a fourth device is determined according to a second identifier, so as to improve the efficiency of determining the fourth device, thereby improving the efficiency of data transmission.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and in particular to a method for establishing a session, a method for transmitting data, and related devices. Background Art

[0002] In the traditional 3rd generation partnership project (3GPP) communication system, data communication is the communication between terminal devices and application servers. 3GPP data communication requires the terminal device to send a data packet to the APP server first, and then the application server forwards the data packet to the terminal device that needs to perform data communication.

[0003] The method of forwarding data packets by the application server requires a long path and a large delay, but the method of using a local switch can solve this problem. The user plane function (UPF) first needs to obtain member information, where the member information includes terminal devices and terminal device identification (ID), and each terminal device corresponds to a unique terminal device ID. Then the UPF identifies whether the data packet needs to be sent to the application server or forwarded to the terminal device through a local switch based on the data radio bearer identification (DRB ID) carried in the data packet. A DRB ID corresponds to a terminal device ID. If the data packet needs to be forwarded to the terminal device through a local switch, the data packet is sent to the base station corresponding to the DRB ID according to the DRB ID, and then the corresponding base station sends the data packet to the corresponding terminal device through the air interface.

[0004] The existing local switching method can solve the problem of long path and large delay caused by the application server forwarding data packets. However, when transmitting data packets between the UPF and the base station and between the base station and the terminal device, if there are multiple terminal devices belonging to the same base station and need to receive data packets, the terminal device IDs corresponding to multiple DRB IDs are required to determine the terminal device that needs to receive the data packet. The determination efficiency of the terminal device is low, which leads to low transmission efficiency of the data packet. Summary of the invention

[0005] The embodiments of the present application provide a method for establishing a session, a method for transmitting data, and related apparatuses. When multiple fourth devices need to receive data packets, the second identifier can be used to obtain information about the group to which the first identifier belongs, thereby determining the group to which multiple fourth devices corresponding to the multiple first identifiers belong. Only one second identifier is required to confirm multiple fourth devices, thereby improving the efficiency of determining the fourth devices and thus improving the transmission efficiency of data packets.

[0006] A first aspect of an embodiment of the present application provides a method for establishing a session, including:

[0007] In a control and user plane separation (CUPS) network architecture, when multiple fourth devices need to receive data packets, a first device receives a first message sent by a second device, and the first device can establish a first session with a third device through the first message, and the first message carries a first identifier and a second identifier, and the second identifier can indicate group information to which the first identifier belongs.

[0008] When multiple fourth devices need to receive data packets, the first device can obtain the group information to which the first identifier indicates, thereby determining the group information to which multiple fourth devices corresponding to the multiple first identifiers belong. Only one second identifier is required to confirm multiple fourth devices, thereby improving the determination efficiency of the fourth devices and thus improving the transmission efficiency of data packets.

[0009] In combination with the first aspect of the embodiments of the present application, in a first implementation method of the first aspect of the embodiments of the present application, after the first device receives the first message sent by the second device, that is, after the first device establishes a first session with the third device, the first device can receive a data packet sent by the third device through the first session, wherein the data packet is marked as belonging to the group indicated by the second identifier.

[0010] In an actual application where a data packet needs to be received, the first device receives a data packet sent by the third device through the first session, and the data packet is marked as belonging to the group indicated by the second identifier. The first device can directly obtain the group information to which the data packet belongs, and the group information can determine to which group the data packet needs to be transmitted, thereby determining the fourth device that needs to receive the data packet, thereby improving the feasibility of the solution.

[0011] In combination with the first implementation method of the first aspect of the embodiment of the present application, in the second implementation method of the first aspect of the embodiment of the present application, after the first device receives the first message sent by the second device, that is, after the first device establishes a first session with the third device, the first device can receive the notification message sent by the second device, and the first device can determine the multicast source data packet based on the notification message.

[0012] The second device determines the multicast source data packet and notifies the first device, so that the first device directly determines the multicast source data packet. When the first device transmits the data packet in a multicast manner, the multicast source data packet can be directly used for multicast, saving the time for determining the multicast data source, thereby improving the data transmission efficiency and the feasibility of the solution.

[0013] In combination with the first implementation method of the first aspect of the embodiment of the present application, in the third implementation method of the first aspect of the embodiment of the present application, after the first device receives the first message sent by the second device, that is, after the first device establishes a first session with the third device, the first device determines the multicast data source and sends a notification message to the second device to notify the second device to determine the multicast source data packet.

[0014] The first device determines the multicast data source and informs the second device, and the second device notifies the third device of this message, so that the third device can directly determine the multicast data source. When the third device decides to transmit a data packet in a multicast manner, it can directly use the multicast source data packet for multicast, saving the time for determining the multicast data source, thereby improving the data transmission efficiency and the feasibility of the solution.

[0015] A second aspect of an embodiment of the present application provides a method for establishing a session, including:

[0016] In the CUPS network architecture, when multiple fourth devices need to receive data packets, the first device receives the second message sent by the second device, so that the first device can establish a second session with the third device based on the second message, wherein the second message carries a third identifier, a second identifier and a first list, the first list is a collection of fourth identifiers, and secondly, the fourth identifier is an identifier corresponding to the fourth device, and the third identifier corresponds to the fourth identifier in the first list, and the second identifier can indicate the group information to which the fourth identifier in the first list belongs.

[0017] When multiple fourth devices need to receive data packets, the second identifier can indicate the group information to which the fourth identifier in the first list belongs. Only one second identifier is needed to confirm multiple fourth devices, thereby improving the efficiency of fourth device determination and thus improving data transmission efficiency.

[0018] In combination with the second aspect of the embodiments of the present application, in a first implementation method of the second aspect of the embodiments of the present application, after the first device receives the second message sent by the second device, that is, after the first device establishes a second session with the third device, the first device and the first device can receive the data packet sent by the third device through the second session, and the data packet is marked as belonging to the group indicated by the second identifier.

[0019] In an actual application where a data packet needs to be received, the first device receives a data packet sent by the third device through the first session, and the data packet is marked as belonging to the group indicated by the second identifier. The first device can directly obtain the group information to which the data packet belongs, and the group information can determine to which group the data packet needs to be transmitted, thereby determining the fourth device that needs to receive the data packet. Secondly, the second session can use only one channel to transmit multiple data packets, reducing transmission resource consumption, thereby improving transmission efficiency and the feasibility of the solution.

[0020] A third aspect of an embodiment of the present application provides a method for establishing a bearer, including:

[0021] In the CUPS network architecture, the first device sends a third message to the fifth device. The first device can establish a first bearer with the fifth device through the third message. The third message also carries a fifth identifier and a second identifier. The second identifier is used to indicate the group information to which the fourth identifier belongs, and the fourth identifier is the identifier corresponding to the fourth device.

[0022] When multiple fourth devices need to receive data packets, the first device can obtain the group information to which the fourth identifier indicated by the second identifier belongs, and only one second identifier is needed to confirm multiple fourth devices, thereby improving the fourth device determination efficiency and thus improving the data packet transmission efficiency.

[0023] In combination with the third aspect of the embodiments of the present application, in a first implementation method of the third aspect of the embodiments of the present application, after the first device sends a third message to the fifth device, that is, after the first device establishes a first bearer with the fifth device, the first device can send a data packet to the fifth device through the first bearer, and the data packet is marked as belonging to the group indicated by the second identifier.

[0024] After the first device sends a data packet to the fifth device, since the data packet is marked as belonging to the group indicated by the second identifier, the fifth device can directly obtain the group information to which the data packet belongs. The group information can determine which group the data packet needs to be transmitted to, thereby determining the fourth device that needs to receive the data packet, thereby improving the feasibility of the solution.

[0025] In combination with the third aspect of the embodiments of the present application or any one of the first implementation methods of the third aspect of the embodiments of the present application, in the second implementation method of the third aspect of the embodiments of the present application, after the first device sends a third message to the fifth device, the first device can receive a notification message sent by the fifth device, and the first device can determine the multicast source data packet based on the notification message.

[0026] The first device determines the multicast source data packet according to the notification message sent by the fifth device, which saves the time of the first device in determining the multicast source data packet, thereby improving the data packet transmission efficiency.

[0027] In combination with the third aspect of the embodiments of the present application or any one of the first implementation methods of the third aspect of the embodiments of the present application, in the third implementation method of the third aspect of the embodiments of the present application, after the first device sends the third message to the fifth device, the first device may send a notification message to the fifth device, so that the fifth device determines the multicast source data packet based on the notification message.

[0028] The fifth device determines the multicast source data packet according to the notification message sent by the first device, which saves the time of the fifth device in determining the multicast source data packet, thereby improving the data packet transmission efficiency.

[0029] In combination with the third aspect of the embodiments of the present application or any one of the first implementation methods of the third aspect of the embodiments of the present application, in a fourth implementation method of the third aspect of the embodiments of the present application, after the first device sends a third message to the fifth device, the first device receives a second list sent by the fifth device, wherein the second list is used by the fifth device to send data packets to the fourth device in a unicast manner.

[0030] In combination with the third aspect of the embodiments of the present application or any one of the first implementation methods of the third aspect of the embodiments of the present application, in the fifth implementation method of the third aspect of the embodiments of the present application, after the first device sends the third message to the fifth device, the first device sends the second list to the fifth device, and when the fifth device needs to send a data packet to the fourth device in unicast mode, the data packet is sent according to the second list.

[0031] The fifth device can obtain the second list in different ways, thereby improving the selectivity and feasibility of this solution.

[0032] In combination with the fourth implementation method of the third aspect of the embodiments of the present application or any one of the fifth implementation methods of the third aspect of the embodiments of the present application, in the sixth implementation method of the third aspect of the embodiments of the present application, after the first device sends the third message to the fifth device, the first device sends the second list to the fourth device, so that the fourth device can receive the data packets sent by the fifth device in unicast mode according to the second list.

[0033] The first device can obtain the second list in different ways. In addition, after obtaining the second list, it sends it to the fourth device, so that the fourth device can receive the data packet sent by unicast, thereby improving the selectivity and feasibility of this solution.

[0034] In combination with the third aspect of the embodiments of the present application or any one of the first implementation methods of the third aspect of the embodiments of the present application, in the seventh implementation method of the third aspect of the embodiments of the present application, after the first device sends a third message to the fifth device, the first device receives a sixth identifier sent by the fifth device, wherein the sixth identifier is used by the fifth device to send a data packet to the fourth device in a multicast manner.

[0035] In combination with the third aspect of the embodiments of the present application or any one of the first implementation methods of the third aspect of the embodiments of the present application, in the eighth implementation method of the third aspect of the embodiments of the present application, after the first device sends the third message to the fifth device, the first device sends a sixth identifier to the fifth device.

[0036] The fifth device can obtain the sixth identifier in different ways, thereby improving the selectivity and feasibility of this solution.

[0037] In combination with the seventh implementation method of the third aspect of the embodiment of the present application or any one of the eighth implementation methods of the third aspect of the embodiment of the present application, in the ninth implementation method of the third aspect of the embodiment of the present application, after the first device sends the third message to the fifth device, the first device sends the sixth identifier to the fourth device, so that the fourth device can receive the data packet sent by the fifth device in multicast manner according to the sixth identifier.

[0038] The first device can obtain the sixth identifier in different ways. In addition, after obtaining the sixth identifier, it sends it to the fourth device, so that the fourth device can receive the data packet sent by multicast, thereby improving the selectivity and feasibility of this solution.

[0039] In combination with the third aspect of the embodiments of the present application or any one of the first implementation methods of the third aspect of the embodiments of the present application, in the tenth implementation method of the third aspect of the embodiments of the present application, after the first device sends a third message to the fifth device, the fifth device can determine that it sends a data packet to the fourth device in a unicast manner, and the fifth device sends a first notification message to the first device, informing the first device that the fifth device sends a data packet to the fourth device in a unicast manner.

[0040] In combination with the third aspect of the embodiments of the present application or any one of the first implementation methods of the third aspect of the embodiments of the present application, in the eleventh implementation method of the third aspect of the embodiments of the present application, after the first device sends the third message to the fifth device, the first device sends a notification message to the fifth device, and the fifth device can determine to send a data packet to the fourth device in a unicast manner based on the notification message.

[0041] The fifth device determines to send the data packet in unicast mode according to different methods, thereby improving the selectivity of this solution.

[0042] A fourth aspect of an embodiment of the present application provides a method for establishing a bearer, including:

[0043] In the CUPS network architecture, the first device sends a fourth message to the fifth device, and the first device can establish a second bearer with the fifth device through the fourth message. The fourth message also carries a seventh identifier, a second identifier and a first list. The first list is a collection of fourth identifiers, the fourth identifier is an identifier corresponding to the fourth device, the seventh identifier corresponds to the fourth identifier in the first list, and the second identifier is used to indicate the group information to which the fourth identifier in the first list belongs.

[0044] When multiple fourth devices need to receive data packets, the first device can obtain the group information to which the fourth identifier indicated by the second identifier belongs, and only one second identifier is needed to confirm multiple fourth devices, thereby improving the fourth device determination efficiency and thus improving the data packet transmission efficiency.

[0045] In combination with the fourth aspect of the embodiments of the present application, in a first implementation method of the fourth aspect of the embodiments of the present application, after the first device sends a fourth message to the fifth device, that is, after the first device establishes a second bearer with the fifth device, the first device can send a data packet to the fifth device through the second bearer, and the data packet is marked as belonging to the group indicated by the second identifier.

[0046] After the first device sends a data packet to the fifth device, since the data packet is marked as belonging to the group indicated by the second identifier, the fifth device can directly obtain the group information to which the data packet belongs. The group information can determine which group the data packet needs to be transmitted to, thereby determining the fourth device that needs to receive the data packet, thereby improving the feasibility of the solution.

[0047] In combination with the fourth aspect of the embodiments of the present application or any one of the first implementation methods of the fourth aspect of the embodiments of the present application, in the second implementation method of the fourth aspect of the embodiments of the present application, the first device receives a second list sent by a fifth device, wherein the second list is used by the fifth device to send data packets to the fourth device in a unicast manner.

[0048] In combination with the fourth aspect of the embodiments of the present application or any one of the first implementation manner of the fourth aspect of the embodiments of the present application, in a third implementation manner of the fourth aspect of the embodiments of the present application, the first device sends a second list to the fifth device.

[0049] The fifth device can obtain the second list in different ways, thereby improving the selectivity and feasibility of this solution.

[0050] In combination with the second implementation method of the fourth aspect of the embodiments of the present application or any one of the third implementation methods of the fourth aspect of the embodiments of the present application, in the fourth implementation method of the fourth aspect of the embodiments of the present application, the first device sends a second list to the fourth device, wherein the second list is used for the fourth device to receive data packets sent by the fifth device in unicast mode.

[0051] The first device can obtain the second list in different ways. In addition, after obtaining the second list, it sends it to the fourth device, so that the fourth device can receive the data packet sent by unicast, thereby improving the selectivity and feasibility of this solution.

[0052] In combination with the fourth aspect of the embodiments of the present application or any one of the first implementation methods of the fourth aspect of the embodiments of the present application, in the fifth implementation method of the fourth aspect of the embodiments of the present application, the first device receives a sixth identifier sent by a fifth device, wherein the sixth identifier is used by the fifth device to send a data packet to the fourth device in a multicast manner.

[0053] In combination with the fourth aspect of the embodiment of the present application or any one of the sixth implementation methods of the fourth aspect of the embodiment of the present application, in the sixth implementation method of the fourth aspect of the embodiment of the present application, the first device sends a sixth identifier to the fifth device.

[0054] The fifth device can obtain the sixth identifier in different ways, thereby improving the selectivity and feasibility of this solution.

[0055] In combination with the fifth implementation method of the fourth aspect of the embodiment of the present application or any one of the sixth implementation methods of the fourth aspect of the embodiment of the present application, in the seventh implementation method of the fourth aspect of the embodiment of the present application, the first device sends a sixth identifier to the fourth device, wherein the sixth identifier is used for the fourth device to receive data packets sent by the fifth device in a multicast manner.

[0056] The first device can obtain the sixth identifier in different ways. In addition, after obtaining the sixth identifier, it sends it to the fourth device, so that the fourth device can receive the data packet sent by multicast, thereby improving the selectivity and feasibility of this solution.

[0057] In combination with the fourth aspect of the embodiments of the present application or any one of the sixth implementation methods of the fourth aspect of the embodiments of the present application, in the eighth implementation method of the fourth aspect of the embodiments of the present application, the fifth device sends a first notification message to the first device, wherein the notification message informs the first device that the fifth device sends the data packet to the fourth device in a unicast manner.

[0058] In combination with the fourth aspect of the embodiments of the present application or any one of the sixth implementation methods of the fourth aspect of the embodiments of the present application, in the ninth implementation method of the fourth aspect of the embodiments of the present application, the fifth device sends a second notification message to the first device, wherein the notification message informs the first device that the fifth device sends the data packet to the fourth device in a multicast manner.

[0059] The fifth device itself determines whether to send the data packet in multicast or unicast mode, thereby improving the selectivity of this solution.

[0060] A fifth aspect of the embodiments of the present application provides a method for data transmission, including:

[0061] In the CUPS network architecture, the fifth device sends a data packet to the fourth device through the second list, wherein the identifier corresponding to the fourth device is the fourth identifier, the set of fourth identifiers is the first list, the second identifier indicates the group information to which the fourth identifier in the first list belongs, and the second list determines the fourth device belonging to the group according to the second identifier.

[0062] When multiple fourth devices need to receive data packets, the fifth device can obtain the group information of the fourth identifier indicated by the second identifier, and secondly, the second list can confirm the fourth device according to the group information. Therefore, multiple fourth devices can be determined according to the second identifier or the second list, thereby improving the fourth device determination efficiency and thus improving the data packet transmission efficiency.

[0063] In combination with the fifth aspect of the embodiments of the present application, in a first implementation manner of the fifth aspect of the embodiments of the present application, the fifth device receives the second list sent by the first device.

[0064] In combination with the fifth aspect of the embodiments of the present application, in a second implementation manner of the fifth aspect of the embodiments of the present application, the fifth device sends a second list to the first device.

[0065] The fifth device can obtain the second list in different ways, thereby improving the selectivity and feasibility of this solution.

[0066] In combination with the first implementation method of the fifth aspect of the embodiment of the present application or any one of the sixth implementation methods of the fifth aspect of the embodiment of the present application, in the third implementation method of the fifth aspect of the embodiment of the present application, the fifth device sends a second list to the fourth device, wherein the second list is used for the fourth device to receive data packets sent by the fifth device in unicast mode.

[0067] In combination with the fifth aspect of the embodiments of the present application, in a fourth implementation method of the fifth aspect of the embodiments of the present application, the fifth device receives a first notification message sent by the first device, wherein the first notification message is used to determine that the fifth device sends a data packet to the fourth device in a unicast manner.

[0068] In combination with the fifth aspect of the embodiments of the present application, in a fifth implementation method of the fifth aspect of the embodiments of the present application, the fifth device sends a first notification message to the first device, wherein the first notification message informs the first device that the fifth device sends a data packet to the fourth device in a unicast manner.

[0069] The fifth device can determine to send the data packet in unicast mode through different methods, thereby improving the selectivity of this solution.

[0070] A sixth aspect of the embodiments of the present application provides a method for data transmission, including:

[0071] In the CUPS network architecture, the fifth device sends a data packet to the fourth device through the sixth identifier, wherein the identifier corresponding to the fourth device is the fourth identifier, the set of fourth identifiers is the first list, the second identifier indicates the group information to which the fourth identifier in the first list belongs, and the sixth identifier determines the fourth device belonging to the group based on the second identifier.

[0072] When multiple fourth devices need to receive data packets, the fifth device can obtain the group information of the fourth identifier indicated by the second identifier, and secondly, the sixth identifier can confirm the fourth device according to the group information. Therefore, multiple fourth devices can be determined based on the second identifier or the sixth identifier, thereby improving the fourth device determination efficiency and thus improving the data packet transmission efficiency.

[0073] In combination with the sixth aspect of the embodiments of the present application, in a first implementation manner of the sixth aspect of the embodiments of the present application, the fifth device receives a sixth identifier sent by the first device.

[0074] In combination with the sixth aspect of the embodiments of the present application, in a second implementation manner of the sixth aspect of the embodiments of the present application, the fifth device sends a sixth identifier to the first device.

[0075] The fifth device can obtain the sixth identifier in different ways, thereby improving the selectivity and feasibility of this solution.

[0076] In combination with the first implementation method of the sixth aspect of the embodiment of the present application or any one of the second implementation method of the sixth aspect of the embodiment of the present application, in the third implementation method of the sixth aspect of the embodiment of the present application, the fifth device sends a sixth identifier to the fourth device, wherein the sixth identifier is used for the fourth device to receive the data packet sent by the fifth device in a multicast manner.

[0077] In combination with the sixth aspect of the embodiments of the present application, in a fourth implementation method of the sixth aspect of the embodiments of the present application, the fifth device receives a notification message sent by the first device, wherein the notification message is used to determine that the fifth device sends a data packet to the fourth device in a multicast manner.

[0078] In combination with the sixth aspect of the embodiments of the present application, in a fifth implementation method of the sixth aspect of the embodiments of the present application, the fifth device sends a second notification message to the first device, wherein the second notification message informs the first device that the fifth device sends a data packet to the fourth device in a multicast manner.

[0079] The fifth device can determine to send the data packet in multicast mode in different ways, thereby improving the selectivity and feasibility of the solution.

[0080] In combination with the sixth aspect of the embodiments of the present application, in a sixth implementation method of the sixth aspect of the embodiments of the present application, the fifth device sends a notification message to the first device, wherein the notification message is used by the first device to determine a multicast source data packet.

[0081] In combination with the sixth aspect of the embodiments of the present application, in a seventh implementation method of the sixth aspect of the embodiments of the present application, the fifth device receives a notification message sent by the first device, wherein the notification message is used by the fifth device to determine a multicast source data packet.

[0082] The fifth device can determine the multicast source data packet in different ways, thereby improving the selectivity and feasibility of this solution.

[0083] In a seventh aspect of the embodiments of the present application, a communication device is provided, which has the function of implementing the first device behavior in the first aspect above. 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.

[0084] In an eighth aspect of the embodiments of the present application, a communication device is provided, which has the function of implementing the first device behavior in the second aspect above. 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.

[0085] In a ninth aspect of the embodiments of the present application, a communication device is provided, which has the function of implementing the first device behavior in the third aspect above. 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.

[0086] In a tenth aspect of the embodiments of the present application, a communication device is provided, which has the function of implementing the first device behavior in the fourth aspect above. 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.

[0087] In an eleventh aspect of the embodiments of the present application, a communication device is provided, which has the function of implementing the fifth device behavior in the fifth aspect above. 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.

[0088] In a twelfth aspect of the embodiments of the present application, a communication device is provided, which has the function of implementing the fifth device behavior in the 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.

[0089] In the thirteenth aspect of the embodiments of the present application, a session establishment device is provided, comprising: a processor, a memory, a bus, and an input-output device, wherein the processor is connected to the memory and the input-output device, and the bus is respectively connected to the processor, the memory, and the input-output device, and the processor executes any method in the above-mentioned first aspect and its possible implementation methods or any method in the above-mentioned second aspect and its possible implementation methods.

[0090] In the fourteenth aspect of the embodiments of the present application, a bearer establishment device is provided, which includes: a processor, a memory, a bus, and an input-output device, wherein the processor is connected to the memory and the input-output device, and the bus is respectively connected to the processor, the memory, and the input-output device, and the processor executes any method in the above-mentioned third aspect and its possible implementation methods or any method in the above-mentioned fourth aspect and its possible implementation methods.

[0091] In the fifteenth aspect of the embodiments of the present application, a data transmission device is provided, comprising: a processor, a memory, a bus, and an input / output device, wherein the processor is connected to the memory and the input / output device, and the bus is respectively connected to the processor, the memory, and the input / output device, and the processor executes any method in the above-mentioned fifth aspect and its possible implementation methods or any method in the above-mentioned sixth aspect and its possible implementation methods.

[0092] The present application also provides a communication device, which may be an integrated circuit chip, for implementing the functions of the aforementioned first device.

[0093] The present application also provides a communication device, which may be an integrated circuit chip, for implementing the functions of the aforementioned fifth device.

[0094] Another aspect of the present application provides a method for establishing a session, the method for establishing a session is applied to a communication system, the communication system includes a first device, a second device and a third device;

[0095] The first device is used to receive a first message sent by the second device;

[0096] The first device is further configured to establish a first session with a third device through a first message.

[0097] The first device is further configured to receive a second message sent by the second device;

[0098] The first device is further configured to establish a second session with the third device through a second message.

[0099] Another aspect of the present application provides a method for establishing a bearer, the method for establishing a session is applied to a communication system, the communication system includes a first device and a fifth device;

[0100] The first device is used to send a third message to the fifth device;

[0101] The first device is further configured to establish a first bearer with a fifth device through a third message;

[0102] The first device is further configured to send a fourth message to a fifth device;

[0103] The first device is further used to establish a second bearer with the device through a fourth message.

[0104] Another aspect of the present application provides a method for data transmission, the method for session establishment is applied to a communication system, the communication system includes a first device and a fifth device;

[0105] a fifth device, configured to send a data packet to a fourth device via a second list;

[0106] The fifth device is further used to send a data packet to the fourth device through the sixth identifier.

[0107] Another aspect of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, and when the computer-readable storage medium is run on a computer, the computer executes the methods described in the above aspects.

[0108] In the technical solution provided in the embodiment of the present application, when multiple fourth devices need to receive data packets, the second identifier can be used to obtain the group information to which the first identifier belongs, thereby determining the group information to which multiple fourth devices corresponding to the multiple first identifiers belong. Only one second identifier is required to confirm the multiple fourth devices, thereby improving the fourth device determination efficiency and thus improving the data packet transmission efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0109] Figure 1 This is a schematic diagram of the system architecture of the new air interface communication system in the embodiment of the present application;

[0110] Figure 2 A schematic diagram of an embodiment of a method for establishing a session in an embodiment of the present application;

[0111] Figure 3 A schematic diagram of another embodiment of the method for establishing a session in an embodiment of the present application;

[0112] Figure 4 A schematic diagram of an embodiment of a method for establishing a bearer in an embodiment of the present application;

[0113] Figure 5 A schematic diagram of another embodiment of the method for establishing a bearer in an embodiment of the present application;

[0114] Figure 6 A schematic diagram of an embodiment of a method for data transmission in an embodiment of the present application;

[0115] Figure 7 A schematic diagram of another embodiment of the method for data transmission in the embodiment of the present application;

[0116] Figure 8 This is a schematic diagram of another embodiment of the method for data transmission in the embodiment of the present application;

[0117] Fig. 9 This is a schematic diagram of another embodiment of the method for data transmission in the embodiment of the present application;

[0118] Fig.10 This is a schematic diagram of another embodiment of the method for data transmission in the embodiment of the present application;

[0119] Fig.11 A schematic diagram of another embodiment of the method for data transmission in the embodiment of the present application;

[0120] Fig.12 A schematic diagram of another embodiment of the method for data transmission in the embodiment of the present application;

[0121] Fig.13 A schematic diagram of another embodiment of the method for data transmission in the embodiment of the present application;

[0122] Fig.14 This is a schematic diagram of another embodiment of the method for data transmission in the embodiment of the present application;

[0123] Fig.15 A schematic diagram of an embodiment of a communication device in an embodiment of the present application;

[0124] Fig.16 A schematic diagram of another embodiment of a communication device in an embodiment of the present application;

[0125] Fig.17 This is a schematic diagram of another embodiment of a communication device in an embodiment of the present application;

[0126] Fig.18 A schematic diagram of another embodiment of a communication device in an embodiment of the present application;

[0127] Fig.19 A schematic diagram of another embodiment of a communication device in an embodiment of the present application;

[0128] Fig. 20 This is a schematic diagram of another embodiment of a communication device in an embodiment of the present application;

[0129] Fig.21 This is a schematic diagram of another embodiment of a communication device in an embodiment of the present application;

[0130] Fig. 22 It is a schematic diagram of another embodiment of the communication device in the embodiment of the present application. DETAILED DESCRIPTION

[0131] The embodiments of the present application provide a method for establishing a session, a method for transmitting data, and related devices, which are used to improve the determination efficiency of terminal devices, thereby improving the transmission efficiency of data packets.

[0132] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments.

[0133] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0134] The technical solutions of the embodiments of the present application can be applied to various data processing communication systems, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA) and other systems. The term "system" can be interchangeable with "network". The CDMA system can implement wireless technologies such as universal terrestrial radio access (UTRA) and CDMA2000. UTRA can include wideband CDMA (WCDMA) technology and other CDMA variant technologies. CDMA2000 can cover interim standard (IS) 2000 (IS-2000), IS-95 and IS-856 standards. The TDMA system can implement wireless technologies such as global system for mobile communication (GSM). The OFDMA system can implement wireless technologies such as evolved universal radio terrestrial access (evolved UTRA, E-UTRA), ultra mobile broadband (ultra mobile broadband, UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash OFDMA, etc. UTRA and E-UTRA are UMTS and UMTS evolution versions. 3GPP's long term evolution (long term evolution, LTE) and various versions based on LTE evolution are new versions of UMTS using E-UTRA. The fifth generation (5 Generation, 5G) communication system, the new radio (New Radio, NR), and the future sixth generation (6th generation, 6G) mobile communication system are the next generation communication systems under study. The technical solution of the embodiment of the present application can be applied to various communication systems such as V2X, LTE-V, V2V, Internet of Vehicles, MTC, IoT, LTE-M, M2M and Internet of Things. In addition, the communication system can also be applied to future-oriented communication technologies, all of which are applicable to the technical solution provided in the embodiment of the present application.The system architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0135] The embodiments of the present application are mainly applied to Figure 1 The system architecture diagram of the new air interface communication system shown in the figure, in which the core network element functions are divided into user plane function (UPF) and access and mobility management function (AMF), among which UPF is mainly responsible for receiving and forwarding data packets, while AMF is mainly responsible for establishing a session connection to the base station device. AMF can also receive uplink data sent by the terminal device.

[0136] Correspondingly, the base station is divided into a centralized unit (CU) and a distributed unit (DU) according to its function, wherein the CU provides an interface with the AMF and the UPF, which can be used to establish a session connection with the AMF and receive data packets sent by the UPF. Secondly, there is also an interface between the CU and the DU, which is mainly used to control and coordinate multiple DUs within the base station device. In the embodiment of the present invention, the function of the CU to control and coordinate data packets to the DU is mainly applied. There is an interface between the DU and the CU, and its function is mainly used to receive data packets sent by the CU. Secondly, there is also an interface between the DU and the terminal device, which is used to send data packets received from the CU to the terminal device. In addition, the base station can communicate with terminal devices 1 to 6, and can also communicate with terminal devices 1 to 6 through relay stations. Terminal devices 1 to 6 can support communication with multiple base stations of different technologies. For example, the terminal device can support communication with base stations of LTE networks, can also support communication with base stations of 5G networks, and can also support dual connection with base stations of LTE networks and base stations of 5G networks. Terminal devices 1 to 6, also known as user equipment (UE), mobile station (MS), mobile terminal (MT), terminal, etc., are devices that provide voice and / or data connectivity to users, or chips set in the device, such as handheld devices with wireless connection capabilities, vehicle-mounted devices, etc. At present, some examples of terminal devices are: mobile phones, tablet computers, laptops, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.

[0137] It should be noted that "AMF" is only a general term for devices that perform access and mobility management functions, and does not specifically refer to one or some devices. In actual applications, devices that perform access and mobility management functions may not be called "AMF" but may be replaced by other names. The specific names are not limited here. In the embodiments of this application, only "AMF" is used as an example for explanation.

[0138] Similarly, "UPF" is only a general term for devices that perform user plane functions, and does not specifically refer to one or some devices. In actual applications, the device that performs user plane functions may not be called "UPF", but may be replaced by other names. The specific name is not limited here. In the embodiments of this application, only "UPF" is used as an example for illustration.

[0139] In actual applications, AMF and UPF can be either separate devices or a group of functional entities on other devices (such as servers, etc.), and the specific details are not limited here.

[0140] To facilitate understanding, some terms or concepts involved in the embodiments of the present application are explained here.

[0141] Air interface multicast, that is, in order to meet the needs of multiple users watching the same content at the same time in the network, multicast can be used to consume only one air interface resource to ensure high air interface efficiency. The earliest multicast is the multimedia broadcast multicast service (MBMS), which centralizes multiple cells with similar geographical locations to the same multicast / multicast single frequency network (MBSFN) area. All cells in the same MBSFN area need to broadcast the same content on the same time-frequency resource at the same time to ensure that edge terminal devices can receive signals from multiple cells at the same time, merge gains and improve reception reliability. However, since the MBMS system is based on the static division of MBMSF areas and cannot be dynamically time-varying, for some small-scale group communication needs, for example, broadcasting or multicasting only in one cell, these services will still be broadcasted in all cells in the entire MBSFN area, even if the terminal devices in most cells do not need to receive the service. Therefore, a single cell to multicast transmission (SCPTM) solution based on cell multicast broadcast is proposed to further enhance the single cell point-to-multipoint transmission. SCPTM is a multicast / broadcast mechanism based on a single cell. Compared with the traditional single-cell unicast mechanism in which only one terminal receives the service, it can send data to all terminals that want to receive the same service or service in a single cell, but only consumes one air interface resource. Therefore, it is more efficient than using unicast to send a unicast data with the same content to each user in the cell, resulting in multiple unicast users consuming multiple air interface resources. SCPTM uses a group radio network temporary identifier (G-RNTI) for scrambling through the PHY layer, while unicast uses a cell radio network temporary identifier (C-RNTI) for scrambling through the PHY layer.

[0142] For easier understanding, see Figure 2 As shown, Figure 2 This is a schematic diagram of an embodiment of a method for establishing a session in an embodiment of the present application, which mainly includes the following steps:

[0143] 201. A first device receives a first message sent by a second device;

[0144] First, the first device receives the first message sent by the second device, and the first device can trigger step 202 according to the first message. Secondly, the first message also carries a first identifier and a second identifier, and the second identifier can indicate the group information to which the first identifier belongs.

[0145] 202. The first device establishes a first session with a third device.

[0146] The first message in step 201 triggers the first device to establish a first session with the third device. In addition, the first device can receive a data packet sent by the third device through the first session.

[0147] In addition, other types of sessions can be established between the first device and the third device. Figure 3 As shown, Figure 3 This is another embodiment of the method for establishing a session in the embodiment of the present application, which mainly includes the following steps:

[0148] 301. The first device receives a second message sent by the second device;

[0149] First, the first device receives the second message sent by the second device, and the first device can trigger step 302 according to the second message. Secondly, the second message also carries a third identifier, a second identifier and a first list. The first list is a collection of fourth identifiers, and the fourth identifier is the identifier corresponding to the fourth device. The third identifier corresponds one-to-one with the fourth identifier in the first list, and the second identifier can indicate the group information to which the fourth identifier in the first list belongs.

[0150] 302. The first device establishes a second session with the third device.

[0151] The second message in step 301 triggers the first device to establish a second session with the third device. In addition, the first device can receive a data packet sent by the third device through the second session.

[0152] For further information, see Figure 4 As shown, Figure 4 This is a schematic diagram of an embodiment of a method for establishing a bearer in an embodiment of the present application, which mainly includes the following steps:

[0153] 401. The first device sends a third message to the fifth device;

[0154] First, the first device sends a third message to the fifth device, and step 402 can be triggered by the third message. Second, the third message also carries the fifth identifier and the second identifier, and the second identifier can indicate the group information to which the fourth identifier belongs.

[0155] 402. The first device establishes a first bearer with the fifth device.

[0156] The third message in step 401 triggers the first device to establish a first bearer with the fifth device. In addition, the first device can send a data packet to the fifth device through the first bearer.

[0157] In addition, other types of bearers may be established between the first device and the fifth device. Figure 5 As shown, Figure 5 This is a schematic diagram of another embodiment of the method for establishing a bearer in an embodiment of the present application, which mainly includes the following steps:

[0158] 501. The first device sends a fourth message to the fifth device;

[0159] First, the first device sends the fourth message to the fifth device, and step 502 can be triggered by the fourth message. Secondly, the third message also carries the seventh identifier, the second identifier and the first list. The first list is a collection of fourth identifiers, and the fourth identifier is the identifier corresponding to the fourth device. The seventh identifier corresponds one-to-one with the fourth identifier in the first list, and the second identifier can indicate the group information to which the fourth identifier in the first list belongs.

[0160] 502. The first device establishes a second bearer with the fifth device.

[0161] The fourth message in step 502 triggers a device to establish a second bearer with a fifth device. In addition, the first device can send a data packet to the fifth device through the second bearer.

[0162] For further information, see Figure 6 As shown, Figure 6 This is a schematic diagram of an embodiment of the method for data transmission in the embodiment of the present application, which mainly includes the following steps:

[0163] 601. The fifth device obtains the second list;

[0164] First, the fifth device obtains the second list, the identifier corresponding to the fourth device is the fourth identifier, and the set of fourth identifiers is the first list. The second identifier can indicate the group information to which the fourth identifier in the first list belongs. Secondly, the second list can determine the fourth device according to the group information indicated by the second identifier.

[0165] 602. The fifth device sends a data packet to the fourth device.

[0166] The fifth device sends a data packet to the fourth device through the second list obtained in step 601 .

[0167] In addition, the fifth device also sends data packets to the fourth device through other means, see Figure 7 As shown, Figure 7 This is another embodiment of the method for data transmission in the embodiment of the present application, which mainly includes the following steps:

[0168] 701. The fifth device obtains a sixth identifier;

[0169] First, the fifth device obtains the sixth identifier, the identifier corresponding to the fourth device is the fourth identifier, and the set of fourth identifiers is the first list. The second identifier can indicate the group information to which the fourth identifier in the first list belongs. Secondly, the sixth identifier can determine the fourth device based on the group information indicated by the second identifier.

[0170] 702. The fifth device sends a data packet to the fourth device.

[0171] The fifth device sends a data packet to the fourth device through the sixth identifier obtained in step 701.

[0172] In order to better understand and implement the above-mentioned solutions in the embodiments of the present application, the following examples are given for specific explanation by using corresponding application scenarios.

[0173] In the embodiment of the present application, the first device may be a centralized unit (CU), the second device may be an access and mobility management function (AMF), the third device may be a user plane function (UPF), the fourth device may be a terminal device, and the fifth device may be a distributed unit (DU). In actual applications, devices that perform the same functions as the first to fifth devices may be replaced by other names, which are not limited here.

[0174] Secondly, in an embodiment of the present application, the first session may be a user protocol data unit session (userequipment PDU session, UE PDU session), the second session may be a group protocol data unit session (GroupPDU session), the first bearer may be a UE data bearer (DRB), the second bearer may be a group data bearer (GroupDRB), the first identifier may be a UE PDU session identifier (identity, ID), the second identifier may be a VLAN ID, the third identifier may be a Group PDU session ID, the fourth identifier may be a terminal device ID, the fifth identifier may be a UE DRBID, the sixth identifier may be a group radio network temporary identifier (group radio network temporary identifier, G-RNTI), the seventh identifier may be a Group DRB ID, the first list may be a terminal device ID list, and the second list may be a cell radio network temporary identifier (cell radio network temporary identifier, C-RNTI) list. For example, in actual applications, sessions, bearers, identifiers, lists and messages that perform the same functions may be replaced by other names, which are not limited here.

[0175] Furthermore, when multiple terminal devices need to receive data packets, if at least one multicast method is used to transmit data packets between CU and UPF, CU and DU, and DU and terminal devices, the efficiency of data packet transmission can be improved.

[0176] It should be noted that the CU and UPF can use multicast or unicast to transmit data packets. The following describes the two methods respectively:

[0177] 1. Multicast is used to transmit data packets between CU and UPF:

[0178] In this embodiment, the CU and the DU may use multicast or unicast to transmit data packets, and the DU and the terminal device may also use multicast or unicast to transmit data packets. It can be understood that in actual applications, the data packet transmission methods between the CU and the DU and the terminal device may be composed of multiple combinations, which are described below:

[0179] 1. Multicast between CU and DU, and multicast between DU and terminal devices:

[0180] In this embodiment, the CU receives the data packet sent by the UPF in a multicast manner through the Group PDU session, and then the CU sends the data packet to the DU in a multicast manner through the Group DRB, and finally the DU sends the data packet to the terminal device in a multicast manner through G-RNTI scrambling. For ease of understanding, please refer to Figure 8 As shown, Figure 8 This is another embodiment of the method for data transmission in the embodiment of the present application, which mainly includes the following steps:

[0181] 801. AMF sends a second message to CU;

[0182] First, AMF needs to send a second message to CU, and CU can trigger step 802 according to the second message. In addition, the second message carries Group PDU session ID, vlan ID and terminal device ID list. Group PDU session ID corresponds one-to-one to the terminal device ID in the terminal device ID list, and vlan ID can indicate that the terminal device ID belongs to the same group, that is, if one or more terminal device IDs correspond to the same vlan ID, then one or more terminal device IDs belong to the same group.

[0183] 802. CU establishes a Group PDU session with UPF;

[0184] Secondly, the CU establishes a Group PDU session with the UPF according to the second message received in step 801, and the established Group PDU session can be used in step 803.

[0185] 803. UPF sends a data packet to CU.

[0186] Furthermore, the UPF may send data packets to the CU in a multicast manner through the Group PDU session established in step 802 .

[0187] It can be understood that the way in which CU obtains the VLAN ID is not only as described in step 801, but also when CU establishes a Group PDU session with UPF, CU obtains it from AMF, or CU obtains it from UPF, which is not limited here.

[0188] It can be known from step 801 that the Group PDU session ID corresponds to the terminal device ID in the terminal device ID list one-to-one, and the VLAN ID can indicate that the terminal device ID belongs to the same group. If the terminal device ID corresponding to the Group PDU session is indicated by the VLAN ID to belong to the same group, the UPF can assume that multiple terminal devices belonging to the same group need to receive the same data packet. The UPF does not need to copy the data packet into multiple copies and then send the data packet to the CU through multiple sessions. It can only send one data packet to the CU through the Group PDU session, thereby saving channel transmission resources and improving data transmission efficiency.

[0189] 804. CU sends a fourth message to DU;

[0190] The CU sends a fourth message to the DU, and then step 805 can be triggered by the fourth message. In addition, the fourth message also carries the Group DRB ID, the VLAN ID and the terminal device ID list. The Group DRB ID is associated with the terminal device ID in the terminal device ID list, and the VLAN ID can indicate that the terminal device IDs belong to the same group.

[0191] 805. CU and DU establish Group DRB;

[0192] Secondly, the CU establishes a Group DRB with the DU according to the fourth message received in step 804 , and the established Group DRB can be used in step 806 .

[0193] It should be noted that there is no difference in the timing sequence between steps 801 to 803 and steps 804 to 805, as long as step 803 is executed before step 806 in timing. For example, the CU can execute steps 801 to 803 and steps 804 to 805 at the same time, or execute steps 804 to 805 first and then execute steps 801 to 803. There is no limitation here.

[0194] 806. CU sends a data packet to DU;

[0195] Furthermore, the CU may send a data packet to the DU via the Group DRB established in step 805 .

[0196] From step 804, it can be known that Group DRB corresponds to the terminal device ID in the terminal device ID list one by one, and vlan ID can indicate that the terminal device ID belongs to the same group. If the terminal device ID corresponding to Group DRB is indicated by vlan ID to belong to the same group, similar to step 803, CU can assume that multiple terminal devices belonging to the same group need to receive the same data packet, and then send a data packet to CU through Group DRB, thereby saving channel transmission resources and improving data transmission efficiency.

[0197] 807. DU obtains G-RNTI;

[0198] After the DU receives the data packet in step 806, the DU can obtain the G-RNTI in different ways, for example:

[0199] DU can generate G-RNTI and send G-RNTI configuration message and corresponding group information to CU through F1 interface, so that CU can obtain G-RNTI and corresponding group information generated by DU.

[0200] or,

[0201] The G-RNTI may also be generated by the CU, and then the DU receives the G-RNTI configuration message and the corresponding group information sent by the CU through the F1 interface, and obtains the G-RNTI and the corresponding group information generated by the CU.

[0202] Further, the DU may send a radio resource control (RRC) message, a system information block (SIB) message, a service data adaptation protocol (SDAP) message, a radio link control (RLC) message, a packet data convergence protocol (PDCP) message, a medium access control layer (MAC) message, or a physical layer (PHY) message to the terminal device through a universal terrestrial radio access network and user to network interface (Uu) interface, so that the terminal device receives the G-RNTI according to any of the foregoing messages. Optionally, the terminal device may also receive an RRC message, a SIB message, a SDAP message, an RLC message, a PDCP message, a MAC message, or a PHY message sent by the CU through the Uu interface, and receive the G-RNTI according to any of the foregoing messages, so that the terminal device can receive the data packet sent by the DU through the G-RNTI scrambling in step 808.

[0203] 808. DU sends a data packet to the terminal device.

[0204] Finally, the DU can send data packets to the terminal device by scrambling the G-RNTI.

[0205] Furthermore, before the DU sends a data packet to the terminal device by means of the G-RNTI scrambling method, the terminal device can receive a multicast reception notification sent by the DU, so that the terminal device can use the G-RNTI to receive the data packet sent by the DU.

[0206] or,

[0207] The terminal device can also receive the multicast reception notification sent by the CU, so that the terminal device can use the G-RNTI to receive the data packets sent by the DU.

[0208] Optionally, the DU may determine whether to send data in a multicast manner. In addition, a second notification message is sent to the CU to inform the CU that the DU sends data to the terminal device in a multicast manner.

[0209] or,

[0210] The DU may also determine whether to send data via multicast. In addition, the DU may determine to send data to the terminal device via multicast based on a notification message sent by the CU.

[0211] In addition, after receiving the second notification message, the CU may send a response reply or a reject reply to the DU. In practical applications, an accept reply may also be sent, which is not limited here. After receiving the notification message, the DU may also send a different reply to the CU that is similar to the one sent by the CU after receiving the second notification message, which is not repeated here.

[0212] Specifically, in this embodiment, the DU sends a data packet to the terminal device through the G-RNTI, which requires a correspondence between the G-RNTI, the VLAN ID, and the terminal device ID.

[0213] Exemplarily, in this embodiment, the correspondence between the G-RNTI, the vlan ID, and the terminal device ID can be as shown in Table 1. It should be noted that Table 1 is only an example of the correspondence between the G-RNTI, the vlan ID, and the terminal device ID. In practical applications, the correspondence may be in other ways, which are not specifically limited here:

[0214] Table 1

[0215] Terminal device ID = 1 Terminal device ID = 2 vlan ID = 1 G-RNTI=1 vlan ID = 2 G-RNTI=2 vlan ID = 3 G-RNTI=3

[0216] Specifically, in this embodiment, as shown in Table 1, when the data packet obtained by the DU through the Group DRB needs to be sent to the terminal device with the terminal device ID of 1, and the vlan ID is 1, the DU can send the data packet to the terminal device through G-RNTI 1, and the terminal device can receive the data packet through G-RNTI 1. Secondly, when the data packet obtained by the DU through the Group DRB needs to be sent to the terminal device with the terminal device ID of 1, and the vlan ID is 2, the DU can send the data packet to the terminal device through G-RNTI 2, and the terminal device can receive the data packet through G-RNTI 2. Further, when the data packet obtained by the DU through the GroupDRB needs to be sent to the terminal device with the terminal device ID of 2, and the vlan ID is 3, the DU can send the data packet to the terminal device through G-RNTI 3, and the terminal device can receive the data packet through G-RNTI 3.

[0217] In this embodiment, the CU can establish a Group PDU session with the UPF through the second message sent by the AMF, and the UPF sends a data packet to the CU in a multicast manner through the Group PDU session. Secondly, after receiving the data packet sent by the UPF in a multicast manner, the CU sends the data packet to the DU in a multicast manner through the Group DRB. Finally, after the DU receives the data packet sent by the CU in a multicast manner, it sends the data packet to the terminal device in a multicast manner through the acquired G-RNTI. The multicast method is used to transmit data packets between the UPF and the CU, the CU and the DU, and the DU and the terminal device, which saves the consumption of channel resources. Secondly, it improves the air interface transmission efficiency, thereby improving the data transmission efficiency.

[0218] 2. Multicast between CU and DU, unicast between DU and terminal devices:

[0219] In this embodiment, the CU receives the data packet sent by the UPF in multicast mode through the Group PDU session, and then the CU sends the data packet to the DU in multicast mode through the Group DRB, and finally the DU sends the data packet to the terminal device in unicast mode through the C-RNTI List scrambling. For ease of understanding, please refer to Fig. 9 As shown, Fig. 9 This is another embodiment of the method for data transmission in the embodiment of the present application, which mainly includes the following steps:

[0220] Steps 901 to 906 in this embodiment are similar to those in the previous embodiment. Figure 8 Steps 801 to 806 in the illustrated embodiment are similar and will not be described in detail here.

[0221] 907. DU obtains C-RNTI List;

[0222] After the DU receives the data packet in step 906, the DU can obtain the C-RNTI List in different ways, for example:

[0223] DU can generate C-RNTI List and send C-RNTI List configuration message, corresponding terminal device identification information and corresponding relationship to CU through F1 interface, so that CU can obtain C-RNTI List generated by DU.

[0224] or,

[0225] The C-RNTI List can also be generated by the CU, and then the DU receives the C-RNTI List configuration message, the corresponding terminal device identification information and the corresponding relationship sent by the CU through the F1 interface, and obtains the C-RNTI List generated by the CU. Among them, the terminal device identification information may include a temporary mobile user identity (temporary mobile subscriber identity, TMSI), an international mobile subscriber identity (international mobile subscriber identity, IMSI), a globally unique temporary UE identity (globally unique temporary UE identity, GUTI), or an F1 interface UE identifier. Among them, the F1 interface UE identifier includes a gNB-CU UE F1 interface identifier, or a gNB-DU UE F1 interface identifier.

[0226] Further, the DU may send an RRC message, a SIB message, a SDAP message, an RLC message, a PDCP message, a MAC message, or a PHY message to the terminal device through the Uu interface, so that the terminal device receives the C-RNTI List according to any of the foregoing messages. Optionally, the terminal device may also receive an RRC message, a SIB message, a SDAP message, an RLC message, a PDCP message, a MAC message, or a PHY message sent by the CU through the Uu interface, and receive the C-RNTI List according to any of the foregoing messages, so that the terminal device can receive the data packet sent by the DU through the C-RNTI List encryption in step 908.

[0227] 908. DU sends a data packet to the terminal device.

[0228] Finally, the DU can send data packets to the terminal device through the C-RNTI List scrambling.

[0229] Furthermore, before the DU sends a data packet to the terminal device by scrambling the C-RNTI List, the terminal device can receive a unicast reception notification sent by the DU, so that the terminal device can use the C-RNTI List to receive the data packet sent by the DU.

[0230] or,

[0231] The terminal device can also receive the unicast reception notification sent by the CU, so that the terminal device can use the C-RNTIList to receive the data packets sent by the DU.

[0232] Optionally, the DU may determine whether to send data in a unicast manner. In addition, a first notification message is sent to the CU to inform the CU that the DU sends data to the terminal device in a unicast manner.

[0233] or,

[0234] The DU may also determine whether to send data in unicast mode by the CU. In addition, the DU may determine to send data to the terminal device in unicast mode according to a notification message sent by the CU.

[0235] In addition, after receiving the first notification message, the CU may send a response reply or a reject reply to the DU. In practical applications, an accept reply may also be sent, which is not limited here. After receiving the notification message sent by the CU, the DU may also send a different reply to the CU similar to the one sent by the CU after receiving the first notification message, which will not be repeated here.

[0236] Specifically, in this embodiment, the DU needs a corresponding relationship between C-RNTIList, vlan ID and terminal device ID to send a data packet to the terminal device through C-RNTI List. The corresponding relationship between C-RNTI List, vlan ID and terminal device ID is similar to the above Table 1, which will not be repeated here.

[0237] In this embodiment, the CU can establish a Group PDU session with the UPF through the second message sent by the AMF, and the UPF sends a data packet to the CU in a multicast manner through the Group PDU session. Secondly, after receiving the data packet sent by the UPF in a multicast manner, the CU sends the data packet to the DU in a multicast manner through the Group DRB. Finally, after the DU receives the data packet sent by the CU in a multicast manner, it sends the data packet to the terminal device in a unicast manner through the acquired C-RNTI List. The multicast method is used to transmit data packets between the UPF and the CU, and between the CU and the DU, which saves the consumption of channel resources and improves the data transmission efficiency.

[0238] 3. Unicast between CU and DU, multicast between DU and terminal devices:

[0239] In this embodiment, the CU receives the data packet sent by the UPF in multicast mode through the Group PDU session, and then the CU sends the data packet to the DU in unicast mode through the UE DRB to the DU, and finally the DU sends the data packet to the terminal device in multicast mode through G-RNTI scrambling. For ease of understanding, please refer to Fig.10 As shown, Fig.10This is another embodiment of the method for data transmission in the embodiment of the present application, which mainly includes the following steps:

[0240] Steps 1001 to 1003 in this embodiment are similar to those in the previous embodiment. Figure 8 Steps 801 to 803 in the illustrated embodiment are similar and will not be described in detail here.

[0241] 1004. CU sends a third message to DU;

[0242] CU sends a third message to DU, and then step 1005 can be triggered by the third message. Secondly, the third message also carries DRB ID and VLAN ID. One DRB ID corresponds to one terminal device ID, and the VLAN ID can indicate that the DRB ID belongs to the same group, that is, the VLAN ID can indicate that the terminal device ID belongs to the same group.

[0243] 1005. CU and DU establish UE DRB;

[0244] Secondly, the CU establishes a UE DRB with the DU according to the third message received in step 1004 , and the established UE DRB can be used in step 1006 .

[0245] It should be noted that there is no difference in the timing sequence between steps 1001 to 1003 and steps 1004 to 1005, as long as step 1003 is executed before step 1006 in timing. For example, the CU can execute steps 1001 to 1003 and steps 1004 to 1005 at the same time, or execute steps 1004 to 1005 first and then execute steps 1001 to 1003. There is no limitation here.

[0246] 1006. CU sends a data packet to DU;

[0247] Further, the CU may send a data packet to the DU via the UE DRB established in step 1005 .

[0248] 1007. DU obtains G-RNTI;

[0249] After the DU receives the data packet in step 1006, the DU can obtain the G-RNTI in different ways. The way in which the DU obtains the G-RNTI is the same as the above Figure 8 Similar to step 807 in the embodiment shown, the terminal device can receive the G-RNTI and the Figure 8 Step 807 in the illustrated embodiment is similar and will not be described in detail here.

[0250] 1008. DU sends a data packet to the terminal device.

[0251] Finally, the DU can send data packets to the terminal device through the G-RNTI scrambling.

[0252] Furthermore, the terminal device can receive the multicast reception notification sent by the CU or DU and the aforementioned Figure 8 Step 808 in the embodiment shown is similar and will not be described again here. The DU determines to send a data packet to the terminal device in a multicast manner in a different manner than the aforementioned Figure 8 Step 808 in the illustrated embodiment is similar and will not be described in detail here.

[0253] Secondly, the DU needs to send data packets to the terminal device through G-RNTI, which requires the correspondence between G-RNTI, vlan ID and terminal device ID. The correspondence between G-RNTI, vlan ID and terminal device ID is similar to the above Table 1, which will not be repeated here.

[0254] Exemplarily, it can be known from step 1004 that one DRB ID corresponds to one terminal device ID, and the vlan ID can indicate that the terminal device IDs belong to the same group. If two UE DRBs corresponding to two terminal device IDs are indicated by the vlan ID to belong to the same group, that is, step 1006 is that the DU receives two data packets through two UE DRBs, and the two data packets can be considered to have the same actual content, that is, the DU can select one of the two data packets as a multicast source data packet, and then send the selected multicast source data packet to the terminal device through the G-RNTI.

[0255] Specifically, the DU can determine the multicast source data packet in the two data packets and send a notification message to the CU, so that the CU determines the multicast source data packet according to the notification message. After the CU determines the multicast source data packet, it can choose whether to unicast or multicast with the multicast source data packet in subsequent data packet transmission.

[0256] or,

[0257] The multicast source data packet can also be determined by the CU, and a notification message is sent to the DU, so that the DU determines the multicast source data packet in the two data packets, and selects the multicast source data packet to send to the terminal device through the G-RNTI. Secondly, the non-multicast source data packet in the two data packets can be deleted or discarded by the DU.

[0258] In addition, when the CU receives the notification message, it can send a response reply or a reject reply to the DU. In actual applications, it can also send an accept reply, which is not limited here. After receiving the notification message, the DU can also send a similar or different reply to the CU after receiving the notification message, which is not repeated here.

[0259] In this embodiment, the CU can establish a Group PDU session with the UPF through the second message sent by the AMF, and the UPF sends data packets to the CU in a multicast manner through the Group PDU session. Secondly, after receiving the data packets sent by the UPF in a multicast manner, the CU sends data packets to the DU in a unicast manner through the UE DRB. Finally, after the DU receives the data packets sent by the CU in a unicast manner, the DU determines the multicast source data packets in different ways, and sends the determined multicast source data packets to the terminal device in a multicast manner through the obtained G-RNTI. The multicast method is used to transmit data packets between the UPF and the CU, and between the DU and the terminal device, which saves the consumption of channel resources. Secondly, it improves the air interface transmission efficiency, thereby improving the data transmission efficiency.

[0260] 4. Unicast between CU and DU, unicast between DU and terminal device:

[0261] In this embodiment, the CU receives the data packet sent by the UPF in multicast mode through the Group PDU session, and then the CU sends the data packet to the DU in unicast mode through the UE DRB to the DU, and finally the DU sends the data packet to the terminal device in unicast mode through the C-RNTI List scrambling. For ease of understanding, please refer to Fig.11 As shown, Fig.11 This is another embodiment of the method for data transmission in the embodiment of the present application, which mainly includes the following steps:

[0262] Steps 1101 to 1103 in this embodiment are similar to those in the previous embodiment. Figure 8 Steps 801 to 803 in the illustrated embodiment are similar and will not be described in detail here.

[0263] 1104. CU sends a third message to DU;

[0264] CU sends a third message to DU, and then step 1105 can be triggered by the third message. Secondly, the third message also carries DRB ID and VLAN ID. One DRB ID corresponds to one terminal device ID, and the VLAN ID can indicate that the terminal device IDs belong to the same group.

[0265] 1105. CU and DU establish UE DRB;

[0266] Secondly, the CU establishes a UE DRB with the DU according to the fourth message received in step 1104 , and the established UE DRB can be used in step 1106 .

[0267] It should be noted that there is no difference in the timing sequence between steps 1101 to 1103 and steps 1104 to 1105, as long as step 1103 is executed before step 1106 in timing. For example, the CU can execute steps 1101 to 1103 and steps 1104 to 1105 at the same time, or execute steps 1104 to 1105 first and then execute steps 1101 to 1103. There is no limitation here.

[0268] 1106. CU sends a data packet to DU;

[0269] Further, the CU may send a data packet to the DU via the UE DRB established in step 1105 .

[0270] 1107. DU obtains C-RNTI List;

[0271] After the DU receives the data packet in step 1106, the DU can obtain the C-RNTI List in different ways. The various ways for the DU to obtain the C-RNTI List are similar to those described above. Fig. 9 Similar to step 907 in the embodiment shown, the terminal device can receive the C-RNTI List and the Fig. 9 Step 907 in the illustrated embodiment is similar and will not be described in detail here.

[0272] 1108. DU sends a data packet to the terminal device.

[0273] Finally, the DU can send data packets to the terminal device through the C-RNTI List scrambling.

[0274] Furthermore, the terminal device can receive the unicast reception notification sent by the CU or DU and the aforementioned Fig. 9 Step 908 in the embodiment shown is similar and will not be described again here. The DU determines in different ways whether to send a data packet to the terminal device in a unicast manner or in accordance with the aforementioned Fig. 9 Step 908 in the illustrated embodiment is similar and will not be described again here.

[0275] Secondly, the DU needs to send data packets to the terminal device through the C-RNTI List. The correspondence between the C-RNTI List, the vlan ID and the terminal device ID is similar to the above Table 1, which will not be repeated here.

[0276] In this embodiment, the CU can establish a Group PDU session with the UPF through the second message sent by the AMF, and the UPF sends a data packet to the CU in a multicast manner through the Group PDU session. Secondly, after receiving the data packet sent by the UPF in a multicast manner, the CU sends the data packet to the DU in a unicast manner through the UE DRB. Finally, after the DU receives the data packet sent by the CU in a unicast manner, it sends the data packet to the terminal device in a unicast manner through the acquired C-RNTI List. The multicast method is used to transmit data packets between the UPF and the CU, which saves the consumption of channel resources and improves the data transmission efficiency.

[0277] 2. Unicast is used to transmit data packets between CU and UPF:

[0278] In this embodiment, data packets can be transmitted between CU and DU in a multicast or unicast manner, and data packets can also be transmitted between DU and terminal devices in a multicast or unicast manner. It can be understood that in actual applications, the data packet transmission methods between CU and DU and between DU and terminal devices can be composed of multiple combinations, which are described below. It can be understood that this embodiment mainly describes the method of transmitting data packets in a multicast manner at least once, so this embodiment does not describe the method of transmitting data packets in a unicast manner between CU and DU and between DU and terminal devices:

[0279] 1. Multicast between CU and DU, and multicast between DU and terminal devices:

[0280] In this embodiment, the CU receives the data packet sent by the UPF in unicast mode through the UE PDU session, and then the CU sends the data packet to the DU in multicast mode through the Group DRB, and finally the DU sends the data packet to the terminal device in multicast mode through G-RNTI scrambling. For ease of understanding, please refer to Fig.12 As shown, Fig.12 This is another embodiment of the method for data transmission in the embodiment of the present application, which mainly includes the following steps:

[0281] 1201. AMF sends a first message to CU;

[0282] First, AMF needs to send a first message to CU, and CU can trigger step 1202 according to the first message. In addition, the first message carries UE PDU session ID and VLAN ID. One UE PDU session ID corresponds to one terminal device ID, and the VLAN ID can indicate that the UE PDU session ID belongs to the same group, that is, the VLAN ID can indicate that the terminal device ID belongs to the same group. It can be known that if one or more terminal device IDs correspond to the same VLAN ID, then one or more terminal device IDs belong to the same group.

[0283] 1202. CU establishes UE PDU session with UPF;

[0284] Secondly, the CU establishes a UE PDU session with the UPF according to the first message received in step 1201, and the established UE PDU session can be used in step 1203.

[0285] 1203. UPF sends a data packet to CU.

[0286] Furthermore, the UPF may send data packets to the CU in a unicast manner through the UE PDU session established in step 1202 .

[0287] 1204. CU sends a fourth message to DU;

[0288] The CU sends a fourth message to the DU, and then step 1205 can be triggered by the fourth message. In addition, the fourth message also carries the Group DRB ID, the vlan ID and the terminal device ID list. The Group DRB ID corresponds one-to-one to the terminal device ID in the terminal device ID list, and the vlan ID can indicate that the terminal device ID belongs to the same group.

[0289] 1205. CU and DU establish Group DRB;

[0290] Secondly, the CU establishes a Group DRB with the DU according to the fourth message received in step 1204 , and the established Group DRB can be used in step 1206 .

[0291] It should be noted that there is no difference in the timing sequence between steps 1201 to 1203 and steps 1204 to 1205, as long as step 1203 is executed before step 1206 in timing. For example, the CU can execute steps 1201 to 1203 and steps 1204 to 1205 at the same time, or execute steps 1204 to 1205 first and then execute steps 1201 to 1203. There is no limitation here.

[0292] 1206. CU sends a data packet to DU;

[0293] Furthermore, the CU may send a data packet to the DU via the Group DRB established in step 1205 .

[0294] In the exemplary embodiment, it can be known from step 1204 that a UE PDU session ID corresponds to a terminal device ID, and the VLAN ID can indicate that the terminal device IDs belong to the same group. If there are two UE PDU session IDs corresponding to two terminal device IDs, which are indicated by the VLAN ID to belong to the same group, that is, step 1203 is that the UPF sends three data packets to the CU through two UE PDU sessions. The three data packets can be considered to have the same actual content, that is, the CU can select one of the three data packets as a multicast source data packet, and then send the selected multicast source data packet to the DU through the Group DRB.

[0295] Specifically, AMF can determine the multicast source data packet in the two data packets and send a notification message to CU, so that CU determines the multicast source data packet in the two data packets according to the notification message, and selects the multicast source data packet to send to DU through Group DRB. Secondly, for the non-multicast source data packet in the two data packets, CU can choose to delete or discard it.

[0296] or,

[0297] The multicast source data packet can also be determined by the CU, and a notification message is sent to the AMF, so that the AMF determines the multicast source data packet based on the notification message. After the AMF determines the multicast data packet, it can choose to unicast or multicast with the multicast source data packet during subsequent data packet transmission.

[0298] In addition, when the CU receives the notification message, it can send a response reply or a reject reply to the AMF. In actual applications, it can also send an accept reply, which is not limited here. After receiving the notification message, the AMF can also send a similar or different reply to the CU after receiving the notification message, which is not repeated here.

[0299] 1207. DU obtains G-RNTI;

[0300] After the DU receives the data packet in step 1206, the DU can obtain the G-RNTI in different ways, for example:

[0301] DU can generate G-RNTI and send G-RNTI configuration message and corresponding group information to CU through F1 interface, so that CU can obtain G-RNTI and corresponding group information generated by DU.

[0302] or,

[0303] The G-RNTI may also be generated by the CU, and then the DU receives the G-RNTI configuration message and the corresponding group information sent by the CU through the F1 interface, and obtains the G-RNTI and the corresponding group information generated by the CU.

[0304] Further, the DU may send an RRC message, a SIB message, a SDAP message, an RLC message, a PDCP message, a MAC message, or a PHY message to the terminal device through the Uu interface, so that the terminal device receives the G-RNTI according to any of the foregoing messages. Optionally, the terminal device may also receive an RRC message, a SIB message, a SDAP message, an RLC message, a PDCP message, a MAC message, or a PHY message sent by the CU through the Uu interface, and receive the G-RNTI according to any of the foregoing messages, so that the terminal device can receive the data packet sent by the DU scrambled by the G-RNTI in step 1208.

[0305] 1208. DU sends a data packet to the terminal device.

[0306] Finally, the DU can send data packets to the terminal device through the G-RNTI scrambling.

[0307] Furthermore, before the DU sends a data packet to the terminal device by means of the G-RNTI scrambling method, the terminal device can receive a multicast reception notification sent by the DU, so that the terminal device can use the G-RNTI to receive the data packet sent by the DU.

[0308] or,

[0309] The terminal device can also receive the multicast reception notification sent by the CU, so that the terminal device can use the G-RNTI to receive the data packets sent by the DU.

[0310] Optionally, the DU may determine whether to send data in a multicast manner. In addition, a second notification message is sent to the CU to inform the CU that the DU sends data to the terminal device in a multicast manner.

[0311] or,

[0312] The DU may also determine whether to send data via multicast. In addition, the DU may determine to send data to the terminal device via multicast based on a notification message sent by the CU.

[0313] In addition, after receiving the second notification message, the CU may send a response reply or a reject reply to the DU. In practical applications, an accept reply may also be sent, which is not limited here. After receiving the notification message, the DU may also send a different reply to the CU that is similar to the one sent by the CU after receiving the second notification message, which is not repeated here.

[0314] Specifically, in this embodiment, the DU needs a corresponding relationship between G-RNTI, vlan ID and terminal device ID to send a data packet to the terminal device through G-RNTI. The corresponding relationship between G-RNTI, vlan ID and terminal device ID is similar to the aforementioned Table 1, which will not be repeated here.

[0315] In this embodiment, the CU can establish a UE PDU session with the UPF through the first message sent by the AMF, and the UPF sends a data packet to the CU in a unicast manner through the UE PDU session. Secondly, after receiving the data packet sent by the UPF in a unicast manner, the CU sends the data packet to the DU in a multicast manner through the Group DRB. Finally, after the DU receives the data packet sent by the CU in a multicast manner, it sends the data packet to the terminal device in a multicast manner through the obtained G-RNTI. The multicast method is used to transmit data packets between the CU and the DU, and between the DU and the terminal device, which saves the consumption of channel resources. Secondly, it improves the air interface transmission efficiency, thereby improving the data transmission efficiency.

[0316] 2. Multicast between CU and DU, unicast between DU and terminal devices:

[0317] In this embodiment, the CU receives the data packet sent by the UPF in unicast mode through the UE PDU session, and then the CU sends the data packet to the DU in multicast mode through the Group DRB, and finally the DU sends the data packet to the terminal device in unicast mode through the C-RNTI List scrambling. For ease of understanding, please refer to Fig.13 As shown, Fig.13 This is another embodiment of the method for data transmission in the embodiment of the present application, which mainly includes the following steps:

[0318] Steps 1301 to 1306 in this embodiment are similar to those in the previous embodiment. Fig.12 Steps 1201 to 1206 in the illustrated embodiment are similar and will not be described in detail here.

[0319] 1307. DU obtains C-RNTI List;

[0320] After the DU receives the data packet in step 1306, the DU can obtain the C-RNTI List in different ways, for example:

[0321] DU can generate C-RNTI List and send C-RNTI List configuration message, corresponding terminal device identification information and corresponding relationship to CU through F1 interface, so that CU can obtain C-RNTI List generated by DU.

[0322] or,

[0323] The C-RNTI List can also be generated by the CU, and then the DU receives the C-RNTI List configuration message, the corresponding terminal device identification information and the corresponding relationship sent by the CU through the F1 interface, and obtains the C-RNTI List generated by the CU. The terminal device identification information may include TMSI, IMSI, GUTI, or F1 interface UE identification. The F1 interface UE identification includes the gNB-CU UE F1 interface identification, or the gNB-DU UE F1 interface identification.

[0324] Further, the DU may send an RRC message, a SIB message, a SDAP message, an RLC message, a PDCP message, a MAC message, or a PHY message to the terminal device via the Uu interface, so that the terminal device receives the C-RNTI List according to any of the foregoing messages. Optionally, the terminal device may also receive an RRC message, a SIB message, a SDAP message, an RLC message, a PDCP message, a MAC message, or a PHY message sent by the CU via the Uu interface, and receive the C-RNTI List according to any of the foregoing messages, so that the terminal device can receive the data packet sent by the DU via the C-RNTI List encryption in step 1308.

[0325] 1308. DU sends a data packet to the terminal device.

[0326] Finally, the DU can send data packets to the terminal device through the C-RNTI List scrambling.

[0327] Furthermore, before the DU sends a data packet to the terminal device by scrambling the C-RNTI List, the terminal device can receive a unicast reception notification sent by the DU, so that the terminal device can use the C-RNTI List to receive the data packet sent by the DU.

[0328] or,

[0329] The terminal device can also receive the unicast reception notification sent by the CU, so that the terminal device can use the C-RNTIList to receive the data packets sent by the DU.

[0330] Optionally, the DU may determine whether to send data in a unicast manner. In addition, a first notification message is sent to the CU to inform the CU that the DU sends data to the terminal device in a unicast manner.

[0331] or,

[0332] The DU may also determine whether to send data in unicast mode by the CU. In addition, the DU may determine to send data to the terminal device in unicast mode according to a notification message sent by the CU.

[0333] In addition, after receiving the first notification message, the CU may send a response reply or a reject reply to the DU. In practical applications, an accept reply may also be sent, which is not limited here. After receiving the notification message sent by the CU, the DU may also send a different reply to the CU similar to the one sent by the CU after receiving the first notification message, which will not be repeated here.

[0334] Specifically, in this embodiment, the DU needs a corresponding relationship between C-RNTIList, vlan ID and terminal device ID to send a data packet to the terminal device through C-RNTI List. The corresponding relationship between C-RNTI List, vlan ID and terminal device ID is similar to the above Table 1, which will not be repeated here.

[0335] In this embodiment, the CU can establish a UE PDU session with the UPF through the first message sent by the AMF, and the UPF sends a data packet to the CU in unicast mode through the UE PDU session. Secondly, after receiving the data packet sent by the UPF in unicast mode, the CU determines the multicast source data packet in different ways, and then sends the determined multicast source data packet to the DU in multicast mode through the Group DRB. Finally, after the DU receives the data packet sent by the CU in multicast mode, it sends the data packet to the terminal device in unicast mode through the obtained C-RNTI List. The multicast mode is used to transmit data packets between the CU and the DU, which saves the consumption of channel resources and improves the data transmission efficiency.

[0336] 3. Unicast between CU and DU, multicast between DU and terminal devices:

[0337] In this embodiment, the CU receives the data packet sent by the UPF in unicast mode through the UE PDU session, and then the CU sends the data packet to the DU in unicast mode through the UE DRB, and finally the DU sends the data packet to the terminal device in multicast mode through G-RNTI scrambling. For ease of understanding, please refer to Fig.14 As shown, Fig.14 This is another embodiment of the method for data transmission in the embodiment of the present application, which mainly includes the following steps:

[0338] Steps 1401 to 1403 in this embodiment are similar to those in the previous embodiment. Fig.12 Steps 1201 to 1203 in the illustrated embodiment are similar and will not be described in detail here.

[0339] 1404. CU sends a third message to DU;

[0340] CU sends a third message to DU, and step 1405 can be triggered by the third message. The third message also carries DRB ID and VLAN ID. One DRB ID corresponds to one terminal device ID, and the VLAN ID can indicate that the DRB ID belongs to the same group, that is, the VLAN ID can indicate that the terminal device ID belongs to the same group.

[0341] 1405. CU and DU establish UE DRB;

[0342] Secondly, the CU establishes a UE DRB with the DU according to the third message received in step 1404 , and the established UE DRB can be used in step 1406 .

[0343] It should be noted that there is no difference in the timing sequence between steps 1401 to 1403 and steps 1404 to 1405, as long as step 1403 is executed before step 1406 in timing. For example, the CU can execute steps 1401 to 1403 and steps 1404 to 1405 at the same time, or execute steps 1404 to 1405 first and then execute steps 1401 to 1403. There is no limitation here.

[0344] 1406. CU sends a data packet to DU;

[0345] Further, the CU may send a data packet to the DU via the UE DRB established in step 1405 .

[0346] 1407. DU obtains G-RNTI;

[0347] After the DU receives the data packet in step 1406, the DU can obtain the G-RNTI in different ways. The way in which the DU obtains the G-RNTI is the same as the above Fig.12 Similar to step 1207 in the embodiment shown, the terminal device can receive the G-RNTI and the Fig.12 Step 1207 in the illustrated embodiment is similar and will not be described in detail here.

[0348] 1408. DU sends a data packet to the terminal device.

[0349] Finally, the DU can send data packets to the terminal device through the G-RNTI scrambling.

[0350] Furthermore, the terminal device can receive the multicast reception notification sent by the CU or DU and the aforementioned Fig.12 Step 1208 in the illustrated embodiment is similar and will not be described again here. The DU determines in different ways to send a data packet to the terminal device in a multicast manner and the aforementioned Fig.12 Step 1208 in the illustrated embodiment is similar and will not be described again here.

[0351] Secondly, the DU needs to send data packets to the terminal device through G-RNTI, which requires the correspondence between G-RNTI, vlan ID and terminal device ID. The correspondence between G-RNTI, vlan ID and terminal device ID is similar to the above Table 1, which will not be repeated here.

[0352] Exemplarily, it can be known from step 1404 that one DRB ID corresponds to one terminal device ID, and the vlan ID can indicate that the terminal device IDs belong to the same group. If there are five UE DRBs corresponding to five terminal device IDs, which are indicated by the vlan ID to belong to the same group, that is, step 1406 is that the DU receives five data packets through five UE DRBs, and the five data packets can be considered to have the same actual content, that is, the DU can select one of the five data packets as a multicast source data packet, and then send the selected multicast source data packet to the terminal device through the G-RNTI.

[0353] Specifically, the DU can determine the multicast source data packet among the five data packets and send a notification message to the CU, so that the CU determines the multicast source data packet according to the notification message. After the CU determines the multicast source data packet, it can choose whether to unicast or multicast with the multicast source data packet in subsequent data packet transmission.

[0354] or,

[0355] The multicast source data packet can also be determined by the CU, and a notification message is sent to the DU, so that the DU determines the multicast source data packet among the five data packets, and selects the multicast source data packet to send to the terminal device through the G-RNTI. Secondly, the non-multicast source data packet among the five data packets can be deleted or discarded by the DU.

[0356] In addition, when the CU receives the notification message, it can send a response reply or a reject reply to the DU. In actual applications, it can also send an accept reply, which is not limited here. After receiving the notification message, the DU can also send a similar or different reply to the CU after receiving the notification message, which is not repeated here.

[0357] In this embodiment, the CU can establish a UE PDU session with the UPF through the first message sent by the AMF, and the UPF sends a data packet to the CU in unicast mode through the UE PDU session. Secondly, after receiving the data packet sent by the UPF in unicast mode, the CU sends the data packet to the DU in unicast mode through the UE DRB. Finally, after the DU receives the data packet sent by the CU in unicast mode, the DU determines the multicast source data packet in different ways, and sends the determined multicast source data packet to the terminal device in multicast mode through the obtained G-RNTI. The multicast mode is used to transmit data packets between the DU and the terminal device, which improves the air interface transmission efficiency, thereby improving the data transmission efficiency.

[0358] The data transmission method in the embodiment of the present application is described above. The first device in the embodiment of the present application is described below:

[0359] See also Fig.15 , Fig.15 This is a schematic diagram of an embodiment of a communication device in an embodiment of the present application. The communication device 1500 includes:

[0360] The receiving module 1501 is used to receive a first message sent by the second device, wherein the first message is used for the first device to establish a first session with a third device, and the first message carries a first identifier and a second identifier, and the second identifier indicates information about the group to which the first identifier belongs.

[0361] In an optional implementation, in the above Fig.15 Based on the corresponding embodiment, in another embodiment of the communication device 1500 provided in the embodiment of the present application, the receiving module 1501 is also used to receive a data packet sent by a third device through the first session, wherein the data packet is marked as belonging to the group indicated by the second identifier.

[0362] In an optional implementation, in the above Fig.15 On the basis of the corresponding embodiment, in another embodiment of the communication device 1500 provided in the embodiment of the present application, the receiving module 1501 is also used to receive a notification message sent by the second device, wherein the notification message is used by the first device to determine the multicast source data packet.

[0363] In an optional implementation, in the above Fig.15 Based on the corresponding embodiment, in another embodiment of the communication device 1500 provided in the embodiment of the present application, the communication device 1500 also includes a sending module 1502 for sending a notification message to the second device, wherein the notification message is used by the second device to determine the multicast source data packet.

[0364] See also Fig.16 , Fig.16 This is another embodiment schematic diagram of the first device in the embodiment of the present application, the communication device 1600 includes:

[0365] Receiving module 1601 is used to receive a second message sent by a second device, wherein the second message is used for the first device to establish a second session with a third device, the second message carries a third identifier, a second identifier and a first list, the first list is a collection of fourth identifiers, the fourth identifier is an identifier corresponding to the fourth device, the third identifier corresponds to the fourth identifier in the first list, and the second identifier indicates the group information to which the fourth identifier in the first list belongs.

[0366] In an optional implementation, in the above Fig.16 On the basis of the corresponding embodiment, in another embodiment of the communication device 1600 provided in the embodiment of the present application, the receiving module 1601 is also used to receive a data packet sent by a third device through a second session, wherein the data packet is marked as belonging to the group indicated by the second identifier.

[0367] See also Fig.17 , Fig.17 This is another embodiment schematic diagram of the first device in the embodiment of the present application, the communication device 1700 includes:

[0368] Sending module 1701 is used to send a third message to the fifth device, wherein the third message is used to establish a first bearer between the first device and the fifth device, the third message carries a fifth identifier and a second identifier, the second identifier indicates the group information to which the fourth identifier belongs, and the fourth identifier is the identifier corresponding to the fourth device.

[0369] In an optional implementation, in the above Fig.17 On the basis of the corresponding embodiment, in another embodiment of the communication device 1700 provided in the embodiment of the present application, the sending module 1701 is also used to send a data packet to a fifth device through the first bearer, wherein the data packet is marked as belonging to the group indicated by the second identifier.

[0370] In an optional implementation, in the above Fig.17Based on the corresponding embodiment, in another embodiment of the communication device 1700 provided in the embodiment of the present application, the communication device 1700 also includes a receiving module 1702 for receiving a notification message sent by a fifth device, wherein the notification message is used by the first device to determine a multicast source data packet.

[0371] In an optional implementation, in the above Fig.17 On the basis of the corresponding embodiment, in another embodiment of the communication device 1700 provided in the embodiment of the present application, the sending module 1701 is also used to send a notification message to the fifth device, wherein the notification message is used by the fifth device to determine the multicast source data packet.

[0372] In an optional implementation, in the above Fig.17 On the basis of the corresponding embodiment, in another embodiment of the communication device 1700 provided in the embodiment of the present application, the receiving module 1702 is also used to receive a second list sent by the fifth device, wherein the second list is used for the fifth device to send a data packet to the fourth device in a unicast manner.

[0373] In an optional implementation, in the above Fig.17 On the basis of the corresponding embodiment, in another embodiment of the communication device 1700 provided in the embodiment of the present application, the sending module 1701 is further used to send the second list to the fifth device.

[0374] In an optional implementation, in the above Fig.17 On the basis of the corresponding embodiment, in another embodiment of the communication device 1700 provided in the embodiment of the present application, the sending module 1701 is also used to send a second list to the fourth device, wherein the second list is used for the fourth device to receive data packets sent by the fifth device in unicast mode.

[0375] In an optional implementation, in the above Fig.17 On the basis of the corresponding embodiment, in another embodiment of the communication device 1700 provided in the embodiment of the present application, the receiving module 1702 is also used to receive the sixth identifier sent by the fifth device, wherein the sixth identifier is used by the fifth device to send a data packet to the fourth device in a multicast manner.

[0376] In an optional implementation, in the above Fig.17 On the basis of the corresponding embodiment, in another embodiment of the communication device 1700 provided in the embodiment of the present application, the sending module 1701 is further used to send a sixth identifier to the fifth device.

[0377] In an optional implementation, in the above Fig.17On the basis of the corresponding embodiment, in another embodiment of the communication device 1700 provided in the embodiment of the present application, the sending module 1701 is also used to send a sixth identifier to a fourth device, wherein the sixth identifier is used for the fourth device to receive data packets sent by the fifth device in a multicast manner.

[0378] In an optional implementation, in the above Fig.17 On the basis of the corresponding embodiment, in another embodiment of the communication device 1700 provided in the embodiment of the present application, the sending module 1701 is also used to send a first notification message to the first device, wherein the first notification message is used to inform the first device that the fifth device sends a data packet to the fourth device in a unicast manner.

[0379] In an optional implementation, in the above Fig.17 On the basis of the corresponding embodiment, in another embodiment of the communication device 1700 provided in the embodiment of the present application, the sending module 1701 is also used to send a notification message to the fifth device, wherein the notification message is used to determine that the fifth device sends a data packet to the fourth device in a unicast manner.

[0380] See also Fig.18 , Fig.18 This is another embodiment schematic diagram of the first device in the embodiment of the present application, the communication device 1800 includes:

[0381] Sending module 1801 is used to send a fourth message to a fifth device, wherein the fourth message is used to establish a second bearer between the first device and the fifth device, the fourth message carries a seventh identifier, a second identifier and a first list, the first list is a collection of fourth identifiers, the fourth identifier is an identifier corresponding to the fourth device, the seventh identifier corresponds to the fourth identifier in the first list, and the second identifier indicates the group information to which the fourth identifier in the first list belongs.

[0382] In an optional implementation, in the above Fig.18 On the basis of the corresponding embodiment, in another embodiment of the communication device 1800 provided in the embodiment of the present application, the sending module 1801 is also used to send a data packet to a fifth device through a second bearer, wherein the data packet is marked as belonging to the group indicated by the second identifier.

[0383] In an optional implementation, in the above Fig.18 Based on the corresponding embodiment, in another embodiment of the communication device 1800 provided in the embodiment of the present application, the communication device 1800 also includes a receiving module 1802 for receiving a second list sent by a fifth device, wherein the second list is used by the fifth device to send a data packet to the fourth device in a unicast manner.

[0384] In an optional implementation, in the above Fig.18On the basis of the corresponding embodiment, in another embodiment of the communication device 1800 provided in the embodiment of the present application, the sending module 1801 is further used to send the second list to the fifth device.

[0385] In an optional implementation, in the above Fig.18 On the basis of the corresponding embodiment, in another embodiment of the communication device 1800 provided in the embodiment of the present application, the sending module 1801 is also used to send a second list to the fourth device, wherein the second list is used for the fourth device to receive data packets sent by the fifth device in unicast mode.

[0386] In an optional implementation, in the above Fig.18 On the basis of the corresponding embodiment, in another embodiment of the communication device 1800 provided in the embodiment of the present application, the receiving module 1802 is also used to receive the sixth identifier sent by the fifth device, wherein the sixth identifier is used by the fifth device to send a data packet to the fourth device in a multicast manner.

[0387] In an optional implementation, in the above Fig.18 On the basis of the corresponding embodiment, in another embodiment of the communication device 1800 provided in the embodiment of the present application, the sending module 1801 is further used to send a sixth identifier to the fifth device.

[0388] In an optional implementation, in the above Fig.18 On the basis of the corresponding embodiment, in another embodiment of the communication device 1800 provided in the embodiment of the present application, the sending module 1801 is also used to send a sixth identifier to a fourth device, wherein the sixth identifier is used for the fourth device to receive data packets sent by the fifth device in a multicast manner.

[0389] In an optional implementation, in the above Fig.18 On the basis of the corresponding embodiment, in another embodiment of the communication device 1800 provided in the embodiment of the present application, the sending module 1801 is also used to send a first notification message to the first device, wherein the first notification message is used to inform the first device that the fifth device sends a data packet to the fourth device in a unicast manner.

[0390] In an optional implementation, in the above Fig.18 On the basis of the corresponding embodiment, in another embodiment of the communication device 1800 provided in the embodiment of the present application, the sending module 1801 is also used to send a notification message to the fifth device, wherein the notification message is used to determine that the fifth device sends a data packet to the fourth device in a multicast manner.

[0391] The first device in the embodiment of the present application is described above. The fifth device in the embodiment of the present application is described below:

[0392] See also Fig.19 , Fig.19 This is a schematic diagram of an embodiment of the fifth device in the embodiment of the present application. The communication device 1900 includes:

[0393] Sending module 1901 is used to send a data packet to a fourth device through a second list, wherein the identifier corresponding to the fourth device is a fourth identifier, the set of fourth identifiers is a first list, the second identifier indicates the group information to which the fourth identifier in the first list belongs, and the second list determines the fourth device belonging to the group according to the second identifier.

[0394] In an optional implementation, in the above Fig.19 On the basis of the corresponding embodiment, in another embodiment of the communication device 1900 provided in the embodiment of the present application, the communication device 1900 further includes a receiving module 1902 for receiving a second list sent by the first device.

[0395] In an optional implementation, in the above Fig.19 On the basis of the corresponding embodiment, in another embodiment of the communication device 1900 provided in the embodiment of the present application, the sending module 1901 is further used to send the second list to the first device.

[0396] In an optional implementation, in the above Fig.19 On the basis of the corresponding embodiment, in another embodiment of the communication device 1900 provided in the embodiment of the present application, the sending module 1901 is also used to send a second list to the fourth device, wherein the second list is used for the fourth device to receive data packets sent by the fifth device in unicast mode.

[0397] In an optional implementation, in the above Fig.19 On the basis of the corresponding embodiment, in another embodiment of the communication device 1900 provided in the embodiment of the present application, the receiving module 1902 is also used to receive a notification message sent by the first device, wherein the notification message is used to determine that the fifth device sends a data packet to the fourth device in a unicast manner.

[0398] In an optional implementation, in the above Fig.19 On the basis of the corresponding embodiment, in another embodiment of the communication device 1900 provided in the embodiment of the present application, the sending module 1901 is also used to send a first notification message to the first device, wherein the first notification message is used to inform the first device that the fifth device sends a data packet to the fourth device in a unicast manner.

[0399] See also Fig. 20 , Fig. 20 This is another embodiment schematic diagram of the fifth device in the embodiment of the present application, the communication device 2000 includes:

[0400] Sending module 2001 is used to send a data packet to a fourth device through a sixth identifier, wherein the identifier corresponding to the fourth device is the fourth identifier, the set of fourth identifiers is the first list, the second identifier indicates the group information to which the fourth identifier in the first list belongs, and the sixth identifier determines the fourth device belonging to the group based on the second identifier.

[0401] In an optional implementation, in the above Fig. 20 On the basis of the corresponding embodiment, in another embodiment of the communication device 2000 provided in the embodiment of the present application, the communication device 2000 further includes a receiving module 2002 for receiving a sixth identifier sent by the first device.

[0402] In an optional implementation, in the above Fig. 20 On the basis of the corresponding embodiment, in another embodiment of the communication device 2000 provided in the embodiment of the present application, the sending module 2001 is further used to send a sixth identifier to the first device.

[0403] In an optional implementation, in the above Fig. 20 On the basis of the corresponding embodiment, in another embodiment of the communication device 2000 provided in the embodiment of the present application, the sending module 2001 is also used to send a sixth identifier to a fourth device, wherein the sixth identifier is used for the fourth device to receive data packets sent by the fifth device in a multicast manner.

[0404] In an optional implementation, in the above Fig. 20 On the basis of the corresponding embodiment, in another embodiment of the communication device 2000 provided in the embodiment of the present application, the receiving module 2002 is also used to receive a notification message sent by the first device, wherein the notification message is used to determine that the fifth device sends a data packet to the fourth device in a multicast manner.

[0405] In an optional implementation, in the above Fig. 20 On the basis of the corresponding embodiment, in another embodiment of the communication device 2000 provided in the embodiment of the present application, the sending module 2001 is also used to send a second notification message to the first device, wherein the second notification message informs the first device that the fifth device sends a data packet to the fourth device in a multicast manner.

[0406] In an optional implementation, in the above Fig. 20 On the basis of the corresponding embodiment, in another embodiment of the communication device 2000 provided in the embodiment of the present application, the sending module 2001 is also used to send a notification message to the first device, wherein the notification message is used by the first device to determine the multicast source data packet.

[0407] In an optional implementation, in the above Fig. 20 On the basis of the corresponding embodiment, in another embodiment of the communication device 2000 provided in the embodiment of the present application, the receiving module 2002 is also used to receive a notification message sent by the first device, wherein the notification message is used by the fifth device to determine the multicast source data packet.

[0408] See also Fig.21 , Fig.21 This is another embodiment diagram of the first device in the embodiment of the present application. The communication device 2100 may include one or more central processing units (CPU) 2101 and a memory 2105. The memory 2105 stores one or more applications or data.

[0409] The memory 2105 may be a volatile storage or a persistent storage. The program stored in the memory 2105 may include one or more modules, each of which may include a series of instruction operations in the first device. Furthermore, the central processor 2101 may be configured to communicate with the memory 2105 and execute a series of instruction operations in the memory 2105 on the communication device 2100.

[0410] The communication device 2100 may also include one or more power supplies 2102, one or more wired or wireless network interfaces 2103, one or more input and output interfaces 2104, and / or one or more operating systems, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

[0411] The CPU 2101 can execute the aforementioned Figures 15 to 18 The operations performed by the communication device in the illustrated embodiment will not be described in detail here.

[0412] See also Fig. 22 , Fig. 22 This is a schematic diagram of another embodiment of the fifth device in the embodiment of the present application. The communication device 2200 may include one or more central processing units (CPU) 2201 and a memory 2205. The memory 2205 stores one or more applications or data.

[0413] The memory 2205 may be a volatile storage or a persistent storage. The program stored in the memory 2205 may include one or more modules, each of which may include a series of instruction operations in the fifth device. Furthermore, the central processor 2201 may be configured to communicate with the memory 2205 and execute a series of instruction operations in the memory 2205 on the communication device 2200.

[0414] The communication device 2200 may also include one or more power supplies 2202, one or more wired or wireless network interfaces 2203, one or more input and output interfaces 2204, and / or one or more operating systems, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

[0415] The CPU 2201 can execute the aforementioned Figures 19 to 20 The operations performed by the communication device in the illustrated embodiment will not be described in detail here.

[0416] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0417] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present invention is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, a computer, a server, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server, or data center. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or a data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive Solid State Disk (SSD)), etc.

[0418] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0419] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0420] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0421] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0422] If 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 the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0423] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for establishing a session, characterized in that: include: The first device receives a first message sent by the second device, wherein the first message is used for the first device to establish a first session with a third device, the first message carries a first identifier and a second identifier, the second identifier indicates information about a group to which the first identifier belongs, and the first identifier is an identifier of the first session; The first device determines, based on the group information indicated by the second identifier, a fourth device that receives the data packet; The first device is a first radio access network RAN ​​device, the second device is a device that performs access and mobility management functions, and the third device is a device that performs user plane functions. The access and mobility management functions and the user plane functions are included in the core network element functions.

2. The method according to claim 1, characterized in that After the first device receives the first message sent by the second device, the method further includes: The first device receives a data packet sent by the third device through the first session, wherein the data packet is marked as belonging to the group indicated by the second identifier.

3. A method for establishing a session, characterized in that: include: The first device receives a second message sent by the second device, wherein the second message is used for the first device to establish a second session with a third device, the second message carries a third identifier, a second identifier, and a first list, the first list is a set of fourth identifiers, the fourth identifier is an identifier corresponding to the fourth device, the third identifier corresponds to the fourth identifier in the first list, and the second identifier indicates group information to which the fourth identifier in the first list belongs; The fourth identifier corresponding to the third identifier is indicated by the second identifier as belonging to the same group; The first device is a first RAN device, the second device is a device that performs access and mobility management functions, and the third device is a device that performs user plane functions. The access and mobility management functions and the user plane functions are included in the core network element functions.

4. The method according to claim 3, characterized in that After the first device receives the second message sent by the second device, the method further includes: The first device receives a data packet sent by the third device through the second session, wherein the data packet is marked as belonging to the group indicated by the second identifier.

5. A method for establishing a bearer, characterized in that: include: The first device sends a third message to the fifth device, wherein the third message is used for the first device to establish a first bearer with the fifth device, the third message carries a fifth identifier and a second identifier, the second identifier indicates information about a group to which a fourth identifier belongs, and the fourth identifier is an identifier corresponding to the fourth device; The first device is a first radio access network RAN ​​device, and the fifth device is a second RAN device; The fourth device is a terminal device, and the fifth identifier is an identifier of the first bearer.

6. The method according to claim 5, characterized in that After the first device sends the third message to the fifth device, the method further includes: The first device sends a data packet to the fifth device through the first bearer, wherein the data packet is marked as belonging to the group indicated by the second identifier.

7. The method according to claim 5 or 6, characterized in that: After the first device sends the third message to the fifth device, the method further includes: The first device receives a second list sent by a fifth device, wherein the second list is used by the fifth device to send a data packet to the fourth device in a unicast manner.

8. The method according to claim 5 or 6, characterized in that: After the first device sends the third message to the fifth device, the method further includes: The first device receives a sixth identifier sent by the fifth device, wherein the sixth identifier is used by the fifth device to send a data packet to the fourth device in a multicast manner.

9. The method according to claim 8, characterized in that After the first device sends the third message to the fifth device, the method further includes: The first device sends the sixth identifier to the fourth device, wherein the sixth identifier is used by the fourth device to receive the data packet sent by the fifth device in a multicast manner.

10. The method according to claim 5 or 6, characterized in that: After the first device sends the third message to the fifth device, the method further includes: The fifth device sends a first notification message to the first device, wherein the first notification message is used to inform the first device that the fifth device sends a data packet to the fourth device in a unicast manner.

11. A method for establishing a bearer, characterized in that: include: The first device sends a fourth message to the fifth device, wherein the fourth message is used for the first device to establish a second bearer with the fifth device, the fourth message carries a seventh identifier, a second identifier, and a first list, the first list is a set of fourth identifiers, the fourth identifier is an identifier corresponding to the fourth device, the seventh identifier corresponds to the fourth identifier in the first list, and the second identifier indicates group information to which the fourth identifier in the first list belongs; The first device is a first RAN device, and the fifth device is a second RAN device; The fourth device is a terminal device, and the seventh identifier is an identifier of the second bearer.

12. The method according to claim 11, characterized in that After the first device sends the fourth message to the fifth device, the method further includes: The first device sends a data packet to the fifth device through the second bearer, wherein the data packet is marked as belonging to the group indicated by the second identifier.

13. The method according to claim 11 or 12, characterized in that: After the first device sends the fourth message to the fifth device, the method further includes: The first device receives a second list sent by a fifth device, wherein the second list is used by the fifth device to send a data packet to the fourth device in a unicast manner.

14. The method according to claim 11 or 12, characterized in that: After the first device sends the third message to the fifth device, the method further includes: The first device receives a sixth identifier sent by the fifth device, wherein the sixth identifier is used by the fifth device to send a data packet to the fourth device in a multicast manner.

15. The method according to claim 14, characterized in that After the first device sends the third message to the fifth device, the method further includes: The first device sends the sixth identifier to the fourth device, wherein the sixth identifier is used by the fourth device to receive the data packet sent by the fifth device in a multicast manner.

16. The method according to claim 11 or 12, characterized in that: After the first device sends the third message to the fifth device, the method further includes: The fifth device sends a first notification message to the first device, wherein the first notification message is used to inform the first device that the fifth device sends a data packet to the fourth device in a unicast manner.

17. The method according to claim 11 or 12, characterized in that: After the first device sends the third message to the fifth device, the method further includes: The fifth device sends a second notification message to the first device, wherein the second notification message is used to inform the first device that the fifth device sends a data packet to the fourth device in a multicast manner.

18. A method for data transmission, characterized in that: include: The fifth device receives the second list sent by the first device; The fifth device sends a data packet to the fourth device through the second list, wherein the identifier corresponding to the fourth device is a fourth identifier, the set of the fourth identifiers is the first list, the second identifier indicates the group information to which the fourth identifier in the first list belongs, and the second list determines the fourth device belonging to the group according to the second identifier; The first device is a CU, and the fifth device is a DU.

19. The method according to claim 18, characterized in that Before the fifth device sends the data packet to the fourth device through the second list, the method further includes: The fifth device sends the second list to the first device.

20. The method according to claim 18, characterized in that Before the fifth device sends the data packet to the fourth device through the second list, the method further includes: The fifth device sends a first notification message to the first device, wherein the first notification message is used to inform the first device that the fifth device sends the data packet to the fourth device in a unicast manner.

21. A method for data transmission, characterized in that: include: The fifth device receives the sixth identifier sent by the first device; The fifth device sends a data packet to the fourth device through the sixth identifier, wherein the identifier corresponding to the fourth device is a fourth identifier, the set of the fourth identifiers is a first list, the second identifier indicates the group information to which the fourth identifier in the first list belongs, and the sixth identifier determines the fourth device belonging to the group according to the second identifier; The first device is a CU, and the fifth device is a DU.

22. The method according to claim 21, characterized in that Before the fifth device sends the data packet to the fourth device through the sixth identifier, the method further includes: The fifth device sends the sixth identifier to the first device.

23. The method according to claim 22, characterized in that Before the fifth device sends the data packet to the fourth device through the sixth identifier, the method further includes: The fifth device sends the sixth identifier to the fourth device, wherein the sixth identifier is used by the fourth device to receive the data packet sent by the fifth device in a multicast manner.

24. The method according to claim 21, characterized in that Before the fifth device sends the data packet to the fourth device through the sixth identifier, the method further includes: The fifth device sends a second notification message to the first device, wherein the second notification message informs the first device that the fifth device sends the data packet to the fourth device in a multicast manner.

25. A communication device, characterized in that: The communication device is a first device, comprising: a receiving module, configured to receive a first message sent by a second device, wherein the first message is used by the first device to establish a first session with a third device, the first message carries a first identifier and a second identifier, the second identifier indicates information about a group to which the first identifier belongs, and the first identifier is an identifier of the first session; A processing module, determining a fourth device that receives a data packet based on the group information indicated by the second identifier; The first device is a first RAN device, the second device is a device that performs access and mobility management functions, and the third device is a device that performs user plane functions. The access and mobility management functions and the user plane functions are included in the core network element functions.

26. A communication device, characterized in that: The communication device is a first device, comprising: a receiving module, configured to receive a second message sent by a second device, wherein the second message is used for the first device to establish a second session with a third device, the second message carries a third identifier, a second identifier, and a first list, the first list is a set of fourth identifiers, the fourth identifier is an identifier corresponding to the fourth device, the third identifier corresponds to the fourth identifier in the first list, and the second identifier indicates information about a group to which the fourth identifier in the first list belongs; The fourth identifier corresponding to the third identifier is indicated by the second identifier as belonging to the same group; The first device is a first RAN device, the second device is a device that performs access and mobility management functions, and the third device is a device that performs user plane functions. The access and mobility management functions and the user plane functions are included in the core network element functions.

27. A communication device, characterized in that: The communication device is a first device, comprising: a sending module, configured to send a third message to a fifth device, wherein the third message is used for the first device to establish a first bearer with the fifth device, the third message carries a fifth identifier and a second identifier, the second identifier indicates information about a group to which a fourth identifier belongs, and the fourth identifier is an identifier corresponding to the fourth device; The first device is a first radio access network RAN ​​device, and the fifth device is a second RAN device; The fourth device is a terminal device, and the fifth identifier is an identifier of the first bearer.

28. A communication device, characterized in that: The communication device is a first device, comprising: a sending module, configured to send a fourth message to a fifth device, wherein the fourth message is used for the first device to establish a second bearer with the fifth device, the fourth message carries a seventh identifier, a second identifier, and a first list, the first list is a set of fourth identifiers, the fourth identifier is an identifier corresponding to the fourth device, the seventh identifier corresponds to the fourth identifier in the first list, and the second identifier indicates information about the group to which the fourth identifier in the first list belongs; The first device is a first radio access network RAN ​​device, and the fifth device is a second RAN device; The fourth device is a terminal device, and the seventh identifier is an identifier of the second bearer.

29. A communication device, characterized in that: The communication device is a fifth device, comprising: A receiving unit, configured to receive a second list sent by the first device; a sending module, configured to send a data packet to a fourth device through the second list, wherein the identifier corresponding to the fourth device is a fourth identifier, the set of the fourth identifiers is the first list, the second identifier indicates the group information to which the fourth identifier in the first list belongs, and the second list determines the fourth device belonging to the group according to the second identifier; The first device is a CU, and the fifth device is a DU.

30. A communication device, characterized in that: The communication device is a fifth device, comprising: a receiving module, configured to receive a sixth identifier sent by the first device; a sending module, configured to send a data packet to a fourth device through the sixth identifier, wherein the identifier corresponding to the fourth device is a fourth identifier, the set of the fourth identifiers is a first list, the second identifier indicates the group information to which the fourth identifier in the first list belongs, and the sixth identifier determines the fourth device belonging to the group according to the second identifier; The first device is a CD, and the fifth device is a DU.

Images