METHOD AND APPARATUS FOR INFORMATION CONTROL AND BASE STATION

Abstract

This application describes an information control method and apparatus and a base station; the information control method applied to a base station includes: transmitting a first signal from a CU of the base station to a DU of the base station, wherein the first signal includes information about MBS traffic, and the information about MBS traffic is used to indicate to the DU that MBS traffic is to be transmitted in a first mode; generating configuration information related to MBS traffic in the DU; and transmitting the configuration information from the DU to the CU.

Description

METHOD AND APPARATUS FOR INFORMATION CONTROL AND BASE STATION CROSS-REFERENCE WITH RELATED APPLICATIONS This application claims priority from Chinese Patent Application No. 202010814979.1, filed in China on August 13, 2020, which is incorporated herein by reference in its entirety. TECHNICAL FIELD This application belongs to the field of communication technologies and, specifically, relates to a method and apparatus for information control and a base station. BACKGROUND OF THE INVENTION Currently, multicast broadcast service (MBS) is typically implemented using a base station. With the development of communications technologies, the Central Unit (CU)-Distributed Unit (DU) architecture is being introduced into existing base station configurations to meet various requirements. In the CU-DU architecture, a base station includes a separate CU and DU, and a standardized interface is provided between the CU and DU. However, even after the introduction of the CU-DU architecture, how to support the transmission of MBS traffic remains undefined. BRIEF DESCRIPTION OF THE INVENTION One objective of the modalities of this application is to provide an information control method and apparatus and a base station, to address how MBS traffic transmission is implemented after introducing a CU-DU architecture in a base station. To resolve the above technical problem, this request is implemented as follows: According to a first aspect, an information control method is provided, where the method is applied to a base station, the base station includes a CU and a DU, and the method includes: transmit the first signaling from the CU to the DU, where the first signaling includes information about the MBS traffic, and the information about the MBS traffic is used to indicate MA / a / ZUZJ / UUIIUU that the DU transmits MBS traffic in a first mode; Generate configuration information related to MBS traffic in the DU; and transmit configuration information from the DU to the CU. According to a second aspect, an information control apparatus is provided, where the apparatus is applied to a base station, and the apparatus includes a CU and a DU, where the CU is configured to transmit the first signaling to the DU, where the first signaling includes information about MBS traffic, and the information about MBS traffic is used to indicate that the DU transmits MBS traffic in a first mode; and the DU is configured to generate configuration information related to MBS traffic and transmit the configuration information to the CU. According to a third aspect, a base station is provided, where the base station includes a processor, a memory, and a program or instructions stored in memory and capable of execution on the processor, and when the program or instructions are executed by the processor, the steps of the method according to the first aspect are implemented. According to a fourth aspect, a readable storage medium is provided, where the readable storage medium stores a program or instructions, and when a processor executes the program or instructions, the steps of the method according to the first aspect are implemented. According to a fifth aspect, a chip is provided, where the chip includes a processor and a communications interface, the communications interface is coupled to the processor and the processor is configured to execute a program or instructions, to implement the method according to the first aspect. According to a sixth aspect, a computer program product is provided and stored on a non-volatile readable storage medium, where the computer program product is executed by at least one processor to implement the method according to the first aspect. According to a seventh aspect, a base station is provided, where the base station is configured to implement the method according to the first aspect. In the modes described in this application, the initial signaling can be transmitted from a CU to a DU. This initial signaling includes information about MBS traffic, and this MBS traffic information is used to indicate that the DU is transmitting MBS traffic in the first mode. Configuration information related to MBS traffic is generated in the DU, and this configuration information is then transmitted from the DU to the CU. In this way, after implementing a CU-DU architecture in a base station, MBS traffic transmission can be supported. Therefore, in a network with a CU-DU architecture, a terminal can also efficiently perform the correct processing of received MBS traffic based on the MBS traffic transmission parameter configured by the network, further improving the quality of service guarantee for the traffic and enhancing the user experience and system efficiency. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a block diagram of a wireless communications system according to one modality of this application; Figure 2 is a schematic diagram of a control plane protocol stack architecture for unicast traffic in a CU-DU architecture according to one modality of this request; Figure 3 is a schematic diagram of a control plane protocol stack architecture for multicast traffic in a CU-DU architecture according to one modality of this application; Figure 4 is a first schematic diagram of a user plane protocol stack architecture in a CU-DU architecture according to one modality of this request; Figure 5 is a second schematic diagram of a user plane protocol stack architecture in a CU-DU architecture according to one modality of this request; Figure 6 is a third schematic diagram of a user plane protocol stack architecture in a CU-DU architecture according to one modality of this request; Figure 7 is a flowchart of an information control method according to one modality of this request; Figure 8 is a schematic structural diagram of an information control apparatus according to one modality of this request; Figure 9 is a schematic structural diagram of a base station according to one modality of this request; and Figure 10 is a schematic structural diagram of another base station according to one modality of this request. DETAILED DESCRIPTION OF THE INVENTION The following clearly and completely describes the technical solutions in the forms covered by this application with reference to the accompanying drawings. It appears that the forms described are some, but not all, of the forms covered by this application. All other forms obtained by a person of average skill in the art, based on the forms covered by this application without creative effort, will fall within the scope of protection of this application.All other forms obtained by a person skilled in the art based on the forms in this application without creative effort will be within the scope of protection of this application. The terms "first," "second," and similar in this specification and claims of this application are used to distinguish between similar objects rather than to describe a specific order or sequence. It should be understood that the data used in this manner are interchangeable under appropriate circumstances so that the modalities of this application may be implemented in orders other than the order illustrated or described herein. Furthermore, "first" and "second" are commonly used to distinguish objects of the same category but do not limit the number of objects. For example, there may be one or more "first" objects. Additionally, in this specification and claims, "and / or" indicates at least one of the connected objects, and the character generally indicates a relationship between associated objects. It should be noted that the technologies described in the modalities of this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, and can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems.The terms "system" and "network" in the modalities of this application are often used interchangeably, and the technologies described herein may be used in the radio systems and technologies mentioned above, as well as in other radio systems and technologies. However, in the following descriptions, a New Radio (NR) system is described for illustrative purposes, and the term NR is used in most of the following descriptions, although these technologies may also apply to applications other than an NR system application, for example, a 6th Generation (6G) communications system. Figure 1 is a block diagram of a wireless communications system to which a modality of this application applies. The wireless communications system includes a terminal 11 and a network-side device 12. Terminal 11 may also be referred to as a terminal device or user equipment (UE). Terminal 11 may be a terminal-side device such as a mobile phone, a tablet personal computer, a laptop computer (also called a lightweight laptop), a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), a wearable device, vehicle user equipment (VUE), or pedestrian user equipment (PUE).The portable device includes a headband, headphones, glasses, or similar items. It should be noted that a specific type of terminal 11 is not limited in the modalities of this application. The network-side device 12 can be a base station or a core network. The base station may be called a NodeB, evolved NodeB, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), home NodeB, home evolved NodeB, WLAN access point, Wi-Fi node, transmitting / receiving point (TRP), or another term appropriate in the art. As long as the same technical effect is achieved, the base station is not limited to a specific technical term.It should be noted that the base station in the NR system is only used as an example in the modalities of this application, but is not limited to a specific type of base station. To facilitate understanding of this application, the following content is described first. Figure 2 is a schematic diagram of a typical UE control plane protocol stack architecture for unicast traffic in a CU-DU architecture. As shown in Figure 2, the UE includes a non-access stratum (NAS) entity, a radio resource control (RRC) entity, a packet data convergence protocol (PDCP) entity, a radio link control (RLC) entity, a media access control (MAC) entity, and a physical layer (PHY) entity. A CU in a gNB base station includes an RRC entity and a PDCP entity, corresponding to the UE's RRC and PDCP entities, respectively. A DU in the gNB includes an RLC entity, a MAC entity, and a PHY entity.Specifically, the RLC entity and the protocol layer entities below the RLC entity are located in the DU and correspond to the UE's RLC entity, MAC entity, and PHY entity, respectively. The UE's NAS entity corresponds to a NAS entity in a core network, for example, an Access Management Function (AMF). It should be noted that a UE user plane has a protocol stack architecture similar to that in Figure 2, where a Service Data Adaptation Protocol (SDAP) entity and a PDCP entity are located in a CU, and an RLC entity and protocol layer entities below the RLC entity are located in a DU. In this application mode, a similar protocol stack division can be used for MBS traffic based on a protocol stack division between the CU and DU for unicast traffic. However, the differences mainly materialize in the following aspects: (1) For the UE receiving multicast traffic, the multicast traffic is not directly controlled by a Non-Access Stratum (NAS) of the UE. Instead, a core network multicast entity and a base station (a gNB-CU) interact to determine that the multicast traffic should be delivered to the base station (a gNB-DU), and then the base station (the gNB-DU) determines whether the transmission will be over an air interface and which transmission mode to use. (2) For multicast traffic, certain control information is still required, such as neighbor cell support information for the multicast traffic, and a traffic identifier, scheduling, cycle, resource allocation, and other information about the multicast traffic. If the control information is transmitted to the UE using dedicated signaling, the processing is similar to that of the UE's existing RRC signaling. However, if the control information is transmitted to the UE using broadcast or multicast signaling, the protocol stack architecture for this transmission mode may differ from the protocol stack architecture for unicast traffic. For example, if no operation, such as a security operation, is provided, a PDCP entity may default to or perform a transparent transmission. (3) For multicast traffic, if a point-to-multipoint (PTM) mode of an air interface is used for transmission, an implementation of a protocol stack entity may be that an SDAP entity is the default and / or a PDCP entity is the default; or whether a related protocol stack entity is the default may be determined based on a configuration. (4) For multicast traffic, if a point-to-point (PTP) mode of an air interface is used for transmission, an implementation of a protocol stack entity may be that an SDAP entity is defaulted and / or a default of the PDCP entity; or if a related protocol stack entity is defaulted it is determined on the basis of a configuration; or a protocol stack entity may be mapped in different ways. Optionally, in the CU-DU architecture, the division of functions and a protocol stack entity architecture related to multicast traffic include a control plane and a user plane. A basic idea is as follows: A protocol stack entity related to Layer 3 is located in a CU, a Layer 2 protocol stack entity and the protocol stack entities below Layer 2 are located in a DU. The CU is responsible for the UE's RRC signaling procedure, and the DU is responsible for information exchange at Layer 2 and below. Optionally, for a multicast traffic control plane, a control plane procedure related to the transmission of multicast traffic is primarily the notification of control information from an air interface. If dedicated RRC signaling is used for notification, an existing unicast protocol stack split form can be fully reused as a protocol stack split form. However, if broadcast or multicast RRC signaling is used for notification, as shown in Figure 3, it can be determined whether a PDCP entity is default based on a stipulation in a protocol or configuration. An RLC mode can be determined by default or through configuration. For example, the RLC mode can be either Unacknowledged Mode (UM) or Transparent Mode (TM). Optionally, for a multicast traffic user plane, if a PTM mode is used for transmission, as shown in Figure 4, it can be determined whether a PDCP entity is the default based on a stipulation in a protocol or configuration. It can also be determined whether an SDAP entity is the default based on a stipulation in a protocol or configuration. In particular, because SDAP entities are not symmetrical, an SDAP entity on a gNB-CU side can be used to map a multicast Quality of Service (QoS) flow to a Multicast Services Radio Bearer (MRB), while an SDAP entity on a UE side serving as the receiving end does not perform an actual function and can therefore still be the default. Optionally, for a multicast traffic user plane, if a PTP mode is used for transmission, as shown in Figure 5 or Figure 6, it can be determined whether a PDCP entity is the default based on a stipulation in a protocol or configuration. It can also be determined whether an SDAP entity is the default based on a stipulation in a protocol or configuration. Figure 5 is a schematic diagram of a protocol stack architecture in PTP mode 1. Figure 6 is a schematic diagram of a protocol stack architecture in PTP mode 2. It should be noted that the main differences between the protocol stack architectures corresponding to PTM mode and the two PTP modes are as follows: (1) PTM Mode: On the base station side, regardless of whether it's a CU or a DU, for the same multicast traffic (e.g., a Temporary Mobile Group Identity, TMGI, is used), the CU or DU has only one set of user plane protocol entities. Specifically, a set of SDAP and PDCP entities resides in the CU, and a set of RLC, MAC, and PHY entities resides in the DU. However, the corresponding SDAP, PDCP, RLC, MAC, and PHY entities can be set for different UE_n based on a configuration and / or for specific needs. A plurality of UEs correspond to the same network-side protocol stack. (2) PTP Mode 1: On the base station side, for the same multicast traffic (e.g., using a TMGI identifier), a CU maintains one set of user plane protocol entities, while a DU needs to maintain different protocol stack entities for the UEs. Specifically, the CU maintains only one set of SDAP and PDCP entities for the traffic, and the DU needs to establish a set of RLC, MAC, and PHY entities for each UE, corresponding to the user plane protocol entities on the UE side. Because the multicast traffic is also transmitted in unicast mode, the MAC and PHY entities can be shared with existing unicast traffic entities of the UE. Additionally, in PTP mode, the UE needs to be in an RRC connected state.Therefore, the RLC entity, MAC entity, and PHY entity can be established and maintained between the UE and the DU using a procedure similar to an existing unicast procedure. However, for the unified SDAP entity and the PDCP entity, when the CU establishes a PTP MRB or a Data Radio Bearer (DRB) for the UE (in this document, a dedicated bearer is established to transmit multicast traffic, or optionally, no other type of bearer, and the content is multicast traffic, but a type of bearer can be similar to a DRB), the UE must be notified of the current states of the SDAP entity and the PDCP entity to facilitate establishment by the UE.Alternatively, status notification using RRC signaling is not required; instead, the UE is notified that the unicast setup is being used for multicast, and the UE performs a special PDCP processing procedure. For example, a PDCP status variable is initiated to be calculated based on a serial number (SN) from the first received data packet. (3) PTP Mode 2: On the base station side, for the same multicast traffic (e.g., using a TMGI identifier), a CU and a DU each maintain an independent set of user plane protocol entities for each UE. Specifically, the CU establishes and maintains a set of SDAP and PDCP entities for each UE, and the DU also needs to establish and maintain a set of RLC, MAC, and PHY entities for each UE. Because the multicast traffic is also transmitted in unicast mode, the MAC and PHY entities can be shared with existing unicast traffic entities of the UE.In this case, because each UE has its own independent SDAP entity and / or PDCP entity, similar to that of unicast traffic, the initialization of the PDCP entity state can start from 0 and, consequently, the UE can initialize the PDCP entity and / or the SDAP entity in a manner similar to the establishment of the unicast bearer. In the modalities of this application, MBS traffic may also be referred to as multicast traffic or multimedia broadcast multicast traffic (Multimedia Broadcast Multicast Service, MBMS). Optionally, PTM mode may also be called PTM send mode or PTM transmit mode. Optionally, PTP mode may also be called PTP sending mode or PTP transmission mode. Optionally, the control plane may also be called the control surface. Optionally, the user plane may also be called the user surface. It should be noted that, in the modes described in this application, both PTM and PTP modes are transmission modes for a Uu interface on one side of the RAN; that is, transmission between a base station and the UE is point-to-multipoint and / or point-to-point. Both PTM and PTP transmission modes of the Uu interface rely on a shared multicast channel between a core network (CN) and a gNB. A full channel from the CN to the gNB and the UE is in unicast mode, similar to existing unicast traffic, and an existing procedure can be reused. This is not addressed in this application. The following describes in detail a method of controlling the information provided in the modalities of this application with reference to the attached drawings and by using specific modalities and application scenarios thereof. Figure 7 is a flowchart of an information control method according to one modality of this request. The method is applied to a base station. The base station includes a CU and a DU. A standardized interface, for example, an F1 interface, is provided between the CU and the DU. Information exchange between the CU and the DU can be implemented through this interface. As shown in Figure 7, the method includes the following steps. Step 71: Transmit the signaling from the CU to the DU first. In this mode, the first signaling includes information about the MBS traffic, and this MBS traffic information is used to indicate that the DU is transmitting MBS traffic in a first mode. The MBS traffic information includes, but is not limited to, a TMGI, cycle information, QoS information for the traffic, and similar data. The QoS information for the traffic includes, but is not limited to, a bit rate, a block error rate, a delay, a priority, a traffic type, and similar data. Optionally, the first mode includes any of the following: a PTM mode and a PTP mode. For example, if the first mode includes PTM mode, the first signaling is the F1 interface signaling, and any existing non-UE-associated signaling, such as gNB-CU configuration update signaling, between the CU and DU can be reused. Alternatively, the first signaling is a newly established F1 interface signaling, which is also non-UE-associated signaling.For example, a name might be gNB-CU MBS configuration signaling, specifically used to carry a request to establish, modify, and / or release MBS-related information; or a name might be gNB-CU MBS configuration establishment signaling, used to establish MBS traffic; or a name might be gNB-CU MBS configuration modification signaling, used to modify MBS traffic; or a name might be gNB-CU MBS configuration release signaling, used to release MBS traffic. It can be understood that, in this case, the transmission is performed in multicast mode, and therefore the first signaling is not directly associated with any UE; that is, the first signaling is a non-UE-associated signaling. For another example, if the first mode includes PTP mode, the first signaling is Fl interface signaling, and some of the existing UE-associated signaling, such as Context Modification signaling, between the CU and DU can be reused. Alternatively, the first signaling is newly established Fl interface signaling, which is also UE-associated signaling.For example, a name is UE MBS configuration signaling, specifically used to carry a request to establish, modify, and / or release information related to UE and MBS; or a name is UE MBS configuration establishment signaling, used to establish MBS traffic; or a name is UE MBS configuration modification signaling, used to modify MBS traffic; or a name is UE MBS configuration release signaling, used to release MBS traffic. Step 72: Generate configuration information related to MBS traffic in the DU. In this mode, after receiving the first signaling, the DU can learn that MBS traffic will be transmitted in the first mode and reserve a required resource for MBS traffic and generate a related configuration based on information about MBS traffic. Optionally, in PTM mode, MBS traffic-related configuration information includes, but is not limited to, RLC settings, MAC settings, PHY transmission settings, and similar configurations. For example, MAC settings include a Discontinuous Reception (DRX) offset, enabling / disabling a Hybrid Automatic Repeat reQuest (HARQ), a group Radio Network Temporary Identity (g-RNTI), a logical channel identity (LCID), and similar configurations. For example, PHY transmission settings include a Modulation and Coding Scheme (MCS) box, a transmission mode, and similar configurations. Optionally, in PTP mode, MBS traffic-related configuration information includes, but is not limited to, RLC settings, MAC address settings, PHY transmission settings, and similar configurations. For example, MAC address settings include disabling / enabling HARQ, an LCID, and similar configurations. If it is also necessary to change a unicast transmission parameter, for example, the PHY transmission settings include an MCS table, a transmission mode, and similar configurations. Step 73: Transmit the DU configuration information to the CU. In the information control method for this application mode, the first signaling can be transmitted from the CU to the DU. This initial signaling includes information about MBS traffic, which indicates that the DU is transmitting MBS traffic in the first mode. Configuration information related to MBS traffic is generated at the DU and then transmitted from the DU to the CU. In this way, after implementing a CU-DU architecture at a base station, MBS traffic transmission can be supported. Therefore, in a network with a CU-DU architecture, a terminal can also efficiently perform the correct processing of received MBS traffic based on the MBS traffic transmission parameter configured by the network, further improving the quality of service guarantee for the traffic and enhancing the user experience and system efficiency.In this application mode, PTM, transmission is based on a cell and / or frequency within each DU. For example, cell 1 and / or frequency 1 in DU 1 must transmit in PTM mode, but other cells and frequencies do not; and cell 5 and / or frequency 2 in DU 2 must transmit in PTM mode, but other cells and frequencies do not. Frequency 1 and frequency 2 can be the same or different. The CU can specify a particular cell / frequency for transmission. For example, a cell at the same frequency with continuous coverage is preferred for transmission. This facilitates traffic continuity for the UE, and the UE can achieve continuous multicast traffic reception as long as it moves within the same frequency range. Alternatively, the selection can be made by the DU.For example, a cell with sufficient resources or a cell suitable for PTM transmission is preferably selected. In PTP mode, transmission occurs only on a Uu interface, and data from a CN to a gNB / gNB-CU is still in multicast form. Specifically, a transmission tunnel from the CN to the gNB / gNB-CU is not associated with any UE, and the gNB chooses to serve a small number of UEs in PTP mode to improve transmission efficiency simply because the number of users with interest is small. If transmission from the CN to the gNB / gNB-CU is also in UE-specific unicast form, the case is the same as for conventional unicast traffic when PTP mode is selected for an air interface. It can be understood that a large number of UEs covered by a cell must be incorporated into PTM mode, making the transmission mode inefficient. For example, the transmission level is low, and an omnidirectional antenna is used. One advantage of PTM lies in its lower resource consumption, as multiple UEs consume only one transmission resource. In PTP mode, transmission is performed for only one UE, and the adjustment of transmission parameters, antenna beamforming, and similar operations can be performed for that UE, resulting in high transmission efficiency. However, in PTP mode, each UE consumes a transmission resource, and therefore, resource consumption is much higher than in PTM mode if there are a large number of UEs. Therefore, the number of UEs is a significant indicator for selecting between PTP and PTM modes. Optionally, to allow the DU to reserve an appropriate resource for MBS traffic, the first signaling may also include at least one of the following: cell information and / or frequency information expected by the CU, for example, a cell identifier ID, a frequency ID, cell list information and / or frequency list information; cell type information and / or expected frequency type information by the CU, for example, frequency type information includes a high or low frequency, an FR 1 or an FR2, or similar, and cell type information includes a cell with a large coverage, a cell with a large capacity, a cell with the greatest possible number of resources, or similar; priority information on MBS traffic; information on a comparison between MBS traffic priority and unicast traffic priority; Information on whether MBS traffic can be overridden by other MBS traffic and / or unicast traffic, for example, MBS traffic can be overridden by other MBS traffic and / or unicast traffic, or MBS traffic cannot be overridden by other MBS traffic and / or unicast traffic; and information on whether MBS traffic can override other MBS traffic and / or unicast traffic, for example, MBS traffic can override other MBS traffic and / or unicast traffic, or MBS traffic cannot override other MBS traffic and / or unicast traffic. In one implementation, the priority information for MBS traffic can be the actual priority of the MBS traffic. In this case, with reference to the information included in the first signaling, comparing the priority of the MBS traffic with the priority of the unicast traffic, the priorities of the MBS traffic and the unicast traffic can be compared. In another implementation, the priority information for MBS traffic can be a unicast traffic priority that corresponds to a converted priority of the MBS traffic. In this case, the priority of the MBS traffic can be directly compared to that of the unicast traffic using the priority information for the MBS traffic. It can be understood that MBS traffic priority and unicast traffic priority may not have the same meaning in the same priority space. In conventional unicast, within the same priority space, a smaller priority value indicates a higher priority. However, MBS traffic priority and unicast traffic priority are independent sequences, and a lower priority value does not necessarily mean a higher priority. For example, priority 1 is not necessarily higher than priority 3. Therefore, a specific additional configuration can be implemented, such as a comparison ratio between MBS traffic priority and unicast traffic priority, so that MBS traffic can be compared to any other unicast traffic. Optionally, information about a comparison between MBS traffic priority and unicast traffic priority may include at least one of the following: MBS traffic priority being higher, lower, or equal to the unicast traffic priority; Report information from a terminal about the priority of MBS traffic and the priority of unicast traffic, for example, the terminal considers that MBS traffic has priority, or the terminal considers that unicast traffic has priority, or the terminal considers that MBS traffic has priority over certain unicast traffic, such as Internet access traffic, but does not have precedence over other unicast traffic, such as telephone traffic; a priority threshold for MBS traffic; a priority threshold for unicast traffic; and a priority threshold for MBS traffic and a priority threshold for unicast traffic. For example, if only the priority threshold for unicast traffic is present, unicast traffic with a priority value less than or equal to the threshold (a higher priority) takes precedence over all MBS traffic. MBS traffic can have a higher priority than other unicast traffic that does not reach the threshold (i.e., is higher than the threshold). Alternatively, if only the priority threshold for unicast traffic is present, MBS traffic can take priority over unicast traffic whose priority value is greater than or equal to the threshold (a lower priority), and all unicast traffic that does not meet the threshold (i.e., below the threshold) takes priority over MBS traffic. For another example, if only the priority threshold is present for MBS traffic, MBS traffic with a priority value less than or equal to the threshold (a higher priority) takes precedence over all unicast traffic, and some unicast traffic can be excluded through a stipulation in a protocol. Unicast traffic can have a higher priority than other MBS traffic that does not reach the threshold (i.e., is higher than the threshold). Alternatively, if only the priority threshold for MBS traffic is present, unicast traffic can take priority over MBS traffic whose priority value is greater than or equal to the threshold (a lower priority), and all other MBS traffic that does not meet the threshold (i.e., below the threshold) takes priority over unicast traffic. For another example, if both the priority threshold for MBS traffic and the priority threshold for unicast traffic are present, the following can be stipulated: MBS traffic has priority when an MBS traffic priority value is less than or equal to a corresponding threshold (one priority is higher) and a unicast traffic priority value is greater than or equal to a corresponding threshold (one priority is lower); otherwise, unicast traffic has priority. Alternatively, if both the priority threshold for MBS traffic and the priority threshold for unicast traffic are present, the following may be stipulated: Unicast traffic takes priority when a priority value for unicast traffic is less than or equal to a corresponding threshold (one priority is higher) and a priority value for MBS traffic is greater than or equal to a corresponding threshold (one priority is lower); otherwise, MBS traffic takes priority. Optionally, if the first mode is PTM mode, the above procedure for generating the MBS traffic-related configuration information in the DU may include: determine, by DU, a target cell and / or a target frequency; reserve, by the DU in the target cell and / or target frequency, a resource required for MBS traffic; and generate, by the DU based on the reserved resource, the configuration information iviA / a / ¿u¿ó / uu 11 uu related to MBS traffic. For example, MBS traffic is typically periodic and has a specific requirement for a guaranteed bit rate. In this case, a suitable periodic resource can be reserved for service transmission based on a corresponding cycle and rate, and a specific retransmission resource can be reserved according to the service's block error rate requirement. For example, if the required block error rate is high, such as less than 10Λ, a specific retransmission is necessary to guarantee the block error rate requirement. Furthermore, a periodic offset can be selected for the periodic traffic based on the current state of other traffic. In this application mode, if the first mode is PTM mode, the DU can determine the target cell and / or target frequency in different ways. This is described separately below. (1) The first signaling includes the cell information expected by the CU, and the target cell is a cell, among the cells corresponding to the cell information, that successfully performs the acceptance; and / or the first signaling includes the frequency information expected by the CU, and the target frequency is a frequency, among the frequencies corresponding to the frequency information, that successfully performs the acceptance. It can be understood that when the CU has selected a cell and / or frequency to transmit MBS traffic in PTM mode, the initial signaling may include the cell and / or frequency information expected by the CU. There may be more than one piece of cell and / or frequency information; that is, there may be multiple pieces of cell and / or frequency information. In this case, the DU can reserve and configure a resource on only one cell and / or frequency expected by the CU. If the cell / frequency expected by the CU cannot perform the acceptance, the DU returns acceptance failure information to the CU.If some cells / frequencies expected by the CU can successfully perform the acceptance, the DU can return acceptance success information that includes detailed configuration information, and return acceptance failure information for a cell / frequency that cannot perform the acceptance, where the acceptance failure information carries, for example, a cell ID / frequency ID of the cell / frequency that fails. Optionally, in the event that the cells corresponding to the expected cell information by the CU include a cell that fails to perform the acceptance, and / or the frequencies corresponding to the expected frequency information by the CU include a frequency that fails to perform the acceptance, the DU may transmit acceptance failure information to the CU, where the acceptance failure information may include information about the cell that fails to perform the acceptance and / or information about the frequency that fails to perform the acceptance. (2) The target cell is a cell that successfully performs the acceptance and is selected by the DU from the DU-related cells; and / or the target frequency is a frequency that successfully performs the acceptance and is selected by the DU from the DU-related frequencies. It can be understood that the CU may alternatively not determine a specific cell and / or frequency to transmit MBS traffic in PTM mode. In this case, the DU may select one or more cells / frequencies based on the resources, coverage, and other cell and frequency states managed by the DU, perform acceptance on the cells / frequencies, and return specific configuration information to the base station for a cell / frequency that successfully performs acceptance. Furthermore, because the CU does not specify a cell / frequency, acceptance failure information is returned to the CU only if no cell / frequency can perform acceptance; otherwise, it is not necessary to return acceptance failure information as long as a cell / frequency can successfully perform acceptance. (3) The first signaling includes the cell type information expected by the CU, and the target cell is a cell that successfully performs the acceptance and is selected by the DU based on the cell type information of the cells related to the DU; and / or the first signaling includes the frequency type information expected by the CU, and the target frequency is a frequency that successfully performs the acceptance and is selected by the DU based on the frequency type information of the frequencies related to the DU. It can be understood that when the CU has selected a cell type and / or frequency type to transmit MBS traffic in PTM mode, the initial signaling may include the cell type and / or frequency type information expected by the CU. In this case, the DU can select a cell and / or frequency based on the cell type and / or frequency type information, and reserve and configure a resource on that cell and / or frequency. It can be understood that the unicasting unit (UD) generally distinguishes between PTP-mode acceptance for a single unicast unit (UE) and PTM-mode acceptance. This is because PTP transmission is clearer, and the UD has specific information about the UE, such as link state, and can estimate, based on the UE's link state and similar data, the size of a resource required to transmit MBS traffic when a given bit rate needs to be guaranteed. In PTM mode, an inefficient link assumption is used. For example, normal reception for a UE at a cell edge must be guaranteed. The resource size calculated in this way, and required to achieve the guaranteed bit rate needed to transmit MBS traffic, may differ from, and is typically larger than, the unicast resource size. Furthermore, for a PTP mode configuration for a single UE, an existing UE state, such as an existing bearer configuration, must be considered. An LCID for multicast traffic must be distinguished from an existing unicast LCID. An existing DRX cycle, offset, and similar parameters are also changed based on the characteristics of the multicast traffic. Regarding DU cell information, because the UE is in a connected state, the DU is fully aware of the UE's current serving cell configurations. Typically, a DRB corresponding to MBS traffic can be transmitted on any existing serving cell. Alternatively, the DU can add a new serving cell for the UE based on resource and service states to ensure good transmission and QoS guarantees for both the existing unicast traffic and the new MBS. Optionally, after receiving the MBS traffic-related configuration information from the DU, the CU can transmit the target configuration information to the terminal using any of the following: broadcast RRC signaling, multicast RRC signaling, dedicated RRC signaling, or a System Information Block (SIB). The target configuration information includes the MBS traffic-related configuration information, or the target configuration information includes updated MBS traffic-related configuration information. Optionally, the CU needs to perform a first operation before transmitting the first signal to the DU. The first operation includes any of the following: determine to transmit MBS traffic in the first mode; and determine to change a transmission mode for MBS traffic to the first mode. In addition, the CU can perform the first operation based on at least one of the following: MBS traffic information of interest collected by the CU; a request for a suggestion from the DU; MBS traffic measurement information reported by the DU; and auxiliary information or request information transmitted by a core network node, for example, auxiliary information or request information can be transmitted using an NG interface signaling procedure. That is, the determination, by the CU, to transmit MBS traffic in the first mode or the determination to change a transmission mode for MBS traffic to the first mode can be activated by the CU, based on the suggestion request of the DU, or on the basis of an indication or a request from the core network node. Optionally, if the CU performs the activation, one method for collecting MBS traffic information of interest may include at least one of the following: (1) The CU activates the terminal to report MBS traffic information of interest. For example, when network-side resources are insufficient, learned MBS traffic interest information has expired, or the CU needs to collect interest information for a specific TMGI / TMGI list in another CU-based implementation, the CU can collect interest information for a related TMGI / TMGI list using a signaling procedure, such as broadcast signaling, multicast RRC signaling, or dedicated RRC signaling. The signaling carries a corresponding MBS traffic list to be collected, such as a TMGI list. After receiving the information collection signaling from the network side, the UE with interest reports its MBS traffic interest information to the CU base station using dedicated RRC, for decision-making by the CU base station. (2) The terminal actively reports MBS traffic interest information. For example, the UE actively reports and updates the MBS traffic reception or interest status. At least for the UE in an RRC-connected state, when a function change for MBS traffic interest or reception status is enabled on the network side—for example, the function change could be an identifier in a SIB or an identifier in dedicated RRC signaling—and when the UE is interested in or receiving MBS traffic, the UE needs to report the MBS traffic information list to the network in a timely manner. In the case of an update—for example, a new service arrives, reception ends, interest is no longer shown, or a new interest joins—the UE also reports the latest status in a timely manner, for example, a TMGI list.The network side can assess, based on a list of services in which the UE is interested, the number of UEs interested in the service, thus facilitating decision-making by the CU. Optionally, a triggering condition for the DU's suggestion request may stem from a resource occupancy issue, a transmission efficiency issue, a terminal feedback status, or similar. The DU may be unable to determine whether to transmit MBS traffic in PTP / PTM mode or change the transmission mode for MBS traffic to PTP / PTM mode and, therefore, may suggest to the CU that the operation be performed. The triggering condition for the DU's suggestion request may include, but is not limited to, at least one of the following: (a) The use of a target resource meets a first preset condition. The first preset condition can be preset according to an actual requirement. For example, the DU can provide a suggestion on changing the PTP / PTM mode based on current resource usage. For example, if current resources are abundant and the cell resource load is quite low, PTP mode can be recommended to achieve a better transmission effect; or if current resource occupancy is quite high and the cell resource load is quite high, PTM mode can be recommended to reduce the resources consumed by MBS traffic. (b) The transmission efficiency of a target resource meets a second preset condition. The second preset condition can be preset according to an actual requirement. For example, the DU can provide a suggestion on changing the PTP / PTM mode based on the current transmission efficiency. For example, if the DU finds that the resource consumption of N PTP loads is much higher than the resource consumption of PTM loads, the DU can request the CU to switch to PTM mode; or if the PTM UE provides feedback that the transmission efficiency in PTP mode is higher, the DU can request the CU to switch to PTP mode. (c) A terminal feedback state meets a third preset condition. The third preset condition can be preset according to an actual requirement. For example, the DU might provide a suggestion to change the PTP / PTM mode based on a feedback state from the interested UE. For example, MBS traffic is configured to support HARQ feedback. When no feedback is received, or only a few comments are received in a feedback location, it can be assumed that most UEs have left or are no longer interested, and the DU requests the CU to change the mode. Alternatively, in PTP feedback detection, if PTM is deemed more efficient, the DU requests the CU to change the mode. (d) Another form of requesting suggestions implemented by the DU. In addition, the CU is a centralized control node and can configure measurement information about MBS traffic to the DU by using Fl interface signaling, for example, adding an MBS measurement requirement to the existing reporting configuration information or configuring MBS traffic measurement information by using new signaling, for example, an MBS Resource Status Reporting Indication. Optionally, in this application mode, the CU can transmit a second signal to the DU, where the second signal is used to configure the MBS traffic measurement information. The existing Fl interface signal can be reused as the second signal, or a new signal can be used. Optionally, MBS traffic measurement information may include at least one of the following: (1) Total use of MBS traffic resources in PTM mode and / or PTP mode. (2) Use of resources for each MBS traffic in PTM mode and / or PTP mode. (3) Use of MBS traffic resources in a preset MBS traffic list in PTM mode and / or PTP mode. Optionally, in PTM mode, resource usage in (1) to (3) can be the average number of occupied periodic physical resource blocks (PRBs), for example, the number of PRBs occupied by MBS traffic in N milliseconds, subframes, slots, or other units, or the total number of PRBs. N is a mean value for continuous evaluation. For example, 0-N, N-2N, and 2N-3N each have a measurement value, and the average number of occupied periodic PRBs is obtained using an arithmetic mean or a filtered mean. Alternatively, resource usage can be the number of resources occupied in a specific periodic pattern. For example, the measurement is performed in M ​​units of every N milliseconds, subframes, slots, or other units, where N > M, and M is an on-stage DRX of the service, i.e., MBS traffic is transmitted only within an interval of M, and is not transmitted in other intervals.The number of PRBs occupied by MBS traffic is measured in M ​​units or the total number of PRBs. Alternatively, the arithmetic mean, filtered average, or similar can be performed over a plurality of N cycles. Optionally, in PTP mode, resource usage in (1) to (3) can be the average number of occupied periodic PRBs, for example, the number of PRBs occupied by a DRB used for MBS transmission, in N milliseconds, subframes, slots, or other units, or the total number of PRBs. N is a mean value for continuous evaluation. For example, 0-N, N-2n, and 2N-3N each have a measurement value, and the average number of occupied periodic PRBs is obtained using an arithmetic mean or a filtered mean. Alternatively, resource usage can be the number of resources occupied in a specific periodic pattern. For example, the measurement is taken in M ​​units of every N milliseconds, subframes, slots, or other units, where N > M, and M is a DRX in the MBS traffic scenario; that is, MBS traffic is transmitted only within an interval of M and is not transmitted in other intervals.The number of PRBs occupied by a DRB used for MBS transmission is measured in M ​​units, or the total number of PRBs. Alternatively, the arithmetic mean, filtered mean, or similar can be performed over a plurality of N cycles. (4) Total use of MBS traffic resources in PTP mode for each terminal or for a given one. (5) Use of resources for each MBS traffic in PTP mode for each terminal or for a given one. (6) Use of MBS traffic resources in a preset MBS traffic list in PTP mode for each or a given terminal. (7) Feedback information for MBS traffic in PTM mode. For example, if feedback, such as HARQ feedback, is enabled for MBS traffic transmitted in PTM mode, information related to HARQ feedback can be collected, such as HARQ correction rate, retransmission probability, and link quality information from the worst endpoint. (8) For MBS traffic in PTP mode, terminal information that specifies or meets a fourth preset condition and is configured to be reported. For example, terminal information is link quality information. (9) Total number of active terminals for MBS traffic in PTM mode. (10) Number of active terminals per MBS traffic in PTM mode. (11) Number of active terminals for a given MBS traffic in PTM mode. (12) Number of active terminals for MBS traffic in a preset MBS traffic list in PTM mode. Optionally, the number in (9) to (12) can be a specific value, or a reported indication of being greater than or less than a threshold. Typically, the UE number can be determined based on HARQ feedback. (13) Hardware loading of PTM mode and / or PTP mode. Optionally, the hardware load of (13) can be determined on the basis of all MBS traffic, or determined on the basis of each MBS traffic, or determined on the basis of a pre-established MBS traffic list. (14) Remaining capacity of PTM mode and / or PTP mode. Optionally, the remaining capacity in (14) can be determined on the basis of all MBS traffic, or determined on the basis of each MBS traffic, or determined on the basis of a pre-established MBS traffic list. It should be noted that all measurement information in (1) to (14) can be configured to be reported periodically or when triggered by an event. When a reporting condition is met, the DU reports the corresponding measurement information to the CU, so that the CU determines or changes the PTP / PTM mode. In this application modality, a UE-related procedure, such as a UE RRC procedure, primarily involves the generation and transmission of broadcast, multicast, or dedicated RRC signaling. A generation procedure is described above. Some information, such as configurations in an RLC layer and lower layers, may be generated by the DU and transmitted to the CU. The CU combines this information with some of the information generated by the CU, such as configurations in a PDCP layer and higher layers, to form RRC signaling and transmits the RRC signaling to the UE through an air interface of the DU. Typical procedures include an MBS PTM / PTP signaling configuration procedure, activation of MBS traffic interest collection and counting, and similar procedures.In a UE uplink reporting procedure, for example, the MBS Counting response or MBS Interest Indication can be transmitted using a UL unicast SRB 1. The transmission of this information between the DU and CU is the same as for a conventional Uu SRB. This application is described in detail below with reference to example 1 through example 3. EXAMPLE 1 Example 1 describes in detail how to establish a PTM transmission mode for MBS traffic on one side of the base station. A prerequisite is as follows: A CU has determined, based on a service interest information gathering result from a core network or the CU itself, that MBS traffic should be transmitted in a PTM mode. For example, the gathering result might show that the number of terminals of interest exceeds a specific threshold. A corresponding establishment procedure might include the following steps. Step 1: The CU transmits F1 interface signaling (i.e., first signaling) to a DU, where the signaling includes information about MBS traffic, and is used to notify the DU that MBS traffic will be transmitted in a PTM mode. Optionally, for information included in the F1 interface signaling and MBS traffic information, refer to the content above. The details are not described again here. Step 2: After receiving signaling from interface Fl, the DU learns that MBS traffic must be transmitted in PTM mode; determines a target cell and / or target frequency based on information about MBS traffic; reserves, in the target cell and / or target frequency, a resource required for MBS traffic; and generates the corresponding configuration information. Step 3: The DU returns to the CU a list of cells that successfully perform the acceptance and the corresponding configuration information. Optionally, by returning the list of cells that successfully performed the acceptance and the corresponding configuration information, the DU can establish related MRB bearers, for example, a corresponding RLC entity, on these cells based on the configuration information, to prepare for subsequent multicast transmission of MBS traffic. Step 4: After receiving the configuration information fed back by the DU, the CU learns from the specific configuration information in the cells that successfully perform the acceptance, organizes the configuration information into broadcast signaling, multicast RRC signaling, or unicast RRC signaling, and transmits the signaling to the UE using the DU, so that the UE interested in the service can obtain configuration information and service scheduling information. Step 5: When the service starts, the CU transmits, using an established PTM configuration channel, MBS traffic related to a cell, from the DU, that belongs to the PTM transmission. Step 6: After receiving MBS traffic, the DU schedules a resource for the MBS traffic data based on a configured cycle and offset and by using a configured g-RNTI, and transmits a service data packet on the scheduled resource. It should be noted that if the UE receives configuration information about MBS traffic, it can establish a corresponding MRB bearer based on the content of that configuration information. This MRB bearer can include an SDAP entity, a PDCP entity, and / or an RLC entity. A MAC entity can perform the corresponding MBS PTM reception by scheduling, decoding, and receiving data at a specific cycle location using a related cycle configuration and a configured g-RNTI. EXAMPLE 2 Example 2 describes in detail how to establish a PTP transmission mode for MBS traffic on one side of the base station. A prerequisite is as follows: A CU has determined, based on a CU service interest information gathering result, that MBS traffic should be transmitted in a PTP mode for a specific UE. For example, the gathering result might show that the number of terminals of interest is below a specific threshold. A corresponding establishment procedure might include the following steps. Step 1: The CU transmits the F1 interface signaling (i.e., the first signaling) to a DU, where the signaling is a signaling associated with the UE, includes information about MBS traffic, and is used to notify the DU that MBS traffic will be transmitted in a PTP mode. Optionally, for information included in the F1 interface signaling and MBS traffic information, refer to the previous content. The details are not described again here. It should be noted that, because the transmission is in unicast mode, a priority can be assigned to MBS traffic transmitted in PTP mode, which can be directly compared to that of unicast traffic, for comparison with other unicast traffic. Step 2: After receiving signaling from interface Fl, the DU learns that MBS traffic should be transmitted to the UE in PTP mode; reserves, based on information about MBS traffic, a resource required for the service; and generates the corresponding configuration information. Step 3: The DU returns UE acceptance and configuration information to the CU. If acceptance is successful, the configuration information is returned; otherwise, acceptance error information is returned. Optionally, the DU can establish a corresponding RLC bearer, for example, an RLC entity, for the UE while returning the UE's acceptance and configuration information to the CU, and waits for the subsequent arrival of MBS traffic and performs the transmission. Step 4: After receiving the configuration information fed back by the DU, the CU learns the PTP configuration information specific to the UE, organizes the configuration information into dedicated RRC signaling, and transmits the signaling to the UE using the DU, so that the UE can obtain configuration information and service scheduling information. Step 5: When the service starts or a data packet arrives, the CU transmits, to the DU using an established PTP configuration channel, the MBS traffic related to the UE. Step 6: After receiving the MBS traffic packet, the DU schedules a resource for the service data based on a configured cycle and offset and using a UE CCNTI, and transmits a service data packet on the scheduled resource. It should be noted that if the UE receives RRC reconfiguration information from a DRB (for example, one carrying a TMGI or other identifier) ​​corresponding to MBS traffic, the UE can establish a corresponding DRB bearer based on the content of the reconfiguration information. This DRB bearer may include an SDAP entity, a PDCP entity, and / or an RLC entity. A MAC entity can perform the corresponding MBS PTP reception by scheduling, decoding, and receiving data at a specific cycle location using a related cycle configuration and the C-RNTI. EXAMPLE 3 In example 3, when a CU determines to perform the PTP / PTM mode change, a specific procedure may include the following steps. Step 1: The CU transmits a resource and configuration request for a target mode to a DU. For example, in the case of switching to a PTM mode, a signaling procedure not associated with the UE (namely, first signaling) is used to establish the MBS PTM mode, as described in Example 1; or in the case of switching to a PTP mode, a signaling procedure associated with the UE (i.e., first signaling) is used to establish the MBS PTP mode, as described in Example 2. Step 2: The DU receives the request, accepts it, generates configuration information, and returns the configuration information to the CU. This is similar to the procedure in Example 1 or Example 2. Specifically, if the mode change request is triggered by the DU to the CU, when triggering the request, the DU can also add an acceptance result and configuration for the target mode to the CU, thus preventing the CU from requesting acceptance and configuration from the DU again, and reducing delay. The details are as follows: (1) If the target mode is PTM mode, because a related QoS requirement is also transmitted to the DU during PTP establishment for MBS traffic, PTM and PTP do not affect the QoS requirement, or the way it affects it is known to the DU (stipulated in a protocol or configured by the CU), and the DU can directly perform the acceptance and generate a configuration according to the QoS requirement. (2) If the target mode is PTP mode, the DU can generate, based on an activation state of the UE known to the DU, a PTP configuration corresponding to the UE; or provide a universally recommended configuration without specifying a specific UE, and provide the number of UEs that can be accepted. Optionally, after the CU receives the acceptance and configuration result for the target mode in the previous procedure of requesting the DU or actively triggering the report by the DU, the CU can decide to change the mode, organize an RRC message, and transmit the message to the UE using broadcast, multicast, or dedicated signaling. After receiving the switchover message, the UE performs service reception in the new mode. It can be understood that the previous modality basically describes a control plane procedure, and the following describes a user plane procedure, which is mainly the establishment and maintenance of an Fl-U tunnel (Fl interface user plane). Optionally, the first mode is PTM mode, meaning the MBS traffic transmission mode configured between the CU and the DU is PTM mode, and the CU corresponds to a plurality of DUs. In this case, a user-plane tunnel can be established between the CU and each DU; or a user-plane multicast tunnel can be established between the CU and the plurality of DUs. For example, the MBS traffic transmission mode configured between the CU and the DU is PTM mode. This is equivalent to multiple cells from a DU, or cells from multiple DUs corresponding to a CU, transmitting the same service data. In this case, a TMGI tunnel can be established between the CU and each involved DU. For example, when N DUs are involved, there are N equivalent channels, such as a GTP-U tunnel, used to transmit MBS traffic from the CU to the DU. Alternatively, a multicast TMGI tunnel can be established between the CU and each involved DU. For example, when N DUs are involved, it is also a single tunnel. A specific multicast address can be used for the multicast TMGI tunnel. For example, a multicast IP address or a multicast Transport Network Layer (TNL) address is used for identification.After the DU joins the multicast, the DU listens to the data in the corresponding multicast direction. Optionally, the first mode is PTP mode (corresponding to PTP mode 1 above). The CU corresponds to a plurality of DUs. The CU maintains a unified user plane foreground entity, for example, an SDAP entity and a PDCP entity, per terminal, and the plurality of DUs each maintain a second user plane entity, for example, an RLC entity, a MAC entity, and a PHY entity, for each terminal. In this case, a user plane tunnel can be established between the CU and each DU; or a user plane multicast tunnel can be established between the CU and the plurality of DUs. For example, the MBS traffic transmission mode configured between the CU and the DU is the previous PTP mode 1. As shown in Figure 5, in this case, a TMGI tunnel can be established between the CU and each involved DU. For example, when N DUs are involved, there are N equivalent channels, such as a GTP-U tunnel, used to transmit MBS traffic from the CU to the DU. Alternatively, a multicast TMGI tunnel can be established between the CU and each involved DU. For example, when N DUs are involved, it is also a single tunnel. A specific multicast address can be used for the multicast TMGI tunnel. For example, a multicast IP address or a multicast TNL address is used for identification. After the DU joins the multicast, it listens for data on the corresponding multicast address. Optionally, the first mode is PTP mode (corresponding to PTP mode 2 above), and the CU and DU maintain a unified user-plane foreground entity and a unified user-plane background entity for each terminal. For example, the first user-plane entity is an SDAP entity and a PDCP entity, and the second user-plane entity is an RLC entity, a MAC entity, and a PHY entity. In this case, a separate user-plane tunnel can be established between the CU and DU for each terminal; or a distinguishable user-plane multicast tunnel can be established between the CU and DU for each terminal. For example, the MBS traffic transmission mode configured between the CU and the DU is the previous PTP mode 2. As shown in Figure 6, a tunnel is established for each terminal (per UE) between the CU and the DU. In this case, a separate or distinguishable tunnel needs to be established for each UE's PTP service. A separate tunnel means that a separate GTP-U tunnel with a separate ID is established for each MBS PTP service corresponding to a specific TMGI. For example, a Tunnel Endpoint Identifier (TEID) is used for distinction. After establishing a separate tunnel between the CU and the DU for each UE, the service data corresponding to a specific TMGI of the corresponding UE is transmitted over the tunnel. A distinguishable tunnel means that a tunnel can be shared with other MBS PTP services.However, an internal flow, for example, a GTP-U header, carries a TMGI identifier to distinguish between different MBS traffic. Even a unicast tunnel from the corresponding UE can be reused. Nevertheless, MBS traffic must also be clearly identified and a specific TMGI is carried to distinguish between different services. It can be understood that, after the Fl-U tunnel is clearly established and maintained, the DU transmits the PTM data received on an air interface in PTM mode according to a configuration, and transmits the PTP data on the air interface in unicast mode. It should be noted that the information control method provided in the terms of this application may be performed by an information control device or by a control module within the information control device that is configured to perform the information control method. In the terms of this application, an information control device provided herein is described using an example in which the device performs the information control method. Figure 8 is a schematic structural diagram of an information control apparatus according to one modality of this application. The information control apparatus is applied to a base station. As shown in Figure 8, the information control apparatus 80 includes a CU 81 and a DU 82. Optionally, CU 81 is configured to transmit the first signaling to DU 82, where the first signaling includes information about MBS traffic, and the information about MBS traffic is used to indicate that DU 82 transmits MBS traffic in a first mode; And DU 82 is configured to generate configuration information related to MBS traffic and transmit the configuration information to CU 81. Optionally, the first mode includes any of the following: a PTM mode and a PTP mode. Optionally, the first signaling also includes at least one of the following: cell information and / or expected frequency information for the CU; cell type information and / or expected frequency type information for the CU; priority information on MBS traffic; information on a comparison between MBS traffic priority and unicast traffic priority; Information on whether MBS traffic can be overridden by other MBS traffic and / or unicast traffic; and information on whether MBS traffic can override other MBS traffic and / or unicast traffic. Optionally, information on a comparison between MBS traffic priority and unicast traffic priority includes at least one of the following: MBS traffic priority being higher, lower, or equal to the unicast traffic priority; report information from a terminal regarding MBS traffic priority and unicast traffic priority; a priority threshold for MBS traffic; a priority threshold for unicast traffic; and a priority threshold for MBS traffic and a priority threshold for unicast traffic. Optionally, the first mode is PTM mode, and the DU 82 includes: a determination module, configured to determine a target cell and / or a target frequency; a reservation module, configured to reserve, in the target cell and / or target frequency, a resource required for MBS traffic; and a generation module, configured to generate, based on the reserved resource, the configuration information related to MBS traffic. Optionally, the first signaling includes the cell information expected by the CU, and the target cell is a cell, among the cells corresponding to the cell information, that successfully performs the acceptance; and / or the first signaling includes the frequency information expected by the CU, and the target frequency is a frequency, among the frequencies corresponding to the frequency information, that successfully performs the acceptance. Optionally, in case the cells corresponding to the cell information include a cell that does not perform the acceptance, and / or the frequencies corresponding to the frequency information include a frequency that does not perform the acceptance, DU 82 is further configured to transmit the acceptance failure information to CU 81, where the acceptance failure information includes information about the cell that fails to perform the acceptance, and / or information about the frequency that fails to perform the acceptance. Optionally, the target cell is a cell that successfully performs the acceptance and is selected by the DU from the cells related to the DU; and / or the target frequency is a frequency that successfully performs the acceptance and is selected by the DU from the frequencies related to the DU. Optionally, the first signaling includes information on the cell type expected by the CU, and the target cell is a cell that successfully performs the acceptance and is selected by the DU based on the cell type information of the cells related to the DU; and / or the first signaling includes information on the frequency type expected by the CU, and the target frequency is a frequency that successfully performs the acceptance and is selected by the DU based on the frequency type information of the frequencies related to the DU. Optionally, CU 81 can also be configured to: transmit destination configuration information to a terminal using any of the following: RRC broadcast signaling, RRC multicast signaling, dedicated RRC signaling and a SIB, where the target configuration information includes configuration information related to MBS traffic, or the target configuration information includes updated configuration information related to MBS traffic. Optionally, CU 81 is further configured to perform a first operation, where the first operation includes any of the following: determining to transmit MBS traffic in the first mode; and determining to change a transmission mode of MBS traffic to the first mode. Optionally, CU 81 is further configured to perform the first operation based on at least one of the following: MBS traffic information of interest collected by the CU; a request for a suggestion from the DU; MBS traffic measurement information reported by the DU; and auxiliary information or request information transmitted by a central network node. Optionally, a method for collecting information of interest for MBS traffic includes at least one of the following: The CU activates the terminal to communicate MBS traffic information of interest; and the terminal actively notifies MBS traffic information of interest. Optionally, an activation condition for the DU suggestion request includes at least one of the following: The use of an objective resource fulfills a first pre-established condition; The transmission efficiency of a target resource meets a second pre-established condition; and a terminal feedback state meets a third pre-established condition. Optionally, CU 81 is also configured to transmit a second signal to the DU, where the second signal is used to configure MBS traffic measurement information. Optionally, MBS traffic measurement information includes at least one of the following: total MBS traffic resource occupancy in PTM mode and / or PTP mode; resource occupancy of each MBS traffic in PTM mode and / or PTP mode; MBS traffic resource occupation in a pre-established MBS traffic list in PTM mode and / or PTP mode; total occupancy of MBS traffic resources in PTP mode for each terminal or for a specific one; resource occupancy of each MBS traffic in PTP mode for each or a given terminal; MBS traffic resource occupancy in a pre-set MBS traffic list in PTP mode for each or a given terminal; feedback information for MBS traffic in PTM mode; For MBS traffic in PTP mode, terminal information that specifies or meets a fourth preset condition and is configured to be reported; total number of active terminals for MBS traffic in PTM mode; number of active terminals per MBS traffic in PTM mode; number of active terminals for a given MBS traffic in PTM mode; number of active terminals for MBS traffic in a preset MBS traffic list in PTM mode; hardware load of PTM mode and / or PTP mode; and remaining capacity of PTM mode and / or PTP mode. Optionally, the first mode is PTM mode, CU 81 corresponds to a plurality of DU 82, and CU 81 is further configured to perform any of the following: establish a user plane tunnel between CU 81 and each DU 82; and establish a user plane multicast tunnel between CU 81 and the plurality of DU 82. Optionally, the first mode is PTP mode, CU 81 corresponds to a plurality of DU 82, and when CU 81 maintains a unified first user plane entity for the terminal and the plurality of DU 82 each maintains a second user plane entity for each terminal, CU 81 is further configured to perform any of the following: establish a user plane tunnel between CU 81 and each DU 82; and establish a user plane multicast tunnel between CU 81 and the plurality of DU 82. Optionally, the first mode is PTP mode, CU 81 and DU 82 maintain a unified user plane foreground entity and a unified user plane background entity for each terminal, and CU 81 is further configured to do any of the following: establish a separate user plane tunnel between CU 81 and DU 82 for each terminal; and establish a distinguishable user plane multicast tunnel between CU 81 and DU 82 for each terminal. The information control device 80 provided in this version of this application is capable of implementing the procedures implemented in the version of the method shown in Figure 7, with the same technical effects achieved. To avoid repetition, the details are not described again here. Optionally, as shown in Figure 9, one embodiment of this application further provides a base station 90, which includes a processor 91, a memory 92, and a program or instructions stored in memory 92 and capable of execution by the processor 91. When the program or instructions are executed by the processor 91, the procedures of the embodiment of the method shown in Figure 7 are implemented, with the same technical effects achieved. To avoid repetition, the details are not described again here. Optionally, one version of this application also provides a base station 100. As shown in Figure 10, base station 100 includes an antenna 101, a radio frequency device 102, and a baseband device 103. Antenna 101 is connected to radio frequency device 102. In an uplink direction, radio frequency device 102 receives information using antenna 101 and sends the received information to baseband device 103 for processing. In a downlink direction, baseband device 103 processes the information to be sent and sends it to radio frequency device 102; and radio frequency device 102 processes the received information and then sends it using antenna 101. The baseband apparatus 103 may include, for example, at least one baseband processing unit, where a plurality of chips are arranged in the baseband processing unit. As shown in Figure 10, one of the chips is, for example, the processor 104, and is connected to memory 105, to invoke the program in memory 105 to perform the network device operations shown in the mode of the previous method. The baseband apparatus 103 may further include a network interface 106, configured to exchange information with the radio frequency apparatus 102, where the interface is, for example, a common public radio interface (CPRI for short). Specifically, the base station 100 in this application mode uses a CU-DU architecture and also includes instructions or a program stored in memory 105 and capable of execution by processor 104. Processor 104 then invokes the instructions or program in memory 105 to perform the method shown in Figure 7, achieving the same technical effects. To avoid repetition, the details are not described again here. One version of this application also provides a readable storage medium. The readable storage medium stores a program or instructions. When the program or instructions are executed by a processor, the procedures of the method version shown in Figure 7 are implemented, achieving the same technical effects. To avoid repetition, the details are not described again here. The processor is a processor in the base station in the previous modes. The readable storage medium includes a computer-readable storage medium, for example, a computer read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk. One embodiment of this application further provides a chip. The chip includes a processor and a communications interface. The communications interface is coupled to the processor. The processor is configured to execute a program or instructions for a network-side device, to implement the procedures of the embodiment of the method shown in Figure 7, with the same technical effects achieved. To avoid repetition, the details are not described again here. It should be understood that the chip mentioned in this form of this application may also be called a system-level chip, system chip, system-on-a-chip, or similar. It should be noted that, in this specification, the terms "include," "comprise," or any of their variants are intended to cover a non-exclusive inclusion, such that a procedure, method, article, or apparatus that includes a set of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent in such procedure, method, article, or apparatus. In the absence of further restrictions, an element preceded by the statement "includes a..." does not preclude the existence of other identical elements in the procedure, method, article, or apparatus that includes the element. Furthermore, it should be noted that the scope of the method and apparatus in the implementations of this application is not limited to performing functions in the sequence shown or discussed, and may also include performing functions substantially simultaneously or in a reverse sequence, depending on the functions involved.For example, the described method can be performed in a different sequence, and steps can be added, omitted, or combined. Furthermore, features described with reference to some examples can be combined in other examples. From the preceding description of the implementations, a subject matter expert can clearly understand that the method described above can be implemented using software with a general hardware platform. Certainly, the method described above can also be implemented using hardware. However, in many cases, the former is the preferred implementation. Based on this understanding, the technical solutions of this application, or a portion thereof that contributes to the technique described above, can be incorporated into a software product.The computer software product is stored on a storage medium (e.g., ROM / RAM, magnetic disk, or optical disk) and includes several instructions to instruct a terminal (which may be a mobile phone, computer, server, air conditioner, network device, or similar) to perform the method described in the modalities of this application. It should be understood that the division of a device into modules is simply a division of logical function. Modules may be fully or partially integrated into a physical entity, or they may be physically separate in an actual implementation. Furthermore, all modules may be implemented as software invoked by a processing component, or they may all be implemented as hardware; or some modules may be implemented as software invoked by a processing component, and others as hardware. For example, a determination module may be a processing component that is separately available, or it may be integrated into a chip of the device for implementation.Furthermore, the determination module can be stored in the device's memory as program code and is invoked by a processing component to perform a function of the determination module. The implementation of other modules is similar. Additionally, the modules can be fully or partially integrated, or they can be implemented independently. Here, the processing component can be an integrated circuit and has signal processing capabilities. In an implementation procedure, the steps of the previous method or the modules described above can be implemented using a hardware integrated logic circuit in the processor component or using software instructions. For example, the modules, units, subunits, or submodules can be one or more integrated circuits configured to implement the method described above, such as one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs). Alternatively, when one of the five modules described above is implemented as program code invoked by a processing component, the processing component can be a general-purpose processor, such as a central processing unit (CPU), or another processor capable of invoking program code. Finally, the modules can be integrated into a system-on-a-chip (SoC) for implementation. The foregoing describes the embodiments of this application with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative rather than restrictive. As stated in this application, a person of ordinary skill in the art may develop many other embodiments without departing from the substance of this application and the scope of protection of the 15 claims, and all such embodiments will fall within the scope of protection of this application.

