Multicast broadcast service in various radio resource control states

Abstract

Disclosed aspects relate to managing multicast broadcast services (MBS) in different radio resource control (RRC) states, including a wireless communication device receiving, from a network, a point-to-multipoint (PTM) configuration for each of a plurality of MBSs using signaling specific to the wireless communication device when the wireless communication device is in an RRC connected state. The wireless communication device transitions from the RRC connected state to an RRC inactive state. In response to transitioning to the RRC inactive state, the wireless communication device receives, from the network, data for at least one of the plurality of MBSs using the PTM configuration received in the RRC connected state when the wireless communication device is in the RRC inactive state.

Description

[0001] Cross-reference to related applications

[0002] This application relates to application filed on May 31, 2022, with agency number ZTE-2022-000613-WO, entitled "Multicast Broadcast Service in Different Radio Resource Controls," the disclosure of which is incorporated herein by reference in its entirety. This application also relates to application filed on May 31, 2022, with agency number ZTE-2022-000896-WO, entitled "Multicast Broadcast Service in Different Radio Resource Controls," the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] This invention relates to wireless communication, and more particularly, to systems, methods, apparatus, and non-volatile computer-readable media for managing multicast and broadcast services (MBS) under various Radio Resource Control (RRC) states. Background Technology

[0004] MBS is one of the most prominent use cases for New Radio (NR) in fifth-generation (5G) mobile networks, providing reliable, low-latency, and resource-efficient transmission to multiple terminals receiving the same content. Key use cases for MBS include deployment in areas with a high concentration of terminals, such as concert halls, stadiums, racetracks, gatherings, and densely populated areas, to transmit the same content (e.g., the same video). In some embodiments, MBS content (e.g., video) is synchronized to terminals, requiring multiple viewpoints of the video. Furthermore, it is used when a large number of users and terminals in the same cell simultaneously watch live Virtual Reality (VR) broadcasts. Summary of the Invention

[0005] In some examples, when the wireless communication device is in an RRC connected state, it uses device-specific signaling to receive from the network a point-to-multipoint (PTM) configuration for each of the multiple MBS. The wireless communication device then transitions from the RRC connected state to an RRC inactive state. In response to the transition to the RRC inactive state, while in the RRC inactive state, the wireless communication device uses the PTM configuration received in the RRC connected state to receive data from the network for at least one of the multiple MBS.

[0006] In some examples, when the wireless communication device is in an RRC connected state, the network uses device-specific signaling to send the PTM configuration of each of the multiple MBS to the wireless communication device. The network then releases the wireless communication device to an RRC inactive state. When the wireless communication device is in an RRC inactive state, the network uses the PTM configuration sent when the UE is in an RRC connected state to send data to the wireless communication device corresponding to at least one of the multiple MBS.

[0007] In some examples, when the wireless communication device is in an RRC connected state, it receives indication information from the network indicating that it has obtained the PTM configuration for each of the multiple MBS from broadcast signaling. The wireless communication device receives the PTM configuration from the network for receiving broadcast signaling for the multiple MBS when it is in an RRC connected state.

[0008] In some examples, the network uses device-specific signaling to send indication information to the wireless communication device. This indication information indicates the need to obtain the PTM configuration for each of the multiple MBS from broadcast signaling for transmitting multiple MBS when the wireless communication device is in an RRC connected state, and to obtain the PTM configuration for each of the multiple MBS from at least one MBS when the wireless communication device is in an RRC inactive state. The network uses broadcast signaling to send to the wireless communication device the PTM configuration for transmitting multiple MBS when the wireless communication device is in an RRC connected state and the updated PTM configuration for transmitting at least one MBS when the wireless communication device is in an RRC inactive state.

[0009] In some examples, the wireless communication device uses a first signaling specific to the wireless communication device to receive from the network a PTM configuration for receiving at least one MBS when the wireless communication device is in an RRC connected state. When the wireless communication device is in an RRC connected state, the wireless communication device uses a second signaling specific to the wireless communication device to receive indication information from the network, which indicates that when the wireless communication device is in an RRC inactive state, a PTM configuration for receiving at least one MBS is obtained from broadcast signaling.

[0010] In some examples, the network uses a first signaling specific to the wireless communication device to send a PTM configuration for receiving at least one MBS when the wireless communication device is in an RRC connected state to the wireless communication device. When the wireless communication device is in an RRC connected state, the network uses a second signaling specific to the wireless communication device to send indication information to the wireless communication device, the indication information indicating that when the wireless communication device is in an RRC inactive state, the PTM configuration for receiving the at least one MBS is obtained from broadcast signaling.

[0011] The above and other aspects, and their implementations, are described in more detail in the accompanying drawings, description, and claims. Attached Figure Description

[0012] These and other aspects and features of this implementation will be apparent to those skilled in the art after reading the following description of a specific implementation in conjunction with the accompanying drawings, in which:

[0013] Figure 1 This is a schematic diagram illustrating exemplary wireless communication networks according to various schemes.

[0014] Figure 2 This is a schematic diagram illustrating a block diagram of an exemplary wireless communication system for transmitting and receiving downlink and uplink communication signals according to various schemes.

[0015] Figure 3 A flowchart illustrating exemplary methods for managing MBS according to various schemes is shown.

[0016] Figure 4 A flowchart illustrating exemplary methods for managing MBS according to various schemes is shown.

[0017] Figure 5 This is a flowchart illustrating exemplary methods for managing MBS according to various schemes.

[0018] Figure 6 This is a table illustrating the implementation of PTM configurations carried in a dedicated RRC reconfiguration for the UE according to different schemes.

[0019] Figure 7 This is a table illustrating the broadcast PTM configuration carried in the MCCH according to some schemes.

[0020] Figure 8 This is a flowchart illustrating exemplary methods for managing MBS according to various schemes.

[0021] Figure 9 This is a flowchart illustrating exemplary methods for managing MBS according to various schemes.

[0022] Figure 10 This is a flowchart illustrating exemplary methods for managing MBS according to various schemes.

[0023] Figure 11 This is a flowchart illustrating exemplary methods for managing MBS according to various schemes.

[0024] Figure 12 This is a flowchart illustrating exemplary methods for managing MBS according to various schemes.

[0025] Figure 13 This is a flowchart illustrating exemplary methods for managing MBS according to various schemes. Detailed Implementation

[0026] This embodiment will now be described in detail with reference to the accompanying drawings, which are provided as illustrative examples of the embodiments to enable those skilled in the art to practice the embodiments and alternatives that are obvious to them. It should be noted that the following drawings and embodiments are not intended to limit the scope of this embodiment to a single embodiment, but other implementations may be achieved by interchangeing some or all of the described or illustrated elements. Furthermore, where certain elements of this implementation may be partially or completely implemented using known components, only those portions of such known components necessary for understanding this implementation are described, and detailed descriptions of other portions of such known components are omitted so as not to obscure the implementation. Embodiments described as software implementations are not intended to be limited thereto, but may include implementations implemented in hardware, or a combination of software and hardware, and vice versa, as will be apparent to those skilled in the art, unless otherwise specified herein. In this specification, implementations of a single component are shown and should not be considered limiting. Rather, this disclosure is intended to cover other implementations that include multiple identical components, and vice versa, unless expressly stated herein. Furthermore, the applicant does not intend to assign any terminology in the specification or claims a rare or special meaning unless expressly stated so. Furthermore, this implementation covers current and future known equivalents of the known components mentioned herein in an illustrative manner.

[0027] In MBS deployment scenarios, given the limited number of terminals or user equipment (UEs) connected to the same cell and the limited service capacity carried by the cell, cell congestion can occur frequently. This congestion can lead to the rejection and / or reduction of other services and / or UE transmissions, negatively impacting user experience.

[0028] In 5G NR, a UE has three Radio Resource Control (RRC) states: RRC Connected, RRC Idle, and RRC Inactive. The RRC Inactive state is defined in 5G NR. For example, when a UE enters the RRC Inactive state, it retains a portion of its network access context. The core network may not be aware that the UE has transitioned to the RRC Inactive state. That is, the RRC Inactive state can be transparent to the core network.

[0029] In the RRC inactive state, the UE transitions from the RRC inactive state to the RRC connected state through a connection recovery process to send or receive data. The RRC inactive state not only saves energy but also manages control plane latency (for example, compared to a UE in the RRC idle state, the UE can quickly enter the RRC connected state with lower control plane (CP) latency).

[0030] In some implementations of MBS multicast reception involving cell congestion and / or power saving, for some UEs using MBS multicast, the RRC state can be transitioned to an RRC inactive state. Such a UE transitions from an RRC connected state to an RRC inactive state to receive or continue receiving multicast sessions.

[0031] In some implementations, a point-to-multipoint (PTM) configuration delivery method is specified. For multicast services or sessions, dedicated signaling is used. For broadcast services or sessions, only broadcast signaling (e.g., System Information Block (SIB) and MBS Control Channel (MCCH)) is used. For broadcast reception in other secondary cells (SCells), dedicated signaling for transmitting system information can be used. When in RRC inactive state, the UE can receive multicast data or information.

[0032] This application relates to enabling a UE to receive or continue receiving multicast services in an RRC inactive state. To receive multicast services, the UE needs to obtain the correct configuration, referred to herein as, for example, PTM configuration, multicast configuration, or MBS configuration; these names are interchangeable. The PTM configuration includes at least the access stratum information used by the UE to obtain multicast data. Multicast services and multicast sessions are used interchangeably to identify a multicast service within the Radio Access Network (RAN) context.

