Patent Description:
<NUM> New Radio (NR) is targeting support for Multicast and Broadcast services in 3GPP release <NUM> version of specification being prepared by <NUM>rd Generation Partnership Project (3GPP). In legacy MBMS (Multimedia Broadcast Multicast Services) were supported in a LTE (Long Term Evolution) <NUM> wireless systems. However, the architecture and the requirements of <NUM> Multicast Broadcast Services (MBS) could be very different and there is an effort in the direction of designing the architecture for the network as well as the User Equipment (UE) is in progress.

Specifically, multicast services refer to services being transmitted and availed by a set of UEs registered to a group e.g., MCPTT (Mission Critical Push-To-Talk) service. Broadcast services refer to services being transmitted and available to all the UEs in a specific coverage area where broadcast is performed and typically, UE may not need to be registered e.g., Television services. Therefore, effectively, both multicast and broadcast services are PTM (Point-To-MultiPoint) services as there is one transmitter and multiple recipient of contents. It is also possible to provide multicast and broadcast services in a PTP (Point-to-Point) manner, wherein there are multiple PTP connections to provide the same MBS services to a number of individual recipients. Apart from Multicast and Broadcast services, there are another category of services termed as Unicast services which is meant for one recipient only for this is one to one dedicated connection between transmitter and receiver.

It is possible to have PTM bearer, PTP bearer or a combination of PTM and PTP bearer to carry the same MBS service. Combination of PTM and PTP bearer may provide a lot of features with respect to increase reliability of reception of MBS service packets, efficient switching between these two modes of reception when needed e.g., because of mobility, network loading conditions or based on the user request density for the reception of the MBS service and accordingly network may decide the delivery modes and/or switching across. A bearer configuration which has possibly both legs of PTM and PTP is termed as MBS split bearer.

The principal object of the embodiments herein is to disclose methods and systems for providing notifications and configurations for Multicast/Broadcast services in a <NUM> network.

The method can be used to enable a reliable delivery of MBS services by introducing split radio bearer (i.e., PTP + PTM). The method can be used for group notifications for UEs in an idle/inactive state about MBS services which is more efficient when compared to legacy methods (unicast paging).

The textbook "<NPL>, basically explains how LTE can be used as technology enabler for Public Safety networks.

A method for selecting a cell by a user equipment (UE) to receive a Multimedia Broadcast/Multicast Service (MBMS) service in a mobile communication system which supports the MBMS service with different frequency allocations (FAs) in the same area is described in <CIT>. In the method, a radio network controller (RNC) transmits information on an MBMS cell to the UP, and the MBMS cell information includes an MBMS offset for guaranteeing priority for cell reselection to the MBMS cell. The UE performs cell reselection using the MBMS cell information and receives the MBMS service from the reselected cell.

A method, an apparatus, and a computer program product for wireless communication according to <CIT> enable a user equipment operating in a current cell that provides a multimedia broadcast/multicast service to distinguish between neighboring cells that have different operational characteristics. The presence of a neighboring cell is identified while the user equipment is operating in a first cell and it is determined whether the neighboring cell provides services different from the ser-vices provided in the current cell, based on information maintained by the user equipment. The user equipment may move to the neighboring cell to obtain better or different service.

Accordingly, the embodiments herein disclose methods for handling a service notification and configuration for an MBS in a <NUM> communication network.

The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those of skill in the art to practice the embodiments herein.

The embodiments herein achieve methods for handling a service notification and configuration for an MBS in a <NUM> communication network. The method includes receiving, by a UE, an MBS information through at least one of at least one SIB or a MCCH. The MBS information includes a list of MBS services. Further, the method includes indicating, by the UE, an available list of MBS services to a service layer of the UE from a lower layer of the UE based on the received MBS information. Further, the method includes synchronizing, by the UE, an MBS service list in a user service description (USD) with the available list of MBS services based on the indication. Further, the method includes determining, by the UE, at least one of at least one available MBS service or at least one unavailable MBS service in the USD. Further, the method includes performing, by the UE, at least one of: identifying at least one interested MBS service from the at least one unavailable MBS service and sending an interest indication message to a network entity, wherein the interest indication message comprises information associated with at least one interested MBS service or identifying at least one interested MBS service from the at least one available MBS service and triggering a service join procedure.

Referring now to the drawings, and more particularly to <FIG>, where similar reference characters denote corresponding features consistently throughout the figures, there are shown at least one embodiment.

<FIG> illustrates the architecture <NUM> for the protocol stack for the UE implementation supporting MBS services. Mainly, three types of radio bearer architecture are shown, and are as follows:.

RLC PTM can be based unacknowledged mode (UM) RLC, which does not support functionality of automatic repeat request (ARQ) i.e., no RLC level transmission are supported as there is no feedback or status report between transmitting a sending RLC entity. Whereas RLC PTP can be either a UM mode or an acknowledged mode (AM) RLC. AM RLC supports status/feedback sharing from receiver to transmitter and retransmission of NACKed RLC packets from transmitter to receiver. Thereby, there is a further enhancement in the reliability that can be ensured with the AM RLC layer. Effectively, there is a lossless operation is achieved with utilizing the AM RLC mode.

