Multicast reception in inactive state

Abstract

The 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

Technical Field

[0001] This application relates to the field of wireless technology, and more specifically to multicast reception in an inactive state. Background Technology

[0002] The 3GPP network specifies that base stations multicast signals to one or more designated user equipment (UEs). The base station configures these designated UEs to receive multicast signals, while other UEs not designated to receive multicast signals are not configured to do so. Attached Figure Description

[0003] Figure 1 Examples of network environments based on some implementation schemes are provided.

[0004] Figure 2 Examples of multicast or broadcast service (MBS) configuration instances based on some implementation schemes are shown.

[0005] Figure 3 It is a signaling diagram based on some implementation schemes.

[0006] Figure 4 This is another signaling diagram based on some implementation schemes.

[0007] Figure 5 This is another signaling diagram based on some implementation schemes.

[0008] Figure 6 It is a change instruction field based on some implementation schemes.

[0009] Figure 7 This is another signaling diagram based on some implementation schemes.

[0010] Figure 8 This is another signaling diagram based on some implementation schemes.

[0011] Figure 9 This is another signaling diagram based on some implementation schemes.

[0012] Figure 10 It is based on the operation process / algorithm structure of some implementation schemes.

[0013] Figure 11 It is another operational process / algorithm structure based on some implementation schemes.

[0014] Figure 12 It is another operational process / algorithm structure based on some implementation schemes.

[0015] Figure 13 It is another operational process / algorithm structure based on some implementation schemes.

[0016] Figure 14 These are example UEs based on some implementation schemes.

[0017] Figure 15 These are example base stations based on some implementation schemes. Detailed Implementation

[0018] 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 drawings. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrases “A / B” and “A or B” refer to (A), (B), or (A and B); the phrase “(A)B” refers to (B) or (A and B), i.e., A is optional. And the phrase “based on A” means “at least partially based on A,” for example, it can be “based only on A” or it can be “partially based on A.”

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

[0020] As used herein, the term "circuit" refers to, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-chips (SoCs)), digital signal processors (DSPs), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functionalities. 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 that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0021] As used herein, the term "processor circuit" means a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data; a part of, or including, a circuit 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 also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, 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 procedures).

[0022] As used herein, the term "interface circuit" refers to circuitry that enables the exchange of information between two or more components or devices, a portion thereof, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, or network interface cards.

[0023] As used herein, the term "user equipment" or "UE" refers to equipment of a remote user that has radio communication capabilities and can describe network resources in a communication network. Furthermore, the term "user equipment" or "UE" may be considered synonymous and may refer to 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. Additionally, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

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

[0025] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components 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 supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources that a computer device / system can access via a communication network. The term "system resource" can refer to any kind of shared entity providing a service and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0026] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to transmit 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 indicating a means or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices for the purpose of transmitting and receiving information.

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

[0028] The term "connection" can refer to an established signaling relationship between two or more elements at a common communication protocol layer through a communication channel, link, interface, or reference point.

[0029] 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 networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.

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

[0031] Figure 1 A network environment 100 according to some embodiments is illustrated. Network environment 100 may include UE 104 and base station 108. In some embodiments, base station 108 may provide one or more radio access cells, such as serving cell 112, through which UE 104 can communicate with a cellular network. Base station 108 may be part of a radio access network (RAN) coupled to a core network (CN) 116. As used herein, references to a network may include RAN or CN 116.

[0032] UE 104 and base station 108 can communicate via an air interface compatible with fifth-generation (5G) NR (latest) system standards provided by technical specifications such as the 3rd Generation Partnership Project (3GPP).

[0033] UE 104 may include a Radio Resource Control (RRC) state machine, which performs operations related to various RRC procedures, including, for example, paging, RRC connection establishment, RRC connection reconfiguration, and RRC connection release. The RRC state machine may be controlled by protocol processing circuitry (see, for example...). Figure 14 The processor 1404 is implemented.

[0034] The RRC state machine can transition UE 104 to one of several RRC states (or "modes"), including, for example, a connected state (RRC connected), an inactive state (RRC inactive), and an idle state (RRC idle). When UE 104 first camps on a serving cell, it can begin in RRC idle, either after UE 104 is enabled or after cell reselection from another cell. To participate in active communications, the RRC state machine can transition UE 104 from RRC idle to RRC connected by executing an RRC setup procedure to establish a logical connection with the base station, such as an RRC connection. In an RRC connection, UE 104 can be configured with at least one signaling radio bearer (SRB) for signaling interaction (e.g., control messages) with the base station; and one or more data radio bearers (DRBs) for data transmission. When UE 104 is less actively involved in network communications, the RRC state machine can use an RRC release procedure to transition UE 104 from RRC connected to RRC inactive. Compared to an RRC connection, an RRC inactive state allows UE 104 to reduce power consumption, but will still allow UE 104 to quickly switch back to an RRC connection to deliver application data or signaling messages.

[0035] In some implementations, the base station may provide multicast or broadcast services (MBS) to UEs (such as UE 104) in serving cell 112. MBS can be used for a variety of use cases, including, for example, public safety and mission-critical applications, vehicle-to-everything (V2X) applications, Internet Protocol Television (IPTV), live video, software delivery over wireless networks, and Internet of Things (IoT) applications.

[0036] The 3GPP Release 17 (Rel-17) standard only specifies multicast for UEs in RRC connected state. However, this may be detrimental to some MBS use cases, such as the provision of mission-critical services. Furthermore, keeping the UE in RRC connected state at all times may not be power efficient. Therefore, supporting multicast reception for UEs in RRC inactive state may be beneficial.

[0037] To properly support MBS reception for UEs in an RRC inactive state, several aspects need to be considered. For example, it may be desirable for UEs in an RRC inactive state to receive updated point-to-multipoint (PTM) configurations to facilitate continuous MBS transmission reception. Furthermore, for UEs receiving MBS transmissions in an RRC inactive state, both mobility and state transitions may need to be considered.

