Multicast control, switching configuration methods, devices and equipment

Abstract

This application discloses a multicast control and handover configuration method, apparatus, and device. The multicast control method includes: a core network node sending multicast PDU session signaling to a first network-side device based on first information; wherein the first information includes at least one of the following: terminal information accessing the first network-side device; service information performed by the terminal; the home cell of the terminal accessing the first network-side device; a multicast PDU session establishment request; a first service that is the same as the service transmitted in the multicast PDU session, wherein the first service is the service requested by the first terminal through the cell or the first network-side device that established the multicast PDU session; a multicast PDU session update request; a second terminal ceasing to receive the multicast service transmitted in the multicast PDU session; and the second terminal being uninterested in the multicast service transmitted in the multicast PDU session.

Description

Technical Field

[0001] This application belongs to the field of communications, and specifically relates to a multicast control, handover configuration method, apparatus and device. 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 flexible and rapid dynamic multicast service establishment and transmission based on needs. Therefore, it cannot effectively address a wider range of service and transmission requirements. Summary of the Invention

[0003] This application provides a multicast control, switching configuration method, apparatus, and device that can solve the problem that existing technologies cannot flexibly perform multicast control.

[0004] Firstly, a multicast control method is provided, including:

[0005] Based on the first information, the core network node sends multicast protocol data unit (PDU) session signaling to the first network-side device;

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

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

[0008] The business information processed by the terminal;

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

[0010] Multicast PDU session establishment request;

[0011] The first service is the same as the service transmitted in the multicast PDU session. The first service is the service requested by the first terminal through the cell or the first network-side device that establishes the multicast PDU session.

[0012] A multicast PDU session update request, wherein the multicast PDU session update request is used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session; the second terminal moves out of the first network-side device; and the second terminal joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session.

[0013] The second terminal stops receiving multicast services transmitted in the multicast PDU session;

[0014] The second terminal is not interested in the multicast services transmitted in the multicast PDU session.

[0015] Secondly, a multicast control device is provided, applied to core network nodes, including:

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

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

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

[0019] The business information processed by the terminal;

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

[0021] Multicast PDU session establishment request;

[0022] The first service is the same as the service transmitted in the multicast PDU session. The first service is the service requested by the first terminal through the cell or the first network-side device that establishes the multicast PDU session.

[0023] A multicast PDU session update request, wherein the multicast PDU session update request is used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session; the second terminal moves out of the first network-side device; and the second terminal joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session.

[0024] The second terminal stops receiving multicast services transmitted in the multicast PDU session;

[0025] The second terminal is not interested in the multicast services transmitted in the multicast PDU session.

[0026] Thirdly, a multicast control method is provided, including:

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

[0028] Fourthly, a multicast control device is provided, applied to a first network-side device, comprising:

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

[0030] Fifthly, a method for switching configurations is provided, including:

[0031] The second network-side device sends the first configuration information of the fourth terminal to the first network-side device;

[0032] The second network-side device receives the second configuration information fed back by the first network-side device;

[0033] The first configuration information is the transmission configuration of the fourth terminal under the second network-side device. The first configuration information includes the correspondence between service flows and unicast radio bearers and / or multicast radio bearers. The second configuration information is the transmission configuration used by the fourth terminal after switching to the first network-side device.

[0034] Sixthly, a switching configuration device is provided, applied to a second network-side device, comprising:

[0035] The second sending module is used to send the first configuration information of the fourth terminal to the first network-side device;

[0036] The second receiving module is used to receive the second configuration information fed back by the first network-side device;

[0037] The first configuration information is the transmission configuration of the fourth terminal under the second network-side device. The first configuration information includes the correspondence between service flows and unicast radio bearers and / or multicast radio bearers. The second configuration information is the transmission configuration used by the fourth terminal after switching to the first network-side device.

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

[0039] 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 signaling to the first network-side device based on first information;

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

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

[0042] The business information processed by the terminal;

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

[0044] Multicast PDU session establishment request;

[0045] The first service is the same as the service transmitted in the multicast PDU session. The first service is the service requested by the first terminal through the cell or the first network-side device that establishes the multicast PDU session.

[0046] A multicast PDU session update request, wherein the multicast PDU session update request is used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session; the second terminal moves out of the first network-side device; and the second terminal joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session.

[0047] The second terminal stops receiving multicast services transmitted in the multicast PDU session;

[0048] The second terminal is not interested in the multicast services transmitted in the multicast PDU session.

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

[0050] 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 signaling sent by a core network node.

[0051] Eleventhly, a network-side device is provided, the network-side device being a second 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.

[0052] In a twelfth aspect, a network-side device is provided, the network-side device being a second network-side device, including a processor and a communication interface, wherein the communication interface is used to send first configuration information of a fourth terminal to a first network-side device; and to receive second configuration information fed back by the first network-side device;

[0053] The first configuration information is the transmission configuration of the fourth terminal under the second network-side device. The first configuration information includes the correspondence between service flows and unicast radio bearers and / or multicast radio bearers. The second configuration information is the transmission configuration used by the fourth terminal after switching to the first network-side device.

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

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

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

[0057] In this embodiment of the application, by dynamically managing multicast PDU sessions based on the first information, dynamic control of multicast can be performed according to the network status, thereby improving the flexibility of multicast control. Attached Figure Description

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

[0059] Figure 2 This is one of the flowcharts illustrating the multicast control method according to an embodiment of this application;

[0060] Figure 3 This is one of the module schematic diagrams of the multicast control device according to an embodiment of this application;

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

[0062] Figure 5 This is a second schematic flowchart of the multicast control method according to an embodiment of this application;

[0063] Figure 6 This is a second schematic diagram of the multicast control device according to an embodiment of this application;

[0064] Figure 7 This is a flowchart illustrating the configuration switching method according to an embodiment of this application;

[0065] Figure 8 This is a schematic diagram of the switching configuration device according to an embodiment of this application;

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

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

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

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

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

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

[0072] I. Broadcasting and Multicast

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

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

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

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

[0077] The multicast control, switching configuration method, apparatus, and device provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0078] like Figure 2 As shown, this application provides a multicast control method, including:

[0079] Step 201: Based on the first information, the core network node sends a multicast protocol data unit (PDU) session signaling message to the first network-side device;

[0080] It should be noted that this multicast PDU session signaling can be either multicast PDU session establishment signaling or multicast PDU session update signaling. Under normal circumstances, at any given time, a core network node can only send multicast PDU session establishment signaling or multicast PDU session update signaling to the first network-side device.

[0081] Optionally, the first information includes at least one of the following:

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

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

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

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

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

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

[0088] A14. Multicast PDU session establishment request;

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

[0090] A15. The first service is the same as the service transmitted in the multicast PDU session;

[0091] It should be noted that the first service is the service requested by the first terminal through the cell or the first network-side device that establishes a multicast PDU session;

[0092] A16, Multicast PDU Session Update Request;

[0093] It should be noted that this multicast PDU session update request is used to indicate at least one of the following:

