Method, apparatus, storage medium and electronic device for transmitting multicast broadcast information

Abstract

The disclosure provides a multicast broadcast information transmission method and device, a storage medium and an electronic device. The method comprises the following steps: sending first multicast broadcast information containing multicast broadcast service area configuration information to a first network element; or receiving second multicast broadcast information containing multicast broadcast service area configuration information from the first network element. Through the disclosure, the problem of configuring the service area of multicast broadcast in the related art is solved.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the field of communications, and in particular, to a multicast broadcast information transmission method and apparatus, a storage medium, and an electronic device. BACKGROUND

[0002] With the continuous development of 5G (5th generation mobile networks), 5G solutions for various application scenarios are accelerating the completion. The multicast broadcast service scenario is a traditional service scenario to meet the needs of most users for the same service.

[0003] Currently, the 5G-related technologies discussed and standardized in the industry are mainly about the unicast service scenario, that is, the PTP (Point to Point) service mode. The standardization discussion of the PTM (Point to multipoint) service mode has not yet started. In addition, with the rapid growth of the number of users and the multi-dimensionality of application scenarios, the point-to-multipoint service mode will inevitably become one of the indispensable service modes.

[0004] Therefore, how to reasonably and effectively implement the multicast broadcast service under the technical framework of 5G-NR (New Radio) is an urgent problem to be discussed and solved.

[0005] For the problem of how to configure the service area of multicast broadcast in the related art, no effective solution has been proposed. SUMMARY

[0006] Embodiments of the present disclosure provide a multicast broadcast information transmission method and apparatus, a storage medium, and an electronic device to at least solve the problem of configuring the service area of multicast broadcast in the related art.

[0007] According to one embodiment of the present disclosure, a multicast broadcast information transmission method is provided, comprising: sending first multicast broadcast information containing multicast broadcast service area configuration information to a first network element; or receiving second multicast broadcast information containing multicast broadcast service area configuration information from the first network element.

[0008] According to another embodiment of the present disclosure, a multicast broadcast information transmission method is also provided, comprising: sending fourth multicast broadcast information containing multicast broadcast service area configuration information to a distributed unit DU; and / or receiving fifth multicast broadcast information containing multicast broadcast service area configuration information from the distributed unit DU.

[0009] According to another embodiment of the present disclosure, a transmission apparatus of multicast broadcast information is provided, comprising: a first sending module configured to send first multicast broadcast information containing multicast broadcast service area configuration information to a first network element; or a first receiving module configured to receive second multicast broadcast information containing multicast broadcast service area configuration information from the first network element.

[0010] According to another embodiment of the present disclosure, a transmission apparatus of multicast broadcast information is provided, comprising: a second sending module configured to send third multicast broadcast information containing multicast broadcast service area configuration information to a distributed unit (DU); and / or a second receiving module configured to receive fourth multicast broadcast information containing multicast broadcast service area configuration information from the distributed unit (DU).

[0011] According to another embodiment of the present disclosure, a computer readable storage medium is provided, wherein the computer readable storage medium stores a computer program, and the computer program is configured to execute the steps in any of the method embodiments when running.

[0012] According to another embodiment of the present disclosure, an electronic device is provided, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to execute the steps in any of the method embodiments.

[0013] According to the present disclosure, the configuration of the service area of multicast broadcast is achieved by sending first multicast broadcast information containing multicast broadcast service area configuration information to a first network element or receiving second multicast broadcast information containing multicast broadcast service area configuration information from the first network element, that is, the way how to configure the multicast broadcast service area is explicitly proposed, thereby solving the problem of configuring the service area of multicast broadcast in the related art. BRIEF DESCRIPTION OF DRAWINGS

[0014] Figure 1 is a service area schematic diagram according to an embodiment of the present disclosure;

[0015] Figure 2 is a transmission method schematic diagram of multicast broadcast information according to an embodiment of the present disclosure;

[0016] Figure 3 is an interaction flowchart of a base station and a MCE according to an embodiment of the present disclosure;

[0017] Figure 4 is an interaction flowchart of a MCE and an AMF according to an embodiment of the present disclosure;

[0018] Figure 5is a NGC initiated multicast / broadcast session establishment flowchart according to an embodiment of the present disclosure;

[0019] Figure 6 is a multicast / broadcast session handling flowchart according to an embodiment of the present disclosure;

[0020] Figure 7 is another multicast / broadcast information transmission method schematic diagram according to an embodiment of the present disclosure;

[0021] Figure 8 is a multicast / broadcast service area configuration schematic diagram according to an embodiment of the present disclosure;

[0022] Figure 9 is another multicast / broadcast service area configuration schematic diagram according to an embodiment of the present disclosure;

[0023] Figure 10 is a CU and DU interaction flowchart according to an embodiment of the present disclosure;

[0024] Figure 11 is a structure block diagram of a multicast / broadcast information transmission device according to an embodiment of the present disclosure;

[0025] Figure 12 is another structure block diagram of a multicast / broadcast information transmission device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0026] Hereinafter, the present disclosure will be described in detail with reference to the accompanying drawings and in conjunction with embodiments.

[0027] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily describe a specific order or sequence.

[0028] With the rise of multicast broadcast video services, public safety groupcast communication, and vehicle-to-everything services, the network needs to support flexible dynamic resource allocation between unicast and groupcast, and support standalone deployment of groupcast / broadcast networks. A flexible groupcast broadcast service enables the 5G system to efficiently support such services.

[0029] For broadcast / multicast service, the broadcast area of traditional MBMS (Multimedia Broadcast and Multicast Service) service is SAI (Service Area) which is composed of multiple cells, which can be nationwide or within a city or region. In different regions, the same MBMS service (identified by TMGI or other identifiers available to identify MBMS service or MBMS session) can broadcast the same or different content. In LTE (Long-Term Evolution), for the same MBMS service, if different broadcast / multicast content is sent in disjoint regions, an MBMS session corresponding to different flow id (flow identifier) needs to be established. For MBMS broadcast service, the corresponding service area can be determined semi-statically according to the characteristics of the service when the network is deployed, and the corresponding SAI is configured for the related cells.

[0030] For some multicast communications, such as public safety and V2X (intelligent networked automobile technology) multicast communications, the service area is related to the location of the group members (group members) who join the multicast group. Considering that the group members may move, it means that the service area corresponding to the multicast communication is also constantly changing, and the list of cells included in the corresponding service area is also constantly changing. For such services, it is difficult to semi-statically configure the service area corresponding to the multicast service when the network is deployed, and only dynamic adjustment according to the geographical location of the group members can be made.

[0031] In 5G NR V2X, SA2 defines a range value for PC5 V2X communication in groupcast mode. For receiving UEs that are not within the range specified range, only best effort communication needs to be guaranteed. For receiving UEs within the range specified range, PC5 QoS (Quality of Service) parameter requirements need to be guaranteed. For V2X communication transmitted through NR Uu multicast, there may be similar range-related QoS requirements from the application, i.e. not all members of the group member are required to guarantee to obtain the multicast information, only the group member UEs within the range around the message source UE can obtain the corresponding multicast information.

[0032] For broadcast V2X communication, it is generally only necessary to ensure that UEs within a few hundred meters of the UE transmitting the V2X message can receive it, and it is not meaningful for UEs further away to receive the information, so the concept of transmission range is also meaningful for V2X message transmission based on NR Uu broadcast.

