Performing channel measurements for NR-u and handling MBS in telecommunication network

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments herein is to perform channel measurements for NR-U and handling MBS in telecommunication network.

Description

PERFORMING CHANNEL MEASUREMENTS FOR NR-U AND HANDLING MBS IN TELECOMMUNICATION NETWORK

[0001] The proposed embodiments relate to the field of telecommunication network. More particularly present disclosure relates to performing channel measurements for NR-U and handling MBS in telecommunication network.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] The principal object of the embodiments herein is to perform channel measurements for NR-U and handling MBS in telecommunication network.

[0009] Another object of the invention is to perform RSSI and channel occupancy measurement for NR-U operation.

[0010] Another object of the invention is to perform the RSSI and channel occupancy measurement for NR-U operation on the frequency configured by the RMTC frequency in measurement object.

[0011] Another object of the invention is to handle SDT and MBS reception when UE is in inactive state.

[0012] Another object of the invention is to handle MBS broadcast and unicast / MBS multicast reception when UE in connected state.

[0013] The technical subjects pursued in the disclosure may not be limited to the above-mentioned technical subjects, and other technical subjects which are not mentioned may be clearly understood, through the following descriptions, by those skilled in the art to which the disclosure pertains.

[0014] In one aspect, the objectives are achieved by providing a method for performing measurement for New Radio Unlicensed (NR-U) in a telecommunication network system. The method includes receiving, by a User Equipment (UE), a measurement configuration from a network apparatus. The measurement configuration comprises of measurement identity list and at least one measurement object and at least one measurement report configuration. Also, the measurement object comprises a RSSI Measurement Timing Configuration (RMTC) configuration including at least one RMTC-frequency and a measurement identity is associated with a measurement object and a measurement report configuration. Further, the method includes performing, by the UE, the measurement for the NR-U on the RMTC-frequency indicated by the RMTC-configuration in the associated measurement object and based on the associated measurement report configuration for a measurement identity.

[0015] In an embodiment, the method of performing the measurement for the NR-U on the RMTC-frequency indicated by the RMTC-configuration in the associated measurement object and based on the associated measurement report configuration for a measurement identity includes determining, by the UE, whether a report type for the associated measurement report configuration is one of a periodic measurement type, an event triggered measurement type, or a conditional trigger configuration measurement type. Further, the method includes determining, by the UE, whether a measurement gap configuration is set up or the UE does not require the measurement gap to perform the measurement, when the report type for the associated measurement report configuration is one of the periodic measurement type, the event triggered measurement type, or the conditional trigger configuration measurement type. Further, the method includes determining, by the UE, whether a measure RSSI-Report configuration is configured in the associated measurement report configuration when the measurement gap configuration is set up or the measurement gap configuration is not required for the measurement. Further, the method includes performing the measurement for the NR-U on the frequency configured by RMTC-frequency in the associated measurement object, when the measure RSSI-Report configuration is configured in the associated measurement report configuration.

[0016] In an embodiment, the measurement for the NR-U comprises at least one of a Received Signal Strength Indicator (RSSI) measurement, a channel occupancy measurement, and a measurement of other parameters related to the NR-U.

[0017] In an embodiment, the method includes determining, by the UE, whether the RMTC configuration is configured in the associated measurement object for a measurement identity in the measurement configuration. Further, the method includes selecting, by the UE, at least one of the Synchronization Signal Block (SSB) frequency or Channel State Information Reference Signal (CSI-RS) reference frequency based on reference signal type provided in the associated measurement report configuration, when the RMTC configuration is not configured in the associated measurement object for a measurement identity in the measurement configuration. Further, the method includes performing measurement for the NR-U on the SSB frequency, when the reference signal type is set as SSB. Also, the method includes performing measurement for the NR-U on the CSI-RS frequency, when the reference signal type is set as CSI-RS.

[0018] In an embodiment, the method includes determining, by the UE, whether the measurement object in the measurement configuration is associated with an Inter- Radio Access Technology (Inter-RAT) Long Term Evolution (LTE) measurement. Further, the method includes performing, by the UE, the measurement for the NR-U on a carrier frequency in the concerned measurement object, when the measurement object in the measurement configuration is associated with an Inter-RAT Long Term Evolution (LTE) measurement.

[0019] Accordingly, the embodiment herein is to provide a user equipment for performing measurement for New Radio Unlicensed (NR-U) in a telecommunication network system. The UE comprises at least one of a processor and a NR-U controller coupled to the processor. The NR-U controller is configured to receive a measurement configuration from a network apparatus. The measurement configuration comprises of measurement identity list and at least one measurement object and at least one measurement report configuration. Also, the measurement object comprises a RSSI Measurement Timing Configuration (RMTC) configuration including at least one RMTC-frequency and a measurement identity is associated with a measurement object and a measurement report configuration. Further, the NR-U controller performs the measurement for the NR-U on the RMTC-frequency indicated by the RMTC-configuration in the associated measurement object and based on the associated measurement report configuration for a measurement identity.

[0020] Accordingly, the embodiment herein is to provide a method for handling Multicast Broadcast Service (MBS) in a telecommunication network system. The method includes receiving, by a UE, at least one of a MBS broadcast System Information Block (SIB), MBS Control Channel (MCCH), MBS broadcast session data over MBS Traffic Channel (MTCH), a MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH from a network apparatus when the UE is in an inactive state. Further, the method includes determining, by the UE, whether a SDT procedure is at least one of initiated and ongoing at the UE. Further, the method includes determining, by the UE, whether one or more conditions for concurrent operations of unicast and MBS are met. Further, the method includes performing, by the UE, one of suspending or stopping reception of at least one of a MBS broadcast System Information Block (SIB), MBS Control Channel (MCCH), MBS broadcast session data over MBS Traffic Channel (MTCH), a MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH. Also, suspending monitoring for a downlink channel associated with at least one of the MBS broadcast session data and the MBS multicast session data from a network apparatus, when the SDT procedure is at least one of initiated and ongoing at the UE and one or more conditions for concurrent operations of unicast and MBS are not met. Further, the method includes continuing the reception of at least one of a MBS broadcast System Information Block (SIB), MBS Control Channel (MCCH), MBS broadcast session data over MBS Traffic Channel (MTCH), a MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH and continuing monitoring for a downlink channel associated with at least one of the MBS broadcast session data and the MBS multicast session data from a network apparatus, when the SDT procedure is at least one of initiated and ongoing at the UE and one or more conditions for concurrent operations of unicast and MBS are met.

[0021] In an embodiment, the method of determining whether the one or more conditions for concurrent operations of unicast and MBS are met includes determining, by the UE, whether the UE has capability of receiving at least one of MBS broadcast and MBS multicast along with unicast. Further, the method includes determining, by the UE, whether beams for the at least one of MBS broadcast and MBS multicast are quasi-co located (QCL) with the unicast beams.

[0022] In an embodiment, when the SDT procedure is at least one of initiated and ongoing at the UE, the method includes determining, by the UE, whether the SDT procedure is completed successfully or unsuccessfully. Further, the method includes determining, by the UE, whether the UE was receiving at least one of the MBS broadcast System Information Block (SIB), the MBS Control Channel (MCCH), the MBS broadcast session data over MBS Traffic Channel (MTCH) before initiation of SDT procedure. Further, the method includes performing, by the UE, one of resuming or starting receiving of at least one of the MBS broadcast System Information Block (SIB), the MBS Control Channel (MCCH), the MBS broadcast session data over MBS Traffic Channel (MTCH), when the SDT procedure is completed successfully and the UE was receiving at least one of the MBS broadcast System Information Block (SIB), the MBS Control Channel (MCCH), the MBS broadcast session data over MBS Traffic Channel (MTCH) before initiation of SDT procedure. Also, the method includes transiting, by the UE, to idle state from inactive state and resuming or starting receiving of at least one of the MBS broadcast System Information Block (SIB), the MBS Control Channel (MCCH), the MBS broadcast session data over MBS Traffic Channel (MTCH) in the idle state, when the SDT procedure is completed unsuccessfully and the UE was receiving at least one of the MBS broadcast System Information Block (SIB), the MBS Control Channel (MCCH), the MBS broadcast session data over MBS Traffic Channel (MTCH) before initiation of SDT procedure.

[0023] In an embodiment, when the SDT procedure is at least one of initiated and ongoing at the UE, the method includes determining, by the UE, whether the SDT procedure is completed successfully or unsuccessfully. Further, the method includes determining, by the UE, whether the UE was receiving the at least one of MBS multicast SIB, multicast MCCH, and the MBS multicast session data over multicast MTCH. Further, the method includes determining, by the UE, whether at least one of a RRC release message, RRC release message configured with suspend configuration, or RRC resume message is received from the network apparatus, when the SDT procedure is completed successfully and the UE was receiving at least one of the MBS multicast SIB, the multicast MCCH, and MBS multicast session data over multicast MTCH. Further, the method includes performing one of transiting, by the UE, to the idle state from the inactive state and releasing configurations for at least one multicast session, when the UE receives the RRC release message from the network apparatus. Also forwarding, by the UE, at least one of Temporary Mobile Group Identifier (TMGI) associated with at least one of the MBS multicast session to the upper layer of the UE. Further, the method includes starting or resuming, by the UE, receiving of the MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH in the inactive state, when the UE receives the RRC release message configured with suspend configuration from the network apparatus. Also, the method includes transiting, by the UE, to connected state from the inactive state, and continue receiving at least one of the MBS multicast sessions, when the UE receives RRC resume message from the network apparatus; and. Further, the method includes transiting, by the UE, to idle state from inactive state and forwarding list of TMGIs of the multicast sessions configured for reception in the inactive sate to upper layer of the UE, when the SDT procedure is completed unsuccessfully and the UE was receiving at least one of the MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH.

