Data transmission methods, devices, core network nodes, network-side equipment and terminals

Abstract

This application discloses a data transmission method, apparatus, core network node, network-side device, and terminal, belonging to the field of communication technology. The data transmission method of this application includes: a core network node sending a multicast protocol data unit (PDU) session establishment signaling to a first network-side device; the core network node sending a unicast PDU session establishment signaling to the first network-side device; wherein the multicast path established by the multicast PDU session establishment signaling is used to transmit downlink data streams for multiple terminals in a target service, and the unicast path established by the unicast PDU session establishment signaling is used to transmit uplink data streams and / or downlink data streams for one terminal in the target service.

Description

Technical Field

[0001] This application belongs to the field of communications, and specifically relates to a data transmission method, apparatus, core network node, network-side equipment, and terminal. Background Technology

[0002] In existing technologies, unicast transmission establishes an independent channel and transmission processing mechanism for each user equipment (UE) based on its service requirements, resulting in resource consumption that increases exponentially with the number of UEs. Multicast transmission, on the other hand, follows a pre-planned multicast service schedule, first collecting a list of interested UEs, and then establishing and transmitting multicast connections to those UEs. While existing multicast services offer relatively high transmission efficiency, the pre-planning and collection of interested UE lists makes the entire preparation process cumbersome, hindering the flexible and rapid establishment and transmission of dynamic multicast services as needed. Therefore, it cannot effectively address a wider range of service and transmission requirements.

[0003] In existing solutions, only one of multicast and unicast transmissions can be used at a time for the same service. This results in low service transmission efficiency and is not conducive to the simultaneous transmission of public data, terminal personalized data, and terminal uplink data. Summary of the Invention

[0004] This application provides a data transmission method, apparatus, core network node, network-side equipment, and terminal, which can solve the problem of low system efficiency caused by existing data transmission methods.

[0005] Firstly, a data transmission method is provided, including:

[0006] The core network node sends a multicast protocol data unit (PDU) session establishment signaling to the first network-side device;

[0007] The core network node sends a unicast PDU session establishment signaling to the first network-side device;

[0008] The multicast path established by the multicast PDU session establishment signaling is used to transmit downlink data streams for multiple terminals in the target service, and the unicast path established by the unicast PDU session establishment signaling is used to transmit uplink data streams and / or downlink data streams for one terminal in the target service.

[0009] Secondly, a data transmission device is provided for use in a core network node, comprising:

[0010] The first sending module is used to send multicast protocol data unit (PDU) session establishment signaling to the first network-side device;

[0011] The second sending module is used to send unicast PDU session establishment signaling to the first network-side device;

[0012] The multicast path established by the multicast PDU session establishment signaling is used to transmit downlink data streams for multiple terminals in the target service, and the unicast path established by the unicast PDU session establishment signaling is used to transmit uplink data streams and / or downlink data streams for one terminal in the target service.

[0013] Thirdly, a data transmission method is provided, including:

[0014] The first network-side device receives the multicast protocol data unit (PDU) session establishment signaling sent by the core network node;

[0015] The first network-side device receives unicast PDU session establishment signaling sent by the core network node;

[0016] The multicast path established by the multicast PDU session establishment signaling is used to transmit downlink data streams for multiple terminals in the target service, and the unicast path established by the unicast PDU session establishment signaling is used to transmit uplink data streams and / or downlink data streams for one terminal in the target service.

[0017] Fourthly, a data transmission apparatus is provided, applied to a first network-side device, comprising:

[0018] The first receiving module is used to receive multicast protocol data unit (PDU) session establishment signaling sent by the core network node;

[0019] The second receiving module is used to receive unicast PDU session establishment signaling sent by the core network node;

[0020] The multicast path established by the multicast PDU session establishment signaling is used to transmit downlink data streams for multiple terminals in the target service, and the unicast path established by the unicast PDU session establishment signaling is used to transmit uplink data streams and / or downlink data streams for one terminal in the target service.

[0021] Fifthly, a data transmission method is provided, including:

[0022] The terminal receives multicast configuration information sent by the first network-side device. The multicast configuration information is used to establish a multicast radio bearer for terminals belonging to the same cell.

[0023] The terminal receives unicast configuration information sent by the first network-side device, the unicast configuration information being used to establish a unicast wireless bearer for the terminal;

[0024] The terminal processes downlink service data in both multicast and unicast wireless bearers.

[0025] Sixthly, a data transmission device is provided, applied to a terminal, comprising:

[0026] The third receiving module is used to receive multicast configuration information sent by the first network-side device. The multicast configuration information is used to establish a multicast wireless bearer for terminals belonging to the same cell.

[0027] The fourth receiving module is used to receive unicast configuration information sent by the first network-side device, wherein the unicast configuration information is used to establish a unicast wireless bearer for the terminal.

[0028] The processing module is used to process downlink service data in multicast radio bearers and downlink service data in unicast radio bearers.

[0029] In a seventh aspect, a core network node is provided, the core network node including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0030] Eighthly, a core network node is provided, including a processor and a communication interface, wherein the communication interface is used to send multicast protocol data unit (PDU) session establishment signaling to a first network-side device; and to send unicast PDU session establishment signaling to the first network-side device;

[0031] The multicast path established by the multicast PDU session establishment signaling is used to transmit downlink data streams for multiple terminals in the target service, and the unicast path established by the unicast PDU session establishment signaling is used to transmit uplink data streams and / or downlink data streams for one terminal in the target service.

[0032] In a ninth aspect, a network-side device is provided, the network-side device being a first network-side device, comprising a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the third aspect.

[0033] In a tenth aspect, a network-side device is provided, the network-side device being a first network-side device, including a processor and a communication interface, wherein the communication interface is used to receive multicast protocol data unit (PDU) session establishment signaling sent by a core network node; and to receive unicast PDU session establishment signaling sent by a core network node;

[0034] The multicast path established by the multicast PDU session establishment signaling is used to transmit downlink data streams for multiple terminals in the target service, and the unicast path established by the unicast PDU session establishment signaling is used to transmit uplink data streams and / or downlink data streams for one terminal in the target service.

[0035] Eleventhly, a terminal is provided, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the third aspect.

[0036] In a twelfth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is configured to receive multicast configuration information sent by a first network-side device, the multicast configuration information being used to establish a multicast radio bearer for terminals belonging to the same cell; and to receive unicast configuration information sent by the first network-side device, the unicast configuration information being used to establish a unicast radio bearer for the terminal; the processor is configured to perform data processing on downlink service data in the multicast radio bearer and downlink service data in the unicast radio bearer.

[0037] In a thirteenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method as described in the first, third, or fifth aspects.

[0038] In a fourteenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the steps of the methods described in the first, third, or fifth aspects.

[0039] In a fifteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a non-transient storage medium, the program / program product being executed by at least one processor to perform the steps of the method as described in the first aspect, the third aspect, or the fifth aspect.

[0040] In this embodiment, by sending multicast PDU session establishment signaling and unicast PDU session establishment signaling to the first network-side device, multicast PDU sessions and unicast PDU sessions are established, enabling the system to simultaneously transmit downlink data streams for multiple terminals in the target service in the multicast PDU session and uplink data streams and / or downlink data streams for one terminal in the unicast PDU session, thereby achieving simultaneous transmission of uplink and downlink data streams and improving transmission efficiency. Attached Figure Description

