Methods and user equipment for handling DRX operation in a wireless network

IN595797BActive Publication Date: 2026-07-17SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
IN202241014701
Authority / Receiving Office
IN · IN
Patent Type
Patents
Current Assignee / Owner
Filing Date
2022-03-17
Publication Date
2026-07-17
Estimated Expiration
2042-03-17

AI Technical Summary

Technical Problem

Current wireless communication networks face issues with Discontinuous Reception (DRX) operations for New Radio (NR) Multicast Broadcast Service (MBS), leading to early sleep mode activation and packet loss when Hybrid Automatic Repeat Request (HARQ) feedback is disabled or not configured, resulting in unsuccessful multicast transport block decoding.

Method used

Implementing methods for User Equipment (UE) to detect HARQ feedback disablement or unsuccessful decoding, and configuring local timers to track HARQ Round Trip Time (RTT) and Retransmission (ReTx) timers, allowing the UE to stay awake and monitor for potential retransmissions, even after the DRX active time has elapsed, by adding additional timing durations to preconfigured timers or waiting for battery threshold levels.

Benefits of technology

Prevents packet loss and ensures reliable delivery of MBS by keeping the UE awake during potential retransmissions, even when HARQ feedback is not configured, thereby improving power efficiency and reliability of 5G MBS services.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

ABSTRACT METHODS AND WIRELESS NETWORK FOR HANDLING DRX OPERATION IN WIRELESS NETWORK Embodiments herein disclose methods for handling a DRX operation in a wireless network (400) by a UE (200). The method includes detecting an event. The event includes at least one of a HARQ feedback being disabled, a HARQ feedback not being configured, and an unsuccessful multicast TB decoding. Further, the method includes performing an action based on the detected event. In an example, the action includes adding an additional timing duration to at least one preconfigured DRX timer value and staying awake by the UE (200) while the preconfigured timer is running. In another example, the action includes staying awake by the UE in spite of a multicast DRX active time being over and continuing to monitor for potential HARQ retransmission. The method can be used to handle the DRX operation in a power efficient and reliable manner when the UE receives NR MBS delivery of 5G MBS services. FIG. 3
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[001] Embodiments disclosed herein relate to wireless communicationnetworks (or wireless networks), and more particularly to methods and the UserEquipment (UE) for handling Discontinuous reception (DRX) operations forreceiving New Radio (NR) Multicast Broadcast Service (MBS).BACKGROUND

[002] In wireless communication networks, a New Radio MulticastBroadcast Service (NR MBS) can refer to multicast services where intendedcommon contents are targeted to a group of User Equipments (UEs) which havejoined a multicast group in a multicast coverage area. Broadcast services comprisecontents targeted to all the UEs in a broadcast coverage area. The multicastcoverage area or the broadcast coverage area can be one cell or larger cells.

[003] Two delivery methods are utilized by the UE for receiving themulticast services from the wireless network (e.g., a gNB). The gNB delivers MBSdata to the UEs using either Point-to-Point (PTP) delivery or Point-to-Multipoint(PTM) delivery. The PTP delivery is data transmission to a single target UE in theMBS. The PTM delivery is data transmission to multiple target UEs in the MBS.Further, at the UE, a multicast bearer can comprise a common Protocol DataConvergence Protocol (PDCP) entity with the PTP, the PTM or a combination ofPTP and PTM legs or Radio link control (RLC) entities (also termed as MBS splitbearer).

[004] In the wireless communication networks, unicast is traditional datatransmission from a single source to a single target. For the purpose of power savingand efficient scheduling, an unicast reception is associated with a unicastDiscontinuous Reception (DRX) approach. Further, there is a need for the DRXapproach for reception of MBS services on PTM and PTP paths.A session specificDRX configuration is needed for power-effectively receiving multicast servicereception. Unlike a LTE eMBMS (which supported primarily broadcast services),a NR MBS is also targeted to support higher reliability multicast services for whichmechanism for increased reliability; e.g., Hybrid Automatic Repeat Request(HARQ) feedback and retransmissions are needed to ensure recovery of packet lossover a channel. Further, the HARQ feedback can be enabled or disabled by the gNBdynamically depending on channel conditions or service kinds and so on.

[005] If at least one of the HARQ feedback is disabled or the HARQfeedback is not configured for the UE, the gNB can still possibly retransmit the datafor other UEs or perform blind retransmission(s), especially for a cell-edge or apoor coverage UE. A potential issue here is that the UE for which at least one ofthe HARQ feedback is disabled or the HARQ feedback is not configured, will notstart a drx-HARQ-RTT-TimerDL-PTM timer and therefore, the drx15 RetransmissionTimerDL-PTM timer will also not be operated for the UE.Consequently, the Multicast DRX's Active Time may lapse early, and the UE maygo to a sleep mode, in spite of not decoding the multicast transport blocksuccessfully and the UE suffers packet loss. This has been illustrated in FIG. 1.

[006] FIG. 1 illustrating a 3GPP procedure (100) for HARQ feedback andHARQ retransmissions, according to prior arts. At 102, the UE (200) is receivingthe multicast. At 104, the method includes determining whether the UE (200)(explained in FIG. 2) is configured with harqFeedbackEnablerMulticast? Inresponse to determining that the UE (200) is configured with theharqFeedbackEnablerMulticast then, at 106, the method includes determiningwhether the harq-FeedbackEnablerMulticast is set to enabled or harqFeedbackEnablerMulticast is set to dci-enabler and HARQ feedback is indicated asenabled by the DCI (e.g. the DCI 4_2 can include a field to indicate whether HARQfeedback is enabled or disabled. While DCI 4_1 when scheduled implies thatHARQ feedback is enabled) ?

[007] In response to determining that the UE (200) is not configured withthe harqFeedbackEnablerMulticast or the harq-FeedbackEnablerMulticast is not setto enabled or harq-FeedbackEnablerMulticast is not set to dci-enabler and / or theHARQ feedback is not indicated as enabled by the DCI (i.e. it is disabled) then, at108, the UE (200) provides no HARQ feedback and the UE (200) does not startRTT and ReTx timer. At 110, the UE (200) goes to the sleep mode when an on5 Duration timer and an inactivity timer expires in spite of multicast TB not decodedsuccessfully.

[008] In response to determining that the harq-FeedbackEnablerMulticast isset to enabled or harq-FeedbackEnablerMulticast is set to dci-enabler and theHARQ feedback is indicated as enabled by the DCI then, at 112, the UE (200)provides the HARQ feedback and the UE (200) starts RTT after HARQ feedbacktransmission and ReTx timer upon RTT timer expiry with multicast TB decode notsuccessful.

[009] At 114, the UE (200) stays awake when at least one of on-Durationtimer, an inactivity timer and ReTx timer is running and receives retransmission forthe multicast TB not decoded successfully.

[0010] The issue as noticed at step 110 wherein UE is not able to receivemulticast TB successfully and still it goes to sleep is not addressed by present 3GPPspecification (i.e., Release 17 MBS specifications) and needs a solution to beperformed by the UE implementation and / or network implementation to resolve the20 aforementioned issue and associated drawbacks.OBJECTS

[0011] The principal object of the embodiments herein is to disclosemethods and a wireless network for handling a DRX operation for a UE receivingNew Radio Multicast Broadcast Service (NR MBS).

[0012] Another object of the embodiments herein is to disclose methods andthe wireless network for handling DRX operation for the UE receiving the NRMBS, which supports power efficient and reliable delivery of the 5G MBS services,wherein MBS multicast uses session specific DRX configuration for the powersaving. The UE stays awake and prevent or recovers the potential loss of multicastpacket when the HARQ feedback is not configured and / or not enabled and there isan successful decoding of multicast packet or Transport block (TB).

[0013] Another object of the embodiments herein is to disclose methods andthe wireless network for handling the DRX operation for the UE receiving the NRMBS, in which Radio Resource Control (RRC) layer controls multicast DRXoperation for a PTM per G-RNTI or per Group-Configured Scheduling - RadioNetwork Temporary Identifier (G-CS-RNTI) by configuring a plurality ofparameters and HARQ feedback configuration.SUMMARY