[0024] In an embodiment, the method includes determining, by the UE, whether a cell reselection occurs while the SDT procedure is ongoing. Further, the method includes determining, by the UE, whether the UE was receiving at least one of the MBS broadcast System Information Block (SIB), the MBS Control Channel (MCCH), the MBS broadcast session data over MBS Traffic Channel (MTCH) before initiation of SDT procedure. Further, the method includes transiting, by the UE, to the idle state from the inactive state and starting or resuming reception of at least one of the MBS broadcast System Information Block (SIB), the MBS Control Channel (MCCH), the MBS broadcast session data over MBS Traffic Channel (MTCH), when the cell reselection occurs while the SDT procedure is ongoing and the UE was receiving at least one of the MBS broadcast System Information Block (SIB), the MBS Control Channel (MCCH), the MBS broadcast session data over MBS Traffic Channel (MTCH) before initiation of SDT procedure.

[0025] In an embodiment, the method includes sending, by the UE, an indication from a lower layer of the UE to an upper layer of the UE. The indication indicates at least one of suspending or stopping of the MBS session, the resuming or starting of MBS session, when the SDT procedure is at least one of initiated, ongoing, successfully completed or unsuccessfully completed, and when the UE is at least one of configured or interested or was receiving the MBS broadcast session data or MBS multicast session data in the inactive state before initiation of the SDT procedure.

[0026] In an embodiment, the downlink channel is at least one of a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH).

[0027] In an embodiment, the downlink channel is monitored for a System Information - Radio Network Temporary Identifier (SI-RNTI), Paging - Radio Network Temporary Identifier (P-RNTI), MBS Control Channel - Radio Network Temporary Identifier (MCCH-RNTI), multicast MCCH-RNTI, Group-Radio Network Temporary Identifier (G-RNTI) or a G-CS-RNTI associated with at least one of the MBS broadcast and the MBS multicast

[0028] In an embodiment, the method includes receiving, by the UE, at least one of a unicast session data and a MBS multicast session data from the network apparatus when the UE is in a connected state. Further, the method includes receiving, by the UE, at least one of a System Information Block (SIB), at least one MBS broadcast specific SIB, at least one broadcast MCCH channel, and at least one broadcast MTCH channel without disrupting the reception of at least one of the unicast data and the MBS multicast session data, when one or more conditions for concurrent operations of MBS broadcast and at least one of unicast and MBS multicast are met.

[0029] In an embodiment, the method of determining whether the one or more conditions for concurrent operations of MBS broadcast and at least one of unicast and MBS multicast are met includes determining, by the UE, whether the UE has capability of receiving MBS broadcast along with at least one of unicast and MBS multicast. Further, the method includes determining, by the UE, whether beams for the MBS broadcast are quasi-co located (QCL) with at least one of the unicast beams and multicast beams.

[0030] In an embodiment, when the SDT procedure is ongoing the method includes determining, by the UE, whether a need to receive the MBS broadcast or UE was receiving MBS broadcast service before the initiation of the SDT procedure. Further, the method includes continue receiving, by the UE, the MBS broadcast session data through the downlink channel while SDT procedure is ongoing, when there was a need to receive the MBS or UE was receiving MBS broadcast service before the initiation of the SDT procedure.

[0031] In an embodiment, wherein when the SDT procedure is ongoing, the method includes, detecting, by the UE, an occurrence of a cell reselection event and whether the at least one SDT procedure is ongoing. Further, the method includes transiting, by the UE, to an idle state from the inactive state, when the cell reselection is occurred, SDT procedure is ongoing and there was a need by the UE to receive MBS broadcast or UE was receiving MBS broadcast service before the initiation of the SDT procedure. Further, the method includes starting or resuming, by the UE, reception of MBS broadcast session data, when the UE is transited to the idle state.

[0032] In an embodiment, the method includes detecting, by the UE, the MBS broadcast session data or MBS multicast session data is halted, when the SDT procedure is initiated or ongoing. Further, the method includes stopping, by the UE, a DRX timer used for the MBS broadcast session data or MBS multicast session data addressed by a G-RNTI or a G-CS-RNTI in the inactive state.

[0033] In an embodiment, the method includes detecting, by the UE, the MBS broadcast session data or MBS multicast session data is halted, when the SDT procedure is initiated or ongoing. Further, the method includes clearing, by the UE, a HARQ buffer used for the MBS broadcast session data or MBS multicast session data addressed by a G-RNTI or a G-CS-RNTI in the inactive state.

[0034] Accordingly, the embodiments herein provides a UE for handling Multicast Broadcast Service (MBS) in a telecommunication network system. The UE comprises a processor and a MBS controller coupled to the processor. The MBS controller is configured to receive at least one of a MBS broadcast System Information Block (SIB), MBS Control Channel (MCCH), MBS broadcast session data over MBS Traffic Channel (MTCH), a MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH from a network apparatus when the UE is in an inactive state. Further, the MBS controller determines whether a SDT procedure is at least one of initiated and ongoing at the UE. Further, the MBS controller determines whether one or more conditions for concurrent operations of unicast and MBS are met. Also, the MBS controller performs one of suspend or stop reception of at least one of a MBS broadcast System Information Block (SIB), MBS Control Channel (MCCH), MBS broadcast session data over MBS Traffic Channel (MTCH), a MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH. Also suspends monitoring for a downlink channel associated with at least one of the MBS broadcast session data and the MBS multicast session data from a network apparatus, when the SDT procedure is at least one of initiated and ongoing at the UE and one or more conditions for concurrent operations of unicast and MBS are not met. Further, the MBS controller continue the reception of at least one of a MBS broadcast System Information Block (SIB), MBS Control Channel (MCCH), MBS broadcast session data over MBS Traffic Channel (MTCH), a MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH and continue monitoring for a downlink channel associated with at least one of the MBS broadcast session data and the MBS multicast session data from a network apparatus, when the SDT procedure is at least one of initiated and ongoing at the UE and one or more conditions for concurrent operations of unicast and MBS are met.

[0035] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications be made within the scope of the embodiments herein.

[0036] An embodiment of the disclosure provides a method and apparatus to perform channel measurements for NR-U and handling MBS in telecommunication network.

[0037] An embodiment of the disclosure provides a method and apparatus to perform RSSI and channel occupancy measurement for NR-U operation.

[0038] An embodiment of the disclosure provides a method and apparatus to perform the RSSI and channel occupancy measurement for NR-U operation on the frequency configured by the RMTC frequency in measurement object.

[0039] An embodiment of the disclosure provides a method and apparatus to handle SDT and MBS reception when UE is in inactive state.

[0040] An embodiment of the disclosure provides a method and apparatus to handle MBS broadcast and unicast / MBS multicast reception when UE in connected state.

[0041] Advantageous effects obtainable from the disclosure may not be limited to the above-mentioned effects, and other effects which are not mentioned may be clearly understood, through the following descriptions, by those skilled in the art to which the disclosure pertains.

[0042] These and other features, aspects, and advantages of the present embodiments are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

[0043] FIG. 1 is a sequence diagram that illustrates a method for RSSI and channel occupancy measurement for NR unlicensed, according to the prior art as disclosed herein;

[0044] FIG. 2 is a block diagram that illustrates a UE for performing measurement for New Radio Unlicensed (NR-U) in a telecommunication network system, according to the embodiments as disclosed herein;

[0045] FIG. 3 is a flow diagram that illustrates a method for performing measurement for New Radio Unlicensed (NR-U) in a telecommunication network system, according to the embodiments as disclosed herein; and

[0046] FIG. 4 is a block diagram that illustrates a UE for handling Multicast Broadcast Service (MBS) in a telecommunication network system, according to the embodiments as disclosed herein; and

[0047] FIG. 5 is a flow chart that illustrates a method for handling Multicast Broadcast Service (MBS) in a telecommunication network system, according to embodiments as disclosed herein.

[0048] FIG. 6 illustrates a block configuration of a base station according to an embodiment of the disclosure.

[0049] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term "or" as used herein, refers to a non-exclusive or, unless otherwise indicated. 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 skilled in the art to practice the embodiments herein. Accordingly, the examples are not be construed as limiting the scope of the embodiments herein.

[0050] As is traditional in the field, embodiments are described and illustrated in terms of blocks that carry out a described function or functions.　These blocks, which referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and optionally be driven by firmware and software. The circuits, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.　The circuits constituting a block be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments be physically separated into two or more interacting and discrete blocks without departing from the scope of the proposed method.　Likewise, the blocks of the embodiments be physically combined into more complex blocks without departing from the scope of the proposed method.

[0051] The accompanying drawings are used to help easily understand various technical features and it is understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the proposed method is construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. used herein to describe various elements, these elements are not be limited by these terms. These terms are generally used to distinguish one element from another.

[0052] It may be noted that to the extent possible, like reference numerals have been used to represent like elements in the drawing. Further, those of ordinary skill in the art will appreciate that elements in the drawing are illustrated for simplicity and may not have been necessarily drawn to scale. For example, the dimension of some of the elements in the drawing may be exaggerated relative to other elements to help to improve the understanding of aspects of the invention. Furthermore, the elements may have been represented in the drawing by conventional symbols, and the drawings may show only those specific details that are pertinent to the understanding the embodiments of the invention so as not to obscure the drawing with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.

[0053] NR-U brings to 5G a variety of options for flexibly utilizing unlicensed spectrum and 3rdGeneration Partnership Project (3GPP) Release 16 is the first global cellular standard that supports both license-assisted and standalone use of unlicensed spectrum. The specifications allow devices to access up to 400 MHz and 100 MHz of unlicensed spectrum bandwidth in downlink and uplink, respectively.