PDCP layer performs reordering operation and employs a reordering timer t-Reordering to ensure the out of order packets received from RLC (from two RLCs in MBS split bearer) are re-arranged in order of their sequence numbers (SN) before expiry of reordering timer t-Reordering. In case reordering timer expires, and there is still a gap with PDCP receive window (i.e., missing a PDCP PDU SN so that reordering and in-sequence delivery could not be done to the higher layer), PDCP moves its own receive window (i.e., update its own state variable RX_DELIV) further and performs the delivery of PDCP PDUs received until window's lower edge, RX_DELIV (of course gap of missing PDCP PDU SN is also delivered).

Having an MBS split bearer with both PTM RLC and PTP RLC bearer adds to the reliability of the MBS bearer as lossless operation is achieved from the PTP path where a PTM path provides the packet with lesser delay as no retransmission is involved albeit with possible loss. With combining these two paths through the PDCP reordering operation, there is higher chances of receiving PDCP PDUs before t-Reordering expiry and providing ordered in-sequence delivery to the higher layer.

<FIG> illustrates an overview of a <NUM> communication network <NUM> for handling a service notification and configuration for the MBS according to embodiments as disclosed herein. In an embodiment, the <NUM> communication network <NUM> includes a UE <NUM> and a network entity <NUM>. The UE <NUM> can be, for example, but not limited to a laptop, a desktop computer, a notebook, a relay device, a vehicle to everything (V2X) device, a smartphone, a tablet, an internet of things (IoT) device, an immersive device, a virtual reality device, a foldable device, a television with communication facility, a connected car, or the like. The network entity <NUM> may also include or be referred to by those skilled in the art as a base station, a base transceiver station, a radio base station, an access point, a radio transceiver, an eNB, a gNodeB (gNB), or the like.

In an embodiment, the UE <NUM> is configured to receive the MBS information through a SIB or a MCCH. The MBS information comprises the list of MBS services. Based on the received MBS information, the UE <NUM> is configured to indicate an available list of MBS services to a service layer of the UE <NUM> from a lower layer of the UE <NUM>. The MBS information associated with each MBS service from the list of MBS services includes at least one field, wherein the at least one field comprises a TMGI of the MBS service, a session ID, a service type, a DRX configuration for the MBS service, MBS traffic channel (MTCH) configuration for the MBS service, neighbour cell information for the MBS service where for at least one neighbour cell same MBS service (as on serving cell) is one of available and not available, or a BWP over which MBS service, is being delivered.

The MCCH carries complete PTM configuration information and neighbor cell information for PTM service availability indication in at least one neighbor cell to support one of a cell reselection and getting connected to avail service reception through unicast. The neighbor cell information includes a bitmap with a first value indicating at least one PTM service availability in the neighbor cell and a bitmap with a second value indicating at least one PTM service unavailability in the neighbor cell, where in the at least one PTM service is provided in the serving cell.

In an embodiment, the neighbor cell information is used to select a cell where the at least one PTM service, that the UE <NUM> is receiving or interested to receive, is indicated as available on the neighbor cell as the source cell. In another embodiment, the neighbor cell information is used to establish a RRC connection and avail MBS service through a unicast mode, upon handover to the neighbor cell where the at least one PTM service, that the UE <NUM> is receiving or interested to receive, is indicated as unavailable on the neighbor cell as the source cell. In an embodiment, the cell reselection is performed with prioritizing at least one frequency over which the MBS service is currently being provided on a source cell or on a frequency for a neighbor where MBS service is available.

In an embodiment, the at least one SIB is used for providing at least one of a MCCH configuration, a notification configuration or a control information, wherein the SIB is transmitted by at least one of a periodical SIB transmission, a SIB transmission only when there is change in the SIB, or an on-demand SIB acquisition when the UE <NUM> does not have stored SIB information and no page or a PDCCH change is indicated, wherein the at least one SIB is provided on a cell supporting MBS. In another embodiment, the at least one SIB is used for providing mapping of at least one of a MBS services, frequencies for reception and Service Area Identities (SAIs), wherein the at least one SIB is transmitted by at least one of a periodical SIB transmission, a SIB transmission only when there is change in the at least one SIB, or an on-demand SIB acquisition when the UE <NUM> does not have stored SIB information, wherein the at least one SIB is provided on a cell supporting MBS and not supporting MBS.

In another embodiment, the at least one SIB is used for also providing information for the frequencies which are supporting MBS and/or supporting multicast services and/or supporting specific service area identities (SAIs) pertaining to multicast services.

