Patent Description:
Efforts have been made to develop an improved 5th generation (<NUM>) communication system or pre-<NUM> communication system to keep up with growing wireless data traffic demand after the commercialization of 4th generation (<NUM>) communication systems. For this reason, the <NUM> or pre-<NUM> communication system is called a beyond <NUM> network communication system or a post long-term evolution (LTE) system. Implementation of <NUM> communication systems in an ultra-high frequency (millimeter-wave (mmWave)) band (such as a <NUM>-GHz band) is under consideration to achieve high data transfer rates. To mitigate path loss of radio waves and increase transmission distance of radio waves in an ultra-high frequency band for <NUM> communication systems, technologies such as beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antennas are being studied. Furthermore, to improve system networks for <NUM> communication systems, various technologies including evolved small cells, advanced small cells, cloud radio access network (Cloud-RAN), ultra-dense networks, device to device (D2D) communication, wireless backhaul, moving networks, cooperative communication, coordinated multi-points (CoMP), and received-interference cancellation are currently being developed. In addition, for <NUM> systems, advanced coding modulation (ACM) schemes, such as Hybrid FSK and QAM Modulation (FQAM) and Sliding Window Superposition Coding (SWSC), and advanced access techniques, such as Filter Bank Multicarrier (FBMC), non-orthogonal multiple access (NOMA), sparse code multiple access (SCMA), etc. are being developed.

Moreover, the Internet has evolved from a human-centered connection network, in which humans create and consume information, to the Internet of things (IoT) network in which dispersed components such as objects exchange information with one another to process the information. Internet of Everything (IoE) technology has emerged, in which the loT technology is combined with, for example, technology for processing big data through connection with a cloud server. To implement the loT, technologies such as a sensing technology, a wired/wireless communication and network infrastructure, a service interface technology, and a security technology are required, and thus, research has recently been conducted into technologies such as sensor networks for interconnecting objects, machine to machine (M2M) communication, and machine type communication (MTC). In an IoT environment, intelligent Internet technology services may be provided to create new values for human life by collecting and analyzing data obtained from interconnected objects. The loT may be applied to various fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, a smart grid, healthcare, smart home appliances, advanced medical services, etc., through convergence and integration between existing information technology (IT) and various industries.

Thus, various attempts are being made to apply a <NUM> communication system to the loT network. For example, technologies such as sensor networks, M2M communication, MTC, etc., are implemented using <NUM> communication techniques such as beamforming, MIMO, array antennas, etc. The application of a cloud RAN as the above-described big data processing technology may be an example of convergence between the <NUM> and IoT technologies.

As various services may be provided with the advancements in mobile communication systems as described above, in particular, a method of efficiently providing a multicast and broadcast service (MBS) service is required.

Document <NPL>, includes some general discussions on UE interpretation of the DCI fields in BWP switching DCI, UE behavior/assumption on SRS transmission, CSI report and quasi-colocation for DCl/timer-based active BWP switching; and Reception of SI update & ETWS/CMAS when SI/ETWS/CMAS broadcast doesn't exist in a UE's active BWP.

Document <CIT> discloses a sidelink (SL) configuration for SL communications directly between a communication terminal and another communication terminal that is separate from a communication network link configuration for communications with network equipment in some embodiments. An SL configuration, which could be an SL reconfiguration or an SL preconfiguration for use by the communication terminal after the terminal transitions from in coverage to out of coverage, could be transmitted through network/terminal signaling, and detailed examples of such signaling are disclosed herein. An SL configuration could be or include an SL bandwidth part (BWP) configuration and an SL communication resource configuration, such as one or more resource pools, within the SL BWP. An SL configuration that is determined and transmitted by network equipment to one or more terminals could also or instead involve a common or initial SL configuration to be used for SL communications by multiple communication terminals.

Document <CIT> discloses a control signal management method in a wireless communication system that comprises the steps of: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing step to the base station.

Embodiments of the present disclosure provide a device and method for effectively providing a multicast and broadcast service (MBS) service in a mobile communication system.

In particular, the embodiments of the present disclosure provide a method and device for effectively providing an MBS service when a bandwidth part (BWP) where the corresponding MBS service is provided is different from an active BWP of a user equipment (UE).

The present invention is according to the independent claims.

According to an embodiment of the present disclosure, an operation method of a user equipment (UE) in a wireless communication system, the operation method comprises: identifying whether an active bandwidth part (BWP) is the same as a BWP for a multicast and broadcast service (MBS) service of interest; transmitting, to a base station, a message indicating the MBS service of interest in case that the active BWP is different from the BWP for the MBS service of interest; receiving, from the base station, based on the message indicating the MBS service of interest, information related to the MBS service of interest; and receiving the MBS service of interest, based on the information related to the MBS service of interest.

According to an embodiment of the present disclosure, an operation method of a user equipment (UE) in a wireless communication system, the operation method comprises: identifying whether an active bandwidth part (BWP) is the same as a BWP for a multicast and broadcast service (MBS) service of interest; transmitting, to a base station, a message indicating the MBS service of interest in case that the active BWP is different from the BWP for the MBS service of interest; receiving, from the base station, based on the message indicating the MBS service of interest, information related to the MBS service of interest; and receiving the MBS service of interest, based on the information related to the MBS service of interest.

According to an embodiment, the operation method may further include, in case that the information for providing the service based on the MBS service of interest includes BWP switching information, switching, based on the BWP switching information, the active BWP from a BWP configured for the UE to another BWP, and the receiving of the MBS service of interest may include receiving the MBS service of interest on the switched active BWP.

According to an embodiment, the BWP switching information may be included in a radio resource control (RRC) Reconfiguration message or downlink control information (DCI).

According to an embodiment, in case that the information for providing the service based on the MBS service of interest includes updated MBS information, the updated MBS information may include information about an added MBS provided on the active BWP, and the receiving of the MBS may include receiving, based on the updated MBS information, the MBS service of interest on the active BWP.

According to an embodiment, the updated MBS information may be included in an RRC reconfiguration message or a system information block message.

According to an embodiment, the operation method may further include, after transmitting the message including the information about the MBS service of interest, starting a timer for prohibiting retransmission of the message including the information about the MBS service of interest.

According to an embodiment of the present disclosure, an operation method of a base station in a wireless communication system, the operation method comprises: in case that an active bandwidth part (BWP) is different from a BWP for a multicast and broadcast service (MBS) service of interest, receiving, from a user equipment (UE), a message indicating the MBS service of interest; determining, based on the message indicating the MBS service of interest, information related to the MBS service of interest; transmitting, to the UE, the information related to the MBS service of interest; and transmitting, to the UE, the MBS service of interest based on the information related to the MBS service of interest.

According to an embodiment, in case that the information for providing the service based on the MBS service of interest includes BWP switching information, the active BWP may be switched from a BWP configured for the UE to another BWP based on the BWP switching information, and the transmitting of the MBS service of interest may include transmitting the MBS service of interest on the switched active BWP.

According to an embodiment, the BWP switching information may be included in an RRC reconfiguration message or DCI.

According to an embodiment, in case that the information for providing the service based on the MBS service of interest includes updated MBS information, the updated MBS information may include information about an added MBS service of interest provided on the active BWP, and the transmitting of the MBS service of interest may include transmitting, based on the updated MBS information, the MBS service of interest on the active BWP.

According to an embodiment of the present disclosure, a user equipment operating in a wireless communication system, the UE comprises: a communicator; and at least one processor connected with the communicator and configured to: identify whether an active bandwidth part (BWP) is the same as a BWP for a multicast and broadcast service (MBS) service of interest, transmit, to a base station, a message indicating the MBS service of interest in case that the active BWP is different from the BWP for the MBS service of interest, receive, from the base station, based on the message indicating the MBS service of interest, information related to MBS service of interest, and receive the MBS service of interest, based on the information related to the MBS service of interest.

According to an embodiment, the at least one processor may be further configured to, in case that the information for providing the service based on the MBS service of interest includes BWP switching information, switch, based on the BWP switching information, the active BWP from a BWP configured for the UE to another BWP, and receive the MBS service of interest on the switched active BWP.

According to an embodiment, in case that the information for providing the service based on the MBS service of interest includes updated MBS information, the updated MBS information may include information about an added MBS service of interest provided on the active BWP, and the at least one processor may be further configured to receive, based on the updated MBS information, the MBS service of interest on the active BWP.

