An enhanced transmission method and apparatus for MBS messages

Abstract

This application discloses an enhanced transmission method for MBS messages. The network side allows the MTCH channel to be carried within a BWP that does not contain the complete Control Resource Set 0. The network side configures the RedCap terminal with an initial downlink BWP containing the complete Control Resource Set 0, and a RedCap-specific initial downlink BWP that does not contain the complete Control Resource Set 0; it also configures the frequency domain range of the MCCH channel to fall within the initial downlink BWP, and the frequency domain range of the MTCH channel to fall within the RedCap-specific initial downlink BWP. The RedCap terminal operates within the RedCap-specific initial downlink BWP in idle and inactive states; when the MCCH channel reception opportunity arrives, the RedCap terminal retunes to listen to the MCCH channel within its frequency resources and receives the MBS indication and control information carried by the MCCH channel. This application extends the MBS broadcast service from a BWP containing the complete Control Resource Set 0 to a BWP that does not contain the complete Control Resource Set 0, fully utilizing network resources and improving the MBS reception user experience for RedCap terminals.

Description

Technical Field

[0001] This application relates to a mobile communication technology, and more particularly to a method for a 5G NR (new radio) terminal (UE, user equipment) to receive MBS (multicast and broadcast services) messages. Background Technology

[0002] With the evolution of 5G mobile communication technology, the 3GPP Release 17 standard introduced MBS, providing an efficient group communication and scheduling mechanism that can distribute the same content to multiple users simultaneously. Currently, the 5G NR protocol stipulates that MBS messages can only be distributed to 5G terminals within the BWP (Band Width Part) containing the complete Control Resource Set #0 (CORESET#0 or CORESET 0). Figure 1 As shown, the initial downlink BWP contains the complete control resource set 0. The MBS CFR (common frequency resource) is within the frequency range of control resource set 0.

[0003] Under existing 5G NR technology, before executing the access procedure, the network configures the initial downlink BWP for the 5G terminal through SIB1 (System Information Block Type 1). The initial downlink BWP contains the complete control resource set No. 0, such as... Figure 2 As shown, this is used for downlink reception and cell access for 5G terminals. After the 5G terminal accesses the cell and enters the connected state (RRC_CONNECT), the network configures a dedicated downlink BWP for the 5G terminal through RRC (Radio Resource Control) signaling. The control resource set included in the dedicated downlink BWP may not be CORESET#0, but other control resource sets, such as control resource set #1 (CORESET#1), as... Figure 3 As shown. Alternatively, the control resource set contained in the dedicated downlink BWP is CORESET#0, such as... Figure 4 As shown.

[0004] In connected mode, if the 5G terminal's currently active BWP—either the initial downlink BWP or a dedicated downlink BWP—contains the complete set of control resources number 0, then... Figure 4As shown, the MBS CFR resources are within the frequency range of Control Resource Set 0. At this time, the 5G terminal can normally receive MBS broadcast services and maintain continuity in idle state (RRC_IDLE), inactive state (RRC_INACTIVE), or connected state. In connected state, if the currently active BWP—Dedicated Downlink BWP—of the 5G terminal does not contain the complete Control Resource Set 0, such as... Figure 5 As shown, the activated BWP cannot allocate MBS CFR resources in the connected state, which causes the UE to be unable to receive MBS broadcast services normally, and the MSB broadcast service has to be interrupted.

[0005] Lightweight (RedCap, reduced capability) 5G terminals are abbreviated as RedCap terminals, while non-RedCap terminals are abbreviated as ordinary 5G terminals. To avoid resource congestion caused by all 5G terminals concentrating cell measurements in the frequency domain near the CD-SSB (Cell-Defining SSB), lightweight 5G terminals support serving cell measurements in the NCD-SSB (Non-Cell-Defining SSB). This avoids the 5G terminal needing to repeatedly tune to the CD-SSB for measurements, thus preventing performance degradation. Here, SSB stands for Synchronization Signal Block. Please refer to [link to relevant documentation]. Figure 6 If a dedicated downlink BWP configured for a RedCap terminal in connected mode does not contain the complete Control Resource Set 0, but contains other control resource sets such as Control Resource Set 1, then the dedicated downlink BWP must contain an NCD SSB. Please refer to [link to relevant documentation]. Figure 7 If the dedicated downlink BWP configured for the RedCap terminal in connected mode does not contain the complete No. 0 control resource set, but contains other control resource sets such as No. 1 control resource set, the dedicated downlink BWP cannot allocate MBS CFR resources in connected mode, causing the UE to be unable to receive MBS broadcast services normally in connected mode. Summary of the Invention

[0006] The technical problem to be solved by this application is: when a RedCap terminal is working in a RedCap-specific initial downlink BWP that does not contain the complete No. 0 control resource set, or when a RedCap terminal is working in connected mode in a dedicated downlink BWP that does not contain the complete No. 0 control resource set, how to carry and support MBS services in these BWPs that do not contain the complete No. 0 control resource set, so that the RedCap terminal can support receiving MBS messages.

[0007] To address the aforementioned technical problems, this application proposes an embodiment of an enhanced MBS message transmission method, comprising the following steps: Step S11: The network side of the 5G mobile communication system limits the MCCH channel to be carried within a BWP containing the complete No. 0 control resource set, while allowing the MTCH channel to be carried within a BWP that does not contain the complete No. 0 control resource set. Step S12: The network side of the 5G mobile communication system configures an initial downlink BWP containing the complete No. 0 control resource set and a RedCap-specific initial downlink BWP that does not contain the complete No. 0 control resource set for the RedCap terminal; the network side of the 5G mobile communication system also configures the frequency domain range of the MCCH channel to fall within the initial downlink BWP, and also configures the frequency domain range of the MTCH channel to fall within the RedCap-specific initial downlink BWP. Step S13: The RedCap terminal operates within the RedCap-specific initial downlink BWP in idle and inactive states; when the MCCH channel reception opportunity arrives, the RedCap terminal retunes to listen to the MCCH channel within its frequency resources and receives the MBS indication and control information carried by the MCCH channel. Step S14: In the idle or inactive state, the RedCap terminal obtains the configuration information of the MTCH channel according to the MBS indication and control information, and receives the MBS service data carried by the MTCH channel on the frequency resources of the MTCH channel within the RedCap dedicated initial downlink BWP, in conjunction with the frequency domain information of the MTCH channel. Step S15: When the RedCap terminal transitions from the idle or inactive state to the connected state, the network side of the 5G mobile communication system configures multiple dedicated downlink BWPs for the RedCap terminal. At least one dedicated downlink BWP contains the complete set of control resources No. 0 and is called the first active BWP. At least one dedicated downlink BWP does not contain the complete set of control resources No. 0 and is called the second active BWP. The first active BWP contains the frequency domain range of the MCCH channel, and the second active BWP contains the frequency domain range of the MTCH channel. Step S16: The network side of the 5G mobile communication system configures the RedCap terminal to work on two different active BWPs at different time periods in the connected state; when the RedCap terminal is working on the first active BWP in the connected state, it listens to the MCCH channel and receives the MBS control information carried by the MCCH channel; when the RedCap terminal is working on the second active BWP in the connected state, it receives the MBS service data carried by the MTCH channel.