[0054] As part of NR Unlicensed requirements, the 3GPP has introduced RSSI and channel occupancy measurements for identifying percentage of channel occupancy. The method of identifying the channel occupancy is achieved by introducing a new configuration in existing measurement object, which is named as rmtc-Config.

[0055] Below section in the 3GPP TS 38.331 Release 17 depicts the inclusion of the rmtc-Config in a MeasObjectNR.

[0056] 6.3.2 Radio resource control information elements　- MeasObjectNRThe IEMeasObjectNRspecifies information applicable for SS / PBCH block(s) intra / inter-frequency measurements and / or CSI-RS intra / inter-frequency measurements.-- ASN1START-- TAG-MEASOBJECTNR-STARTMeasObjectNR ::= SEQUENCE {ssbFrequency ARFCN-ValueNR OPTIONAL, -- Cond SSBorAssociatedSSBssbSubcarrierSpacing SubcarrierSpacing OPTIONAL, -- Cond SSBorAssociatedSSBsmtc1 SSB-MTC OPTIONAL, -- Cond SSBorAssociatedSSBsmtc2 SSB-MTC2 OPTIONAL, -- Cond IntraFreqConnectedrefFreqCSI-RS ARFCN-ValueNR OPTIONAL, -- Cond CSI-RSreferenceSignalConfig ReferenceSignalConfig,absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need RabsThreshCSI-RS-Consolidation ThresholdNR OPTIONAL, -- Need RnrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need RnrofCSI-RS-ResourcesToAverage INTEGER (2..maxNrofCSI-RS-ResourcesToAverage) OPTIONAL, -- Need RquantityConfigIndex INTEGER (1..maxNrofQuantityConfig),offsetMO Q-OffsetRangeList,cellsToRemoveList PCI-List OPTIONAL, -- Need NcellsToAddModList CellsToAddModList OPTIONAL, -- Need NexcludedCellsToRemoveList PCI-RangeIndexList OPTIONAL, -- Need NexcludedCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need NallowedCellsToRemoveList PCI-RangeIndexList OPTIONAL, -- Need NallowedCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need N...,[[freqBandIndicatorNR FreqBandIndicatorNR OPTIONAL, -- Need RmeasCycleSCell ENUMERATED {sf160, sf256, sf320, sf512, sf640, sf1024, sf1280} OPTIONAL -- Need R]],[[smtc3list-r16 SSB-MTC3List-r16 OPTIONAL, -- Need Rrmtc-Config-r16 SetupRelease {RMTC-Config-r16} OPTIONAL, -- Need Mt312-r16 SetupRelease { T312-r16 } OPTIONAL -- Need M]],[[associatedMeasGapSSB-r17 MeasGapId-r17 OPTIONAL, -- Need RassociatedMeasGapCSIRS-r17 MeasGapId-r17 OPTIONAL, -- Need Rsmtc4List-r17 SSB-MTC4List-r17 OPTIONAL, -- Cond SSBorAssociatedSSBmeasCyclePSCell-r17 ENUMERATED {ffs} OPTIONAL -- Need R FFS]]}

[0057] The rmtc-Config contains information elements like rmtc-Periodicity, rmtc-Frequency etc. Below section in the 3GPP TS 38.331 Release 17 depicts the content of the rmtc-Config.

[0058] 6.3.2 Radio resource control information elements　RMTC-Config-r16 ::= SEQUENCE {rmtc-Periodicity-r16 ENUMERATED {ms40, ms80, ms160, ms320, ms640},rmtc-SubframeOffset-r16 INTEGER(0..639) OPTIONAL, -- Need MmeasDurationSymbols-r16 ENUMERATED {sym1, sym14or12, sym28or24, sym42or36, sym70or60},rmtc-Frequency-r16 ARFCN-ValueNR,ref-SCS-CP-r16 ENUMERATED {kHz15, kHz30, kHz60-NCP, kHz60-ECP},...,[[rmtc-Bandwidth-r17 ENUMERATED {mhz100, mhz400, mhz800, mhz1600, mhz2000} OPTIONAL, -- Need RmeasDurationSymbols-v1700 ENUMERATED {sym140, sym560, sym1120} OPTIONAL, -- Need Rref-SCS-CP-v1700 ENUMERATED {kHz120, kHz480, kHz960} OPTIONAL -- Need R]]}

[0059] NR MBS can refer to multicast services where intended common contents are targeted to a group of User Equipment (UE) (terminal), which have joined the multicast group in the multicast coverage area and to broadcast services where intended contents may be targeted to all the UEs in the broadcast coverage area. This coverage area can be one radio cell or larger.

[0060] Specifically, multicast services refer to services being transmitted and availed by a set of UEs registered to a group; for example, 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 the broadcast is performed and typically, the UE need not be registered. Therefore, effectively, both multicast and broadcast services are PTM (Point-To-MultiPoint) services, as there is one transmitter and multiple recipients. It is also possible to provide multicast and / or broadcast services in a PTP (Point-to-Point) manner, wherein there are multiple PTP connections to share the same MBS services with multiple 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 the transmitter and the receiver.

[0061] In the legacy system (i.e., 3GPP Release 17 MBS), the UEs could receive multicast service only in the RRC_CONENCTED state. For the purpose of informing the UEs in the RRC_IDLE state or RRC_INACTIVE state about multicast session "activation", a group notification or group paging mechanism is utilized. Based on reception of this paging, the UE transits to RRC_CONNECTED state and starts receiving the multicast session. However, there may also be UEs which can receive multicast session(s) in the RRC_INACTIVE state (e.g., 3GPP Release 18 MBS considers such a scenario).

[0062] MBS broadcast services can be received in all RRC states viz. RRC_CONNECTED, RRC_INACTIVE and RRC_IDLE states. That is, MBS broadcast reception is agnostic to the RRC state of the UE. For MBS broadcast reception, UE needs to acquire SIB1 (provides scheduling information for SIB20), SIB20, MBS Control Channel (MCCH) and MBS Traffic Channel (MTCH). SIB1 provides scheduling information for SIB20. SIB20 is MBS specific SIB and provides configuration for MCCH channel. MCCH provides the scheduling and configuration for MBS broadcast services reception on MTCH channel(s). MTCH channel carries the traffic for MBS broadcast services.

[0063] SDT (small data transmission) is a procedure allowing data and / or signaling transmission while remaining in the RRC_INACTIVE state (i.e., without transitioning to the RRC_CONNECTED state). The SDT is enabled on a radio bearer basis and is initiated by the UE only if less than a configured amount of Uplink (UL) data awaits transmission across all radio bearers for which the SDT is enabled, the downlink (DL) Reference Signal Received Power (RSRP) is above a configured threshold, and a valid SDT resource is available. Logical channel restrictions configured by the network while in the RRC_CONNECTED state and / or in RRCRelease message for radio bearers enabled for the SDT, if any, are applied by the UE during the SDT procedure.

[0064] A potential issue relates to the UE that is capable / configured and / or interested to receive or receiving MBS broadcast service and / or MBS multicast service in RRC_INACTIVE and the SDT procedure is initiated for the UE. It is not clear as to how the UE needs to handle SDT and MBS reception in this scenario.

[0065] Thus, it is desired to address the above-mentioned disadvantages, issues, or other shortcomings or at least provide a useful alternative.

[0066]

[0067] Accordingly, the embodiments disclose a method for performing measurement for New Radio Unlicensed (NR-U) in a telecommunication network system. The method includes receiving, by a User Equipment (UE), a measurement configuration from a network apparatus. The measurement configuration comprises of measurement identity list and at least one measurement object and at least one measurement report configuration. Also, the measurement object comprises a RSSI Measurement Timing Configuration (RMTC) configuration including at least one RMTC-frequency and a measurement identity is associated with a measurement object and a measurement report configuration. Further, the method includes performing, by the UE, the measurement for the NR-U on the RMTC-frequency indicated by the RMTC-configuration in the associated measurement object and based on the associated measurement report configuration for a measurement identity.

[0068] Accordingly, the embodiments disclose a UE for performing measurement for New Radio Unlicensed (NR-U) in a telecommunication network system. The UE comprises at least one of a processor and a NR-U controller coupled to the processor. The NR-U controller is configured to receive a measurement configuration from a network apparatus. The measurement configuration comprises of measurement identity list and at least one measurement object and at least one measurement report configuration. Also, the measurement object comprises a RSSI Measurement Timing Configuration (RMTC) configuration including at least one RMTC-frequency and a measurement identity is associated with a measurement object and a measurement report configuration. Further, the NR-U controller performs the measurement for the NR-U on the RMTC-frequency indicated by the RMTC-configuration in the associated measurement object and based on the associated measurement report configuration for a measurement identity.

[0069] Accordingly, the embodiments disclose a method for handling Multicast Broadcast Service (MBS) in a telecommunication network system. The method includes receiving, by a UE, at least one of a MBS broadcast System Information Block (SIB), MBS Control Channel (MCCH), MBS broadcast session data over MBS Traffic Channel (MTCH), a MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH from a network apparatus when the UE is in an inactive state. Further, the method includes determining, by the UE, whether a SDT procedure is at least one of initiated and ongoing at the UE. Further, the method includes determining, by the UE, whether one or more conditions for concurrent operations of unicast and MBS are met. Further, the method includes performing, by the UE, one of suspending or stopping reception of at least one of a MBS broadcast System Information Block (SIB), MBS Control Channel (MCCH), MBS broadcast session data over MBS Traffic Channel (MTCH), a MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH. Also, suspending monitoring for a downlink channel associated with at least one of the MBS broadcast session data and the MBS multicast session data from a network apparatus, when the SDT procedure is at least one of initiated and ongoing at the UE and one or more conditions for concurrent operations of unicast and MBS are not met. Further, the method includes continuing the reception of at least one of a MBS broadcast System Information Block (SIB), MBS Control Channel (MCCH), MBS broadcast session data over MBS Traffic Channel (MTCH), a MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH and continuing monitoring for a downlink channel associated with at least one of the MBS broadcast session data and the MBS multicast session data from a network apparatus, when the SDT procedure is at least one of initiated and ongoing at the UE and one or more conditions for concurrent operations of unicast and MBS are met.

