Service continuity for multicast transmission for cell reselection

Abstract

The present application relates to devices and components, including apparatuses, systems, and methods, for providing processing of multicast data over user equipment while the user equipment is in an inactive state in a wireless communication system.

Description

[Background technology]

[0001] Third Generation Partnership Project (3GPP) networks provide for multicast transmission between base stations and user equipment (UE). In particular, a base station may multicast a transmission to multiple UEs. A UE may be in a connected state with the base station to receive the multicast transmission from the base station. This can enable the base station to communicate data to multiple UEs simultaneously. [Brief explanation of the drawings]

[0002] [Figure 1] 1 illustrates an exemplary network configuration, according to some embodiments.

[0003] [Figure 2] 1 illustrates an exemplary network configuration, according to some embodiments.

[0004] [Figure 3] 1 is an exemplary signaling chart illustrating lossless reconstruction according to some embodiments.

[0005] [Figure 4] 1 illustrates an exemplary cell selection configuration with a single cell list, according to some embodiments.

[0006] [Figure 5] 1 illustrates an exemplary cell selection configuration with a single cell list, according to some embodiments.

[0007] [Figure 6] 1 illustrates an example cell selection configuration with a frequency list, according to some embodiments.

[0008] [Figure 7] 1 illustrates an example cell selection configuration with a frequency list, according to some embodiments.

[0009] [Figure 8] 1 illustrates an example cell selection configuration with a cell list, according to some embodiments.

[0010] [Figure 9] 1 illustrates an example cell selection configuration with a cell list, according to some embodiments.

[0011] [Figure 10] 1 illustrates an example cell selection configuration with frequency / cell lists, according to some embodiments.

[0012] [Figure 11] 1 illustrates an exemplary procedure for determining resources for a multicast transmission, according to some embodiments.

[0013] [Figure 12] 1 illustrates another exemplary procedure for determining resources for a multicast transmission, according to some embodiments.

[0014] [Figure 13] 1 illustrates an exemplary procedure for indicating resources for a multicast transmission, according to some embodiments.

[0015] [Figure 14] 1 illustrates an exemplary user equipment (UE) in accordance with some embodiments.

[0016] [Figure 15] 1 illustrates an exemplary next generation Node B (gNB) in accordance with some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0017] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc., in order to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to one skilled in the art having the benefit of this disclosure that various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In some instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For purposes of this disclosure, "A or B" means (A), (B), or (A and B).

[0018] The following is a glossary of terms that may be used in this disclosure.

[0019] As used herein, the term “circuitry” refers to, is a part of, or includes a hardware component configured to provide a described functionality, such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group), an application-specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-volume PLD (HCPLD), a structured ASIC, a programmable system-on-chip (SoC)), a digital signal processor (DSP), or the like. In some embodiments, a circuitry can execute one or more software or firmware programs to provide at least a portion of the described functionality. The term “circuitry” can also refer to the combination of one or more hardware elements (or a combination of circuitry used in an electrical or electronic system) with program code used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0020] As used herein, the term "processor circuitry" refers to, is a part of, or includes circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transferring digital data. The term "processor circuitry" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions such as program code, software modules, or functional processes.

[0021] As used herein, the term "interface circuitry" refers to, is a part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as, for example, a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0022] As used herein, the term "user equipment" or "UE" refers to a device having wireless communication capabilities and may represent a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0023] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or component thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computing devices or multiple computing systems that are communicatively coupled to each other and configured to share computing or networking resources.

[0024] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component in a computing environment, or a physical or virtual component in a particular device, such as a computer device, a mechanical device, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link assignments, throughput, memory usage, storage, networks, databases and applications, workload units, etc. "Hardware resources" may refer to computational, storage, or network resources provided by physical hardware element(s). "Virtualized resources" may refer to computational, storage, or network resources provided by a virtualization infrastructure to an application, device, system, etc. The terms "network resources" or "communication resources" may refer to resources accessible by a computer device / system via a communication network. The term "system resources" may refer to any kind of shared entity for providing services and may include computing resources or network resources. A system resource may be thought of as a set of coherent functions, network data objects, or services, where such system resource resides on a single host or multiple hosts and is accessible through a clearly identifiable server.

[0025] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to communicate data or data streams. The term "channel" may be synonymous with or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium over which data is communicated. Additionally, as used herein, the term "link" refers to a connection between two devices for the purpose of transmitting and receiving information.

[0026] As used herein, the terms "instantiate," "instantiation," and the like refer to the creation of an instance. An "instance" also refers to a specific occurrence of an object that may occur, for example, during the execution of program code.

[0027] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other via a communication channel, link, interface, or reference point.

[0028] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communications network services. The term "network element" may be considered synonymous with or referred to as a networked computer, network hardware, network equipment, network node, virtualized network function, etc. In embodiments, the term "network element" may refer to a base station, a NodeB, an evolved NodeB (eNB), and / or a next generation NodeB (gNB) (e.g., gNB 1500 (FIG. 15)).

[0029] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to an information element or an individual piece of content in a data element that contains content. An information element may contain one or more further information elements.

[0030] This disclosure refers to the states "connected" and "inactive." These states are well known in the art and should be interpreted as known in the art. For example, each of the "connected" and "inactive" states may exhibit at least some different characteristics from other states and / or may exhibit different connections from other states.

[0031] MBS Extension

[0032] Justification

[0033] To enable resource-efficient delivery of multicast / broadcast services, the 3rd Generation Partnership Project (3GPP) developed New Radio (NR) Broadcast / Multicast in Release 17 (Rel-17) according to the Work Item Description (WID) in RP-201038, aiming to enable general multicast / broadcast service (MBS) services over fifth-generation systems (5GS). Use cases identified that can benefit from this feature include public safety and mission-critical applications, vehicle-to-everything (V2X) applications, Internet Protocol Television (IPTV), live video, and software distribution over wireless and Internet of Things (IoT) applications. Two delivery modes have been agreed upon for Rel-17 MBS: Delivery Mode 1 (multicast only), which can address higher quality of service (QoS) services, and Delivery Mode 2 (broadcast only), which focuses on lower QoS services. Considering that Rel-17 MBS already provides basic functionality to support MBS services, the general main goal of Release 18 (Rel-18) should be to enable better deployment of MBS, including resource efficiency and capacity improvements based on Rel-17 MBS.

[0034] In Rel-17, the radio access network (RAN) only specifies multicast for user equipment (UE) in RRC_CONNECTED state, which may not fully meet the requirements of, for example, mission-critical services, especially for cells with a large number of UEs according to TR 23.774. Also, keeping UEs in RRC_CONNECTED state all the time is not power efficient. Therefore, it is important to support multicast for UEs in RRC_INACTIVE.

[0035] The New Radio (NR) MBS broadcast solution in Rel-17 allows UEs to receive broadcast services in a downlink-only manner, i.e., perform broadcast reception without the need for prior network access. However, in typical use cases for broadcast, UEs may need to simultaneously receive broadcast and unicast services from the same or another operator's network(s), and some UEs may share hardware resources between broadcast and unicast. Therefore, unicast connectivity may be affected by broadcast reception for this type of UE. Optimization for such cases is not specifically addressed in Rel-17 and should focus on the cases of unicast reception in RRC_CONNECTED and broadcast reception from the same or different operators, including emergency and public safety broadcasts.

[0036] Network sharing is a common practice to reduce network capital expenditures (CAPEX). In a RAN sharing deployment, when the same multicast / broadcast service is provided separately by two (or more) operators, this service is recognized as a separate Temporary Mobile Group Identity (TMGI), resulting in overlapping point-to-multipoint (PTM) radio resource consumption in the same cell for transmission of the same content. This justifies improved resource efficiency in a RAN sharing scenario.

[0037] Note that public safety services benefit from the Rel-17 NR MBS capabilities as well as the Rel-18 extensions following the justifications above.

[0038] the purpose

[0039] The purpose of the System Information (SI) or Core Work Item (WI) or Test Work Item (WI).

[0040] This work item further enhances NR multicast / broadcast capabilities based on Rel-17 MBS. Rel-18 objectives include specifying support for multicast reception by UEs in RRC_INACTIVE state [Radio Access Network Group 2 (RAN2), Radio Access Network Group 3 (RAN3)], PTM configuration for UEs receiving multicast in RRC_INACTIVE state [RAN2], and considering the impact of mobility and state transitions for UEs receiving multicast in RRC_INACTIVE (seamless / lossless mobility is not required) [RAN2, RAN3]. Further objectives include specifying Uu signaling extensions to enable UEs to use shared processing for MBS broadcast and unicast reception, i.e., including UE capability and related assistance information reporting for simultaneous unicast reception and MBS broadcast reception from the same or different operators in RRC_CONNECTED [RAN2], and considering and, if necessary, specifying extensions to improve resource efficiency for MBS reception in RAN sharing scenarios [RAN3]. Note: Collaboration with System Aspects Working Group 2 (SA2) is expected in due course for the above purposes. Issuance Statement

[0041] Multicast service continuity in Release 17 (R17). Multicast transmission is supported only for connected UEs. For handovers between multicast-enabled Next Generation NodeBs (gNBs), service continuity and lossless handover for multicast MBS are supported during handover. Lossless handover is supported from point-to-point (PTP) to PTP or from PTP to PTP + point-to-multipoint (PTM). For service continuity, the network (NW) can provide MBS multicast service continuity during handover. For example, downlink (DL) Packet Data Convergence Protocol (PDCP) sequence number (SN) synchronization and continuity between the source and target cells are supported. The source gNB can forward data from the source gNB to the target gNB for lossless handover or to minimize interruptions. The UE can provide PDCP status reports for the MBS radio bearer (MRB) in the target cell, and the NW can retransmit lossless packets based on the reports.

[0042] For handover from a multicast-supporting gNB to a non-supporting gNB, the core network (CN) can switch the MRB to a dedicated radio bearer (DRB) and continue to provide MBS services over the radio bearer. In Release 18 (R18), service continuity is supported for multicast MBS transmissions in INACTIVE state, and some extensions need to be considered.

[0043] 1 illustrates an exemplary network configuration 100 in accordance with some embodiments. The network configuration 100 illustrates an exemplary UE handover from a first cell 102 supporting MBS data resource bearers (DRBs) to a second cell 104 supporting MBS DRBs.

[0044] The network configuration 100 may include a UE 106. The UE 106 may be moving from a first position 108 in a first cell 102 (indicated by a dotted version of the UE 106 shown in the first position 108) to a second position 110 in a second cell 104.

[0045] The network configuration 100 may include a source base station 112 and a target base station 114 (both shown as gNBs in the illustrated embodiment). The source base station 112 may serve a first cell 102, and the source base station 112 may serve a UE located in the first cell 102. The target base station 114 may serve a second cell 104, and the target base station 114 may serve a UE located in the second cell 104. When the UE 106 moves from a first position 108 in the first cell 102 to a second position 110 in the second cell 104, a handover may be performed to hand over service of the UE 106 from the source base station 112 to the target base station 114.

[0046] The network configuration 100 may include a CN 116. The CN 116 may be coupled to both the source base station 112 and the target base station 114. Both the source base station 112 and the target base station 114 may communicate with the CN 116 to provide services.

[0047] The network configuration 100 may include an MBS server 118. The MBS server 118 may be coupled to the CN 116. The MBS server 118 may provide an MBS session delivered by the CN 116, where the MBS session is represented by a first MBS packet 120 and a second MBS packet 122. The CN 116 may provide the first MBS packet 120 and the second MBS packet 122 to both the source base station 112 and the target base station 114. The first MBS packet 120 transmitted to both the source base station 112 and the target base station 114 may have the same SN. Furthermore, the second MBS packet 122 transmitted to both the source base station 112 and the target base station 114 may have the same SN.

[0048] Because the source base station 112 supports MBS DRB, the UE 106 may receive multicast data via multicast transmission when located at the first position 108. Because the target base station 114 supports MBS DRB, the UE 106 may continue to receive multicast data via multicast transmission when located at the second position 110. Thus, the UE 106 may receive multicast data via multicast transmission from the source base station 112 before handover and may receive multicast data via multicast transmission from the target base station 114 after handover. Handover between the source base station 112 and the target base station 114 may be supported for the UE 106 in a connected state, and may provide the features for handover between gNBs supporting multicast described above.

[0049] 2 illustrates an exemplary network configuration 200 in accordance with some embodiments. The network configuration 200 illustrates an exemplary UE handover from a first cell 202 that supports MBS data resource bearers (DRBs) to a second cell 204 that does not support MBS DRBs.

[0050] The network configuration 200 may include a UE 206. The UE 206 may be moving from a first position 208 (indicated by a dotted version of the UE 206 shown in the first position 208) in a first cell 202 to a second position 210 in a second cell 204.

