Method and system for configuring multicast broadcast service, network device

Abstract

This application discloses a configuration method, system, and network device for multicast broadcast services. The method includes: a base station centralized entity control plane sending a first configuration request message to the base station centralized entity user plane, wherein the configuration information in the first configuration request message includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information; the base station centralized entity control plane receiving a first configuration response message sent by the base station centralized entity user plane, wherein the configuration information in the first configuration response message includes at least one of the following: QoS flow list, PDCP count value, and MRB ID. This application solves the technical problem that related communication protocols cannot meet the need for flexible scheduling of MBS services based on PDCP synchronization status and service requirements.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and more specifically, to a configuration method and system for multicast broadcast services, and network equipment. Background Technology

[0002] 3GPP Rel-17 introduced broadcast and multicast, through 5GS (5 th The Generation System (GRS), a fifth-generation mobile communication system, implements the general MBS (Multimedia Broadcast Service) and provides basic functions to support MBS services. The protocol supports two delivery modes: Delivery Mode 1, used only for multicast, supports services with higher QoS (Quality of Service) requirements, while Delivery Mode 2, used only for broadcast, focuses on services with lower QoS requirements.

[0003] Currently, gNB (the next generation Node B) can send MBS multicast data packets using two methods: PTP (Point-to-Point) and PTM (Point-to-Multipoint). In PTP, the gNB sends an independent copy of the MBS data packet to each UE (User Equipment); in PTM, the gNB delivers a single copy of the MBS data packet to a group of UEs. For cells with a large number of connected terminals, to ensure the QoS requirements of different services are met, the base station also needs to configure multicast services for terminals in the RRC (Radio Resource Control) disconnected state.

[0004] Furthermore, the introduction of the PDCP synchronization indicator is mainly used in the following two situations: First, cells typically follow the mapping rules from QoS flows to the MRB (MBS Control Channel), and the PDCP count is set according to the SN (Serial Number) code of the MBS QoS flow. When a terminal transitioning from connected state to inactive state receives the PDCP synchronization indicator from the base station, it can continue to apply the PDCP state variables from the connected state. Second, when a terminal moves to a neighboring cell, and the neighboring cell and the serving cell belong to the same RNA (RAN-based notification Area) providing the same service, and the PDCP synchronization status of the neighboring cell is consistent with that of the serving cell, the terminal after reselection or handover to the neighboring cell receives the PDCP synchronization indicator and can continue to apply the PDCP state variables of the original serving cell in the neighboring cell. However, in practical applications, it is difficult to determine whether the neighboring cell belongs to the same RNA as the serving cell. Even if they belong to the same RNA, due to clock errors and other reasons, it is difficult to guarantee PDCP synchronization between the source and target cells in the absence of deterministic network technology. Furthermore, when transmitting QoS streams in a base station separation architecture, the relevant protocol (TS37.483) does not map the QoS streams related to MBS services to the corresponding MRBs.

[0005] Considering that the network needs to configure PDCP synchronization for UEs and map MBS service-related QoS flows to the MRB, and that the user plane and control plane (E1 interface) of the base station separation architecture do not support MBS-related configuration, the current protocol has the following problems:

[0006] (1) In the absence of deterministic network technology, the PDCP of the source cell and the target cell may be asynchronous due to clock errors and other reasons. If the terminal receives a PDCP synchronization indication, it will assume that the PDCP of the source cell and the target cell has been synchronized and will still use the original PDCP count value. This will result in inconsistent service delays before and after the handover, which will seriously affect the user experience.

[0007] (2) During QoS flow transmission, the QoS flow related to MBS service is not mapped to the corresponding MRB in the base station separation architecture. The base station centralized entity control plane receives an error report from the base station centralized entity user plane, causing service failure.

[0008] Based on the above analysis of requirements and reasons, the current 3GPP Rel-18 protocol cannot meet the configuration requirements of MBS services. Therefore, a new standardization method needs to be designed to meet the needs of flexible scheduling based on PDCP synchronization status and service requirements when the network provides MBS broadcast or multicast services. Summary of the Invention

[0009] This application provides a configuration method, system, and network device for multicast broadcast services, which at least solves the technical problem that related communication protocols cannot meet the need for flexible scheduling of MBS services based on PDCP synchronization status and service requirements.

[0010] According to one aspect of the embodiments of this application, a configuration method for multicast broadcast service is provided, comprising: a base station centralized entity control plane sending a first configuration request message to the base station centralized entity user plane, wherein the configuration information in the first configuration request message includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRBID, MBS session ID, and MBS area identification information; the base station centralized entity control plane receiving a first configuration response message sent by the base station centralized entity user plane, wherein the configuration information in the first configuration response message includes at least one of the following: Quality of Service (QoS) flow list, PDCP count value, and MRB ID, wherein the QoS flow list includes QoS flow mapping indication information, and the QoS flow mapping indication information, for MBS, is used to map QoS flows to MRB.

[0011] Optionally, the PDCP synchronization indication information is used to indicate that the PDCP count value of the corresponding multicast session has been synchronized in the RAN-based notification area, wherein the cells in the RAN-based notification area follow the same QoS flow to MRB mapping rules and set the PDCP count value according to the sequence number of the MRB QoS flow.

[0012] Optionally, the PDCP synchronization time information is used to synchronize user data or data packets forwarded by the centralized entity user plane of the base station, and to configure the PDCP synchronization to a time point shared by the notification area based on the RAN.

[0013] Optionally, the PDCP count value is the initial RX_DELIV.

[0014] Optionally, RX_DELIV is initialized to indicate the initial value of RX_DELIV during PDCP window initialization, and RX_DELIV is initialized to the leftmost or first bit in the bit string. RX_DELIV is a state variable used within the PDCP entity to indicate the count value of the first PDCP service data unit that has not yet been delivered to the highest layer and is in a waiting-to-deliver state.

[0015] Optionally, the MBS session ID is used to associate MBS sessions that provide the same user data or multicast service data packets.

[0016] Optionally, the type of the first configuration request message includes: a broadcast bearer context establishment request message, a broadcast bearer context modification request message, a multicast bearer context establishment request message, and a multicast bearer context modification request message; the type of the first configuration response message includes: a broadcast bearer context establishment response message, a broadcast bearer context modification response message, a multicast bearer context establishment response message, a multicast bearer context modification request message, or a multicast bearer context modification request message.

[0017] Optionally, when the type of the first configuration request message is a multicast bearer context establishment request message, the base station centralized entity control requests the base station centralized entity user plane to set up MBS session resources for multicast MBS sessions, so as to establish MBS session resources for multicast MBS sessions in the base station centralized entity user plane.

[0018] Optionally, when the type of the first configuration request message is a multicast bearer context modification request message, the base station centralized entity control requests the base station centralized entity user plane to modify the MBS session resources used for the multicast MBS session.

[0019] Optionally, if the base station centralized entity user plane reports a multicast MRB establishment failure or an MBSQoS establishment failure, the base station centralized entity control plane receives a first configuration response message from the base station centralized entity user plane that carries at least a value indicating the establishment failure reason, and determines the reason for the establishment failure based on the establishment failure reason value in the first configuration response message.

[0020] According to another aspect of the embodiments of this application, a configuration method for multicast broadcast services is also provided, comprising: a base station centralized entity user plane receiving a first configuration request message sent by a base station centralized entity control plane, wherein the configuration information in the first configuration request message includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information; the base station centralized entity user plane sending a corresponding first configuration response message to the base station centralized entity control plane, wherein the configuration information in the first configuration response message includes at least one of the following: QoS flow list, PDCP count value, and MRB ID, wherein the QoS flow list includes QoS flow mapping indication information, and the QoS flow mapping indication information, for MBS, is used to map QoS flows to MRB.

[0021] Optionally, the base station centralized entity user plane configures PDCP based on the configuration information in the first configuration request message.

[0022] Optionally, the type of the first configuration request message includes: a broadcast bearer context establishment request message, a broadcast bearer context modification request message, a multicast bearer context establishment request message, and a multicast bearer context modification request message; the type of the first configuration response message includes: a broadcast bearer context establishment response message, a broadcast bearer context modification response message, a multicast bearer context establishment response message, a multicast bearer context modification request message, or a multicast bearer context modification request message.

[0023] Optionally, when the type of the first configuration request message is a multicast bearer context establishment request message, and the multicast bearer context establishment request message includes the identification information of the MBS area, the base station centrally stores the identification information of the MBS area in the user plane and establishes a shared user plane interface NG-U channel based on the identification information of the MBS area service area.

[0024] Optionally, the base station centralized physical user plane obtains data packets from the core network or server and feeds the data packets back to the terminal; if the PDCP synchronization time information is included in the first configuration request message, the base station centralized physical user plane will send the data packets to the terminal at the configured PDCP time point according to the PDCP synchronization time information.

[0025] According to another aspect of the embodiments of this application, a configuration method for multicast broadcast service is also provided, including: a terminal receiving configuration information sent by the centralized entity control plane of a base station through an RRC message, wherein the configuration information includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information.

[0026] Optionally, the terminal receives data packets sent by the base station's centralized entity user plane via RRC messages.

[0027] Optionally, if the configuration information received by the terminal contains a PDCP count value, the terminal will perform configuration according to the initialization RX_DELIV in the configuration information; if the configuration information received by the terminal contains PDCP synchronization time information, the terminal will receive data packets according to the configured time point.

[0028] Optionally, MRBID is used to identify the multicast MRB used by the terminal.

[0029] Optionally, the type of RRC message includes: multicast MCCH message, RRC reconfiguration message, or RRC release message. The multicast MCCH message is a message sent through the multicast MCCH logical channel, and includes at least one of the following: inactive PTM configuration information or inactive MCCH configuration information, wherein the inactive PTM configuration information is used to instruct the terminal to receive MBS messages in an inactive state. The RRC reconfiguration message includes at least: SDAP configuration information, and the SDAP configuration information is used to determine the mapping rules for QoS flows to MRBs, wherein the mapping rules include at least: at least one MBS QoS flow on the downlink is mapped to a single MRB. The RRC release message includes at least: inactive PTM configuration information.

[0030] Optionally, if the RRC release message does not include inactive PTM configuration information, the terminal stops monitoring the G-RNTI of at least one multicast session, wherein the G-RNTI is used to add interference to the PTM scheduling and transmission process of at least one MBS session.

[0031] Optionally, when the multicast PTM configuration information is updated and the terminal moves to a cell that provides MBS configuration MCCH / MTCH information for inactive terminals, the inactive terminal uses the multicast MRB configuration procedure to configure PDCP, RLC, MAC entity, and physical layer. The cell that provides MBS configuration MCCH / MTCH information for inactive terminals is the cell that provides System Information Block (SIB24) messages. When the PTM configuration information is updated via multicast MCCH messages or when the terminal moves to a cell where the PDCP count value of the corresponding multicast MRB is out of sync in the RAN-based notification area, the terminal performs modification of the multicast MRB or release / establishment of the multicast MRB.

[0032] Optionally, when a terminal transitions from connected state to inactive state within the same cell, the terminal continues to use the multicast MRB used in connected state; when a terminal transitions from active state to connected state within the same cell, the terminal releases the MRB configuration information in the RRC release message or multicast MCCH message, and performs incremental configuration based on the MRB configuration information stored in connected state.

[0033] According to another aspect of the embodiments of this application, a configuration system for multicast broadcast services is also provided. This system includes: a base station centralized entity control plane, a base station centralized entity user plane, and a terminal. The base station centralized entity control plane is used to send a first configuration request message to the base station centralized entity user plane, and the configuration information in the first configuration request message includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information; and to send the configuration information in the first configuration request message to the terminal via an RRC message. The base station centralized entity user plane is used to feed back a corresponding first configuration response message to the base station centralized entity control plane, and the configuration information in the first configuration response message includes at least one of the following: a QoS flow list, a PDCP count value, and an MRB ID, wherein the QoS flow list includes QoS flow mapping indication information, and the QoS flow mapping indication information, for MBS, is used to map QoS flows to MRBs.

[0034] According to another aspect of the embodiments of this application, a network device is also provided, the network device including: a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the configuration method of the multicast broadcast service described above through the computer program.

[0035] In this embodiment of the application, in the base station separation architecture, the base station centralized entity control plane sends a first configuration request message to the base station centralized entity user plane. The configuration information in the first configuration request message includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, multicast broadcast service (MBS) session ID, and MBS area identification information. The base station centralized entity control plane receives a first configuration response message sent by the base station centralized entity user plane. The configuration information in the first configuration response message includes at least one of the following: QoS flow list, PDCP count value, and MRB ID. The QoS flow list includes QoS flow mapping indication information, which, for MBS, is used to map QoS flows to MRBs. This ensures that the base station configures the absolute value of PDCP synchronization time for the target cell's base station centralized entity user plane by introducing PDCP synchronization time information, avoiding system asynchrony. At the same time, it maps QoS flows related to MBS services to one or more corresponding MRBs, flexibly scheduling them according to actual conditions to ensure that service data packets are successfully sent to the user terminal, avoiding errors and service establishment failures. This solves the technical problem that the relevant communication protocols cannot meet the need for flexible scheduling of MBS services based on PDCP synchronization status and service requirements. Attached Figure Description

[0036] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0037] Figure 1 This is a schematic diagram of the configuration system for an optional multicast broadcast service according to an embodiment of this application;