[0041] Figure 1This is a block diagram of a wireless communication system applicable to embodiments of this application;

[0042] Figure 2 This is one of the flowcharts illustrating the data transmission method according to an embodiment of this application;

[0043] Figure 3 This is a transmission architecture diagram involving embodiments of this application;

[0044] Figure 4 This is one of the schematic diagrams of a data transmission device according to an embodiment of this application;

[0045] Figure 5 This is a structural block diagram of the core network node in an embodiment of this application;

[0046] Figure 6 This is a second schematic flowchart of the data transmission method according to an embodiment of this application;

[0047] Figure 7 This is a second schematic diagram of a data transmission device according to an embodiment of this application;

[0048] Figure 8 This is the third flowchart illustrating the data transmission method according to an embodiment of this application;

[0049] Figure 9 This is the third schematic diagram of the data transmission device according to an embodiment of this application;

[0050] Figure 10 This is a structural block diagram of the terminal according to an embodiment of this application;

[0051] Figure 11 This is a structural block diagram of a communication device according to an embodiment of this application. Detailed Implementation

[0052] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0053] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0054] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless 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 terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used not only in the systems and radio technologies mentioned above, but also in other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to applications beyond NR systems, such as 6th Generation (6G) communication systems.

[0055] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as a terminal device or user equipment (UE). The terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), etc. Wearable devices include smartwatches, wristbands, headphones, glasses, etc. It should be noted that this application does not limit the specific type of terminal 11. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this application embodiment, only the base station in the NR system is used as an example, but the specific type of base station is not limited.

[0056] The relevant technologies involved in this application are described below:

[0057] I. Broadcasting and Multicast

[0058] In LTE broadcast multicast transmission, it supports Multimedia Broadcast Multicast Service (MBMS) transmission via Multimedia Broadcast Multicast Network (MBSFN) and Single Cell Point-to-Multipoint (SC-PTM) multicast transmission. In MBSFN, cells within the same MBSFN area synchronously transmit the same broadcast service, facilitating UE reception. MBMS control information (control channel parameters, service channel parameters, scheduling information, etc.) and data information are transmitted via broadcast, allowing both idle and connected UEs to receive MBMS services. SC-PTM is a standardized multicast transmission method developed after MBMS. Its biggest difference from MBSFN is that it only schedules transmission within a single cell, using the Group Radio Network Temporary Identifier (g-RNTI) for service scheduling. The broadcast message broadcasts control channel parameters, service identifiers, periodic information, etc. The scheduling information is notified by the Physical Downlink Control Channel (PDCCH) scrambled by g-RNTI. The data part is sent in multicast mode, which means that interested UEs listen to g-RNTI to obtain data scheduling and then receive it.

[0059] II. Point-to-Point (PTP) and Point-to-Multipoint (PTM)

[0060] For a multicast service, the network side can configure two paths for the UE to transmit simultaneously: a PTP path (PTP leg) and a PTM path (PTM leg). The PTM path uses a common RNTI, such as a Group-RNTI, to scramble the PDCCH. All users within the group jointly listen to the Group-RNTI's scheduling and receive subsequent scheduling data; a single transmission can be received by multiple UEs. The PTP path, on the other hand, uses a UE-specific C-RNTI to scramble the PDCCH. Only this UE can listen to the C-RNTI's scheduling and receive subsequent scheduling data; a single transmission can only be received by one UE.

[0061] PTM transmits to multiple UEs simultaneously, offering high transmission efficiency. However, it requires comprehensive coverage of all UEs, necessitating the selection of transmission parameters suitable for all UEs. This includes using omnidirectional antennas and considering link quality for users with poor performance. PTM may not be effective for individual UEs with extremely poor link quality. PTP, on the other hand, is a dedicated transmission for a single UE. It considers the user's link conditions and adjusts transmission parameters accordingly, such as using directional or shaped antennas and setting suitable transmission parameters based on the current UE's link. Therefore, it performs well for a single UE, but requires multiple transmission resources for multiple users, resulting in lower resource efficiency.

[0062] The data transmission method, apparatus, terminal, and network-side device provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0063] like Figure 2 As shown in the figure, this application provides a data transmission method, including:

[0064] Step 201: The core network node sends a multicast protocol data unit (PDU) session establishment signaling to the first network-side device;

[0065] Step 202: The core network node sends a unicast PDU session establishment signaling to the first network-side device;

[0066] The multicast path established by the multicast PDU session establishment signaling (it should be noted that this multicast path can also be called a multicast channel, which includes a multicast PDU session and a multicast user plane General Packet Radio Service Tunneling Protocol (Multicast GTP-U) tunnel; the multicast PDU session is the control plane connection of the multicast path, and the multicast GTP-U tunnel is the user plane transmission channel of the multicast path; it should also be noted that one multicast PDU session corresponds to one or more multicast GTP-U tunnels) is used to transmit downlink data streams for multiple terminals in the target service. The unicast path established by the unicast PDU session establishment signaling (it should be noted that this unicast path can also be called a unicast channel, which includes a unicast PDU session and a unicast user plane General Packet Radio Service Tunneling Protocol (UTP-U) tunnel; the unicast PDU session is the control plane connection of the unicast path, and the unicast GTP-U tunnel is the user plane transmission channel of the unicast path; it should also be noted that one unicast PDU session corresponds to one or more unicast GTP-U tunnels) is used to transmit downlink data streams for multiple terminals in the target service. The tunnel is used to transmit uplink and / or downlink data streams for a single terminal in the target service.

[0067] It should be noted that the multicast PDU session establishment signaling is used to instruct the establishment of a multicast PDU session, a multicast GTP-U tunnel, and a multicast radio bearer (MRB) between the core network node, the first network-side device, and the terminal; the unicast PDU session establishment signaling is used to instruct the establishment of a unicast PDU session, a unicast GTP-U tunnel, and a data radio bearer (DRB, which is used for unicast transmission and can therefore also be called a unicast radio bearer).

[0068] It should be noted that in this embodiment, the core network node establishes both multicast and unicast paths. It's important to note that steps 201 and 202 do not have a specific temporal order. Optionally, the core network node can first send a multicast PDU session establishment signaling to the first network-side device to establish a multicast path, and then send a unicast PDU session establishment signaling to the first network-side device at an appropriate time to establish a unicast path. Alternatively, the core network node can first send a unicast PDU session establishment signaling to the first network-side device to establish a unicast path, and then send a multicast PDU session establishment signaling to the first network-side device at an appropriate time to establish a multicast path. Of course, the core network node can also simultaneously send both unicast and multicast PDU session establishment signaling to the first network-side device to establish both unicast and multicast paths.

[0069] Optionally, in order to enable core network nodes to transmit services simultaneously via unicast and multicast paths, embodiments of this application further include:

[0070] The core network node divides the data stream of the target service into a first data stream and a second data stream based on the service information.

[0071] Map the first data stream to the multicast path and the second data stream to the unicast path;

[0072] The first data stream is a downlink data stream for multiple terminals, and the second data stream is a downlink data stream for one terminal.