[0051] The network configuration 200 may include a source base station 212 and a target base station 214 (both shown as gNBs in the illustrated embodiment). The source base station 212 may serve a first cell 202, and the source base station 212 may serve a UE located in the first cell 202. The target base station 214 may serve a second cell 204, and the target base station 214 may serve a UE located in the second cell 204. When the UE 206 moves from a first position 208 in the first cell 202 to a second position 210 in the second cell 204, a handover may be performed to hand over service of the UE 206 from the source base station 212 to the target base station 214.

[0052] The network configuration 200 may include a CN 216. The CN 216 may be coupled to both the source base station 212 and the target base station 214. Both the source base station 212 and the target base station 214 may communicate with the CN 216 to provide services.

[0053] The network configuration 200 may include an MBS server 218. The MBS server 218 may be coupled to the CN 216. The MBS server 218 may provide MBS sessions distributed by the CN 216. The CN 216 may provide the MBS sessions to the source base station 212, which may support MBS DRB and provide the MBS sessions via multicast transmission. In contrast, the target base station 214 may not support MBS DRB and may instead support unicast DRB. The CN 216 may provide the MBS sessions received from the MBS to the target base station 214 as unicast protocol data unit (PDU) sessions based on the target base station 214's support of unicast DRB.

[0054] Because the source base station 212 supports MBS DRBs, the UE 206 may receive multicast data via multicast transmission when located at the first position 208. Because the target base station 214 does not support MBS DRBs but does support unicast DRBs, the UE 206 may receive unicast PDU data via DRBs when located at the second position 210. Thus, the UE 206 may receive multicast data via multicast transmission from the source base station 212 before handover and may receive unicast PDU data via DRBs from the target base station 214 after handover. Handover between the source base station 212 and the target base station 214 may be supported for the UE 106 in a connected state, and may provide features for handover between multicast-supporting and non-multicast-supporting gNBs, as described above.

[0055] 3 illustrates an exemplary signaling chart 300 illustrating lossless reconfiguration according to some embodiments. For example, signaling chart 300 illustrates signals that may be exchanged to facilitate lossless reconfiguration.

[0056] The signaling chart 300 may include a UE 302 and a network element 304. The UE 302 may include one or more features of the UE 1400 (FIG. 14). The network element 304 may include one or more features of the gNB 1500 (FIG. 15). The signaling chart 300 illustrates signals that may be exchanged between the UE 302 and the network element 304 for lossless reconfiguration of the UE 302.

[0057] The signaling chart 300 may begin with an RRC reconfiguration 306 of the UE 302. In particular, the UE 302 and the network element 304 may exchange one or more signals to reconfigure the RRC of the UE 302. The RRC reconfiguration 306 in the illustrated embodiment may reconfigure the UE 302 for MRBs associated with PTPs and PTMs. Thus, the UE 302 may be reconfigured with configurations for the MRB-related PTPs and PTMs in the illustrated embodiment.

[0058] Once the UE 302 is configured by the RRC reconfiguration 306, the network element may send one or more MBS transmissions 308 to the UE 302 over the PTM and PTP channels. The UE 302 may receive the MBS transmissions 308 and process the MBS transmissions 308 using the configuration indicated by the RRC reconfiguration 306. In some instances, one or more PDCP PDUs and / or service data units (SDUs) provided within the MBS transmissions 308 may not be properly received and / or processed by the UE 302.

[0059] Another RRC reconfiguration 310 may be performed between the UE 302 and the network element 304. For example, one or more signals may be exchanged between the UE 302 and the network element 304 for the RRC reconfiguration 310 to reconfigure the UE 302 with a new configuration. The RRC reconfiguration 310 may indicate the configuration of an MRB with PTP, in the illustrated embodiment. The RRC reconfiguration 310 may further include an indication of a PDCP status report (SR) inquiry for the UE 302. For example, the RRC reconfiguration 310 may request that the UE provide a PDCP status report.

[0060] The UE 302 can send a PDCP status report 312 to the network element 304. The UE 302 may send the PDCP status report 312 in response to the RRC reconfiguration 310. The PDCP status report 312 may indicate SNs for PDUs and / or SDUs that were properly received and processed by the UE 302. The PDCP status report 312 may be for an MRB. In the illustrated embodiment, the PDCP may receive and properly process PDUs and / or SDUs having SNs 6-9 and 11-19. The properly processed PDUs and / or SDUs may be stored by the UE 302. The PDCP status report 312 may indicate SNs for PDUs and / or SDUs stored by the UE 302 and / or SNs for PDUs and / or SDUs that the UE 302 determined were not properly received.

[0061] The network element 304 may send an additional MBS transmission 314 to the UE 302 via PTP. The MBS transmission 314 may include PDUs and / or SDUs that were not previously properly processed by the UE 302. For example, the network element 304 may determine, based on the PDCP status report 312, that the UE 302 did not properly process a PDU or SDU corresponding to SN 5 and a PDU or SDU corresponding to SN 10. The network element 304 may retransmit the PDU or SDU corresponding to SN 5 and the PDU or SDU corresponding to SN 10 in the MBS transmission 314. In particular, the MBS transmission 314 may include PDUs and / or SDUs 316. As can be seen, the PDUs and / or SDUs 316 of the MBS transmission 314 include a PDU or SDU corresponding to SN 5 and a PDU or SDU corresponding to SN 10. Upon receiving SN 5 and SN 10, the UE may deliver all previously stored PDCP SDUs and / or PDUs to higher layers. Approach: Service Continuity During Inactive Mobility

[0062] A network (NW) can provide a cell list / frequency list, and the NW can provide an INACTIVE multicast service to a UE via dedicated signaling or broadcast signaling. For example, an NE can provide a cell list and / or a frequency list, and the NW can provide a multicast service to a UE via dedicated signaling or broadcast signaling when the UE is in an inactive state. A cell in the cell list and / or a frequency in the frequency list may be referred to as a resource. A resource may be provided by the network.

[0063] Optionally, the NW can provide the UE with a cell list associated only with the UE joint multicast MBS session. For example, the NW can provide the UE with a cell list, which can be associated with a PTP link and a PTM link. Signaling format: Dedicated signaling is via an RRCRelease message, and broadcast signaling is via a multicast-related system information block (SIB) and a multicast / broadcast service control channel (MCCH) configuration. For example, the signaling format for dedicated signaling can be via RRCRelease messaging. The signaling format for broadcast signaling can be via a multicast-related SIB and an MCCH configuration.

[0064] Cell / frequency list configuration: Option 1: cells in the list provide multicast services; Option 2: multiple cell / frequency lists, one per multicast MBS session; Option 3: two cell / frequency lists, one for multicast services provided in CONNECTED state and one for multicast services provided in INACTIVE state; Option 4: combination of options 2 and 3, i.e. providing a cell / frequency list per multicast MBS session per RRC state.

[0065] For example, the cell and / or frequency list may have multiple options for configuration. In a first option, the NW may provide a list of cells that provide multicast services. In particular, the cells in the list of cells may be capable of providing multicast services to the UE. In this option, the list of cells may not distinguish which MBS session is provided by which cell in the list.

[0066] In a second option, the NW may provide one or more lists of one or more resources for providing the multicast service. The resources in the lists may be cells in some embodiments and frequencies in other embodiments. Each of the lists may correspond to a multicast MBS session. For example, a first list of resources may correspond to a first multicast MBS session, and a second list of resources may correspond to a second multicast MBS session.

[0067] In a third option, the NW may provide two lists of one or more resources for providing a multicast service. The resources in the lists may be cells in some embodiments and frequencies in other embodiments. The first list of resources may indicate resources for the multicast service that are provided when the UE is in a connected state. The second list of resources may indicate resources for the multicast service that are provided when the UE is in an inactive state.

[0068] A fourth option may combine the second and third options. For example, the NW may provide one or more lists of one or more resources for providing a multicast service. The resources in the list may be cells in some embodiments and frequencies in other embodiments. Each list may correspond to a multicast MBS session and an RRC state.

[0069] UE Behavior. The UE may prioritize camping on a cell in the list 1) when an MBS session is activated, or 2) when the UE is participating in at least one MBS session regardless of the RRC state. If a list is provided per MBS session, the UE may prioritize a cell in the list associated with that joint MBS session. If a list is provided per RRC state, the UE may provide a cell in the list associated with the RRC state according to the following rules: 1) the NW indicates which RRC state has higher priority, or 2) it is up to the UE implementation, or 3) it predefines which RRC state has higher priority.

[0070] During cell reselection, if the UE cannot find a suitable cell in the list, it shall camp on a suitable cell and trigger the RRCResume procedure, requesting to enter the CONNECTED state.

[0071] Example 1: One Cell / Frequency List. The NW provides only one cell / frequency list to indicate cells that support an inactive multicast service. For example, the network may provide a cell list or a frequency list to indicate one or more cells that support a multicast service while the UE is in an inactive state. Figure 4 shows an exemplary cell selection configuration 400 with a single cell list, according to some embodiments. In particular, cell selection configuration 400 shows an example of Option 1, in which the network may provide a list of cells to indicate cells that support an inactive multicast service. In other embodiments, the list of cells may be replaced by a list of frequencies, and the list of frequencies may replace the list of cells in operation throughout this specification.

[0072] The cell selection configuration 400 shows an example location configuration 402 and an example signaling chart 412 for cell selection using a single cell list. The location configuration 402 in the illustrated embodiment shows a first cell area 404, a second cell area 406, and a third cell area 408. The first cell area 404 indicates an area that can be served by a first cell, the second cell area 406 indicates an area that can be served by a second cell, and the third cell area 408 indicates an area that can be served by a third cell.

[0073] The location configuration 402 further shows an arrow 410 indicating movement of the UE within the area. As can be seen from the arrow 410, the UE starts within the first cell area 404. The UE moves from the first cell area 404 to areas within the first cell area 404, the second cell area 406, and the third cell area 408, as shown by the arrow 410. Based on the UE's movement shown by the arrow 410, the UE may determine that a reselection should be performed from being served by a first cell to being served by another cell based on movement toward an edge of the first cell area 404.

[0074] The signaling chart 412 may include a UE 414, a first network element 416 corresponding to a first cell, and a second network element 418 corresponding to a second cell. The UE 414 may correspond to a UE indicated by an arrow 410 in the location configuration 402. The first cell of the first network element 416 may correspond to a first cell area 404, where the first cell serves the first cell area 404. The second cell of the second network element 418 may correspond to a second cell area 406, where the second cell serves the second cell area 406. The UE 414 may include one or more of the features of the UE 1400 (FIG. 14). The first network element 416 and the second network element 418 may each include one or more of the features of the gNB 1500 (FIG. 15).

[0075] At the start of the signaling chart 412, the UE 414 may be in a connected state, as indicated by connection 420. In particular, the UE 414 may be connected to the first network element 416 based on the UE 414 being located within the first cell area 404 at the start of the signaling chart 412.

[0076] The first network element 416 may send an RRC release with suspend configuration message 422 to the UE 414 to transition the UE 414 to an inactive state. The first network element 416, in some embodiments, may send the RRC release with suspend configuration message 422 based on the UE 414 moving toward an edge of the first cell area 404. In some embodiments, the first network element 416 may send the RRC release with suspend configuration message 422 based on a condition being met for transitioning the UE 414 to an inactive state, such as no transmissions being transmitted between the UE 414 and the first network element 416.

[0077] The RRC release with suspend configuration message 422 may include a cell list 424 indicating one or more cells. The cell list 424 may indicate one or more cells that can provide multicast service to the UE 414 while the UE 414 is in an inactive state. In the illustrated example, the cell list 424 indicates that a first cell and a second cell can provide multicast service to the UE 414 while the UE 414 is in an inactive state.

[0078] The UE 414 may receive the RRC release with suspend configuration message 422 and may identify the RRC release with suspend configuration message 422. The UE 414 may further identify a cell list 424 in the RRC release with suspend configuration message 422. The UE 414 may determine which cells and / or network elements can provide multicast service to the UE 414 while the UE 414 is in an inactive state. In the illustrated example, the UE 414 may determine, based on the cell list 424, that a first cell (served by the first network element 416) and a second cell (served by the second network element 418) can provide multicast service to the UE 414 when the UE 414 is in an inactive state. When the UE 414 is in an inactive state to be utilized to select a cell to camp on in a subsequent cell reselection, the UE 414 may store an indication of the first cell and the second cell as being capable of providing multicast service to the UE 414.

[0079] The UE 414 may determine that the UE 414 transitions to an inactive state based on the RRC release with suspend configuration message 422. The UE 414 may transition to an inactive state, as indicated by inactive 426.