[0033] For example, Figure 1 For example, Figure 1 is a service area diagram according to an embodiment of the disclosure, wherein the broadcast range of a certain V2X message is affected by the geographical location of the transmitting UE, the broadcast range requirement, and the cell deployment and cell coverage, specifically:

[0034] For a V2X transmitting UE from cell 10, the broadcast range of its V2X message covers SAI1: cell{10, 5, 7, 8, 12, 13, 15};

[0035] For a V2X transmitting UE from cell 5, the broadcast range of its V2X message covers SAI2: cell{5, 1, 2, 3, 7, 8, 10};

[0036] For a V2X transmitting UE from cell 7, the broadcast range of its V2X message covers SAI3: cell{7, 2, 5, 6, 9, 10, 12};

[0037] For a V2X transmitting UE from cell 8, the broadcast range of its V2X message covers SAI4: cell{8, 3, 4, 5, 10, 11, 13};

[0038] For a V2X transmitting UE from cell 12, the broadcast range of its V2X message covers SAI5: cell{12, 7, 9, 10, 14, 15, 18};

[0039] For a V2X transmitting UE from cell 13, the broadcast range of its V2X message covers SAI6: cell{13, 8, 10, 11, 15, 16, 17};

[0040] For a V2X transmitting UE from cell 15, the broadcast range of its V2X message covers SAI7: cell{15, 10, 12, 13, 17, 18, 19};

[0041] According to the above, for the V2X messages sent by the UEs from cell 10 and cell 5, the cells whose broadcast coverage ranges have overlap, such as cell {5, 10, 7, 8}, are overlapped. This means that the two service areas are overlapped. From the perspective of a single cell, taking cell 10 as an example, it can belong to SAI1, SAI2, SAI3, SAI4, SAI5, SAI6, and SAI7.

[0042] The following describes how to solve the problem of how to configure the multicast broadcast server area in the related art by combining the embodiments in the disclosure:

[0043] In an exemplary embodiment, a method for transmitting multicast broadcast information is provided, as shown in the following: Figure 2 The method comprises the following steps:

[0044] S202, sending first multicast broadcast information containing multicast broadcast service area configuration information to a first network element, or receiving second multicast broadcast information containing multicast broadcast service area configuration information from the first network element.

[0045] The embodiments of the present application can run in a communication system including a base station and a core network element. The 5G base station gNB can perform the above operations. The first network element mentioned above can be a multicast broadcast control unit MCE or an access and mobility management function AMF or other multicast broadcast control network elements. The corresponding SAI related information can be configured by the operation maintenance management OAM before the first multicast broadcast information is sent to the first network element.

[0046] Through the disclosure, the configuration of the service area of the multicast broadcast is realized by sending the first multicast broadcast information containing the multicast broadcast service area configuration information to the first network element or receiving the second multicast broadcast information containing the multicast broadcast service area configuration information from the first network element, that is, the way of how to configure the multicast broadcast service area is explicitly proposed, thereby solving the problem of configuring the service area of the multicast broadcast in the related art.

[0047] In an example embodiment, receiving the second multicast broadcast information including the multicast broadcast service area configuration information from the first network element comprises receiving a multicast broadcast session setup request message from the first network element, wherein the second multicast broadcast information is included in the multicast broadcast session setup request message. In this embodiment, the gNB can receive the second multicast broadcast information from the MCE or the AMF or other multicast broadcast control network element. Before the gNB receives the second multicast broadcast information from the MCE, the MCE can first obtain the relevant information sent by the AMF, and then send the second multicast broadcast information to the gNB. In this embodiment, the purpose of sending the second multicast broadcast information to the gNB can be achieved by the way of sending information from the BMSC to the multicast / broadcast GW, from the multicast / broadcast GW to the AMF, from the AMF to the MCE, and from the MCE to the gNB. The purpose of sending the second multicast broadcast information to the gNB can also be achieved by the way of sending information from the BMSC to the multicast / broadcast GW, from the multicast / broadcast GW to the AMF, and from the AMF to the gNB.

[0048] In an example embodiment, the multicast broadcast session setup request message includes at least one of the following information: a multicast broadcast service identity, a multicast broadcast session identity, one or more multicast broadcast service areas, one or more multicast broadcast cell lists, and one or more user equipment (UE) lists.

[0049] In an example embodiment, the multicast broadcast session setup request message includes one or more downlink user plane tunnel (DL GTP-U tunnel) configuration information, wherein the DL GTP-U tunnel configuration information includes an Internet Protocol (IP) multicast address and a tunnel endpoint identity (TEID).

[0050] In an example embodiment, in the case of configuring different multicast broadcast service identities for different multicast broadcast service areas, different user plane tunnels for different service areas, or configuring the same multicast broadcast service identity for different multicast broadcast service areas, different service area identities, and different user plane tunnels, the multicast broadcast session setup request message includes multiple DL GTP-U tunnel configuration information; or in the case of configuring the same multicast broadcast service identity for different multicast broadcast service areas, different service area identities, and the same user plane tunnel, the multicast broadcast session setup request message includes one DL GTP-U tunnel configuration information.

[0051] In an exemplary embodiment, the method further comprises: sending a multicast broadcast session setup response message to the first network element, wherein the multicast broadcast session setup response message comprises at least one of the following: one or more multicast broadcast session identities, a multicast broadcast service identity, a service area identity, a multicast broadcast cell list, a UE list, user plane tunnel GTP-U tunnel configuration information, wherein the GTP-U tunnel configuration information comprises an Internet Protocol, IP, address and a Tunnel Endpoint Identifier, TEID.

[0052] In an exemplary embodiment, a GTP-U subheader of a data packet transmitted through a user plane tunnel carries a multicast groupcast service area identity.

[0053] In an exemplary embodiment, receiving the second multicast broadcast information comprising multicast broadcast service area configuration information from the first network element comprises: receiving a multicast broadcast session update message from the first network element, wherein the second multicast broadcast information is comprised in the multicast broadcast session update message; wherein the second multicast broadcast information comprises at least one of the following: a multicast broadcast service identity, a multicast broadcast session identity, an updated multicast broadcast service area, an updated multicast broadcast cell list, an updated UE list, updated downlink user plane tunnel, DL GTP-U tunnel configuration information, wherein the DL GTP-U tunnel configuration information comprises an Internet Protocol, IP, multicast address and a Tunnel Endpoint Identifier, TEID.

[0054] In an exemplary embodiment, the updated multicast broadcast service area comprises added and / or released multicast broadcast service area identities.

[0055] In an exemplary embodiment, the updated multicast broadcast cell list comprises new Radio Cell Global Identity, NCGI, information of added and / or released cells.

[0056] In an exemplary embodiment, the updated UE list comprises added and / or released UE identity information, wherein the UE identity comprises a Cell Radio Network Temporary Identity, C-RNTI, a S-Temporary Mobile Subscriber Identity, S-TMSI, an NG UE APID, or other information used to identify a UE.

[0057] In an exemplary embodiment, one or more multicast broadcast service areas comprised in the multicast broadcast service area list comprise at least one of the following: a broadcast groupcast range, whether located in a Quality of Service, QoS, range, QoS information, reliability requirement, rate requirement, retransmission indication, Hybrid Automatic Repeat Request, HARQ, feedback indication.

