Method and UE for handling reception of broadcast transmission in wireless network

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments disclosed herein provide method for handling reception of a broadcast transmission. The method includes receiving, by a UE (100), at least one parameter to indicate a configuration of at least one of: a time interleaving, a frequency interleaving and a repetition from a network entity (200). The at least one parameter to indicate the configuration of at least one of: the time interleaving, the frequency interleaving and the repetition is associated with at least one Multimedia Broadcast Multicast Service (MBMS) session for a Physical Multicast Channel (PMCH). The at least one parameter is signaled and configured to the UE (100) in a PMCH configuration provided in a broadcast message. The method includes receiving, by the UE (100), the broadcast transmission based on the at least one parameter.

Description

METHOD AND UE FOR HANDLING RECEPTION OF BROADCAST TRANSMISSION IN WIRELESS NETWORK

[0001] Embodiments disclosed herein relate to a wireless network (e.g., wireless communication networks or the like), and more particularly to systems, a User Equipment (UE) and methods of handling reception of broadcast transmission in the wireless 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] In general, new radio (NR) Multicast and Broadcast Services (MBS) services can refer to multicast services where intended common contents are targeted to a group of User Equipment (UEs) that have joined the multicast services in a multicast coverage area and broadcast services where intended contents may be targeted to all the UEs in a broadcast coverage area. The coverage area can be one radio cell or larger than one radio cell.

[0009] In a legacy system (i.e., Third Generation Partnership Project (3GPP) Release 17 Multicast Broadcast Service (MBS)), for the purpose of informing UEs in a Radio Resource Control (RRC)_IDLE state or RRC_INACTIVE state about multicast session "activation", a group notification or group paging mechanism is utilized. Based on reception of a paging, the UE transits to RRC_CONNECTED state and starts receiving a multicast session. However, there may also be multicast session(s) for the UEs which can be received in the RRC_INACTIVE state (e.g., 3GPP Release 18 MBS considers such scenario). The motivation is to extend the multicast service delivery to RRC_INACTIVE UEs as well is to enhance the capacity of a network entity to serve more number of UEs.

[0010] FIG. 1 depicts a timing diagram that illustrates a potential scenario with acquiring multicast control channel upon reception of group paging by the UE in the RRC_INACTIVE state. In 3GPP technical specification (TS) 38.331 v18.4.0, if the procedure is triggered by the reception of group paging in a paging message, the UE acquires anMBSMulticastConfigurationmessage on a multicast Multicast-Control Channel (MCCH) in the concerned cell at the next repetition period. However, it is possible that the multicast MCCH may not be updated with a Point-to-Multipoint (PTM) configuration for the MBS session for which group paging was received, in a next repetition period. In case, the UE may fail to acquire PTM configuration and would attempt to resume the RRC connection in order to move to the RRC_CONNECTED state. This is problematic as the MBS session was intended to be provided in the RRC_INACTIVE state and the purpose is defeated.

[0011] Further, it can be noted that MCCH modification period has a much larger range of configurable periodicities and the network entity can choose a most appropriate value that can cater to provisioned services requirements. However, it cannot be restricted to exactly same periodicity as that of a paging cycle used in the specific cell. Moreover, range of the paging cycle lengths do not match with that for the MCCH. Otherwise, it leads to drastic impact to network deployment flexibility and service requirements.

[0012] FIG. 1 depicts a scenario for group paging reception and multicast MCCH acquisition. It is clear that as there are many UEs receiving group paging on their Paging Occasions (POs) and in accordance with the present RRC specification, the UEs would attempt to acquire multicast MCCH at their immediate next repetition period. With all the possibilities considered, some of the UEs would definitely fail to acquire updated multicast MCCH information, if the immediate next repetition period does not carry updated MCCH information. Consequently, these UEs would see an absence of PTM configuration on the acquired multicast MCCH message corresponding to the group-paged MBS sessions and in this situation, would be forced to initiate RRC connection resumption. This is drastic and defeats the purpose.

[0013] It is to be noted that multicast MCCH change notification cannot help in this case, as the change notification is generic for any configuration change and the UE cannot deduce anything about the specific PTM configuration update / inclusion.

[0014] It can also be noted that the above discussed problem is not an issue for non-group paging cases (i.e., the UE moves to a different cell providing SIB24 or the UE receivesRRCReleasemessage configuring the UE to receive MBS multicast in RRC_INACTIVE which does not include PTM configuration for at least one multicast session for which the UE is not indicated to stop monitoring the Group Radio Network Temporary Identifier (G-RNTI)) as there is no paging cycle consideration involved and network can suitably provide updated MCCH information for UE's reception.

[0015] Further,the 5G Broadcast (also referred to as Further Evolved Multimedia Broadcast Multicast Service (FeMBMS), Receive-Only-Mode (ROM), LTE based 5G Broadcast or LTE based 5G terrestrial broadcast) is targeted to provide downlink (DL)-only broadcast services to the UEs on a MBMS-dedicated cell with a large coverage area. One typical service use case is Enhanced Television (EnTV) broadcasting through wireless cellular networks. Further, the MBMS-dedicated cells do not support unicast traffic in the downlink, and these cells cannot be used as a Primary Cell (PCell) or a Primary Secondary Cell (PSCell). The system information required to receive MBMS from MBMS-dedicated cells is broadcasted on non-MBSFN sub-frames. The system information change notification as well as Earth-quake Tsunami Warning System (ETWS) / Commercial Mobile alert Service (CMAS) notification are provided via L1 signalling on non-MBSFN subframes.

[0016] In the existing mechanisms (i.e., previous releases of 3GPP LTE specifications), there was no time interleaving for the transport block or Hybrid Automatic Repeat Request (HARQ) operation with repetitions supported and specified for reception of 5G broadcast transmission. However, due to lack of time interleaving or HARQ operations with repetitions, reception of 5G broadcast transmission may not be highly reliable and robust. Therefore, an approach is needed to clearly specify the configuration of the UE for the reception of 5G Broadcast transmission utilizing time interleaving and / or HARQ operation with repetitions.

[0017] It is not yet specified or clear how the UE configuration is signalled to the UE and how the configuration is handled by the UE for the reception of the 5G Broadcast transmission.

[0018] Hence, there is a need in the art for solutions which will overcome the above mentioned drawback(s), among others.

[0019] The principal object of embodiments herein is to disclose systems and methods for receiving of group paging message and acquiring multicast control channel for MBS multicast in RRC_INACTIVE in a wireless network.

[0020] Another object of embodiments herein is to disclose an enhanced UE configuration for the reception of 5G Broadcast transmission in the wireless network.

[0021] Another object of embodiments herein is to provide a time interleaving and / or a frequency interleaving configuration for reception of 5G Broadcast in the wireless network.

[0022] Another object of embodiments herein is to disclose a mechanism for time-interleaved 5G Broadcast transmission including configuration and capability signaling for the PMCH and Time-interleaving and / or Frequency interleaving.

[0023] Another object of embodiments herein is to disclose a configuration for time interleaving and / or frequency interleaving for a specific MTCH for 5G Broadcast while per PMCH configuration is signalled.

[0024] Another object of embodiments herein is to disclose configuration of rate matching and soft buffer parameters for 5G Broadcast.

[0025] Another object of embodiments herein is to disclose signalling UE capability for alpha parameters indicating cyclic shift for code blocks for 5G Broadcast.

[0026] The embodiments herein disclose a method for handling reception of a broadcast transmission. The method includes receiving, by a UE, at least one parameter to indicate a configuration of at least one of: a time interleaving, a frequency interleaving and a repetition from a network entity. The at least one parameter to indicate the configuration of at least one of: the time interleaving, the frequency interleaving and the repetition is associated with at least one Multimedia Broadcast Multicast Service (MBMS) session for a Physical Multicast Channel (PMCH). The at least one parameter is signaled and configured to the UE in a PMCH configuration provided in a broadcast message. The method includes receiving, by the UE, the broadcast transmission based on the at least one parameter.

[0027] The embodiments herein disclose a UE including a broadcast transmission reception controller coupled with a processor and a memory. The broadcast transmission reception controller is configured to receive at least one parameter to indicate a configuration of at least one of: a time interleaving, a frequency interleaving and a repetition from a network entity, wherein the at least one parameter to indicate the configuration of at least one of: the time interleaving, the frequency interleaving and the repetition is associated with at least one MBMS session for a PMCH. The at least one parameter is signaled and configured to the UE in a PMCH configuration provided in a broadcast message. The broadcast transmission reception controller is configured to receive the broadcast transmission based on the at least one parameter.

[0028] In an embodiment, the broadcast transmission is a Long-Term Evolution (LTE) based fifth generation (5G) Broadcast, wherein the broadcast message comprises at least one of: a Multicast Control Channel (MCCH) message and a System Information Block (SIB) message.

[0029] In an embodiment, the at least one MBMS session is last scheduled MBMS session of a Multicast Channel (MCH).

[0030] In an embodiment, an extended set of configurable values for Multicast Channel (MCH) scheduling period is defined and at least one value from the extended set is configured for at least one PMCH for a 5G Broadcast transmission.