[0080] The UE 414 may perform a cell reselection procedure 428 while in an inactive state. The UE 414 may perform the cell reselection procedure 428 based on conditions for cell reselection being met, such as the quality of service provided by the current cell and / or the signal strength of a signal provided by the current cell being below a threshold level. In the illustrated example, the UE 414 may perform the cell reselection procedure 428 when the UE 414 is located within an area located within the first cell area 404, the second cell area 406, and the third cell area 408.

[0081] The UE 414 may select a cell to camp on using information from the cell list 424. For example, the UE 414 may use stored indications that a first cell and a second cell can provide multicast service to the UE 414 when the UE 414 is in an inactive state. The UE 414 may prioritize selecting the cells indicated in the cell list 424 for reselection. In the illustrated example, the UE 414 may prioritize selecting the first cell and the second cell over other cells based on the cell list 424.

[0082] The UE 414 may determine which cells are available for selection during the cell reselection procedure 428. In the illustrated example, when the UE 414 is located in an area located within the first cell area 404, the second cell area 406, and the third cell area 408, the UE 414 may determine that the first cell, the second cell, and the third cell are available. The UE 414 may also, in some embodiments, determine the signal quality of the available cells. Because the UE 414 is performing reselection from the first cell (possibly based on the signal quality of the first cell being below a threshold quality), the UE 414 may decide not to select the first cell. The UE 414 may still have the opportunity to select the second cell or the third cell. Because the second cell is shown in the cell list 424, the UE 414 may determine to prioritize the second cell over the third cell in the illustrated embodiment. Based on the prioritization, the UE 414 may select a second cell to camp on as a result of a cell reselection procedure 428.

[0083] The second network element 418 (corresponding to the second cell) may transmit a broadcast message 430. The broadcast message 430 may include an indication of an inactive multicast configuration to be utilized to process the multicast transmissions transmitted by the second network element 418. Based on the UE 414 selecting to camp on the second cell, the UE 414 may receive and process the broadcast message 430. Based on the broadcast message 430, the UE 414 may be configured with an inactive multicast configuration to process the multicast transmissions transmitted by the second network element 418.

[0084] The second network element 418 can transmit multicast data 432. The multicast data 432 may correspond to MBS session #X. The UE 414 can receive the multicast data 432 while the UE 414 is in an inactive state. Furthermore, the UE 414 can utilize the inactive multicast configuration from the broadcast message 430 to process the multicast data 432. Thus, the UE 414 can receive and process the multicast data while in an inactive state that was not available with the legacy approach.

[0085] While signaling chart 412 illustrates exemplary signals that may be exchanged by the UE and the network elements, it should be understood that in some embodiments, additional signals may be included or some of the signals may be omitted. For example, the signals may be part of a larger procedure that includes additional signals.

[0086] 5 illustrates an exemplary cell selection configuration 500 with a single cell list, according to some embodiments. In particular, cell selection configuration 500 illustrates an example of Option 1, in which the network may provide a list of cells to indicate cells that support an inactive multicast service. In other embodiments, the list of cells may be replaced by a list of frequencies, and the list of frequencies may replace the list of cells in operation throughout this specification.

[0087] The cell selection configuration 500 shows an example location configuration 502 and an example signaling chart 512 for cell selection using a single cell list. The location configuration 502 in the illustrated embodiment shows a first cell area 504, a second cell area 506, and a third cell area 508. The first cell area 504 indicates an area that can be served by a first cell, the second cell area 506 indicates an area that can be served by a second cell, and the third cell area 508 indicates an area that can be served by a third cell.

[0088] The location configuration 502 further shows an arrow 510 indicating movement of the UE within the area. As can be seen from the arrow 510, the UE starts within the first cell area 504. The UE moves from the first cell area 504 to areas within the first cell area 504 and third cell area 508, as shown by the arrow 510. As can be seen from the arrow 510, the UE does not move into the second cell area 506. Based on the UE's movement shown by the arrow 510, the UE may determine that a reselection should be performed from being served by a first cell to being served by another cell based on movement toward an edge of the first cell area 504.

[0089] The signaling chart 512 may include a UE 514, a first network element 516 corresponding to a first cell, and a second network element 518 corresponding to a third cell. The UE 514 may correspond to a UE indicated by an arrow 510 in the location configuration 502. The first cell of the first network element 516 may correspond to a first cell area 504, where the first cell serves the first cell area 504. The third cell of the second network element 518 may correspond to a third cell area 508, where the third cell serves the third cell area 508. The UE 514 may include one or more of the features of the UE 1400 (FIG. 14). The first network element 516 and the second network element 518 may each include one or more of the features of the gNB 1500 (FIG. 15).

[0090] At the start of the signaling chart 512, the UE 514 may be in a connected state, as indicated by connection 520. In particular, the UE 514 may be connected to a first network element 516 based on the UE 514 being located within the first cell area 504 at the start of the signaling chart 512.

[0091] The first network element 516 may send an RRC release with suspend configuration message 522 to the UE 514 to transition the UE 514 to an inactive state. The first network element 516 may, in some embodiments, send the RRC release with suspend configuration message 522 based on the UE 514 moving toward an edge of the first cell area 504. In some embodiments, the first network element 516 may send the RRC release with suspend configuration message 522 based on a condition being met for transitioning the UE 514 to an inactive state, such as no transmissions being transmitted between the UE 514 and the first network element 516.

[0092] The RRC release with suspend configuration message 522 may include an indication to enable multicast reception in the inactive state. In particular, the indication to enable multicast reception may indicate to the UE 514 that multicast reception should be enabled for the UE 514 when the UE 514 is in the inactive state.

[0093] The UE 514 may receive the RRC Release with Suspend Configuration message 522 and identify the RRC Release with Suspend Configuration message 522. The UE 514 may further identify an indication that multicast reception should be enabled for the UE 514 when the UE 514 is in an inactive state. In some embodiments, the UE 514 may be configured with a configuration for handling multicast transmissions when in an inactive state. The configuration may have been previously received by the UE 514.

[0094] The UE 514 may determine that the UE 514 should transition to an inactive state based on the RRC release with suspend configuration message 522. The UE 514 may transition to an inactive state, as indicated by inactive 524.

[0095] The first network element 516 may transmit a broadcast message 526. The first network element 516 may broadcast the broadcast message 526. The broadcast message 526 may include a cell list 528 indicating one or more cells. The cell list 528 may indicate one or more cells that can provide multicast service to the UE 514 while the UE 514 is in an inactive state. In the illustrated example, the cell list 528 indicates that a first cell and a second cell can provide multicast service to the UE 514 while the UE 514 is in an inactive state.

[0096] The UE 514 may receive the broadcast message 526 and identify the broadcast message 526. The UE 514 may further identify a cell list 528 in the broadcast message 526. The UE 514 may determine which cells and / or network elements can provide multicast service to the UE 514 while the UE 514 is in an inactive state. In the illustrated example, the UE 514 may determine, based on the cell list 528, that a first cell and a second cell (served by the first network element 516) can provide multicast service to the UE 514 when the UE 514 is in an inactive state. The UE 514 may store an indication of the first cell and the second cell as being capable of providing multicast service to the UE 514 when the UE 514 is in an inactive state to be utilized for selecting a cell to camp on in a subsequent cell reselection.

[0097] The UE 514 may perform a cell reselection procedure 530 while in an inactive state. The UE 514 may perform the cell reselection procedure 530 based on conditions for cell reselection being met, such as the quality of service provided by the current cell and / or the signal strength of a signal provided by the current cell being below a threshold level. In the illustrated example, the UE 514 may perform the cell reselection procedure 530 when the UE 514 is located in an area located within the first cell area 504 and the third cell area 508.

[0098] The UE 514 may utilize information from the cell list 528 to select a cell to camp on. For example, the UE 514 may utilize stored indications that a first cell and a second cell can provide multicast service to the UE 514 when the UE 514 is in an inactive state. The UE 514 may prioritize selecting the cells indicated in the cell list 528 for reselection. In the illustrated example, the UE 514 may prioritize selecting the first cell and the second cell over other cells based on the cell list 528.

[0099] The UE 514 may determine which cells are available for selection during the cell reselection procedure 530. In the illustrated example, when the UE 514 is located in an area located within the first cell area 504 and the third cell area 508, the UE 514 may determine that the first cell and the third cell are available. The UE 514 may also, in some embodiments, determine the signal quality of the available cells. Because the UE 514 is performing reselection from the first cell (possibly based on the signal quality of the first cell being below a threshold quality), the UE 514 may decide not to select the first cell. The UE 514 may still have an opportunity to select the third cell. Because the first cell and the second cell have been excluded for service selection, the UE 514 may decide to select the third cell (corresponding to the second network element 518) for camping because it has been determined that the third cell is the only cell available for camping. Because the third cell was not included in the cell list 528 indicating cells that are available for providing multicast services while the UE 514 is in the inactive state, the UE 514 may determine that the third cell cannot provide multicast services while the UE 514 is in the inactive state. Thus, the UE 514 may determine that the UE 514 must establish a connection with the second network element 518 that corresponds to the third cell in order for the UE 514 to receive multicast data.

[0100] The second network element 518 (corresponding to the third cell) may transmit a downlink (DL) timing message 532. The DL timing message 532 may indicate the DL timing for the second network element 518. The UE 514 may identify the DL timing message 532 received from the second network element 518. The UE 514 may determine the DL timing for the second network element 518, and the UE 514 may utilize the DL timing to communicate with the second network element 518.

[0101] The UE 514 may perform an RRC resumption procedure 534 to establish a connection with the second network element 518. For example, the UE 514 and the second network element 518 may exchange transmissions during the RRC resumption procedure 534 to establish an RRC connection between the UE 514 and the second network element 518. The UE 514 may then utilize the RRC connection to receive multicast data.

[0102] While signaling chart 512 illustrates exemplary signals that may be exchanged by the UE and the network elements, it should be understood that in some embodiments, additional signals may be included or some of the signals may be omitted. For example, the signals may be part of a larger procedure that includes additional signals.

[0103] Example 2: Frequency List per MBS Session. The NW provides a frequency list per MBS session. For example, the NW may provide one or more frequency lists, each having a corresponding MBS session for which frequencies in the frequency list can provide multicast service while the UE is in an inactive state. FIG. 6 shows an exemplary cell selection configuration 600 with frequency lists, according to some embodiments. In particular, cell selection configuration 600 shows an example of Option 2, in which the network may provide a list of frequencies per multicast MBS session to indicate frequencies that support inactive multicast services for different multicast MBS sessions. In other embodiments, the list of frequencies per multicast MBS session may be replaced by a list of cells per multicast MBS session, and the list of cells may replace the list of frequencies in operation throughout this specification.

[0104] The cell selection configuration 600 shows an example location configuration 602 and an example signaling chart 612 for cell selection using a frequency list. The location configuration 602 in the illustrated embodiment shows a first cell area 604, a second cell area 606, and a third cell area 608. The first cell area 604 indicates an area that can be served by a first cell, the second cell area 606 indicates an area that can be served by a second cell, and the third cell area 608 indicates an area that can be served by a third cell. In the illustrated example, the first cell corresponding to the first cell area 604 can serve a first frequency, the second cell corresponding to the second cell area 606 can serve a second frequency, and the third cell corresponding to the third cell area 608 can serve a third frequency.

[0105] The location configuration 602 further shows an arrow 610 indicating movement of the UE within the area. As can be seen from the arrow 610, the UE starts within the first cell area 604. The UE moves from the first cell area 604 to areas within the first cell area 604, the second cell area 606, and the third cell area 608, as shown by the arrow 610. Based on the UE's movement shown by the arrow 610, the UE may determine that a reselection should be performed from being served by a first cell to being served by another cell based on movement toward an edge of the first cell area 604.

[0106] The signaling chart 612 may include a UE 614, a first network element 616 corresponding to a first cell, and a second network element 618 corresponding to a second cell. The UE 614 may correspond to a UE indicated by an arrow 610 in the location configuration 602. The first cell of the first network element 616 may correspond to a first cell area 604, where the first cell serves the first cell area 604. The second cell of the second network element 618 may correspond to a second cell area 606, where the second cell serves the second cell area 606. The UE 614 may include one or more of the features of the UE 1400 (FIG. 14). The first network element 616 and the second network element 618 may each include one or more of the features of the gNB 1500 (FIG. 15).

[0107] At the start of the signaling chart 612, the UE 614 may be in a connected state, as indicated by connection 620. In particular, the UE 614 may be connected to the first network element 616 based on the UE 614 being located within the first cell area 604 at the start of the signaling chart 612.

[0108] The first network element 616 may send an RRC release with suspend configuration message 622 to the UE 614 to transition the UE 614 to an inactive state. The first network element 616 may, in some embodiments, send the RRC release with suspend configuration message 622 based on the UE 614 moving toward an edge of the first cell area 604. In some embodiments, the first network element 616 may send the RRC release with suspend configuration message 622 based on a condition being met for transitioning the UE 614 to an inactive state, such as no transmissions being transmitted between the UE 614 and the first network element 616.

