Techniques for multicast reception during mobility by user equipment in inactive state

Abstract

This disclosure describes techniques for enabling a UE to receive a broadcast MBS session in a radio resource control (RRC) inactive state. In some examples, the UE may continue to receive the broadcast MBS session in the RRC inactive state while transitioning from a first network cell to a second network cell. The techniques for multicast reception in an inactive state may also include various methods for obtaining configuration data to enable reception of the multicast in neighboring network cells, notified of configuration changes, and discarding old configuration data. For example, a PTM configuration for a neighboring network cell may be obtained via one or more of a System Information Block (SIB), an MCCH, and dedicated RRC signaling. As such, a timer may be started with a notification of an upcoming configuration change, which upon expiration causes old configuration data to be discarded.

Description

Technical Field

[0001] The present disclosure relates generally to wireless technologies and, more particularly, to supporting multicast reception during inactive mobility. Background Art

[0002] In telecommunications, 5G is the fifth generation technology standard for broadband cellular networks. Like its predecessor, a 5G network is a cellular network in which the service area is divided into small geographical areas called network cells (or cells). The 3rd Generation Partnership Project (3GPP) is an industry alliance that develops standards for 5G. In 5G, a number of different features are supported, such as Multicast Broadcast Service (MBS). MBS is a point-to-multipoint (PTM) service in which data is transmitted from a single source entity to multiple recipients. Thus, MBS services are delivered from a signal data source (e.g., an application service provider) to multiple user equipments (UEs). MBS uses either broadcast sessions or multicast sessions to deliver content. In a broadcast MBS session, content is available to all UEs in the broadcast service area. On the other hand, in a multicast MBS session, content is available to all UEs in a multicast group. Summary of the Invention

[0003] Processes, machines, and articles of manufacture are described for supporting multicast reception during inactive mobility.It should be understood that the embodiments can be combined in any number of ways without departing from the scope of the present disclosure.

[0004] An implementation may include: receiving a multicast session of a multicast service using a user equipment (UE) that is in a radio resource control (RRC) inactive state and located in a first network cell using a first point-to-multipoint (PTM) configuration for the first network cell; determining that the UE is transitioning from the first network cell to a second network cell; and continuing to receive the multicast session of the multicast service using the UE that is in the RRC inactive state and located in the second network cell using a second PTM configuration for the second network cell.

[0005] Other processes, machines, and articles of manufacture are also described herein, which may be combined in any number of ways without departing from the scope of the present disclosure, such as with the embodiments of the summary. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The present invention is illustrated by way of example and is not limited to the figures of the accompanying drawings in which like reference numerals indicate like elements. To easily identify the discussion of any particular element or action, one or more of the most significant digits in a reference numeral refers to the figure number that first introduces the element.

[0007] Figure 1An exemplary wireless communication system in accordance with some embodiments is illustrated.

[0008] Figure 2 A base station (BS) in communication with a user equipment (UE) device is illustrated according to some embodiments.

[0009] Figure 3 An exemplary block diagram of a UE according to some embodiments is illustrated.

[0010] Figure 4 An exemplary block diagram of a BS according to some embodiments is illustrated.

[0011] Figure 5 An exemplary block diagram of cellular communication circuitry is shown in accordance with some embodiments.

[0012] Figure 6 Various aspects of a multicast session according to some embodiments are illustrated.

[0013] Figure 7 An exemplary block diagram of network messaging is illustrated in accordance with some embodiments.

[0014] Figure 8 An example logic flow for UE operation when camping in a new network cell is illustrated in accordance with some embodiments.

[0015] Figure 9 An exemplary process diagram is illustrated for continuing multicast reception in an inactive state when transitioning network cells, according to some embodiments.

[0016] Figure 10 An example process diagram for determining multicast control channel (MCCH) acquisition failure is illustrated in accordance with some embodiments.

[0017] Figure 11 A logic flow is illustrated for an exemplary technique for multicast reception in an inactive state according to some embodiments. DETAILED DESCRIPTION

[0018] Techniques for multicast reception in an inactive state are described. In the following description, numerous specific details are set forth to provide a thorough explanation of the embodiments of the present invention. However, it will be apparent to those skilled in the art that the embodiments of the present invention may be practiced without these specific details. In other instances, well-known components, structures, and techniques have not been shown in detail in order to avoid obscuring the understanding of this description.

[0019] Reference in this specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present invention. The appearance of the phrase "in one embodiment" in various places in this specification is not necessarily to the same embodiment.

[0020] In the following description and claims, the terms "coupled" and "connected," and their derivatives, may be used. It should be understood that these terms are not intended to be synonymous with each other. "Coupled" is used to indicate that two or more elements, which may or may not be in direct physical or electrical contact with each other, cooperate or interact with each other. "Connected" is used to indicate the establishment of communication between two or more elements that are coupled to each other.

[0021] The processes depicted in the following figures are performed by processing logic components that include hardware (e.g., circuitry, dedicated logic components, etc.), software (such as software running on a general-purpose computer system or a dedicated machine), or a combination of both. Although the processes are described below as operating in certain sequential order, it should be understood that some of the operations described may be performed in a different order. Furthermore, some operations may be performed in parallel rather than sequentially.

[0022] The terms "server," "client," and "device" are intended to refer generally to data processing systems and not specifically to specific form factors of a server, client, and / or device.

[0023] In general, the present disclosure describes techniques for multicast reception in an inactive state. For example, the techniques disclosed herein may be used to enable a UE to receive a broadcast MBS session in a radio resource control (RRC) inactive state. In many such examples, the UE may continue to receive the broadcast MBS session in an RRC inactive state when transitioning from a first network cell to a second network cell. The transition of the UE from a first network cell to a second network cell may be referred to as mobility. The techniques for multicast reception in an inactive state may also include various methods for obtaining configuration data to enable reception of the multicast in a neighboring network cell, being notified of configuration changes, and discarding old configuration data. For example, the PTM configuration for a neighboring network cell may be obtained via one or more of a system information block (SIB), an MCCH, and dedicated RRC signaling. As another example, a notification of an upcoming configuration change may be used to start a timer that causes the old configuration data to be discarded upon expiration. It should be understood that various aspects of telecommunication networks, capabilities, protocols and procedures related to the techniques described herein and terminology referenced herein may be found in 3GPP Technical Specifications (TSs), such as TS 23.247, TS 26.502, TS 26.517, TS 38.331 and TS 38.300.

[0024] The subject matter thus described provides numerous technical advantages. For example, the computer-based techniques of the present disclosure improve the functionality of telecommunication systems compared to conventional approaches because these techniques enable robust support for multicast reception in an inactive state, which can improve the accessibility and efficiency of telecommunication networks, reduce congestion, and provide expanded capabilities compared to conventional approaches. For example, facilitating multicast reception in an inactive state can enable available radio resources to support more UEs. As another example, UE battery life can be extended by enabling UEs to spend more time in an inactive state, rather than having to transition back to a connected state, such as to receive configuration data. Thus, the embodiments disclosed herein can be used to improve the functionality of computers and / or improve the technical fields of telecommunications and / or PTM communications.

[0025] Figure 1 A simplified exemplary wireless communication system according to some embodiments is illustrated. Note that Figure 1 The system is only one example of a possible system, and features of the present disclosure may be implemented in any of a variety of systems as desired.