According to an embodiment of the present disclosure, a base station operating in a wireless communication system, the base station comprising: a communicator; and at least one processor connected with the communicator and configured to: in case that an active bandwidth part (BWP) is different from a BWP for a multicast and broadcast service (MBS) service of interest, receive, from a user equipment (UE), a message indicating the MBS service of interest, determine, based on the message indicating the MBS service of interest, information related to the MBS service of interest, transmit, to the UE, the information related to the MBS service of interest, and transmit, to the UE, the MBS service of interest based on the information related to the MBS service of interest.

In the following descriptions of the present disclosure, related known functions or configurations are not described in detail when it is deemed that they would unnecessarily obscure the essence of the present disclosure.

Advantages and features of the present disclosure and methods of accomplishing the same will be more readily appreciated by referring to the following description of embodiments and the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as being limited to the disclosed embodiments set forth herein; rather, the present embodiments are provided so that the present disclosure will be thorough and complete and will fully convey the concept of the present disclosure to those of ordinary skill in the art, and the present disclosure will only be defined by the appended claims. Throughout the specification, like reference numerals refer to like elements.

It will be understood that each block of a flowchart in the drawings and combinations of blocks of the flowchart may be performed by computer program instructions. These computer program instructions may be loaded into a processor of a general-purpose computer, a special-purpose computer, or another programmable data processing equipment, and thus, the instructions performed via the processor of the computer or the other programmable data processing equipment create a means for performing functions specified in the flowchart block(s). The computer program instructions may also be stored in a computer-executable or computer-readable memory capable of directing the computer or the other programmable data processing equipment to implement functions in a specific manner, and thus, the instructions stored in the computer-executable or computer-readable memory may produce an article of manufacture including instruction means for performing the functions described in the flowchart block(s). The computer program instructions may also be loaded into the computer or the other programmable data processing equipment, and thus, instructions for operating the computer or the other programmable data processing equipment by generating a computer-executed process when a series of operations are performed in the computer or the other programmable data processing equipment may provide operations for performing the functions described in the flowchart block(s).

In addition, each block may represent a portion of a module, segment, or code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that, in some alternative implementations, functions mentioned in blocks may occur out of order. For example, two blocks illustrated in succession may be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order depending on functions corresponding thereto.

As used herein, the term 'unit' denotes a software element or a hardware element such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and the 'unit' performs certain functions. However, the term 'unit' is not limited to software or hardware. The 'unit' may be configured so as to be in an addressable storage medium, or may be configured so as to operate one or more processors. Thus, for example, the term 'unit' may include elements, such as software elements, object-oriented software elements, class elements, and task elements, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, micro-codes, circuits, data, a database, data structures, tables, arrays, and variables. Functions provided by the elements and 'units' may be combined into the smaller number of elements and 'units', or may be divided into additional elements and 'units'. Furthermore, the elements and 'units' may be embodied to reproduce one or more central processing units (CPUs) in a device or security multimedia card. In addition, in an embodiment, the 'unit' may include one or more processors.

As used in the following description, terms identifying access nodes, terms indicating network entities, terms indicating messages, terms indicating interfaces between network entities, terms indicating various types of identification information, etc. are exemplified for convenience of descriptions. Accordingly, the present disclosure is not limited to terms to be described later, and other terms representing objects having the equivalent technical meaning may be used.

Hereinafter, for convenience of descriptions, the present disclosure uses terms and names defined in the 3rd Generation Partnership Project Long-Term Evolution (3GPP LTE) standard. However, the present disclosure is not limited to the terms and names but may also be identically applied to systems that comply with other standards. In the present disclosure, for convenience of descriptions, a next-generation Node B (gNB) may be used interchangeably with an evolved Node B (eNB). In other words, a base station (BS) described as an eNB may represent a gNB. Furthermore, the term 'terminal' may refer to a mobile phone, a machine type communication (MTC) device, a narrowband Internet of things (NB-IoT) device, a sensor, and other wireless communication devices.

Hereinafter, a BS is an entity that allocates resources to a terminal, and may be at least one of a gNB, an eNB, a Node B, a BS, a wireless access unit, a BS controller, or a network node. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. However, the BS or terminal is not limited to the above examples.

In particular, the present disclosure may be applied to the 3GPP new radio (NR) (5th generation (<NUM>) mobile communication standard). Furthermore, the present disclosure may be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail businesses, security and safety-related services, etc.), based on a <NUM> communication technology and an loT-related technology. In the present disclosure, for convenience of descriptions, a gNB may be used interchangeably with an eNB. In other words, a BS described as an eNB may represent a gNB. Furthermore, the term 'terminal' may refer to a mobile phone, a machine type communication (MTC) device, a narrowband Internet of things (NB-IoT) device, a sensor, and other wireless communication devices.

Wireless communication systems have progressed beyond providing initial voice-centered services into broadband wireless communication systems that provide highspeed, high-quality packet data services based on communication standards such as 3GPP's High Speed Packet Access (HSPA), LTE or Evolved Universal Terrestrial Radio Access (E-UTRA), LTE-Advanced (LTE-A), LTE Pro, 3GPP2's High Rate Packet Data (HRPD), Ultra Mobile Broadband (UMB), and the Institute of Electrical and Electronic Engineers (IEEE) <NUM>.

As a representative example of a broadband wireless communication system, an LTE system adopts an orthogonal frequency division multiplexing (OFDM) scheme for downlink (DL) and a single carrier frequency division multiple access (SC-FDMA) scheme for uplink (UL). UL refers to a radio link through which a UE (or a MS) transmits data or a control signal to a BS (or an eNB), and DL refers to a radio link through which the BS transmits data or a control signal to the UE. In the multiple access schemes as described above, data or control information of each user may be identified by allocating and operating time-frequency resources carrying the data or the control information for each user to prevent overlapping i.e., obtain orthogonality between the time-frequency resources.

Because a post-LTE communication system, i.e., a <NUM> communication system, needs to be able to freely reflect various requirements from users, service providers, etc., the <NUM> communication system is required to support services that simultaneously satisfy the various requirements. Services being considered for <NUM> communication systems include Enhanced Mobile BroadBand (eMBB), Massive Machine Type Communication (mMTC), Ultra-Reliable Low-Latency Communication (URLLC), etc..

According to some embodiments, eMBB may aim to provide higher data transfer rates than those supported by legacy LTE, LTE-A, or LTE Pro. For example, in <NUM> communication systems, eMBB should be able to deliver peak data rates of <NUM> gigabits per second (Gbps) in DL and <NUM> Gbps in UL from a BS perspective. Furthermore, the <NUM> communication systems should be able to provide better user perceived data rates while simultaneously delivering the peak data rates. To meet such requirements, the <NUM> communication systems may require improvement of various transmission and reception technologies including a further improved multi-input multi-output (MIMO) transmission technology. Furthermore, while a current LTE system transmits signals by using a maximum transmission bandwidth of <NUM> megahertz (MHz) in the <NUM> band, a <NUM> communication system may satisfy data transfer rates required by a <NUM> technology by using a wider frequency bandwidth than <NUM> in the <NUM> to <NUM> bands or the bands above <NUM>.

At the same time, mMTC is being considered to support application services such as the loT in <NUM> communication systems. In order to efficiently provide the loT, the mMTC may require support of massive connections with terminals in a cell, enhanced terminal coverage, improved battery life, low terminal cost, etc. Because the loT is a system equipped with multiple sensors and various devices to provide communication functions, it must be able to support a large number of terminals (e.g., <NUM>,<NUM>,<NUM> terminals per square kilometer (km<NUM>)) in a cell. Furthermore, because a terminal supporting the mMTC is highly likely to be located in a shaded area that cannot be covered by a cell, such as a basement of a building, due to characteristics of the service, the mMTC may require wide area coverage compared to other services provided by a <NUM> communication system. The terminal supporting the mMTC should be configured as a low-cost terminal and require a very long battery lifetime such as <NUM> to <NUM> years because it is difficult to frequently replace a battery of the terminal.

Lastly, URLLC is a cellular-based wireless communication service used for mission-critical applications such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote healthcare, emergency alert services, etc. Thus, URLLC communications should be able to provide very low latency (ultra-low latency) and very high reliability (ultra-high reliability). For example, services supporting URLLC need to satisfy air interface latency of less than <NUM> milliseconds (ms) and simultaneously have requirements of packet error rate of equal to or less than <NUM>-<NUM>. Thus, for the services supporting URLLC, a <NUM> system has to provide a transmit time interval (TTI) shorter than for other services and may simultaneously require a design for allocating wide frequency-band resources to ensure high reliability of a communication link.