[0058] In an example embodiment, in the case that the first network element comprises the MCE, after the first multicast broadcast information is sent to the MCE, the method further comprises at least one of the following: sending, by the MCE, third multicast broadcast information comprising multicast broadcast service area configuration information to the AMF based on the first multicast broadcast information. In this embodiment, the gNB can send the relevant broadcast service area configuration information to the AMF through the MCE, i.e., the MCE sends the relevant broadcast service area configuration information received from the gNB to the AMF.

[0059] In an example embodiment, in the case that the first network element comprises the MCE, after the first multicast broadcast information is sent to the MCE, the method further comprises at least one of the following: sending, by the MCE, third multicast broadcast information comprising multicast broadcast service area configuration information to the AMF based on the first multicast broadcast information. In this embodiment, the gNB can send the relevant broadcast service area configuration information to the AMF through the MCE, i.e., the MCE sends the relevant broadcast service area configuration information received from the gNB to the AMF.

[0060] In an example embodiment, in the case that the first network element comprises the MCE, after the first multicast broadcast information is sent to the MCE, the method further comprises at least one of the following: sending, by the MCE, third multicast broadcast information comprising multicast broadcast service area configuration information to the AMF based on the first multicast broadcast information. In this embodiment, the gNB can send the relevant broadcast service area configuration information to the AMF through the MCE, i.e., the MCE sends the relevant broadcast service area configuration information received from the gNB to the AMF.

[0061] In an example embodiment, the third multicast broadcast information comprises at least one of the following: MCE identifier, MCE name, multicast broadcast service identifier, one or more multicast broadcast service area identifiers, one or more cell identifier lists, multicast broadcast service area identifier list corresponding to each cell, and UE list.

[0062] In an example embodiment, in the case that the first network element comprises the MCE, after the first multicast broadcast information is sent to the MCE, the method further comprises at least one of the following: sending, by the MCE, third multicast broadcast information comprising multicast broadcast service area configuration information to the AMF based on the first multicast broadcast information. In this embodiment, the gNB can send the relevant broadcast service area configuration information to the AMF through the MCE, i.e., the MCE sends the relevant broadcast service area configuration information received from the gNB to the AMF.

[0063] The disclosure will be described in detail in the following specific embodiments:

[0064] The service area of the multicast broadcast can consider the following cases:

[0065] Scenario 1: For broadcast service such as video, the corresponding service area can be determined semi-statically according to the characteristics of the service at the time of network deployment, and the corresponding SAI is pre-configured for the related cells / base stations. For a certain SAI, it is composed of multiple cells, which can be nationwide, or city or regional range, or different broadcast contents corresponding to the same multicast / broadcast service in non-intersecting areas.

[0066] Scenario 2: For V2X type broadcast communication, if considering localized broadcast range, multiple SAIs can be semi-statically configured for each receiving cell supporting the service for a certain multicast / broadcast service, respectively corresponding to the broadcast range of the sending UE of the sending cell sending V2X message. The broadcast areas corresponding to these SAIs may have intersecting cells.

[0067] Scenario 3: For public safety and V2X multicast communication, the service area is determined according to the location of the group members joining the multicast communication group. The service area corresponds to a group cell list. The cell list of the service area will change with the location of the group members.

[0068] Scenario 4: For V2X multicast communication, if considering transmission range configuration, a range corresponding to service area 2 (SAI2) and cell list can be further determined according to the location of the UE sending the multicast message within the entire service area 1 (SAI1) corresponding to the cell list determined by the group members. The multicast transmission in the SAI2 area meets higher QoS requirements, such as supporting HARQ (Hybrid Automatic Repeat Request) feedback to meet reliability requirements. Embodiment 1

[0070] For Scenario 1, each cell can be pre-configured by OAM with its corresponding SAI related information (corresponding to the multicast broadcast service area configuration information described above, and corresponding to the multicast broadcast related information described below), and then the base station informs the MCE or AMF and other multicast broadcast control network elements of the corresponding SAI related information. Specifically, the following information interaction can be included:

[0071] The base station sends multicast / broadcast related information to the MCE or other multicast / broadcast control network element, which contains at least one of the following information: gNB ID, gNB Name, cell NCGI list, and the multicast / broadcast service area list corresponding to each cell. Each service area entry in the multicast / broadcast service area list contains multicast / broadcast service area identifier and / or multicast / broadcast service identifier information. The multicast / broadcast service identifier can identify a multicast / broadcast service or multicast / broadcast bearer service through TMGI or other identifier information. The base station can use the interface-Setup, RAN configuration update message, or multicast / broadcast configuration update information to establish / modify / release the configuration of the multicast / broadcast service area. The interface corresponds to the interface between the base station and the MCE.

[0072] After receiving the above information, the MCE can send a confirmation / response message to the base station. Subsequently, the MCE can determine which service areas the base station belongs to according to the multicast / broadcast related information sent by the base station, and decide whether to initiate the establishment of a corresponding multicast / broadcast session with the base station.

[0073] The base station can also send the above multicast / broadcast related information to the AMF. Similarly, the base station can use the NG-Setup, RAN configuration update message, or the multicast / broadcast configuration update information to establish / modify / release the configuration of the multicast / broadcast service area. After receiving the above multicast / broadcast related information, the AMF can send a confirmation / response message to the base station. Subsequently, the AMF can determine whether to initiate the establishment of the corresponding multicast / broadcast session with the base station according to the multicast / broadcast information sent by the base station to determine which service area the base station belongs to. The interaction process between the base station and the MCE can be seen in the following figure: Figure 3 .

[0074] The MCE or other multicast / broadcast control network element can send the multicast / broadcast related information to the AMF after receiving the multicast / broadcast related information. For example, the MCE sends the multicast / broadcast related information, which contains at least one of the following information: MCE ID, MCE Name, and the multicast / broadcast service area list supported by the MCE. Each service area entry in the multicast / broadcast service area list contains the multicast / broadcast service area identifier and / or the multicast / broadcast service identification information. The multicast / broadcast service identification can identify a multicast / broadcast service or a multicast / broadcast bearer service through the TMGI or other identification information. The MCE or other multicast / broadcast control network element can use the interface-Setup or the multicast / broadcast configuration update information to establish / modify / release the configuration of the multicast / broadcast service area. The interface corresponds to the interface between the MCE or other multicast / broadcast control network element and the AMF.

[0075] After the AMF receives the above multicast / broadcast related information, the AMF can send a confirmation / response message to the MCE or other multicast / broadcast control network element. The subsequent AMF can determine which service areas the MCE or other multicast / broadcast control network element belongs to according to the broadcast / multicast information sent by the MCE or other multicast / broadcast control network element, and decide whether to initiate the establishment of the corresponding multicast / broadcast session with the MCE or other multicast / broadcast control network element. The interaction process between the MCE and the AMF can be seen in the following figure: Figure 4 . Specific embodiment two

[0077] For Scenario 3, it can be considered to transmit the corresponding multicast / broadcast service area information in the multicast / broadcast session establishment process.

[0078] Specifically, the following information transmission methods can be considered during the establishment of the multicast / broadcast session: transmitted by the BMSC to the multicast / broadcast GW, the multicast / broadcast GW to the AMF, the AMF to the MCE, the MCE to the gNB, or transmitted by the BMSC to the multicast / broadcast GW, the multicast / broadcast GW to the AMF, the AMF to the gNB in the multicast / broadcast session establishment request message. The multicast / broadcast session establishment request message can contain multicast / broadcast related information. The multicast / broadcast related information can contain at least one of the following information: multicast / broadcast service identification information, multicast / broadcast session id, multicast / broadcast service area, multicast / broadcast cell list. The multicast / broadcast service identification can identify a multicast / broadcast service or a multicast / broadcast bearer service through TMGI or other identification information, and the multicast / broadcast cell list corresponds to the NCGI list, that is, the multicast / broadcast cell list can be represented by the NCGI list. Figure 5The flow of sending multicast / broadcast session establishment request message containing multicast / broadcast related information from NGC (AMF) to MCE and from MCE to gNB is given.