[0008] Furthermore, in steps S13 to S14, when the paging opportunity arrives, the RedCap terminal retunes to the paging frequency resource to listen for and receive signals in order to realize the paging function.

[0009] This application also proposes a second embodiment of an enhanced transmission method for MBS messages, comprising the following steps: Step S21: The network side of the 5G mobile communication system allows the MCCH channel to be carried within a BWP that does not contain the complete No. 0 control resource set, and simultaneously allows the MTCH channel to be carried within a BWP that does not contain the complete No. 0 control resource set. Step S22: The network side of the 5G mobile communication system configures a RedCap-specific initial downlink BWP for the RedCap terminal that does not contain the complete No. 0 control resource set. The network side of the 5G mobile communication system also configures the frequency domain range of the MCCH channel and the frequency domain range of the MTCH channel to both fall within the RedCap-specific initial downlink BWP. Step S23: The RedCap terminal operates within the RedCap-specific initial downlink BWP in both idle and inactive states; when the reception opportunity for the MCCH channel arrives, the RedCap terminal listens to the MCCH channel within the MCCH channel frequency resources and receives the MBS indication and control information carried by the MCCH channel. Step S24: In idle or inactive states, the RedCap terminal obtains the configuration information of the MTCH channel according to the MBS indication and control information. Combining this with the frequency domain information of the MTCH channel, it receives MBS service data carried by the MTCH channel on the frequency resources of the MTCH channel within the RedCap dedicated initial downlink BWP. Step S25: When the RedCap terminal transitions from idle or inactive state to connected state, the network side of the 5G mobile communication system configures one or more dedicated downlink BWPs for the RedCap terminal. At least one dedicated downlink BWP does not contain the complete set of control resources number 0, referred to as the third active BWP. The third active BWP simultaneously includes the frequency domain range of both the MCCH channel and the MTCH channel. Step S26: In connected state, the RedCap terminal operates in the third active BWP, listens to the MCCH channel, receives MBS control information carried by the MCCH channel, and receives MBS service data carried by the MTCH channel. Alternatively, step S25 can be changed to step S25a, and step S26 can be changed to step S26a. Step S25a: When the RedCap terminal transitions from idle or inactive state to connected state, the network side of the 5G mobile communication system configures multiple dedicated downlink BWPs for the RedCap terminal. At least two of the dedicated downlink BWPs do not contain the complete No. 0 control resource set and are referred to as the fourth active BWP and the fifth active BWP, respectively. The fourth active BWP contains the frequency domain range of the MCCH channel, and the fifth active BWP contains the frequency domain range of the MTCH channel.Step S26a: The network side of the 5G mobile communication system configures the RedCap terminal to operate in two different active BWPs at different time periods in the connected state; when the RedCap terminal is operating in the fourth active BWP in the connected state, it listens to the MCCH channel and receives MBS control information carried by the MCCH channel; when the RedCap terminal is operating in the fifth active BWP in the connected state, it receives MBS service data carried by the MTCH channel.

[0010] Furthermore, in steps S23 to S24, when the paging opportunity arrives, the RedCap terminal retunes to the paging frequency resource to listen for and receive signals in order to realize the paging function.

[0011] This application also proposes a third embodiment of an enhanced transmission method for MBS messages, which sequentially includes steps S11 to S14 in embodiment one and steps S25 to S26 in embodiment two. Alternatively, steps S25 to S26 in embodiment two can be replaced by steps S25a to S26a.

[0012] This application also proposes a fourth embodiment of an enhanced transmission method for MBS messages, which sequentially includes steps S21 to S24 in embodiment two and steps S15 to S16 in embodiment one.

[0013] This application also proposes an embodiment of an enhanced transmission apparatus for MBS messages, including a channel bearer first limiting unit, a BWP and channel first configuration unit, a disconnected state first receiving unit, a disconnected state second receiving unit, a BWP and channel second configuration unit, and a connected state first receiving unit. The channel bearer first limiting unit is used to limit the MCCH channel to be carried within a BWP containing the complete Control Resource Set No. 0, while allowing the MTCH channel to be carried within a BWP that does not contain the complete Control Resource Set No. 0. The BWP and channel first configuration unit is used to configure an initial downlink BWP containing the complete Control Resource Set No. 0 and a RedCap-specific initial downlink BWP that does not contain the complete Control Resource Set No. 0 for the RedCap terminal, and also configures the frequency domain range of the MCCH channel to fall within the initial downlink BWP, and the frequency domain range of the MTCH channel to fall within the RedCap-specific initial downlink BWP. The first receiving unit in the non-connected state is used to enable the RedCap terminal to operate within the RedCap-dedicated initial downlink BWP in both idle and inactive states. When the reception opportunity for the MCCH channel arrives, the RedCap terminal retunes to listen to the MCCH channel within its frequency resources and receives the MBS indication and control information carried by the MCCH channel. The second receiving unit in the non-connected state is used to enable the RedCap terminal to obtain the configuration information of the MTCH channel based on the MBS indication and control information in both idle and inactive states. Combined with the frequency domain information of the MTCH channel, it receives the MBS service data carried by the MTCH channel on the frequency resources of the MTCH channel within the RedCap-dedicated initial downlink BWP. The second BWP and channel configuration unit is used to configure multiple dedicated downlink BWPs for the RedCap terminal when it transitions from the idle or inactive state to the connected state. At least one dedicated downlink BWP contains the complete set of control resource 0 and is called the first active BWP. At least one dedicated downlink BWP does not contain the complete set of control resource 0 and is called the second active BWP. The first active BWP contains the frequency domain range of the MCCH channel, and the second active BWP contains the frequency domain range of the MTCH channel. The first receiving unit in the connected state is used to configure the RedCap terminal to work on two different active BWPs at different time periods in the connected state; when the RedCap terminal is working on the first active BWP in the connected state, it listens to the MCCH channel and receives MBS control information carried by the MCCH channel; when the RedCap terminal is working on the second active BWP in the connected state, it receives MBS service data carried by the MTCH channel.