The above-described three services considered in the <NUM> communication systems, i.e., eMBB, URLLC, and mMTC, may be multiplexed in one system for transmission. In this regard, different transmission and reception techniques and transmission and reception parameters may be used between services to satisfy different requirements for the respective services. However, the mMTC, URLLC, and eMBB are merely examples of different service types, and service types to which the present disclosure is applied are not limited to the above-described examples.

Furthermore, although embodiments of the present disclosure will be described using an LTE, LTE-A, LTE Pro, or <NUM> (or NR that is next-generation mobile communication) system as an example, the embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds and channel configurations. It should be also understood by a person skilled in the art that embodiments of the present disclosure are applicable to other communication systems through some modifications not departing from the scope of the present disclosure.

<FIG> illustrates an operating scheme for multicast and broadcast service (MBS) communication, according to an embodiment of the present disclosure.

MBS communication refers to a method by which one transmitting device communicates with several receiving devices in a mobile communication system. In this case, the transmitting device may be a BS <NUM>, and the receiving devices may be UEs <NUM>, <NUM>, <NUM>, and <NUM>. However, the transmitting device may be the UEs <NUM>, <NUM>, <NUM>, and <NUM>. <FIG> shows that MBS communication is performed between the BS <NUM> that is a transmitting device and the UEs <NUM>, <NUM>, <NUM>, <NUM> that are receiving devices. Such MBS communication may be a broadcast for an unspecified number of devices or a multicast for specific multiple receiving devices. When performing communication using a multicast method, the BS <NUM> may configure only specific UEs to receive corresponding multicast packets. To achieve this, the BS <NUM> may configure a set of UEs with which to perform a specific multicast communication, and the set of UEs are referred to as a multicast group <NUM> in <FIG>. In the embodiment of <FIG>, UE <NUM><NUM>, UE <NUM><NUM>, and UE <NUM><NUM> configured as one multicast group <NUM> are allocated a G-RNTI from the BS <NUM>, and the BS <NUM>. It is assumed that data from. The UEs <NUM>, <NUM>, and <NUM> in the multicast group <NUM> may be assigned the same group radio network temporary identifier (G-RNTI) to receive allocated data by using the corresponding G-RNTI. In the embodiment of <FIG>, it is assumed that UE <NUM><NUM>, UE <NUM><NUM>, and UE <NUM><NUM> configured as the multicast group <NUM> are assigned a G-RNTI by the BS <NUM> and receive data from the BS <NUM> by using a multicast method. Because UE <NUM><NUM> is not included in the multicast group <NUM>, the UE <NUM><NUM> is not assigned the G-RNTI by the BS <NUM>. Accordingly, the UE <NUM><NUM> may not receive the data that the UE <NUM><NUM>, the UE <NUM><NUM>, and the UE <NUM><NUM> receive from the BS (<NUM>). One or more multicast groups <NUM> may be configured in the coverage provided by the BS <NUM>, and each multicast group may be identified by a G-RNTI. One UE may be assigned one or more G-RNTIs by the BS <NUM>. In a radio resource control (RRC) Idle mode or an RRC Inactive mode as well as in an RRC Connected mode, the UE may receive multicast data by using a G-RNTI value assigned in the RRC Connected mode. A G-RNTI may be included and configured in at least one of RRC Reconfiguration, RRC Setup, or RRC Reestablishment messages received by the UE in the RRC Connected mode. However, in another embodiment, the BS <NUM> may transmit a system information block (SIB) including a G-RNTI value that can be received by the UE. The UE configured with the G-RNTI value in this way may apply the G-RNTI value thereafter.

<FIG> illustrates a configuration procedure for performing MBS communication, according to an embodiment of the present disclosure.

A UE <NUM> that does not have an RRC connection with a BS <NUM> may select the BS <NUM> from which to request an MBS service in order to perform MBS communication. In this case, the UE <NUM> may receive synchronization signals transmitted from the BS <NUM> to perform a cell selection or cell reselection procedure for selecting the BS <NUM> with a high received signal strength (<NUM>). In the embodiment of <FIG>, it is assumed that the UE <NUM> performs a cell reselection operation for selecting a cell when it transitions to an RRC Idle mode or RRC Inactive mode after an initial RRC Connected state.

Thereafter, the UE <NUM> may receive a SIB from the selected cell (<NUM>). At that time, if the UE <NUM> wants to receive an MBS service, the UE <NUM> may receive a SIB including MBS information among SIBs. The SIB including the MBS information may include a list of MBS services that are already provided or may be provided by each serving cell. The list of MBS services that are already provided or may be provided by each serving cell as described above may be referred to as AvailableMBSList. AvailableMBSList may include pieces of MBS session information. MBS session information may include a temporary mobile group identity (tmgi) value used to identify a group and an MBS session ID (sessionID). A tmgi value may include a public land mobile network (PLMN) ID (plmn-ID) that identifies whether a service is provided by a communication operator and a service ID (serviceID) that identifies a service provided by the communication operator. When such information is combined, AvailableMBSList may have the following exemplary structure.

When all UEs request RRC configuration in order to receive all MBS services, the BS <NUM> may be overloaded due to a large number of UEs instantaneously attempting access to the BS <NUM>. Therefore, an access control method for an MBS service may be required. To this end, an Access Category value and uac-BarringForAccessldentity for access control may be configured in each tmgi. The frequency of requests for access to the BS <NUM> for each tmgi may be controlled by using the configured Access category and uac-BarringForAccessldentity. Although it is assumed in the embodiment of <FIG> that the UE <NUM> receives the SIB including the MBS information, according to an embodiment, such MBS information may be transmitted in a DL Information Transfer message.

Upon receiving the SIB including the MBS information, the UE <NUM> may identify an MBS service of interest among the list of MBS services that are already provided or may be provided by each serving cell (<NUM>). When the UE <NUM> identifies the MBS service of interest, the identified MBS service may be an MBS service required by an application of the UE <NUM>, and the UE <NUM> may determine which MBS service it is interested in according to other conditions. The UE <NUM> may identify an MBS service based on a tmgi. In other words, the UE <NUM> may check whether a tmgi for an MBS service that the UE <NUM> wants to receive (the UE <NUM> is interested in) is included in the SIB including the MBS information. In detail, the UE <NUM> may check whether the tmgi for the desired MBS service that the UE <NUM> wants to receive is included in the AvailableMBSList in the SIB including the MBS information. If the tmgi for the desired MBS service is included in the SIB including the MBS information, the UE <NUM> may perform an operation of establishing an RRC connection to receive the corresponding MBS service. In order to determine whether the UE <NUM> initiates RRC connection setup, the UE <NUM> may perform an access control operation (<NUM>). The UE <NUM> may perform, based on a PLMN ID (plmn-ID) included in the tmgi for the desired MBS service, access control by using UAC-Barring information for the corresponding PLMN ID. The UE <NUM> may determine whether an access is allowed for the uac-BarringForAccessldentity and Access Category for the desired MBS service. If an access for receiving the MBS service is allowed, the UE <NUM> may start a procedure for requesting an RRC connection.

If the UE <NUM> is allowed access for receiving the MBS service, the UE <NUM> may transmit an RRC Setup Request message to the BS <NUM> (<NUM>). In the present disclosure, an RRC connection request is not limited to the RRC Setup Request message, and according to an embodiment, an RRC Reestablishment Request message may also be used for the same purpose. Because the RRC Setup Request message or RRC Reestablishment Request message is a general message that can be used by the UE <NUM> to transition to an RRC Connected mode, such message may include a cause value indicating a purpose for which the UE <NUM> intends to transition to the RRC Connected mode. At this time, if the UE <NUM> wants to receive an MBS service, it may transmit, to the BS <NUM>, an RRC Setup Request or RRC Reestablishment Request message including a cause value indicating that MBS configuration is desired. However, if the RRC Setup Request or RRC Reestablishment Request message is not for an RRC setup request or RRC reestablishment request transmitted by the UE <NUM> to receive an MBS service, the UE <NUM> may transmit the corresponding message using a cause value passed from an upper layer. The BS <NUM> may transmit an RRC Setup message in order for the UE <NUM> to transition to the RRC Connected mode (<NUM>). However, in the present disclosure, a message for switching the UE <NUM> to the RRC Connected mode is not limited to the RRC Setup message, and according to an embodiment, an RRC Reestablishment message may also be used for the same purpose. When the UE <NUM> receives the RRC Setup message or RRC Reestablishment message, signaling radio bearer <NUM> (SRB1) may be configured by configuration information for the SRB1 included in the corresponding message. SRB1 may be a radio bearer for exchanging RRC messages between the BS <NUM> and the UE <NUM>.