[0038] Figure 2 This is a flowchart illustrating an optional multicast broadcast service configuration method according to an embodiment of this application;

[0039] Figure 3 This is a flowchart illustrating another optional multicast broadcast service configuration method according to an embodiment of this application;

[0040] Figure 4 This is a flowchart illustrating another optional multicast broadcast service configuration method according to an embodiment of this application;

[0041] Figure 5 This is a flowchart illustrating another optional multicast broadcast service configuration method according to an embodiment of this application;

[0042] Figure 6 This is a schematic diagram of the structure of an optional network device according to an embodiment of this application. Detailed Implementation

[0043] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0044] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0045] Furthermore, all information and data (including but not limited to user device information, user personal information, etc.) involved in this application are information and data authorized by the user or fully authorized by all parties. For example, this system has an interface with the relevant user or organization. Before obtaining relevant information, it needs to send an acquisition request to the aforementioned user or organization through the interface, and obtain the relevant information after receiving consent from the aforementioned user or organization.

[0046] To better understand the embodiments of this application, the technical terms involved in the embodiments of this application are explained below:

[0047] MBS (Multimedia Broadcast Service) is a point-to-multipoint service where data can be transmitted from a single source entity to multiple receivers, including all users within the broadcast service area. Therefore, the development of MBS enables multimedia content (such as public safety and mission-critical services, live video, IPTV, etc.) to be transmitted to terminals via broadcast, allowing users to watch broadcast programs or receive data push services anytime, anywhere.