[0033] Figure 1An exemplary wireless communication network 100 is illustrated. Wireless communication network 100 corresponds to group communication or multicast services within a cellular network. In wireless communication network 100, network-side communication nodes or base stations (BS) may include one or more of the following: next-generation node B (gNB), E-Utran node B (also known as evolved Node B, eNodeB, or eNB), picocell, femtocell, transmission / reception point (TRP), access point (AP), etc. Terminal-side nodes or UEs may include remote communication systems (such as, but not limited to, mobile devices, smartphones, personal digital assistants (PDAs), tablet computers, laptop computers) or short-range communication systems (such as, but not limited to, wearable devices, vehicles with vehicle communication systems, etc.). Figure 1 In this context, BS102 represents the network-side communication node, and UE 104a or 104b represents the terminal-side communication node. In some examples, BS102 is sometimes referred to as the "wireless communication node," and UE 104a / 104b is sometimes referred to as the "wireless communication device."

[0034] like Figure 1 As shown, BS102 can provide wireless communication services to UEs 104a and 104b within cell 101. UE 104a can communicate with BS102 via communication channel 103a. Similarly, UE 104b can communicate with BS102 via communication channel 103b. The communication channels (e.g., 103a and 103b) can be via an interface, such as, but not limited to, a Uu interface also known as the Universal Mobile Telecommunications System (UMTS) air interface. BS102 is connected to the core network (CN) 108 via an external interface 107 (e.g., an NG interface).

[0035] Figure 2 A block diagram of an exemplary wireless communication system 150 for transmitting and receiving downlink and uplink communication signals according to some schemes of this disclosure is shown. See also Figure 1 and 2 System 150 is part of network 100. Within system 150, systems such as... Figure 1 The wireless communication network 100 transmits and receives data symbols in a wireless communication environment.

[0036] System 150 generally includes BS 102 and UEs 104a and 104b. BS 102 includes a BS transceiver module 110, a BS antenna 112, a BS memory module 116, a BS processor module 114, and a network communication module 118. Modules / components are coupled and interconnected with each other via data communication bus 120 as needed. UE 104a includes a UE transceiver module 130a, a UE antenna 132a, a UE memory module 134a, and a UE processor module 136a. Modules / components are coupled and interconnected with each other via data communication bus 140a as needed. Similarly, UE 104b includes a UE transceiver module 130b, a UE antenna 132b, a UE memory module 134b, and a UE processor module 136b. Modules / components are coupled and interconnected with each other via data communication bus 140b as needed. BS102 communicates with UE104a and 104b via communication channel 155, which can be any wireless channel or other medium known in the art suitable for data transmission as described herein.

[0037] System 150 may further include, except Figure 2 Any number of modules / elements other than those shown herein. The various illustrative blocks, modules, elements, circuits, and processing logic described in conjunction with the arrangements disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps are described generally according to their functionality. Whether these functions are implemented as hardware, firmware, or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art, skilled in the art, can implement such functions appropriately for each specific application; however, such implementation decisions should not be construed as limiting the scope of this disclosure.

[0038] The wireless transmission from the antenna of each of UEs 104a and 104b to the antenna of BS 102 is referred to as uplink transmission, and the wireless transmission from the antenna of BS 102 to the antenna of each of UEs 104a and 104b is referred to as downlink transmission. According to some embodiments, each of UE transceiver modules 130a and 130b may be referred to herein as an uplink transceiver or a UE transceiver. An uplink transceiver may include transmitter circuitry and receiver circuitry, each coupled to its respective antenna 132a and 132b. Alternatively, a duplex switch may couple the uplink transmitter or receiver to the uplink antenna in a time-duplex manner. Similarly, BS transceiver module 110 may be referred to herein as a downlink transceiver or a BS transceiver. A downlink transceiver may include RF transmitter circuitry and receiver circuitry, each coupled to antenna 112. A downlink duplex switch may selectively couple the downlink transmitter or receiver to antenna 112 in a time-duplex manner. The operation of transceivers 110, 130a, and 130b is time-coordinated such that an uplink receiver is coupled to antennas 132a and 132b for receiving transmissions via wireless communication channel 155 while a downlink transmitter is coupled to antenna 112. In some examples, UEs 104a and 104b can communicate with BS 102 via wireless communication channel 155 using UE transceivers 130a and 130b through the respective antennas 132a and 132b. Wireless communication channel 155 can be any wireless channel or other medium suitable for downlink (DL) and / or uplink (UL) transmission of data as described herein.

[0039] UE transceivers 130a / 130b and BS transceiver 110 are configured to communicate via radio data communication channel 155 and cooperate with an antenna arrangement appropriately configured to support specific wireless communication protocols and modulation schemes. In some examples, UE transceivers 130a / 130b and BS transceiver 110 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to the application of specific standards and associated protocols. Rather, UE transceivers 130a / 130b and BS transceiver 110 may be configured to support alternative or additional radio data communication protocols, including future standards or variations thereof.

[0040] Processor modules 136a, 136b, and 114 may each be implemented or constructed using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, and are designed to perform the functions described herein. In this way, the processor can be implemented as a microprocessor, controller, microcontroller, state machine, etc. The processor can also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors coupled with a digital signal processor core, or any other such configuration.

[0041] Furthermore, the methods or algorithms described in conjunction with the arrangements disclosed herein can be directly embodied in hardware, firmware, software modules executed by processor modules 114, 136a, and 136b respectively, or any actual combination thereof. Memory modules 116, 134a, and 134b can be implemented as RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, removable disk, CD-ROM, or another suitable form of storage medium. Memory modules 116, 134a, and 134b can be coupled to processor modules 114, 136a, and 136b respectively, such that processor modules 114, 136a, and 136b can read information from and write information to memory modules 116, 134a, and 134b respectively. Memory modules 116, 134a, and 134b can also be integrated into their respective processor modules 114, 136a, and 136b. In some examples, memory modules 116, 134a, and 134b may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 114, 136a, and 136b, respectively. Memory modules 116, 134a, and 134b may also each include non-volatile memory for storing instructions to be executed by processor modules 114, 136a, and 136b, respectively.

[0042] Network interface 118 typically represents the hardware, software, firmware, processing logic, and / or other components of BS 102 that enable bidirectional communication between BS transceiver 110 and other network components and communication nodes configured to communicate with BS 102. For example, network interface 118 may be configured to support Internet or WiMAX services. In a typical deployment, network interface 118 provides an 802.3 Ethernet interface, enabling BS transceiver 110 to communicate with a traditional Ethernet-based computer network. In this way, network interface 118 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). As used herein with respect to a specified operation or function, the term "configured for" or "constructed for" refers to a device, component, circuit, structure, machine, signal, etc., physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function. Network interface 118 may allow BS 102 to communicate with other BSs or the core network via wired or wireless connections.

[0043] BS102 can communicate with multiple UEs (including UEs 104a and 104b) using multicast or broadcast (collectively referred to as MBS). Multiple UEs can each receive MBS services via multicast and / or broadcast. To receive MBS services, multiple UEs share a common understanding of the MBS service configuration, including but not limited to frequency resource ranges and scrambling sequences used for resource allocation, referred to herein as PTM configuration, multicast configuration, or MBS configuration. The network (e.g., BS102 or cell 101) can transmit the PTM configuration for MBS multicast reception for UEs 104a or 104b in different RRC states.

[0044] In some examples, UE 104a or 104b receives PTM configuration or its updates from the network (e.g., BS102 or cell 101) via dedicated signaling specific to the UE. Examples of this dedicated signaling include RRC reconfiguration signaling. For instance, when the UE is in an RRC inactive state, it initiates an RRC connection recovery procedure to receive PTM configuration updates. When the UE is in an RRC connected state, the PTM configuration is delivered by the network via dedicated signaling.

[0045] Figure 3 A flowchart is shown for method 300 for managing MBS according to different schemes. See also Figure 1-3 Method 300 can be performed by one of the network (e.g., BS102) and UE 104a or 104b. Communication between the UE and the BS is performed on channels 103a, 103b, or 155, respectively. Figure 3 As shown by the dashed line in the image.

[0046] In step 305, when the UE is in RRC connected state, the network (e.g., BS102) sends the PTM configuration for each of the multiple MBS to the UE using UE-specific signaling (e.g., dedicated signaling). At 310, when the UE is in RRC connected state, the UE receives the PTM configuration for each of the multiple MBS using UE-specific signaling. Thus, for a UE in RRC connected state, the PTM configuration is transmitted to the UE via dedicated signaling.

[0047] In step 315, when the UE is in RRC connected state, the network uses the PTM configuration received at 310 to send data corresponding to multiple MBS. At 320, when the UE is in RRC connected state, the UE uses the PTM configuration to receive data corresponding to multiple MBS from the network.

[0048] In step 325, the network releases the UE to the RRC inactive state. For example, the network sends a signaling or message to the UE indicating that the UE will be released to the RRC inactive state. In step 330, the UE transitions from the RRC connected state to the RRC inactive state.

[0049] To continue multicast reception on some MBS (referred to as at least one MBS) that the UE has already received since the RRC connection state (e.g., in step 320), the corresponding PTM configuration is retained, which includes the MRB and the lower-layer configuration of the multicast session associated with the at least one MBS. For example, in step 335, the UE retains the PTM configuration for the at least one MBS. In some embodiments, the at least one MBS may be some but not all of a plurality of MBS. In other embodiments, the at least one MBS may be all of a plurality of MBS.

[0050] In step 340, when the UE is in an RRC inactive state, the network transmits at least one MBS using the reserved PTM configuration. In step 345, when the UE is in an RRC inactive state, the UE receives at least one MBS using the reserved PTM configuration.

[0051] In step 350, when the UE is in an RRC inactive state, the UE can determine a triggering event. In some embodiments, the network can initiate a paging to notify the UE of the triggering event, such as modification to a retained PTM configuration (including multicast session inactivation, activation, suspension, release, resumption, update, etc.). In some embodiments, the triggering event includes the UE detecting a multicast reception quality degradation exceeding a certain threshold, causing the UE to initiate an RRC connection via dedicated signaling to resume the process and update the retained PTM configuration. In response to this triggering event, the UE modifies the retained PTM configuration based on UE-specific signaling (dedicated signaling). Examples of UE-specific signaling include RRC reconfiguration messages or RRC release messages sent separately to the UE and containing UE-specific content.