[0109] The RRC release with suspend configuration message 622 may include a first frequency list 624 corresponding to multicast MBS session #X and a second frequency list 626 corresponding to multicast MBS session #Y. The first frequency list 624 may indicate one or more frequencies that can provide multicast service for multicast MBS session #X when the UE 614 is in an inactive state. The second frequency list 626 may indicate one or more frequencies that can provide multicast service for multicast MBS session #Y when the UE 614 is in an inactive state. In the illustrated example, the first frequency list 624 indicates that the first and second frequencies can provide multicast service to the UE 614 for multicast MBS session #X while the UE 614 is in an inactive state. Furthermore, in the illustrated example, the second frequency list 626 indicates that the third and fourth frequencies can provide multicast service to the UE 614 for multicast MBS session #Y while the UE 614 is in an inactive state.

[0110] The UE 614 may receive the RRC Release with Suspend Configuration message 622 and may identify the RRC Release with Suspend Configuration message 622. The UE 614 may further identify a first frequency list 624 and a second frequency list 626 in the RRC Release with Suspend Configuration message 622. The UE 614 may determine, for each multicast MBS session, which frequencies and / or network elements can provide multicast service to the UE 614 while the UE 614 is in an inactive state. In the illustrated example, the UE 614 may determine, based on the first frequency list 624, that a first frequency (supported by the first network element 616) and a second frequency (supported by the second network element 618) can provide multicast service to the UE 614 for multicast MBS session #X when the UE 614 is in an inactive state. Further, the UE 614 may determine that the third frequency and the fourth frequency can provide multicast service to the UE 614 for multicast MBS session #Y while the UE 614 is in an inactive state based on the second frequency list 626. The UE 614 may store an indication of the frequency for each multicast MBS session that can provide multicast service to the UE 614 when the UE 614 is in an inactive state. In some embodiments, the UE 614 may store an indication of the frequency for a multicast MBS session for which the UE 614 is configured. In the illustrated embodiment, the UE 614 may be configured for multicast MBS session #X and may store an indication of the frequency for multicast MBS session #X.

[0111] The UE 614 may determine that the UE 614 should transition to an inactive state based on the RRC release with suspend configuration message 622. The UE 614 may transition to an inactive state, as indicated by inactive 628.

[0112] The UE 614 may perform a cell reselection procedure 630 while in an inactive state. The UE 614 may perform the cell reselection procedure 630 based on conditions for cell reselection being met, such as the quality of service provided by the current cell and / or the signal strength of a signal provided by the current cell being below a threshold level. In the illustrated example, the UE 614 may perform the cell reselection procedure 630 when the UE 614 is located in an area located within the first cell area 604, the second cell area 606, and the third cell area 608.

[0113] The UE 614 may use information from the first frequency list 624 and / or the second frequency list 626 to select a cell to camp on. For example, the UE 614 may determine that the UE 614 is configured for session #X. The UE 614 may determine to use a stored indication that the first frequency and the second frequency can provide multicast service to the UE 614 for session #X when the UE 614 is in an inactive state. The UE 614 may prioritize selecting a network element that provides the frequencies indicated in the first frequency list 624 for reselection. In the illustrated example, the UE 614 may prioritize selecting a network element that provides the first frequency and the second frequency over network elements that provide other frequencies based on the first frequency list 624.

[0114] The UE 614 may determine which frequencies are available for selection during the cell reselection procedure 630. In the illustrated example, when the UE 614 is located in an area located within the first cell area 604, the second cell area 606, and the third cell area 608, the UE 614 may determine that a first frequency, a second frequency, and a third frequency are available. The UE 614 may also, in some embodiments, determine signal qualities corresponding to the available frequencies. Because the UE 614 is performing reselection from a first cell providing the first frequency (possibly based on the signal quality of the first cell being below a threshold quality), the UE 614 may decide not to select the first cell. The UE 614 may still have the opportunity to select a second cell providing the second frequency or a third cell providing the third frequency. Because the second frequency is indicated in the first frequency list 624 corresponding to multicast MBS session #X, in the illustrated embodiment, the UE 614 may determine to prioritize the second cell providing the second frequency over the third cell providing the third frequency. Based on the prioritization, the UE 614 may select the second cell to camp on as a result of a cell reselection procedure 630.

[0115] The second network element 618 (corresponding to the second cell) may transmit a broadcast message 632. The broadcast message 632 may include an indication of an inactive multicast configuration to be utilized to process the multicast transmissions of the multicast MBS session #X transmitted by the second network element 618. Based on the UE 614 selecting to camp on the second cell, the UE 614 may receive and process the broadcast message 632. Based on the broadcast message 632, the UE 614 may be configured with an inactive multicast configuration to process the multicast transmissions of the multicast MBS session #X transmitted by the second network element 618.

[0116] The second network element 618 can transmit multicast data 634. The multicast data 634 may correspond to MBS session #X. The UE 614 can receive the multicast data 634 while the UE 614 is in an inactive state. Furthermore, the UE 614 can utilize the inactive multicast configuration from the broadcast message 632 to process the multicast data 634. Thus, the UE 614 can receive and process the multicast data while in an inactive state that was not available with the legacy approach.

[0117] While signaling chart 612 illustrates exemplary signals that may be exchanged by the UE and the network elements, it should be understood that in some embodiments, additional signals may be included or some of the signals may be omitted. For example, the signals may be part of a larger procedure that includes additional signals.

[0118] 7 illustrates an exemplary cell selection configuration 700 with a frequency list, according to some embodiments. In particular, cell selection configuration 700 illustrates an example of Option 2, in which the network may provide a list of frequencies per multicast MBS session to indicate frequencies that support inactive multicast services for different multicast MBS sessions. In other embodiments, the list of frequencies per multicast MBS session may be replaced by a list of cells per multicast MBS session, and the list of cells may replace the list of frequencies in operation throughout this specification.

[0119] The cell selection configuration 700 illustrates an example location configuration 702 and an example signaling chart 712 for cell selection using a frequency list. The location configuration 702 in the illustrated embodiment illustrates a first cell area 704, a second cell area 706, and a third cell area 708. The first cell area 704 indicates an area serviceable by a first cell, the second cell area 706 indicates an area serviceable by a second cell, and the third cell area 708 indicates an area serviceable by a third cell. In the illustrated example, the first cell corresponding to the first cell area 704 can serve a first frequency, the second cell corresponding to the second cell area 706 can serve a second frequency, and the third cell corresponding to the third cell area 708 can serve a third frequency. Furthermore, the first cell corresponding to the first cell area 704 and the second cell corresponding to the second cell area 706 may support multicast MBS session #X. A third cell corresponding to the third cell area 708 may correspond to multicast MBS session #Y.

[0120] The location configuration 702 further shows an arrow 710 indicating movement of the UE within the area. As can be seen from the arrow 710, the UE starts within the first cell area 704. The UE moves from the first cell area 704 to areas within the first cell area 704 and third cell area 708, as shown by the arrow 710. As can be seen from the arrow 710, the UE does not move into the second cell area 706. Based on the UE's movement shown by the arrow 710, the UE may determine that a reselection should be performed from being served by a first cell to being served by another cell based on movement toward an edge of the first cell area 704.

[0121] The signaling chart 712 may include a UE 714, a first network element 716 corresponding to a first cell, and a second network element 718 corresponding to a third cell. The UE 714 may correspond to a UE indicated by arrow 710 in the location configuration 702. The first cell of the first network element 716 may correspond to a first cell area 704, where the first cell serves the first cell area 704. The third cell of the second network element 718 may correspond to a third cell area 708, where the third cell serves the third cell area 708. The UE 714 may include one or more of the features of the UE 1400 (FIG. 14). The first network element 716 and the second network element 718 may each include one or more of the features of the gNB 1500 (FIG. 15).

[0122] At the start of the signaling chart 712, the UE 714 may be in a connected state, as indicated by connection 720. In particular, the UE 714 may be connected to a first network element 716 based on the UE 714 being located within a first cell area 704 at the start of the signaling chart 712.

[0123] The first network element 716 may send an RRC release with suspend configuration message 722 to the UE 714 to transition the UE 714 to an inactive state. The first network element 716 may, in some embodiments, send the RRC release with suspend configuration message 722 based on the UE 714 moving toward an edge of the first cell area 704. In some embodiments, the first network element 716 may send the RRC release with suspend configuration message 722 based on a condition being met for transitioning the UE 714 to an inactive state, such as no transmissions being transmitted between the UE 714 and the first network element 716.

[0124] The RRC release with suspend configuration message 722 may include an indication to enable multicast reception in the inactive state. In particular, the indication to enable multicast reception may indicate to the UE 714 that multicast reception should be enabled for the UE 714 when the UE 714 is in the inactive state.

[0125] The UE 714 may receive the RRC Release with Suspend Configuration message 722 and may identify the RRC Release with Suspend Configuration message 722. The UE 714 may further identify an indication that multicast reception should be enabled for the UE 714 when the UE 714 is in an inactive state. In some embodiments, the UE 714 may be configured with a configuration for handling multicast transmissions when in an inactive state. The configuration may have been previously received by the UE 714.

[0126] The UE 714 may determine that the UE 714 should transition to an inactive state based on the RRC release with suspend configuration message 722. The UE 714 may transition to an inactive state, as indicated by inactive 724.

[0127] The first network element 716 may transmit a broadcast message 726. The first network element 716 may broadcast the broadcast message 726. The broadcast message 726 may include a first frequency list 728 corresponding to multicast MBS session #X and a second frequency list 730 corresponding to multicast MBS session #Y. The first frequency list 728 may indicate one or more frequencies that can provide multicast service for multicast MBS session #X when the UE 714 is in an inactive state. The second frequency list 730 may indicate one or more frequencies that can provide multicast service for multicast MBS session #Y when the UE 714 is in an inactive state. In the illustrated example, the first frequency list 728 indicates that the first frequency and the second frequency can provide multicast service to the UE 714 for multicast MBS session #X while the UE 714 is in an inactive state. Further, in the illustrated example, the second frequency list 730 indicates that the third and fourth frequencies can provide multicast service to the UE 714 for multicast MBS session #Y while the UE 714 is in an inactive state.

[0128] The UE 714 may receive the broadcast message 726 and identify the broadcast message 726. The UE 714 may further identify a first frequency list 728 and a second frequency list 730 in the broadcast message 726. The UE 714 may determine, for each multicast MBS session, which frequencies and / or network elements can provide multicast service to the UE 714 while the UE 714 is in an inactive state. In the illustrated example, the UE 714 may determine, based on the first frequency list 728, that a first frequency (supported by the first network element 716) and a second frequency (supported by the second network element 718) can provide multicast service to the UE 714 for multicast MBS session #X when the UE 714 is in an inactive state. Furthermore, the UE 714 may determine that the third frequency and the fourth frequency can provide multicast service to the UE 714 for multicast MBS session #Y when the UE 714 is in an inactive state based on the second frequency list 730. The UE 714 may store an indication of the frequency for each multicast MBS session that can provide multicast service to the UE 714 when the UE 714 is in an inactive state. In some embodiments, the UE 714 may store an indication of the frequency for a multicast MBS session for which the UE 714 is configured. In the illustrated embodiment, the UE 714 may be configured for multicast MBS session #X and may store an indication of the frequency for multicast MBS session #X.

[0129] The UE 714 may perform a cell reselection procedure 732 while in an inactive state. The UE 714 may perform the cell reselection procedure 732 based on conditions for cell reselection being met, such as the quality of service provided by the current cell and / or the signal strength of the signal provided by the current cell being below a threshold level. In the illustrated example, the UE 714 may perform the cell reselection procedure 732 when the UE 714 is located within the first cell area 704 and the third cell area 708.

[0130] The UE 714 may use information from the first frequency list 728 and / or the second frequency list 730 to select a cell to camp on. For example, the UE 714 may determine that the UE 714 is configured for session #X. The UE 714 may use a stored indication that the first frequency and the second frequency can provide multicast service to the UE 714 for session #X when the UE 714 is in an inactive state. The UE 714 may prioritize selecting a network element that provides the frequencies indicated in the first frequency list 728 for reselection. In the illustrated example, the UE 714 may prioritize selecting a network element that provides the first frequency and the second frequency over network elements that provide other frequencies based on the first frequency list 728.

