Method and UE for signaling multicast broadcast service interest indication

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure relates to a method 300a and a UE 101 for signaling a multicast broadcast service (MBS) interest indication (MII). The method includes transmitting an MII message to a source cell. The method further includes receiving, from the source cell, one of an RRC (Radio Resource Control) Receiving or an RRC Receiving with a Receiving WithSync, and receiving, from the source cell, one of the RRC Receiving and the RRC Receiving with the Receiving WithSync. In one embodiment, an RRC Receiving or an RRC Receiving with a Receiving WithSync is received during the movement of a UE (User Equipment), and the RRC Receiving or an RRC Receiving with a Receiving WithSync is received during the movement of the UE. The method further comprises the step of connecting with the target cell when one of the RRC (Radio Resource Control) Receiving and the RRC Receiving with the Receiving WithSync is received. The method further comprises the step of connecting with the target cell when one of the RRC Receiving and the RRC Receiving with the Receiving WithSync is received. The method finally includes sending the MII message to the target cell.

Description

Technical Field

[0001] This topic generally relates to telecommunications networks, and more specifically, but not exclusively, to methods and user equipment (UE) for signaling notification of multiple broadcast service (MBS) interest indication (MII) in communication systems. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in "sub-6GHz" bands such as 3.5GHz, but also in "above 6GHz" bands, including 28GHz and 39GHz, known as mmWave. Furthermore, 6G mobile communication technology (referred to as "super 5G systems") is being considered for implementation in THz bands (e.g., the 95GHz to 3THz band) to achieve transmission rates 50 times faster than 5G and ultra-low latency one-tenth that of 5G.

[0003] In the early stages of 5G mobile communication technology development, in order to support services and meet the performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization has been carried out on beamforming and massive MIMO for reducing radio wave path loss and increasing radio wave transmission distance in mmWave, dynamic operation of parameter sets (e.g., operating multiple subcarrier spacings) and time slot formats to support efficient utilization of mmWave resources, initial access technologies to support multi-beam transmission and broadband, definition and operation of bandwidth portions (BWP), new channel coding and decoding methods (such as low-density parity-check (LDPC) codes for large data transmissions and polar codes for highly reliable control information transmission), L2 preprocessing, and network slicing for providing dedicated networks for specific services.

[0004] Currently, considering the services that 5G mobile communication technology will support, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology. Furthermore, there are already discussions on technologies such as Vehicle-to-Everything (V2X) for assisting autonomous vehicle driving decisions and enhancing user convenience based on information sent by the vehicle regarding its location and status; New Radio Unlicensed (NR-U) designed to ensure system operation complies with various regulatory requirements in unlicensed frequency bands; NR UE power saving; Non-Terrestrial Networks (NTNs) for providing coverage in areas where communication with terrestrial networks is unavailable; and physical layer standardization for positioning technologies.

[0005] In addition, standardization is underway in air interface architectures / protocols for technologies such as Industrial Internet of Things (IIoT) to support new services through interoperability and convergence with other industries; Integrated Access and Backhaul (IAB) for nodes to provide network service area extension by supporting wireless backhaul and access links in an integrated manner; mobility enhancements including conditional handover and Dual Active Protocol Stack (DAPS) handover; and two-step random access (2-step RACH for NR) to simplify the random access process. Standardization is also underway in system architectures / services for 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, as well as for mobile edge computing (MEC) based on UE location reception services.

[0006] With the commercialization of 5G mobile communication systems, the number of connected devices will increase exponentially, necessitating enhanced functionality and performance of 5G mobile communication systems, as well as integrated operation of connected devices. To this end, new research is planned related to extended reality (XR) that efficiently supports augmented reality (AR), virtual reality (VR), mixed reality (MR), etc.; 5G performance improvements and complexity reductions through the utilization of artificial intelligence (AI) and machine learning (ML); AI service support; metaverse service support; and drone communication.

[0007] Furthermore, this development of 5G mobile communication systems will serve as the foundation for not only developing new waveforms for providing coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies (such as full-dimensional MIMO (FD-MIMO), array antennas, and large antennas), metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS), but also for developing full-duplex technologies to improve the frequency efficiency of 6G mobile communication technology and improve system networks, AI-based communication technologies for system optimization by leveraging satellites and artificial intelligence (AI) from the design stage and internalizing end-to-end AI support capabilities, and next-generation distributed computing technologies for providing services with complexity levels exceeding the limits of UE operational capabilities by utilizing ultra-high-performance communication and computing resources.

[0008] User equipment (UE) may be associated with one or more cells, carriers, frequencies, bandwidth portions (BWP) cell groups (e.g., primary cell group (MCG) or secondary cell group (SCG)), tracking area (TA), non-public network (NPN), public land mobile network (PLMN), network, subscriber identification module (SIM), mobile network operator (MNO) (or simply operator).

[0009] A UE may receive services (e.g., unicast, multicast, broadcast services) on one or more networks or operators. Coordination across these networks or operators may or may not exist. Furthermore, there may be no uplink signaling regarding various broadcast reception states (such as broadcast reception under Radio Resource Control Idle (RRC_IDLE) or Radio Resource Control Inactive (RRC_INACTIVE)). Therefore, the relevant networks may not be aware that the UE is receiving services such as broadcast services.

[0010] For simplicity, without loss of generality, this article considers a maximum of two networks / operators. In the example, consider a UE receiving unicast service on network (NW)-A managed by operator X, and the UE also receiving broadcast service on another network (NW)-B managed by operator Y. In this scenario, NW-A may be unaware that the UE is receiving a broadcast service because this information is not signaled to NW-B, as the UE may be in an RRC_IDLE or RRC_INACTIVE state. Even if this information is signaled to NW-B, NW-B may not have any coordination with NW-A. Because NW-A is unaware that the UE is receiving a broadcast service on NW-B, some of the UE's baseband or hardware resources (processing) capabilities are exhausted while supporting these services. Therefore, NW-A may have incorrect assessments / information about the UE's capabilities and may incorrectly configure the UE with inappropriate settings. For example, NW-A can be configured with a full configuration assuming all baseband resources or processing capabilities (e.g., carrier aggregation configuration with the maximum number of component carriers or serving cells or dual connectivity). However, as a result, the UE may not be able to support this configuration and / or will not function optimally in terms of device or service performance and / or a satisfactory user experience.

[0011] In summary, a UE can receive unicast services from the serving cell and multicast broadcast services (MBS) from non-serving cells belonging to the same or different networks. Furthermore, the networks can belong to the same or different operators. Therefore, the UE needs to notify the serving cell of the cell broadcast reception status on the non-serving cells so that the serving cell can appropriately configure the UE based on its available baseband resources or processing capabilities.

[0012] Furthermore, the UE may encounter two scenarios: synchronous RRC reconfiguration that may occur during UE movement (e.g., handover) and RRC reconstruction that may occur in the event of a radio link failure. In these scenarios, the transmission of MBS Interest Indication (MII) messages may be unreliable, and robustness of MII transmission needs to be ensured. Additionally, the target serving cell (also known as the primary cell or PCell) may not provide broadcast signaling for System Information Block Index 21 (SIB21), thus the UE may face the problem of being unable to initiate MII transmission.