[0052] Figure 4 A flowchart illustrating an exemplary method 400 for managing MBS according to various schemes is shown. See also Figure 1-4 Method 400 can be executed by either UE 104a or 104b. Method 300 is a specific implementation of method 400.

[0053] In step 410, when the UE is in RRC connected state, the UE uses UE-specific signaling to receive the PTM configuration for each of the multiple MBS. Therefore, for a UE in RRC connected state, the PTM configuration is transmitted to the UE via dedicated signaling.

[0054] In step 420, the UE transitions from the RRC connected state to the RRC inactive state. At 430, in response to the transition to the RRC inactive state, while the UE is in the RRC inactive state, it uses the PTM configuration received in the RRC connected state to receive data for at least one of the multiple MBS.

[0055] In some examples, method 400 further includes determining a triggering event when the UE is in an RRC inactive state. In response to determining the triggering event, the UE modifies the PTM configuration to suit the UE.

[0056] Figure 5 This is a flowchart illustrating an exemplary method 500 for managing MBS according to various schemes. See also Figure 1-5 Method 500 can be executed by the network (e.g., BS102). Method 300 is a specific implementation of method 500.

[0057] In step 510, when the UE is in RRC connected state, the network uses UE-specific signaling to send the PTM configuration for each of the multiple MBS to the UE. Therefore, for a UE in RRC connected state, the PTM configuration is transmitted to the UE via dedicated signaling.

[0058] In step 520, the network releases the UE from the RRC connected state to the RRC inactive state. At 530, while the UE is in the RRC inactive state, the network uses the PTM configuration sent when the UE is in the RRC connected state to send data for at least one of the multiple MBS.

[0059] In some examples, method 500 further includes sending the updated PTM configuration for at least one MBS to the UE using UE-specific signaling or broadcast signaling when the UE is in an RRC inactive state.

[0060] In some examples, the phrase "continue to receive when the UE is in an RRC inactive state" refers to at least one MBS from a subset of multiple MBS received when the UE is in an RRC connected state, identifying at least one MBS that will be received or will continue to be received in the RRC inactive state. That is, when the UE is in an RRC inactive state, not all of the multiple MBS need to be or can be received. The at least one MBS is a subset of the multiple MBS received when the UE is in an RRC connected state configured using PTM.

[0061] For example, when the UE is in an RRC inactive state, the network (e.g., BS102) cannot adaptively adjust its configuration based on the UE's reception quality (compared to a UE connected via RRC). Therefore, when the UE is in an RRC inactive state, MBS with high Quality of Service (QoS) requirements are not sent to the UE. The selection of at least one MBS can be determined by the UE or by BS102.

[0062] In some instances, the UE determines whether it can receive an MBS in an RRC inactive state based on one or more conditions. To this end, method 400 further includes the UE selecting at least one MBS from a plurality of MBS based on the QoS requirements of each MBS.

[0063] These factors may include whether the PTM configuration of the MBS includes mechanisms for high QoS requirements. In an example where the MBS PTM configuration includes mechanisms for high QoS, the MBS is suspended in an RRC inactive state. On the other hand, in an example where the MBS PTM configuration does not include any mechanisms for high QoS, the MBS continues to be received in an RRC inactive state. Factors used to determine high QoS requirements include at least one of the following: whether Hybrid Automatic Repeat Request (HARQ) feedback is configured for each of the plurality of MBS; whether Radio Link Control (RLC) Acknowledgment Mode (AM) is configured for at least one MBS Radio Bearer (MRB) for each of the plurality of MBS; or whether Packet Data Convergence Protocol (PDCP) status reporting is configured for each of the plurality of MBS for the at least one MRB. That is, the UE considers whether the PTM configuration includes mechanisms for high QoS requirements by considering whether HARQ feedback is configured, whether the configured MRB has an RLC AM mode, whether some MRBs are configured with PDCP status reporting, etc. In some embodiments, HARQ feedback configured for the MBS indicates that the MBS has high QoS requirements. In some embodiments, AM with RLC enabled for MBS indicates that MBS has high QoS requirements. In some embodiments, PDCP status reporting enabled for MBS indicates that MBS has high QoS requirements.

[0064] In some embodiments, in response to determining that each of at least one PTM configurations meets the condition for retention (e.g., lack of a high QoS mechanism), the PTM configuration of the corresponding MBS session (e.g., at least one MBS) is retained (not suspended) in response to 330, and data for at least one MBS can be received in an RRC inactive state. In some embodiments, in response to determining that the MRB of each of at least one PTM configurations meets the condition for retention (e.g., lack of a high QoS mechanism), the corresponding low-level configuration of the corresponding MBS session (e.g., at least one MBS) is retained (not suspended) in response to 330, and at least one MBS of the corresponding MBS multicast session can be received in an RRC inactive state.

[0065] In some embodiments, the network (e.g., BS102) determines whether MBS can be received in an RRC inactive state based on one or more conditions. For example, when the UE is in an RRC inactive state, the network may determine to stop sending MBS or its sessions with low QoS requirements, such as no data transmission, intermittent data transmission, or temporary data transmission. To reduce the energy consumption of the UE monitoring MBS with low QoS requirements, when the UE is RRC inactive, the network may instruct the UE whether to send MBS to the UE. In other words, when the UE is in an RRC inactive state so that the UE can receive MBS data or continue to receive multicast data, the instruction from the network to the UE can selectively indicate which MBS or MRB the UE needs. Therefore, method 400 further includes receiving an indication identifying at least one MBS from the base station via the UE, wherein, in response to receiving the indication, the at least one MBS is received or continues to be received in the RRC inactive state. Method 500 further includes: when the UE is in RRC inactive, the network determines whether to send at least one MBS to the UE or continue to send at least one MBS to the UE, and the network sends the indication identifying at least one MBS to the UE.

[0066] In some examples, the network can send this indication via RRC signaling. In some embodiments, the RRC signaling includes RRC reconfiguration. The RRC reconfiguration signaling or message includes: when the UE is in an RRC inactive state, it retains indication information of a reserved PTM configuration for the at least one MBS. In other words, after the UE receives an RRC release with a suspended configuration and transitions to an RRC inactive state at 330, the UE retains the reserved PTM configuration, which includes all or some of the multicast MRBs indicated in the RRC reconfiguration and the corresponding low-level configurations for the corresponding MBS sessions. The UE receives or continues to receive data for the corresponding at least one MBS while in the RRC inactive state.

[0067] In some embodiments, the indication identifying the retained PTM configuration can be per MBS or per MRB. In other words, the indication can identify each of at least one MBS (the indication information may include a list of MBS identifiers, such as Temporary Mobile Group Identifiers (TMGIs)), or it can identify each MRB that will be used for at least one MBS. If such an indication is per MRB, the UE retains only the indicated MRB and the low-level configuration of the at least one MBS identified when in RRC inactive. That is, other MRBs of the PTM configuration are suspended when transitioning to RRC inactive. If such an indication is per MBS, all MRBs and low-level configurations of the at least one MBS identified by the indication are retained when transitioning to RRC inactive. No MRBs associated with the at least one MBS identified in the indication are suspended when transitioning to RRC inactive.

[0068] In some embodiments, the RRC signaling includes an RRC version that includes a list of indications regarding which PTM configuration (referred to as at least one MBS) should be retained when the UE is in an RRC inactive state. This indication may include a list of MBS identifiers, such as Temporary Mobile Group Identity (TMGI). In response to the UE receiving an RRC release with a suspension configuration from the network (e.g., in step 325), the UE does not suspend any MRBs associated with at least one MBS in the list and will not reset the HARQ procedures and associated timers associated with at least one MBS. The UE receives or continues to receive data for at least one MBS while in an RRC inactive state. In some embodiments, the network provides a list of MRBIDs and a list of multicast services in the RRC release signaling or message. The UE retains only the indicated MRB and suspends the other MRBs.

[0069] Therefore, this indication is received by the UE via RRC reconfiguration or RRC release. The indication includes an indication for each of a plurality of MBS or for each MRB associated with a plurality of MBS. The indication includes a list of at least one MBS or at least one MRB that will be retained when the UE is in an RRC inactive state. In some embodiments, in response to transitioning to an RRC inactive state, the UE performs at least one of the following: retains (e.g., does not suspend) the indicated at least one MRB, stops all running timers except for the multicast discontinuous reception (DRX) timer used for the indicated at least one MBS, refreshes the soft buffer for all downlink HARQ procedures except for the downlink HARQ procedure used for the indicated at least one MBS, or continues to monitor the Group Radio Network Temporary Identifier (G-RNTI) corresponding to the indicated at least one MBS.

[0070] In some examples, the triggering event includes the network (e.g., BS102) sending a notification to the UE. In response to receiving the notification, the UE modifies the PTM configuration for at least one MBS. In some embodiments, the notification includes paging. The network may apply a group paging mechanism to notify multiple UEs via paging. The paging payload contains a list of MBS session IDs that the UE has joined, such as a list of TMGIs. The notification further includes a notification event associated with the MBS session ID.

[0071] For UEs receiving MBS in RRC inactive state, the triggering events or conditions for group paging include MBS suspension, MBS recovery, MBS inactive, MBS activation, MBS release, or PTM configuration update, in order to reduce unnecessary monitoring energy consumption and reduce the frequency of RRC state transitions.

[0072] For MBS suspension, the notification indicates that one of at least one MBS will be suspended. Modifying the PTM configuration includes, when the UE is in an RRC inactive state, the UE stopping listening to the one MBS, and when the UE is in an RRC inactive state, the UE suspending the PTM configuration corresponding to the one MBS. For example, the Radio Access Network (RAN) node suspends MBS transmission. Therefore, the UE does not need to restore the RRC connection to receive the suspended configuration, but can remain in an RRC inactive state to suspend the MBS reception configuration by, for example, suspending the associated MRB and stopping MBS data reception in the MAC and physical layers (e.g., stopping G-RNTI for MBS monitoring).