After applying the configuration information included in the RRC Setup message or the RRC Reestablishment message, the UE <NUM> may inform the BS <NUM> that reception configuration from the BS <NUM> has been successfully applied by transmitting an RRC Setup Complete or RRC Reestablishment Complete message to the BS <NUM> (<NUM>). In addition, the RRC Setup Complete message or RRC Reestablishment Complete message transmitted in operation <NUM> may include a list of MBS services that the UE <NUM> wants to receive. The list of MBS services may be a list including tmgi values respectively corresponding to the MBS services that the UE <NUM> wants to receive. In this case, a tmgi included in the list of MBS services may be a tmgi included in the SIB (or DL Information Transfer message) transmitted by the BS <NUM> to the UE <NUM> in operation <NUM>. More specifically, the tmgi values included in the list of MBS services may correspond to all or some of the tmgis included in the list of MBS services that are already provided or may be provided by each serving cell.

Because SRB1 is configured and the list of MBS services that the UE <NUM> wants to receive are transmitted to the BS <NUM> in operation <NUM> that is a preceding operation, the BS <NUM> may configure a method of receiving an MBS service based thereon (<NUM>).

According to an embodiment, the MBS service may be configured using an RRC Reconfiguration message transmitted by the BS <NUM> to the UE <NUM>. According to an embodiment, the RRC Reconfiguration message may include configuration information for signaling radio bearer <NUM> (SRB2) used for transmitting and receiving a non-access stratum (NAS) message, a data radio bearer (DRB) used for transmitting and receiving data, and a point-to-multipoint (PTM) DRB used for multicast transmission. Here, the PTM DRB may be configured without being distinguished from a general DRB, or may be configured by a received G-RNTI.

Furthermore, the BS <NUM> may configure a radio link control (RLC) bearer over which the configured radio bearer is to be transmitted, and may also configure which radio bearer will be linked with the configured RLC bearer.

According to an embodiment, the BS <NUM> may configure a G-RNTI via which UEs belonging to a multicast group can receive multicast data. According to an embodiment, a G-RNTI is an RNTI configured for reception of a transport block (TB) and may be used to indicate scheduling information for a physical DL shared channel (PDSCH). According to an embodiment, a G-RNTI may be configured per media access control (MAC) entity, but may be configured per bandwidth part (BWP). If a G-RNTI is configured per BWP, the configured G-RNTI may be used only when receiving PDSCH resources in a corresponding BWP. In other words, the G-RNTI may not be used in another BWP. To this end, the G-RNTI may be included and configured in a DL BWP configuration (BWP-DownLink configuration) field in an RRC message. According to an embodiment, a BWP ID used when the G-RNTI is configured may be configured. In another embodiment, the G-RNTI may be configured per cell. If the G-RNTI is configured for each cell, the configured G-RNTI may be used only when receiving PDSCH resources of the cell. In other words, the corresponding G-RNTI may not be used in another cell. To this end, the G-RNTI may be included and configured in a cell configuration field in the RRC message. However, a cell ID to be used when the G-RNTI is configured may be configured.

According to an embodiment, the BS <NUM> may separately configure the UE <NUM> with a BWP and a search space for reception of an MBS service. Information about a BWP and a search space used for receiving a specific MBS service may be configured by the BS <NUM> for the UE <NUM>. The configuration information may include an MBS BWP and an MBS search space. Here, the MBS BWP may mean a BWP to which the assigned G-RNTI is applied. According to an embodiment, a BWP including the G-RNTI in the BWP-Downlink configuration field may be the MBS BWP. Here, the MBS search space may be a search space for which a DL control information (DCI) format for MBS reception is configured in search space configuration information, or a search space including an indicator indicating a search space for MBS reception in the search space configuration information. According to an embodiment, the search space configuration information may include a <NUM>-bit indicator indicating whether the corresponding search space is an MBS search space. If the indicator indicates that the search space is an MBS search space, the search space may be an MBS search space and may be used as a search space for monitoring a G-RNTI for MBS reception.

If the UE <NUM> has applied information included in the RRC Reconfiguration message in the preceding operation <NUM>, the UE <NUM> may inform the BS <NUM> that the information in the RRC Reconfiguration message has been applied by transmitting an RRC Reconfiguration Complete message to the BS <NUM> (<NUM>).

Based on the above-described process, the UE <NUM> may receive a broadcast or multicast packet by performing MBS communication. In other words, the UE <NUM> may receive the MBS service from the BS <NUM> (<NUM>).

<FIG> illustrates an example in which an active BWP of a UE is different from a BWP associated with an MBS service of interest, according to an embodiment of the present disclosure.

A BS may have several BWPs on a frequency axis. However, only one of these BWPs may be activated and used as an active BWP. The UE monitors and uses only an active BWP while not monitoring a BWP other than the active BWP. In the embodiment of <FIG>, it is assumed that two BWPs <NUM> and <NUM> are configured and only one of the two BWPs is activated as the active BWP <NUM>. However, when a specific MBS service is provided only on the specific BWP <NUM> and the UE receives data on the active BWP <NUM>, the UE cannot receive an MBS service provided on another BWP. For example, when the UE wants to receive specific broadcast data provided to an unspecified UE, an active BWP of the UE may be different from a BWP on which broadcast data that the UE is interested in is transmitted. In the embodiment of <FIG>, the MBS service <NUM> that the UE is interested in is provided on the BWP <NUM> other than the active BWP <NUM>. In this case, in order to receive the corresponding MBS service <NUM>, the UE has to perform data reception in the BWP <NUM> on which the corresponding MBS service <NUM> is provided. Here, the unit of the MBS service <NUM> may be a tmgi. In embodiments of <FIG>, methods performed by the UE to receive the MBS service <NUM> when the BWP <NUM> on which the MBS service <NUM> that the UE is interested in is provided is different from the active BWP <NUM> of the UE are described below.

<FIG> illustrates a method, performed by a UE, of receiving an MBS service by performing BWP switch, according to an embodiment of the present disclosure.

The embodiment of <FIG> relates to, when a BWP on which an MBS service that a UE <NUM> is interested in is provided is different from an active BWP, a method, performed by the UE <NUM>, of informing a BS <NUM> of the MBS service of interest and switching the active BWP to the BWP on which the corresponding MBS service is provided.

In the embodiment of <FIG>, the UE <NUM> may receive, from the BS <NUM>, data on the active BWP. However, at this time, an MBS service that the UE <NUM> is interested in may not be provided on the active BWP (<NUM>).

If the active BWP is different from a BWP associated with the MBS service desired by the UE <NUM>, the UE <NUM> may inform the BS <NUM> that there is an MBS service of interest in order to receive the MBS service of interest, and request or induce switching of the active BWP to the BWP on which the corresponding MBS service is provided (<NUM>). A message transmitted by the UE <NUM> to the BS <NUM> in operation <NUM> may include a list of MBS services that the UE <NUM> desires to receive. According to an embodiment, the unit of the MBS service may be a tmgi. Also, according to an embodiment, a UE assistance information message may be used as the message transmitted in operation <NUM>.

After the UE <NUM> informs the BS <NUM> that there is the MBS service of interest (<NUM>), the BS <NUM> may indicate BWP switch (<NUM>). In operation <NUM>, an operation of the UE <NUM> switching the active BWP may be indicated by the BS <NUM> transmitting an RRC Reconfiguration message to the UE <NUM> in the RRC Connected mode or transmitting a command in DCI on a physical DL control channel (PDCCH).

However, the BS <NUM> is not necessarily required to indicate the BWP switch, and may need to keep the corresponding UE <NUM> staying on the currently active BWP according to the operation of a communication network. However, because the UE <NUM> cannot know a situation of the BS <NUM> and a decision made by the BS <NUM>, the UE <NUM> may repeat operation <NUM> of informing the BS <NUM> that there is an MBS service of interest and requesting or inducing switching of the active BWP to the BWP on which the MBS service is provided. However, because the message repeatedly transmitted by the UE <NUM> may cause unnecessary resource consumption, repeated transmission of the message needs to be avoided. To this end, after the UE <NUM> transmits the message informing the BS <NUM> that there is an MBS service of interest (<NUM>), a prohibit timer for transmission of the corresponding message may be started (<NUM>). When the prohibit timer is running, the UE <NUM> may not transmit a message informing the BS <NUM> that there is an MBS service of interest. Only when the corresponding prohibit timer is stopped, the UE <NUM> may transmit a message informing the BS <NUM> that there is an MBS service of interest. In an embodiment, the message informing the BS <NUM> that there is an MBS service that the UE <NUM> is interested in may be transmitted when the list of MBS services that the UE <NUM> is interested in are changed and the prohibit timer is stopped.