[0014] This application also proposes a second embodiment of an enhanced MBS message transmission device, including a second channel bearer limiting unit, a third BWP and channel configuration unit, a third non-connection state receiving unit, a fourth non-connection state receiving unit, a fourth BWP and channel configuration unit, and a second connection state receiving unit. The second channel bearer limiting unit allows the MCCH channel to be carried within a BWP that does not contain the complete 0th control resource set, and simultaneously allows the MTCH channel to be carried within a BWP that does not contain the complete 0th control resource set. The third BWP and channel configuration unit configures a RedCap-specific initial downlink BWP for the RedCap terminal that does not contain the complete 0th control resource set, and also configures the frequency domain range of the MCCH channel and the MTCH channel to both fall within the RedCap-specific initial downlink BWP. The third non-connection state receiving unit allows the RedCap terminal to operate within the RedCap-specific initial downlink BWP in idle and inactive states; when the MCCH channel reception opportunity arrives, the RedCap terminal listens to the MCCH channel within the MCCH channel frequency resources and receives the MBS indication and control information carried by the MCCH channel. The fourth receiving unit in the non-connected state is used to enable the RedCap terminal to obtain the configuration information of the MTCH channel according to the MBS indication and control information in the idle and inactive states, and to receive the MBS service data carried by the MTCH channel on the frequency resources of the MTCH channel within the RedCap dedicated initial downlink BWP, in combination with the frequency domain information of the MTCH channel. The fourth BWP and channel configuration unit is used to configure one or more dedicated downlink BWPs for the RedCap terminal when the RedCap terminal transitions from the idle or inactive state to the connected state. At least one dedicated downlink BWP does not contain the complete set of control resource No. 0, and is called the third active BWP. The third active BWP simultaneously contains the frequency domain range of the MCCH channel and the frequency domain range of the MTCH channel. The second receiving unit in the connected state is used to enable the RedCap terminal to operate in the third active BWP in the connected state, listen to the MCCH channel, receive the MBS control information carried by the MCCH channel, and receive the MBS service data carried by the MTCH channel. Alternatively, the fourth BWP and channel configuration unit can be replaced by the fifth BWP and channel configuration unit, and the second receiving unit in the connected state can be replaced by the third receiving unit in the connected state. The BWP and the fifth channel configuration unit are used to configure multiple dedicated downlink BWPs for the RedCap terminal when the RedCap terminal transitions from an idle state or an inactive state to a connected state. At least two of the dedicated downlink BWPs do not contain the complete No. 0 control resource set and are referred to as the fourth active BWP and the fifth active BWP, respectively. The fourth active BWP contains the frequency domain range of the MCCH channel, and the fifth active BWP contains the frequency domain range of the MTCH channel.The third receiving unit in the connected state is used to configure the RedCap terminal to work in two different active BWPs at different time periods in the connected state; when the RedCap terminal is working in the fourth active BWP in the connected state, it listens to the MCCH channel and receives the MBS control information carried by the MCCH channel; when the RedCap terminal is working in the fifth active BWP in the connected state, it receives the MBS service data carried by the MTCH channel.

[0015] This application also proposes a third embodiment of an enhanced transmission apparatus for MBS messages, comprising the channel bearer first defining unit, BWP and channel first configuration unit, disconnected state first receiving unit, and disconnected state second receiving unit from the first embodiment, and the BWP and channel fourth configuration unit and connected state second receiving unit from the second embodiment. Alternatively, the BWP and channel fourth configuration unit in the second embodiment may be replaced with a BWP and channel fifth configuration unit, and the connected state second receiving unit may be replaced with a connected state third receiving unit.

[0016] This application also proposes a fourth embodiment of an enhanced transmission device for MBS messages, which consists of the second channel bearer defining unit, the third BWP and channel configuration unit, the third non-connected state receiving unit, and the fourth non-connected state receiving unit in embodiment two, and the second BWP and channel configuration unit and the first connected state receiving unit in embodiment one.

[0017] The technical effect achieved by this application is to extend the MBS broadcast service from a BWP that "contains the complete No. 0 control resource set" to a BWP that "does not contain the complete No. 0 control resource set", making full use of network resources and improving the MBS receiving user experience of RedCap terminals. Attached Figure Description

[0018] Figure 1 This is a schematic diagram of the initial downlink BWP of a 5G terminal, which includes the complete Control Resource Set No. 0 and MBS CFR.

[0019] Figure 2 This is a schematic diagram showing that the initial downlink BWP of a 5G terminal contains the complete set of control resources number 0.

[0020] Figure 3 This is a diagram illustrating that the dedicated downlink BWP for 5G terminals does not include the complete set of control resources number 0.

[0021] Figure 4 This is a schematic diagram of a dedicated downlink BWP for 5G terminals containing the complete set of control resources number 0.

[0022] Figure 5 This is a schematic diagram showing that the dedicated downlink BWP for 5G terminals does not contain the complete set of control resources number 0.

[0023] Figure 6 This is a diagram illustrating that a dedicated downlink BWP for a 5G terminal must include an NCD SSB when it does not contain a complete set of control resources number 0.

[0024] Figure 7 This is a diagram illustrating how MBS CFR resources cannot be allocated when the dedicated downlink BWP of a 5G terminal does not contain a complete set of control resources number 0.

[0025] Figure 8 This is a flowchart illustrating an embodiment of the enhanced transmission method for MBS messages proposed in this application.

[0026] Figure 9 This is a flowchart illustrating a second embodiment of the enhanced transmission method for MBS messages proposed in this application.

[0027] Figure 10 This is a flowchart illustrating Embodiment 3 of the enhanced transmission method for MBS messages proposed in this application.

[0028] Figure 11 This is a flowchart illustrating Embodiment 4 of the enhanced transmission method for MBS messages proposed in this application.

[0029] Figure 12 This is a schematic diagram of an embodiment of the MBS message enhancement transmission device proposed in this application.

[0030] Figure 13 This is a schematic diagram of a second embodiment of the MBS message enhancement transmission device proposed in this application.

[0031] Figure 14 This is a schematic diagram of the structure of Embodiment 3 of the MBS message enhancement transmission device proposed in this application.

[0032] Figure 15 This is a schematic diagram of the fourth embodiment of the MBS message enhancement transmission device proposed in this application.

[0033] The following are the reference numerals in the figures: Channel bearer first limiting unit 11, BWP and channel first configuration unit 12, non-connected state first receiving unit 13, non-connected state second receiving unit 14, BWP and channel second configuration unit 15, connected state first receiving unit 16, channel bearer second limiting unit 21, BWP and channel third configuration unit 22, non-connected state third receiving unit 23, non-connected state fourth receiving unit 24, BWP and channel fourth configuration unit 25, connected state second receiving unit 26, BWP and channel fifth configuration unit 25a, and connected state third receiving unit 26a. Detailed Implementation