[0131] The UE 714 may determine which frequencies are available for selection during the cell reselection procedure 732. In the illustrated example, when the UE 714 is located in an area located within the first cell area 704 and the third cell area 708, the UE 714 may determine that the first frequency and the third frequency are available. The UE 714 may also, in some embodiments, determine signal qualities corresponding to the available frequencies. Because the UE 714 is performing reselection from the first cell providing the first frequency (possibly based on the signal quality of the first cell being below a threshold quality), the UE 714 may decide not to select the first cell. The UE 614 may still have the opportunity to select a third cell providing the third frequency. Because the third cell was not included in the first frequency list 728 indicating cells available for providing multicast service for multicast MBS session #X while the UE 714 was in the inactive state, the UE 714 may determine that the third cell cannot provide multicast service while the UE 714 is in the inactive state. Thus, the UE 714 may determine that the UE 714 must establish a connection with the second network element 718 corresponding to the third cell to receive multicast data for multicast MBS session #X.

[0132] The second network element 718 (corresponding to the third cell) may transmit a DL timing message 734. The DL timing message 734 may indicate the DL timing for the second network element 718. The UE 714 may identify the DL timing message 734 received from the second network element 718. The UE 714 may determine the DL timing for the second network element 718, and the UE 714 may utilize the DL timing to communicate with the second network element 718.

[0133] The UE 714 may perform an RRC resumption procedure 736 to establish a connection with the second network element 718. For example, the UE 714 and the second network element 718 may exchange transmissions during the RRC resumption procedure 736 to establish an RRC connection between the UE 714 and the second network element 718. The UE 714 may then utilize the RRC connection to receive multicast data.

[0134] While signaling chart 712 illustrates exemplary signals that may be exchanged by the UE and the network elements, it should be understood that in some embodiments, additional signals may be included or some of the signals may be omitted. For example, the signals may be part of a larger procedure that includes additional signals.

[0135] Example 3: Cell List Per RRC State. The NW provides a cell list per RRC state. For example, the NW may provide one or more cell lists, each having a corresponding state of UEs for which cells in the cell list can provide multicast service. Figure 8 shows an example cell selection configuration 800 with cell lists, according to some embodiments. In particular, cell selection configuration 800 shows an example of Option 3 in which the network may provide two lists of cells, one list corresponding to an inactive state and one list corresponding to a connected state. In other embodiments, the list of cells for each of the states may be replaced by a list of frequencies for each of the states, where the list of frequencies may replace the list of active cells throughout this specification.

[0136] The cell selection configuration 800 shows an example location configuration 802 and an example signaling chart 812 for cell selection using a cell list. The location configuration 802 in the illustrated embodiment shows a first cell area 804, a second cell area 806, and a third cell area 808. The first cell area 804 indicates an area that can be served by a first cell, the second cell area 806 indicates an area that can be served by a second cell, and the third cell area 808 indicates an area that can be served by a third cell. The first cell corresponding to the first cell area 804 and the second cell corresponding to the second cell area 806 can provide multicast service when the UE is in an inactive state. The third cell corresponding to the third cell area 808 can provide multicast service when the UE is in a connected state.

[0137] The location configuration 802 further shows an arrow 810 indicating movement of the UE within the area. As can be seen from the arrow 810, the UE starts within a first cell area 804. The UE moves from the first cell area 804 to areas within the first cell area 804, the second cell area 806, and the third cell area 808, as shown by the arrow 810. Based on the UE's movement shown by the arrow 810, the UE may determine that a reselection should be performed from being served by a first cell to being served by another cell based on movement toward an edge of the first cell area 804.

[0138] The signaling chart 812 may include a UE 814, a first network element 816 corresponding to a first cell, and a second network element 818 corresponding to a second cell. The UE 814 may correspond to a UE indicated by arrow 810 in the location configuration 802. The first cell of the first network element 816 may correspond to a first cell area 804, where the first cell serves the first cell area 804. The second cell of the second network element 818 may correspond to a second cell area 806, where the second cell serves the second cell area 806. The UE 814 may include one or more of the features of the UE 1400 (FIG. 14). The first network element 816 and the second network element 818 may each include one or more of the features of the gNB 1500 (FIG. 15).

[0139] At the start of the signaling chart 812, the UE 814 may be in a connected state, as indicated by connection 820. In particular, the UE 814 may be connected to the first network element 816 based on the UE 814 being located within the first cell area 804 at the start of the signaling chart 812.

[0140] The first network element 816 may send an RRC release with suspend configuration message 822 to the UE 814 to transition the UE 814 to an inactive state. The first network element 816 may, in some embodiments, send the RRC release with suspend configuration message 822 based on the UE 814 moving toward an edge of the first cell area 804. In some embodiments, the first network element 816 may send the RRC release with suspend configuration message 822 based on a condition being met for transitioning the UE 814 to an inactive state, such as no transmissions being transmitted between the UE 814 and the first network element 816.

[0141] The RRC release 822 with suspend configuration message may include a first cell list 824 corresponding to an inactive state and a second cell list 826 corresponding to a connected state. The first cell list 824 may indicate one or more cells that can provide multicast service to the UE 814 when the UE 814 is in the inactive state. The second cell list 826 may indicate one or more cells that can provide multicast service to the UE 814 when the UE 814 is in the connected state. In the illustrated example, the first cell list 824 indicates that the first cell and the second cell can provide multicast service to the UE 814 while the UE 814 is in the inactive state. Furthermore, in the illustrated example, the second cell list 826 indicates that a third cell can provide multicast service to the UE 814 when the UE 814 is in the connected state. The RRC release 822 with suspend configuration message may further indicate a priority state 830 of the UE 814 for receiving multicast data. In the illustrated example, the priority state 830 may indicate that an inactive state of the UE 814 is prioritized over other states, including a connected state.

[0142] The UE 814 may receive the RRC release with suspend configuration message 822 and may identify the RRC release with suspend configuration message 822. The UE 814 may further identify a first cell list 824, a second cell list 826, and a priority state 830 for the RRC release with suspend configuration message 822. The UE 814 may store an indication of cells capable of providing multicast service in an inactive state, an indication of cells capable of providing multicast service in a connected state, and / or an indication of the priority state 830.

[0143] The UE 814 may determine that the UE 814 should transition to an inactive state based on the RRC release with suspend configuration message 822. The UE 814 may transition to an inactive state, as indicated by inactive 832.

[0144] The UE 814 may perform a cell reselection procedure 834 while in an inactive state. The UE 814 may perform the cell reselection procedure 834 based on conditions for cell reselection being met, such as the quality of service provided by the current cell and / or the signal strength of the signal provided by the current cell being below a threshold level. In the illustrated example, the UE 814 may perform the cell reselection procedure 834 when the UE 814 is located in an area located within the first cell area 804, the second cell area 806, and the third cell area 808.

[0145] The UE 814 may utilize information from the first cell list 824, the second cell list 826, and / or the priority state 830 to select a cell to camp on. For example, the UE 814 may determine, based on the priority state 830, that receiving multicast data should be prioritized while the UE 814 is in an inactive state. Furthermore, the UE 814 may determine, based on the first cell and the second cell included in the first cell list 824, that the first cell and the second cell should be prioritized because the first cell list 824 corresponds to the inactive state.

[0146] The UE 814 may determine which cells are available for selection during the cell reselection procedure 834. In the illustrated example, when the UE 814 is located in an area located within the first cell area 804, the second cell area 806, and the third cell area 808, the UE 814 may determine that the first cell, the second cell, and the third cell are available. The UE 814 may also, in some embodiments, determine signal qualities corresponding to the available cells. Because the UE 814 is performing reselection from the first cell (possibly based on the signal quality of the first cell being below a threshold quality), the UE 814 may decide not to select the first cell. The UE 814 may still have the opportunity to select the second cell or the third cell. Because the inactive state is indicated as preferred by the priority state 830 and the second cell is indicated in the first cell list 824 corresponding to the inactive state, the UE 814 may determine, in the illustrated example, to prioritize the second cell that provides multicast services when the UE 814 is in the inactive state over the third cell that provides multicast services when the UE 814 is in the connected state. Based on the prioritization, the UE 814 may select the second cell to camp on as a result of the cell reselection procedure 834.

[0147] The second network element 818 (corresponding to the second cell) may transmit a broadcast message 836. The broadcast message 836 may include an indication of an inactive multicast configuration to be utilized to process the multicast transmissions of the multicast MBS session #X transmitted by the second network element 818. Based on the UE 814 selecting to camp on the second cell, the UE 814 may receive and process the broadcast message 836. Based on the broadcast message 836, the UE 814 may be configured with an inactive multicast configuration to process the multicast transmissions of the multicast MBS session #X transmitted by the second network element 818.

[0148] The second network element 818 can transmit multicast data 838. The multicast data 838 may correspond to MBS session #X. The UE 814 can receive the multicast data 838 while the UE 814 is in an inactive state. Furthermore, the UE 814 can utilize the inactive multicast configuration from the broadcast message 836 to process the multicast data 838. Thus, the UE 814 can receive and process the multicast data while in an inactive state that was not available with the legacy approach.

[0149] While signaling chart 812 illustrates exemplary signals that may be exchanged by the UE and the network elements, it should be understood that in some embodiments, additional signals may be included or some of the signals may be omitted. For example, the signals may be part of a larger procedure that includes additional signals.

[0150] 9 shows an example cell selection configuration 900 with a cell list, according to some embodiments. In particular, cell selection configuration 900 shows an example of Option 3 in which the network can provide two lists of cells, one list corresponding to an inactive state and one list corresponding to a connected state. In other embodiments, the list of cells for each of the states may be replaced by a list of frequencies for each of the states, where the list of frequencies may replace the list of active cells throughout this specification.

[0151] The cell selection configuration 900 shows an example location configuration 902 and an example signaling chart 912 for cell selection using a cell list. The location configuration 902 in the illustrated embodiment shows a first cell area 904, a second cell area 906, and a third cell area 908. The first cell area 904 indicates an area that can be served by a first cell, the second cell area 906 indicates an area that can be served by a second cell, and the third cell area 908 indicates an area that can be served by a third cell. The first cell corresponding to the first cell area 904 and the second cell corresponding to the second cell area 906 can provide multicast service when the UE is in an inactive state. The third cell corresponding to the third cell area 908 can provide multicast service when the UE is in a connected state.

[0152] The location configuration 902 further shows an arrow 910 indicating movement of the UE within the area. As can be seen from the arrow 910, the UE starts within a first cell area 904. The UE moves from the first cell area 904 to areas within the first cell area 904, the second cell area 906, and the third cell area 908, as indicated by the arrow 910. Based on the UE's movement indicated by the arrow 910, the UE may determine that a reselection should be performed from being served by a first cell to being served by another cell based on movement toward an edge of the first cell area 904.

[0153] The signaling chart 912 may include a UE 914, a first network element 916 corresponding to a first cell, and a second network element 918 corresponding to a third cell. The UE 914 may correspond to a UE indicated by arrow 910 in the location configuration 902. The first cell of the first network element 916 may correspond to a first cell area 904, where the first cell serves the first cell area 904. The third cell of the second network element 918 may correspond to a third cell area 908, where the third cell serves the third cell area 908. The UE 914 may include one or more of the features of the UE 1400 (FIG. 14). The first network element 916 and the second network element 918 may each include one or more of the features of the gNB 1500 (FIG. 15).

[0154] At the start of signaling chart 912, UE 914 may be in a connected state, as indicated by connection 920. In particular, UE 914 may be connected to a first network element 916 based on UE 914 being located within a first cell area 904 at the start of signaling chart 912.

[0155] The first network element 916 may send an RRC release with suspend configuration message 922 to the UE 914 to transition the UE 914 to an inactive state. The first network element 916, in some embodiments, may send the RRC release with suspend configuration message 922 based on the UE 914 moving toward an edge of the first cell area 904. In some embodiments, the first network element 916 may send the RRC release with suspend configuration message 922 based on a condition being met for transitioning the UE 914 to an inactive state, such as no transmissions being transmitted between the UE 914 and the first network element 916.

[0156] The RRC release with suspend configuration message 922 may include a first cell list 924 corresponding to an inactive state and a second cell list 926 corresponding to a connected state. The first cell list 924 may indicate one or more cells that can provide multicast service to the UE 914 when the UE 914 is in the inactive state. The second cell list 926 may indicate one or more cells that can provide multicast service to the UE 914 when the UE 914 is in the connected state. In the illustrated example, the first cell list 924 indicates that the first cell and the second cell can provide multicast service to the UE 914 while the UE 914 is in the inactive state. Furthermore, in the illustrated example, the second cell list 926 indicates that a third cell can provide multicast service to the UE 914 while the UE 914 is in the connected state. The RRC release with suspend configuration message 922 may further indicate a priority state 928 of the UE 914 for receiving multicast data. In the illustrated example, the priority state 928 may indicate that the connected state of the UE 914 is prioritized over other states, including an inactive state.