If the active BWP of the UE <NUM> is switched in operation <NUM>, the UE <NUM> may receive the corresponding MBS service because the currently active BWP is the same as the BWP associated with the MBS service of interest are the same (<NUM>).

<FIG> illustrates a method, performed by a UE, of receiving an MBS service by updating MBS information by a BS, according to an embodiment of the present disclosure.

The embodiment of <FIG> relates to, when a BWP where an MBS service that a UE <NUM> is interested in is provided is different from an active BWP, a method by which the UE <NUM> informs a BS <NUM> of the MBS service of interest and the BS <NUM> provides the MBS service on the currently active BWP of the UE <NUM>.

If the active BWP is different from a BWP associated with the MBS service desired by the UE <NUM>, the UE <NUM> may inform the BS <NUM> that there is an MBS service of interest in order to receive the MBS service of interest, and request or induce the corresponding MBS service to be provided on the currently active BWP (<NUM>). A message transmitted by the UE <NUM> to the BS <NUM> in operation <NUM> may include a list of MBS services that the UE <NUM> desires to receive. According to an embodiment, the unit of the MBS service may be a tmgi. According to an embodiment, a UE assistance information message may be used as the message transmitted in operation <NUM>.

After the UE <NUM> informs the BS <NUM> that there is the MBS service of interest (<NUM>), the BS <NUM> may update MBS information to add an MBS service provided on the active BWP (<NUM>). In operation <NUM>, the BS <NUM> may transmit a list of MBS services provided on the BWP by using an RRC Reconfiguration message or a SIB message. Furthermore, the BS <NUM> may configure a G-RNTI via which the corresponding MBS services can be received. However, the BS <NUM> is not necessarily required to update the MBS information. For example, the BS <NUM> may keep the UE <NUM> staying on the currently active BWP according to the operation of a communication network, and may not transmit data associated with the MBS service that the UE <NUM> is interested in. However, because the UE <NUM> cannot know a situation of the BS <NUM> and a decision made by the BS <NUM>, the UE <NUM> may repeat operation <NUM> of informing the BS <NUM> that there is an MBS service of interest and requesting or inducing the MBS service to be provided. However, the message repeatedly transmitted by the UE <NUM> as described above may cause unnecessary resource consumption, and thus, repeated transmission of the message needs to be avoided. To this end, after the UE <NUM> transmits the message informing the BS <NUM> that there is an MBS service of interest (<NUM>), a prohibit timer for transmission of the corresponding message may be started (<NUM>). When the prohibit timer is running, the UE <NUM> may not transmit a message informing the BS <NUM> that there is an MBS service of interest. Only when the corresponding prohibit timer is stopped, the UE <NUM> may transmit a message informing the BS <NUM> that there is an MBS service of interest. In an embodiment, the message informing the BS <NUM> that there is an MBS service that the UE <NUM> is interested in may be transmitted when the list of MBS services that the UE <NUM> is interested in are changed and the prohibit timer is stopped.

When the list of MBS services are updated by providing, on the active BWP of the UE <NUM>, an MBS service that the UE <NUM> is interested in (<NUM>), the UE <NUM> may receive the corresponding MBS service because the currently active BWP is the same as the BWP associated with the MBS service of interest (<NUM>).

<FIG> illustrates a method, performed by a UE, of receiving an MBS service by configuring an MBS gap by a BS, according to an embodiment of the present disclosure.

The embodiment of <FIG> relates to, when a BWP where an MBS service that a UE <NUM> is interested in is provided is different from an active BWP, a method by which the UE <NUM> informs a BS <NUM> of the MBS service of interest and the BS <NUM> provides the MBS service to the UE <NUM> in a BWP other than the active BWP by configuring a corresponding MBS gap.

If the active BWP is different from a BWP associated with the MBS service desired by the UE <NUM>, the UE <NUM> may inform the BS <NUM> that there is an MBS service of interest in order to receive the MBS service of interest, and request or induce an MBS gap for receiving the MBS service (<NUM>). A message transmitted by the UE <NUM> to the BS <NUM> in operation <NUM> may include a list of MBS services that the UE <NUM> desires to receive. According to an embodiment, the unit of the MBS service may be a tmgi. Furthermore, according to an embodiment, a UE assistance information message may be used as the message transmitted in operation <NUM>. After the UE <NUM> informs the BS <NUM> that there is the MBS service of interest (<NUM>), the BS <NUM> may configure an MBS gap in order for the UE to receive data associated with the MBS service on a BWP where the MBS service is provided (<NUM>). In operation <NUM>, the BS <NUM> may transmit a list of MBS services provided on the BWP and configuration information for the MBS gap by using an RRC Reconfiguration message or a SIB message. Furthermore, the BS <NUM> may configure a G-RNTI via which the corresponding MBS services can be received. However, in order to actually apply the corresponding MBS gap after configuring it, the BS <NUM> may additionally transmit an activation message in the form of DCI or a MAC control element (MAC CE). However, because the BS <NUM> is not required to provide the UE <NUM> with the MBS service that the UE <NUM> is interested in, the BS <NUM> does not necessarily need to perform an operation of configuring the MBS gap or the like. For example, the BS <NUM> may keep the UE <NUM> staying on the currently active BWP according to the operation of a communication network, and may not transmit data associated with the MBS service that the UE <NUM> is interested in. However, because the UE <NUM> cannot know a situation of the BS <NUM> and a decision made by the BS <NUM>, the UE <NUM> may repeat operation <NUM> of informing the BS <NUM> that there is an MBS service of interest and requesting or inducing the MBS service to be provided. However, the message repeatedly transmitted by the UE <NUM> may cause unnecessary resource consumption, and thus, repeated transmission of the message needs to be avoided. To this end, after the UE <NUM> transmits the message informing the BS <NUM> that there is an MBS service of interest (<NUM>), a prohibit timer for transmission of the corresponding message may be started (<NUM>). When the prohibit timer is running, the UE <NUM> may not transmit a message informing the BS <NUM> that there is an MBS service of interest. Only when the corresponding prohibit timer is stopped, the UE <NUM> may transmit a message informing the BS <NUM> that there is an MBS service of interest. In an embodiment, the message informing the BS <NUM> that there is an MBS service that the UE <NUM> is interested in may be transmitted when the list of MBS services that the UE <NUM> is interested in are changed and the prohibit timer is stopped.

Thereafter, in operation <NUM>, an MBS gap is configured for the UE <NUM> so that the UE <NUM> may move to an MBS BWP during an MBS gap period to receive the MBS service of interest therein. The MBS gap for the UE <NUM> may have a gap length <NUM> repeated at a regular gap periodicity <NUM>. In operation <NUM>, at least one of the gap periodicity <NUM> of the MBS gap, the gap length <NUM> of the MBS gap, and an offset time point at which the periodicity starts may be configured in an MBS gap configuration message transmitted by the BS <NUM>. The UE <NUM> does not transmit or receive data on an active BWP during the MBS gap period. In addition, the UE <NUM> may not perform PDCCH monitoring on the active BWP. Instead, the UE <NUM> may receive data associated with the MBS service by moving to a BWP on which the MBS service of interest is provided during the MBS gap period (<NUM> and <NUM>). According to an embodiment, the UE <NUM> may transmit or receive unicast data to or from the BS <NUM> on an active BWP during a duration other than the MBS gap period (<NUM> and <NUM>).

The MBS gap described with reference to <FIG> is configured per cell (or on an active BWP of a cell) so that the UE <NUM> moves to another BWP in the cell to receive an MBS service. Because the MBS gap is for transmitting and receiving MBS services, the MBS gap may not be applied when it overlaps with at least one of random access, a measurement gap, semi-persistent scheduling (SPS), a configured grant, a physical UL control channel (PUCCH), or a sounding reference signal (SRS) on a time axis. In addition, when the BS <NUM> indicates BWP switch to the UE <NUM>, the configured MBS gap may no longer be applied.

<FIG> illustrates a method, performed by a UE, of receiving an MBS service by configuring an MBS switching period by a BS, according to an embodiment of the present disclosure.