[0026] As shown, the example wireless communication system includes a base station 102A that communicates with one or more user devices 106A, 106B, 106N, etc. via a transmission medium. Each user device may be referred to herein as a "user equipment" (UE) or a UE device. Therefore, user device 106 is referred to as a UE or a UE device.

[0027] Base station (BS) 102A may be a base transceiver station (BTS) or a cell site ("cellular base station") and may include hardware that enables wireless communications with UEs 106A through 106N.

[0028] The communication area (or coverage area) of a base station may be referred to as a "cell." Base station 102A and UE 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), also known as wireless communication technologies or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), and the like. It should be noted that if base station 102A is implemented in the context of LTE, it may alternatively be referred to as an 'eNodeB' or 'eNB'. It should be noted that if base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB." Next-generation eNBs (ng-eNBs) may include enhanced versions of eNBs that connect 5G UEs to a 5G core network using a 4G LTE air interface.

[0029] As shown, base station 102A may also be equipped to communicate with network 100 (e.g., a cellular service provider's core network, a telecommunications network such as a public switched telephone network (PSTN), and / or the Internet, among other possibilities). Thus, base station 102A may facilitate communication between user devices and / or between user devices and network 100. Specifically, cellular base station 102A may provide UE 106 with various telecommunications capabilities, such as voice, SMS, and / or data services. It should be understood that, in various embodiments, the term "network" may be used to collectively refer to one or more devices and components that form a telecommunications network. For example, a reference to a network that sends or receives data to or from a UE may refer to one or more portions of a core network of a cellular service provider and / or one or more base stations. In some such examples, data to be sent to a UE may be determined by a core network component and then sent to the UE via a base station.

[0030] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore provide a network of cells that can provide continuous or nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards.

[0031] Thus, although base station 102A may function as Figure 1106A-N, each UE 106 may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which may be provided by base stations 102B-N and / or any other base stations), which may be referred to as "neighboring cells." Such cells may also be capable of facilitating communications between user devices and / or between user devices and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells of any other variety of granularity of service area size. For example, in Figure 1 The base stations 102A-B illustrated in FIG may be macro cells, while the base station 102N may be a micro cell. Other configurations are also possible.

[0032] In some embodiments, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or "gNB." In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and / or to a NR core (5GC) network. Furthermore, a gNB cell may include one or more transition and reception points (TRPs). Furthermore, a UE capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0033] It should be noted that the UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). If desired, the UE 106 may also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocols. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0034] Figure 2 Illustrated in accordance with some embodiments is a user equipment 106 (e.g., one of devices 106A through 106N) in communication with a base station 102. The UE 106 may be a device with cellular communication capabilities, such as a mobile phone, handheld device, computer or tablet, or virtually any type of wireless device.

[0035] The UE 106 may include a processor configured to execute program instructions stored in a memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or in addition, the UE 106 may include a programmable hardware element, such as a field programmable gate array (FPGA) configured to perform any of the method embodiments described herein or any portion of any of the method embodiments described herein.

[0036] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, 5G NR, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), or LTE using a single shared radio and / or GSM or LTE using a single shared radio. The shared radio may be coupled to a single antenna, or may be coupled to multiple antennas (e.g., for MIMO) for performing wireless communications. Generally speaking, the radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio may implement one or more receive chains and transmit chains using the aforementioned hardware. For example, UE 106 may share one or more portions of a receive chain and / or transmit chain between multiple wireless communication technologies (such as those discussed above).

[0037] In some embodiments, the UE 106 may include a separate transmit chain and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As another possibility, the UE 106 may include one or more radio components shared between multiple wireless communication protocols, and one or more radio components used uniquely by a single wireless communication protocol. For example, the UE 106 may include a shared radio component for communicating using either LTE or 5GNR (or LTE or 1xRTT, or LTE or GSM), and a separate radio component for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0038] Figure 3 An exemplary simplified block diagram of a communication device 106 according to some embodiments is illustrated. Note that Figure 3The block diagram of the communication device is only an example of a possible communication device. According to an embodiment, the communication device 106 can be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (such as a laptop computer, a notebook or portable computing device), a tablet computer and / or a combination of devices, in addition to other devices. As shown, the communication device 106 may include a group of components 300 configured to perform core functions. For example, the group of components can be implemented as a system on a chip (SOC), which may include parts for various purposes. Alternatively, the group of components 300 can be implemented as a separate component or group of components for various purposes. The group of components 300 can be coupled to various other circuits of the communication device 106 (e.g., communicatively; directly or indirectly).

[0039] For example, the communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as a connector I / F 320 (e.g., for connecting to a computer system; a docking station; a charging station; input devices such as a microphone, a camera, a keyboard; output devices such as a speaker; etc.), a display 360 that may be integrated with the communication device 106 or external to the communication device, and cellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc., and short-range to medium-range wireless communication circuitry 329 (e.g., Bluetooth TM and WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0040] Cellular communication circuitry 330 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 335 and 336, as shown. Short-range to medium-range wireless communication circuitry 329 may also be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 337 and 338, as shown. Alternatively, short-range to medium-range wireless communication circuitry 329 may be (e.g., communicatively; directly or indirectly) coupled to antennas 335 and 336 in addition to or in lieu of being (e.g., communicatively; directly or indirectly) coupled to antennas 337 and 338. Short-range to medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input, multiple-output (MIMO) configuration.

[0041] In some embodiments, as further described below, the cellular communication circuitry 330 can include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radios) for multiple radio access technologies (RATs) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). Furthermore, in some embodiments, the cellular communication circuitry 330 can include a single transmit chain that can switch between radios dedicated to specific RATs. For example, a first radio can be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with an additional radio, such as a second radio that can be dedicated to a second RAT (e.g., 5G NR) and can communicate with both the dedicated receive chain and the shared transmit chain.

[0042] The communication device 106 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include any of a variety of elements, such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of a touch screen display), a mouse, a microphone and / or speakers, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0043] The communication device 106 may also include one or more smart cards 345 , such as one or more UICCs (Universal Integrated Circuit Cards) 345 , having SIM (Subscriber Identity Module) functionality.

[0044] As shown, the SOC 300 may include a processor 302 that may execute program instructions for the communication device 106 and a display circuit 304 that may perform graphics processing and provide display signals to a display 360. The processor 302 may also be coupled to a memory management unit (MMU) 340 (the MMU may be configured to receive addresses from the processor 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310)) and / or to other circuits or devices (such as the display circuit 304, the short-range wireless communication circuit 229, the cellular communication circuit 330, the connector I / F 320, and / or the display 360). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.

[0045] As described above, the communication device 106 can be configured to communicate using wireless and / or wired communication circuitry. The communication device 106 can be configured to transmit a request to attach to a first network node operating according to a first RAT (e.g., 5G NR, 4G LTE, Bluetooth, Wi-Fi, etc.) and to transmit an indication that the wireless device is capable of maintaining substantially concurrent connections with the first network node and a second network node operating according to a second RAT (e.g., 5G NR, 4G LTE, Bluetooth, Wi-Fi, etc.). The wireless device can also be configured to transmit a request to attach to the second network node. The request can include an indication that the wireless device is capable of maintaining substantially concurrent connections with the first and second network nodes. In addition, the wireless device can be configured to receive an indication that dual connectivity has been established with the first network node and the second network node.

[0046] As described herein, the communication device 106 may include hardware and software components for implementing the above-described features for supporting multicast reception during inactive mobility. The processor 302 of the communication device 106 may be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or additionally), the processor 302 may be configured as a programmable hardware element such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit). Alternatively (or additionally), in combination with one or more of the other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, the processor 302 of the communication device 106 may be configured to implement some or all of the features described herein.