[0073] When the UE is in an RRC inactive state, monitoring MBS data will cause unnecessary power consumption if no data is being transmitted in the RAN temporarily. To improve power efficiency, the network can use group paging (e.g., notification) to inform the UE that certain MBS are suspended or instruct the UE to stop monitoring such MBS and suspend the associated PTM configuration (i.e., without releasing the configuration). In one embodiment, an indication message (e.g., a 1-bit indication) is associated with the MBS session identifier in the group paging payload, indicating that the MBS session has been suspended. Upon receiving such a group paging, the UE stops monitoring MBS data and suspends the associated PTM configuration. In one embodiment, if no such indication message is received, the UE initiates a conventional RRC connection recovery procedure, transitioning to the RRC connected state.

[0074] Regarding MBS recovery, the network resumes MBS transmission. Therefore, the UE recovers the associated MRB and resumes G-RNTI monitoring of the recovered MBS, while remaining in RRC inactive. Therefore, a notification indicates the recovery of one MBS. Modifying the PTM configuration includes: when the UE is in the RRC inactive state, the UE recovers the PTM configuration corresponding to the one MBS; and when the UE is in the RRC inactive state, the UE uses the PTM configuration to receive the one MBS.

[0075] To improve power efficiency, certain MBSs with low QoS that are temporarily unavailable for data transmission to the UE when the UE is in an RRC inactive state can be suspended. The network can use group paging (e.g., notification) to resume reception of such MBSs. In one embodiment, an indication message (e.g., a 1-bit indication) is associated with the MBS session identifier in the group paging payload, indicating that the MBS session has been resumed. Upon receiving such a group paging, the UE resumes the corresponding MBS MRB and the low-level configuration of the MBS session and begins multicast data monitoring. In one embodiment, if no such indication message is available, the UE initiates a conventional RRC connection recovery procedure, transitioning to an RRC connected state.

[0076] Regarding MBS inactivation, in response to receiving MBS inactivation signaling from the core network, the RAN node releases the MBS radio resources and stops MBS transmission. In response to receiving a notification indicating inactive MBS, the UE releases the associated PTM configuration (e.g., MRB and PTM configurations in lower layers) and stops multicast reception. Therefore, the notification indicates that one of at least one MBS will be inactive. Modifying the PTM configuration includes, when the UE is in an RRC inactive state, the UE stopping listening to the one MBS, and when the UE is in an RRC inactive state, the UE releasing the PTM configuration corresponding to the one MBS.

[0077] If no data is available for the MBS being transmitted, and the MBS is inactive in the network, monitoring MBS data for a UE in an RRC inactive state results in unnecessary power consumption. While the network could also notify the UE to restore the RRC connection, this could lead to additional signaling overhead. To improve power efficiency, the network uses group paging functions (e.g., notifications) to inform the UE that certain MBS are inactive. Once this indication is received, the UE stops monitoring such MBS and releases the associated PTM configuration.

[0078] In one embodiment, an indication message (e.g., a 1-bit indication) is associated with the MBS session identifier in the group paging payload, indicating that the MBS session has been inactive. Upon receiving such a group paging, the UE stops monitoring MBS data and releases the associated PTM configuration. In one embodiment, if no such indication message is found, the UE initiates a conventional RRC connection recovery procedure, transitioning to an RRC connected state.

[0079] Regarding PTM configuration updates: The network may update the PTM configuration of a specific MBS within the at least one MBS. If the network updates the PTM configuration (e.g., the network reallocates radio resources for the MBS), the UE may need to frequently switch between RRC-inactive and RRC-connected states, resulting in unnecessary power consumption and signaling overhead. To improve power and air interface resource efficiency, the network uses group paging functions (e.g., notifications) to notify the UE that certain multicast PTM configurations have been updated and / or indicates the method of delivering the updated configuration (i.e., RRC-specific signaling or MCCH).

[0080] In one embodiment, indication information (e.g., a 1-bit indication) is associated with the MBS session identifier in the group paging payload, indicating that the PTM configuration of the MBS session has been updated. Upon receiving such a group paging, the UE initiates an RRC connection recovery procedure and may add a recovery reason value to indicate that the reason for recovery is an updated PTM configuration. BS102 may add the PTM configuration to an RRC message (e.g., an RRC release). Upon receiving an RRC message, the UE updates the PTM configuration of the associated MBS and continues to receive data for that MBS in an RRC inactive state. In some embodiments, the notification indicates that the PTM configuration for one of the at least one MBS will be updated. Modifying the PTM configuration includes the UE initiating an RRC connection recovery procedure, and in response to initiating the RRC connection recovery procedure, the UE receives indication information from the network for one of the at least one MBS. In some embodiments, the UE receives the updated PTM configuration for one of the at least one MBS, and the UE receives data from the network corresponding to the updated PTM configuration. In some embodiments, the indication information is the updated PTM configuration and is received by the UE via an RRC version. Therefore, when a UE initiates an RRC connection recovery procedure, in some embodiments, the updated PTM configuration is sent to the UE via RRC release. In other embodiments, the UE initiates the RRC connection recovery procedure and actually enters the RRC connected state to receive the update. In one embodiment, the indication information is the updated PTM configuration, and the UE in the RRC recovery message indicates the MBS session ID, or uses the MBS session ID as the UE contention resolution identifier during the random access procedure. The following RRC release message includes the updated PTM configuration.

[0081] In another embodiment, an indication message (e.g., a 1-bit indication) is associated with the MBS session identifier in the group paging payload, indicating that the PTM configuration of the MBS session has been updated. Upon receiving such a group paging, the UE updates the PTM configuration obtained from broadcast signaling (e.g., MCCH) and continues to receive data for that MBS in an RRC inactive state. In some embodiments, the network sends an indication message to the UE via an RRC version to indicate that the UE obtains the updated PTM configuration from broadcast signaling (e.g., MCCH). The updated PTM configuration is received by the UE from the broadcast signaling (e.g., MCCH).

[0082] In another embodiment, if no such indication is found, the UE initiates a conventional RRC connection recovery procedure and transitions to the RRC connection state.

[0083] The network can use signaling such as group paging associated with a list of MBS session IDs in the paging payload to send notifications indicating modifications to the PTM configuration of at least one MBS. The notification can have different lengths depending on the supported functions. For example, one bit is required if only indication of suspension and resumption is needed. Two bits are required if support for all suspension, resumption, deactivation, and update functions is required.

[0084] In some examples, PTM configuration updates can be triggered by MAC CE when the UE is in an RRC inactive state. When the UE is in an RRC inactive state, the network can use MAC CE to indicate PTM configuration updates (including suspension, resumption, inactivation, and updates for certain MBS).

[0085] In one embodiment, a MAC CE including indication information identified by the corresponding Logical Channel ID (LCID) is sent by the network to the UE (e.g., by multiplexing with multicast data) to indicate one or more of the following for a certain MBS: suspension, resumption, inactivation, and update.

[0086] Regarding MBS suspension, the RAN node (e.g., BS102) suspends MBS transmission. Therefore, the UE does not need to restore the RRC connection to receive the suspended configuration; instead, it remains in an RRC inactive state to suspend the MBS reception configuration, for example, by suspending the associated MRB in the MAC and physical layers and stopping MBS data reception. For example, the UE can stop G-RNTI for multicast service monitoring.

[0087] Upon MBS recovery, the network resumes MBS transmission. Therefore, the UE restores the associated MRB and resumes G-RNTI monitoring while remaining in an RRC inactive state.

[0088] Regarding MBS inactivation, in response to receiving MBS inactivation signaling from the core network, the RAN node (e.g., BS102) releases MBS radio resources and stops MBS transmission. In response to receiving such an indication, the UE releases the associated PTM configuration (e.g., MRB and PTM configurations in the lower layers) and stops MBS reception.

[0089] For PTM configuration updates, the network can update the PTM configuration of certain MBSs. In response to a MACCE indicating an update, the UE initiates an RRC connection recovery procedure and adds a recovery reason value to indicate that the reason for the RRC recovery is the update of the MBS's PTM configuration.

[0090] In some embodiments, the network can transmit a MAC CE to the UE via a PTM, which is identified by a corresponding G-RNTI associated with the MBS.

[0091] Therefore, in some examples, determining the triggering event includes the UE receiving a MAC CE from the network while in an RRC inactive state, the MAC CE indicating that the PTM configuration for one of at least one MBS will be modified. The MAC CE includes the service ID or service index of an MBS. Modifying the PTM configuration includes one of MBS suspension, MBS resumption, MBS inactivation, or updating the PTM configuration.

[0092] In some configurations, when the UE is in an RRC inactive state, an RRC connection recovery process is triggered when the MBS reception quality drops to a certain threshold. The MBS reception quality can be determined by the BS102 or the UE. For example, the UE can measure at least one of the following: Reference Signal Received Power (RSRP) or Reference Signal Received Quality (RSRQ) of the configured measurement resources, packet loss rate (e.g., in Packet Data Convergence Protocol (PDCP)), or Block Error Rate (BLER) in Layer 1. The network (e.g., the BS102) can indicate the relevant threshold in dedicated signaling to the UE, or alternatively, the UE can determine the relevant threshold. Thus, in other words, the reception quality is determined based on at least one of the measured signal strength or packet loss rate.

[0093] When the UE is in an RRC inactive state, it continuously monitors these indicators (e.g., measured signal strength or packet loss rate) while receiving at least one MBS. In response to determining a reception quality degradation threshold for the MBS, the UE initiates an RRC connection recovery procedure. The UE sets a recovery reason value to indicate that the reason for initiating the RRC connection recovery procedure is reception quality degradation.

[0094] In some embodiments, the network (e.g., BS102) can restore the UE's RRC connection to update the PTM configuration or add the PTM configuration in dedicated signaling (e.g., RRC version). Once such an RRC message is received, the UE updates the PTM configuration of the MBS and continues to receive data for that MBS in either an RRC connected or RRC inactive state.