[0013] The information disclosed in the background section of this disclosure is intended only to enhance the understanding of the general context of this disclosure and should not be construed as an admission or in any way implying that the information constitutes prior art known to those skilled in the art. Summary of the Invention

[0014] Technical issues

[0015] The purpose of this application is to address at least one drawback of the prior art.

[0016] Solution to the problem

[0017] In embodiments, this disclosure relates to a method for signaling notification of a Multicast Broadcast Service (MBS) Interest Indication (MII). The method includes sending an MII message to a source cell. The method also includes receiving from the source cell either an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync. The RRC_Reconfiguration or the RRC_Reconfiguration with reconfigurationWithSync is received during UE mobility. The method further includes connecting to a target cell upon receiving either the RRC_Reconfiguration or the RRC_Reconfiguration with reconfigurationWithSync. Finally, the method includes sending an MII message to the target cell upon receiving an SIB1 including the parameter nonServingCellMII from the target cell.

[0018] In another embodiment, this disclosure relates to a method for signaling notification of a Multicast Broadcast Service (MBS) Interest Indication (MII). The method further includes sending an MII message to a source cell. The method also includes performing conditional reconfiguration. The method further includes connecting to a target cell based on conditional reconfiguration. Finally, the method includes sending an MII message to the target cell when an SIB1 including the parameter nonServingCellMII is received from the target cell.

[0019] In another embodiment, this disclosure relates to a method for signaling notification of a Multicast Broadcast Service (MBS) Interest Indication (MII). The method includes sending an MII message to a source cell. The method also includes receiving an RRC Reestablishment from the source cell. The RRC Reestablishment is received during a radio link failure. The method further includes connecting to a target cell based on the RRC Reestablishment. Finally, the method includes sending an MII message to the target cell when an SIB1 including the parameter nonServingCellMII is received from the target cell.

[0020] This disclosure also relates to a user equipment (UE) for signaling notification of a Multicast Broadcast Service (MBS) Interest Indication (MII). The UE includes a processor and memory. The processor is configured to send an MII message to a source cell. The processor is also configured to receive, from the source cell, one of an RRC_Reconfiguration or an RRC_Reconfiguration with configuration with synchronization. The RRC_Reconfiguration or the RRC_Reconfiguration with configuration with synchronization is received during UE movement. The processor is further configured to connect to a target cell upon receiving one of the RRC_Reconfiguration or the RRC_Reconfiguration with configuration with synchronization. Finally, the processor is configured to send an MII message to the target cell upon receiving an SIB1 including the parameter nonServingCellMII from the target cell.

[0021] This disclosure also relates to a user equipment (UE) for signaling notification of a Multicast Broadcast Service (MBS) Interest Indication (MII). The UE includes a processor and a memory. The processor is configured to send an MII message to a source cell. The processor is also configured to perform conditional reconfiguration. The processor is further configured to reconfigure a connection with a target cell based on conditional reconfiguration. Finally, the processor is configured to send an MII message to the target cell when it receives an SIB1 including the parameter nonServingCellMII from the target cell.

[0022] This disclosure also relates to a user equipment (UE) for signaling notification of a Multicast Broadcast Service (MBS) Interest Indication (MII). The UE includes a processor and memory. The processor is configured to send an MII message to a source cell. The processor is also configured to receive an RRCReestablishment from the source cell. The RRCReestablishment is received during a radio link failure. The processor is further configured to connect to a target cell based on the RRCReestablishment. Finally, the processor is configured to send an MII message to the target cell when it receives an SIB1 including the parameter nonServingCellMII from the target cell.

[0023] The foregoing description of the invention is merely illustrative and is not intended to be limiting in any way. Other aspects, embodiments, and features will become clear from the accompanying drawings and the following detailed description, in addition to the illustrative aspects, embodiments, and features described above.

[0024] Beneficial effects of the invention

[0025] Embodiments of this disclosure provide methods and apparatus for signaling notifications of Multicast Broadcast Service (MBS) Interest Indicators (MIIs). This can improve the reliability and robustness of MII transmission. Attached Figure Description

[0026] Exemplary embodiments are illustrated in conjunction with the accompanying drawings, which form part of this disclosure, and are used together with the specification to explain the disclosed principles. In the drawings, the leftmost numeral of the reference numeral identifies the drawing in which that numeral first appears. The same numerals are used throughout the drawings to refer to features and components. Some embodiments of systems and / or methods according to this subject matter will now be described by way of example only and with respect to the accompanying drawings, wherein:

[0027] Figure 1 An environment for signaling notification of Multicast Service (MBS) Interest Indication (MII) according to some embodiments of the present disclosure is illustrated.

[0028] Figure 2 A UE according to some embodiments of this disclosure is shown.

[0029] Figure 3a , Figure 3b and Figure 3c A flowchart is shown of an exemplary method for signaling notification of MII between a UE and a communication network according to some embodiments of this disclosure.

[0030] Figure 4a , Figure 4b and Figure 4c A message flow diagram of an exemplary method for signaling notification of MII between a system and a UE, according to some embodiments of the present disclosure, is shown.

[0031] Figure 5 A computer system according to some embodiments of the present disclosure is shown.

[0032] Figure 6 A flowchart illustrating MII transport in a synchronous RRC reconfiguration scenario according to some embodiments of this disclosure is shown; and

[0033] Figure 7 A flowchart of MII transmission in an RRC reconstruction scenario according to some embodiments of the present disclosure is shown.

[0034] Those skilled in the art will understand that any block diagram herein represents a conceptual view of an illustrative system embodying the principles of the subject matter. Similarly, it should be understood that any flowchart, diagram, state transition diagram, pseudocode, etc., represents various processes that can be substantially represented in a computer-readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown. Detailed Implementation

[0035] Before proceeding with the detailed description below, it may be helpful to define certain words and phrases used throughout this patent document: the terms “comprising” and “including” and their derivatives refer to, but are not limited to, others; the term “or” is inclusive, referring to and / or; the phrases “associated with” and “associated with” and their derivatives may refer to, including, being included in, interconnected with, containing, contained within, connected to or connected to, coupled to or coupled to, able to communicate with, cooperate with, interleaved, juxtaposed, proximate, bound to or bound to, having, having the properties of, etc.; and the term “controller” means any device, system or part thereof that controls at least one operation, such device may be implemented in hardware, firmware or software or some combination of at least two of these. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether local or remote.

[0036] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drives, compact discs (CDs), digital video optical discs (DVDs), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media in which data can be permanently stored and media in which data can be stored and later overwritten, such as rewritable optical discs or erasable memory devices.

[0037] Definitions of certain words and phrases are provided throughout this patent document, and those skilled in the art will understand that, in many cases (if not most), such definitions apply to the prior and future use of the words and phrases defined in this way.

[0038] In this document, the word "exemplary" is used to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