[0047] Furthermore, as described herein, processor 302 may include one or more processing elements. Thus, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 302.

[0048] Furthermore, as described herein, both the cellular communication circuitry 330 and the short-range wireless communication circuitry 329 may include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuitry 330, and similarly, one or more processing elements may be included in the short-range wireless communication circuitry 329. Thus, the cellular communication circuitry 330 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuitry 330. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuitry 330. Similarly, the short-range wireless communication circuitry 329 may include one or more ICs configured to perform the functions of the short-range wireless communication circuitry 329. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-range wireless communication circuitry 329.

[0049] Figure 4 An exemplary block diagram of a base station 102 according to some embodiments is illustrated. Note that Figure 4 The base station 102 is only one example of a possible base station. As shown, the base station 102 may include a processor 404 that may execute program instructions for the base station 102. The processor 404 may also be coupled to a memory management unit (MMU) 440 that may be configured to receive addresses from the processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450) or to other circuits or devices.

[0050] The base station 102 may include at least one network port 470. The network port 470 may be configured to couple to a telephone network and provide access to the telephone network as described above. Figure 1 and Figure 2 Multiple devices of the telephone network described in, such as UE device 106.

[0051] The network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to a plurality of devices, such as the UE device 106. In some cases, the network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0052] In some embodiments, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or "gNB." In such embodiments, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). Furthermore, a UE capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0053] Base station 102 may include at least one antenna 434, and may include multiple antennas. At least one antenna 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE device 106 via radio 430. Antenna 434 communicates with radio 430 via communication chain 432. Communication chain 432 may be a receive chain, a transmit chain, or both. Radio 430 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, and the like.

[0054] Base station 102 may be configured to communicate wirelessly using multiple wireless communication standards. In some instances, base station 102 may include multiple radio components that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for communicating according to LTE and a 5G NR radio component for communicating according to 5G NR. In this case, base station 102 may be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of communicating according to any one of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0055] As further described later herein, BS102 may include hardware and software components for implementing or supporting the specific implementation of the features described herein. The processor 404 of the base station 102 may be configured to implement or support part or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit) or a combination thereof. Alternatively (or in addition), in combination with one or more of the other components 430, 432, 434, 440, 450, 460, 470, the processor 404 of the BS102 may be configured to implement or support part or all of the features described herein.

[0056] Furthermore, as described herein, processor 404 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor 404. Thus, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 404.

[0057] Furthermore, as described herein, radio 430 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 430. Thus, radio 430 may include one or more integrated circuits (ICs) configured to perform the functions of radio 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio 430.

[0058] Figure 5 An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is illustrated. Note that Figure 5 The block diagram of the cellular communication circuitry is only one example of possible cellular communication circuitry. Depending on the embodiment, the cellular communication circuitry 330 may be included in a communication device such as the communication device 106 described above. As described above, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of devices, among other devices.

[0059] The cellular communication circuitry 330 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 335a-335b and 336 as shown. In some embodiments, the cellular communication circuitry 330 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, Figure 5 As shown, the cellular communication circuitry 330 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the modem 520 may be configured for communication according to a second RAT (e.g., such as 5G NR).

[0060] As shown, the modem 510 may include one or more processors 512 and a memory 516 in communication with the processor 512. The modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 530 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, the receive circuitry 532 may communicate with a downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0061] Similarly, the modem 520 may include one or more processors 522 and a memory 526 in communication with the processors 522. The modem 520 may communicate with an RF front end 540. The RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, the receive circuitry 542 may communicate with a DL front end 560, which may include circuitry for receiving radio signals via the antenna 335b.

[0062] In some embodiments, the switch 570 can couple the transmit circuitry 534 to an uplink (UL) front end 572. Additionally, the switch 570 can couple the transmit circuitry 544 to the UL front end 572. The UL front end 572 can include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuitry 330 receives an instruction to transmit according to a first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572), the switch 570 can be switched to a first state that allows the modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572). Similarly, when the cellular communication circuitry 330 receives an instruction to transmit according to a second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572), the switch 570 can be switched to a second state that allows the modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572).

[0063] As described herein, the modem 510 may include hardware and software components for implementing the features described above or for supporting multicast reception during inactive mobility and various other techniques described herein. The processor 512 may be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or additionally), the processor 512 may be configured as a programmable hardware element such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit). Alternatively (or additionally), in combination with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336, the processor 512 may be configured to implement some or all of the features described herein.

[0064] Furthermore, as described herein, processor 512 may include one or more processing elements. Thus, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0065] As described herein, the modem 520 may include hardware and software components for implementing the above-described features for supporting multicast reception during inactive mobility and various other technologies described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 522 may be configured to implement some or all of the features described herein. Alternatively (or additionally), the processor 522 may be configured as a programmable hardware element such as a field programmable gate array (FPGA), or as an ASIC (application-specific integrated circuit). Alternatively (or additionally), in combination with one or more of the other components 540, 542, 544, 550, 570, 572, 335, and 336, the processor 522 may be configured to implement some or all of the features described herein.

[0066] Furthermore, as described herein, processor 522 may include one or more processing elements. Thus, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0067] Figure 6 6. Logic flow 600 illustrating various aspects of a multicast session according to some embodiments. More specifically, logic flow 600 may provide an overview of the lifecycle of a multicast session. One or more of UE session join and UE session leave may be performed for a particular UE, and one or more of MBS session creation, service announcement, session establishment, no data reception, data transfer, session release, and session deletion may be performed for a particular service. In various embodiments, the techniques described herein for multicast reception in an inactive state may generally occur within and / or between a UE session join and a UE session leave. It should be understood that UE active and inactive states (e.g., RRC active and RRC inactive states) are distinct from the MBS session states described below. The embodiments are not limited to this context.

[0068] In the illustrated embodiment, the logic flow 600 begins at block 602. Block 602 includes MBS session creation and service announcement. MBS session creation may refer to a phase in which information about a multicast MBS session is provided by an MBS-related core network function (such as an application function (AF), an MBS function, or one or more other functional entities). In various embodiments, the MBS function may include or refer to one or more of a multicast / broadcast session management function (MB-SMF), a multicast / broadcast user plane function (MB-UPF), a multicast / broadcast service function (MBSF), and a multicast / broadcast service transport function (MBSTF). In some embodiments, MBS session creation may request the allocation of a temporary mobile group identity (TMGI). Alternatively, in various embodiments, information about the multicast MBS session may be pre-configured in the network. In various such embodiments, the MBS session state may be "Start (NULL)".

[0069] MBS session creation may indicate whether a multicast MBS session may be established in an active state or an inactive state (different from the UE inactive state), and when the multicast MBS session may become active. The AF may perform creation which is a number of steps, such as first requesting a TMGI, and then providing complete information about the multicast MBS session and allowing it to be established, or updating information on whether the multicast session is to be in an active or inactive state after establishment. Creation of a multicast MBS session by the AF may transition the multicast MBS session state from "Start (Empty)" to a configured state. In the configured state, information about the multicast MBS session (e.g., QoS information) is available in the 5G core network function serving the multicast MBS session, but no user plane resources are reserved towards the Next Generation Radio Access Network (NG-RAN) node, and MBS data cannot be transmitted. An NG-RAN node may refer to a base station, such as a gNB or ng-eNB.