[0079] Considering the multicast / broadcast service areas that can have overlap, the multicast / broadcast session establishment request message can contain multiple multicast / broadcast service area lists and corresponding multicast / broadcast cell lists.

[0080] After receiving the multicast / broadcast related information, the gNB can send the multicast / broadcast configuration through broadcast or dedicated signaling on the Uu interface. Specifically, the gNB multicasts the multicast / broadcast configuration in the multicast / broadcast cells corresponding to the multicast / broadcast service areas associated with the multicast / broadcast session. UEs that are served by or camped on these cells and are interested in the multicast / broadcast session / service can accordingly establish multicast / broadcast bearers and receive multicast / broadcast data corresponding to these multicast / broadcast sessions.

[0081] Considering that the multicast / broadcast service area is dynamically changed with the location of the group members, the multicast / broadcast service area corresponding to the multicast / broadcast session needs to be updated accordingly. The following information sending mode can be considered: the multicast / broadcast session update message sent by the BMSC to the multicast / broadcast GW, the multicast / broadcast GW to the AMF, the AMF to the MCE, the MCE to the gNB, or the multicast / broadcast session update message sent by the BMSC to the multicast / broadcast GW, the multicast / broadcast GW to the AMF, the AMF to the gNB, which can contain the updated multicast / broadcast service area and / or multicast / broadcast cell list. Specifically, the updated multicast / broadcast service area information includes the multicast / broadcast service area identifier added or released. The updated multicast / broadcast cell list includes the NCGI information added or released.

[0082] For the base station / cell that is no longer within the multicast / broadcast service area, the following information sending mode can be considered: the multicast / broadcast session stop message sent by the BMSC to the multicast / broadcast GW, the multicast / broadcast GW to the AMF, the AMF to the MCE, the MCE to the gNB, or the multicast / broadcast session stop message sent by the BMSC to the multicast / broadcast GW, the multicast / broadcast GW to the AMF, the AMF to the gNB, which ends the multicast / broadcast session. Specific embodiment three

[0084] For Scenario 2 and 4, the multicast / broadcast service area that may overlap needs to be considered. For this case, the following possible processing modes can be considered:

[0085] Way one: for the same multicast / broadcast service, different multicast / broadcast service identifiers (or called TMGI or other identifier for identifying multicast / broadcast service or bearer service) are configured for different multicast / broadcast service areas with overlap, as shown in (c) flow in Figure 6 .

[0086] A multicast / broadcast session is established between UPF / multicast / broadcast GW and gNB corresponding to different TMGI, and a GTP-U tunnel is established. This way greatly increases the configuration requirement of multicast / broadcast service identifier. For a base station, it means that multicast / broadcast sessions and GTP-U tunnels are established respectively for the overlap of multiple multicast / broadcast service areas corresponding to the same multicast / broadcast service.

[0087] Way two: for the same multicast / broadcast service, the same multicast / broadcast service identifier (or called TMGI or other identifier for identifying multicast / broadcast service or bearer service) is configured for different multicast / broadcast service areas with overlap, and different service area identifiers, corresponding to different multicast / broadcast data transmission GTP-U tunnels, as shown in (a) flow in Figure 6 . The multicast / broadcast service identifier and SAI jointly determine a multicast / broadcast session / GTP-U tunnel, that is, different multicast / broadcast sessions are established between UPF / multicast / broadcast GW and gNB, and different GTP-U tunnels are established.

[0088] This way requires the base station to establish multicast / broadcast session and corresponding GTP-U tunnel between the NGC and the multiple multicast / broadcast service areas corresponding to the same multicast / broadcast service of the overlap. Since these multicast / broadcast sessions and GTP-U tunnels correspond to the same multicast / broadcast service identifier, the gNB can assemble the data packets received from multiple GTP-U tunnels into a MAC PDU and send them on the Uu interface after receiving multicast / broadcast data from the NGC from these DL GTP-U tunnels.

[0089] For the above-mentioned way one and way two, from the signaling point of view, the multicast / broadcast session establishment / update request information sent from the AMF to the MCE, the MCE to the gNB, or the AMF to the gNB can contain corresponding DL GTP-U tunnel configuration information for different multicast / broadcast service identifiers and SAI combinations. The DL GTP-U tunnel information contains the following information: IP multicast address, TEID information. In addition, the multicast / broadcast session establishment / update response information sent by the gNB to the NGC can contain DL GTP-U tunnel configuration information for different multicast / broadcast service identifiers and SAI combinations. This way is suitable for the base station to transmit multicast / broadcast data in unicast mode with the NGC.

[0090] It should be noted that the multicast / broadcast session establishment / update response information sent or received by the gNB and the NGC can contain one or more multicast / broadcast session ids, multicast / broadcast service identifiers, SAI, and corresponding GTP-U tunnel configuration information.

[0091] Option 3: For the same multicast / broadcast service, configure the same multicast / broadcast service identity (or called TMGI or other identity used to identify multicast / broadcast service or bearer service) for different multicast / broadcast service areas with overlap, multiplex the same multicast / broadcast data transmission multicast / broadcast session / GTP-U tunnel, corresponding to Figure 6 Option (b) in the flow.

[0092] This option means that for the same multicast / broadcast service, no matter how many overlapping service areas, a multicast / broadcast session is established between the UPF / multicast / broadcast GW and the gNB related to the service area, and a GTP-U tunnel is established. Subsequent NGC (such as UPF or multicast / broadcast GW) when sending multicast / broadcast data, includes the service area information corresponding to the data packet in the user plane data packet header. Specifically, the SAI information corresponding to the data packet can be added in the GTP-U packet header. After receiving the information, the gNB determines which cells need to be transmitted according to the SAI indication to find the multicast / broadcast cell list corresponding to the SAI.

[0093] From the signaling perspective, one multicast / broadcast session and GTP-U tunnel can be used to transmit data packets corresponding to different multicast / broadcast service areas, which means that multiple multicast / broadcast service areas and corresponding multicast / broadcast cell lists can be included in the multicast / broadcast session establishment request / update messages transmitted between the gNB and the NGC. Specifically, the multicast / broadcast session establishment / update request information sent from the AMF to the MCE, the MCE to the gNB, or the AMF to the gNB includes at least one of the following information: multicast / broadcast session id, multicast / broadcast service identity, SAI list, multicast / broadcast cell list, and DL GTP-U tunnel information. The DL GTP-U tunnel information includes the following information: IP multicast address and TEID information. In addition, the multicast / broadcast session establishment / update response information sent by the gNB to the NGC can include DL GTP-U tunnel configuration information for different multicast / broadcast service identities and SAI combinations. This approach is suitable for the transmission of multicast / broadcast data between the base station and the NGC using unicast. Embodiment Four

[0095] For Scenario 4, the transmission of multicast data can reach the area of SAI1, but only the multicast transmission in the area of SAI2 needs to meet the QoS requirements, such as supporting HARQ feedback to meet the reliability requirements.