[0094] The second terminal is removed from the cell corresponding to the multicast PDU session;

[0095] The second terminal was removed from the first network-side device;

[0096] The second terminal joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session.

[0097] It should be noted that this multicast PDU session update request is usually sent by the first network-side device to the core network node to request the core network node to perform a multicast PDU session update.

[0098] A17. The second terminal stops receiving multicast services transmitted in the multicast PDU session;

[0099] A18. The second terminal is not interested in the multicast services transmitted in the multicast PDU session.

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

[0101] The implementation of this application will be explained in detail below from the perspectives of multicast PDU session establishment and multicast PDU session update.

[0102] I. Establishment of Multicast PDU Sessions

[0103] It should be noted that, typically, the core network node sends a multicast PDU session establishment signaling to the first network-side device according to at least one of A11-A14.

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

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

[0106] 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).

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

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

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

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

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

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

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

[0114] It should be noted that the multicast establishment process in Specific Use Case 1 and Specific Use Case 2 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 A12 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, the serving cell information of each UE needs to be updated to the CN node in real time. Furthermore, for cases where UEs belong to different cells but can switch to the same cell due to the same cell coverage, the CN node also needs to be informed 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.

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

[0116] 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 connected and receiving the same service.

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

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

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

[0120] In summary, the multicast establishment in this application is not pre-planned, but dynamically determined based on the UE's service situation or the number of UEs receiving the same service. A typical scenario is that N UEs are already receiving the same service via unicast within a single cell. The core network node (e.g., SMF / AMF / User Plane Function (UPF)) can decide to establish multicast for these UEs to transmit the service, based on the fact that these UEs belong to the same cell, have identical service content, and the service meets certain Quality of Service (QoS) attributes, such as strong real-time performance and low sensitivity to block error rate.

[0121] The core network node (e.g., the AMF) then initiates a new PDU session establishment process with the base station where these UEs are located. This process is used to establish a multicast path between the core network node and the base station. It should be noted that this multicast path can also be called a multicast channel, which includes a multicast PDU session and a 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. Typically, the multicast PDU session establishment signaling needs to carry identification information of at least one terminal associated with the session (which can be understood as carrying a list of terminals (UEs) associated with the session). Optionally, this identification information can be at least one of the following: AMF UE NGAP ID, RAN UE NGAP ID, and 5G Temporary Mobile Subscriber Identity (5G-S-TMSI). Typically, when the multicast path is established for a cell, these UEs need to be under the same base station and belong to the same cell or be able to hand over to the same cell; or when the multicast path is established for the base station, after receiving the multicast PDU session establishment signaling, the base station determines which cells to use PTM in based on the cell information of the terminals included in the UE list and responds to the CN node. Each UE's current home cell can be updated to the core network node through the mobility process. Therefore, the core network node knows the UE's current home cell. For example, during or after intra-site handover, the serving base station will inform the AMF of the new serving cell. As for other UEs that can be handed over to in the same cell, this is determined by the fact that the home cell of other UEs is in the same coverage as the cell to be established for multicast. This information is obtained by the core network node through network planning or deployment information.

[0122] It should also be noted that after the first network-side device receives the multicast PDU session establishment signaling and obtains the UElist, it can further implement the following process:

[0123] If there is a third terminal among the terminals corresponding to the multicast PDU session, a configuration message is sent to the third terminal. The configuration message is used to indicate at least one of the following: the third terminal switches to the cell corresponding to the multicast PDU session, adds the cell corresponding to the multicast PDU session as the secondary cell of the third terminal, and notifies the third terminal of the cell corresponding to the multicast PDU session and the configuration.

[0124] The serving cell of the third terminal is different from the cell corresponding to the multicast PDU session.

[0125] It should be noted that if the terminal can only receive multicast services under the serving cell, the first network-side device can initiate a handover process to switch the UE that is not connected to the current cell to the current cell or add the current cell as a secondary cell (Scell). If the UE that is not in the current cell has the relevant capabilities (for example, it can receive multicast services on a non-serving cell), the first network-side device does not need to perform the above process, but can directly inform the terminal of the cell corresponding to the multicast PDU session and the configuration.

[0126] Optionally, after the first network-side device receives the multicast PDU session establishment signaling and obtains the UE list, it can further implement the following process:

[0127] The first network-side device sends a response message to the core network node;

[0128] The response message carries acceptance information and / or rejection information;

[0129] The rejection information is used to indicate terminal information that cannot perform multicast reception in the cell under the first network side device;

[0130] The received information is used to indicate terminal information that can perform multicast reception in a cell under the first network-side device.

[0131] In other words, in this case, the first network-side device can report the accepted and / or rejected terminals back to the core network node.

[0132] Optionally, the first network-side device configures MRB-related configurations for UEs in the UE list that can perform multicast reception through a dedicated RRC signaling process. These configurations include, for example, G-RNTI, discontinuous reception (DRX) parameters, MRB ID, etc., as well as Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Medium Access Control (MAC), and physical (PHY) layer configurations, and the mapping relationship between QoS flow and MRB.

[0133] It should also be noted that after the first network-side device completes the multicast PDU session establishment, it needs to send a multicast PDU session establishment completion message to the core network node. Upon receiving this message, the core network node, when a data transmission request arises, will transmit the common data on one or more Multicast GTP-U tunnels corresponding to the multicast PDU session. It will no longer use the unicast path (which can also be called a unicast channel, including the unicast PDU session and the unicast user plane General Packet Radio Service Tunneling Protocol channel (unicast GTP-U tunnel)) originally used by each UE for this data transmission. The core network can decide whether to release or retain the unicast path. Retention is generally due to UE-specific services requiring transmission on that unicast path, or for better UE mobility. If the unicast path is retained, the base station will not delete the corresponding data radio bearer (DRB; it should be noted that the DRB is used for unicast transmission, so it can also be called a unicast radio bearer). If the unicast path is released, the base station will send the corresponding DRB release signaling to the UE.

[0134] For the UE, if a reconfiguration message or MRB establishment signaling is received in the connected state, the UE establishes the MRB according to the message, returns a completion message to the base station, and starts listening to the data scheduled by the corresponding Group Radio Network Temporary Identifier (G-RNTI).

[0135] Once the MRB of the multicast GTP-U tunnel and the Uu interface is established, the core network can start using this path to transmit public data. That is, the public data is first transmitted to the base station through the public multicast GTP-U tunnel, and then the base station sends it to N UEs at once through G-RNTI group scheduling, which greatly saves resource overhead. It changes from unicast scheduling that originally required N transmission resources to multicast scheduling that only requires 1 transmission resource.

[0136] Specifically, when the base station is a network architecture composed of Centralized Unit / Distributed Unit (CU-DU) nodes, the multicast path from the core network node to the base station is established as a data plane pipeline between the UPF and CU nodes, such as a GTP-U tunnel. A pipeline is also needed between the CU and DU nodes to carry the data. In general, a shared F1 pipeline, such as a GTP-U tunnel, can also be used to transmit data from the CU to the DU node where the cell is located.