[0070] Accordingly, the embodiments disclose a UE for handling Multicast Broadcast Service (MBS) in a telecommunication network system. The UE comprises a processor and a MBS controller coupled to the processor. The MBS controller is configured to receive at least one of a MBS broadcast System Information Block (SIB), MBS Control Channel (MCCH), MBS broadcast session data over MBS Traffic Channel (MTCH), a MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH from a network apparatus when the UE is in an inactive state. Further, the MBS controller determines whether a SDT procedure is at least one of initiated and ongoing at the UE. Further, the MBS controller determines whether one or more conditions for concurrent operations of unicast and MBS are met. Also, the MBS controller performs one of suspend or stop reception of at least one of a MBS broadcast System Information Block (SIB), MBS Control Channel (MCCH), MBS broadcast session data over MBS Traffic Channel (MTCH), a MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH. Also suspends monitoring for a downlink channel associated with at least one of the MBS broadcast session data and the MBS multicast session data from a network apparatus, when the SDT procedure is at least one of initiated and ongoing at the UE and one or more conditions for concurrent operations of unicast and MBS are not met. Further, the MBS controller continue the reception of at least one of a MBS broadcast System Information Block (SIB), MBS Control Channel (MCCH), MBS broadcast session data over MBS Traffic Channel (MTCH), a MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH and continue monitoring for a downlink channel associated with at least one of the MBS broadcast session data and the MBS multicast session data from a network apparatus, when the SDT procedure is at least one of initiated and ongoing at the UE and one or more conditions for concurrent operations of unicast and MBS are met. The one or more conditions includes, determining whether the UE has capability of receiving at least one of MBS broadcast and MBS multicast along with unicast and also determining whether beams for the at least one of MBS broadcast and MBS multicast are quasi-co located (QCL) with the unicast beams.

[0071] Fig. 1 is a sequence diagram that illustrates a method for RSSI and channel occupancy measurement for NR unlicensed, according to the prior art as disclosed herein. In an existing art, at S1, a UE (101) is in connected mode with a network apparatus (103). Further, at step S2, the network apparatus (e.g., base station) (103) transmits a RRC reconfiguration message to the UE (101). The Radio Resource Control (RRC) reconfiguration message comprises a Measobject. Further, the Measobject contains one or more frequencies including a ssbFrequency, the refFreqCSI-RS and the rmtc-Frequency. Also, a measRSSI ReportConfig is configured in the associated reportConfig.

[0072] The below section in TS 38.331 depicts that MeasObjectNR that contain multiple frequencies such as the ssbFrequency , the reffreqCSI-RS and the rmtc-Frequency:

[0073] 6.3.2 Radio resource control information elements　- MeasObjectNRThe IEMeasObjectNRspecifies information applicable for SS / PBCH block(s) intra / inter-frequency measurements and / or CSI-RS intra / inter-frequency measurements-- ASN1START-- TAG-MEASOBJECTNR-STARTMeasObjectNR ::= SEQUENCE {ssbFrequency ARFCN-ValueNR OPTIONAL, -- Cond SSBorAssociatedSSB　　ssbSubcarrierSpacing SubcarrierSpacing OPTIONAL, -- Cond SSBorAssociatedSSBsmtc1 SSB-MTC OPTIONAL, -- Cond SSBorAssociatedSSBsmtc2 SSB-MTC2 OPTIONAL, -- Cond IntraFreqConnectedrefFreqCSI-RS ARFCN-ValueNR OPTIONAL, -- Cond CSI-RSreferenceSignalConfig ReferenceSignalConfig,absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need RabsThreshCSI-RS-Consolidation ThresholdNR OPTIONAL, -- Need RnrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need RnrofCSI-RS-ResourcesToAverage INTEGER (2..maxNrofCSI-RS-ResourcesToAverage) OPTIONAL, -- Need RquantityConfigIndex INTEGER (1..maxNrofQuantityConfig),offsetMO Q-OffsetRangeList,cellsToRemoveList PCI-List OPTIONAL, -- Need NcellsToAddModList CellsToAddModList OPTIONAL, -- Need NexcludedCellsToRemoveList PCI-RangeIndexList OPTIONAL, -- Need NexcludedCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need NallowedCellsToRemoveList PCI-RangeIndexList OPTIONAL, -- Need NallowedCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need N...,[[freqBandIndicatorNR FreqBandIndicatorNR OPTIONAL, -- Need RmeasCycleSCell ENUMERATED {sf160, sf256, sf320, sf512, sf640, sf1024, sf1280} OPTIONAL -- Need R]],[[smtc3list-r16 SSB-MTC3List-r16 OPTIONAL, -- Need Rrmtc-Config-r16 SetupRelease {RMTC-Config-r16} OPTIONAL, -- Need Mt312-r16 SetupRelease { T312-r16 } OPTIONAL -- Need M]],[[associatedMeasGapSSB-r17 MeasGapId-r17 OPTIONAL, -- Need RassociatedMeasGapCSIRS-r17 MeasGapId-r17 OPTIONAL, -- Need Rsmtc4List-r17 SSB-MTC4List-r17 OPTIONAL, -- Cond SSBorAssociatedSSBmeasCyclePSCell-r17 ENUMERATED {ffs} OPTIONAL -- Need R FFS]]}　RMTC-Config-r16 ::= SEQUENCE {rmtc-Periodicity-r16 ENUMERATED {ms40, ms80, ms160, ms320, ms640},rmtc-SubframeOffset-r16 INTEGER(0..639) OPTIONAL, -- Need MmeasDurationSymbols-r16 ENUMERATED {sym1, sym14or12, sym28or24, sym42or36, sym70or60},rmtc-Frequency-r16 ARFCN-ValueNR,ef-SCS-CP-r16 ENUMERATED {kHz15, kHz30, kHz60-NCP, kHz60-ECP},...,[[rmtc-Bandwidth-r17 ENUMERATED {mhz100, mhz400, mhz800, mhz1600, mhz2000} OPTIONAL, -- Need RmeasDurationSymbols-v1700 ENUMERATED {sym140, sym560, sym1120} OPTIONAL, -- Need Rref-SCS-CP-v1700 ENUMERATED {kHz120, kHz480, kHz960} OPTIONAL -- Need R]]}

[0074] Further, at step S3, the UE (101) sends a RRC reconfiguration complete message upon successfully receiving the RRC reconfiguration message.

[0075] However, at step S4, the UE (101) faces ambiguity in choosing the frequency among the messbfrequency, the refFreqCSI and the rmtc-Frequency included in the MeasOject of the RRC reconfiguration for performing the RSSI and the channel occupancy measurement. Also, when UE (101) chooses a frequency arbitrarily for performing the RSSI and the channel occupancy measurement, this could lead to the degradation of the performance of the UE (101).

[0076] The ssbFrequency indicates the frequency of the synchronization signal associated to the MeasObjectNR and refFreqCSI-RS denotes the frequency of the Channel State Information Reference Signal (CSI-RS) associated to the MeasObjectNR. Whereas, the rmtc-Frequency from the rmtc-Config indicates the centre frequency of the measured bandwidth for the frequency which operates with shared spectrum channel access. In general, the RSSI measurement can be performed with any configured reference signal and different types of the RSSI measurement can use different kind of reference signals. As in the Long Term Evolution (LTE) system, a carrier frequency (carrier-Freq) is considered for the RSSI measurement. The mechanism for the NR RSSI measurement is adopted from the LTE. The UE implementation may go wrong with incorrect selection of the frequency for the RSSI measurement. Particularly, the RSSI comprises the linear average of the total received power observed only per configured Orthogonal Frequency-Division Multiplexing (OFDM) symbol and in the measurement bandwidth indicated by higher layers or corresponding to the channel bandwidth. Where the channel has the centre-frequency configured by the selected frequency, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise. Wrong selection of frequency causes an incorrect measurement of the RSSI value and resultantly, the UE failed to perform UE's operation which will lead to drastic problem.

[0077] The proposed solution provides a method for performing measurement for NR-U in telecommunication network system. Particularly, the method aims to select a suitable frequency for RSSI and channel occupancy measurement when operating in a shared spectrum channel access. Further, the proposed solution provides a clear approach for the NR specification for NR-U measurement operation. Also, the proposed solution ensures a consistent and accurate performance between the UE and network apparatus. Also, the proposed solution provides a deterministic approach for frequency selection and achieves a required measurement performance.

[0078] In a conventional technique, when the UE is capable or configured to receive at least one of MBS broadcast service or MBS multicast service in RRC INACTIVE state and also SDT procedure is initiated, the UE is not aware of handling both SDT and MBS reception.

[0079] The proposed solution provides a system and method for handling SDT and MBS reception. The present method includes handling SDTs along with NR MBS broadcast service and / or MBS multicast service reception, when the UE is in RRC_INACTIVE state.

[0080] FIG. 2 is a block diagram that illustrates a UE for performing measurement for New Radio Unlicensed (NR-U) in a telecommunication network system, according to the embodiments as disclosed herein. The UE (201) includes a processor (203), an I / O interface (transceiver / transmitter / receiver / communication unit) (205), a memory, and a NR-U controller (209). The UE (201) can be an end-user device that connects with a communication network to access services. For example, the UE (101) can include, but not limited to a mobile phone, a smart phone, tablets, a palmtop, Personal Digital Assistant (PDA), laptops, Internet of Things (IoT), devices a virtual reality device, a television, a connected car, a foldable device, a flexible device, a display device and an immersive system.