[0070] Service announcements may be used to distribute information about the service required for service reception (such as IP multicast addresses) and possibly other service related parameters (such as service start time) towards UEs.In various embodiments, service announcements may be optional.

[0071] Block 604 includes UE session joining and session establishment. UE session joining may include the process by which a UE joins an MBS session, such as by indicating to the network that the UE wants to receive multicast data identified by a specific MBS session ID. In many embodiments, a UE may only receive multicast services after it has joined the session. Session establishment may include the phase in which a multicast MBS session is established. For example, when a first UE's join request for a multicast MBS session is accepted, the multicast MBS session is established with the NG-RAN node and the UE.

[0072] When a multicast MBS session is established, it transitions from the "Start (Empty)" or configured state to either the inactive or active state. In the active state, radio resources for the multicast MBS session can be established, and transmission of the multicast MBS session to UEs can begin. In the inactive state, the multicast MBS session is established, but no MBS data is transmitted to UEs that have joined the multicast MBS session. In various embodiments, after the session is established, the multicast session state can be switched between active and inactive several times.

[0073] At block 606, data is transmitted. Data transmission is the phase in which multicast data is transmitted to the UE. Block 608 includes UE session leaving and session release. UE session leaving may include the process by which a UE leaves an MBS session (because the UE no longer wishes to receive multicast data identified by a specific MBS session ID). Session release may include the phase in which resources used for the multicast MBS session are released. Continuing at block 610, the multicast MBS session may be deleted.

[0074] Figure 7 A network message 702 is illustrated, including multiple information elements (IEs) 704a, 704b, 704c, and 704d (collectively, IEs 704). In various embodiments, various network messages 702 comprised of one or more information elements may be used for communication between different components. For example, one or more network messages 702 in one or more formats may be exchanged between one or more UEs and one or more network components to perform one or more procedures. For example, obtaining PTM configuration via one or more of SIB, MCCH, or RRC signaling to enable multicast reception for UEs in an inactive state may utilize the exchange of multiple network messages 702. It should be understood that network messages 702 and IEs 704 may appear in various formats and carry various information. Various network messages 702, IEs 704, and procedures are generally defined by various standards and technical specifications, such as 3GPP technical specifications (e.g., TS 23.247, TS 26.502, TS 26.517, TS 38.331, and TS 38.300). Embodiments are not limited in this context.

[0075] Various techniques for multicast reception in an inactive state will be described in more detail below. These techniques can be used to enable a UE to receive a broadcast MBS session in an RRC inactive state. In many embodiments, the UE can continue to receive a broadcast MBS session in an RRC inactive state when transitioning from a first network cell to a second network cell. The techniques for multicast reception in an inactive state may also include various methods for obtaining configuration data to enable multicast reception in a neighboring network cell, being notified of configuration changes, and discarding old configuration data. For example, the PTM configuration for a neighboring network cell may be obtained via one or more of a system information block (SIB), a multicast control channel (MCCH), and dedicated RRC signaling. As another example, a notification of an upcoming configuration change may be used to start a timer that causes the old configuration data to be discarded upon expiration.

[0076] Various techniques may include or involve multicast data reception and PTM configuration acquisition by a UE in a newly selected cell during an inactive state. In some embodiments, when the network configures the UE to continue multicast reception in an inactive state, the network may provide the PTM configuration for the activated multicast session via RRC dedicated signaling at least for the serving cell. In various embodiments, the MCCH may be used when the PTM configuration needs to be indicated (such as when the PTM configuration needs to be changed) or during mobility beyond the serving cell (e.g., moving from a first network cell to a second network cell). In some embodiments, the MCCH configuration may be initially provided to the UE via dedicated signaling. In various embodiments, the UE may acquire the PTM configuration via RRC dedicated signaling and may acquire the PTM configuration via the MCCH during mobility.

[0077] In many embodiments, a UE in an inactive state (also referred to as an inactive UE) may not support PTM configuration acquisition via MCCH. If the inactive UE has a valid PTM configuration for the new camping cell (the cell to which the UE is transitioning), the UE may perform multicast reception according to the PTM configuration. If the inactive UE is unable to obtain a valid PTM configuration for its multicast session in the new camping cell, the UE initiates an RRC connection recovery procedure (also referred to as an RRC recovery procedure), which causes the UE to transition out of the inactive state and into the connected state. Various embodiments disclosed herein may relate to avoiding or preventing the UE from initiating the RRC recovery procedure. The initiation of the RRC recovery procedure may occur in a variety of scenarios, including when the network does not provide multicast services for the inactive UE, when the network does not provide services for the multicast session for the inactive UE, and when the UE has problems obtaining the PTM configuration via MCCH (e.g., poor radio quality). In addition, in various embodiments, when the UE's multicast session is in an inactive state and the network does not provide PTM configuration, the UE does not need to initiate the RRC recovery procedure. Instead, the UE monitors for multicast session activation notifications from the network and then initiates the RRC recovery procedure.

[0078] Figure 8 800 illustrates a logic flow for UE operation when camping on a new network cell according to some embodiments. In many embodiments, in order to receive a multicast session in an inactive state, the UE needs to have a PTM configuration for the network cell in which the UE is camped. In embodiments corresponding to logic flow 800, the PTM configuration may already be provided (as described below, such as with respect to Figure 9 Detailed description) or acquired via MCCH, otherwise the UE may initiate an RRC recovery procedure. The embodiments are not limited in this context.

[0079] Logic flow 800 begins at block 802. At block 802, a UE is enabled to receive a multicast service while in an RRC inactive state and is located in a first network cell. Continuing at block 804, the UE transitions from the first network cell to a second network cell. In many embodiments, the UE's transition from the first network cell to the second network cell may include the UE performing cell reselection and camping on the new cell.

[0080] In many embodiments, the operation of a UE when camped on a new cell may be described with respect to one of three scenarios. Using existing techniques, each of these scenarios is not supported and / or causes the UE to initiate an RRC recovery procedure. In the first scenario, the UE has a pre-configured PTM configuration for the new cell (e.g., via the source cell). In the first scenario, the UE may directly perform multicast reception based on the pre-configured PTM configuration. Referring back to logic flow 800, the first scenario may correspond to a "yes" answer to decision block 806, causing logic flow 800 to proceed from decision block 806 to block 818 and receive multicast services in an RRC inactive state.

[0081] In the second scenario, the UE does not have a PTM configuration, and the UE does not support PTM configuration acquisition via the MCCH. In the second scenario, the UE may initiate an RRC recovery procedure. Referring back to logic flow 800, the second scenario may correspond to the following: decision block 806 has a "no" answer, causing the logic flow 800 to proceed from decision block 806 to decision block 808, and because the UE does not support PTM configuration acquisition via the MCCH, decision block 808 has a "no" answer, causing the logic flow 800 to proceed from decision block 808 to block 816 and initiate an RRC recovery procedure.

[0082] In the third case, the UE does not have a PTM configuration and the UE supports PTM configuration acquisition via the MCCH. Referring back to logic flow 800, the third scenario may correspond to the following: decision block 806 has a "no" answer, thereby causing the logic flow 800 to proceed from decision block 806 to decision block 808, and because the second network cell provides multicast reception service to the UE in the RRC inactive state, decision block 808 has a "yes" answer, thereby causing the logic flow 800 to proceed from decision block 808 to block 810.