[0039] While this disclosure is readily adaptable to various modifications and alternatives, specific embodiments thereof have been illustrated by way of example in the accompanying drawings and will be described in detail below. However, it should be understood that this disclosure is not intended to be limited to the particular forms disclosed, but rather, this disclosure is intended to cover all modifications, equivalents, and substitutions falling within the spirit and scope of this disclosure.

[0040] The terms “comprising,” “including,” or any other variations thereof are intended to cover non-exclusive inclusion, such that an arrangement, device, or method that includes a list of components or steps includes not only those components or steps but may also include other components or steps not expressly listed or inherent to such arrangement, device, or method. In other words, without further constraints, one or more elements in an apparatus or system or device that begins with “comprising…” do not exclude the presence of other elements or additional elements in the apparatus or system or device.

[0041] The terms “comprising,” “including,” or any other variations thereof are intended to cover non-exclusive inclusion, such that an arrangement, apparatus, or method that includes a list of components or steps includes not only those components or steps but may also include other components or steps not expressly listed or inherent to such arrangement, apparatus, or method. In other words, without further constraints, one or more elements in a system or apparatus that begins with “comprising…” do not exclude the presence of other elements or additional elements in the system or method.

[0042] Unless otherwise expressly stated, the terms “an embodiment,” “an embodiment,” “multiple embodiments,” “the embodiment,” “these multiple embodiments,” “one or more embodiments,” “some embodiments,” and “an embodiment” refer to “one or more (but not all) embodiments of this disclosure.”

[0043] Unless otherwise expressly stated, the terms “including,” “comprising,” “having,” and variations thereof refer to “including but not limited to.”

[0044] As used herein, the term "communication" can refer to the receiving, retrieval, sending, transmission, provision, etc., of information (e.g., data, signals, messages, instructions, commands, etc.). Communication between one unit (e.g., a device, system, component of a device or system, combination thereof, etc.) and another unit means that the first unit is able to receive information directly or indirectly from and / or send information to the other unit. This can refer to a direct or indirect connection that is inherently wired and / or wireless (e.g., a direct communication connection, an indirect communication connection, etc.). Furthermore, two units can communicate with each other, even if the transmitted information can be modified, processed, relayed, and / or routed between the first and second units. For example, the first unit can communicate with the second unit even if the first unit passively receives information and does not actively send information to the second unit. As another example, the first unit can communicate with the second unit if at least one intermediate unit (e.g., a third unit located between the first and second units) processes information received from the first unit and transmits the processed information to the second unit. In some non-limiting embodiments, a message can refer to a network packet (e.g., a data packet, etc.) that includes data. It should be understood that various other arrangements are possible.

[0045] As used herein, the term "user equipment" or "UE" can refer to any electronic device that can be carried and operated by a user, which also provides remote communication capabilities to a network and supports cellular communication. Examples of remote communication capabilities include the use of mobile phone (wireless) networks, wireless data networks (e.g., 5G or similar networks), or any other communication medium that can provide access to a communication network. Examples of user equipment include mobile phones (e.g., cellular phones), PDAs, tablet computers, netbooks, laptop computers, personal computers, etc. Mobile devices can include any suitable hardware and software for performing such functions, and can also include multiple devices or components (e.g., when a device remotely accesses a network via a tethered connection to another device, i.e., using another device as a relay, the two devices used together can be considered a single mobile device).

[0046] As used herein, the term "processor" can refer to any suitable one or more data computing devices. A processor can include one or more microprocessors that work together to perform a desired function. A processor can include a CPU that includes at least one high-speed data processor sufficient to execute program components for performing user and / or system-generated requests. A CPU can be a microprocessor such as AMD's Athlon, Duron, and / or Opteron; IBM and / or Motorola's PowerPC; IBM and Sony's Cell processors; Intel's Celeron, Itanium, Pentium, Xeon, and / or XScale; and / or similar processors.

[0047] As used herein, the term "memory" can refer to any suitable one or more devices capable of storing electronic data. Suitable memory can include non-transitory computer-readable media whose storage can be executed by a processor to implement desired methods. Examples of memory can include one or more memory chips, disk drives, etc. Such memory can be operated using any suitable electrical, optical, and / or magnetic modes of operation.

[0048] As used herein, the term "SIB1" refers to "System Information Block 1" and contains information relevant to assessing whether a UE is allowed to access the cell, and defines the scheduling of other system information. It also contains radio resource configuration information common to all UEs and prohibition information applied to unified access control.

[0049] As used herein, the term “conditional reconfiguration” refers to one of the conditions for handover, PCell condition additions or changes that enable the UE to make a final decision on the timing of the handover based on the surveillance radio channel.

[0050] As used herein, the term "serving cell" can refer to the primary cell (PCell) in a mobile network that is responsible for managing the active radio connections, data transmission, and control signaling of user equipment.

[0051] As used herein, the term “non-serving cell” can refer to a neighboring cell, such as a secondary cell (SCell) in carrier aggregation or a cell in a neighboring network, which does not actively handle the UE’s connection but can be measured for potential handover or load balancing.

[0052] In the following detailed description of embodiments of this disclosure, reference is made to the accompanying drawings, which form part of and illustrate specific embodiments in which this disclosure may be practiced. These embodiments have been described in sufficient detail to enable those skilled in the art to practice this disclosure, and it should be understood that other embodiments may be utilized and changes may be made without departing from the scope of this disclosure. Therefore, the following description should not be considered limiting.

[0053] Embodiments of this disclosure disclose methods and systems for robust interest indication signaling for multicast broadcast services (MBS) using New Radio (NR) and 5th Generation Radio Access Technology (RAT). This disclosure discloses how to notify network signaling of MBS interest indication (MII) reports when a UE is simultaneously receiving broadcast and unicast from one or more networks.

[0054] The embodiments of this document implement methods and systems for robust interest indication signaling for multicast broadcast services (MBS) using New Radio (NR) and 5th Generation Radio Access Technology (RAT). Embodiments of this disclosure disclose how to notify network signaling of MBS interest indication (MII) reports when a UE is simultaneously receiving broadcast and unicast from one or more networks.

[0055] In an embodiment, the NR MBS service may include a multicast service, for which the network transmits public user data intended to be received only by a group of specific UEs that have joined a specific multicast group. Furthermore, the NR MBS service may include a broadcast service, for which the network transmits public user data that can be received by all UEs interested in receiving the service.

[0056] The network can provide MBS services in a limited portion of the network, and the coverage area of ​​MBS services can be a cell or larger.

[0057] The 5G core network (CN) can deliver MBS user data to the radio access network (RAN) using various delivery methods such as individual delivery and shared delivery. In individual delivery, for each individual UE receiving MBS service, the CN can deliver a separate copy of the MBS user data packet to the RAN (i.e., via per UE PDU session, similar to the case of unicast delivery). In shared delivery, the CN delivers a single copy of the MBS user data to the RAN (i.e., via a shared PDU session / tunnel), where the RAN handles delivery to one or more UEs.