[0031] In an embodiment, the extended set comprises at least one of a configurable value for the MCH scheduling period among values rf1, rf2, rf4, rf8, rf16, rf32, rf64, rf128, rf256, rf512, rf1024 and at least one intermediate value without restricting a possible value for configuration of the MCH scheduling period, wherein at least one of: an optimized scheduling for a MBMS session and efficient resource utilization for the 5G Broadcast transmission is configured by the network entity to the UE based on the extended set of configurable values for the MCH scheduling period.

[0032] In an embodiment, the extended set comprises the at least one configurable value is configured by the network entity to the UE.

[0033] In an embodiment, the at least one intermediate value comprises at least one of: rf12, rf24, rf48,rf96, rf192, rf384, and rf768.

[0034] In an embodiment, the at least one parameter for a rate matching for the PMCH is configured to the UE, wherein the at least one parameter comprises at least one of: a number of soft channel bits, a number of soft channel bits according to UE-category, a scaling factor for soft buffer size, a soft buffer size for a transport block, the soft buffer size for a code block, and an alpha parameter, wherein the alpha parameter indicates a cyclic shift for code blocks.

[0035] In an embodiment, the UE informs the network entity with its capability to support at least one of: a rate matching and an associated parameter for a reception of R19 5G Broadcast in a UE capability information message, wherein the associated parameter comprises at least one of: a number of soft channel bits, implicitly indicated number of soft channel bits according to a UE-category, a scaling factor for soft buffer size and an alpha parameter, wherein the alpha parameter indicates a cyclic shift for code blocks.

[0036] In an embodiment, the at least one MBMS session belonging to the PMCH does not apply Time-Frequency Interleaving (TFI) and skips to comprise at least one of: a field, a bit, a bitmap, a flag, an index and a code-point that provides a mapping to at least one TFI configuration among a plurality of TFI configurations, wherein the at least one MBMS session is last scheduled MBMS session of the MCH.

[0037] In an embodiment, a TFI configuration is provided for the PMCH configuration and all MBMS sessions belonging to the PMCH apply the same TFI configuration with or without an explicit indication.

[0038] In an embodiment, at least one MBMS session belonging to the PMCH does not apply a TFI configuration that is provided for an associated PMCH configuration and is indicated by a disabling field, wherein the at least one MBMS session is last scheduled MBMS session of the MCH and wherein disabling is indicated by N parameter being set to 1.

[0039] In an embodiment, at least one configuration of the time interleaving, the frequency interleaving and repetitions among a plurality of TFI configurations provided in a MCCH message is associated to the MBMS session in the PMCH, wherein the at least one MBMS session is last scheduled MBMS session of the MCH.

[0040] In an embodiment, at least one MTCH session comprises at least one of no TFI configuration, no activated configuration and no enabled TFI configuration.

[0041] 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 at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the scope thereof, and the embodiments herein include all such modifications.

[0042] This disclosure provides a method and apparatus for enhancing transmission reliability for MBMS data by applying time-frequency interleaving.

[0043] Embodiments herein 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 following illustratory drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:

[0044] FIG. 1 illustrates a timing diagram that illustrates a potential scenario with acquiring multicast control channel upon reception of group paging by a UE in RRC_INACTIVE state, according to existing arts;

[0045] FIG. 2 illustrates a wireless network for handling reception of a broadcast transmission, according to embodiments as disclosed herein;

[0046] FIG. 3 is a block diagram illustrating a UE, according to embodiments as disclosed herein;

[0047] FIG. 4 is a flow chart illustrating a method for handling reception of a broadcast transmission in the wireless network, according to embodiments as disclosed herein;

[0048] FIG. 5 illustrates an operational flow diagram that illustrates receiving of a group paging message and acquiring multicast control channel by a UE in RRC_INACTIVE state, according to embodiments as disclosed herein;

[0049] FIG. 6 illustrates an operational flow diagram that illustrates receiving of a group paging message and acquiring multicast control channel by a UE in RRC_INACTIVE state, according to embodiments as disclosed herein;

[0050] FIG. 7 illustrates an operational flow diagram that illustrates receiving of a group paging message and acquiring multicast control channel by a UE in RRC_INACTIVE state, according to embodiments as disclosed herein.

[0051] FIG. 8 is a flow diagram that illustrates a method for configuring the UE for the reception of 5G Broadcast transmission(s), according to embodiments as disclosed herein; and

[0052] FIG. 9 illustrates a plurality of message structures for configuring the UE for the reception of 5G Broadcast transmission, according to embodiments as disclosed herein.

[0053] FIG. 10 illustrates a plurality of message structures for configuring the UE for the reception of 5G Broadcast transmission, according to embodiments as disclosed herein.

[0054] FIG. 11 illustrates a plurality of message structures for configuring the UE for the reception of 5G Broadcast transmission, according to embodiments as disclosed herein.

[0055] FIG. 12 illustrates a flow diagram that illustrates a method for configuring the UE with the time and frequency inter-leaver configuration parameters for reception of 5G Broadcast transmission(s), according to embodiments as disclosed herein;

[0056] FIG. 13 illustrates a flow diagram that illustrates a method for configuring the UE with the time and frequency inter-leaver configuration parameters for reception of 5G Broadcast transmission(s), according to embodiments as disclosed herein;

[0057] FIG. 14 illustrates a flow diagram that illustrates a method for configuring the UE with the time and frequency inter-leaver configuration parameters for reception of 5G Broadcast transmission(s), according to embodiments as disclosed herein; and

[0058] FIG. 15 illustrates a flow diagram that illustrates a method for configuring the UE with the time and frequency inter-leaver configuration parameters for reception of 5G Broadcast transmission(s), according to embodiments as disclosed herein.

[0059] The figures illustrate embodiments of the disclosure for purposes of illustration only. One skilled in the art will readily recognize from the following description that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the disclosure described herein.

[0060] 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. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0061] The words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.,", "i.e.," are merely used herein to mean "serving as an example, instance, or illustration. Any embodiment or implementation of the present subject matter described herein using the words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," is not necessarily to be construed as preferred or advantageous over other embodiments.

[0062] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions.　These blocks, which may be 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 may optionally be driven by a firmware. The circuits may, 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 may 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 may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.　Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0063] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts / sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components / modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0064] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components / elements / steps is for the purposes of this description and should not be construed as sequential ordering / placement / occurrence unless specified otherwise.

[0065] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0066] In describing the embodiments, descriptions related to technical contents well-known in the art and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea.

[0067] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0068] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, in describing the disclosure, a detailed description of known functions or constitution incorporated herein will be omitted in the case that it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0069] Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded individually or collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0070] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks (or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0071] As used in embodiments of the disclosure, a "~unit / module" may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word "~unit / module" does not always have a meaning limited to software or hardware. The "~unit / module" may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the "~unit / module" includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the "~unit / module" may be either combined into a smaller number of components and a "~unit / module," or divided into additional components and a "~unit / module." Moreover, the components and "~units / module" may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the "unit / module" may include one or more processors.

[0072] The entirety of the one or more computer programs may be stored in a single memory device, or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0073] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, microprocessors, microcontrollers, digital　signal processors, FPGA, ASIC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like. The one processor or the combination of processors executes instructions that can be stored in a memory, such as the　operating system, in order to control the overall operation of the device.　Also, the one processor or the combination of processors is also capable of executing other processes and programs　resident in the memory, such as processes for the disclosure.

[0074] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0075] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure. Additionally, or alternatively, such software may be a computer program [product] comprising instructions which, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0076] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0077] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0078] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0079] In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0080] In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0081] Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0082] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0083] Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0084] Furthermore, "if condition A and condition B are satisfied," as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0085] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, elements or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0086] Furthermore, the terms "first ~", "second ~", etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0087] Furthermore, even if "first ~" and "second ~" are described in the present disclosure, it may be understood that element(s) referred to by "first ~" and "second ~" may be the same or different. For example, in case of element(s) being information, first information and second information may both be the same information, and, in some cases, are separate and different information.

[0088] In addition, the terms "if ~" and "in case that ~" as used in the disclosure or claims may be interpreted to include the meanings of "when (or upon) ~," "in response to ~," "based on ~," or "according to ~," and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure. If a method step (e.g., transmit a signal) is performed according to the disclosure of the application in connection with one of the above terms (such as "in case that ~" or the like), it may be interpreted to include the meanings (disclosure) of a prior determination that a feature has a specific state "~" (e.g., a bit length is above X), and then perform the method step in response to said determination.

[0089] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0090] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0091] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0092] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0093] The drawings or flowcharts described below illustrate example methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0094] The process of the flowchart may be performed by a device. One or more of the steps of the　flowchart can be implemented by one or more processors / computer programs executing　instructions to perform the noted functions.

[0095] The methods and apparatuses proposed in the embodiments of the present disclosure may be disclosed in connection with drawings disclosing flowcharts to illustrate example methods that may be implemented according to the principles of the present disclosure. Such flowcharts may contain different branches and / or sub-branches. It is understood that the principles of the present disclosure do not only contain the combination of all branches / sub-branches disclosed in the embodiment, but the present disclosure also contains at least one isolated branch / isolated sub-branch, in particular to a single branch / single sub-branch.