[0048] MCCH (MBS Control Channel): A PTM (Point-to-Multipoint) downlink channel used to transmit MBS (MBS Radio Bearer) broadcast or multicast control information associated with one or more MTCH (MBS Traffic Channel) to terminals from the network. Broadcast MCCH and multicast MCCH are independent channels, and multicast MCCH is only used for multicast reception in the RRC_INACTIVE state.

[0049] MTCH: PTM downlink channel used to transmit MBS data from the network to the UE for multicast or broadcast sessions.

[0050] DTCH (Dedicated Traffic Channel): A PTP channel used to transmit MBS data of multicast sessions from the network to the UE.

[0051] RLC (Radio Link Control) layer: Located above the MAC layer, it provides segmentation and retransmission services for user and control data.

[0052] RAN (Radio Access Network): This is the core component of a 5G network, responsible for connecting user equipment to the network and handling data transmission.

[0053] SDAP (Service Data Adaptation Protocol): It is a key part of the 5G QoS mechanism. It is responsible for mapping QoS flows to DRB and configuring them through RRC signaling. The protocol includes uplink and downlink data transmission rules, as well as reflection QoS mechanism.

[0054] Example 1

[0055] The specific structure of the configuration system for the multicast broadcast service provided in this application embodiment is as follows: Figure 1 As shown. The system may include a base station 10, which can provide communication coverage for a specific geographical area and communicate with terminals located within that coverage area. Optionally, the base station 10 may be a base station (BTS) in a GSM or CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved Node B (eNB or eNodeB) in an LTE system. Furthermore, the base station 10 used in this embodiment is a split-architecture base station, which can be separated into two parts: a centralized physical control plane (g-NB CU CP) 11 and a centralized physical user plane (g-NB CU UP) 12.

[0056] In addition, the system includes at least one terminal 13 located within the coverage area of ​​base station 10. The term "terminal" as used herein includes, but is not limited to, devices configured to receive / transmit communication signals via wired connections, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM radio transmitters; and / or other terminal devices. Terminal devices configured to communicate via a wireless interface may be referred to as "wireless communication terminal," "wireless terminal," or "mobile terminal." Examples of mobile terminals include, but are not limited to, satellite or cellular phones; personal communications system (PCS) terminals that can combine cellular radiotelephony with data processing, fax, and data communication capabilities; PDAs that may include radiotelephones, pagers, Internet / intranet access, web browsers, notebooks, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or handheld receivers or other electronic devices that include radiotelephone transceivers. Terminal equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile devices, user terminals, terminals, wireless communication equipment, user agents, or user equipment. Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in future PLMNs, etc.