[0096] Specifically, at the multicast / broadcast session establishment, the following information sending manner can be considered: BMSC sends to multicast / broadcast GW, multicast / broadcast GW sends to AMF, AMF sends to MCE, MCE sends to gNB, or BMSC sends to multicast / broadcast GW, multicast / broadcast GW sends to AMF, AMF sends to gNB, or BMSC sends to multicast / broadcast GW, multicast / broadcast GW sends to AMF, AMF sends to gNB. The multicast / broadcast session establishment request message sent by multicast / broadcast GW, AMF, or gNB. The multicast / broadcast session establishment request message contains a multicast / broadcast service area list. For each multicast / broadcast service area contained in the multicast / broadcast service area list, at least one of the following information is contained: broadcast / groupcast range, whether within QoS range, QoS profile, reliability requirement (such as PER, etc.), rate requirement, retransmission indication, or HARQ feedback indication information. Embodiment five

[0098] For Scenario 1 and 2, semi-static multicast / broadcast service area configuration scenario, the AMF / MCE can also send multicast / broadcast related information to the gNB.

[0099] Specifically, the gNB receives multicast / broadcast related information from the AMF / MCE. The multicast / broadcast related information contains at least one of the following information: multicast / broadcast service identifier (or TMGI or other identifier used to identify multicast / broadcast service or bearer service), one or more multicast / broadcast service areas, one or more cell lists, and one or more UE lists (identified by S-TMSI, UE AP ID, C-RNTI, etc.). After receiving the UE list, the gNB only needs to send broadcast / multicast data to the UEs contained in the UE list.

[0100] The gNB can send a multicast / broadcast support indication to the AMF / MCE. The AMF uses the multicast / broadcast support indication to determine whether to establish a multicast / broadcast session with the gNB.

[0101] In an example embodiment, for the CU and DU separation scenario, another method of transmitting multicast broadcast information is also provided, as shown in Figure 7 includes the following steps:

[0102] S702, sending fourth multicast broadcast information containing multicast broadcast service area configuration information to the distributed unit DU; and / or, receiving fifth multicast broadcast information containing multicast broadcast service area configuration information from the distributed unit DU.

[0103] The above operations can be performed by the centralized unit CU, and the configuration of the multicast broadcast service area is realized through the interaction between the CU and the DU. In the above embodiment, the way how to configure the multicast broadcast service area is explicitly proposed, thereby solving the problem of configuring the multicast broadcast service area in the related art.

[0104] In an example embodiment, the fourth multicast broadcast information includes at least one of the following information: multicast broadcast service identifier, multicast broadcast session identifier, one or more multicast broadcast service area identifier information, one or more multicast broadcast cell list, one or more user equipment list, and user plane tunnel F1 GTP-U tunnel configuration information.

[0105] In an example embodiment, the F1 GTP-U tunnel configuration information includes: Internet Protocol IP multicast address and / TEID information.

[0106] In an example embodiment, for each multicast broadcast service area or multicast broadcast cell list or user equipment list included in the fourth multicast broadcast information, at least one of the following information is further included: broadcast multicast range, whether located in a quality of service QoS range, QoS configuration, reliability requirement, rate requirement, retransmission indication, and hybrid automatic repeat request HARQ feedback indication.

[0107] In an example embodiment, the fourth multicast broadcast information includes at least one of the following information: CU multicast broadcast F1AP ID, to-be-established signaling radio bearer SRB, to-be-established multicast bearer MRB list, and centralized unit CU to distributed unit DU information.

[0108] In an example embodiment, the to-be-established MRB list includes quality of service QoS configuration information of the MRB and / or QoS configuration information of the QoS flow.

[0109] In an example embodiment, the sending the fourth multicast broadcast information including multicast broadcast service area configuration information to the distributed unit DU comprises: sending the fourth multicast broadcast information to the DU through a first message; and the receiving the fifth multicast broadcast information including multicast broadcast service area configuration information from the distributed unit DU comprises: receiving the fifth multicast broadcast information sent by the DU through a second message; wherein, when the first message is a multicast broadcast context setup request message, the second message is a multicast broadcast context setup response message; when the first message is a multicast broadcast context modification request message, the second message is a multicast broadcast context modification response message; when the first message is a multicast broadcast context release request message, the second message is a multicast broadcast context release response message.

[0110] Or,

[0111] The receiving the fifth multicast broadcast information including multicast broadcast service area configuration information from the distributed unit DU comprises: receiving a multicast broadcast context modification request message from the DU; and obtaining the fifth multicast broadcast information included in the multicast broadcast context modification request message.

[0112] In an example embodiment, the fifth multicast broadcast information includes multicast broadcast user plane tunnel DL UP TNL information.

[0113] In an example embodiment, a GTP-U subheader of a data packet transmitted through the user plane tunnel carries multicast broadcast area identification.

[0114] In an example embodiment, the fifth multicast broadcast information includes at least one of the following information: CU multicast broadcast F1AP ID, DU multicast broadcast F1AP ID, multicast broadcast session identification, G-RNTI, multicast broadcast service identification, DU to CU RRC message, one or more multicast broadcast service area identification information, MRB setup list, MRB setup failure list, MTCH scheduling information, a list of supportable cells corresponding to a multicast broadcast session or a multicast broadcast service area, a list of non-supportable cells corresponding to a multicast broadcast session or a multicast broadcast service area, multicast broadcast transport channel scheduling related information, inactivity timer, persistence timer, scheduling period, scheduling offset.

[0115] In an example embodiment, the MRB setup list includes a first MRB ID, LCID, and multicast broadcast DL UP TNL information.

[0116] In an example embodiment, the MRB setup failure list includes a second MRB ID and a cause value.

[0117] In one example embodiment, the DU to CU RRC message includes configuration information of RLC, MAC and logical channel corresponding to the MRB.

[0118] In one example embodiment, the fifth multicast broadcast message further includes at least one of the following information: updated multicast broadcast service area information, updated MRB information, updated multicast broadcast cell list information, updated multicast broadcast user equipment list information, and updated user plane tunnel F1 GTP-U tunnel information.

[0119] The following illustrates the multicast broadcast area configuration in the CU / DU separation scenario with specific embodiments: Embodiment six

[0121] In the CU / DU separation scenario, there are multiple cells under each DU. For a certain multicast / broadcast service area, it is possible to contain cell1 under a certain DU, but not contain cell2 and cell3 under the DU. Therefore, the DU needs to obtain the cell list information corresponding to the multicast / broadcast service area, so as to facilitate the DU to perform admission control and data transmission.

[0122] Specifically, the CU sends multicast broadcast related information to the DU. The multicast broadcast related information contains multicast / broadcast session / bearer establishment / modification / release information. For multicast / broadcast session / bearer establishment / modification information, it can contain at least one of the following information: multicast / broadcast service identifier (also known as TMGI or other identifier for identifying multicast / broadcast service or bearer service), multicast / broadcast session id / MRB id, one or more multicast / broadcast service area identifiers, one or more multicast / broadcast cell list information, one or more UE list (which can be identified by C-RNTI or UE F1AP ID) information, and F1 GTP-U tunnel information.

[0123] The DL GTP-U tunnel information contains the following information: IP multicast address, TEID information. In addition, the DU sends the multicast / broadcast session setup / update response information to the CU, which can contain the DL F1 GTP-U tunnel configuration information. This method is suitable for the scenario where the CU and the DU use unicast to transmit multicast / broadcast data.