[0096] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0097] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0098] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project　(3GPP) technical specifications (TS) or similar technical specifications, e.g., from ETSI, where appropriate.

[0099] Hereinafter, a base station (BS) is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a sNode B (6G base station), a wireless access unit, a BS controller, or a node on a network.

[0100] Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5G base station architectures in which such CU and DU functional splits are implemented.

[0101] A terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a television, a wearable device, a connected car or a Vehicle to anything (V2X) device, an Internet of Things (IoT) device, or any other device / system capable of performing communication functions.

[0102] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a terminal, and an uplink (UL) refers to a radio link through which a terminal transmits a signal to a BS.

[0103] Furthermore, hereinafter, 4th generation (4G) Long Term Evolution (LTE) mobile communication technologies, 5th generation (5G) mobile communication technologies, 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 4G, 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure.

[0104] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) or physical multicast channel (PMCH) refers to a physical channel through which data is transmitted, but the term PDSCH or PMCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel." Further, in the invention description and embodiments, a transport channel multicast channel (MCH) may be interchangeably used in place of a physical multicast channel (PMCH) and vice-versa.

[0105] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), radio resource control (RRC), or medium access control (MAC) control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as Layer 3 (L3) signaling.

[0106] In addition, Layer 1 (L1) signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), downlink control information (DCI), user equipment (UE)-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0107] For example, the physical layer signaling (i.e., L1 signaling) may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0108] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0109] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0110] The embodiments herein achieve systems and methods for receiving of group paging message acquiring multicast control channel (MCCH) for MBS multicast in the RRC_INACTIVE state in a wireless network. In an embodiment, the method provides an approach to acquire the MBSMulticastConfiguration message on multicast MCCH in the concerned cell at the next repetition period and if PTM configuration is not included for multicast session(s) for which TMGI(s) is indicated in the group paging, acquiring the MBSMulticastConfiguration message on multicast MCCH in the concerned cell at the next MCCH Modification Period.

[0111] The principal object of the invention herein is to provide systems and methods for configuring the UE for the reception of 5G Broadcast transmission(s) utilizing time interleaving and / or frequency interleaving and / or HARQ operation with repetitions in the wireless network.

[0112] Another object of embodiments herein is to disclose methods and systems for signaling the UE configuration parameters for the reception of 5G Broadcast transmission utilizing time interleaving and / or frequency interleaving and / or HARQ operation with repetitions.

[0113] Yet another object of embodiments herein is to disclose methods and systems for handling the UE configuration parameters for the reception of 5G Broadcast transmission utilizing time interleaving and / or frequency interleaving and / or HARQ operation with repetitions.

[0114] Embodiments herein provide an enhanced configuration for User Equipments (UEs) for receiving 5G Broadcast transmission(s). Embodiments herein disclose methods and systems for signaling time interleaving and / or frequency interleaving and / or repetitions configuration information to the UEs for the reception of 5G Broadcast transmission(s), where in at least one of time-interleaving and frequency interleaving may be utilized for the transmissions along with repetitions to enhance the transmission reliability.

[0115] The present disclosure provides systems and methods for a Time and Frequency Inter-leaver (TFI) configuration for the reception of 5G Broadcast transmission(s). The principal object of the invention herein is to provide systems and methods for configuring the UE with the time and frequency inter-leaver (TFI) configuration parameters for receiving 5G Broadcast transmission(s) utilizing time interleaving and / or frequency interleaving and / or HARQ operation with repetitions in the wireless networks. Another object of embodiments herein is to disclose methods and systems for signalling to the UE, the time and frequency inter-leaver configuration parameters for the reception of 5G Broadcast transmission.

[0116] Referring now to the drawings, and more particularly to FIGS. 2 through 15, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

[0117] Embodiments herein disclose systems and methods for receiving of group paging message acquiring multicast control channel (MCCH) for MBS multicast in the RRC_INACTIVE state in a wireless network. Embodiments herein disclose an approach to acquire the MBSMulticastConfiguration message on multicast MCCH in the concerned cell at the next repetition period and if PTM configuration is not included for multicast session(s) for which Temporary Mobile Group Identifiers (TMGI(s)) is indicated in the group paging, acquiring the MBSMulticastConfiguration message on multicast MCCH in the concerned cell at the next MCCH Modification Period.

[0118] The method can be used to facilitate inter-operability for the UEs and a network element.

[0119] FIG. 2 illustrates a wireless network (300) for handling reception of a broadcast transmission, according to embodiments as disclosed herein. The wireless network (300) includes a UE (100) and a network entity (200). The network entity (200) can be, for example, but not limited to a gNode B, an eNode B, a Node B, a sNodeB, a wireless access unit, a BS controller, or a node on a network.

[0120] In an embodiment herein, upon reception of GroupPaging in the paging message, the UE (100) acquires multicast MCCH in the next modification period: It is guaranteed that the UE (100) would get updated multicast MCCH information in the next modification period after receiving group paging. However, it may add to latency in some cases, when previous modification period could also carry updated information. An example of the specification for acquiring theMBSMulticastConfigurationmessage on multicast MCCH upon reception of group paging is provided as below:

[0121] Example 1:

[0122] 5.10.2.3Multicast MCCH information acquisition by the UE

[0123] A UE (100) configured to receive an MBS multicast service in RRC_INACTIVE shall:

[0124] 1> if the procedure is triggered by a multicast MCCH information change notification:

[0125] 2> start acquiring theMBSMulticastConfigurationmessage on multicast MCCH in the concerned cell from the slot in which the change notification was received;

[0126] 1> if the UE moves to a different cell providingSIB24;or

[0127] 1> if the UE receivesRRCReleaseconfiguring the UE to receive MBS multicast in RRC_INACTIVE which does not include PTM configuration for at least one multicast session for which the UE is not indicated to stop monitoring the G-RNTI:

[0128] 1> acquire theMBSMulticastConfigurationmessage on multicast MCCH in the concerned cell at the next repetition period.

[0129] 1> if the procedure is triggered by the reception ofGroupPagingin the paging message in 5.3.2.3:

[0130] 2> acquire theMBSMulticastConfigurationmessage on multicast MCCH in the concerned cell at nextmcch-ModificationPeriod.

[0131] In an example, FIG. 6 depicts an operational flow diagram that illustrates receiving of a group paging message and acquiring multicast control channel by the UE (100) in RRC_INACTIVE state. In an embodiment herein, upon reception of GroupPaging in the paging message, the UE (100) acquires multicast MCCH in the immediate next repetition period and if PTM configuration for group-paged session is not included, ensure to acquire multicast MCCH in the next modification period: This approach ensures that UE (100) attempts to avail updated multicast MCCH information (i.e. PTM configuration for the sessions that are group-paged) until the next modification period when it is not provided in the immediate next repetition period. An example of the specification for acquiring theMBSMulticastConfigurationmessage on multicast MCCH upon reception of group paging is provided as below:

[0132] Example 2:

[0133] 5.10.2.3Multicast MCCH information acquisition by the UE

[0134] The UE (100) configured to receive an MBS multicast service in RRC_INACTIVE shall:

[0135] 1> if the procedure is triggered by a multicast MCCH information change notification:

[0136] 2> start acquiring theMBSMulticastConfigurationmessage on multicast MCCH in the concerned cell from the slot in which the change notification was received;

[0137] 1> if the UE moves to a different cell providingSIB24;or

[0138] 1> if the UE receivesRRCReleaseconfiguring the UE to receive MBS multicast in RRC_INACTIVE which does not include PTM configuration for at least one multicast session for which the UE is not indicated to stop monitoring the G-RNTI:

[0139] 2> acquire theMBSMulticastConfigurationmessage on multicast MCCH in the concerned cell at the next repetition period.

[0140] 1> if the procedure is triggered by the reception ofGroupPagingin the paging message in 5.3.2.3:

[0141] 2> acquire the MBSMulticastConfiguration message on multicast MCCH in the concerned cell at the next repetition period and if PTM configuration is not included for multicast session(s) for which TMGI(s) is indicated in pagingGroupList, acquire theMBSMulticastConfigurationmessage on multicast MCCH in the concerned cell at the nextmcch-ModificationPeriod.

[0142] FIG. 7 depicts an operational flow diagram that illustrates receiving of a group paging message and acquiring multicast control channel by the UE (100) in RRC_INACTIVE state. In an embodiment, the network entity (200) first updates MBSMulticastConfiguration message on multicast MCCH with the PTM configuration for the MBS multicast session(s) which is being activated for reception in RRC_INACTIVE state and then sends a group paging to the UE (100) including the TMGI(s) for that MBS multicast session(s). This approach ensures UE (100) definitely receives updated multicast MCCH information when it is group-paged. That is, the UE (100) acquires MBSMulticastConfiguration on multicast MCCH in the concerned cell at the next repetition period. However, there is additional latency and network requirements on the timing of the group paging. An example of the specification for acquiring theMBSMulticastConfigurationmessage on multicast MCCH upon reception of group paging is provided as below:

[0143] Example 3:

[0144] 5.10.2.3Multicast MCCH information acquisition by the UE

[0145] The UE (100) configured to receive an MBS multicast service in RRC_INACTIVE shall:

[0146] 1> if the procedure is triggered by a multicast MCCH information change notification:

[0147] 2> start acquiring theMBSMulticastConfigurationmessage on multicast MCCH in the concerned cell from the slot in which the change notification was received;

[0148] 1> if the UE moves to a different cell providingSIB24;or

[0149] 1> if the procedure is triggered by the reception ofGroupPagingin the paging message in 5.3.2.3; or

[0150] 1> if the UE receivesRRCReleaseconfiguring the UE to receive MBS multicast in RRC_INACTIVE which does not include PTM configuration for at least one multicast session for which the UE is not indicated to stop monitoring the G-RNTI:

[0151] 2> acquire the MBSMulticastConfiguration on multicast MCCH in the concerned cell at the next repetition period.

[0152] Please note the network entity (200) ensures to page the UE (100) only after MBSMulticastConfiguration message on multicast MCCH is updated with the PTM configuration.

[0153] In an embodiment herein, if the UE (100) fails to receive the PTM configuration (pertaining to multicast session(s) for which TMGI(s) is indicated in the group paging) in the MCCH message in the concerned cell in the next repetition period, the UE (100) initiates a RRC connection resume procedure.

[0154] In an embodiment herein, if the UE (100) fails to receive the PTM configuration (pertaining to multicast session(s) for which TMGI(s) is indicated in the group paging) in the MCCH message in the concerned cell in the next modification period, the UE initiates a RRC connection resume procedure.

[0155] Accordingly, the embodiments herein disclose systems and methods for configuring User Equipments (UEs) for receiving 5G Broadcast transmission. Embodiments herein disclose methods and systems for signaling time interleaving and / or frequency interleaving and / or repetitions configuration information for the reception of 5G Broadcast transmission, where in at least one of time-interleaving and frequency interleaving may be utilized for the transmissions along with repetitions to enhance the transmission reliability.

[0156] Embodiments herein disclose systems and methods of configuring the UE (100) for the reception of 5G Broadcast transmission(s) utilizing time interleaving and / or frequency interleaving and / or HARQ operation with repetitions in the wireless networks.

[0157] In an embodiment herein, the Release 19 (R19) version of 5G Broadcast transmission may include at least one of a time interleaving, a frequency interleaving or a combination of time interleaving and frequency interleaving. The time interleaving may involve the repetitions of the different redundancy versions of the one or more transport block(s) in an interleaved pattern across sub-frames. The frequency interleaving may involve the interleaved pattern of sub-carriers within at least one of a symbol, slot and a sub-frame. There may be different modes defined, configured and signaled to indicate a pattern for a time interleaving or a frequency interleaving or a combination of both.

[0158] In an embodiment herein, the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions are signaled to the UEs (100) by the network element (200).

[0159] In an embodiment herein, the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions may be associated with at least one MBMS session for a PMCH. Further, the parameters may be signaled and configured to the UEs as part of the at least one MBMS session configuration in the PMCH configuration provided in the broadcast message (e.g., MCCH message or SIB message).

[0160] In an embodiment herein, the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions may be associated with a specific PMCH. Further, the parameters may be signaled and configured to the UEs as part of the PMCH configuration. Further, the specific PMCH may be Release 19 (R19) PMCH. That is, the one of more of these parameters are not configured for a Pre-Release 19 (Pre-R19) PMCH. Further, the parameters may be signaled and configured to the UEs as part of the at least one PMCH configuration provided in the broadcast message (e.g., MCCH message or SIB message).

[0161] In an embodiment herein, the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions may be associated with a specific PMCH. Further, the parameters may be signaled and configured to the UEs as part of the PMCH configuration, as illustrated in FIG. 9. Further, the specific PMCH may be Release 19 (R19) PMCH. That is, the one of more of these parameters are not configured for a Pre-Release 19 (Pre-R19) PMCH.

[0162] In an embodiment herein, the R19 PMCH is configured with additionally providing the existing PMCH configuration with the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions, if applicable.

[0163] In an embodiment herein, a Pre-R19 UE may access the PMCH associated with additional configuration parameters e.g. Time-frequency interleaving or repetitions (that are not visible in the configuration to Pre-R19 UEs), and may successfully decode the first transmission (i.e. redundancy version 0) but fail to decode the repetitions (i.e. other redundancy versions). However, if all the first transmissions could be successfully decoded, the Pre-R19 UE may also be able to receive Rel-19 5G Broadcast transmission.

[0164] In an embodiment herein, an example message for the PMCH (e.g. R19 PMCH) configuration is provided, wherein the additional parameters are associated to the PMCH, is given as the below table 1.

[0165]

[0166] In an embodiment herein, the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions may be associated with a specific PMCH. The parameters may be signaled and configured to the UEs as part of the PMCH configuration. Further, at least one MTCH belonging to the specific PMCH may be enabled or disabled or activated or deactivated for the time interleaving and / or frequency interleaving and / or repetitions, as illustrated in FIG. 10.

[0167] In an embodiment herein, the enabling or activation of the time interleaving and / or frequency interleaving and / or repetitions for the MTCH is implicitly or explicitly indicated or is by default at the time of configuration or reconfiguration. In another embodiment herein, the enabling or activation of the time interleaving and / or frequency interleaving and / or repetitions for the MTCH is implicitly or explicitly indicated through a MAC CE (e.g., Multicast Scheduling Information (MSI) MAC CE or extended MSI MAC CE).

[0168] In an embodiment herein, the disabling or deactivation of the time interleaving and / or frequency interleaving and / or repetitions for the MTCH is implicitly or explicitly indicated or is by default at the time of configuration or reconfiguration. In another embodiment herein, the disabling or deactivation of the time interleaving and / or frequency interleaving and / or repetitions for the MTCH is implicitly or explicitly indicated through a MAC CE (e.g., MSI MAC CE or extended MSI MAC CE).

[0169] In an embodiment herein, the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions may be associated with a specific MBMS session for a PMCH. Further, the parameters may be signaled and configured to the UEs as part of the at least one MBMS session configuration in the PMCH configuration, as illustrated in FIG. 11.

[0170] In an embodiment herein, the PMCH configuration may comprise at least one of MTCH configuration(s) including the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions and MTCH configuration(s) not including the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions.

[0171] In an embodiment herein, the PMCH configuration may comprise either MTCH configuration(s) including the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions and the MTCH configuration, or MTCH configuration(s) not including the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions.

[0172] In an embodiment herein, an example message for the MBMS session configuration in the PMCH configuration is provided, wherein the one or more parameters of the configuration of the time interleaving and / or frequency interleaving and / or repetitions are associated to the specific MBMS sessions in the PMCH, is given as the below table 2.

[0173]

[0174] In an embodiment, MTCH sessions with the configuration for time-frequency interleaving or repetitions parameters (e.g. MBMS-SessionInfoListExt-r19) may not be visible or accessible to the pre-R19 UEs as the MBMS-SessionInfoListExt-r19 configurations may be encoded with a R19 version of ASN encoding. Accordingly, only R19 UEs get configured for the monitoring and receiving of the MBMS-SessionInfoListExt-r19 utilizing the parameters for the time-frequency interleaving or repetitions. While configurations for legacy MTCH sessions (that are not utilizing the parameters for the time-frequency interleaving or repetitions) are visible and accessible to both pre-R19 UEs and R19 UEs. Accordingly, Pre-R19 UEs (and R19 UEs) get configured for the monitoring and receiving of the legacy MTCH sessions.

[0175] In an embodiment herein, the R19 PMCH is separately configured from the existing PMCH configuration and includes the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions, if applicable.

[0176] In an embodiment herein, the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions may be associated with more than one PMCH and / or with all the PMCHs of the FeMBMS cell.

[0177] In an embodiment herein, separate PMCH(s) may be configured for the R19 UEs, wherein the R19 PMCHs may support at least one of a time interleaving, a frequency interleaving and a combination of time interleaving and frequency interleaving, as compared to the PMCH(s) that may be configured to be also receivable by pre-Rel19 UEs (i.e. R19 UEs may also receive these PMCH(s)) (say, termed as legacy PMCHs), wherein the legacy PMCHs may not support a time interleaving or a frequency interleaving or a combination of time interleaving and frequency interleaving.

[0178] In an embodiment herein, the configurations of the R19 PMCHs are placed after the configuration for the Pre-R19 PMCH configurations in the PMCH-Config message. That is, the implicitly determined (or explicitly assigned) PMCH index for the R19 PMCHs follow the implicitly determined (or explicitly assigned) PMCH index for the Pre-R19 PMCHs. This would facilitate the identification of the PMCHs and / or the scheduling of the PMCHs transmissions e.g. without explicit indication of the index of the PMCH. Further, Pre-R19 UEs would be scheduled and receiving the first set of PMCHs (i.e. Pre-R19 PMCHs) and R19 UEs could be scheduled and receiving also for the first set and second set of PMCHs.