[0057] The following will combine Figure 2The configuration process for multicast broadcast services between the base station centralized entity control plane (g-NB CU CP) 11, the base station centralized entity user plane (g-NB CU CP) 12, and the terminal (UE) 13 is described in detail.

[0058] Step 1: The base station centralized entity control plane 11 sends a first configuration request message to the base station centralized entity user plane 12.

[0059] The first configuration request message mentioned above is used to configure PDCP layer parameters. Therefore, the configuration information to be configured carried in the first configuration request message includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information. Specifically:

[0060] (1) The PDCP synchronization indication information mentioned above indicates that the PDCP count values ​​of the corresponding multicast session have been synchronized in the RAN Notification Area (RNA). That is, cells within the RNA follow the same QoS flow to MRB mapping rules (i.e., cells within the same area have PDCP count values ​​mapped based on the same QoS flow), and set the PDCP count values ​​according to the sequence number of the MRB QoS flow. By introducing PDCP synchronization indication information into the above message, it can be ensured that all cells within the RNA have consistent PDCP layer processing for a specific MBS session, thereby enhancing the stability and reliability of multicast services.

[0061] (2) The PDCP count value mentioned above is the initial RX_DELIV (i.e., initialRX_DELIV). Initial RX_DELIV indicates the initial value of RX_DELIV during PDCP window initialization, and is the leftmost or first bit in the bit string. RX_DELIV is a state variable used within the PDCP entity to indicate the count value when the first PDCP Service Data Unit (SDU) has not yet been submitted to the highest layer and is in a waiting-to-submit state. The initial value of RX_DELIV during PDCP window initialization is indicated by the initial RX_DELIV in the configuration information. This helps the terminal initialize the PDCP layer state according to the latest configuration information when receiving multicast or broadcast services, ensuring the continuity and accuracy of data reception, thereby avoiding system asynchrony.

[0062] (3) The aforementioned PDCP synchronization time information is used to synchronize user data or data packets forwarded by the centralized entity user plane of the base station, and to configure PDCP synchronization to a time point shared by the notification area based on the RAN. By introducing PDCP synchronization time information into the request message, it can be ensured that user data or data packets forwarded by the centralized entity user plane of the base station achieve PDCP layer synchronization at a specific time point. This solves the problem of asynchronous PDCP between the source cell and the target cell caused by clock errors, ensures a smooth transition of data packets between different cells, avoids inconsistent service delays or data loss caused by system asynchrony, and thus improves the user experience.

[0063] (4) MBS Session ID is used to associate MBS sessions that provide the same user data or multicast service data packets.

[0064] (5) The identification information of the MBS area is used to identify a specific MBS area, which can be used to determine whether the UE is located in a specific service area and whether it can receive MBS services in that area.

[0065] Optionally, the aforementioned first configuration request message can be divided into: a broadcast bearer context setup request (BC BearerContext Setup Request) message, a broadcast bearer context modification request (BC Bearer ContextModification Request) message, a multicast bearer context setup request (MC Bearer Context Setup Request) message, and a multicast bearer context modification request (MC Bearer Context Modification Request) message.

[0066] When the type of the first configuration request message is a multicast bearer context setup request (MC Bearer Context Setup Request) message, the base station centralized entity control plane 11 requests the base station centralized entity user plane 12 to set up MBS session resources for multicast MBS sessions, so as to establish MBS session resources for multicast MBS sessions in the base station centralized entity user plane 12.

[0067] When the first configuration request message is of type Multicast Bearer ContextModification Request (MC Bearer ContextModification Request), the base station centralized entity control plane 11 requests the base station centralized entity user plane 12 to modify the MBS session resources used for multicast MBS sessions.

[0068] Furthermore, in the event that the base station centralized entity user plane reports a multicast MRB (i.e., MC MRB) establishment failure or an MBS QoS flow establishment failure, the base station centralized entity control plane 11 receives a first configuration response message from the base station centralized entity user plane 12, which carries at least a value indicating the reason for the establishment failure, and determines the reason for the establishment failure based on the value in the first configuration response message. The aforementioned failure reason value needs to be sufficiently accurate so that the base station centralized entity control plane 11 can understand the reason for the unsuccessful establishment.

[0069] Step 2: The base station centralized entity user plane 12 sends the corresponding first configuration request message to the base station centralized entity control plane 11.

[0070] The configuration information in the first configuration response message includes at least one of the following: QoS flow list, PDCP count value, and MRB ID. The QoS flow list includes QoS flow mapping indication information, which is used to map QoS flows to MRBs for MBS and to map QoS flows to DRBs for non-MRBs.

[0071] Specifically, when the first configuration request message is a Broadcast Bearer Context Setup Request (BC Bearer ContextSetup Request) message, the base station centralized entity user plane 12 sends a corresponding first configuration request message to the base station centralized entity control plane 11 as a Broadcast Bearer Context Setup Response (BC Bearer Context Setup Response) message; when the first configuration request message is a Broadcast Bearer Context Modification Request (BC Bearer ContextModification Request) message, the base station centralized entity user plane 12 sends a corresponding first configuration request message to the base station centralized entity control plane 11 as a Broadcast Bearer Context Modification Response (BC Bearer ContextModification Response) message; when the first configuration request message is a Multicast Bearer Context Setup Request (MCBearer Context Setup Request) message, the base station centralized entity user plane 12 sends a corresponding first configuration request message to the base station centralized entity control plane 11 as a Multicast Bearer Context Setup Response (MC Bearer Context Modification) message; when the first configuration request message is a Multicast Bearer Context Modification Request (MC Bearer Context Modification) message... In the case of a Request message, the base station centralized entity user plane 12 sends a corresponding first configuration request message to the base station centralized entity control plane 11, which is either a Multicast Bearer ContextModification Response message or a Multicast Bearer ContextModification Required message.