Claims

1. An information control method, applied to a base station, wherein the base station comprises a central unit (CU) and a distributed unit (DU), and the method comprises: transmitting the first signaling from the CU to the DU, wherein the first signaling comprises information about the MBS traffic of the multicast broadcast service, and the information about the MBS traffic is used to indicate that the DU transmits MBS traffic in a first mode; generating configuration information related to the MBS traffic in the DU; and transmitting the configuration information from the DU to the CU.

2. The method according to claim 1, further characterized in that the first mode comprises any of the following: a point-to-multipoint PTM mode and a point-to-point PTP mode.

3. The method according to claim 1, further characterized in that the first signaling further comprises at least one of the following: cell information and / or frequency information expected by the CU; cell type information and / or frequency type information expected by the CU; priority information on MBS traffic; information on the comparison between the priority of MBS traffic and the priority of unicast traffic; information on whether MBS traffic can be overridden by other MBS traffic and / or unicast traffic; and information on whether MBS traffic can override other MBS traffic and / or unicast traffic.

4. The method according to claim 3, further characterized in that the information on the comparison between the priority of MBS traffic and the priority of unicast traffic comprises at least one of the following: the priority of MBS traffic being higher, lower or equal to the priority of unicast traffic; reporting information from a terminal on the priority of MBS traffic and the priority of unicast traffic; a priority threshold for MBS traffic; a priority threshold for unicast traffic; and a priority threshold for MBS traffic and a priority threshold for unicast traffic.