[0179] In an embodiment herein, at least one of legacy PMCHs and R19 PMCHs may be configured to the UEs through a broadcasted RRC signaling (e.g. a system information block (SIB) e.g. SystemInformationBlockType1-MBMS and SystemInformation-MBMS (carrying one or more SIBs like SIB13) and / or a MBMS Control Channel (MCCH)). R19 PMCHs configuration may not be visible or accessible to the pre-R19 UEs as the R19 PMCH configurations may be encoded with a R19 version of ASN encoding. Accordingly, only R19 UEs get configured for the monitoring and receiving of the R19 PMCHs utilizing the parameters for the R19 PMCHs configurations (and / or corresponding MTCH(s) configurations). While legacy PMCHs are visible and accessible to both pre-R19 UEs and R19 UEs. Accordingly, Pre-R19 UEs (and R19 UEs) get configured for the monitoring and receiving of the legacy PMCHs utilizing the parameters for the legacy PMCHs configurations (and / or corresponding MTCH(s) configurations).

[0180] In an embodiment herein, an example message for the R19 PMCH configuration is provided, wherein the extended list for the R19 PMCH is given as the below table 3.

[0181]

[0182] In an embodiment herein, an example message for the MBMS session configuration in the PMCH configuration is provided, wherein the one or more parameters of the configuration of the time interleaving and / or frequency interleaving and / or repetitions are associated to the specific MBMS session(s) in the PMCH, is given as the below table 4.

[0183]

[0184] In an embodiment herein, the parameter "modeTFI" specifies the index to the type of time interleaving and / or frequency interleaving and / or HARQ repetitions. For an example, the value "mode1" may specify that 3 TBs (say, TB0, TB1 and TB2) with 3 redundancy versions (say, RV0, RV1 and RV2) are interleaved so as to have RV0 versions of TB0, TB1 and TB2, followed by RV1 versions of TB0, TB1 and TB2, followed by RV2 versions of TB0, TB1 and TB2 in the ordinal number of multimedia broadcast multicast service single frequency network (MBSFN) sub-frames. The ordinal number of MBSFN sub-frames may be consecutive or non-consecutive sub-frames excluding the sub-frames utilized for non-MBSFN contents (e.g. CAS sub-frames or following non-MBSFN sub-frame(s) configured carrying MIB or SIB) and certain MBSFN sub-frames (e.g., MBSFN sub-frames carrying MSI or extended MSI or MCCH). The approach may be generalized for M number of TBs and N number of redundancy versions.

[0185] In an embodiment herein, for an example, the value "mode2" may specify 3 TBs (say, TB0, TB1 and TB2) with redundancy versions (say, RV0, RV1 and RV2) are interleaved so as to have RV0, RV1 and RV2 versions of TB0, followed by RV0, RV1 and RV2 versions of TB1, followed by RV0, RV1 and RV2 versions of TB2 in the ordinal number of MBSFN sub-frames. The ordinal number of MBSFN sub-frames may be consecutive or non-consecutive sub-frames excluding the sub-frames utilized for non-MBSFN contents (e.g. CAS sub-frames or additional non-MBSFN sub-frames configured carrying MIB or SIB) and certain MBSFN sub-frames (e.g., MBSFN sub-frames carrying MSI or extended MSI or MCCH). The approach may be generalized for M TBs and N redundancy versions.

[0186] In an embodiment herein, the parameter "TimeInterleaving" indicates whether time interleaving is configured / enabled or not configured / disabled. Absence of this parameter may also be interpreted as time interleaving is not configured. When groupTB or M parameter is configured to 1 and numRV or N parameter is configured to 1 may also be interpreted as time interleaving is not configured.

[0187] In an embodiment herein, the parameter "FreqInterleaving" indicates whether frequency interleaving is configured / enabled or not configured / disabled. Absence of this parameter may also be interpreted as time interleaving is not configured.

[0188] In an embodiment herein, the parameter "groupTB" indicates the number of transport blocks that may be grouped together for time-frequency interleaving and / or repetitions. Whether number of grouped transport blocks are interleaved together in ordinal MBSFN subframes followed by their redundancy versions / repetitions or each of the transport block along with their repetitions in the group are interleaved may be at least one of pre-specified or configured. In case it is configured, it may be indicated by at least one parameter e.g. in the PMCH configuration. GroupTB may also be indicated or interpreted as M parameter. GroupTB or M parameter may have a range of configurable values, for example, 1,2, 4, 8,16,32 and at least one value may be configured for a specific MTCH or for a specific PMCH.

[0189] In an embodiment herein, the parameter "numRV" indicates the number of redundancy versions (repetitions) for a transport blocks are scheduled and / or transmitted. The sequence or order of the redundancy versions in the set of possible redundancy versions (repetitions) may be at least one of pre-specified or configured. In case it is configured, it may be indicated by at least one parameter e.g. in the PMCH configuration. numRV may be indicated or interpreted as N parameter. numRV or N parameter may have a range of configurable values, for example, 1,2, 3, 4, 5, 6, 7, 8,16,32 and at least one value may be configured for a specific MTCH or for a specific PMCH.

[0190] In an embodiment herein, the "modeTFI" configuration may be associated with at least one of a frequency interleaver, a frequency offset interleaver, a time interleaver, a time-frequency interleaver, a diagonal time-frequency interleaver and a set of additional related configuration parameters.

[0191] In an embodiment herein, an extended set of configurable values for MCH scheduling period is defined and at least one value from the extended set may be configured for at least one PMCH for the 5G Broadcast transmission. The extended set may include at least one of the configurable values for MCH scheduling period among values rf1, rf2, rf4, rf8, rf16, rf32, rf64, rf128, rf256, rf512, rf1024 and at least one of other intermediate values (e.g., rf12, rf24, rf48,rf96, rf192, rf384, rf768 and so on), without restricting any other possible value for configuration of MCH scheduling period. With extended set of configurable values for MCH scheduling period, embodiments herein enable the network entity (200) to achieve better scheduling for the MBMS sessions and efficient resource utilization for 5G Broadcast transmission.

[0192] In an embodiment herein, one or more parameters for the Frequency Interleaver including but not limited to M and N size of row column interleaver, a row permutation order and an offset of each row. Further, one or more of the parameters may be optionally configured.

[0193] In an embodiment herein, one or more parameters for the Frequency Offset interleaver including but not limited to M and N size of row column interleaver, a row permutation order, an offset of each row, an offset information for each redundancy version and a Rate Matching (RM) offset in circular buffer for each redundancy version. Further, one or more of the parameters may be optionally configured.

[0194] In an embodiment herein, one or more parameters for the Time-Frequency interleaver including but not limited to M and N dimensions of row column interleaver, m and n dimensions of subblock, a row permutation order, an offset while reading. Further, one or more of the parameters may be optionally configured.

[0195] In an embodiment herein, one or more parameters for the Diagonal Time-Frequency Offset interleaver including but not limited to M and N dimensions of row column interleaver, Diagonal permutations order, permutation or offset rule for each diagonal. Further, one or more of the parameters may be optionally configured.

[0196] In an embodiment herein, at least one parameter for the rate matching for the one or more R19 PMCH may be configured to the UE (100) including but not limited to the number of transport blocks, number of redundancy versions, number of repetitions, interleaver length, interleaver depth, number of HARQ processes, number of soft channel bits, number of soft channel bits according to ue-Category, scaling factor for soft buffer, soft buffer size for transport block, soft buffer size for the r-th code block, alpha parameter indicating cyclic shift for code blocks, size of code block, number of code blocks, length of circular buffer for the r-th code block, the total number of bits available for the transmission of one transport block, the number of rows, memory size, and so on.

[0197] In an embodiment herein, at least one of legacy PMCHs and R19 PMCHs may be configured to the UEs through a broadcasted RRC signaling (e.g. a system information block (SIB) and / or a MBMS Control Channel (MCCH)).

[0198] In an embodiment herein, the network entity (200) may indicate its support for R19 5G Broadcast transmission through an indication comprising at least one of a bit or bitmap or index or a flag or a field included in at least one of the MIB (e.g., MasterInformationBlock-MBMS) or SIB (e.g., SystemInformationBlockType1-MBMS and / or SystemInformation-MBMS or SystemInformationBlockType2 or SystemInformationBlockType13) provided in the CAS sub-frame or additional non-MBSFN sub-frames configured after sub-frame which has PBCH (i.e., MIB).

[0199] In an embodiment herein, the UE (100) informs the network entity (200) (e.g. LTE or 5G NR) with its capability to support the Release 19 5G Broadcast transmission feature in the UE capability information message.

[0200] In an embodiment herein, the UE (100) informs the network entity (200) (e.g. LTE or 5G NR) with its capability to support the time interleaving and / or frequency interleaving and / or HARQ operation with repetitions (e.g., termed as pmch-TFI) in the UE capability information message.

[0201] In an embodiment herein, the UE (100) informs the network entity (200) (e.g. LTE or 5G NR) with its capability to support the one or more scaling factors for operating with different modes of time interleaving and / or frequency interleaving and / or HARQ operation with repetitions and / or associated parameters in the UE capability information message.

[0202] In an embodiment herein, the UE (100) informs the network entity (200) (e.g., LTE or 5G NR, either same or different cell than the cell that provides 5G Broadcast transmission) with its capability to support the different modes of time interleaving and / or frequency interleaving and / or HARQ operation with repetitions and / or associated parameters in the UE capability information message. The different modes may include at least one of a frequency interleaver, a frequency offset interleaver, a time interleaver, a time-frequency interleaver, a diagonal time-frequency interleaver and associated parameters may include at least one of interleaver length, interleaver depth, number of HARQ processes, M and N size of row column interleaver, a row permutation order and an offset of each row, an offset information for each redundancy version and a Rate Matching (RM) offset in circular buffer for each redundancy version, m and n dimensions of subblock, a row permutation order, an offset while reading, and so on.