[0038] In some implementations, after the network establishes an MBS multicast session with the UE, the network can activate the MBS multicast session when there is data to be sent, and deactivate the MBS multicast session during periods when it is not expected to send a certain amount or type of data. The operation of MBS multicast session activation / deactivation for a UE in an RRC inactive state (which may also be referred to as an inactive UE) can be described as follows.

[0039] For MBS multicast session activation, group paging can be used to provide MBS multicast session activation notification. New indications can be added to each Temporary Mobile Group Identifier (TMGI) in the group paging. Upon receiving the MBS multicast session activation notification, an inactive UE with a valid PTM configuration can begin monitoring multicast control channel (MCCH) transmissions using the corresponding Group Radio Network Temporary Identifier (G-RNTI), which is used to schedule MBS transmissions on the Physical Downlink Shared Channel (PDSCH). If the UE cannot obtain a valid PTM configuration, it will initiate RRC connection recovery to transition to an RRC connected state and obtain a valid PTM configuration.

[0040] In some implementations, the network can use the MCCH to send an MC session deactivation notification. Upon receiving the MC session deactivation notification, an inactive UE can remain in an RRC inactive state and stop using the corresponding G-RNTI to monitor the MCCH. One of two options can be used to provide PTM configuration for inactive multicast reception. In the first option, the network can provide PTM configuration in an RRC release with a suspendConfig message, which can be used to transition the UE to an RRC inactive state. In the second option, PTM configuration can be provided via the MCCH. If the network does not provide detailed PTM configuration in the RRC release message, the UE can obtain the PTM configuration via the MCCH channel.

[0041] The network can notify UEs of multicast MBS PTM configuration changes using a change notification mechanism similar to that described in 3GPP Technical Specifications (TS) 38.300 v17.5.0 (2023-06-30) and TS 38.331 v17.5.0 (2023-07-01) for Rel-17 broadcast MBS configuration changes via MCCH. If the network implements a PTM configuration change, it can provide indication of the change by scheduling downlink control information (DCI) on the MCCH carrying the PTM configuration.

[0042] Figure 2 An example MBS configuration instance 200 according to some implementation schemes is illustrated. MBS configuration instance 200 can be used to configure UE 104 to receive MBS transmissions sent by base station 108.

[0043] MBS configuration instance 200 is represented by a signaling diagram that illustrates the transmissions that can be exchanged between UE 104 and base station 108 to configure UE 104 for receiving MBS transmissions from base station 108. Figure 2 Example information elements that can be exchanged as part of MBS configuration instance 200 according to some implementation schemes are illustrated.

[0044] In the illustrated implementation, UE 104 may be configured to receive MBS transmissions from base station 108, as indicated by 206. However, UE 104 may not be able to process these MBS transmissions from base station 108 until UE 104 is correctly configured to receive MBS transmissions. Therefore, a configuration procedure can be performed to configure UE 104 to receive and process MBS transmissions.

[0045] In some implementations, a two-step MBS configuration acquisition operation can be performed on UE 104 in an RRC connected / inactive / idle state. For example, the process for configuring UE 104 to receive MBS transmissions from base station 108 may involve two acquisition steps for UE 104.

[0046] At position 208, UE 104 can receive a System Information Broadcast (SIB) message that includes MCCH configuration (MCCH-Config). The SIB can be an SIB. x ,in x This is, for example, an integer from 1 to 21. MCCH-Config can be an Information Element (IE) that provides information to be used to configure UE 104 to receive and process transmitted data via MCCH. For example, the MCCH-Config IE may include a repeat period and offset indication corresponding to the MCCH, a window start time slot indication corresponding to the MCCH, a window duration indication corresponding to the MCCH, or a modification period indication corresponding to the MCCH. UE 104 can then receive MCCH transmissions at 210 based on the MCCH-Config.

[0047] In the first transmission of MCCH transmission 210, base station 108 may transmit the Physical Downlink Control Channel (PDCCH) at 214 to schedule the second transmission of MCCH transmission 210. The PDCCH may be addressed to the MCCH-RNTI in the MCCH search space. In the second transmission, base station 108 may transmit the MBS multicast configuration at 216 via MCCH / PDSCH at 216. The second transmission 216 may include an IE that provides configuration for UE 104 to receive and process data transmitted from base station 108 via MBS transmission. The IE may include a session information list, a neighboring cell list, a configured PTM list, a multicast traffic channel (MTCH) configuration, and / or a mapping window list.

[0048] The session information list may include session ID, RNTI, broadcast list, scheduling information, neighbor cell indication, configuration index, or mapping window index. The neighbor cell list may include the physical cell ID or carrier frequency of neighboring cells. The PTM configuration list may include a PTM start duration timer indication, a PTM activity timer indication, a PTM Hybrid Automatic Repeat Request (HARQ) round-trip time (RTT) downlink (DL) timer indication, a PTM long cycle start offset indication, or a PTM timeslot offset indication. The MTCH configuration may include a PDSCH configuration list, a time-domain allocation list for PDSCH, a rate matching mode for adding or modifying list indications, a modulation and decoding scheme (MCS) table, or an overhead indication. The mapping window list may indicate the period offset of the mapping window to be used for the synchronization signal block (SSB) to be transmitted by base station 108.

[0049] UE 104 can use MBS multicast configuration to receive one or more MBS transmissions 218 from base station 108.

[0050] Figure 3 Signaling diagram 300 illustrates the validity and change notification of MCCH information according to some implementation schemes. This signaling diagram may include the DCI of the PDCCH that schedules the MCCH, where the MCCH provides the MBS configuration used by UE 104 to receive various MBS multicast sessions. Signaling diagram 300 shows three MBS multicast sessions; however, it should be understood that UE 104 may be configured for a subset of these MBS multicast sessions.

[0051] Within an MCCH modification period, the same MCCH information can be sent multiple times based on a repeat period configuration. Changes to the MCCH information can occur at the boundaries of the MCCH modification period.