[0014] Accordingly, the embodiments herein provide methods for handlinga Discontinuous Reception (DRX) operation in a wireless network. The methodincludes detecting, by a User Equipment (UE), an event. The event includes at leastone of a hybrid automatic repeat request (HARQ) feedback being disabled, a HARQfeedback not being configured, and an unsuccessful multicast transport block (TB)decoding. Further, the method includes performing, by the UE, at least one actionbased on the detected event.

[0015] In an embodiment, the at least one action includes configuring andrunning at least one local timer to track at least one of a HARQ Round Trip Time(RTT) and a HARQ Retransmission (ReTx) and staying awake by the UE while theat least one local timer is running.

[0016] In another embodiment, the at least one action includes adding anadditional timing duration to at least one preconfigured DRX timer value andstaying awake by the UE while the at least one preconfigured timer is running.

[0017] In an embodiment, the at least one action includes staying awake bythe UE in spite of a multicast DRX active time being over and continuing to monitorfor potential HARQ retransmission.

[0018] In an embodiment, the at least one action includes moving the UE toa sleep mode after clearing a HARQ buffer in which the UE expects a nexttransmission to be a new transmission and considering New Data Indictor (NDI) bitas toggled regardless of an actual value of NDI bit.

[0019] In an embodiment, the at least one action includes staying awake andwaiting for the HARQ retransmissions upon determining a battery level of the UEmeets a predefined threshold battery level.

[0020] In an embodiment, the at least one action includes performing one ofstaying awake or moving the UE to a sleep mode based on a service informationprovided by an application layer associated with the UE or a service layer associatedwith the UE.

[0021] In an embodiment, the at least one local timer is configured perdownlink (DL) HARQ process associated to a multicast service.

[0022] In an embodiment, a value of the at least one local timer is at leastone of: at least one of a configured value for a RTT timer and a configured valuefor a ReTx timer before a HARQ feedback is disabled, a timer value received duringa radio resource control (RRC) configuration, a one or more HARQ retransmissionsduration time, and a maximum value defined for a RTT time or a maximum valuedefined for a ReTx time.

[0023] In an embodiment, the DRX operation is handled, when the UEreceives a New Radio Multicast Broadcast Service (NR MBS).

[0024] Accordingly, the embodiments herein provide methods for handlinga DRX operation in a wireless network. The method includes detecting, by a UE,an event. The event includes at least one of a HARQ feedback being disabled andthe HARQ feedback not being configured. Further, the method includesdetermining, by the UE, a multicast TB decoding is not successful. In anembodiment, the method includes starting a local timer associated with a HARQprocess and continue monitoring a Physical Downlink Control Channel (PDCCH)for at least one retransmission upon determining that the multicast TB decoding wasnot successful. In another embodiment, the method includes stopping the local timerassociated with the HARQ process upon determining that the local timer is running,and the multicast TB decoding is successful.

[0025] In an embodiment, the method further includes determining, by theUE, whether a downlink (DL) data is received with same New Data Indictor (NDI)as compared to previous transmission in the HARQ process in response to continuemonitoring the PDCCH for the at least one retransmission. In an embodiment, themethod includes stopping the local timer associated with the HARQ process upondetermining that the DL data has been received with different NDI as compared toa previous transmission in the HARQ process. In another embodiment, the methodincludes determining whether the multicast TB decoding is successful upondetermining that the DL data has been received with same NDI as compared to aprevious transmission in the HARQ process and stopping the local timer when themulticast TB decoding is determined to be successful or continuing the local timerwhen the multicast TB decoding is determined to be not successful. In anotherembodiment, the method includes determining whether the local timer has expiredupon determining that the DL data has not been received and moving the UE to asleep mode when the local timer is determined to be expired.

[0026] Accordingly, the embodiments herein provide methods for handlinga DRX operation in a wireless network. The method includes detecting, by a UE,an event. The event includes at least one of a HARQ feedback being disabled andthe HARQ feedback not being configured. Further, the method includes identifying,by the UE, at least one metric value and a threshold value that is identified basedon at least one of a measured signal information, a decoding performanceinformation, and a channel quality information, wherein at least one the metricvalue and the threshold value can be at least one of predefined, configured orimplementation determined. Further, the method includes determining, by the UE,the at least one metric value meets a threshold value. In an embodiment, the methodincludes staying awake waiting for a HARQ retransmission when multicast TB isnot successfully decoded, even when multicast DRX Active Time is elapsed upondetermining that the at least one metric value meets the threshold value. In anotherembodiment, the method includes moving to a sleep mode when multicast activetime elapses in spite of a multicast TB is not successfully decoded upon determiningthat the at least one metric value does not meet the threshold value.

[0027] Accordingly, the embodiments herein provide methods for handlinga DRX operation in a wireless network. The method includes detecting, by anetwork entity, an event. The event includes at least one of a HARQ feedback beingdisabled, the HARQ feedback not being configured, and a multicast TB decodingnot being successful. Further, the method includes sending, by the network entity,a message to a UE. The message includes a modified configuration associated witha DRX timer, on detecting the event.

[0028] In an embodiment, detecting the event is based on a parameter. Theparameter comprises at least one of a measurement reporting information, ameasured block error rate information, a State Information (CSI) feedbackinformation, a Sounding Reference Signal (SRS) transmission information, aservice QoS constraint information, a Quality of experience (QoE) reporting andlocation information.

[0029] Accordingly, the embodiments herein provide methods for handlinga DRX operation in a wireless network. The method includes receiving, by anetwork entity, a message from a network device based on an input received fromthe network device. The message indicates whether a MBS HARQ retransmissionis needed for all the UEs or for a sub-set of the UEs or an individual UE. Further,the method includes handling, by the network entity, the DRX operation based onthe received message where handling the DRX operation includes at least one of:configuring a UE for a waiting time for a MBS HARQ retransmission orconfiguring the UE for sending a HARQ feedback.

[0030] In an embodiment, the network entity includes a gNB and thenetwork device comprises at least one of a Network Exposure Function (NEF)entity, an Access and Mobility Management Function (AMF), an User PlaneFunction (UPF) entity, a Multicast Broadcast Single Frequency Network (MBSFN),a gNB and a Multicast Broadcast Session Management Function (MB-SMF). Theinput includes at least one of an experienced packet error rate and an expectedservice quality.

[0031] Accordingly, the embodiments herein provide a UE including aDRX operation controller coupled with a processor and a memory. The DRXoperation controller is configured to detect an event, where the event includes atleast one of a HARQ feedback being disabled, the HARQ feedback not beingconfigured, and an unsuccessful multicast TB decoding. Further, the DRXoperation controller is configured to perform at least one action based on thedetected event.

[0032] Accordingly, the embodiments herein provide a UE including aDRX operation controller coupled with a processor and a memory. The DRXoperation controller is configured to detect an event, where the event includes atleast one of a HARQ feedback being disabled and the HARQ feedback not beingconfigured. Further, the DRX operation controller is configured to determine amulticast TB decoding is not successful. In an embodiment, the DRX operationcontroller is configured to start a local timer associated with a HARQ process andcontinue monitor a PDCCH for at least one HARQ retransmission upondetermining that the multicast TB decoding was not successful. In anotherembodiment, the DRX operation controller is configured to stop the local timerassociated with the HARQ process upon determining that the local timer is running,and the multicast TB decoding is successful.

[0033] In an embodiment, the DRX operation controller is configured todetermine whether a DL data received with same NDI as compared to previoustransmission in the HARQ process in response to continue monitoring the PDCCHfor the at least one retransmission. In an embodiment, the DRX operation controlleris configured to stop the local timer associated with the HARQ process upondetermining that the DL data has been received with different NDI as compared toa previous transmission in the HARQ process. In another embodiment, the DRXoperation controller is configured to determine whether the multicast TB decodingis successful upon determining that the DL data has been received with same NDIas compared to a previous transmission in the HARQ process and stopping the localtimer when the multicast TB decoding is determined to be successful or continuingthe local timer when the multicast TB decoding is determined to be not successful.In another embodiment, the DRX operation controller is configured to determinewhether the local timer has expired upon determining that the DL data has not beenreceived and moving the UE to a sleep mode when the local timer is determined tobe expired.

