Multicast reception in inactive state

Abstract

The present application relates to devices and components, including apparatuses, systems and methods for configuring user equipment for multicast reception in an inactive state in a wireless communication system.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 483,714, filed on February 7, 2023, entitled “Multicast Reception in Inactive State,” the disclosure of which is incorporated herein by reference in its entirety for all purposes. Technical Field

[0003] The present application relates to the field of wireless technology, and in particular to multicast reception in an inactive state. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) network stipulates that a base station multicasts signals to one or more designated user equipments (UEs). The base station configures these designated UEs to receive the multicast signals, while other UEs not designated to receive the multicast signals are not configured to receive the multicast signals. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 Illustrated are example multicast and broadcast service (MBS) broadcast configuration instances according to some embodiments.

[0006] Figure 2 Illustrated is a method that can be used according to some embodiments Figure 1 Example information elements exchanged as part of an MBS broadcast configuration example.

[0007] Figure 3 An example multicast MBS control representation is illustrated in accordance with some embodiments.

[0008] Figure 4 A first portion of example information elements for MBS multicast configuration according to some embodiments is illustrated.

[0009] Figure 5 A second portion of example information elements for MBS multicast configuration according to some embodiments is illustrated.

[0010] Figure 6 A third portion of an example information element for MBS multicast configuration is illustrated according to some embodiments.

[0011] Figure 7 An example signaling diagram showing multicast configuration via a first approach is illustrated according to some embodiments.

[0012] Figure 8 An example signaling diagram illustrating multicast configuration via the second approach is illustrated in accordance with some embodiments.

[0013] Figure 9 An example signaling diagram showing multicast configuration via a third approach is illustrated, according to some embodiments.

[0014] Figure 10 An example signaling diagram showing multicast configuration via a fourth approach is illustrated in accordance with some embodiments.

[0015] Figure 11 Example processes for operating a user equipment (UE) according to some embodiments are illustrated.

[0016] Figure 12 Example processes for operating a base station according to some embodiments are illustrated.

[0017] Figure 13 Example procedures for operating a UE according to some embodiments are illustrated.

[0018] Figure 14 Example processes for operating a base station according to some embodiments are illustrated.

[0019] Figure 15 Example procedures for operating a UE according to some embodiments are illustrated.

[0020] Figure 16 Example processes for operating a base station according to some embodiments are illustrated.

[0021] Figure 17 An example UE according to some embodiments is illustrated.

[0022] Figure 18 An example next-generation Node B (gNB) is illustrated in accordance with some embodiments. DETAILED DESCRIPTION

[0023] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different figures. In the following description, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth for the purpose of illustration and not limitation, so as to provide a thorough understanding of the various aspects of the various embodiments. However, it will be apparent to those skilled in the art who benefit from this disclosure that the various aspects of the various embodiments may be practiced in other examples that deviate 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 due to unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

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

[0025] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group) configured to provide the described functionality, 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 capacity PLD (HCPLD), a structured ASIC, or a programmable system on a chip (SoC)), a digital signal processor (DSP), etc. In some embodiments, the circuit can execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) and program code for executing the functionality of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0026] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit that is capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, or transmitting digital data. The term "processor circuit" 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, and / or functional processes).

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

[0028] As used herein, the term "user equipment" or "UE" refers to a device with radio communication capabilities and may describe a remote user of network resources in a communication network. Furthermore, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, 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.

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

[0030] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database and application, workload units, etc. "Hardware resources" may refer to computing, storage, or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, 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 that a computer device / system can access via a communication network. The term "system resource" may refer to any type of shared entity that provides a service and may include computing resources or network resources. System resources can be considered a set of coherent functions, network data objects, or services that can be accessed through a server, where such system resources reside on a single host or multiple hosts and can be clearly identified.

[0031] As used herein, the term "channel" refers to any tangible or intangible transmission medium for conveying data or data streams. The term "channel" may be synonymous or equivalent with "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 representing a path or medium through which data is conveyed. Additionally, as used herein, the term "link" refers to a connection between two devices for sending and receiving information.

[0032] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a concrete occurrence of an object, which may occur, for example, during the execution of program code.

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

[0034] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, etc.

[0035] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents. An information element may include one or more additional information elements.

[0036] To enable resource-efficient delivery of multicast / broadcast services, the Third Generation Partnership Project (3GPP) developed New Radio (NR) broadcast / multicast in Release 17 (Rel-17), aiming to enable general multicast and broadcast services (MBS) over the fifth generation system (5GS). Use cases identified as benefiting from this feature include public safety and mission-critical applications, vehicle-to-everything (V2X) applications, Internet Protocol television (IPTV), live video, software delivery over wireless and Internet of Things (IoT) applications, and more. For Rel-17 MBS, two delivery modes have been agreed upon: Delivery Mode 1 (for multicast only) addresses higher Quality of Service (QoS) services, and Delivery Mode 2 (for broadcast only) focuses on lower QoS services. Given that Rel-17 MBS already provides basic functionality to support MBS services, the overall primary goal of Rel-18 should be to achieve better deployment of MBS, such as improvements in resource efficiency and capacity based on Rel-17 MBS.

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

[0038] The Rel-17 New Radio (NR) MBS broadcast method allows UEs to receive broadcast services only in a downlink manner, i.e., to perform broadcast reception without prior network access. However, in a typical use case for broadcasting, the UE may be required to receive broadcast services and unicast services from the same or another operator's network at the same time, 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 this situation is not explicitly mentioned in Rel-17, and should focus on the case of unicast reception under RRC_CONNECTED and broadcast reception (including emergency and public safety broadcasts) from the same or different operators.

[0039] Network sharing is a common practice for reducing network capital expenditure (CAPEX). In a RAN sharing deployment, if the same multicast / broadcast service is provided by two (or more) operators separately, the service will be identified as a separate temporary mobile group identity (TMGI), resulting in duplicate point-to-multipoint (PTM) radio resource consumption in the same cell to transmit the same content. PTM can refer to a single point to two or more points. This justifies the resource efficiency improvements in RAN sharing scenarios.

[0040] Note that public safety services benefit from Rel-17 NR MBS functionality as well as Rel-18 enhancements following the above rationale.

[0041] Further enhancements to NR multicast / broadcast capabilities based on Rel-17 MBS are expected. Some of the goals for Rel-18 include those discussed below.

[0042] A first goal may be to specify support for multicast reception for UEs in the RRC_INACTIVE state. For example, PTM configuration may be desired for UEs receiving multicast in the RRC_INACTIVE state. Additionally, it may be desirable to study the impact of mobility and state transitions on UEs receiving multicast in the RRC_INACTIVE state. UEs in the RRC_INACTIVE state do not require seamless / lossless mobility to support multicast reception.

[0043] Another goal may be to specify Uu signaling enhancements to allow UEs to use shared processing for MBS broadcast and unicast reception, i.e. including UE capability and related assistance information reporting on simultaneous unicast reception in RRC_CONNECTED and MBS broadcast reception from the same or different operators.

[0044] Another goal may be to study and, if necessary, specify enhancements to improve resource efficiency of MBS reception in RAN sharing scenarios.

[0045] Figure 1 An example MBS broadcast configuration example 100 is illustrated according to some embodiments. Specifically, Figure 1 An example MBS broadcast configuration example 100 is illustrated for configuring a UE 102 to receive a broadcast transmission sent by a base station 104. The UE 102 may include a UE 1700 ( Figure 17 ) features. The base station 104 may include a next generation node B (gNB) 1800 ( Figure 18 ) features.

[0046] MBS broadcast configuration example 100 is represented by a signaling diagram illustrating transmissions that may be exchanged between UE 102 and base station 104 to configure UE 102 to receive broadcast transmissions from base station 104 . Figure 2 Illustrated are example information elements 200 that may be exchanged as part of the MBS broadcast configuration instance 100 according to some embodiments.

[0047] In the illustrated embodiment, UE 102 may be configured to receive broadcast transmissions sent by base station 104, as indicated at 106. However, UE 102 may not be able to process broadcast transmissions from base station 104 until UE 102 is configured to receive broadcast transmissions from base station 104. Therefore, a configuration procedure may be performed to configure UE 102 to receive and process broadcast transmissions.

[0048] A two-step MBS broadcast configuration acquisition may be performed for UE 102 in RRC_CONNECTED / IDLE / INACTIVE states. For example, the process for configuring UE 102 to receive broadcast transmissions from base station 104 when in RRC_CONNECTED, RRC_IDLE, and RRC_INACTIVE may involve two acquisition steps for the UE. UE 102 may receive the MBS configuration for a broadcast session via the Multicast / Broadcast Service Control Channel (MCCH). In these embodiments, the MBS configuration may omit the multicast session configuration. UE 102 may receive the MCCH based on the MCCH configuration provided in the System Information Block Type X (SIBx).

[0049] Base station 104 may transmit SIBx 108 to UE 102. SIBx 108 may include an RRC transmission. SIBx 108 may include configuration information for the MCCH of base station 104. SIBx 108 may include an MCCH-Config information element and / or a cfr-ConfigMCCH-MTCH information element, which may be used to configure UE 102 to receive transmissions via the MCCH of base station 104.

[0050] Information element 200 includes an example MCCH-Config information element 202 that may be included in SIBx 108 according to some embodiments. MCCH-Config information element 202 may provide data that may be used to configure UE 102 to receive and process transmissions via the MCCH of base station 104. For example, MCCH-Config information element 202 may include a repetition period and offset indication corresponding to the MCCH, a window start slot indication corresponding to the MCCH, a window duration indication corresponding to the MCCH, and / or a modification period indication corresponding to the MCCH. UE 102 may receive MCCH-Config information element 202 in SIBx 108 and may determine the repetition period and offset, window start slot, window duration, and / or modification period for the MCCH.

[0051] According to some embodiments, information element 200 includes a cfr-ConfigMCCH-MTCH information element 204, which may be included in SIBx 108. The cfr-ConfigMCCH-MTCH information element 204 may provide data that may be used to configure UE 102 to receive and process transmissions via the MCCH of base station 104. For example, the cfr-ConfigMCCH-MTCH may include information for configuring common frequency resources for MCCH and / or multicast traffic channel (MTCH) reception. In some embodiments, the cfr-ConfigMCCH-MTCH information element 204 may include a location and bandwidth broadcast indication corresponding to the MCCH, a physical downlink shared channel (PDSCH) configuration indication corresponding to the MCCH, and / or a common control resource set extension indication corresponding to the MCCH. UE 102 may receive the cfr-ConfigMCCH-MTCH information element 204 in SIBx 108 and may determine the location and bandwidth for the MCCH, the PDSCH configuration, and / or the common control resource set extension.

[0052] UE 102 may be configured to receive transmissions via the MCCH of base station 104 based on SIBx 108. For example, UE 102 may utilize data from information elements included in SIBx 108 to configure UE 102 to receive and process transmissions received via the MCCH of the base station.

[0053] Once UE 102 has been configured to receive and process transmissions via the MCCH of base station 104, UE 102 may receive one or more MCCH transmissions from base station 104. For example, base station 104 may transmit MCCH transmission 110. Base station 104 may broadcast MCCH transmission 110 via base station 104's MCCH.

[0054] The base station 104 may provide the MBS broadcast configuration in the MCCH. For example, the base station 104 may provide data regarding the MBS broadcast configuration in the MCCH transmission 110. The MCCH provides a list of all broadcast services with ongoing sessions transmitted on the MTCH and associated information for the broadcast session (e.g., an MBS session identifier (ID), a Global System for Mobile Communications EDGE Radio Access Network Radio Network Temporary Identifier (G-RNTI) and scheduling information, neighboring cell information for the MTCH). For example, the base station 104 may provide transmissions that include a list of all broadcast services with ongoing sessions transmitted on the MTCH and associated information broadcast sessions via the MCCH.