[0034] MBS service is primarily carried by two key channels—MCCH (Multicast Control Channel) and MTCH (Multicast Traffic Channel). Existing communication protocols limit the operation of these two channels to a BWP containing the complete 0th control resource set. This application employs different enhancement techniques for these two channels, providing flexible options for RedCap terminals in various application scenarios to expand network capacity and resource utilization, while simultaneously improving the user experience of MBS service on RedCap terminals.

[0035] Please see Figure 8 The first embodiment of the enhanced transmission method for MBS messages proposed in this application includes the following steps.

[0036] Step S11: The network side of the 5G mobile communication system limits the MCCH channel to be carried in a BWP containing the complete set of control resources No. 0, while allowing the MTCH channel to be carried in a BWP that does not contain the complete set of control resources No. 0. In other words, the network side allows the MTCH channel and the MCCH channel to be carried in the same or different BWPs.

[0037] Step S12: The network side of the 5G mobile communication system configures an initial downlink BWP containing the complete Control Resource Set 0 (CR0) and a RedCap-specific initial downlink BWP not containing the complete CR0 via SIB1 for the RedCap terminal. The network side of the 5G mobile communication system also configures the frequency domain range of the MCCH channel to fall within the initial downlink BWP via SIB1 and SIB20, and further configures the frequency domain range of the MTCH channel to fall within the RedCap-specific initial downlink BWP.

[0038] Preferably, the frequency domain range (bandwidth) of the RedCap-dedicated initial downlink BWP is narrower than that of the initial downlink BWP. A portion of the frequency resources of the initial downlink BWP is used to transmit MBS indication and control information on the MCCH channel, while a portion of the frequency resources of the RedCap-dedicated initial downlink BWP are used to transmit MBS service data on the MTCH channel. This allows the RedCap terminal to spend more time operating on the smaller bandwidth of the RedCap-dedicated initial downlink BWP, which is beneficial for RedCap terminal power saving and also for network load balancing and matching scheduling.

[0039] Step S13: The RedCap terminal operates within the RedCap-dedicated initial downlink BWP in both idle and inactive states. If the network side enables (activates) MBS service, the serving cell transmits MBS indication and control information to the RedCap terminal on the frequency resources of the MCCH channel within the initial downlink BWP. When the MCCH channel reception time arrives, the RedCap terminal retunes to listen to the MCCH channel within its frequency resources and receives the MBS indication and control information carried by the MCCH channel. The MBS indication and control information includes: whether the MBS service is activated and the configuration information of the MCCH channel. After listening and receiving within the frequency resources of the MCCH channel, the RedCap terminal returns to the RedCap-dedicated initial downlink BWP.

[0040] In this step, the RedCap terminal retunes to the frequency resources of the MCCH channel, rather than switching to the initial downlink BWP. This is crucial because the bandwidth of the initial downlink BWP may exceed the bandwidth capability supported by the RedCap terminal, while the frequency resources of the MCCH channel (i.e., the bandwidth of the MBS CFR resources) must be within the capabilities of the RedCap terminal. For example, in the FR1 (Frequency Range 1) band, the initial downlink BWP can be configured with a maximum bandwidth of 100MHz, while the RedCap terminal's supported bandwidth is 20MHz. The retuning refers to the RedCap terminal operating within the frequency range of the MCCH channel (i.e., the MBS CFR) of the initial downlink BWP. This frequency range is limited to the RedCap terminal's capability (20MHz bandwidth), which is consistent with existing communication protocols. The RedCap terminal does not need to operate in the full initial downlink BWP; therefore, it does not switch to the initial downlink BWP.

[0041] Step S14: In the idle state and inactive state, the RedCap terminal obtains the configuration information of the MTCH channel according to the MBS indication and control information, and combines it with the frequency domain information of the MTCH channel obtained from SIB1 and SIB20 to receive the MBS service data carried by the MTCH channel on the frequency resources of the MTCH channel within the RedCap dedicated initial downlink BWP.

[0042] Due to the lightweight design of RedCap terminals' bandwidth capabilities and the congestion of frequency domain resources near the complete Control Resource Set 0, RedCap terminals operate in the RedCap-dedicated Initial Downlink BWP in idle and inactive states, and can receive MBS services after MBS service is enabled. Only when the MCCH channel's reception opportunity arrives does the RedCap terminal retune to listen and receive on the frequency resources where the MCCH channel resides. This improves the MBS service experience of RedCap terminals in idle and inactive states.

[0043] Furthermore, in the idle and inactive states, paging frequency resources can only be configured within the No. 0 control resource set. Since the RedCap-specific initial BWP does not contain the complete No. 0 control resource set, it cannot be configured for paging in the idle and inactive states. To enable paging functionality, the RedCap terminal retunes to the paging frequency resource to listen and receive signals when a paging opportunity arises.

[0044] Step S13 enables the RedCap terminal to receive MBS indication and control information carried on the MCCH channel, and step S14 enables the RedCap terminal to receive MBS service data carried on the MTCH channel. Therefore, steps S13 and S14 are switched according to the MBS service reception requirements and there is no strict order restriction.

[0045] Step S15: When the RedCap terminal transitions from idle or inactive state to connected state, in order to maintain the continuity and feasibility of MBS service, the network side of the 5G mobile communication system configures multiple dedicated downlink BWPs to the RedCap terminal via RRC signaling. At least one dedicated downlink BWP contains the complete set of control resources No. 0 and is called the first active BWP. At least one dedicated downlink BWP does not contain the complete set of control resources No. 0 and is called the second active BWP. The first active BWP contains the frequency domain range of the MCCH channel, and the second active BWP contains the frequency domain range of the MTCH channel.

[0046] Step S16: Based on service requirements, network capacity, and resource utilization, the network side of the 5G mobile communication system comprehensively considers the coexistence capability of MBS services and other services, and configures the RedCap terminal to operate on two different active BWPs during different time periods in the connected state via RRC signaling. When the RedCap terminal is operating in the first active BWP in the connected state, it listens to the MCCH channel and receives MBS control information carried by the MCCH channel. When the RedCap terminal is operating in the second active BWP in the connected state, it receives MBS service data carried by the MTCH channel.

[0047] Due to the lightweight design of RedCap terminals' bandwidth capabilities and the congestion of frequency domain resources near the complete Control Resource Set 0, the network side tends to configure RedCap terminals to operate in the second active BWP for more time. For MBS services that last for extended periods, this improves the MBS service experience of RedCap terminals in the connected state.