[0095] Therefore, in some embodiments, determining the triggering event includes the UE determining, while in an RRC inactive state, that the reception quality of one of at least one MBS is below a threshold. Modifying the PTM configuration includes the UE initiating the RRC connection recovery procedure and adding a recovery reason value to indicate the initiation of the RRC connection recovery procedure to update the PTM configuration for the one MBS. Furthermore, the UE receives the updated PTM configuration for the one MBS from the network. The UE uses the updated PTM configuration to receive the one MBS from the network.

[0096] In some examples, when the UE is in an RRC inactive state, to reduce the frequency of state transitions caused by PTM configuration updates, the PTM configuration may be delivered during an RRC release. Therefore, modifying the PTM configuration for at least one MBS includes receiving an updated PTM configuration in the RRC release signaling, wherein the updated PTM configuration includes at least one of a multicast configuration and a broadcast configuration. The forms of PTM configuration in the RRC version include, but are not limited to, multicast configurations carried in UE-specific RRC reconfigurations or broadcast PTM configurations carried in the MCCH of multiple UEs. For example, Figure 6 This is a table illustrating the PTM configuration of an embodiment carried in a dedicated RRC reconfiguration for the UE according to some schemes. Figure 7 A table showing the broadcast PTM configuration carried in the MCCH according to some schemes is illustrated.

[0097] In some examples, when UE 104a or 104b is in an RRC connected or RRC inactive state, the UE receives PTM configuration or its updates from the network (e.g., BS102 or cell 101) via broadcast signaling (e.g., MCCH). For example, when the UE is in an RRC connected state, the UE monitors broadcast signaling or MCCH to receive PTM configuration or its updates for multicast. When the UE is in an RRC inactive state, the UE monitors broadcast signaling or MCCH to receive PTM configuration or its updates for multicast, so that the UE does not need to restore the RRC connection to receive PTM configuration or its updates.

[0098] In some examples, to minimize protocol modifications, the multicast PTM configuration carried in the MCCH can be the same as the broadcast PTM configuration; examples of this are shown in [examples would be inserted here]. Figure 7 As shown in the image.

[0099] Figure 8 This is a flowchart illustrating an exemplary method 800 for managing MBS according to various schemes. See also Figure 1-8Method 800 can be performed by one of the network (e.g., BS 102) and UE 104a or 104b. Communication between the UE and the BS is performed on channels 103a, 103b, or 155, respectively. Figure 8 As shown by the dashed line in the image.

[0100] In step 802, when the UE is in RRC connected state, the network (e.g., BS102) sends an indication message indicating that the PTM configuration for each of the multiple MBSs is obtained from broadcast signaling. In step 804, the UE receives the indication message indicating that the PTM configuration for each of the multiple MBSs is obtained from broadcast signaling, wherein the broadcast signaling is received when the UE is in RRC connected state.

[0101] In step 805, when the UE is in RRC connected state, the network (e.g., BS102) uses the UE's broadcast signaling to send the PTM configuration for each of the multiple MBSs to the UE. In step 810, when the UE is in RRC connected state, the UE uses broadcast signaling to receive the PTM configuration for each of the multiple MBSs. Therefore, for a UE in RRC connected state, the PTM configuration is transmitted to the UE via broadcast signaling.

[0102] In step 815, when the UE is in RRC connection state, the network uses the PTM configuration received in step 810 to send data corresponding to multiple MBS. In step 820, when the UE is in RRC connection state, the UE uses the PTM configuration to receive data corresponding to multiple MBS from the network.

[0103] In step 825, the network releases the UE to the RRC inactive state. For example, the network sends appropriate signaling, messages, or notifications to the UE indicating that the UE will be released to the RRC inactive state. In step 830, the UE transitions from the RRC connected state to the RRC inactive state.

[0104] In step 835, the UE monitors broadcast signaling to obtain updates to the PTM configuration. In step 840, the network transmits the updated PTM configuration via broadcast signaling. In step 845, the UE receives the updated PTM configuration via broadcast signaling. In step 850, the network uses the updated PTM configuration to transmit at least one MBS. In step 855, the UE uses the updated PTM configuration to receive at least one MBS.

[0105] Figure 9 This is a flowchart illustrating an exemplary method 900 for managing MBS according to various schemes. See also Figure 1-9Method 900 can be executed by either UE 104a or 104b. Method 800 is a specific implementation of method 900.

[0106] In step 910, when the UE is in RRC connected state, the UE receives indication information indicating that the PTM configuration for each of the multiple MBSs is obtained from broadcast signaling. In step 920, when the UE is in RRC connected state, the UE uses broadcast signaling for receiving the multiple MBSs to receive the PTM configuration for each of the multiple MBSs. The PTM configuration is used to receive the multiple MBSs when the UE is in RRC connected state.

[0107] In some examples, method 900 further includes the UE receiving multiple MBS from the network based on a PTM configuration while the UE is in an RRC connected state. The UE transitions from the RRC connected state to an RRC inactive state. While the UE is in the RRC inactive state, the UE monitors broadcast signaling for PTM configuration. The UE uses the broadcast signaling to receive the PTM configuration from the network. The PTM configuration is used to receive at least one MBS while the UE is in the RRC inactive state. The UE receives at least one MBS from the network based on the PTM configuration.

[0108] Figure 10 This is a flowchart illustrating an exemplary method 1000 for managing MBS according to various schemes. See also Figure 1-10 Method 1000 can be executed by the network (e.g., BS102). Method 800 is a specific implementation of method 1000.

[0109] In step 1010, the network (e.g., BS102) sends indication information to the UE using UE-specific signaling, which indicates that when the UE is in an RRC connected state, it should obtain the PTM configuration for each of the multiple MBS from the broadcast signaling used to send multiple MBS, and when the UE is in an RRC inactive state, it should obtain the PTM configuration for each of the multiple MBS from the broadcast signaling used to send multiple MBS.

[0110] In step 1020, the network uses broadcast signaling to send to the UE a PTM configuration for sending multiple MBS when the UE is in RRC connected state and a PTM configuration for sending at least one MBS when the UE is in RRC inactive state.

[0111] In some examples, method 1000 also includes the network sending multiple MBS based on the PTM configuration to the UE when the UE is in the RRC connected state. The network releases the UE from the RRC connected state to the RRC inactive state. When the UE is in the RRC inactive state, the network sends at least one MBS to the UE based on the PTM configuration.

[0112] In some embodiments, there are multicast services with both high and low QoS requirements. Multicast PTM configuration via broadcast signaling (e.g., MCCH) lacks the flexibility of UE-level configuration, which may fail to meet high QoS requirements. For multicast services with high QoS requirements, dedicated signaling can be used to send PTM configuration to ensure reliability. For multicast services with low QoS requirements, even if the UE is in an RRC connected state, the UE can obtain the PTM configuration by monitoring MCCH signaling based on gNB scalability indications.

[0113] In some examples, a method is provided to indicate the distribution of PTM configuration to UEs via broadcast signaling, using the MCCH carrying the PTM configuration for a UE that needs to receive MBS, and other ancillary information, such as the service availability of MBS service in a neighboring cell. The MCCH also uses a modification period, where modification of the MCCH content is only permitted at the boundary of each modification period. A notification mechanism is used to announce changes to the MCCH content due to the start, modification, or termination of a broadcast session, as well as changes due to modifications to neighboring cell information.

[0114] When the UE is in RRC connected state, it obtains PTM configuration by receiving MCCH, which can be used when the UE is in RRC inactive state. In this case, it would be beneficial to assist the UE in using some dedicated signaling to obtain broadcast (e.g., MCCH) information to reduce power consumption and overall signaling overhead. The assisting or indicative information via dedicated signaling (e.g., UE-specific signaling) includes: (1) information indicating that the PTM configuration is obtained via broadcast signaling (e.g., MCCH); (2) the associated System Information Block (SIB) required to receive the broadcast signaling (e.g., MCCH); and (3) the associated broadcast (e.g., MCCH) information, including the information required to receive the PTM configuration.

[0115] Therefore, signaling dedicated to the UE (e.g., special signaling) is used to receive indication information. This indication information instructs the UE to obtain PTM information from broadcast signaling. The indication information includes at least one of the following: information indicating that the PTM configuration of the at least one MBS is provided via broadcast signaling, an SIB for receiving broadcast signaling, and broadcast signaling information containing the PTM configuration of the plurality of MBS and / or the at least one MBS.

[0116] In some configurations, dedicated signaling (e.g., RRC reconfiguration) carries indication information that instructs the UE to obtain a multicast PTM configuration or an update to the multicast PTM configuration by monitoring the MCCH in an RRC connected state. In other words, the indication information includes an indication that at least one of a PTM configuration or an update to the PTM configuration has been received via broadcast signaling. Upon receiving this indication information, the UE initiates an MCCH process to receive multicast data, for example, by receiving the MCCH configuration information from the SIB, and then obtaining the relevant multicast PTM configuration information by monitoring the MCCH. The method also includes the UE monitoring an SIB message containing the configuration for receiving broadcast signaling. The UE receives broadcast signaling containing the PTM configuration or an update to the PTM configuration from the network. Based on the updated PTM configuration, the UE receives data from the network corresponding to at least one MBS.

[0117] In some configurations, dedicated signaling (e.g., RRC reconfiguration) carries an associated system information block message, which includes information required to receive the MCCH. The UE performs MCCH monitoring based on this information. In some embodiments, the SIB message explicitly indicates that for such an MBS, the UE obtains the PTM configuration by monitoring the MCCH instead of through dedicated signaling. Without such an indication, the UE assumes that the PTM configuration is delivered via conventional configuration methods (e.g., through dedicated signaling). Therefore, the indication information includes the SIB message. The SIB message contains the configuration for receiving broadcast signaling. The indication information indicates that the PTM configuration or an update to the PTM configuration is obtained from the broadcast signaling. The SIB message is used to obtain the configuration for receiving broadcast signaling. Data corresponding to the MBS is received based on the PTM configuration. This mechanism reduces the latency of obtaining the associated SIB.