5. The method according to claim 2, further characterized in that the first mode is the PTM mode, and the generation of configuration information related to MBS traffic in the DU comprises: determining, by the DU, a target cell and / or a target frequency; reserving, by the DU in the target cell and / or the target frequency, a resource required for MBS traffic; and generating, by the DU based on the reserved resource, the configuration information related to MBS traffic.

6. The method according to claim 5, further characterized in that the first signaling comprises the cell information expected by the CU, and the target cell is a cell, among the cells corresponding to the cell information, that successfully performs the acceptance; and / or the first signaling comprises the frequency information expected by the CU, and the target frequency is a frequency, among the frequencies corresponding to the frequency information, that successfully performs the acceptance.

7. The method according to claim 6, further characterized in that the cells corresponding to the cell information comprise a cell that fails to achieve acceptance, and / or the frequencies corresponding to the frequency information comprise a frequency that fails to achieve acceptance, and the method further comprises: transmitting acceptance failure information from the DU to the CU, wherein the acceptance failure information comprises information about the cell that fails to achieve acceptance, and / or information about the frequency that fails to achieve acceptance.

8. The method according to claim 5, further characterized in that the target cell is a cell that successfully performs acceptance and is selected by the DU from the cells related to the DU; and / or the target frequency is a frequency that successfully performs acceptance and is selected by the DU from the frequencies related to the DU.