[0058] In addition to MBS services, UEs can also participate in unicast services, and in some scenarios, UEs can also utilize unicast services and MBS services from one or more networks. In summary, the embodiments described herein consider UEs receiving unicast services from the serving cell and also receiving MBS services from non-serving cells belonging to the same or different networks.

[0059] In one embodiment, the UE can receive unicast on at least one serving cell on a first network, and the UE can receive at least one MBS service (e.g., MBS broadcast) on at least one non-serving cell on a second network. The UE can use a MII message to report MBS broadcast reception on a non-serving cell to the serving cell. In another embodiment, the UE can proactively report a MII message to the serving cell before actually starting to receive MBS service on a non-serving cell. For example, although the UE is interested in MBS broadcast service on a non-serving cell, the service may not have started yet. In another embodiment, when unicast reception has not yet been received on the serving cell and the UE is receiving on a non-serving cell or may be interested in receiving MBS service on a non-serving cell, the UE may not report a MII message to the serving cell.

[0060] In this embodiment, when the UE can be in the Radio Resource Control Connection (RRC_CONNECTED) state on the serving cell, the UE can initiate an MBS Interest Indication procedure corresponding to MBS broadcast reception on a non-serving cell in at least one of the following situations:

[0061] a) When broadcast reception begins from a non-serving cell;

[0062] b) When broadcast reception from a non-serving cell is stopped;

[0063] c) When interest in receiving broadcasts from non-serving cells is lost;

[0064] d) When interest arises in receiving broadcasts from a non-serving cell;

[0065] e) When initiating a broadcast session from a non-serving cell;

[0066] f) When stopping a broadcast session from a non-serving cell;

[0067] g) When interest in broadcast sessions from non-serving cells is lost;

[0068] h) When interest arises in a broadcast session from a non-serving cell;

[0069] i) When the frequency of broadcast reception from a non-serving cell changes;

[0070] j) When the bandwidth of broadcast reception from a non-serving cell changes;

[0071] k) When the public frequency resource (CFR) received from a broadcast from a non-serving cell changes;

[0072] l) When coverage of a non-serving cell providing broadcast reception is lost; and / or

[0073] m) When the subcarrier spacing of broadcast reception from a non-serving cell changes.

[0074] In the embodiments, robustness of MII transmission can be ensured for the ReconfigurationWithSync and rebuild processes. Furthermore, MII transmission can be re-initiated if it occurs one second before receiving an RRCReconfiguration message or an RRCReestablishment message, or after receiving an RRCReconfiguration message due to conditional reconfiguration execution.

[0075] In this embodiment, robustness of Rep. 18 (Rel-18) MII transmission (i.e., related to shared processing for unicast and broadcast reception) is ensured when the primary cell (PCell) does not broadcast SIB21. The UE can receive unicast services on the serving cell and also MBS broadcast services on non-serving cells. Due to the simultaneous reception of unicast and broadcast services, MII transmission can essentially provide the UE with dynamic baseband or hardware processing capabilities. For Rep. 18 MII, no broadcast service is required from the serving cell's gNodeB (gNB), and SIB21 may not be broadcast by the PCell. However, SIB1, including non-ServingCell MII, is considered for PCell-permitted Rep. Importantly, the serving cell's gNB interprets the non-serving cell information in the Rep. 18 MII for unicast service scheduling. Therefore, this disclosure considers non-servingCell MII provided by the PCell in SIB1 for initiating MII transmission during ReconfigurationWithSync and rebuild scenarios.

[0076] In an embodiment, such as Figure 6 As shown, when the PCell provides non-servingCellMII in SIB1, the UE initiates the transmission of the MII message during the ReconfigurationWithSync scenario. That is, for the case where the MII transmission is initiated one second before the RRCReconfiguration message is received or after the RRCReconfiguration message is received due to conditional reconfiguration execution, the ReconfigurationWithSync is included in the RRCReconfiguration message.

[0077] In the embodiments, a standard example is provided for processing the UE's reception of RRCReconfiguration including reconfigurationWithSync and initiating the transmission of MII messages, as shown below.

[0078] Example 1:

[0079]

[0080] In an embodiment, such as Figure 7 As shown, when the PCell provides non-servingCellMII in SIB1, the UE can initiate the transmission of MII messages during the reconstruction scenario, that is, for the case where the MII message transmission is initiated one second before the RRCReestablishment message is received.

[0081] A standard example is provided for handling the UE's reception of RRCReestablishment and initiation of MII transmission, as shown below.

[0082] Example 2:

[0083]

[0084] In an embodiment, the MBS Interest Indication (MII) message initiated during ReconfigurationWithSync and rebuild scenarios includes a report on MBS reception on the serving cell (when SIB21 is provided by the PCell) and / or a report on MBS reception on a non-serving cell (e.g., MBS broadcast) (when the non-ServingCell MII is provided by the PCell in SIB1). For example, this could be for cases where an MII is initiated one second before receiving an RRCReconfiguration message or an RRCReestablishment message, or after receiving an RRCReconfiguration message due to conditional reconfiguration execution.

[0085] In embodiments, MBS interest indication messages initiated during ReconfigurationWithSync and reconstruction scenarios include empty reports for MBS reception on the serving cell (when the PCell does not provide SIB21 but provides a non-ServingCell MII in SIB1) and / or empty reports for MBS reception on non-serving cells (e.g., MBS broadcast) (when the PCell provides SIB21 but does not provide a non-ServingCell MII in SIB1). For example, this could be for cases where an MII is initiated one second before receiving an RRCReconfiguration message or an RRCReestablishment message, or after receiving an RRCReconfiguration message due to conditional reconfiguration execution.

[0086] In an embodiment, during a mobile scenario (e.g., inter-node message exchange during handover), MBS interest indication (MII) messages transmitted from the source cell / gNB to the target cell / gNB report MBS reception on the serving cell (when the target cell / gNB supports MII reporting for MBS broadcast services on the serving cell) and / or report MBS reception on non-serving cells (e.g., MBS broadcast) (when the target cell / gNB supports MII reporting for MBS broadcast reception on non-serving cells).

[0087] In an embodiment, the MBS interest indication message transmitted from the source cell / gNB to the target cell / gNB during a mobile scenario (e.g., inter-node message exchange during handover) includes an empty report for MBS reception on the serving cell (when the target cell / gNB does not support MII reports for MBS broadcast reception on the serving cell but supports MII reports for MBS broadcast reception on non-serving cells) and / or an empty report for MBS reception on non-serving cells (e.g., MBS broadcast) (when the target cell / gNB supports MII reports for MBS broadcast reception on the serving cell but does not support MII reports for MBS broadcast reception on non-serving cells).

[0088] Figure 1 An environment 100 for signaling notification of Multicast Service (MBS) Interest Indication (MII) is illustrated. Environment 100 may include User Equipment (UE) 101, source cell 102, and target cell 103. Various components such as source cell 102 and target cell 103 belong to a communication network and may be implemented as software or hardware components. Environment 100 may include a system 104 for signaling notification of MII, and includes at least source cell 102 and target cell 103.