[0034] Accordingly, the embodiments herein provide a UE including aDRX operation controller coupled with a processor and a memory. The DRXoperation controller is configured to detect an event, where the event includes atleast one of a HARQ feedback being disabled and the HARQ feedback not beingconfigured. Further, the DRX operation controller is configured to identify at leastone of a metric value and a threshold value that is identified based on at least oneof a measured signal information, a decoding performance information, and achannel quality information, wherein at least one of the metric value and thethreshold value can be at least one of predefined, configured or implementationdetermined. Further, the DRX operation controller is configured to determine thatthe at least one metric value meets a threshold value. In an embodiment, the DRXoperation controller is configured to stay awake waiting for a HARQ retransmissionwhen multicast TB is not successfully decoded, even when multicast DRX activetime is elapsed upon determining that the at least one metric value meets thethreshold value. In another embodiment, the DRX operation controller isconfigured to move to a sleep mode when multicast active time elapses in spite ofa multicast TB is not successfully decoded upon determining that the at least onemetric value does not meet the threshold value.

[0035] Accordingly, the embodiments herein provide a network entityincluding a DRX operation controller coupled with a processor and a memory. TheDRX operation controller is configured to detect an event, where the event includesat least one of a HARQ feedback being disabled, the HARQ feedback not beingconfigured, and a multicast TB decoding not being successful. The DRX operationcontroller is configured to send a message to a UE, where the message includes amodified configuration associated with a DRX timer, on detecting the event.

[0036] Accordingly, the embodiments herein provide a network entityincluding a DRX operation controller coupled with a processor and a memory. TheDRX operation controller is configured to receive a message from a network devicebased on an input received from the network device, where the message indicateswhether a MBS HARQ retransmission is needed for all the UEs or for a sub-set ofUEs or an individual UE. Further, the DRX operation controller is configured tohandle the DRX operation based on the received message wherein handle the DRXoperation includes at least one of: configure a UE for a waiting time for a MBSHARQ retransmission or configure the UE for sending a HARQ feedback.

[0037] These and other aspects of the embodiments herein will be betterappreciated and understood when considered in conjunction with the followingdescription and the accompanying drawings. It should be understood, however, thatthe following descriptions, while indicating at least one embodiment and numerousspecific details thereof, are given by way of illustration and not of limitation. Manychanges and modifications may be made within the scope of the embodimentsherein without departing from the spirit thereof, and the embodiments hereininclude all such modifications.BRIEF DESCRIPTION OF FIGURES

[0038] The embodiments disclosed herein are illustrated in theaccompanying drawings, throughout which like reference letters indicatecorresponding parts in the various figures. The embodiments herein will be betterunderstood from the following description with reference to the drawings, in which:

[0039] FIG. 1 illustrating 3GPP procedure for HARQ feedback and HARQretransmissions, according to prior arts;

[0040] FIG. 2 shows a schematic overview of a wireless network forhandling a DRX operation when a UE receives a multicast and broadcast service,according to the embodiments as disclosed herein;

[0041] FIG. 3 shows various hardware components of the UE, according tothe embodiments as disclosed herein;

[0042] FIG. 4 shows various hardware components of a network entity,according to the embodiments as disclosed herein;

[0043] FIG. 5 illustrates an example flow chart of a method for defininglocal timer Txxx while handling the DRX operation, according to embodiments asdisclosed herein;

[0044] FIG. 6 illustrates an example flow chart of a method for operatinglocal timer Txxx while handling the DRX operation, according to embodiments asdisclosed herein;

[0045] FIG. 7 illustrates an example flow chart of a method for receivingHARQ retransmission(s) while handling the DRX operation, according toembodiments as disclosed herein;

[0046] FIG. 8 illustrates an example flow chart of a method, implementedby a network entity, for network providing modified configuration for receivingHARQ retransmission(s) while handling the DRX operation, according toembodiments as disclosed herein; and

[0047] FIG. 9 is a flow chart illustrating a method for handling the DRXoperation in the wireless network, according to embodiments as disclosed herein.DETAILED DESCRIPTION

[0048] The embodiments herein and the various features and advantageousdetails thereof are explained more fully with reference to the non-limitingembodiments that are illustrated in the accompanying drawings and detailed in thefollowing description. Descriptions of well-known components and processingtechniques are omitted so as to not unnecessarily obscure the embodiments herein.The examples used herein are intended merely to facilitate an understanding ofways in which the embodiments herein can be practiced and to further enable thoseof skill in the art to practice the embodiments herein. Accordingly, the examples10 should not be construed as limiting the scope of the embodiments herein.

[0049] The embodiments herein achieve methods for handling a DRXoperation in a wireless network. The method includes detecting, by a UE, an event.The event includes at least one of a HARQ feedback being disabled, a HARQfeedback not being configured, and an unsuccessful multicast TB decoding.Further, the method includes performing, by the UE, at least one action based onthe detected event. The method can be used to handle the DRX operation in a powerefficient and reliable manner when the UE receives 5G MBS services. In theproposed method, the UE can prevent or recover the loss of MBS multicast packetwhen the multicast TB decoding is not successful and the HARQ feedback is notconfigured or not enabled. With no starting of RTT and / or ReTX timer, the UE maynormally go to sleep and loose the multicast packet. In the proposed method, theUE stays awake and avail HARQ retransmission and prevent or recover the loss ofMBS multicast packet.

[0050] Referring now to the drawings, and more particularly to FIGS. 2through 9, where similar reference characters denote corresponding featuresconsistently throughout the figures, there are shown at least one embodiment.

[0051] FIG. 2 shows a schematic overview of a wireless network (400) forhandling a DRX operation when a UE (200) receives a multicast and broadcastservice, according to the embodiments as disclosed herein. The wireless network(400) can be, for example, but not limited to a fourth generation wireless network,a fifth generation wireless network, Open Radio Access Network (ORAN) or thelike. The wireless network (400) includes the UE (200) and a network entity (300).The UE (200) can be, for example, but not limited to a laptop, a smart phone, adesktop computer, a notebook, a Device-to-Device (D2D) device, a vehicle toeverything (V2X) device, a foldable phone, a smart TV, a tablet, a television, aconnected car, an immersive device, and an internet of things (IoT) device. Thenetwork entity (300) can be, for example, but not limited to a gNB, a new radio(NR) base station, a NR transceiver or the like. In the proposed method, a RadioResource Control (RRC) layer controls multicast DRX operation for PTM per GRNTI or per Group-Configured Scheduling - Radio Network Temporary Identifier(G-CS-RNTI) by configuring a plurality of parameters. A parameter from theplurality of parameters are defined as follow:a) drx-onDurationTimerPTM: The duration at a beginning of a DRX cycle.b) drx-SlotOffsetPTM: A delay before starting the drxonDurationTimerPTM.c) drx-InactivityTimerPTM: The duration after a PDCCH occasion inwhich a PDCCH indicates a new DL multicast transmission for aMedium Access Control (MAC) entity.d) drx-LongCycleStartOffsetPTM: A long DRX cycle and drxStartOffsetPTM which defines the subframe where the long DRX cyclee) drx-RetransmissionTimerDL-PTM (per DL HARQ process formulticast MBS): The maximum duration until a DL multicastretransmission is received. Embodiments herein may also refer to it asReTx timer.f) drx-HARQ-RTT-TimerDL-PTM (per DL HARQ process for multicastMBS): The minimum duration before a DL multicast assignment forHARQ retransmission is expected by the MAC entity. Embodimentsherein may also refer to it as RTT timer.g) Active Time is the time period during which the MAC entity monitors aset of allocated RNTIs. The time period which is not Active Time iscalled non-Active Time.h) Multicast DRX Active Time is the time period during which the MACentity monitors a set of allocated group RNTIs, i.e., G-RNTI and G-CSRNTI on group-common PDCCH. Unicast DRX Active Time is the timeperiod during which the MAC entity monitors a set of UE-specificRNTIs, i.e., C-RNTI and CS-RNTI on UE-specific PDCCH.

[0052] The PTP DRX configuration is same as the unicast DRXconfiguration. Further, there is also HARQ based retransmission support forreliability. The UE (200) can be configured and provided NACK only HARQfeedback or ACK-NACK based HARQ feedback. The HARQ feedback can also beenabled or disabled by the UE specific signaling, which can be for reasons such as,Physical Uplink Control Channel (PUCCH) resource limitations. More particularly,the HARQ feedback enable / disable is supported by Downlink Control Information(DCI) or a RRC reconfiguration message. The RRC reconfiguration message canprovide the related configuration as follows:

[0053] harq-FeedbackEnablerMulticast: This indicates whether the UE(200) shall provide HARQ-ACK feedback for MBS multicast. Value dci-enablermeans that whether the UE (200) shall feedback HARQ-ACK for the MBSmulticast is indicated by the DCI (e.g. the DCI 4_2 can include a field to indicatewhether HARQ feedback is enabled or disabled. While DCI 4_1 when scheduledimplies that HARQ feedback is enabled). The value enabled means the UE (200)shall always feedback the HARQ-ACK for the MBS multicast. When the field isabsent, the UE shall not feedback the HARQ-ACK for the multicast (i.e., HARQfeedback is disabled).

[0054] Local timer based implementation: In an embodiment, the UE (200)maintains at least one local timer to track the HARQ Round Trip Time (RTT) and / orHARQ Retransmission(s) (ReTx) for the case when at least one of the HARQfeedback is disabled or the HARQ feedback is not configured and the multicast TBdecoding is not successful. The local timer can be configured per downlink (DL)HARQ process associated to the multicast (i.e., addressed to a transmissionindicated by a G-RNTI or a G-CS-RNTI or a configured downlink assignment forMBS multicast).

[0055] In an embodiment, the UE (200) configures the local timer Txxx inat least one of the following ways (as depicted in FIG. 5):a) Timer Txxx is configured to the same value of as at least one of the configuredvalue for RTT time and the configured value for ReTx timer before the HARQfeedback is disabled or if the RRC configurations are available with the UEb) Timer Txxx value is determined by the UE (200) considering the potential oneor more HARQ retransmissions duration e.g., Timer Txxx value = Max HARQReTx * ReTx timer duration.c) Timer Txxx value is determined by the UE (200) considering the maximumvalue defined for RTT time or the maximum value defined for ReTx time.d) Any combination of configured RTT timer value and / or configured ReTx timervalue.e) Any UE (200) defined or determined value for Txxx timer.

[0056] In another embodiment, referring to FIG. 6, the UE (200) starts thetimer Txxx for the associated HARQ process to consider potential blindretransmission(s), or retransmission(s) for other UEs in the case of multicasttransport block (TB) decoding failure and continues to stay awake, while the timerTxxx is running. The UE (200) monitors PDCCH addressed to relevant multicastG-RNTI or G-CS-RNTI while being awake. If decoding of the MAC TB fails andUE's HARQ feedback is disabled or the HARQ feedback is not configured, the UE(200) starts the time Txxx for the associated HARQ process.

[0057] If a new transmission is received (i.e., New Data Indictor (NDI) bitin PDCCH is toggled as compared to previous transmission and PDCCH isaddressed to the relevant multicast G-RNTI or G-CS-RNTI), the UE (200) stops thetimer Txxx for the associated HARQ process.

[0058] If the retransmission is received (i.e., same NDI as compared toprevious transmission and PDCCH is addressed to the relevant multicast G-RNTIor G-CS-RNTI), the UE (200) receives and decodes the retransmission. If thedecoding of the retransmission is successful, the UE (200) stops the timer Txxx forthe associated HARQ process. If the decoding of the retransmission is notsuccessful, the UE (200) may start or restart Txxx for the associated HARQ process.In an alternative embodiment, if the decoding of the retransmission is notsuccessful, the UE (200) may continue Txxx running for the associated HARQprocess.

[0059] If the timer Txxx expires or is not running (and also other configuredDRX timers are not running, e.g., drx-onDurationTimerPTM timer and drxInactivityTimerPTM timer for the relevant G-RNTI or G-CS-RNTI configuration),the UE (200) goes to the sleep mode, otherwise, the UE (200) continues to beawake.

[0060] In another embodiment, the UE (200) appends an additional timingduration to the configured drx-InactivityTimer-PTM in the case when at least oneof the HARQ feedback is disabled or the HARQ feedback is not configured.

[0061] In another embodiment, the UE (200) appends an additional timingduration to the configured drx-InactivityTimer-PTM in the case, when at least oneof the HARQ feedback is disabled or the HARQ feedback is not configured, andthe UE (200) is not able to decode the multicast transport block successfully.

[0062] In another embodiment, when at least one of the HARQ feedback isdisabled or the HARQ feedback is not configured, the UE (200) stays awake in spiteof the multicast DRX Active time being over, if the decoding of the received MACTB is not successful i.e., the HARQ buffer is not empty. The UE (200) continues tomonitor for potential HARQ retransmission(s). Once the decoding is successful(i.e., the HARQ buffer becomes empty or the UE (200) fails to decode in spite ofmaximum retransmissions received), the UE (200) goes to the DRX sleep.

[0063] In another embodiment, when at least one of the HARQ feedback isdisabled or the HARQ feedback is not configured, and the multicast DRX Activetime is over and if the decoding of the received MAC TB is not successful yet (i.e.,HARQ buffer is not empty), the UE (200) clears the HARQ buffer. The UE (200)expects the next transmission to be a new transmission and consider NDI bit astoggled regardless of the actual value of NDI bit.

[0064] In another embodiment (as depicted in FIG. 7), the UE (200) staysawake waiting for the HARQ retransmissions, when at least one of the HARQfeedback is disabled or the HARQ feedback is not configured and the multicasttransport block decoding is not successful, based on the received signal strength orreceived signal quality (e.g., Signal to Inference and Noise Ratio (SINR) / ReferenceSignal Received Power (RSRP) / Reference Signal Received quality (RSRQ) / Received Signal Strength Indicator (RSSI)) or the measured DL block error rate(BLER) or the channel quality (e.g. Channel quality indicator (CQI), Pre-codingMatric Index (PMI), Rank Indicator (RI)). For example, if the measuredSINR / RSRP / RSRQ / RSSI values or the measured DL block error rate (BLER) orother metric are determined as below certain thresholds, the UE (200) does not goto the sleep mode and monitors PDCCH for HARQ Retransmission(s) for the casewhen at least one of the HARQ feedback is disabled or the HARQ feedback is notconfigured and the multicast transport block decoding is not successful. The UE(200) implementation defines at least one of the metric(s) and the associatedthreshold(s) and accordingly, determines the UE behavior for HARQretransmission(s) reception.

[0065] In an embodiment, the UE (200) stays awake waiting for HARQretransmissions when at least one of the HARQ feedback is disabled or the HARQfeedback is not configured and the multicast transport block decoding is notsuccessful, based on a battery level of the UE (100). If battery level is above acertain threshold, the UE (200) doesn't go to the sleep mode and monitors PDCCHfor HARQ Retransmission(s) for the case when at least one of the HARQ feedbackis disabled or the HARQ feedback is not configured, and the multicast transportblock decoding is not successful.

[0066] In an embodiment, an application layer (or operating system ortelephony framework) or the (MBS) service layer informs the UE (radio) protocolstack on whether to stay awake waiting for the HARQ retransmissions when at leastone of the HARQ feedback is disabled or the HARQ feedback is not configured andthe multicast transport block decoding is not successful or the UE (200) can directlygo to the sleep mode, and / or provides the targeted error rate or signalstrength / quality or quality of service (QoS) (e.g. packet loss rate, packet delaybudget) / quality of experience (QoE) (e.g. application level Mean Opinion Score(MoS) or SINR values for the video quality assessment, jitter, latency, buffering,play-out delay etc.) inputs or other factors governing or guiding whether the UE(200) needs to stay awake for HARQ retransmission. The application layer (oroperating system or telephony framework) can communicate to the UE (200)through ATtention (AT) commands. Further, the afore-mentioned feature orsolution for staying awake for HARQ retransmissions can be applied statically orsemi-statically or dynamically based on the input from the application layer or theservice layer.

[0067] Measurement / CSI based HARQ feedback enabling / disabling: In anembodiment, the network entity (300) considers at least one of the UE (200)measurements reporting (e.g., SINR, RSRP, RSRQ, RSSI), measured block errorrate (BLER), Channel State Information (CSI) feedback (e.g., CQI, PMI, RI),Sounding Reference Signal (SRS) transmission, service QoS constraints, QoEreporting and location information, and accordingly, configures / de-configures orenables / disables the HARQ feedback.