[0203] In an embodiment herein, the UE (100) informs the network entity (200) (e.g., LTE or 5G NR) with its capability to support the rate matching and / or associated parameters for the reception of R19 5G Broadcast in the UE capability information message. The associated parameters may include at least one of number of soft channel bits, implicitly indicated number of soft channel bits according to ue-Category, a scaling factor for soft buffer, soft buffer size for transport block, soft buffer size for the r-th code block, alpha parameter indicating cyclic shift for code blocks, size of code block, number of code blocks, length of circular buffer for the r-th code block, the total number of bits available for the transmission of one transport block, the number of rows, memory size, and so on.

[0204] Accordingly, the embodiments herein provide methods and systems for time and frequency inter-leaver (TFI) configuration for User Equipment (UEs) for receiving 5G Broadcast transmission(s). Embodiments herein disclose methods and systems for signalling time interleaving and / or frequency interleaving configuration information to the UEs for the reception of 5G Broadcast transmission(s), where in at least one of time interleaving and frequency interleaving may be utilized for the transmissions along with repetitions to enhance the transmission reliability.

[0205] In an embodiment herein, at least one Physical Multicast Channel (PMCH) configuration carries a list or a set or a plurality of TFI configurations (e.g. represented bymch-TfiConfigList) as illustrated in FIG. 12, where in each TFI configuration comprises at least one configuration parameter including but not limited to "TimeInterleaving" indicates whether time interleaving is configured / enabled or not configured / disabled, "FreqInterleaving" (indicates whether frequency interleaving is configured / enabled or not configured / disabled), "modeTFI" (specifies the index to the type of time interleaving and / or frequency interleaving), "groupTB" (may also be represented by "M" and indicates the number of transport blocks that may be grouped together for time-frequency interleaving and / or repetitions), "numRV" (may also be represented by "N" and indicates the number of redundancy versions (repetitions) for a transport blocks are scheduled and / or transmitted) and any other associated parameters for time interleaving and / or frequency interleaving and / or rate matching. Each of the TFI configuration among the plurality of TFI configurations, if present, in the PMCH is explicitly assigned an index or implicitly mapped to an index e.g. based on the order of the TFI configuration in the set or the list. Further, at least one MBMS session belonging to the PMCH comprises at least one of a field, a bit, a bitmap, a flag, an index and a code-point that provides a mapping to at least one TFI configuration among the plurality of TFI configurations, if present, in the associated PMCH configuration. For example, an index may provide mapping to the relevant TFI configuration among the plurality of TFI configurations. For example, a bit in the bitmap provides an enabling (e.g. bit set to 1) or disabling (e.g. bit set to 0) and mapping to the relevant TFI configuration among the plurality of TFI configurations based on the order of the bit in the bitmap. The maximum number of TFI configurations (e.g. represented by a termmaxTfiConfig) may be pre-configured by the RRC signalling or specified in the 3GPP specifications. The actual number of TFI configurations that are provided for a PMCH can be less than or equal tomaxTfiConfig.

[0206] In an embodiment, an MBMS session belonging to the PMCH may not apply TFI and skips to comprise at least one of a field, a bit, a bitmap, a flag, an index and a code-point that provides a mapping to at least one TFI configuration among the plurality of TFI configurations.

[0207] In an embodiment, only one TFI configuration is provided for the PMCH configurations and all MBMS sessions belonging to the PMCH apply the same TFI configuration with or without an explicit indication. In an embodiment, at least one MBMS session belonging to the PMCH may not apply the TFI configuration that is provided for the associated PMCH configuration and is indicated by a disabling field.

[0208] In an embodiment, only one TFI configuration is activated among a plurality of TFI configurations provided for the PMCH configuration and all MBMS sessions apply the same activated TFI configuration with or without an explicit indication. In an embodiment, at least one MBMS session may not apply the activated TFI configuration that is provided for the associated PMCH configuration and is indicated by a disabling field.

[0209] In an embodiment herein, an example message for the MBMS session configuration included in the PMCH configuration is provided, wherein the at least one configuration of the time interleaving and / or frequency interleaving and / or repetitions among the plurality of TFI configurations provided for the PMCH configuration is associated to the specific MBMS sessions in the PMCH, is given as the below table 5.

[0210]

[0211]

[0212] In an embodiment, a list or a set or a plurality of TFI configurations (e.g. represented by mch-TfiConfigList) is configured through a Multicast Control Channel (MCCH) message and a sub-set of TFI configurations from this list may be applied / configured for a specific PMCH (or a specific MBSFN Area). The sub-set may also be a null set (with zero elements) and a full set having as many elements as there in the set or list. The sub-set may be represented by a at least one of a field, a bit, a bitmap, a flag, an index and a code-point that provides a mapping to at least one TFI configuration among the plurality of TFI configurations. Further, a specific MBMS session belonging to the PMCH (or PMCH of the specific MBSFN Area) may refer to the sub-set applied / configured for the respective PMCH (or PMCH of the specific MBSFN Area), in accordance with other embodiments described in this invention.

[0213] In an embodiment, a list or a set or a plurality of TFI configurations (e.g. represented by mch-TfiConfigList) is configured through a MCCH message (e.g. as part of MBSFNAreaConfiguration as illustrated in FIG. 13 or separate from the MBSFNAreaConfiguration i.e. commonly for each of the MBSFN area configured as illustrated in FIG. 14). Each of the TFI configuration among the plurality of TFI configurations, if present, in the MCCH message is explicitly assigned an index or implicitly mapped to an index e.g. based on the order of the TFI configuration in the set or the list. Further, at least one MBMS session belonging to a specific PMCH comprises at least one of a field, a bit, a bitmap, a flag, an index and a code-point that provides a mapping to at least one TFI configuration among the plurality of TFI configurations, if present, in the MCCH message. For example, an index may provide mapping to the relevant TFI configuration among the plurality of TFI configurations. For example, a bit in the bitmap provides an enabling (e.g. bit set to 1) or disabling (e.g. bit set to 0) and mapping to the relevant TFI configuration among the plurality of TFI configurations based on the order of the bit in the bitmap. The maximum number of TFI configurations (e.g. represented by a termmaxTfiConfig) may be pre-configured by the RRC signalling or specified in the 3GPP specifications. The actual number of TFI configurations that are provided in the MCCH message can be less than or equal tomaxTfiConfig.

[0214] In an embodiment herein, an example message for the MBMS session configuration is provided, wherein the at least one configuration of the time interleaving and / or frequency interleaving and / or repetitions among the plurality of TFI configurations provided in the MCCH message is associated to the specific MBMS sessions in the PMCH, is given as the below table 6.

[0215]

[0216] In an embodiment herein, at least one Multicast Traffic Channel (MTCH) session (e.g. MBMS-SessionInfo) comprises of at least one TFI configuration wherein at least one TFI configuration comprises at least one configuration parameter including but not limited to "TimeInterleaving" indicates whether time interleaving is configured / enabled or not configured / disabled, "FreqInterleaving" (indicates whether frequency interleaving is configured / enabled or not configured / disabled), "modeTFI" (specifies the index to the type of time interleaving and / or frequency interleaving), "groupTB" (may also be represented by "M" and indicates the number of transport blocks that may be grouped together for time-frequency interleaving and / or repetitions), "numRV" (may also be representd by "N" and indicates the number of redundancy versions (repetitions) for a transport blocks are scheduled and / or transmitted) and any other associated parameters for time interleaving and / or frequency interleaving and / or rate matching. In another embodiment, at least one MTCH session comprises at least one of no TFI configuration, no activated configuration and no enabled TFI configuration. This is illustrated in FIG.15.

[0217] FIG. 3 is a block diagram of the UE (100). The UE (100) can be, for example, but not limited to a smart phone, a gaming device, a smart watch, a laptop, a desktop computer, a notebook, a smart TV, a tablet, a connected car, an immersive device, a virtual reality (VR) device, an augmented reality (AR) device, a mixed reality (MR) device, a Head-mounted display (HMD), a visual see-through (VST) device, a smart ring, a smart band, a foldable phone, or the like.

[0218] The UE (100) includes a processor (110), a communicator (120), a memory (130), and a broadcast transmission reception controller (140). The processor (110) is coupled with the communicator (120), the memory (130), and the broadcast transmission reception controller (140).

[0219] The broadcast transmission reception controller (140) receives the at least one parameter to indicate a configuration of at least one of: the time interleaving, the frequency interleaving and the repetition from the network entity (200), where the at least one parameter to indicate the configuration of at least one of: the time interleaving, the frequency interleaving and the repetition is associated with at least one MBMS session for the PMCH. The at least one parameter is signaled and configured to the UE (100) in the PMCH configuration provided in the broadcast message. In an embodiment, the at least one MBMS session is last scheduled MBMS session of the MCH. The broadcast transmission reception controller (140) receives the broadcast transmission based on the at least one parameter. In an embodiment, the at least one parameter for the rate matching for the PMCH is configured to the UE (100), where the at least one parameter comprises at least one of: the number of soft channel bits, the number of soft channel bits according to UE-category, the scaling factor for soft buffer size, the soft buffer size for the transport block, the soft buffer size for a code block, and the alpha parameter, where the alpha parameter indicates the cyclic shift for code blocks. In an embodiment, the broadcast transmission is the LTE based 5G Broadcast. In an embodiment, the broadcast message includes the MCCH message and the SIB message.