[0157] The UE 914 may receive the RRC release with suspend configuration message 922 and may identify the RRC release with suspend configuration message 922. The UE 914 may further identify a first cell list 924, a second cell list 926, and a priority state 928 for the RRC release with suspend configuration message 922. The UE 914 may store an indication of cells capable of providing multicast service in an inactive state, an indication of cells capable of providing multicast service in a connected state, and / or an indication of the priority state 928.

[0158] The UE 914 may determine that the UE 914 should transition to an inactive state based on the RRC release with suspend configuration message 922. The UE 914 may transition to an inactive state, as indicated by inactive 930.

[0159] The UE 914 may perform a cell reselection procedure 932 while in an inactive state. The UE 914 may perform the cell reselection procedure 932 based on conditions for cell reselection being met, such as the quality of service provided by the current cell and / or the signal strength of a signal provided by the current cell being below a threshold level. In the illustrated example, the UE 914 may perform the cell reselection procedure 932 when the UE 914 is located in an area located within the first cell area 904, the second cell area 906, and the third cell area 908.

[0160] The UE 914 may use information from the first cell list 924, the second cell list 926, and / or the priority state 928 to select a cell to camp on. For example, the UE 914 may determine that receiving multicast data should be prioritized while the UE 914 is in a connected state based on the priority state 928. Furthermore, the UE 914 may determine that a third cell should be prioritized based on the third cell being included in the second cell list 926 because the second cell list 926 corresponds to the connected state.

[0161] The UE 914 may determine which cells are available for selection during the cell reselection procedure 932. In the illustrated example, when the UE 914 is located in an area located within the first cell area 904, the second cell area 906, and the third cell area 908, the UE 914 may determine that the first cell, the second cell, and the third cell are available. The UE 914 may also, in some embodiments, determine signal qualities corresponding to the available cells. Because the UE 914 is performing reselection from the first cell (possibly based on the signal quality of the first cell being below a threshold quality), the UE 914 may decide not to select the first cell. The UE 914 may still have the opportunity to select the second cell or the third cell. Because the connected state is indicated as preferred by the priority state 928 and the third cell is indicated in the second cell list 926 corresponding to the connected state, the UE 914 may determine, in the illustrated example, to prioritize the third cell that provides multicast service when the UE 914 is in the connected state over the second cell that provides multicast service when the UE 914 is in the inactive state. Based on the prioritization, the UE 914 may select the third cell to camp on as a result of a cell reselection procedure 932.

[0162] The UE 914 may perform an RRC resumption procedure 934 to establish a connection with the second network element 918. For example, the UE 914 and the second network element 918 may exchange transmissions during the RRC resumption procedure 934 to establish an RRC connection between the UE 914 and the second network element 918. The UE 914 may then utilize the RRC connection to receive multicast data.

[0163] While signaling chart 912 illustrates exemplary signals that may be exchanged by the UE and the network elements, it should be understood that in some embodiments, additional signals may be included or some of the signals may be omitted. For example, the signals may be part of a larger procedure that includes additional signals.

[0164] Example 4: RRC release with redirection to a multicast carrier / cell. The NW is aware that the UE has a joint multicast MBS session. When the NW releases the UE, it can enable the RRC redirection function and redirect the UE to a frequency / cell with an INACTIVE multicast service. For example, the NW can indicate frequencies and / or cells that provide multicast service while the UE is in an inactive state, which can indicate that the UE should select an indication frequency and / or cell to camp on. Note: Reuse of RRCRelease by the redirection mechanism. The UE can maintain the prioritization configuration for a period of time (controlled by the redirection timer).

[0165] 10 illustrates an exemplary cell selection configuration 1000 with a frequency / cell list, according to some embodiments. In particular, the cell selection configuration 1000 illustrates an example in which the network may indicate a particular frequency and / or cell that the UE should select for camping. The particular frequency and / or cell may provide multicast services while the UE is in an inactive state.

[0166] The cell selection configuration 1000 shows an example location configuration 1002 and an example signaling chart 1012 for cell selection using a frequency / cell list. The location configuration 1002 in the illustrated embodiment shows a first cell area 1004, a second cell area 1006, and a third cell area 1008. The first cell area 1004 indicates an area that can be served by a first cell, the second cell area 1006 indicates an area that can be served by a second cell, and the third cell area 1008 indicates an area that can be served by a third cell.

[0167] The location configuration 1002 further shows an arrow 1010 indicating movement of the UE within the area. As can be seen from the arrow 1010, the UE starts within the first cell area 1004. The UE moves from the first cell area 1004 to areas within the first cell area 1004, the second cell area 1006, and the third cell area 1008, as indicated by the arrow 1010. Based on the UE's movement indicated by the arrow 1010, the UE may determine that a reselection should be performed from being served by a first cell to being served by another cell based on movement toward an edge of the first cell area 1004.

[0168] The signaling chart 1012 may include a UE 1014, a first network element 1016 corresponding to a first cell, and a second network element 1018 corresponding to a second cell. The UE 1014 may correspond to a UE indicated by arrow 1010 in the location configuration 1002. The first cell of the first network element 1016 may correspond to a first cell area 1004, where the first cell serves the first cell area 1004. The second cell of the second network element 1018 may correspond to a second cell area 1006, where the second cell serves the second cell area 1006. The UE 1014 may include one or more of the features of the UE 1400 (FIG. 14). The first network element 1016 and the second network element 1018 may each include one or more of the features of a gNB 1500 (FIG. 15).

[0169] At the start of the signaling chart 1012, the UE 1014 may be in a connected state, as indicated by connection 1020. In particular, the UE 1014 may be connected to the first network element 1016 based on the UE 1014 being located within the first cell area 1004 at the start of the signaling chart 1012.

[0170] The first network element 1016 may send an RRC release with suspend configuration message 1022 to the UE 1014 to transition the UE 1014 to an inactive state. The first network element 1016, in some embodiments, may send the RRC release with suspend configuration message 1022 based on the UE 1014 moving toward an edge of the first cell area 1004. In some embodiments, the first network element 1016 may send the RRC release with suspend configuration message 1022 based on a condition being met for transitioning the UE 1014 to an inactive state, such as no transmissions being transmitted between the UE 1014 and the first network element 1016.

[0171] The RRC release with suspend configuration message 1022 may include an indication of resources 1024 to which the UE 1014 is redirected in a subsequent cell reselection. The resources 1024 may be frequencies and / or cells that the UE 1014 should select for camping. In the illustrated embodiment, the resources 1024 may indicate that the UE 1014 should select a second frequency and second cell for camping, if available.

[0172] The UE 1014 may receive the RRC release with suspend configuration message 1022 and may identify the RRC release with suspend configuration message 1022. The UE 1014 may further identify an indication of the resources 1024. The UE 1014 may store the indication of the resources 1024. For example, the UE may store an indication of the second frequency and the second cell for cell selection.

[0173] The UE 1014 may determine that the UE 1014 should transition to an inactive state based on the RRC release with suspend configuration message 1022. The UE 1014 may transition to an inactive state, as indicated by inactive 1026.

[0174] The UE 1014 may perform a cell reselection procedure 1028 while in an inactive state. The UE 1014 may perform the cell reselection procedure 1028 based on conditions for cell reselection being met, such as the quality of service provided by the current cell and / or the signal strength of a signal provided by the current cell being below a threshold level. In the illustrated example, the UE 1014 may perform the cell reselection procedure 1028 when the UE 1014 is located within the first cell area 1004, the second cell area 1006, and the third cell area 1008.

[0175] The UE 1014 may use information from the resources 1024 to select a cell to camp on. For example, the UE 1014 may use a stored indication that the UE 1014 should select a second frequency and a second cell for camping, if available. The UE 1014 may prioritize the resources indicated by the resources 1024. In the illustrated example, the UE 1014 may prioritize the second frequency and the second cell.

[0176] The UE 1014 may determine which cells are available for selection during the cell reselection procedure 1028. In the illustrated example, when the UE 1014 is located in an area located within the first cell area 1004, the second cell area 1006, and the third cell area 1008, the UE 1014 may determine that the first cell, the second cell, and the third cell are available. The UE 1014 may also, in some embodiments, determine the signal quality of the available cells. Because the UE 1014 is performing reselection from the first cell (possibly based on the signal quality of the first cell being below a threshold quality), the UE 1014 may decide not to select the first cell. The UE 1014 may still have the opportunity to select the second cell or the third cell. Because the resources 1024 indicate that the second frequency and the second cell should be preferred, the UE 1014 may select the second cell to camp on.

[0177] The second network element 1018 may transmit a broadcast message 1030. The second network element 1018 may broadcast the broadcast message 1030. The broadcast message 1030 may include an indication of a multicast configuration. The multicast configuration may indicate a configuration for the UE 1014 to receive multicast data for multicast MBS session #X received from the second network element 1018 when the UE 1014 is in an inactive state.

[0178] The second network element 1018 (corresponding to the second cell) may transmit a broadcast message 1030. The broadcast message 1030 may include an indication of an inactive multicast configuration to be utilized to process the multicast transmissions transmitted by the second network element 1018. Based on the UE 1014 selecting to camp on the second cell, the UE 1014 may receive and process the broadcast message 1030. Based on the broadcast message 1030, the UE 1014 may be configured with an inactive multicast configuration to process the multicast transmissions transmitted by the second network element 1018.

[0179] The second network element 1018 can transmit multicast data 1032. The multicast data 1032 may correspond to MBS session #X. The UE 1014 can receive the multicast data 1032 while the UE 1014 is in an inactive state. Furthermore, the UE 1014 can utilize the inactive multicast configuration from the broadcast message 1030 to process the multicast data 1032. Thus, the UE 1014 can receive and process the multicast data while in an inactive state that was not available with the legacy approach.

[0180] While signaling chart 1012 illustrates exemplary signals that may be exchanged by the UE and the network elements, it should be understood that in some embodiments, additional signals may be included or some of the signals may be omitted. For example, the signals may be part of a larger procedure that includes additional signals.

[0181] 11 shows an example procedure 1100 for determining resources for a multicast transmission according to some embodiments. Procedure 1100 may be performed by a UE, such as UE 414 (FIG. 4), UE 514 (FIG. 5), UE 614 (FIG. 6), UE 714 (FIG. 7), UE 814 (FIG. 8), UE 914 (FIG. 9), UE 1014 (FIG. 10), and / or UE 1400 (FIG. 14). The UE may perform procedure 1100 to determine one or more resources for receiving a multicast transmission.

[0182] The procedure 1100 may include, at 1102, identifying an indication of one or more resources. For example, the UE may identify an indication of one or more resources that may provide multicast services while the UE is in an inactive state. In some embodiments, the indication of the one or more resources may indicate resources to which the UE is redirected.

[0183] In some embodiments, the indication of one or more resources may include a list of cells that can provide multicast service while the UE is in an inactive state. For example, the list of cells may include any of the cell lists described throughout this disclosure. In some of these embodiments, the list of cells may include a list of cells per RRC state.

[0184] In some embodiments, the indication of one or more resources may include a list of frequencies over which the multicast service can be provided while the UE is in an inactive state. For example, the list of frequencies may include any of the frequency lists described throughout this disclosure. In some of these embodiments, the list of frequencies may include a list of frequencies per MBS session.

[0185] The procedure 1100 may include, at 1104, determining available resources. For example, the UE may determine resources available for serving the UE. In embodiments where the indication of one or more resources indicates resources to which the UE is redirected, determining resources for receiving the multicast transmission may include determining that the resources to which the UE is to be redirected are resources for receiving the multicast transmission. In some embodiments, the resources available for serving the UE are determined as part of a handover from the first base station to the second base station.

[0186] The procedure 1100 may include determining resources for receiving the multicast transmission at 1106. For example, the UE may determine the resources for receiving the multicast transmission based on the indication of one or more resources and resources available for providing multicast service to the UE. In some embodiments, determining the resources for receiving the multicast transmission may include determining that the resources available for providing service to the UE do not include any of the one or more resources from the indication and determining the resources from the resources available for providing service to the UE.

[0187] The procedure 1100 may include initiating an RRC restart procedure at 1108. For example, the UE may initiate an RRC restart procedure to receive a multicast transmission. In embodiments where the resources available to serve the UE do not include any of the one or more resources from the indication, the UE may initiate the RRC restart procedure. In some embodiments, 1108 may be omitted. For example, when a resource is included in one or more resources from the indication, 1108 may be omitted.

[0188] The procedure 1100 may include, at 1110, identifying an indication of an inactive multicast configuration. For example, the UE may identify an indication of an inactive multicast configuration for receiving multicast transmissions. In some embodiments, 1110 may be omitted.

[0189] The procedure 1100 may include, at 1112, utilizing an inactive multicast configuration to process the multicast transmission. For example, the UE may utilize an inactive multicast configuration to process the multicast transmission received by the UE. In some embodiments, 1112 may be omitted.