[0052] In some implementations, a notification mechanism can be used to provide MCCH change notifications to announce changes to MCCH information due to the start / stop / change of a broadcast session or modification of neighboring cell information. The notification design can include a 2-bit bitmap in the MCCH scheduling DCI, for example, "XY". The "X" bit can be used to indicate the start of a new MBS service, and the "Y" bit can be used to indicate a change to the PTM configuration.

[0053] When UE 104 receives a change notification, it can obtain the updated MCCH within the same MCCH modification period during which the notification was transmitted. Before UE 104 obtains the new MCCH information, UE 104 can apply the previously obtained MCCH information.

[0054] When the MBS multicast session is deactivated, the UE operation for MTCH reception / monitoring is explicit; that is, the UE does not need to monitor G-RNTI or receive MTCH. However, when the MBS multicast session is deactivated, the UE operation for MCCH monitoring still needs to be further clarified. According to some implementation schemes, for Figure 4 Signaling diagram 400 and Figure 5 Signaling diagram 500 describes two options for defining UE operations.

[0055] In signaling diagram 400, base station 108 can deactivate the MBS multicast session by sending an RRC release message with an MBS multicast session deactivation indication at 404. With this option, UE 104 can continue monitoring the MCCH while the MBS multicast session is deactivated. Therefore, even during the deactivation mode of the MBS multicast session, UE 104 can still receive the MCCH DCI sent by base station 108. Base station 108 can send a paging message with an MBS activation indication at 408, and UE 104 can enter the activation phase of the MBS multicast session. UE 104 can then receive MBS transmissions via the MTCH based on a valid PTM configuration, even if that PTM configuration changes during the inactive phase of the MC session.

[0056] While this option can be beneficial for providing UE 104 with updated PTM configuration, it may be inefficient from a UE power perspective, especially when no PTM configuration change has occurred or when the PTM configuration change is for an MBS multicast session that UE 104 has not yet subscribed to.

[0057] exist Figure 5 In signaling diagram 500, base station 108 can deactivate the MBS multicast session by sending an RRC release message with an MBS multicast session deactivation indication at 504. With this option, UE 104 may not monitor the MCCH when the MBS multicast session is deactivated. Therefore, UE 104 may miss PTM configuration changes that occur when base station 108 sends an MCCH DCI with a change bit set to "1" and subsequently sends a new PTM configuration via the MCCH at 508. Base station 108 can send a paging message with an MBS activation indication at 512, and UE 104 can enter the active mode of the MBS multicast session. However, since the UE missed the PTM configuration change while in deactivation mode, if UE 104 does not have a valid PTM configuration for the activated MBS multicast session, the UE can initiate an RRC recovery procedure at 516.

[0058] Various aspects of this disclosure provide power-saving techniques for avoiding UE monitoring of MCCH scheduling / reception when there are no PTM configuration changes associated with the MBS multicast session configured for the UE. Three aspects are described below. These aspects are not mutually exclusive. For example, a concept from one aspect can be combined with concepts from one or more of the other aspects.

[0059] In the first aspect, UE 104 can save power during MCCH data reception by introducing MCCH change indication with finer granularity.

[0060] Secondly, when the MBS multicast session is deactivated, UE 104 can save power during MCCH monitoring by relaxing the UE requirements for monitoring the MCCH.

[0061] Thirdly, UE 104 can save power by monitoring the MCCH only when the MBS multicast session is active. After receiving the MBS multicast session activation notification, UE 104 begins receiving MBS transmissions via the MTCH when it obtains a valid PTM configuration.

[0062] These aspects will be described in further detail in this article.

[0063] As briefly described above, the first aspect includes using finer-grained MCCH change indications to save UE power during MCCH data reception. In this regard, the MCCH DCI may include change indications specific to a single MBS multicast session or a set of MBS multicast sessions. This change indication may be referred to as a session-level change indication. The set of MBS multicast sessions may be a subset of the total number of MBS multicast sessions provided by base station 108. When UE 104 receives a session-level change indication, the UE may subsequently only need to obtain PTM configuration when the change relates to the MBS multicast session configured at UE 104.

[0064] In some implementations, the session-level change indication can be provided in the DCI, such as, for example, DCI format 4_0. If the DCI includes cyclic redundancy check (CRC) scrambled by MCCH-RNTI, then UE 104 can interpret one or more bits of that DCI as a session-level change indication.

[0065] Figure 6 An example is shown of a field 600 that can provide multiple session-level change indications according to some embodiments. Field 600 is shown as having 14 bits; however, in other embodiments, the field may have a different number of bits. Figure 6Each bit position indicated by the index can include a single bit to provide a session-level change indication (C-ind) for an MBS multicast session or set of MBS multicast sessions. For example, a bit value of "0" can indicate that the corresponding MBS multicast session (set) has not changed, while a bit value of "1" can indicate that the corresponding MBS multicast session (set) has changed.

[0066] The bit position in field 600 can be mapped to an MBS multicast session through any of a variety of options. For example, in the first option, the network can use RRC signaling to configure the mapping between the MBS multicast session and the bit position. For example, the network can provide... M:1 Mapping, where M Each MBS multicast session is mapped to a single bit location. Therefore, the numerical value... M The number of MBS multicast sessions within a subset can be defined. For example, consider MBS multicast sessions 1 and 2 mapped to index 0. If the C-ind of index 0 is "1", the PTM configuration corresponding to at least one MBS multicast session in MBS multicast session 1 or 2 will be changed.

[0067] In the second option, you can use 1:1 The mapping assigns MBS multicast sessions to positions in ascending (or descending) order. For example, if MBS multicast sessions #1 / 5 / 9 are configured in a cell, these MBS multicast sessions can be mapped to indices 0 / 1 / 2 respectively. Therefore, if the PTM configuration is changed for MBS multicast session #5, but not for MBS multicast sessions #1 and #9, the C-ind values ​​for indices 0, 1, and 2 can be 0, 1, and 0 respectively.

[0068] In the third option, MBS multicast session bit positioning can be accomplished by mapping the MBS multicast session number to a bit position with a matching index number. 1:1 Mapping. For example, MBS multicast session #0 is mapped to index #0, MBS multicast session #1 is mapped to index #1, and so on.