[0089] In this embodiment, source cell 102 may be a serving cell, and target cell 103 may be a non-serving cell that can provide broadcast services. In this embodiment, source cell 102 and target cell 103 may belong to the same or different networks / operators.

[0090] In this embodiment, UE 101 can be configured to perform the following operations: UE 101 can be configured to send an MII message to source cell 102. UE 101 is also configured to receive one of the following from the source cell: an RRC_Reconfiguration or an RRC_Reconfiguration with configuration with synchronization. The RRC_Reconfiguration or the RRC_Reconfiguration with configuration with synchronization is received during UE mobility. UE 101 sends the MII message to the source cell during a time period prior to receiving one of the RRC_Reconfiguration or the RRC_Reconfiguration with configuration with synchronization. For example, if UE 101 initiates the transmission of an MBSInterestIndication message in the last second before receiving the RRCReconfiguration message, then in the subsequent connection between UE 101 and target cell 102, UE 101 can send an MII message to target cell 103 in response to receiving SIB1 including nonServingCellMII from target cell 103. In an embodiment, UE 101 may connect to target cell 103 upon receiving either RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync.

[0091] In this embodiment, the MII message includes, but is not limited to, providing subcarrier spacing information, carrier frequency, frequency band indicator, and common frequency resources (CFR) for one or more non-serving cells of the MBS. Furthermore, the CFR may be represented as the CFR bandwidth in terms of the number of physical resource blocks, or as the CFR location and bandwidth.

[0092] In another embodiment, UE 101 is configured to send an MII message to source cell 102. UE 101 can then be configured to perform conditional reconfiguration. UE 101 can then be configured to connect to target cell 103 based on conditional reconfiguration. UE 101 can then send an MII message to target cell 103.

[0093] In an embodiment, the UE configured to connect to the target cell 103 is also configured to receive SIB1, which includes nonServingCellMII, from the target cell 103.

[0094] In another embodiment, UE 101 is configured to send an MII message to source cell 102. UE 101 is then configured to receive an RRCReestablishment from source cell 102. The RRCReestablishment is received during a radio link failure. UE 101 is then configured to connect to target cell 103 based on the RRCReestablishment. UE 101 subsequently sends an MII message to target cell 103 in response to receiving an SIB1 including a nonServingCell MII from target cell 103.

[0095] In this embodiment, UE 101 sends an MII message to source cell 102 during the time period prior to receiving the RRCReestablishment message. For example, but not limited to, if UE 101 initiates the transmission of an MBSInterestIndication message in the last second before receiving the RRCReconfiguration message, then during the subsequent connection between UE 101 and target cell 102, UE 101 may send an MII message to target cell 103 in response to receiving SIB1 including nonServingCellMII from target cell 103.

[0096] Figure 2 A detailed block diagram of user equipment (UE) 101 is shown. UE 101 may include a processor 203, an input / output (I / O) interface 202, a memory 204, and a module 206. The memory 204 may also include data 205. The module 206 may also include modules such as, but not limited to, a transceiver module 207, a connectivity module 208, an execution module 209, and other modules 210.

[0097] In an embodiment, data 205 may include various temporary data and files generated by module 206.

[0098] As used herein, the term "module" can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a hardware processor (shared, dedicated, or grouped) and memory executing one or more software or firmware programs, combinational logic circuitry, and / or other suitable components that provide the described functionality. In an implementation, each of modules 206 can be configured as an independent hardware computing unit. In embodiments, other modules 209 can be used to perform various miscellaneous functions of UE 101. It should be understood that such modules 206 can be represented as a single module or a combination of different modules.

[0099] In this embodiment, transceiver module 207 can be configured to send an MII message to source cell 102. The transceiver module can then be configured to receive either an RRC_Reconfiguration or an RRC_Reconfiguration with `reconfigurationWithSync` from source cell 102. The RRC_Reconfiguration or the RRC_Reconfiguration with `reconfigurationWithSync` is received during UE movement. UE 101 sends the MII message to source cell 102 during a time period prior to receiving either the RRC_Reconfiguration or the RRC_Reconfiguration with `reconfigurationWithSync`. For example, this time period could be, but is not limited to, one second prior to receiving the RRC_Reconfiguration or the RRC_Reconfiguration with `reconfigurationWithSync`.

[0100] In an embodiment, the MII message includes at least one of the following: subcarrier spacing information, carrier frequency, frequency band indicator, and CFR (Carrier Freeway) for one or more non-serving cells of the MBS. Furthermore, the CFR may be represented as the CFR bandwidth in terms of the number of physical resource blocks, or as the CFR location and bandwidth.

[0101] The connection module 208 can be configured to connect to the target cell 103 upon receiving either an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync.

[0102] Then, transceiver module 207 can be configured to receive SIB1, including nonServingCellMII, from target cell 103. Then, transceiver module 207 can be configured to send MII messages to target cell 103.

[0103] In this embodiment, source cell 102 may be a serving cell, and target cell 103 may be a non-serving cell that can provide broadcast services. In this embodiment, source cell 102 and target cell 103 may belong to the same or different networks / operators.

[0104] In another embodiment, transceiver module 207 is configured to send MII messages to source cell 102.

[0105] Execution module 209 is configured to perform conditional reconfiguration based on radio link conditions. Then, connection module 208 is configured to connect to target cell 103 based on conditional reconfiguration. Transceiver module 207 is then configured to receive SIB1, including the nonServingCell MII, from target cell 103. Transceiver module 207 can be configured to send MII messages to target cell 103.

[0106] In an embodiment, the MII message includes at least one of the following: subcarrier spacing information, carrier frequency, frequency band indicator, and CFR (Carrier Freeway) for one or more non-serving cells of the MBS. Furthermore, the CFR may be represented as the CFR bandwidth in terms of the number of physical resource blocks, or as the CFR location and bandwidth.

[0107] In another embodiment, transceiver module 207 is configured to send an MII message to source cell 102. Transceiver module 207 is also configured to receive an RRCReestablishment from source cell 102. In this embodiment, the RRCReestablishment is received during a radio link failure.

[0108] Connection module 208 is configured to connect to target cell 103 based on RRCReestablishment. Transceiver module 207 is configured to receive SIB1, including nonServingCell MII, from target cell 103. Subsequently, transceiver module 207 is configured to send MII messages to target cell 103.

[0109] UE 101 sends an MII message to source cell 102 during the period prior to receiving the RRCReestablishment. For example, this period may be, but is not limited to, one second prior to receiving the RRCReestablishment.

[0110] In an embodiment, the MII message includes at least one of the following: subcarrier spacing information, carrier frequency, frequency band indicator, and CFR (Carrier Freeway) for one or more non-serving cells of the MBS. Furthermore, the CFR may be represented as the CFR bandwidth in terms of the number of physical resource blocks, or as the CFR location and bandwidth.

[0111] Figure 3a A flowchart is depicted for an exemplary method 300a for signaling notification of MII between a UE and a communication network.

[0112] In step 301a, UE 101 may send an MII message to source cell 102. In an embodiment, the MII message includes at least one of the following: subcarrier spacing information of one or more non-serving cells providing MBS, carrier frequency, frequency band indicator, and common frequency resource (CFR). Furthermore, the CFR may be represented as CFR bandwidth in terms of the number of physical resource blocks, or as CFR location and bandwidth.