9. The method according to claim 8, further characterized in that the first signaling comprises the cell type information expected by the CU, and the target cell is a cell that successfully performs the acceptance and is selected by the DU based on the cell type information of the cells related to the DU; and / or the first signaling comprises the frequency type information expected by the CU, and the target frequency is a frequency that successfully performs the acceptance and is selected by the DU based on the frequency type information of the frequencies related to the DU.

10. The method according to claim 1, further characterized in that after transmitting the configuration information from the DU to the CU, the method further comprises: transmitting destination configuration information to a terminal from the CU using any of the following: broadcast resource control RRC signaling, multicast RRC signaling, dedicated RRC signaling and a system information block (SIB), wherein the target configuration information comprises configuration information related to MBS traffic, or the target configuration information comprises updated configuration information related to MBS traffic.

11. The method according to claim 1, further characterized in that before transmitting the first signaling from the CU to the DU, the method further comprises: performing, by the CU, a first operation, wherein the first operation comprises any of the following: determining to transmit the MBS traffic in the first mode; and determining to change a transmission mode of the MBS traffic to the first mode.

12. The method according to claim 11, further characterized in that the performance of a first operation comprises: the UC performing the first operation based on at least one of the following: MBS traffic interest information collected by the CU; a suggestion request from the DU; MBS traffic measurement information reported by the DU; and auxiliary information or request information transmitted by a core network node.