[0069] As briefly described above, in the second aspect of this disclosure, when the MBS multicast session is deactivated, the UE requirements for monitoring the MCCH can be relaxed to save power in the MCCH monitoring section. This can be based on the requirements for... Figure 7 and Figure 8 Complete this task using one or more of the following options described below.

[0070] Figure 7 This is signaling diagram 700 based on some implementation schemes. Signaling diagram 700 includes eight MCCH modification periods.

[0071] At 704, UE 104 can detect a deactivation event, for example, via a command sent through the MCCH. UE 104 can then enter the deactivation mode of the MBS multicast session (the MBS multicast session is deactivated). When the MBS multicast session is deactivated, UE 104 can... N MCCH is monitored during each modification period. (Value) N This can be a predefined integer in the 3GPP TS, or configured by the network in, for example, an RRC release message or an SIB. As shown in the figure, N=2 Furthermore, UE 104 can monitor the MCCH every MCCH modification period, for example, at 708 and 712.

[0072] At 716, UE 104 can detect the activation event and enter the active mode of the MBS multicast session (the MBS multicast session is activated). When the MBS multicast session is active, UE 104 can monitor the MCCH during each MCCH modification period, for example, at 720 and 724.

[0073] Figure 8 This is signaling diagram 800 based on some implementation schemes. Signaling diagram 800 includes eight MCCH modification periods for the deactivation mode of MBS multicast sessions. Figure 8 MCCH monitoring can be based on the paging time (PO) 804 defined for UE 104. PO 804 is shown in MCCH modification period B.