[0072] Therefore, when the base station centralized entity control plane sends a multicast bearer context establishment request or modification request, it can include PDCP synchronization time information. This ensures that the need for PDCP synchronization can be taken into account when establishing or modifying multicast bearers, thereby achieving PDCP synchronization configuration within the target cell.

[0073] Specifically, the base station centralized entity user plane 12 configures the PDCP layer according to the configuration information in the first configuration request message. In other words, the base station centralized entity user plane 12 sets up the synchronization mechanism of the PDCP layer based on the configuration information.

[0074] Optionally, when the type of the first configuration request message is a multicast bearer context setup request (MC BearerContext Setup Request) message, and the multicast bearer context setup request message includes the identification information of the MBS area (i.e., MBS area ID), the base station central entity user plane 12 stores the identification information of the MBS area and establishes a shared NG-U (i.e., user plane interface) channel based on the identification information of the MBS area service area.

[0075] It should be noted that in the first and second steps above, the base station centralized entity user plane 11 and the base station centralized entity user plane 12 inside the base station are interconnected through the E1 interface to transmit configuration request messages and configuration response messages.

[0076] Step 3: The base station centrally obtains data packets from the core network or server at the physical user plane 12, and feeds back the data packets to the terminal 13 via RRC messages.

[0077] Among them, the PDCP synchronization time information in the first configuration request message means that the base station centralized entity user plane will send data packets to the terminal at the configured PDCP time point according to the PDCP synchronization time information.

[0078] Step 4: Terminal 13 receives configuration information sent by the base station centralized entity control plane 11 via RRC message.

[0079] The configuration information mentioned above includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information.

[0080] Specifically, when the configuration information received by the terminal contains a PDCP count value, the terminal 13 performs the following configuration based on the initialization RX_DELIV in the configuration information:

[0081] (1) Receive window management: Since RX_DELIV indicates the count value of the first PDCP service data unit that has not yet been delivered to the highest layer and is in a waiting state, its initial value is usually 0. Therefore, this value can be used to manage the receive window of the PDCP layer to ensure that the PDCP SDU is delivered to the upper layer in order.

[0082] (2) Data delivery: If the count value of the PDCP data PDU received by the UE is equal to RX_DELIV, the UE can perform header decompression and deliver the PDCP SDUs corresponding to the consecutive count values ​​starting from RX_DELIV to the upper layer in sequence.

[0083] (3) Update RX_DELIV: After all consecutive PDCP SDUs have been delivered, the UE can update RX_DELIV to the count value of the first PDCP SDU that is greater than the current RX_DELIV and has not yet been delivered to the upper layer.

[0084] (4) Reordering timer management: If the t-Reordering timer is running and RX_DELIV is greater than or equal to RX_RECORD (the Count value corresponding to the PDCP data PDU that started the t-Reordering timer in the receive window), the UE will stop and reset the t-Reordering timer.

[0085] (5) Handling packet loss: If there is a count gap between RX_DELIV and RX_NEXT (received state variable, the next expected count value to be received), it indicates that a PDCP SDU has been lost. The UE will start the t-Reordering timer as needed and set RX_RECORD to RX_NEXT.

[0086] When the configuration information received by the terminal includes PDCP synchronization time information, the terminal receives data packets according to the configured time point.

[0087] Additionally, the MRB ID within the configuration information identifies the multicast MRB used by the terminal. That is, it identifies the radio bearer that supports multicast services, allowing the network to transmit the same data simultaneously to a specific group of terminals.

[0088] Optionally, the types of RRC messages used by the base station (base station centralized entity control plane 11, base station centralized entity user plane 12) to send configuration information and data packets to the terminal 13 include: multicast MCCH messages, RRC reconfiguration messages, or RRC release messages, wherein:

[0089] Multicast MCCH messages are messages sent through the multicast MCCH logical channel, and each multicast MCCH message includes at least one of the following: inactive PTM (Point To Multipoint) configuration information or inactive MCCH configuration information. The inactive PTM configuration information instructs terminal 13 to receive MBS messages in an inactive state, and generally includes, but is not limited to: RNA (RAN Notification Area) configuration, DRX (Discontinuous Reception) configuration, cell reselection and mobility management, measurement report configuration, system information, paging configuration, etc., so that even if the terminal is in an RRC inactive state, it can still receive multicast service configuration information. The inactive MCCH configuration information is used to instruct terminal 13 to receive and process control information for multicast services in the RRC inactive state. It generally includes, but is not limited to, RNA (RAN Notification Area) configuration, paging configuration, QoS parameters, cell reselection and mobility management, etc. It can ensure that the terminal can receive and process control information for multicast services during the RRC inactive state, which helps the terminal to keep track of multicast services in the sleep state without having to stay in the RRC connected state.

[0090] The aforementioned RRC reconfiguration message includes at least: SDAP configuration information, and the SDAP configuration information is used to determine the mapping rules of QoS flows to MRBs, wherein the mapping rules include at least: at least one MBS QoS flow on the downlink is mapped to a single MRB.

[0091] The aforementioned RRC release message includes at least the PTM configuration information for the inactive state. This means that when a terminal releases from the RRC connected state to the inactive state, it can still obtain the configuration information required to receive multicast services, avoiding the situation where it cannot receive multicast services due to the lack of configuration information in the inactive state.

[0092] It should be noted that if the RRC release message does not include inactive PTM configuration information, terminal 13 stops monitoring the G-RNTI (Group Radio Network Temporary Identifier) ​​of at least one multicast session. The G-RNTI is used to add interference to the PTM scheduling and transmission process of at least one MBS session.

[0093] In addition, to ensure the continuous stability and quality of service of terminal 13 when receiving multicast services, the following mechanism can be used to manage the mobility of terminal 13:

[0094] When the multicast PTM configuration information is updated and terminal 13 moves to a cell that provides MBS configuration MCCH / MTCH information for inactive terminals, terminal 13 in the inactive state (RRC_INACTIVE) uses the multicast MRB configuration procedure to configure PDCP, RLC (Radio Link Control), MAC (Media Access Control) entities, and the physical layer. The cell that provides MBS configuration MCCH / MTCH information for inactive terminals is the cell that provides SIB (System Information Block) 24 messages.

[0095] When PTM configuration information is updated via multicast MCCH messages or when terminal 13 moves to a cell where the PDCP count of the corresponding multicast MRB is out of sync within the RAN-based notification area (RNA), the terminal performs modification or release / establishment of the multicast MRB. In other words, when terminal 13 moves to a cell where the PDCP count of the corresponding multicast MRB is synchronized within the RNA, it performs modification of the multicast MRB. Alternatively, when terminal 13 moves to a cell where the PDCP count of the multicast MRB is out of sync, it sends an indication to a lower layer to notify that the PCDP count is not synchronized with the corresponding multicast MRB.

[0096] In addition, terminal 13 can also manage its state according to the following rules, including:

[0097] When terminal 13 transitions from connected state to inactive state within the same cell, terminal 13 can continue to use the multicast MRB used in the connected state, wherein the same logical channel identifies the same multicast MRB.

[0098] When terminal 13 transitions from active state to connected state within the same cell, terminal 13 releases the MRB configuration information in the RRC release message or multicast MCCH message and performs incremental configuration based on the MRB configuration information stored in the connected state.

[0099] In the configuration system for the aforementioned multicast broadcast service, the base station centralized entity control plane sends a first configuration request message to the base station centralized entity user plane, containing PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information. The base station centralized entity user plane configures the PDCP layer based on the configuration information in the first configuration request message, achieving flexible configuration of multicast broadcast services and PDCP synchronization in a separated architecture base station. Furthermore, the terminal can also receive configuration information sent by the base station centralized entity control plane, ensuring that terminals in the RRC inactive state can also receive multicast services without constantly maintaining the RRC connected state, thus achieving terminal energy saving.

[0100] Example 2

[0101] Under the aforementioned base station architecture, this application embodiment provides a configuration method for multicast broadcast services. In principle, this method can be executed by any electronic device with computing capabilities.

[0102] In some embodiments, the configuration method for multicast broadcast services provided in this disclosure can be executed by the base station centralized entity control plane 11. Figure 3 This is a flowchart illustrating an optional resource allocation method for a base station based on a split architecture, according to an embodiment of this application. Figure 3 As shown, this method is applied to the base station centralized entity control plane in Embodiment 1 above, and the method includes at least the following steps S302-S304, wherein:

[0103] In step S302, the base station centralized entity control sends a first configuration request message to the base station centralized entity user plane, and the configuration information in the first configuration request message includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information.

[0104] In step S304, the base station centralized entity control plane receives the first configuration response message sent by the base station centralized entity user plane, and the configuration information in the first configuration response message includes at least one of the following: QoS flow list, PDCP count value, and MRBID.

[0105] The aforementioned QoS flow list includes QoS flow mapping indication information, and for MBS, the QoS flow mapping indication information is used to map QoS flows to MRB.

[0106] In some embodiments, the configuration method for multicast broadcast services provided in this disclosure can be executed by the base station centralized entity user plane. Figure 4This is a flowchart illustrating an optional resource allocation method for a base station based on a split architecture, according to an embodiment of this application. Figure 4 As shown, this method is applied to the base station centralized entity user plane 12 in the above embodiment 1, and the method includes at least the following steps S402-S404, wherein:

[0107] In step S402, the user plane of the base station centralized entity receives the first configuration request message sent by the control plane of the base station centralized entity, and the configuration information in the first configuration request message includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information.

[0108] In step S404, the base station centralized entity user sends a corresponding first configuration response message to the base station centralized entity control plane, and the configuration information in the first configuration response message includes at least one of the following: QoS flow list, PDCP count value, and MRB ID.

[0109] The aforementioned QoS flow list includes QoS flow mapping indication information, and for MBS, the QoS flow mapping indication information is used to map QoS flows to MRB.

[0110] In some embodiments, the configuration method for multicast broadcast services provided in this disclosure can be executed by a terminal. Figure 5 This is a flowchart illustrating an optional resource allocation method for a base station based on a split architecture, according to an embodiment of this application. Figure 5 As shown, the method is applied to terminal 13 in the above embodiment 1, and the method includes at least the following step S502, wherein:

[0111] In step S502, the terminal receives configuration information sent by the base station centralized entity control plane through RRC messages. The configuration information includes at least one of the following: QoS flow list, PDCP count value, and MRB ID. The QoS flow list includes QoS flow mapping indication information, and the QoS flow mapping indication information, for MBS, is used to map QoS flows to MRB.

[0112] The specific implementation schemes of the above steps S302-S304, S402-S404 and S502 have been described in detail in Embodiment 1, and will not be repeated here.

[0113] Example 3

[0114] According to an embodiment of this application, a non-volatile storage medium is also provided, which stores a program, wherein the program controls the device where the non-volatile storage medium is located to execute the configuration method of the multicast broadcast service in Embodiment 2 when it runs.

[0115] According to an embodiment of this application, a computer program product is also provided, which includes a stored computer program, wherein when the computer program is executed by a processor, it implements the configuration method for the multicast broadcast service in Embodiments 2 and 3.

[0116] According to an embodiment of this application, a processor is also provided for running a program, wherein the program executes the configuration method for the multicast broadcast service in Embodiment 2 during runtime.

[0117] According to an embodiment of this application, a network device is also provided, wherein the network device includes one or more processors; a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors are configured to run the programs, wherein the programs are configured to execute the configuration method for the multicast broadcast service in Embodiment 2 above.