[0081] Further, the processor (203) of the UE (201) communicates with the memory (207), the I / O interface (205) and the NR-U controller (209). The processor (203) is configured to execute instructions stored in the memory (207) and to perform various processes. The processor (203) can include one or a plurality of processors, can 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 Artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0082] Further, the memory (207) of the UE (201) includes storage locations to be addressable through the processor (203). The memory (207) is not limited to a volatile memory and / or a non-volatile memory. Further, the memory (207) can include one or more computer-readable storage media. The memory (207) can include non-volatile storage elements. For example, non-volatile storage elements can include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. The memory (207) can store the media streams such as audios stream, video streams, haptic feedbacks and the like. The memory (207) can store several information received in the measurement configuration. The several information can include, but not limited to measurement identity list, measurement object and measurement report configuration can be stored in the memory (207).

[0083] The I / O interface (205) transmits the information between the memory (207) and external peripheral devices. The peripheral devices are the input-output devices associated with the UE (201). The I / O interface (205) can receive measurement configuration from the network apparatus through the I / O interface (205).

[0084] The NR-U controller (209) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components.

[0085] The NR-U controller (209) receives the measurement configuration from the network apparatus. The measurement configuration comprises the measurement identity list, at least one measurement object and at least one measurement report configuration. The measurement object comprises a RSSI Measurement Timing Configuration (RMTC) configuration. Further, the RMTC configuration includes the RMTC-frequency. Also, a measurement identity is associated with the measurement object and the measurement report configuration. Further, the NR-U controller (209) performs the measurement for the NR-U on the RMTC-frequency indicated by the RMTC-configuration in the associated measurement object and based on the associated measurement report configuration for a measurement identity. Particularly, the measurement for the NR-U is a RSSI measurement and the channel occupancy measurement. The RSSI measurement and the channel occupancy measurement is performed by determining whether the report type for the associated measurement report configuration is one of a periodic measurement type, an event triggered measurement type, or a conditional trigger configuration measurement type. Further, the NR-U controller (209) determines whether a measurement gap configuration is set up or the UE does not require the measurement gap to perform the measurement, when the report type for the associated measurement report configuration is one of the periodic measurement type, the event triggered measurement type, or the conditional trigger configuration measurement type. Further, the NR-U controller (209) determines whether a measure RSSI-Report configuration is configured in the associated measurement report configuration when the measurement gap configuration is set up or the measurement gap configuration is not required for the measurement. Further, the NR-U controller (209) performs the measurement for the NR-U on the frequency configured by RMTC-frequency in the associated measurement object, when the measure RSSI-Report configuration is configured in the associated measurement report configuration. In an embodiment, the processor (203) and the NR-U controller (209) may be the same at least one processor / controller. The processor (203) and the NR-U controller (209) may mean performing functionally different operations.

[0086] In an embodiment, examples of specification text is provided as below for performing measurements such that the RSSI and channel occupancy measurement is performed on the rmtc-Frequency as provided in the rmtc configuration in the associated measurement object of the NR measurement.

[0087] Example 1:

[0088] 5.5.3 Performing measurements　 5.5.3.1 GeneralThe UE shall:1> for eachmeasIdincluded in themeasIdListwithinVarMeasConfig:2> if thereportTypefor the associatedreportConfigisperiodical,eventTriggeredorcondTriggerConfig:　　　　 3> if a measurement gap configuration is setup, or　　　　 3> if the UE does not require measurement gaps to perform the concerned measurements:　　　　　　　　　　 4> if themeasRSSI-ReportConfigis configured in the associatedreportConfig:　　　　　　　　　　　　　　　　5> perform the RSSI and channel occupancy measurements on the rmtc-frequency indicated by the rmtc-Config in the associatedmeasObject;

[0089] Example 2:

[0090] 5.5.3 Performing measurements　 5.5.3.1 GeneralThe UE shall:1> for eachmeasIdincluded in themeasIdListwithinVarMeasConfig:2> if thereportTypefor the associatedreportConfigisperiodical,eventTriggeredorcondTriggerConfig:　　　　 3> if a measurement gap configuration is setup, or　　　　 3> if the UE does not require measurement gaps to perform the concerned measurements:　　　　　　　　　　 4> if themeasRSSI-ReportConfigis configured in the associatedreportConfigand measObject corresponds to NR:　　　　　　　　　　　　　　　　5> perform the RSSI and channel occupancy measurements on the rmtc-frequency indicated by the rmtc-Config in the associatedmeasObject;

[0091] In an embodiment, when the measurement object configured for the UE (201) corresponds to the NR and the measurement does not correspond to the shared channel access or NR-Unlicensed, the UE (201) performs the RSSI measurement on the ssbFrequency and / or refFreqCSI-RS as provided in the configuration of the associated measurement object. The selection among Synchronization Signal Block (SSB) and the CSI-RS based measurement can be based on the reference signal type field (rsType) in the reportConfig being set to the SSB or the CSI-RS.

[0092] In an embodiment, when the measurement object configured for the UE (201) corresponds to the NR and the rmtc-Config and / or rmtc-Frequcncy is not configured / provided, the UE (201) performs the RSSI and the channel occupancy measurement on the ssbFrequency and / or refFreqCSI-RS as provided in the configuration of the associated measurement object. The selection among the SSB and the CSI-RS based measurement can be based on the reference signal type field (rsType) in the reportConfig being set to the SSB or the CSI-RS.

[0093] In an embodiment, when the measurement object configured for the UE (201) corresponds to inter-RAT LTE measurement, the UE (201) performs the RSSI and the channel occupancy measurement on the carrier frequency (e.g. termed as carrierFreq) as provided in the configuration of the associated measurement object.

[0094] FIG. 3 is a flow diagram that illustrates a method for performing measurement for New Radio Unlicensed (NR-U) in a telecommunication network system, according to the embodiments as disclosed herein.

[0095] At block 301, the NR-U controller (209) receives a measurement configuration from a network apparatus, the measurement configuration comprises of measurement identity list and at least one measurement object and at least one measurement report configuration. The measurement object comprises a RSSI Measurement Timing Configuration (RMTC) configuration including at least one RMTC-frequency and also the measurement identity is associated with a measurement object and a measurement report configuration.

[0096] At block 303, the NR-U controller (209) performs the measurement for the NR-U on the RMTC-frequency indicated by the RMTC-configuration in the associated measurement object and based on the associated measurement report configuration for a measurement identity. Then, the controller (203) transmits the result of the measurement based on the associated measurement report configuration for a measurement identity.

[0097] FIG. 4 is a block diagram that illustrates a UE for handling Multicast Broadcast Service (MBS) in a telecommunication network system, according to the embodiments as disclosed herein. The UE (401) includes a processor (403), an I / O interface (transceiver / transmitter / receiver / communication unit) (405), a memory (407) and a MBS controller (409). The UE (401) can be at least one of a mobile phone, tablet, computer, laptop, and smart watch. Further, the processor (403) of the UE (401) communicates with the memory (407), the I / O interface (405) and the MBS controller (409). The processor (403) is configured to execute instructions stored in the memory (407) and to perform various processes. The processor (403) can include one or a plurality of processors, can 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 Artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0098] Further, the memory (407) of the UE (401) includes storage locations to be addressable through the processor (403). The memory (407) is not limited to a volatile memory and / or a non-volatile memory. Further, the memory (407) can include one or more computer-readable storage media. The memory (407) can include non-volatile storage elements. For example, non-volatile storage elements can include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. The memory (407) can store the media streams such as audios stream, video streams, haptic feedbacks and the like. The memory (407) can store at least one of the MBS broadcast System Information Block (SIB), the MBS broadcast session data received over MBS Traffic Channel (MTCH), a MBS multicast SIB, and the MBS multicast session data received over multicast MTCH from the network apparatus. Also, the memory (407) can store one or more conditions for concurrent operations of unicast and MBS.

[0099] The I / O interface (405) transmits the information between the memory (407) and external peripheral devices. The peripheral devices are the input-output devices associated with the UE (401). The I / O interface (405) receives MBS broadcast SIB, MCCH, MBS broadcast session data over MTCH, the MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH from the network apparatus. Also, the I / O interface (405) can receive one or more conditions for concurrent operations of unicast and MBS.

[0100] The MBS controller (409) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components. In an embodiment, the processor (403) and the MBS controller (409) may be the same at least one processor / controller. The processor (403) and the MBS controller (409) may mean performing functionally different operations.

[0101] The MBS controller (409) receives at least one MBS SIB, MCCH, MBS broadcast session data over MTCH, the MBS multicast SIB, the multicast MCCH, and MBS multicast session data over MTCH from the network apparatus. Further, the MBS controller (409) whether a SDT procedure is at least one of initiated and ongoing at the UE (401). Further, the MBS controller (409) whether one or more conditions for concurrent operations of unicast and MBS are met. The one or more conditions are determining whether the UE (401) has capability of receiving at least one of MBS broadcast and MBS multicast along with unicast and determining whether beams for the at least one of MBS broadcast and MBS multicast are quasi-co located (QCL) with the unicast beams. The concurrent operation of at least one of MBS broadcast and MBS multicast along with unicast may also imply at least one of Time-Division Multiplexed (TDM) and Frequency-Division Multiplexed (FDM) reception operations between at least one of MBS broadcast and MBS multicast and the unicast.

[0102] Further, the MBS controller (409) suspends or stops reception of the at least one MBS SIB, MCCH, MBS broadcast session data over MTCH, the MBS multicast SIB, the multicast MCCH, and MBS multicast session data over MTCH from the network apparatus, when the one or more conditions are not met and the SDT procedure is at least one of initiated and ongoing at the UE (401).