[0083] Referring back to logic flow 800, the second scenario may correspond to the following: decision block 806 has a "no" answer, causing the logic flow 800 to proceed from decision block 806 to decision block 808, and because the second network cell does not provide multicast reception service to the UE in the RRC inactive state, decision block 808 has a "no" answer, causing the logic flow 800 to proceed from decision block 808 to block 816 and initiate the RRC recovery process.

[0084] The third scenario can be broken down into two sub-scenarios. In the first sub-scenario, the network does not provide multicast services to the inactive UE in the new cell. In the first sub-scenario, the UE may initiate an RRC recovery procedure. Referring back to logic flow 800, the first sub-scenario may correspond to the following: decision block 806 has a "no" answer, causing logic flow 800 to proceed from decision block 806 to decision block 808, and because the second network cell does not provide multicast reception services to the UE in the RRC inactive state, decision block 808 has a "no" answer, causing logic flow 800 to proceed from decision block 808 to block 816 and initiate an RRC recovery procedure.

[0085] In the second sub-scenario, the network provides multicast services to inactive UEs in the new cell, which causes decision block 808 to have a "yes" answer and logic flow 800 to proceed to block 810, and then to decision block 812, where the UE performs MCCH acquisition to attempt to acquire the PTM configuration. Therefore, in the second sub-scenario, the UE may attempt to acquire the PTM configuration via the MCCH. The UE's attempt to acquire the PTM configuration via the MCCH may result in one of three scenarios. In the first scenario, the UE fails to acquire the MCCH and initiates an RRC recovery procedure. Referring back to logic flow 800, the first scenario may correspond to a "no" answer to decision block 812, causing logic flow 800 to proceed from decision block 812 to block 816 and initiate an RRC recovery procedure. The UE may declare MCCH acquisition failure using one or more of the following techniques. Using the first technique, MCCH acquisition failure may be determined when the UE is unable to acquire the MCCH within one or more MCCH modification periods. The number of MCCH modification periods to wait before determining MCCH acquisition failure may be set based on implementation details. With the second technique, if the radio quality of the UE is below a threshold, it can be determined that the MCCH acquisition has failed. With the third technique, the MCCH acquisition has failed can be determined based on a timer, such as the following example with respect to Figure 10 Described in more detail.

[0086] In the second case, the UE acquires the MCCH, but there is no PTM configuration for the UE's multicast session, causing the UE to initiate an RRC recovery procedure. Referring back to logic flow 800, the second case may correspond to the following: since the UE acquires the MCCH, decision block 812 has a "yes" answer, but decision block 814 has a "no" answer, causing logic flow 800 to proceed from decision block 814 to block 816 and initiate an RRC recovery procedure.

[0087] In the third case, the UE obtains the PTM configuration for the UE's multicast session and the UE begins performing multicast reception. Referring back to logic flow 800, the third case may correspond to a "yes" answer to decision block 812 and a "yes" answer to decision block 814, causing logic flow 800 to proceed from decision block 814 to block 818 and receive the multicast service in the RRC inactive state.

[0088] Figure 9 A process diagram 900 is illustrated for continuing multicast reception in an inactive state while transitioning between network cells, according to some embodiments. Process diagram 900 may involve obtaining a PTM configuration and / or updating a PTM configuration for a neighboring network cell. Process diagram 900 may include a UE 902, a first network cell 904a, and a second network cell 904b. Process diagram 900 may correspond to UE 902 transitioning from first network cell 904a to second network cell 904b while in an inactive state.

[0089] In process diagram 900, UE 902 may initially be in a connected state 912 (e.g., an RRC connected state). UE 902 may then receive an RRC release 906 network message with a suspended configuration. In many embodiments, RRC release 906 with a suspended configuration includes a PTM configuration for a first network cell 904a and a second network cell 904b. In many such embodiments, UE 902 may store the PTM configuration. In response to the RRC release 906 with a suspended configuration indication from first network cell 904a, UE 902 may transition to an inactive state 914 (e.g., an RRC inactive state). Once in inactive state 914, UE 902 may receive or continue to receive a multicast session reception 908 from first network cell 904a. UE 902 may then move to a second network cell 916 (i.e., second network cell 904b). Once camped on the second network cell 904b, the UE 902 may utilize the PTM configuration received for the second network cell 904b in the RRC release with suspension configuration 906 to receive the multicast session reception 910 from the second network cell 904b.

[0090] More generally, the embodiments disclosed herein may utilize a variety of techniques to receive PTM configurations for neighboring network cells (e.g., second network cell 904b). In some embodiments, such as the scenario described above with respect to process diagram 900, the network may provide the PTM configurations for neighboring cells via dedicated signaling. In such embodiments, when the network provides PTM for the current serving cell (e.g., first network cell 904a that sends RRC release 906 with pause configuration), the network may also provide the PTM configurations for neighboring cells for the same multicast session. In other embodiments, for each multicast session, the network may provide neighboring cell information that may provide the same service or have the same PTM configuration. In such other embodiments, the configurations may be provided in a system information block (SIB), MCCH (see, e.g., logic flow 800), or via UE-specific RRC signaling.

[0091] In various implementations, the PTM configuration of a neighboring cell may change. In such implementations, four scenarios may occur. In the first scenario, the network uses multicast or broadcast to transmit a notification of a neighboring cell's PTM configuration change to the UE. For example, group paging may be used to indicate the neighboring cell information change.

[0092] In the second scenario, the network may send a UE-specific RAN paging. For example, the network may request the UE to return to the connected state (e.g., via RRC recovery), and the network may provide the UE in the connected state with updated configuration changes of neighboring cells.

[0093] In the third scenario, the network can indicate the configuration change of the neighboring cell via the MCCH channel. For example, a bit in the MCCH Downlink Control Information (DCI) network message can be used to indicate whether the neighboring cell configuration has changed. For another example, a bit for each multicast session in the PTM configuration can be used.

[0094] In the fourth scenario, time can be used to avoid outdated information. For example, the network can configure a validity timer along with the PTM configuration. In such an example, when the timer expires, the UE can discard neighbor cell information for the multicast session. It should be understood that one or more scenarios, situations, examples, or procedures described herein should not be construed as mutually exclusive. For example, the validity timer can be utilized in one or more of the other scenarios.

[0095] Figure 10 Illustrated is a process diagram 1000 for determining MCCH acquisition failure according to some embodiments. More specifically, process diagram 1000 may involve determining MCCH acquisition failure in response to expiration of MCCH acquisition timer 1020. Process diagram 1000 may include UE 1002, first network cell 1004a, and second network cell 1004b.

[0096] In process diagram 1000, UE 1002 may initially be in connected state 1012 (e.g., RRC connected state). UE 1002 may then receive an RRC release with pause configuration 1006 network message. In many embodiments, RRC release with pause configuration 1006 does not include a PTM configuration for second network cell 1004b. In response to the RRC release with pause configuration 1006 indication from first network cell 1004a, UE 1002 may transition to an inactive state 1014 (e.g., RRC inactive state). Once in inactive state 1014, UE 1002 may receive or continue to receive a multicast session 1008 from first network cell 1004a. UE 1002 may then move to a second network cell 1016 (i.e., second network cell 1004b). In various embodiments, upon transitioning to the second network cell 1004b, the UE 1002 may initialize an MCCH acquisition timer 1020 and perform an MCCH acquisition attempt 1010. For example, the MCCH acquisition timer 1020 may be initialized at the beginning of the transition. In another example, the MCCH acquisition timer 1020 may be initialized at the end of the transition. In yet another example, the MCCH acquisition timer 1020 may be initialized after cell selection. If the UE cannot acquire the MCCH before the expiration 1022 of the MCCH acquisition timer 1020, the UE 1002 may initiate an RRC recovery procedure 1018. The amount of time before the expiration 1022 of the MCCH acquisition timer 1020 may be determined based on implementation details.