[0137] It's important to note that before a multicast path is successfully established, the network transmits data through each UE's own unicast GTP-U tunnel. Since each UE joins the service at different times, their unicast GTP-U tunnel transmission patterns differ; specifically, the GTP-U tunnel SN may be different. Therefore, for a newly established multicast GTP-U tunnel, since it's impossible to guarantee simultaneous synchronization with all UEs' unicast GTP-U tunnels, the simplest approach is to treat the multicast GTP-U tunnel as a new pipeline and start transmission from the initial state. The transmitted data content can be tailored to different UEs, prioritizing slower UEs by starting transmission from their current progress. This ensures that most users see continuous downlink data, with some minor overlap but no missing data.

[0138] For the UE, although the data previously received from the DRB and the data subsequently received from the MRB belong to the same QoS flow and service source, because the pipeline has been completely re-established—typically, the MRB and DRB are completely independent protocol stacks, with independent PDCP entities and unrelated SNs—the UE cannot perform any reordering or duplicate detection to achieve a completely lossless and continuous service experience. If lossless and continuous performance is required, relevant ordering and duplicate detection must be performed on the service source side. Therefore, this approach is more suitable for live streaming or real-time video services.

[0139] Because data switching between two pipelines cannot achieve complete continuity and losslessness, it can only ensure continuity and cannot avoid temporary duplication or loss. Therefore, data switching between pipelines should not be frequent or dynamic, and this generally occurs in the following situations:

[0140] The establishment, release, or modification of a multicast pipeline can cause a UE to enter or leave a multicast group.

[0141] The UE has been switched over.

[0142] It should be noted that the above describes the situation where multiple UEs are receiving services, that is, multiple UEs have already established unicast PDU sessions, unicast GTP-U tunnels and DRB pipes with the core network nodes for service transmission. Subsequently, the network side will establish a new multicast PDU session, multicast GTP-U tunnel and MRB pipe for the transmission of common data in these services.

[0143] II. Updates for Multicast PDU Sessions

[0144] It should be noted that, typically, the core network node sends a multicast PDU session update signaling to the first network-side device according to one of A15-A18.

[0145] The specific usage of each parameter in A15-A18 is explained below.

[0146] Specific usage scenario 1: The core network node sends a multicast PDU session update signaling to the first network-side device based on A15.

[0147] It should be noted that in this case, the core network learns that a new terminal can join the multicast PDU session, and sends a multicast PDU session update signaling to the first network-side device to indicate that a terminal has been added to the multicast PDU session. Usually, in this case, the multicast PDU session update signaling will carry the identification information of the first terminal (the newly joined terminal).

[0148] Specific Usage Scenario 2: The core network node sends multicast PDU session update signaling to the first network-side device based on A16.

[0149] It should be noted that in this case, the multicast PDU session update is requested by the first network-side device. Optionally, if the second terminal moves out of the cell corresponding to the multicast PDU session or moves out of the second network-side device, the first network-side device sends a multicast PDU session update request to the core network node. It should be noted that this update is to reduce the number of terminals, so the multicast PDU session update signaling is used to indicate that the second terminal is not included in the multicast PDU session. In specific implementation, the multicast PDU session update signaling may only carry the identifier of the second terminal, or it may carry the updated UE list.

[0150] Optionally, the first network-side device may also send a multicast PDU session update request to the core network node if the second terminal joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session. It should be noted that this update is for adding a terminal, and the multicast PDU session update signaling is used to indicate that the second terminal is included in the multicast PDU session. In specific implementation, the multicast PDU session update signaling may only carry the identifier of the second terminal, or it may carry the updated UE list.

[0151] Specific Usage Scenario 3: The core network node sends multicast PDU session update signaling to the first network-side device based on A17 or A18.

[0152] It should be noted that if the second terminal stops receiving multicast services transmitted by the multicast PDU session or is not interested in the multicast services transmitted by the multicast PDU session, it means that it is no longer suitable to use multicast for transmission for the second terminal. In this case, the second terminal needs to be removed from the multicast path.

[0153] In this case, the update is to reduce the number of terminals. The multicast PDU session update signaling is used to indicate that the second terminal is not included in the multicast PDU session. In specific implementation, the multicast PDU session update signaling may only carry the identifier of the second terminal, or it may carry the updated UE list.

[0154] It should be noted that, regarding the addition of terminals in Specific Use Cases 1 and 2, when a UE requests the same service through a NAS procedure, such as a service request, and the core network discovers that the service has established a multicast channel in the cell, the core network has two ways to handle the new UE's request:

[0155] The first method is to directly initiate a multicast PDU session modification process, add a new UE to the UE list involved in the multicast PDU session, and inform the gNB that the new UE also wants to receive the same services. Then the gNB can configure the new UE with the same MRB and layer configuration as other UEs in other multicast groups, so that the new UE can use the multicast channel to receive services.

[0156] In the second approach, in addition to the multicast PDU session modification process mentioned above, the core network also initiates the traditional unicast PDU session establishment process, triggering the gNB to establish MRB and DRB for the new UE. The establishment of unicast PDU session, unicast GTP-U tunnel and DRB is mainly for UE-specific DL data transmission other than public DL data, UE UL data transmission, and backup preparation for various possible path handovers.

[0157] It should be noted that when adding a new terminal, by establishing one or two sets of pipelines, the core network can use the configured pipelines to transmit data with the UE.

[0158] 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:

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

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

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

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

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

[0164] 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 can send the multicast PDU session release request according to the following conditions.

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

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

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

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

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

[0170] Generally, when a UE moves out of the coverage of the current cell, switches to another cell, can no longer receive multicast services from that cell, or is no longer interested in the service, the gNB performs a multicast PDU session modification procedure with the core network node, removing the UE from the UE list. On the Uu interface, the gNB also sends a reconfiguration signaling to the UE to remove all MRB-related configurations.

[0171] When a UE is removed from a multicast group, it no longer listens to G-RNTI but only to C-RNTI scheduling. The core network will switch the UE's service data back to the unicast GTP-U tunnel for transmission. On the Uu interface, this is done through DRB. The UE's data is switched from the multicast channel to the unicast channel.

[0172] When the number of UEs in a multicast group decreases below a certain threshold (e.g., only two or even one terminal in the group), the network may decide to release the multicast channel, transferring the remaining UEs entirely to the unicast channel for reception. The gNB can request, or the core network node can decide independently, to initiate a multicast PDUsession release process. The AMF sends signaling to the gNB to release the signal, and the gNB initiates the release process for the MRB and its configuration to all UEs in the group using dedicated signaling, then returns a completion message to the core network.

[0173] For each UE, there is no need to distinguish whether it is removed from the multicast group or the multicast is completely released, because the UE's behavior and experience are the same.

[0174] It should be noted that the embodiments of this application provide a dynamic multicast management method. The network side can flexibly perform multicast establishment and release management processes as needed, and transmit multiple UEs with the same services using multicast. This improves resource efficiency while taking into account UE reception performance, and greatly improves the overall system efficiency and resource utilization.

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