The embodiment of <FIG> relates to, when a BWP where an MBS service that a UE <NUM> is interested in is provided is different from an active BWP, a method by which the UE <NUM> informs a BS <NUM> of the MBS service of interest and the BS <NUM> provides the MBS service to the UE <NUM> on a BWP other than the active BWP by configuring a corresponding MBS switching period.

If the active BWP is different from a BWP associated with the MBS service desired by the UE <NUM>, the UE <NUM> may inform the BS <NUM> that there is an MBS service of interest in order to receive the MBS service of interest, and request or induce configuration of an MBS switching period for receiving the MBS service (<NUM>). A message transmitted by the UE <NUM> to the BS <NUM> in operation <NUM> may include a list of MBS services that the UE <NUM> desires to receive. According to an embodiment, the unit of the MBS service may be a tmgi. Furthermore, according to an embodiment, a UE assistance information message may be used as the message transmitted in operation <NUM>.

After the UE <NUM> informs the BS <NUM> that there is the MBS service of interest (<NUM>), the BS <NUM> may configure an MBS switching period in order for the UE <NUM> to receive data associated with the MBS service on a BWP where the MBS service is provided (<NUM>). In operation <NUM>, the BS <NUM> may transmit a list of MBS services provided on the BWP and configuration information for the MBS switching period by using an RRC Reconfiguration message or a SIB message. Furthermore, the BS <NUM> may configure a G-RNTI via which the corresponding MBS services can be received. However, after configuring the MBS switching period, the configured MBS switching period may be applied by a switch for MBS command from the BS <NUM> (<NUM>). After receiving the switch for MBS command from the BS <NUM>, the UE <NUM> may move to a BWP on which the MBS service of interest is provided during a switching period <NUM> to receive data for the MBS service on the BWP. However, because the BS <NUM> is not required to provide the UE <NUM> with the MBS service that the UE <NUM> is interested in, the BS <NUM> does not necessarily need to perform an operation of configuring the MBS switching period or the like. For example, the BS <NUM> may keep the UE <NUM> staying on the currently active BWP according to the operation of a communication network, and may not transmit data associated with the MBS service that the UE <NUM> is interested in. However, because the UE <NUM> cannot know the situation of the BS <NUM> and a decision made by the BS <NUM>, the UE <NUM> may repeat operation <NUM> of informing the BS <NUM> that there is an MBS service of interest and requesting or inducing the MBS service to be provided. However, the message repeatedly transmitted by the UE <NUM> may cause unnecessary resource consumption, and thus, repeated transmission of the message needs to be avoided. To this end, after the UE <NUM> transmits the message informing the BS <NUM> that there is an MBS service of interest (<NUM>), a prohibit timer for transmission of the corresponding message may be started (<NUM>). When the prohibit timer is running, the UE <NUM> may not transmit a message informing the BS <NUM> that there is an MBS service of interest. Only when the corresponding prohibit timer is stopped, the UE <NUM> may transmit a message informing the BS <NUM> that there is an MBS service of interest. According to an embodiment, the message informing the BS <NUM> that there is an MBS service that the UE <NUM> is interested in may be transmitted when the list of MBS services that the UE <NUM> is interested in are changed and the prohibit timer is stopped.

In a case that the MBS switching period is configured for the UE <NUM> in operation <NUM>, after receiving the switch for MBS command from the BS <NUM> in operation <NUM>, the UE <NUM> may move to an MBS BWP during the switching period to receive the MBS service of interest in the MBS BWP. At this time, the switch for MBS command from the BS <NUM> may be indicated to the UE <NUM> by DCI or a MAC CE. Configuration of the MBS switching period and a length of the switching period may be configured in an MBS switching period configuration message transmitted in operation <NUM>. The UE <NUM> does not transmit or receive data in an active BWP during the switching period <NUM>. In addition, the UE <NUM> may not perform PDCCH monitoring on the active BWP. Instead, the UE <NUM> may receive data associated with the MBS service by moving to a BWP on which the MBS service of interest is provided during the switching period <NUM> (<NUM>). According to an embodiment, the UE <NUM> may transmit or receive unicast data to or from the BS <NUM> in an active BWP during a duration other than the switching period <NUM> (<NUM>). According to an embodiment, when the UE <NUM> receives a preset positive number of PDSCHs or MAC protocol data units (PDUs) in the switching period <NUM>, the UE <NUM> may move to an active BWP regardless of a length of the remaining switching period. In this embodiment, the preset positive number may be <NUM>.

The MBS switching period described with reference to <FIG> is configured per cell (or in an active BWP of a cell) so that the UE <NUM> moves to another BWP in the cell to receive an MBS service. Because the MBS switching period is for transmitting and receiving MBS services, the MBS switching period may not be applied when it overlaps with resources for at least one of random access, a measurement gap, a PUCCH, or a SRS on a time axis. In addition, when the BS <NUM> indicates BWP switch to the UE <NUM>, the configured MBS switching period may no longer be applied.

The embodiment of <FIG> relates to, when a BWP where an MBS service that a UE <NUM> is interested in is provided is different from an active BWP, a method by which the UE <NUM> informs a BS <NUM> of the MBS service of interest and the BS <NUM> provides the MBS service to the UE <NUM> in a BWP other than the active BWP by configuring a corresponding MBS switching period.

If the active BWP is different from a BWP associated with the MBS service desired by the UE <NUM>, the UE <NUM> may inform the BS <NUM> that there is an MBS service of interest in order to receive the MBS service of interest, and request or induce configuration of an MBS switching period for receiving the MBS service (<NUM>). A message transmitted by the UE <NUM> to the BS <NUM> in operation <NUM> may include a list of MBS services that the UE <NUM> desires to receive. According to an embodiment, the unit of the MBS service may be a tmgi. Furthermore, according to an embodiment, a UE assistance information message may be used as the message transmitted in operation <NUM>. After the UE <NUM> informs the BS <NUM> that there is the MBS service of interest (<NUM>), the BS <NUM> may configure an MBS switching period in order for the UE <NUM> to receive data associated with the MBS service on a BWP where the MBS service is provided (<NUM>). In operation <NUM>, the BS <NUM> may transmit a list of MBS services provided on the BWP and configuration information for the MBS switching period by using an RRC Reconfiguration message or a SIB message. When configuring the MBS switching period, a duration of a FallBackToActiveBWP timer may be set. Furthermore, the BS <NUM> may configure a G-RNTI via which the corresponding MBS services can be received. However, after configuring the MBS switching period, the configured MBS switching period may be applied by a switch for MBS command from the BS <NUM> (<NUM>). After receiving the switch for MBS command from the BS <NUM>, the UE <NUM> may move to a BWP on which the MBS service of interest is provided during a switching period to receive data for the MBS service on the BWP.

In the embodiment of <FIG> , a length of the switching period may not be a predetermined value. According to an embodiment, the length of the switching period may be a duration of time until expiry of the FallBackToActiveBWP timer <NUM> which starts when the switch for MBS command is received or data for MBS is received. The UE <NUM> may stay in the BWP where the MBS service of interest is provided during the length of the switching period.

In the present embodiment, because the BS <NUM> is not required to provide the UE <NUM> with the MBS service that the UE <NUM> is interested in, the BS <NUM> does not necessarily need to perform an operation of configuring the MBS switching period or the like. For example, the BS <NUM> may keep the UE <NUM> staying on the currently active BWP according to the operation of a communication network, and may not transmit data associated with the MBS service that the UE <NUM> is interested in. However, because the UE <NUM> cannot know a situation of the BS <NUM> and a decision made by the BS <NUM>, the UE <NUM> may repeat operation <NUM> of informing the BS <NUM> that there is an MBS service of interest and requesting or inducing the MBS service to be provided. However, the message repeatedly transmitted by the UE <NUM> may cause unnecessary resource consumption, and thus, repeated transmission of the message needs to be avoided. To this end, after the UE <NUM> transmits the message informing the BS <NUM> that there is an MBS service of interest (<NUM>), a prohibit timer for transmission of the corresponding message may be started (<NUM>). When the prohibit timer is running, the UE <NUM> may not transmit a message informing the BS <NUM> that there is an MBS service of interest. Only when the corresponding prohibit timer is stopped, the UE <NUM> may transmit a message informing the BS <NUM> that there is an MBS service of interest. In an embodiment, the message informing the BS <NUM> that there is an MBS service that the UE <NUM> is interested in may be transmitted when the list of MBS services that the UE <NUM> is interested in are changed and the prohibit timer is stopped.