Based on the indication, the UE <NUM> is configured to synchronize an MBS service list in the USD with the available list of MBS services. Further, the UE <NUM> is configured to determine the available MBS service or the unavailable MBS service in the USD. Based on the determination, the UE <NUM> is configured to identify the interested MBS service from the available MBS service and trigger the service join procedure. Further, the UE <NUM> is configured to identify the interested MBS service from the unavailable MBS service and send the interest indication message to the network entity <NUM>. The interest indication message includes information associated with the interested MBS service.

In another embodiment, the UE <NUM> is configured to receive the CN paging message from the network entity <NUM>. The CN paging message includes the MBS paging list of a TMGIs for session activation. The UE <NUM> is in the RRC_IDLE state. Further, the UE <NUM> is configured to determine the activation for the non-activated session pertaining to the UE <NUM> based on the CN paging message. Further, the UE <NUM> is configured to perform the RRC connection establishment procedure between the UE <NUM> and the network entity <NUM>.

Based on the RRC connection establishment procedure, the UE <NUM> is configured to send the session join request to the network entity <NUM>. Further, the UE <NUM> is configured to receive the RRC reconfiguration message comprising an MBS service configuration from the network entity <NUM> for the activated MBS service based on the session join request. Based on the RRC reconfiguration message, the UE <NUM> is configured to receive the MBS data from the network entity <NUM>.

In another embodiment, the UE <NUM> is configured to receive the RAN paging message from the network entity <NUM>, where the RAN paging message comprises the MBS paging list of a TMGIs for session activation. The UE <NUM> is in the RRC_INACTIVE state. Based on the RAN paging message, the UE <NUM> is configured to determine the activation for the non-activated session pertaining to the UE <NUM>.

Further, the UE <NUM> is configured to perform the RRC resume procedure between the UE <NUM> and the network entity <NUM>. Further, the UE <NUM> is configured to receive the RRC reconfiguration message comprising an MBS service configuration from the network entity <NUM> for the activated MBS service. Based on the RRC reconfiguration message, the UE <NUM> is configured to receive the MBS data from the network entity <NUM>.

In another embodiment, the UE <NUM> is in the RRC_CONNECTED state. The UE <NUM> receives the RRC reconfiguration message comprising an MBS service configuration from the network entity <NUM> for the activated MBS service. Further, the UE <NUM> determines the activation for the non-activated session pertaining to the UE <NUM> based on the RRC reconfiguration message. Further, the UE <NUM> receives the MBS data from the network entity <NUM> based on the RRC reconfiguration message.

In another embodiment, the network entity <NUM> is configured to receive one of a RRC resume request and a RRC connection request with at least one indication from the UE <NUM>. The UE <NUM> is in one of an RRC_INACTIVE state and an RRC_IDLE state. The indication comprises the low priority MBS cause, the high priority MBS cause, the mt-access cause, and the critical MBS cause. Further, the network entity <NUM> is configured to accept one of the RRC resume request and the RRC connection request from the UE <NUM> if the at least one indication comprises a high priority MBS cause, the mt-access cause and the critical MBS cause. Further, the network entity <NUM> is configured to reject one of the RRC resume request and the RRC connection request from the UE <NUM> if the at least one indication comprises a low priority MBS cause, when the <NUM> communication network <NUM> is having congestion.

In an example, embodiments herein provide a mechanism for service notification and service configuration for multicast broadcast services for new radio (NR). In the NR, there can be possibly many different deployment scenarios e.g., A1, A2, B and B-Variant as detailed:.

Scenario: A2 (or A1): the UE <NUM> in idle/Inactive (as well as a connected mode) may be able to identify MBS service as multicast and broadcast so as to an initiate specific joining procedure (NAS) or a bearer configuration procedure (RRC).

Method <NUM>: broadcasted MBS service list (for multicast and broadcast services OR only for broadcast services) (applicable for an idle, an inactive, and a connected mode UEs).

In an embodiment, overall available MBS services information is broadcasted and includes a list of MBS services with each having certain fields including at least one of TMGI of the MBS service, Session Id, Service type - whether broadcast or multicast, BWP over which MBS service is being delivered. The UEs <NUM> in a connected mode also avail this list of services to know availability over radio access network (RAN). In general, lower layer informs the available list of services (as received in broadcast i.e., RAN signalling) to the service layer, which can sync up with the service list in USD or program guide with the availability status. Unavailable MBS services, if desired, may add to interested MBS services (may also be considered in interest indication message). Whereas, available MBS services, if desired, may cause a service join procedure.

Some possible use cases for service type are as follows:.

In an embodiment, with assuming solution A2 (or A1), limited information is broadcasted for MBS and rest configuration is availed in a connected mode dedicated signaling. System information block (SIB) provides this broadcast and MCCH is not required.

In an embodiment, SIB providing broadcast about MBS services information accessed on demand (i.e., SIB on demand, as and when the UE <NUM> requires to check present MBS service availability on the present cell). Any change for the SIB contents is determined by paging (change here implies addition/deletion of an MBS service). Alternatively, the broadcasted information is delivered by MCCH (MBS control channel).