[0055] The MCCH transmission 110 may include one or more messages transmitted via the MCCH of the base station 104. The UE 102 may establish one or more broadcast MBS radio bearers based on the MCCH transmission 110, as indicated by 112. In addition, the UE 102 may establish a service data adaptation protocol (SDAP) entity, a packet data convergence protocol (PDCP) entity, and / or a radio link control entity based on the MCCH transmission 110. The UE 102 may further apply a physical layer (PHY) configuration and / or notify upper layers of a TMGI based on the MCCH transmission 110.

[0056] The base station 104 may provide a first transmission 114 of the MCCH transmissions 110. The first transmission 114 may cause a physical downlink control channel (PDCCH) to be scheduled using an MCCH-radio network temporary identifier (RNTI).

[0057] Base station 104 may provide a second transmission 116 in MCCH transmission 110. Second transmission 116 may include an MBS broadcast configuration for configuring UE 102 to receive and process the broadcast signal transmitted by base station 104. Second transmission 116 may be transmitted via the MCCH or a physical downlink shared channel (PDSCH) of base station 104.

[0058] The second transmission 116 may include an information element 206 that provides data for configuring the UE 102 to receive and process the transmission broadcast by the base station 104. The information element 206 may include a session information list, a neighbor cell list, a configured PTM list, an MTCH configuration, and / or a mapping window list.

[0059] The session information list of information element 206 may include a session list information element 208. Session list information element 208 may include a session ID, an RNTI, a broadcast list, scheduling information, a neighbor cell indication, a configuration index, and / or a mapping window index. UE 102 may use session list information element 208 to determine a session list corresponding to base station 104.

[0060] The neighbor cell list of information element 206 may include a neighbor cell list information element 210. The neighbor cell list information element 210 may include a physical cell ID and / or a carrier frequency. UE 102 may utilize neighbor cell list information element 210 to determine neighbor cell information related to base station 104.

[0061] The configured PTM list of information element 206 may include a PTM configuration element 212. The PTM configuration element 212 may include a PTM on-duration timer indication, a PTM active timer indication, a PTM hybrid automatic repeat request (HARQ) round trip time (RTT) downlink (DL) timer indication, a PTM long cycle start offset indication, and / or a PTM slot offset indication. The UE 102 may utilize the PTM configuration element 212 to determine the configuration for the PTM associated with the base station 104.

[0062] The MTCH configuration of the information element 206 may include an MTCH configuration information element 214. The MTCH configuration information element 214 may include a PDSCH configuration list, a time domain allocation list for the PDSCH, a rate matching mode for adding a mod list indication, a modulation and coding scheme (MCS) table, and / or an overhead indication. The UE 102 may use the MTCH configuration information element 214 to determine the configuration of the MTCH of the base station 104.

[0063] The mapping window list of information element 206 may include a mapping window cyclic offset information element 216. The mapping window cyclic offset information element 216 may indicate a cyclic offset for the mapping window. The UE 102 may use the mapping window cyclic offset information element 216 to determine a mapping window for a synchronization signal / physical broadcast channel block (SSB) corresponding to the base station 104.

[0064] The UE 102 may be configured to receive and process transmissions broadcast by the base station 104 based on the MCCH transmission 110. For example, the base station 104 may transmit one or more broadcast MBS service transmissions 118. Based on the UE 102 being configured to receive and process the broadcast transmissions, the UE 102 may receive the one or more broadcast MBS service transmissions 118 and may process the broadcast MBS service transmissions 118.

[0065] Figure 3An example multicast MBS control representation 300 is illustrated according to some embodiments. For example, the multicast MBS control representation 300 illustrates some example control operations related to multicast MBS that may be implemented by the system. The multicast MBS control representation 300 is illustrated by a signal diagram between a base station 302 and multiple UEs.

[0066] The multicast MBS control representation 300 includes a base station 302. The base station 302 may include a gNB 1800 ( Figure 18 ) features. The multicast MBS control representation 300 includes a first UE 304, a second UE 306, and a third UE 308. Each of the first UE 304, the second UE 306, and the third UE 308 may include UE 1700 ( Figure 17 ) features.

[0067] When an RRC_CONNECTED UE joins a multicast session, the network (NW) may transmit an RRC reconfiguration message with the relevant MBS configuration for the multicast session to the UE. For example, a first UE 304 may be RRC-connected to a base station 302, as indicated by connection 310. A second UE 306 may be RRC-connected to the base station 302, as indicated by connection 312. A third UE 308 may be RRC-connected to the base station 302, as indicated by connection 314.

[0068] Base station 302 may send an RRC reconfiguration message 316 to first UE 304. RRC reconfiguration message 316 may include the relevant MBS configuration for the multicast session for first UE 304. In the illustrated embodiment, RRC reconfiguration message 316 indicates that first UE 304 is configured for MBS session #1. First UE 304 may be configured for MBS session #1 based on RRC reconfiguration message 316.

[0069] Base station 302 may send an RRC reconfiguration message 318 to second UE 306. RRC reconfiguration message 318 may include the relevant MBS configuration for the multicast session for second UE 306. In the illustrated embodiment, RRC reconfiguration message 318 indicates that second UE 306 is configured for MBS session #1. Second UE 306 may be configured for MBS session #1 based on RRC reconfiguration message 318.

[0070] Base station 302 may send an RRC reconfiguration message 320 to third UE 308. RRC reconfiguration message 320 may include the relevant MBS configuration for the multicast session of third UE 308. In the illustrated embodiment, RRC reconfiguration message 320 indicates that third UE 308 is configured for MBS session #1. Third UE 308 may be configured for MBS session #1 based on RRC reconfiguration message 320.

[0071] Once first UE 304, second UE 306, and third UE 308 have been configured for MBS Session #1, first UE 304, second UE 306, and third UE 308 may receive transmissions related to MBS Session #1 multicast by base station 302. For example, base station 302 may multicast MBS service delivery 322. First UE 304, second UE 306, and third UE 308 may receive and process MBS service delivery 322. First UE 304 may monitor and receive MBS service during the time indicated by 334. Second UE 306 may monitor and receive MBS service during the time indicated by 336. Third UE 308 may monitor and receive MBS service during the time indicated by 338.

[0072] The base station 302 may be able to deactivate the MBS session. For example, the base station 302 may deactivate MBS session #1 after the MBS service delivery 322, as indicated at 340.

[0073] When a multicast session is deactivated, the NW may release the UEs participating in the session to the IDLE / INACTIVE state. For example, the base station 302 may send a message to the UE participating in MBS session #1 to transition the UE to the idle state and / or inactive state.

[0074] The base station 302 may send an RRC release message 324 with a suspension configuration to the first UE 304. The RRC release message 324 with the suspension configuration may indicate that the first UE 304 will transition to an inactive state. The first UE 304 may transition to the inactive state based on the RRC release message 324 with the suspension configuration, as indicated by inactive 326. The first UE 304 may stop monitoring and receiving MBS services from the base station 302 based on the first UE 304 receiving the RRC release message 324 with the suspension configuration, as indicated by end (334) when the first UE 304 receives the RRC release message 324 with the suspension configuration. The first UE 304 may not monitor and receive MBS services from the base station 302 until the first UE 304 transitions back to the connected state.

[0075] The base station 302 may send an RRC release message 328 to the second UE 306. The RRC release message 328 may indicate that the second UE 306 will transition to an idle state. The second UE 306 may transition to an idle state based on the RRC release message 328, as indicated by idle 330. The second UE 306 may stop monitoring and receiving MBS services from the base station 302 based on the second UE 306 receiving the RRC release message 325, as indicated by end 336 when the second UE 306 receives the RRC release message 328. The second UE 306 may not monitor and receive MBS services from the base station 302 until the second UE 306 transitions back to a connected state.

[0076] When a multicast session is activated, the NW notifies idle / inactive UEs of the multicast session activation via a paging mechanism. For gNBs supporting MBS, the paging message contains the MBS session ID to address all idle / inactive UEs participating in the MBS multicast session. Paging is used for group notification. For example, UEs are not paged individually. For gNBs not supporting MBS, the paging message is addressed to each UE individually because the core network (CN) initiates paging in a legacy manner.

[0077] For example, base station 302 may activate MBS session #1, as indicated by 342. Base station 302 may send a paging transmission 332. Paging transmission 332 may include the MBS session ID to address idle and / or inactive UEs that previously joined the MBS session corresponding to the MBS session ID. In the illustrated embodiment, paging transmission 332 includes MBS session ID #1. Paging transmission 332 may address idle and / or inactive UEs that have joined MBS session #1. If base station 302 supports MBS, paging transmission 332 may be sent for group notification. If base station 302 does not support MBS, paging transmission 332 may be sent individually to each of the UEs.

[0078] Base station 302 may perform an RRC recovery procedure 344 with first UE 304. RRC recovery procedure 344 may configure first UE 304 for MBS session #1. First UE 304 may transition to a connected state based on RRC recovery procedure 344, as indicated by 346. After transitioning to the connected state, first UE 304 may monitor and receive MBS services from base station 302, as indicated by 352.

[0079] The base station 302 may perform an RRC setup procedure and an RRC reconfiguration 348 with the second UE 306. The RRC setup procedure and the RRC reconfiguration 348 may configure the second UE 306 for MBS session #1. The second UE 306 may transition to a connected state based on the RRC setup procedure and the RRC reconfiguration 348, as indicated by 350. After transitioning to the connected state, the second UE 306 may monitor and receive MBS services from the base station 302, as indicated by 354.

[0080] The base station 302 may multicast the MBS service delivery 356. The first UE 304, the second UE 306, and the third UE 308 may receive the MBS service delivery 356 and process the MBS service delivery 356.

[0081] If through Figure 3 As can be seen, when the UE is in a connected state, the UE monitors and receives MBS services. However, when the UE is in an inactive and idle state, the UE does not monitor and receive MBS services. This may cause the UE to miss any MBS services sent while the UE is in an inactive and idle state, which may be undesirable.

[0082] During legacy MBS multicast configuration, the NW only provides configuration for MBS multicast via the RRCReconfiguration message. The MBS multicast configuration includes the following parts. Figure 4 A first portion of example information elements for MBS multicast configuration according to some embodiments is illustrated. Figure 5 A second portion of example information elements for MBS multicast configuration according to some embodiments is illustrated. Figure 6 A third portion of an example information element for MBS multicast configuration is illustrated according to some embodiments.

[0083] Part 1 of the MBS multicast configuration is the multicast session / multicast radio bearer (MRB) configuration in RadioBearerConfig. The MRB configuration in RadioBearerConfig may include Figure 4 The MRB information element 402 to be added provides data on MRB configuration. The MRB information element 402 to be added may provide data for the UE to use MRB for MBS multicast.

[0084] Part 2 of the MBS multicast configuration is the PTM-related G-RNTI and discontinuous reception (DRX) configuration in the MAC-CellGroupConfig. The PTM-related G-RNTI and DRX configuration may include Figure 4 Cell group configuration information element 404, Figure 5 RNTI specific configuration information element 502 and / or Figure 6 The cell group configuration information element 404, the RNTI specific configuration information element 502 and / or the DRX PTM configuration information element 602 may provide data for the UE to use G-RNTI and DRX for MBS multicast.

[0085] Part 3 of the MBS multicast configuration is the PTM PDCCH / PDSCH configuration in the Crest Factor Reduction (CFR) configuration within each BWP DL configuration. The PTM PDCCH / PDSCH configuration may include Figure 5 The BWP downlink dedicated information element 504 may provide data for the UE to configure PDCCH / PDSCH for MBS multicast.

