Multicast MBS reception in RRC inactive state

Abstract

Techniques discussed herein can facilitate multicast and broadcast services (MBS) in radio resource control (RRC) inactive states. One example aspect is a baseband processor of a user equipment (UE) comprising one or more processors configured to receive a pause configuration in a radio resource control (RRC) message. The one or more processors further configure the UE for the RRC inactive state based on the pause configuration, and receive a multicast and broadcast service (MBS) session configuration before or after configuring the RRC inactive state. The one or more processors further configure multicast (MBS) reception based on the MBS session configuration; and receiving multicast (MBS) data based on the MBS session configuration when the UE is configured for the RRC inactive state.

Description

Technical Field

[0001] The present disclosure relates to wireless technologies including New Radio (NR) radio Multicast and Broadcast Service (MBS). Background Art

[0002] Mobile communications in the next generation wireless communication system 5G or New Radio (NR) networks will provide ubiquitous connectivity and access to information and the ability to share data on a global scale. 5G networks and network slicing will be a unified service-based framework that aims to meet common and sometimes conflicting performance standards. 5G networks will provide services to extremely heterogeneous application domains ranging from enhanced mobile broadband (eMBB) to massive machine type communications (mMTC), ultra-reliable low latency communications (URLLC) and other communications. In general, NR will evolve based on the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) Advanced technology and additional enhanced radio access technologies (RATs) to achieve seamless and faster wireless connectivity solutions. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Figure 1 is an exemplary block diagram illustrating an example of a user equipment (UE) communicatively coupled to a network in accordance with various aspects described herein.

[0004] Figures 2 to 4 A diagram illustrating Multicast and Broadcast Service (MBS) signaling in a Radio Resource Control (RRC) inactive state with dedicated signaling between a Base Station (BS) and a UE.

[0005] Figure 5 to Figure 6 A diagram illustrating MBS signaling in RRC inactive state with broadcast signaling between the BS and the UE.

[0006] Figures 7 and 8 A diagram illustrating MBS signaling in RRC inactive state with multicast signaling of activation or deactivation of an MBS session is illustrated.

[0007] Figures 9 to 11 A diagram illustrating MBS signaling in an RRC inactive state according to a small data transmission (SDT) procedure is illustrated.

[0008] Fig.12 A diagram illustrating MBS signaling in the RRC inactive state, where the UE can receive MBS data before and after changing cells.

[0009] Fig.13 A diagram illustrating MBS signaling in RRC inactive state, where the UE fails to receive the MBS session configuration.

[0010] Fig.14 A flow chart illustrating an example method for MBS signaling in an RRC inactive state for a UE.

[0011] Fig.15 A flow chart illustrating an example method for MBS signaling in an RRC inactive state for a BS.

[0012] Fig.16 Examples of infrastructure equipment according to various aspects disclosed are illustrated.

[0013] Fig.17 Examples of UE or BS platforms according to various aspects disclosed are illustrated. DETAILED DESCRIPTION

[0014] With the development of new radio (NR) fifth generation (5G) and future communication standards, network flexibility and scalability can adapt to enhanced performance protocols such as multicast and broadcast services (MBS). MBS can deliver services such as vehicle-to-everything (V2X), emergency and public safety applications, live video delivery, Internet of Things (IoT) applications, etc. in an efficient manner, especially when user equipment (UE) receives the same content. Although MBS can be deployed for radio resource control (RRC) connected state, enhancements to MBS are required for MBS RRC inactive state operation. MBS in the RRC connected state may not be power efficient and may not meet the usage requirements of mission-critical services in cells with a large number of UEs. MBS operation in the RRC inactive state can provide the benefits of lower power operation and extend multicast support for UEs to achieve improved resource efficiency in radio access network (RAN) sharing scenarios.

[0015] Various aspects of the present disclosure relate to multicast MBS reception in an RRC inactive state. A mechanism is proposed herein by which a UE can directly receive MBS data when entering an RRC inactive state. For example, when a UE and a base station (BS) enable and support MBS and an MBS session associated with the UE is activated, the UE can directly receive MBS data when transitioning to an RRC inactive state.

[0016] This document proposes a mechanism by which MBS can be enabled or disabled in the RRC inactive state. For example, the UE may receive dedicated or broadcast RRC signaling that enables MBS reception in the RRC inactive state. The dedicated RRC signaling may include an MBS session configuration that the UE uses for MBS data reception after transitioning to the RRC inactive state. In addition, when the UE is in the RRC connected state or the inactive state, the UE may receive an MBS activation or deactivation notification to enable or disable MBS reception in the RRC inactive state.

[0017] This article proposes a mechanism for the BS to provide MBS session configuration in the RRC inactive state through dedicated signaling or broadcast signaling. For example, the UE may receive dedicated signaling of the MBS session configuration provided in the RRC connected state, provided in an RRC release or RRC suspension configuration message, or received in response to a small data transmission (SDT) request from the UE. When the UE is in the RRC inactive state, the UE may receive broadcast signaling of the MBS session configuration through a system information block (SIB) or an MBS control channel (MCCH) message.

[0018] Figure 1 An example architecture of a wireless communication system 100 of a network including UE 101a and UE 101b (collectively referred to as "UE 101"), a radio access network (RAN) 110, and a core network (CN) 120 is illustrated. The UE communicates with the CN 120 via the RAN 110. In various aspects, the RAN 110 may be a next generation (NG) RAN or 5G RAN, an evolved UMTS terrestrial RAN (E-UTRAN), or a traditional RAN such as a UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to the RAN 110 operating in an NR or 5G system 100, while the term "E-UTRAN" or the like may refer to the RAN 110 operating in an LTE or 4G system 100. The UE 101 utilizes connections (or channels) 102 and 104, respectively, each of which includes a physical communication interface / layer. Channels 102 and 104 may facilitate one or more of licensed or unlicensed communication bands between UE 101 and RAN 110 .

[0019] Alternatively or additionally, each UE in UE 101 may be configured with dual connectivity (DC) as multi-RAT or multi-radio dual connectivity (MR-DC), where a UE with multi-Rx / Tx capabilities may be configured to utilize resources provided by two different nodes (e.g., 111a, 111b, 112 or other network nodes) that can be connected via a non-ideal backhaul, for example, where one of the nodes provides NR access and the other node provides E-UTRA for LTE or NR access for 5G.

[0020] Alternatively or additionally, each of the UEs 101 may be configured in a CA mode, where multiple frequency bands are aggregated in a component carrier (CC) to increase data throughput between the UE 101 and the nodes 111a, 111b. For example, the UE 101a may communicate with the node 111a in the CA mode according to the CC. Furthermore, the UE 101a may simultaneously communicate with the node 111 in the DC mode, and additionally communicate with each of the nodes 111 in the CA mode.

[0021] In this example, connections 102 and 104 are illustrated as air interfaces to achieve communication coupling. In various aspects, UE 101 can directly exchange communication data via ProSe interface 105. ProSe interface 105 can alternatively be referred to as a side link (SL) interface 105 and can include one or more logical channels. In other aspects, ProSe interface 105 can be direct (peer) communication.

[0022] The RAN 110 may include one or more access nodes or RAN nodes 111a and 111b (collectively referred to as "RAN nodes 111") that enable connections 102 and 104. As used herein, the terms "access node," "access point," and the like may describe equipment that provides radio baseband functionality for data and / or voice connectivity between a network and one or more users. These access nodes may be referred to as base stations (BSs), next generation base stations (gNBs), RAN nodes, evolved next generation base stations (eNBs), Node Bs, RSUs, transmit receive points (TRxPs), or TRPs, among others.

[0023] In aspects where the system 100 is a 5G or NR system, the interface 112 may be an Xn interface 112. The Xn interface is defined between two or more RAN nodes 111 (e.g., two or more gNBs, etc.) connected to the 5GC 120, between a RAN node 111 (e.g., a gNB) and an eNB connected to the 5GC 120, and / or between two eNBs connected to the 5GC 120.

[0024] UE 101 may receive MBS session configuration, MBS activation indication, or MBS activation or deactivation notification from BS 111. In addition, UE 101 may receive multicast MBS reception (eg, MBS data) from BS 111 when UE 101 is in the RRC inactive state.

[0025] UE 101 and RAN node 111 may utilize a Uu interface to exchange control plane data via a protocol stack including a PHY layer (e.g., layer 1 (L1)), a MAC layer (e.g., layer 2 (L2)), an RLC layer, a PDCP layer, and an RRC layer (e.g., layer 3 (L3)). The Uu interface may be one or more of connections 102 and 104.

[0026] In various aspects, the CN 120 may be a 5GC (referred to as “5GC 120” or the like), and the RAN 110 may be connected to the CN 120 via a next generation (NG) interface 113. In various aspects, the NG interface 113 may be divided into two parts: an NG user plane (NG-U) interface 114, which carries traffic data between the RAN node 111 and a user plane function (UPF); and an S1 control plane (NG-C) interface 115, which is a signaling interface between the RAN node 111 and an access and mobility management function (AMF).

[0027] In various aspects, in the case where CN 120 is an evolved packet core (EPC) (referred to as "EPC 120" or the like), RAN 110 may be connected to CN 120 via an S1 interface 113. In various aspects, S1 interface 113 may be divided into two parts: an S1 user plane (S1-U) interface 114, which carries traffic data between RAN node 111 and S-GW; and an S1-MME interface 115, which is a signaling interface between RAN node 111 and MME.

[0028] UE 101 may receive signaling (eg, MBS data) from BS 111 through connection 102 or 104. In addition, UE 101 may perform an SDT procedure or an RRC recovery procedure on connection 102 or 104.

[0029] The RAN 110 is shown as being communicatively coupled to a core network—in this regard, to the CN 120. The CN 120 may include a plurality of network components 122 (or network devices) configured to provide various data and telecommunication services to customers / subscribers (e.g., users of the UE 101) connected to the CN 120 via the RAN 110.

[0030] Multicast MBS Reception in RRC Inactive State

[0031] Figures 2 to 4 Diagrams 200 to 400 illustrate multicast and broadcast service (MBS) signaling in a radio resource control (RRC) inactive state with dedicated signaling between BS 111 and UE 101. In diagrams 200 to 400, UE 101 may be Figure 1 BS 111 may be UE 101a or UE 101b. Figure 1BS111a or BS111b of UE 101. In order for UE 101 to receive multicast data (e.g., MBS data 214) in the RRC inactive state, one or more conditions may be met. For example, the one or more conditions may include that UE 101 supports MBS reception in the RRC inactive state. UE 101 may determine and configure RRC inactive state MBS reception based on the capabilities of UE 101. In similar or other examples, the one or more conditions may include that BS111 supports the sending of MBS data 214 when UE 101 is in the RRC inactive state. BS111 may support the sending of MBS data 214 and enable the feature. In similar or other examples, the one or more conditions may include that an MBS session associated with UE 101 is activated. UE 101 may consider MBS session activation based on a prerequisite, or UE 101 may receive an MBS session activation notification.