[0118] In some configurations, dedicated signaling (e.g., RRC reconfiguration) carries the MCCH content or the entire MCCH content for the MBS of interest to the UE. This indicates that for such an MBS, the corresponding PTM configuration is delivered via a method similar to MCCH. The UE then applies the multicast PTM configuration to the MCCH content and, upon receiving the MCCH content, performs multicast data reception based on this information. The UE can either listen for the MCCH and MCCH change notifications itself after the MCCH listening process, or obtain the MCCH via other dedicated signaling containing MCCH content. This indication information includes broadcast signaling information containing the PTM configuration for at least one MBS. In some examples, broadcast signaling information containing the PTM configuration for at least one MBS is received. Data corresponding to the at least one MBS is received based on the PTM configuration. This mechanism reduces latency caused by monitoring the MCCH.

[0119] In some configurations, when a UE is in an RRC connected state, it periodically monitors the MCCH during modification cycles to obtain the multicast PTM configuration. Compared to dedicated signaling configurations, this offers improved scalability, reducing air interface overhead associated with configuration updates if there are many UEs in the cell occupying the same MBS. However, continuous MCCH monitoring also introduces additional power consumption, especially in the current MCCH modification notification mechanism, where the UE must monitor MCCH change notifications every modification cycle, even if the modification is for other MBS in the cell (broadcast and multicast services; if the MCCH is used for multicast services for RRC-inactive UEs). Therefore, it is possible that a UE monitors the MCCH, but the PTM configuration it is interested in is not updated.

[0120] In some embodiments, to reduce power consumption and notify the UE of PTM updates for multicast services, the network sends a short message with group paging to the UE. In response to receiving the short message indicating a PTM update to the MBS, the UE applies an MCCH acquisition procedure in the next modification. If no short message is received, the UE does not perform the MCCH acquisition procedure. Thus, in some examples, the UE receives a short message from the network indicating an update to the PTM configuration. In response to receiving the short message, the UE performs an acquisition procedure (e.g., an MCCH acquisition procedure) to obtain broadcast signaling for receiving updates to the PTM configuration.

[0121] In some embodiments, to reduce power consumption when monitoring the MCCH and changes in multicast services, the network sends an indication in the Downlink Control Information (DCI) to indicate whether there is an update or modification to the PTM configuration of the MBS. For UEs only interested in multicast services, if no such indication is found, the UE can ignore MCCH reception during the modification period. Therefore, in some examples, the UE receives DCI broadcast signaling from the network indicating an update to the PTM configuration. In response to receiving the DCI, the UE performs an acquisition procedure to obtain the broadcast signaling for receiving the update to the PTM configuration.

[0122] In some embodiments, when the UE is in an RRC connected state, the network can notify the UE via dedicated signaling (e.g., RRC signaling, MAC CE) to indicate that the PTM configuration of the multicast service UE is interested in being updated. During the current or next modification cycle, the UE listens for MCCH transmissions to receive the latest PTM configuration of the multicast service it is interested in. Thus, in some examples, the UE receives a MAC CE from the network indicating an update to the PTM configuration. In response to receiving the MAC CE, the UE performs an acquisition procedure to obtain broadcast signaling for receiving the update to the PTM configuration.

[0123] In some examples, when the UE is in an RRC connected state indicating an update to the PTM configuration, the UE receives UE-specific update signaling from the network. In response to receiving the update signaling, broadcast signaling is monitored in the current or next modification period to update the PTM configuration.

[0124] In some configurations, when a UE is in an RRC inactive state, if an indication message is added to the RRC connected state UE, indicating that the PTM configuration is obtained from the MCCH via multicast, then the UE in the RRC inactive state performs a method similar to that of the MCCH. For example, the UE receives indications from the network indicating the receipt of the PTM configuration and updates to the PTM configuration via broadcast signaling in both the RRC connected state and the RRC inactive state.

[0125] In some examples, UE 104a or 104b receives PTM configuration or its updates from the network (e.g., BS102 or cell 101) via dedicated signaling and broadcast signaling (e.g., MCCH). For example, when the UE is in an RRC inactive state, the UE monitors broadcast signaling (e.g., MCCH) to receive PTM configuration or its updates for multicast. When the UE is in an RRC connected state, the UE receives PTM configuration from the network via dedicated signaling.

[0126] In some examples, when the UE is in RRC connected state, the MBS PTM configuration is obtained from dedicated signaling. When the UE is in RRC inactive state, the MBS PTM configuration is obtained from broadcast signaling (e.g., MCCH).

[0127] Figure 11 This is a flowchart illustrating an exemplary method 1100 for managing MBS according to various schemes. See also Figure 1-11 Method 1100 can be performed by either a network (e.g., BS 102) or a UE 104a or 104b. Communication between the UE and the BS is performed on channels 103a, 103b, or 155, respectively. Figure 11 As shown by the dashed line in the image.

[0128] In step 1105, when the UE is in RRC connected state, the network (e.g., BS102) sends the PTM configuration to the UE using UE-specific first signaling (e.g., dedicated signaling) for each of at least one MBS. In step 1110, when the UE is in RRC connected state, the UE uses UE-specific first signaling to receive the PTM configuration for each of at least one MBS. Thus, for a UE in RRC connected state, the PTM configuration is transmitted to the UE via dedicated signaling.

[0129] In step 1115, when the UE is in RRC connection state, the network uses the PTM configuration received in step 1110 to send data corresponding to at least one MBS. In step 1120, when the UE is in RRC connection state, the UE uses the PTM configuration to receive data corresponding to at least one MBS from the network.

[0130] In step 1125, when the UE is in an RRC inactive state, the network sends indication information to the UE using a second signaling method. This indication information indicates that a PTM configuration for receiving at least one MBS should be obtained from broadcast signaling when the UE is in an RRC inactive state. In step 1130, when the UE is in an RRC connected state, the UE receives indication information from the network using UE-specific second signaling. This indication information indicates that a PTM configuration for receiving at least one MBS should be obtained from broadcast signaling when the UE is in an RRC inactive state. In some embodiments, the first signaling and the second signaling are the same signaling. In other embodiments, the first signaling and the second signaling are different.

[0131] In step 1135, the network releases the UE to the RRC inactive state. For example, the network sends appropriate signaling, messages, or notifications to the UE indicating that the UE will be released to the RRC inactive state. In 1140, the UE transitions from the RRC connected state to the RRC inactive state.

[0132] In step 1145, the UE monitors broadcast signaling for the PTM configuration of any one of at least one MBS, or updates to the PTM configuration of any one of at least one MBS. In step 1150, when the UE is in an RRC inactive state, the network sends the PTM configuration or an update to the PTM configuration via broadcast signaling. In step 1155, when the UE is in an RRC inactive state, the UE receives the PTM configuration or an update to the PTM configuration from the network via broadcast signaling.

[0133] In step 1160, when the UE is in an RRC inactive state, the network uses the updated PTM configuration to send at least one MBS. In step 1165, when the UE is in an RRC inactive state, the UE uses the updated PTM configuration to receive at least one MBS.

[0134] Figure 12 This is a flowchart illustrating an exemplary method 1200 for managing MBS according to various schemes. See also Figure 1-12 Method 1200 can be executed by either UE 104a or 104b. Method 1100 is a specific implementation of method 1200.

[0135] In step 1210, when the UE is in RRC connected state, the UE uses UE-specific first signaling to receive the PTM configuration for each of at least one MBS. Therefore, for a UE in RRC connected state, the PTM configuration is transmitted to the UE via dedicated signaling.

[0136] In step 1220, when the UE is in an RRC connected state, the UE uses a UE-specific second signaling to receive indication information from the network. This indication information indicates that when the UE is in an RRC inactive state, it obtains a PTM configuration for receiving at least one MBS from broadcast signaling. In some embodiments, the first and second signaling are the same signaling. In other embodiments, the first and second signaling are different.

[0137] In some examples, method 1200 further includes: when the UE is in an RRC inactive state, the UE uses broadcast signaling to receive PTM configuration for receiving at least one MBS from the network; and when the UE is in an RRC inactive state, the UE receives PTM configuration from the network via broadcast signaling.

[0138] The indication information includes at least one of the following: information indicating the PTM configuration of at least one MBS provided via broadcast signaling, an SIB for receiving broadcast signaling, and broadcast signaling information containing the PTM configuration of at least one MBS used in the RRC inactive state.

[0139] Figure 13 A flowchart illustrating an exemplary method 1300 for managing MBS according to various schemes is shown. See also Figure 1-13 Method 1300 can be executed by a network (e.g., BS102). Method 1100 is a specific implementation of method 1300.

[0140] In step 1310, when the UE is in RRC connected state, the network (e.g., BS102) sends a UE-specific first signaling (e.g., dedicated signaling) PTM configuration to the UE for each of at least one MBS. Thus, for a UE in RRC connected state, the PTM configuration is transmitted to the UE via dedicated signaling.

[0141] In step 1320, the network sends indication information to the UE using second signaling when the UE is in an RRC inactive state. This indication information indicates the PTM configuration for receiving at least one MBS from broadcast signaling when the UE is in an RRC inactive state. In some embodiments, the first and second signaling are the same signaling. In other embodiments, the first and second signaling are different.

[0142] In some embodiments, method 1300 further includes the network using broadcast signaling to send a PTM configuration to the UE for receiving at least one MBS when the UE is in an RRC inactive state, and the network sending an update to the PTM configuration to the UE when the UE is in an RRC inactive state.

[0143] Therefore, when the UE is in RRC connected state, the PTM configuration of MBS is transmitted via dedicated signaling. In response to the UE being released to RRC inactive state by the network, the PTM configuration is retrieved again from broadcast (e.g., MCCH) in order to continue MBS reception.