[0220] In an embodiment, the extended set of configurable values for the MCH scheduling period is defined and at least one value from the extended set is configured for at least one PMCH for the 5G Broadcast transmission. In an embodiment, the extended set includes at least one of a configurable value for the MCH scheduling period among values rf1, rf2, rf4, rf8, rf16, rf32, rf64, rf128, rf256, rf512, rf1024 and at least one intermediate value without restricting the possible value for configuration of the MCH scheduling period. The optimized scheduling for the MBMS session and efficient resource utilization for the 5G Broadcast transmission is configured by the network entity (200) to the UE (100) based on the extended set of configurable values for the MCH scheduling period. In an embodiment, the extended set includes the at least one configurable value is configured by the network entity (200) to the UE (100). In an embodiment, the at least one intermediate value comprises at least one of: rf12, rf24, rf48,rf96, rf192, rf384, and rf768.

[0221] In an embodiment, the UE (100) informs the network entity (200) with its capability to support at least one of: a rate matching and an associated parameter for a reception of R19 5G Broadcast in the UE capability information message, wherein the associated parameter comprises at least one of: a number of soft channel bits, implicitly indicated number of soft channel bits according to a UE-category, a scaling factor for soft buffer size and an alpha parameter, wherein the alpha parameter indicates the cyclic shift for code blocks.

[0222] In an embodiment, the at least one MBMS session belonging to the PMCH does not apply Time-Frequency Interleaving (TFI) and skips to comprise at least one of: a field, a bit, a bitmap, a flag, an index and a code-point that provides a mapping to at least one TFI configuration among a plurality of TFI configurations, wherein the at least one MBMS session is last scheduled MBMS session of the MCH.

[0223] In an embodiment, a TFI configuration is provided for the PMCH configuration and all MBMS sessions belonging to the PMCH apply the same TFI configuration with or without an explicit indication.

[0224] In an embodiment, at least one MBMS session belonging to the PMCH does not apply a TFI configuration that is provided for an associated PMCH configuration and is indicated by a disabling field, wherein the at least one MBMS session is last scheduled MBMS session of the MCH and wherein disabling is indicated by N parameter being set to 1.

[0225] In an embodiment, at least one configuration of the time interleaving, the frequency interleaving and repetitions among a plurality of TFI configurations provided in a MCCH message is associated to the MBMS session in the PMCH, wherein the at least one MBMS session is last scheduled MBMS session of the MCH. This implies the last scheduled MBMS session may have same TFI configuration as other scheduled MBMS sessions. This also implies the last scheduled MBMS session may have different TFI configuration as compared to other scheduled MBMS sessions.

[0226] In an embodiment, at least one MTCH session comprises at least one of no TFI configuration, no activated configuration and no enabled TFI configuration.

[0227] FIG. 4 is a flow chart illustrating a method for handling reception of a broadcast transmission according to embodiments as disclosed herein. The operations (402-404) are handled by the broadcast transmission reception controller (140).

[0228] At S402, the method includes receiving the at least one parameter to indicate a configuration of at least one of: a time interleaving, a frequency interleaving and a repetition from the network entity (200). The at least one parameter to indicate the configuration of at least one of: the time interleaving, the frequency interleaving and the repetition is associated with at least one Multimedia Broadcast Multicast Service (MBMS) session for a Physical Multicast Channel (PMCH). The at least one parameter is signaled and configured to the UE (100) in a PMCH configuration provided in a broadcast message. The method includes receiving, by the UE, the broadcast transmission based on the at least one parameter.

[0229] FIG. 5 depicts an operational flow diagram that illustrates receiving of a group paging message and acquiring multicast control channel by the UE (100) in RRC_INACTIVE state, according to embodiments as disclosed herein. The operations (502-504) are handled by the broadcast transmission reception controller (140).

[0230] At 502, the UE (100) is configured to receive multicast in RRC_INACTIVE state and the UE (100) is in RRC_INACTIVE state and the UE (100) received the group paging message including TMGI(s) in the pagingGroupList for one or more multicast session(s) joined by the UE (100). At 504, the UE (100) acquires the MBSMulticastConfiguration message on the multicast MCCH in the concerned cell at next mcch-ModificationPeriod.

[0231] FIG. 6 depicts an operational flow diagram that illustrates receiving of a group paging message and acquiring multicast control channel by the UE (100) in the RRC_INACTIVE state, according to embodiments as disclosed herein. The operations (602-604) are handled by the broadcast transmission reception controller (140).

[0232] At 602, the UE (100) is configured to receive multicast in the RRC_INACTIVE state and the UE (100) is in the RRC_INACTIVE state and the UE (100) received the group paging message including TMGI(s) in the pagingGroupList for one or more multicast session(s) joined by the UE (100). At 604, the UE (100) acquires the MBSMulticastConfiguration message on the multicast MCCH in the concerned cell at the next repetition period. If PTM configuration is not included for multicast session(s) for which TMGI(s) is indicated in pagingGroupList, the UE (100) acquires the MBSMulticastConfiguration message on the multicast MCCH in the concerned cell at the next mcch-ModificationPeriod.

[0233] FIG. 7 depicts an operational flow diagram that illustrates receiving of a group paging message and acquiring multicast control channel by the UE (100) in the RRC_INACTIVE state, according to embodiments as disclosed herein. The operations (704-706) are handled by the broadcast transmission reception controller (140).

[0234] At 702, the network entity (200) first updates MBSMulticastConfiguration message on the multicast MCCH with the PTM configuration and then sends a group paging to the UE (100). At 704, the UE (100) receives the group paging message including TMGI(s) in the pagingGroupList for one or more multicast session(s) joined by the UE (100). At 706, the UE (100) acquires the MBSMulticastConfiguration message on multicast MCCH in the concerned cell at the next repetition period

[0235] FIG. 8 is a flow diagram that illustrates a method for configuring the UE (100) for the reception of 5G Broadcast transmission(s), according to embodiments as disclosed herein. The operations (804-806) are handled by the broadcast transmission reception controller (140).

[0236] At 802, the network entity (200) supports the Pre-R19 5G Broadcast transmission and / or R19 5G Broadcast transmissions and provides associated R19 PMCH configurations to the UE (100) by adding additional configuration parameters relevant only to R19 PMCH over existing Pre-19 PMCH configuration or by extending PMCH list to include new R19 PMCHs in the MCCH message. At 804, the UE (100) receives MCCH message and configures the Pre-R19 PMCHs and / or R19 PMCH accordingly. At 806, the UE (100) receives the Pre-R19 5G Broadcast transmission and / or R19 5G Broadcast transmission.

[0237] FIG. 9 to FIG. 11 illustrate a plurality of message structures for configuring the UE (100) for the reception of 5G Broadcast transmission, according to embodiments as disclosed herein. In an embodiment herein, the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions may be associated with a specific PMCH. Further, the parameters may be signaled and configured to the UEs as part of the PMCH configuration, as illustrated in FIG. 9. In an embodiment herein, the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions may be associated with a specific PMCH. The parameters may be signaled and configured to the UEs as part of the PMCH configuration. Further, at least one MTCH belonging to the specific PMCH may be enabled or disabled or activated or deactivated for the time interleaving and / or frequency interleaving and / or repetitions, as illustrated in FIG. 10.

[0238] In an embodiment herein, the one or more parameters to indicate the configuration of the time interleaving and / or frequency interleaving and / or repetitions may be associated with a specific MBMS session for a PMCH. Further, the parameters may be signaled and configured to the UEs as part of the at least one MBMS session configuration in the PMCH configuration, as illustrated in FIG. 11.

[0239] FIG. 12 illustrates a method for configuring the UE (100) with the time and frequency inter-leaver configuration parameters for reception of 5G Broadcast transmission(s), according to embodiments as disclosed herein.