[0032] The example shown in diagram 200 assumes that the one or more conditions include at least: UE 101 supports MBS reception in an RRC inactive state, and BS111 supports MBS data 214 transmission when UE 101 is in an RRC inactive state. At 202, UE 101 may be in an RRC connected state with BS111. At 204, BS111 may generate an RRC release message 206 and send it to UE 101. RRC release message 206 includes a suspension configuration (SuspendCfg) and is transmitted in an RRC message. In some aspects, the RRC message may be a dedicated RRC message for UE 101. The RRC message including the RRC release message 206 with the suspension configuration also includes an MBS session configuration 208. The MBS session configuration 208 configured by BS111 conveys to UE 101 the configuration for multicast MBS reception and the associated session for multicast MBS reception. Thus, the MBS session configuration 208 may include one or more information elements, such as an MBS session ID identifying the MBS session and an associated Internet Protocol (IP) multicast address, a frequency for the MBS session, and other associated information elements.

[0033] After UE 101 receives the suspension configuration in the RRC message, UE 101 is configured for the RRC inactive state based on the suspension configuration at 210. In addition, UE 101 may determine that the MBS session configuration 208 received at 204 is an indication of MBS session activity (e.g., an MBS session activation notification). In this regard, UE 101 may configure multicast MBS reception based on the MBS session configuration at 210. Note that the order of configuring multicast MBS reception may be different, for example, the configuration of multicast MBS reception may occur before, during, or after the RRC inactive state configuration.

[0034] After UE 101 configures the RRC inactive state and configures multicast MBS reception based on MBS session configuration 208, UE 101 may receive MBS data 214 at 212. MBS data 214 is associated with an MBS session ID identified by MBS session configuration 208. In this regard, BS 111 generates MBS data 214 at 212 and sends it to UE 101. MBS data 214 may be sent by BS 111 in an MBS traffic channel (MTCH) and received by UE 101. MBS data 214 may, for example, be or include various service data, such as V2X, emergency or public safety data, live video, IoT data, etc. In addition, BS 111 may send MBS data 214 to one or more UEs including UE 101. Therefore, when UE 101 is configured for the RRC inactive state, MBS data 214 is received by UE 101.

[0035] In some aspects, BS 111 may determine to deactivate the MBS session, so BS 111 may generate and send an MBS session deactivation notification 218 at 216. The MBS session deactivation notification 218 may indicate to UE 101 that multicast MBS reception in the RRC inactive state is deactivated. The MBS session deactivation notification 218 is associated with the MBS session ID identified by the MBS session configuration 208. In response to the MBS session deactivation notification 218, UE 101 may deconfigure multicast MBS reception at 220. The MBS session deactivation notification 218 may be included in a system information block (SIB), a dedicated message such as an RRC message, a paging message, or an MBS control channel (MCCH) message. Alternatively, when changing cells (e.g., a cell reselection process), when MBS data 214 is not received within a corresponding time period, or according to a broadcast configuration, UE 101 may deconfigure multicast MBS reception at 220. For example, UE 101 may configure an MBS timer and a reception time threshold, and deconfigure multicast MBS reception at 220 when no MBS data 214 is received before the MBS timer exceeds the reception time threshold.

[0036] Figure 2The aspects described in provide a mechanism for RRC inactive state MBS reception according to dedicated MBS signaling from BS 111. The aspect describes dedicated MBS session configuration 208 signaling, wherein UE 101 is configured for multicast MBS reception in RRC inactive state without additional MBS session activation signaling from BS 111. Thus, BS 111 can configure RRC inactive state MBS services (e.g., MBS session configuration 208, MBS session deactivation notification 218) for a specific UE (e.g., UE 101) according to dedicated signaling, and UE 101 can save resources by autonomously determining that the MBS session is active without additional signaling. Additional examples of solutions that provide RRC inactive state MBS reception for various network configurations are described herein.

[0037] Diagram 300 illustrates an example of Figure 2 An alternative feature of diagram 200 of , wherein UE 101 receives MBS session activation notification 304 after configuring the RRC inactive state, and wherein UE 101 may deconfigure multicast MBS reception in response to broadcast configuration 310.

[0038] After UE 101 configures the RRC inactive state at 210, BS 111 may generate and send an MBS session activation notification 304 to UE 101 at 302. MBS session activation notification 304 may be dedicated signaling for UE 101 and indicates to UE 101 that BS 111 supports RRC inactive state communications. After UE 101 receives MBS session activation notification 304, UE 101 may configure multicast MBS reception according to MBS session configuration 208 at 306. In this regard, MBS session activation notification 304 corresponds to an MBS session ID identified by MBS session configuration 208.

[0039] After configuring multicast MBS reception at 306, UE 101 may receive MBS data 214 at 212. In some aspects, BS 111 may determine to deactivate the MBS session, and therefore, BS 111 may generate and send broadcast configuration 310 at 308. UE 101 may determine to deconfigure multicast MBS reception at 220. Broadcast configuration 310 may include Figure 2The broadcast configuration 310 may be an MBS session deactivation notification 218 or may be MBS signaling that overrides the dedicated MBS session configuration 208. In some aspects, the broadcast configuration 310 does not include an IE with an MBS session ID associated with the MBS session configuration 208. When the UE 101 detects that the broadcast configuration 310 does not include an MBS session ID associated with the MBS session configuration 208, the UE 101 may determine at 220 to deconfigure multicast MBS reception. The broadcast configuration may be included in a SIB or MCCH message and may be a dedicated message. Alternatively, the UE 101 may determine at 220 to deconfigure the multicast MBS reception based on the broadcast configuration 310 in the SIB or MCCH message. Figure 2 The feature discussed at 216 deconfigures multicast MBS reception.

[0040] Figure 3 The aspects described in the present disclosure provide a mechanism for RRC inactive state MBS reception according to dedicated MBS signaling from BS 111. Diagram 300 depicts dedicated MBS session configuration 208 signaling, wherein UE 101 is configured for multicast MBS reception in RRC inactive state according to MBS session activation notification 304 from BS 111. Thus, BS 111 has flexibility in configuring RRC inactive state MBS services, such as MBS session configuration 208 and MBS session activation / deactivation for a specific UE (e.g., UE 101).

[0041] Diagram 400 illustrates an example of Figure 2 200 , wherein the UE 101 may receive an MBS session activation notification 304 with an RRC message at 204 , and wherein the UE 101 may deconfigure multicast MBS reception in response to changing cells.

[0042] At 204, BS 111 may generate and send an RRC release message 206 to UE 101. RRC release message 206 includes a suspension configuration (SuspendCfg) and is transmitted in an RRC message. In some aspects, the RRC message may be a dedicated RRC message for UE 101. In some aspects, the RRC message including the RRC release message 206 with the suspension configuration also includes an MBS session configuration 208, and UE 101 may determine that receiving the MBS session configuration 208 is an indication (implicit notification) of MBS session activity, such as in Figure 2204 of . In an alternative aspect, the RRC message including the RRC release message 206 with the suspension configuration also includes an MBS session configuration 208 and an MBS session activation notification 304. In this aspect, the UE 101 determines the MBS session activation by generating and sending the MBS session activation notification 304 (explicit notification) by the BS 111. Therefore, when the UE 101 is in the RRC connected state, the UE 101 can implicitly or explicitly determine that the MBS session is active.

[0043] At 210, UE 101 may configure an RRC inactive state and configure multicast MBS reception. After configuring multicast MBS reception, UE 101 may receive MBS data 214 at 212. Figures 2 to 3 , UE 101 may determine to deconfigure multicast MBS reception at 406. Alternatively, UE 101 may determine to deconfigure multicast MBS reception at 406 in response to the cell change procedure at 402. For example, UE 101 may perform a cell reselection procedure and connect to a new BS 111b (e.g., Figure 1 111b). In some aspects, UE 101 may connect to new BS 111b based on an indication in a SIB message received from BS 111. After changing cells at 402, UE 101 may receive a broadcast message from new BS 111b at 404. The broadcast message from new BS 111b may indicate that RRC inactive MBS reception is deactivated, or may not indicate RRC inactive MBS resources, or may not indicate RRC inactive MBS resources for a session ID associated with MBS session configuration 208. In this aspect, UE 101 may determine to deconfigure multicast MBS reception at 406 in response to the broadcast message from the new BS at 404.

[0044] Figure 4The aspects described in provide a mechanism for performing RRC inactive state MBS reception based on dedicated MBS signaling from BS 111. Diagram 400 depicts dedicated MBS session configuration 208 signaling, wherein UE 101 is configured for multicast MBS reception in an RRC inactive state based on an MBS session activation determined from an RRC message at 204. In one aspect, BS 111 has flexibility in explicitly configuring MBS session activation based on an MBS session activation notification. In another aspect, UE 101 implicitly determines that the MBS session is activated based on receiving the MBS session configuration 208. In either aspect, while UE 101 is in a connected state, UE 101 determines that the MBS session is activated, and UE 101 can directly receive MBS data 214 without additional signaling when the RRC inactive state is configured. A mechanism is presented by which UE 101 can deconfigure multicast MBS at 406 based on a cell change. Although Figures 2 to 4 A specific mechanism for UE 101 to deconfigure multicast MBS reception is described, but it should be understood that the mechanism for deconfiguring multicast MBS reception is not limited to the following. Figures 2 to 4 are interchangeable.

[0045] Figure 5 to Figure 6 Figures 500 to 600 illustrate MBS signaling in an RRC inactive state with broadcast signaling between BS 111 and UE 101. In Figures 500 to 600, UE 101 may be Figure 1 BS 111 may be UE 101a or UE 101b. Figure 1 BS111a or BS111b of the RRC inactive state. In illustrations 500 to 600, it is assumed that the one or more conditions include at least: UE 101 supports MBS reception in the RRC inactive state, and BS111 supports MBS data 214 transmission when UE 101 is in the RRC inactive state. BS111 may generate and send MBS session configuration 208 through broadcast signaling (e.g., broadcast SIB, MCCH message transmission, RRC message transmission, etc.). In some aspects, when UE 101 is in the RRC connected state, UE 101 is notified that BS 111 enables MBS reception, and then receives MBS session activation notification 304 and MBS session configuration 208 when UE 101 is in the RRC inactive state. In other aspects, UE 101 determines the MBS capability of UE 101, and receives the MBS session activation notification 304 and MBS session configuration 208 based on the MBS capability of UE 101.

[0046] Diagram 500 shows an example in which MBS signaling for an RRC inactive state is enabled when UE 101 is in an RRC connected state. In diagram 500, UE 101 receives an RRC release message 206 from BS 111 at 502. RRC release message 206 includes a suspension configuration and is transmitted to UE 101 in an RRC message. The RRC message may also include an MBS reception enable message 504, which indicates that BS 111 enables MBS services for the RRC inactive state. Therefore, BS 111 may generate and send an RRC message including the MBS reception enable message 504. After receiving the RRC message with the RRC release message 206 and the MBS reception enable message 504 at 502, UE 101 may configure the RRC inactive state at 210. Aspects of action 210 correspond to Figure 3 Action 210.