[0118] Optionally, the program executes the following steps during runtime: the base station centralized entity control plane sends a first configuration request message to the base station centralized entity user plane, and the configuration information in the first configuration request message includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information; the base station centralized entity control plane receives a first configuration response message sent by the base station centralized entity user plane, and the configuration information in the first configuration response message includes at least one of the following: QoS flow list, PDCP count value, and MRB ID, wherein the QoS flow list includes QoS flow mapping indication information, and the QoS flow mapping indication information, for MBS, is used to map QoS flows to MRB.

[0119] Optionally, the program executes the following steps during runtime: the user plane of the base station centralized entity receives a first configuration request message sent by the control plane of the base station centralized entity, and the configuration information in the first configuration request message includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information; the user plane of the base station centralized entity feeds back a corresponding first configuration response message to the control plane of the base station centralized entity, and the configuration information in the first configuration response message includes at least one of the following: QoS flow list, PDCP count value, and MRB ID, wherein the QoS flow list includes QoS flow mapping indication information, and the QoS flow mapping indication information, for MBS, is used to map QoS flows to MRB.

[0120] Optionally, the program executes the following steps during runtime: The terminal receives configuration information sent by the base station centralized entity control plane via RRC messages, wherein the configuration information includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information.

[0121] As an alternative implementation, the network device described above may exist in the form of a mobile terminal, a computer terminal, or a similar computing device. Figure 6 A hardware block diagram of a network device for implementing a configuration method for multicast broadcast services is shown. Figure 6 As shown, network device 60 may include one or more processors 602 (shown as 602a, 602b, ..., 602n in the figure) 602 (processor 602 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 604 for storing data, and a transmission device 606 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 6 The structure shown is for illustrative purposes only and does not limit the structure of the network device described above. For example, network device 60 may also include... Figure 6 The more or fewer components shown, or having the same Figure 6 The different configurations shown.

[0122] It should be noted that the aforementioned one or more processors 602 and / or other data processing circuitry are generally referred to herein as "data processing circuitry". This data processing circuitry may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuitry may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the network device 60. As involved in the embodiments of this application, this data processing circuitry serves as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0123] The memory 604 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the configuration method of multicast broadcast service in this embodiment of the application. The processor 602 executes various functional applications and data processing by running the software programs and modules stored in the memory 604, thereby implementing the above-mentioned application vulnerability detection method. The memory 604 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 604 may further include memory remotely located relative to the processor 602, and these remote memories can be connected to the network device 60 via a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0124] The transmission device 606 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the network device 60. In one example, the transmission device 606 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 606 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0125] The display may be, for example, a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the network device 60.

[0126] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0127] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0128] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0129] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0130] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0131] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to related technologies, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0132] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A configuration method for a multicast broadcast service, characterized in that, include: The base station centralized entity control sends a first configuration request message to the base station centralized entity user plane, and the configuration information in the first configuration request message includes at least one of the following: Packet Data Convergence Protocol (PDCP) synchronization indication information, PDCP count value, PDCP synchronization time information, Multicast Broadcast Service Radio Bearer (MRBID), Multicast Broadcast Service (MBS) Session ID, and MBS area identification information. The base station centralized entity control plane receives a first configuration response message sent by the base station centralized entity user plane, and the configuration information in the first configuration response message includes at least one of the following: Quality of Service (QoS) flow list, PDCP count value, and MRB ID, wherein the QoS flow list includes QoS flow mapping indication information, and the QoS flow mapping indication information, for MBS, is used to map QoS flows to MRB.

2. The method according to claim 1, characterized in that, The PDCP synchronization indication information is used to indicate that the PDCP count value of the corresponding multicast session has been synchronized in the notification area based on the Radio Network Architecture (RAN). The cells in the RAN-based notification area follow the same QoS flow to MRB mapping rule, and the PDCP count value is set according to the sequence number of the MRB QoS flow.

3. The method according to claim 1, characterized in that, The PDCP synchronization time information is used to synchronize the user data or data packets forwarded by the centralized entity user plane of the base station, and to configure the PDCP synchronization to the time point shared by the notification area based on the RAN.

4. The method according to claim 1, characterized in that, The PDCP count value is the initial RX_DELIV.

5. The method according to claim 4, characterized in that, The initial RX_DELIV is used to indicate the initial value of RX_DELIV during PDCP window initialization, and the initial RX_DELIV is the leftmost or first bit in the bit string. RX_DELIV is a state variable used within the PDCP entity to indicate the count value of the first PDCP service data unit that has not yet been delivered to the highest layer and is in a waiting-to-deliver state.

6. The method according to claim 1, characterized in that, The MBS session ID is used to associate MBS sessions that provide the same user data or multicast service data packets.

7. The method according to claim 1, characterized in that, The types of the first configuration request message include: broadcast bearer context establishment request message, broadcast bearer context modification request message, multicast bearer context establishment request message, and multicast bearer context modification request message; The first configuration response message includes the following types: broadcast bearer context establishment response message, broadcast bearer context modification response message, multicast bearer context establishment response message, multicast bearer context modification request message, or multicast bearer context modification requirement message.

8. The method according to claim 7, characterized in that, When the type of the first configuration request message is the multicast bearer context establishment request message, the base station centralized entity control requests the base station centralized entity user plane to set up MBS session resources for multicast MBS sessions, so as to establish MBS session resources for multicast MBS sessions in the base station centralized entity user plane.

9. The method according to claim 7, characterized in that, When the type of the first configuration request message is the multicast bearer context modification request message, the base station centralized entity control requests the base station centralized entity user plane to modify the MBS session resources used for multicast MBS sessions.

10. The method according to claim 8, characterized in that, When the base station centralized entity user plane reports a multicast MRB establishment failure or an MBS QoS flow establishment failure, the base station centralized entity control plane receives a first configuration response message from the base station centralized entity user plane that carries at least a establishment failure reason value, and determines the reason for the establishment failure based on the establishment failure reason value in the first configuration response message.