[0103] Further, the MBS controller (409) continues the reception of the at least one MBS SIB, MCCH, MBS broadcast session data over MTCH, the MBS multicast SIB, the multicast MCCH, and MBS multicast session data over MTCH from the network apparatus when the one or more conditions are met and the SDT procedure is at least one of initiated and ongoing at the UE (401).

[0104] In an embodiment, reception of data and / or signaling messages over radio bearers configured for multicast MBS radio bearers (MRBs) that are configured for multicast reception in the RRC_INACTIVE to the UE (401) (i.e. pertaining to the active MBS sessions), is suspended or stopped whilst the UE (401) is in RRC_INACTIVE state and SDT procedure is ongoing.

[0105] In an embodiment, reception of data and / or signaling messages over radio bearers configured for multicast MBS radio bearers (MRBs) that are configured for multicast reception in the RRC_INACTIVE to the UE (401) (i.e. pertaining to the active MBS sessions), is continued whilst the UE (401) is in RRC_INACTIVE state and SDT procedure is ongoing.

[0106] In an embodiment, reception of data and / or signaling messages over radio bearers configured for multicast MBS radio bearers (MRBs) that are configured for multicast reception in the RRC_INACTIVE to the UE (401) (i.e. pertaining to the active MBS sessions), is one of continued or suspended / stopped whilst the UE (401) is in RRC_INACTIVE state and SDT procedure is ongoing, depending on at least one of the UE capability / implementation to support the scenario and network configuration / support for the scenario. UE (401) may indicate its capability to the network in the UE capability information message. Network may configure the UE (401) about the configuration or support for the scenario in a signaling message (e.g. RRCRelease with suspendConfig, multicast MCCH message, SIB message).

[0107] In an embodiment, the UE (401) in RRC_CONNECTED state, is only required to acquire broadcastedSIB1,and / or MBS broadcast specific SIBs (e.g.SIB20 for MCCH configuration for broadcast and / or SIB21 for MBS frequencyinformation), and / or MCCH channel(s) and / or broadcast MTCH channel(s) if the UE (401) can acquire them without disrupting unicast / multicast data reception, i.e. the broadcast and unicast / multicast beams are quasi co-located.

[0108] In an embodiment, the UE (401) in RRC_INACTIVE state while SDT procedure is ongoing, is only required to acquire broadcastedSIB1,MIBand / or MBS broadcast specific SIBs (e.g.SIB20 for MCCH configuration for broadcast and / or SIB21 for MBS frequency information), and / or broadcast MCCH channel(s) and / or broadcast MTCH channel(s)if the UE (401) can acquire them without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.

[0109] In an embodiment, the UE (401) in RRC_INACTIVE state while SDT procedure is ongoing, skips acquiringMBS broadcast specific SIBs (e.g.SIB20 for MCCH configuration for broadcast and / or SIB21 for MBS frequency information), and / or broadcast MCCH channel(s) and / or broadcast MTCH channel(s).

[0110] In an embodiment, the UE (401) in RRC_INACTIVE state while SDT procedure is ongoing, is only required to acquire broadcastedSIB1,MIBand / or MBS multicast specific SIBs (e.g.SIBxfor multicast MCCH configuration), and / or multicast MCCH channel(s) and / or multicast MTCH channel(s)if the UE (401) can acquire them without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.

[0111] In an embodiment, the UE (401) in RRC_INACTIVE state while SDT procedure is ongoing, skips acquiringMBS multicast specific SIBs (e.g.SIBxfor multicast MCCH configuration), and / or multicast MCCH channel(s) and / or multicast MTCH channel(s)

[0112] In an embodiment, when the SDT procedure is initiated, the UE (401) which is interested to receive and / or receiving MBS broadcast service, may stop or suspend the MBS broadcast MCCH and / or MBS broadcast MTCH(s) reception. Further, UE may suspend / stop broadcast MRBs. Further, UE (401) skips receiving MBS broadcast MCCH and / or MBS broadcast MTCH(s) when the SDT procedure is ongoing.

[0113] In an embodiment, when SDT procedure is successfully completed and the UE (401) which is interested to receive and / or was receiving MBS broadcast service before SDT procedure, may start or resume the MBS broadcast MCCH and / or MBS broadcast MTCH(s) reception. Further, UE (401) may resume / start broadcast MRBs.

[0114] In an embodiment, when SDT procedure is unsuccessfully completed and the UE (401) which is interested to receive and / or was receiving MBS broadcast service before SDT procedure initiation, transits to RRC_IDLE state and may start or resume the MBS broadcast MCCH and / or MBS broadcast MTCH(s) reception in RRC_IDLE state. Further, UE (401) may resume / start broadcast MRBs.

[0115] In an embodiment, while the SDT procedure is ongoing, the UE (401) which is interested to receive and / or receiving MBS broadcast service, may continue the MBS broadcast MCCH and / or MBS broadcast MTCH(s) reception. That is, UE (401) may continue broadcast MRBs.

[0116] In an embodiment, if the cell reselection occurs while the SDT procedure is ongoing and the UE (401) is interested to receive and / or has been receiving MBS broadcast service before SDT procedure initiation, the UE (401) goes to RRC_IDLE state from RRC_INACTIVE state. Further, the UE (401) may start or resume the MBS broadcast MCCH and / or MBS broadcast MTCH(s) reception in RRC_IDLE state. That is, UE (401) may resume / start broadcast MRBs.

[0117] In an embodiment, the UE (401) may initiate a transmission of UE assistance information (UAI) message to indicate availability of data and / or signaling mapped to radio bearers which are not configured for the SDT. Further for MBS multicast MRBs, the availability of data and / or signaling may pertain to, for example, a MBS Interest Indication message. Further, the non-SDT-DataIndication or MBS broadcast cause may be indicated in the UAI message. Further, a resumeCause as indicated by the upper layer may be included and set according to the information received from upper layer.

[0118] In an embodiment, when the UE (401) is configured or capable to receive MBS multicast in RRC_INACTIVE state and / or UE (401) was actively receiving at least one multicast session in RRC_INACTIVE state before SDT procedure initiation, the network may direct the UE (401) to be in RRC_INACTIVE state, upon successful completion of the SDT procedure (e.g. via RRC Release with suspendConfig or RRCReject). That is, network avoids directing the UE (401) to transit to RRC_IDLE and / or RRC_CONNECTED state upon completion of SDT procedure. The UE (401) resumes the reception of the multicast session in RRC_INACTIVE state. The UE (401) may utilize the multicast PTM configuration, if present, in the RRC Release with suspendConfig or a RRCReject message while the SDT procedure is ongoing as latest PTM configuration for the multicast sessions.

[0119] In an embodiment, UE (401) is configured or capable to receive MBS multicast in RRC_INACTIVE state and / or UE (401) is actively receiving at least one multicast session in RRC_INACTIVE state while SDT procedure is ongoing, the network may direct the UE (401) to be in RRC_INACTIVE state, upon successful completion of the SDT procedure (e.g. via RRC Release with suspendConfig or RRCReject). That is, network avoids directing the UE (401) to transit to RRC_IDLE and / or RRC_CONNECTED state upon completion of SDT procedure. This is to ensure multicast reception in RRC_INACTIVE remains intact. The UE (401) may utilize the multicast PTM configuration, if present, in the RRC Release with suspendConfig or a RRCReject message while the SDT procedure is ongoing as latest PTM configuration for the multicast sessions.

[0120] In an embodiment, the UE (401) upon receiving the RRCReject message from the network as a response to the RRCResumeRequest / RRCResumeRequest1 triggered as part of the SDT procedure, and the UE (401) is configured to receive and / or receiving at least one multicast service in RRC_INACTIVE state, the UE (401) indicates to upper layer about the failure to resume and / or the list of TMGIs configured / activated for reception in the RRC_INACTIVE state.

[0121] In an embodiment, upon receiving indication from lower layer that resume request was rejected, the upper layer can initiate a RRC Connection request to regain the multicast services.

[0122] In an embodiment, upon receiving multicast PTM configuration in the RRC Release with suspendConfig or a RRCReject message while the SDT procedure is ongoing, the UE (401) resumes the reception of the multicast session in RRC_INACTIVE state. The UE (401) may utilize the multicast PTM configuration, if present, in the RRC Release with suspendConfig or a RRCReject message while the SDT procedure is ongoing as latest PTM configuration for the multicast sessions.

[0123] In an embodiment, upon unsuccessful completion of SDT procedure, UE (401) indicates to upper layer the RRC Connection resume failure and if configured to receive at least one Multicast session in RRC INACTIVE state, UE Access Stratum (AS) layer reports the list of TMGIs of Multicast sessions configured for reception in RRC_INACTIVE state and performs actions upon transition to RRC_IDLE. Further, upper layers may establish a RRC connection to avail multicast sessions in RRC_CONNECTED state.

[0124] In an embodiment, while the SDT procedure is ongoing, if UE (401) is receiving and / or interested to receive MBS multicast session in RRC_INACTIVE state, the UE initiates a "multicast reception in RRC_INACTIVE indication" using UEAssistanceInformation message to the network and may include the resume cause set as "multicastInRRCInactive".

[0125] In an embodiment, in RRC_INACTIVE state, when an SDT procedure is initiated and the UE (401), which is configured and / or indicated for multicast reception in RRC_INACTIVE state and / or receiving at least one multicast session in RRC_INACTIVE, may suspend or stop monitoring the relevant G-RNTI(s) for the PDCCH and / or PDSCH channels and / or suspend or stop the reception of the multicast MCCH channel and / or suspend or stop the reception of the multicast session(s).