[0097] It should be understood that in some embodiments, the UE may receive an RRC release message with a suspension configuration in an RRC inactive state, such as using a fast RRC recovery procedure or during a small data transfer (SDT) process. Thus, in some embodiments, the UE may receive one or more PTM configurations via an RRC release with a suspension configuration in an RRC inactive state.

[0098] Figure 11 Illustrated is a logic flow 1100 of an exemplary technique for multicast reception in an inactive state according to some embodiments. Aspects of the logic flow 1100 may relate to the various embodiments described herein.

[0099] Logic flow 1100 may begin at block 1102. Block 1102 may include receiving a multicast session for a multicast service with a UE in an RRC inactive state and located in a first network cell using a first PTM configuration for the first network cell. For example, UE 902 may receive multicast session reception 908 in first network cell 904a.

[0100] Continuing with block 1104, a transition of the UE from a first network cell to a second network cell may be determined. For example, UE 902 may move to second network cell 916 (e.g., second network cell 904b). Proceeding with block 1106, the UE may utilize a second PTM configuration for the second network cell in an RRC inactive state to continue receiving the multicast session of the multicast service while in the second network cell. For example, UE 902 may utilize the PTM configuration received for the second network cell in RRC release 906 with a pause configuration to receive the multicast session 910 in second network cell 904b.

[0101] The part of the above content can be realized by utilizing a logic circuit such as a dedicated logic circuit or utilizing a microcontroller or other form of processing core for executing program code instructions.Thus, program code such as machine executable instructions can be utilized to execute the process taught by the above discussion, and the machine executable instructions make the machine execute these instructions to perform certain functions.In this context, "machine" can be a machine that converts an intermediate form (or "abstract") instruction into an instruction specific to a processor (for example, an abstract execution environment such as a "virtual machine" (for example, a Java virtual machine), an interpreter, a common language runtime, a high-level language virtual machine, etc.), and / or an electronic circuit that is arranged on a semiconductor chip (for example, a "logic circuit" realized using a transistor), and the electronic circuit is designed to execute instructions, and the processor is such as a general-purpose processor and / or a special-purpose processor.The process taught by the above discussion can also be executed by (as a substitute of a machine or in combination with a machine) an electronic circuit, and the electronic circuit is designed to execute a process (or a part thereof) without executing program code.

[0102] The present invention also relates to an apparatus for performing the operations described herein. The apparatus may be specially constructed for the required purpose, or may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored on a computer-readable storage medium, such as, but not limited to, any type of disk, including floppy disks, optical disks, CD-ROMs, and magneto-optical disks, read-only memory (ROM), RAM, EPROM, EEPROM, magnetic or optical cards, or any type of medium suitable for storing electronic instructions, and each coupled to a computer system bus.

[0103] A machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, machine-readable media include read-only memory ("ROM"); random access memory ("RAM"); magnetic disk storage media; optical storage media; flash memory devices; and the like.

[0104] Articles of manufacture can be used to store program code. Articles of manufacture storing program code can be implemented as, but not limited to, one or more memories (e.g., one or more flash memories, random access memories (static, dynamic, or other)), optical disks, CD-ROMs, DVD ROMs, EPROMs, EEPRO M, magnetic or optical cards, or other types of machine-readable media suitable for storing electronic instructions. Program code can also be downloaded from a remote computer (e.g., a server) to a requesting computer (e.g., a client) by means of a data signal contained in a propagation medium (e.g., via a communication link (e.g., a network connection)).

[0105] Various example implementations are described herein.

[0106] Embodiment 1 is a computer-implemented method comprising: receiving a multicast session of a multicast service using a first point-to-multipoint (PTM) configuration for a first network cell when a user equipment (UE) is in a radio resource control (RRC) inactive state and is located in a first network cell; determining that the UE is transitioning from the first network cell to a second network cell; and continuing to receive the multicast session of the multicast service using a second PTM configuration for the second network cell when the UE is in the RRC inactive state and is located in the second network cell.

[0107] Embodiment 2 is a computer-implemented method according to embodiment 1, and the computer-implemented method may optionally include: receiving an RRC release message with a pause configuration; and receiving the multicast session of the multicast service based on the RRC release message with the pause configuration in the RRC inactive state.

[0108] Embodiment 3 is a computer-implemented method according to embodiment 2, which may optionally include: the RRC release message with suspension configuration includes the PTM configuration for the second network cell.

[0109] Embodiment 4 is a computer-implemented method according to embodiment 3, which may optionally include: the RRC release message with suspension configuration includes the PTM configuration for the first network cell.

[0110] Embodiment 5 is a computer-implemented method according to embodiment 1, optionally including receiving the second PTM configuration together with the first PTM configuration.

[0111] Embodiment 6 is a computer-implemented method according to embodiment 5, optionally comprising receiving the PTM configuration for the first network cell and the second network cell via RCC dedicated signaling.

[0112] Embodiment 7 is a computer-implemented method according to embodiment 1, which may optionally include receiving the second PTM configuration in the second network cell when the UE is in the RRC inactive state.

[0113] Embodiment 8 is a computer-implemented method according to embodiment 7, optionally including receiving the second PTM configuration via a multicast control channel (MCCH).

[0114] Embodiment 9 is a computer-implemented method according to embodiment 8, optionally including performing MCCH acquisition to receive the second PTM configuration via the MCCH.

[0115] Embodiment 10 is a computer-implemented method according to embodiment 1, and the computer-implemented method may optionally include: the second PTM configuration includes an updated second PTM configuration for the second network cell, and the computer-implemented method also includes: receiving a notification that the initial second PTM configuration for the second network cell has been updated when the UE is located in the first network cell.

[0116] Embodiment 11 is a computer-implemented method according to embodiment 10, which may optionally include: starting a validity timer in response to receiving the notification that the initial second PTM configuration for the second network cell has been updated; and discarding the initial second PTM configuration for the second network after the validity timer expires.

[0117] Embodiment 12 is a computer-implemented method according to embodiment 1, optionally comprising performing a multicast control channel (MCCH) acquisition to receive the second PTM configuration via the MCCH before expiration of a timer.

[0118] Embodiment 13 is a computer-implemented method according to embodiment 12, optionally including initializing the timer based on transitioning from the first network cell to the second network cell.

[0119] Embodiment 14 is a computer-implemented method according to embodiment 1, and the computer-implemented method may optionally include: joining the multicast session of the multicast service when the UE is in an RRC connected state; receiving an RRC release message with a pause configuration when the UE is in the RRC connected state; transitioning to the RRC inactive state in response to the RRC release message with a pause configuration; and receiving the multicast session of the multicast service in the RRC inactive state.

[0120] Embodiment 15 is a computer-implemented method according to embodiment 14, and the computer-implemented method may optionally include: the RRC release message with suspension configuration includes one or more of the PTM configuration for the first network cell and the PTM configuration for the second network cell.

[0121] Embodiment 16 is a computer-implemented method according to embodiment 1, which may optionally include: determining that the UE fails to support PTM configuration acquisition via a multicast control channel (MCCH); and initiating an RRC recovery process to acquire the second PTM configuration.