[0068] In an embodiment, the afore-mentioned channel measurementsand / or CSI feedback can be referred, derived, estimated, and predicted based on theunicast measurement reporting and / or CSI feedback / SRS transmission. Thenetwork entity (300) may define threshold value(s) for at least one of the aforementioned factors or parameters in order to determine whether to configure / deconfigure or enable / disable HARQ feedback.

[0069] PTM to PTP delivery mode switch: In an embodiment, the networkentity (300) switches the UE (200) between the PTM delivery mode and the PTPdelivery mode based on reliability need or HARQ feedback configuration. Forexample, if the HARQ feedback is disabled or not configured for the G-RNTI (i.e.for all UEs receiving this G-RNTI), and certain UEs may need more reliability, thenetwork entity (300) switches the UEs from the PTM delivery mode to the PTPdelivery mode.

[0070] Configuration of drx-InactivityTimer-PTM: In an embodiment, thenetwork entity (300) modifies the configuration for the UE (200) (e.g., increasesdrx-InactivityTimer-PTM timer duration) for the UE (200) for which at least one ofthe HARQ feedback is disabled or the HARQ feedback is not configured. This isdepicted in FIG. 8.

[0071] In an embodiment, when the UE (200) is not configured with and / orhaving HARQ disabled, and is running the local timer Txxx to receive aretransmission for a failed decoding of a multicast TB, if the UE (200) receives aPTP retransmission for that TB, the local timer for PTM retransmission is stopped.This helps in reducing power wasted in monitoring for PTM retransmission andalso avoid duplicate reception in case of network retransmitting over the PTP andthe PTM.

[0072] In an embodiment, the UE (200) with at least one of the HARQfeedback disabled or the HARQ feedback not configured, may not monitor orreceive PTP retransmission. The PTP retransmission is UE specific and is tightlycoupled with HARQ feedback provided by the specific UE.

[0073] In an embodiment, the UE (200) may overrule the NDI rule whenUE (200) receives the PTP retransmission for the PTM for which at least one of theHARQ feedback is disabled or is not configured; i.e., consider NDI to be a newtransmission regardless of the NDI value when it is addressed to the C-RNTI andreceived on the HARQ process previously addressed by G-RNTI / G-CS-RNTI.

[0074] In an embodiment, the UE behavior described herein, when at leastone of the HARQ feedback is disabled or the HARQ feedback not configured isdirectly applicable for the UE (200) receiving multicast in RRC_INACTIVE state.This is because the UE (200) is receiving the same PTM transmission as receivedby other UEs in the RRC_CONNECTED state. Accordingly, the UE (200) whichis in RRC_INACTIVE state can potentially receive blind retransmission(s) and / orretransmission(s) for other UEs in RRC_CONNECTED state.

[0075] In an embodiment, when the UE (200) is transitioned fromRRC_CONNECTED state to RRC_INACTIVE state and is receiving multicastservice, at least one of the HARQ feedback is disabled or the HARQ feedback isnot configured. Further, when the UE (200) is transitioned from RRC_INACTIVEstate to RRC_CONNECTED state and is receiving multicast service, at least one ofthe HARQ feedback is enabled or the HARQ feedback is configured.

[0076] In an embodiment, the network entity (300) may configure the UE(200) for waiting for MBS HARQ retransmissions based on the input from at leastone of the plurality of network entities (not shown). The plurality of network entities(not shown) includes Network Exposure Function (NEF) entity, an AMF entity, anUPF entity, a MBSF entity, a gNB and a MB-SMF entity. The network entity (300)indicates to the gNB whether the HARQ retransmissions are needed for all the UEsor for a sub-set of UEs or individual UEs based on the experienced packet error rateand the expected service quality. The gNB may configure the UEs for sendingHARQ feedback based on a threshold of Signal to Interference noise Ratio (SINR) / Reference signal Received Power (RSRP) / Received Signal Received Quality(RSRQ) / Received Signal Strength Indicator (RSSI) / Channel State Indication(CSI ) / Channel Quality Indication (CQI) / Block Error Rate (BLER) etc. and thetype of service using MBS and the availability of uplink resources like Physicaluplink control channel (PUCCH).

[0077] FIG. 3 shows various hardware components of the UE (200),according to the embodiments as disclosed herein. In an embodiment, the UE (200)includes a processor (210), a communicator (220), a memory (230) and a DRXoperation controller (240). The processor (210) is coupled with the communicator(220), the memory (230) and the DRX operation controller (240).

[0078] In an embodiment, the DRX operation controller (240) detects theevent. The event can be, for example, but not limited to the HARQ feedback beingdisabled, the HARQ feedback not being configured, and the unsuccessful multicastTB decoding. Based on the detected event, the DRX operation controller (240)performs one or more action(s).

[0079] In an embodiment, the one or more action(s) includes configuringand running the at least one local timer to track at least one of the HARQ RTT andthe HARQ Retransmission (ReTx) and staying awake by the UE (200) while the atleast one local timer is running. The at least one local timer is configured per DLHARQ process associated to a multicast service. The value of the at least one localtimer is at least one of at least one of a configured value for a RTT timer and aconfigured value for a ReTx timer before the HARQ feedback is disabled, a timervalue received during a RRC configuration, a one or more HARQ retransmissionsduration time, and a maximum value defined for the RTT time or a maximum valuedefined for the ReTx time.

[0080] In another embodiment, the one or more action(s) includes addingthe additional timing duration to at least one preconfigured DRX timer value andstaying awake by the UE (200) while the at least one preconfigured timer is running.

[0081] In another embodiment, the one or more action(s) includes stayingawake by the UE (200) in spite of the multicast DRX active time being over andcontinuing to monitor for potential HARQ retransmission. In another embodiment,the one or more action(s) includes moving the UE (200) to the sleep mode afterclearing the HARQ buffer in which the UE (200) expects the next transmission tobe a new transmission and considering New NDI bit as toggled regardless of anactual value of NDI bit.

[0082] In another embodiment, the one or more action(s) includes stayingawake and waiting for the HARQ retransmissions upon determining the batterylevel of the UE (200) meets a predefined threshold battery level. In anotherembodiment, the one or more action(s) includes performing one of staying awakeor moving the UE (200) to the sleep mode based on the service informationprovided by the application layer associated with the UE (200) or the service layerassociated with the UE (200).

[0083] In another embodiment, the DRX operation controller (240) detectsthe event, where the event can be, for example, but not limited to the HARQfeedback being disabled and the HARQ feedback not being configured. Further, theDRX operation controller (240) determines the multicast TB decoding is notsuccessful. In an embodiment, the DRX operation controller (240) starts the localtimer associated with the HARQ process and continue monitoring the PDCCH forat least one retransmission upon determining that the multicast TB decoding wasnot successful. Alternately, the DRX operation controller (240) stops the local timerassociated with the HARQ process upon determining that the local timer is running,and the multicast TB decoding is successful.

[0084] Further, the DRX operation controller (240) determines whether theDL data is received with same NDI as compared to previous transmission in theHARQ process in response to continue monitoring the PDCCH for theretransmission. In an embodiment, the DRX operation controller (240) stops thelocal timer associated with the HARQ process upon determining that the DL datahas been received with different NDI as compared to the previous transmission inthe HARQ process. In another embodiment, the DRX operation controller (240)determines whether the multicast TB decoding is successful upon determining thatthe DL data has been received with same NDI as compared to a previoustransmission in the HARQ process and stops the local timer when the multicast TBdecoding is determined to be successful or continuing the local timer when themulticast TB decoding is determined to be not successful. In another embodiment,the DRX operation controller (240) determines whether the local timer has expiredupon determining that the DL data has not been received and moving the UE (200)to a sleep mode when the local timer is determined to be expired.