[0086] Part 4 of the MBS multicast configuration is a certain HARQ feedback related configuration in the bandwidth part (BWP) configuration. The HARQ feedback related configuration may be based on the MRB information element 402 to be added, the cell group configuration information element 404, the RNTI specific configuration information element 502, the BWP downlink dedicated information element 504, and / or Figure 6 For legacy systems, the UE needs all four parts to receive and process multicast messages sent by the base station.

[0087] In Release 17 (R17) MBS configurations, for MBS multicast services, only connected UEs that have completed MBS multicast authentication and joined the CN's multicast session via non-access stratum (NAS) procedures can receive data for the joint session. The NW provides configuration via dedicated RRC signaling, which has security protection. For MBS broadcast services, all UEs can receive the MBS services of interest. The NW provides configuration via MTCH broadcast configuration on the MCCH channel, which is broadcast and has no security protection.

[0088] For Release 18 (R18), a hybrid approach to multicast configuration / reconfiguration can be considered for MBS multicast reception in the INACTIVE state. Dedicated RRC signaling can be used to switch a multicast receiving UE from RRC_CONNECTED to RRC_INACTIVE and continue multicast reception. MCCH can be used when PTM configuration needs to be indicated, when PTM configuration needs to be changed, or during mobility beyond the serving cell / gNB.

[0089] For R18 multicast PTM configuration via the MCCH channel, if the UE has not yet authenticated for multicast session reception or has not yet joined the MBS multicast session, the UE may not be able to obtain the multicast configuration and perform data reception accordingly. However, MBS configuration via the MCCH channel is not secure and can be obtained by any UE within the cell. This may be a vulnerability that malicious actors can exploit. To ensure more secure multicast configuration via the MCCH channel, several enhancements can be utilized as described throughout this disclosure.

[0090] The idea behind at least some of the approaches described herein may be to not allow UEs to get multicast PTM configuration for free.

[0091] This article proposes a method for configuring multicast PTM for inactive UEs via MCCH. In the first method, the NW only provides a portion of the multicast configuration via the MCCH channel. For example, the multicast configuration can be divided into two parts. The first part of the multicast configuration can be provided via RRC dedicated signaling. The second part of the multicast configuration can be provided via MCCH.

[0092] In the second method, the NW only provides the index of the multicast PTM configuration via the MCCH channel. For example, multiple candidate multicast PTM configurations can be provided to the UE in advance. The NW can then notify the UE of the configuration ID / index via the MCCH channel to implement the multicast PTM configuration.

[0093] In the third method, UE-specific configuration of the MCCH channel for multicast configuration may be performed. The configuration of the MCCH channel is not provided via broadcast, but rather via UE-specific signaling.

[0094] In the fourth method, a security scheme may be applied to the MBS multicast configuration sent via the MCCH channel. The multicast configuration via the MCCH channel may be provided with a security method (such as encryption, signature, or integrity protection). The NW may provide some or all parameters for security checks via RRC dedicated signaling.

[0095] Whether to provide multicast PTM configuration via MCCH channel may depend on UE capability or UE preference. UE may indicate whether UE supports or whether UE prefers to receive reconfiguration via MCCH channel. If not, NW may provide reconfiguration via RRC dedicated signaling.

[0096] For the first method involving partial multicast configuration via MCCH, the NW does not provide all parts to the UE via the MCCH channel. Figure 7An example signaling diagram 700 is illustrated showing multicast configuration via a first approach, according to some embodiments. For example, the signaling diagram 700 illustrates messages that may be exchanged for a portion of the multicast configuration approach.

[0097] The multicast configuration for INACTIVE reception may include three parts. Part 1 may include the MRB configuration in RadioBearerConfig. Part 2 may include PTM-related MAC configuration. For example, in some embodiments, Part 2 may include PTM-related G-RNTI and DRX configuration in MAC-CellGroupConfig. Part 3 may include PTM-related PHY configuration. For example, in some embodiments, Part 3 may include PTM PDCCH / PDSCH configuration in the CFR configuration within each BWP DL configuration.

[0098] The provisioning of each part of the configuration may be as follows. For part 1, the multicast session / MRB configuration may be provided via RRC dedicated configuration. For session / MRB related reconfiguration, the NW may require the UE to return to CONNECTED mode and provide the reconfiguration via UE dedicated RRC signaling. For example, the NW may perform an RRC recovery procedure (such as RRC recovery procedure 344 ( Figure 3 )) and / or RRC establishment procedures (such as RRC establishment procedures and RRC reconfiguration 348 ( Figure 3 )) to transition the UE back to the connected state. The session / radio bearer (RB) related configuration may be closely related to the UE MBS session joint NAS procedure, which can only be performed via RRC dedicated signaling. Therefore, it is sufficient to change the multicast session / MRB configuration via UE dedicated signaling.

[0099] For part 2, MAC-related scheduling / DRX configuration can be performed via RRC dedicated configuration or via the MCCH channel. For option 1, reconfiguration can be limited via RRC dedicated configuration. The DRX / scheduling mode can be determined according to the quality of service (QoS) requirements of the MBS multicast service. Therefore, no multicast service change means no QoS requirement change and no scheduling / DRX mode change. For option 2, some parameters (e.g., DRX offset) can be reconfigured via the MCCH channel. For example, it may be necessary to adjust according to the data arrival time. For option 3, reconfiguration can be performed via the MCCH channel. For option 4, the above three options can be predefined or preconfigured by RRC via UE-dedicated RRC signaling.

[0100] For part 3, the PTM PDCCH / PDSCH configuration in the CFR may be reconfigured via the MCCH channel. Detailed physical layer (PHY) resources may be changed for data transmission.

[0101] Signaling diagram 700 may include UE 702 and base station 704. UE 702 may include first UE 304 ( Figure 3 ), the second UE 306 ( Figure 3 ), the third UE 308 ( Figure 3 ) and / or UE 1700( Figure 17 ) features. The base station 704 may include the base station 302 ( Figure 3 ) and / or gNB 1800( Figure 18 Signaling diagram 700 illustrates example messages that may be exchanged between UE 702 and base station 704 to configure UE 702 for MBS multicast transmissions from base station 704 when UE 702 is in an inactive state.

[0102] UE 702 may be in a connected state, as indicated by 710. When UE 702 is in the connected state, base station 704 may send an RRC dedicated message 706 to UE 702. RRC dedicated message 706 may include a first portion of an MBS multicast configuration for UE 702.

[0103] The RRC dedicated message 706 may include the parts described above. The parts included in the RRC dedicated message 706 may depend on the options being implemented. In option 1, the RRC dedicated message 706 may include the multicast session / MRB configuration and the MAC-related scheduling / DRX configuration. In option 2, the RRC dedicated message 706 may include the multicast session / MRB configuration and the first part of the MAC-related scheduling / DRX configuration. In option 3, the RRC dedicated message may include the multicast session / MRB configuration. In option 4, the elements to be included in the RRC dedicated message 706 may be elements of option 1, elements of option 2, or elements of option 3 as predefined or preconfigured via UE-specific RRC signaling.

[0104] In some embodiments, UE 702 may transition to an inactive state after RRC dedicated message 706, as indicated by 708. While UE 702 is in the inactive state, base station 704 may send an MCCH message 712 to UE 702 via the MCCH of base station 704. MCCH message 712 may include a second portion of the MBS multicast configuration for UE 702.

[0105] The MCCH message 712 may include the parts as described above. The parts included in the MCCH message 712 may depend on the options being implemented. In Option 1, the MCCH message 712 may include the PTM PDCCH / PDSCH configuration in the CFR. In Option 2, the MCCH message 712 may include the PTM PDCCH / PDSCH configuration in the CFR and the second part of the MAC-related scheduling / DRX configuration. In Option 3, the MCCH message 712 may include the PTM PDCCH / PDSCH configuration in the CFR and the MAC-related scheduling / DRX configuration. In Option 4, the elements to be included in the MCCH message 712 may be elements of Option 1, elements of Option 2, or elements of Option 3 as predefined or preconfigured via UE-specific RRC signaling.

[0106] Because the three parts for multicast configuration are separated between RRC dedicated message 706 and MCCH message 712, the UE needs to receive both RRC dedicated message 706 and MCCH message 712 to be configured to properly receive multicast transmissions from base station 704. Because RRC dedicated message 706 is protected from access by UEs other than UE 702, UE 702 may be the only UE that can receive both RRC dedicated message 706 and MCCH message 712. Therefore, the partial multicast configuration method can provide protection against malicious actors.

[0107] For the second method, a multicast configuration index may be provided via MCCH to indicate the multicast PTM configuration to be implemented. For example, the NW may provide multiple multicast PTM configurations as a candidate configuration set to the UE via UE-specific signaling. When the configuration changes, the NW may indicate the new configuration via the configuration index sent to the UE. If the UE cannot find the indicated index, the UE may initiate an RRC Resume procedure (such as RRC Recovery procedure 344 ( Figure 3 )) to transition back to CONNECTED mode and inform the NW of the information. The information provided to the NW may indicate that the UE cannot find the indicated index. The NW may later provide the correct configuration to the UE based on the information being notified.

[0108] Figure 8 An example signaling diagram 800 showing multicast configuration via the second method according to some embodiments is illustrated. For example, the signaling diagram illustrates messages that may be exchanged for the multicast configuration index method.

[0109] Signaling diagram 800 may include UE 802 and base station 804. UE 802 may include first UE 304 ( Figure 3 ), the second UE 306 ( Figure 3 ), the third UE 308 ( Figure 3), UE 702( Figure 7 ) and / or UE 1700( Figure 17 ) features. The base station 804 may include the base station 302 ( Figure 3 ), base station 704 ( Figure 7 ) and / or gNB 1800( Figure 18 Signaling diagram 800 illustrates example messages that may be exchanged between UE 802 and base station 804 to configure UE 802 for MBS multicast transmissions from base station 804 when UE 802 is in an inactive state.

[0110] UE 802 may be in a connected state, as indicated by 806. When UE 802 is in the connected state, base station 804 may send an RRC dedicated message 808 to UE 802. RRC dedicated message 808 may include an RRC release message with a suspension configuration (such as RRC release message 324 with a suspension configuration ( Figure 3 )). The RRC dedicated message 808 may include a candidate configuration set. The candidate configuration set may include one or more multicast PTM configurations that can be utilized by the UE 802. Each of the multicast PTM configurations may have a corresponding configuration index. In the illustrated embodiment, the RRC dedicated message 808 includes PTM configuration #1, PTM configuration #2, and PTM configuration #3. The UE 802 may receive the RRC dedicated message 808 and store the PTM configurations included in the candidate configuration set of the RRC dedicated message 808.

[0111] UE 802 may transition to an inactive state following RRC dedicated message 808, as indicated by 810. While UE 802 is in the inactive state, base station 804 may send an MCCH message 812 to UE 802 via the MCCH of base station 804. MCCH message 812 may include a configuration index corresponding to a PTM configuration for UE 802 to implement.

[0112] UE 802 may receive MCCH message 812 and identify the configuration index included in MCCH message 812. UE 802 may compare the configuration index from MCCH message 812 with the configuration index corresponding to the stored PTM configuration from RRC dedicated message 808. If UE 802 determines that the configuration index from MCCH message 812 matches one of the configuration indexes of the stored PTM configurations, UE 802 may be configured with the PTM configuration corresponding to the configuration index. If UE 802 determines that the configuration index from MCCH message 812 does not match any of the configuration indexes of the stored PTM configurations, UE 802 may send a message to base station 804 indicating that UE 802 was unable to find the indicated configuration index. In the illustrated embodiment, MCCH message 812 may indicate configuration index 2. Based on MCCH message 812, UE 802 may determine that the indicated configuration index corresponds to PTM configuration #2 and may be configured with PTM configuration #2.

[0113] Access to the RRC dedicated message 808 may be limited to the UE 802, and other UEs may not be able to access the RRC dedicated message 808. Because the RRC dedicated message 808 includes the PTM configuration, other UEs may not be aware of the PTM configuration that may be implemented to receive multicast transmissions from the base station. Therefore, because other UEs are unaware of the PTM configuration, protection from malicious actors is provided.

[0114] For the third method involving MCCH configuration via non-broadcast mode, the NW may choose to provide a configuration for the UE to receive data via the MCCH channel according to one of the following options. For option 1, the NW may provide the configuration to the UE via UE-specific signaling. For option 2, the NW may provide part of the MCCH configuration via UE-specific signaling and provide another part of the MCCH configuration via broadcast. For option 3, the NW may provide multiple MCCH configurations via UE-specific signaling and indicate the MCCH configuration index (for PDSCH reception) in the scheduling downlink control information (DCI).

[0115] The UE may follow the MCCH channel to receive the multicast PTM configuration via the MCCH channel. For example, once the UE has been configured to receive data via the MCCH channel according to one of these options, the UE may monitor the MCCH channel for the multicast PTM configuration used to configure the UE.

[0116] Access to the RRC dedicated message 808 may be limited to the UE 802, and other UEs may not be able to access the RRC dedicated message 808. Because the RRC dedicated message 808 includes the PTM configuration, other UEs may not be aware of the PTM configuration that may be implemented to receive multicast transmissions from the base station. Therefore, because other UEs are unaware of the PTM configuration, protection from malicious actors is provided.

[0117] Figure 9 An example signaling diagram 900 showing multicast configuration via a third method according to some embodiments is illustrated. For example, the signaling diagram 900 illustrates signals that may be exchanged for MCCH configuration via a non-broadcast approach.

[0118] Signaling diagram 900 may include UE 902 and base station 904. UE 902 may include first UE 304 ( Figure 3 ), the second UE 306 ( Figure 3 ), the third UE 308 ( Figure 3 ), UE 702( Figure 7 ), UE 802( Figure 8 ) and / or UE 1700( Figure 17 ) features. The base station 904 may include the base station 302 ( Figure 3 ), base station 704 ( Figure 7 ), base station 804 ( Figure 8 ) and / or gNB1800( Figure 18 ) features. Signaling diagram 900 illustrates example messages that may be exchanged between UE 902 and base station 904 to configure UE 902 for MBS multicast transmissions from base station 904.

[0119] UE 902 may be in a connected state, as indicated by 906. When UE 902 is in the connected state, base station 904 may send an RRC dedicated message 908 to UE 902. In option 1, RRC dedicated message 908 may include an MCCH configuration for UE 902. UE 902 may be configured with the indicated MCCH configuration from RRC dedicated message 908 in option 1. In option 2, RRC dedicated message 908 may include a first portion of the MCCH configuration for UE 902. In option 3, RRC dedicated message 908 may include one or more MCCH configurations that may be implemented by UE 902. In some embodiments, RRC dedicated message 908 may include an RRC release message with a suspended configuration (such as RRC release message 324 with a suspended configuration). Figure 3 )).