[0073] Optionally, the service information can be a service attribute, such as the QoS flow of the service. Different QoS flows correspond to different identifiers. In this application, the data flow of the service can be divided based on the identifier of the QoS flow.

[0074] It should be noted that in this embodiment of the application, when the core network node sends service data to the terminal, it divides the data stream of the same service into two parts, and transmits one part each through a multicast path and a unicast path, thereby improving the data transmission efficiency and reducing communication latency.

[0075] It should be noted that the first network-side device mentioned in this application embodiment refers to the device on the access network side, such as a base station or a central unit node on the access network side.

[0076] It should be noted that after the first network-side device receives the multicast PDU session establishment signaling, it needs to send multicast configuration information to the terminal. The multicast configuration information is used to establish a multicast radio bearer for terminals belonging to the same cell. After the first network-side device receives the unicast PDU session establishment signaling, it needs to send unicast configuration information to the terminal. The unicast configuration information is used to establish a unicast radio bearer for the terminal. In this way, a unicast PDU transmission path (including the unicast path and DRB) and a multicast PDU transmission path (including the multicast path and MRB) are established from the core network node to the terminal.

[0077] Specifically, the network architecture involved in this application is as follows: Figure 3 As shown, Figure 3 Taking a terminal as an example, the data transmission path between the network side and the UE side is given. The core network node and the base station transmit data through multicast PDU sessions and their corresponding multicast GTP-U tunnels, and unicast PDU sessions and their corresponding unicast GTP-U tunnels. Data transmission between the base station and the terminal is through MRB and DRB. The terminal uses the Group Radio Network Temporary Identifier (G-RNTI) to listen to multicast data transmitted by the base station and uses the Cell Radio Network Temporary Identifier (C-RNTI) to listen to unicast data transmitted by the base station. Simultaneously, the terminal also sends the uplink data it needs to send to the base station via unicast radio bearer. In practice, there are numerous UEs, and the architecture of each UE and the network side is different. Figure 3 Similarly, the transmission path is also similar. Multiple terminals simultaneously listen to the same G-RNTI on the air interface to obtain the MRB's scheduling and data. Thus, the network side achieves the effect of consuming one set of resources to transmit the common data part to multiple terminals at the same time. The resource utilization rate is greatly improved compared to pure unicast transmission per UE.

[0078] In summary, when core network nodes transmit data, they typically first distinguish the application's service data. Based on service information (e.g., the attributes or content of the service data), they divide it into data common to multiple terminals (i.e., data applicable to multiple terminals) and data independent for each terminal (i.e., data specific to each terminal). For example, different QoS flows can be used to distinguish them. Specifically, the background data of XR services is the common data, while the data from different perspectives of each UE is the terminal-specific data. The transmission characteristics of these two parts of data may be the same or similar, but because their triggering and requirements are different, they can be distinguished by port numbers or other dimensions. Thus, by setting different dimensions, they can be filtered into different QoS flows.

[0079] Next, the core network node can transmit the differentiated data for different QoS flows to the base station (e.g., gNB) via multicast GTP-U tunnel and unicast GTP-U tunnel, respectively. When the base station adopts a Centralized Unit / Distributed Unit (CU-DU) architecture, a corresponding F1 interface GTP-U tunnel needs to be established and maintained between the CU and DU. At least one shared F1 GTP-U tunnel should be established for the multicast PDU session for the transmission of common data on the F1 interface, and a specific F1 GTP-U tunnel should be established for each UE's unicast PDU session for the transmission of UE-specific data on the F1 interface.

[0080] Then, on the Uu interface, the gNB will use G-RNTI to schedule MRB data in the multicast path to be transmitted to all UEs in the group, while using C-RNTI to schedule DRB data in the unicast path to be transmitted to a specific UE.

[0081] For the UE, both the data received from the MRB and the data received from the DRB are sent to the APP layer for unified coordination and processing. If the APP layer has uplink data to send, it sends it to the application server side of the core network through the DRB and unicast path.

[0082] In other words, when transmitting data, this application can simultaneously utilize both multicast and unicast paths to send downlink data, while the terminal can use the unicast path to send uplink data, thereby improving data transmission efficiency.

[0083] Optionally, step 201 in this embodiment of the application can be implemented as follows:

[0084] Based on the first information, the core network node sends a multicast PDU session establishment signaling message to the first network-side device;

[0085] The first information includes at least one of the following:

[0086] A11. Terminal information accessing the first network-side device;

[0087] It should be noted that this terminal information may refer to the number of terminals. Since the core network node and the first network-side device need to establish control plane connections and user plane pipelines for the terminals, the core network node can directly obtain the number of terminals accessing the first network-side device.

[0088] A12. Business information processed by the terminal;

[0089] The core network nodes can directly obtain information about the type of service the terminal is performing. This service information is mainly used to distinguish between service types and service content.

[0090] A13. The cell to which the terminal accessing the first network-side device belongs;

[0091] It should be noted that the home cell is the cell that the terminal accesses under the first network-side device, which can also be understood as the serving cell of the terminal.

[0092] A14. Multicast PDU session establishment request;

[0093] It should be noted that the multicast PDU session establishment request is usually sent by the first network-side device to the core network node to request the core network node to establish a multicast PDU session.

[0094] The specific usage of each parameter in A11-A14 is explained below.

[0095] Specific usage scenario 1: The core network node sends multicast PDU session establishment signaling to the first network-side device based on A11 and A12.

[0096] It should be noted that in this case, the core network node sends multicast PDU session establishment signaling to the first network-side device based on the number of terminals accessing the first network-side device that are performing the same service (e.g., performing the same type and content of service, such as multiple terminals transmitting the same video).

[0097] Optionally, further, if the core network node determines that the number of terminals accessing the first network-side device to perform the same service is greater than or equal to the first threshold, then it sends a multicast PDU session establishment signaling to the first network-side device.

[0098] It should be noted that this situation can be understood as the core network node establishing a large multicast path for the first network-side device. This multicast path is for the first network-side device as a whole. In this case, the first network-side device needs to further determine the cells that can establish the multicast path based on the multicast path establishment signaling.

[0099] Specific Usage Scenario 2: The core network node sends multicast PDU session establishment signaling to the first network-side device based on A11, A12, and A13.

[0100] It should be noted that when the core network node can obtain the cell to which the terminal belongs, the core network node can accurately establish a multicast path for the cell. Typically, when a new terminal accesses a cell or the terminal performs a cell handover under the first network side device, the cell to which the terminal belongs changes. Therefore, the first network side device needs to send the cell to which the terminal belongs to the core network node every time this happens.

[0101] It should be noted that in this case, the core network node sends multicast PDU session establishment signaling to the first network side device based on the number of terminals performing the same service in the same cell connected to the first network side device.

[0102] Optionally, further, if the core network node determines that the number of terminals performing the same service in the same cell accessing the first network-side device is greater than or equal to the second threshold, then it sends a multicast PDU session establishment signaling to the first network-side device.

[0103] For example, when the core network node obtains that there are 50 terminals accessing cell A, 100 terminals accessing cell B, and 80 terminals accessing cell C under the first network-side device, and the second threshold is set to 3, the core network node determines, based on the service information of the terminals, that there are 2 terminals performing the same service under cell A, 5 terminals performing the same service under cell B, and 2 terminals performing the same service under cell C. Then, the core network node establishes a multicast path for cell B and sends a multicast path establishment signaling to the core network node.