[0190] 11, it should be understood that in other embodiments, the order of the operations may differ and / or one or more of the operations may be performed simultaneously. Furthermore, it should be understood that in other embodiments, one or more of the operations may be omitted and / or one or more additional operations may be included.

[0191] 12 shows another example procedure 1200 for determining resources for a multicast transmission according to some embodiments. Procedure 1200 may be performed by a UE, such as UE 414 (FIG. 4), UE 514 (FIG. 5), UE 614 (FIG. 6), UE 714 (FIG. 7), UE 814 (FIG. 8), UE 914 (FIG. 9), UE 1014 (FIG. 10), and / or UE 1400 (FIG. 14). The UE may perform procedure 1200 to determine one or more resources for receiving a multicast transmission.

[0192] The methodology 1200 may include initiating a handover procedure, at 1202. For example, the UE may initiate a handover procedure from a first cell to a second cell while the UE is in an inactive state.

[0193] The procedure 1200 may include, at 1204, determining a procedure for receiving multicast data. For example, the UE may determine a procedure for receiving the multicast service from the second cell based on an indication of one or more resources capable of providing the multicast service. The indication of the one or more resources may be received from the first cell. In some embodiments, the indication of the one or more resources may include an indication of one or more cells capable of providing the multicast service while the UE is in an inactive state. Further, in some embodiments, the indication of the one or more resources may include an indication of one or more frequencies capable of providing the multicast service while the UE is in an inactive state. In some embodiments, the procedure may further be determined based on an indication of a priority state for the UE when receiving the multicast data from the second cell, where the indication of the priority state may be received from the first cell.

[0194] In some embodiments, the indication of the one or more resources may include an indication of one or more resources that can provide multicast service while the UE is in an inactive state. In these embodiments, determining a procedure for receiving multicast data may include determining to implement an inactive multicast configuration for processing the received multicast data.

[0195] In some embodiments, the indication of the one or more resources may not include resources corresponding to the second cell. In some of these embodiments, determining a procedure for receiving the multicast data includes determining an RRC resumption procedure for receiving the multicast data based on the resource corresponding to the second cell not being included in the indication of the one or more resources.

[0196] In some embodiments, the indication of the one or more resources includes an indication that the UE should be in a connected state when receiving the multicast data from the second cell. In some of these embodiments, determining the procedure may include determining an RRC resumption procedure for receiving the multicast data based on the indication that the UE should be in a connected state when receiving the multicast data from the second cell.

[0197] The procedure 1200 may include initiating a procedure for receiving multicast data at 1206. For example, the UE may initiate the procedure determined at 1204 to process the multicast data received from the second cell.

[0198] In some embodiments, initiating the procedure may include implementing an inactive multicast configuration for processing the multicast data received from the second cell. For example, if it is determined in 1204 to implement an inactive multicast configuration, the inactive multicast configuration may be implemented.

[0199] In some embodiments, initiating the procedure may include initiating an RRC restart procedure for processing the multicast data. For example, if it is determined in 1204 that an RRC restart procedure is to be utilized, the RRC restart procedure may be initiated.

[0200] Procedure 1200 references a first cell and a second cell. It should be understood that the first cell and the second cell should be interpreted in accordance with the present disclosure. For example, the first cell may be served by a first base station, and the second cell may be served by a second base station. Thus, it should be understood that communications related to the first cell may be communicated via the first base station, and communications related to the second cell may be communicated via the second base station. In other embodiments, a base station may serve two or more cells, with both the first cell and the second cell being served by the same base station.

[0201] 12, it should be understood that in other embodiments, the order of the operations may differ and / or one or more of the operations may be performed simultaneously. Furthermore, it should be understood that in other embodiments, one or more of the operations may be omitted and / or one or more additional operations may be included.

[0202] 13 shows an example procedure 1300 for indicating resources for a multicast transmission according to some embodiments. The procedure 1300 may be performed by a base station, such as the first network element 416 (FIG. 4), the second network element 418 (FIG. 4), the first network element 516 (FIG. 5), the second network element 518 (FIG. 5), the first network element 616 (FIG. 6), the second network element 618 (FIG. 6), the first network element 716 (FIG. 7), the second network element 718 (FIG. 7), the first network element 816 (FIG. 8), the second network element 818 (FIG. 8), the first network element 916 (FIG. 9), the second network element 918 (FIG. 9), the first network element 1016 (FIG. 10), the second network element 1018 (FIG. 10), and / or the gNB 1500 (FIG. 15). A network element may perform the procedure 1300 to indicate one or more resources for receiving a multicast transmission.

[0203] The procedure 1300 may involve determining to transition a UE to an inactive state, at 1302. For example, a base station may determine to transition a UE coupled to the base station to an inactive state.

[0204] The procedure 1300 may include, at 1304, determining one or more resources over which the multicast service can be provided. For example, the base station may determine one or more resources over which the multicast service can be provided to the UE. In some embodiments, determining the one or more resources may include determining one or more cells over which the multicast service can be provided to the UE while the UE is in an inactive state. Further, determining the one or more resources may include determining one or more frequencies over which the multicast service can be provided to the UE while the UE is in an inactive state.

[0205] The procedure 1300 may include determining a corresponding state of the UE for receiving multicast data from each of the one or more resources, at 1306. For example, the base station may determine a corresponding state of the UE for receiving multicast data from each of the one or more resources. In some embodiments, 1306 may be omitted.

[0206] The procedure 1300 may include, at 1308, generating an RRC release with suspend configuration message. For example, the base station may generate the RRC release with the suspend configuration message including an indication of one or more resources. The RRC release with suspend configuration message may include one or more of the features of the RRC release with suspend configuration message described throughout this disclosure. In some embodiments, the RRC release with suspend configuration message may further include an indication of a corresponding state of the UE to receive multicast data from each of the one or more resources.

[0207] The procedure 1300 may involve sending an RRC Release with Suspend Configuration message, at 1310. For example, the base station may send the RRC Release with Suspend Configuration message to the UE to transition the UE to an inactive state.

[0208] 13, it should be understood that in other embodiments, the order of the operations may differ and / or one or more of the operations may be performed simultaneously. Furthermore, it should be understood that in other embodiments, one or more of the operations may be omitted and / or one or more additional operations may be included.

[0209] 14 illustrates an exemplary UE 1400 according to some embodiments. The UE 1400 may be any mobile or non-IoT device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a barometric pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, an actuator, etc.), a video surveillance / monitoring device (e.g., a camera, a video camera, etc.), a wearable device (e.g., a smart watch), a relaxed mobile computing device, etc. In some embodiments, the UE 1400 may be a RedCap UE or an NR-Light UE.

[0210] The UE 1400 may include a processor 1404, an RF interface circuit 1408, a memory / storage 1412, a user interface 1416, a sensor 1420, a driver circuit 1422, a power management integrated circuit (PMIC) 1424, an antenna structure 1426, and a battery 1428. The components of the UE 1400 may be implemented as an integrated circuit (IC), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof. The block diagram of FIG. 14 is intended to illustrate a high-level view of some of the components of the UE 1400. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other embodiments.

[0211] The components of the UE 1400 may be coupled to various other components via one or more interconnects 1432, which may represent any type of interface, input / output, bus (local, system, or extended), transmission line, trace, optical connection, etc., that allows various circuit components (on a common or different chips or chipsets) to interact with one another.

[0212] The processor 1404 may include processor circuitry such as, for example, a baseband processor circuit (BB) 1404A, a central processing unit circuit (CPU) 1404B, and a graphics processing unit circuit (GPU) 1404C. The processor 1404 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage 1412, to cause the UE 1400 to perform the operations described herein.

[0213] In some embodiments, the baseband processor circuit 1404A may access a communications protocol stack 1436 in the memory / storage 1412 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 1404A may access the communications protocol stack to perform user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers, and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and non-access layers. In some embodiments, PHY layer operations may additionally / alternatively be performed by components of the RF interface circuit 1408.

[0214] The baseband processor circuit 1404A may generate or process baseband signals or waveforms that carry information in a 3GPP-compliant network. In some embodiments, waveforms for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0215] The memory / storage 1412 may include one or more non-transitory computer-readable media (e.g., communication protocol stack 1436) that include instructions that may be executed by one or more of the processors 1404 to cause the UE 1400 to perform various operations described herein. The memory / storage 1412 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1400. In some embodiments, some of the memory / storage 1412 may be located on the processor 1404 itself (e.g., L1 and L2 cache), while other memory / storage 1412 may be external to the processor 1404 but accessible via a memory interface. The memory / storage 1412 may include, but is not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or other types of memory device technologies.

[0216] The RF interface circuitry 1408 may include transceiver circuitry and a radio frequency front end module (RFEM) that enable the UE 1400 to communicate with other devices over a radio access network. The RF interface circuitry 1408 may include various elements disposed in the transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, combiner circuits, control circuits, etc.

[0217] In the receive path, the RFEM may receive a radiated signal from the air interface via the antenna structure 1426 and proceed to filter and amplify the signal (using a low noise amplifier). The signal may be provided to a transceiver receiver that downconverts the RF signal to a baseband signal that is provided to a baseband processor of the processor 1404.

[0218] On the transmit path, the transmitter of the transceiver upconverts the baseband signal received from the baseband processor and provides an RF signal to the RFEM, which may amplify the RF signal through a power amplifier before the signal is radiated over the air interface via the antenna 1426.

[0219] In various embodiments, the RF interface circuitry 1408 may be configured to transmit and receive signals in accordance with NR access technologies.

[0220] The antenna 1426 may include antenna elements that convert electrical signals into radio waves that travel through the air and convert received radio waves into electrical signals. The antenna elements may be arranged in one or more antenna panels. The antenna 1426 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input, multiple-output communications. The antenna 1426 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. The antenna 1426 may have one or more panels designed for a specific frequency band, including bands in FR1 or FR2.

[0221] User interface circuitry 1416 includes various input / output (I / O) devices designed to enable user interaction with UE 1400. User interface 1416 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, including, among other things, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying or otherwise communicating information, such as sensor readings, actuator position(s), or other similar information. The output device circuitry may include any number or combination of audio or visual displays, including, among other things, one or more simple visual outputs / indicators (e.g., binary status indicators such as light emitting diodes "LEDs" and multi-character visual outputs, or more complex outputs such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), and output of characters, graphics, multimedia objects, etc. generated or produced from operation of the UE 1400.

[0222] Sensors 1420 may include devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others, inertial measurement units including accelerometers, gyroscopes, or magnetometers, microelectromechanical or nanoelectromechanical systems including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers, level sensors, flow sensors, temperature sensors (e.g., thermistors), pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless iris); light detection and ranging sensors, proximity sensors (e.g., infrared detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers, microphones or other similar audio capture devices, etc.

[0223] The driver circuitry 1422 may include software and hardware elements that operate to control particular devices embedded in, attached to, or otherwise communicatively coupled to the UE 1400. The driver circuitry 1422 may include individual drivers that enable other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 1400. For example, the driver circuitry 1422 may include a display driver that controls and enables access to a display device, a touchscreen driver that controls and enables access to a touchscreen interface, a sensor driver that obtains sensor readings of the sensor circuitry 1420 and controls and enables access to the sensor circuitry 1420, a driver that obtains actuator positions of or controls and enables access to electromechanical components, a camera driver that controls and enables access to an embedded image capture device, and an audio driver that controls and enables access to one or more audio devices.

[0224] The PMIC 1424 may manage the power supplied to various components of the UE 1400. In particular, with respect to the processor 1404, the PMIC 1424 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0225] In some embodiments, the PMIC 1424 may control or otherwise be a part of various power saving mechanisms of the UE 1400. For example, if the platform UE is in an RRC_Connected state, where it is still connected to a RAN node because it expects to receive traffic soon, after a period of inactivity, the platform UE may enter a state known as Discontinuous Reception Mode (DRX). While in this state, the UE 1400 may power down for short intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the UE 1400 may transition to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The UE 1400 enters a very low power state, periodically waking up to listen to the network, and then performing paging, where it powers down again. The UE 1400 may not be able to receive data in this state. To receive data, it must transition back to the original RRC_Connected state. In a further power saving mode, the device may be allowed to be unavailable from the network for a period longer than the paging interval (ranging from a few seconds to several hours). During this time, the device may be completely unable to reach the network and may be completely powered down. Any data transmitted during this time will be significantly delayed, but the delay is deemed acceptable.

[0226] The battery 1428 may provide power to the UE 1400, although in some examples the UE 1400 may be deployed and attached to a fixed location and may have a power source coupled to a power grid. The battery 1428 may 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 vehicle-based applications, the battery 1428 may be a typical automotive lead-acid battery.

[0227] 15 illustrates an exemplary gNB 1500 according to some embodiments. The gNB 1500 may include a processor 1504, an RF interface circuit 1508, a core network (CN) interface circuit 1512, a memory / storage circuit 1516, and an antenna structure 1526.