[0176] like Figure 3As shown, this application embodiment provides a multicast control device 300, applied to a core network node, including:

[0177] The first sending module 301 is used to send multicast protocol data unit (PDU) session signaling to the first network-side device based on the first information;

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

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

[0180] The business information processed by the terminal;

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

[0182] Multicast PDU session establishment request;

[0183] The first service is the same as the service transmitted in the multicast PDU session. The first service is the service requested by the first terminal through the cell or the first network-side device that establishes the multicast PDU session.

[0184] A multicast PDU session update request, wherein the multicast PDU session update request is used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session; the second terminal moves out of the first network-side device; and the second terminal joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session.

[0185] The second terminal stops receiving multicast services transmitted in the multicast PDU session;

[0186] The second terminal is not interested in the multicast services transmitted in the multicast PDU session.

[0187] Optionally, the multicast PDU session signaling includes at least one of the following:

[0188] Multicast PDU session establishment signaling;

[0189] Multicast PDU session update signaling.

[0190] Optionally, if the first information includes a multicast PDU session establishment request, the apparatus further includes:

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

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

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

[0194] The identification information includes at least one of the following: the NG interface application protocol identifier of the Access and Mobility Management Function (AMF) terminal, the NG interface application protocol identifier of the Radio Access Network (RAN) terminal, and the 5G Temporary Mobile Subscriber Identity (TMI).

[0195] Optionally, when the multicast PDU session signaling includes multicast PDU session update signaling, the apparatus further includes:

[0196] The fourth sending module is used to send unicast PDU session establishment signaling to the first network-side device.

[0197] Optionally, the multicast PDU session update message carries the identification information of the first terminal; and / or

[0198] The multicast PDU session update message is used to indicate that the second terminal is not included in the multicast PDU session.

[0199] Optionally, if the first information includes a multicast PDU session establishment request, the apparatus further includes:

[0200] The third receiving module is used to receive the response message sent by the first network-side device;

[0201] The response message carries acceptance information and / or rejection information;

[0202] The rejection information is used to indicate terminal information that cannot perform multicast reception in the cell under the first network side device;

[0203] The received information is used to indicate terminal information that can perform multicast reception in a cell under the first network-side device.

[0204] Optionally, the device further includes:

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

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

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

[0208] A multicast PDU session release request is sent by the first network-side device.

[0209] Optionally, if the first information includes a multicast PDU session update request, the apparatus further includes:

[0210] The fourth receiving module is used to receive multicast PDU session update requests sent by the first network-side device;

[0211] The multicast PDU session update request is sent by the first network-side device when the second terminal moves out of the cell corresponding to the multicast PDU session, moves out of the first network-side device, or joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session.

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

[0213] The multicast control 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.

[0214] This application embodiment also provides a core network node, including a processor and a communication interface, wherein the communication interface is used to send multicast protocol data unit (PDU) session signaling to the first network-side device based on first information;

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

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

[0217] The business information processed by the terminal;

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

[0219] Multicast PDU session establishment request;

[0220] The first service is the same as the service transmitted in the multicast PDU session. The first service is the service requested by the first terminal through the cell or the first network-side device that establishes the multicast PDU session.

[0221] A multicast PDU session update request, wherein the multicast PDU session update request is used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session; the second terminal moves out of the first network-side device; and the second terminal joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session.

[0222] The second terminal stops receiving multicast services transmitted in the multicast PDU session;

[0223] The second terminal is not interested in the multicast services transmitted in the multicast PDU session.

[0224] 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 4 A schematic diagram of the hardware structure of a core network node to implement an embodiment of this application.

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

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

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

[0228] The baseband device 403 may also include a network interface 406 for exchanging information with the radio frequency device 402, such as a common public radio interface (CPRI).

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

[0230] 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 multicast control 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.

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

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

[0233] Corresponding to the implementation of core network nodes, such as Figure 5 As shown in the embodiments of this application, a multicast control method is also provided, including:

[0234] Step 501: The first network-side device receives the multicast protocol data unit (PDU) session signaling sent by the core network node.

[0235] It should be noted that this multicast PDU session signaling is sent by the core network node based on the first information, which includes at least one of the following:

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

[0237] The business information processed by the terminal;

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

[0239] Multicast PDU session establishment request;

[0240] The first service is the same as the service transmitted in the multicast PDU session. The first service is the service requested by the first terminal through the cell or the first network-side device that establishes the multicast PDU session.

[0241] A multicast PDU session update request, wherein the multicast PDU session update request is used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session; the second terminal moves out of the first network-side device; and the second terminal joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session.

[0242] The second terminal stops receiving multicast services transmitted in the multicast PDU session;

[0243] The second terminal is not interested in the multicast services transmitted in the multicast PDU session.

[0244] Optionally, the multicast PDU session signaling includes at least one of the following:

[0245] Multicast PDU session establishment signaling;

[0246] Multicast PDU session update signaling.

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

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

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

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

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

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

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

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

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

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

[0257] The identification information includes at least one of the following: the NG interface application protocol identifier of the Access and Mobility Management Function (AMF) terminal, the NG interface application protocol identifier of the Radio Access Network (RAN) terminal, and the 5G Temporary Mobile Subscriber Identity (TMI).

[0258] Optionally, when the multicast PDU session signaling includes multicast PDU session update signaling, the method further includes:

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

[0260] Optionally, the multicast PDU session update signaling carries the identification information of the first terminal; and / or

[0261] The multicast PDU session update signaling is used to indicate that the second terminal is not included in the multicast PDU session.

[0262] Optionally, when the multicast PDU session signaling includes multicast PDU session update signaling, the method further includes:

[0263] If at least one of the following occurs: the second terminal moves out of the cell corresponding to the multicast PDU session, moves out of the second network-side device, or joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session, a multicast PDU session update request is sent to the core network node.

[0264] Optionally, when the multicast PDU session signaling includes multicast PDU session establishment signaling, the method further includes:

[0265] The first network-side device sends a response message to the core network node;

[0266] The response message carries acceptance information and / or rejection information;

[0267] The rejection information is used to indicate terminal information that cannot perform multicast reception in the cell under the first network side device;

[0268] The received information is used to indicate terminal information that can perform multicast reception in a cell under the first network-side device.

[0269] Optionally, the method further includes:

[0270] If a third terminal exists among the terminals corresponding to the multicast PDU session, a configuration message is sent to the third terminal, the configuration message indicating at least one of the following:

[0271] The third terminal switches to the cell corresponding to the multicast PDU session;

[0272] Add the cell corresponding to the multicast PDU session as the secondary cell of the third terminal;

[0273] Notify the third terminal of the cell and configuration corresponding to the multicast PDU session;

[0274] The serving cell of the third terminal is different from the cell corresponding to the multicast PDU session.

[0275] Optionally, the method further includes:

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

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

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

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

[0280] 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:

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

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

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