11. A method for configuring a multicast broadcast service, characterized in that, include: The base station centralized entity user plane receives a first configuration request message sent by the base station centralized entity control plane, and the configuration information in the first configuration request message includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information; The user of the base station centralized entity sends a corresponding first configuration response message to the control plane of the base station centralized entity, and the configuration information in the first configuration response message includes at least one of the following: QoS flow list, PDCP count value, and MRBID, wherein the QoS flow list includes QoS flow mapping indication information, and the QoS flow mapping indication information, for MBS, is used to map QoS flows to MRB.

12. The method according to claim 11, characterized in that, The base station centralized entity user plane configures PDCP based on the configuration information in the first configuration request message.

13. The method according to claim 11, characterized in that, The types of the first configuration request message include: broadcast bearer context establishment request message, broadcast bearer context modification request message, multicast bearer context establishment request message, and multicast bearer context modification request message; The first configuration response message includes the following types: broadcast bearer context establishment response message, broadcast bearer context modification response message, multicast bearer context establishment response message, multicast bearer context modification request message, or multicast bearer context modification requirement message.

14. The method according to claim 13, characterized in that, When the type of the first configuration request message is the multicast bearer context establishment request message, and the multicast bearer context establishment request message includes the identification information of the MBS area, the base station central entity user plane stores the identification information of the MBS area, and establishes a shared user plane interface NG-U channel based on the identification information of the MBS area service area.

15. The method according to claim 11, characterized in that, The base station centralized entity user plane obtains data packets from the core network or server and feeds the data packets back to the terminal; if the first configuration request message includes PDCP synchronization time information, then the base station centralized entity user plane sends the data packets to the terminal at the configured PDCP time point according to the PDCP synchronization time information.

16. A method for configuring a multicast broadcast service, characterized in that, include: The terminal receives configuration information sent by the centralized entity control plane of the base station via RRC messages, wherein the configuration information includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information.

17. The method according to claim 16, characterized in that, The terminal receives data packets sent by the base station's centralized entity user plane via RRC messages.

18. The method according to claim 16, characterized in that, When the configuration information received by the terminal contains a PDCP count value, the terminal performs configuration according to the initialization RX_DELIV in the configuration information; When the configuration information received by the terminal includes PDCP synchronization time information, the terminal receives data packets according to the configured time point.

19. The method according to claim 16, characterized in that, The MRB ID is used to identify the multicast MRB used by the terminal.

20. The method according to claim 16, characterized in that, The types of RRC messages include: multicast MBS control channel MCCH messages, RRC reconfiguration messages, or RRC release messages, wherein... The multicast MCCH message is a message sent through the multicast MCCH logical channel, and the multicast MCCH message includes at least one of the following: inactive point-to-multipoint PTM configuration information, inactive MCCH configuration information, wherein the inactive PTM configuration information is used to instruct the terminal to receive MBS messages in an inactive state. The RRC reconfiguration message includes at least: Service Data Adaptation Protocol (SDAP) configuration information, and the SDAP configuration information is used to determine the mapping rules of QoS flows to MRBs, wherein the mapping rules include at least: at least one MBS QoS flow on the downlink is mapped to a single MRB; The RRC release message includes at least the inactive PTM configuration information.

21. The method according to claim 20, characterized in that, If the RRC release message does not include inactive PTM configuration information, the terminal stops monitoring the Group Radio Network Temporary Identifier (G-RNTI) of at least one multicast session, wherein the G-RNTI is used to add interference to the PTM scheduling and transmission process of at least one MBS session.

22. The method according to claim 16, characterized in that, When the multicast PTM configuration information is updated and the terminal moves to a cell that provides MBS configuration MCCH / multicast service channel MTCH information for inactive terminals, the inactive terminal uses the multicast MRB configuration procedure to configure PDCP, Radio Link Layer Control Protocol (RLC), Media Access Control (MAC) entity, and physical layer. The cell that provides MBS configuration MCCH / MTCH information for inactive terminals is the cell that provides System Information Block (SIB24) messages. When the PTM configuration information is updated via the multicast MCCH message or when the terminal moves to a cell where the PDCP count value of the corresponding multicast MRB is out of sync within the RAN-based notification area, the terminal performs modification of the multicast MRB or release / establishment of the multicast MRB.

23. The method according to claim 16, characterized in that, When the terminal transitions from connected state to inactive state within the same cell, the terminal continues to use the multicast MRB used in the connected state; When the terminal transitions from active state to connected state within the same cell, the terminal releases the MRB configuration information in the RRC release message or the multicast MCCH message, and performs incremental configuration based on the MRB configuration information stored in the connected state.

24. A configuration system for multicast broadcast services, characterized in that, The system includes: a base station centralized entity control plane, a base station centralized entity user plane, and terminals, wherein... The base station centralized entity control plane is used to send a first configuration request message to the base station centralized entity user plane, and the configuration information in the first configuration request message includes at least one of the following: PDCP synchronization indication information, PDCP count value, PDCP synchronization time information, MRB ID, MBS session ID, and MBS area identification information; and sends the configuration information in the first configuration request message to the terminal through an RRC message. The base station centralized entity user plane is used to feed back a corresponding first configuration response message to the base station centralized entity control plane, and the configuration information in the first configuration response message includes at least one of the following: QoS flow list, PDCP count value, and MRB ID, wherein the QoS flow list includes QoS flow mapping indication information, and the QoS flow mapping indication information, for MBS, is used to map QoS flows to MRB.

25. A network device, characterized in that, include: A memory and a processor, the processor being configured to run a program stored in the memory, wherein the program, when running, executes the configuration method for the multicast broadcast service according to any one of claims 1 to 23.

Images