[0113] In step 302a, UE 101 may receive either an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync from source cell 102. UE 101 sends an MII message to the source cell during a time period prior to receiving either the RRC_Reconfiguration or the RRC_Reconfiguration with reconfigurationWithSync. For example, this time period may be, but is not limited to, one second.

[0114] In step 303a, UE 101 may connect to target cell 103 upon receiving either an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync. The UE can then receive SIB1, including nonServingCellMII, from target cell 103.

[0115] In this embodiment, source cell 102 may be a serving cell, and target cell 103 may be a non-serving cell that can provide broadcast services. In this embodiment, source cell 102 and target cell 103 may belong to the same or different networks / operators.

[0116] In step 304a, UE 101 may send an MII message to the target cell. The MII message may include at least one of the following: subcarrier spacing information, carrier frequency, frequency band indicator, and CFR of one or more non-serving cells providing MBS. Furthermore, the CFR may be represented as the CFR bandwidth in terms of the number of physical resource blocks, or as the CFR location and bandwidth.

[0117] Figure 3b A flowchart is depicted for an exemplary method 300a for signaling notification of MII between a UE and a communication network.

[0118] In step 301b, UE 101 may send an MII message to source cell 102. In an embodiment, the MII message includes at least one of the following: subcarrier spacing information of one or more non-serving cells providing MBS, carrier frequency, frequency band indicator, and CFR. Furthermore, the CFR may be represented as CFR bandwidth in terms of the number of physical resource blocks, or as CFR location and bandwidth. The MII message is sent after receiving the RRCReconfiguration message.

[0119] At step 302b, UE 101 may perform a conditional reconfiguration. The RRCReconfiguration message is applied as a result of the conditional reconfiguration.

[0120] In step 303b, UE 101 can conditionally reconfigure its connection with target cell 103. Then, UE 101 can receive SIB1, including the nonServingCellMII, from the target cell.

[0121] In this embodiment, source cell 102 may be a serving cell, and target cell 103 may be a non-serving cell that can provide broadcast services. In this embodiment, source cell 102 and target cell 103 may belong to the same or different networks / operators.

[0122] In step 304b, UE 101 may send an MII message to the target cell. The MII message may include at least one of the following: subcarrier spacing information, carrier frequency, frequency band indicator, and CFR of one or more non-serving cells providing MBS. Furthermore, the CFR may be represented as the CFR bandwidth in terms of the number of physical resource blocks, or as the CFR location and bandwidth.

[0123] Figure 3c A flowchart is depicted for an exemplary method 300a for signaling notification of MII between a UE and a communication network.

[0124] In step 301c, UE 101 may send an MII message to source cell 102. In an embodiment, the MII message includes at least one of the following: subcarrier spacing information of one or more non-serving cells providing MBS, carrier frequency, frequency band indicator, and CFR. Furthermore, the CFR may be represented as CFR bandwidth in terms of the number of physical resource blocks, or as CFR location and bandwidth.

[0125] At step 302c, UE 101 can receive RRCReestablishment from source cell 102. UE 101 sends an MII message to the source cell during a time period prior to receiving the RRCReestablishment. For example, this time period can be, but is not limited to, one second.

[0126] In step 303c, UE 101 can connect to target cell 103 based on RRCReestablishment. Then, the UE can receive SIB1, including nonServingCellMII, from target cell 103.

[0127] In this embodiment, source cell 102 may be a serving cell, and target cell 103 may be a non-serving cell that can provide broadcast services. In this embodiment, source cell 102 and target cell 103 may belong to the same or different networks / operators.

[0128] In step 304c, UE 101 may send an MII message to the target cell. The MII message may include at least one of the following: subcarrier spacing information, carrier frequency, frequency band indicator, and CFR of one or more non-serving cells providing MBS. Furthermore, the CFR may be represented as the CFR bandwidth in terms of the number of physical resource blocks, or as the CFR location and bandwidth.

[0129] Figure 4a A message flow diagram depicts an exemplary method for signaling notification of MII between system 104 and UE 101 for signaling notification of MII, according to some embodiments of the present disclosure.

[0130] In step 401a, the source cell 102 of system 104 is configured to receive an MII message from UE 101. This MII message includes at least one of the following: subcarrier spacing information of one or more non-serving cells providing MBS, carrier frequency, frequency band indicator, and CFR. Furthermore, the CFR may be represented as the CFR bandwidth in terms of the number of physical resource blocks, or as the CFR location and bandwidth.

[0131] In step 402a, the source cell 102 of system 104 can be configured to send one of an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync. The RRC_Reconfiguration or the RRC_Reconfiguration with reconfigurationWithSync can be sent while the UE is moving. The source cell 102 can receive the MII message during a time period prior to sending one of the RRC_Reconfiguration or the RRC_Reconfiguration with reconfigurationWithSync. For example, if UE 101 initiates the transmission of an MBSInterestIndication message in the last second before the source cell 102 sends the RRCReconfiguration message, then in the subsequent connection between UE 101 and the target cell 102, UE 101 can send an MII message to the target cell 103 in response to receiving an SIB1 including nonServingCellMII from the target cell 103.

[0132] In step 403a, target cell 103 may connect to UE 101 based on either RRC_Reconfiguration received by UE 101 or RRC_Reconfiguration with reconfigurationWithSync.

[0133] In step 404a, target cell 103 may send SIB1, which includes nonServingCellMII, to UE 101.

[0134] In step 405a, target cell 103 can receive MII messages from UE 101.

[0135] Figure 4b A message flow diagram depicts an exemplary method for signaling notification of MII between system 104 and UE 101 for signaling notification of MII, according to some embodiments of the present disclosure.

[0136] In step 401b, the source cell 102 of system 104 is configured to receive an MII message from UE 101. This MII message includes at least one of the following: subcarrier spacing information of one or more non-serving cells providing MBS, carrier frequency, frequency band indicator, and CFR. Furthermore, the CFR may be represented as the CFR bandwidth in terms of the number of physical resource blocks, or as the CFR location and bandwidth.

[0137] In step 402b, UE 101 can be configured to perform condition reconfiguration.

[0138] In step 403b, target cell 103 may reconfigure its connection with UE 101 based on conditions performed by UE 101.

[0139] In step 404b, target cell 103 may send SIB1, which includes nonServingCellMII, to UE 101.

[0140] In step 405b, target cell 103 can receive MII messages from UE 101.

[0141] Figure 4c A message flow diagram depicts an exemplary method for signaling notification of MII between system 104 and UE 101 for signaling notification of MII, according to some embodiments of the present disclosure.

[0142] In step 401c, the source cell 102 of system 104 is configured to receive an MII message from UE 101. This MII message includes at least one of the following: subcarrier spacing information of one or more non-serving cells providing MBS, carrier frequency, frequency band indicator, and CFR. Furthermore, the CFR may be represented as CFR bandwidth in terms of the number of physical resource blocks, or as CFR location and bandwidth.