In an embodiment, operational details for the UE <NUM> in different modes, after accessing the broadcasted information through SIB or MCCH, are as follows:.

For scenario A1, the UE <NUM> after availing the PTM configuration falls back to the idle/inactive mode and continue receiving the service. In an embodiment, the UE <NUM> determines the MBS service requirement whether the UE can be continued in the idle/inactive mode and accordingly, determines to fall back to the idle/inactive mode or continue in the connected mode. In some cases, it could be due to coexistence of other unicast services being received in the connected mode.

In an embodiment, a UE <NUM>, which may or may not be able to support more than N (e.g., one, two or so on) G-RNTI at a time due to the implementation capability limitation, may indicate the same to the gNB through a RRC signalling message e.g., UE capability message. Based on the UE's capability and consequently, by network configuration, actual number of G-RNTIs supported for the UE <NUM> is determined. Accordingly, the PTM configuration to the UE <NUM> is provided for which the UE <NUM> is configured to use less or equal to N G-RNTIs at a time. In case the DRX scheduling configuration for the MBS services are disjoint, then potentially more than N G-GNTIs can also be configured. Alternatively, the gNB can multiplex more than one MBS services over a MAC PDU or transport block (TB) which is addressed by same G-RNTI. This way, a constrained UE can also support more services simultaneously.

An example MBS configuration parameters received in a connected mode is shown in table.

In one embodiment of Method <NUM>, group paging approach (only for multicast services) (applicable for an idle mode UEs), a group paging or group notification is employed for the UEs <NUM> which transited to the idle mode but interested in multicast service. The group paging message includes the TMGI as paging identity. The UE <NUM> responds to the group paging with a session join procedure with TMGI and transits to a connected mode. The RAN sets up PTM/PTP/MBS-split bearer for the UE <NUM> as detailed in method <NUM>. For inactive mode UEs, the RAN transits the inactive mode UEs to a connected state (when MBS session context is activated by AMF). The UE <NUM> receives the paging from RAN. A rest procedure can be same as that for the idle mode.

In an embodiment, following possible deployment approaches for scenario A2 (or A1) include:.

Scenario: B (applicable for broadcast and/or multicast services in an idle/inactive modes).

In one embodiment of Method <NUM>,utilizing MCCH channel for services information, an SIB is used for providing configuration of MCCH. PDCCH based notification for change of MCCH (change implies only new service start). MCCH carries complete PTM configuration information and neighbor cell information along with same PTM configuration indication in the neighbor cell(s) to support cell reselection. The neighbor cell information could be a bitmap with value <NUM> indicating same PTM configuration in neighbor cell and <NUM> indicating different PTM configuration information in the neighbor cell. Number of total bits can be N e.g., <NUM> bits to indicate <NUM> possible neighboring cells.

In an embodiment, considering large number of MBS service configurations, some standardized/default configuration are specified (e.g., certain SDAP/PDCP/RLC/MAC configuration options may be indexed). PTM configuration for MBS service can just carry the index to refer to standardized/default configurations where applicable. This way, it helps in processing and comparison/determination of any configuration change efficiently.

In an embodiment, a cell reselection is performed with prioritizing the frequency over which MBS services is currently being provided on the source cell or on the frequency for the neighbor where MBS service is available. Neighbor cell information is used to choose the cell where the PTM service configuration is same as the source cell so as the service continuity is maintained across cell reselection with minimum interruption time.

In one embodiment of Method <NUM>, dedicated MBS SIB, an SIB is used for providing MBS service information and configuration. Paging and/or PDCCH based notification for SIB change is provided. SIB transmission in the provided approach is undertaken as per one of the different options as follows:.

In an embodiment, only broadcast services and/or low reliability multicast services are provided in the idle/inactive mode for the UEs <NUM>. For such MBS services, UM mode RLC and no HARQ or HARQ without a feedback mode is used.

<FIG> illustrates various hardware components of the UE <NUM> according to embodiments as disclosed herein. The UE <NUM> includes a processor <NUM>, a communicator <NUM>, a memory <NUM> and an MBS service notification and configuration controller <NUM>. The processor <NUM> is coupled with the communicator <NUM>, the memory <NUM> and the MBS service notification and configuration controller <NUM>.

In an embodiment, the MBS service notification and configuration controller <NUM> is configured to receive the MBS information through the SIB or the MCCH. The MBS information comprises the list of MBS services. Based on the received MBS information, the MBS service notification and configuration controller <NUM> is configured to indicate the available list of MBS services to the service layer of the UE <NUM> from the lower layer of the UE <NUM>. Based on the indication, the MBS service notification and configuration controller <NUM> is configured to synchronize an MBS service list in the USD with the available list of MBS services. Further, the MBS service notification and configuration controller <NUM> is configured to determine the available MBS service or the unavailable MBS service in the USD.