[0240] In an embodiment herein, at least one Physical Multicast Channel (PMCH) configuration carries a list or a set or a plurality of TFI configurations (e.g. represented bymch-TfiConfigList) as illustrated in FIG. 12 where in each TFI configuration comprises at least one configuration parameter including but not limited to "TimeInterleaving" indicates whether time interleaving is configured / enabled or not configured / disabled, "FreqInterleaving" (indicates whether frequency interleaving is configured / enabled or not configured / disabled), "modeTFI" (specifies the index to the type of time interleaving and / or frequency interleaving), "groupTB" (may also be represented by "M" and indicates the number of transport blocks that may be grouped together for time-frequency interleaving and / or repetitions), "numRV" (may also be representd by "N" and indicates the number of redundancy versions (repetitions) for a transport blocks are scheduled and / or transmitted) and any other associated parameters for time interleaving and / or frequency interleaving and / or rate matching. Each of the TFI configuration among the plurality of TFI configurations, if present, in the PMCH is explicitly assigned an index or implicitly mapped to an index e.g. based on the order of the TFI configuration in the set or the list. Further, at least one MBMS session belonging to the PMCH comprises at least one of a field, a bit, a bitmap, a flag, an index and a code-point that provides a mapping to at least one TFI configuration among the plurality of TFI configurations, if present, in the associated PMCH configuration. For example, an index may provide mapping to the relevant TFI configuration among the plurality of TFI configurations. For example, a bit in the bitmap provides an enabling (e.g. bit set to 1) or disabling (e.g. bit set to 0) and mapping to the relevant TFI configuration among the plurality of TFI configurations based on the order of the bit in the bitmap. The maximum number of TFI configurations (e.g. represented by a termmaxTfiConfig) may be pre-configured by the RRC signalling or specified in the 3GPP specifications. The actual number of TFI configurations that are provided for a PMCH can be less than or equal tomaxTfiConfig.

[0241] FIG. 13 illustrates a method for configuring the UE (100) with the time and frequency inter-leaver configuration parameters for reception of 5G Broadcast transmission(s), according to embodiments as disclosed herein. FIG. 14 illustrates a flow diagram that illustrates a method for configuring the UE (100) with the time and frequency inter-leaver configuration parameters for reception of 5G Broadcast transmission(s), according to embodiments as disclosed herein. In an embodiment, the list or a set or a plurality of TFI configurations (e.g. represented by mch-TfiConfigList) is configured through a MCCH message (e.g. as part of MBSFNAreaConfiguration as illustrated in FIG. 13 or separate from the MBSFNAreaConfiguration i.e. commonly for each of the MBSFN area configured as illustrated in FIG. 14).

[0242] FIG. 15 illustrates a method for configuring the UE (100) with the time and frequency inter-leaver configuration parameters for reception of 5G Broadcast transmission(s), according to embodiments as disclosed herein.

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

[0244] The embodiments disclosed herein describe systems and methods for receiving of group paging message acquiring multicast control channel (MCCH) for MBS multicast in the RRC_INACTIVE state in a wireless network. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile deviceor any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g., using a plurality of CPUs.

[0245] 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 should and 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 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.

Claims

1.A method performed by a base station in a wireless communication system, the method comprising:transmitting, to a user equipment (UE), a multicast control channel (MCCH) message including physical multicast control channel (PMCH) information, the PMCH information including first information on a PMCH configuration and second information on a plurality of multimedia broadcast multicast service (MBMS) sessions, wherein a time - frequency interleaving (TFI) configuration is configured for the PMCH configuration; andtransmitting, to the UE, data for a multicast traffic channel (MTCH) associated with an MBS session among the plurality of MBMS sessions, based on the TFI configuration,wherein the TFI configuration includes at least one parameter applied for the plurality of MBMS sessions, andwherein transport blocks (TBs) for the data with redundancy versions (RVs) are time-interleaved within multimedia broadcast multicast service single frequency network (MBSFN) subframes based on the at least one parameter.2.The method of claim 1,wherein the at least one parameter includes a first parameter for identifying two consecutive TB transmissions for the data within the MBSFN subframes, a second parameter associated with a number of soft channel bits for a UE category, a third parameter associated with a scaling factor for a soft buffer, or a fourth parameter for an alpha value of a cyclic shift, andwherein a sequence of the RVs applied for the TBs is pre-configured.3.The method of claim 2,receiving, from the UE, UE capability information message including information indicating at least one alpha value for the cyclic shift supported by the UE.4.The method of claim 1,wherein information on a multicast channel (MCH) scheduling period is further configured for the PMCH configuration,wherein multicast scheduling information (MSI) for the MTCH is transmitted via a medium access control (MAC) control element (CE) based on the MCH scheduling period, andwherein the second information includes information on a temporary mobile group identity (TMGI), information on session identity (ID) of the MBS session, and information on a logical channel ID for the MTCH.5.A method performed by a user equipment (UE) in a wireless communication system, the method comprising:receiving, from a base station, a multicast control channel (MCCH) message including physical multicast control channel (PMCH) information, the PMCH information including first information on a PMCH configuration and second information on a plurality of multimedia broadcast multicast service (MBMS) sessions, wherein a time - frequency interleaving (TFI) configuration is configured for the PMCH configuration; andreceiving, from the base station, data for a multicast traffic channel (MTCH) associated with an MBS session among the plurality of MBMS sessions, based on the TFI configuration,wherein the TFI configuration includes at least one parameter applied for the plurality of MBMS sessions, andwherein transport blocks (TBs) for the data with redundancy versions (RVs) are time-interleaved within multimedia broadcast multicast service single frequency network (MBSFN) subframes based on the at least one parameter.6.The method of claim 5,wherein the at least one parameter includes a first parameter for identifying two consecutive TB transmissions for the data within the MBSFN subframes, a second parameter associated with a number of soft channel bits for a UE category, a third parameter associated with a scaling factor for a soft buffer, or a fourth parameter for an alpha value of a cyclic shift, andwherein a sequence of the RVs applied for the TBs is pre-configured.7.The method of claim 6,transmitting, to the base station, UE capability information message including information indicating at least one alpha value for the cyclic shift supported by the UE.8.The method of claim 5,wherein information on a multicast channel (MCH) scheduling period is further configured for the PMCH configuration,wherein multicast scheduling information (MSI) for the MTCH is received via a medium access control (MAC) control element (CE) based on the MCH scheduling period, andwherein the second information includes information on a temporary mobile group identity (TMGI), information on session identity (ID) of the MBS session, and information on a logical channel ID for the MTCH.9.A base station in a wireless communication system, the base station comprising:a transceiver; anda controller configured to:transmit, to a user equipment (UE) via the transceiver, a multicast control channel (MCCH) message including physical multicast control channel (PMCH) information, the PMCH information including first information on a PMCH configuration and second information on a plurality of multimedia broadcast multicast service (MBMS) sessions, wherein a time - frequency interleaving (TFI) configuration is configured for the PMCH configuration, andtransmit, to the UE via the transceiver, data for a multicast traffic channel (MTCH) associated with an MBS session among the plurality of MBMS sessions, based on the TFI configuration,wherein the TFI configuration includes at least one parameter applied for the plurality of MBMS sessions, andwherein transport blocks (TBs) for the data with redundancy versions (RVs) are time-interleaved within multimedia broadcast multicast service single frequency network (MBSFN) subframes based on the at least one parameter.10.The base station of claim 9,wherein the at least one parameter includes a first parameter for identifying two consecutive TB transmissions for the data within the MBSFN subframes, a second parameter associated with a number of soft channel bits for a UE category, a third parameter associated with a scaling factor for a soft buffer, or a fourth parameter for an alpha value of a cyclic shift, andwherein a sequence of the RVs applied for the TBs is pre-configured.11.The base station of claim 10, wherein the controller is further configured to:receive, from the UE via the transceiver, UE capability information message including information indicating at least one alpha value for the cyclic shift supported by the UE.12.The base station of claim 9,wherein information on a multicast channel (MCH) scheduling period is further configured for the PMCH configuration,wherein multicast scheduling information (MSI) for the MTCH is transmitted via a medium access control (MAC) control element (CE) based on the MCH scheduling period, andwherein the second information includes information on a temporary mobile group identity (TMGI), information on session identity (ID) of the MBS session, and information on a logical channel ID for the MTCH.13.A user equipment (UE) in a wireless communication system, the UE comprising:a transceiver; anda controller configured to:receive, from a base station via the transceiver, a multicast control channel (MCCH) message including physical multicast control channel (PMCH) information, the PMCH information including first information on a PMCH configuration and second information on a plurality of multimedia broadcast multicast service (MBMS) sessions, wherein a time - frequency interleaving (TFI) configuration is configured for the PMCH configuration, andreceive, from the base station via the transceiver, data for a multicast traffic channel (MTCH) associated with an MBS session among the plurality of MBMS sessions, based on the TFI configuration,wherein the TFI configuration includes at least one parameter applied for the plurality of MBMS sessions, andwherein transport blocks (TBs) for the data with redundancy versions (RVs) are time-interleaved within multimedia broadcast multicast service single frequency network (MBSFN) subframes based on the at least one parameter.14.The UE of claim 13,wherein the at least one parameter includes a first parameter for identifying two consecutive TB transmissions for the data within the MBSFN subframes, a second parameter associated with a number of soft channel bits for a UE category, a third parameter associated with a scaling factor for a soft buffer, or a fourth parameter for an alpha value of a cyclic shift,wherein a sequence of the RVs applied for the TBs is pre-configured, andwherein the controller is further configured to transmit, to the base station via the transceiver, UE capability information message including information indicating at least one alpha value for the cyclic shift supported by the UE.15.The UE of claim 13,wherein information on a multicast channel (MCH) scheduling period is further configured for the PMCH configuration,wherein multicast scheduling information (MSI) for the MTCH is received via a medium access control (MAC) control element (CE) based on the MCH scheduling period, andwherein the second information includes information on a temporary mobile group identity (TMGI), information on session identity (ID) of the MBS session, and information on a logical channel ID for the MTCH.

Images