[0104] It should be noted that in both Specific Use Case 1 and Specific Use Case 2, the multicast establishment process is triggered by the core network node, for example, by the Access and Mobility Management Function (AMF) or the Session Management Function (SMF). Since the core network node has a relatively detailed understanding of which services each UE has, it can directly determine the number of UEs receiving the same service. However, the core network node does not currently have real-time knowledge of the UE's home cell. This is because, for the core network node, which is a node on the core network side, most of the interaction between the core network (CN) and the access network (RAN) is sufficient at the base station level. That is, according to the existing process, the CN node can know which base station the UE belongs to, but it does not always need to know the specific cell information. In Specific Use Case 2 of this application, in order for the core network node to clearly determine the number of UEs receiving the same service under the same cell, it is necessary to update the serving cell information of each UE to the CN node in real time. Optionally, for cases where UEs belong to different cells but can switch to the same cell because the cell coverage is the same, it is also necessary to inform the CN node of the coverage of different cells under the base station. In summary, with the above information, the CN node can accurately determine the number of UEs receiving the same service within the same cell.

[0105] Specific Usage Scenario 3: The core network node sends a multicast PDU session establishment signaling to the first network-side device based on A14.

[0106] It should be noted that the multicast PDU session establishment request is usually sent by the first network-side device to the core network node. The first network-side device usually sends the multicast PDU session establishment request based on the number of terminals that are accessing and performing the same service.

[0107] Optionally, the first network-side device can send a multicast PDU session establishment request based on the number of terminals it has accessed that receive the same service. For example, when the first network-side device learns that the number of terminals it has accessed that receive the same service is greater than or equal to the third threshold, it can send a multicast PDU session establishment request to the core network node.

[0108] Alternatively, the first network-side device may send a multicast PDU session establishment request based on the number of terminals receiving the same service accessed under each cell. For example, when the first network-side device learns that the number of terminals receiving the same service accessed under cell A, cell B, and cell C is greater than or equal to the fourth threshold, it may send a multicast PDU session establishment request to the core network node.

[0109] It should be noted that, in this case, in order for the first network-side device to distinguish whether the terminals are performing the same service, the core network node should send service attribute information to the first network-side device. The service attribute information is used to determine whether different terminals are performing the same service.

[0110] It should be noted that in specific use case three, the first network-side device determines whether to establish a multicast path and requests it from the core network node. For example, the gNB or CU can determine whether to establish a multicast path and request it from the core network node. Since the gNB has the most real-time information on the serving cell of each UE, and can more accurately judge whether UEs receiving the same service can be switched to a single cell for multicast reception based on the coverage of different cells under the gNB, the RAN node is also a good choice for judgment. However, the RAN node's current knowledge of UE service information is not accurate enough. For example, UE 1's unicast PDU session 1 carries QoS flows 1-8, and UE 2's unicast PDU session 1 also carries QoS flows 1-7. For the RAN node, the above information alone is not enough to determine whether the two UEs are receiving the same service. The core network needs to provide additional indications for the service information. For example, when the core network sends PDU session or QoS flow information to the RAN node, it can use special display indications or a unified index identifier so that the RAN node can know their consistency and thus determine which UEs are receiving the same service.

[0111] Optionally, in order to clearly inform the base station which terminals can transmit data through the multicast path, the multicast PDU session establishment signaling usually needs to include the identification information of at least one terminal. That is, the multicast PDU session establishment signaling carries a terminal list. After receiving the terminal list, the base station can know which terminals have the possibility of joining multicast and which terminals it can send multicast configuration to in order to configure the multicast radio bearer for the terminals.

[0112] Optionally, the multicast PDU session establishment signaling may also include Quality of Service (QoS) flow information;

[0113] The QoS flow information is used to assist the first network-side device in performing Radio Resource Control (RRC) reconfiguration.

[0114] It should be noted that when configuring multicast for the terminal, the first network-side device needs to inform the terminal of the QoS flow information so that the terminal knows the mapping relationship between the multicast radio bearer and the QoS flow (i.e., which QoS flows can be transmitted in the multicast radio bearer), so as to ensure that the terminal can accurately receive the QoS flow.

[0115] It should be noted that multicast transmission paths only have a definite gain when the number of UEs receiving the same service within the same cell reaches a certain level. Otherwise, when the number of UEs is too small, the multicast transmission gain is unclear, resulting only in additional control signaling and complexity overhead. This application's embodiments provide a basic scheme for modifying the path under different circumstances to further adapt to different needs and achieve better system efficiency.

[0116] The specific process of changing the path is explained below: For the establishment of multicast paths, generally speaking, when the service has not started, the service has just started, or the number of receiving UEs is small, it is not necessary to directly decide to establish a multicast path. This is because at this time, the distribution of receiving UEs is very likely that no UE in most cells is receiving the service, and only a few cells have one UE receiving it. In such scenarios, the establishment of multicast paths can only bring additional signaling overhead and processing complexity, and cannot bring the gain of multicast transmission. Therefore, it is not recommended to establish multicast paths.

[0117] Multicast path establishment is only required when the number of users receiving the same service in a cell reaches a certain scale, i.e., exceeds a certain threshold. Specifically, the number of UEs in a cell can refer to the UEs connected to that cell as their serving cell, or it can refer to UEs that are not currently configured as the UE's serving cell, but can be configured as such, for example, because the UE's own serving cell and the current cell share the same carrier coverage, allowing the UE to switch to the current cell, or when the UE has the capability to receive multicast transmissions in a non-serving cell.

[0118] Once a multicast path is established, for UEs that have already established unicast paths and DRBs (Data Receipt Blocks) and have entered the service earlier, they are reconfigured, and some data streams are remapping onto the new transmission channel for transmission. The remapping process is performed by the network implementation, and since the multicast path and unicast path, as well as the air interface RB, are two completely independent sets, it is difficult to ensure that there is no loss during the path switching process. We can only try to ensure that the UE can continue to receive data, and there may be a small number of interruptions and duplicates.

[0119] For UEs joining a new service after a multicast path has been established, they can directly use both the multicast and unicast paths to receive data without needing a data remapping process.

[0120] When a multicast path is established, the CN node needs to inform the RAN node which UE services can be transmitted via the multicast path, i.e., the relevant UE list. More detailed information can include QoS flow information, so that the gNB can perform the RRC reconfiguration process for the relevant UEs, configure one or more MRB bearers corresponding to the multicast path on the Uu interface, and map which QoS flows to these MRB bearers respectively.

[0121] Optionally, after establishing a multicast path, the multicast path may become unsuitable due to changes in terminal access. In this case, it is necessary to release the multicast path. One specific implementation of this application embodiment is as follows:

[0122] Based on the second information, the core network node sends a multicast PDU session release signaling to the first network-side device;

[0123] The second information includes at least one of the following:

[0124] B11. Terminal information for receiving multicast services when accessing the first network-side device;