[0120] The illustrated implementation of signaling diagram 900 implements Option 3. Specifically, RRC dedicated message 908 includes MCCH PDSCH configuration #1, MCCH PDSCH configuration #2, and MCCH PDSCH configuration #3. UE 902 may receive RRC dedicated message 908 and may store the MCCH PDSCH configuration from the RRC dedicated message.

[0121] UE 902 may transition to an inactive state following RRC dedicated message 908, as indicated by 910. When UE 902 is in the inactive state, the message sent by base station 904 for MBS multicast configuration may depend on the implemented options. For options 2 and 3, when UE 902 is in the inactive state, base station 904 may send message 912 and MCCH message 914. For option 1, base station 904 may send MCCH message 914 and may omit message 912.

[0122] For option 2, a message 912 may be broadcast by the base station 904. The message 912 for option 2 may include a second portion of the MCCH configuration to supplement the first portion of the MCCH configuration sent in the RRC dedicated message 908. For option 2, the UE 902 may utilize the first portion of the MCCH configuration from the RRC dedicated message 908 and the second portion of the MCCH configuration from the message 912 to configure the UE to receive MCCH transmissions from the base station 904.

[0123] For option 3, message 912 may include a scheduling DCI message for the MCCH. Message 912 for option 3 may include an MCCH configuration index indicating the MCCH configuration for UE 902. For option 3, UE 902 may identify a stored MCCH configuration corresponding to the indicated MCCH configuration index and configure the identified MCCH configuration for UE 902.

[0124] In the illustrated embodiment, message 912 indicates the MCCH configuration index of PDSCH index #3. UE 902 may determine that the MCCH configuration index corresponds to the stored MCCH PDSCH configuration #3. UE 902 may be configured with MCCH PDSCH configuration #3 based on the MCCH configuration index.

[0125] Once configured to receive messages from the base station 904 via the MCCH, the UE 902 may monitor the MCCH transmissions from the base station 904 for the multicast PTM configuration for the UE 902. The base station 904 may transmit an MCCH message 914 indicating the multicast PTM configuration for the UE 902. The MCCH message 914 may be transmitted according to the MCCH configuration for the UE 902. The UE 902 may identify the multicast PTM configuration indicated by the MCCH message 914 and may be configured with the multicast PTM configuration.

[0126] Access to RRC dedicated message 908 may be limited to UE 802, and other UEs may not be able to access RRC dedicated message 908. Since RRC dedicated message 908 includes the MCCH configuration, the first part of the MCCH configuration, or the PTM configuration, other UEs may not be aware of the MCCH configuration, the first part of the MCCH configuration, or the PTM configuration that may be implemented to receive multicast transmissions from the base station. Therefore, since other UEs are not aware of the MCCH configuration, the first part of the MCCH configuration, or the PTM configuration, protection from malicious actors is provided.

[0127] A fourth method may involve applying a security scheme to the multicast configuration sent via the MCCH. For example, one of the following security schemes may be applied to the multicast PTM configuration sent via the MCCH channel.

[0128] Figure 10 An example signaling diagram 1000 illustrating multicast configuration via a fourth approach according to some embodiments is illustrated. For example, the signaling diagram 1000 illustrates signals that may be exchanged for the security scheme approach.

[0129] The signaling diagram 1000 may include a UE 1002 and a base station 1004. The UE 1002 may include a first UE 304 ( Figure 3 ), the second UE 306 ( Figure 3 ), the third UE 308 ( Figure 3 ), UE 702( Figure 7 ), UE 802( Figure 8 ), UE 902( Figure 9 ) and / or UE 1700( Figure 17 ) features. The base station 1004 may include the base station 302 ( Figure 3 ), base station 704 ( Figure 7 ), base station 804 ( Figure 8 ), base station 904 ( Figure 9 ) and / or gNB 1800( Figure 18). Signaling diagram 1000 illustrates example messages that may be exchanged between UE 1002 and base station 1004 to configure UE 1002 for MBS multicast transmissions from base station 1004.

[0130] UE 1002 may be in a connected state, as indicated at 1010. When UE 1002 is in the connected state, base station 1004 may send an RRC dedicated message 1012 to UE 1002. RRC dedicated message 1012 may include data related to a security scheme applied to an MBS multicast configuration provided by base station 1004 to UE 1002. The data included in RRC dedicated message 1012 may depend on implementation options for the security scheme described below.

[0131] UE 1002 may be in an inactive state, as indicated by 1006. UE 1002 may be configured to receive MCCH transmissions from base station 1004. Base station 1004 may send an MCCH message 1008 to UE 1002 via the MCCH of base station 1004. MCCH message 1008 may indicate an MBS multicast configuration for UE 1002. One of the security schemes described in the following options may be applied to MCCH message 1008, thereby protecting MCCH message 1008.

[0132] In Option 1, a hash ID may be added to protect the MBS multicast configuration. For example, the hash ID may be added to the MBS multicast configuration included in MCCH message 1008. The NW may generate the hash ID based on the configuration message and a specific value. For example, the NW may generate the hash ID based on MCCH message 1008 and a specific value. For Option 1, the RRC dedicated message 1012 may indicate a specific value to be used by UE 1002 to process the MBS multicast configuration, thereby configuring the MBS multicast configuration for UE 1002.

[0133] In option 2, a signature may be added to protect the MBS multicast configuration. For example, a signature may be added to the MBS multicast configuration included in the MCCH message 1008. The parameters / configuration used to generate the signature may be per MBS session / MRB or per MCCH message. For example, the network may define which parameters and / or configurations to utilize to generate the signature for each MBS session / MRB or MCCH message. The generated signature may be generated on a per MBS session / MRB or per MCCH message basis. For option 2, the RRC dedicated message 1012 may indicate the parameters, configurations, and / or signatures to be utilized by the UE 1002 to process the MBS multicast configuration, for configuring the MBS multicast configuration for the UE 1002. The RRC dedicated message 1012 may indicate the MBS session / MRB or MCCH message corresponding to the parameters, configurations, and / or signatures provided in the RRC dedicated message 1012.

[0134] In Option 3, the multicast configuration may be encrypted and integrity protected on a per-MBS session basis. The NW may use the multicast session ID to encrypt or integrity protect the RRC message, and the UE may decrypt or verify the integrity protection (IP) based on the multicast session ID or session-specific security keys. For session / MRB-specific keys, the NW may provide the keys along with the MRB configuration or when the UE is released to the INACTIVE state via UE-specific RRC signaling. For example, the NW may encrypt or integrity protect the MBS multicast configuration. In an embodiment where the UE 1002 utilizes session-specific security keys to decrypt or verify the IP, the RRC dedicated message 1012 may include the security keys. The MBS multicast configuration included in the MCCH message 1008 may be encrypted and / or integrity protected. The UE 1002 may utilize the multicast session ID and / or security keys to decrypt the MBS multicast configuration and / or verify the IP used for the MBS multicast configuration.

[0135] In Option 4, the multicast configuration may be encrypted and integrity-protected using a specific security key. This differs from Option 3 in that the multicast configuration may include more than one multicast session. The specific security key is configured to the UE via dedicated RRC signaling, which is common to all multicast sessions in the same cell or specific area. For example, the NW may encrypt or integrity-protect the MBS multicast configuration. The RRC dedicated message 1012 may include the security key. The MBS multicast configuration included in the MCCH message 1008 may be encrypted and / or integrity-protected. The UE 1002 may use the security key to decrypt the MBS multicast configuration and / or verify the IP address used for the MBS multicast configuration.

[0136] The security scheme applied to the MBS multicast configuration may protect UEs other than the UE 1002 from accessing the MBS multicast configuration. Thus, the security scheme may provide protection from malicious actors.

[0137] Figure 11 An example process 1100 for operating a UE according to some embodiments is illustrated. For example, the process 1100 may be performed by a UE (such as the first UE 304 ( Figure 3 ), the second UE 306 ( Figure 3 ), the third UE 308 ( Figure 3 ), UE 702( Figure 7 ), UE 802( Figure 8 ), UE 902( Figure 9 ),UE 1002( Figure 10 ) and / or UE 1700( Figure 17 )) to execute.

[0138] The process 1100 may include receiving a first transmission at 1102, the first transmission providing first data for a multicast PTM configuration. Specifically, the UE may receive the first transmission via RRC dedicated signaling, the first transmission providing first data for a multicast PTM configuration for an inactive state of the UE. In some embodiments, the first transmission may include an RRC dedicated message 706 ( Figure 7 ), RRC dedicated message 808 ( Figure 8 ), RRC dedicated message 908 ( Figure 9 ) and / or RRC dedicated message 1012 ( Figure 10 ) features.

[0139] In some embodiments, the first data may include a multicast session / MRB configuration. In some of these embodiments, the first data may also include a MAC-related scheduling / DRX configuration. In some embodiments, the first data may include one or more multicast PTM configurations.