[0047] After UE 101 is configured for the RRC inactive state, the UE may receive an MBS session configuration 208 from BS 111 upon entering the RRC inactive state or after receiving an MBS session activation notification 304 from BS 111 .

[0048] For example, at 506, UE 101 receives an MBS session activation notification 304 corresponding to an MBS session ID, and subsequently receives an MBS session configuration 208 corresponding to the MBS session ID. Alternatively, at 508, UE 101 receives an MBS session configuration 208 corresponding to the MBS session ID after entering the RRC inactive state, and subsequently receives an MBS session activation notification 304 corresponding to the MBS session ID. When UE 101 is in the RRC inactive state, both the MBS session activation notification 304 and the MBS session configuration 208 at 506 and 508 are generated by BS 111 and sent to UE 101, and may be configured in broadcast signaling (e.g., broadcast SIB or broadcast MCCH). In addition, when receiving the MBS reception enable message 504, UE 101 may reserve resources for MBS reception in the RRC inactive state. When the MBS reception enablement message 504 is not received, the UE 101 may save resources associated with receiving one or more of the MBS session activation notification 304 or the MBS session configuration 208 .

[0049] Alternatively or additionally, SIB or MCCH signaling associated with actions 506 and 508 may indicate deactivation of the multicast MBS session, and the UE 101 may deconfigure multicast MBS reception accordingly.

[0050] In an alternative example, at 510, UE 101 receives a SIB or MCCH message from BS 111. If the SIB or MCCH message at 510 includes the MBS session configuration 208, UE 101 may determine that the MBS session is activated. In this respect, the SIB or MCCH message at 510 is similar to the MBS session activation notification 304 at 506 or 508. If the SIB or MCCH message at 510 does not include the MBS session configuration 208, UE 101 may determine that the MBS session is deactivated.

[0051] After receiving the MBS session configuration 208 at 506, 508 or 510, the UE 101 may configure multicast MBS reception at 306 and receive MBS data 214 associated with the session ID of the MBS session configuration 208 at 212. Aspects of action 306 correspond to Figure 3 Action 306, and aspects of action 212 correspond to Figure 2 If UE 101 receives a SIB or MCCH message without MBS session configuration 208 at 510, UE 101 may determine that the MBS session associated with MBS session configuration 208 is deactivated and deconfigure multicast MBS reception. Figure 4 Actions 402, 404 and 406, Figure 3 Actions 308 and 220, or Figure 2 Deconfiguring multicast MBS reception is determined by actions 216 and 220 of FIG. 500 provides a mechanism by which BS 111 can enable UE 101 to receive MBS session configuration 208 when UE 101 is in RRC inactive state.

[0052] Diagram 600 shows an example in which UE 101 determines to receive MBS session configuration 208 based on the MBS capability of UE 101. While UE 101 is in an RRC connected state, UE 101 receives an RRC release message 206 from BS 111 at 602. RRC release message 206 includes a suspension configuration and is transmitted to UE 101 in the RRC message. After receiving the RRC message with RRC release message 206 at 602, UE 101 may configure an RRC inactive state at 210. Aspects of action 210 correspond to Figure 3 Action 210.

[0053] After UE 101 is in the RRC inactive state, UE 101 may determine the MBS capabilities of UE 101. In this aspect, UE 101 determines whether UE 101 meets criteria for RRC inactive state reception. For example, in some aspects, the MBS capabilities of UE 101 are determined based on whether UE 101 has the capability to receive multicast MBS in the inactive state. If UE 101 determines that UE 101 does not meet criteria for RRC inactive state reception, UE 101 will not receive MBS session configuration 208 (e.g., at actions 506, 508, or 510), and therefore will not configure multicast MBS reception or receive MBS data 214. If UE 101 meets criteria for RRC inactive state reception, UE 101 may determine to receive MBS session activation notification 304. For example, as Figure 5 As described in the above, the MBS session activation notification 304 may be received at actions 506, 508 or 510, and then when the UE 101 is in the RRC inactive state, the multicast MBS reception is configured at 306 and the MBS data 214 is received at 212. In addition, the UE 101 may receive the MBS session activation notification 304 at actions 506, 508 or 510. Figure 4 Actions 402, 404 and 406, Figure 3 Actions 308 and 220, or Figure 2 Deconfiguring multicast MBS reception is determined by actions 216 and 220 of UE 101. Diagram 600 minimizes signaling from BS 111 and provides a mechanism by which UE 101 can determine whether UE 101 can be enabled for RRC inactive state MBS reception.

[0054] Figures 7 and 8 Figures 700 to 800 illustrate MBS signaling in the RRC inactive state with multicast signaling of activation or deactivation of an MBS session. In Figures 700 to 800, UE 101 may be Figure 1 BS 111 may be UE 101a or UE 101b. Figure 1 In the diagrams 700 to 800, it is assumed that the one or more conditions include at least: UE 101 supports MBS reception in the RRC inactive state, and BS111 supports MBS data 214 transmission when UE 101 is in the RRC inactive state. After sending the MBS reception enable message 504 when UE 101 is in the RRC connected state, BS111 may generate and send the MBS session activation notification 304 through multicast signaling when UE 101 is in the RRC inactive state. The multicast signaling may include multicast SIB, multicast paging, multicast MCCH signaling, etc.

[0055] BS 111 may generate and send MBS session configuration 208 via broadcast signaling (e.g., broadcast SIB, MCCH messaging, RRC messaging, etc.). In some aspects, UE 101 is configured to enable MBS reception by BS 111 when UE 101 is in an RRC connected state, and then receive MBS session activation notification 304 and MBS session configuration 208 when UE 101 is in an RRC inactive state.

[0056] Diagram 700 shows an example in which UE 101 receives an MBS reception enable message 504 in an RRC connected state and receives an MBS session activation notification 304 through multicast signaling. UE 101 receives an RRC release message 206 according to the RRC message at 502. The RRC message may also include an MBS reception enable message 504, which indicates that BS 111 enables MBS services for the RRC inactive state. Aspects of 502 correspond to the following aspects: Figure 5 Features described at 502. After receiving the RRC message with the RRC release message 206 and the MBS reception enable message 504 at 502, the UE 101 can configure the RRC inactive state at 210. Aspects of action 210 correspond to Figure 3 ACT 210 or Figure 5 Action 210.

[0057] At 702, BS111 generates an MBS session activation notification 304 and sends it to UE 101. The MBS session activation notification 304 may be signaled via multicast signaling. For example, the MBS session activation notification 304 may be signaled via a multicast SIB message, a multicast paging message, a multicast RRC message, a multicast MCCH message, etc. In this aspect, BS111 may indicate to a group of UEs that may include UE 101 that the MBS session is activated. BS111 may generate and send an MBS session configuration 208 at 704, which has a session ID corresponding to the session ID of the MBS session activation notification 304. In some aspects, the MBS session configuration 208 may be generated by BS111 in a multicast message, similar to the MBS session activation notification 304 at 702. In other aspects, the MBS session activation notification 304 may be activated according to dedicated signaling (e.g., Figure 3 ), BS111 generates and sends the MBS session configuration 208 at 704, and UE 101 receives the MBS session configuration. In other aspects, the MBS session configuration 208 at 704 is received before the RRC inactive state is configured at 210 or is received in other dedicated or broadcast signaling.

[0058] After receiving the MBS session activation notification 304 at 702 and the MBS session configuration 208 at 704, the UE 101 may configure multicast MBS reception at 306. Subsequently, the UE 101 may receive MBS data 214 from the BS 111 at 212. Aspects of action 212 correspond to Figure 2 At 212 of . At 708, BS 111 may generate and send an MBS session deactivation notification 706 to UE 101. After receiving the MBS session deactivation notification 706, UE 101 may deconfigure multicast MBS reception at 220. In this regard, as described according to the MBS session activation notification 304 at 702, the MBS session deactivation notification 706 at 708 may be sent and received in multicast signaling.

[0059] In some aspects, BS 111 may indicate the MBS session state in a multicast MCCH transmission, e.g., an MBS session activation notification 304 or an MBS session deactivation notification 706. In this aspect, the MBS session state may be indicated by BS 111 at intervals or per multicast MCCH transmission. Thus, UE 101 may receive multiple multicast MCCH transmissions indicating the MBS session state. When the multicast MCCH message includes an MBS activation notification, UE 101 may configure multicast MBS reception (e.g., as described at 306). When the multicast MCCH message includes an MBS deactivation notification, UE 101 may deconfigure multicast MBS reception (e.g., as described at 220).

[0060] In some aspects, BS 111 may indicate the MBS session status, for example, in an MBS paging message. In this aspect, BS 111 may indicate the MBS session status at certain intervals or according to the MBS paging message. Thus, UE 101 may receive multiple MBS paging messages indicating the MBS session status. When the MBS paging message includes an MBS activation notification, UE 101 may configure multicast MBS reception (e.g., as described at 306). When the MBS paging message includes an MBS deactivation notification, UE 101 may deconfigure multicast MBS reception (e.g., as described at 220). In some examples, the MBS paging message is a multicast MBS paging message or a multicast specific paging message, wherein the MBS paging message is dedicated to indicating the MBS session status.

[0061] In some aspects, BS 111 may indicate the MBS session state in a layer 1 (L1) or layer 2 (L2) multicast MBS indication, such as MBS session activation notification 304 or MBS session deactivation notification 706. In this aspect, BS 111 may indicate the MBS session state in the L1 or L2 multicast MBS indication at intervals or on a repetitive basis. Thus, UE 101 may receive multiple L1 or L2 multicast MBS indications including the MBS session state. When the L1 or L2 multicast MBS indication includes the MBS activation notification, UE 101 may configure multicast MBS reception (e.g., as described at 306). When the L1 or L2 multicast MBS indication includes the MBS deactivation notification, UE 101 may deconfigure multicast MBS reception (e.g., as described at 220). In some examples, the L1 or L2 multicast MBS indication is sent by BS 111 through beam scanning to send the L1 or L2 multicast MBS indication to the group of UEs, which may include UE 101. In similar or alternative aspects, the L1 or L2 multicast MBS indication is an MBS medium access control (MAC) control element (CE) indication, and the MBS MAC CE indicates MBS session information for one or more MBS sessions. In similar or alternative aspects, the MBS MAC CE is sent according to L2 signaling.

[0062] In some aspects, when UE 101 is in the RRC inactive state, BS 111 may determine to activate the MBS session for MBS reception in the RRC connected state (not illustrated). For example, after UE 101 is configured for the RRC inactive state at 210, the UE may receive the MBS session activation notification 304 and the MBS session configuration 208 at 702 and 704. Signaling associated with either the MBS session activation notification 304 and the MBS session configuration 208 may further indicate MBS data 214 reception in the RRC connected state, and thus include an RRC resume indication. UE 101 may be configured for the RRC connected state based on the RRC resume indication, and configure multicast MBS reception based on the MBS session configuration 208. Then, when UE 101 is configured for the RRC connected state, UE 101 may receive multicast MBS data (e.g., MBS data 214) based on the MBS session configuration. In this aspect, the UE 101 receives MBS configuration data when configured in the RRC inactive state for MBS data reception occurring in the RRC connected state. Thus, the UE 101 can immediately receive MBS data reception in the RRC connected state without further signaling.