[0125] Optionally, in this case, for the core network node to actively release the multicast path, the core network node may send a multicast PDU session release signaling message based on the number of terminals receiving multicast services connected to the first network-side device. For example, when the number of terminals receiving multicast services connected to the first network-side device is less than or equal to a fifth threshold, the core network node sends a multicast PDU session release signaling message to the first network-side device. Alternatively, the core network node may send a multicast PDU session release signaling message based on the number of terminals receiving multicast services connected to a specific cell connected to the first network-side device. For example, when the number of terminals receiving multicast services connected to a specific cell (e.g., cell A) connected to the first network-side device is less than or equal to a sixth threshold, the core network node sends a multicast PDU session release signaling message to the first network-side device.

[0126] B12. Multicast PDU session release request, which is sent by the first network-side device;

[0127] It should be noted that the multicast PDU session release request is usually sent by the first network-side device to the core network node. The first network-side device may send the multicast PDU session release request under the following circumstances.

[0128] Scenario 1: Send a multicast PDU session release request based on the terminal information receiving the multicast service.

[0129] Optionally, the terminal information can be the number of terminals. In this case, for example, when the first network-side device learns that the number of terminals it has accessed to receive multicast services is less than or equal to the seventh threshold, it can send a multicast PDU session release request to the core network node.

[0130] Scenario 2: Send a multicast PDU session release request based on the terminal information of the multicast service receiving terminals accessing each cell.

[0131] Optionally, the terminal information can be the number of terminals. For example, when the first network-side device learns that the number of terminals receiving multicast services accessed by cells A, B, and C is less than or equal to the eighth threshold, it can send a multicast PDU session release request to the core network node.

[0132] It should be noted that the first to eighth thresholds mentioned in the embodiments of this application can be agreed upon by the protocol or configured on the network side.

[0133] In other words, when the number of UEs in the same service group under a cell changes, for example, some UEs are no longer interested in the service and give up receiving it, or some UEs switch to other cells due to mobility, eventually causing the number of UEs in this cell who are interested in the service to fall below a certain threshold, continuing to maintain the multicast path and MRB multicast transmission will have additional complexity for both the network and the UE, but the gain is not significant. At this time, the network can decide to release the multicast path and MRB, and for the small number of UEs that are still receiving the service, the data of the original multicast path will be remapping to the unicast path and DRB to continue transmission.

[0134] Operations such as the establishment, release, and maintenance of multicast paths and MRBs can be implemented on the network. For the UE side, this mainly involves the establishment and release of MRB(s) through the RRC reconfiguration process. With the establishment of the MRB(s), the UE begins to use the corresponding G-RNTI and possible DRX pattern configuration for multicast data monitoring. With the release of the MRB(s), the UE stops using the G-RNTI for multicast data monitoring.

[0135] It should be noted that the embodiments of this application provide a data transmission method that uses multicast path transmission for the common downlink data of multiple users, and unicast path transmission for the relevant UE personalized downlink data and all uplink data. This improves resource utilization while taking into account UE performance and greatly enhances the overall system efficiency.

[0136] It should be noted that the data transmission method provided in this application can be executed by a data transmission device, or by a control module within that data transmission device for executing the data transmission method. This application uses the execution of the data transmission method by a data transmission device as an example to illustrate the data transmission device provided in this application.

[0137] like Figure 4 As shown, this application embodiment provides a data transmission device 400, which utilizes a core network node and includes:

[0138] The first sending module 401 is used to send multicast protocol data unit (PDU) session establishment signaling to the first network-side device;

[0139] The second sending module 402 is used to send unicast PDU session establishment signaling to the first network-side device;

[0140] The multicast path established by the multicast PDU session establishment signaling is used to transmit downlink data streams for multiple terminals in the target service, and the unicast path established by the unicast PDU session establishment signaling is used to transmit uplink data streams and / or downlink data streams for one terminal in the target service.

[0141] Optionally, the first sending module 401 is configured to:

[0142] Based on the first information, a multicast PDU session establishment signaling is sent to the first network-side device;

[0143] The first information includes at least one of the following:

[0144] Terminal information accessing the first network-side device;

[0145] The business information processed by the terminal;

[0146] The cell to which the terminal accessing the first network-side device belongs;

[0147] Multicast PDU session establishment request.

[0148] Optionally, if the first information includes a multicast PDU session establishment request, before the first sending module 401 sends the multicast PDU session establishment signaling to the first network-side device based on the first information, the method further includes:

[0149] The fifth sending module is used to send service attribute information to the first network-side device;

[0150] The service attribute information is used to determine whether different terminals are performing the same service.

[0151] Optionally, the multicast PDU session establishment signaling includes identification information of at least one terminal.

[0152] Optionally, the multicast PDU session establishment signaling may also include Quality of Service (QoS) flow information;

[0153] The QoS flow information is used to assist the first network-side device in performing Radio Resource Control (RRC) reconfiguration.

[0154] Optionally, after the first sending module 401 sends the multicast protocol data unit (PDU) session establishment signaling to the first network-side device, the method further includes:

[0155] The sixth sending module is used to send a multicast PDU session release signaling to the first network-side device based on the second information;

[0156] The second information includes at least one of the following:

[0157] Terminal information for receiving multicast services when accessing the first network-side device;

[0158] Multicast PDU session release request.

[0159] Optionally, the device further includes:

[0160] The segmentation module is used to divide the data stream of the target business into a first data stream and a second data stream based on business information.

[0161] A mapping module is used to map the first data stream to the multicast path and the second data stream to the unicast path;

[0162] The first data stream is a downlink data stream for multiple terminals, and the second data stream is a downlink data stream for one terminal.

[0163] It should be noted that this device embodiment corresponds to the above method embodiment. All implementation processes and methods of the above method embodiment can be applied to this device embodiment and can achieve the same technical effect.

[0164] The data transmission device provided in this application embodiment can achieve... Figure 2 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0165] This application embodiment also provides a core network node, including a processor and a communication interface. The communication interface is used to send multicast protocol data unit (PDU) session establishment signaling to a first network-side device and to send unicast PDU session establishment signaling to the first network-side device.

[0166] The multicast path established by the multicast PDU session establishment signaling is used to transmit downlink data streams for multiple terminals in the target service, and the unicast path established by the unicast PDU session establishment signaling is used to transmit uplink data streams and / or downlink data streams for one terminal in the target service.

[0167] This core network node embodiment corresponds to the aforementioned core network node-side method embodiment. All implementation processes and methods of the aforementioned method embodiments can be applied to this core network node embodiment and achieve the same technical effects. Specifically, Figure 5 A schematic diagram of the hardware structure of a core network node to implement an embodiment of this application.

[0168] The core network node 500 includes an antenna 501, a radio frequency (RF) device 502, and a baseband device 503. The antenna 501 is connected to the RF device 502. In the uplink direction, the RF device 502 receives information through the antenna 501 and transmits the received information to the baseband device 503 for processing. In the downlink direction, the baseband device 503 processes the information to be transmitted and sends it to the RF device 502. The RF device 502 processes the received information and then transmits it through the antenna 501.

[0169] The aforementioned frequency band processing device can be located in the baseband device 503. The method executed by the first network-side device in the above embodiments can be implemented in the baseband device 503, which includes a processor 504 and a memory 505.

[0170] The baseband device 503 may, for example, include at least one baseband board on which multiple chips are disposed, such as... Figure 5 As shown, one of the chips is, for example, a processor 504, which is connected to a memory 505 to call the program in the memory 505 and execute the data transmission method shown in the above method embodiment.