Based on the determination, the MBS service notification and configuration controller <NUM> is configured to identify the interested MBS service from the available MBS service and trigger the service join procedure. Further, the MBS service notification and configuration controller <NUM> is configured to identify the interested MBS service from the unavailable MBS service and send the interest indication message to the network entity <NUM>. The interest indication message includes information associated with the interested MBS service.

In another embodiment, the MBS service notification and configuration controller <NUM> is configured to receive the CN paging message from the network entity <NUM>. The CN paging message includes the MBS paging list of a TMGIs for session activation. The UE <NUM> is in the RRC_IDLE state. Further, the MBS service notification and configuration controller <NUM> is configured to determine the activation for the non-activated session pertaining to the UE <NUM> based on the CN paging message. Further, the MBS service notification and configuration controller <NUM> is configured to perform the RRC connection establishment procedure between the UE <NUM> and the network entity <NUM>.

Based on the RRC connection establishment procedure, the MBS service notification and configuration controller <NUM> is configured to send the session join requestto the network entity <NUM>. Further, the MBS service notification and configuration controller <NUM> is configured to receive the RRC reconfiguration message comprising an MBS service configuration from the network entity <NUM> for the activated MBS service based on the session join request. Based on the RRC reconfiguration message, the MBS service notification and configuration controller <NUM> is configured to receive the MBS data from the network entity <NUM>.

In another embodiment, the MBS service notification and configuration controller <NUM> is configured to receive the RAN paging message from the network entity <NUM>, where the RAN paging message comprises the MBS paging list of a TMGIs for session activation. The UE <NUM> is in the RRC_INACTIVE state. based on the RAN paging message, the MBS service notification and configuration controller <NUM> is configured to determine the activation for the non-activated session pertaining to the UE <NUM>.

Further, the MBS service notification and configuration controller <NUM> is configured to perform the RRC resume procedure between the UE <NUM> and the network entity <NUM>. Further, the MBS service notification and configuration controller <NUM> is configured to receive the RRC reconfiguration message comprising an MBS service configuration from the network entity <NUM> for the activated MBS service. based on the RRC reconfiguration message, the MBS service notification and configuration controller <NUM> is configured to receive the MBS data from the network entity <NUM>.

The MBS service notification and configuration controller <NUM> is configured to receive the RRC reconfiguration message comprising an MBS service configuration from the network entity <NUM> for the activated MBS service, where the UE <NUM> is in the RRC_CONNECTED state. Further, the MBS service notification and configuration controller <NUM> is configured to determine an activation for at least one non-activated session pertaining to the UE <NUM> based on the RRC reconfiguration message. Further, the MBS service notification and configuration controller <NUM> is configured to receive the MBS data from the network entity <NUM> based on the RRC reconfiguration message.

The the MBS service notification and configuration controller <NUM> is physically implemented by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware.

Further, the processor <NUM> is configured to execute instructions stored in the memory <NUM> and to perform various processes. The communicator <NUM> is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory <NUM> also stores instructions to be executed by the processor <NUM>. The memory <NUM> may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory <NUM> may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory <NUM> is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in random access memory (RAM) or cache).

Further, at least one of the plurality of modules/controller may be implemented through the AI model. A function associated with the AI model may be performed through the non-volatile memory, the volatile memory, and the processor <NUM>. The processor <NUM> may include one or a plurality of processors. At this time, one or a plurality of processors may be a general purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an AI-dedicated processor such as a neural processing unit (NPU).

The one or a plurality of processors control the processing of the input data in accordance with a predefined operating rule or AI model stored in the non-volatile memory and the volatile memory. The predefined operating rule or artificial intelligence model is provided through training or learning.

Here, being provided through learning means that a predefined operating rule or AI model of a desired characteristic is made by applying a learning algorithm to a plurality of learning data. The learning may be performed in a device itself in which AI according to an embodiment is performed, and/o may be implemented through a separate server/system.

The AI model may comprise of a plurality of neural network layers. Each layer has a plurality of weight values and performs a layer operation through calculation of a previous layer and an operation of a plurality of weights. Examples of neural networks include, but are not limited to, convolutional neural network (CNN), deep neural network (DNN), recurrent neural network (RNN), restricted Boltzmann Machine (RBM), deep belief network (DBN), bidirectional recurrent deep neural network (BRDNN), generative adversarial networks (GAN), and deep Q-networks.

The learning algorithm is a method for training a predetermined target device (for example, a robot) using a plurality of learning data to cause, allow, or control the target device to make a determination or prediction. Examples of learning algorithms include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

Although the <FIG> shows various hardware components of the UE <NUM> but it is to be understood that other embodiments are not limited thereon. In other embodiments, the UE <NUM> may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the disclosure. One or more components can be combined together to perform same or substantially similar function in the UE <NUM>.