[0063] Diagram 800 shows an example in which UE 101 receives MBS session configuration 208 before entering the RRC inactive state and directly receives MBS data 214 in the RRC inactive state. In addition, in diagram 800, UE 101 may receive an MBS session deactivation notification according to multicast signaling.

[0064] In diagram 800, when UE 101 is in the RRC connected state, BS 111 generates RRC release message 206 at 804 and sends the RRC release message in an RRC message. In some aspects, UE 101 may receive RRC inactive state MBS configuration data, such as one or more of MBS reception enablement message 504, MBS session activation notification 304, or MBS session configuration 208. According to various aspects described herein, the RRC inactive state MBS configuration data may be received in multicast signaling, broadcast signaling, or dedicated signaling. In some aspects, the RRC inactive state MBS configuration data is received in an RRC message at 804, and in other aspects, the RRC inactive state MBS configuration data may be received in other messaging before configuring the RRC inactive state at 210. In some aspects, BS 111 generates MBS session configuration 208 and UE 101 receives the MBS session configuration, and UE 101 determines that the MBS session is activated based on receiving the MBS session configuration 208. In other aspects, UE 101 receives MBS session activation notification 304, which indicates to the UE that the MBS session is active (e.g., an MBS session according to a common MBS session ID between MBS session activation notification 304 and MBS session configuration 208). In still other aspects, UE 101 receives MBS reception enable message 504, which notifies UE 101 that BS 111 supports RRC inactive state reception, and then UE 101 receives at least MBS session configuration 208.

[0065] After UE 101 receives the suspension configuration in the RRC message, UE 101 is configured for the RRC inactive state based on the suspension configuration at 210. UE 101 may configure multicast MBS reception based on the MBS session configuration 208 received when UE 101 is in the RRC connected state. Note that the order of configuring multicast MBS reception may be different, for example, the configuration of multicast MBS reception may occur before, during, or after the RRC inactive state configuration. After UE 101 configures the RRC inactive state and configures multicast MBS reception based on the MBS session configuration 208, UE 101 may receive MBS data 214 at 212. Aspects of 212 correspond to Figure 2 Description of action 212.

[0066] UE 101 may receive MBS session deactivation notification 706 at 808. Figure 7 As described at action 708 of diagram 700, an MBS session deactivation notification 706 may be received according to multicast signaling. At 220, UE 101 may also deconfigure multicast MBS reception at 220 according to diagram 700. In some examples, for example, if another MBS session activation notification 304 is received, UE 101 may retain MBS session configuration 208 after deconfiguring multicast MBS reception to use MBS session configuration 208 for subsequent signaling. Diagram 800 provides a mechanism by which UE 101 may directly receive MBS data 214 after entering the RRC inactive state based on the RRC inactive state MBS configuration data received before entering the RRC inactive state without additional signaling.

[0067] Figures 9 to 11 Figures 900 to 1100 illustrate MBS signaling in an RRC inactive state according to a small data transmission (SDT) procedure. In the diagrams 900 to 1100, the UE 101 may be Figure 1 BS 111 may be UE 101a or UE 101b. Figure 1 BS111a or BS111b of the RRC inactive state. In illustrations 900 to 1100, it is assumed that the one or more conditions include at least: UE 101 supports MBS reception in the RRC inactive state, and BS111 supports MBS data 214 transmission when UE 101 is in the RRC inactive state. UE 101 may determine that UE 101 does not have MBS session configuration 208 after receiving the MBS session activation notification 304, and then perform an SDT process. By performing the SDT process, UE 101 may inquire BS111 for MBS session configuration 208. In some aspects, UE 101 receives MBS session configuration 208 in the RRC inactive state and receives MBS data 214. In other aspects, BS111 instructs UE 101 to perform an RRC recovery process and receive MBS data 214 in the RRC connected state. In still other aspects, the UE 101 determines that the SDT procedure fails and autonomously performs an RRC recovery procedure or an RRC establishment procedure and receives the MBS data 214 in an RRC connected state.

[0068] Diagram 900 shows an example in which UE 101 receives an MBS session activation notification 304 at 302 after configuring the RRC inactive state. Aspects of actions 202, 502, 210, and 302 may correspond to Figures 2 to 8After receiving the MBS session activation notification 304 at 302, the UE 101 may determine at 910 whether the UE 101 has an MBS session configuration 208 associated with the session ID of the MBS session activation notification 304. For example, the UE 101 may have sent (e.g., Figure 6 508) or in a previous RRC connection state (eg, Figures 2 to 4 or Figure 8 ) has received the MBS session configuration 208. If the UE 101 determines that the UE 101 does not have the MBS session configuration associated with the MBS session activation notification 304, the UE 101 may determine at 914 to perform the SDT process.

[0069] Thus, while the UE 101 is in the RRC inactive state, the UE 101 may generate and send an MBS session resource request 912. In some aspects, the MBS session request 912 may be one of a new RRC message, a new MAC CE sent with the first UL SDT message (e.g., RRCResumeRequest), or a specific RRC resume request message configured with the first UL SDT message. The MBS session resource request 912 may identify a session ID associated with the MBS session activation notification 304. In response, the BS 111 may generate and send an MBS session configuration 208 associated with the MBS session activation notification. The UE 101 may configure multicast MBS reception according to the MBS session configuration 208 at 306, and then receive MBS data 214 at 212. While the UE 101 is in the RRC connected state or the RRC inactive state, the UE 101 may deconfigure multicast MBS reception according to the features described herein. In this regard, UE 101 may receive MBS session activation notification 304 that may not correspond to MBS session configuration 208 previously received by UE 101. If UE 101 does not have MBS session configuration, UE 101 may query BS 111 for MBS session configuration, giving UE 101 the flexibility to request MBS session configuration 208.

[0070] Diagram 1000 shows an example in which UE 101 receives an RRC resume indication 1004 in response to MBS session resource request 912. This example shows an alternative aspect relative to diagram 900 after UE 101 generates and sends MBS session resource request 912 as part of an SDT procedure.

[0071] After determining that UE 101 does not have an MBS session configuration associated with the MBS session activation notification 304, UE 101 performs an SDT procedure at 1002. BS 111 may determine that UE 101 should receive MBS data 214 in the RRC connected state, and respond to the MBS session resource request 912 with an RRC resume indication 1004. In some aspects, BS 111 transmits the MBS session configuration 208 with the RRC resume indication 1004 to UE 101. In other aspects, BS 111 transmits the MBS session configuration 208 to UE 101 after sending the RRC resume indication 1004 and before sending the MBS data 214 at 212. UE 101 configures multicast MBS reception based on receiving the MBS session configuration 208. In response to the RRC recovery indication 1004, the UE 101 may perform an RRC recovery procedure at 1006, transition to an RRC connected state at 1008, and receive MBS data 214 at 212 when the UE 101 is configured for the RRC connected state. While the UE 101 is in the RRC connected state or the RRC inactive state, the UE 101 may deconfigure multicast MBS reception according to the features described herein.

[0072] Diagram 1000 provides a mechanism by which UE 101 can request MBS session resources when UE 101 lacks MBS session resources associated with MBS session activation notification 304, thereby providing UE 101 with flexibility in requesting configuration information when in RRC inactive state. In addition, BS 111 has the flexibility to determine whether UE 101 should receive MBS data 214 when UE 101 is in RRC connected state, and to indicate both MBS session configuration 208 and RRC resumption indication 1004 to UE 101 when UE 101 is in RRC inactive state for multicast reception after UE 101 transitions to RRC connected state.

[0073] Diagram 1100 shows an example in which the SDT procedure fails and the UE 101 performs an RRC recovery procedure or an RRC establishment procedure to configure an RRC connection state and receive an MBS session configuration 208. The example shows an alternative aspect relative to diagram 1000 after the UE 101 generates and sends an MBS session resource request 912 as part of the SDT procedure. After the UE 101 sends the MBS session resource request 912, the SDT procedure fails at 1104. The SDT procedure may fail under a variety of conditions, for example, the BS 111 may not receive the MBS session resource request 912, and the BS 111 may not respond with the MBS session configuration 208 within a specified time period. The BS 111 may receive the MBS session resource request 912, but the MBS session configuration 208 sent by the BS 111 in response may not be received by the UE 101 within a specified time period. If UE 101 receives MBS session configuration 208 from BS 111 in response to MBS session resource request 912 , where the session ID of MBS session configuration 208 does not correspond to the session ID of MBS session activation notification 304 at 302 , the SDT process may fail.

[0074] After detecting that the SDT process fails, the UE 101 may perform an RRC recovery process or an RRC establishment process at 1106. The UE 101 may receive an MBS session configuration 208 from the BS 111 in response to performing the RRC recovery process or the RRC establishment process, wherein the MBS session configuration 208 corresponds to the session ID of the MBS session activation notification 304. The UE 101 may configure an RRC connection state at 1008, configure multicast MBS reception according to the MBS session activation notification 304, and receive MBS data 214 at 212 while the UE 101 is in the RRC connection state. When the UE 101 is in the RRC connection state or the RRC inactive state, the UE 101 may deconfigure the multicast MBS reception according to the features described herein. Diagram 1100 provides a mechanism by which the UE 101 may recover the MBS session configuration 208 by performing an RRC recovery process or an RRC establishment process when the SDT process fails.

[0075] Fig.12 Diagram 1200 illustrates MBS signaling in an RRC inactive state, where UE 101 may receive MBS data 214 before and after changing cells. In diagram 1200, UE 101 may be Figure 1 101a or 101b of UE 101a. Diagram 1200 shows two BSs, for example, a first BS 111a and a second BS 111b, and the two BSs may be Figure 11200 , it is assumed that the one or more conditions include at least: UE 101 supports MBS reception in the RRC inactive state, and BS 111 supports MBS data 214 transmission when UE 101 is in the RRC inactive state.

[0076] Aspects of actions 202, 204, 210, and 212 may correspond to Figure 2 The actions described in or alternatively correspond to Figures 3 to 11 . For example, UE 101 receives RRC release message 206 at 204 and configures RRC inactive state at 210. Before UE 101 receives MBS data 214 from BS 111 at 212, UE 101 receives at least MBS session configuration 208. MBS session configuration 208 may be received at 204, or alternatively, may be received at any time before receiving MBS data 214. Thus, MBS session configuration 208 may be received in RRC inactive state or RRC connected state, and may be received through dedicated signaling, broadcast signaling, or multicast signaling, and may be received through an SDT procedure. In addition, UE 101 may receive MBS session activation notification 304 (not shown) or MBS reception enable message 504 (not shown).