[0144] When the UE is in an RRC inactive state, it is beneficial to assist the UE in obtaining MCCH information using some dedicated signaling (e.g., RRC reconfiguration, RRC release, etc.). This reduces power consumption and overall signaling overhead. The indication information via dedicated signaling includes information indicating that MBS configuration is broadcast (e.g., MCCH), at least one of the associated SIB and related MCCH information required to receive MCCH, including information required to receive MBS configuration.

[0145] In some embodiments, the RRC reconfiguration carries indication information instructing the UE to obtain a multicast PTM configuration or an update to the multicast PTM configuration by listening to the MCCH in an RRC inactive state. Therefore, in some embodiments, the indication information includes an indication that at least one of the following has been received via broadcast signaling: a PTM configuration of at least one MBS or an update to the PTM configuration. When the UE is in an RRC inactive state, broadcast signaling is received and monitored by the UE in response to the reception indication. This indication information is carried in the RRC reconfiguration message.

[0146] In one embodiment, in response to receiving an indication and in response to the UE being released to an RRC inactive state by the network, the corresponding PTM configuration (e.g., the associated MRB and low-layer configuration of the multicast session) is temporarily retained to continue MBS reception. In the RRC inactive state, the UE begins a process similar to MCCH reception, such as receiving the SIB to obtain MCCH configuration information, and then obtaining the relevant PTM configuration information by listening to the MCCH. Before obtaining an updated PTM configuration, the UE continues to apply the current PTM configuration to receive one or more of at least one MBS, wherein the current PTM configuration can be received when the UE is in an RRC connected state. Therefore, in response to receiving the indication and in response to the UE transitioning from an RRC connected state to an RRC inactive state, the UE retains the PTM configuration corresponding to one of the at least one MBS to continue receiving that MBS. After receiving the PTM configuration via broadcast signaling in the RRC inactive state, the UE releases the PTM configuration received in the RRC connected state.

[0147] For example, when the UE receives this indication and the network releases the UE to the RRC inactive state, it initiates a process similar to MCCH in the RRC inactive state to receive multicast data. For instance, it receives the MCCH configuration information from the SIB and then obtains the relevant multicast PTM configuration information by listening to the MCCH. Therefore, in response to receiving this indication, the UE releases the PTM configuration corresponding to at least one MBS in response to the UE transitioning from the RRC connected state to the RRC inactive state, and receives broadcast signaling for updating the PTM configuration in response to the UE transitioning from the RRC connected state to the RRC inactive state.

[0148] In some configurations, the RRC version carries an indication message that in the RRC inactive state, the UE obtains the multicast PTM configuration or an update of the multicast PTM configuration by listening to the MCCH.

[0149] In response to a transition from an RRC connected state to an RRC inactive state, the UE monitors an SIB message, which includes a configuration for receiving broadcast signaling when the UE is in the RRC inactive state. When the UE is in the RRC inactive state, it receives broadcast signaling from the network for obtaining a PTM configuration or an update to the PTM configuration for at least one MBS. Based on the updated PTM configuration, the UE receives data corresponding to at least one MBS.

[0150] In one embodiment, in response to the UE being released to an RRC inactive state by the network, the corresponding PTM configuration (e.g., the associated MRB and low-layer configuration of the multicast session) is temporarily retained to continue MBS reception. In the RRC inactive state, the UE initiates a procedure similar to MCCH to receive MBS data, for example, receiving the SIB to obtain MCCH configuration information, and then obtaining the relevant multicast PTM configuration information by listening to the MCCH. Therefore, in response to the reception indication information, the UE retains the PTM configuration corresponding to one of the at least one MBS to continue receiving that one MBS in response to the UE transitioning from the RRC connected state to the RRC inactive state. After receiving the PTM configuration via broadcast signaling in the RRC inactive state, the UE releases the PTM configuration received in the RRC connected state. Before obtaining an updated PTM configuration, the UE continues to apply the current PTM configuration to receive one or more of the at least one MBS, wherein the current PTM configuration can be received when the UE is in the RRC connected state.

[0151] For example, when a UE is released to an RRC inactive state by the network, the UE begins a process similar to MCCH in the RRC inactive state to receive MBS data. For instance, it receives SIBs to obtain MCCH configuration information and then obtains relevant multicast PTM configuration information by listening to the MCCH. In other words, in response to receiving indication information, the UE releases the PTM configuration corresponding to one of the at least one MBS in response to the wireless communication device transitioning from the RRC connected state to the RRC inactive state. The UE receives the broadcast signaling for updating the PTM configuration in response to the UE transitioning from the RRC connected state to the RRC inactive state.

[0152] In some configurations, the RRC version carries an associated SIB message, which includes information required to receive the MCCH. The UE is released to an RRC inactive state, and the UE performs MCCH monitoring based on this information. This SIB, indicating the information, is carried in the RRC release message. This mechanism reduces the latency of acquiring the associated SIB.

[0153] In some examples, in response to a transition from an RRC connected state to an RRC inactive state, when the UE is in the RRC inactive state, the UE receives broadcast signaling from the network based on the SIB to obtain or update the PTM configuration for use in at least one MBS. Based on the updated PTM configuration, the UE receives data from the network corresponding to at least one MBS.

[0154] In some embodiments, the SIB explicitly indicates that for the selected MBS, in order to continue MBS reception, in response to the UE being released to the RRC inactive state, the corresponding PTM configuration (e.g., the low-level configuration of the associated MRB and MBS session) should be temporarily retained. In the RRC inactive state, the UE initiates a procedure similar to MCCH to receive MBS data, for example, by listening to the MCCH to obtain the relevant multicast PTM configuration information. Thus, in response to receiving the SIB, the UE retains the PTM configuration corresponding to one of the at least one MBS to continue receiving that MBS in response to the UE transitioning from the RRC connected state to the RRC inactive state. After receiving the PTM configuration via broadcast signaling in the RRC inactive state, the UE releases the PTM configuration received in the RRC connected state.

[0155] Without receiving such an indication, the UE initiates a conventional RRC connection release procedure and transitions to an RRC inactive state. Before acquiring an updated PTM configuration, the UE continues to apply the current PTM configuration to receive one or more of at least one MBS, where the current PTM configuration can be received when the UE is in an RRC connected state.

[0156] In some embodiments, the SIB explicitly indicates that, for the selected MBS, in response to the UE being released to an RRC inactive state, the UE initiates an MCCH-like procedure to receive MBS data in the RRC inactive state, for example, by monitoring the MCCH to obtain relevant PTM configuration information. Thus, in response to receiving the SIB, the UE releases the PTM configuration corresponding to one of the at least one MBS in response to the UE transitioning from an RRC connected state to an RRC inactive state, and the UE receives broadcast signaling from the network to update the PTM configuration in response to the UE transitioning from an RRC connected state to an RRC inactive state. In the absence of such an indication, the UE initiates a conventional RRC connection release procedure and transitions to an RRC inactive state.

[0157] In some configurations, the RRC version carries the MCCH content or the entire MCCH content for the MBS of interest to the UE. This indicates that for such an MBS, the corresponding PTM configuration is delivered in an MCCH-like manner during RRC inactivity. This mechanism reduces latency caused by monitoring the MCCH. The indication information includes broadcast signaling information containing the PTM configuration of at least one MBS used when the UE is in RRC inactivity.

[0158] In one embodiment, to continue MBS reception, the UE temporarily retains the corresponding PTM configuration (e.g., the associated MRB and low-layer configuration of the multicast session) in response to being released into an RRC inactive state. The UE applies the PTM configuration to the MCCH content and performs MBS data reception according to that configuration. Then, after the conventional MCCH monitoring process, the UE acquires the MCCH through its own MCCH monitoring and MCCH change notifications. Before acquiring the updated PTM configuration, the UE continues to apply the current PTM configuration to receive one or more of at least one MBS, wherein the current PTM configuration can be received when the UE is in an RRC connected state.

[0159] In another embodiment, in response to the UE being released to the RRC inactive state, the UE applies the PTM configuration in the MCCH content and performs multicast data reception according to the configuration. Then, after the conventional MCCH monitoring process, the UE obtains the MCCH by monitoring the MCCH itself and receiving MCCH change notifications.

[0160] In some embodiments, in response to a transition from an RRC connected state to an RRC inactive state, the UE receives data from the network corresponding to at least one MBS based on the PTM configuration in the indication information. In response to receiving the indication information, the UE retains the PTM configuration corresponding to one of the at least one MBS to continue receiving that one MBS in response to the UE transitioning from the RRC connected state to the RRC inactive state. In response to receiving the indication information, the UE monitors updates to the PTM configuration in response to the wireless communication device transitioning from the RRC connected state to the RRC inactive state.

[0161] The topics described herein sometimes illustrate different components contained within or connected to different other components. It should be understood that the architectures described are illustrative, and many other architectures that achieve the same functionality can actually be implemented. Conceptually, any arrangement of components that achieve the same function is effectively “associated” to achieve the desired functionality. Therefore, any two components combined herein to achieve a specific function can be considered “associated” with each other, thus enabling the desired functionality, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operably connected” or “operably coupled” to each other to achieve the desired functionality, and any two components that can be suchly associated can also be considered “operably coupled” to each other to achieve the desired functionality. Specific instances of operably coupled components include (but are not limited to) physically matable and / or physically interactive components and / or wirelessly interactive and / or logically interactive and / or logically interactive components.

[0162] Regarding the use of plural and / or singular terms in this document, those skilled in the art can translate plural to singular and / or singular to plural as needed by the context and / or application. For clarity, various singular / plural arrangements are explicitly described herein.

[0163] Those skilled in the art will understand that, generally, the terms used herein and especially in the appended claims (e.g., the body of the appended claims) are intended to be “open-ended” terms (e.g., the term “comprising” should be interpreted as “including but not limited to”, the term “having” should be interpreted as “at least having”, the term “comprising” should be interpreted as “including but not limited to”, etc.).