<FIG> shows various hardware components of the network entity <NUM> according to embodiments as disclosed herein. The network entity <NUM> includes a processor <NUM>, a communicator <NUM>, a memory <NUM> and an MBS service notification and configuration controller <NUM>. The processor <NUM> is coupled with the communicator <NUM>, the memory <NUM> and the MBS service notification and configuration controller <NUM>.

In an embodiment, the MBS service notification and configuration controller <NUM> is configured to send the CN paging message to the UE <NUM>. The CN paging message includes the MBS paging list of the TMGIs for session activation and the UE <NUM> is in the RRC_IDLE state. Further, the MBS service notification and configuration controller <NUM> is configured to perform the RRC connection establishment procedure between the UE <NUM> and the network entity <NUM> in response to determining the activation for at least one non-activated session pertaining to the UE <NUM> based on the CN paging message. Based on the RRC connection establishment procedure, the MBS service notification and configuration controller <NUM> is configured to receive the session join request from the UE <NUM>.

Further, the MBS service notification and configuration controller <NUM> is configured to send the RRC reconfiguration message comprising the MBS service configuration to the UE <NUM> for the activated MBS service based on the session join request. Based on the RRC reconfiguration message, the MBS service notification and configuration controller <NUM> is configured to send the MBS data to the UE <NUM>.

In another embodiment, the MBS service notification and configuration controller <NUM> is configured to send the RAN paging message to the UE <NUM>. The RAN paging message includes the MBS paging list of the TMGIs for session activation and the UE <NUM> is in the RRC_INACTIVE state. Further, the MBS service notification and configuration controller <NUM> is configured to perform the RRC resume procedure between the UE <NUM> and the network entity <NUM> in response to determining the activation for at least one non-activated session pertaining to the UE <NUM> based on the RAN paging message.

Further, the MBS service notification and configuration controller <NUM> is configured to send the RRC reconfiguration message comprising the MBS service configuration to the UE <NUM> for the activated MBS service. Based on the RRC reconfiguration message, the MBS service notification and configuration controller <NUM> is configured to send the MBS data to the UE <NUM>.

The MBS service notification and configuration controller <NUM> is configured to send the RRC reconfiguration message comprising the MBS service configuration to the UE <NUM> for the activated MBS service, where the UE <NUM> is in the RRC_CONNECTED state. Further, the MBS service notification and configuration controller <NUM> is configured to send the MBS data to the UE <NUM> based on the RRC reconfiguration message upon determining an activation for the non-activated session pertaining to the UE <NUM> based on the RRC reconfiguration message.

In another embodiment, the MBS service notification and configuration controller <NUM> is configured to receive one of a RRC resume request and a RRC connection request with at least one indication from the UE <NUM>. The UE <NUM> is in one of an RRC_INACTIVE state and an RRC_IDLE state. The indication comprises the low priority MBS cause, the high priority MBS cause, the mt-access cause, and the critical MBS cause. Further, the MBS service notification and configuration controller <NUM> is configured to accept one of the RRC resume request and the RRC connection request from the UE <NUM> if the at least one indication comprises a high priority MBS cause, the mt-access cause and the critical MBS cause. Further, the MBS service notification and configuration controller <NUM> is configured to reject one of the RRC resume request and the RRC connection request from the UE <NUM> if the at least one indication comprises a low priority MBS cause, when the <NUM> communication network <NUM> is having congestion.

The MBS service notification and configuration controller <NUM> is physically implemented by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware.

The AI model may comprise of a plurality of neural network layers. Each layer has a plurality of weight values and performs a layer operation through calculation of a previous layer and an operation of a plurality of weights. Examples of neural networks include, but are not limited to, convolutional neural network (CNN), deep neural network (DNN), recurrent neural network (RNN), restricted Boltzmann machine (RBM), deep belief network (DBN), bidirectional recurrent deep neural network (BRDNN), generative adversarial networks (GAN), and deep Q-networks.

Although the <FIG> shows various hardware components of the network entity <NUM> but it is to be understood that other embodiments are not limited thereon. In other embodiments, the network entity <NUM> may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the disclosure. One or more components can be combined together to perform same or substantially similar function in the network entity <NUM>.

<FIG> is a flow chart <NUM> illustrating a method, implemented by the UE <NUM>, for handling the service notification and configuration for the MBS in the <NUM> communication network <NUM> based on the MBS information according to embodiments as disclosed herein. The operations <NUM>-<NUM> are handled by the MBS service notification and configuration controller <NUM>.

At <NUM>, the method includes receiving the MBS information through the SIB or the MCCH. The MBS information comprises a list of MBS services. At <NUM>, the method includes indicating the available list of MBS services to a service layer of the UE <NUM> from a lower layer of the UE <NUM> based on the received MBS information. At <NUM>, the method includes synchronizing an MBS service list in the USD with the available list of MBS services based on the indication. At <NUM>, the method includes determining the available MBS service or the unavailable MBS service in the USD.