[0228] The components of the gNB 1500 may be coupled to various other components via one or more interconnects 1528.

[0229] The processor 1504, RF interface circuitry 1508, memory / storage circuitry 1516 (including communication protocol stack 1510), antenna structure 1526, and interconnect 1528 may be similar to the like-named elements shown and described with respect to FIG.

[0230] The CN interface circuit 1512 may provide connectivity to a core network, e.g., a fifth-generation core network (5GC), using a 5GC-compliant network interface protocol, such as a Carrier Ethernet protocol or some other suitable protocol. Network connectivity may be provided to or from the gNB 1500 via optical fiber or wireless backhaul. The CN interface circuit 1512 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1512 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0231] It is understood that use of personally identifiable information should comply with generally recognized privacy policies and practices that meet or exceed industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of permitted uses should be clearly indicated to users.

[0232] For one or more embodiments, at least one of the components depicted in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Example Section below. For example, the baseband circuitry described above in connection with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. As another example, circuitry associated with a UE, a base station, a network element, etc., as described above in connection with one or more of the foregoing figures, may be configured to operate according to one or more of the examples described below in the Example Section. Example

[0233] Further exemplary embodiments are provided in the following sections.

[0234] Example 1 may include a method of operating a user equipment (UE), the method including: identifying an indication of one or more resources that may provide multicast service while the UE is in an inactive state; determining resources available for providing the service to the UE; and determining resources for receiving a multicast transmission based on the indication of the one or more resources and the resources that are available for providing multicast service to the UE.

[0235] Example 2 may include the method of example 1, in which the indication of the one or more resources includes a list of cells that can provide the multicast service while the UE is in an inactive state.

[0236] Example 3 may include the method of example 2, in which the list of cells includes a list of cells for each radio resource control (RRC) state.

[0237] Example 4 may include the method of example 1, in which the indication of the one or more resources includes a list of frequencies that can provide the multicast service while the UE is in an inactive state.

[0238] Example 5 may include the method of example 4, in which the list of frequencies includes a list of frequencies for each multicast / broadcast service (MBS) session.

[0239] Example 6 may include the method of Example 1, in which the indication of the one or more resources indicates resources to which the UE is redirected, and determining resources for receiving the multicast transmission includes determining that the resources to which the UE is redirected are resources for receiving the multicast transmission.

[0240] Example 7 may include the method of example 1, wherein determining resources for receiving the multicast transmission includes determining that resources available for serving the UE do not include any of the one or more resources from the indication, and determining resources from the available resources for serving the UE, and the method further includes initiating a radio resource control (RRC) resumption procedure for receiving the multicast transmission.

[0241] Example 8 may include the method of Example 1, further including identifying an indication of an inactive multicast configuration for receiving the multicast transmission; and utilizing the inactive multicast configuration to process the received multicast transmission by the UE.

[0242] Example 9 may include the method of example 1, in which the resources available for serving the UE are determined as part of a handover from the first base station to the second base station.

[0243] Example 10 may include a method of operating a user equipment (UE), the method including initiating a handover procedure from a first cell to a second cell while the UE is in an inactive state; determining a procedure for receiving multicast data from the second cell based on an indication of one or more resources capable of providing multicast service, the indication of the one or more resources having been received from the first cell; and initiating a procedure for processing the multicast data received from the second cell.

[0244] Example 11 may include the method of Example 10, wherein the indication of the one or more resources includes an indication of one or more resources that can provide a multicast service while the UE is in an inactive state, and determining a procedure for receiving multicast data includes determining to implement an inactive multicast configuration for processing the received multicast data, and initiating the procedure includes implementing an inactive multicast configuration for processing the multicast data received from the second cell.

[0245] Example 12 may include the method of Example 10, wherein the indication of the one or more resources does not include resources corresponding to the second cell, and determining a procedure for receiving the multicast data includes determining a radio resource control (RRC) resumption procedure for receiving the multicast data based on resources corresponding to the second cell that are not included in the indication of the one or more resources, and initiating the procedure includes initiating an RRC resumption procedure for processing the multicast data received from the second cell.

[0246] Example 13 may include the method of Example 10, wherein the indication of the one or more resources includes an indication that the UE will be in a connected state when receiving the multicast data from the second cell, and determining the procedure includes determining a radio resource control (RRC) resumption procedure for receiving the multicast data based on the indication that the UE will be in a connected state when receiving the multicast data from the second cell, and initiating the procedure includes initiating an RRC resumption procedure for processing the multicast data received from the second cell.

[0247] Example 14 may include the method of Example 10, wherein the indication of the one or more resources includes an indication of one or more cells that can provide the multicast service while the UE is in an inactive state.

[0248] Example 15 may include the method of Example 10, wherein the indication of the one or more resources includes an indication of one or more frequencies that can provide the multicast service while the UE is in an inactive state.

[0249] Example 16 may include the method of Example 10, wherein the procedure is further determined based on an indication of a priority status for the UE when receiving multicast data from the second cell, and the indication of the priority status is received from the first cell.

[0250] Example 17 may include a method of operating a base station, the method including: determining to transition a user equipment (UE) coupled to the base station to an inactive state; determining one or more resources capable of providing multicast service to the UE; generating a radio resource control (RRC) release with a suspend configuration message including an indication of the one or more resources; and sending the RRC release with the suspend configuration message to the UE to transition the UE to the inactive state.

[0251] Example 18 may include the method of Example 17, wherein determining the one or more resources includes determining one or more cells that can provide a multicast service to the UE while the UE is in an inactive state.

[0252] Example 19 may include the method of Example 17, wherein determining the one or more resources includes determining one or more frequencies on which the multicast service can be provided to the UE while the UE is in an inactive state.

[0253] Example 20 may include the method of Example 17, further including determining a corresponding state of the UE for receiving multicast data from each of the one or more resources, and the RRC release with suspend configuration message further includes an indication of a corresponding state of the UE for receiving multicast data from each of the one or more resources.

[0254] Example 21 may include an apparatus including means for performing one or more elements of the method described or related to any of Examples 1 to 20, or any other method or process described herein.

[0255] Example 22 may include one or more non-transitory computer-readable media containing instructions that, in response to execution of the instructions by one or more processors of the electronic device, cause an electronic device to perform one or more elements of a method described in or related to any of Examples 1-20, or any other method or process described herein.

[0256] Example 23 may include an apparatus including logic, modules, or circuitry for performing one or more elements of a method described or related to any of Examples 1 to 20, or any other method or process described herein.

[0257] Example 24 may include any method, technique, or process described in or related to any of Examples 1-20, or any part or portion thereof.

[0258] Example 25 may include an apparatus comprising one or more processors and one or more computer-readable media having instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in connection with any or a portion of Examples 1 to 20.

[0259] Example 26 may include a signal described in or related to any of Examples 1 to 20, or a part or portion thereof.

[0260] Example 27 may include a datagram, information element, packet, frame, segment, PDU, or message described or associated with any of Examples 1 through 20, or a portion or part thereof, or others described in this disclosure.

[0261] Example 28 may include a signal encoded with data described in or related to any of Examples 1 to 20, or a portion or parts thereof, or other methods described in this disclosure.

[0262] Example 29 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message described or related to any of Examples 1 to 20, or a portion or part thereof, or a signal described otherwise in this disclosure.

[0263] Example 30 may include an electromagnetic signal carrying a plurality of computer-readable instructions, the execution of which by one or more processors causes the one or more processors to perform a method, technique, or process described in or related to any of Examples 1 through 20 or portions thereof.

[0264] Example 31 may include a computer program including instructions, the execution of which by a processing element causes the processing element to perform a method, technique, or process described in or related to any of Examples 1 to 20, or a portion thereof.

[0265] Example 32 may include signals in a wireless network as shown and described herein.

[0266] Example 33 may include a method of communicating in a wireless network as shown and described herein.

[0267] Example 34 may include a system for providing wireless communication as shown and described herein.

[0268] Example 35 may include a device for providing wireless communication as shown and described herein.

[0269] Any of the above examples may be combined with any other example (or combination of examples) unless otherwise stated. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0270] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated, and it is intended that the following claims be interpreted to embrace all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed by one or more processors, cause a user equipment (UE) to: identifying an indication of one or more resources over which a multicast service can be provided while the UE is in an inactive state; determining available resources for serving the UE; A computer-readable medium for determining resources for receiving a multicast transmission based on the indication of the one or more resources and the resources available for providing a multicast service to the UE.

2. The computer-readable medium of claim 1 , wherein the indication of the one or more resources includes a list of cells that can provide multicast services while the UE is in the inactive state.

3. The computer-readable medium of claim 2 , wherein the list of cells includes a list of cells by radio resource control (RRC) state.

4. The computer-readable medium of claim 1 , wherein the indication of the one or more resources includes a list of frequencies over which multicast services can be provided while the UE is in the inactive state.

5. The computer-readable medium of claim 4 , wherein the list of frequencies comprises a list of frequencies for each Multicast / Broadcast Service (MBS) session.

6. 2. The computer-readable medium of claim 1, wherein the indication of the one or more resources indicates a resource to which the UE is redirected, and determining the resource for receiving the multicast transmission includes determining that the resource to which the UE is redirected is the resource for receiving the multicast transmission.

7. Determining the resources for receiving the multicast transmission comprises: determining that the resources available for serving the UE do not include any of the one or more resources from the indication; and determining the resources from the available resources for serving the UE; The instructions, when executed by the one or more processors, further cause the UE to initiate a radio resource control (RRC) resumption procedure to receive the multicast transmission. The computer-readable medium of claim 1 .

8. The instructions, when executed by the one or more processors, further cause the UE to: identifying an indication of an inactive multicast configuration for receiving the multicast transmission; The computer-readable medium of claim 1 , further comprising: utilizing the inactive multicast configuration to process the multicast transmission received by the UE.

9. The method of claim 1 , wherein the resources available for serving the UE are determined as part of a handover from a first base station to a second base station.

10. 1. A method of operating a user equipment (UE), comprising: initiating a handover procedure from a first cell to a second cell while the UE is in an inactive state; determining a procedure for receiving multicast data from the second cell based on an indication of one or more resources capable of providing a multicast service, the indication of the one or more resources having been received from the first cell; and initiating the procedure for processing multicast data received from the second cell; A method comprising:

11. 11. The method of claim 10, wherein the indication of the one or more resources includes an indication of one or more resources capable of providing a multicast service while the UE is in the inactive state, and wherein determining the procedure for receiving multicast data includes determining to implement an inactive multicast configuration for processing received multicast data, and initiating the procedure includes implementing the inactive multicast configuration for processing the multicast data received from the second cell.

12. 11. The method of claim 10, wherein the indication of the one or more resources does not include resources corresponding to the second cell, and wherein determining the procedure for receiving multicast data includes determining a radio resource control (RRC) restart procedure for receiving multicast data based on the resources corresponding to the second cell that are not included in the indication of the one or more resources, and wherein initiating the procedure includes initiating the RRC restart procedure for processing the multicast data received from the second cell.

13. 11. The method of claim 10, wherein the indication of the one or more resources includes an indication that the UE will be in a connected state when receiving multicast data from the second cell, and determining the procedure includes determining a radio resource control (RRC) restart procedure for receiving multicast data based on the indication that the UE will be in a connected state when receiving multicast data from the second cell, and initiating the procedure includes initiating the RRC restart procedure for processing the multicast data received from the second cell.

14. The method of claim 10 , wherein the indication of the one or more resources includes an indication of one or more cells that can provide multicast services while the UE is in the inactive state.

15. The method of claim 10 , wherein the indication of the one or more resources includes an indication of one or more frequencies over which multicast services can be provided while the UE is in the inactive state.

16. 11. The method of claim 10, wherein the procedure is further determined based on an indication of a priority state for the UE when receiving multicast data from the second cell, the indication of the priority state being received from the first cell.

17. 1. A method of operating a base station, comprising: determining to transition a user equipment (UE) coupled to the base station to an inactive state; determining one or more resources on which a multicast service can be provided to the UE; generating a radio resource control (RRC) release having a suspend configuration message including an indication of the one or more resources; sending an RRC release with the suspend configuration message to the UE to transition the UE to the inactive state; A method comprising:

18. 20. The method of claim 17, wherein determining the one or more resources includes determining one or more cells that can provide a multicast service to the UE while the UE is in the inactive state.

19. 20. The method of claim 17, wherein determining the one or more resources includes determining one or more frequencies over which a multicast service can be provided to the UE while the UE is in the inactive state.

20. determining a corresponding state of the UE for receiving multicast data from each of the one or more resources, and wherein the RRC release with suspend configuration message further includes an indication of the corresponding state of the UE for receiving multicast data from each of the one or more resources.

18. The method of claim 17.

Images