[0143] At step 402c, source cell 102 of system 104 can be configured to send an RRCReestablishment. The RRCReestablishment can be sent in the event of a radio link failure. Source cell 102 can receive MII messages during the time period preceding the transmission of the RRCReestablishment. For example, if UE 101 initiates the transmission of an MBSInterestIndication message in the last second before source cell 102 sends the RRCReestablishment message, then in the subsequent connection between UE 101 and target cell 102, UE 101 can send an MII message to target cell 103 in response to receiving an SIB1 including nonServingCellMII from target cell 103.

[0144] In step 403c, target cell 103 can connect to UE 101 based on UE 101 receiving RRCReestablishment.

[0145] In step 404c, target cell 103 may send SIB1, which includes nonServingCellMII, to UE 101.

[0146] In step 405c, target cell 103 can receive MII messages from UE 101.

[0147] Figure 5 A block diagram of an exemplary computer system 400 for implementing embodiments consistent with this disclosure is shown. The computer system may be, but is not limited to, UE 101, source cell 102, or target cell 103. Computer system 600 may include a central processing unit (“CPU” or “processor”) 501. Processor 501 may include at least one data processor for performing processing. Processor 501 may include dedicated processing units such as an integrated system (bus) controller, a memory management control unit, a floating-point unit, a graphics processing unit, a digital signal processing unit, etc.

[0148] The processor 501 can be configured to communicate with one or more input / output (I / O) devices 508 and 509 via I / O interface 507. I / O interface 507 can employ communication protocols / methods such as, but not limited to, audio, analog, digital, mono, RCA, stereo, IEEE-1394, serial bus, Universal Serial Bus (USB), infrared, PS / 2, BNC, coaxial, component, composite, digital video interface (DVI), high-definition multimedia interface (HDMI), RF antenna, S-Video, VGA, IEEE 802.n / b / g / n / x, Bluetooth, cellular (e.g., Code Division Multiple Access (CDMA), High Speed ​​Packet Access (HSPA+), Global System for Mobile Communications (GSM), Long Term Evolution (LTE), WiMax, etc.).

[0149] Using I / O interface 507, computer system 600 can communicate with one or more I / O devices 508 and 509. For example, input device 508 can be an antenna, keyboard, mouse, joystick, (infrared) remote control, camera, card reader, fax machine, dongle, biometric reader, microphone, touchscreen, touchpad, trackball, stylus, scanner, storage device, transceiver, video device / source, etc. Output device 509 can be a printer, fax machine, video display (e.g., cathode ray tube (CRT), liquid crystal display (LCD), light-emitting diode (LED), plasma display panel (PDP), organic light-emitting diode (OLED), etc.), audio speakers, etc.

[0150] In some embodiments, processor 501 may be configured to communicate with external components, such as external computer systems, servers, or network components. Network interface 510 may employ connectivity protocols, including but not limited to direct connection, Ethernet (e.g., twisted pair 10 / 100 / 1000 Base T), Transmission Control Protocol / Internet Protocol (TCP / IP), Token Ring, IEEE 802.11a / b / g / n / x, etc.

[0151] In some embodiments, the processor 501 may be configured to communicate with the memory 503 (e.g., RAM, ROM, etc.) via a storage interface 502. The storage interface 502 may be connected to the memory 503 using connection protocols such as Serial Advanced Technology Attachment (SATA), Integrated Drive Electronics (IDE), IEEE-1394, Universal Serial Bus (USB), Fibre Channel, Small Computer System Interface (SCSI), etc., including but not limited to memory drivers, removable disk drives, etc. Memory drivers may also include drum memory, disk drives, magneto-optical drives, optical drives, redundant arrays of independent disks (RAID), solid-state storage devices, solid-state drives, etc.

[0152] Memory 503 may store a collection of program or database components, including but not limited to user interface 504, operating system 505, web browser 506, etc. In some embodiments, computer system 600 may store user / application data, such as data, variables, records, etc., as described in this disclosure. Such a database may be implemented as a fault-tolerant, relational, scalable, and secure database, such as Oracle® or Sybase®.

[0153] Operating system 505 facilitates resource management and operation of computer system 600. Examples of operating systems include, but are not limited to, Apple Macintosh® OS X, UNIX®, and UNIX-like system distributions (e.g., Berkeley Software Publisher). TM (BSD), FreeBSD TM NETBSD TM OPENBSD TM etc.), LINUX DISTRIBUTIONS TM (For example, RED HAT) TM UBUNTU TM KUBUNTU TM etc.), IBM TM OS / 2, Microsoft TM WINDOWS TM (XP) TMVISTA TM / 7 / 8, 10, etc.), APPLE® IOS TM Google® Android TM BLACKBERRY® OS, etc.

[0154] In some embodiments, the computer system 400 may implement the program components stored in the web browser 506. The web browser 506 may be a hypertext viewing application, such as Microsoft. ® INTERNET EXPLORER ® Google TM CHROME TM MOZILLA ® FIREFOX ® APPLE ® SAFARI ® Secure web browsing can be provided using protocols such as Hypertext Transfer Protocol Secure (HTTPS), Secure Sockets Layer (SSL), and Transport Layer Security (TLS). Web browsers can utilize technologies such as AJAX, DHTML, and Adobe... ® FLASH ® JAVASCRIPT ® JAVA ® Application programming interfaces (APIs), etc. In some embodiments, the computer system 600 may implement program components stored in the mail server. The mail server may be an Internet mail server, such as Microsoft Exchange. The mail server may utilize technologies such as Dynamic Server Pages (ASP), ActiveX, etc. ® ANSI ® C++ / C#, Microsoft ® .NET, CGI SCRIPTS, JAVA ® JAVASCRIPT ® PERL ® PHP, Python ® WEBOBJECTS ® Mail servers can utilize communication protocols such as Internet Message Access Protocol (IMAP), Message Passing Application Programming Interface (MAPI), and Microsoft... ® Email clients can be stored in various formats, including Point of Post (POP) and Simple Mail Transfer Protocol (SMTP). In some embodiments, the computer system 600 may implement a program component for storing an email client. The email client can be an email viewing application, such as Apple's... ®MAIL, MICROSOFT ® ENTOURAGE ® MICROSOFT ® OUTLOOK ® MOZILLA ® THUNDERBIRD ® wait.

[0155] Furthermore, embodiments consistent with this disclosure may be implemented using one or more computer-readable storage media. A computer-readable storage medium refers to any type of physical memory capable of storing processor-readable information or data. Therefore, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor to perform steps or stages consistent with the embodiments described herein. The term "computer-readable medium" should be understood to include tangible articles and exclude carrier waves and transient signals, i.e., it is non-transitory. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, non-volatile memory, hard disk drives, CD-ROMs, DVDs, flash memory drives, magnetic disks, and any other known physical storage media.