[0074] In some implementations, UE 104 can be located before / after the position of PO 804. M Monitor MCCH during the MCCH modification period. Values M This can be a predefined integer in the 3GPP TS, or configured by the network in, for example, an RRC release message or an SIB. As shown in the figure, M=1 Furthermore, UE 104 can monitor the MCCH at location 808 (corresponding to MCCH modification period A) or location 812 (corresponding to MCCH modification period C). In some implementations, the number of MCCH modification periods monitored before location PO 804 (e.g., M This can differ from the number of MCCH modification periods monitored after that location (e.g., M' ).

[0075] In some implementations, UE 104 may monitor the MCCH during a modification period including PO 804, for example, at 816 (corresponding to MCCH modification period B). This could be before / after the location of PO 804. MMonitoring MCCH during the MCCH modification period can supplement or replace it.

[0076] In some implementation schemes, for Figure 7 and Figure 8 The described MCCH monitoring behaviors can be applied together. For example, UE 104 can monitor the MCCH in various combinations of the following: each N The MCCH modification period, before the PO M The MCCH modification period, after PO. M One (or M’ The MCCH modification period for a single PO or the MCCH modification period for a PO.

[0077] In another option of the third aspect of this disclosure, UE 104 may not monitor the MCCH if the network indicates that the inactive PTM configuration has not changed. This indication may be sent to UE 104 via the MCCH. In this option, the network may disable UE monitoring of the MCCH when UE 104 is in an RRC inactive state and the MBS multicast session is deactivated. UE 104 may apply the inactive PTM configuration provided in RRC Reset to inactive multicast reception before UE 104 later establishes a connection with the same cell.

[0078] In another option of the third aspect of this disclosure, the network may indicate, for example, the presence of a potential PTS configuration change in the Early Paging Indication (PEI) during the associated paging cycle. UE 104 may use this indication as a prompt to begin monitoring the MCCH. Monitoring may be performed during each MCCH modification period, or within a subset of MCCH modification periods discussed in conjunction with other embodiments described herein.

[0079] As briefly described above, in the third aspect of this disclosure, UE 104 can be configured to monitor the MCCH only when an MBS multicast session is active. For Figure 9 This describes that aspect.

[0080] Figure 9 Signaling diagram 900 illustrates the concept of a third aspect of this disclosure according to some implementation schemes.

[0081] At point 904, base station 108 can deactivate the MBS multicast session by sending an RRC release message with an MBS multicast session deactivation indication. In this respect, UE 104 may not monitor the MCCH when the MBS multicast session is inactive.

[0082] At 908, UE 104 can receive a paging message with an MBS multicast session activation notification, and UE 104 can enter the active mode of the MBS multicast session. After receiving the paging message, UE 104 can begin monitoring the MCCH to obtain the latest valid PTM configuration. At 912, UE 104 can receive the MCCH DCI with the change bit set to "1" from base station 108, and subsequently receive the new PTM configuration via the MCCH. Upon receiving the valid PTM configuration, UE 104 can begin receiving MTCH transmissions.

[0083] In some implementations, a time window (T) can be defined within which UE 104 will receive a valid PTM configuration. If UE 104 fails to acquire a valid PTM configuration within the time window (T), UE 104 can declare failure. The length of the time window (T) can be set to be equal to one or more MCCH modification periods. In some implementations, this length can be predefined by 3GPP TS or configured by the network.

[0084] In some implementations, UE 104 may declare a PTM configuration reception failure if one or more of the following conditions are detected: A first condition can be detected if UE 104 cannot acquire the MCCH. For example, UE 104 does not receive the MCCH DCI at 908. A second condition can be detected if UE 104 acquires the MCCH but does not acquire a valid PTM configuration. For example, UE 104 receives the MCCH DCI at 908 but cannot correctly receive or decode the PTM configuration via the MCCH, or although it receives the PTM configuration, it does not contain any configuration associated with an active MBS multicast session.

[0085] When a PTM configuration reception failure is declared, UE 104 can operate according to one or more of the following options. In the first option, when the number of detected failures reaches a predetermined threshold, UE 104 can initiate an RRC recovery procedure. This threshold can be predefined by 3GPP TS or configured by the network. In the second option, UE 104 can log the failure in a failure log stored in memory and remain in an RRC inactive state. UE 104 can report this failure log to the network when it subsequently transitions to an RRC connected state.

[0086] Figure 10 This is an operation flow / algorithm structure 1000 based on some implementation schemes. For example, the operation flow / algorithm structure 1000 can be executed by a UE (such as UE 104) or its components (e.g., processor 1404).

[0087] The operation flow / algorithm structure 1000 may include, at 1004, receiving an MCCH DCI with a change indication for the MBS multicast session and scheduling information for the PTM configuration associated with the MBS multicast session. The change indication may be an MBS session-level change indication, which indicates whether a particular MBS multicast session (set) has a change to the associated PTM configuration.

[0088] The MCCH DCI may include a change indicator field with one or more bits. Each bit may represent a change indication for a specific MBS multicast session (set). The mapping of bit positions to MBS multicast sessions (sets) may be pre-configured by the 3GPP TS or dynamically configured by the network (e.g., via RRC signaling). In some implementations, bit indices may be mapped to MBS multicast session (set) in ascending or descending order. In other implementations, bit indices may be mapped to matching MBS multicast session (set) indices; for example, bit index #0 may be mapped to MBS multicast session #0.

[0089] The operation flow / algorithm structure 1000 may further include: at 1008, determining that an MBS multicast session associated with the MCCH DCI change indication is configured at the UE. Thus, the UE can determine that the MCCH DCI indication represents a PTM configuration change for one of the MBS multicast sessions configured for the UE.

[0090] The operation flow / algorithm structure 1000 may also include: at 1012, obtaining the PTM configuration. The PTM configuration can be obtained by receiving the MCCH, which carries the PTM configuration scheduled by the MCCH DCI received at 1004.

[0091] Figure 11 This is an operation flow / algorithm structure 1100 based on some implementation schemes. For example, the operation flow / algorithm structure 1100 can be executed by a UE (such as UE 104) or its components (e.g., processor 1404).

[0092] The operation flow / algorithm structure 1100 may include detecting a deactivation event at 1104. The deactivation event may be based on command signaling from the network.

[0093] The operation flow / algorithm structure 1100 may also include: at 1108, entering the deactivation mode of the MBS multicast session. In deactivation mode, the UE may not receive MTCH transmissions.

[0094] The operation flow / algorithm structure 1100 may further include: at 1112, when in the deactivation mode of an MBS multicast session, monitoring the MCCH within a subset of the MCCH modification period. In some implementations, the subset of the MCCH modification period includes each event occurring when in the deactivation mode. N MCCH modification period. Value N It can be an integer greater than 1, which can be predefined by the network in, for example, RRC or SIB signaling or signaled.

[0095] In some implementations, a subset is selected based on the UE's PO. For example, the UE may monitor one or more MCCH modification periods before the MO, monitor MCCH modification periods including the PO, or monitor one or more MCCH modification periods after the PO.

[0096] In some implementations, the UE can receive a PEI in the DCI. The PEI can indicate a potential PTM configuration change in the paging cycle associated with the PEI. The UE can then monitor a subset of MCCH modification periods based on the indication in the PEI.

[0097] Figure 12 This is an operation flow / algorithm structure 1200 according to some implementation schemes. For example, the operation flow / algorithm structure 1200 can be executed by a UE (such as UE 104) or its components (e.g., processor 1404).

[0098] The operation flow / algorithm structure 1200 may include: at 1204, detecting a deactivation event. The deactivation event may be based on command signaling from the network.

[0099] The operation flow / algorithm structure 1200 may further include: at 1208, receiving an indication of the static state of the PTM configuration. In some implementations, the indication of the static state of the PTM configuration may be provided via the MCCH. The static state of the PTM configuration may imply that the PTM configuration will not change (or at least is not expected to change) when the UE is in deactivation mode.

[0100] The operation flow / algorithm structure 1200 may also include: at 1212, entering the deactivation mode of the MBS multicast session. This can be based on a deactivation event.

[0101] The operation procedure / algorithm structure 1200 may also include: at 1216, when in deactivation mode, abandoning MCCH monitoring. The UE may apply the PTM configuration provided in the RRC release message to inactive reception before it later establishes a connection with the same cell.

[0102] Figure 13This is an operation flow / algorithm structure 1300 based on some implementation schemes. For example, the operation flow / algorithm structure 1300 can be executed by a UE (such as UE 104) or its components (e.g., processor 1404).

[0103] The operation process / algorithm structure 1300 may include: at 1304, entering the activation mode of the MBS multicast session.

[0104] The operation flow / algorithm structure 1300 may further include: at 1308, determining that no valid PTM configuration was acquired within the time window after entering the activation mode. In some implementations, if the UE detects that it failed to acquire the MCCH within the time window, or acquired the MCCH within the time window but did not acquire a valid PTM configuration from the MCCH, it can be determined that no valid PTM configuration was acquired.

[0105] The operation process / algorithm structure 1300 may also include: at 1312, declaring failure based on the determination that no valid PTM configuration was obtained within the time window.

[0106] In some implementations, if the UE determines the number of declared failure thresholds, the UE can initiate an RRC recovery procedure to transition to the RRC connected state. While in the RRC connected state, the UE can acquire a valid PTM configuration.

[0107] Detected failures can be logged in a failure log, which can then be reported to the network. Failure log reporting can be periodic or event-based, for example, reporting when the failure log reaches a predetermined number of failures.

[0108] Although Figures 10 to 13 This may imply the order of operations; however, it should be understood that in other embodiments, these operations may be performed in a different order, or one or more of these operations may be performed simultaneously. Additionally, it should be understood that in other embodiments, the operation flow / algorithm structure may include one or more additional operations, or one or more of these operations may be omitted.

[0109] Figure 14 Example UE 1400 is illustrated according to some implementation schemes. UE 1400 can be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (e.g., microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, inventory sensors, voltmeters / ammeters, actuators, etc.), video surveillance / monitoring devices (e.g., cameras, camcorders, etc.), wearable devices (e.g., smartwatches), and loosely coupled IoT devices.

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

[0111] The components of UE 1400 can be coupled to various other components via one or more interconnects 1432, which can represent any type of interface, input / output, bus (local, system, or extended), transmit line, trace, optical connection, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

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

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

[0114] The baseband processor circuit 1404A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0115] Memory / storage device 1412 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 1436) that can be executed by one or more processors in processor 1404 to cause UE 1400 to perform the various operations described herein. Memory / storage device 1412 includes any type of volatile or non-volatile memory that can be distributed throughout UE 1400. In some embodiments, some memory / storage devices in memory / storage device 1412 may be located on processor 1404 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 1412 are external to processor 1404 but accessible via a memory interface. Memory / storage device 1412 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.

[0116] RF interface circuitry 1408 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows UE 1400 to communicate with other devices via a radio access network. RF interface circuitry 1408 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0117] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna structure 1426, and continue to filter and amplify the signal (using a low-noise amplifier). The signal can be provided to the receiver of the transceiver, which down-converts the RF signal into a baseband signal that is provided to the baseband processor of processor 1404.