[0085] In an embodiment, the DRX operation controller (240) detects theevent, where the event can be, for example, but not limited to the HARQ feedbackbeing disabled and the HARQ feedback not being configured. Further, the DRXoperation controller (240) identifies the at least one metric value and the thresholdvalue that is identified based on at least one of the measured signal information, thedecoding performance information, and the channel quality information, wherein atleast one the metric and the threshold value can be at least one of predefined,configured or implementation determined. In an embodiment, the DRX operationcontroller (240) determines the at least one metric value meets the threshold value..In an embodiment, the DRX operation controller (240) stays awake waiting for theHARQ retransmission when multicast TB is not successfully decoded, even whenmulticast DRX Active Time is elapsed upon determining that the at least one metricvalue meets the threshold value. In an embodiment, the DRX operation controller(240) moves to a sleep mode when multicast active time elapses in spite of amulticast TB is not successfully decoded upon determining that the at least onemetric value does not meet the threshold value.

[0086] The DRX operation controller (240) is implemented by analogand / or digital circuits such as logic gates, integrated circuits, microprocessors,microcontrollers, memory circuits, passive electronic components, active electroniccomponents, optical components, hardwired circuits and the like, and mayoptionally be driven by firmware.

[0087] Further, the processor (210) is configured to execute instructionsstored in the memory (230) and to perform various processes. The communicator(220) is configured for communicating internally between internal hardwarecomponents and with external devices via one or more networks. The memory (230)also stores instructions to be executed by the processor (210). The memory (230)may include non-volatile storage elements. Examples of such non-volatile storageelements may include magnetic hard discs, optical discs, floppy discs, flashmemories, or forms of electrically programmable memories (EPROM) orelectrically erasable and programmable (EEPROM) memories. In addition, thememory (230) may, in some examples, be considered a non-transitory storagemedium. The term "non-transitory" may indicate that the storage medium is notembodied in a carrier wave or a propagated signal. However, the term "non20 transitory" should not be interpreted that the memory (230) is non-movable. Incertain examples, a non-transitory storage medium may store data that can, overtime, change (e.g., in Random Access Memory (RAM) or cache).

[0088] Although the FIG. 3 shows various hardware components of the UE(200) but it is to be understood that other embodiments are not limited thereon. Inother embodiments, the UE (200) may include less or more number of components.Further, the labels or names of the components are used only for illustrative purposeand does not limit the scope of the invention. One or more components can becombined together to perform same or substantially similar function in the UE(200).

[0089] FIG. 4 shows various hardware components of the network entity(300), according to the embodiments as disclosed herein. The network entity (300)25 / 41can be, for example, but not limited the gNB and a NR base station. In anembodiment, the network entity (300) includes a processor (310), a communicator(320), a memory (330) and a DRX operation controller (340). The processor (310)is coupled with the communicator (320), the memory (330) and the DRX operationcontroller (340).

[0090] In an embodiment, the DRX operation controller (340) detects theevent, where the event can be, for example, but not limited to the HARQ feedbackbeing disabled, the HARQ feedback not being configured, and the multicast TBdecoding not being successful. Detecting the event is based on a parameter, wherethe parameter can be, for example, but not limited to the measurement reportinginformation, the measured block error rate information, the CSI feedbackinformation, the SRS transmission information, the service QoS constraintinformation, and the QoE reporting and location information. On detecting theevent, the DRX operation controller (340) sends the message to the UE (200). Themessage includes the modified configuration associated with the DRX timer.

[0091] In an embodiment, the DRX operation controller (340) receives themessage from the network device (not shown) based on the input received from thenetwork device. The input includes at least one of the experienced packet error rateand the expected service quality. The network device can be, for example, but notlimited to at least one of the NEF entity, the AMF entity, the UPF entity, theMBSFN, the gNB and the MB-SMF entity. The message indicates whether theMBS HARQ retransmission is needed for all the UEs or for the sub-set of the UEsor the individual UE. Based on the received message, the DRX operation controller(340) handles the DRX operation. Handling the DRX operation includes at leastone of: configuring the UE (200) for a waiting time for the MBS HARQretransmission or configuring the UE (200) for sending a HARQ feedback.

[0092] The DRX operation controller (340) is physically implemented byanalog and / or digital circuits such as logic gates, integrated circuits,microprocessors, microcontrollers, memory circuits, passive electroniccomponents, active electronic components, optical components, hardwired circuitsand the like, and may optionally be driven by firmware.

[0093] Further, the processor (310) is configured to execute instructionsstored in the memory (330) and to perform various processes. The communicator(320) is configured for communicating internally between internal hardwarecomponents and with external devices via one or more networks. The memory (330)also stores instructions to be executed by the processor (310). The memory (330)may include non-volatile storage elements. Examples of such non-volatile storageelements may include magnetic hard discs, optical discs, floppy discs, flashmemories, or forms of electrically programmable memories (EPROM) orelectrically erasable and programmable (EEPROM) memories. In addition, thememory (330) may, in some examples, be considered a non-transitory storagemedium. The term "non-transitory" may indicate that the storage medium is notembodied in a carrier wave or a propagated signal. However, the term "nontransitory" should not be interpreted that the memory (330) is non-movable. Incertain examples, a non-transitory storage medium may store data that can, overtime, change (e.g., in Random Access Memory (RAM) or cache).

[0094] Although the FIG. 4 shows various hardware components of thenetwork entity (300) but it is to be understood that other embodiments are notlimited thereon. In other embodiments, the network entity (300) may include lessor more number of components. Further, the labels or names of the components areused only for illustrative purpose and does not limit the scope of the invention. Oneor more components can be combined together to perform same or substantiallysimilar function in the network entity (300).

[0095] FIG. 5 illustrates an example flow chart (500) of a method fordefining the local timer Txxx while handling the DRX operation, according toembodiments as disclosed herein. The operations (502-512) are handled by theDRX operation controller (240).