[0124] For the scenario where one F1 GTP-U tunnel is used for multicast / broadcast data of multiple different multicast / broadcast service areas, the F1-U data packet header sent by the CU to the DU should carry SAI information. After receiving the data packet, the DU can determine the corresponding cell list or UE list according to the SAI, and then send the data packet to the corresponding cell or UE.

[0125] Further, the multicast / broadcast related information sent by the CU to the DU corresponding to a certain service area can contain at least one of the following information: broadcast / multicast range, whether within QoS range, QoS profile, reliability requirement (such as PER, etc.), rate requirement, retransmission indication, or HARQ feedback, etc. Indication information corresponding to a certain multicast / broadcast service area, whether within range, whether QoS needs to be guaranteed, or whether HARQ feedback is needed, etc.

[0126] In the multicast / broadcast session setup / update response information sent by the DU to the CU, one or more multicast / broadcast session ids / multicast / broadcast bearer ids, and or service area identifiers, and or cell lists, and or UE list information that can be supported and cannot be supported can be contained.

[0127] For the semi-static multicast / broadcast service area configuration of the aforementioned Scenario 1 and Scenario 2, the corresponding SAI can also be configured by OAM for the DU. The DU sends each cell and the corresponding multicast / broadcast service area information to the CU through the F1 interface. Eighth Embodiment

[0129] In CU / DU separation scenario, after CU maps the QoS flow contained in multicast / broadcast session to MRB, it needs to establish corresponding F1 GTP-U tunnel with DU for multicast / broadcast data transmission. Specifically, the following MRB-based GTP-U tunnel establishment method can be considered:

[0130] non-overlapping multicast / broadcast service area:

[0131] If for a certain multicast / broadcast service identifier, if only non-overlapping multicast / broadcast service area is considered, the multicast / broadcast data corresponding to different multicast / broadcast service areas can be mapped to different one or more MRBs, and the corresponding GTP-U tunnel on F1 interface is established. After DU receives the data packet of the GTP-U tunnel corresponding to the MRB, it delivers the data packet to the corresponding cell according to the service area information associated with the GTP-U tunnel for Uu interface transmission.

[0132] Overlapping multicast / broadcast service area:

[0133] As Figure 8 mentioned above, for a certain multicast / broadcast service, assuming the service identifier is TMGI 1, there is overlapping multicast / broadcast service area. Among them, service area 1 corresponds to cells 1, 2, 3, and 4, and service area 2 corresponds to cells 3, 4, 5, and 6. Assuming that the data corresponding to service area 1 is P1, and the data corresponding to service area 2 is P2, cell 1 and cell 2 need to send P1 on the Uu interface, cell 3 and cell 4 need to send P1+P2 on the Uu interface, and cell 5 and cell 6 need to send P2 on the Uu interface.

[0134] If the multicast / broadcast data corresponding to different multicast / broadcast service areas are mapped to different MRBs, it means that two F1-U GTP-U tunnels need to be established between CU and DU. The multicast / broadcast data corresponding to MRB1 and MRB2 need to be sent from two F1-U GTP-U tunnels on cell3 and cell4 for TMGI1. That is, for the cells corresponding to two overlapping service areas of one TMGI, the DU needs to establish two logical channels for multicast / broadcast data transmission.

[0135] In which, the F1-U GTP tunnel establishment mode shown can also be considered Figure 9 The CU aggregates the multicast / broadcast data of service area1 and the multicast / broadcast data of service area2 to one MRB3, and establishes a special GTP-U tunnel on the F1 interface to transmit the multicast / broadcast data corresponding to TMGI1 to cell3 and cell4. This mode means that the CU combines the multicast / broadcast data of the overlapping service areas on the F1 interface, and then redefines non-overlapping service areas on the F1 interface and establishes corresponding MRBs and GTP-U tunnels. That is, F1-U tunnel1 for MRB1 corresponds to cell1 and cell2, F1-U tunnel2 for MRB2 corresponds to cell5 and cell6, and F1-U tunnel3 for MRB3 corresponds to cell3 and cell4. In this case, only one MRB and the corresponding logical channel need to be established on the UE side for one multicast / broadcast service.

[0136] In addition to the two methods mentioned above, an MRB and corresponding F1-U tunnel can be established on the F1 interface for a multicast / broadcast service identifier (or TMGI or other identifier used to identify multicast / broadcast services or bearer services). Unifying the PDCP SN numbering of multicast / broadcast data corresponding to different service areas will result in some cells only transmitting PDCP PDUs corresponding to a portion of the PDCP SNs, leading to inherent PDCP SN gaps in data transmission.

[0137] For the different service areas and GTP-U tunnel establishment methods mentioned above, it is necessary to consider designing the creation, modification, and release processes for multicast / broadcast related contexts between the CU and DU. Considering that the DU controls resource allocation, it is also necessary to consider having the DU initiate the release or modification of certain MRBs.

[0138] Taking a multicast / broadcast context setup request as an example, such as Figure 10 As shown, the information sent by the CU to the DU may include at least one of the following: CU multicast / broadcast F1AP ID, multicast / broadcast service identifier (or TMGI or other identifier used to identify multicast / broadcast service or bearer service), multicast / broadcast session ID, multicast / broadcast service area, multicast / broadcast cell list / UE list, SRB to be setup, MRB to be setupList, and CU to DU Information. The MRB to be setup list may contain the MRB's QoS profile and / or the QoS profile information of the QoS flow.

[0139] In addition, it is also possible to include multiple multicast / broadcast service areas and corresponding multicast / broadcast cell lists or UE lists in a single multicast / broadcast context setup request.

[0140] Further, a list of corresponding MRB to be setup can be included for each multicast / broadcast service area. If IP multicast is used for transmission of multicast / broadcast data corresponding to the MRB between the CU and multiple DUs, IP multicast address, IP source address, GTP DL TEID information can be further included in the TNL information included in the multicast / broadcast context setup request message. If IP multicast is not used, multicast / broadcast DL UP TNL info can be included in the multicast / broadcast context setup response message sent by the DU to the CU.

[0141] Specifically, the multicast / broadcast context setup response message can contain at least one of the following information: CU multicast / broadcast FlAP ID, DU multicast / broadcast FlAP ID, multicast / broadcast session id, G-RNTI, multicast / broadcast service identity (or called TMGI or other identity used to identify multicast / broadcast service or bearer service), DU to CU RRC Information, one or more multicast / broadcast service area identifier, MRB setup list, MRB failed to setup list. Among them, the MRB setup list contains MRB ID, LCID, multicast / broadcast DL UP TNLinfo (GTP-U tunnel transport layer address, GTP-TEID). The MRB failed to setup list contains MRB id and cause value. The DU to CU RRC Information can contain the related configuration of the RLC / MAC and logical channel corresponding to the MRB. In addition, the multicast / broadcast context setup response can also contain MTCH scheduling related information, such as inactivity timer, on duration timer, scheduling cycle, scheduling offset, etc.

[0142] In addition, the multicast / broadcast context setup response message can contain a list of cells that can support and / or a list of cells that cannot support corresponding to a certain MRB / multicast / broadcast session / multicast / broadcast service area. Among them, the cell information is identified using NCGI / PCI and other information.