In a case that the MBS switching period is configured for the UE <NUM> in operation <NUM>, after receiving the switch for MBS command from the BS <NUM>, the UE <NUM> may move to an MBS BWP until the FallBackToActiveBWP timer <NUM> expires to receive the MBS service of interest in the MBS BWP. At this time, the switch for MBS command from the BS <NUM> may be indicated to the UE <NUM> by DCI or a MAC CE. Configuration of the MBS switching period may be configured in an MBS switching period configuration message transmitted in operation <NUM>. The UE <NUM> does not transmit or receive data in an active BWP while the FallBackToActiveBWP timer <NUM> is running. Also, the UE <NUM> may not perform PDCCH monitoring on the active BWP. Instead, the UE <NUM> may receive data associated with the MBS service by moving to a BWP on which the MBS service of interest is provided (<NUM>). According to an embodiment, the UE <NUM> may transmit or receive unicast data to or from the BS <NUM> in an active BWP during a duration other than the MBS switching period (<NUM>).

The MBS switching period described with reference to <FIG> is configured per cell (or in an active BWP of a cell) so that the UE <NUM> moves to another BWP in the cell to receive an MBS service. Because the MBS switching period is for transmitting and receiving MBS services, the MBS switching period may not be applied when it overlaps with resources for at least one of random access, a measurement gap, a PUCCH, or a SRS on the time axis. In addition, when the BS <NUM> indicates BWP switch to the UE <NUM>, the configured MBS switching period may no longer be applied.

<FIG> illustrates a method, performed by a UE, of receiving an MBS service by configuring discontinuous reception (DRX) by a base station, according to an embodiment of the present disclosure.

The embodiment of <FIG> relates to, when a BWP where an MBS service that a UE <NUM> is interested in is provided is different from an active BWP, a method by which the UE <NUM> informs a BS <NUM> of the MBS service of interest and the BS <NUM> provides the MBS service to the UE <NUM> in a BWP other than the active BWP by configuring corresponding DRX.

If the active BWP is different from a BWP associated with the MBS service desired by the UE <NUM>, the UE <NUM> may inform the BS <NUM> that there is an MBS service of interest in order to receive the MBS service of interest, and request or induce configuration of DRX for receiving the MBS service (<NUM>). A message transmitted by the UE <NUM> to the BS <NUM> in operation <NUM> may include a list of MBS services that the UE <NUM> desires to receive. According to an embodiment, the unit of the MBS service may be a tmgi. Furthermore, according to an embodiment, a UE assistance information message may be used as the message transmitted in operation <NUM>.

After the UE <NUM> informs the BS <NUM> that there is the MBS service of interest (<NUM>), the BS <NUM> may configure DRX in order for the UE <NUM> to receive data associated with the MBS service on a BWP where the MBS service is provided (<NUM>). In operation <NUM>, by using an RRC Reconfiguration message or a SIB message, the BS <NUM> may transmit a list of MBS services provided on the BWP, configuration information for the DRX, and indicator information indicating that the UE <NUM> may move to a BWP on which the MBS service of interest is provided during a time other than an active time of a DRX cycle to receive the MBS service. Furthermore, the BS <NUM> may configure a G-RNTI via which the corresponding MBS services can be received. However, in order to actually apply the corresponding DRX after configuring it, the BS <NUM> may additionally transmit an activation message in the form of DCI or a MAC CE.

However, because the BS <NUM> is not required to provide the UE <NUM> with the MBS service that the UE <NUM> is interested in, the BS <NUM> does not necessarily need to perform an operation of configuring the DRX for receiving data for the MBS service or the like. For example, the BS <NUM> may keep the UE <NUM> staying on the currently active BWP according to the operation of a communication network, and may not transmit data associated with the MBS service that the UE <NUM> is interested in. However, because the UE <NUM> cannot know a situation of the BS <NUM> and a decision made by the BS <NUM>, the UE <NUM> may repeat operation <NUM> of informing the BS <NUM> that there is an MBS service of interest and requesting or inducing the MBS service to be provided. However, the message repeatedly transmitted by the UE <NUM> may cause unnecessary resource consumption, and thus, repeated transmission of the message needs to be avoided. To this end, after the UE <NUM> transmits the message informing the BS <NUM> that there is an MBS service of interest (<NUM>), a prohibit timer for transmission of the corresponding message may be started (<NUM>). When the prohibit timer is running, the UE <NUM> may not transmit a message informing the BS <NUM> that there is an MBS service of interest. Only when the corresponding prohibit timer is stopped, the UE <NUM> may transmit a message informing the BS <NUM> that there is an MBS service of interest. In an embodiment, the message informing the BS <NUM> that there is an MBS service that the UE <NUM> is interested in may be transmitted when the list of MBS services that the UE <NUM> is interested in are changed and the prohibit timer is stopped.

In a case that the DRX for an MBS service is configured for the UE <NUM> in operation <NUM>, the UE <NUM> may move to an MBS BWP during a time period other than an active time <NUM> to receive the MBS service of interest in the MBS BWP (<NUM> and <NUM>). The DRX for the UE <NUM> may be repeated for each DRX cycle <NUM> that is a regular cycle. A length of the DRX cycle of the UE <NUM> and an offset time point at which the DRX cycle starts may be configured in a DRX configuration message for MBS transmitted in operation <NUM>. The UE <NUM> does not transmit or receive data in an active BWP during a time period other than the active time <NUM>. In addition, the UE <NUM> may not perform PDCCH monitoring on the active BWP. Instead, the UE <NUM> may receive data associated with the MBS service by moving to a BWP on which the MBS service of interest is provided during the time period other than the active time <NUM> (<NUM> and <NUM>). On the other hand, the UE <NUM> may transmit or receive unicast data to or from the BS <NUM> in an active BWP during the active time <NUM> (<NUM> and <NUM>).

The DRX for MBS described with reference to <FIG> is configured per cell or per group of multiple cells so that the UE <NUM> moves to another BWP in the cell to receive an MBS service. Because the DRX configured in this way is for MBS services, the UE <NUM> may stay in the active time <NUM> in a case where the DRX overlaps with at least one of random access, a measurement gap, a PUCCH, or a SRS on the time axis even during a time period other than the active time <NUM>. In addition, when the BS <NUM> indicates BWP switch to the UE <NUM>, the configured DRX may no longer be applied.

<FIG> illustrates a structure of a UE having two RX chains for an MBS service, according to an embodiment of the present disclosure.

While a UE <NUM> operates in a specific active BWP, an MBS service that the UE <NUM> is interested in may not be provided on the active BWP. In this case, a BWP <NUM> used by the UE <NUM> to transmit or receive unicast data to or from a BS <NUM> may be different from a BWP <NUM> on which the UE <NUM> receives an MBS service. Accordingly, the UE <NUM> may include two RX chains, i.e., an RX chain <NUM> for unicast and an RX chain <NUM> for MBS. However, in this case, the UE <NUM> may need to receive, from the BS <NUM>, information about when to use the RX chain <NUM> for MBS and a reception configuration when using the RX chain <NUM> for MBS. In an embodiment of <FIG>, an operation in which the UE <NUM> having two RX chains receives an MBS service and data for the MBS service is described below.

<FIG> illustrates a method, performed by a UE, of receiving an MBS service by using two RX chains, according to an embodiment of the present disclosure.

The embodiment of <FIG> relates to, when a BWP where an MBS service that a UE <NUM> is interested in is provided is different from an active BWP, a method by which the UE <NUM> informs a BS <NUM> of the MBS service of interest and receives data for the MBS service by using RX chains for the MBS service.