[0284] It is understood that, in the case of terminal handover, the first network-side device mentioned in this application embodiment 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 handover. The second network-side device can be considered as the source network-side device, such as the source base station, and the first network-side device can be considered as the target network-side device, such as the target base station.

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

[0286] Optionally, the first network-side device determines the second configuration information used by the fourth terminal based on the first configuration information, including at least one of the following:

[0287] C11. If the second network-side device uses multicast and / or unicast for transmission, and the first network-side device uses unicast for transmission, then the second configuration information is determined to be transmitted in unicast mode.

[0288] This implementation method includes the following situations:

[0289] The first scenario is: the source cell transmits via unicast (unicast path and DRB), and the target cell transmits via unicast. This is the traditional handover scenario, and the traditional handover process can be used directly, meaning the terminal can directly hand over from the source cell to the target cell.

[0290] The second scenario involves multicast transmission (multicast path and MRB) in the source cell and unicast transmission in the target cell. This method is common when multicast transmission is used on the source cell side, but the target cell side cannot use multicast transmission due to lack of support for this mechanism or insufficient number of UEs. Therefore, the target cell needs to use unicast transmission. In this scenario, since multicast cannot directly switch to unicast and involves cross-cell communication, a more reasonable approach is to first switch to unicast transmission on the source cell side and then perform the traditional handover procedure, or to switch to the third scenario below.

[0291] The third scenario: The source cell transmits data via multicast and is configured for unicast, while the target cell transmits data via unicast. Similar to the second scenario, this method is common when multicast is used on the source cell side, but the target cell cannot use multicast due to lack of support for this mechanism or insufficient number of UEs. Therefore, the target cell needs to use unicast for transmission. This method is more recommended than the second scenario because it is more handover-friendly. A typical approach is to convert the data from the multicast path to the unicast path on the source cell side before handover, effectively performing a traditional handover process during the handover.

[0292] C12. If the second network-side device uses unicast transmission, the first network-side device must at least use multicast transmission, and the second configuration information is determined to be transmitted in unicast mode.

[0293] This implementation method includes the following situations:

[0294] The first scenario: the source cell transmits via unicast, and the target cell transmits via multicast. To ensure continuity and compatibility during handover, it is not recommended to directly switch from unicast to multicast across cells. A more reasonable approach is to first switch from unicast in the source cell to unicast in the target cell, and then perform the unicast to multicast conversion in the target cell.

[0295] The second scenario is: the source cell transmits via unicast, and the target cell transmits via multicast with unicast configuration. In this scenario, the unicast-to-unicast handover is similar to the traditional process. After reaching the target cell, the path is changed from unicast to multicast.

[0296] C13. If the second network-side device uses multicast transmission and the first network-side device also uses multicast transmission, then the second configuration information is determined to be transmitted using multicast.

[0297] This implementation method includes the following situations:

[0298] The source cell transmits via multicast, and the target cell transmits via multicast. This method is also quite ideal. After the UE accesses the target cell, it can continue to receive data directly via multicast. However, since the multicast PDU session and MRB of the source cell and the target cell are not related, they can be considered as two independent channels without any state information transmission. Therefore, the service continuity of the UE cannot be guaranteed.

[0299] C14. If the second network-side device uses multicast and unicast transmission, and the first network-side device uses multicast and unicast transmission, then the second configuration information is determined to be multicast and unicast transmission.

[0300] This implementation method includes the following situations:

[0301] The first scenario is: the source cell transmits via multicast and the target cell transmits via multicast with unicast configuration. This scenario is not recommended. Before switching the source cell, it is usually necessary to establish a unicast connection before switching, which is equivalent to the third scenario below.

[0302] The second scenario is: the source cell transmits via multicast and is configured with unicast, while the target cell transmits via multicast. Although this method is feasible, the timing of releasing the unicast PDU session is debatable, and it is usually converted to the third scenario below.

[0303] The third scenario involves both the source and target cells using multicast and unicast configurations. In this scenario, both the source and target cells have multicast and unicast channel configurations, allowing for efficient service handover. Typically, unicast-to-unicast handover uses traditional handover methods. The key difference between multicast and traditional handover is that the source cell can include its multicast configuration in the handover preparation message sent to the target cell. Similarly, the target cell can configure both multicast and unicast when deciding to accept the UE's services, feeding back its configuration to the source cell, which then sends a handover command to the UE. Based on the target cell's unicast and multicast configurations, the UE receives the relevant multicast and unicast signals after accessing the target cell.

[0304] In other words, when a UE leaves the coverage area of ​​the current serving cell and needs to switch to the target cell, the above method can be used to achieve the handover, depending on the different transmission methods of the source cell and the target cell for the same service.

[0305] During the aforementioned handover process, the unicast-to-unicast path handover, being a dedicated transmission path and channel for the UE, ensures continuous data transmission before and after the handover for the core network. Furthermore, PDCP SN status transfer and data forwarding can occur between the source and target base station interfaces, supporting and configuring the UE to report PDCP status, thus ensuring lossless and continuous service. However, in any other form of path handover, regardless of changes in path attributes, even in a multicast-to-multicast path handover, the source and target multicast connections are established separately with the core network and can be considered independent. For two independent PDU sessions, the core network cannot guarantee continuous service transmission, and the base station interfaces cannot exchange status and data. The UE's PDCP layer must be reset before setting the initial PDCP SN value based on the first data packet received at the target side. Therefore, lossless and continuous service cannot be guaranteed. It can only be ensured to a certain extent, such as based on the time characteristics of live streaming. Therefore, for services that require lossless operation, at least unicast to unicast switching is usually included, while for other services that do not require lossless operation, unicast to unicast switching may not be included.

[0306] This application embodiment specifies the network behavior during terminal handover based on dynamic multicast control, thereby ensuring smooth terminal handover and reliable transmission of terminal services during the handover process.

[0307] like Figure 6 As shown in the illustration, this application also provides a multicast control device 600, applied to a first network-side device, comprising:

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

[0309] Optionally, the multicast PDU session signaling includes at least one of the following:

[0310] Multicast PDU session establishment signaling;

[0311] Multicast PDU session update signaling.

[0312] Optionally, before the first receiving module 601 receives the multicast protocol data unit (PDU) session signaling sent by the core network node, it further includes:

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

[0314] Optionally, the sixth sending module is configured to:

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

[0316] Optionally, before the first receiving module 601 receives the multicast protocol data unit (PDU) session signaling sent by the core network node, it further includes:

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

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

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

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

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

[0322] The identification information includes at least one of the following: the NG interface application protocol identifier of the Access and Mobility Management Function (AMF) terminal, the NG interface application protocol identifier of the Radio Access Network (RAN) terminal, and the 5G Temporary Mobile Subscriber Identity (TMI).

[0323] Optionally, when the multicast PDU session signaling includes multicast PDU session update signaling, the apparatus further includes:

[0324] The sixth receiving module is used to receive unicast PDU session establishment signaling sent by the core network node.