[0143] It should be noted that in addition to the multicast / broadcast context setup request / response procedure, the CU and the DU need to interact with each other in the multicast / broadcast context modification procedure, which can be initiated by the DU or the CU. In addition, the CU can also initiate the multicast / broadcast context release procedure. In the multicast / broadcast context modification procedure initiated by the CU or the DU, the DU can send at least one of the following information to the CU or the CU to the DU: CU multicast / broadcast F1AP ID, DU multicast / broadcast F1AP ID, multicast / broadcast session id, G-RNTI, multicast / broadcast service identity (TMGI or other identity identifying multicast / broadcast service or bearer service), DU to CU RRC information, updated multicast / broadcast service area information, updated MRB information, updated multicast / broadcast cell list or UE list information, updated F1 GTP-U tunnel information, etc.

[0144] After the DU completes the multicast / broadcast bearer / multicast / broadcast session configuration, it can subsequently send the data packets received from the F1 GTP-U tunnel to the UE in a point-to-point or point-to-multipoint manner.

[0145] From the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be realized by means of software and the necessary general hardware platform, of course, it can also be realized by hardware, but in many cases the former is a better embodiment. Based on such understanding, the technical solutions of the disclosure can be embodied in the form of a software product in essence or in the form of a contribution to the prior art. The computer software product is stored in a storage medium (such as a ROM / RAM, a magnetic disk, or an optical disk), and includes a plurality of instructions for causing a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the method described in each embodiment of the disclosure.

[0146] A multicast broadcast information transmission apparatus is also provided in the embodiments, which is configured to implement the embodiments and preferred embodiments described above, and will not be described again. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

[0147] Figure 11 is a structural block diagram of a multicast broadcast information transmission apparatus according to an embodiment of the present disclosure, as shown in Figure 11 The apparatus comprises:

[0148] A first sending module 112 is configured to send first multicast broadcast information containing multicast broadcast service area configuration information to a first network element; or

[0149] A first receiving module 114 is configured to receive second multicast broadcast information containing multicast broadcast service area configuration information from the first network element.

[0150] In an exemplary embodiment, the first network element comprises a multicast broadcast control element (MCE) or an access and mobility management function (AMF).

[0151] In an exemplary embodiment, the first receiving module 114 can receive the second multicast broadcast information containing multicast broadcast service area configuration information from the first network element by receiving a multicast broadcast session establishment request message from the first network element, wherein the second multicast broadcast information is included in the multicast broadcast session establishment request message.

[0152] In an exemplary embodiment, the multicast broadcast session establishment request message comprises at least one of the following information: multicast broadcast service identification, multicast broadcast session identification, one or more multicast broadcast service areas, one or more multicast broadcast cell lists, and one or more user equipment (UE) lists.

[0153] In an exemplary embodiment, the multicast broadcast session establishment request message comprises one or more downlink user plane tunnel (DL GTP-U tunnel) configuration information, wherein the DL GTP-U tunnel configuration information comprises an Internet Protocol (IP) multicast address and a tunnel endpoint identification (TEID).

[0154] In an example embodiment, the multicast broadcast session setup request message includes one or more DL GTP-U tunnel configuration information in case that different multicast broadcast service identities are configured for different multicast broadcast service areas, different user plane tunnels are configured for different multicast broadcast service areas, or different multicast broadcast service identities are configured for different multicast broadcast service areas and different user plane tunnels are configured for different multicast broadcast service areas; or the multicast broadcast session setup request message includes one DL GTP-U tunnel configuration information in case that different multicast broadcast service identities are configured for different multicast broadcast service areas and same user plane tunnels are configured for different multicast broadcast service areas.

[0155] In an example embodiment, the multicast broadcast session setup request message further includes: multicast broadcast session identity, multicast broadcast service identity, service area identity list, multicast broadcast cell list in case that same multicast broadcast service identity is configured for different multicast broadcast service areas and same user plane tunnels are configured for different multicast broadcast service areas.

[0156] In an example embodiment, the apparatus is further configured to send a multicast broadcast session setup response message to the first network element, wherein the multicast broadcast session setup response message includes one or more of: multicast broadcast session identity, multicast broadcast service identity, service area identity, multicast broadcast cell list, UE list, and GTP-U tunnel configuration information, wherein the GTP-U tunnel configuration information includes IP address and TEID.

[0157] In an example embodiment, a GTP-U subheader of a data packet transmitted through a user plane tunnel carries a multicast broadcast service area identity.

[0158] In an example embodiment, the first receiving module 114 can receive the second multicast broadcast information including multicast broadcast service area configuration information from the first network element by receiving a multicast broadcast session update message from the first network element, wherein the second multicast broadcast information is included in the multicast broadcast session update message, and wherein the second multicast broadcast information includes one or more of: multicast broadcast service identity, multicast broadcast session identity, updated multicast broadcast service area, updated multicast broadcast cell list, updated UE list, and DL GTP-U tunnel configuration information, wherein the DL GTP-U tunnel configuration information includes IP multicast address and TEID.

[0159] In an exemplary embodiment, the updated multicast broadcast service area list comprises added and / or released multicast broadcast service area identities.

[0160] In an exemplary embodiment, the updated multicast broadcast cell list comprises added and / or released new radio cell global identity (NCGI) information of cells.

[0161] In an exemplary embodiment, the updated UE list comprises added and / or released UE identity information, wherein the UE identity comprises cell radio network temporary identity (C-RNTI), S-TMSI, NG UE APID, or other information used to identify a UE.

[0162] In an exemplary embodiment, one or more multicast broadcast service areas included in the multicast broadcast service area list comprises at least one of the following information: broadcast multicast range, whether located in a quality of service (QoS) range, QoS information, reliability requirement, rate requirement, retransmission indication, hybrid automatic repeat request (HARQ) feedback.

[0163] In an exemplary embodiment, when sending the first multicast broadcast information comprising multicast broadcast service area configuration information to the first network element, the first multicast broadcast information comprises at least one of the following information: base station identity, base station name, multicast broadcast service identity, one or more multicast broadcast service area identities, one or more cell identity lists, multicast broadcast service area identity lists corresponding to each cell, UE list.

[0164] In an exemplary embodiment, when sending the first multicast broadcast information comprising multicast broadcast service area configuration information to the first network element, the apparatus is further configured to: instruct the first network element to perform a first processing on the multicast broadcast service area configuration through the first message; wherein the first processing comprises at least one of the following: establishing, modifying, releasing. In this embodiment, the interface corresponds to an interface between the gNB and the first network element.

[0165] In an exemplary embodiment, when the first network element comprises the MCE, after sending the first multicast broadcast information to the MCE, the MCE is configured to perform the following operation: sending, by the MCE, third multicast broadcast information comprising multicast broadcast service area configuration information to the AMF based on the first multicast broadcast information.

[0166] In an exemplary embodiment, the third multicast broadcast information comprises at least one of the following information: MCE identity, MCE name, multicast broadcast service identity, one or more multicast broadcast service area identities, one or more cell identity lists, multicast broadcast service area identity lists corresponding to each cell, UE list.

[0167] In an example embodiment, after sending, by the MCE, the third multicast broadcast information containing the multicast broadcast service area configuration information to the AMF based on the first multicast broadcast information, the MCE is further configured to instruct the AMF to perform a third processing on the multicast broadcast service area configuration through a third message; wherein the third processing comprises at least one of: establishing, modifying, and releasing. In this embodiment, the interface corresponds to an interface between the MCE and the AMF.

