Broadcast / multicast service management method and apparatus, and electronic device and storage medium
Patent Information
- Application Number
- IN202227067437
- Authority / Receiving Office
- IN · IN
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-04-24
- Filing Date
- 2022-11-23
- Publication Date
- 2026-10-27
- Estimated Expiration
- 2041-04-23
AI Technical Summary
Current multimedia broadcast multicast services in cellular networks face inefficiencies due to a lack of dynamic scheduling and resource management in 5G radio access networks, leading to resource waste and limited flexibility in supporting diverse application scenarios like public safety and IoT.
A broadcast/multicast service management method and apparatus that enables effective management of broadcast/multicast services by communicating between centralized and distributed units in a 5G network, allowing for dynamic establishment, modification, and release of broadcast/multicast services, incorporating features like flexible scheduling and user equipment mobility support.
This solution enhances resource utilization and reliability, ensuring continuous service delivery across various scenarios by enabling flexible and efficient management of broadcast/multicast services in 5G networks, supporting diverse applications and improving user equipment reception reliability.
Smart Images

Figure 00000053_0000 
Figure 00000053_0001 
Figure 00000054_0000
Abstract
Description
TECHNICAL FIELDThe present application relates to wireless communication networks and, in particular, to abroadcast / multicast service management method and apparatus, an electronic device, and astorage medium.BACKGROUNDThere has always been a need for multimedia broadcast multicast services in cellular networks.The application scenarios of multimedia broadcast multicast services are gradually expandedfrom initial video broadcasting services of terrestrial broadcast television to vertical servicessuch as public safety, vehicle-to-everything, and Internet of Things (IoT).Multimedia broadcast multicast services (MBMS) is a point-to-multipoint service that sendsdata from one data source to multiple users. The technologies related to the 5th generationmobile communication technology (5G), which have been discussed and standardized in theindustry, are mainly related to a unicast service scenario, that is, a point-to-point service mode,while the standardized discussion of a point-to-multipoint service mode has not been carriedout. With the rapid increase of users and the multi-dimensioning of application scenarios, thepoint-to-multipoint service mode inevitably becomes one of the indispensable service modes.To meet the increasing requirements of the point-to-multipoint service, how to effectivelyimplement the MBMS on the radio access network (RAN) air interface under the 5Gframework becomes an urgent problem to be solved.SUMMARYThe present application provides a broadcast / multicast service management method andapparatus, an electronic device, and a storage medium.An embodiment of the present application provides a broadcast / multicast service managementmethod. The method includes sending first information to a second communication unit,where the first information is used to instruct the second communication unit to execute anoperation related to broadcast / multicast service management, and receiving secondinformation sent by the second communication unit, where the second information is used toindicate an execution result of the operation to a first communication unit.An embodiment of the present application provides another broadcast / multicast servicemanagement method. The method includes receiving first information sent by a firstcommunication unit, where the first information is used to instruct a second communicationunit to execute an operation related to broadcast / multicast service management, and sendingsecond information to the first communication unit, where the second information is used toindicate an execution result of the operation to the first communication unit.An embodiment of the present application provides another broadcast / multicast servicemanagement method. The method includes sending third information to a first communicationunit, where the third information is used to instruct the first communication unit to execute anoperation related to broadcast / multicast service management, and receiving fourth informationsent by the first communication unit, where the fourth information is used to indicate anexecution result of the operation to a second communication unit.An embodiment of the present application provides another broadcast / multicast servicemanagement method. The method includes receiving third information sent by a secondcommunication unit, where the third information is used to instruct a first communication unitto execute an operation related to broadcast / multicast service management, and sending fourthinformation to the second communication unit, where the fourth information is used to indicatean execution result of the operation to the second communication unit.An embodiment of the present application provides a broadcast / multicast service managementapparatus. The apparatus includes a first sending module and a first reception module.The first sending module is configured to send first information to a second communicationunit. The first information is used to instruct the second communication unit to execute anoperation related to broadcast / multicast service management.The first reception module is configured to receive second information sent by the secondcommunication unit. The second information is used to indicate an execution result of theoperation to a first communication unit.An embodiment of the present application provides another broadcast / multicast servicemanagement apparatus. The apparatus includes a second reception module and a secondsending module.The second reception module is configured to receive first information sent by a firstcommunication unit. The first information is used to instruct a second communication unit toexecute an operation related to broadcast / multicast service management.The second sending module is configured to send second information to the firstcommunication unit. The second information is used to indicate an execution result of theoperation to the first communication unit.An embodiment of the present application provides another broadcast / multicast servicemanagement apparatus. The apparatus includes a third sending module and a third receptionmodule.The third sending module is configured to send third information to a first communicationunit. The third information is used to instruct the first communication unit to execute anoperation related to broadcast / multicast service management.The third reception module is configured to receive fourth information sent by the firstcommunication unit. The fourth information is used to indicate an execution result of theoperation to a second communication unit.An embodiment of the present application provides another broadcast / multicast servicemanagement apparatus. The apparatus includes a fourth reception module and a fourth sendingmodule.The fourth reception module is configured to receive third information sent by a secondcommunication unit. The third information is used to instruct a first communication unit toexecute an operation related to broadcast / multicast service management.The fourth sending module is configured to send fourth information to the secondcommunication unit. The fourth information is used to indicate an execution result of theoperation to the second communication unit.An embodiment of the present application provides an electronic device. The device includesone or more processors and a memory.The memory is configured to store one or more programs.When executed by the one or more processors, the one or more programs cause the one ormore processors to implement the method in any embodiment of the present application.An embodiment of the present application provides a storage medium storing a computerprogram which, when executed by a processor, implements the method in any embodiment ofthe present application.BRIEF DESCRIPTION OF DRAWINGSFIG. 1 is a flowchart of a broadcast / multicast service management method according to anembodiment of the present application.FIG. 2 is a flowchart of another broadcast / multicast service management method according toan embodiment of the present application.FIG. 3 is a flowchart of another broadcast / multicast service management method according toan embodiment of the present application.FIG. 4 is a flowchart of another broadcast / multicast service management method according toan embodiment of the present application.FIG. 5 is a flowchart illustrating the establishment of a broadcast / multicast service between agNB-CU and a gNB-DU according to an embodiment of the present application.FIG. 6 is a flowchart illustrating the modification of a broadcast / multicast service between agNB-CU and a gNB-DU initiated by the gNB-CU according to an embodiment of the presentapplication.FIG. 7 is a flowchart illustrating the modification of a broadcast / multicast service between agNB-CU and a gNB-DU initiated by the gNB-DU according to an embodiment of the presentapplication.FIG. 8 is a flowchart illustrating the release of a broadcast / multicast service between a gNBCU and a gNB-DU initiated by the gNB-CU according to an embodiment of the presentapplication.FIG. 9 is a flowchart illustrating the release of a broadcast / multicast service between a gNBCU and a gNB-DU initiated by the gNB-DU according to an embodiment of the presentapplication.FIG. 10 is a block diagram illustrating the structure of a broadcast / multicast servicemanagement apparatus according to an embodiment of the present application.FIG. 11 is a block diagram illustrating the structure of another broadcast / multicast servicemanagement apparatus according to an embodiment of the present application.FIG. 12 is a block diagram illustrating the structure of another broadcast / multicast servicemanagement apparatus according to an embodiment of the present application.FIG. 13 is a block diagram illustrating the structure of another broadcast / multicast servicemanagement apparatus according to an embodiment of the present application.DETAILED DESCRIPTIONEmbodiments of the present application are described hereinafter in detail in conjunction withdrawings.Multimedia broadcast multicast services is a point-to-multipoint service that sends data fromone data source to multiple users. The broadcast network architecture of a conventional longterm evolution evolved MBMS (LTE eMBMS) is essentially designed for semi-static videoservice distribution. For example, the distribution of LTE eMBMS at the air interface does notrely on user feedback. Alternatively, there is only optional and limited feedback. Thus, thenetwork can understand the reception interest and reception quality of users to a limited extent.The network cannot flexibly schedule services. For example, the network cannot dynamicallyadjust a broadcast area and resource occupation of broadcast. The preceding factors cause thewaste of air interface resources to a certain extent, thereby hindering the use andpopularization of the technology.The single-cell point-to-multipoint (SC-PTM) technology introduced in the 3rd GenerationPartnership Project Release 13 (3GPP Rel-13) is introduced to solve the flexibility of airinterface scheduling to a certain extent. However, the SC-PTM technology essentially relieson the network architecture basis set in Release 9 (Rel-9). That is, a new bearing mode of airinterface data is added based on an original architecture. This bearing mode is based onindependent scheduling of a single cell and flexible use of air interface resources. For example,instead of using the physical multicast channel (PMCH) used in the multicast-broadcastsingle-frequency network (MBSFN) in the conventional eMBMS, a physical downlink sharedchannel (PDSCH) consistent with unicast data is used to implement dynamic and flexiblescheduling. Although SC-PTM introduces some flexibility in air interface, the SC-PTM failsto solve the architecture problem: the semi-static configuration characteristic of the broadcastarea. The dynamic adjustment of the broadcast area relying on the driving of a service levelcannot be linked with the flexible and powerful UE air interface connection management inthe 3GPP in the related art to implement efficient utilization of resources and assurance of thereliability and continuity of services to a certain extent.The preceding problem is expected to be solved in a new radio (NR) system. A new broadcastarchitecture of 5G is defined. Multicast is supported. New service types such as public safety,consumer Internet of Things, and vehicle-to-everything are taken as scenario targets. With thepreceding diverse scenarios as targets needing to be supported by a NR broadcast servicebearing service, a flexible multicast broadcast architecture is provided and can accommodaterequirements of various scenarios, such as point-to-point multicast / broadcast streams, deliveryof IPv4 / IPv6 multicast, IPTV, software delivery over wireless, group communication andbroadcast / multicast IoT applications, vehicle-to-everything applications (V2X applications),or public safety. In the preceding scenarios, the newly provided framework can provide acertain degree of reliability, and can also support an energy-saving and resource-constrainedreceiving device. A receiving user equipment (UE) can switch between a receiving mode ofpoint-to-point sending and a receiving mode of point-to-multipoint sending, therebyimplementing a balance between reliability and receiving efficiency. In addition, basic UEmobility is supported in NR, thereby ensuring continuity of service reception by the UE in aswitch / reselection scenario. In addition, uplink feedback of the UE is also supported in NR,thereby improving reception reliability of the UE. Based on the preceding analysis,introducing a support scheme of the broadcast / multicast service in NR needs to be considered,and an establishment flow of a broadcast / multicast service radio bearer also needs to beconsidered emphatically.FIG. 1 is a flowchart of a broadcast / multicast service management method according to anembodiment of the present application. The method may be executed by a broadcast / multicastservice management apparatus. The apparatus may be implemented by software and / orhardware, typically configured in an electronic device such as a base station. As shown in FIG.1, the method includes operations below.In operation 110, first information is sent to a second communication unit.In this embodiment of the present application, the base station may be a split 5G base station.Split here means that the base station logically or physically includes a first communicationunit and a second communication unit. For example, the first communication unit may be acentralized unit (CU), or a logical unit or a physical unit that implements the same or similarfunctions as the centralized unit. The second communication unit may be a distributed unit(DU), or a logical unit or a physical unit that implements the same or similar functions as thedistributed unit. The centralized unit of the base station and the distributed unit of the basestation may be denoted by gNB-CU and gNB-DU, respectively.It is to be noted that the second communication unit is the gNB-DU to which a cell related tobroadcast / multicast service management belongs. The cell related to broadcast / multicastservice management is a cell in which a broadcast / multicast service needs to be established,modified, or released.For example, the gNB-CU receives a broadcast / multicast service establishment requestmessage sent by a core network, performs admission control on the broadcast / multicastservice establishment request message, and determines in which cells the broadcast / multicastservice can be established. Alternatively, due to some scenario requirements, the gNB-CUneeds to modify parameter information of an established MBMS session to determine whichcells need to be updated, modified, or released.In this embodiment of the present application, a cell belongs to a service area. One servicearea includes multiple cells.The first information is used for indicating the second communication unit to execute anoperation related to broadcast / multicast service management. For example, the gNB-CU sendsthe first information to the gNB-DU to which a cell related to broadcast / multicast servicemanagement belongs to indicate the gNB-DU to execute the operation related tobroadcast / multicast service management.The first information includes a broadcast / multicast service establishment request message, abroadcast / multicast service modification request message, or a broadcast / multicast servicerelease request message.If the first information includes the broadcast / multicast service establishment request messageor the broadcast / multicast service modification request message, the first information includesany combination or at least one of the following: a broadcast / multicast service identifier usedto identify a broadcast / multicast service; a first interface identifier assigned by the firstcommunication unit on the communication interface between the first communication unit andthe second communication unit for a broadcast / multicast service; a second interface identifierassigned by the second communication unit on the communication interface between the firstcommunication unit and the second communication unit for a broadcast / multicast service; oneor more service area identifiers supporting a broadcast / multicast service; one or more cellidentifiers of one or more cells which needs to establish, modify, or release abroadcast / multicast service, where the one or more cell identifiers include NR cell globalidentifier (NCGI) information or physical cell identifier (PCI) information; a cell list identifierof a service area; information of a broadcast / multicast service radio bearer needing to beestablished or modified; configuration information of a broadcast / multicast service;information of a radio link control (RLC) mode of a broadcast / multicast service radio bearer;information of a broadcast / multicast service radio bearer needing to be released, includingidentifier information of a broadcast / multicast service radio bearer; or change notificationindication information, where the change notification indication information is used for thefirst communication unit to notify the second communication unit that configurationinformation of a broadcast / multicast service is changed.Information of the established or modified broadcast / multicast service radio bearer includesidentifier information of a broadcast / multicast service radio bearer and / or attributeinformation of a broadcast / multicast service radio bearer.Specifically, the attribute information of a broadcast / multicast service radio bearer includesquality of service information of the broadcast / multicast service radio bearer, dataflowinformation mapped to the broadcast / multicast service radio bearer, and notification control.The dataflow information mapped to the broadcast / multicast service radio bearer includesdataflow identifier information and / or quality of service information of the dataflow mappedto the broadcast / multicast service radio bearer.In this embodiment of the present application, the quality of service information of thebroadcast / multicast service radio bearer and the quality of service information of the dataflowmay include any combination or at least one of the following: nondynamic 5G quality ofservice identifier (5QI) information, dynamic 5QI information, allocation and retentionpriority, or data guaranteed flow bit rate quality of service (GFBR QoS) information.The nondynamic 5QI information further includes any combination or at least one of thefollowing: 5QI, priority level, averaging window, or maximum data burst volume.The dynamic 5QI information further includes any combination or at least one of the following:priority level, packet delay budget, packet error rate, 5QI, critical delay, averaging window, ormaximum data burst volume.The allocation and retention priority further includes any combination or at least one of thefollowing: priority level, pre-emption capability, or pre-emption vulnerability.The data guaranteed flow bit rate quality of service information further includes anycombination or at least one of the following: maximum downlink flow bit rate, downlinkguaranteed flow bit rate, notification control, or maximum downlink packet loss rate.In this embodiment of the present application, the configuration information of abroadcast / multicast service includes any combination or at least one of the following: systeminformation of broadcast / multicast service information, control channel / informationconfiguration parameters of the broadcast / multicast service, transport channel / informationconfiguration parameters of the broadcast / multicast service, or radio bearer configurationparameters of the broadcast / multicast service.Optionally, if the transport mode between the first communication unit and the secondcommunication unit is Internet protocol (IP) multicasting, the first information also includesIP multicasting downlink user plane transport network layer (DL UP TNL) informationassigned to the second communication unit.The IP multicasting DL UP TNL information includes any combination or at least one of thefollowing: an IP multicast address, an IP source address, or a general packet radio servicetunneling protocol downlink tunnel endpoint identifier (GTP DL TEID).If the first information includes the broadcast / multicast service release request message, thefirst information includes any combination or at least one of the following: a first interfaceidentifier assigned by the first communication unit on the communication interface betweenthe first communication unit and the second communication unit for a broadcast / multicastservice, a second interface identifier assigned by the second communication unit on thecommunication interface between the first communication unit and the second communicationunit for a broadcast / multicast service, or a reason for releasing a broadcast / multicast service.In operation 120, second information sent by the second communication unit is received.It is to be noted that the gNB-DU receives the first information sent by the gNB-CU, performsadmission control according to the first information, and decides whether to execute theoperation related to broadcast / multicast service management in the corresponding cellindicated by the gNB-CU. Deciding whether to execute the operation related tobroadcast / multicast service management in the corresponding cell indicated by the gNB-CUmay include deciding whether to establish or modify a broadcast / multicast service radio bearerin the corresponding cell indicated by the gNB-CU. If the gNB-DU receives thebroadcast / multicast service release request message sent by the gNB-CU, thebroadcast / multicast service radio bearer in the corresponding cell indicated by the gNB-CU isreleased.In this embodiment of the present application, the second information is used for indicatingan execution result of the operation related to broadcast / multicast service management to thefirst communication unit. The second information includes a broadcast / multicast serviceestablishment response message, a broadcast / multicast service modification response message,or a broadcast / multicast service release response message.For example, if the gNB-DU agrees to establish a corresponding broadcast / multicast serviceradio bearer in the corresponding cell indicated by the gNB-CU, a broadcast / multicast serviceestablishment acknowledgement message is returned to the gNB-CU. If the gNB-DU does notagree to establish a corresponding broadcast / multicast service radio bearer in thecorresponding cell indicated by the gNB-CU, a broadcast / multicast service establishmentfailure message is returned to the gNB-CU. Alternatively, if the gNB-DU agrees to modify acorresponding broadcast / multicast service radio bearer in the corresponding cell indicated bythe gNB-CU, a broadcast / multicast service modification acknowledgement message isreturned to the gNB-CU. If the gNB-DU does not agree to modify a correspondingbroadcast / multicast service radio bearer in the corresponding cell indicated by the gNB-CU,a broadcast / multicast service modification failure message is returned to the gNB-CU.Alternatively, if the NB-DU receives the broadcast / multicast service release request messagesent by the gNB-CU, a broadcast / multicast service release complete message is returned tothe gNB-CU.In this embodiment of the present application, if the second information includes thebroadcast / multicast service establishment response message or the broadcast / multicast servicemodification response message, the second information includes any combination or at leastone of the following: a broadcast / multicast service identifier used to identify abroadcast / multicast service; a first interface identifier assigned by the first communicationunit on the communication interface between the first communication unit and the secondcommunication unit for a broadcast / multicast service; a second interface identifier assignedby the second communication unit on the communication interface between the firstcommunication unit and the second communication unit for a broadcast / multicast service; oneor more service area identifiers supporting a broadcast / multicast service; one or more piecesof cell identifier information of an established, modified, or released broadcast / multicastservice; information of successfully established or modified broadcast / multicast service radiobearer including identifier information of a successfully established or modifiedbroadcast / multicast service radio bearer and / or a logical channel identifier of a successfullyestablished or modified broadcast / multicast service radio bearer; information of successfullyreleased broadcast / multicast service radio bearer; configuration information of a secondcommunication unit of a broadcast / multicast service; downlink data TNL information of asuccessfully established or modified broadcast / multicast service radio bearer, where thedownlink data TNL information includes an IP address and / or a GTP DL TEID; informationof a broadcast / multicast service radio bearer which is failed to be established, includingidentifier information of the broadcast / multicast service radio bearer which is failed to beestablished and / or a reason for establishment failure of the broadcast / multicast service radiobearer; information of a broadcast / multicast service radio bearer which is failed to be modified,including identifier information of the broadcast / multicast service radio bearer which is failedto be modified and / or a reason for modification failure of the broadcast / multicast service radiobearer; a reason for establishment failure of a broadcast / multicast service; or a reason formodification failure of a broadcast / multicast service.The downlink data TNL information of a successfully established or modifiedbroadcast / multicast service radio bearer is unique downlink data TNL information shared byall cells in the second communication unit or multiple pieces of downlink data TNLinformation unique to each cell in the second communication unit.Specifically, the configuration information of a second communication unit of abroadcast / multicast service includes any combination or at least one of the following:configuration parameters of a second communication unit of control channel / information ofthe broadcast / multicast service, configuration parameters of a second communication unit oftransport channel / information of the broadcast / multicast service, or configuration parametersof a second communication unit of the broadcast / multicast service radio bearer.The configuration parameters of a second communication unit of control channel / informationof a broadcast / multicast service include any combination or at least one of the following: arepetition period of broadcast / multicast control channel / information, an offset ofbroadcast / multicast control channel / information, a start slot of broadcast / multicast controlchannel / information, a duration of broadcast / multicast control channel / information, amodification period of broadcast / multicast control channel / information, or a frequencydomain bandwidth part identifier of broadcast / multicast control channel / information.The configuration parameters of a second communication unit of transportchannel / information of a broadcast / multicast service include scheduling configurationinformation of broadcast / multicast transport channel / information. The schedulingconfiguration information of broadcast / multicast transport channel / information includes anycombination or at least one of the following: a duration timer of broadcast / multicast transportchannel / information, a timer related to discontinuous reception (DRX) of broadcast / multicasttransport channel / information, a scheduling period of broadcast / multicast transportchannel / information, a scheduling offset of broadcast / multicast transport channel / information,or a frequency domain bandwidth part identifier of broadcast / multicast transportchannel / information.The configuration parameters of a second communication unit of a broadcast / multicast serviceradio bearer include any combination or at least one of the following: a sequence numberlength of an RLC layer or a reassembly timer.If the second information includes the broadcast / multicast service release response message,the second information includes any combination or at least one of the following: a firstinterface identifier assigned by the first communication unit on the communication interfacebetween the first communication unit and the second communication unit for abroadcast / multicast service or a second interface identifier assigned by the secondcommunication unit on the communication interface between the first communication unit andthe second communication unit for a broadcast / multicast service.FIG. 2 is a flowchart of another broadcast / multicast service management method according toan embodiment of the present application. The method may be executed by abroadcast / multicast service management apparatus. The apparatus may be implemented bysoftware and / or hardware, typically configured in an electronic device such as a base station.As shown in FIG. 2, the method includes operations below.In operation 210, first information sent by a first communication unit is received.In operation 220, second information is sent to the first communication unit.According to the technical solution in this embodiment of the present application, a RAN airinterface effectively implements related management flows such as establishment,modification, or release of a broadcast / multicast service under an NR architecture.FIG. 3 is a flowchart of another broadcast / multicast service management method according toan embodiment of the present application. The method may be executed by abroadcast / multicast service management apparatus. The apparatus may be implemented bysoftware and / or hardware, typically configured in an electronic device such as a base station.As shown in FIG. 3, the method includes operations below.In operation 310, third information is sent to a first communication unit.It is to be noted that the third information is used for indicating the first communication unitto execute an operation related to broadcast / multicast service management. For example, agNB-DU sends the third information to a gNB-CU to indicate the gNB-CU to execute theoperation related to broadcast / multicast service management. Due to some scenariorequirements, the gNB-DU needs to modify or release an established broadcast / multicastservice. In this case, the third information is sent to the gNB-CU to indicate the gNB-CU tomodify or release a corresponding broadcast / multicast service.Specifically, the third information includes a broadcast / multicast service modification requestmessage or a broadcast / multicast service release request message.If the third information includes the broadcast / multicast service modification request message,the third information includes any combination or at least one of the following: abroadcast / multicast service identifier used to identify a broadcast / multicast service; a firstinterface identifier assigned by the first communication unit on the communication interfacebetween the first communication unit and a second communication unit for abroadcast / multicast service; a second interface identifier assigned by a second communicationunit on the communication interface between the first communication unit and the secondcommunication unit for a broadcast / multicast service; one or more service area identifierssupporting a broadcast / multicast service; one or more cell identifiers of one or more cellswhich needs to modify or release a broadcast / multicast service, where the cell identifiersinclude NCGI information or PCI information; a cell list identifier of a service area; attributeinformation of a broadcast / multicast service radio bearer needing to be modified;configuration information of a second communication unit of a broadcast / multicast service;or downlink data TNL information of a broadcast / multicast service radio bearer needing to bemodified, where the downlink data TNL information includes an IP address and / or a GTP DLTEID.The downlink data TNL information of a broadcast / multicast service radio bearer needing tobe modified may be unique downlink data TNL information shared by all cells in a secondcommunication unit or multiple pieces of downlink data TNL information unique to each cellin a second communication unit.Specifically, the attribute information of a broadcast / multicast service radio bearer needing tobe modified includes any combination or at least one of the following: identifier informationof the broadcast / multicast service radio bearer or an RLC status of the broadcast / multicastservice radio bearer.Specifically, the configuration information of a second communication unit of abroadcast / multicast service includes any combination or at least one of the following:configuration parameters of a second communication unit of control channel / information ofthe broadcast / multicast service, configuration parameters of a second communication unit oftransport channel / information of the broadcast / multicast service, or configuration parametersof a second communication unit of a broadcast / multicast service radio bearer.The configuration parameters of a second communication unit of control channel / informationof a broadcast / multicast service include any combination or at least one of the following: arepetition period of broadcast / multicast control channel / information, an offset ofbroadcast / multicast control channel / information, a start slot of broadcast / multicast controlchannel / information, a duration of broadcast / multicast control channel / information, amodification period of broadcast / multicast control channel / information, or a frequencydomain bandwidth part identifier of broadcast / multicast control channel / information.The configuration parameters of a second communication unit of transportchannel / information of a broadcast / multicast service include scheduling configurationinformation of broadcast / multicast transport channel / information. The schedulingconfiguration information of broadcast / multicast transport channel / information includes anycombination or at least one of the following: a duration timer of broadcast / multicast transportchannel / information, a timer related to discontinuous reception (DRX) of broadcast / multicasttransport channel / information, a scheduling period of broadcast / multicast transportchannel / information, a scheduling offset of broadcast / multicast transport channel / information,or a frequency domain bandwidth part identifier of broadcast / multicast transportchannel / information.The configuration parameters of a second communication unit of a broadcast / multicast serviceradio bearer include any combination or at least one of the following: a sequence numberlength of an RLC layer or a reassembly timer.Optionally, if the third information includes a broadcast / multicast service release requestmessage, the third information includes a first interface identifier assigned by the firstcommunication unit on the communication interface between the first communication unit andthe second communication unit for a broadcast / multicast service, a second interface identifierassigned by a second communication unit on the communication interface between the firstcommunication unit and the second communication unit for a broadcast / multicast service, ora reason for releasing a broadcast / multicast service.In operation 320, fourth information sent by the first communication unit is received.It is to be noted that the fourth information is used for indicating an execution result of anoperation related to broadcast / multicast service management to the second communicationunit. For example, the gNB-CU sends the fourth information to the gNB-DU to indicatemodification acknowledgement of a broadcast / multicast service to the gNB-DU. If the gNB-CU agrees to the modification, the fourth information may be a broadcast / multicast servicemodification acknowledgement message. If the gNB-CU does not agree to the modification,the fourth information may be a broadcast / multicast service modification failure message.In this embodiment of the present application, the fourth information includes anycombination or at least one of the following: a broadcast / multicast service identifier used toidentify a broadcast / multicast service, a first interface identifier assigned by the firstcommunication unit on the communication interface between the first communication unit andthe second communication unit for a broadcast / multicast service, a second interface identifierassigned by the second communication unit on the communication interface between the firstcommunication unit and the second communication unit for a broadcast / multicast service, oneor more service area identifiers supporting a broadcast / multicast service, one or more piecesof cell identifier information of a modified or released broadcast / multicast service, orinformation of successfully modified or released broadcast / multicast service radio bearer.FIG. 4 is a flowchart of another broadcast / multicast service management method according toan embodiment of the present application. The method may be executed by abroadcast / multicast service management apparatus. The apparatus may be implemented bysoftware and / or hardware, typically configured in an electronic device such as a base station.As shown in FIG. 4, the method includes operations below.In operation 410, third information sent by a second communication unit is received.In operation 420, fourth information is sent to the second communication unit.According to the technical solution in this embodiment of the present application, a RAN airinterface effectively implements related management flows such as modification or release ofa broadcast / multicast service under an NR architecture.In an example embodiment, a broadcast / multicast service establishment flow between a CUand a DU in a base station is specifically described. FIG. 5 is a flowchart illustrating theestablishment of a broadcast / multicast service between a gNB-CU and a gNB-DU accordingto an embodiment of the present application. As shown in FIG. 5, the flow includes theoperations below.In operation 510, a gNB-CU receives an MBMS session establishment request message of acore network sent by the core network.The MBMS session establishment request message of a core network mainly includes anycombination or at least one of the following: a broadcast / multicast service identifier;information of a service area identifier (SAI), where the MBMS session is located in theservice area; or an MBMS session flow identifier and attribute parameter information ofquality of service (QoS) of the MBMS session flow included in the MBMS session. Thebroadcast / multicast service identifier may identify a broadcast / multicast service through anMBMS session identity document (ID), a temporary mobile group identity (TMGI), or otheridentifier information.In operation 520, the gNB-CU performs admission control on the MBMS session anddetermines in which cells of which gNB-CUs the MBMS session can be established.Meanwhile, according to the QoS profile information of each flow included in the MBMSsession indicated by the core network, the gNB-CU performs mapping from flows tobroadcast / multicast service radio bearers, determines the broadcast / multicast service radiobearer to be established in the corresponding cell, and generates the QoS profile informationof the broadcast / multicast service radio bearer according to the QoS profile information of theflow mapped to the broadcast / multicast service radio bearer. The broadcast / multicast serviceradio bearer is mainly used for carrying MBMS data sent by a base station to a UE on theradio access network. In addition, if the transport mode between the gNB-CU (or simply CU)and the gNB-DU (or simply DU) is IP multicast, the gNB-CU further needs to assign downlinkdata TNL information for transmitting the broadcast / multicast service radio bearer to the DU.Specifically, the downlink data TNL information includes an IP multicast address, an IP sourceaddress, and a GTP-TEID.In operation 530, the gNB-CU initiates an establishment request session flow of the MBMSsession to gNB-DUs in which the cells that can support the MBMS session are located.Specifically, the gNB-CU sends an MBMS session establishment request message to thesegNB-DUs.Optionally, the granularity of the message may be an MBMS session or a non-UE associatedsignaling.The message mainly includes any combination or at least one of the following: abroadcast / multicast service identifier; a unique interface identifier (that is, MBMS Session F1Application Protocol (F1AP) ID) assigned by the gNB-CU on the F1 interface between thegNB-CU and the gNB-DU for the broadcast / multicast service; if the transport mode betweenthe gNB-CU and the gNB-DU is IP multicast, needing to carry the IP multicast TNLinformation assigned for each gNB-DU; one or more service area identifiers (SAIs) supportingthe broadcast / multicast service; adding one or more cell identifiers supporting thebroadcast / multicast service, where the cell identifiers include NCGI information or PCIinformation; a cell list identifier of a service area; information of a broadcast / multicast serviceradio bearer needing to be established; change notification indication information used for thegNB-CU to notify the gNB-DU that the configuration information of the broadcast / multicastservice is changed; configuration information of the broadcast / multicast service; orinformation of an RLC mode of a broadcast / multicast service radio bearer.The broadcast / multicast service identifier may identify a broadcast / multicast service throughan MBMS session ID, a TMGI, or other identifier information.The IP multicast TNL information specifically includes any combination or at least one of thefollowing: an IP multicast address, an IP source address, or a GTP DL TEID.The information of the broadcast / multicast service radio bearer needing to be establishedincludes identifier information of a broadcast / multicast service radio bearer and / or attributeinformation of a broadcast / multicast service radio bearer.The attribute information of a broadcast / multicast service radio bearer further includes QoSinformation of the broadcast / multicast service radio bearer, dataflow information mapped tothe broadcast / multicast service radio bearer, and notification control. The dataflowinformation mapped to the broadcast / multicast service radio bearer includes any combinationor at least one of the following: dataflow identifier information or QoS information of thedataflow mapped to the broadcast / multicast service radio bearer.The change notification indication information is used for the CU to notify the DU that theconfiguration information of the broadcast / multicast service is changed. After receiving thechange notification indication information, the DU sends downlink control information (DCI)to a UE, indicating that the configuration information of the broadcast / multicast servicecontrol channel / information is changed.The configuration information of the broadcast / multicast service includes any combination orat least one of the following: system information of broadcast / multicast service information,control channel / information configuration parameters of the broadcast / multicast service,transport channel / information configuration parameters of the broadcast / multicast service, orradio bearer configuration parameters of the broadcast / multicast service.In operation 540, after receiving the MBMS session establishment request message sent bythe gNB-CU, the gNB-DU performs admission control and decides whether to establish acorresponding broadcast / multicast service radio bearer in the corresponding cell indicated bythe CU.In operation 550, if yes, an MBMS session establishment response message is returned to thegNB-CU. The response message indicates a broadcast / multicast service radio bearer which isestablished successfully and a broadcast / multicast service radio bearer which is failed to beestablished.In the case where the MBMS session is established successfully, the MBMS sessionestablishment response message returned by the DU to the CU includes any combination orat least one of the following: a broadcast / multicast service identifier; a unique interfaceidentifier (that is, MBMS Session F1 AP ID) assigned by the CU on the F1 interface betweenthe CU and the DU for the broadcast / multicast service; a unique interface identifier (that is,MBMS Session F1 AP ID) assigned by the DU on the F1 interface between the CU and theDU for the broadcast / multicast service; one or more service area identifiers (SAIs) supportingthe broadcast / multicast service; one or more pieces of cell identifier information of anestablished broadcast / multicast service; a cell list identifier of a service area; information of asuccessfully established broadcast / multicast service radio bearer including identifierinformation of the successfully established broadcast / multicast service radio bearer and / or alogical channel identifier (LCID) of the successfully established broadcast / multicast serviceradio bearer; configuration information of a second communication unit of abroadcast / multicast service; downlink data TNL information of a successfully establishedbroadcast / multicast service radio bearer, where the downlink data TNL information includesan IP address and / or a GTP DL TEID, and the downlink data TNL information of thesuccessfully established broadcast / multicast service radio bearer may be unique downlink dataTNL information shared by all cells in the second communication unit, or may be multiplepieces of downlink data TNL information unique to each cell in the second communicationunit; or information of a broadcast / multicast service radio bearer which is failed to beestablished, including any combination or at least one of the following: identifier informationof the broadcast / multicast service radio bearer which is failed to be established or a reason forestablishment failure of the broadcast / multicast service radio bearer. The broadcast / multicastservice identifier may identify a broadcast / multicast service through an MBMS session ID, aTMGI, or other identifier information.The configuration information of a second communication unit of a broadcast / multicastservice includes any combination or at least one of the following: configuration parameters ofa DU of control channel / information of the broadcast / multicast service, configurationparameters of a DU of transport channel / information of the broadcast / multicast service, orconfiguration parameters of a DU of a broadcast / multicast service radio bearer.The configuration parameters of a DU of control channel / information of thebroadcast / multicast service include any combination or at least one of the following: arepetition period (that is, mcch-RepetionPeriod) of broadcast / multicast controlchannel / information, an offset of broadcast / multicast control channel / information, a start slot(that is, mcch-slot-bitmap) of broadcast / multicast control channel / information, a duration (thatis, mcch-duration) of broadcast / multicast control channel / information, a modification period(that is, mcch-ModificationPeriod) of broadcast / multicast control channel / information, or afrequency domain bandwidth part ID (BWP ID) of broadcast / multicast controlchannel / information.The configuration parameters of a DU of transport channel / information of thebroadcast / multicast service include scheduling configuration information (that is, mtch-scheduling info) of broadcast / multicast transport channel / information. The schedulingconfiguration information (that is, mtch-scheduling info) of broadcast / multicast transportchannel / information includes any combination or at least one of the following: a durationtimer (that is, onduration timer) of the broadcast / multicast transport channel / information, atimer (that is, drx-inactivity timer) related to discontinuous reception (DRX) of thebroadcast / multicast transport channel / information, a scheduling period of thebroadcast / multicast transport channel / information, a scheduling offset of thebroadcast / multicast transport channel / information, or a frequency domain bandwidth partidentifier (BWP ID) of the broadcast / multicast transport channel / information.The configuration parameters of a DU of a broadcast / multicast service radio bearer include asequence number length of an RLC layer and / or a reassembly timer (that is, T-Reassemblytimer).In operation 560, if no, an establishment failure message is returned to the gNB-CU.The MBMS session establishment failure message returned by the DU to the CU includes anycombination or at least one of the following: a unique interface identifier (that is, MBMSSession F1 AP ID) assigned by the CU on the F1 interface between the CU and the DU for thebroadcast / multicast service, a unique interface identifier (that is, MBMS Session F1 AP ID)assigned by the DU on the F1 interface between the CU and the DU for the broadcast / multicastservice, or a reason for establishment failure of the MBMS session.In an example embodiment, a broadcast / multicast service modification flow between a CUand a DU in a base station is specifically described. FIG. 6 is a flowchart illustrating themodification of a broadcast / multicast service between a gNB-CU and a gNB-DU initiated bythe gNB-CU according to an embodiment of the present application. As shown in FIG. 6, theflow includes the operations below.In operation 610, the gNB-CU determines that an established MBMS session needs to bemodified.For example, parameters of a broadcast / multicast service radio bearer are modified. It mayalso be necessary to update, modify, or release the existing broadcast / multicast service radiobearer for the established MBMS session. Configuration information related to the MBMSsession may also need to be modified. The cell list corresponding to the service area of theMBMS session may also need to be added, modified, and released.In operation 620, the gNB-CU initiates a modification request session flow of the MBMSsession to gNB-DUs in which the cells that need to modify the MBMS session are located.Specifically, the gNB-CU sends an MBMS session modification request message to thesegNB-DUs.Optionally, the granularity of the message may be an MBMS session or a non-UE associatedsignaling.In operation 630, after receiving the MBMS session modification request message sent by thegNB-CU, a gNB-DU performs admission control and decides whether to modify acorresponding broadcast / multicast service radio bearer in the corresponding cell indicated bythe CU.In operation 640, if yes, an MBMS session modification response message is returned to thegNB-CU. The response message indicates a broadcast / multicast service radio bearer which ismodified successfully and a broadcast / multicast service radio bearer which is failed to bemodified.In operation 650, if no, the gNB-DU returns a modification failure message to the gNB-CU.In an example embodiment, a broadcast / multicast service modification flow between a DUand a CU in a base station is specifically described. FIG. 7 is a flowchart illustrating themodification of a broadcast / multicast service between a gNB-CU and a gNB-DU initiated bythe gNB-DU according to an embodiment of the present application. As shown in FIG. 7, theflow includes the operations below.In operation 710, the gNB-DU determines that an established MBMS session needs to bemodified.For example, configuration parameters of a DU of a broadcast / multicast service radio bearerare modified. An established broadcast / multicast service radio bearer may also need to bemodified or released. Configuration information related to the MBMS session may also needto be modified. The cell list corresponding to the service area of the MBMS session may alsoneed to be modified and released.In operation 720, the gNB-DU initiates a modification request session flow of the MBMSsession to the gNB-CU. Specifically, the gNB-DU sends an MBMS session modificationrequest message to the gNB-CU.Optionally, the granularity of the message may be an MBMS session or a non-UE associatedsignaling.The message mainly includes any combination or at least one of the following: abroadcast / multicast service identifier; a unique interface identifier (that is, MBMS Session F1AP ID) assigned by the CU on the F1 interface between the CU and the DU for thebroadcast / multicast service; a unique interface identifier (that is, MBMS Session F1 AP ID)assigned by the DU on the F1 interface between the CU and the DU for the broadcast / multicastservice; one or more service area identifiers (SAIs) supporting the broadcast / multicast service;one or more cell identifiers of one or more cells which needs to modify or release thebroadcast / multicast service, where the cell identifiers include NCGI information or PCIinformation; a cell list identifier of a service area; attribute information of abroadcast / multicast service radio bearer needing to be modified or released; configurationinformation of a DU of the broadcast / multicast service; or downlink data TNL information ofa broadcast / multicast service radio bearer needing to be modified, where the downlink dataTNL information includes an IP address and / or a GTP DL TEID, and the downlink data TNLinformation of the broadcast / multicast service radio bearer needing to be modified is uniquedownlink data TNL information shared by all cells in a second communication unit or multiplepieces of downlink data TNL information unique to each cell in a second communication unit.The broadcast / multicast service identifier may identify a broadcast / multicast service throughan MBMS session ID, a TMGI, or other identifier information.The attribute information of a broadcast / multicast service radio bearer needing to be modifiedspecifically includes any combination or at least one of the following: identifier informationof the broadcast / multicast service radio bearer or an RLC status of the broadcast / multicastservice radio bearer.The configuration information of a DU of the broadcast / multicast service includes anycombination or at least one of the following: configuration parameters of a DU of controlchannel / information of the broadcast / multicast service, configuration parameters of a DU oftransport channel / information of the broadcast / multicast service, or configuration parametersof a DU of a broadcast / multicast service radio bearer.The configuration parameters of a DU of control channel / information of thebroadcast / multicast service include any combination or at least one of the following: arepetition period (that is, mcch-RepetionPeriod) of broadcast / multicast controlchannel / information, an offset of broadcast / multicast control channel / information, a start slot(that is, mcch-slot-bitmap) of broadcast / multicast control channel / information, a duration (thatis, mcch-duration) of broadcast / multicast control channel / information, a modification period(that is, mcch-ModificationPeriod) of broadcast / multicast control channel / information, or afrequency domain bandwidth part ID (BWP ID) of broadcast / multicast controlchannel / information.The configuration parameters of a DU of transport channel / information of thebroadcast / multicast service include scheduling configuration information (that is, mtch-scheduling info) of broadcast / multicast transport channel / information. The schedulingconfiguration information (that is, mtch-scheduling info) of broadcast / multicast transportchannel / information includes any combination or at least one of the following: a durationtimer (that is, onduration timer) of the broadcast / multicast transport channel / information, atimer (that is, drx-inactivity timer) related to discontinuous reception (DRX) of thebroadcast / multicast transport channel / information, a scheduling period of thebroadcast / multicast transport channel / information, a scheduling offset of thebroadcast / multicast transport channel / information, or a frequency domain bandwidth partidentifier (BWP ID) of the broadcast / multicast transport channel / information.In operation 730, after receiving the MBMS session modification request message sent by thegNB-DU, the gNB-CU performs admission control and decides whether to makecorresponding modification.In operation 740, if yes, a modification acknowledgement message is returned to the gNBDU.The MBMS session modification acknowledgement message returned by the CU to the DUincludes any combination or at least one of the following: a broadcast / multicast serviceidentifier, a unique interface identifier (that is, MBMS Session F1 AP ID) assigned by the CUon the F1 interface between the CU and the DU for the broadcast / multicast service, a uniqueinterface identifier (that is, MBMS Session F1 AP ID) assigned by the DU on the F1 interfacebetween the CU and the DU for the broadcast / multicast service. one or more service areaidentifiers (SAIs) supporting the broadcast / multicast service, one or more pieces of cellidentifier information having modified or released the broadcast / multicast service, a cell listidentifier of a service area, or information of successfully modified or releasedbroadcast / multicast service radio bearer.The broadcast / multicast service identifier may identify a broadcast / multicast service throughan MBMS session ID, a TMGI, or other identifier information.In operation 750, if no, the gNB-CU returns a modification rejection message to the gNB-DU.The MBMS session modification rejection message returned by the CU to the DU includesany combination or at least one of the following: a unique interface identifier (that is, MBMSSession F1 AP ID) assigned by the CU on the F1 interface between the CU and the DU for thebroadcast / multicast service, a unique interface identifier (that is, MBMS Session F1 AP ID)assigned by the DU on the F1 interface between the CU and the DU for the broadcast / multicastservice; or a reason for modification failure of the MBMS session.In an example embodiment, a broadcast / multicast service release flow between a CU and aDU in a base station is specifically described. FIG. 8 is a flowchart illustrating the release ofa broadcast / multicast service between a gNB-CU and a gNB-DU initiated by the gNB-CUaccording to an embodiment of the present application. As shown in FIG. 8, the flow includesthe operations below.In operation 810, the gNB-CU determines that an established MBMS session needs to bereleased. The gNB-CU initiates a release request session flow of the MBMS session to thegNB-DU in which the cell that needs to release the MBMS session is located. Specifically, thegNB-CU sends an MBMS session release request message to the gNB-DU.Optionally, the granularity of the message may be an MBMS session or a non-UE associatedsignaling.The message mainly includes any combination or at least one of the following: a uniqueinterface identifier (that is, MBMS Session F1 AP ID) assigned by the CU on the F1 interfacebetween the CU and the DU for the broadcast / multicast service, a unique interface identifier(that is, MBMS Session F1 AP ID) assigned by the DU on the F1 interface between the CUand the DU for the broadcast / multicast service, or a reason for releasing thebroadcast / multicast service.In operation 820, after receiving the MBMS session release request message sent by the gNBCU, the gNB-DU returns an MBMS session release complete message to the gNB-CU.The message mainly includes any combination or at least one of the following: a uniqueinterface identifier (that is, MBMS Session F1 AP ID) assigned by the CU on the F1 interfacebetween the CU and the DU for the broadcast / multicast service or a unique interface identifier(that is, MBMS Session F1 AP ID) assigned by the DU on the F1 interface between the CUand the DU for the broadcast / multicast service.In an example embodiment, a broadcast / multicast service release flow between a DU and aCU in a base station is specifically described. FIG. 9 is a flowchart illustrating the release ofa broadcast / multicast service between a gNB-CU and a gNB-DU initiated by the gNB-DUaccording to an embodiment of the present application. As shown in FIG. 9, the flow includesthe operations below.In operation 910, the gNB-DU determines that an established MBMS session needs to bereleased, and the gNB-DU initiates a release request session flow of the MBMS session to thegNB-CU. Specifically, the gNB-DU sends an MBMS session release request message to thegNB-CU.The setting scenario requirements include that an established MBMB session needs to bereleased for reasons such as poor air interface link quality.Optionally, the granularity of the message may be an MBMS session or a non-UE associatedsignaling.The message mainly includes any combination or at least one of the following: a uniqueinterface identifier (that is, MBMS Session F1 AP ID) assigned by the CU on the F1 interfacebetween the CU and the DU for the broadcast / multicast service, a unique interface identifier(that is, MBMS Session F1 AP ID) assigned by the DU on the F1 interface between the CUand the DU for the broadcast / multicast service, or a reason for releasing thebroadcast / multicast service.FIG. 10 is a block diagram illustrating the structure of a broadcast / multicast servicemanagement apparatus according to an embodiment of the present application. The apparatusmay be implemented by software and / or hardware, typically configured in an electronic devicesuch as a base station. As shown in FIG. 10, the apparatus includes a first sending module1010 and a first reception module 1020.The first sending module 1010 is configured to send first information to a secondcommunication unit. The first information is used to instruct the second communication unitto execute an operation related to broadcast / multicast service management.The first reception module 1020 is configured to receive second information sent by thesecond communication unit. The second information is used to indicate an execution result ofthe operation to a first communication unit.The broadcast / multicast service management apparatus provided in this embodiment canexecute the broadcast / multicast service management method provided in the embodiments ofthe present application and has function modules and beneficial effects corresponding to themethod.FIG. 11 is a block diagram illustrating the structure of another broadcast / multicast servicemanagement apparatus according to an embodiment of the present application. The apparatusmay be implemented by software and / or hardware, typically configured in an electronic devicesuch as a base station. As shown in FIG. 11, the apparatus includes a second reception module1110 and a second sending module 1120.The second reception module 1110 is configured to receive first information sent by a firstcommunication unit. The first information is used to instruct a second communication unit toexecute an operation related to broadcast / multicast service management.The second sending module 1120 is configured to send second information to the firstcommunication unit. The second information is used to indicate an execution result of theoperation to the first communication unit.The broadcast / multicast service management apparatus provided in this embodiment canexecute the broadcast / multicast service management method provided in the embodiments ofthe present application and has function modules and beneficial effects corresponding to themethod.FIG. 12 is a block diagram illustrating the structure of another broadcast / multicast servicemanagement apparatus according to an embodiment of the present application. The apparatusmay be implemented by software and / or hardware, typically configured in an electronic devicesuch as a base station. As shown in FIG. 12, the apparatus includes a third sending module1210 and a third reception module 1220.The third sending module 1210 is configured to send third information to a firstcommunication unit. The third information is used to instruct the first communication unit toexecute an operation related to broadcast / multicast service management.The third reception module 1220 is configured to receive fourth information sent by the firstcommunication unit. The fourth information is used to indicate an execution result of theoperation to a second communication unit.The broadcast / multicast service management apparatus provided in this embodiment canexecute the broadcast / multicast service management method provided in the embodiments ofthe present application and has function modules and beneficial effects corresponding to themethod.FIG. 13 is a block diagram illustrating the structure of another broadcast / multicast servicemanagement apparatus according to an embodiment of the present application. The apparatusmay be implemented by software and / or hardware, typically configured in an electronic devicesuch as a base station. As shown in FIG. 13, the apparatus includes a fourth reception module1310 and a fourth sending module 1320.The fourth reception module 1310 is configured to receive third information sent by a secondcommunication unit. The third information is used to instruct a first communication unit toexecute an operation related to broadcast / multicast service management.The fourth sending module 1320 is configured to send fourth information to the secondcommunication unit. The fourth information is used to indicate an execution result of theoperation to the second communication unit.The broadcast / multicast service management apparatus provided in this embodiment canexecute the broadcast / multicast service management method provided in the embodiments ofthe present application and has function modules and beneficial effects corresponding to themethod.An embodiment of the present application provides an electronic device. The electronic deviceincludes one or more processors and a memory.The memory is configured to store one or more programs.When executed by the one or more processors, the one or more programs cause the one ormore processors to implement the method in any embodiment of the present application.An embodiment of the present application provides a storage medium storing a computerprogram which, when executed by a processor, implements the method in any embodiment ofthe present application.The above are only example embodiments of the present application and are not intended tolimit the scope of the present application.A block diagram of any logic flow among the drawings of the present application mayrepresent program steps, may represent interconnected logic circuits, modules, and functions,or may represent a combination of program steps with logic circuits, modules, and functions.Computer programs may be stored in a memory. The memory may be of any type suitable fora local technical environment and may be implemented using any suitable data storagetechnology, for example, but not limited to, a read-only memory (ROM), a random-accessmemory (RAM), and an optical memory device and system (digital versatile disc (DVD) orcompact disc (CD)). A computer-readable medium may include a non-transitory storagemedium. A data processor may be in any type suitable for the local technical environment, forexample, but not limited to, a general-purpose computer, a special-purpose computer, amicroprocessor, a digital signal processor (DSP), an application-specific integrated circuit(ASIC), a field-programmable gate array (FGPA), and a processor based on a multi-coreprocessor architecture.
Claims
1. A broadcast / multicast service management method, comprising: sending first information to a second communication unit, wherein the first information is used to instruct the second communication unit to execute an operation related to broadcast / multicast service management; and receiving second information sent by the second communication unit, wherein the second information is used to indicate an execution result of the operation related to the broadcast / multicast service management to a first communication unit.
2. The method of claim 1, wherein the first information comprises a broadcast / multicast service establishment request message, a broadcast / multicast service modification request message, or a broadcast / multicast service release request message.
3. The method of claim 2, wherein in a case where the first information comprises the broadcast / multicast service establishment request message or the broadcast / multicast service modification request message, the first information comprises at least one of the following: a broadcast / multicast service identifier used to identify a broadcast / multicast service; a first interface identifier assigned by the first communication unit on a communication interface between the first communication unit and the second communication unit for a broadcast / multicast service; a second interface identifier assigned by the second communication unit on a communication interface between the first communication unit and the second communication unit for a broadcast / multicast service; at least one service area identifier supporting a broadcast / multicast service; a cell identifier of at least one cell which needs to establish, modify, or release a broadcast / multicast service, wherein the cell identifier comprises new radio cell global identifier (NCGI) information or physical cell identifier (PCI) information; a cell list identifier of a service area; information of a broadcast / multicast service radio bearer needing to be established or modified; configuration information of a broadcast / multicast service; information of a radio link control (RLC) mode of a broadcast / multicast service radio bearer; information of a broadcast / multicast service radio bearer needing to be released comprising identifier information of a broadcast / multicast service radio bearer; or change notification indication information, wherein the change notification indication information is used for the first communication unit to notify the second communication unit that configuration information of a broadcast / multicast service is changed.
4. The method of claim 3, wherein the information of the broadcast / multicast service radio bearer needing to be established or modified comprises at least one of identifier information of a broadcast / multicast service radio bearer or attribute information of a broadcast / multicast service radio bearer.
5. The method of claim 4, wherein the attribute information of the broadcast / multicast service radio bearer comprises quality of service information of the broadcast / multicast service radio bearer, dataflow information mapped to the broadcast / multicast service radio bearer, and notification control, wherein the dataflow information mapped to the broadcast / multicast service radio bearer comprises at least one of dataflow identifier information or quality of service information of a dataflow mapped to the broadcast / multicast service radio bearer.
6. The method of claim 3, wherein the configuration information of the broadcast / multicast service comprises at least one of the following: system information of broadcast / multicast service information; control channel / information configuration parameters of the broadcast / multicast service; transport channel / information configuration parameters of the broadcast / multicast service; or radio bearer configuration parameters of the broadcast / multicast service.
7. The method of claim 3, wherein in a case where a transport mode between the first communication unit and the second communication unit is Internet protocol (IP) multicasting, the first information further comprises IP multicasting downlink user plane transport network layer (DL UP TNL) information assigned to the second communication unit, wherein the IP multicasting DL UP TNL information comprises at least one of the following: an IP multicast address; an IP source address; or a general packet radio service tunneling protocol downlink tunnel endpoint identifier (GTP DL TEID).
8. The method of claim 2, wherein in a case where the first information comprises the broadcast / multicast service release request message, the first information comprises at least one of the following: a first interface identifier assigned by the first communication unit on a communication interface between the first communication unit and the second communication unit for a broadcast / multicast service; a second interface identifier assigned by the second communication unit on a communication interface between the first communication unit and the second communication unit for a broadcast / multicast service; or a reason for releasing a broadcast / multicast service.
9. The method of claim 1, wherein the second information comprises a broadcast / multicast service establishment response message, a broadcast / multicast service modification response message, or a broadcast / multicast service release response message.
10. The method of claim 9, wherein in a case where the second information comprises the broadcast / multicast service establishment response message or the broadcast / multicast service modification response message, the second information comprises at least one of the following: a broadcast / multicast service identifier used to identify a broadcast / multicast service; a first interface identifier assigned by the first communication unit on a communication interface between the first communication unit and the second communication unit for a broadcast / multicast service; a second interface identifier assigned by the second communication unit on a communication interface between the first communication unit and the second communication unit for a broadcast / multicast service; at least one service area identifier supporting a broadcast / multicast service; cell identifier information of at least one cell which has an established, modified, or released broadcast / multicast service; information of a successfully established or modified broadcast / multicast service radio bearer comprising at least one of identifier information of a successfully established or modified broadcast / multicast service radio bearer or a logical channel identifier of a successfully established or modified broadcast / multicast service radio bearer; information of a successfully released broadcast / multicast service radio bearer; configuration information of a second communication unit of a broadcast / multicast service; downlink data transport network layer (TNL) information of a successfully established or modified broadcast / multicast service radio bearer, wherein the downlink data TNL information comprises an IP address and / or a GTP DL TEID; information of a broadcast / multicast service radio bearer which is failed to be established, comprising at least one of identifier information of the broadcast / multicast service radio bearer which is failed to be established or a reason for establishment failure of the broadcast / multicast service radio bearer; information of a broadcast / multicast service radio bearer which is failed to be modified, comprising at least one of identifier information of the broadcast / multicast service radio bearer which is failed to be modified or a reason for modification failure of the broadcast / multicast service radio bearer; a reason for establishment failure of a broadcast / multicast service; or a reason for modification failure of a broadcast / multicast service.
11. The method of claim 10, wherein the downlink data TNL information of the successfully established or modified broadcast / multicast service radio bearer is unique downlink data TNL information shared by all cells in the second communication unit or a plurality of pieces of downlink data TNL information unique to each cell in the second communication unit.
12. The method of claim 10, wherein the configuration information of the second communication unit of the broadcast / multicast service comprises at least one of the following: configuration parameters of the second communication unit of control channel / information of the broadcast / multicast service; configuration parameters of the second communication unit of transport channel / information of the broadcast / multicast service; or configuration parameters of the second communication unit of a broadcast / multicast service radio bearer, wherein the configuration parameters of the second communication unit of control channel / information of the broadcast / multicast service comprise at least one of the following: a repetition period of broadcast / multicast control channel / information; an offset of broadcast / multicast control channel / information; a start slot of broadcast / multicast control channel / information; a duration of broadcast / multicast control channel / information; a modification period of broadcast / multicast control channel / information; or a frequency domain bandwidth part identifier of broadcast / multicast control channel / information; the configuration parameters of the second communication unit of transport channel / information of the broadcast / multicast service comprise scheduling configuration information of the broadcast / multicast transport channel / information, wherein the scheduling configuration information of the broadcast / multicast transport channel / information comprises at least one of the following: a duration timer of the broadcast / multicast transport channel / information; a timer related to discontinuous reception (DRX) of the broadcast / multicast transport channel / information; a scheduling period of the broadcast / multicast transport channel / information; a scheduling offset of the broadcast / multicast transport channel / information; or a frequency domain bandwidth part identifier of the broadcast / multicast transport channel / information; and the configuration parameters of the second communication unit of the broadcast / multicast service radio bearer comprise at least one of the following: a sequence number length of a radio link control (RLC) layer; or a reassembly timer.
13. The method of claim 9, wherein in a case where the second information comprises the broadcast / multicast service release response message, the second information comprises at least one of the following: a first interface identifier assigned by the first communication unit on a communication interface between the first communication unit and the second communication unit for a broadcast / multicast service; or a second interface identifier assigned by the second communication unit on a communication interface between the first communication unit and the second communication unit for a broadcast / multicast service.
14. A broadcast / multicast service management method, comprising: receiving first information sent by a first communication unit, wherein the first information is used to instruct a second communication unit to execute an operation related to broadcast / multicast service management; and sending second information to the first communication unit, wherein the second information is used to indicate an execution result of the operation related to broadcast / multicast service management to the first communication unit.
15. A broadcast / multicast service management method, comprising: sending third information to a first communication unit, wherein the third information is used to instruct the first communication unit to execute an operation related to broadcast / multicast service management; and receiving fourth information sent by the first communication unit, wherein the fourth information is used to indicate an execution result of the operation related to broadcast / multicast service management to a second communication unit.
16. The method of claim 15, wherein the third information comprises a broadcast / multicast service modification request message or a broadcast / multicast service release request message.
17. The method of claim 16, wherein in a case where the third information comprises the broadcast / multicast service modification request message, the third information comprises at least one of the following: a broadcast / multicast service identifier used to identify a broadcast / multicast service; a first interface identifier assigned by the first communication unit on a communication interface between the first communication unit and the second communication unit for a broadcast / multicast service; a second interface identifier assigned by the second communication unit on a communication interface between the first communication unit and the second communication unit for a broadcast / multicast service; at least one service area identifier supporting a broadcast / multicast service; a cell identifier of at least one cell which needs to modify or release a broadcast / multicast service, wherein the cell identifier comprises new radio cell global identifier (NCGI) information or physical cell identifier (PCI) information; a cell list identifier of a service area; attribute information of a broadcast / multicast service radio bearer needing to be modified; configuration information of a second communication unit of a broadcast / multicast service; or downlink data TNL information of a broadcast / multicast service radio bearer needing to be modified, wherein the downlink data TNL information comprises at least one of an Internet protocol (IP) address or a general packet radio service tunneling protocol downlink tunnel endpoint identifier (GTP DL TEID).
18. The method of claim 17, wherein the downlink data TNL information of a broadcast / multicast service radio bearer needing to be modified is unique downlink data TNL information shared by all cells in the second communication unit or a plurality of pieces of downlink data TNL information unique to each cell in the second communication unit.
19. The method of claim 17, wherein the attribute information of a broadcast / multicast service radio bearer needing to be modified comprises at least one of the following: identifier information of the broadcast / multicast service radio bearer; or a radio link control (RLC) state of the broadcast / multicast service radio bearer.
20. The method of claim 17, wherein the configuration information of a second communication unit of a broadcast / multicast service comprises at least one of the following: configuration parameters of a second communication unit of control channel / information of the broadcast / multicast service; configuration parameters of a second communication unit of transport channel / information of the broadcast / multicast service; or configuration parameters of a second communication unit of a broadcast / multicast service radio bearer, wherein the configuration parameters of a second communication unit of control channel / information of the broadcast / multicast service comprise at least one of the following: a repetition period of broadcast / multicast control channel / information; an offset of broadcast / multicast control channel / information; a start slot of broadcast / multicast control channel / information; a duration of broadcast / multicast control channel / information; a modification period of broadcast / multicast control channel / information; or a frequency domain bandwidth part identifier of broadcast / multicast control channel / information; the configuration parameters of a second communication unit of transport channel / information of the broadcast / multicast service comprise scheduling configuration information of broadcast / multicast transport channel / information, wherein the scheduling configuration information of broadcast / multicast transport channel / information comprises at least one of the following: a duration timer of the broadcast / multicast transport channel / information; a timer related to discontinuous reception (DRX) of the broadcast / multicast transport channel / information; a scheduling period of the broadcast / multicast transport channel / information; a scheduling offset of the broadcast / multicast transport channel / information; or a frequency domain bandwidth part identifier of the broadcast / multicast transport channel / information; and the configuration parameters of a second communication unit of a broadcast / multicast service radio bearer comprise at least one of the following: a sequence number length of an RLC layer; or a reassembly timer.
21. The method of claim 16, wherein in a case where the third information comprises the broadcast / multicast service release request message, the third information comprises: a first interface identifier assigned by the first communication unit on a communication interface between the first communication unit and the second communication unit for a broadcast / multicast service; a second interface identifier assigned by the second communication unit on a communication interface between the first communication unit and the second communication unit for a broadcast / multicast service; and a reason for releasing a broadcast / multicast service.
22. The method of claim 15, wherein the fourth information comprises at least one of the following: a broadcast / multicast service identifier used to identify a broadcast / multicast service; a first interface identifier assigned by the first communication unit on a communication interface between the first communication unit and the second communication unit for a broadcast / multicast service; a second interface identifier assigned by the second communication unit on a communication interface between the first communication unit and the second communication unit for a broadcast / multicast service; at least one service area identifier supporting a broadcast / multicast service; cell identifier information of at least one cell which has a modified or released broadcast / multicast service; or information of successfully modified or released broadcast / multicast service radio bearer.
23. A broadcast / multicast service management method, comprising: receiving third information sent by a second communication unit, wherein the third information is used to instruct a first communication unit to execute an operation related to broadcast / multicast service management; and sending fourth information to the second communication unit, wherein the fourth information is used to indicate an execution result of the operation related to broadcast / multicast service management to the second communication unit.
24. A broadcast / multicast service management apparatus, comprising: a first sending module configured to send first information to a second communication unit, wherein the first information is used to instruct the second communication unit to execute an operation related to broadcast / multicast service management; and a first reception module configured to receive second information sent by the second communication unit, wherein the second information is used to indicate an execution result of the operation related to broadcast / multicast service management to a first communication unit.
25. A broadcast / multicast service management apparatus, comprising: a second reception module configured to receive first information sent by a first communication unit, wherein the first information is used to instruct a second communication unit to execute an operation related to broadcast / multicast service management; and a second sending module configured to send second information to the first communication unit, wherein the second information is used to indicate an execution result of the operation related to broadcast / multicast service management to the first communication unit.
26. A broadcast / multicast service management apparatus, comprising: a third sending module configured to send third information to a first communication unit, wherein the third information is used to instruct the first communication unit to execute an operation related to broadcast / multicast service management; and a third reception module configured to receive fourth information sent by the first communication unit, wherein the fourth information is used to indicate an execution result of the operation related to broadcast / multicast service management to a second communication unit.
27. A broadcast / multicast service management apparatus, comprising: a fourth reception module configured to receive third information sent by a second communication unit, wherein the third information is used to instruct a first communication unit to execute an operation related to broadcast / multicast service management; and a fourth sending module configured to send fourth information to the second communication unit, wherein the fourth information is used to indicate an execution result of the operation related to broadcast / multicast service management to the second communication unit.
28. An electronic device, comprising: at least one processor; and a memory configured to store at least one program, wherein executed by the at least one processor, the at least one program causes the at least one processor to implement the method of any one of claims 1 to 23.
29. A storage medium storing a computer program which, when executed by a processor, implements the method of any one of claims 1 to 23.