13. The method according to claim 12, further characterized in that a form of collecting MBS traffic information of interest comprises at least one of the following: the CU activates the terminal to communicate MBS traffic information of interest; and the terminal actively notifies the MBS traffic information of interest.

14. The method according to claim 12, further characterized in that an activation condition for the DU suggestion request comprises at least one of the following: the use of a target resource satisfies a first pre-set condition; the transmission efficiency of a target resource satisfies a second pre-set condition; and a feedback state of the terminal satisfies a third pre-set condition.

15. The method according to claim 1 or 12, further characterized in that it further comprises: transmitting a second signaling from the CU to the DU, wherein the second signaling is used to configure MBS traffic measurement information.

16. The method according to claim 15, further characterized in that the MBS traffic measurement information comprises at least one of the following: total MBS traffic resource occupancy in PTM mode and / or PTP mode; resource occupancy of each MBS traffic in PTM mode and / or PTP mode; MBS traffic resource occupancy in a pre-established MBS traffic list in PTM mode and / or PTP mode; total MBS traffic resource occupancy in PTP mode for each terminal or for a given terminal; resource occupancy of each MBS traffic in PTP mode for each or a given terminal; MBS traffic resource occupancy in a pre-established MBS traffic list in PTP mode for each or a given terminal; feedback information for MBS traffic in PTM mode;For MBS traffic in PTP mode, terminal information that specifies or meets a fourth preset condition and is configured to be reported; total number of active terminals for MBS traffic in PTM mode; number of active terminals for each MBS traffic in PTM mode; number of active terminals for a given MBS traffic in PTM mode; number of active terminals for MBS traffic in a preset MBS traffic list in PTM mode; hardware load of PTM mode and / or PTP mode; and remaining capacity of PTM mode and / or PTP mode.

17. The method according to claim 2, further characterized in that the first mode is the PTM mode, the CU corresponds to a plurality of DUs, and the method further comprises any of the following: establishing a user plane tunnel between the CU and each DU; and establishing a user plane multicast tunnel between the CU and the plurality of DUs.

18. The method according to claim 2, further characterized in that the first mode is the PTP mode, the CU corresponds to a plurality of DUs, the CU maintains a unified user plane foreground entity for terminals, and the plurality of DUs each maintains a second user plane entity for each terminal, the method further comprising any of the following: establishing a user plane tunnel between the CU and each of the DUs; and establishing a user plane multicast tunnel between the CU and the plurality of DUs.

19. The method according to claim 2, further characterized in that the first mode is the PTP mode, the CU and the DU maintain a unified first-user-plane entity and a unified second-user-plane entity for each terminal, and the method further comprises any of the following: establishing a separate user-plane tunnel between the CU and the DU for each terminal; and establishing a distinguishable user-plane multicast tunnel between the CU and the DU for each terminal.

20. A base station, comprising a processor, a memory, and a program or instructions stored in the memory and capable of execution by the processor, wherein when the program or instructions are executed by the processor, the steps of the information control method are implemented in accordance with any of claims 1 to 19.

Images