[0126] In an embodiment, in RRC_INACTIVE state, while SDT procedure is ongoing and the UE (401), which is configured and / or indicated for multicast reception in RRC_INACTIVE state and / or receiving at least one multicast session in RRC_INACTIVE before SDT procedure initiation, skips monitoring the relevant G-RNTI(s) for the PDCCH and / or PDSCH channels and / or skip the reception of the multicast MCCH channel and / or skip the reception of the multicast session(s).

[0127] In an embodiment, in RRC_INACTIVE state, when an SDT procedure is unsuccessfully completed and the UE, which is configured and / or indicated for multicast reception in RRC_INACTIVE state and / or was receiving at least one multicast session in RRC_INACTIVE before SDT procedure was initiated, may transit to RRC_IDLE state and release the configuration for multicast session(s). The unsuccessful completion of the SDT procedure can be due to at least one of the reasons including cell re-selection, expiry of the SDT failure detection timer, a MAC entity reaching a configured maximum PRACH preamble threshold, an RLC entity reaching a configured maximum retransmission threshold, or expiry of SDT-specific timing alignment timer while SDT procedure is ongoing over Configured Grant (CG) and the UE (401) has not received a response from the network after the initial PUSCH transmission.

[0128] Further, UE (401) resumes monitoring for the paging channel (e.g. for group paging for the multicast session activation notification). Further, UE (401) may inform the relevant TMGIs of the multicast session(s) to the upper layers. The upper layer may initiate a RRC connection establishment request to move the UE (401) to RRC CONNECTED state and at least one of setup the multicast session(s) in RRC_CONNECTED and release the multicast session(s) in RRC_CONNECTED.

[0129] In an embodiment, in RRC_INACTIVE state, when an SDT procedure is successfully completed and the UE (401), which is configured and / or indicated for multicast reception in RRC_INACTIVE state and / or was receiving at least one multicast session in RRC_INACTIVE before SDT procedure was initiated, UE performs at least one of the following:

[0130] a) If the UE (401) receives RRCRelease message from network, UE (401) may transit to RRC_IDLE state and UE (401) may release the configuration for multicast session(s). Further, UE (401) may inform the relevant TMGIs of the multicast session(s) to the upper layers. The upper layer may initiate a RRC connection establishment request to move the UE (401) to RRC CONNECTED state and at least one of setup the multicast session(s) in RRC_CONNECTED and release the multicast session(s) in RRC_CONNECTED;

[0131] b) If the UE (401) receives RRCRelease with suspendConfig or RRCReject message from network, UE (401) may continue in RRC_INACTIVE state and UE (401) may start or resume the MBS multicast MCCH and / or MBS multicast MTCH(s) reception.

[0132] c) If the UE receives RRCResume message from network, UE (401) may transit to RRC_CONNECTED state and UE (401) may release the configuration for multicast session(s) used in RRC_INACTIVE. UE (401) may continue to receive multicast session in RRC_CONNECTED.

[0133] In an embodiment, an example of specification procedure is provided for handling resumption of MBS broadcast MRBs and / or multicast MRBs and receiving MBS broadcast and / or multicast upon reception of the RRCReject by the UE (401) in response to an RRCResumeRequest or an RRCResumeRequest1, when the resume is triggered for SDT:

[0134] Example:

[0135] 5.3.15.2Reception of the RRCReject by the UE

[0136] The UE shall:

[0137] <Omitted Text>

[0138] 1> stop timer T319a, if running and consider SDT procedure is not ongoing;

[0139] <Omitted Text>

[0140] 1> else if RRCReject is received in response to an RRCResumeRequest or an RRCResumeRequest1:

[0141] 2> if resume is triggered by upper layers:

[0142] 3> inform upper layers about the failure to resume the RRC connection;

[0143] 2> if resume is triggered due to an RNA update; or

[0144] 2> if resume is triggered for SDT and T380 has expired:

[0145] 3> set the variable pendingRNA-Update to true;

[0146] 2> discard the current KgNBkey, the KRRCenckey, the KRRCintkey, the KUPintkey and the KUPenckey derived in accordance with 5.3.13.3;

[0147] 2> if resume is triggered for SDT:

[0148] 3> for SRB2, if it is resumed and for SRB1:

[0149] 4> trigger the PDCP entity to perform SDU discard as specified in TS 38.323 [5];

[0150] 4> re-establish the RLC entity as specified in TS 38.322 [4];

[0151] 3> for each DRB that is not suspended:

[0152] 4> indicate PDCP suspend to lower layers;

[0153] 4> re-establish the RLC entity as specified in TS 38.322 [4];

[0154] 2> suspend SRB1 and the radio bearers configured for SDT, if any;

[0155] 2> resume broadcast MRB(s), if suspended / stopped upon SDT initiation, and continue receiving broadcast session(s);

[0156] 2> resume multicast MRB(s), if suspended / stopped upon SDT initiation, and continue receiving multicast session(s)

[0157] 2> the procedure ends.

[0158] In an embodiment, an example of specification procedure is provided for handling resumption of MBS broadcast MRBs and / or multicast MRBs and receiving MBS broadcast and / or multicast upon reception of the RRCRelease with suspendConfig by the UE (401) in response to an RRCResumeRequest or an RRCResumeRequest1, when the resume is triggered for SDT:

[0159] Example:

[0160] 1> if theRRCReleaseincludessuspendConfig:

[0161] 2> <Omitted Text>

[0162] 2> if theRRCReleasemessage withsuspendConfigwas received in response to anRRCResumeRequestor anRRCResumeRequest1:

[0163] 3> stop the timer T319 if running;

[0164] 3> in the stored UE Inactive AS context:

[0165] 4> replace the KgNBand KRRCintkeys with the current KgNBand KRRCintkeys;

[0166] 4> replace thenextHopChainingCountwith the value ofnextHopChainingCountreceived in theRRCReleasemessage;

[0167] 4> replace thecellIdentitywith thecellIdentityof the cell the UE has received theRRCReleasemessage;

[0168] 4> if thesuspendConfigcontains thesl-UEIdentityRemote(i.e. the UE is a L2 U2N Remote UE):

[0169] 5> replace the C-RNTI with the value of thesl-UEIdentityRemote;

[0170] 5> replace the physical cell identitywith the value of thesl-PhysCellIdinsl-ServingCellInfocontained in the discovery message received from the connected L2 U2N Relay UE;

[0171] 4> else:

[0172] 5> replace the C-RNTI with the C-RNTI used in the cell (see TS 38.321 [3]) the UE has received theRRCReleasemessage;

[0173] 5> replace the physical cell identitywith the physical cell identity of the cell the UE has received theRRCReleasemessage;

[0174] 3> replace thenextHopChainingCountwith the value associated with the current KgNB;

[0175] 3> stop the timer T319a if running and consider SDT procedure is not ongoing;

[0176] <Omitted Text>

[0177] 3> resume broadcast MRB(s), if suspended / stopped upon SDT initiation, and continue receiving broadcast session(s);

[0178] 3> resume multicast MRB(s), if suspended / stopped upon SDT initiation, and continue receiving multicast session(s)

[0179] In an embodiment, the UE (401) applies the MCCH information acquisition procedure to acquire the MBS broadcast configuration information broadcasted by the network. The procedure applies to MBS capable UEs (401) interested to receive or that are receiving MBS broadcast services that are in RRC_IDLE, RRC_INACTIVE(if SDT procedure is not ongoing)or RRC_CONNECTED with an active BWP with common search space configured bysearchSpaceMCCH.

[0180] In an embodiment, the broadcast MRB configuration procedure is used by the UE (401) to configure PDCP, RLC, MAC and the physical layer upon starting and / or stopping to receive a broadcast MRB transmitted on MTCH, or upon modification of a configuration of a broadcast MRB received by the UE (401). The procedure applies to MBS capable UEs that are interested to receive or that are receiving an MBS broadcast service that are in RRC_IDLE, RRC_INACTIVE (if SDT procedure is not ongoing) or RRC_CONNECTED with an active BWP with common search space configured bysearchSpaceMTCHorsearchSpaceMCCH.

[0181] In an embodiment, MAC entity of the UE (401) stops the DRX timers for the MBS broadcast session(s) and / or multicast session addressed by G-RNTI and / or G-CS-RNTI in the RRC_INACTIVE state when the SDT procedure is initiated and the MBS broadcast session(s) and / or multicast session data reception is halted. Further, the MAC entity of the UE (401) starts or restarts the DRX timers for the MBS broadcast session(s) and / or multicast session(s) addressed by G-RNTI and / or G-CS-RNTI in the RRC_INACTIVE state when the SDT procedure is successfully completed and the MBS broadcast session(s) and / or multicast session(s) data reception is resumed. Further, the MAC entity of the UE (401) starts or restarts the DRX timers for the MBS broadcast session(s) addressed by G-RNTI and / or G-CS-RNTI in the RRC_INACTIVE state when the SDT procedure is unsuccessfully completed and the MBS broadcast session(s) data reception is resumed.

[0182] In an embodiment, MAC entity of the UE (401) clears the HARQ buffers used for the MBS broadcast session(s) and / or multicast session addressed by G-RNTI and / or G-CS-RNTI in the RRC_INACTIVE state when the SDT procedure is initiated and the MBS broadcast session(s) and / or multicast session data reception is halted.

[0183] In an embodiment, UE (401) reinitializes the PDCP sequence numbers used for the MBS broadcast session(s) addressed by G-RNTI and / or G-CS-RNTI in the RRC_INACTIVE state and the MBS broadcast session(s) is resumed after the SDT procedure is completed successfully or unsuccessfully and / or UE (401) receives at least one of RRCRelease, RRCRelease with suspendConfig, RRCReject and RRCResume message from the network.