[0122] Embodiment 17 is a computer-implemented method according to embodiment 1, which may optionally include: failing to acquire a second updated PTM via multicast control channel (MCC H) acquisition before the expiration of a timer; and utilizing an RRC recovery procedure to receive the second PTM configuration in response to the expiration of the timer.

[0123] Embodiment 18 is a computer-implemented method according to embodiment 14, optionally including initializing the timer based on a transition from the first network cell to the second network cell.

[0124] Embodiment 19 is a computer-implemented method according to embodiment 1, which may optionally include: determining that the signal quality at the UE is lower than a threshold; and utilizing an RRC recovery process to receive the second PTM configuration in response to determining that the signal quality at the UE is lower than the threshold.

[0125] Embodiment 20 is a computer-implemented method according to embodiment 1, which may optionally include: failing to obtain a second updated PTM via multicast control channel (MCCH) acquisition within a predefined number of MCCH modification periods; and utilizing an RRC recovery process to receive the second PTM configuration in response to failing to obtain the second updated PTM within the predefined number of MCCH modification periods.

[0126] Embodiment 21 is a user equipment (UE), the UE comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 1 to 20.

[0127] Embodiment 22 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method according to any one of embodiments 1 to 20.

[0128] Embodiment 23 is a computer-implemented method comprising: enabling a user equipment (UE) to receive a multicast session of a multicast service using a first point-to-multipoint (PTM) configuration for a first network cell when the UE is in a radio resource control (RRC) inactive state and is located in a first network cell; determining that the UE is transitioning from the first network cell to a second network cell; and enabling the UE to continue receiving the multicast session of the multicast service using a second PTM configuration for the second network cell when the UE is in the RRC inactive state and is located in the second network cell.

[0129] Embodiment 24 is a computer-implemented method according to embodiment 23, which may optionally include: transmitting an RRC release message with a suspension configuration to enable the UE to receive the multicast session of the multicast service in the RRC inactive state.

[0130] Embodiment 25 is a computer-implemented method according to embodiment 24, which may optionally include: the RRC release message with suspension configuration includes the PTM configuration for the second network cell.

[0131] Embodiment 26 is a computer-implemented method according to embodiment 25, which may optionally include: the RRC release message with suspension configuration includes the PTM configuration for the first network cell.

[0132] Embodiment 27 is a computer-implemented method according to embodiment 23, optionally including transmitting the second PTM configuration in a network message along with the first PTM configuration.

[0133] Embodiment 28 is a computer-implemented method according to embodiment 27, optionally comprising transmitting the PTM configuration for the first network cell and the second network cell via RCC dedicated signaling.

[0134] Embodiment 29 is a computer-implemented method according to embodiment 23, which may optionally include receiving the second PTM configuration in the second network cell when the UE is in the RRC inactive state.

[0135] Embodiment 30 is the computer-implemented method of embodiment 29, optionally comprising transmitting the second PTM configuration via a multicast control channel (MCCH).

[0136] Embodiment 31 is a computer-implemented method according to embodiment 30, optionally comprising transmitting the second PTM configuration via the MCCH.

[0137] Embodiment 32 is a computer-implemented method according to embodiment 23, and the computer-implemented method may optionally include: the second PTM configuration includes an updated second PTM configuration for the second network cell, and the computer-implemented method also includes: transmitting a notification that the initial second PTM configuration for the second network cell has been updated when the UE is located in the first network cell.

[0138] Embodiment 33 is a computer-implemented method according to embodiment 32, which may optionally include: in response to receiving the notification that the initial second PTM configuration for the second network cell has been updated, causing the UE to start a validity timer, wherein the UE discards the initial second PTM configuration for the second network after the validity timer expires.

[0139] Embodiment 34 is a computer-implemented method according to embodiment 23, which may optionally include: transmitting the second PTM configuration via a multicast control channel (MCCH) before expiration of a timer in response to a multicast control channel (MCCH) acquisition procedure initiated by the UE.

[0140] Embodiment 35 is a computer-implemented method according to embodiment 23, which may optionally include: enabling the UE to join the multicast session of the multicast service when the UE is in an RRC connected state; transmitting an RRC release message with a pause configuration when the UE is in the RRC connected state; causing the UE to transition to the RRC inactive state based on the RRC release message with the pause configuration; and transmitting the multicast session of the multicast service to the UE in the RRC inactive state.

[0141] Embodiment 36 is a computer-implemented method according to embodiment 35, and the computer-implemented method may optionally include: the RRC release message with the suspension configuration includes one or more of the PTM configuration for the first network cell and the PTM configuration for the second network cell.

[0142] Embodiment 37 is a computer-implemented method according to embodiment 23, which may optionally include providing the second PTM configuration via an RRC recovery procedure based on the UE failing to support PTM configuration acquisition via a multicast control channel (MCCH).

[0143] Embodiment 38 is a computer-implemented method according to embodiment 23, which may optionally include: providing the second PTM configuration to the UE based on an RRC recovery process based on the UE failing to acquire the second updated PTM via a multicast control channel (MCCH) before the timer expires.

[0144] Embodiment 39 is a computer-implemented method according to embodiment 23, which may optionally include providing the second PTM configuration via an RRC recovery procedure based on determining that signal quality between the UE and a base station is below a threshold.

[0145] Embodiment 40 is a computer-implemented method according to embodiment 23, and the computer-implemented method may optionally include: providing the second PTM configuration via an RRC recovery process based on the UE failing to obtain a second updated PTM via MCCH acquisition within a predefined number of multicast control channel (MCCH) modification periods.

[0146] Embodiment 41 is a base station (BS), comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 23 to 40.

[0147] Embodiment 42 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method according to any one of embodiments 23 to 40.

[0148] The foregoing detailed description has been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the tools used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm, as used here and generally, refers to a self-consistent sequence of operations leading to a desired result. These operations are those requiring physical manipulation of physical quantities. Typically, but not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient, primarily for common sense, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

[0149] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless otherwise specifically stated, it will be apparent from the foregoing discussion that discussions throughout this specification using terms such as "select," "determine," "receive," "form," "group," "aggregate," "generate," "remove," and the like will be understood to refer to actions and processes on a computer system or similar electronic computing device that manipulates data represented as physical (electronic) quantities in the computer system's registers and memories and converts it into other data similarly represented as physical quantities in the computer system's memories or registers or other such information storage, transmission, or display devices.

[0150] The process presented herein and display are not inherently relevant to any particular computer or other device. According to the teaching content of this paper, various general-purpose systems can be used together with program, or can prove that it is convenient to construct the more special-purpose device for carrying out described operation. According to the description below, the required structure for various these systems will be apparent. In addition, the present invention is not described with reference to any specific programming language. Should be appreciated that multiple programming languages ​​can be used for realizing the teaching content of the present invention as described herein.

[0151] 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.

[0152] The foregoing discussion describes only some exemplary embodiments of the present invention. Those skilled in the art will readily recognize from these discussions, drawings and claims that various modifications can be made without departing from the spirit and scope of the present invention.

Claims

1. A computer-implemented method, comprising: receiving a multicast session of a multicast service using a first point-to-multipoint (PTM) configuration for a first network cell while a user equipment (UE) is in a radio resource control (RRC) inactive state and is located in the first network cell; determining that the UE is transitioning from the first network cell to a second network cell; as well as The multicast session of the multicast service is continued to be received using a second PTM configuration for the second network cell while the UE is in the RRC inactive state and located in the second network cell.