[0118] In the transmission path, the transceiver's transmitter up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM can then amplify the RF signal using a power amplifier before it is radiated across the air interface via antenna structure 1426.

[0119] In various implementations, the RF interface circuit 1408 can be configured to transmit / receive signals in a manner compatible with NR access technologies.

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

[0121] User interface 1416 includes various input / output (I / O) devices designed to enable user interaction with UE 1400. User interface 1416 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual components for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, or a headset. Output device circuitry includes any physical or virtual components for displaying information 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, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators, such as light-emitting diodes (LEDs) and multi-character visual outputs, or more complex outputs, such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.)), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 1400.

[0122] Sensor 1420 may include devices, modules, or subsystems designed to detect events or changes in its environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEM) with 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; and so on.

[0123] The driving circuitry 1422 may include software and hardware elements that operate to control a specific device embedded in, attached to, or otherwise communicatively coupled to the UE 1400. The driving circuitry 1422 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 1400. For example, the driving circuitry 1422 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for obtaining sensor readings of sensor 1420 and controlling and allowing access to sensor 1420; a driver for obtaining actuator positions of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0124] The PMIC 1424 manages the power supplied to various components of the UE 1400. Specifically, for the processor 1404, the PMIC 1424 controls power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0125] In some implementations, the PMIC 1424 can control or otherwise be part of various power-saving mechanisms of the UE 1400. For example, if the platform UE is in the RRC_Connected state, where it remains connected to the RAN node as it anticipates receiving traffic soon, then after a period of inactivity, the platform UE can enter a state known as Discontinuous Receive Mode (DRX). During this state, the UE 1400 can power down for short intervals, thus saving power. If there is no data traffic activity during a longer period, the UE 1400 can transition to the RRC_Idle state, in which it disconnects from the network and does not perform operations such as channel quality feedback or handover. The UE 1400 enters a very low-power state and performs paging, at which point it periodically wakes up again to listen to the network and then power down again. The UE 1400 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 renders the device unusable for a period exceeding the paging interval (from seconds to hours). During this time, the device is completely unconnected to the network and may be completely powered off. Any data transmitted during this period will incur significant latency, which is assumed to be acceptable.

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

[0127] Figure 15 An example base station 1500 according to some implementation schemes is illustrated. Base station 1500 may include processor 1504, RF interface circuitry 1508, core network (CN) interface circuitry 1512, memory / storage circuitry 1516, and antenna structure 1526.

[0128] The components of base station 1500 can be coupled to various other components via one or more interconnects 1528.

[0129] The processor 1504, RF interface circuit 1508, memory / storage circuit 1516 (including communication protocol stack 1510), antenna structure 1526, and interconnect 1528 can be similar to those for... Figure 14 Similar named elements are shown and described.

[0130] The CN interface circuit 1512 can provide connectivity to a core network (e.g., a 5GC using a 5G core network (5GC) compatible network interface protocol, such as carrier Ethernet or some other suitable protocol). Network connectivity can be provided to / from base station 1500 via fiber optic or wireless backhaul. The CN interface circuit 1512 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1512 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0131] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting 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 explained to users.

[0132] For one or more embodiments, at least one of the components illustrated in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more examples below. Similarly, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more embodiments described in the Embodiments section below.

[0133] Example Further exemplary implementations are provided in the following sections.

[0134] Example 1 includes a method comprising: when in an inactive state, receiving multicast control channel (MCCH) downlink control information (DCI), the MCCH DCI having a change indication for a multicast or broadcast service (MBS) multicast session and scheduling information for downlink transmission with a point-to-multipoint (PTM) configuration associated with the MBS multicast session; determining that the MBS multicast session is configured at the UE; and based on the determination that the MBS multicast session is configured at the UE, obtaining the PTM configuration from the downlink transmission.

[0135] Example 2 includes the method according to Example 1 or some other embodiment of this document, wherein the MCCHDCI includes a change indicator field having one or more bits corresponding to one or more change indicators, and the method further includes: determining a mapping between the one or more bits and a plurality of MBS multicast sessions.

[0136] Example 3 includes the method according to Example 2 or some other embodiment of this document, the method further comprising: receiving mapping configuration information in a Radio Resource Control (RRC) signal; and determining the mapping based on the mapping configuration information.

[0137] Example 4 includes the method according to Example 2 or some other embodiment of this document, wherein the one or more bits are associated with one or more bit indices, the plurality of MBS multicast sessions are associated with a plurality of MBS multicast session indices, and determining the mapping further includes associating the one or more bit indices with the plurality of MBS multicast session indices in ascending or descending order.

[0138] Example 5 includes the method according to Example 2 or some other embodiment of this document, wherein the one or more bits include multiple bits respectively associated with multiple bit indices, the multiple MBS multicast sessions are respectively associated with multiple MBS multicast session indices, and determining the mapping further includes: associating each of the multiple bit indices with a matching MBS multicast session index among the multiple MBS multicast session indices.

[0139] Example 6 includes the method according to Example 1, wherein the change indication includes a bit associated with a plurality of MBS multicast sessions including the MBS multicast session.