[0077] In addition to receiving at least the MBS session configuration 208, the UE 101 also receives a configuration area or cell list. The configuration area or cell list specifies an area or a cell list of one or more cells, where inactive MBS reception is enabled in the RRC inactive state for the session ID associated with the MBS session configuration. Therefore, the BS111 determines the configuration area or cell list that is enabled for MBS reception for the session associated with the MBS session configuration 208. In this regard, the cell list may be a single cell or a radio access network (RAN). For the configuration area or cell list, the UE 101 may perform inactive MBS reception using the MBS session configuration 208 after changing the cell to a new BS111b used with the serving BS111a. Therefore, after changing from the serving BS111a to the new BS111b, the UE 101 may directly receive MBS data 214 in the RRC inactive state according to the MBS session configuration 208 received from the serving BS111a.

[0078] Thus, at 212, UE 101 receives MBS data 214 from serving BS 111a according to MBS session configuration 208. At 1202, UE 101 may perform a cell handover procedure or a cell reselection procedure, wherein UE 101 is connected to new BS 111b. At 1204, UE 101 may receive MBS data 214 based on MBS session configuration 208 when UE 101 is configured for RRC inactive state and after connecting to new BS 111b. UE 101 receives MBS data 214 according to an area configuration or a cell list, wherein new BS 111b is in a configured area or a cell list of enabled MBS reception. UE 101 may deconfigure multicast MBS reception according to various aspects previously described herein. Diagram 1200 provides a mechanism by which UE 101 can directly receive MBS data 214 in an RRC inactive state after connecting to a new BS without additional signaling and according to the MBS session configuration 208 received from the previous serving BS.

[0079] Fig.13 Diagram 1300 illustrates MBS signaling in an RRC inactive state, where UE 101 fails to receive MBS session configuration 208. In diagram 1300, UE 101 may be Figure 1 BS 111 may be UE 101a or UE 101b. Figure 1 BS111a or BS111b. In diagram 1300, it is assumed that the one or more conditions include at least: UE 101 supports MBS reception in the RRC inactive state, and BS111 supports MBS data 214 transmission when UE 101 is in the RRC inactive state. Diagram 1300 shows that after UE 101 is configured for the RRC inactive state at 210 and before receiving MBS data 214, UE 101 fails to receive MBS session configuration 208 at 1302. Therefore, after receiving the MBS session activation notification 304 at 302, UE 101 fails to receive the MBS session configuration 208. Alternatively, the MBS session activation notification 304 may be received when UE 101 is in the RRC active state, or UE 101 may implicitly determine that the MBS session is active, for example, as Figure 4 Described in .

[0080] When UE 101 fails to receive MBS session configuration 208, UE 101 determines or detects that the MBS session has failed. According to aspects previously described herein, UE 101 may fail to receive MBS session configuration 208. For example, when UE 101 receives RRC release message 206, UE 101 may fail to Figures 2 to 4 Action 204 or Figure 8 At action 804, the MBS session configuration 208 is received. Figure 5 to Figure 6 Action 506, 508 or Figure 7 Action 704 or Fig. 9 Action 914, or in combination Fig.10 According to action 1002, UE 101 may fail to receive MBS session configuration 208 in the RRC inactive state. Therefore, when UE fails to receive MBS session configuration 208 after configuring the RRC inactive state, MBS session failure may be detected. Additionally, when UE 101 connects to a BS that does not provide MBS session configuration after configuring the RRC inactive state, MBS session failure may be detected. Furthermore, when UE 101 receives MBS session configuration 208 associated with a session ID different from the session ID of the MBS session activation notification 304, MBS session failure may be detected.

[0081] After detecting or determining that the MBS session has failed or failing to receive the MBS session configuration 208, the UE 101 may perform an RRC recovery procedure or an RRC establishment procedure. At 1106, as part of or in response to performing the RRC recovery procedure or the RRC establishment procedure, the UE 101 may receive the MBS session configuration. After performing the RRC recovery procedure or the RRC establishment procedure, the UE 101 may configure the RRC connection state at 1008 and subsequently receive the MBS data 214 when configured for the RRC connection state.

[0082] Diagram 1300 provides a mechanism by which UE 101 may fall back to the RRC Connected state for MBS data 214 reception when MBS failure is detected when UE 101 initiates MBS reception in the RRC Inactive state.

[0083] Fig.14 A flow chart illustrating an example method 1400 for MBS signaling in an RRC inactive state for a UE. The example method 1400 may be performed, for example, by Figure 1 UE 101 executes.

[0084] At 1402, the method includes receiving an RRC release message while the UE is in an RRC connected state. Figures 2 to 4 and Fig.12 At 202 and 204, Figure 5 At 202 and 502, Figure 6 At 202 and 602, Figure 7 At 202 and 502, Figure 8 At 202 and 804 and Figures 9 to 11 At 202 and 502 some aspects of action 1402 are corresponded.

[0085] At 1404 , the UE may configure an RRC inactive state in response to receiving the RRC release message at 1402 . Figures 2 to 12 At 210 , some aspects of action 1404 are corresponded.

[0086] At 1412, the method includes receiving MBS configuration data, the MBS configuration data including one or more of the following: an MBS session configuration including a session ID for RRC inactive state MBS reception, an associated MBS reception enabling message, or an MBS session activation notification. The MBS reception enabling message may indicate to the UE that the BS to which the UE is connected supports RRC inactive state MBS reception. The MBS session activation notification may indicate to the UE that the MBS session for RRC inactive state MBS reception is activated. The MBS configuration data may be received by the UE 101 before configuring the RRC inactive state or after configuring the RRC inactive state. In some aspects, the UE determines that the BS is enabled for RRC inactive state MBS messaging and / or that the MBS session is implicitly active (implicit notification). Figure 2 and Figure 3 At 204, Figure 4 At 204 and 402, Figure 5 At 502, 506, 508 and 510, Figure 6 At 506, 508 and 510, Figure 7 At 502, 702 and 704, Figure 8 At 804, Figures 9 to 11 At 502 and 302, Fig.12 At 204 and Fig.13 At 302 and 1106 there are some aspects corresponding to action 1412 .

[0087] At 1414, the method includes optionally performing an SDT procedure. If the UE determines that the UE does not have a valid MBS session configuration, the SDT procedure may be performed to request an MBS session configuration. Thus, the UE may send an MBS session resource request and may receive an MBS session configuration in response. Alternatively, the UE may receive an indication to perform an RRC recovery procedure, or the UE may determine that the SDT procedure has failed and autonomously perform an RRC recovery procedure or an RRC establishment procedure. Fig. 9 At 914, Fig.10 At 1102 to 1008 and Fig.11 At 1102 , 1106 , and 1008 , some aspects of action 1414 are corresponded.

[0088] At 1416, the method includes optionally performing an MBS capability procedure. The UE may determine the MBS capability of the UE, then determine whether the UE supports RRC inactive state MBS reception, and then receive one or more of the MBS configuration data described at 1412. Therefore, action 1416 may be performed before the action described at 1412. Figure 6 At 604 , some aspects of action 1416 are corresponded.

[0089] At 1418, the method includes optionally changing the cell by performing a cell handover procedure or a cell reselection procedure. Thus, while the UE 101 is in the RRC inactive state, the UE may use the MBS session configuration received from the serving BS after connecting to the new BS. Fig.12 At 1202 , some aspects of action 1418 are corresponded.

[0090] At 1406, the method includes configuring multicast MBS reception. When the UE is configured for the RRC inactive state, the UE may configure multicast MBS reception. In other examples, after the UE transitions to the RRC connected state, the UE may configure multicast MBS reception according to an MBS session configuration received when the UE is in the RRC inactive state, the RRC connected state, or during an RRC recovery process. Multicast MBS reception is configured based on the MBS session configuration. Figure 2 , Figure 3 and Figure 8 At 210, Figures 4 to 7 and Fig. 9 At 406, Fig.10 At 1002, 1006 and 1008, Fig.11 At 1102, 1106 and 1008, Fig.12 At 204 and 210 and Fig.13 At 1106 and 1008 there are some aspects corresponding to action 1406 .

[0091] At 1408, the method includes receiving MBS data. The MBS data corresponds to an MBS session configuration and may be received when the UE is in an RRC inactive state or an RRC connected state. Figures 2 to 13 At 212 and Fig.12 At 1204 , some aspects of action 1408 are corresponded.

[0092] At 1410, the method includes optionally deconfiguring multicast MBS reception. Multicast MBS reception may be deconfigured according to signaling such as an MBS session deactivation notification, upon performing a cell change procedure, receiving a broadcast configuration indicating deconfiguration, or the like. Figure 2 , Figure 4 , Figure 7and Figure 8 At 220 and Figure 3 At 302 , 304 , and 406 , some aspects of action 1410 are corresponded.

[0093] Fig.15 A flow chart illustrating an example method 1500 for MBS signaling for a BS when a UE is in an RRC inactive state. The example method 1500 may be performed, for example, by Figure 1 The BS 111a or BS 111b may be used to perform the above operation.

[0094] At 1502, the method includes generating a suspension configuration indicating to a UE that an RRC inactive state is configured. Figures 2 to 4 and Fig.12 At 204, Figure 5 , Figure 7 and Figures 9 to 11 At 502, Figure 6 At 602 and Figure 8 At 804 , some aspects of action 1502 are corresponded.

[0095] At 1504, the method includes generating MBS configuration data, the MBS configuration data including one or more of the following: an MBS session configuration including a session ID for RRC inactive state MBS reception, an associated MBS reception enablement message, or an MBS session activation notification. The MBS reception enablement message may indicate to the UE that the BS supports RRC inactive state MBS reception for the UE. The MBS session activation notification may indicate to the UE that the MBS session for RRC inactive state MBS reception is activated. In some aspects, at 1502, one or more of the MBS configuration data in the MBS configuration data is included in a message transmission for suspending configuration. Figure 2 and Figure 3 At 204, Figure 4 At 204 and 402, Figure 5 At 502, 506, 508 and 510, Figure 6 At 506, 508 and 510, Figure 7 At 502, 702 and 704, Figure 8 At 804, Figures 9 to 11 At 502 and 302, Fig.12 At 204 and Fig.13 At 302 and 1106 there are some aspects corresponding to action 1504 .

[0096] At 1506, the method includes optionally receiving a session resource request as part of the SDT procedure. In response, the method may include generating an MBS session configuration or RRC resume request. The session resource request indicates that the requesting UE does not have an MBS session configuration corresponding to a session ID, such as an MBS session activation notification. Fig. 9 At 914, Fig.10 At 1102 to 1008 and Fig.11 At 1102 , 1106 , and 1008 , some aspects of action 1506 are corresponded.

[0097] At 1508, the method includes optionally generating an RRC resume indication.If the BS determines that the UE should receive MBS data in an RRC connected state, the BS may determine to generate an RRC resume indication. Fig.10 At 1002 and Fig.13 At 1106 , some aspects of action 1508 are corresponded.

[0098] At 1510, the method includes generating MBS data. The MBS data may be sent to the UE when the UE is in an RRC inactive state or an RRC connected state. Figures 2 to 13 At 212 and Fig.12 At 1204 , some aspects of action 1510 are corresponded.

[0099] At 1512, the method includes optionally generating an MBS session deactivation notification indicating to the UE that RRC inactive state MBS reception is terminated. Figure 2 , Figure 4 , Figure 7 and Figure 8 At 220 and Figure 3 At 302 , 304 , and 406 , some aspects of action 1512 are corresponded.