[0140] Process 1100 may include receiving a second transmission at 1104, the second transmission providing second data for multicast PTM configuration. Specifically, the UE may receive the second transmission via the MCCH, the second transmission providing second data for multicast PTM configuration for the active state. In some embodiments, the second transmission may include MCCH message 712 ( Figure 7 ), MCCH message 812( Figure 8 ), MCCH message 914( Figure 9 ), and / or MCCH message 1008 ( Figure 10 ) features.

[0141] In some embodiments, the second data may include a PTM PDCCH / PDSCH configuration in a CFR. Furthermore, in some embodiments, the second data may include a MAC-related scheduling / DRX configuration. In some embodiments, the second data may include a configuration index. The configuration index may indicate a multicast PTM configuration to be implemented from one or more multicast PTM configurations provided by the first data.

[0142] Process 1100 may include determining a multicast PTM configuration at 1106. Specifically, the UE may determine a multicast PTM configuration for an inactive state based on the first data and the second data.

[0143] Process 1100 may include implementing multicast PTM configuration at 1108. Specifically, the UE may implement multicast PTM configuration for an inactive state.

[0144] In some embodiments, process 1100 may also include receiving reconfiguration information related to MAC-related scheduling / DRX configuration. Specifically, the UE may receive the reconfiguration information related to MAC-related scheduling / DRX configuration via RRC dedicated signaling. In some embodiments, the reconfiguration information may include DRX offset information. The UE may reconfigure the multicast PTM configuration based on the reconfiguration information.

[0145] In some embodiments, process 1100 may further include receiving reconfiguration information related to MAC-related scheduling / DRX configuration. Specifically, the UE may receive the reconfiguration information related to MAC-related scheduling / DRX configuration via the MCCH. The UE may reconfigure the multicast PTM configuration based on the reconfiguration information.

[0146] In some embodiments, process 1100 may further include receiving an indication of a first portion of MAC-related scheduling / DRX reconfiguration information to be received via RRC dedicated signaling and a second portion of MAC-related scheduling / DRX reconfiguration information to be received via MCCH. Specifically, the UE may receive, via RRC dedicated signaling, an indication of the first portion of MAC-related scheduling / DRX reconfiguration information to be received via RRC dedicated signaling and the second portion of MAC-related scheduling / DRX reconfiguration information to be received via MCCH.

[0147] In some embodiments, process 1100 may further include determining that the configuration index does not correspond to any of the one or more PTM configurations. Specifically, the UE may determine that the configuration index from the second data does not correspond to any of the one or more multicast PTM configurations from the first data. The UE may initiate an RRC recovery procedure to transition to a connected state. While in connected mode, the UE may provide an indication that the configuration index does not correspond to any of the one or more multicast PTM configurations. The UE may also receive an indication of a multicast PTM configuration to implement based on providing the indication that the configuration index does not correspond to any of the one or more multicast PTM configurations.

[0148] Although Figure 11 The order of the operations of process 1100 may be implied, but it should be understood that in other embodiments, the operations may be performed in a different order and / or one or more of the operations may be performed simultaneously. Additionally, it should be understood that in other embodiments, one or more additional operations may be included in process 1100 and / or one or more of the operations may be omitted.

[0149] Figure 12 An example process 1200 for operating a base station according to some embodiments is illustrated. For example, process 1100 may be performed by a base station, such as base station 302 ( Figure 3 ), base station 704 ( Figure 7 ), base station 804 ( Figure 8 ), base station 904 ( Figure 9 )、Base Station 1004( Figure 10 ) and / or gNB 1800( Figure 18 )) to execute.

[0150] Process 1200 may include sending a request for the UE to transition to a connected mode at 1202. Specifically, the base station may send a request to the UE for the UE to transition to a connected mode.

[0151] Process 1200 may include generating a first transmission at 1204 that indicates first data for a multicast PTM configuration. Specifically, the base station may generate the first transmission that indicates first data for a multicast PTM configuration for an inactive state of the UE. The first transmission may include an RRC dedicated message 706 ( Figure 7 ), RRC dedicated message 808 ( Figure 8 ), RRC dedicated message 908 ( Figure 9 ) and / or RRC dedicated message 1012 ( Figure 10 ) features.

[0152] In some embodiments, the first data may include a multicast session / MRB configuration. In some of these embodiments, the first data may also include a MAC-related scheduling / DRX configuration. Furthermore, in some embodiments, the first data may include one or more multicast PTM configurations.

[0153] Process 1200 may include sending a first transmission to the UE at 1206. Specifically, the base station may send the first transmission to the UE via RRC dedicated signaling when the UE is in connected mode.

[0154] Process 1200 may include generating a second transmission at 1208, the second transmission indicating second data for multicast PTM configuration. Specifically, the base station may generate the second transmission indicating second data for multicast PTM configuration. The second transmission may include MCCH message 712 ( Figure 7 ), MCCH message 812( Figure 8 ), MCCH message 914( Figure 9 ) and / or MCCH message 1008 ( Figure 10 ) features.

[0155] In some embodiments, the second data may include a PTM PDCCH / PDSCH configuration in a CFR. In some embodiments, the second data may include a MAC-related scheduling / DRX configuration. Furthermore, in some embodiments, the second data may include a configuration index. The configuration index may indicate a multicast PTM configuration to be implemented from one or more multicast PTM configurations provided by the first data.

[0156] Process 1200 may include sending a second transmission to the UE at 1210. Specifically, the base station may send the second transmission to the UE via the MCCH. The first data and the second data may be used to configure a multicast PTM configuration for the UE.

[0157] In some embodiments, process 1200 may also include generating reconfiguration information related to MAC-related scheduling / DRX configuration. Specifically, the base station may generate reconfiguration information related to MAC-related scheduling / DRX configuration. The base station may send the reconfiguration information related to MAC-related scheduling / DRX configuration via RRC dedicated signaling. The reconfiguration information may cause the UE to reconfigure the multicast PTM configuration.

[0158] In some embodiments, process 1200 may also include generating reconfiguration information related to MAC-related scheduling / DRX configuration. Specifically, the base station may generate reconfiguration information related to MAC-related scheduling / DRX configuration. In some embodiments, the reconfiguration information may include DRX offset information. The base station may transmit the reconfiguration information related to MAC-related scheduling / DRX configuration via the MCCH. The reconfiguration information may cause the UE to reconfigure the multicast PTM configuration.

[0159] In some embodiments, process 1200 may further include determining a first portion of MAC-related scheduling / DRX reconfiguration information to be sent via RRC dedicated signaling and a second portion of MAC-related scheduling / DRX reconfiguration information to be sent via MCCH. Specifically, the base station may determine the first portion of MAC-related scheduling / DRX reconfiguration information to be sent via RRC dedicated signaling and the second portion of MAC-related scheduling / DRX reconfiguration information to be sent via MCCH. The base station may generate a third transmission indicating the first portion of MAC-related scheduling / DRX reconfiguration information to be sent via RRC dedicated signaling and the second portion of MAC-related scheduling / DRX reconfiguration information to be sent via MCCH. The base station may send the third transmission to the UE via RRC dedicated signaling.

[0160] Although Figure 12 The order of the operations of process 1200 may be implied, but it should be understood that in other embodiments, the operations may be performed in a different order and / or one or more of the operations may be performed simultaneously. Additionally, it should be understood that in other embodiments, one or more additional operations may be included in process 1200 and / or one or more of the operations may be omitted.

[0161] Figure 13 An example process 1300 for operating a UE according to some embodiments is illustrated. For example, the process 1300 may be performed by a UE (such as the first UE 304 ( Figure 3 ), the second UE 306 ( Figure 3 ), the third UE 308 ( Figure 3 ), UE 702( Figure 7 ), UE 802( Figure 8 ), UE 902( Figure 9 ),UE 1002( Figure 10 ) and / or UE 1700( Figure 17 )) to execute.

[0162] Process 1300 may include receiving a transmission at 1302 that provides MCCH configuration information. Specifically, the UE may receive the transmission via UE-specific signaling that provides MCCH configuration information. The transmission may include RRC dedicated message 706 ( Figure 7 ), RRC dedicated message 808 ( Figure 8 ), RRC dedicated message 908 ( Figure 9 ) and / or RRC dedicated message 1012 ( Figure 10 ) features.

[0163] In some embodiments, the MCCH configuration may include an indication of the MCCH configuration. In some embodiments, the transmission may include a first transmission. Furthermore, in some embodiments, the MCCH configuration information may include first MCCH configuration information. In some of these embodiments, the first MCCH configuration information may include a first portion of the MCCH configuration. Furthermore, in some embodiments, the first MCCH configuration information may include one or more MCCH configurations.

[0164] Process 1300 may include determining an MCCH configuration for the MCCH of the UE at 1304. Specifically, the UE may determine the MCCH configuration for the MCCH of the UE based on the MCCH configuration information. In some embodiments, determining the MCCH configuration may include identifying an indication of the MCCH configuration in the MCCH configuration information.

[0165] Process 1300 may include implementing MCCH configuration for the MCCH at 1306. Specifically, the UE may implement MCCH configuration for the MCCH.

[0166] Process 1300 may include receiving a multicast PTM configuration at 1308. Specifically, the UE may receive the multicast PTM configuration for an inactive state of the UE via an MCCH configured with the MCCH configuration.

[0167] Process 1300 may include implementing multicast PTM configuration at 1310. Specifically, the UE may implement multicast PTM configuration for an inactive state.

[0168] In some embodiments, process 1300 may further include receiving a second transmission that provides second MCCH configuration information. Specifically, the UE may receive the second transmission via broadcast signaling that provides second MCCH configuration information. The second transmission may include MCCH message 712 ( Figure 7 ), MCCH message 812( Figure 8 ), MCCH message 914( Figure 9 ) and / or MCCH message 1008 ( Figure 10). The second MCCH configuration information may include a second part of the MCCH configuration. In addition, the MCCH configuration may be further determined based on the second MCCH configuration information.

[0169] In some embodiments, process 1300 may include receiving a second transmission that provides an MCCH configuration index. Specifically, the UE may receive the second transmission via a scheduling DCI that provides an MCCH configuration index. The second transmission may include message 912 ( Figure 9 In some embodiments, the MCCH configuration index may be used for PDSCH reception. In some embodiments, determining the MCCH configuration may include determining the MCCH configuration from one or more MCCH configurations based on the MCCH configuration index.

[0170] Although Figure 13 The order of the operations of process 1300 may be implied, but it should be understood that in other embodiments, the operations may be performed in a different order and / or one or more of the operations may be performed simultaneously. Additionally, it should be understood that in other embodiments, one or more additional operations may be included in process 1300 and / or one or more of the operations may be omitted.

[0171] Figure 14 An example process 1400 for operating a base station according to some embodiments is illustrated. For example, the process 1400 may be performed by a base station, such as base station 302 ( Figure 3 ), base station 704 ( Figure 7 ), base station 804 ( Figure 8 ), base station 904 ( Figure 9 )、Base Station 1004( Figure 10 ) and / or gNB 1800( Figure 18 )) to execute.

[0172] Process 1400 may include sending a request for the UE to transition to a connected mode at 1402. Specifically, the base station may send a request to the UE for the UE to transition to a connected mode.

[0173] Process 1400 may include generating a transmission at 1404 that provides MCCH configuration information. Specifically, the base station may generate a transmission that provides MCCH configuration information. The transmission may include RRC dedicated message 706 ( Figure 7 ), RRC dedicated message 808 ( Figure 8 ), RRC dedicated message 908 ( Figure 9 ) and / or RRC dedicated message 1012 ( Figure 10 ) features.

[0174] In some embodiments, the MCCH configuration information may include an indication of an MCCH configuration for the MCCH. In some embodiments, the transmission may include a first transmission. In addition, in some embodiments, the MCCH configuration information may include first MCCH configuration information. In some embodiments, the first MCCH configuration information may include a first portion of an MCCH configuration. In some embodiments, the first MCCH configuration information may include one or more MCCH configurations.