[0168] Figure 12 is a structural block diagram of another multicast broadcast information transmission device according to an embodiment of the disclosure, as shown in Figure 12 the device comprises:

[0169] a second sending module 122, configured to send, to a distributed unit DU, third multicast broadcast information containing multicast broadcast service area configuration information; and / or,

[0170] a second receiving module 124, configured to receive, from the distributed unit DU, fourth multicast broadcast information containing multicast broadcast service area configuration information.

[0171] In an example embodiment, the fourth multicast broadcast information comprises at least one of: multicast broadcast service identity, multicast broadcast session identity, one or more multicast broadcast service area identity information, one or more multicast broadcast cell list, one or more user equipment list, and user plane tunnel F1 GTP-U tunnel configuration information.

[0172] In an example embodiment, the F1 GTP-U tunnel configuration information comprises: Internet Protocol IP multicast address and / TEID information.

[0173] In an example embodiment, for each multicast broadcast service area or multicast broadcast cell list or user equipment list included in the fourth multicast broadcast information, at least one of the following information is further included: broadcast multicast range, whether located in a quality of service QoS range, QoS configuration, reliability requirement, rate requirement, retransmission indication, and hybrid automatic repeat request HARQ feedback indication.

[0174] In an example embodiment, the fourth multicast broadcast information comprises at least one of: CU multicast broadcast F1AP ID, signaling radio bearer SRB to be established, multicast bearer MRB list to be established, and centralized unit CU to distributed unit DU information.

[0175] In an example embodiment, the MRB list to be established comprises quality of service (QoS) configuration information of the MRB and / or QoS configuration information of a QoS flow.

[0176] In an example embodiment, the second sending module 122 is configured to send the fourth multicast broadcast information comprising multicast broadcast service area configuration information to the distributed unit (DU) by sending the fourth multicast broadcast information to the DU via a first message, and the second receiving module 124 is configured to receive the fifth multicast broadcast information comprising multicast broadcast service area configuration information from the distributed unit (DU) by receiving the fifth multicast broadcast information sent by the DU via a second message, wherein when the first message is a multicast broadcast context setup request message, the second message is a multicast broadcast context setup response message; when the first message is a multicast broadcast context modification request message, the second message is a multicast broadcast context modification response message; when the first message is a multicast broadcast context release request message, the second message is a multicast broadcast context release response message.

[0177] Alternatively,

[0178] The second receiving module 124 is configured to receive the fifth multicast broadcast information comprising multicast broadcast service area configuration information from the distributed unit (DU) by receiving a multicast broadcast context modification request message from the DU, and obtaining the fifth multicast broadcast information included in the multicast broadcast context modification request message.

[0179] In an example embodiment, the fifth multicast broadcast information comprises multicast broadcast user plane tunnel (DL UP TNL) information.

[0180] In an example embodiment, a GTP-U subheader of a data packet transmitted via the user plane tunnel carries multicast broadcast area identification.

[0181] In an example embodiment, the fifth multicast broadcast information comprises at least one of the following: CU multicast broadcast F1AP ID, DU multicast broadcast F1AP ID, multicast broadcast session identification, G-RNTI, multicast broadcast service identification, DU-to-CU RRC message, one or more multicast broadcast service area identification information, MRB establishment list, MRB establishment failure list, MTCH scheduling information, list of supportable cells corresponding to a multicast broadcast session or a multicast broadcast service area, list of non-supportable cells corresponding to a multicast broadcast session or a multicast broadcast service area, multicast broadcast transport channel scheduling related information, inactivity timer, persistence timer, scheduling period, scheduling offset.

[0182] In an example embodiment, the MRB setup list includes a first MRB ID, LCID, and a multicast broadcast DL UP TNL message.

[0183] In an example embodiment, the MRB setup failure list includes a second MRB ID and a cause value.

[0184] In an example embodiment, the DU to CU RRC message includes configuration information of RLC, MAC, and logical channels corresponding to the MRB.

[0185] In an example embodiment, the fifth multicast broadcast message further includes at least one of the following information: updated multicast broadcast service area information, updated MRB information, updated multicast broadcast cell list information, updated multicast broadcast user equipment list information, and updated user plane tunnel F1 GTP-U tunnel information.

[0186] It should be noted that each of the above modules can be implemented by software or hardware, and for the latter, the following implementation manners can be used, but are not limited thereto: all the above modules are located in the same processor; or the above modules are located in different processors in any combination.

[0187] Embodiments of the present disclosure further provide a computer readable storage medium having a computer program stored therein, where the computer program is configured to execute the steps in any of the above method embodiments when running.

[0188] In the present embodiment, the above computer readable storage medium can include, but is not limited to, a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store computer programs.

[0189] Embodiments of the present disclosure further provide an electronic device including a memory having a computer program stored therein and a processor configured to execute the computer program to perform the steps in any of the above method embodiments.

[0190] The above electronic device can further include a transmission device connected to the processor and an input / output device connected to the processor.

[0191] The specific examples in the present embodiment can refer to the examples described in the above embodiments and optional implementation manners, which will not be described herein again.

[0192] It is apparent that those skilled in the art should understand that the modules or steps of the present disclosure described above can be realized by general computing devices, and they can be centralized on a single computing device or distributed on a network composed of multiple computing devices, and optionally, they can be realized by program codes executable by computing devices, so that they can be stored in storage devices and executed by computing devices, and in some cases, the steps shown or described can be executed in different orders, or they can be respectively manufactured into individual integrated circuit modules, or multiple modules or steps among them can be manufactured into a single integrated circuit module to be realized. Thus, the present disclosure is not limited to any particular combination of hardware and software.

[0193] The preferred embodiments of the present disclosure are described above, but the present disclosure is not limited to the above, and various modifications and changes can be made by those skilled in the art. Any modification, equivalent replacement, improvement, etc. within the principles of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A method for transmitting multicast broadcast information, characterized in that, include: Send a fourth multicast broadcast message containing multicast broadcast service area configuration information to the Distributed Unit (DU). The fourth multicast broadcast information includes a list of multicast radio bearers (MRBs) to be established and one or more multicast broadcast cell lists; and Receive a fifth multicast broadcast message containing multicast broadcast service area configuration information from the Distributed Unit (DU). The fifth multicast broadcast information includes multicast broadcast user plane (UP) transport network layer (TNL) information.

2. The method according to claim 1, characterized in that, The fourth and fifth multicast broadcast information also include at least one of the following: One or more multicast broadcast service area identification information, and one or more user equipment lists.

3. The method according to claim 1, characterized in that, The fourth multicast broadcast information also includes at least one of the following: The centralized unit (CU) multicast broadcast F1AP ID, the signaling radio bearer (SRB) to be established, a multicast broadcast service area identifier, a list of one or more user equipment (UE) devices, and information from the centralized unit (CU) to the distributed unit (DU).

4. The method according to claim 1, characterized in that, The MRB list to be established includes the QoS configuration information of the MRB and / or the QoS configuration information of the QoS flow.

5. The method according to claim 2, characterized in that, The GTP-U header of data packets transmitted through the user plane tunnel carries a multicast broadcast area identifier.

6. The method according to claim 1, characterized in that, The fifth multicast broadcast information also includes at least one of the following: One or more multicast broadcast service area identification information, cell list.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program is configured to perform the method described in any one of claims 1 to 6 when executed.

8. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to run the computer program to perform the method as described in any one of claims 1 to 6.

Images