[0100] Fig.16 An example of infrastructure equipment 1600 according to various aspects is illustrated. The infrastructure equipment 1600 (or "system 1600") can be implemented as a base station, a radio head, a RAN node (such as Figure 1 BS111 of the present invention) and / or any other element / component / device discussed herein. In other examples, the system 1600 can be implemented in a UE (such as Figure 1 In other aspects, some features of the system 1600 may be implemented in or by the UE 101. Fig.12 The method is implemented in or by the first BS 111a or the second BS 111b.

[0101] System 1600 includes: application circuit 1605, baseband circuit 1610, one or more radio front end modules (RFEM) 1615, memory circuit 1620 (including memory interface), power management integrated circuit (PMIC) 1625, power tee circuit 1630, network controller circuit 1635, network interface connector 1640, satellite positioning circuit 1645 and user interface 1650. In some aspects, the device of system 1600 may include additional elements / components / devices, such as, for example, memory / storage, display, camera, sensor or input / output (I / O) interface. In other aspects, the components / devices described below may be included in more than one device. For example, the circuit may be separately included in more than one device for CRAN, vBBU or other similar implementations.

[0102] The baseband circuit 1610 may be used to configure an MBS reception enablement message, an MBS session activation notification, or an MBS session configuration by the BS 111 described herein. The baseband circuit 1610 may be used to receive an MBS reception enablement message, an MBS session activation notification, or an MBS session configuration by the UE 101 .

[0103] The application circuit 1605 includes circuits such as, but not limited to, one or more processors (or processor cores), processing circuits, cache memory, and one or more of the following: a low dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, I2C or a general programmable serial interface module, a real-time clock (RTC), a timer-counter (including an interval timer and a watchdog timer), a general input / output (I / O or IO), a memory card controller such as a secure digital (SD) multimedia card (MMC) or similar product, a universal serial bus (USB) interface, a mobile industry processor interface (MIPI) interface, and a joint test access group (JTAG) test access port. The processor (or core) of the application circuit 1605 may be coupled to or may include a memory / storage element / component / device, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the system 1600. In some implementations, the memory / storage element / component / device may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0104] The processor of the application circuit 1605 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some aspects, the application circuit 1605 may include or may be a dedicated processor / controller for operating in accordance with various aspects of the present disclosure. As an example, the processor of the application circuit 1605 may include one or more processor, Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or processors; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors provided by Cavium(TM), Inc. and MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some aspects, system 1600 may not utilize application circuit 1605, and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0105] User interface 1650 may include one or more user interfaces designed to enable a user to interact with system 1600 or a peripheral component or device interface designed to enable a peripheral component or device to interact with system 1600. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touch pad, a touch screen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. Peripheral component or device interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0106] Fig.16The components or devices shown can communicate with each other using an interface circuit coupled to each other, which can include any number of buses and / or interconnect (IX) technologies, such as industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus / IX can be a proprietary bus, for example, used in a SoC-based system. Other bus / IX systems can be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus, etc.

[0107] Fig.17 An example of a platform 1700 (or "device 1700") according to various aspects is illustrated. In various aspects, the platform 1700 may be suitable for use as Figure 1 UE 101 and / or any other element / component / device discussed herein, such as BS111, first BS111a or second BS111b. Platform 1700 may include any combination of components or devices shown in the examples. Components or devices of platform 1700 may be implemented as integrated circuits (ICs), parts of ICs, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted in platform 1700, or as components or devices otherwise combined within a chassis of a larger system. Fig.17 The block diagram is intended to show a high-level view of the components or devices of the platform 1700. However, some of the components or devices shown may be omitted, additional components or devices may be present, and different arrangements of the components or devices shown may occur in other implementations.

[0108] The application circuit 1705 includes circuits such as, but not limited to, one or more processors (or processor cores), memory circuit 1720 (which includes a memory interface), cache memory, and one or more of the following items: LDO, interrupt controller, serial interface such as SPI, I2C or general programmable serial interface module, RTC, timer-counter (including interval timer and watchdog timer), general I / O, memory card controller such as SD MMC or similar products, USB interface, MIPI interface and JTAG test access port. The processor (or core) of the application circuit 1705 may be coupled to or may include a memory / storage element / component / device, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the system 1700. In some implementations, the memory / storage element / component / device may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0109] For example, the processor of application circuit 1705 may include a general purpose or special purpose processor, such as a processor available from Inc., Cupertino, CA's A-series processor (e.g., A13 Bionic) or any other such processor. The processor of the application circuit 1705 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s core processors, Snapdragon by Technologies, Inc. TM Processor, Texas Instruments, Open Multimedia ApplicationsPlatform(OMAP) TMprocessors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some implementations, the application circuit 1705 can be part of a system on a chip (SoC), in which the application circuit 1705 and other components or devices are formed as a single integrated circuit or a single package.

[0110] The baseband circuit or processor 1710 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. In addition, the baseband circuit or processor 1710 may cause the transmission of various resources.

[0111] The platform 1700 may also include an interface circuit (not shown) for connecting an external device to the platform 1700. The interface circuit may communicatively couple one interface to another interface. The external devices connected to the platform 1700 via the interface circuit include a sensor circuit 1721 and an electromechanical component (EMC) 1722, and a removable memory device coupled to the removable memory circuit 1723.

[0112] The battery 1730 can power the platform 1700, but in some examples, the platform 1700 can be mounted in a fixed location and can have a power source coupled to a power grid. The battery 1730 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in V2X applications, the battery 1730 can be a typical lead-acid car battery.

[0113] Although the method is illustrated above and described as a series of actions or events, it should be understood that the order of such actions or events illustrated should not be interpreted as having a limiting meaning. For example, some actions can occur simultaneously with other actions or events other than those illustrated and / or described herein in different orders. In addition, all illustrated actions may not be required to implement one or more aspects or embodiments disclosed herein. In addition, one or more actions in the actions shown herein may be performed in one or more separate actions and / or stages. In some examples, the method illustrated above can be implemented in a computer-readable medium or a non-transient computer-readable medium using instructions stored in a memory. Many other embodiments and variations are possible within the scope of the present disclosure protected by the claims.

[0114] As used in this specification, the term "processor" may refer to substantially any computing processing unit or device, including but not limited to single-core processors; single processors with software multithreaded execution capabilities; multi-core processors; multi-core processors with software multithreaded execution capabilities; multi-core processors with hardware multithreading technology; parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor may refer to an integrated circuit, an application-specific integrated circuit, a digital signal processor, a field programmable gate array, a programmable logic controller, a complex programmable logic device, a discrete gate or transistor logic, a discrete hardware component or device, or any combination thereof designed to perform the functions and / or processes described herein. The processor may utilize nanoscale architectures, such as but not limited to molecular and quantum dot-based transistors, switches, and gates, in order to optimize space usage or enhance the performance of a mobile device. The processor may also be implemented as a combination of computing processing units. The processor or baseband processor may be configured to execute the instructions described herein.

[0115] UE or BS, e.g. Figure 1 The UE 101 or BS 111 may include a memory interface and a processing circuit communicatively coupled to the memory interface, the processing circuit being configured to execute the instructions described herein.

[0116] Embodiments (aspects) may include subject matter, such as a method, components for performing actions or blocks of the method, and at least one machine-readable medium comprising instructions that, when executed by a machine (e.g., a processor with memory, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc.), cause the machine to perform actions of a method or apparatus or system for concurrent communication using multiple communication technologies according to the aspects and embodiments described herein.

[0117] Embodiment 1 is a baseband processor of a user equipment (UE), the baseband processor comprising: one or more processors, the one or more processors being configured to: receive a pause configuration in a radio resource control (RRC) message; configure the UE for an RRC inactive state based on the pause configuration; receive a multicast and broadcast service (MBS) session configuration before or after configuring the RRC inactive state; configure multicast MBS reception based on the MBS session configuration; and receive multicast MBS data based on the MBS session configuration when the UE is configured for the RRC inactive state.

[0118] Embodiment 2 is the baseband processor according to embodiment 1, wherein the baseband processor is further configured to receive an MBS session activation notification before receiving the multicast MBS data.

[0119] Embodiment 3 is the baseband processor according to embodiment 2, wherein the MBS session activation notification is received before or after configuring multicast MBS reception.

[0120] Embodiment 4 is a baseband processor according to any one of embodiments 1 to 3, wherein the MBS session configuration and the MBS session activation notification are included in the RRC message including the suspension configuration.

[0121] Embodiment 5 is a baseband processor according to embodiment 1, wherein the MBS session configuration is included in the RRC message including the suspension configuration.

[0122] Embodiment 6 is the baseband processor of any one of embodiments 1 to 5, wherein the MBS session configuration is received in a dedicated RRC message.

[0123] Embodiment 7 is the baseband processor according to embodiment 1, the baseband processor being further configured to receive an MBS session deactivation notification, and deconfigure multicast MBS reception based on the MBS session deactivation notification.

[0124] Embodiment 8 is the baseband processor of embodiment 7, wherein the MBS session deactivation notification is received in a dedicated RRC message.

[0125] Embodiment 9 is the baseband processor of embodiment 1, the baseband processor being further configured to receive a broadcast configuration and deconfigure multicast MBS reception based on the broadcast configuration.

[0126] Embodiment 10 is a baseband processor according to embodiment 1, wherein the one or more processors further configure an MBS timer and a reception time threshold; and when multicast MBS data is not received before the MBS timer exceeds the reception time threshold, multicast MBS reception is deconfigured.

[0127] Embodiment 11 is the baseband processor according to embodiment 1, the baseband processor being further configured to perform a cell reselection procedure and to deconfigure multicast MBS reception in response to performing the cell reselection procedure.

[0128] Embodiment 12 is a baseband processor according to embodiment 1, wherein the RRC message including the suspension configuration further includes an indication of enabling inactive MBS reception by a base station (BS).

[0129] Embodiment 13 is the baseband processor according to embodiment 1, wherein the baseband processor is further configured to determine the MBS capability of the UE and receive the MBS session configuration based on the MBS capability.

[0130] Embodiment 14 is a baseband processor according to any one of embodiments 11 to 12, wherein after the UE is configured for the RRC inactive state, the MBS session configuration is received through broadcast signaling; after receiving the MBS session configuration, an MBS session activation notification is received; and after receiving the MBS session activation notification, multicast MBS reception is configured.

[0131] Embodiment 15 is a baseband processor according to any one of embodiments 11 to 12, wherein the baseband processor is further configured to receive an MBS session activation notification after configuring the RRC inactive state, and to receive the MBS session configuration through broadcast signaling after receiving the MBS session activation notification.

[0132] Embodiment 16 is a baseband processor according to any one of embodiments 11 to 12, wherein the baseband processor is further configured to receive a system information block (SIB) or an MBS control channel (MCCH) message via broadcast signaling; and when the SIB or the MCCH message includes the MBS session configuration, activate the MBS session of the MBS session configuration, and the one or more processors further configure multicast MBS reception in response to receiving the SIB or the MCCH message; or when the SIB or the MCCH message does not include the MBS session configuration, deactivate the MBS session of the MBS session configuration, and the one or more processors further deconfigure multicast MBS reception in response to receiving the SIB or the MCCH message.