[0175] The process 1400 may include sending the transmission to the UE at 1406. Specifically, the base station may send the transmission to the UE via UE-specific signaling for configuring the MCCH configuration associated with the MCCH configuration information for the UE's MCCH. The transmission may include an RRC dedicated message 706 ( Figure 7 ), RRC dedicated message 808 ( Figure 8 ), RRC dedicated message 908 ( Figure 9 ) and / or RRC dedicated message 1012 ( Figure 10 ) features.

[0176] Process 1400 may include determining a multicast PTM configuration at 1408. Specifically, the base station may determine a multicast PTM configuration for an inactive state of the UE.

[0177] The process 1400 may include sending a multicast PTM configuration to the UE at 1410. Specifically, the base station may send the multicast PTM configuration to the UE via the MCCH to configure the multicast PTM configuration for the UE. Figure 7 ), MCCH message 812( Figure 8 ), MCCH message 914( Figure 9 ) and / or MCCH message 1008 ( Figure 10 )'s features in sending a multicast PTM configuration.

[0178] In some embodiments, process 1400 may also include generating a second transmission that provides second MCCH configuration information. Specifically, the base station may generate a second transmission that provides second MCCH configuration information. The second transmission may include message 912 ( Figure 9 The second MCCH configuration information may include a second part of the MCCH configuration. The base station may send a second signal to the UE to configure the MCCH.

[0179] In some embodiments, process 1400 may also include generating a second transmission that provides an MCCH configuration index. Specifically, the base station may generate a second transmission that provides an MCCH configuration index. The second transmission may include message 912 ( Figure 9 ) features. The MCCH configuration index indicates an MCCH configuration from one or more MCCH configurations from the first MCCH configuration information. In some embodiments, the MCCH configuration index may be used for PDSCH reception. The base station may send a second transmission to the UE via a scheduling DCI.

[0180] Although Figure 14 The order of the operations of process 1400 may be implied, but it should be understood that in other embodiments, the operations may be performed in a different order and / or one or more of the operations may be performed simultaneously. Additionally, it should be understood that in other embodiments, one or more additional operations may be included in process 1400 and / or one or more of the operations may be omitted.

[0181] Figure 15 An example process 1500 for operating a UE according to some embodiments is illustrated. For example, the process 1500 may be performed by a UE (such as the first UE 304 ( Figure 3 ), the second UE 306 ( Figure 3 ), the third UE 308 ( Figure 3 ), UE 702( Figure 7 ), UE 802( Figure 8 ), UE 902( Figure 9 ),UE 1002( Figure 10 ) and / or UE 1700( Figure 17 )) to execute.

[0182] The process 1500 may include receiving security information for multicast PTM configuration at 1502. Specifically, the UE may receive security information for multicast PTM configuration for an inactive state of the UE via RRC dedicated signaling. Figure 7 ), RRC dedicated message 808 ( Figure 8 ), RRC dedicated message 908 ( Figure 9 ) and / or RRC dedicated message 1012 ( Figure 10 ) in sending one or more of the characteristics of the receiving device.

[0183] In some embodiments, the security information may include a value associated with the hash. Furthermore, in some embodiments, the security information may include information associated with the signature. In some embodiments, the security information may include a security key. In some of these embodiments, the security key may be specific to an MBS session. In some of these embodiments, the security key may be applicable to multiple MBS sessions.

[0184] The process 1500 may include receiving an indication of a multicast PTM configuration at 1504. Specifically, the UE may receive an indication of a multicast PTM configuration with security protection via the MCCH. Figure 7 ), MCCH message 812( Figure 8 ), MCCH message 914( Figure 9 ) and / or MCCH message 1008 ( Figure 10 ) in the transmission of one or more of the features of the multicast PTM configuration.

[0185] In some embodiments, the indication of the multicast PTM configuration with security protection may include a hashed indication of the multicast PTM configuration generated via a hash. Furthermore, in some embodiments, the indication of the multicast PTM configuration with security protection may include a signed indication of the multicast PTM configuration signed via a signature. In some embodiments, the indication of the multicast PTM configuration with security protection may include an indication of encryption or integrity protection of the multicast PTM configuration.

[0186] Process 1500 may include utilizing the security information to determine the multicast PTM configuration at 1506. Specifically, the UE may utilize the security information to determine the multicast PTM configuration with security protection.

[0187] In some embodiments, utilizing the security information to determine the multicast PTM configuration may include utilizing the value to determine the multicast PTM configuration based on a hash indication of the multicast PTM configuration. In some embodiments, utilizing the security information to determine the multicast PTM configuration may include utilizing information associated with the signature to determine the multicast PTM configuration based on a signed indication of the multicast PTM configuration. Additionally, in some embodiments, utilizing the security information to determine the multicast PTM configuration may include utilizing a security key to determine the multicast PTM configuration based on an encryption or integrity protection indication of the multicast PTM configuration.

[0188] Process 1500 may include implementing multicast PTM configuration at 1508. Specifically, the UE may implement multicast PTM configuration for an inactive state.

[0189] Although Figure 15 The order of the operations of process 1500 may be implied, but it should be understood that in other embodiments, the operations may be performed in a different order and / or one or more of the operations may be performed simultaneously. Additionally, it should be understood that in other embodiments, one or more additional operations may be included in process 1500 and / or one or more of the operations may be omitted.

[0190] Figure 16An example process 1600 for operating a base station according to some embodiments is illustrated. For example, process 1100 may be performed by a base station, such as base station 302 ( Figure 3 ), base station 704 ( Figure 7 ), base station 804 ( Figure 8 ), base station 904 ( Figure 9 )、Base Station 1004( Figure 10 ) and / or gNB 1800( Figure 18 )) to execute.

[0191] Process 1600 may include sending a request for the UE to transition to a connected mode at 1602. Specifically, the base station may send a request to the UE to transition to a connected mode.

[0192] The process 1600 may include sending security information for multicast PTM configuration in 1604. Specifically, when the UE is in connected mode, the base station may send security information for multicast PTM configuration for the inactive state of the UE to the UE via RRC dedicated signaling. Figure 7 ), RRC dedicated message 808 ( Figure 8 ), RRC dedicated message 908 ( Figure 9 ) and / or RRC dedicated message 1012 ( Figure 10 )'s features when sending security information.

[0193] In some embodiments, the security information may include a value associated with the hash. In some embodiments, the security information may include information associated with the signature. Furthermore, in some embodiments, the security information may include a security key. In some of these embodiments, the security key may be specific to an MBS session. In some of these embodiments, the security key may be applicable to multiple MBS sessions.

[0194] Process 1600 may include generating an indication of a multicast PTM configuration with security protection at 1606. Specifically, the base station may generate an indication of a multicast PTM configuration with security protection associated with security information applied to the indication. Figure 7 ), MCCH message 812( Figure 8 ), MCCH message 914( Figure 9 ) and / or MCCH message 1008 ( Figure 10 )'s features in sending an indication of the multicast PTM configuration.

[0195] In some embodiments, the indication of the multicast PTM configuration with security protection may include a hashed indication of the multicast PTM configuration generated via a hash. In some embodiments, the indication of the multicast PTM configuration with security protection may include a signed indication of the multicast PTM configuration signed via a signature. Furthermore, the indication of the multicast PTM configuration with security protection may include an indication of encryption or integrity protection of the multicast PTM configuration.

[0196] Process 1600 may include sending an indication of the multicast PTM configuration to the UE at 1608. Specifically, the base station may send an indication of the multicast PTM configuration to the UE. The UE may utilize the security information to determine the multicast PTM configuration with security protection.

[0197] Although Figure 16 The order of the operations of process 1600 may be implied, but it should be understood that in other embodiments, the operations may be performed in a different order and / or one or more of the operations may be performed simultaneously. Additionally, it should be understood that in other embodiments, one or more additional operations may be included in process 1600 and / or one or more of the operations may be omitted.

[0198] Figure 17 An example of an example UE 1700 according to some embodiments is illustrated. UE 1700 can be any mobile or non-mobile computing 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 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 smartwatch), or a loose IoT device. In some embodiments, UE 1700 can be a RedCap UE or an NR-Light UE.

[0199] UE 1700 may include a processor 1704, RF interface circuitry 1708, memory / storage 1712, a user interface 1716, sensors 1720, driver circuitry 1722, a power management integrated circuit (PMIC) 1724, antenna structures 1726, and a battery 1728. The components of UE 1700 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 17 The block diagram is intended to show a simplified view of some of the components of the UE 1700. 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 implementations.

[0200] Components of UE 1700 may be coupled to various other components via one or more interconnects 1732, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connection, etc., that allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0201] The processor 1704 may include processor circuitry, such as, for example, a baseband processor circuit (BB) 1704A, a central processing unit circuit (CPU) 1704B, and a graphics processor unit circuit (GPU) 1704C. The processor 1704 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 the memory / storage 1712 to cause the UE 1700 to perform operations as described herein. For example, the processor 1704 may include interface circuitry coupled to the BB 1704A, the CPU 1704B, and / or the GPU 1704C, which may communicatively couple the BB 1704A, the CPU 1704B, and / or the GPU 1704C to the memory / storage 1712 to retrieve computer-executable instructions (and other operations) from the memory / storage 1712 for execution.

[0202] In some embodiments, the baseband processor circuit 1704A can access the communication protocol stack 1136 in the memory / storage device 1712 to communicate over a 3GPP-compatible network. Generally speaking, the baseband processor circuit 1704A can access the communication protocol stack to perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and to perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer. In some embodiments, PHY layer operations can additionally / alternatively be performed by components of the RF interface circuit 1708.

[0203] The baseband processor circuit 1704A may generate or process baseband signals or waveforms that carry information in 3GPP-compliant networks. In some embodiments, the waveforms used 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.

[0204] The memory / storage 1712 may include one or more non-transitory computer-readable media containing instructions (e.g., the communication protocol stack 1136) that are executable by one or more processors in the processor 1704 to cause the UE 1700 to perform the various operations described herein. The memory / storage 1712 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1700. In some embodiments, some of the memory / storage 1712 may be located on the processor 1704 itself (e.g., L1 cache and L2 cache), while other memory / storage 1712 may be external to the processor 1704 but accessible via a memory interface. The memory / storage 1712 may include any suitable volatile or non-volatile memory, such as, but 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 any other type of memory device technology.

[0205] The RF interface circuit 1708 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allow the UE 1700 to communicate with other devices via a radio access network. The RF interface circuit 1708 may include various components arranged in a transmit path or a receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, and the like.

[0206] In the receive path, the RFEM receives the radiated signal from the air interface via the antenna structure 1726 and further filters and amplifies the signal (using a low-noise amplifier). The signal is provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 1704.

[0207] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides an RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before radiating the signal across the air interface via the antenna 1726.

[0208] In various embodiments, the RF interface circuit 1708 may be configured to send / receive signals in a manner compatible with NR access technology.

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