At <NUM>, the method includes identifying an interested MBS service from the available MBS service and triggering a service join procedure. At <NUM>, the method includes identifying the interested MBS service from the unavailable MBS service and sending an interest indication message to the network entity <NUM>. The interest indication message includes information associated with the interested MBS service.

<FIG> is a flow chart <NUM> illustrating a method, implemented by the UE <NUM>, for handling the service notification and configuration for the MBS in the <NUM> communication network <NUM> based on the CN paging message according to embodiments as disclosed herein. The operations <NUM>-<NUM> are handled by the MBS service notification and configuration controller <NUM>.

At <NUM>, the method includes receiving the CN paging message from the network entity <NUM>. The CN paging message includes the MBS paging list of a TMGIs for session activation. The UE <NUM> is in the RRC_IDLE state. At <NUM>, the method includes determining the activation for the non-activated session pertaining to the UE <NUM> based on the CN paging message. At <NUM>, the method includes performing the RRC connection establishment procedure between the UE <NUM> and the network entity <NUM>.

At <NUM>, the method includes sending the session join request to the network entity <NUM> based on the RRC connection establishment procedure. At <NUM>, the method includes receiving the RRC reconfiguration message comprising an MBS service configuration from the network entity <NUM> for the activated MBS service based on the session join request. At <NUM>, the method includes receiving the MBS data from the network entity <NUM> based on the RRC reconfiguration message.

<FIG> is a flow chartn <NUM> illustrating a method, implemented by the UE <NUM>, for handling the service notification and configuration for the MBS in the <NUM> communication network <NUM> based on the RAN paging message according to embodiments as disclosed herein. The operations <NUM>-<NUM> are handled by the MBS service notification and configuration controller <NUM>.

At <NUM>, the method includes receiving the RAN paging message from the network entity <NUM>, where the RAN paging message comprises an MBS paging list of a TMGIs for session activation. The UE <NUM> is in an RRC_INACTIVE state. At <NUM>, the method includes determining the activation for the non-activated session pertaining to the UE <NUM> based on the RAN paging message.

At <NUM>, the method includes performing the RRC resume procedure between the UE <NUM> and the network entity <NUM>. At <NUM>, the method includes receiving the RRC reconfiguration message comprising an MBS service configuration from the network entity <NUM> for the activated MBS service. At <NUM>, the method includes receiving an MBS data from the network entity <NUM> based on the RRC reconfiguration message.

<FIG> is a flow chart <NUM> illustrating a method, implemented by the network <NUM>, for handling the service notification and configuration for the MBS in the <NUM> communication network <NUM> based on the CN paging message according to embodiments as disclosed herein. The operations <NUM>-<NUM> are handled by the MBS service notification and configuration controller <NUM>.

At <NUM>, the method includes sending the CN paging message to the UE <NUM>. The CN paging message includes an MBS paging list of a TMGIs for session activation and the UE <NUM> is in an RRC_IDLE state. At <NUM>, the method includes performing the RRC connection establishment procedure between the UE <NUM> and the network entity <NUM> in response to determining an activation for at least one non-activated session pertaining to the UE <NUM> based on the CN paging message. At <NUM>, the method includes receiving the session join request from the UE <NUM> based on the RRC connection establishment procedure.

At <NUM>, the method includes sending the RRC reconfiguration message comprising an MBS service configuration to the UE <NUM> for the activated MBS service based on the session join request. At <NUM>, the method includes sending an MBS data to the UE <NUM> based on the RRC reconfiguration message.

<FIG> is a flow chart <NUM> illustrating a method, implemented by the network <NUM>, for handling the service notification and configuration for the MBS in the <NUM> communication network <NUM> based on the RAN paging message according to embodiments as disclosed herein. The operations <NUM>-<NUM> are handled by the MBS service notification and configuration controller <NUM>.

At <NUM>, the method includes sending the RAN paging message to the UE <NUM>. The RAN paging message includes an MBS paging list of a TMGIs for session activation and the UE <NUM> is in an RRC_INACTIVE state. At <NUM>, the method includes performing the RRC resume procedure between the UE <NUM> and the network entity <NUM> in response to determining the activation for at least one non-activated session pertaining to the UE <NUM> based on the RAN paging message.

At <NUM>, the method includes sending the RRC reconfiguration message comprising the MBS service configuration to the UE <NUM> for the activated MBS service. At <NUM>, the method includes sending the MBS data to the UE <NUM> based on the RRC reconfiguration message.

<FIG> is a flow chart <NUM> illustrating a method, implemented by the network <NUM>, for handling the service notification and configuration for the MBS in the <NUM> communication network <NUM> according to embodiments as disclosed herein. The operations <NUM>-<NUM> are handled by the MBS service notification and configuration controller <NUM>.