[0164] Although the accompanying drawings and descriptions may illustrate a specific order of method steps, such order may differ from the order depicted and described unless otherwise specified above. Furthermore, two or more steps may be performed simultaneously or partially simultaneously unless otherwise specified above. Such variations may depend, for example, on the chosen software and hardware system and on the designer's choices. All such variations are within the scope of this disclosure. Similarly, the software implementation of the described method can be implemented using standard programming techniques with rule-based logic and other logic to perform the various connection steps, processing steps, comparison steps, and decision steps.

[0165] Those skilled in the art will further understand that if a particular number of claims is intended to be recited in the introduced claims, then such an intention is explicitly stated in the claims, and without such a statement, such an intention does not exist. For example, to aid understanding, the appended claims may contain the use of introductory phrases “at least” and “one or more” to introduce the recitation of a claim. However, the use of such phrases should not be construed as implying that the introduction of a claim recitation by the indefinite article “a” or “an” limits any particular claim containing such an introduced claim recitation to containing only one such recitation in this disclosure, even when the same claim includes the introductory phrase “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and / or “an” should typically be interpreted as meaning “at least one” or “one or more”); the same applies to the use of definite articles to introduce the recitation of a claim. Furthermore, even if a particular number of claims is explicitly stated, those skilled in the art will recognize that this statement should generally be interpreted as meaning at least the number recited (e.g., “two recitations” without other modifiers generally means at least two recitations, or two or more recitations).

[0166] Furthermore, when using conventions such as "at least one of A, B, and C, etc.", this construction is generally intended to ensure that a person skilled in the art will understand the meaning of the convention (e.g., "a system having at least one of A, B, and C" includes, but is not limited to, a system having A alone, having B alone, having C alone, A together with B, A together with C, B together with C, and / or A, B, and C together, etc.). When using conventions such as "at least one of A, B, or C, etc.", this construction is generally intended to ensure that a person skilled in the art will understand the meaning of the convention (e.g., "a system having at least one of A, B, or C" includes, but is not limited to, a system having A alone, having B alone, having C alone, A together with B, A together with C, B together with C, and / or A, B, and C together, etc.). Those skilled in the art should also understand that virtually any separate words and / or phrases presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibility of including one, any, or both of these terms. For example, the phrase “A or B” should be understood as including the possibility of “A” or “B” or “A and B”.

[0167] In addition, unless otherwise specified, the use of words such as “approximately,” “about,” “probably,” “basically,” etc. implies ±10%.

[0168] For purposes of illustration and description, the foregoing description of illustrative implementations has been presented. It is not intended to be exhaustive or to limit the precise form disclosed, and modifications and variations are possible, or may be obtained, from practice of the disclosed embodiments in light of the foregoing teachings. The scope of this disclosure is intended to be defined by the appended claims and their equivalents.

Claims

1. A wireless communication method, comprising: When the wireless communication device is in the Radio Resource Control (RRC) connection state, the wireless communication device uses signaling specific to the wireless communication device to receive from the network the MBS configuration for each of the multiple multicast broadcast services (MBS). The wireless communication device transitions from the RRC connected state to the RRC inactive state; The wireless communication device receives an indication identifying at least one of the plurality of MBS, wherein the indication includes an indication for each MBS radio bearer MRB associated with the plurality of MBS; In response to switching to the RRC inactive state, when the wireless communication device is in the RRC inactive state, the wireless communication device uses the MBS configuration received in the RRC connection state to receive data from at least one of the plurality of MBS from the network.

2. The wireless communication method according to claim 1, wherein, The at least one MBS is a subset of the plurality of MBS configured to be received when the wireless communication device is in the RRC connection state.

3. The wireless communication method according to claim 1, wherein, The wireless communication device continues to receive at least one MBS when it is in the RRC inactive state.

4. The wireless communication method according to claim 1, further comprising: In response to receiving the instruction, the at least one MBS is received or continues to be received in the RRC inactive state.

5. The wireless communication method according to claim 4, wherein, The wireless communication device receives the instruction via RRC release; The instructions include instructions for each of the plurality of MBS.

6. The wireless communication method according to claim 4, wherein, The wireless communication device receives the instruction via RRC release.

7. The wireless communication method according to claim 1, further comprising: When the wireless communication device is in the RRC inactive state, the wireless communication device determines a trigger event, wherein determining the trigger event includes the wireless communication device receiving a notification from the network, wherein the wireless communication device receives the notification via a paging message, the paging message including: The first part corresponds to the list of MBS session IDs associated with one of the at least one MBS; and The second part corresponds to the modification information associated with the MBS session ID list in the first part.

8. The wireless communication method according to claim 7, wherein, The wireless communication method further includes: In response to determining the triggering event, the wireless communication device determines that the modification information indicates the restoration of the at least one MBS, and determines at least one of the following: When the wireless communication device is in the RRC inactive state, the wireless communication device restores the MBS configuration corresponding to the at least one MBS; or When the wireless communication device is in the RRC inactive state, the wireless communication device uses the MBS configuration to monitor the at least one MBS.

9. The wireless communication method according to claim 7, wherein, The wireless communication method further includes: In response to determining the triggering event, the wireless communication device determines that the modification information indicates an MBS configuration update for the at least one MBS; and The wireless communication device initiates the RRC connection recovery process.

10. The wireless communication method according to claim 1, further comprising: When the wireless communication device is in the RRC inactive state, the wireless communication device determines a trigger event, wherein determining the trigger event includes determining that the reception quality of one of the at least one MBS is lower than a threshold, wherein the threshold includes at least one of a measured signal strength or a packet loss rate, and the threshold is configured by the network; In response to determining the triggering event, the wireless communication device modifies the MBS configuration, wherein modifying the MBS configuration includes: The wireless communication device initiates the RRC connection recovery process; The wireless communication device receives from the network an updated MBS configuration for the one MBS; and The wireless communication device receives the MBS from the network using the updated MBS configuration.

11. A wireless communication device, comprising at least one processor for: When the wireless communication device is in the Radio Resource Control (RRC) connection state, the receiver receives the MBS configuration for each of the multiple multicast broadcast services (MBS) from the network using signaling specific to the wireless communication device. The process transitions from the RRC connected state to the RRC inactive state. Receive an indication identifying at least one of the plurality of MBS, wherein the indication includes an indication for each MBS radio bearer MRB associated with the plurality of MBS; as well as In response to switching to the RRC inactive state, when the wireless communication device is in the RRC inactive state, the data of at least one of the plurality of MBS is received from the network by the receiver using the MBS configuration received in the RRC connected state.

12. A wireless communication method, comprising: When a wireless communication device is in a Radio Resource Control (RRC) connected state, the network uses signaling specific to the wireless communication device to send the MBS configuration for each of the multiple Multicast Broadcast Services (MBS) to the wireless communication device. The network releases the wireless communication device to an RRC inactive state; The network sends an indication to the wireless communication device that identifies at least one of the plurality of MBS, wherein the indication includes an indication for each MBS radio bearer MRB associated with the plurality of MBS; as well as When the wireless communication device is in the RRC inactive state, the network uses the MBS configuration sent when the wireless communication device is in the RRC connected state to send data to the wireless communication device corresponding to at least one of the plurality of MBS.

13. The wireless communication method according to claim 12, wherein, The at least one MBS is a subset of the plurality of MBS configured by the network to be sent to the wireless communication device when the wireless communication device is in the RRC connection state.

14. The wireless communication method according to claim 12, wherein, When the wireless communication device is in the RRC inactive state, the network continues to transmit the at least one MBS.

15. The wireless communication method according to claim 12, further comprising: When the wireless communication device is in the RRC inactive state, the network determines whether to send or continue sending the at least one MBS, and sends the indication identifying the at least one MBS to the wireless communication device.

16. The wireless communication method according to claim 15, wherein, The network releases the instruction via RRC; The instructions include instructions for each of the plurality of MBS.

17. The wireless communication method according to claim 15, wherein, The network sends the instruction via RRC release.

18. The wireless communication method according to claim 12, further comprising: The network sends a notification to the wireless communication device, wherein the network sends the notification via a paging message, the paging message including: The first part corresponds to the list of MBS session IDs associated with one of the at least one MBS; and The second part corresponds to the modification information associated with the MBS session ID list in the first part.

19. The wireless communication method according to claim 18, wherein, The modified information indicates the restoration of the at least one MBS, wherein... When the wireless communication device is in the RRC inactive state, the wireless communication device restores the MBS configuration corresponding to the at least one MBS; and / or When the wireless communication device is in the RRC inactive state, the wireless communication device uses the MBS configuration to monitor the at least one MBS.

20. The wireless communication method according to claim 18, wherein, The modification information indicates an MBS configuration update for at least one MBS, and the network receives an RRC connection recovery process initiated by the wireless communication device.

21. The wireless communication method according to claim 12, further comprising: The network configuration threshold, wherein when the wireless communication device is in the RRC inactive state, the wireless communication device determines a trigger event, wherein determining the trigger event includes determining that the reception quality of one of the at least one MBS is lower than the threshold, wherein the threshold includes at least one of the measured signal strength or packet loss rate; The network receives the RRC connection recovery process initiated by the wireless communication device; The network sends an updated MBS configuration for the one MBS to the wireless communication device; and The network uses the updated MBS configuration to send the MBS to the wireless communication device.

22. A network node, comprising at least one processor for: When the wireless communication device is in the Radio Resource Control (RRC) connection state, the transmitter sends the MBS configuration for each of the multiple multicast broadcast services (MBS) to the wireless communication device using signaling specific to the wireless communication device. Release the wireless communication device to the RRC inactive state; Send to the wireless communication device an indication identifying at least one of the plurality of MBS, wherein the indication includes an indication for each MBS radio bearer MRB associated with the plurality of MBS; as well as When the wireless communication device is in the RRC inactive state, the MBS configuration sent when the wireless communication device is in the RRC connected state is used to send data corresponding to at least one of the plurality of MBS to the wireless communication device via the transmitter.

Images