[0210] User interface circuitry 1716 includes various input / output (I / O) devices designed to enable a user to interact with UE 1700. User interface 1716 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual component for accepting input, including, in particular, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a trackpad, a touch screen, a microphone, a scanner, or a headset. Output device circuitry includes any physical or virtual component for displaying or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, including, in particular, one or more simple visual outputs / indicators (e.g., binary state indicators such as light emitting diodes (LEDs) and multi-character visual outputs, or more complex outputs such as a display device or touch screen (e.g., a liquid crystal display (LCD), an LED display, a quantum dot display, a projector, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of UE 1700.

[0211] Sensors 1720 may include devices, modules, or subsystems designed to detect events or changes in their environment and communicate information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a 3-axis accelerometer, 3-axis gyroscope, or magnetometer; a fluid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; and the like.

[0212] The driver circuit 1722 may include software and hardware elements that operate to control specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1700. The driver circuit 1722 may include various drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 1700. For example, the driver circuit 1722 may include a display driver for controlling and enabling access to a display device, a touch screen driver for controlling and enabling access to a touch screen interface, a sensor driver for obtaining sensor readings from the sensor circuit 1720 and controlling and enabling access to the sensor circuit 1720, a driver for obtaining actuator positioning of an electromechanical component or controlling and enabling access to an electromechanical component, a camera driver for controlling and enabling access to an embedded image capture device, and an audio driver for controlling and enabling access to one or more audio devices.

[0213] The PMIC 1724 may manage power provided to various components of the UE 1700. Specifically, with respect to the processor 1704, the PMIC 1724 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0214] In some embodiments, the PMIC 1724 may control or otherwise be part of various power-saving mechanisms for the UE 1700. For example, if a platform UE is in the RRC_Connected state, in which it remains 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). During this state, the UE 1700 may power down for short intervals, thereby saving power. If there is no data traffic activity for an extended period, the UE 1700 may transition to the RRC_Idle state, in which the UE is disconnected from the network and does not perform operations such as channel quality feedback or handovers. The UE 1700 enters a very low-power state and performs paging, in which the UE periodically wakes up again to listen to the network, and then powers down again. The UE 1700 may not receive data in this state; to receive data, the UE must transition back to the RRC_Connected state. An additional power saving mode can disable the device from the network for periods exceeding the paging interval (from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered down. Any data transmitted during this time will incur significant latency, assuming that latency is acceptable.

[0215] Battery 1728 can power UE 1700, but in some examples, UE 1700 can be installed and deployed in a fixed location and can have a power source coupled to the power grid. Battery 1728 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 1728 can be a typical lead-acid automobile battery.

[0216] Figure 18 An example gNB 1800 is illustrated in accordance with some embodiments. The gNB 1800 may include a processor 1804, RF interface circuitry 1808, core network (CN) interface circuitry 1812, memory / storage circuitry 1816, and antenna structures 1826.

[0217] The components of gNB 1800 may be coupled to various other components via one or more interconnects 1828.

[0218] The processor 1804, RF interface circuitry 1808, memory / storage circuitry 1816 (including communication protocol stack 1810), antenna structures 1826, and interconnects 1828 may be similar to those described with respect to FIG. Figure 17 Like-named elements are shown and described.

[0219] The CN interface circuitry 1812 can provide connectivity to a core network (e.g., a 5th Generation Core Network (5GC) using a 5GC-compatible network interface protocol, such as a Carrier Ethernet protocol or some other suitable protocol). Network connectivity can be provided to / from the gNB 1800 via optical fiber or wireless backhaul. The CN interface circuitry 1812 can include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1812 can include multiple controllers for providing connectivity to other networks using the same or different protocols.

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

[0221] For one or more embodiments, at least one of the components described in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, or methods described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the preceding figures may be configured to operate in accordance with one or more of the embodiments described below. For another example, circuitry associated with the UE, base station, network element, etc. described above in conjunction with one or more of the preceding figures may be configured to operate in accordance with one or more of the embodiments described below in the Examples section.

[0222] Example

[0223] In the following sections, additional exemplary embodiments are provided.

[0224] Embodiment 1 may include a method of operating a user equipment (UE), the method comprising: receiving a first transmission via radio resource control (RRC) dedicated signaling, the first transmission providing first data for a multicast point-to-multipoint (PTM) configuration for an inactive state of the UE; receiving a second transmission via a multicast / broadcast service control channel (MCCH), the second transmission providing second data for the multicast PTM configuration for the inactive state; determining the multicast PTM configuration for the inactive state based at least in part on the first data and the second data; and implementing the multicast PTM configuration for the inactive state.

[0225] Embodiment 2 may include the method of embodiment 1, wherein the first data comprises a multicast session / multicast radio bearer (MRB) configuration, and the second data comprises a physical layer (PHY) configuration related to an inactive multicast PTM transmission.

[0226] Embodiment 3 may include the method of embodiment 2, wherein the first data further includes a medium access control (MAC) configuration related to a multicast PTM for an inactive state.

[0227] Embodiment 4 may include the method of embodiment 2, wherein the second data further includes medium access control (MAC) related scheduling / discontinuous reception (DRX) configuration.

[0228] Embodiment 5 may include the method according to embodiment 2, further comprising: receiving reconfiguration information related to medium access control (MAC) related scheduling / discontinuous reception (DRX) configuration via RRC dedicated signaling; and reconfiguring the multicast PTM configuration based at least in part on the reconfiguration information.

[0229] Embodiment 6 may include the method according to embodiment 2, further comprising: receiving reconfiguration information related to medium access control (MAC) related scheduling / discontinuous reception (DRX) configuration via the MCCH; and reconfiguring the multicast PTM configuration based at least in part on the reconfiguration information.

[0230] Embodiment 7 may include the method of embodiment 6, wherein the reconfiguration information causes reconfiguration of the MAC DRX configuration of the UE.

[0231] Embodiment 8 may include a method according to embodiment 2, the method further comprising receiving, via RRC dedicated signaling, an indication of a first part of medium access control (MAC) related scheduling / discontinuous reception (DRX) reconfiguration information to be received via RRC dedicated signaling and a second part of the MAC related scheduling / DRX reconfiguration information to be received via MCCH.

[0232] Embodiment 9 may include the method of embodiment 1, wherein the first data comprises one or more multicast PTM configurations, and the second data comprises a configuration index indicating the multicast PTM configuration to be implemented from the one or more multicast PTM configurations.

[0233] Embodiment 10 may include a method according to embodiment 1, wherein the first data includes one or more multicast PTM configurations, the second data includes a configuration index, and the method further includes: determining that the configuration index does not correspond to any multicast PTM configuration of the one or more multicast PTM configurations; initiating an RRC recovery procedure to transition to a connected mode; when in the connected mode, providing an indication that the configuration index does not correspond to any multicast PTM configuration of the one or more multicast PTM configurations; and receiving an indication of the multicast PTM configuration to be implemented based at least in part on providing the indication that the configuration index does not correspond to any multicast PTM configuration of the one or more multicast PTM configurations.

[0234] Embodiment 11 may include a method of operating a base station, the method comprising: sending a request to a user equipment (UE) to transition the device to a connected mode; generating a first transmission, the first transmission indicating first data for a multicast point-to-multipoint (PTM) configuration for an inactive state of the UE; when the UE is in the connected mode, sending the first transmission to the UE via radio resource control (RRC) dedicated signaling; generating a second transmission, the second transmission indicating second data for the multicast PTM configuration; and sending the second transmission to the UE via a multicast / broadcast service control channel (MCCH), the first data and the second data being used to configure the multicast PTM configuration for the UE.

[0235] Embodiment 12 may include a method according to embodiment 11, wherein the first data includes a multicast session / multicast radio bearer (MRB) configuration, and the second data includes a PTM physical downlink control channel (PDCCH) / physical downlink shared channel (PDSCH) configuration in crest factor reduction (CFR).

[0236] Embodiment 13 may include the method of embodiment 12, wherein the first data further includes a medium access control (MAC) related scheduling / discontinuous reception (DRX) configuration.

[0237] Embodiment 14 may include the method of embodiment 12, wherein the second data includes a medium access control (MAC) related scheduling / discontinuous reception (DRX) configuration.

[0238] Embodiment 15 may include the method according to embodiment 12, the method further comprising: generating reconfiguration information related to medium access control (MAC) related scheduling / discontinuous reception (DRX) configuration; and sending the reconfiguration information related to the MAC related scheduling / DRX configuration via RRC dedicated signaling, the reconfiguration information being used to enable the UE to reconfigure the multicast PTM configuration.

[0239] Embodiment 16 may include the method according to embodiment 12, the method further comprising: generating reconfiguration information related to medium access control (MAC) related scheduling / discontinuous reception (DRX) configuration; and sending the reconfiguration information related to the MAC related scheduling / DRX configuration via the MCCH, the reconfiguration information being used to enable the UE to reconfigure the multicast PTM configuration.

[0240] Embodiment 17 may include the method of embodiment 16, wherein the reconfiguration information includes DRX offset information.

[0241] Embodiment 18 may include the method according to embodiment 12, the method further comprising: determining a first part of medium access control (MAC) related scheduling / discontinuous reception (DRX) reconfiguration information to be sent via RRC dedicated signaling and a second part of the MAC related scheduling / DRX reconfiguration information to be sent via the MCCH; generating a third transmission, the third transmission indicating the first part of the MAC related scheduling / DRX reconfiguration information to be sent via RRC dedicated signaling and the second part of the MAC related scheduling / DRX reconfiguration information to be sent via the MCCH; and sending the third transmission to the UE via RRC dedicated signaling.

[0242] Embodiment 19 may include the method of embodiment 11, wherein the first data comprises one or more multicast PTM configurations, and the second data comprises a configuration index indicating the multicast PTM configuration to be implemented from the one or more multicast PTM configurations.

[0243] Embodiment 20 may include a method of operating a user equipment (UE), the method comprising: determining an MCCH configuration for an MCCH of the UE based at least in part on multicast / broadcast service control channel (MCCH) configuration information; implementing the MCCH configuration for the MCCH; receiving a multicast point-to-multipoint (PTM) configuration for an inactive state of the UE via the MCCH configured with the MCCH configuration; and implementing the multicast PTM configuration for the inactive state.

[0244] Embodiment 21 may include the method of embodiment 20, wherein the MCCH configuration information includes an indication of the MCCH configuration, and determining the MCCH configuration includes identifying the indication of the MCCH configuration in the MCCH configuration information.

[0245] Embodiment 22 may include a method according to embodiment 20, wherein the transmission includes a first transmission, wherein the MCCH configuration information includes first MCCH configuration information, wherein the first MCCH configuration information includes a first part of the MCCH configuration, and wherein the method further includes: receiving a second transmission via broadcast signaling, the second transmission providing second MCCH configuration information, wherein the second MCCH configuration information includes a second part of the MCCH configuration, and wherein the MCCH configuration is further determined at least in part based on the second MCCH configuration information.

[0246] Embodiment 23 may include a method according to embodiment 20, wherein the transmission includes a first transmission, wherein the MCCH configuration information includes first MCCH configuration information, wherein the first MCCH configuration information includes one or more MCCH configurations, and wherein the method further includes: receiving a second transmission via scheduling downlink control information (DCI), the second transmission providing an MCCH configuration index, wherein determining the MCCH configuration includes determining the MCCH configuration from the one or more MCCH configurations based at least in part on the MCCH configuration index.

[0247] Embodiment 24 includes the method of embodiment 23, wherein the MCCH configuration index is for physical downlink shared channel (PDSCH) reception.

[0248] Embodiment 25 may include the method of embodiment 20, further comprising receiving a transmission via UE-specific signaling, the transmission providing MCCH configuration information.

[0249] Embodiment 26 may include a method of operating a base station, the method comprising: sending a request to a user equipment (UE) to transition the UE to a connected mode; generating a transmission that provides multicast / broadcast service control channel (MCCH) configuration information; sending the transmission to the UE via UE-dedicated signaling to configure the MCCH of the UE using an MCCH configuration associated with the MCCH configuration information; determining a multicast point-to-multipoint (PTM) configuration for an inactive state of the UE; and sending the multicast PTM configuration to the UE via the MCCH to configure the UE using the multicast PTM configuration.

[0250] Embodiment 27 may include the method of embodiment 26, wherein the MCCH configuration information includes an indication of an MCCH configuration for the MCCH.

[0251] Embodiment 28 may include a method according to embodiment 26, wherein the transmission includes a first transmission, wherein the MCCH configuration information includes first MCCH configuration information, wherein the first MCCH configuration information includes a first part of the MCCH configuration, and wherein the method further includes: generating a second transmission, the second transmission providing second MCCH configuration information, wherein the second MCCH configuration information includes a second part of the MCCH configuration; and sending the second transmission to the UE for configuring the MCCH.

[0252] Embodiment 29 may include a method according to embodiment 26, wherein the transmission includes a first transmission, wherein the MCCH configuration information includes first MCCH configuration information, wherein the first MCCH configuration information includes one or more MCCH configurations, and wherein the method further includes: generating a second transmission, the second transmission providing an MCCH configuration index, the MCCH configuration index indicating the MCCH configuration from the one or more MCCH configurations; and sending the second transmission to the UE via scheduling downlink control information (DCI).

[0253] Embodiment 30 may include the method of embodiment 29, wherein the MCCH configuration index is for MCCH reception.

[0254] Embodiment 31 may include a method of operating a user equipment (UE), the method comprising: receiving security information for a multicast point-to-multipoint (PTM) configuration for an inactive state of the UE via radio resource control (RRC) dedicated signaling; receiving an indication of the multicast PTM configuration with security protection via a multicast / broadcast service control channel (MCCH); utilizing the security information to determine the multicast PTM configuration with the security protection; and implementing the multicast PTM configuration for the inactive state.

[0255] Embodiment 32 may include a method according to embodiment 31, wherein the security information includes a value associated with a hash, wherein the indication of the multicast PTM configuration with security protection includes a hash indication of the multicast PTM configuration generated via the hash, and wherein determining the multicast PTM configuration using the security information includes using the value to determine the multicast PTM configuration based on the hash indication of the multicast PTM configuration.

[0256] Embodiment 33 may include a method according to embodiment 31, wherein the security information includes information related to the signature, wherein the indication of the multicast PTM configuration with security protection includes a signed indication of the multicast PTM configuration signed via the signature, and wherein determining the multicast PTM configuration using the security information includes determining the multicast PTM configuration based on the signed indication of the multicast PTM configuration using the information related to the signature.

[0257] Embodiment 34 may include a method according to embodiment 31, wherein the security information includes a security key, wherein the indication of the multicast PTM configuration with security protection includes an encryption or integrity protection indication of the multicast PTM configuration, and wherein determining the multicast PTM configuration using the security information includes determining the multicast PTM configuration based on the encryption or integrity protection indication of the multicast PTM configuration using the security key.

[0258] Embodiment 35 may include the method of embodiment 34, wherein the security key is specific to a multicast and broadcast service (MBS) session.

[0259] Embodiment 36 may include the method of embodiment 34, wherein the security key is used for multiple MBS sessions.

[0260] Embodiment 37 may include a method of operating a base station, the method comprising: sending a request to a user equipment (UE) to transition the UE to a connected mode; when the UE is in the connected mode, sending security information for a multicast point-to-multipoint (PTM) configuration for an inactive state of the UE to the UE via radio resource control (RRC) dedicated signaling; generating an indication of the multicast PTM configuration with security protection, the security protection being associated with the security information applied to the indication; and sending the indication of the multicast PTM configuration to the UE, the UE determining the multicast PTM configuration using the security information through the security protection.

[0261] Embodiment 38 may include the method of embodiment 37, wherein the security information comprises a value associated with a hash, and wherein the indication of the multicast PTM configuration with security protection comprises a hash indication of the multicast PTM configuration generated via the hash.

[0262] Embodiment 39 may include the method of embodiment 37, wherein the security information includes information related to a signature, and wherein the indication of the multicast PTM configuration with security protection includes a signed indication of the multicast PTM configuration signed via the signature.

[0263] Embodiment 40 may include the method of embodiment 37, wherein the security information comprises a security key, and wherein the indication of the multicast PTM configuration with security protection comprises an indication of encryption or integrity protection of the multicast PTM configuration.

[0264] Embodiment 41 may include the method of embodiment 40, wherein the security key is specific to a multicast and broadcast service (MBS) session.

[0265] Embodiment 42 may include the method of embodiment 40, wherein the security key is used for multiple MBS sessions.

[0266] Example 43 may include an apparatus comprising means for performing one or more elements of the method described in or related to any one of Examples 1-42, or any other method or process described herein.

[0267] Embodiment 44 may include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described or related to any one of Embodiments 1 to 42 or any other method or process described herein.

[0268] Embodiment 45 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Embodiments 1-42, or any other method or process described herein.

[0269] Example 46 may include methods, techniques, or processes as described or related to any one of Examples 1 to 42, or portions or components thereof.

[0270] Example 47 may include a device comprising: one or more processors; and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process as described or related to any one of Examples 1 to 42, or a portion thereof.

[0271] Embodiment 48 may include signals as described or in connection with any one of embodiments 1 to 42, or portions or components thereof.

[0272] Embodiment 49 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or composition thereof, as described or associated with any of Embodiments 1 to 42 or otherwise described in this disclosure.

[0273] Embodiment 50 may include a signal encoded with data as described or related to any of Embodiments 1 to 42 or otherwise described in this disclosure, or a portion or component thereof.

[0274] Embodiment 51 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message, or a portion or composition thereof, as described or associated with any of Embodiments 1 to 42 or otherwise described in this disclosure.

[0275] Embodiment 52 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process described in accordance with or in connection with any one of Embodiments 1 to 42, or portions thereof.

[0276] Embodiment 53 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process as described or related to any one of embodiments 1 to 42, or a portion thereof.

[0277] Embodiment 54 may include signals in a wireless network as shown and described herein.

[0278] Embodiment 55 may include a method of communicating in a wireless network as shown and described herein.

[0279] Embodiment 56 may include a system for providing wireless communications as shown and described herein.

[0280] Embodiment 57 may include an apparatus for providing wireless communications as shown and described herein.

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

[0282] 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. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed, cause a device to: determining a multicast / broadcast service control channel (MCCH) configuration for the MCCH of the device based on MCCH configuration information; implementing the MCCH configuration for the MCCH; identifying an inactive state multicast point-to-multipoint (PTM) configuration for the device received via the MCCH configured with the MCCH configuration; and The multicast PTM configuration for the inactive state is implemented.

2. One or more computer-readable media according to claim 1, wherein: The MCCH configuration information includes an indication of the MCCH configuration; and Determining the MCCH configuration includes identifying the indication of the MCCH configuration in the MCCH configuration information.

3. The one or more computer-readable media of claim 1 , wherein the MCCH configuration information comprises first MCCH configuration information, and wherein the instructions, when executed, further cause the device to: identifying a first transmission, the first transmission comprising the first MCCH configuration information, wherein the first MCCH configuration information comprises a first portion of the MCCH configuration; and A second transmission is identified that provides second MCCH configuration information received via broadcast signaling, wherein the second MCCH configuration information includes a second portion of the MCCH configuration, and wherein the MCCH configuration is further determined based at least in part on the second MCCH configuration information.

4. The one or more computer-readable media of claim 1 , wherein the MCCH configuration information comprises first MCCH configuration information, and wherein the instructions, when executed, further cause the device to: Identifying a first transmission, the first transmission comprising the first MCCH configuration information, wherein the first MCCH configuration information comprises one or more MCCH configurations; and A second transmission is identified that provides an MCCH configuration index received via scheduling downlink control information (DCI), wherein determining the MCCH configuration comprises determining the MCCH configuration from the one or more MCCH configurations based at least in part on the MCCH configuration index.

5. The one or more computer-readable media of claim 4, wherein the MCCH configuration index is for physical downlink shared channel (PDSCH) reception.

6. The one or more computer-readable media of claim 1 , wherein the instructions, when executed, further cause the device to: The identification is sent, where the sending includes the MCCH configuration information received via UE-specific signaling.

7. The one or more computer-readable media of claim 1 , wherein the instructions, when executed, further cause the device to: identifying reconfiguration information related to a medium access control (MAC) related scheduling / discontinuous reception (DRX) configuration received via the MCCH; and The multicast PTM configuration is reconfigured based at least in part on the reconfiguration information.

8. The one or more computer-readable media of claim 7, wherein the reconfiguration information comprises DRX offset information.

9. A method comprising: sending a request to a device to transition the device to a connected mode; generating a transmission providing multicast / broadcast service control channel (MCCH) configuration information; sending, via UE-dedicated signaling, to the device to configure an MCCH for the device using the MCCH configuration associated with the MCCH configuration information; determining an inactive multicast point-to-multipoint (PTM) configuration for the device; as well as The multicast PTM configuration is sent to the device via the MCCH to configure the device with the multicast PTM configuration.

10. The method of claim 9, wherein the MCCH configuration information comprises an indication of the MCCH configuration for the MCCH.

11. The method of claim 9, wherein the transmitting comprises a first transmitting, wherein the MCCH configuration information comprises first MCCH configuration information, wherein the first MCCH configuration information comprises a first part of the MCCH configuration, and wherein the method further comprises: generating a second transmission, the second transmission providing second MCCH configuration information, wherein the second MCCH configuration information includes a second portion of the MCCH configuration; as well as The second transmission is sent to the device for configuring the MCCH.

12. The method of claim 9, wherein the transmitting comprises a first transmitting, wherein the MCCH configuration information comprises first MCCH configuration information, wherein the first MCCH configuration information comprises one or more MCCH configurations, and wherein the method further comprises: generating a second transmission, the second transmission providing an MCCH configuration index, the MCCH configuration index indicating the MCCH configuration from the one or more MCCH configurations; as well as The second transmission is sent to the device via scheduling downlink control information (DCI). The method according to claim 12 , wherein the MCCH configuration index is used for MCCH reception.

14. The method according to claim 9, further comprising: generating reconfiguration information related to medium access control (MAC) related scheduling / discontinuous reception (DRX) configuration; as well as The reconfiguration information related to the MAC-related scheduling / DRX configuration is sent via the MCCH, where the reconfiguration information is used to enable the device to reconfigure the multicast PTM configuration. The method according to claim 14 , wherein the reconfiguration information comprises DRX offset information.

16. A baseband processor, the baseband processor being configured to: identifying a transmission comprising multicast / broadcast service control channel (MCCH) configuration information received via user equipment (UE) dedicated signaling; determining an MCCH configuration for the MCCH of the apparatus based on the MCCH configuration information; implementing the MCCH configuration for the MCCH; identifying an inactive state multicast point-to-multipoint (PTM) configuration for the apparatus received via the MCCH configured with the MCCH configuration; and The multicast PTM configuration for the inactive state is implemented.

17. The baseband processor of claim 16, wherein: The MCCH configuration information includes an indication of the MCCH configuration; and Determining the MCCH configuration includes identifying the indication of the MCCH configuration in the MCCH configuration information.

18. The baseband processor of claim 16, wherein the transmission comprises a first transmission, wherein the MCCH configuration information comprises first MCCH configuration information, wherein the first transmission comprises the first MCCH configuration information, wherein the first MCCH configuration information comprises a first portion of the MCCH configuration, and wherein the baseband processor is further configured to: A second transmission is identified that provides second MCCH configuration information received via broadcast signaling, wherein the second MCCH configuration information includes a second portion of the MCCH configuration, and wherein the MCCH configuration is further determined based at least in part on the second MCCH configuration information.

19. The baseband processor of claim 16, wherein the transmission comprises a first transmission, wherein the MCCH configuration information comprises first MCCH configuration information, wherein the first transmission comprises the first MCCH configuration information, wherein the first MCCH configuration information comprises one or more MCCH configurations, and wherein the baseband processor is further configured to: A second transmission is identified that provides an MCCH configuration index received via scheduling downlink control information (DCI), wherein determining the MCCH configuration comprises determining the MCCH configuration from the one or more MCCH configurations based at least in part on the MCCH configuration index.

20. The baseband processor of claim 19, wherein the MCCH configuration index is for physical downlink shared channel (PDSCH) reception.

Images