[0140] Example 7 includes a method comprising: generating multicast control channel (MCCH) downlink control information (DCI), the multicast control channel downlink control information (MCCH DCI) having an MBS session-level change indication for a multicast or broadcast service (MBS) multicast session and scheduling information for downlink transmission using a point-to-multipoint (PTM) configuration associated with the MBS multicast session; and transmitting the MCCH DCI and the downlink transmission.

[0141] Example 8 includes the method according to Example 7 or some other embodiment herein, wherein the MCCHDCI includes a change indicator field having one or more bits mapped to a plurality of MBS multicast sessions, wherein each of the one or more bits corresponds to an MBS multicast session-level change indicator.

[0142] Example 9 includes a method comprising: detecting a deactivation event; entering a deactivation mode of a multicast or broadcast service (MBS) session based on the detection of the deactivation event; and monitoring the MCCH within a subset of the multicast control channel (MCCH) modification period when in the deactivation mode of the MBS multicast session.

[0143] Example 10 includes the method according to Example 9 or some other embodiment of this document, the method further comprising: when in the active mode of the MBS multicast session, monitoring the MCCH during each MCCH modification period, wherein when in the deactivated mode of the MBS multicast session, monitoring the MCCH within the subset of the MCCH modification periods comprises: when in the deactivated mode of the MBS multicast session, monitoring the MCCH every N MCCH modification periods, wherein N is an integer greater than 1.

[0144] Example 11 includes the method according to Example 10 or some other embodiment of this document, the method further comprising: receiving an indication of N in a radio resource control message or system information block.

[0145] Example 12 includes the method according to Example 9 or some other embodiment of this document, wherein the UE is configured with a paging time (PO), and the method further includes: selecting the subset based on the PO.

[0146] Example 13 includes the method according to Example 12 or some other embodiment herein, wherein, when in multicast deactivation mode, monitoring the MCCH within the subset of the MCCH modification period includes: monitoring one or more MCCH modification periods before the PO; monitoring the MCCH modification period including the PO; or monitoring at least one MCCH modification period after the PO.

[0147] Example 14 includes the method according to Example 12 or some other embodiment herein, the method further comprising: receiving an Early Paging Indication (PEI) in downlink control information; and, based on the PEI, monitoring the MCCH in the subset of the MCCH modification period in the deactivation mode.

[0148] Example 15 includes a method comprising: detecting a deactivation event; receiving from a network an indication of a static state of a point-to-multipoint (PTM) configuration; entering a deactivation mode of a multicast or broadcast service (MBS) session based on the detection of the deactivation event; and, based on the indication of the static state of the PTM configuration, abandoning monitoring of the multicast control channel (MCCH) when in the deactivation mode of the MBS multicast session.

[0149] Example 16 includes the method according to Example 15, the method further comprising: receiving an inactive PTM configuration from a radio resource control (RRC) release message from a cell; and applying the inactive PTM configuration to the MBS multicast session before entering an RRC connection state with the cell.

[0150] Example 17 includes a method comprising: entering an activation mode of a multicast or broadcast service (MBS) session; determining that no valid point-to-multipoint (PTM) configuration has been acquired within a time window after entering the activation mode; and declaring a failure based on the determination that no valid PTM configuration has been acquired within the time window.

[0151] Example 18 includes the method according to Example 17 or some other embodiment herein, wherein determining that the valid PTM configuration was not acquired within the time window includes: failing to acquire the multicast control channel (MCCH) within the time window.

[0152] Example 19 includes the method according to Example 17 or some other embodiment of this document, wherein determining that the valid PTM configuration was not obtained within the time window includes: obtaining the MCCH within the time window, and failing to obtain the valid PTM configuration via the MCCH within the time window.

[0153] Example 20 includes the method according to Example 17 or some other embodiment of this document, the method further comprising: determining a threshold number of declared failures; and initiating a Radio Resource Control (RRC) recovery procedure based on the determination of the threshold number of declared failures.

[0154] Example 21 includes the method according to Example 17 or some other embodiment of this document, the method further comprising: recording MCCH acquisition failure in a failure log.

[0155] Example 22 includes the method according to Example 21 or some other embodiment of this document, the method further comprising: reporting the failure log to the network.

[0156] Another embodiment may include an apparatus comprising one or more elements for performing the method described or associated with any of Embodiments 1 to 22 or any other method or process described herein.

[0157] Another embodiment may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein according to any one of embodiments 1 to 22.

[0158] Another embodiment may include an apparatus comprising one or more elements for performing the methods described or associated with any one of Embodiments 1 to 22 or any other methods or processes described herein.

[0159] Another embodiment may include the methods, techniques or processes described or associated with any one of embodiments 1 to 22 or any part or component thereof.

[0160] Another embodiment may include an apparatus comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform the methods, techniques or processes described or associated with any one or more of embodiments 1 to 22.

[0161] Another embodiment may include signals described or associated with any one of embodiments 1 to 22 or any part or component thereof.

[0162] Another embodiment may include datagrams, information elements, packets, frames, segments, PDUs, or messages described or associated with any one of embodiments 1 to 22 or any part or component thereof, or otherwise described in this disclosure.

[0163] Another embodiment may include a signal encoded with data as described or associated with any one of embodiments 1 to 22 or a part or component thereof, or otherwise described in this disclosure.

[0164] Another embodiment may include signals encoded as datagrams, IEs, packets, frames, segments, PDUs, or messages as described or associated with any one of embodiments 1 to 22 or any part or component thereof, or otherwise described in this disclosure.

[0165] Another embodiment 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 the methods, techniques, or processes described or associated with any one or more of embodiments 1 to 22.

[0166] Another embodiment may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform the methods, techniques, or processes described or associated with any one or a portion thereof according to Embodiments 1 to 22.

[0167] Another embodiment may include signals in a wireless network as shown and described herein.

[0168] Another embodiment may include a method for communicating in a wireless network as shown and described herein.

[0169] Another embodiment may include a system for providing wireless communication as shown and described herein.

[0170] Another embodiment may include a device for providing wireless communication as shown and described herein.