[0325] Optionally, the multicast PDU session update signaling carries the identification information of the first terminal; and / or

[0326] The multicast PDU session update signaling is used to indicate that the second terminal is not included in the multicast PDU session.

[0327] Optionally, when the multicast PDU session signaling includes multicast PDU session update signaling, the apparatus further includes:

[0328] The eighth sending module is used to send a multicast PDU session update request to the core network node when at least one of the following occurs: the second terminal moves out of the cell corresponding to the multicast PDU session, moves out of the second network-side device, or joins the cell corresponding to the multicast PDU session and the service it performs is the same as the service corresponding to the multicast PDU session.

[0329] Optionally, when the multicast PDU session signaling includes multicast PDU session establishment signaling, the apparatus further includes:

[0330] The ninth sending module is used to send response messages to the core network nodes;

[0331] The response message carries acceptance information and / or rejection information;

[0332] The rejection information is used to indicate terminal information that cannot perform multicast reception in the cell under the first network side device;

[0333] The received information is used to indicate terminal information that can perform multicast reception in a cell under the first network-side device.

[0334] Optionally, the device further includes:

[0335] The tenth sending module is configured to send a configuration message to the third terminal if a third terminal exists among the terminals corresponding to the multicast PDU session. The configuration message is used to indicate at least one of the following:

[0336] The third terminal switches to the cell corresponding to the multicast PDU session;

[0337] Add the cell corresponding to the multicast PDU session as the secondary cell of the third terminal;

[0338] Notify the third terminal of the cell and configuration corresponding to the multicast PDU session;

[0339] The serving cell of the third terminal is different from the cell corresponding to the multicast PDU session.

[0340] Optionally, the device further includes:

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

[0342] Optionally, the twelfth transmitting module is used for:

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

[0344] Optionally, the device further includes:

[0345] The seventh receiving module is used to receive the first configuration information of the fourth terminal sent by the second network side device. The first configuration information includes the correspondence between the service flow of the fourth terminal and the unicast radio bearer and / or multicast radio bearer.

[0346] The determination module is used by the first network-side device to determine the second configuration information used by the fourth terminal based on the first configuration information. The second configuration information is the transmission configuration used by the fourth terminal after switching to the first network-side device.

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

[0348] Optionally, the determining module is configured to implement at least one of the following:

[0349] If the second network-side device uses multicast and / or unicast for transmission, and the first network-side device uses unicast for transmission, then the second configuration information is determined to be transmitted in unicast mode.

[0350] If the second network-side device uses unicast transmission, the first network-side device must at least use multicast transmission, thus determining that the second configuration information is transmitted in unicast mode.

[0351] If the second network-side device uses multicast transmission and the first network-side device also uses multicast transmission, then the second configuration information is determined to be transmitted using multicast.

[0352] If the second network-side device uses multicast and unicast transmission, and the first network-side device uses multicast and unicast transmission, then the second configuration information is determined to be multicast and unicast transmission.

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

[0354] 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 multicast control 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.

[0355] 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 multicast control method embodiment applied to the first network-side device side and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0357] 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 signaling sent by core network nodes.

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

[0359] 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 4 The structure will not be elaborated here.

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

[0361] like Figure 7 As shown in the embodiments of this application, a method for switching configurations is also provided, including:

[0362] Step 701: The second network-side device sends the first configuration information of the fourth terminal to the first network-side device;

[0363] Step 702: The second network-side device receives the second configuration information fed back by the first network-side device;

[0364] The first configuration information is the transmission configuration of the fourth terminal under the second network-side device. The first configuration information includes the correspondence between service flows and unicast radio bearers and / or multicast radio bearers. The second configuration information is the transmission configuration used by the fourth terminal after switching to the first network-side device.

[0365] Optionally, after the second network-side device receives the second configuration information fed back by the first network-side device, it further includes at least one of the following:

[0366] If the second network-side device uses multicast transmission, and the second configuration information is transmitted in unicast mode, then the terminal is switched to unicast transmission and the device is switched to the first network-side device.

[0367] The second network-side device shall at least use unicast transmission. If the second configuration information is transmitted in unicast mode, switch to the first network-side device.

[0368] If the second configuration information is transmitted via multicast, the system switches to the first network-side device.

[0369] If the second network-side device uses multicast transmission, and if the second configuration information is both multicast and unicast transmission, then unicast transmission is established for the terminal, and the device is switched to the first network-side device.

[0370] If the second network-side device uses multicast and unicast transmission, and the second configuration information is multicast and unicast transmission, then switch to the first network-side device.

[0371] It should be noted that all descriptions of the second network-side device in the above embodiments are applicable to the embodiments of this switching configuration method and can achieve the same technical effect, so they will not be repeated here.

[0372] like Figure 8 As shown, this application embodiment also provides a switching configuration device 800, applied to a second network-side device, including:

[0373] The second sending module 801 is used to send the first configuration information of the fourth terminal to the first network-side device;

[0374] The second receiving module 802 is used to receive the second configuration information fed back by the first network-side device;

[0375] The first configuration information is the transmission configuration of the fourth terminal under the second network-side device. The first configuration information includes the correspondence between service flows and unicast radio bearers and / or multicast radio bearers. The second configuration information is the transmission configuration used by the fourth terminal after switching to the first network-side device.

[0376] Optionally, after the second receiving module 802 receives the second configuration information fed back by the first network-side device, it further includes at least one of the following:

[0377] The first switching module is used to transmit in multicast mode on the second network-side device. If the second configuration information is transmitted in unicast mode, the terminal is switched to unicast mode and switched to the first network-side device.

[0378] The second switching module is used to switch to the first network side device if the second configuration information is transmitted in unicast mode at least in the second network side device.

[0379] The third switching module is used to switch to the first network side device if the second configuration information is transmitted in a multicast mode on the second network side device.

[0380] The fourth switching module is used to establish unicast transmission for the terminal if the second network-side device uses multicast transmission and the second configuration information is multicast transmission and unicast transmission, and then switch to the first network-side device.

[0381] The fifth switching module is used to switch to the first network-side device if the second network-side device uses multicast and unicast transmission.

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

[0383] Preferably, this application embodiment also provides a network-side device, which is a second 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 switching configuration method embodiment applied to the second network-side device and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0384] 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 handover configuration method embodiment applied to the second network-side device side and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0386] It should be noted that the readable storage medium in the embodiments of this application can be volatile or non-volatile. In addition, the readable storage medium can be a non-transient readable storage medium.

[0387] This application embodiment also provides a network-side device, which is a second network-side device, including a processor and a communication interface. The communication interface is used to send first configuration information of a fourth terminal to a first network-side device and receive second configuration information fed back by the first network-side device.

[0388] The first configuration information is the transmission configuration of the fourth terminal under the second network-side device. The first configuration information includes the correspondence between service flows and unicast radio bearers and / or multicast radio bearers. The second configuration information is the transmission configuration used by the fourth terminal after switching to the first network-side device.

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

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