[0048] The above-described embodiment 1 follows the existing 3GPP Release 17 standard's BWP conventions for MCCH channel transmission, only enhancing the BWP for MTCH channel transmission (i.e., a breakthrough from existing mobile communication protocols) – allowing the MTCH channel to operate within a BWP that does not contain the complete Control Resource Set 0. For typical MBS service application scenarios, such as IPTV and live streaming, the network side transmits MBS service data on the MTCH channel for extended periods. This enhancement provides users with a better MBS service experience and allows RedCap terminals to better enjoy MBS technology. It also maintains compatibility with the technology of ordinary 5G terminals operating on the initial downlink BWP while monitoring the MCCH channel.

[0049] Please see Figure 9 The second embodiment of the enhanced transmission method for MBS messages proposed in this application includes the following steps.

[0050] Step S21: The network side of the 5G mobile communication system allows the MCCH channel to be carried in a BWP that does not contain the complete No. 0 control resource set, and also allows the MTCH channel to be carried in a BWP that does not contain the complete No. 0 control resource set. Furthermore, the network side allows the MTCH channel and the MCCH channel to be carried in the same or different BWPs.

[0051] Step S22: The network side of the 5G mobile communication system configures a RedCap-specific initial downlink BWP for the RedCap terminal through SIB1 that does not contain the complete No. 0 control resource set. The network side of the 5G mobile communication system also configures the frequency domain range of the MCCH channel and the frequency domain range of the MTCH channel to fall within the RedCap-specific initial downlink BWP through SIB1 and SIB20.

[0052] Step S23: The RedCap terminal operates within the RedCap dedicated initial downlink BWP in both idle and inactive states. If the network side enables (activates) MBS service, the serving cell transmits MBS indication and control information to the RedCap terminal on the frequency resources of the MCCH channel within the RedCap dedicated initial downlink BWP. When the MCCH channel reception opportunity arrives, the RedCap terminal listens to the MCCH channel within the MCCH channel frequency resources and receives the MBS indication and control information carried by the MCCH channel.

[0053] Furthermore, in the idle and inactive states, paging frequency resources can only be configured within the No. 0 control resource set. Since the RedCap-specific initial BWP does not contain the complete No. 0 control resource set, it cannot be configured for paging in the idle and inactive states. To enable paging functionality, the RedCap terminal retunes to the paging frequency resource to listen and receive signals when a paging opportunity arises.

[0054] Step S24: In the idle state and inactive state, the RedCap terminal obtains the configuration information of the MTCH channel according to the MBS indication and control information, and combines it with the frequency domain information of the MTCH channel obtained from SIB1 and SIB20 to receive the MBS service data carried by the MTCH channel on the frequency resources of the MTCH channel within the RedCap dedicated initial downlink BWP.

[0055] Since the frequency domain ranges of both the MCCH and MTCH channels are contained within the RedCap-specific initial downlink BWP, the RedCap terminal does not need to switch back and forth between different BWPs to monitor and receive the MCCH and MTCH channels. Step S23 enables the RedCap terminal to receive MBS indication and control information carried by the MCCH channel, and step S24 enables the RedCap terminal to receive MBS service data carried by the MTCH channel. Therefore, steps S23 and S24 are switched according to the reception requirements of the MBS service, and there is no strict order restriction.

[0056] Step S25: When the RedCap terminal transitions from idle or inactive state to connected state, in order to maintain the continuity and feasibility of MBS service, the network side of the 5G mobile communication system configures one or more dedicated downlink BWPs to the RedCap terminal through RRC signaling. At least one dedicated downlink BWP does not contain the complete No. 0 control resource set and is called the third active BWP. The third active BWP contains both the frequency domain range of the MCCH channel and the frequency domain range of the MTCH channel.

[0057] Step S26: The RedCap terminal operates in the third active BWP in the connected state, listens to the MCCH channel, receives MBS control information carried by the MCCH channel, and receives MBS service data carried by the MTCH channel.

[0058] Alternatively, step S25 can be changed to step S25a, and step S26 can be changed to step S26a.

[0059] Step S25a: When the RedCap terminal transitions from idle or inactive state to connected state, in order to maintain the continuity and feasibility of MBS service, the network side of the 5G mobile communication system configures multiple dedicated downlink BWPs for the RedCap terminal through RRC signaling. At least two of these dedicated downlink BWPs do not contain the complete No. 0 control resource set and are referred to as the fourth active BWP and the fifth active BWP, respectively. The fourth active BWP contains the frequency domain range of the MCCH channel, and the fifth active BWP contains the frequency domain range of the MTCH channel.

[0060] Step S26a: Based on service requirements, network capacity, and resource utilization, the network side of the 5G mobile communication system comprehensively considers the coexistence capability of MBS services and other services, and configures the RedCap terminal to operate in two different active BWPs during different time periods in the connected state via RRC signaling. When the RedCap terminal is operating in the fourth active BWP in the connected state, it listens to the MCCH channel and receives MBS control information carried by the MCCH channel. When the RedCap terminal is operating in the fifth active BWP in the connected state, it receives MBS service data carried by the MTCH channel.

[0061] Steps S25 and S26 are referred to as Scheme 1, and steps S25a and S26a are referred to as Scheme 2. In order to reduce the cost and implementation difficulty of RedCap terminals switching back and forth between different BWPs, Scheme 1 is the preferred scheme.

[0062] The above-described embodiment two enhances both the MCCH and MTCH channels (i.e., breaks through existing mobile communication protocols) by allowing both the MCCH and MTCH channels to operate within a BWP that does not contain the complete Control Resource Set 0. Ideally, the RedCap terminal can monitor the MCCH channel and receive the MTCH channel within the same BWP without switching back and forth, thereby reducing the cost and implementation difficulty of the RedCap terminal switching between different BWPs.

[0063] The enhanced transmission method for MBS messages proposed in this application is applicable to various RRC states, including idle, inactive, and connected states. In Embodiment 1, steps S11 to S14 correspond to the idle or inactive state, and steps S15 to S16 correspond to the connected state. In Embodiment 2, steps S21 to S24 correspond to the idle or inactive state, and steps S25 to S26 (or steps S25a to S26a) correspond to the connected state. The steps of different states in the above two embodiments can be combined to form new embodiments. For example, steps S11 to S14 superimposed with steps S25 to S26 can constitute Embodiment 3. Steps S11 to S14 superimposed with steps S25a to S26a can constitute a variation of Embodiment 3. Furthermore, steps S21 to S24 superimposed with steps S15 to S16 can constitute Embodiment 4.

[0064] Please see Figure 10 In Embodiment 3 of the enhanced transmission method for MBS messages proposed in this application, steps S11 to S14 are superimposed with steps S25 to S26. Alternatively, steps S25 to S26 can be replaced with steps S25a to S26a.

[0065] Please see Figure 11 The fourth embodiment of the enhanced transmission method for MBS messages proposed in this application is a superposition of steps S21 to S24 and steps S15 to S16.