In the embodiment of <FIG>, the UE <NUM> may receive, from the BS <NUM>, data on the active BWP. However, at this time, an MBS service that the UE <NUM> is interested in may not be provided on the active BWP (<NUM>). If the active BWP is different from a BWP associated with the MBS service desired by the UE <NUM>, the UE <NUM> may inform the BS <NUM> that there is an MBS service of interest in order to receive the MBS service of interest, and request or induce a configuration for receiving the MBS service by using an RX chain for MBS (<NUM>). A message transmitted by the UE <NUM> to the BS <NUM> in operation <NUM> may include a list of MBS services that the UE <NUM> desires to receive. According to an embodiment, the unit of the MBS service may be a tmgi. Furthermore, according to an embodiment, a UE assistance information message may be used as the message transmitted in operation <NUM>. After the UE <NUM> informs the BS <NUM> that there is the MBS service of interest (<NUM>), the BS <NUM> may configure and indicate the UE <NUM> to use an RX chain for MBS (<NUM>). In operation <NUM>, an operation of configuring the UE <NUM> to use RX chain for MBS may be indicated by the BS <NUM> transmitting an RRC Reconfiguration message to the UE <NUM> in the RRC Connected mode or transmitting a command in DCI on a PDCCH. However, because the BS <NUM> is not required to make the UE <NUM> receive data for an MBS service by using the RX chain for MBS, the BS <NUM> may allow the UE <NUM> to transmit and receive data only on the currently active BWP according to the operation of a communication network. However, because the UE <NUM> cannot know a situation of the BS <NUM> and a decision made by the BS <NUM>, the UE <NUM> may repeat operation <NUM> of informing the BS <NUM> that there is an MBS service of interest and requesting or inducing reception of data for the MBS service by using the RX chain for MBS. However, the message repeatedly transmitted by the UE <NUM> as described above may cause unnecessary resource consumption, and thus, repeated transmission of the message needs to be avoided. To this end, after the UE <NUM> transmits the message informing the BS <NUM> that there is an MBS service of interest (<NUM>), a prohibit timer for transmission of the corresponding message may be started (<NUM>). When the prohibit timer is running, the UE <NUM> may not transmit a message informing the BS <NUM> that there is an MBS service of interest. Only when the corresponding prohibit timer is stopped, the UE <NUM> may transmit a message informing the BS <NUM> that there is an MBS service of interest. According to an embodiment, the message informing the BS <NUM> that there is an MBS service that the UE <NUM> is interested in may be transmitted when the list of MBS services that the UE <NUM> is interested in are changed and the prohibit timer is stopped.

If the UE <NUM> is configured to receive data for an MBS service by using an RX chain for MBS in operation <NUM>, the UE <NUM> may receive data on the currently active BWP by using an RX chain for unicast and receive the data for the MBS service on a BWP where the MBS service is provided by using the RX chain for MBS (<NUM>).

<FIG> is a diagram illustrating a structure of a BS according to an embodiment of the present disclosure.

Referring to <FIG>, the BS may include a transceiver <NUM>, a controller <NUM>, and a storage <NUM>. However, all the illustrated components are not essential. For example, the BS may include more or fewer components than those shown in <FIG>. In addition, the transceiver <NUM>, the controller <NUM>, and the storage <NUM> may be implemented as a single chip according to another embodiment. In the present disclosure, the controller <NUM> may be defined as a circuit or an application-specific integrated circuit, or at least one processor.

The transceiver <NUM> may transmit or receive signals to or from other network entities. For example, the transceiver <NUM> may transmit, to a UE, system information as well as a synchronization signal or a reference signal. The transceiver <NUM> may include an RF transmitter for up-converting and amplifying a frequency of a signal to be transmitted and an RF receiver for low-noise amplifying a received signal and down-converting its frequency. However, according to another embodiment, the transceiver <NUM> may be implemented by more or fewer components than those described above.

The transceiver <NUM> may be connected to the controller <NUM> to transmit and/or receive signals. The signals may include control information and data. Furthermore, the transceiver <NUM> may receive a signal via a radio channel and output the signal to the controller <NUM>. The transceiver <NUM> may transmit a signal output from the controller <NUM> via a radio channel.

The controller <NUM> may control all operations of the BS according to an embodiment proposed in the present disclosure. For example, the controller <NUM> may control a flow of signals between blocks so that the BS performs operations according to the above-described flowcharts.

The storage <NUM> may store at least one of information transmitted and received via the transceiver <NUM> and information generated via the controller <NUM>.

Also, the storage <NUM> may store control information or data included in a signal obtained by the BS. The storage <NUM> may be connected to the controller <NUM> to store at least one instruction, protocol, or parameter for a proposed function, process and/or method. The storage <NUM> may be composed of storage media, such as read-only memory (ROM), random access memory (RAM), hard discs, compact disc (CD)-ROM, and digital versatile discs (DVDs), or a combination thereof.

<FIG> is a diagram illustrating a structure of a UE according to an embodiment of the present disclosure.

Referring to <FIG>, the UE may include a transceiver <NUM>, a controller <NUM>, and a storage <NUM>. However, all the illustrated components are not essential. For example, the UE may include more or fewer components than those shown in <FIG>. In addition, the transceiver <NUM>, the controller <NUM>, and the storage <NUM> may be implemented as a single chip according to another embodiment. In the present disclosure, the controller <NUM> may be defined as a circuit or an application-specific integrated circuit, or at least one processor.

The transceiver <NUM> may transmit or receive signals to or from other network entities. For example, the transceiver <NUM> may receive, from a BS, system information as well as a synchronization signal or a reference signal. Furthermore, the transceiver <NUM> may include an RF transmitter for up-converting and amplifying a frequency of a signal to be transmitted and an RF receiver for low-noise amplifying a received signal and down-converting its frequency. However, according to another embodiment, the transceiver <NUM> may be implemented by more or fewer components than those described above.

The controller <NUM> may control all operations of the UE according to an embodiment proposed in the present disclosure. For example, the controller <NUM> may control a flow of signals between blocks so that the UE performs operations according to the above-described flowcharts.

Also, the storage <NUM> may store control information or data included in a signal obtained by the UE. The storage <NUM> may be connected to the controller <NUM> to store at least one instruction, protocol, or parameter for a proposed function, process and/or method. The storage <NUM> may be composed of storage media, such as ROM, RAM, hard discs, CD-ROM, and DVDs, or a combination of the storage media.

It should be noted that the above-described configuration diagrams, exemplary diagrams for a control/data signal transmission method, exemplary diagrams for operating procedures, and configuration diagrams are not intended to limit the scope of the present disclosure. In other words, all components, entities, or operations described in embodiments of the present disclosure should not be construed as being essential components for implementation of the present disclosure, and the present disclosure may be implemented by including only some of the components without departing the essence of the present disclosure. Furthermore, the embodiments may be combined with each other for operation when necessary. For example, parts of the methods presented in the present disclosure may be combined with one another to operate a network entity and a UE.

The above-described operations of the BS or UE may be implemented by providing a memory device storing corresponding program code in any component in the BS or UE. That is, a controller of the BS or UE may perform the above-described operations by causing a processor or a CPU to read and execute the program code stored in the memory device.

Various components, modules, etc. of an entity, the BS, or the UE described in the present specification may operate by using a hardware circuit, e.g., a complementary metal-oxide-semiconductor (CMOS)-based logic circuit, firmware, software, and/or a combination of hardware, firmware and/or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates, and an ASIC.

When the components and modules are implemented in software, a computer-readable storage medium having at least one program (software module) stored therein may be provided. The at least one program stored in the computer-readable storage medium is configured for execution by at least one processor within an electronic device. The at least one program includes instructions that cause the electronic device to execute the methods according to the embodiments of the present disclosure described in the claims or specification thereof.

The program (software module or software) may be stored in RAM, non-volatile memory including a flash memory, ROM, electrically erasable programmable ROM (EEPROM), magnetic disc storage devices, CD-ROM, DVDs or other types of optical storage devices, and magnetic cassettes. Alternatively, the program may be stored in a memory configured as a combination of some or all of the stated devices. A plurality of such devices may be included in the memory.

Furthermore, the program may be stored in an attachable storage device that may be accessed through communication networks, such as the Internet, Intranet, a local area network (LAN), a wide LAN (WLAN), and a storage area network (SAN), or a communication network configured in a combination thereof. The storage device may connect to a device for performing the methods according to the embodiments of the present disclosure via an external port. Furthermore, a separate storage device on a communication network may also connect to a device for performing the methods according to the embodiments of the present disclosure.

In the specific embodiments of the present disclosure, a component included in the present disclosure is expressed in a singular or plural form depending on the presented specific embodiments. However, singular or plural expressions are selected to be suitable for situations presented for convenience of descriptions, and the present disclosure is not limited to elements in a singular or plural form, i.e., an element expressed in a plural form may be configured as a single element, or an element expressed in a singular form may be configured as a plurality of elements.

Claim 1:
An operation method of a user equipment, UE, in a wireless communication system, the operation method comprising:
identifying (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) that an active bandwidth part, BWP, is different from a BWP for a multicast and broadcast service, MBS, service of interest;
transmitting (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>), to a base station, a message indicating the MBS service of interest based on the identification;
receiving (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>), from the base station, based on the message indicating the MBS service of interest, information related to the MBS service of interest; and
receiving (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) the MBS service of interest, based on the information related to the MBS service of interest.