At <NUM>, the method includes receiving one of a RRC resume request and a RRC connection request with at least one indication from the UE <NUM>. The UE <NUM> is in one of an RRC_INACTIVE state and an RRC_IDLE state. The indication comprises a low priority MBS cause, a high priority MBS cause, a mt-access cause, a critical MBS cause. At <NUM>, the method includes accepting one of the RRC resume request and the RRC connection request from the UE <NUM> if the at least one indication comprises a high priority MBS cause, the mt-access cause and the critical MBS cause. At <NUM>, the method includes rejecting one of the RRC resume request and the RRC connection request from the UE <NUM> if the at least one indication comprises a low priority MBS cause, when the <NUM> communication network <NUM> is having congestion.

<FIG> is a sequence flow diagram illustrating step by step operations for handling the service notification and configuration for the MBS in the <NUM> communication network <NUM> based on the CN paging message according to embodiments as disclosed herein.

At <NUM>, the UE <NUM> receives the CN paging message from the network entity <NUM>. The CN paging message includes the MBS paging list of the TMGIs for session activation. The UE <NUM> is in the RRC_IDLE state. Further, the UE <NUM> determines the activation for the non-activated session pertaining to the UE <NUM> based on the CN paging message. At <NUM>, the RRC connection establishment procedure is performed between the UE <NUM> and the network entity <NUM>.

At <NUM>, the UE <NUM> sends the session join request to the network entity <NUM> based on the RRC connection establishment procedure. At <NUM>, the UE <NUM> receives the RRC reconfiguration message comprising the MBS service configuration from the network entity <NUM> for the activated MBS service based on the session join request. At <NUM>, the UE <NUM> receives the MBS data from the network entity <NUM> based on the RRC reconfiguration message.

<FIG> is a sequence flow diagram illustrating step by step operations for handling the service notification and configuration for the MBS in the <NUM> communication network <NUM> based on the RAN paging message according to embodiments as disclosed herein.

At <NUM>, the UE <NUM> receives the RAN paging message from the network entity <NUM>, where the RAN paging message comprises an MBS paging list of the TMGIs for session activation. The UE <NUM> is in the RRC_INACTIVE state. Further, the UE <NUM> determines the activation for the non-activated session pertaining to the UE <NUM> based on the RAN paging message.

At <NUM>, the RRC resume procedure is performed between the UE <NUM> and the network entity <NUM>. At <NUM>, the UE <NUM> receives the RRC reconfiguration message comprising the MBS service configuration from the network entity <NUM> for the activated MBS service. At <NUM>, the UE <NUM> receives the MBS data from the network entity <NUM> based on the RRC reconfiguration message.

<FIG> is a flow chart <NUM> illustrating a method, implemented by the UE <NUM>, for handling a service notification and configuration for the MBS in the <NUM> communication network <NUM>, when the UE <NUM> is in the RRC CONNECTED state. according to embodiments as disclosed herein. The operations <NUM>-<NUM> are handled by the MBS service notification and configuration controller <NUM>.

At <NUM>, the method includes receiving the RRC reconfiguration message comprising the MBS service configuration from the network entity <NUM> for an activated MBS service. The UE <NUM> is in the RRC CONNECTED state. At <NUM>, the method includes determining the activation for at least one non-activated session pertaining to the UE <NUM> based on the RRC reconfiguration message. At <NUM>, the method includes receiving the MBS data from the network entity <NUM>, upon determination, based on the RRC reconfiguration message.

<FIG> is a flow chart <NUM> illustrating a method, implemented by the network entity <NUM>, for handling the service notification and configuration for the MBS in the <NUM> communication network <NUM>, when the UE <NUM> is in the RRC CONNECTED state according to embodiments as disclosed herein. The operations <NUM> and <NUM> are handled by the MBS service notification and configuration controller <NUM>.

At <NUM>, the method includes sending the RRC reconfiguration message comprising the MBS service configuration to the UE <NUM> for the activated MBS service, wherein the UE <NUM> is in an RRC_CONNECTED state. At <NUM>, the method includes sending the MBS data to the UE <NUM> based on the RRC reconfiguration message upon determining an activation for at least one non-activated session pertaining to the UE <NUM> based on the RRC reconfiguration message.

The various actions, acts, blocks, steps, or the like in the flow charts <NUM>-<NUM>, <NUM> and <NUM> may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the disclosure.

The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements can be at least one of a hardware device, or a combination of hardware device and software module.

Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims. device to make a determination or prediction. Examples of learning algorithms include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

Claim 1:
A method of a user equipment, UE, (<NUM>) in a wireless communication network, the method comprising:
receiving (<NUM>), from a network entity (<NUM>), system information block, SIB, and a notification for multicast control channel, MCCH, information change;
receiving, from the network entity, multicast broadcast service, MBS, configuration information based on the notification, wherein the MBS configuration information is received on an MCCH;
transmitting (<NUM>), to the network entity, an interest indication message including a list of at least one MBS of interest, based on the SIB;
transmitting, to the network entity, a first message indicating UE capability including a maximum number of at least one radio network temporary identifier, RNTI, for a multicast; and
receiving, from the network entity, a second message including configuration information about at least one RNTI for an MBS.