[0066] Please see Figure 12 The first embodiment of the enhanced transmission apparatus for MBS messages proposed in this application includes a channel bearer first limiting unit 11, a BWP and channel first configuration unit 12, a non-connected state first receiving unit 13, a non-connected state second receiving unit 14, a BWP and channel second configuration unit 15, and a connected state first receiving unit 16. Figure 12 The device shown corresponds to Figure 8 The method shown.

[0067] The first limiting unit 11 for channel bearers is used to limit the MCCH channel bearer to a BWP that includes the complete set of control resources No. 0, while allowing the MTCH channel bearer to be carried in a BWP that does not include the complete set of control resources No. 0.

[0068] The BWP and the first channel configuration unit 12 are used to configure an initial downlink BWP containing the complete No. 0 control resource set and a RedCap-specific initial downlink BWP that does not contain the complete No. 0 control resource set for the RedCap terminal. The frequency domain range of the MCCH channel is also configured to fall within the initial downlink BWP, and the frequency domain range of the MTCH channel is also configured to fall within the RedCap-specific initial downlink BWP.

[0069] The non-connected first receiving unit 13 is used to enable the RedCap terminal to operate within the RedCap-dedicated initial downlink BWP in the idle and inactive states. When the reception opportunity of the MCCH channel arrives, the RedCap terminal retunes to listen to the MCCH channel within the frequency resources of the MCCH channel and receives the MBS indication and control information carried by the MCCH channel.

[0070] The non-connected state second receiving unit 14 is used to enable the RedCap terminal to obtain the configuration information of the MTCH channel according to the MBS indication and control information in the idle state and inactive state, and to receive the MBS service data carried by the MTCH channel on the frequency resources of the MTCH channel within the RedCap dedicated initial downlink BWP, in combination with the frequency domain information of the MTCH channel.

[0071] The BWP and the second channel configuration unit 15 are used to configure multiple dedicated downlink BWPs to the RedCap terminal when the RedCap terminal transitions from an idle state or an inactive state to a connected state. At least one dedicated downlink BWP contains the complete set of control resources No. 0 and is called the first active BWP. At least one dedicated downlink BWP does not contain the complete set of control resources No. 0 and is called the second active BWP. The first active BWP contains the frequency domain range of the MCCH channel, and the second active BWP contains the frequency domain range of the MTCH channel.

[0072] The first receiving unit 16 in the connected state is used to configure the RedCap terminal to operate on two different active BWPs during different time periods in the connected state. When the RedCap terminal is operating on the first active BWP in the connected state, it listens to the MCCH channel and receives MBS control information carried by the MCCH channel. When the RedCap terminal is operating on the second active BWP in the connected state, it receives MBS service data carried by the MTCH channel.

[0073] Please see Figure 13 The second embodiment of the enhanced transmission apparatus for MBS messages proposed in this application includes a second channel bearer defining unit 21, a third BWP and channel configuration unit 22, a third receiving unit in a disconnected state 23, a fourth receiving unit in a disconnected state 24, a fourth BWP and channel configuration unit 25, and a second receiving unit in a connected state 26. Figure 13 The device shown corresponds to Figure 9 The method shown.

[0074] The second channel bearer limiting unit 21 is used to allow the MCCH channel to be carried in a BWP that does not contain the complete set of control resources No. 0, and at the same time allow the MTCH channel to be carried in a BWP that does not contain the complete set of control resources No. 0.

[0075] The BWP and the third channel configuration unit 22 are used to configure a RedCap-specific initial downlink BWP for the RedCap terminal that does not contain the complete No. 0 control resource set, and also configure the frequency domain range of the MCCH channel and the frequency domain range of the MTCH channel to fall within the RedCap-specific initial downlink BWP.

[0076] The non-connected third receiving unit 23 is used to enable the RedCap terminal to operate within the RedCap-dedicated initial downlink BWP in idle and inactive states. When the reception opportunity for the MCCH channel arrives, the RedCap terminal listens to the MCCH channel within the MCCH channel frequency resources and receives the MBS indication and control information carried by the MCCH channel.

[0077] The non-connected fourth receiving unit 24 is used to enable the RedCap terminal to obtain the configuration information of the MTCH channel according to the MBS indication and control information in the idle state and inactive state, and to receive the MBS service data carried by the MTCH channel on the frequency resources of the MTCH channel within the RedCap dedicated initial downlink BWP, in combination with the frequency domain information of the MTCH channel.

[0078] The BWP and the fourth channel configuration unit 25 are used to configure one or more dedicated downlink BWPs to the RedCap terminal when the RedCap terminal transitions from an idle state or an inactive state to a connected state. At least one dedicated downlink BWP does not contain the complete set of control resources No. 0 and is called the third active BWP. The third active BWP contains both the frequency domain range of the MCCH channel and the frequency domain range of the MTCH channel.

[0079] The second receiving unit 26 in the connected state is used to enable the RedCap terminal to work in the third activated BWP in the connected state, listen to the MCCH channel, receive MBS control information carried by the MCCH channel, and receive MBS service data carried by the MTCH channel.

[0080] Alternatively, the BWP and channel fourth configuration unit 25 can be replaced with the BWP and channel fifth configuration unit 25a, and the connection state second receiving unit 26 can be replaced with the connection state third receiving unit 26a.

[0081] The BWP and the fifth channel configuration unit 25a are used to configure multiple dedicated downlink BWPs to the RedCap terminal when the RedCap terminal transitions from an idle state or an inactive state to a connected state. At least two of the dedicated downlink BWPs do not contain the complete No. 0 control resource set and are respectively called the fourth active BWP and the fifth active BWP. The fourth active BWP contains the frequency domain range of the MCCH channel, and the fifth active BWP contains the frequency domain range of the MTCH channel.

[0082] The third receiving unit 26a in the connected state is used to configure the RedCap terminal to operate in two different active BWPs during different time periods in the connected state. When the RedCap terminal is operating in the fourth active BWP in the connected state, it listens to the MCCH channel and receives MBS control information carried by the MCCH channel. When the RedCap terminal is operating in the fifth active BWP in the connected state, it receives MBS service data carried by the MTCH channel.

[0083] Please see Figure 14 The third embodiment of the enhanced MBS message transmission apparatus proposed in this application consists of a channel bearer first limiting unit 11, a BWP and a channel first configuration unit 12, a non-connection state first receiving unit 13, a non-connection state second receiving unit 14, superimposed with a BWP and a channel fourth configuration unit 25, and a connection state second receiving unit 26. Alternatively, the BWP and channel fourth configuration unit 25 can be replaced with a BWP and a channel fifth configuration unit 25a, and the connection state second receiving unit 26 can be replaced with a connection state third receiving unit 26a.