[0096] At 502, the UE (200) is receiving the multicast and the PDSCHdecode fails. At 504, the method includes determining whether the HARQ feedbackis configured and enabled (i.e. harq-FeedbackEnablerMulticast set to enabled orharqFeedbackEnablerMulticast is set to dci-enabler and HARQ feedback isindicated as enabled by the DCI (e.g. the DCI 4_2 can include a field to indicatewhether HARQ feedback is enabled or disabled. While DCI 4_1 when scheduledimplies that HARQ feedback is enabled)). In response determining that the HARQfeedback is not configured and not enabled then, at 506, the method includesdetermining whether RTT and ReTx timer configuration are available or wereavailable earlier to the HARQ feedback disabling or deconfiguration? In responsedetermining that the HARQ feedback is configured and enabled then, at 508, themethod follows the normal procedure defined in the 3GPP specification (Refer FIG.

[0097] In response to determining that RTT and ReTx timer configurationare available or were available earlier to the HARQ feedback disabling ordeconfiguration then, at 510, the UE (200) determines Txxx as: (option 1: Txxx =configured RTT timer value or configured ReTx timer value, option 2: Txxx = MaxHARQ ReTX * configured ReTx timer value, and option 3: any combination ofconfigured RTT timer value and / or configured ReTX timer value). In response todetermining that RTT and ReTx timer configuration are not available or were notavailable earlier to the HARQ feedback disabling or deconfiguration then, at 512,the UE (200) determines the Txxx as the maximum value defined for RTT time orReTx time.

[0098] FIG. 6 illustrates an example flow chart (600) of a method foroperating the local timer Txxx while handling the DRX operation, according toembodiments as disclosed herein. The operations (602-618) are handled by theDRX operation controller (240).

[0099] At 602, the UE (200) is receiving the multicast. At 604, the methodincludes determining whether the HARQ feedback is configured and enabled (i.e.harq-FeedbackEnablerMulticast is set to enabled or harqFeedbackEnablerMulticastis set to dci-enabler and HARQ feedback is indicated as enabled by the DCI (e.g.the DCI 4_2 can include a field to indicate whether HARQ feedback is enabled ordisabled. While DCI 4_1 when scheduled implies that HARQ feedback isenabled))? Upon determining that the HARQ feedback is configured and enabledthen, at 606, the method follows the normal procedure as defined in the 3GPPspecification (Refer FIG. 1). Upon determining that the HARQ feedback is notconfigured and enabled then, at 608, the method includes determining whether thedecoding of multicast TB fails? Upon determining that the decoding of multicastTB does not fails then, at 610, the method includes stopping the local timer Txxxassociated with the HARQ process if the local timer Txxx is running. Upondetermining that the decoding of multicast TB fails then, at 612, the methodincludes starting the local timer Txxx associated with the HARQ process. At 614,the method includes continue monitoring the PDCCH for retransmission(s).

[00100] At 616, the method includes determining whether the DL data isreceived with same NDI as compared to previous transmission in same HARQprocess? Upon determining that the DL data is not received with same NDI ascompared to previous transmission in same HARQ process then at 618, the methodincludes stopping the local timer Txxx associated with the HARQ process if thelocal timer (Txxx) is running.

[00101] FIG. 7 illustrates an example flow chart (700) of a method forreceiving HARQ retransmission(s) while handling the DRX operation, accordingto embodiments as disclosed herein.

[00102] At 702, the UE (200) is receiving the multicast and at least one ofthe HARQ feedback is disabled or the HARQ feedback is not configured. At 704,the UE (200) applies at least one metric and the threshold value that includes butnot limited to measured signal (e.g., SINR / RSRP / RSRQ / RSSI) and / or decodingperformance (e.g., BLER) and / or channel quality (e.g., CSI, CQI, PMI, RI).

[00103] At 706, the UE (200) determines whether the determined metric isnot meeting the threshold value? In response to determining that the determinedmetric is not meeting the threshold value then, at 708, the UE (200) stays awakewaiting for the HARQ retransmissions when multicast TB is not successfullydecoded, even when multicast Active time is elapse. In response to determining thatthe determined metric is meeting the threshold value then, at 710, the UE (200) goesto the sleep mode when the multicast active time elapses in spite of multicast TB isnot successfully decoded.

[00104] FIG. 8 illustrates an example flow chart (800) of a method,implemented by the network entity (300) while handling the DRX operation, forproviding modified configuration for receiving HARQ retransmission(s), accordingto embodiments as disclosed herein.

[00105] At 802 (predefined step), the UE (200) is receiving the multicast.At 804, the network entity (300) signals the DRX configuration includingdrxInactivityTimer-PTM for the UE (200) when at least one of the HARQ feedbackis enabled or the HARQ feedback is configured. At 806, the method includesdetermining that at least one of the HARQ feedback is disabled or the HARQfeedback is not configured by the network entity (300)? Upon determining that atleast one of the HARQ feedback is disabled or the HARQ feedback is notconfigured by the network entity (300) then, at 808, the network entity (300) signalsthe modified configuration for drxInactivityTimer-PTM for the UE (200) (i.e.,drxInactivityTimer-PTM is increased for the UE (200). Upon determining that atleast one of the HARQ feedback is not disabled or the HARQ feedback isconfigured by the network entity (300) then the operation moves to step 802.

[00106] FIG. 9 is a flow chart (900) illustrating a method for handling theDRX operation in the wireless network (400), according to embodiments asdisclosed herein. The operations (902 and 904) are handled by the DRX operationcontroller (240).

[00107] At 902, the method includes detecting the event. The event includesat least one of the HARQ feedback being disabled, the HARQ feedback not beingconfigured, and the unsuccessful multicast TB decoding. At 904, the methodincludes performing the at least one action based on the detected event. In anembodiment, the at least one action includes configuring and running at least onelocal timer to track at least one of a HARQ RTT and a HARQ Retransmission(ReTx) and staying awake by the UE (200) while the at least one local timer isrunning.

[00108] In another embodiment, the at least one action includes adding anadditional timing duration to at least one preconfigured DRX timer value andstaying awake by the UE (200) while the at least one preconfigured timer is running.In another embodiment, the at least one action includes staying awake by the UE(200) in spite of a multicast DRX active time being over and continuing to monitorfor potential HARQ retransmission.

[00109] In another embodiment, the at least one action includes moving theUE (200) to a sleep mode after clearing a HARQ buffer in which the UE (200)expects a next transmission to be a new transmission and considering New DataIndictor (NDI) bit as toggled regardless of an actual value of NDI bit. In anotherembodiment, the at least one action includes staying awake and waiting for theHARQ retransmissions upon determining a battery level of the UE (200) meets apredefined threshold battery level. In an embodiment, the at least one actionincludes performing one of staying awake or moving the UE (200) to a sleep modebased on a service information provided by an application layer associated with theUE (200) or a service layer associated with the UE (200).

[00110] In an embodiment, the MBS service considered for the describedembodiments of the invention pertains to at least one of the MBS multicast servicewhich is dynamically scheduled over the PDCCH and addressed to the G-RNTI orthe G-CS-RNTI, the MBS multicast service which is semi-persistently scheduledand the MBS multicast service which is provided through configured downlinkmulticast assignment. Further, in an embodiment, the multicast service may be theone which is being received in at least one of the RRC_CONNECTED state and theRRC_INACTIVE state.

[00111] The various actions, acts, blocks, steps, or the like in the flow charts(500-900) may be performed in the order presented, in a different order orsimultaneously. Further, in some embodiments, some of the actions, acts, blocks,steps, or the like may be omitted, added, modified, skipped, or the like withoutdeparting from the scope of the invention.

[00112] The embodiments disclosed herein can be implemented through atleast one software program running on at least one hardware device and performingnetwork management functions to control the elements. The elements can be at leastone of a hardware device, or a combination of hardware device and softwaremodule. The elements can also include inter-module, inter-layer and inter-processorcommunication, interactions across application entities and communication entities,user defined features and functions and memory, storage and database management.

[00113] The foregoing description of the specific embodiments will so fullyreveal the general nature of the embodiments herein that others can, by applyingcurrent knowledge, readily modify and / or adapt for various applications suchspecific embodiments without departing from the generic concept, and, therefore,such adaptations and modifications should and are intended to be comprehendedwithin the meaning and range of equivalents of the disclosed embodiments. It is tobe understood that the phraseology or terminology employed herein is for thepurpose of description and not of limitation. Therefore, while the embodimentsherein have been described in terms of at least one embodiment, those skilled in theart will recognize that the embodiments herein can be practiced with modificationwithin the spirit and scope of the embodiments as described herein.

Claims

1. A method for handling a Discontinuous Reception (DRX) operation in a wireless network (400), comprises: detecting, by a User Equipment (UE) (200), an event, wherein the event comprises at least one of a hybrid automatic repeat request (HARQ) feedback being disabled, a HARQ feedback not being configured, and an unsuccessful multicast transport block (TB) decoding; and performing, by the UE (200), at least one action based on the detected event.

2. The method as claimed in claim 1, wherein the at least one action comprises at least one of: configuring and running at least one local timer to track at least one of a HARQ Round Trip Time (RTT) and a HARQ Retransmission (ReTx) and staying awake by the UE (200) while the at least one local timer is running; adding an additional timing duration to at least one preconfigured DRX timer value and staying awake by the UE (200) while the at least one preconfigured timer is running; staying awake by the UE (200) in spite of a multicast DRX active time being over and continuing to monitor for potential HARQ retransmission; moving the UE (200) to a sleep mode after clearing a HARQ buffer in which the UE (200) expects a next transmission to be a new transmission and considering New Data Indictor (NDI) bit as toggled regardless of an actual value of NDI bit; staying awake and waiting for the HARQ retransmissions upon determining a battery level of the UE (200) meets a predefined threshold battery level; and performing one of staying awake or moving the UE (200) to a sleep mode based on a service information provided by an application layer associated with the UE (200) or a service layer associated with the UE (200).

3. The method as claimed in claim 2, wherein the at least one local timer is configured per downlink (DL) HARQ process associated to a multicast service.

4. The method as claimed in claim 2, wherein a value of the at least one local timer is at least one of: at least one of a configured value for a RTT timer and a configured value for a ReTx timer before a HARQ feedback is disabled; a timer value received during a radio resource control (RRC) configuration; a one or more HARQ retransmissions duration time; and a maximum value defined for a RTT time or a maximum value defined for a ReTx time.

5. The method as claimed in claim 1, wherein the DRX operation is handled, when the UE (200) receives a New Radio Multicast Broadcast Service (NR MBS).

6. A method for handling a Discontinuous Reception (DRX) operation in a wireless network (400), comprises: detecting, by a User Equipment (UE) (200), an event, wherein the event comprises at least one of a HARQ feedback being disabled and the HARQ feedback not being configured; determining, by the UE (200), a multicast transport block (TB) decoding is not successful; and performing, by the UE (200), at least one of: starting a local timer associated with a HARQ process and continue monitoring a Physical Downlink Control Channel (PDCCH) for at least one retransmission upon determining that the multicast TB decoding was not successful; and stopping the local timer associated with the HARQ process upon determining that the local timer is running, and the multicast TB decoding is successful.

7. The method as claimed in claim 6, wherein the method comprises: determining, by the UE (200), whether a downlink (DL) data is received with same New Data Indictor (NDI) as compared to previous transmission in the HARQ process in response to continue monitoring the PDCCH for the at least one retransmission; and performing, by the UE (200), at least one of: stopping the local timer associated with the HARQ process upon determining that the DL data has been received with different NDI as compared to a previous transmission in the HARQ process; determining whether the multicast TB decoding is successful upon determining that the DL data has been received with same NDI as compared to a previous transmission in the HARQ process and stopping the local timer when the multicast TB decoding is determined to be successful or continuing the local timer when the multicast TB decoding is determined to be not successful; and determining whether the local timer has expired upon determining that the DL data has not been received and moving the UE (200) to a sleep mode when the local timer is determined to be expired.

8. A method for handling a Discontinuous Reception (DRX) operation in a wireless network (400), comprises: detecting, by a User Equipment (UE) (200), an event, wherein the event comprises at least one of a HARQ feedback being disabled and the HARQ feedback not being configured; identifying, by the UE (200), at least one metric value and a threshold value based on at least one of a measured signal information, a decoding performance information, and a channel quality information; determining, by the UE (200), the at least one metric value meets the threshold value; and performing, by the UE (200), one of: staying awake waiting for a HARQ retransmission when multicast TB is not successfully decoded, even when multicast DRX Active Time is elapsed upon determining that the at least one metric value meets the threshold value; and moving to a sleep mode when multicast active time elapses in spite of a multicast TB is not successfully decoded upon determining that the at least one metric value does not meet the threshold value.

9. A method for handling a Discontinuous Reception (DRX) operation in a wireless network (400), comprises: detecting, by a network entity (300), an event, wherein the event comprises at least one of a HARQ feedback being disabled, the HARQ feedback not being configured, and a multicast transport block (TB) decoding not being successful; and sending, by the network entity (300), a message to a User Equipment (UE) (200), wherein the message includes a modified configuration associated with a DRX timer, on detecting the event.

10. The method as claimed in claim 9, wherein detecting the event is based on a parameter, wherein the parameter comprises at least one of a measurement reporting information, a measured block error rate information, a State Information (CSI) feedback information, a Sounding Reference Signal (SRS) transmission information, a service QoS constraint information, a Quality of experience (QoE) reporting and location information.

11. A method for handling a Discontinuous Reception (DRX) operation in a wireless network (400), comprises: receiving, by a network entity (300), a message from a network device based on an input received from the network device, wherein the message indicates whether a MBS HARQ retransmission is needed for all the UEs or for a sub-set of the UEs or an individual UE; and handling, by the network entity (300), the DRX operation based on the received message wherein handling the DRX operation includes at least one of: configuring a User Equipment (UE) (200) for a waiting time for a MBS HARQ retransmission or configuring the UE (200) for sending a HARQ feedback.

12. The method as claimed in claim 11, wherein the network entity (300) comprises a gNB and the network device comprises at least one of a Network Exposure Function (NEF) entity, an Access and Mobility Management Function (AMF), an User Plane Function (UPF) entity, a Multicast Broadcast Single Frequency Network (MBSFN), a gNB and a Multicast Broadcast Session Management Function (MB-SMF), and wherein the input comprises at least one of an experienced packet error rate and an expected service quality.

13. A User Equipment (UE) (200), comprising: a processor (210); a memory (230); and a DRX operation controller (240), coupled with the processor (210) and the memory (230), configured to: detect an event, wherein the event comprises at least one of a hybrid automatic repeat request (HARQ) feedback being disabled, the HARQ feedback not being configured, and an unsuccessful multicast transport block (TB) decoding; and perform at least one action based on the detected event.

14. The UE (200) as claimed in claim 13, wherein the at least one action comprises: configuring and running at least one local timer to track at least one of a HARQ Round Trip Time (RTT) and a HARQ Retransmissions (ReTx) and staying awake by the UE (200) while the at least one local timer is running; adding an additional timing duration to at least one preconfigured DRX timer value and staying awake by the UE (200) while the at least one preconfigured timer is running; staying awake by the UE (200) in spite of a multicast DRX active time being over and continuing to monitor for potential HARQ retransmission; moving the UE (200) to a sleep mode after clearing a HARQ buffer in which the UE (200) expects a next transmission to be a new transmission and considering New Data Indictor (NDI) bit as toggled regardless of an actual value of NDI bit; staying awake waiting for the HARQ retransmissions upon determining a battery level of the UE (200) meets a predefined threshold battery level; and performing to one of staying awake or moving the UE (200) to a sleep mode based on a service information provided by an application layer associated with the UE (200) or a service layer associated with the UE (200).

15. A User Equipment (UE) (200), comprising: a processor (210); a memory (230); and a DRX operation controller (240), coupled with the processor (210) and the memory (230), configured to: detect an event, wherein the event comprises at least one of a HARQ feedback being disabled and the HARQ feedback not being configured; determine a multicast transport block (TB) decoding is not successful; and perform at least one of: start a local timer associated with a HARQ process and continue monitor a Physical Downlink Control Channel (PDCCH) for at least one retransmission upon determining that the multicast TB decoding was not successful; and stop the local timer associated with the HARQ process upon determining that the local timer is running, and the multicast TB decoding is successful.

16. The UE (200) as claimed in claim 15, wherein the DRX operation controller (240) is configured to: determine whether a downlink (DL) data received with same New Data Indictor (NDI) as compared to previous transmission in the HARQ process in response to continue monitoring the PDCCH for the at least one retransmission; and perform at least one of: stop the local timer associated with the HARQ process upon determining that the DL data has been received with different NDI as compared to a previous transmission in the HARQ process; determine whether the multicast TB decoding is successful upon determining that the DL data has been received with same NDI as compared to a previous transmission in the HARQ process and stopping the local timer when the multicast TB decoding is determined to be successful or continuing the local timer when the multicast TB decoding is determined to be not successful; and determine whether the local timer has expired upon determining that the DL data has not been received and moving the UE (200) to a sleep mode when the local timer is determined to be expired.

17. A User Equipment (UE) (200), comprising: a processor (210); a memory (230); and a DRX operation controller (240), coupled with the processor (210) and the memory (230), configured to: detect an event, wherein the event comprises at least one of a HARQ feedback being disabled and the HARQ feedback not being configured; identify at least one metric value and a threshold value is identified based on at least one of a measured signal information, a decoding performance information, and a channel quality information, wherein at least one metric and a threshold value can be at least one of predefined, configured or implementation determined; determine the at least one metric value meets a threshold value; and perform one of: stay awake waiting for a HARQ retransmission when multicast TB is not successfully decoded, even when multicast DRX active time is elapsed upon determining that the at least one metric value meets the threshold value; and move to a sleep mode when multicast active time elapses in spite of a multicast TB is not successfully decoded upon determining that the at least one metric value does not meet the threshold value.

18. A network entity (300), comprising: a processor (310); a memory (330); and a DRX operation controller (340), coupled with the processor (310) and the memory (330), configured to: detect an event, wherein the event comprises at least one of a HARQ feedback being disabled, the HARQ feedback not being configured, and a multicast transport block (TB) decoding not being successful; and send a message to a User Equipment (UE) (200), wherein the message includes a modified configuration associated with a DRX timer, on detecting the event.

19. A network entity (300), comprising: a processor (310); a memory (330); and a DRX operation controller (340), coupled with the processor (310) and the memory (330), configured to: receive a message from a network device based on an input received from the network device, wherein the message indicates whether a MBS HARQ retransmission is needed for all the UEs or for a sub-set of UEs or an individual UE; and handle the DRX operation based on the received message wherein handle the DRX operation includes at least one of: configure a User Equipment (UE) (200) for a waiting time for a MBS HARQ retransmission or configure the UE (200) for sending a HARQ feedback.