[0156] The described operations can be implemented as methods, systems, or articles of art using standard programming and / or engineering techniques to produce software, firmware, hardware, or any combination thereof. The described operations can be implemented as code held in a "non-transitory computer-readable medium," wherein a processor can read and execute the code from the computer-readable medium. A processor is at least one of a microprocessor and a processor capable of processing and executing queries. Non-transitory computer-readable media can include media such as magnetic storage media (e.g., hard disk drives, floppy disks, magnetic tapes, etc.), optical storage devices (CD-ROMs, DVDs, optical discs, etc.), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, flash memory, firmware, programmable logic, etc.). Furthermore, non-transitory computer-readable media can include all computer-readable media other than transient ones. The code implementing the described operations can also be implemented in hardware logic (e.g., integrated circuit chips, programmable gate arrays (PGAs), application-specific integrated circuits (ASICs), etc.).

[0157] "Article of manufacture" includes a non-transitory computer-readable medium and / or hardware logic in which code can be implemented. A device in which code implementing embodiments of the described operations is encoded may include computer-readable medium or hardware logic. Of course, those skilled in the art will recognize that many modifications can be made to this configuration without departing from the scope of this disclosure, and that the article of manufacture may include suitable information-carrying media known in the art.

[0158] Unless otherwise expressly stated, the terms “an embodiment,” “an embodiment,” “multiple embodiments,” “the embodiment,” “these multiple embodiments,” “one or more embodiments,” “some embodiments,” and “an embodiment” refer to “one or more (but not all) embodiments of this disclosure.”

[0159] Unless otherwise expressly stated, the terms “including,” “comprising,” “having,” and variations thereof refer to “including but not limited to.”

[0160] Unless otherwise expressly stated, the list of items does not imply that any or all items are mutually exclusive.

[0161] Unless otherwise expressly stated, the terms “a,” “an,” and “the” mean “one or more.”

[0162] The description of embodiments having several components that communicate with each other does not imply that all of these components are required. Rather, various optional components are described to illustrate various possible embodiments of this disclosure.

[0163] When a single device or item is described herein, it is clear that more than one device / item (whether or not they cooperate) may be used in place of a single device / item. Similarly, when more than one device or item (whether or not they cooperate) is described herein, it will be clear that a single device / item may be used in place of more than one device or item, or a different number of devices / items may be used in place of the number of devices or programs shown. The functionality and / or features of a device may alternatively be embodied by one or more other devices not explicitly described as having such functionality / features. Therefore, other embodiments of this disclosure do not necessarily need to include the device itself.

[0164] Figure 3a , Figure 3b and Figure 3c The operations illustrated show certain events occurring in a specific order. In alternative embodiments, some operations may be performed, modified, or removed in a different order. Furthermore, steps can be added to the logic described above and still conform to the described embodiments. Additionally, the operations described herein may occur sequentially, or some operations may be processed in parallel. Furthermore, the operations may be performed by a single processing unit or by distributed processing units.

[0165] Finally, the language used in this specification has been chosen primarily for readability and guidance purposes and may not have been chosen to depict or limit the subject matter of the invention. Therefore, it is intended that the scope of this disclosure is not limited by this detailed description, but rather by any claims set forth in the application based herein. Accordingly, the disclosure of embodiments of the invention is intended to illustrate, and not limit, the scope of the disclosure set forth in the appended claims.

[0166] While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The aspects and embodiments disclosed herein are for illustrative purposes and not restrictive; the true scope and spirit are indicated by the appended claims.

[0167] Although this disclosure has been described with reference to various embodiments, various changes and modifications may be suggested to those skilled in the art. This disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims.

Claims

1. A method performed by a user equipment (UE) for signaling notification of a multicast broadcast service (MBS) interest indication (MII), the method comprising: Send an MII message to the source cell; Receive one of the following from the source cell: RRC_Reconfiguration or RRC_Reconfiguration with reconstructionWithSync, wherein the RRC_Reconfiguration or RRC_Reconfiguration with reconstructionWithSync is received during UE movement; Upon receiving either an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync, connect to the target cell; and Send an MII message to the target cell.

2. The method according to claim 1, wherein, Connection to the target cell also includes: Receive a System Information Block (SIB) including the nonServingCellMII from the target cell.

3. The method according to claim 1, further comprising: During the time period prior to receiving either an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync, a MII message is sent to the source cell.

4. The method according to claim 1, wherein, The MII message includes at least one of the following: subcarrier spacing information, carrier frequency, frequency band indicator, and common frequency resource (CFR) of one or more non-serving cells providing MBS.

5. A user equipment (UE) for signaling notification of Multicast Broadcast Service (MBS) Interest Indication (MII), the UE comprising: transceiver; and The processor is configured as follows: Send MII message to the source cell Receive one of the following from the source cell: an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync, wherein the RRC_Reconfiguration or the RRC_Reconfiguration with reconfigurationWithSync is received during UE movement. Upon receiving either an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync, connect to the target cell, and Send an MII message to the target cell.

6. The UE according to claim 5, wherein, The processor is also configured to: Receive a System Information Block (SIB) including the nonServingCellMII from the target cell.

7. The UE according to claim 5, wherein, The processor is also configured to send an MII message to the source cell during a time period prior to receiving either an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync.

8. The UE according to claim 5, wherein, The MII message includes at least one of the following: subcarrier spacing information, carrier frequency, frequency band indicator, and common frequency resource (CFR) of one or more non-serving cells providing MBS.

9. A system for signaling notification of Multicast Broadcast Service (MBS) Interest Indication (MII), the system comprising: Target residential area; The source cell is configured as follows: Receive MII messages from user equipment (UE). Send one of the following to the UE: an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync, wherein the RRC_Reconfiguration or the RRC_Reconfiguration with reconfigurationWithSync is sent during UE movement. The target cell is configured as follows: Based on the UE receiving either an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync, the connection is established with the UE. Receive MII messages from the UE.

10. The system according to claim 9, in, The target community was also configured as follows: Connect to UE; and Send a system information block (SIB) including nonServingCellMII to the UE.

11. The system according to claim 9, in, The source cell receives MII messages from the UE during the time period prior to receiving either an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync.

12. The system according to claim 9, in, The MII message includes at least one of the following: subcarrier spacing information, carrier frequency, frequency band indicator, and common frequency resource (CFR) of one or more non-serving cells providing MBS.

13. A method for signaling multicast broadcast service (MBS) interest indications (MIIs) performed by a system including a source cell and a target cell. The source cell receives MII messages from the user equipment (UE); The source cell sends one of two RRC_Reconfiguration or RRC_Reconfiguration with reconfigurationWithSync to the UE, where... RRC_Reconfiguration or RRC_Reconfiguration with reconfigurationWithSync is sent during UE movement; The connection between the target cell and the UE is established based on the UE receiving either an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync; and The target cell receives MII messages from the UE.

14. The method according to claim 13, in, The connection between the target cell and the UE also includes: Send a system information block (SIB) including nonServingCellMII to the UE.

15. The method according to claim 13, in, The source cell receives MII messages from the UE during the time period prior to receiving either an RRC_Reconfiguration or an RRC_Reconfiguration with reconfigurationWithSync.

Images