[0084] Please see Figure 15 The fourth embodiment of the enhanced transmission device for MBS messages proposed in this application is a superimposed BWP and channel bearer second limiting unit 21, BWP and channel third configuration unit 22, non-connected state third receiving unit 23, non-connected state fourth receiving unit 24, BWP and channel second configuration unit 15, and connected state first receiving unit 16.

[0085] This application extends existing MBS service reception schemes, providing the possibility for RedCap terminals operating on BWPs that do not contain the complete Control Resource Set 0 (CR0) to receive MBS services. Existing MBS service reception schemes are limited to, for example, BWPs containing the complete CR0 carrying the MBS service. Various embodiments of this application add two enhanced MBS service transmission schemes. The first new embodiment involves both BWPs containing the complete CR0 and BWPs not containing the complete CR0 carrying the MBS service. The second new embodiment involves a BWP not containing the complete CR0 carrying the MBS service. This application facilitates the joint development of MBS broadcast technology and RedCap technology, effectively expanding network capacity and resource utilization, and also improving the user experience of RedCap terminals.

[0086] The above are merely preferred embodiments of this application and are not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. An enhanced transmission method for MBS messages, characterized in that, Includes the following steps; Step S11: The network side of the 5G mobile communication system limits the MCCH channel to be carried in a BWP that includes the complete set of control resources No. 0, while allowing the MTCH channel to be carried in a BWP that does not include the complete set of control resources No.

0. Step S12: The network side of the 5G mobile communication system configures the RedCap terminal with an initial downlink BWP containing the complete set of control resources No. 0, and a RedCap-specific initial downlink BWP that does not contain the complete set of control resources No. 0; the network side of the 5G mobile communication system also configures the frequency domain range of the MCCH channel to fall within the initial downlink BWP, and also configures the frequency domain range of the MTCH channel to fall within the RedCap-specific initial downlink BWP. Step S13: The RedCap terminal operates in the RedCap dedicated initial downlink BWP in the idle state and inactive state; when the reception opportunity of the MCCH channel arrives, the RedCap terminal retunes to the frequency resource of the MCCH channel to listen to the MCCH channel and receive the MBS indication and control information carried by the MCCH channel. Step S14: In the idle state and inactive state, the RedCap terminal obtains the configuration information of the MTCH channel according to the MBS indication and control information, and in combination with the frequency domain information of the MTCH channel, receives the MBS service data carried by the MTCH channel on the frequency resources of the MTCH channel within the RedCap dedicated initial downlink BWP. Step S15: When the RedCap terminal transitions from idle or inactive state to connected state, the network side of the 5G mobile communication system configures multiple dedicated downlink BWPs for the RedCap terminal. At least one dedicated downlink BWP contains the complete set of control resources No. 0 and is called the first active BWP. At least one dedicated downlink BWP does not contain the complete set of control resources No. 0 and is called the second active BWP. The first active BWP contains the frequency domain range of the MCCH channel, and the second active BWP contains the frequency domain range of the MTCH channel. Step S16: The network side of the 5G mobile communication system configures the RedCap terminal to work on two different active BWPs at different time periods in the connected state; when the RedCap terminal is working on the first active BWP in the connected state, it listens to the MCCH channel and receives the MBS control information carried by the MCCH channel. When the RedCap terminal is in connected mode and operating with the second activated BWP, it receives MBS service data carried on the MTCH channel.

2. The enhanced transmission method for MBS messages according to claim 1, characterized in that, In steps S13 to S14, when the paging opportunity arrives, the RedCap terminal retunes to the paging frequency resource to listen for and receive messages in order to realize the paging function.

3. An enhanced transmission method for MBS messages, characterized in that, Includes the following steps; Step S21: The network side of the 5G mobile communication system allows the MCCH channel to be carried in a BWP that does not contain the complete No. 0 control resource set, and also allows the MTCH channel to be carried in a BWP that does not contain the complete No. 0 control resource set. Step S22: The network side of the 5G mobile communication system configures a RedCap-specific initial downlink BWP for the RedCap terminal that does not contain the complete No. 0 control resource set. The network side of the 5G mobile communication system also configures the frequency domain range of the MCCH channel and the frequency domain range of the MTCH channel to fall within the RedCap-specific initial downlink BWP. Step S23: The RedCap terminal operates in the RedCap dedicated initial downlink BWP in the idle state and inactive state; when the reception opportunity of the MCCH channel arrives, the RedCap terminal listens to the MCCH channel in the MCCH channel frequency resources and receives the MBS indication and control information carried by the MCCH channel. Step S24: In the idle state and inactive state, the RedCap terminal obtains the configuration information of the MTCH channel according to the MBS indication and control information, and in combination with the frequency domain information of the MTCH channel, receives the MBS service data carried by the MTCH channel on the frequency resources of the MTCH channel within the RedCap dedicated initial downlink BWP. Step S25: When the RedCap terminal transitions from idle or inactive state to connected state, the network side of the 5G mobile communication system configures one or more dedicated downlink BWPs for the RedCap terminal. At least one dedicated downlink BWP does not contain the complete set of control resources No. 0 and is called the third active BWP. The third active BWP contains both the frequency domain range of the MCCH channel and the frequency domain range of the MTCH channel. Step S26: The RedCap terminal operates in the third active BWP in the connected state, listens to the MCCH channel, receives MBS control information carried by the MCCH channel, and receives MBS service data carried by the MTCH channel. Alternatively, step S25 can be changed to step S25a, and step S26 can be changed to step S26a. Step S25a: When the RedCap terminal transitions from idle or inactive state to connected state, the network side of the 5G mobile communication system configures multiple dedicated downlink BWPs for the RedCap terminal. At least two dedicated downlink BWPs do not contain the complete No. 0 control resource set and are referred to as the fourth active BWP and the fifth active BWP, respectively. The fourth active BWP contains the frequency domain range of the MCCH channel, and the fifth active BWP contains the frequency domain range of the MTCH channel. Step S26a: The network side of the 5G mobile communication system configures the RedCap terminal to work in two different active BWPs at different time periods in the connected state; when the RedCap terminal is working in the fourth active BWP in the connected state, it listens to the MCCH channel and receives the MBS control information carried by the MCCH channel. When the RedCap terminal is in connected mode and operating in the fifth active BWP, it receives MBS service data carried on the MTCH channel.

4. The enhanced transmission method for MBS messages according to claim 3, characterized in that, In steps S23 to S24, when the paging opportunity arrives, the RedCap terminal retunes to the paging frequency resource to listen for and receive messages in order to realize the paging function.