[0391] Optional, such as Figure 9As shown, this application embodiment also provides a communication device 900, including a processor 901, a memory 902, and a program or instructions stored in the memory 902 and executable on the processor 901. For example, when the communication device 900 is a second network-side device, the program or instructions executed by the processor 901 implement the various processes of the above-described switching configuration method embodiment and achieve the same technical effect. When the communication device 900 is a first network-side device, the program or instructions executed by the processor 901 implement the various processes of the above-described multicast control method embodiment and achieve the same technical effect. When the communication device 900 is a core network node, the program or instructions executed by the processor 901 implement the various processes of the above-described multicast control method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

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

[0393] The first network-side device and the second 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 are not limited here.

[0394] Network-side devices and terminals can each use one or more antennas for 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, pre-coding transmission, or beamforming transmission, etc.

[0395] 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-described multicast control method or switching configuration method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0397] 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 multicast control method or switching configuration method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

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

[0400] 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 multicast control method characterized by comprising: include: In the case where a unicast path exists between the core network node and the terminal, the core network node sends a multicast protocol data unit (PDU) session signaling to the first network-side device based on the first information; wherein, the terminal is a terminal accessing the first network-side device or the same cell of the first network-side device performing the same service, the service satisfies a preset QoS quality attribute, and the terminal includes a second terminal; wherein, the unicast path is a unicast path used for transmitting public data; The core network node sends a multicast PDU session release signaling to the first network-side device based on the second information; wherein, the second information includes terminal information for receiving multicast services accessing the first network-side device; The first information includes at least one of the following: Terminal information accessing the first network-side device; wherein, the terminal information is the number of terminals; The cell to which the terminal accessing the first network-side device belongs; Wherein, if the first information includes: terminal information accessing the first network-side device, or the home cell of the terminal accessing the first network-side device, the multicast PDU session signaling is multicast PDU session establishment signaling, and the multicast establishment process is triggered by the core network node.

2. The method according to claim 1, characterized in that, The first information also includes at least one of the following: The business information processed by the terminal; Multicast PDU session establishment request; A multicast PDU session update request sent by a first network-side device, the multicast PDU session update request being used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session; the second terminal moves out of the first network-side device and the second terminal joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session; The second terminal stops receiving multicast services transmitted in the multicast PDU session; The second terminal is not interested in the multicast services transmitted in the multicast PDU session; When the first information includes the multicast PDU session update request, or the second terminal stops receiving the multicast services transmitted by the multicast PDU session, or the second terminal is not interested in the multicast services transmitted by the multicast PDU session, the multicast PDU session signaling is multicast PDU session update signaling.

3. The method according to claim 2, characterized in that, If the first information includes a multicast PDU session establishment request, the method further includes: The core network node sends 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.

4. The method according to claim 1, characterized in that, The multicast PDU session establishment signaling includes identification information of at least one terminal; The identification information includes at least one of the following: the NG interface application protocol identifier of the Access and Mobility Management Function (AMF) terminal, the NG interface application protocol identifier of the Radio Access Network (RAN) terminal, and the 5G Temporary Mobile Subscriber Identity (TMI).

5. The method according to claim 2, characterized in that, When the multicast PDU session signaling is multicast PDU session update signaling, the method further includes: The core network node sends a unicast PDU session establishment signaling to the first network-side device.

6. The method according to claim 2, characterized in that, The multicast PDU session update signaling carries the identification information of the first terminal, which is a terminal that has newly joined the multicast PDU session; and / or The multicast PDU session update signaling is used to indicate that the second terminal is not included in the multicast PDU session.

7. The method according to claim 1 or 2, characterized in that, The method further includes: The core network node receives the response message sent by the first network-side device; The response message carries acceptance information and / or rejection information; The rejection information is used to indicate terminal information that cannot perform multicast reception in the cell under the first network side device; The received information is used to indicate terminal information that can perform multicast reception in a cell under the first network-side device.

8. The method according to claim 1, characterized in that, The second information also includes: A multicast PDU session release request is sent by the first network-side device.

9. The method according to claim 2, characterized in that, If the first information includes a multicast PDU session update request, the method further includes: The core network node receives a multicast PDU session update request sent by the first network-side device; The multicast PDU session update request is sent by the first network-side device when the second terminal moves out of the cell corresponding to the multicast PDU session, moves out of the first network-side device, or joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session.

10. A multicast control method, characterized in that, include: The first network-side device receives multicast protocol data unit (PDU) session signaling sent by the core network node; The first network-side device sends a multicast PDU session release request to the core network node; the multicast PDU session release request is a request sent by the first network-side device according to second information, the second information including terminal information of the terminal receiving multicast services accessing the first network-side device; Wherein, the multicast PDU session signaling is sent by the core network node based on first information when there is a unicast path between the core network node and the terminal, wherein the terminal is a terminal that accesses the first network-side device or the same cell of the first network-side device and performs the same service, the service satisfies a preset QoS quality attribute, and the terminal includes a second terminal; wherein, the unicast path is a unicast path used for transmitting public data; The first information includes at least one of the following: Terminal information accessing the first network-side device; wherein, the terminal information is the number of terminals; The cell to which the terminal accessing the first network-side device belongs; Wherein, if the first information includes: terminal information accessing the first network-side device, or the home cell of the terminal accessing the first network-side device, the multicast PDU session signaling is multicast PDU session establishment signaling, and the multicast establishment process is triggered by the core network node.

11. The method according to claim 10, characterized in that, The first information also includes at least one of the following: The business information processed by the terminal; Multicast PDU session establishment request; A multicast PDU session update request sent by a first network-side device, the multicast PDU session update request being used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session; the second terminal moves out of the first network-side device and the second terminal joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session; The second terminal stops receiving multicast services transmitted in the multicast PDU session; The second terminal is not interested in the multicast services transmitted in the multicast PDU session; When the first information includes the multicast PDU session update request, or the second terminal stops receiving the multicast services transmitted by the multicast PDU session, or the second terminal is not interested in the multicast services transmitted by the multicast PDU session, the multicast PDU session signaling is multicast PDU session update signaling.

12. The method according to claim 10, characterized in that, Before the first network-side device receives the multicast protocol data unit (PDU) session signaling sent by the core network node, the following is also included: The first network-side device sends the terminal's home cell to the core network node.

13. The method according to claim 12, characterized in that, The first network-side device sends the terminal's home cell to the core network node, including: 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.

14. The method according to claim 10, characterized in that, The method further includes: before the first network-side device receives the multicast protocol data unit (PDU) session signaling sent by the core network node. The first network-side device sends a multicast PDU session establishment request to the core network node.

15. The method according to claim 14, characterized in that, Before the first network-side device sends a multicast PDU session establishment request to the core network node, the process also includes: The first network-side device receives service attribute information sent by the core network node; The service attribute information is used to determine whether different terminals are performing the same service.