2. The computer-implemented method of claim 1 , further comprising: Receiving an RRC release message with a suspend configuration; as well as The multicast session of the multicast service is received in the RRC inactive state based on information provided in the RRC release message with suspension configuration.

3. The computer-implemented method of claim 2, wherein the RRC release message with suspension configuration includes the PTM configuration for the second network cell. 4 . The computer-implemented method of claim 3 , wherein the RRC release message with suspension configuration includes the PTM configuration for the first network cell. The computer-implemented method of claim 1 , wherein the second PTM configuration is received together with the first PTM configuration.

6. The computer-implemented method of claim 5 , further comprising: The PTM configuration for the first network cell and the second network cell is received via RCC dedicated signaling.

7. The computer-implemented method of claim 1 , wherein the second PTM configuration is received in the second network cell while the UE is in the RRC inactive state.

8. The computer-implemented method of claim 7, wherein the second PTM configuration is received via a multicast control channel (MCCH).

9. The computer-implemented method of claim 8, further comprising: MCCH acquisition is performed to receive the second PTM configuration via the MCCH.

10. The computer-implemented method of claim 1 , wherein the second PTM configuration comprises an updated second PTM configuration for the second network cell, and the computer-implemented method further comprises: A notification is received, with the UE located in the first network cell, that an initial second PTM configuration for the second network cell has been updated.

11. The computer-implemented method of claim 10 , further comprising: starting a validity timer in response to receiving the notification that the initial second PTM configuration for the second network cell has been updated; as well as After expiration of the validity timer, the initial second PTM configuration for the second network is discarded.

12. The computer-implemented method of claim 1 , further comprising: A multicast control channel (MCCH) acquisition is performed before expiration of a timer to receive the second PTM configuration via the MCCH.

13. The computer-implemented method of claim 12, further comprising: The timer is initialized based on a transition from the first network cell to the second network cell.

14. The computer-implemented method of claim 1 , further comprising: Joining the multicast session of the multicast service when the UE is in an RRC connected state; receiving an RRC release message with a suspension configuration while the UE is in the RRC connected state; transitioning to the RRC inactive state in response to the RRC release message with the suspend configuration; as well as The multicast session of the multicast service is received in the RRC inactive state.

15. The computer-implemented method of claim 14, wherein the RRC release message with suspension configuration includes one or more of the PTM configuration for the first network cell and the PTM configuration for the second network cell.

16. The computer-implemented method of claim 1 , further comprising: determining that the UE fails to support PTM configuration acquisition via a multicast control channel (MCCH); as well as An RRC recovery procedure is initiated to obtain the second PTM configuration.

17. The computer-implemented method of claim 1 , further comprising: Failure to acquire a second updated PTM via multicast control channel (MCCH) acquisition before expiration of the timer; as well as The second PTM configuration is received using an RRC recovery procedure in response to expiration of the timer.

18. The computer-implemented method of claim 14, further comprising: The timer is initialized based on a transition from the first network cell to the second network cell.

19. The computer-implemented method of claim 1 , further comprising: Determining that a signal quality at the UE is lower than a threshold; as well as The second PTM configuration is received utilizing an RRC recovery procedure in response to determining that the signal quality at the UE is below the threshold.

20. The computer-implemented method of claim 1 , further comprising: Failure to acquire a second updated PTM via Multicast Control Channel (MCCH) acquisition within a predefined number of MCCH modification periods; as well as The second PTM configuration is received utilizing an RRC recovery procedure in response to a failure to acquire the second updated PTM within the predefined number of MCCH modification periods.

21. A user equipment (UE) comprising one or more processors configured to perform the computer-implemented method according to any one of claims 1 to 20.

22. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method of any one of claims 1 to 20.

23. A computer-implemented method, comprising: enabling a user equipment (UE) to receive a multicast session of a multicast service using a first point-to-multipoint (PTM) configuration for a first network cell while the UE is in a radio resource control (RRC) inactive state and located in the first network cell; determining that the UE is transitioning from the first network cell to a second network cell; as well as The UE is enabled to continue receiving the multicast session of the multicast service using a second PTM configuration for the second network cell when the UE is in the RRC inactive state and located in the second network cell.

24. The computer-implemented method of claim 23, further comprising: An RRC release message with a suspension configuration is transmitted to enable the UE to receive the multicast session of the multicast service in the RRC inactive state.

25. The computer-implemented method of claim 24, wherein the RRC release message with suspension configuration includes the PTM configuration for the second network cell.

26. The computer-implemented method of claim 25, wherein the RRC release message with suspension configuration includes the PTM configuration for the first network cell.

27. The computer-implemented method of claim 23, wherein the second PTM configuration is transmitted in a network message along with the first PTM configuration.

28. The computer-implemented method of claim 27, transmitting the PTM configuration for the first network cell and the second network cell via RCC dedicated signaling.

29. The computer-implemented method of claim 23, wherein the second PTM configuration is received in the second network cell while the UE is in the RRC inactive state.

30. The computer-implemented method of claim 29, wherein the second PTM configuration is transmitted via a multicast control channel (MCCH).

31. The computer-implemented method of claim 30, further comprising: The second PTM configuration is transmitted via the MCCH.

32. The computer-implemented method of claim 23, wherein the second PTM configuration comprises an updated second PTM configuration for the second network cell, and the computer-implemented method further comprises: A notification is transmitted, with the UE located in the first network cell, that an initial second PTM configuration for the second network cell has been updated.

33. The computer-implemented method of claim 32, further comprising: The UE is caused to start a validity timer in response to receiving the notification that the initial second PTM configuration for the second network cell has been updated, wherein the UE discards the initial second PTM configuration for the second network cell after expiration of the validity timer.

34. The computer-implemented method of claim 1 , further comprising: The second PTM configuration is transmitted via the multicast control channel (MCCH) before expiration of a timer in response to a multicast control channel (MCCH) acquisition procedure initiated by the UE.

35. The computer-implemented method of claim 1 , further comprising: enabling the UE to join the multicast session of the multicast service when the UE is in an RRC connected state; Transmitting an RRC release message with a suspension configuration while the UE is in the RRC connected state; causing the UE to transition to the RRC inactive state based on the RRC release message with the suspension configuration; as well as The multicast session of the multicast service is transmitted to the UE in the RRC inactive state.

36. The computer-implemented method of claim 35, wherein the RRC release message with suspension configuration includes one or more of the PTM configuration for the first network cell and the PTM configuration for the second network cell.

37. The computer-implemented method of claim 23, further comprising: The second PTM configuration is provided via an RRC recovery procedure based on the UE failing to support PTM configuration acquisition via a multicast control channel (MCCH).

38. The computer-implemented method of claim 23, further comprising: The second PTM configuration is provided to the UE based on an RRC recovery procedure based on the UE failing to acquire a second updated PTM via multicast control channel (MCCH) acquisition before expiration of a timer.

39. The computer-implemented method of claim 23, further comprising: The second PTM configuration is provided via an RRC recovery procedure based on determining that signal quality between the UE and a base station is below a threshold.

40. The computer-implemented method of claim 23, further comprising: The second PTM configuration is provided via an RRC recovery procedure based on the UE failing to acquire a second updated PTM via Multicast Control Channel (MCCH) acquisition within a predefined number of MCCH modification periods.

41. A base station (BS), the BS comprising one or more processors configured to perform the computer-implemented method according to any one of claims 23 to 40.

42. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method of any one of claims 23 to 40.

Images