[0171] The baseband device 503 may also include a network interface 506 for exchanging information with the radio frequency device 502, such as a common public radio interface (CPRI).

[0172] Specifically, the first network-side device in this embodiment of the invention further includes: instructions or programs stored in memory 505 and executable on processor 504, wherein processor 504 calls the instructions or programs in memory 505 to execute... Figure 4 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0173] Preferably, this application embodiment also provides a core network node, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor. When the program or instructions are executed by the processor, they implement various processes of the data transmission method embodiment applied to the core network node side and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0174] This application also provides a readable storage medium on which a program or instruction is stored. When the program or instruction is executed by a processor, it implements various processes of the data transmission method embodiment applied to the core network node side and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0175] The computer-readable storage medium mentioned above includes, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0176] Corresponding to the implementation of core network nodes, such as Figure 6 As shown in the embodiments of this application, a data transmission method is also provided, including:

[0177] Step 601: The first network-side device receives the multicast protocol data unit (PDU) session establishment signaling sent by the core network node;

[0178] Step 602: The first network-side device receives the unicast PDU session establishment signaling sent by the core network node;

[0179] The multicast path established by the multicast PDU session establishment signaling is used to transmit downlink data streams for multiple terminals in the target service, and the unicast path established by the unicast PDU session establishment signaling is used to transmit uplink data streams and / or downlink data streams for one terminal in the target service.

[0180] Optionally, before the first network-side device receives the multicast protocol data unit (PDU) session establishment signaling sent by the core network node, the method further includes:

[0181] The first network-side device sends the terminal's home cell to the core network node.

[0182] Optionally, the first network-side device sends the terminal's home cell to the core network node, including:

[0183] When a terminal connected to the first network side device changes its access cell, the first network side device sends the terminal's home cell to the core network node.

[0184] Optionally, before the first network-side device receives the multicast protocol data unit (PDU) session establishment signaling sent by the core network node, the method further includes:

[0185] The first network-side device sends a multicast PDU session establishment request to the core network node.

[0186] Optionally, before the first network-side device sends a multicast PDU session establishment request to the core network node, the method further includes:

[0187] The first network-side device receives service attribute information sent by the core network node;

[0188] The service attribute information is used to determine whether different terminals are performing the same service.

[0189] Optionally, the multicast PDU session establishment signaling includes identification information of at least one terminal.

[0190] Optionally, the multicast PDU session establishment signaling may also include Quality of Service (QoS) flow information;

[0191] The QoS flow information is used to assist the first network-side device in performing Radio Resource Control (RRC) reconfiguration.

[0192] Optionally, after the first network-side device receives the multicast protocol data unit (PDU) session establishment signaling sent by the core network node, the method further includes:

[0193] The first network-side device sends a multicast PDU session release request to the core network node.

[0194] Optionally, the first network-side device sends a multicast PDU session release request to the core network node, including:

[0195] The first network-side device sends a multicast PDU session release request to the core network node based on the terminal information receiving the multicast service.

[0196] Optionally, after the first network-side device receives the multicast protocol data unit (PDU) session establishment signaling sent by the core network node, the method further includes:

[0197] The first core network node sends multicast configuration information to the terminal, which is used to establish multicast radio bearers for terminals belonging to the same cell.

[0198] Optionally, after the first network-side device receives the unicast PDU session establishment signaling sent by the core network node, the method further includes:

[0199] The first core network node sends unicast configuration information to the terminal, which is used to establish a unicast wireless bearer for the terminal.

[0200] It should be noted that the above implementation process corresponds to the implementation process of the core network node. All implementation methods in the above embodiments are applicable to this embodiment and can achieve the same technical effect, so they will not be repeated here.

[0201] Optionally, this application embodiment also provides a method for configuring the terminal to ensure smooth data transmission when the terminal switches to the first network-side device. The specific implementation process is as follows:

[0202] The first network-side device receives the first configuration information of the terminal sent by the second network-side device. The first configuration information includes the correspondence between service flows and unicast radio bearers and / or multicast radio bearers.

[0203] The first network-side device determines the second configuration information used by the terminal based on the first configuration information. The second configuration information is the transmission configuration used by the terminal after switching to the first network-side device.

[0204] The first network-side device sends the second configuration information to the second network-side device.

[0205] It is understood that, in the case of terminal switching, the first network-side device mentioned in the embodiments of this application refers to the network-side device that the terminal will access, while the second network-side device refers to the network-side device that the terminal accesses before the switching. The second network-side device can be considered as the source network-side device, and the first network-side device can be considered as the target network-side device.

[0206] It should be further noted that if a terminal switches between different cells on the same network-side device, then the source network-side device and the target network-side device are the same network-side device. The cell that the terminal accesses before the switch is called the source cell, and the cell that the terminal accesses after the switch is called the target cell.

[0207] In other words, when a UE needs to switch cells due to mobility reasons, the transmission path of the target cell may be the same as or different from that of the current cell. However, after switching to the target cell, the UE can at least continue to receive services using unicast PDU sessions and DRBs.

[0208] Taking the handover between different cells within the same base station as an example, the general handover process is as follows: the source cell informs the target cell of the UE's configuration in this cell, and the target cell determines the new configuration for the UE. In previous interactions, these configurations were mainly air interface configurations. However, in our multi-channel scenario, due to the multicast PDUsession, it is not suitable to directly transmit the MRB configuration from the source cell to the target cell. This is because the target cell does not know what content is being transmitted from the MRB configuration alone. Moreover, this dynamically established multicast transmission channel lacks a unified TMGI identifier that can be recognized by each cell to identify the service. Therefore, the most important thing from the source cell to the target cell is to carry the UE's service requirements. If the DRB configuration or UE QoS flow already contains service information suitable for establishing a multicast channel, then the existing interface information is sufficient. If there is no detailed service information, the detailed service information of the UE can be added to the interface information. For example, explicitly indicating which QoS flows are being transmitted via multicast channels established in the source cell. The target cell can then choose to use unicast or multicast transmission according to its own situation. If the target side selects unicast for transmission, the configuration generated on the target side only needs to include the DRB configuration and the mapping relationship between QoS flow and DRB. If the target side selects multicast for transmission, in addition to the DRB configuration, the target side also needs to include the MRB configuration and the corresponding mapping relationship between QoS flow and the two bearers.

[0209] The target cell's configuration is sent to the source cell via an interface procedure. The source cell organizes handover signaling and sends it to the UE. The UE then accesses the target cell and uses the configuration to perform operations on the target side.

[0210] like Figure 7 As shown, this application embodiment also provides a data transmission device 700, applied to a first network-side device, including:

[0211] The first receiving module 701 is used to receive multicast protocol data unit (PDU) session establishment signaling sent by the core network node;

[0212] The second receiving module 702 is used to receive unicast PDU session establishment signaling sent by the core network node;

[0213] The multicast path established by the multicast PDU session establishment signaling is used to transmit downlink data streams for multiple terminals in the target service, and the unicast path established by the unicast PDU session establishment signaling is used to transmit uplink data streams and / or downlink data streams for one terminal in the target service.

[0214] Optionally, before the first receiving module 701 receives the multicast protocol data unit (PDU) session establishment signaling sent by the core network node, the method further includes:

[0215] The third sending module is used to send the terminal's home cell to the core network node.

[0216] Optionally, the third sending module is configured to:

[0217] When a terminal accessing the first network-side device changes its access cell, the terminal's home cell is sent to the core network node.

[0218] Optionally, before the first receiving module 701 receives the multicast protocol data unit (PDU) session establishment signaling sent by the core network node, the method further includes:

[0219] The fourth sending module is used to send multicast PDU session establishment requests to core network nodes.

[0220] Optionally, before the sixth sending module sends a multicast PDU session establishment request to the core network node, the method further includes:

[0221] The fifth receiving module is used to receive service attribute information sent by the core network nodes;

[0222] The service attribute information is used to determine whether different terminals are performing the same service.

[0223] Optionally, the multicast PDU session establishment signaling includes identification information of at least one terminal.

[0224] Optionally, the multicast PDU session establishment signaling may also include Quality of Service (QoS) flow information;

[0225] The QoS flow information is used to assist the first network-side device in performing Radio Resource Control (RRC) reconfiguration.

[0226] Optionally, before the first receiving module 701 receives the multicast protocol data unit (PDU) session establishment signaling sent by the core network node, the method further includes:

[0227] The seventh sending module is used to send multicast PDU session release requests to core network nodes.

[0228] Optionally, the seventh sending module is configured to:

[0229] Based on the terminal information receiving the multicast service, a multicast PDU session release request is sent to the core network node.

[0230] Optionally, before the first receiving module 701 receives the multicast protocol data unit (PDU) session establishment signaling sent by the core network node, the method further includes:

[0231] The eighth sending module is used to send multicast configuration information to the terminal, wherein the multicast configuration information is used to establish a multicast radio bearer for terminals belonging to the same cell.

[0232] Optionally, before the first receiving module 701 receives the multicast protocol data unit (PDU) session establishment signaling sent by the core network node, the method further includes:

[0233] The ninth sending module is used to send unicast configuration information to the terminal, the unicast configuration information being used to establish a unicast wireless bearer for the terminal.

[0234] Optionally, the device further includes:

[0235] The sixth receiving module is used to receive the first configuration information of the terminal sent by the second network side device. The first configuration information includes the correspondence between service flows and unicast radio bearers and / or multicast radio bearers.

[0236] The determining module is used to determine the second configuration information used by the terminal based on the first configuration information, wherein the second configuration information is the transmission configuration used by the terminal after switching to the first network-side device;

[0237] The tenth sending module is used to send the second configuration information to the second network-side device.

[0238] It should be noted that this device embodiment corresponds to the above method embodiment. All implementation processes and methods of the above method embodiment can be applied to this device embodiment and can achieve the same technical effect.

[0239] Preferably, this application embodiment also provides a network-side device, which is a first network-side device, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor. When the program or instructions are executed by the processor, they implement various processes of the data transmission method embodiment applied to the first network-side device and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0240] This application also provides a readable storage medium on which a program or instructions are stored. When the program or instructions are executed by a processor, they implement various processes of the data transmission method embodiment applied to the first network-side device side and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0241] The computer-readable storage medium mentioned above includes, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0242] This application embodiment also provides a network-side device, which is a first network-side device, including a processor and a communication interface. The communication interface is used to receive multicast protocol data unit (PDU) session establishment signaling sent by the core network node; and to receive unicast PDU session establishment signaling sent by the core network node.

[0243] The multicast path established by the multicast PDU session establishment signaling is used to transmit downlink data streams for multiple terminals in the target service, and the unicast path established by the unicast PDU session establishment signaling is used to transmit uplink data streams and / or downlink data streams for one terminal in the target service.

[0244] This network-side device embodiment corresponds to the method embodiment applied to the first network-side device described above. All implementation processes and methods of the above method embodiment can be applied to this network-side device embodiment and can achieve the same technical effect.

[0245] Specifically, this application embodiment also provides a network-side device, which is a first network-side device. The structure of the first network-side device can be found in [reference needed]. Figure 5 The structure will not be elaborated here.

[0246] Specifically, the processor executes instructions or programs stored in memory. Figure 7 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0247] like Figure 8 As shown in the embodiments of this application, a data transmission method is also provided, including:

[0248] Step 801: The terminal receives multicast configuration information sent by the first network-side device. The multicast configuration information is used to establish a multicast radio bearer for terminals belonging to the same cell.

[0249] Step 802: The terminal receives unicast configuration information sent by the first network-side device. The unicast configuration information is used to establish a unicast wireless bearer for the terminal.

[0250] It should be noted that steps 801 and 802 do not show a specific time sequence. Optionally, the first network-side device can first send multicast configuration information to the terminal to establish a multicast wireless bearer, and then send unicast configuration information to the terminal at an appropriate time to establish a unicast wireless bearer. Optionally, the first network-side device can also first send unicast configuration information to the terminal to establish a unicast wireless bearer, and then send multicast configuration information to the terminal at an appropriate time to establish a multicast wireless bearer. Of course, the first network-side device can also send both unicast configuration information and multicast configuration information to the terminal simultaneously, and establish both unicast and multicast wireless bearers at the same time.

[0251] Through steps 801 and 802, the final terminal simultaneously possesses both multicast and unicast wireless bearers.

[0252] Step 803: The terminal processes the downlink service data in the multicast radio bearer and the downlink service data in the unicast radio bearer.

[0253] Optionally, one implementation of the data processing method described in this application embodiment is as follows: taking XR service as an example, low-definition background service data is received in the multicast channel, while high-definition service data from the UE's current perspective is received in the unicast channel. The two parts are then combined at the APP layer to form a complete picture. What the UE sees is a very clear picture from its current perspective, with slightly blurred surrounding images.

[0254] Optionally, the method further includes:

[0255] The terminal transmits uplink data to the first network-side device via unicast wireless bearer.

[0256] It should be noted that, by transmitting uplink data in a unicast wireless bearer, the embodiments of this application enable the transmission of uplink data and the reception of downlink data to occur simultaneously, thereby improving the interactivity and transmission effect of service data.

[0257] like Figure 9 As shown in the figure, this application embodiment also provides a data transmission device 900, applied to a terminal, including:

[0258] The third receiving module 901 is used to receive multicast configuration information sent by the first network-side device. The multicast configuration information is used to establish a multicast wireless bearer for terminals belonging to the same cell.

[0259] The fourth receiving module 902 is used to receive unicast configuration information sent by the first network-side device, wherein the unicast configuration information is used to establish a unicast wireless bearer for the terminal.

[0260] The processing module 903 is used to process downlink service data in multicast radio bearers and downlink service data in unicast radio bearers.

[0261] Optionally, the device further includes:

[0262] The eleventh transmitting module is used to transmit uplink data to the first network-side device via unicast wireless bearer.

[0263] It should be noted that this device embodiment corresponds to the above method embodiment. All implementation processes and methods of the above method embodiment can be applied to this device embodiment and can achieve the same technical effect.

[0264] The data transmission device in this application embodiment can be a device, a device or electronic device with an operating system, or a component, integrated circuit, or chip in a terminal. The device or electronic device can be a mobile terminal or a non-mobile terminal. For example, a mobile terminal can include, but is not limited to, the types of terminals 11 listed above, while a non-mobile terminal can be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not impose specific limitations.