[0133] Embodiment 17 is a baseband processor according to any one of embodiments 11 to 12, wherein the baseband processor is further configured to receive the MBS session configuration in a system information block (SIB) or an MBS control channel (MCCH) message through broadcast signaling.

[0134] Embodiment 18 is a baseband processor according to any one of embodiments 11 to 12, wherein the baseband processor is further configured to receive a system information block (SIB) or an MBS control channel (MCCH) message via broadcast signaling, wherein the SIB or the MCCH message includes an MBS session activation notification or an MBS session deactivation notification; and configure multicast MBS reception in response to receiving the MBS session activation notification; or deconfigure multicast MBS reception based on the MBS session deactivation notification.

[0135] Embodiment 19 is a device of a user equipment (UE), comprising: one or more processors, wherein the one or more processors are configured to: receive a suspension configuration in a radio resource control (RRC) message, wherein the RRC message includes an indication of enabling inactive multicast and broadcast service (MBS) reception by a base station (BS); configure the UE for an RRC inactive state based on the suspension configuration; receive an MBS activation notification and an MBS session configuration; configure multicast MBS reception based on the MBS session configuration; and, when the UE is configured for the RRC inactive state, receive multicast MBS data based on the MBS session configuration and after receiving the MBS activation notification.

[0136] Embodiment 20 is the apparatus of embodiment 19, wherein the MBS session configuration is received in dedicated signaling or broadcast signaling.

[0137] Embodiment 21 is the apparatus of embodiment 20, wherein the MBS session configuration is received before configuring the RRC inactive state.

[0138] Embodiment 22 is the apparatus of embodiment 20, the apparatus being further configured to determine MBS capabilities of the UE, and wherein multicast MBS reception is configured based on the MBS capabilities of the UE.

[0139] Embodiment 23 is the apparatus of embodiment 19, wherein the MBS activation notification and the MBS session configuration are received in the RRC message including the suspension configuration.

[0140] Embodiment 24 is an apparatus according to embodiment 23, wherein the MBS activation notification is received in multicast signaling, and the one or more processors are further configured to: receive an MBS session deactivation notification; and deconfigure multicast MBS reception based on the MBS session deactivation notification.

[0141] Embodiment 25 is a device according to embodiment 19, wherein the device is further configured to receive an MBS control channel (MCCH) message, wherein the MCCH message includes the MBS activation notification or the MBS deactivation notification; and configure multicast MBS reception when the MCCH message includes the MBS activation notification; or deconfigure multicast MBS reception when the MCCH message includes the MBS deactivation notification.

[0142] Embodiment 26 is a device according to embodiment 19, wherein the device is further configured to receive an MBS paging message, wherein the MBS paging message includes the MBS activation notification or the MBS deactivation notification; and configure multicast MBS reception when the MBS paging message includes the MBS activation notification; or deconfigure multicast MBS reception when the MBS paging message includes the MBS deactivation notification.

[0143] Embodiment 27 is the apparatus of embodiment 26, wherein the MBS paging message is a multicast specific paging message for indicating the MBS activation notification or the MBS deactivation notification.

[0144] Embodiment 28 is an apparatus according to embodiment 19, wherein the apparatus is further configured to receive a layer 1 (L1) or layer 2 (L2) multicast MBS indication, wherein the L1 or L2 multicast MBS indication includes the MBS activation notification or the MBS deactivation notification; and when the L1 or L2 multicast MBS indication includes the MBS activation notification, configure multicast MBS reception; or when the L1 or L2 multicast MBS indication includes the MBS deactivation notification, deconfigure multicast MBS reception.

[0145] Embodiment 29 is the apparatus of embodiment 28, wherein the L1 or L2 multicast MBS indication is an MBS medium access control (MAC) control element (CE), and the MBS MAC CE indicates MBS session information for one or more MBS sessions.

[0146] Embodiment 30 is a baseband processor of a user equipment (UE), the baseband processor comprising: one or more processors, the one or more processors being configured to: receive a suspension configuration in a radio resource control (RRC) message, wherein the RRC message comprises an indication of enabling inactive multicast and broadcast service (MBS) reception by a base station (BS); configure the UE for an RRC inactive state based on the suspension configuration; after configuring the RRC inactive state, receive an MBS activation notification, an MBS session configuration, and an RRC resumption indication; configure the UE for an RRC connected state based on the RRC resumption indication; configure multicast MBS reception based on the MBS session configuration; and when the UE is configured for the RRC connected state, receive multicast MBS data based on the MBS session configuration.

[0147] Embodiment 31 is a baseband processor of a user equipment (UE), the baseband processor comprising: one or more processors, the one or more processors being configured to: receive a pause configuration in a radio resource control (RRC) message, wherein the RRC message comprises an indication of enabling inactive multicast and broadcast service (MBS) reception by a base station (BS); configure the UE for an RRC inactive state based on the pause configuration; receive an MBS activation notification after configuring the UE for the RRC inactive state; perform a small data transmission (SDT) process and receive an MBS session configuration in response to performing the SDT process; and configure multicast MBS reception based on the MBS session configuration; and receive multicast MBS data based on the MBS session configuration.

[0148] Embodiment 32 is a baseband processor according to embodiment 31, wherein the SDT process includes: generating an MBS session resource request; receiving the MBS session configuration in response to generating the MBS session resource request; and receiving the multicast MBS data when the UE is configured for the RRC inactive state.

[0149] Embodiment 33 is a baseband processor according to embodiment 31, wherein the SDT process includes: generating an MBS session resource request; receiving the MBS session configuration and RRC recovery indication in response to generating the MBS session resource request; configuring the UE for an RRC connected state based on the RRC recovery indication; and receiving the multicast MBS data when the UE is configured for the RRC connected state.

[0150] Embodiment 34 is a baseband processor according to embodiment 31, wherein the baseband processor is further configured to detect failure of the SDT process; perform an RRC recovery process or an RRC establishment process in response to detecting failure of the SDT process; receive the MBS session configuration in response to performing the RRC recovery process or the RRC establishment process; configure the UE for an RRC connected state based on the RRC recovery process or the RRC establishment process; and receive the multicast MBS data based on the MBS session configuration when the UE is configured for the RRC connected state.

[0151] Embodiment 35 is a baseband processor according to any one of embodiments 31 to 34, wherein the one or more processors are further configured to: after receiving the MBS activation notification, determine that the UE does not have the MBS session configuration; and then perform the SDT process.

[0152] Embodiment 36 is a baseband processor of a user equipment (UE), comprising: one or more processors, wherein the one or more processors are configured to: receive a pause configuration in a radio resource control (RRC) message; configure the UE for an RRC inactive state based on the pause configuration; receive a multicast and broadcast service (MBS) session configuration and an MBS activation notification; perform a cell handover process or a cell reselection process, wherein the UE is connected to a new base station (BS); and receive multicast MBS data based on the MBS session configuration when the UE is configured for the RRC inactive state and after connecting to the new BS.

[0153] Embodiment 37 is a baseband processor according to embodiment 36, wherein the MBS session configuration includes a configuration region for enabling MBS reception for a session associated with the MBS session configuration; and the new BS is in the configuration region for enabled MBS reception.

[0154] Embodiment 38 is a baseband processor according to embodiment 36, wherein the MBS session configuration includes a cell list, the cell list indicating one or more cells enabled for MBS reception for a session associated with the MBS session configuration; and the new BS is included in the cell list indicating one or more cells.

[0155] Embodiment 38 is a baseband processor according to embodiment 38, wherein the cell list indicating one or more cells indicates a single cell or a radio access network (RAN).

[0156] Embodiment 40 is a baseband processor of a user equipment (UE), comprising: one or more processors, wherein the one or more processors are configured to: detect a multicast and broadcast service (MBS) session failure after receiving a multicast and broadcast service (MBS) activation notification when the UE is configured for an RRC inactive state; perform an RRC recovery process or an RRC establishment process after detecting the MBS session failure; receive an MBS session configuration in response to performing the RRC recovery process or the RRC establishment process; configure the UE for an RRC connected state based on the RRC recovery process or the RRC establishment process; and receive multicast MBS data based on the MBS session configuration when the UE is configured for the RRC connected state.

[0157] Embodiment 41 is a baseband processor according to embodiment 40, wherein the MBS session failure is detected when the UE fails to receive the MBS session configuration after configuring the RRC inactive state.

[0158] Embodiment 42 is a baseband processor according to embodiment 40, wherein the MBS session failure is detected when the UE is connected to a cell that does not provide the MBS session configuration after configuring the RRC inactive state.

[0159] Embodiment 43 is a baseband processor according to embodiment 40, wherein the MBS session failure is detected when the UE receives an MBS configuration associated with a session ID different from the session ID of the MBS activation notification.

[0160] Embodiment 44 is a baseband processor of a base station (BS), comprising: one or more processors, wherein the one or more processors are configured to: generate a pause configuration in a radio resource control (RRC) message, and generate a multicast and broadcast service (MBS) session configuration and an MBS activation notification, wherein the MBS session configuration and the MBS activation notification are used for RRC inactive state signaling; and after generating the MBS session configuration and the MBS activation notification, generate multicast MBS data based on the MBS session configuration for one or more user equipments (UEs) in an RRC inactive state.

[0161] Embodiment 45 is a baseband processor according to embodiment 44, wherein the MBS session configuration and the MBS activation notification are included in the RRC message together with the suspension configuration.

[0162] Embodiment 46 is the baseband processor of embodiment 44, the baseband processor being further configured to generate an indication to enable inactive MBS reception and include the indication in the RRC message.

[0163] Embodiment 47 is a baseband processor according to embodiment 44, wherein the baseband processor is further configured to generate the MBS session configuration in a system information block (SIB) or an MBS control channel (MCCH) message.

[0164] Embodiment 48 is a baseband processor according to embodiment 44, wherein the MBS session configuration is included in dedicated signaling.

[0165] Embodiment 49 is a baseband processor according to embodiment 44, wherein the MBS session configuration is included in broadcast signaling.

[0166] Embodiment 50 is a baseband processor according to embodiment 44, wherein the one or more processors are further configured to: after generating the MBS activation notification, receive a small data transmission (SDT) with an MBS session resource request; and generate the MBS session configuration after receiving the MBS session resource request.

[0167] Embodiment 51 is a baseband processor according to embodiment 44, wherein the MBS session configuration includes a configuration area for enabling MBS reception for a session associated with the MBS session configuration.

[0168] Embodiment 52 is a baseband processor according to embodiment 44, wherein the MBS session configuration includes a cell list indicating one or more cells enabled for MBS reception for a session associated with the MBS session configuration.

[0169] Embodiment 53 is a baseband processor according to embodiment 52, wherein the cell list indicating one or more cells indicates a single cell or multiple cells.

[0170] A method as substantially described herein with reference to each or any combination of those substantially described herein, including in Examples 1 to 53 and in the Detailed Description.