5. An enhanced transmission method for MBS messages, characterized in that, It includes, in sequence, steps S11 to S14 of claim 1 and steps S25 to S26 of claim 3; Alternatively, it may include steps S11 to S14 of claim 1 and steps S25a to S26a of claim 3 in sequence.

6. An enhanced transmission method for MBS messages, characterized in that, It includes, in sequence, steps S21 to S24 of claim 3 and steps S15 to S16 of claim 1.

7. An enhanced transmission device for MBS messages, characterized in that, It includes a channel bearer first limiting unit, a BWP and channel first configuration unit, a non-connected state first receiving unit, a non-connected state second receiving unit, a BWP and channel second configuration unit, and a connected state first receiving unit; The first channel bearer limiting unit is used to limit the MCCH channel bearer to a BWP that includes the complete set of control resources No. 0, while allowing the MTCH channel bearer to be carried in a BWP that does not include the complete set of control resources No.

0. The BWP and the first channel configuration unit are used to configure an initial downlink BWP containing the complete set of control resources No. 0 and a RedCap-specific initial downlink BWP that does not contain the complete set of control resources No. 0 for the RedCap terminal. The frequency domain range of the MCCH channel is also configured to fall within the initial downlink BWP, and the frequency domain range of the MTCH channel is also configured to fall within the RedCap-specific initial downlink BWP. The non-connected state first receiving unit is used to enable the RedCap terminal to work in the RedCap dedicated initial downlink BWP in the idle state and inactive state; when the reception opportunity of the MCCH channel arrives, the RedCap terminal retunes to listen to the MCCH channel in the frequency resources of the MCCH channel and receives the MBS indication and control information carried by the MCCH channel. The non-connected state second receiving unit is used to enable the RedCap terminal to obtain the configuration information of the MTCH channel according to the MBS indication and control information in the idle state and inactive state, and to receive the MBS service data carried by the MTCH channel on the frequency resources of the MTCH channel within the RedCap dedicated initial downlink BWP in combination with the frequency domain information of the MTCH channel. The BWP and the second channel configuration unit are used to configure multiple dedicated downlink BWPs for the RedCap terminal when the RedCap terminal transitions from an idle state or an inactive state to a connected state. At least one dedicated downlink BWP contains the complete set of control resources No. 0 and is called the first active BWP. At least one dedicated downlink BWP does not contain the complete set of control resources No. 0 and is called the second active BWP. The first active BWP contains the frequency domain range of the MCCH channel, and the second active BWP contains the frequency domain range of the MTCH channel. The first receiving unit in the connected state is used to configure the RedCap terminal to work on two different active BWPs at different time periods in the connected state; when the RedCap terminal is working on the first active BWP in the connected state, it listens to the MCCH channel and receives the MBS control information carried by the MCCH channel. When the RedCap terminal is in connected mode and operating with the second activated BWP, it receives MBS service data carried on the MTCH channel.

8. An enhanced transmission apparatus for MBS messages, characterized in that, It includes a second channel bearer defining unit, a third BWP and channel configuration unit, a third receiving unit in a non-connected state, a fourth receiving unit in a non-connected state, a fourth BWP and channel configuration unit, and a second receiving unit in a connected state; The second channel bearer limiting unit is used to allow the MCCH channel to be carried in a BWP that does not contain the complete set of control resources No. 0, and at the same time allow the MTCH channel to be carried in a BWP that does not contain the complete set of control resources No.

0. The BWP and the third channel configuration unit are used to configure a RedCap-specific initial downlink BWP for the RedCap terminal that does not contain the complete No. 0 control resource set, and also configure the frequency domain range of the MCCH channel and the frequency domain range of the MTCH channel to fall within the RedCap-specific initial downlink BWP. The non-connected third receiving unit is used to enable the RedCap terminal to work in the RedCap dedicated initial downlink BWP in the idle and inactive states; when the reception opportunity of the MCCH channel arrives, the RedCap terminal listens to the MCCH channel in the MCCH channel frequency resources and receives the MBS indication and control information carried by the MCCH channel. The non-connected fourth receiving unit is used to enable the RedCap terminal to obtain the configuration information of the MTCH channel according to the MBS indication and control information in the idle and inactive states, and to receive the MBS service data carried by the MTCH channel on the frequency resources of the MTCH channel within the RedCap dedicated initial downlink BWP, in combination with the frequency domain information of the MTCH channel. The BWP and the fourth channel configuration unit are used to configure one or more dedicated downlink BWPs to the RedCap terminal when the RedCap terminal transitions from the idle state or the inactive state to the connected state. At least one dedicated downlink BWP does not contain the complete set of control resources No. 0 and is called the third active BWP. The third active BWP contains both the frequency domain range of the MCCH channel and the frequency domain range of the MTCH channel. The second receiving unit in the connected state is used to enable the RedCap terminal to work in the third activated BWP in the connected state, listen to the MCCH channel, receive MBS control information carried by the MCCH channel, and receive MBS service data carried by the MTCH channel. Alternatively, the BWP and the fourth channel configuration unit can be changed to the BWP and the fifth channel configuration unit, and the second connection state receiving unit can be changed to the third connection state receiving unit. The BWP and the fifth channel configuration unit are used to configure multiple dedicated downlink BWPs to the RedCap terminal when the RedCap terminal transitions from an idle state or an inactive state to a connected state. At least two dedicated downlink BWPs do not contain the complete No. 0 control resource set and are respectively called the fourth active BWP and the fifth active BWP. The fourth active BWP contains the frequency domain range of the MCCH channel, and the fifth active BWP contains the frequency domain range of the MTCH channel. The third receiving unit in the connected state is used to configure the RedCap terminal to work in two different active BWPs at different time periods in the connected state; when the RedCap terminal is working in the fourth active BWP in the connected state, it listens to the MCCH channel and receives the MBS control information carried by the MCCH channel. When the RedCap terminal is in connected mode and operating in the fifth active BWP, it receives MBS service data carried on the MTCH channel.

9. An enhanced transmission device for MBS messages, characterized in that, It is composed of the channel bearer first defining unit, BWP and channel first configuration unit, non-connected state first receiving unit, non-connected state second receiving unit as in claim 7, and the BWP and channel fourth configuration unit and connected state second receiving unit as in claim 8; Alternatively, it may consist of the channel bearer first defining unit, BWP and channel first configuration unit, non-connected state first receiving unit, and non-connected state second receiving unit as described in claim 7, and the BWP and channel fifth configuration unit and connected state third receiving unit as described in claim 8.

10. An enhanced transmission apparatus for MBS messages, characterized in that, It is composed of the channel bearer second defining unit, BWP and channel third configuration unit, non-connected state third receiving unit, and non-connected state fourth receiving unit as in claim 8, and the BWP and channel second configuration unit and connected state first receiving unit as in claim 7.

Images