16. The method according to claim 10, characterized in that, The multicast PDU session establishment signaling includes identification information of at least one terminal; The identification information includes at least one of the following: the NG interface application protocol identifier of the Access and Mobility Management Function (AMF) terminal, the NG interface application protocol identifier of the Radio Access Network (RAN) terminal, and the 5G Temporary Mobile Subscriber Identity (TMI).

17. The method according to claim 11, characterized in that, When the multicast PDU session signaling is multicast PDU session update signaling, the method further includes: The first network-side device receives the unicast PDU session establishment signaling sent by the core network node.

18. The method according to claim 11, characterized in that, The multicast PDU session update signaling carries the identification information of the first terminal, which is a terminal that has newly joined the multicast PDU session; and / or The multicast PDU session update signaling is used to indicate that the second terminal is not included in the multicast PDU session.

19. The method according to claim 11, characterized in that, When the multicast PDU session signaling is multicast PDU session update signaling, the method further includes: If at least one of the following occurs: the second terminal moves out of the cell corresponding to the multicast PDU session, moves out of the second network-side device, or joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session, a multicast PDU session update request is sent to the core network node.

20. The method according to claim 10, characterized in that, When the multicast PDU session signaling is used to establish a multicast PDU session, the method further includes: The first network-side device sends a response message to the core network node; The response message carries acceptance information and / or rejection information; The rejection information is used to indicate terminal information that cannot perform multicast reception in the cell under the first network side device; The received information is used to indicate terminal information that can perform multicast reception in a cell under the first network-side device.

21. The method according to claim 10, characterized in that, Also includes: If a third terminal exists among the terminals corresponding to the multicast PDU session, a configuration message is sent to the third terminal, the configuration message indicating at least one of the following: The third terminal switches to the cell corresponding to the multicast PDU session; Add the cell corresponding to the multicast PDU session as the secondary cell of the third terminal; Notify the third terminal of the cell and configuration corresponding to the multicast PDU session; The serving cell of the third terminal is different from the cell corresponding to the multicast PDU session.

22. The method according to claim 10, characterized in that, The first network-side device sends a multicast PDU session release request to the core network node, including: 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.

23. The method according to claim 10, characterized in that, Also includes: The first network-side device receives the first configuration information of the fourth terminal sent by the second network-side device. The first configuration information includes the correspondence between the service flow of the fourth terminal and the unicast radio bearer and / or multicast radio bearer. The first network-side device determines the second configuration information used by the fourth terminal based on the first configuration information. The second configuration information is the transmission configuration used by the fourth terminal after switching to the first network-side device. The first network-side device sends the second configuration information to the second network-side device.

24. The method according to claim 23, characterized in that, The first network-side device determines the second configuration information used by the fourth terminal based on the first configuration information, including at least one of the following: If the second network-side device uses multicast and / or unicast for transmission, and the first network-side device uses unicast for transmission, then the second configuration information is determined to be transmitted in unicast mode. If the second network-side device uses unicast transmission, the first network-side device must at least use multicast transmission, thus determining that the second configuration information is transmitted in unicast mode. If the second network-side device uses multicast transmission and the first network-side device also uses multicast transmission, then the second configuration information is determined to be transmitted using multicast. If the second network-side device uses multicast and unicast transmission, and the first network-side device uses multicast and unicast transmission, then the second configuration information is determined to be multicast and unicast transmission.

25. A multicast control device, applied to a core network node, characterized in that, include: The first sending module is configured to send multicast protocol data unit (PDU) session signaling to a first network-side device based on first information, when a unicast path exists between the core network node and the terminal; wherein the terminal is a terminal accessing the first network-side device or the same cell of the first network-side device performing the same service, the service satisfying a preset QoS quality attribute, and the terminal includes a second terminal; wherein the unicast path is a unicast path used for transmitting public data. The fifth sending module is used to send a multicast PDU session release signaling to the first network-side device according to the second information; wherein, the second information includes terminal information for receiving multicast services accessing the first network-side device; The first information includes at least one of the following: Terminal information accessing the first network-side device; wherein, the terminal information is the number of terminals; The cell to which the terminal accessing the first network-side device belongs; Wherein, if the first information includes: terminal information accessing the first network-side device, or the home cell of the terminal accessing the first network-side device, the multicast PDU session signaling is multicast PDU session establishment signaling, and the multicast establishment process is triggered by the core network node.

26. The apparatus according to claim 25, characterized in that, The first information also includes at least one of the following: The business information processed by the terminal; Multicast PDU session establishment request; A multicast PDU session update request sent by a first network-side device, the multicast PDU session update request being used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session; the second terminal moves out of the first network-side device and the second terminal joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session; The second terminal stops receiving multicast services transmitted in the multicast PDU session; The second terminal is not interested in the multicast services transmitted in the multicast PDU session; When the first information includes the multicast PDU session update request, or the second terminal stops receiving the multicast services transmitted by the multicast PDU session, or the second terminal is not interested in the multicast services transmitted by the multicast PDU session, the multicast PDU session signaling is multicast PDU session update signaling.

27. A core network node, characterized in that, It includes 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 multicast control method as described in any one of claims 1 to 9.

28. A multicast control device, applied to a first network-side device, characterized in that, include: The first receiving module is used to receive multicast protocol data unit (PDU) session signaling sent by the core network node; The eleventh sending module is used to send a multicast PDU session release request to the core network node; the multicast PDU session release request is a request sent by the first network-side device according to the second information, the second information including terminal information of the terminal receiving multicast services accessing the first network-side device; Wherein, the multicast PDU session signaling is sent by the core network node based on first information when a unicast path exists between the core network node and the terminal, wherein the terminal is a terminal accessing the first network-side device or the same cell of the first network-side device performing the same service, the service satisfying a preset QoS quality attribute, and the terminal includes a second terminal; wherein the unicast path is a unicast path used for transmitting public data; the first information includes at least one of the following: Terminal information accessing the first network-side device; wherein, the terminal information is the number of terminals; The cell to which the terminal accessing the first network-side device belongs; Wherein, if the first information includes: terminal information accessing the first network-side device, or the home cell of the terminal accessing the first network-side device, the multicast PDU session signaling is multicast PDU session establishment signaling, and the multicast establishment process is triggered by the core network node.

29. The apparatus according to claim 28, characterized in that, The first information also includes at least one of the following: The business information processed by the terminal; Multicast PDU session establishment request; A multicast PDU session update request sent by a first network-side device, the multicast PDU session update request being used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session; the second terminal moves out of the first network-side device and the second terminal joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session; The second terminal stops receiving multicast services transmitted in the multicast PDU session; The second terminal is not interested in the multicast services transmitted in the multicast PDU session; When the first information includes the multicast PDU session update request, or the second terminal stops receiving the multicast services transmitted by the multicast PDU session, or the second terminal is not interested in the multicast services transmitted by the multicast PDU session, the multicast PDU session signaling is multicast PDU session update signaling.

30. A network-side device, wherein the network-side device is a first network-side device, characterized in that, It includes 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 multicast control method as described in any one of claims 10 to 24.

31. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the multicast control method as described in any one of claims 1 to 24.

Images