[0171] A non-transitory computer-readable medium as substantially described herein with reference to each or any combination of those substantially described herein, including in Examples 1 to 53 and in the detailed description.

[0172] A wireless device configured to perform any action or combination of actions as substantially described herein, including in Embodiments 1 to 53 and in the detailed description.

[0173] An integrated circuit configured to perform any action or combination of actions as substantially described herein, including in Examples 1 to 53 and in the detailed description.

[0174] A device configured to perform any action or combination of actions as substantially described herein, including in Examples 1 to 53 and in the detailed description.

[0175] A baseband processor configured to perform any action or combination of actions as substantially described herein, including in Examples 1 to 53 and in the detailed description.

[0176] In addition, various aspects or features described herein may be implemented as methods, devices or articles using standard programming and / or engineering techniques. As used herein, the term "article" is intended to cover computer programs accessible from any computer-readable device, carrier or medium. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips, etc.), optical disks (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., EPROMs, cards, sticks, key drives, etc.). Additionally, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data. Additionally, a computer program product may include a computer-readable medium having one or more instructions or codes that are operable to cause a computer to perform the functions described herein.

[0177] Communication media embodies computer readable instructions, data structures, program modules, or other structured or unstructured data in a data signal such as a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery or transmission media. The term "modulated data signal" or signal refers to a signal that has one or more of its characteristics set or changed in a manner that encodes information in one or more signals. By way of example, and not limitation, communication media include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

[0178] An exemplary storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integrated with the processor. In addition, in some aspects, the processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a user terminal or device.

[0179] In this regard, while the disclosed subject matter has been described in conjunction with various aspects and corresponding drawings, it should be understood that other similar aspects may be used or modifications and additions may be made to the described aspects to perform the same, similar, alternative or substitute functions of the disclosed subject matter without departing from the described aspects. Therefore, the disclosed subject matter should not be limited to any single aspect described herein, but should be interpreted in accordance with the breadth and scope of the claims appended hereto.

[0180] In particular, with respect to the various functions performed by the above-mentioned components or devices (components, devices, circuits, systems, etc.), unless otherwise specified, the terms used to describe such components or devices (including references to "components") are intended to correspond to any component, device, or structure that performs the specified function of the component or device (e.g., functionally equivalent), even if not structurally equivalent to the disclosed structure that performs the function in the exemplary implementation of the present disclosure illustrated herein. In addition, although specific features have been disclosed with respect to only one of several implementations, for any given or specific application, such features may be combined with one or more other features of other implementations, which may be desirable and advantageous.

[0181] The present disclosure is described with reference to the accompanying drawings, wherein throughout the text, similar figure numerals are used to refer to similar elements, devices or parts, and the structures and devices illustrated therein need not be drawn to scale. As used herein, the terms "device", "component", "system", "interface", etc. are intended to refer to entities, hardware, software (e.g., in execution) and / or firmware related to a computer. For example, a component may be a processor (e.g., a microprocessor, a controller or other processing device), a process running on a processor, a controller, an object, an executable file, a program, a storage device, a computer, a tablet computer and / or a user equipment (e.g., a mobile phone, etc.) with a processing device. In an illustrative manner, an application and a server running on a server may also be a component. One or more components may reside in a process, and a component may be located on a computer and / or distributed between two or more computers. Element sets or other component sets may be described herein, wherein the term "set" may be interpreted as "one or more".

[0182] In addition, these components can execute from various computer-readable or non-transitory computer-readable storage media having various data structures stored thereon, such as using modules, for example. The components can communicate via local and / or remote processes, such as according to signals having one or more data packets (e.g., data from one component interacts with another component in a local system, a distributed system, and / or an entire network, such as the Internet, a local area network, a wide area network, or a similar network with other systems via signals).

[0183] As another example, a component may be a device having a specific function, the specific function being provided by a mechanical component operated by an electrical or electronic circuit, wherein the electrical or electronic circuit may be operated by a software application or a firmware application executed by one or more processors. The one or more processors may be internal or external to the device and may execute at least a portion of the software application or the firmware application. As another example, a component may be a device that provides a specific function by electronic components without mechanical components; the electronic components may include one or more processors therein to execute at least a portion of the software and / or firmware that gives the electronic components their functions.

[0184] As used herein, the term "circuit" may refer to, may be a part of, or may include an application specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or group), or associated memory (shared, dedicated, or group) operably coupled to the circuit that executes one or more software or firmware programs, combinational logic circuits, or other suitable hardware components that provide the functionality described. In some aspects, the circuit may be implemented in one or more software or firmware modules, or the functions associated with the circuit may be implemented by one or more software or firmware modules. In some aspects, the circuit may include logic that may operate at least partially in hardware.

[0185] The use of the word "exemplary" is intended to present concepts in a specific way. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, "X adopts A or B" is intended to mean any natural inclusive arrangement of natural inclusive arrangements. That is, if X adopts A; X adopts B; or X adopts both A and B, then "X adopts A or B" is satisfied in any of the aforementioned cases. In addition, the articles "one" and "an" used in this application and the appended claims should generally be interpreted as meaning "one or more", unless otherwise specified or clear from the context to point to a singular form. In addition, to the extent that the terms "including", "including", "having", "having", "with" or their variations are used in the specific embodiments and claims, such terms are intended to be included in a manner similar to the term "comprising". Additionally, in the case of discussing one or more numbered items (e.g., "first X", "second X", etc.), generally, the one or more numbered items may be different or they may be the same, but in some cases, the context may indicate that they are different or that they are the same.

[0186] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

Claims

1. A baseband processor of a user equipment (UE), the baseband processor comprising: One or more processors configured to: receiving a suspension configuration in a radio resource control (RRC) message; configuring the UE for an RRC inactive state based on the suspension configuration; receiving a multicast and broadcast service (MBS) session configuration before or after configuring the RRC inactive state; configuring multicast MBS reception based on the MBS session configuration; as well as When the UE is configured for the RRC inactive state, multicast MBS data is received based on the MBS session configuration. 2 . The baseband processor of claim 1 , further configured to receive an MBS session activation notification before receiving the multicast MBS data. 3 . The baseband processor of claim 2 , wherein the MBS session activation notification is received before or after configuring multicast MBS reception. 4 . The baseband processor according to claim 1 , wherein the MBS session configuration and the MBS session activation notification are included in the RRC message including the suspension configuration. 5 . The baseband processor of claim 1 , the baseband processor being further configured to receive a broadcast configuration and deconfigure multicast MBS reception based on the broadcast configuration.

6. The baseband processor of claim 1, wherein the one or more processors further configure an MBS timer and a reception time threshold; and When the multicast MBS data is not received before the MBS timer exceeds the reception time threshold, the multicast MBS reception is deconfigured. 7 . The baseband processor of claim 1 , the baseband processor being further configured to perform a cell reselection procedure and to deconfigure multicast MBS reception in response to performing the cell reselection procedure.

8. The baseband processor of claim 7, wherein the MBS session configuration is received through broadcast signaling after the UE is configured for the RRC inactive state; After receiving the MBS session configuration, receiving an MBS session activation notification; and After receiving the MBS session activation notification, multicast MBS reception is configured.

9. The baseband processor of claim 7, the baseband processor being further configured to receive an MBS session activation notification after configuring the RRC inactive state, and to receive the MBS session configuration through broadcast signaling after receiving the MBS session activation notification.

10. The baseband processor of claim 1, wherein the RRC message including the suspension configuration further includes an indication of enabling inactive MBS reception by a base station (BS).

11. The baseband processor of claim 10, wherein the baseband processor is further configured to receive a system information block (SIB) or an MBS control channel (MCCH) message through broadcast signaling; and When the SIB or the MCCH message includes the MBS session configuration, activating the MBS session of the MBS session configuration, and the one or more processors further configuring multicast MBS reception in response to receiving the SIB or the MCCH message; or When the SIB or the MCCH message does not include the MBS session configuration, an MBS session of the MBS session configuration is deactivated, and the one or more processors further deconfigure multicast MBS reception in response to receiving the SIB or the MCCH message.

12. A device of a user equipment (UE), the device comprising: One or more processors configured to: receiving a suspension configuration in a radio resource control (RRC) message, wherein the RRC message includes an indication to enable inactive multicast and broadcast service (MBS) reception by a base station (BS); configuring the UE for an RRC inactive state based on the suspension configuration; Receive MBS activation notification and MBS session configuration; configuring multicast MBS reception based on the MBS session configuration; as well as When the UE is configured for the RRC inactive state, multicast MBS data is received based on the MBS session configuration and after receiving the MBS activation notification.

13. The apparatus of claim 12, wherein the MBS activation notification and the MBS session configuration are received in the RRC message including the suspension configuration.

14. The apparatus of claim 13, wherein the MBS activation notification is received in multicast signaling, and the one or more processors are further configured to: receiving an MBS session deactivation notification; and Multicast MBS reception is deconfigured based on the MBS session deactivation notification.

15. The apparatus according to claim 12, the apparatus being further configured to receive an MBS paging message, wherein the MBS paging message includes the MBS activation notification or the MBS deactivation notification; as well as configuring multicast MBS reception when the MBS paging message includes the MBS activation notification; or Multicast MBS reception is deconfigured when the MBS paging message includes the MBS deactivation notification. 16 . The apparatus according to claim 15 , wherein the MBS paging message is a multicast specific paging message for indicating the MBS activation notification or the MBS deactivation notification.

17. A baseband processor of a user equipment (UE), the baseband processor comprising: One or more processors configured to: receiving a suspension configuration in a radio resource control (RRC) message, wherein the RRC message includes an indication to enable inactive multicast and broadcast service (MBS) reception by a base station (BS); configuring the UE for an RRC inactive state based on the suspension configuration; receiving an MBS activation notification after configuring the UE for the RRC inactive state; performing a small data transmission (SDT) procedure and receiving an MBS session configuration in response to performing the SDT procedure; as well as configuring multicast MBS reception based on the MBS session configuration; as well as Multicast MBS data is received based on the MBS session configuration.

18. The baseband processor of claim 17, wherein the SDT process comprises: Generate an MBS session resource request; receiving the MBS session configuration in response to generating the MBS session resource request; as well as The multicast MBS data is received when the UE is configured for the RRC inactive state.

19. The baseband processor of claim 17, wherein the SDT process comprises: Generate an MBS session resource request; receiving the MBS session configuration and an RRC resume indication in response to generating the MBS session resource request; configuring the UE for an RRC connected state based on the RRC recovery indication; as well as The multicast MBS data is received when the UE is configured for the RRC connected state.

20. The baseband processor of claim 17, the baseband processor being further configured to detect failure of the SDT process; performing an RRC recovery procedure or an RRC establishment procedure in response to detecting that the SDT procedure fails; receiving the MBS session configuration in response to performing the RRC recovery procedure or the RRC establishment procedure; configuring the UE for an RRC connected state based on the RRC recovery procedure or the RRC establishment procedure; as well as The multicast MBS data is received based on the MBS session configuration when the UE is configured for the RRC connected state.

Images