[0184] In an embodiment, UE (401) reinitializes the PDCP sequence numbers used for the MBS multicast session(s) addressed by G-RNTI and / or G-CS-RNTI in the RRC_INACTIVE state and the MBS nulticast session(s) is resumed after the SDT procedure is completed successfully and / or UE (401) receives at least one of RRCRelease with suspendConfig, RRCReject and RRCResume message from the network, comprising of the initialRX-DELIV.

[0185] In an embodiment, the lower layer(s) in UE (401) (e.g. MAC layer) may inform the upper layer(s) (e.g. service layer or application layer) about the at least one event comprising of MBS data session suspension / stopping, MBS data session resumption / starting when one of SDT procedure is initiated, SDT procedure is ongoing, SDT procedure is successfully completed or SDT procedure is unsuccessfully completed and UE is configured / capable and / or interested or receiving broadcast session and / or multicast session in the RRC_INACTIVE state.

[0186] FIG. 5 is a flow chart that illustrates a method for handling Multicast Broadcast Service (MBS) in a telecommunication network system, according to embodiments as disclosed herein.

[0187] At block 501, the MBS controller (409) receives at least one of a MBS broadcast SIB, MCCH, MBS broadcast session data over MTCH, the MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH from the network apparatus when the UE (401) is in an inactive state.

[0188] At block 503, the MBS controller (409) determines whether the SDT procedure is at least one of initiated and ongoing at the UE (401).

[0189] At block 505, the MBS controller (409) determines whether one or more conditions for concurrent operations of unicast and MBS are met. The one or more conditions includes determining whether the UE (401) has capability of receiving at least one of MBS broadcast and MBS multicast along with unicast. Also, determining whether beams for the at least one of MBS broadcast and MBS multicast are quasi-co located (QCL) with the unicast beams. The concurrent operation of at least one of MBS broadcast and MBS multicast along with unicast may also imply at least one of Time-Division Multiplexed (TDM) and Frequency-Division Multiplexed (FDM) reception operations between at least one of MBS broadcast and MBS multicast and the unicast.

[0190] At block 507, the MBS controller (409) suspends or stops reception at least one of the MBS broadcast SIB, MCCH, MBS broadcast session data over MTCH, the MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH from the network apparatus, when the SDT procedure is at least one of initiated and ongoing at the UE (401) and one or more conditions for concurrent operations of unicast and MBS are not met.

[0191] At block 509, the MBS controller (409) suspends monitoring for a downlink channel associated with at least one of the MBS broadcast session data and the MBS multicast session data from a network apparatus.

[0192] At block 511, the MBS controller (409) continues the reception of at least one of a MBS broadcast SIB, MCCH, MBS broadcast session data over MTCH, the MBS multicast SIB, multicast MCCH, and MBS multicast session data over multicast MTCH.

[0193] At block 513, the MBS controller (409) continues monitoring for a downlink channel associated with at least one of the MBS broadcast session data and the MBS multicast session data from a network apparatus, when the SDT procedure is at least one of initiated and ongoing at the UE (401) and one or more conditions for concurrent operations of unicast and MBS are met.

[0194] The various actions, acts, blocks, steps, or the like in the method is 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 are omitted, added, modified, skipped, or the like without departing from the scope of the proposed method.

[0195] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

[0196] FIG. 6 illustrates a block configuration of a base station according to an embodiment of the disclosure.

[0197] Referring to FIG. 6, the base station includes an RF processor 610, a baseband processor 620, a backhaul communication unit 630, a storage unit 640, and a controller 650.

[0198] The RF processor 610 performs a function, such as signal band change, amplification, etc., for transmitting or receiving a signal through a wireless channel. That is, the RF processor 610 upconverts a baseband signal provided from the baseband processor 620, into an RF band signal, and then transmits the RF band signal through an antenna, and downconverts an RF band signal received through the antenna, into a baseband signal. For example, the RF processor 610 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), and the like. In FIG. 6, only one antenna is illustrated, but the base station may include a plurality of antennas. In addition, the RF processor 610 may include a plurality of RF chains. Moreover, the RF processor 610 may perform beamforming. To perform the beamforming, the RF processor 610 may adjust the phase and size of each of signals transmitted or received through a plurality of antennas or antenna elements. The RF processor 610 may perform a downlink MIMO operation by transmitting at least one layer.

[0199] The baseband processor 620 performs a function of conversion between a baseband signal and a bit stream according to a physical layer specification of a first wireless access technology. For example, when data is transmitted, the baseband processor 620 generates complex symbols by encoding and modulating a transmission bit stream. In addition, when data is received, the baseband processor 620 reconstructs a reception bit stream by demodulating and decoding a baseband signal provided from the RF processor 610. For example, in a case where an OFDM scheme is applied, when data is transmitted, the baseband processor 620 generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through IFFT calculation and CP insertion. In addition, when data is received, the baseband processor 620 divides a baseband signal provided from the RF processor 610, by the units of OFDM symbols, reconstructs signals mapped to subcarriers, through FFT calculation, and then reconstructs a reception bit stream through demodulation and decoding. The baseband processor 620 and the RF processor 610 transmit and receive a signal as described above. Accordingly, the baseband processor 620 and the RF processor 610 may be called a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0200] The backhaul communication unit 630 provides an interface for performing communication with other nodes within a network.

[0201] The storage unit 640 stores data such as a basic program, an application program, and configuration information for an operation of the base station. Particularly, the storage unit 640 may store information relating to a bearer assigned to a connected terminal, a measurement result reported from a connected terminal, etc. In addition, the storage unit 640 may store information serving as a determination criterion of whether to provide or stop providing multi-connection to a terminal. Then, the storage unit 640 provides stored data in response to a request of the controller 650.

[0202] The controller 650 controls overall operations of the base station. For example, the controller 650 transmits or receives a signal via the baseband processor 620 and the RF processor 610, or via the backhaul communication unit 630. In addition, the controller 650 records and reads data in and from the storage unit 640. To this end, the controller 650 may include at least one processor.

[0203] In the above-described detailed embodiments of the disclosure, an element included in the disclosure is expressed in the singular or the plural according to presented detailed embodiments. However, the singular form or plural form is selected appropriately to the presented situation for the convenience of description, and the disclosure is not limited by elements expressed in the singular or the plural. Therefore, either an element expressed in the plural may also include a single element or an element expressed in the singular may also include multiple elements.

[0204] Although specific embodiments have been described in the detailed description of the disclosure, it will be apparent that various modifications and changes may be made thereto without departing from the scope of the disclosure. Therefore, the scope of the disclosure should not be defined as being limited to the embodiments, but should be defined by the appended claims and equivalents thereof.

Claims

1.A method performed by a terminal in a wireless communication system, the method comprising:receiving, from a base station, measurement configuration information comprising information on at least one measurement object and information on at least one reporting configuration; andin case that configuration associated with a received signal strength indicator (RSSI) measurement reporting is configured in a reporting configuration, performing an RSSI and channel occupancy measurements on a frequency configured by a RSSI measurement timing configuration (RMTC) frequency in a measurement object associated with the reporting configuration.2.The method of claim 1, further comprising:determining whether a report type for the reporting configuration is at least one of a periodical, an event triggered, or a conditional triggered configuration.3.The method of claim 1, further comprising:determining whether a measurement gap configuration is setup or the terminal does not require measurement gaps to perform measurements.4.The method of claim 1,wherein the measurement configuration information is included in a radio resource control (RRC) reconfiguration message.5.A method performed by a base station in a wireless communication system, the method comprising:transmitting, to a terminal, measurement configuration information comprising information on at least one measurement object and information on at least one reporting configuration; andin case that configuration associated with a received signal strength indicator (RSSI) measurement reporting is configured in a reporting configuration, receiving, from the terminal, a measurement report based on an RSSI and channel occupancy measurements on a frequency configured by a RSSI measurement timing configuration (RMTC) frequency in a measurement object associated with the reporting configuration.6.The method of claim 5,wherein a report type for the reporting configuration is at least one of a periodical, an event triggered, or a conditional triggered configuration.7.The method of claim 5,wherein a measurement gap configuration is setup or the terminal does not require measurement gaps to perform measurements.8.The method of claim 5,wherein the measurement configuration information is included in a radio resource control (RRC) reconfiguration message.9.A terminal in a wireless communication system, the terminal comprising:a transceiver; anda controller configured to:receive, from a base station via the transceiver, measurement configuration information comprising information on at least one measurement object and information on at least one reporting configuration, andin case that configuration associated with a received signal strength indicator (RSSI) measurement reporting is configured in a reporting configuration, perform an RSSI and channel occupancy measurements on a frequency configured by a RSSI measurement timing configuration (RMTC) frequency in a measurement object associated with the reporting configuration.10.The terminal of claim 9, wherein the controller is further configured to:determine whether a report type for the reporting configuration is at least one of a periodical, an event triggered, or a conditional triggered configuration.11.The terminal of claim 9, wherein the controller is further configured to:determine whether a measurement gap configuration is setup or the terminal does not require measurement gaps to perform measurements.12.The terminal of claim 9,wherein the measurement configuration information is included in a radio resource control (RRC) reconfiguration message.13.A base station in a wireless communication system, the base station comprising:transmitting, to a terminal, measurement configuration information comprising information on at least one measurement object and information on at least one reporting configuration; andin case that configuration associated with a received signal strength indicator (RSSI) measurement reporting is configured in a reporting configuration, receiving, from the terminal, a measurement report based on an RSSI and channel occupancy measurements on a frequency configured by a RSSI measurement timing configuration (RMTC) frequency in a measurement object associated with the reporting configuration.14.The base station of claim 13,wherein a report type for the reporting configuration is at least one of a periodical, an event triggered, or a conditional triggered configuration, andwherein a measurement gap configuration is setup or the terminal does not require measurement gaps to perform measurements.15.The base station of claim 13,wherein the measurement configuration information is included in a radio resource control (RRC) reconfiguration message

Images