[0171] Unless otherwise expressly stated, any embodiment described above may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments is illustrative and descriptive, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from practice of various embodiments.

[0172] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed by one or more processors, cause a user equipment (UE) to: receive, while in an inactive state, a multicast control channel (MCCH) downlink control information (DCI) having a change indication for a multicast or broadcast service (MBS) multicast session and scheduling information for a downlink transmission employing a point-to-multipoint (PTM) configuration associated with the MBS multicast session; determine that the MBS multicast session is configured at the UE; and based on the determination that the MBS multicast session is configured at the UE, acquire the PTM configuration from the downlink transmission. the MCCH DCI includes a change indicator field having one or more bits corresponding to one or more change indications, and the instructions, when executed, further cause the UE to:

2. The one or more computer-readable media of claim 1, wherein, determine a mapping between the one or more bits and a plurality of MBS multicast sessions. the instructions, when executed, further cause the UE to:

3. The one or more computer-readable media of claim 1 or 2, wherein, receive mapping configuration information in a radio resource control (RRC) signal; and determine the mapping based on the mapping configuration information. the one or more bits are respectively associated with one or more bit indexes, the plurality of MBS multicast sessions are respectively associated with a plurality of MBS multicast session indexes, and to determine the mapping, the UE is further to:

4. The one or more computer-readable media of claim 1 or 2, wherein, associate the one or more bit indexes with the plurality of MBS multicast session indexes in ascending or descending order. the one or more bits include a plurality of bits respectively associated with a plurality of bit indexes, the plurality of MBS multicast sessions are respectively associated with a plurality of MBS multicast session indexes, and to determine the mapping, the UE is further to:

5. The one or more computer-readable media of claim 1 or 2, wherein, associate each bit index of the plurality of bit indexes with a matching one of the plurality of MBS multicast session indexes. the change indication includes one bit associated with a plurality of MBS multicast sessions including the MBS multicast session.

6. The one or more computer-readable media of claim 1 or 2, wherein, 7. An apparatus having processing circuitry to: generate a multicast control channel (MCCH) downlink control information (DCI) having a multicast or broadcast service (MBS) session-level change indication for a MBS multicast session and scheduling information for a downlink transmission employing a point-to-multipoint (PTM) configuration associated with the MBS multicast session; and transmit the MCCH DCI and the downlink transmission. the MCCH DCI includes a change indicator field having one or more bits mapped to a plurality of MBS multicast sessions, wherein each bit of the one or more bits corresponds to a MBS multicast session-level change indication.

8. The apparatus of claim 7, wherein, 9. A method comprising: detecting a deactivation event; ​ entering a deactivation mode for a multicast or broadcast service (MBS) session based on the detecting the deactivation event; and monitoring a multicast control channel (MCCH) within a subset of MCCH modification periods while in the deactivation mode for the MBS multicast session.

10. The method of claim 9, further comprising: monitoring the MCCH within each MCCH modification period while in an active mode for the MBS multicast session, wherein monitoring the MCCH within the subset of MCCH modification periods when in the deactivated mode of the MBS multicast session comprises monitoring the MCCH at every MCCH modification period when in the deactivated mode of the MBS multicast session, wherein the subset of MCCH modification periods is a subset of all MCCH modification periods. N wherein monitoring the MCCH within the subset of MCCH modification periods when in the deactivated mode of the MBS multicast session comprises monitoring the MCCH at every MCCH modification period when in the deactivated mode of the MBS multicast session, wherein the subset of MCCH modification periods is a subset of all MCCH modification periods. N is an integer greater than 1.

11. The method of claim 9 or 10, further comprising: receiving an indication in a radio resource control message or a system information block N of the one or more radio access technologies.

12. The method of claim 9 or 10, wherein, the UE being configured with a paging occasion (PO), and the method further comprising: selecting the subset based on the PO.

13. The method of claim 12, wherein, the monitoring the MCCH within the subset of MCCH modification periods while in the multicast deactivation mode comprises: monitoring one or more MCCH modification periods before the PO; monitoring a MCCH modification period that includes the PO; or monitoring at least one MCCH modification period after the PO.

14. The method of claim 12, further comprising: receiving a paging early indication (PEI) in downlink control information; and monitoring the MCCH within the subset of MCCH modification periods in the deactivation mode based on the PEI.

15. An apparatus, the apparatus comprising: a radio frequency (RF) interface; and processing circuitry coupled with the RF interface, the processing circuitry to: detect a deactivation event; receive an indication of a static state for a point-to-multipoint (PTM) configuration from a network of the RF interface; enter a deactivation mode for a multicast or broadcast service (MBS) session based on the detecting the deactivation event; and abandon monitoring a multicast control channel (MCCH) while in the deactivation mode for the MBS multicast session based on the indication of the static state for the PTM configuration.

16. The apparatus of claim 15, wherein, the processing circuitry further to: receive an inactive PTM configuration in a radio resource control (RRC) release message from a cell via the RF interface; and apply the inactive PTM configuration to the MBS multicast session prior to entering an RRC connected state with the cell.

17. A method, the method comprising: entering an active mode for a multicast or broadcast service (MBS) session; determining that a valid point-to-multipoint (PTM) configuration has not been acquired within a time window after entering the active mode; and declaring a failure based on the determining that the valid PTM configuration has not been acquired within the time window.

18. The method of claim 17, wherein, the determining that the valid PTM configuration has not been acquired within the time window comprises: failing to acquire a multicast control channel (MCCH) within the time window.

19. The method of claim 17 or 18, wherein, the determining that the valid PTM configuration has not been acquired within the time window comprises: acquiring a MCCH within the time window and failing to acquire the valid PTM configuration via the MCCH within the time window.

20. The method of claim 17 or 18, further comprising: determining that a threshold number of failures have been declared; and initiate a radio resource control (RRC) resume procedure based on the determination that the threshold number of failures has been declared.

21. The method of claim 17 or 18, the method further comprising: recording the failure to acquire the MCCH in a failure log.

22. The method of claim 21, the method further comprising: reporting the failure log to a network.

Images