[0265] Specifically, Figure 10 A schematic diagram of the hardware structure for implementing a terminal.

[0266] The terminal 1000 includes, but is not limited to, at least some of the following components: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.

[0267] Those skilled in the art will understand that the terminal 1000 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 1010 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 10 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0268] It should be understood that, in this embodiment, the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042. The GPU 10041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0269] In this embodiment, the radio frequency unit 1001 receives downlink data from the network-side device and processes it for the processor 1010; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 1001 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0270] The memory 1009 can be used to store software programs or instructions and various data. The memory 1009 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1009 may include high-speed random access memory and non-volatile memory, wherein the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0271] Processor 1010 may include one or more processing units; optionally, processor 1010 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1010.

[0272] The radio frequency unit 1001 is used to implement:

[0273] The system receives multicast configuration information sent by a first network-side device, the multicast configuration information being used to establish a multicast radio bearer for terminals belonging to the same cell; and receives unicast configuration information sent by the first network-side device, the unicast configuration information being used to establish a unicast radio bearer for the terminal.

[0274] The processor 1010 is used to implement:

[0275] Data processing is performed on downlink service data in multicast wireless bearers and downlink service data in unicast wireless bearers.

[0276] Optionally, the radio frequency unit 1001 is further configured to:

[0277] Uplink data is sent to the first network-side device via unicast wireless bearer.

[0278] Preferably, this application embodiment also provides a terminal, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor. When the program or instructions are executed by the processor, they implement the various processes of the data transmission method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0279] This application also provides a readable storage medium storing a program or instructions. When executed by a processor, the program or instructions implement various processes of the data transmission method embodiment and achieve the same technical effect. To avoid repetition, these will not be described again here. The computer-readable storage medium may include read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. It should be noted that the readable storage medium in this application embodiment can be volatile or non-volatile. Furthermore, the readable storage medium can be a non-transient readable storage medium.

[0280] Optional, such as Figure 11As shown in the illustration, this application also provides a communication device 1100, including a processor 1101, a memory 1102, and a program or instructions stored in the memory 1102 that can run on the processor 1101. For example, when the communication device 1100 is a terminal, the program or instructions executed by the processor 1101 implement the various processes of the above-described data transmission method embodiments and achieve the same technical effect. When the communication device 1100 is a first network-side device, the program or instructions executed by the processor 1101 implement the various processes of the above-described data transmission method embodiments and achieve the same technical effect. When the communication device 1100 is a core network node, the program or instructions executed by the processor 1101 implement the various processes of the above-described data transmission method embodiments and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0281] The terminal involved in the embodiments of this application can be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The name of the terminal device may differ in different systems; for example, in a 5G system, the terminal device can be called a User Equipment (UE). The wireless terminal device can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). The wireless terminal device can be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device, for example, a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device. These exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments of this application.

[0282] The first network-side device involved in the embodiments of this application can be a base station (BTS) in Global System for Mobile communication (GSM) or Code Division Multiple Access (CDMA), a base station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), an evolved Node B (eNB or eNodeB) in LTE, a relay station or access point, or a base station in a future 5G network, etc., and is not limited thereto.

[0283] The first network-side device and the terminal can each use one or more antennas to perform multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multiple-user MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, precoding transmission, or beamforming transmission, etc.

[0284] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above data transmission method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0285] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0286] This application also provides a computer program / program product, which is stored in a non-transient storage medium. The program / program product is executed by at least one processor to implement the various processes of the above-described data transmission method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0287] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0288] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0289] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A data transmission method, characterized by, The method comprises: The core network node sends multicast protocol data unit (PDU) session establishment signaling to the first network side device; The core network node sends unicast PDU session establishment signaling to the first network side device; The multicast path established by the multicast PDU session establishment signaling is used to transmit downlink data flow for multiple terminals in the target service, and the unicast path established by the unicast PDU session establishment signaling is used to transmit uplink data flow and / or downlink data flow for one terminal in the target service; The multicast path and the unicast path can simultaneously transmit the target service; The method further comprises: The core network node divides data flow of the target service into first data flow and second data flow through service information, wherein the service information is service attribute; The first data flow is mapped to the multicast path, and the second data flow is mapped to the unicast path, so as to realize simultaneous transmission of the first data flow and the second data flow; The first data flow is downlink data flow for multiple terminals, and the second data flow is downlink data flow for one terminal.

2. The method of claim 1, wherein, The core network node sends multicast protocol data unit (PDU) session establishment signaling to the first network side device, which comprises: The core network node sends multicast PDU session establishment signaling to the first network side device according to first information; The first information comprises at least one of the following: Terminal information accessing the first network side device; Service information performed by the terminal; A home cell of the terminal accessing the first network side device; Multicast PDU session establishment request.

3. The method of claim 2, wherein, In the case where the first information comprises the multicast PDU session establishment request, before the core network node sends the multicast PDU session establishment signaling to the first network side device according to the first information, the method further comprises: The core network node sends service attribute information to the first network side device; The service attribute information is used to determine whether services performed by different terminals are the same.

4. The method of claim 2, wherein, The multicast PDU session establishment signaling comprises identification information of at least one terminal.

5. The method of claim 4, wherein, The multicast PDU session establishment signaling further comprises quality of service (QoS) flow information; The QoS flow information is used to assist the first network side device in performing radio resource control (RRC) reconfiguration.

6. The method of claim 1, wherein, After the core network node sends the multicast protocol data unit (PDU) session establishment signaling to the first network side device, the method further comprises: The core network node sends multicast PDU session release signaling to the first network side device according to second information; The second information comprises at least one of the following: Terminal information accessing the first network side device and receiving multicast service; Multicast PDU session release request. 7.A data transmission apparatus applied to a core network node, characterized in that, The method comprises: A first sending module configured to send multicast protocol data unit (PDU) session establishment signaling to the first network side device; A second sending module configured to send unicast PDU session establishment signaling to the first network side device; The multicast PDU session establishment signaling establishes a multicast path for transmitting downlink data streams for multiple terminals in a target service, and the unicast PDU session establishment signaling establishes a unicast path for transmitting uplink data streams and / or downlink data streams for one terminal in the target service. The multicast path and the unicast path can simultaneously transmit the target service. The apparatus further includes: The dividing module divides data streams of the target service into first data streams and second data streams according to service information, wherein the service information is service attributes. The mapping module maps the first data streams to the multicast path and maps the second data streams to the unicast path, so as to simultaneously transmit the first data streams and the second data streams. The first data streams are downlink data streams for multiple terminals, and the second data streams are downlink data streams for one terminal.

8. The apparatus of claim 7, wherein, The first sending module sends multicast PDU session establishment signaling to a first network side device according to first information. The first information includes at least one of the following: Terminal information accessing the first network side device; Service information performed by a terminal; A home cell of a terminal accessing the first network side device; A multicast PDU session establishment request. The processor, the memory, and the program or instructions stored on the memory and executable on the processor are used to implement the steps of the data transmission method according to any one of claims 1 to 6.

9. A core network node, characterized by, The program or instructions stored on the readable storage medium are used to implement the steps of the data transmission method according to any one of claims 1 to 6 when executed by the processor.

10. A readable storage medium, characterized by, ​

Images