Method and apparatus for supporting MBS in wireless communication system

Abstract

A method and an apparatus for supporting MBS in a wireless communication system are provided. A method performed by a user equipment (UE) in a wireless communication system includes: receiving configuration information for a multicast broadcast service (MBS) via a radio resource control (RRC) release message; entering an RRC inactive state based on the received RRC release message; and receiving the MBS in an RRC inactive state based on the configuration information for the MBS, where the MBS is received via a multicast bearer for the MBS, and where the MBS is received via a multicast bearer for the MBS. At least one of a Packet Data Convergence Protocol (PDCP) entity, a Radio Link Control (RLC) entity, a Medium Access Control (MAC) entity, a Physical Layer entity and a Service Data Adaptation Protocol (SDAP) entity is configured for a multicast bearer of the MBS.

Description

[0001] This application is a divisional application of Chinese patent application No. 202180055675.4, filed on June 14, 2021, entitled "Method and apparatus for supporting MBS in a wireless communication system". Technical Field

[0002] This disclosure relates to a method and apparatus for supporting a multicast or unicast bearer structure in a next-generation mobile communication system. Background Technology

[0003] To meet the growing demand for wireless data services following the commercialization of 4G communication systems, efforts have been made to develop advanced 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are referred to as super-4G networks or post-LTE systems. To achieve high data transmission rates, implementation of 5G communication systems in ultra-high frequency (mmWave) bands (e.g., the 60 GHz band) has been considered. To mitigate radio wave propagation loss and increase transmission distance in ultra-high frequency bands, technologies such as beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO have been discussed in 5G communication systems. Furthermore, to improve the network of the system, technologies such as advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receive interference cancellation have been developed in 5G communication systems. In addition, advanced coding and modulation (ACM) schemes (i.e., hybrid frequency shift keying (FSK) and quadrature amplitude modulation (QAM) (FQAM and sliding window superposition coding (SWSC)) and advanced access technologies (i.e. filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse coded multiple access (SCMA)) have been developed in 5G communication systems.

[0004] Simultaneously, the internet is evolving from a human-centric network where humans generate and use information into an Internet of Things (IoT) network where distributed entities or things send, receive, and process information. Internet of Everything (IoE) technologies, combining IoT with big data processing technologies such as those based on connections to cloud servers, have also emerged. To realize IoT, technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology are required. Therefore, technologies for connecting things, such as sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC), have recently been studied. In the IoT environment, intelligent internet technology (IT) services can be provided to create new value for human life by collecting and analyzing data generated between connected things. Based on the integration and combination of existing information technology (IT) and various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0005] Therefore, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, M2M communication, and MTC have been implemented based on 5G communication technologies such as beamforming, MIMO, and array antennas. As mentioned above, cloud RAN can be applied because big data processing technology can also be seen as an example of the integration of 5G and IoT technologies.

[0006] As mentioned above, with the development of wireless communication systems, various services can be provided, thus requiring a method for seamless service provision. Specifically, a structure or configuration method for multicast or unicast bearers supporting multicast or broadcast services (MBS) is needed, along with a data processing method configured to receive and process MBS data at the physical (PHY) layer, media access control (MAC) layer, radio link control (RLC) layer, or packet data convergence protocol (PDCP) layer. Furthermore, to support MBS based on handover between MBS-supporting base stations or networks, or based on terminal mobility, a method is needed to reconfigure (or switch) multicast bearers to unicast bearers or vice versa.

[0007] The above information is presented as background information only to aid in understanding this disclosure. No determination or assertion is made as to whether any of the above applies to the prior art as disclosed herein. Summary of the Invention

[0008] In next-generation mobile communication systems, to support services such as broadcast / multicast services, mission-critical services, or public safety services, multicast or broadcast services (MBS), multimedia broadcast and multicast services (MBMS), or multicast and broadcast services can be supported. MBS can provide services to terminals via multicast or unicast bearers.

[0009] To support MBS, a structure or configuration method for supporting MBS multicast or unicast bearers is required, as well as a data processing method configured to receive and process MBS data at the physical (PHY) layer, media access control (MAC) layer, radio link control (RLC) layer, or packet data convergence protocol (PDCP) layer.

[0010] In addition, the signaling procedures or operations of the terminal must be specified to ensure continuous support for MBS during Radio Resource Control (RRC) connected mode, RRC idle mode, or RRC inactive mode, or during transitions between these modes.

[0011] In addition, in order to support MBS based on the handover between base stations or networks that support MBS or based on the mobility of terminals, a method is needed to reconfigure (or switch) multicast bearers to unicast bearers or to reconfigure (or switch) unicast bearers to multicast bearers.

[0012] The present disclosure is intended to at least address the aforementioned problems and / or disadvantages, and to provide at least the advantages described below. Therefore, one aspect of the disclosure is to provide a method, performed by a terminal, for properly receiving MBS under the various conditions described above.

[0013] According to one aspect of this disclosure, a method performed by a user equipment (UE) in a wireless communication system includes: receiving configuration information regarding a multicast service (MBS); receiving MBS data in Radio Resource Control (RRC) _Connected mode based on the configuration information; and wherein the MBS data is transmitted to a plurality of UEs including a UE for multicast transmission, or to a UE for unicast transmission; and wherein a Hybrid Automatic Repeat Request (HARQ) retransmission is applied to the transmission of the MBS data.

[0014] MBS bearers include the Service Data Adaptation Protocol (SDAP) entity and the Packet Data Convergence Protocol (PDCP) entity.

[0015] The PDCP entity provides header compression functionality by using Robust Header Compression (ROHC) and PDCP reordering functionality.

[0016] The bearer of MBS includes at least one of Radio Link Control (RLC) Acknowledgment mode (AM) or RLC Unacknowledgment mode (UM) for dynamic switching between unicast and multicast transmissions.

[0017] MBS data is scheduled using the Cell Radio Network Temporary Identifier (C-RNTI) transmitted via unicast and the MBS-RNTI transmitted via multicast.

[0018] According to another aspect of this disclosure, a method performed by a base station in a wireless communication system includes: sending configuration information about a multicast service (MBS) to a user equipment (UE); sending MBS data in Radio Resource Control (RRC) _Connected mode based on the configuration information; and wherein the MBS data is sent to a plurality of UEs including a UE for multicast transmission, or to a UE for unicast transmission, and wherein Hybrid Automatic Repeat Request (HARQ) retransmission is applied to the transmission of the MBS data.

[0019] According to one aspect of this disclosure, a user equipment (UE) in a wireless communication system includes: a transceiver; and at least one processor connected to the transceiver and configured to: receive configuration information regarding a multicast service (MBS); receive MBS data in Radio Resource Control (RRC)_Connected mode based on the configuration information; and wherein the MBS data is transmitted to a plurality of UEs including a UE for multicast transmission, or to a UE for unicast transmission, and wherein Hybrid Automatic Repeat Request (HARQ) retransmission is applied to the transmission of the MBS data.

[0020] According to one aspect of this disclosure, a base station in a wireless communication system includes: a transceiver; and at least one processor connected to the transceiver and configured to: send configuration information about a multicast service (MBS) to a user equipment (UE); transmit MBS data in Radio Resource Control (RRC)_Connected mode based on the configuration information; and wherein the MBS data is transmitted to a plurality of UEs including a UE for multicast transmission, or to a UE for unicast transmission, and wherein Hybrid Automatic Repeat Request (HARQ) retransmission is applied to the transmission of the MBS data.

[0021] According to one aspect of this disclosure, a method performed by a user equipment (UE) in a wireless communication system includes: receiving configuration information for a multicast service (MBS) via a Radio Resource Control (RRC) release message; entering an RRC inactive state based on receiving the RRC release message; and receiving the MBS in the RRC inactive state based on the configuration information for the MBS, wherein the MBS is received via a multicast bearer for the MBS, and wherein at least one of a Packet Data Convergence Protocol (PDCP) entity, a Radio Link Control (RLC) entity, a Media Access Control (MAC) entity, a Physical Layer entity, and a Service Data Adaptation Protocol (SDAP) entity is configured for the multicast bearer of the MBS.

[0022] According to one aspect of this disclosure, a method performed by a base station in a wireless communication system includes: sending configuration information for a multicast broadcast service (MBS) to a user equipment (UE) via a Radio Resource Control (RRC) release message, wherein the RRC release message causes the UE to enter an RRC inactive state; and sending the MBS in the RRC inactive state based on the configuration information for the MBS, wherein the MBS is sent via a multicast bearer for the MBS, and wherein at least one of a Packet Data Convergence Protocol (PDCP) entity, a Radio Link Control (RLC) entity, a Media Access Control (MAC) entity, a Physical Layer entity, and a Service Data Adaptation Protocol (SDAP) entity is configured for the multicast bearer of the MBS.

[0023] According to one aspect of this disclosure, a user equipment (UE) in a wireless communication system includes: a transceiver; and at least one processor operatively connected to the transceiver and configured to: receive configuration information for a multicast broadcast service (MBS) via a Radio Resource Control (RRC) release message; enter an RRC inactive state based on receiving the RRC release message; and receive the MBS in the RRC inactive state based on the configuration information for the MBS, wherein the MBS is received via a multicast bearer for the MBS, and wherein at least one of a Packet Data Convergence Protocol (PDCP) entity, a Radio Link Control (RLC) entity, a Medium Access Control (MAC) entity, a Physical Layer entity, and a Service Data Adaptation Protocol (SDAP) entity is configured for the multicast bearer of the MBS.

[0024] According to one aspect of this disclosure, a base station in a wireless communication system includes: a transceiver; and at least one processor operatively connected to the transceiver and configured to: send configuration information for a Multicast Broadcast Service (MBS) to a User Equipment (UE) via a Radio Resource Control (RRC) release message, wherein the RRC release message causes the UE to enter an RRC inactive state; and send the MBS in the RRC inactive state based on the configuration information for the MBS, wherein the MBS is sent via a multicast bearer for the MBS, and wherein at least one of a Packet Data Convergence Protocol (PDCP) entity, a Radio Link Control (RLC) entity, a Media Access Control (MAC) entity, a Physical Layer entity, and a Service Data Adaptation Protocol (SDAP) entity is configured for the multicast bearer of the MBS.

[0025] Other aspects will be set forth in part in the description which follows, and in part will be apparent from the description or may be learned by practice of the presented embodiments.

[0026] Other aspects, advantages, and key features of this disclosure will become apparent to those skilled in the art from the following detailed description of various embodiments disclosed in conjunction with the accompanying drawings. Attached Figure Description

[0027] The above and other aspects, features, and advantages of specific embodiments of the present disclosure will become apparent from the following description taken in conjunction with the accompanying drawings, wherein:

[0028] Figure 1A This is a diagram illustrating the architecture of a Long Term Evolution (LTE) system according to an embodiment of this disclosure;

[0029] Figure 1B This is a diagram of the radio protocol architecture of an LTE system according to an embodiment of the present disclosure;

[0030] Figure 1C This is a diagram illustrating the architecture of a next-generation mobile communication system according to embodiments of the present disclosure;

[0031] Figure 1D This is a diagram of the radio protocol architecture of a next-generation mobile communication system according to embodiments of the present disclosure;

[0032] Figure 1E This is a diagram illustrating the process of providing services to a terminal in a next-generation mobile communication system by efficiently utilizing a large frequency bandwidth, according to an embodiment of this disclosure.

[0033] Figure 1FThe diagram illustrates the process of a terminal in a next-generation mobile communication system switching from Radio Resource Control (RRC) idle mode to RRC connected mode according to an embodiment of the present disclosure, as well as the method of configuring multiple Bandwidth Parts (BWPs) and configuring a default BWP or a first active BWP.

[0034] Figure 1G This is a diagram of the bearer structure established by a base station or network to support multicast or broadcast services (MBS) for a terminal in RRC connected mode, RRC inactive mode, or RRC idle mode, according to embodiments of this disclosure.

[0035] Figure 1H This is a diagram illustrating a method for demultiplexing received MBS data via a Media Access Control (MAC) layer when a terminal in RRC connected mode, RRC inactive mode, or RRC idle mode receives MBS data (e.g., MBS control data, MBS user data, or general data other than MBS data) via a multicast or unicast bearer supporting MBS, according to an embodiment of this disclosure.

[0036] Figure 1I This is a diagram illustrating a method for reusing MBS data to be transmitted via a MAC entity when a terminal in RRC connected mode, RRC inactive mode, or RRC idle mode transmits MBS data (e.g., MBS control data, MBS user data, or general data other than MBS data) via a multicast or unicast bearer supporting MBS, according to an embodiment of this disclosure.

[0037] Figure 1J This is a diagram of a first signaling process supporting MBS according to an embodiment of this disclosure;

[0038] Figure 1K This is a diagram of a second signaling process supporting MBS according to an embodiment of this disclosure;

[0039] Figure 1L This is a diagram of a third signaling process supporting MBS according to an embodiment of this disclosure;

[0040] Figure 1M This is a diagram of a fourth signaling process supporting MBS according to an embodiment of this disclosure;

[0041] Figure 1N This is a diagram illustrating a situation where general data and MBS data conflict or overlap when a terminal receives general data service and MBS in RRC connection mode, according to an embodiment of this disclosure.

[0042] Figure 10This is a diagram of an efficient signaling process supporting MBS according to an embodiment of the present disclosure;

[0043] Figure 1P This is a diagram illustrating a method for instructing each of a plurality of MBS according to embodiments of the present disclosure;

[0044] Figure 1Q This is a diagram of a method for retransmitting MBS data according to an embodiment of this disclosure;

[0045] Figure 1R This is a diagram of a first handover method or a second handover method in a method for supporting MBS proposed in a next-generation mobile communication system or access layer (AS) according to an embodiment of the present disclosure, wherein the first handover method involves continuously supporting (transmitting or receiving) MBS by switching a multicast service or multicast bearer to a unicast service or unicast bearer, and the second handover method involves continuously supporting (transmitting or receiving) MBS by switching a unicast service or unicast bearer to a multicast service or multicast bearer;

[0046] Figure 1S This is a diagram illustrating the operation of a terminal according to an embodiment of this disclosure;

[0047] Figure 1T A diagram showing the structure of a terminal according to an embodiment of this disclosure; and

[0048] Figure 1U This is a block diagram of Tx / Rx points (TRP) according to an embodiment of the present disclosure.

[0049] Throughout the accompanying drawings, similar reference numerals will be understood to refer to similar parts, components, and structures. Detailed Implementation

[0050] The following description, taken with reference to the accompanying drawings, is intended to aid in a full understanding of the various embodiments of this disclosure as defined by the claims and their equivalents. It includes various specific details to aid understanding, but these details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of this disclosure. Furthermore, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

[0051] The terms and words used in the appended description and claims are not limited to their literal meaning, but are merely those used by the inventors to enable a clear and consistent understanding of this disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of this disclosure is for illustrative purposes only and not intended to limit the disclosure, which is defined by the appended claims and their equivalents.

[0052] It should be understood that, unless the context clearly specifies otherwise, the singular forms “a,” “an,” and “the” include plural references. Thus, for example, the reference to “a component surface” includes the reference to one or more such surfaces.

[0053] Throughout this disclosure, the expression “at least one of a, b or c” indicates only a, only b, only c, a and b, a and c, b and c, a, b and c, or all or variations thereof.

[0054] Examples of terminals may include user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, multimedia system capable of performing communication functions, etc.

[0055] In this disclosure, the controller may also be referred to as a processor.

[0056] Throughout the specification, a layer (or layer device) may also be referred to as an entity.

[0057] In describing this disclosure, detailed descriptions of relevant known functions or configurations may be omitted where such descriptions would unnecessarily obscure the essential points of the disclosure. Hereinafter, embodiments of the disclosure are described with reference to the accompanying drawings.

[0058] For ease of description, the terms used to identify access nodes, network entities, messages, interfaces between network entities, and various types of identification information are illustrative. Therefore, this disclosure is not limited to the terms described below, and other terms referring to entities with equivalent technical meanings may also be used.

[0059] For ease of description, this document uses the terms and names defined in the 3GPP LTE standard. However, this disclosure is not limited to these terms and names and can be applied equivalently to systems conforming to other standards. For ease of description, the term "eNB" as used herein is used interchangeably with the term "gNB." That is, a base station described as an eNB can also represent a gNB.

[0060] Figure 1A This is a diagram illustrating the structure of a Long Term Evolution (LTE) system according to an embodiment of this disclosure.

[0061] refer to Figure 1AThe radio access network of the LTE system includes next-generation base stations (evolved Node Bs, hereinafter referred to as eNBs, Node Bs, or BSs) 1a-05, 1a-10, 1a-15, and 1a-20, a Mobility Management Entity (MME) 1a-25, and a Serving Gateway (S-GW) 1a-30. The UE (or terminal) 1a-35 accesses external networks through eNBs 1a-05 to 1a-20 and S-GW 1a-30.

[0062] refer to Figure 1A eNBs 1a-05 to 1a-20 can correspond to existing NodeBs in the Universal Mobile Telecommunications System (UMTS). eNBs 1a-05 to 1a-20 can connect to UE 1a-35 via radio channels and can play a more complex role than existing NodeBs. In LTE systems, all user services, including real-time services such as Voice over IP (VoIP) via the Internet Protocol, can be served through a shared channel. Therefore, it may be necessary to collect and schedule state information such as the UE's buffer state, available transmission power state, and channel state. This can be handled by eNBs 1a-05 to 1a-20. A single eNB can typically control multiple cells. For example, to achieve a transmission rate of 100 Mbps, an LTE system can use, for example, an Orthogonal Frequency Division Multiplexing (OFDM) scheme as the radio access technology within a 20 MHz bandwidth. Furthermore, an Adaptive Modulation and Coding (AMC) scheme, which determines the modulation scheme and channel coding rate based on the UE's channel state, can be applied. The S-GW 1a-30 is the entity that provides data bearers and can add or release data bearers under the control of the MME 1a-25. The MME 1a-25 is the entity responsible for various control functions and UE mobility management functions, and can be connected to multiple base stations.

[0063] Figure 1B This is a diagram of the radio protocol architecture of an LTE system according to an embodiment of the present disclosure.

[0064] refer to Figure 1B In an LTE system, the radio protocols for each UE and eNB may include Packet Data Convergence Protocol (PDCP) 1b-05 or 1b-40, Radio Link Control (RLC) 1b-10 or 1b-35, Media Access Control (MAC) 1b-15 or 1b-30, and Physical Entity (PHY) 1b-20 or 1b-25. PDCP 1b-05 and 1b-40 can handle operations such as IP header compression / decompression. The main functions of PDCP are summarized below.

[0065] - Header compression and decompression functions (header compression and decompression: ROHC only).

[0066] - User data transfer function (user data transfer).

[0067] - Sequential delivery function (sequential delivery of upper-layer entity PDUs during PDCP reconstruction for RLC AM).

[0068] - Reordering function (for split bearers in DC (RLC AM only): PDCP PDU routing for transmission and PDCP PDU reordering for reception).

[0069] - Repeat detection function (repeated detection of lower-level SDUs during PDCP reconstruction for RLC AM)

[0070] - Retransmission function (for split bearers in DC, retransmit PDCP SDU during handover, and for RLC AM, retransmit PDCP PDU during PDCP data recovery).

[0071] - Encryption and decryption functions (encryption and decryption).

[0072] - Timer-based SDU dropping function (timer-based SDU dropping in the uplink).

[0073] RLC 1b-10 and 1b-35 can perform Automatic Repeat Request (ARQ) operations by reconfiguring PDCP Protocol Data Units (PDUs) to an appropriate size. The main functions of the RLC are summarized below.

[0074] - Data transmission function (upper-layer entity PDU transmission).

[0075] - ARQ function (error correction via ARQ (only for AM data transmission)).

[0076] - Cascading, segmenting and reassembling functions (Cascading, segmenting and reassembling RLC SDU (for UM and AM data transfer only)).

[0077] - Re-segmentation function (re-segmentation of RLC data PDUs (for AM data transmission only)).

[0078] - Reordering function (reorder RLC data PDUs (only for UM and AM data transfer)).

[0079] - Duplicate detection function (Duplicate detection (only for UM and AM data transmission)).

[0080] - Error detection function (protocol error detection (AM data transmission only)).

[0081] - RLC SDU discard function (RLC SDU discard (only for UM and AM data transmission)).

[0082] - RLC Reconstruction Function (RLC Reconstruction).

[0083] MAC 1b-15 and 1b-30 can connect to multiple RLC entities configured in a UE and can perform operations such as multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of the MAC are summarized below.

[0084] - Mapping function (mapping between logical channels and transport channels).

[0085] - Multiplexing and demultiplexing functions (multiplexing MAC SDUs belonging to one or more different logical channels onto a transport channel and delivering them to a physical entity in a transport block (TB) / demultiplexing MAC SDUs belonging to one or more different logical channels from a transport block delivered to a physical entity on a transport channel)

[0086] - Scheduling information reporting function (Scheduling information report).

[0087] - Hybrid Automatic Repeat Request (HARQ) function (error correction via HARQ).

[0088] - Functionality for handling priorities between logical channels (priority handling between logical channels of a UE).

[0089] - Functionality for handling priorities among UEs (priority handling among UEs via dynamic scheduling).

[0090] - MBMS Service Identification Function (MBMS Service Identification).

[0091] - Transmission format selection function (transmission format selection).

[0092] - Padding function (padding).

[0093] PHY entities 1b-20 and 1b-25 can perform channel coding and modulation operations on upper-layer entity data, convert the channel-coded and modulated upper-layer entity data into OFDM symbols, and transmit the OFDM symbols on the radio channel, or demodulate the OFDM symbols received through the radio channel, perform channel decoding on the demodulated OFDM symbols, and transmit the channel-decoded OFDM symbols to the upper-layer entity.

[0094] Figure 1C This is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

[0095] refer to Figure 1C The radio access network for next-generation mobile communication systems (hereinafter referred to as New Radio (NR) systems or 5G systems) includes the next-generation base station (New Radio Node B, hereinafter referred to as NR gNB or NR BS) 1c-10 and the New Radio Core Network (NR CN) 1c-05. New Radio User Equipment (NR UE) (or terminal) 1c-15 can access external networks through NR gNB 1c-10 and NR CN 1c-05.

[0096] refer to Figure 1C The NR gNB 1c-10 corresponds to the eNB in ​​existing LTE systems. The NR gNB 1c-10 can connect to the NR UE 1c-15 via radio channels and can provide services superior to existing Node Bs. In next-generation mobile communication systems, all user services can be served through a shared channel. Therefore, a device may be needed to collect and schedule state information such as the NR UE's buffer state, available transmission power state, and channel state. This can be handled by the NR gNB 1c-10. One NR gNB 1c-10 can typically control multiple cells. Compared to existing LTE, next-generation mobile communication systems can have bandwidths exceeding the current maximum to achieve ultra-high-speed data transmission and can additionally utilize beamforming technology by using OFDM as the radio access technology. Furthermore, an AMC scheme that determines the modulation scheme and channel coding rate based on the NR UE's channel state can be applied. The NR CN 1c-05 can perform functions such as mobility support, bearer configuration, and quality of service (QoS) configuration. The NR CN 1c-05 is the entity responsible for various control functions and the NR UE's mobility management functions and can connect to multiple base stations. Furthermore, the next-generation mobile communication system is interoperable with existing LTE systems, and the NR CN 1c-05 can connect to the MME 1c-25 via a network interface. The MME 1c-25 can connect to the eNB 1c-30, i.e., existing base stations.

[0097] Figure 1D This is a diagram of the radio protocol architecture of a next-generation mobile communication system according to an embodiment of the present disclosure.

[0098] refer to Figure 1D The radio protocols in each of the UE and NR gNB in ​​the next-generation mobile communication system include NRSDAP 1d-01 or 1d-45, NR PDCP entity 1d-05 or 1d-40, NR RLC entity 1d-10 or 1d-35, NR MAC 1d-15 or 1d-30, and physical entity (PHY) 1d-20 or 1d-25.

[0099] The main functions of NR SDAP 1d-01 or 1d-45 may include one or more of the following functions.

[0100] - User data transmission function (user plane data transmission).

[0101] - The function of mapping between QoS flows and data bearers in the uplink (UL) and downlink (DL) (mapping between QoS flows and data radio bearers (DRB) in DL and UL).

[0102] - Functionality to mark QoS flow IDs in UL and DL (mark QoS flow IDs in DL and UL packets).

[0103] - The function of mapping reflected QoS streams to data bearers of UL SDAP PDUs (mapping of reflected QoS streams to DRBs of UL SDAP PDUs).

[0104] Regarding SDAP entities, the UE can receive RRC messages to configure whether to use the SDAP entity header or its functionality for each PDCP entity, bearer, or logical channel. Furthermore, when configuring the SDAP header, the 1-bit Non-Access Stratum (NAS) reflected QoS indicator and 1-bit Access Stratum (AS) reflected QoS indicator in the SDAP header can instruct the UE to update or reconfigure the mapping information between QoS flows and data bearers in the UL and DL. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used for data processing priority, scheduling information, etc., to support efficient service.

[0105] The main functions of NR PDCP entities 1d-05 and 1d-40 may include some of the following functions.

[0106] - Header compression and decompression functions (header compression and decompression: ROHC only).

[0107] - User data transfer function (user data transfer).

[0108] - Sequential delivery function (sequentially delivers upper-level entity PDUs).

[0109] - Out-of-order delivery function (delivers upper-level entity PDUs out of order).

[0110] - Reordering function (for reordering received PDCP PDUs).

[0111] - Duplicate detection function (duplicate detection underlying SDU)

[0112] - Retransmission function (retransmit PDCP SDU).

[0113] - Encryption and decryption functions (encryption and decryption).

[0114] - Timer-based SDU dropping function (timer-based SDU dropping in the uplink).

[0115] The reordering function of NR PDCP entities 1d-05 and 1d-40 can refer to the function of reordering PDCP PDUs received from the lower layer in sequence based on the PDCP sequence number (SN). The reordering function of NR PDCP entities 1d-05 and 1d-40 can include the function of sending data to the upper layer entity in the reordered order, the function of sending data immediately regardless of order, the function of reordering PDCP PDUs and recording lost PDCP PDUs, the function of reporting the status of lost PDCP PDUs to the sender, and the function of requesting retransmission of lost PDCP PDUs.

[0116] The main functions of NR RLC entities 1d-10 and 1d-35 may include some of the following functions.

[0117] - Data transmission function (upper-layer entity PDU transmission).

[0118] - In-sequence delivery function (delivers upper-level entity PDUs sequentially).

[0119] - Out-of-sequence delivery function (delivers upper-level entity PDUs out of order).

[0120] - ARQ function (error correction via ARQ).

[0121] - Cascading, segmenting, and reassembling capabilities (Cascading, segmenting, and reassembling RLC SDU).

[0122] - Resegmentation function (resegmentation of RLC data PDU).

[0123] - Reordering function (reorder RLC data PDUs).

[0124] - Duplicate detection function (duplicate detection).

[0125] - Error detection function (protocol error detection).

[0126] - RLC SDU discard function (RLC SDU discard).

[0127] - RLC Reconstruction Function (RLC Reconstruction).

[0128] The sequential delivery function of NR RLC entities 1d-10 and 1d-35 refers to the function of sequentially sending RLC SDUs received from the lower layer to the upper layer entity. When an original single RLC SDU is split into multiple RLC SDUs and multiple RLC SDUs are received, the sequential delivery function of the NR RLC entity can include the function of reassembling the received RLC SDUs and sending the reassembled RLC SDUs, the function of reordering the received RLC PDUs based on the RLC SN or PCDP SN, the function of reordering RLCPDUs and recording lost RLC PDUs, the function of reporting the status of lost RLC PDUs to the sender, and the function of requesting retransmission of lost RLC PDUs. When there are lost RLC SDUs, the sequential delivery function of NR RLC entities 1d-10 and 1d-35 can include sequentially sending only the RLC SDUs up to the lost RLC SDU to the upper layer entity. Furthermore, when a lost RLC SDU exists but a specific timer expires, the sequential delivery function of NR RLC entities 1d-10 and 1d-35 can include sequentially sending all RLC SDUs received before the timer started to the upper-layer entity. Alternatively, when a lost RLC SDU exists and a specific timer expires, the sequential delivery function of NR RLC entities 1d-10 and 1d-35 can include sequentially sending all RLC SDUs received to date to the upper-layer entity. Additionally, NR RLC entities 1d-10 and 1d-35 can process RLC PDUs in the order they were received (according to the order of arrival, regardless of sequence number and order number), and send processed RLC PDUs to the PDCP entity out of order (out-of-order delivery). When the received RLC PDU is a segment, segments stored in a buffer or to be received in the future can be received, reconfigured into a complete RLC PDU, and processed and sent to the PDCP entity. NR RLC entities 1d-10 and 1d-35 may not include cascading functionality, and cascading functionality may be performed by NR MAC entities, or may be replaced by multiplexed functionality of NR MAC entities.

[0129] The out-of-order delivery function of NR RLC entities 1d-10 and 1d-35 can refer to the function of sending RLC SDUs received from the lower layer directly to the upper layer entity without regard to the order. When an RLC SDU is received after being split into multiple RLC SDUs, it can include the function of reassembling and sending the split and received RLC SDUs, as well as the function of storing the RLC SN or PDCP SN of the received RLC PDUs, reordering RLC PDUs, and recording lost RLC PDUs.

[0130] NR MAC 1d-15 and 1d-30 can connect to multiple NR RLC entities configured in a UE, and the main functions of NRMAC 1d-15 and 1d-30 may include some of the following functions.

[0131] - Mapping function (mapping between logical channels and transport channels).

[0132] - Multiplexing and demultiplexing functions (multiplexing / demultiplexing MAC SDU)

[0133] - Scheduling information reporting function (Scheduling information report).

[0134] - HARQ function (error correction via HARQ).

[0135] - Functionality for handling priorities between logical channels (priority handling between logical channels of a UE).

[0136] - Functionality for handling priorities among UEs (priority handling among UEs via dynamic scheduling).

[0137] - MBMS Service Identification Function (MBMS Service Identification).

[0138] - Transmission format selection function (transmission format selection).

[0139] - Fill function (fill).

[0140] The NR PHY layers 1d-20 and 1d-25 can perform channel coding and modulation on upper-layer entity data, convert the channel-coded and modulated upper-layer entity data into OFDM symbols, and transmit the OFDM symbols on the radio channel. Alternatively, they can demodulate OFDM symbols received through the radio channel, perform channel decoding on the demodulated OFDM symbols, and transmit the channel-decoded OFDM symbols to the upper-layer entity.

[0141] In next-generation mobile communication systems, ultra-high frequency bands can be used, thus significantly increasing the frequency bandwidth. However, from the perspective of UE implementation, this requires high implementation complexity and incurs significant costs to support the entire frequency range of the significantly increased bandwidth. Therefore, in next-generation mobile communication systems, the concept of Bandwidth Parts (BWPs) can be introduced, and multiple BWPs can be configured in a single cell (Special Cell (SPcell) or Secondary Cell (SCell)). Data can be transmitted and received in one or more BWPs according to the instructions of the base station.

[0142] This disclosure provides a state transition method considering the state of an SCell and multiple BWPs configured in the SCell, or a BWP switching method and detailed operations when a dormant BWP is used. Furthermore, this disclosure provides methods for managing idle modes and state transitions at the BWP level, methods for switching BWPs, and detailed operations for each BWP based on the state of each SCell, and the state or mode (active, inactive, or idle) of each BWP.

[0143] Furthermore, according to embodiments of this disclosure, for each DL or each UL, multiple BWPs can be configured in a cell (SPCell, primary cell (PCell), primary SCell (PSCell), or SCell), and active BWPs (active DL or UL BWPs), dormant BWPs (dormant DL BWPs), or inactive BWPs (inactive or deactivated DL / UL BWPs) can be configured and operated by switching BWPs. That is, for a cell, a DL BWP or UL BWP can be switched to an active state; therefore, by using a method similar to carrier integration, the data transmission rate can be increased. Furthermore, by switching or turning a DL BWP to a dormant BWP, the UE can avoid performing Physical Downlink Control Channel (PDCCH) monitoring on the aforementioned cell to reduce battery consumption, and the UE can perform channel measurements on the DL BWP and report the results to subsequently support rapid activation of the cell or BWP. Additionally, by switching a DL (or UL) BWP to an inactive state in a cell, the UE's battery consumption can be reduced. State transitions or handovers of each BWP relative to each cell can be configured or indicated using RRC messages, MAC control elements (CE), or downlink control information (DCI) of the PDCCH.

[0144] In this disclosure, BWP can be used without distinguishing between UL and DL, and can refer to each of the UL BWP and DL BWP based on context.

[0145] In this disclosure, links can be used without distinguishing between UL and DL, and each of UL and DL can be referred to based on context.

[0146] In this disclosure, a dormant BWP can be configured or employed for the SCell of a UE performing carrier integration technology, and the PDCCH can be ignored in the dormant BWP to reduce battery consumption. Furthermore, channel measurements (e.g., Channel State Information (CSI) or Channel Quality Information (CQI)) or beam measurements, beam tracking, or beam manipulation can be performed in the dormant BWP. Therefore, when data transmission is required, the dormant BWP can be switched to or activated as a normal BWP to quickly initiate data transmission in the normal BWP. For SPCells (PCells of MCGs or PCells of SCGs (or PSCells)) or SCells configured with PUCCHs (which must continuously monitor signals, send or receive feedback, or identify and maintain synchronization), a dormant BWP can be left unconfigured or unapplied.

[0147] This disclosure provides various embodiments for operating a dormant BWP for a UE’s SCell using DCI, MAC CE, or RRC messages based on PDCCH.

[0148] A network or base station can configure a UE's SPCell (PCell and PSCell) and multiple SCells. When a UE communicates with one base station, the SPCell can refer to the PCell, and when a UE communicates with two base stations (a primary base station and a secondary base station), it can refer to the PCell of the primary base station or the PSCell of the secondary base station. The PCell or PSCell indicates the primary cell used by each MAC entity when the UE and the base station communicate with each other, and represents the cell used for adjusting synchronization timing, performing random access, sending HARQ ACK / NACK feedback based on PUCCH transmission resources, and exchanging most control signals. The technique of a base station operating multiple SCells with SPCells to increase transmission resources and increase UL or DL ​​data transmission resources is called carrier integration technology.

[0149] When a UE is configured with an SPCell and multiple SCells via an RRC message, the UE can configure the state or mode of the BWP for each SCell and each SCell via an RRC message, MAC CE, or DCI of the PDCCH. The state or mode of an SCell can be configured as active mode, active state, deactivated mode, or deactivated state. An active or active state of an SCell indicates that in an active or active SCell, the UE in the BWP of an SCell other than an active BWP, an active normal BWP, or an active dormant BWP can exchange UL data and DL data with the base station, can monitor the PDCCH to identify the base station's indication, can perform channel measurements on the DL of an active or active SCell (or the BWP of an SCell other than an active BWP, an active normal BWP, or an active dormant BWP), can periodically report measurement information to the base station, and can periodically send pilot signals (SRS) to the base station so that the base station can perform UL channel measurements.

[0150] However, the SCell being in deactivated mode or deactivated state can indicate that the BWP configured in the SCell is inactive, the configured BWP is not activated, or there is no activated BWP among the configured BWPs. Therefore, the UE may not exchange data with the base station, may not monitor the PDCCH to identify the base station's indication, may not perform channel measurements, may not perform measurement reports, and may not send pilot signals.

[0151] Therefore, to activate a SCell in deactivated mode, the base station first configures frequency measurement configuration information for the UE using RRC messages, and the UE can then perform cell or frequency measurements based on this configuration information. Furthermore, the base station can receive cell or frequency measurement reports from the UE and then activate the deactivated SCell based on the frequency / channel measurement information. Consequently, a significant delay occurs when the base station activates carrier integration technology for the UE and begins data transmission and reception.

[0152] In this disclosure, in order to reduce the power consumption of the UE and quickly start data transmission or reception, an idle mode or sleep state for the BWP for each active SCell (or active SCell) is provided, or a configuration or adoption of a sleep BWP for each active SCell is provided.

[0153] In an idle BWP or a dormant BWP in an active SCell, or when a dormant BWP is activated, the UE may not exchange data with the base station, may not monitor the PDCCH to identify base station indications, or may not transmit pilot signals. However, the UE can perform channel measurements and can periodically or, depending on the base station configuration, report the measurement results for the frequency / cell / channel. Therefore, because the UE does not monitor the PDCCH and transmit pilot signals in a dormant BWP in an active SCell, power consumption can be reduced compared to a normal BWP in an active SCell (or a BWP other than a dormant BWP), or compared to when a normal BWP in an active SCell (or a BWP other than a dormant BWP) is activated. Furthermore, unlike when the SCell is deactivated, the UE can report channel measurements; therefore, the base station can quickly activate a normal BWP in an active SCell based on the measurement report or the measurement report of a dormant BWP in an active SCell to quickly utilize carrier integration technology, thus reducing transmission latency.

[0154] Therefore, in this disclosure, SCell being in active mode or active state can mean that in an active or active SCell, the UE in the BWP of the SCell (excluding active BWP, active normal BWP, or active dormant BWP) can exchange UL data and DL data with the base station, can monitor the PDCCH to identify the base station's indication, can perform channel measurements on the DL of the active or active SCell (or the BWP of the SCell other than active BWP, active normal BWP, or active dormant BWP), can periodically report measurement information to the base station, and can periodically send pilot SRS to the base station so that the base station can perform UL channel measurements. Furthermore, in this disclosure, SCell being in active mode or active state can mean that the UE in an active dormant BWP in an active or active SCell can not exchange UL data or DL ​​data with the base station, and can not monitor the PDCCH to identify the base station's indication, but the UE can perform channel measurements on the DL of the active dormant BWP in the active or active SCell, and can periodically report measurement information to the base station.

[0155] Furthermore, in this disclosure, a dormant BWP can indicate the state of a BWP, or a dormant BWP can be used as a term indicating the logical concept of a particular BWP. Therefore, a dormant BWP can be activated, deactivated, or switched. For example, an instruction to switch a second active BWP in a first SCell to a dormant BWP, an instruction to deactivate the first SCell or switch the first SCell to idle mode, or an instruction to activate a dormant BWP in the first SCell can be interpreted as having the same meaning.

[0156] Furthermore, in this disclosure, a normal BWP can indicate, via RRC messages, the BWPs configured in each SCell of the UE, excluding the dormant BWP. In a normal BWP, the UE can exchange UL data or DL ​​data with the base station, monitor the PDCCH to identify indications from the base station, perform channel measurements on the DL, periodically report measurement information to the base station, and periodically send pilot SRS to the base station so that the base station can perform UL channel measurements. Additionally, a normal BWP can represent a first active BWP, a default BWP, a first active BWP from a dormant state, or an initial BWP.

[0157] Furthermore, among the BWPs configured in each SCell of the UE, only the sleep BWP is configured for the DL. According to another method, among the BWPs configured in each SCell of the UE, a sleep BWP can be configured for either the UL or the DL.

[0158] Figure 1E This is a diagram illustrating the process of providing services to a terminal in a next-generation mobile communication system by efficiently utilizing a large frequency bandwidth, according to an embodiment of this disclosure.

[0159] refer to Figure 1E It describes how next-generation mobile communication systems can efficiently use large frequency bandwidth to provide services to UEs with different capabilities or categories, and allow UEs to reduce power consumption.

[0160] A cell to which a base station provides service may receive service in a significantly large frequency band, 1e-05. However, in order to provide service to UEs with different capabilities, the large frequency band can be divided into multiple BWPs and managed as a single cell.

[0161] First, the pre-activated UE can search the entire frequency band provided by the operator (PLMN) in units of predetermined resource blocks (e.g., 12 resource blocks (RBs)). That is, the UE can begin searching for the primary synchronization sequence (PSS) / secondary synchronization sequence (SSS) across the entire system bandwidth in units of RB 1e-10. When the UE searches for PSS / SSS 1e-01 or 1e-02 in units of RBs and detects a signal, the UE can read and interpret (decode) the signal to identify the boundary between subframes and radio transmission resource frames. Therefore, subframes can be identified in 1 ms units, and the base station can synchronize with the DL signal. RBs can be defined in two-dimensional units based on the size of predetermined frequency and time resources. For example, based on time resources, an RB can be defined as a unit of 1 ms, and based on frequency resources, an RB can be defined as a unit of 12 subcarriers (1 carrier x 15 kHz = 180 kHz). After synchronization is complete, the UE can identify the Master System Information Block (MIB) or Minimum System Information (MSI) to identify the Control Resource Set (CORESEST) information and the Initial Access BWP information (1e-15 and 1e-20). CORESEST information refers to the location of time / frequency transmission resources through which control signals are transmitted from the base station, and for example, indicates the location of transmission resources through which PDCCH is transmitted. That is, CORESEST information can indicate where the first system information (System Information Block 1 (SIB1)) is transmitted from, and CORESEST information can indicate via which frequency / time resources the PDCCH is transmitted. When the UE reads the first system information, the UE can identify information about the initial BWP. As described above, the UE can complete the synchronization of the DL signal with the base station, and when the UE can receive control signals, in the initial BWP of the cell where the UE is camped, the UE can perform a random access procedure, request RRC connection configuration, receive RRC messages, and perform RRC connection configuration.

[0162] In RRC connection configuration, multiple BWPs can be configured for each cell (PCell, PSCell, SPCell, or SCell). Within a single cell, multiple BWPs can be configured for the DL, and additionally, multiple BWPs can be configured for the UL.

[0163] Multiple BWPs can be indicated or configured via BWP identifiers to be used as the initial BWP, default BWP, first active BWP, hibernation BWP, or the first active BWP from a hibernation state.

[0164] The initial BWP can be defined as a cell-specific BWP existing in each cell, and can be used as a BWP that is used when a UE initially accessing the cell configures a connection with the cell through a random access procedure or performs synchronization after connection configuration. Furthermore, for each cell, the base station can configure each of the initial downlink BWP to be used in the DL and the initial uplink BWP to be used in the UL. Additionally, configuration information regarding the initial BWP can be broadcast via the first system information (System Information 1, SIB1) indicated by CORESET, and the base station can reconfigure the initial UL BWP to UEs accessing the connection using an RRC message. Furthermore, the initial BWP can be used by specifying the number 0 for the BWP identifier in both the UL and DL. That is, all UEs accessing the same cell can use the initial BWP by equivalently specifying the initial BWP via a BWP identifier with the number 0. This is because, during random access, the contention-based random access procedure can be simplified when the base station can send a Random Access Response (RAR) message using the initial BWP that can be read by all UEs.

[0165] The first active BWP can be configured differently for each UE (UE-specific) and can be indicated from among multiple BWPs by specifying a BWP identifier. The first active BWP can be configured for each of the DL and UL, and each of the first active DL BWP and the first active UL BWP can be configured via a BWP identifier. When multiple BWPs are configured in a cell, the first active BWP can be used to indicate which BWP will be activated and used first. For example, when a UE is configured with a PCell or PSCell and multiple SCells, and multiple BWPs are configured in the PCell, PSCell, or SCell, when the PCell, PSCell, or SCell is activated, the UE can activate and use the first active BWP from among the multiple BWPs configured in the PCell, PSCell, or SCell. That is, the UE can activate and use the first active DL BWP for the DL and the first active UL BWP for the UL.

[0166] When the UE receives an instruction to activate a deactivated SCell or BWP via an RRC message, MAC control information, or DCI, it can perform the following operations: the UE switches the current DL BWP or activates the DL BWP in the SCell to activate the current DL BWP or activate the DL BWP in the SCell as the first active DL BWP (or the BWP configured or indicated via an RRC message), or switches the current UL BWP or activates the UL BWP in the SCell to activate the current UL BWP or activate the UL BWP in the SCell as the first active UL BWP (or the BWP configured or indicated via an RRC message). Furthermore, the UE can perform this operation when it receives an instruction to switch an SCell or BWP to a sleep state via an RRC message, MAC control information, or DCI. This is because when the current DL BWP or active DL BWP in an active SCell or BWP is switched to be activated as the first active DL BWP (or the BWP configured or indicated by using RRC messages) or the UL BWP is switched to be activated as the first active UL BWP (or the BWP configured or indicated by using RRC messages), even when performing channel measurements and reporting in a dormant state, frequency / channel measurements must be performed and reported against the first active DL / UL BWP so that the base station can efficiently use carrier integration technology.

[0167] A default BWP can be configured differently for each UE (UE-specific) and can be indicated from multiple BWPs by specifying a BWP identifier. A default BWP can be configured only for DL. The default BWP can be used as the BWP to which the active BWP among multiple downlink BWPs will fall back after a predetermined time. For example, a BWP deactivation timer (BWP inactivity timer) can be configured for each cell or each BWP using RRC messages, and the BWP deactivation timer can be started or restarted when data transmission and reception occur in an active BWP other than the default BWP, or when the active BWP switches to another BWP. When the BWP deactivation timer expires, the UE can fall back or switch the active DLBWP in the cell to the default BWP. A handover can represent the process of deactivating the currently active BWP and activating the BWP indicating the handover, and the handover can be triggered via RRC messages, MAC control information (MAC CE), or L1 signaling (DCI of PDCCH). Switching can be triggered by indicating the BWP to switch to or activate, and the BWP can be indicated by a BWP identifier (e.g., 0, 1, 2, 3, or 4).

[0168] The reason for using the default BWP only for DL ​​is that, for each cell, the base station can allow the UE to fall back to the default BWP after a specific period of time to receive instructions from the base station (e.g., DCI of the PDCCH), thus simplifying base station scheduling. For example, when the base station configures the default BWP for a UE accessing a cell as the initial BWP, after a specific period of time, the base station can execute scheduling instructions only for the initial BWP. When no default BWP is configured in the RRC message, the initial BWP can be considered the default BWP, and the BWP can fall back to the initial BWP when the BWP deactivation timer expires.

[0169] According to another method, in order to increase the flexibility of the base station implementation, a default BWP can also be defined and configured for UL, and can be used in the same way as the default BWP for DL.

[0170] A dormant BWP refers to a BWP in idle mode or a dormant BWP in an active SCell. When a dormant BWP is active, depending on the base station configuration, the UE may not exchange data with the base station, may not monitor the PDCCH to identify base station indications, or may not transmit pilot signals. However, it can perform channel measurements and report measurement results periodically or when events occur for the measured frequency / cell / channel. Therefore, because the UE does not monitor the PDCCH and transmit pilot signals in a dormant BWP in an active SCell, power consumption can be reduced compared to a normal BWP in an active SCell (or a BWP other than a dormant BWP), or compared to when a normal BWP in an active SCell (or a BWP other than a dormant BWP) is activated. Furthermore, unlike when the SCell is deactivated, the UE can report channel measurements. Therefore, the base station can quickly activate a normal BWP in an active SCell based on measurement reports or measurement reports from a dormant BWP in an active SCell to quickly utilize carrier integration technology, thus reducing transmission latency.

[0171] The first active BWP that is switched and activated from a dormant state or a dormant BWP (or a first active non-dormant BWP or a BWP configured or indicated by using an RRC message) can be a BWP that the UE must activate by switching the current or active BWP in the active SCell, or a BWP that the UE must activate from a dormant state configured via an RRC message, according to the following indications: when the UE operates a BWP in an active SCell as a dormant BWP, the active BWP in the active SCell is a dormant BWP, or the BWP in the SCell is converted to a dormant BWP, an indication from the base station to the UE via a DCI, MAC CE, or RRC message of the PDCCH to switch the BWP in the active SCell from a dormant BWP to a normal BWP (or a BWP other than a dormant BWP); an indication to switch or convert the active BWP in the dormant BWP to a normal BWP; or an indication to switch, convert, or activate the active BWP in the dormant BWP to a normal BWP (e.g., the first active BWP activated from a dormant state).

[0172] Figure 1F The diagram illustrates the process of a UE transitioning from RRC idle mode to RRC connected mode in a next-generation mobile communication system according to embodiments of the present disclosure, as well as the method of configuring multiple BWPs and configuring a default BWP or a first active BWP.

[0173] A cell to which a base station provides service can receive services over a significantly large frequency band. First, the UE can search the entire frequency band provided by the operator (PLMN) in units of predetermined resource blocks (e.g., 12 RBs). That is, the UE can begin searching the entire system bandwidth for the PSS / SSS in RB units. When the UE searches for the PSS / SSS in RB units and detects a signal, the UE can read and interpret (decode) the signal to identify the boundary between subframes and radio transmission resource frames. After synchronization is complete, the UE can read the system information of the currently camped cell. That is, the UE can identify the MIB or MSI to identify CORESET information and read the system information to identify information about the initial BWP (1f-01 and 1f-05). CORESET information refers to the location of time / frequency transmission resources through which control signals are transmitted from the base station, and for example, indicates the location of transmission resources through which PDCCH is transmitted.

[0174] As described above, when the UE completes DL synchronization with the base station and can receive control signals, the UE can perform a random access procedure in the initial BWP, request RRC connection configuration, receive RRC messages, and perform RRC connection configuration (1f-10, 1f-15, 1f-20, 1f-25 and 1f-30).

[0175] After the default RRC connection configuration is complete, the base station can send an RRC message to the UE to query UE capabilities and identify UE capabilities (UECapabilityEnquiry, 1f-35). Alternatively, the base station can query the MME or AMF to identify UE capabilities. This is because the MME or AMF can store information about UE capabilities when the UE was previously connected. When the information about UE capabilities required by the base station is not available, the base station can request such information from the UE.

[0176] The base station can send RRC messages to the UE to identify the UE's capabilities, thereby identifying the UE's performance, such as the range of frequency bands the UE can read or the frequency domain the UE can read. Furthermore, after identifying the UE's performance, the base station can configure an appropriate BWP for the UE. When the UE receives an RRC message inquiring about its capabilities, the UE can respond to the RRC message by indicating the range of bandwidth it supports or the range of bandwidth supported by the current system bandwidth, either via an offset from the reference center frequency, by directly indicating the start and end points of the supported frequency bandwidth, or via the center frequency and bandwidth (1f-40).

[0177] BWPs can be configured via RRC Setup, RRC Resume, or RRC Reconfiguration messages (1f-45) configured through an RRC connection. RRC messages can include configuration information about the PCell, PSCell, or multiple SCells, and multiple BWPs can be configured for each cell (PCell, PSCell, or SCell). When multiple BWPs are configured for each cell, multiple BWPs can be configured for use with the DL (Deep Node) of each cell. In the case of an FDD system, multiple BWPs for use with the UL (Upper Node) of each cell can be configured separately from the DL BWPs. In the case of a TDD system, multiple BWPs can be configured for use by both the DL and UL of each cell.

[0178] The information used to configure the BWP for each cell (PCell, PSCell, or SCell) may include some of the following information.

[0179] - DL BWP configuration information for the community.

[0180] - Initial DL BWP configuration information.

[0181] - Information about the configuration of multiple BWPs and the BWP identifier (ID) corresponding to each BWP.

[0182] - Information about the initial state configuration of the cell's DL BWP (e.g., active, dormant, or deactivated state).

[0183] - Indicates the BWP ID of the first active DL BWP.

[0184] - Indicates the BWP ID of the default BWP.

[0185] - Configuration information used for PDCCH monitoring for each BWP. For example, CORESET information, search space resource information, or information about PDCCH transmission resources, period, or subframe number.

[0186] - For each BWP in the BWP configuration information, indicate the BWP ID of the hibernating BWP, or a 1-bit indicator for the hibernating BWP.

[0187] - For each BWP in the BWP configuration information, indicate the BWP ID of the first active BWP activated from the dormant state, or a 1-bit indicator of the first active BWP activated from the dormant state.

[0188] - BWP deactivates timer configuration and timer values.

[0189] - UL BWP configuration information for the community.

[0190] - Initial UL BWP configuration information.

[0191] - Configuration information for multiple BWPs and the BWP ID corresponding to each BWP.

[0192] - Initial state configuration information of the cell's DL BWP (e.g., active state, dormant state, or deactivated state).

[0193] - For each BWP in the BWP configuration information, indicate the BWP ID of the hibernating BWP, or a 1-bit indicator of the hibernating BWP.

[0194] - Indicates the BWP ID of the first active UL BWP.

[0195] The configured initial BWP, default BWP, or first active BWP can be used for the following purposes and can be operated according to the purposes described below.

[0196] The initial BWP can be defined as a cell-specific BWP existing in each cell, and can be used as a BWP that is configured to connect to the cell by the UE initially accessing the cell through a random access procedure or when performing synchronization after connection configuration. Furthermore, for each cell, the base station can configure each of the initial downlink BWP to be used in the DL and the initial uplink BWP to be used in the UL. Additionally, configuration information regarding the initial BWP can be broadcast via the first system information (System Information 1, SIB1) indicated by CORESET, and the base station can reconfigure the initial UL BWP to the UE accessing the connection using an RRC message. Furthermore, the initial BWP can be used by specifying the number 0 for the BWP identifier in both the UL and DL. That is, all UEs accessing the same cell can use the initial BWP by equivalently specifying the initial BWP via a BWP identifier with the number 0. This is because, during the random access procedure, the contention-based random access procedure can be simplified when the base station can send a Random Access Response (RAR) message using the initial BWP that can be read by all UEs.

[0197] The first active BWP can be configured differently for each UE (UE-specific) and can be indicated from among multiple BWPs by specifying a BWP identifier. The first active BWP can be configured for each of the DL and UL, and each of the first active DL BWP and the first active UL BWP can be configured via a BWP identifier. When multiple BWPs are configured in a cell, the first active BWP can be used to indicate which BWP will be activated and used first. For example, when a UE is configured with a PCell or PSCell and multiple SCells, and multiple BWPs are configured in the PCell, PSCell, or SCell, when the PCell, PSCell, or SCell is activated, the UE can activate and use the first active BWP from among the multiple BWPs configured in the PCell, PSCell, or SCell. That is, the UE can activate and use the first active DL BWP for the DL and the first active UL BWP for the UL.

[0198] When the UE receives an instruction via RRC message, MAC CE, or PDCCH DCI to activate a BWP in a specific active SCell or a BWP in a deactivated or dormant state, or an instruction to switch or activate a deactivated or dormant BWP as a normal BWP, it can perform the following operations: the UE switches the current DL BWP or activates the DL BWP in the SCell to activate the current DL BWP or activate the DL BWP in the SCell as the first active DL BWP (or a BWP configured or indicated via RRC message), or switches the current UL BWP or activates the UL BWP in the SCell to activate the current UL BWP or activate the UL BWP in the SCell as the first active UL BWP (or a BWP configured or indicated via RRC message). Furthermore, when the UE receives an instruction via RRC message, MAC CE, or PDCCH DCI to convert an active SCell or BWP to a dormant state, or to switch an active SCell or BWP to a dormant BWP, the UE can switch or activate the BWP as a dormant BWP, or may choose not to activate the BWP.

[0199] Not activating, switching to a dormant BWP, or activating a dormant BWP can indicate that the operations provided in the dormant state according to this disclosure are performed. That is, the UE can refrain from PDCCH monitoring and can perform channel measurements on the DL BWP (or dormant BWP) and report the measurement results to the base station. According to another method, when the SCell is activated or the BWP is activated or switched to a normal BWP, the initial active DL BWP can be activated by switching the DL BWP, and the initial active UL BWP can be activated by switching the UL BWP. Therefore, the dormant BWP can be configured as an initial active DL BWP, an initial active UL BWP, or a default BWP. The default BWP can be configured differently for each UE (UE-specific) and can be indicated from multiple BWPs by specifying a BWP ID. The default BWP can be configured only for DL. The default BWP can be used as the active BWP among multiple downlink BWPs that will fall back to its BWP after a predetermined time. For example, a BWP deactivation timer (BWP inactivity timer) can be configured for each cell or each BWP using RRC messages. This timer can be started or restarted when data transmission and reception occur in an active BWP other than the default BWP, or when an active BWP switches to another BWP. When the BWP deactivation timer expires, the UE can fall back or switch the active DL BWP in the cell to the default BWP. A handover can represent the process of deactivating the currently active BWP and activating the BWP indicating the handover, and the handover can be triggered via RRC messages, MAC control information (MAC CE), or L1 signaling (DCI of PDCCH). A handover can be triggered by indicating the BWP to switch to or activate, and the BWP can be indicated by a BWP identifier (e.g., 0, 1, 2, 3, or 4).

[0200] The reason for using the default BWP only for DL ​​is that, for each cell, the base station can allow the UE to fall back to the default BWP after a specific period of time to receive instructions from the base station (e.g., DCI of the PDCCH), thus simplifying base station scheduling. For example, when the base station configures the default BWP for a UE accessing a cell as the initial BWP, after a specific period of time, the base station can execute scheduling instructions only for the initial BWP. When no default BWP is configured in the RRC message, the initial BWP can be considered the default BWP, and the BWP can fall back to the initial BWP when the BWP deactivation timer expires.

[0201] According to another method, in order to increase the freedom of the base station implementation, a default BWP can also be defined and configured for UL, and can be used in the same way as the default BWP of DL.

[0202] A dormant BWP refers to a BWP in idle mode or a dormant BWP in an active SCell. When a dormant BWP is active, depending on the base station configuration, the UE may not exchange data with the base station, may not monitor the PDCCH to identify base station indications, or may not transmit pilot signals. However, it can perform channel measurements and report measurement results periodically or when events occur for the measured frequency / cell / channel. Therefore, because the UE does not monitor the PDCCH and transmit pilot signals in a dormant BWP in an active SCell, power consumption can be reduced compared to a normal BWP in an active SCell (or a BWP other than a dormant BWP), or compared to when a normal BWP in an active SCell (or a BWP other than a dormant BWP) is activated. Furthermore, unlike when the SCell is deactivated, the UE can report channel measurements. Therefore, the base station can quickly activate a normal BWP in an active SCell based on measurement reports or measurement reports from a dormant BWP in an active SCell to quickly utilize carrier integration technology, thus reducing transmission latency.

[0203] The first active BWP activated from a dormant state (or the first active non-dormant BWP) can be a BWP that the UE must activate by switching the current or active BWP in the active SCell, or a BWP that the UE must activate from a dormant state configured via an RRC message, according to the following indications: when the UE operates a BWP in an active SCell as a dormant BWP, the active BWP in the active SCell is a dormant BWP, or the BWP in the SCell is converted to a dormant BWP, an indication from the base station to the UE via a DCI, MAC CE, or RRC message of the PDCCH to switch the BWP in the active SCell from a dormant BWP to a normal BWP (or a BWP other than a dormant BWP); an indication to switch or convert the active BWP in the dormant BWP to a normal BWP; or an indication to switch, convert, or activate the active BWP in the dormant BWP to a normal BWP (e.g., the first active BWP activated from a dormant state).

[0204] In this disclosure, switching the first BWP to the second BWP can mean activating the second BWP or deactivating the already activated first BWP and activating the second BWP.

[0205] Furthermore, in the RRC Setup message, RRC Resume message 1f-25, or RRC Reconfiguration message 1f-45 within the RRC connection configuration, a state transition timer can be configured so that the UE can directly perform a state transition even when it has not received an indication from the base station via RRC messages, MAC control information, or DCI of the PDCCH. For example, a cell deactivation timer (ScellDeactivationTimer) can be configured for each SCell, and when the cell deactivation timer expires, the SCell can transition to a deactivated state. Alternatively, a BWP sleep timer (DLBWPHibernationTimer or ULBWPHibernationTimer) for the DL (or UL) can be configured for each SCell or each SCell's BWP, and a SCell sleep timer (SCellHibernationTimer) can be configured for each SCell. Therefore, when the SCell sleep timer or the DL (or UL) BWP sleep timer expires, the SCell or the DL (or UL) BWP can transition to a hibernation state or switch to a hibernation BWP. For example, when the cell sleep timer or DL ​​(or UL) BWP sleep timer expires, an active SCell or DL ​​(or UL) BWP can transition to a sleep state or switch to a sleep BWP, while a sleep SCell or DL ​​(or UL) BWP cannot transition to a sleep state or sleep BWP. Furthermore, the BWP sleep timer can start when an instruction to switch BWPs or activate BWPs is received via RRC messages, MAC CE, or PDCCH DCI; or it can stop when an instruction to switch a BWP to a sleep BWP, deactivate a BWP, or activate a sleep BWP is received via RRC messages, MAC CE, or PDCCH DCI. Furthermore, a dormant cell deactivation timer (dormantSCellDeactivationTimer) or a dormant DL (or UL) dormant BWP deactivation timer (dormantDLDeactivationTimer or dormantULDeactivationTimer) can be configured for each SCell or DL ​​(or UL) BWP. Therefore, a dormant SCell or DL ​​(or UL) dormant BWP can be converted to a deactivated state. When the dormant cell deactivation timer or the dormant DL (or UL) dormant BWP deactivation timer expires, only dormant SCells or DL ​​(or UL) dormant BWPs can be converted to a deactivated state; SCells or DL ​​(or UL) BWPs in active or deactivated states cannot be converted to a deactivated state.Furthermore, the sleep timer for the hibernating BWP can be started when an instruction to switch to a hibernating BWP, to deactivate a hibernating BWP, or to activate a hibernating BWP is received via RRC messages, MAC CE, or PDCCH DCI. Alternatively, the sleep timer can be stopped when an instruction to deactivate or activate a BWP or SCell, or to activate a normal BWP (e.g., a BWP other than the hibernating BWP configured via RRC), is received via RRC messages, MAC CE, or PDCCH DCI. When the SCell deactivation timer (or DL ​​(or UL) BWP sleep timer) and the cell sleep timer (or DL ​​(or UL) hibernating BWP deactivation timer) are configured together, the SCell hibernation timer (or DL ​​(or UL) hibernating BWP sleep timer) can be prioritized. In other words, when a SCell hibernation timer (or DL ​​(or UL) BWP hibernation timer) is configured, the SCell or DL ​​(or UL) BWP may not be deactivated even if the SCell deactivation timer (or DL ​​(UL) hibernation BWP deactivation timer) expires. In other words, when a cell hibernation timer (or DL ​​(or UL) BWP hibernation timer) is configured, the SCell or DL ​​(or UL) BWP can initially transition from an active state to a hibernation state or switch to a hibernation BWP upon timer expiration, and the SCell or BWP in hibernation state can gradually transition back to a deactivated state upon the expiration of its hibernation state SCell or BWP deactivation timer. Therefore, when configuring a SCell sleep timer or a BWP sleep timer, the SCell deactivation timer or the hibernation BWP deactivation timer does not affect the state transition of the SCell or DL ​​(or UL) BWP. Furthermore, when configuring a SCell hibernation timer or a BWP sleep timer, even when the SCell deactivation timer or the hibernation BWP deactivation timer expires, the SCell or DL ​​(or UL) BWP may not directly transition to a deactivated state.

[0206] When the SCell deactivation timer (or DL ​​(or UL) BWP sleep timer) is not configured in the RRC message, the UE may assume that the SCell deactivation timer (or DL ​​(or UL) BWP sleep timer) is configured to an infinite value.

[0207] Furthermore, the RRCSetup message, RRCResume message 1f-25, or RRCReconfiguration message 1f-45 for RRC connection configuration can configure frequency measurement configuration information, frequency measurement interval configuration information, etc., and can include frequency measurement object information. Additionally, the RRCSetup message, RRCResume message 1f-25, or RRCReconfiguration message 1f-45 for RRC connection configuration can configure a power-saving mode to reduce UE power consumption. Along with the power-saving function, it can configure discontinuous reception (DRX) period, offset or on-duration portion (the portion of the PDCCH the UE needs to monitor), configuration information (such as time information), time information regarding the time point during the DRX period before the on-duration portion of the PDCCH monitored from the base station, short time period information, etc. When configuring features to reduce UE power consumption, the UE can configure the DRX period and detect the Wake-Up Signal (WUS) during the portion of the call duration configured to monitor the base station's PDCCH. The base station can then instruct the UE via the DCI of the PDCCH in the WUS whether to skip (or not perform) or perform PDCCH monitoring in the next call duration portion. The UE must always monitor the PDCCH during the call duration portion. However, through the aforementioned WUS, the base station can instruct the UE not to perform PDCCH monitoring during the call duration portion, thus reducing UE battery consumption.

[0208] When RRC connection configuration is completed as described above, the UE can configure multiple BWPs according to the instructions configured using RRC messages. Furthermore, the UE can activate one or a few of the configured BWPs to reduce power consumption. For example, one BWP can be indicated for activation. Additionally, the base station can indicate BWP activation using RRC messages, MAC CE, or L1 signaling (PHY layer control signals, such as the DCI of the PDCCH) to indicate the initial access BWP to switch to a new BWP. According to another method, new bitmap information can be defined in the DCI of the PDCCH, indicating whether to activate, deactivate, or deactivate. According to another method, whether to activate a normal BWP (e.g., the first active BWP to be activated from sleep), whether to activate a dormant BWP, or whether to switch a BWP to a dormant BWP, or whether to switch BWPs, can be indicated using a bitmap. In the initial access BWP, there may be many newly accessed users; therefore, in terms of scheduling, it may be more advantageous to allocate new BWPs and manage connected users individually. This is because the initial access BWP is not configured for each UE and may be shared by all UEs. In addition, to reduce signaling overhead, the default BWP can be dynamically indicated using MAC CE, L1 signaling, or system information.

[0209] In this disclosure, when a base station or network supports MBS for a UE, the base station or network can configure the bearer configuration information or transmission resource information (e.g., time resources, frequency resources, bandwidth, frequency, BWP (or BWP ID), bandwidth, subcarrier spacing, transmission resource period, radio network temporary identifier (RNTI) for each MBS, or logical channel ID for each MBS) for the UE using system information, RRC messages (e.g., RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message), or control messages for the MBS channel. According to another method, the bearer configuration information of the MBS can be agreed upon or specified using default configuration. From the perspective of the base station or UE, the bearer of the MBS can be regarded as a multicast bearer or a unicast bearer. According to another method, the base station or network can configure additional IDs or indicators by using system information, RRC messages (e.g., RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or newly defined new RRC messages) or control messages of the MBS channel, thereby configuring the UE's bearer by distinguishing between the multicast bearer and the unicast bearer of the MBS.

[0210] The DL shared channel (DL-SCH) described in this disclosure may include or indicate a common control channel (CCCH), a dedicated control channel (DCCH), or a dedicated traffic channel (DTCH).

[0211] The bearer, multicast bearer, or unicast bearer of MBS described in this disclosure can be interpreted as a multicast bearer or a unicast bearer.

[0212] In this disclosure, a bearer can represent the concepts of a signaling radio bearer (SRB) and a data radio bearer (DRB). An SRB can be primarily used for sending and receiving RRC messages for an RRC entity, and a DRB can be primarily used for sending and receiving user-layer data. Furthermore, a UM DRB can represent a DRB using an RLC entity operating in unacknowledged mode (UM), and an AMDRB can represent a DRB using an RLC entity operating in acknowledged mode (AM).

[0213] The MBS data described in this disclosure can be interpreted as MBS channel configuration information, MBS control data (control plane data) for bearer configuration or service configuration, or MBS user data (user plane data) supporting MBS.

[0214] The RNTI described in this disclosure is an identifier used when: the UE monitors the PDCCH via the PHY layer, descrambles or checks the cyclic redundancy check (CRC) of the received PDCCH, identifies whether the CRC of the PDCCH corresponds to an RNTI value configured for the UE or an RNTI value corresponding to a PDCCH to be received by the UE, and determines whether the CRC of the PDCCH is a PDCCH to be read by the UE.

[0215] Figure 1G This is a diagram illustrating the bearer structure established by a base station or network to support the UE's MBS in RRC connected mode, RRC inactive mode, or RRC idle mode, according to embodiments of this disclosure, when the base station or network configures MBS using system information, RRC messages, or control messages for the MBS channel. Furthermore, Figure 1G The infrastructure provided in the application can also be extended or configured to support general data services.

[0216] Figure 1G This is a diagram of a bearer structure for supporting MBS according to embodiments of the present disclosure. The bearer is configured by using system information, RRC messages, or control messages for the MBS channel when the base station or network supports the UE's MBS in RRC connected mode, RRC inactive mode, or RRC idle mode, or when the UE receives MBS.

[0217] refer to Figure 1GThe bearer structure configured for MBS can have one or more of the following bearer structures. For MBS bearer configuration information, one or more of the following bearer structures can be agreed upon or specified using default configuration. Furthermore, the following bearer structures can be configured in the UE or base station, or applied to the UE or base station.

[0218] First bearer structure 1g-01: When the unicast or multicast bearer of MBS is configured as Figure 1GIn the first bearer structure 1g-01 shown, the UE can configure the bearer structure directly connecting the MAC entity and the upper MBS application layer as the bearer for MBS. In the first bearer structure, the MAC entity's processes of sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ may not be applied to the first bearer structure. Alternatively, in the first bearer structure, the UE can send MBS data (MBS control data or MBS user data) received through the PHY layer or MAC entity to the upper MBS application layer. In the first bearer structure, MBS data may not include a MAC header. For example, this is because when configuring additional physical channels or transport channels for MBS and configuring additional transport resources (frequency, time resources, or transmission period), MBS data can be identified by the MAC entity without a MAC header. According to another method, for example, this is because when configuring additional physical channels or transport channels for MBS and configuring additional transport resources (frequency, time resources, or transmission period), and when allocating or defining the first RNTI for MBS data, the PHY layer or MAC entity can identify MBS data without a MAC header. The RNTI for MBS data can be assigned or specified with each of the first RNTI for MBS control data (or MBS control data channel) and the first RNTI for MBS user data (or MBS user data channel). In the first bearer structure, the MAC entity may not send HARQ ACK or NACK, retransmit HARQ, or process HARQ to the bearer application that supports MBS by default. Alternatively, by using system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message), or control messages for the MBS channel, the configuration information of the SDAP entity may not be configured for the first bearer structure, and the SDAP entity may not process (e.g., bypass) the data of the first bearer and may directly send the data to the MBS application layer. According to another method, configuration information for SDAP entities of bearers can be configured using system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message), or control messages of the MBS channel. Furthermore, the mapping information between QoS flows and bearers can be configured or reconfigured. Additionally, the configuration information for SDAP entities can be configured to specify whether to configure SDAP headers for DL ​​data and UL data. Moreover, by using the mapping information between QoS flows and bearers, reconfiguration or handover processes between unicast and multicast bearers can be supported.Furthermore, in the SDAP configuration information for the bearer, QoS flows for MBS can be mapped to the bearer to support MBS. MBS data to be received or transmitted in the first bearer structure can have a 1g-11 or 1g-12 structure. For example, based on the configuration information of system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message), or control messages for the MBS channel, MBS data to be received or transmitted in the first bearer structure can have a 1g-11 or 1g-12 structure. Based on this configuration, overhead due to headers can be reduced.

[0219] - Second Bearer Structure 1g-02: When the MBS's unicast or multicast bearer is configured as Figure 1GIn the second bearer structure 1g-02 shown, the UE can configure an RLC entity corresponding to the MBS control data channel, an MBS user data channel, or a logical channel ID (or MBS) of the MBS user data channel connected to the MAC entity. Furthermore, the UE can configure a bearer structure directly connecting the RLC entity and the upper-layer MBS application layer as the MBS bearer. In the second bearer structure, the MAC entity's processes of sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ may not apply to the second bearer. Alternatively, in the second bearer structure, the UE can send MBS data (MBS control data or MBS user data) received through the PHY layer or MAC entity to the upper-layer MBS application layer via the RLC entity. In the second bearer structure, the MBS data may not include a MAC header. For example, this is because when configuring additional physical channels or transport channels for the MBS and configuring additional transmission resources (frequency, time resources, or transmission period), the MBS data can be identified by the MAC entity without a MAC header. According to another method, for example, this is because, when configuring additional physical channels or transport channels for MBS, and configuring additional transport resources (frequency, time resources, or transport cycles), and when allocating or defining the first RNTI for MBS data, the PHY layer or MAC entity can identify MBS data without a MAC header. The RNTI for MBS data can be allocated or specified with each of the first RNTI for MBS control data (or MBS control data channel) and the first RNTI for MBS user data (or MBS user data channel, logical channel ID, or MBS). According to another method, in the second bearer structure, when additional physical channels or transport channels for MBS are configured, when MBS is used for DL-SCH support of general data services, or when additional transport resources (frequency, time resources, or transmission cycles) are configured, MBS data may include a MAC header, and the PHY layer or MAC entity may identify MBS control data (or MBS control data channel), MBS user data (or MBS user data channel, logical channel ID, or each MBS) or MBS based on the logical channel ID included in the MAC header, or may demultiplex the identified MBS control data, MBS user data, or MBS, and send the demultiplexed MBS control data, MBS user data, or MBS to the RLC entity. According to another method, in the second bearer structure, when additional physical channels or transport channels for MBS are configured, when MBS is used for DL-SCH support of general data services, or when additional transport resources (frequency, time resources, or transmission cycles) are configured, MBS data may be received via transport resources. When the first RNTI for MBS data is allocated or defined, MBS data can be received via transport resources according to the indication of the PDCCH through the RNTI.MBS data may include a MAC header, and MBS control data (or MBS control data channel), MBS user data (or MBS user data channel, logical channel ID, or each MBS) or MBS may be identified based on the logical channel ID included in the MAC header, or the identified MBS control data, MBS user data, or MBS may be demultiplexed and sent to each RLC entity. That is, to support MBS, different logical channel IDs can be configured or defined for each of the MBS control data channel, MBS user data channel, and MBS. In the second bearer structure, the configured RLC entity can be configured to be in transparent mode TM, and the MBS data may not include an RLC header. Alternatively, the RLC sequence number length may not be configured in the RLC entity. Alternatively, the RLC entity may not apply data processing procedures to the MBS data. Furthermore, the RLC entity configured in the second bearer structure may not apply the process of segmenting or reassembling data for the MBS data in TM mode. Alternatively, in the second bearer structure, the configured RLC entity can configure the RLC receive window size to 0, or it can choose not to operate the RLC receive window. In the second bearer structure, the MAC entity can choose not to send HARQ ACK or NACK, retransmit HARQ, or process HARQ to bearer applications that support MBS by default. Alternatively, by using system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message), or control messages of the MBS channel, the configuration information of the SDAP entity can be configured without targeting the second bearer structure, and the SDAP entity can choose not to process (e.g., bypass) the data of the second bearer and can directly send the data to the MBS application layer. According to another method, the configuration information of the SDAP entity for the bearer can be configured using RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message) or control messages of the MBS channel, and the mapping information between QoS flows and bearers can be configured or reconfigured. Furthermore, the configuration information for the SDAP entity allows configuration of whether to configure SDAP headers for DL ​​data and UL data. Additionally, by using mapping information between QoS flows and bearers, reconfiguration or handover processes between unicast and multicast bearers can be supported. Moreover, in the SDAP configuration information for bearers, QoS flows for MBS can be mapped to bearers to support MBS. MBS data to be received or transmitted in the second bearer structure can have a 1g-21 structure. Based on this configuration, overhead due to headers can be reduced.For example, based on the configuration information of system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message) or control messages of the MBS channel, the MBS data to be received or transmitted in the second bearer structure can have a 1g-21 structure.

[0220] - Third Bearer Structure 1g-03: When the MBS's unicast or multicast bearer is configured as Figure 1GWhen using the third bearer structure 1g-03 as shown, the UE can configure the logical channel ID (or MBS) of the RLC entity corresponding to the MBS control data channel, the MBS user data channel, or the MBS user data channel connected to the MAC entity. Furthermore, the UE can configure a bearer structure directly connecting the RLC entity and the upper-layer MBS application layer as the bearer for the MBS. In the third bearer structure, the process of the MAC entity sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ can be excluded from the third bearer. According to another method, the process of executing or not executing the MAC entity's sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ can be configured via system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message) or control messages of the MBS channel through an indicator. For example, when an indicator is configured in system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message) or control messages of the MBS channel to execute the procedure for sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ for the MAC entity (when the indicator value indicates a specific value or there is no indicator field), the procedure for sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ for the MAC entity can be executed. Alternatively, when an indicator is configured not to execute the procedure for sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ for the MAC entity (when the indicator value indicates a specific value or there is no indicator field), the corresponding procedure may not be executed, or the corresponding procedure (the procedure for sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ for the MAC entity) may not be applied to bearers that support MBS by default. Alternatively, the indicator can be configured for each of the MBS control data channel, MBS user data channel, logical channel ID (or MBS) or bearer ID of the MBS user data channel.According to another method, when the MAC entity's process of sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ is to be performed or configured to be performed, or configured for a specific logical channel ID, MBS, or bearer, an indicator (the indicator value may indicate a specific value or may not have an indicator field) can be configured via RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message) or control messages for the MBS channel to perform HARQ reordering or RLC reordering (or sequential delivery) relative to the RLC entity configured for the logical channel ID (or MBS) of the MBS control data channel, MBS user data channel, or MBS user data channel. Alternatively, the size of the RLC receive window can be configured and operated to a value greater than 0 (e.g., value = 2^(RLC sequence number length - 1)). This is because when HARQ processing or retransmission is performed on MBS data, the data order may be mixed. Therefore, MBS data reordering must be performed based on the RLC receive window or RLC sequence number, or a reordering timer must run to sequentially support MBS. According to another method, when the MAC entity's HARQ ACK or NACK transmission, HARQ retransmission, or HARQ processing procedures are not performed or are configured not to be performed, an indicator (the indicator value may indicate a specific value or may not have an indicator field) can be configured via RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message) or control messages of the MBS channel to prevent HARQ reordering or RLC reordering (or sequential delivery) from being performed relative to the logical channel ID (or MBS) configured for the MBS control data channel, MBS user data channel, or MBS user data channel. This allows HARQ reordering or RLC reordering (or sequential delivery) to be avoided. Alternatively, the MAC entity's processes for sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ may not be applied by default to MBS-supporting bearers, allowing RLC entities configured in MBS-supporting bearers to not perform HARQ reordering or RLC reordering (or sequential delivery) by default. Alternatively, the RLC receive window size can be configured to 0, thus the receive RLC window may not be operated. For example, when configuration information is absent or by default, the UE can always send data to upper-layer entities via the RLC entity through out-of-order delivery regardless of order. Furthermore, in the third bearer architecture, the UE can send MBS data (MBS control data or MBS user data) received through the PHY layer or MAC entity to the upper-layer MBS application layer via the RLC entity.In the third bearer structure, MBS data may include a MAC header. Alternatively, the logical channel ID included in the MAC header may be configured or defined to indicate the MBS control data channel, the MBS user data channel, or each MBS. For example, when configuring additional physical channels or transport channels for the MBS and configuring additional transport resources (frequency, time resources, or transport cycles), and when allocating or defining the first RNTI for the MBS data, the PHY layer or MAC entity may, based on the RNTI or logical channel ID, identify whether the MBS data is MBS control data or MBS user data, or identify which MBS the data corresponds to, or may demultiplex the identified data and send the demultiplexed data to each RLC entity. The RNTI for the MBS data may be allocated or specified with each of the first 1-1 RNTI for MBS control data (or MBS control data channel) and the first 1-2 RNTIs for MBS user data (or MBS user data channel, logical channel ID, or each MBS). According to another method, in the third bearer structure, when additional physical channels or transport channels for MBS are configured, when MBS is used for DL-SCH support of general data services, or when additional transport resources (frequency, time resources, or transmission cycles) are configured, MBS data may include a MAC header, and based on the logical channel ID included in the MAC header, MBS control data (or MBS control data channel), MBS user data (or MBS user data channel, logical channel ID, or each MBS) or MBS can be identified, or the identified MBS control data, MBS user data, or MBS can be demultiplexed and sent to each RLC entity. According to another method, in the third bearer structure, when additional physical channels or transport channels for MBS are configured, when MBS is used for DL-SCH support of general data services, or when additional transport resources (frequency, time resources, or transmission cycles) are configured, the PHY layer or MAC entity can receive MBS data via transport resources. When the first RNTI of MBS data is allocated or defined, MBS data can be received via transport resources according to the indication of the PDCCH through the RNTI. MBS data may include a MAC header, and MBS control data (or MBS control data channel), MBS user data (or MBS user data channel, logical channel ID, or each MBS) or MBS may be identified based on the logical channel ID included in the MAC header, or the identified MBS control data, MBS user data, or MBS may be demultiplexed and sent to each RLC entity. That is, to support MBS, different logical channel IDs can be configured or defined for each of the MBS control data channel, MBS user data channel, and MBS. In the third bearer structure, the configured RLC entity can be configured to be in TM, UM, UM unidirectional mode, UM bidirectional mode, or AM.In RLC TM, MBS data may not include an RLC header, while in RLC UM or AM, MBS data may include an RLC header. Furthermore, in RLC TM, the RLC entity may not apply data processing procedures (e.g., data segmentation or reassembly) to MBS data. In RLC UM or AM, the RLC entity may apply data processing procedures to MBS data. Alternatively, by using system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message), or control messages for the MBS channel, the configuration information of the SDAP entity may not be configured for the third bearer structure, and the SDAP entity may not process (e.g., bypass) the data of the third bearer and may directly send the data to the MBS application layer. According to another method, configuration information for SDAP entities targeting bearers can be configured using RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message) or control messages for the MBS channel. The mapping information between QoS flows and bearers can be configured or reconfigured. Furthermore, the configuration information for SDAP entities can be configured to include whether to configure SDAP headers for DL ​​data and UL data. Additionally, by using the mapping information between QoS flows and bearers, reconfiguration or handover processes between unicast and multicast bearers can be supported. Moreover, in the SDAP configuration information for bearers, QoS flows for MBS can be mapped to bearers to support MBS. MBS data to be received or transmitted in the third bearer structure can have a 1g-31 or 1g-32 structure. Based on this configuration, overhead due to headers can be reduced. For example, based on configuration information from system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message), or control messages of the MBS channel, the MBS data to be received or transmitted in the third bearer structure can have a 1g-31 or 1g-32 structure. When configured via an indicator to perform the MAC entity's process of sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ via system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message), or control messages of the MBS channel, information on transmission resources (e.g., time, frequency resources, transmission channel, frequency interval, etc.) for sending HARQ ACK or NACK can also be transmitted.When a UE in RRC connected mode, RRC inactive mode, or RRC idle mode is configured to process MAC entity transmission of HARQ ACK or NACK, retransmission of HARQ, or processing of HARQ, the UE may transmit HARQ ACK or NACK via transmission resources (e.g., physical transmission resources) configured after receiving DL MBS data. When the base station detects at least one NACK or detects at least one UE transmitting a NACK in the transmission resources, the base station may perform a retransmission for MBS. Alternatively, the base station may perform a retransmission such that all UEs can receive MBS data through the MBS channel. According to another method, after a UE in RRC connected mode, RRC inactive mode, or RRC idle mode receives DL MBS data, the UE can define MAC control information (or RLC control information, PDCP control information, or RRC message) and send MAC control information (or RLC control information, PDCP control information, or RRC message) including UE ID, MBS ID, logical channel ID, RNTI, or bearer ID to indicate to the base station which UE failed to receive data (e.g., MAC control information (or RLC control information, PDCP control information, or RRC message) can be sent via configured transmission resources). The base station can retransmit MBS data only for UEs in RRC connected mode, RRC idle mode, or RRC inactive mode that send a NACK or indicate unsuccessful reception via transmission resources. According to another method, the base station can perform a retransmission for MBS when it detects at least one NACK or detects at least one UE sending a NACK in transmission resources. Alternatively, the base station can perform a retransmission so that all UEs can receive MBS data via the MBS channel.

[0221] - Fourth Bearer Structure 1g-04: When the MBS's unicast or multicast bearer is configured as Figure 1GIn the fourth bearer structure 1g-04 shown, the UE can configure the RLC entity corresponding to the MBS control data channel, the MBS user data channel, or the logical channel ID (or MBS) of the MBS user data channel connected to the MAC entity. Furthermore, a PDCP entity connected to the RLC entity can be configured, and a bearer structure directly connecting the PDCP entity and the upper-layer MBS application layer can be configured as the bearer for the MBS. In the fourth bearer structure, the process of the MAC entity sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ can be excluded from the fourth bearer. According to another method, the process of executing or not executing the MAC entity's sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ can be configured via system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message) or control messages of the MBS channel through an indicator. For example, when an indicator is configured in system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message) or control messages of the MBS channel to execute the process of sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ for the MAC entity (when the indicator value indicates a specific value or there is no indicator field), the process of sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ for the MAC entity can be executed. Alternatively, when an indicator is configured not to execute the process of sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ for the MAC entity (when the indicator value indicates a specific value or there is no indicator field), the corresponding process may not be executed, or the corresponding process (the process of sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ for the MAC entity) may not be applied to bearers that support MBS by default. Alternatively, the indicator can be configured for each of the MBS control data channel, MBS user data channel, logical channel ID (or MBS), or bearer ID of the MBS user data channel.According to another method, when the MAC entity's process of sending HARQ ACK or NACK, retransmitting HARQ, or processing HARQ is to be performed or configured to be performed, or configured for a specific logical channel ID, MBS, or bearer, an indicator (the indicator value may indicate a specific value or may not have an indicator field) can be configured via RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message) or control messages for the MBS channel to perform HARQ reordering or RLC reordering (or sequential delivery) relative to the RLC entity configured for the logical channel ID (or MBS) of the MBS control data channel, MBS user data channel, or MBS user data channel. Alternatively, the size of the RLC receive window can be configured and operated to a value greater than 0 (e.g., value = 2^(RLC sequence number length - 1)). This is because when HARQ processing or retransmission is performed on MBS data, the data order may be mixed. Therefore, MBS data reordering must be performed based on the RLC receive window or RLC sequence number, or a reordering timer must run to sequentially support MBS. According to another method, when the MAC entity's HARQ ACK or NACK transmission, HARQ retransmission, or HARQ processing procedures are not performed or are configured not to be performed, an indicator (the indicator value may indicate a specific value or may not have an indicator field) can be configured via RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message) or control messages of the MBS channel. This prevents the RLC entity configured relative to the logical channel ID (or MBS) of the MBS control data channel, MBS user data channel, or MBS user data channel from performing HARQ reordering or RLC reordering (or sequential delivery), thus allowing HARQ reordering or RLC reordering (or sequential delivery) to be avoided. Alternatively, the MAC entity's process of sending HARQACK or NACK, retransmitting HARQ, or processing HARQ may not be applied by default to MBS-supporting bearers, allowing RLC entities configured in MBS-supporting bearers to not perform HARQ reordering or RLC reordering (or sequential delivery) by default. Alternatively, the RLC receive window size can be configured to 0, thus the receive RLC window may not be operated. For example, when the configuration information is absent or used as the default, the UE can always send data to upper-layer entities via RLC entities through out-of-order delivery regardless of order.Alternatively, in the fourth bearer architecture, the UE can transmit MBS data (MBS control data or MBS user data) received through the PHY layer or MAC entity to the upper MBS application layer via the RLC entity or PDCP entity. In the fourth bearer architecture, the MBS data may include a MAC header. Alternatively, the logical channel ID included in the MAC header can be configured or defined to indicate the MBS control data channel, MBS user data channel, or each MBS. For example, when configuring additional physical channels or transport channels for the MBS, and configuring additional transmission resources (frequency, time resources, or transmission period), and when allocating or defining the first RNTI for the MBS data, the PHY layer or MAC entity can identify whether the MBS data is MBS control data or MBS user data, or identify which MBS the data corresponds to, based on the RNTI or logical channel ID, or can demultiplex the identified data and send the demultiplexed data to each RLC entity. The RNTI for MBS data can be assigned or specified with each of the first RNTI for MBS control data (or MBS control data channel) and the first RNTI for MBS user data (or MBS user data channel, logical channel ID, or per MBS). According to another method, in the fourth bearer structure, when additional physical or transport channels for MBS are configured, when MBS is used for DL-SCH support in general data services, or when additional transport resources (frequency, time resources, or transport cycles) are configured, MBS data may include a MAC header. The MAC header may identify MBS control data (or MBS control data channel), MBS user data (or MBS user data channel, logical channel ID, or per MBS) or MBS based on the logical channel ID included in the MAC header, or the identified MBS control data, MBS user data, or MBS may be demultiplexed and sent to each RLC entity. According to another method, in the third bearer structure, when additional physical channels or transport channels for MBS are configured, when MBS is used for DL-SCH support in general data services, or when additional transport resources (frequency, time resources, or transmission cycles) are configured, the PHY layer or MAC entity can receive MBS data via transport resources. When the first RNTI for MBS data is allocated or defined, MBS data can be received via transport resources according to the indication of the PDCCH through the RNTI. MBS data may include a MAC header, and the MAC entity can identify MBS control data (or MBS control data channel), MBS user data (or MBS user data channel, logical channel ID, or each MBS) or MBS based on the logical channel ID included in the MAC header, or can demultiplex the identified MBS control data, MBS user data, or MBS and send them to each RLC entity.In other words, to support MBS, different logical channel IDs can be configured or defined for the MBS control data channel, MBS user data channel, and each within MBS. In the fourth bearer structure, the configured RLC entity can be configured to be in TM, UM, UM unidirectional mode, UM bidirectional mode, or AM. In RLC TM, MBS data may not include an RLC header, while in RLC UM or AM, MBS data may include an RLC header. Furthermore, in RLC TM, the RLC entity may not apply data processing procedures (e.g., data segmentation or reassembly) to MBS data. In RLC UM or AM, the RLC entity can apply data processing procedures to MBS data. For the fourth bearer structure, the RLC entity can be configured to be in TM using system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message), or control messages for the MBS channel; therefore, the overhead of MBS data can be reduced (e.g., overhead can be reduced by not using an RLC header). Alternatively, for the fourth bearer structure, out-of-order delivery functionality can be configured in the PDCP entity using system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message), or control messages for the MBS channel, thus preventing MBS data transmission delays. According to another approach, in the fourth bearer structure for the MBS bearer, the PDCP entity can perform out-of-order delivery functionality by default (e.g., the out-of-order delivery indicator is always configured to true), thus preventing MBS data transmission delays. This is because, when retransmission or HARQ processing is not performed, and the retransmission RLC process for MBS data is not performed, the PDCP entity's reordering function may cause transmission delays when data loss occurs. According to another approach, the PDCP entity can perform PDCP reordering functionality by default, the receive window size can be determined based on the PDCP sequence number length (e.g., if the PDCP sequence number length is 16 bits, the window size is 2^(16-1)), and a reordering timer can be run. Alternatively, in the fourth bearer structure, configuration information for the SDAP entity of the bearer can be configured using RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message) or control messages of the MBS channel, and the mapping information between QoS flows and bearers can be configured or reconfigured. Furthermore, the configuration information of the SDAP entity can be configured to specify whether to configure SDAP headers for DL ​​data and whether to configure SDAP headers for UL data.Furthermore, by using mapping information between QoS flows and bearers, reconfiguration or handover processes between unicast and multicast bearers can be supported. Additionally, by using system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message), or control messages for the MBS channel, the configuration information of the SDAP entity can be configured without targeting the fourth bearer structure, and the SDAP entity can bypass (e.g., process) the data of the fourth bearer and directly send the data to the MBS application layer. Furthermore, in the SDAP configuration information for the bearer, QoS flows for MBS can be mapped to the bearer to support MBS. MBS data to be received or transmitted in the fourth bearer structure can have a 1g-41, 1g-42, 1g-43, or 1g-44 structure. For example, based on configuration information from system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message), or control messages of the MBS channel, the MBS data to be received or transmitted in the fourth bearer structure can have a 1g-41, 1g-42, 1g-43, or 1g-44 structure. This configuration reduces overhead due to headers. When configured via an indicator or configured to perform the MAC entity's HARQ ACK or NACK transmission, HARQ retransmission, or HARQ processing procedures via system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message), or control messages of the MBS channel, information about transmission resources (e.g., time, frequency resources, transmission channel, frequency interval, etc.) for transmitting HARQ ACK or NACK can also be transmitted. When a UE in RRC connected mode, RRC inactive mode, or RRC idle mode is configured to process MAC entity transmission of HARQ ACK or NACK, retransmission of HARQ, or processing of HARQ, the UE may transmit HARQ ACK or NACK via transmission resources (e.g., physical transmission resources) configured after receiving DL MBS data. When the base station detects at least one NACK or detects at least one UE transmitting a NACK in the transmission resources, the base station may perform a retransmission for MBS. Alternatively, the base station may perform a retransmission such that all UEs can receive MBS data through the MBS channel.According to another method, after a UE in RRC connected mode, RRC inactive mode, or RRC idle mode receives DL MBS data, the UE can define MAC control information (or RLC control information, PDCP control information, or RRC message) and send the MAC control information (or RLC control information, PDCP control information, or RRC message) including UE ID, MBS ID, logical channel ID, RNTI, or bearer ID to indicate to the base station which UE failed to receive data (e.g., the MAC control information (or RLC control information, PDCP control information, or RRC message) can be sent via configured transmission resources). The base station can retransmit the MBS data only for UEs in RRC connected mode, RRC idle mode, or RRC inactive mode that send a NACK or indicate unsuccessful reception via transmission resources. According to another method, the base station can perform a retransmission for MBS when it detects at least one NACK or detects at least one UE sending a NACK in transmission resources. Alternatively, the base station can perform a retransmission so that all UEs can receive MBS data via the MBS channel.

[0222] When a UE receives system information indicating that it will receive a service of interest, has a service of interest, or has identified a system of interest, when the UE is in or enters a cell or domain that supports MBS as indicated in the system information, when MBS (or session) is configured or connected, or when receiving or broadcasting MBS configuration information or bearer configuration information via system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message), or control messages of the MBS channel (e.g., sent from the MBS control data channel), the UE can configure a unicast bearer, multicast bearer, or MBS bearer to receive an MBS with the provided bearer structure.

[0223] Figure 1H This diagram illustrates a method for demultiplexing received MBS data via the MAC layer when a UE in RRC connected mode, RRC inactive mode, or RRC idle mode receives MBS data (e.g., MBS control data, MBS user data, or general data other than MBS data) via a multicast or unicast bearer supporting MBS, according to an embodiment of this disclosure.

[0224] also, Figure 1H It can be Figure 1G One of the bearer structures provided in the document. Furthermore, a method is provided for transmitting UL MBS data (e.g., MBS control data, MBS user data, or general data other than MBS data) performed by the UE.

[0225] refer to Figure 1H The method for receiving MBS data, or the method for receiving and demultiplexing MBS data, may use one or more of the following methods. According to another method, different methods may be applied depending on whether the UE is in RRC connected mode, RRC inactive mode, or RRC idle mode.

[0226] - Method 1-1 for receiving MBS 1h-10: In Figure 1HIn the first-1 method of receiving MBS 1h-10, additional physical channels or transport channels for the MBS (e.g., MBS channel (MBCH)) can be configured, and additional transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), or subcarrier spacing) can be configured or defined in system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or newly defined new RRC messages) or control messages for the MBS channel (e.g., sent from the MBS control data channel)). A MAC header can always be appended to the MBS data to be sent for the MBS, and the logical channel ID included in the MAC header can be assigned differently for each of the MBS control data channel (e.g., MBS control channel (MBCCH)) and the MBS user data channel (e.g., MBS traffic channel (MBTCH)). Furthermore, a different logical channel ID can be assigned for each MBS provided via the MBS user data channel. Each MBS's first or second ID can be configured or broadcast, and each logical channel ID corresponding to each MBS's first or second ID can be configured or broadcast in system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message), or MBS channel control messages (e.g., sent from the MBS control data channel). The first ID may indicate the Public Land Mobile Network (PLMN) providing the MBS, the type of MBS, or the session. The second ID may indicate a more detailed session or MBS type. In DL-SCH, logical channel IDs that can be assigned to bearers of general data services (voice, internet, or video services) can be allocated using a specific bit combination (e.g., 6 bits) in a logical channel ID space generated with specific bits (e.g., 6 bits). Logical channel IDs for each service of the MBS control data channel, MBS user data channel, or MBS user data channel can be allocated using a specific bit combination (e.g., 6 bits) in a first logical channel ID space. Alternatively, MBS control information (MAC CE, e.g., MAC CE for network to indicate the suspension of MBS or for UE to indicate the stop of MBS reception) or logical channel IDs for padding MBS data to support MBS can also be allocated in the first logical channel ID space with a specific bit combination (e.g., 6 bits).According to another method, to double the logical channel ID space, the logical channel ID for each service of the MBS control data channel, MBS user data channel, or MBS user data channel can be allocated in the new second logical channel ID space using a specific bit combination (e.g., 6 bits). Alternatively, MBS control information (MAC CE, e.g., MAC CE for network instruction of BMS suspension or for UE instruction of MBS reception stop) used to support MBS, or logical channel IDs for padding MBS data to support MBS, can also be allocated in the new second logical channel ID space using a specific bit combination (e.g., 6 bits). The first and second logical channel ID spaces can be distinguished from each other in the MAC entity via MBS channels, DL-SCH channels, or transport resources (frequency, time transport resources, frequency information, BWP ID, BWP configuration information, dedicated carrier or dedicated SCell ID, or dedicated cell information), or they can be distinguished from each other by using different RNTIs. Therefore, when the UE's MAC entity receives MBS data via the channel or transport resources through which it receives MBS, the MAC entity can identify or demultiplex the identified MBS data based on the received transport channel (e.g., MBCH, DL-SCH, BCH, etc.), BWP ID, SCell ID, logical channel ID, or RNTI, and send the data to the corresponding upper-layer entity. The MBS reception method described in section 1-1 can be applied to UEs in RRC connected mode, RRC inactive mode, or RRC idle mode.

[0227] - Methods 1-2 for receiving MBS 1h-10: In Figure 1HIn the first and second methods of receiving MBS 1h-10, additional physical channels or transport channels (e.g., MBCH) of the MBS can be configured, and additional transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), or subcarrier spacing) can be configured or defined in system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or newly defined new RRC messages) or control messages of the MBS channels (e.g., sent from the MBS control data channel)). A MAC header can be appended to the MBS data to be transmitted for the MBS, and the logical channel ID included in the MAC header can be assigned differently for each of the MBS control data channels (e.g., MBCCH) and MBS user data channels (e.g., MBTCH). Furthermore, a different logical channel ID can be assigned for each MBS provided via the MBS user data channel. Furthermore, RNTIs can be assigned differently to each of the MBS control data channels (e.g., MBCCH) and MBS user data channels (e.g., MBTCH). Additionally, different RNTIs can be assigned to each MBS provided in the MBS user data channels. Therefore, since each MBS provided in the MBS control data channels (e.g., MBCCH), MBS user data channels, or MBS user data channels can be identified by an RNTI, the logical channel ID can be assigned the same logical channel ID for each MBS provided in the MBS control data channels, MBS user data channels, or MBS user data channels. According to another method, the same RNTI can be assigned to each MBS provided in the MBS control data channels (e.g., MBCCH), MBS user data channels, or MBS user data channels. Further specific identification can be performed by assigning different logical channel IDs to each MBS provided in the MBS control data channels (e.g., MBCCH), MBS user data channels, or MBS user data channels. The RNTI of the MBS can be configured differently from the RNTI of the DL-SCH (e.g., C-RNTI, MCS-C-RNTI, or CS-RNTI). According to another method, the RNTI of the MBS can be configured to be the same as the RNTI of the DL-SCH (e.g., C-RNTI, MCS-C-RNTI, or CS-RNTI), and further identification can be performed through the logical channel ID.Furthermore, for each MBS provided in the MBS user data channel, a first ID or a second ID of each MBS can be configured or broadcast, and can be configured or broadcast in system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message) or control messages of the MBS channel (e.g., sent from the MBS control data channel), for each logical channel ID or each RNTI corresponding to the first ID or second ID of each MBS. The first ID may indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID may indicate a more detailed session or the type of MBS. In DL-SCH, the logical channel ID that can be assigned to a bearer of a general data service (voice, Internet, or video service) can be allocated in a logical channel ID space generated in specific bits (e.g., 6 bits) using a specific bit combination (e.g., 6 bits). The logical channel ID for each service of the MBS control data channel, MBS user data channel, or MBS user data channel can be allocated in a first logical channel ID space using a specific bit combination (e.g., 6 bits). Alternatively, MBS control information (MAC CE, e.g., MAC CE for network instruction of MBS suspension or for UE instruction of MBS reception stop) or logical channel IDs for padding MBS data to support MBS can also be allocated in the first logical channel ID space using a specific bit combination (e.g., 6 bits). According to another method, to double the logical channel ID space, logical channel IDs for each service of the MBS control data channel, MBS user data channel, or MBS user data channel can be allocated in the new second logical channel ID space using a specific bit combination (e.g., 6 bits). Alternatively, MBS control information (MAC CE, e.g., MAC CE for network instruction of MBS suspension or for UE instruction of MBS reception stop) or logical channel IDs for padding MBS data to support MBS can also be allocated in the new second logical channel ID space using a specific bit combination (e.g., 6 bits). The first logical channel ID space and the second logical channel ID space can be distinguished from each other in the MAC entity via the MBS channel, DL-SCH channel, or transmission resources (frequency, time transmission resources, frequency information, BWP ID, BWP configuration information, dedicated carrier or dedicated SCell ID, or dedicated cell information), or they can be distinguished from each other by using different RNTIs.Therefore, when the UE's MAC entity receives MBS data via the channel or transport resources through which it receives MBS, the MAC entity can identify or demultiplex the identified MBS data based on the received transport channel (e.g., MBCH, DL-SCH, BCH, etc.), BWP ID, SCell ID, logical channel ID, or RNTI, and send the data to the corresponding upper-layer entity. The MBS reception methods described in sections 1-2 can be applied to UEs in RRC connected mode, RRC inactive mode, or RRC idle mode.

[0228] - Methods 1-3 for receiving MBS 1h-10: In Figure 1HIn methods 1-3 of receiving MBS 1h-10, additional physical channels or transport channels (e.g., MBCH) for the MBS can be configured, and additional transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), or subcarrier spacing) can be configured or defined in system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or newly defined new RRC messages) or control messages for the MBS channels (e.g., sent from the MBS control data channel)). In the MBS data sent for the MBS, a MAC header may not be appended, and each of the MBS control data channel (e.g., MBCCH) and the MBS user data channel (e.g., MBTCH) can be identified differently based on the RNTI. Furthermore, different RNTIs can be assigned for each MBS provided in the MBS user data channel. Therefore, since each MBS provided in the MBS control data channel (e.g., MBCCH), MBS user data channel, or MBS user data channel can be identified by an RNTI, the logical channel ID does not need to be configured for each MBS provided in the MBS control data channel, MBS user data channel, or MBS user data channel, and the MAC header does not need to be included in the MBS data. Furthermore, for each MBS provided in the MBS user data channel, a first ID or a second ID for each MBS can be configured or broadcast, and each RNTI corresponding to the first ID or second ID of each MBS can be configured or broadcast in system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message), or control messages of the MBS channel (e.g., sent from the MBS control data channel). The first ID can indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID can indicate a more detailed session or type of MBS. Therefore, when the UE's MAC entity receives MBS data via the channel or transport resources through which it receives MBS, the MAC entity can identify or demultiplex the identified MBS data based on the received transport channel (e.g., MBCH, DL-SCH, BCH, etc.), BWPID, SCell ID, logical channel ID, or RNTI, and send the data to the corresponding upper-layer entity. The MBS reception methods described in sections 1-3 can be applied to UEs in RRC connected mode, RRC inactive mode, or RRC idle mode.

[0229] - Method 2-1 for receiving MBS 1h-20: In Figure 1HIn method 2-1 of receiving MBS 1h-20, additional physical channels or transport channels (e.g., MBCH) of the MBS can be configured, and additional transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), or subcarrier spacing) can be configured or defined in system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or newly defined new RRC messages) or control messages of the MBS channel (e.g., sent from the MBS control data channel)). A MAC header can always be appended to the MBS data sent for the MBS, and a logical channel ID included in the MAC header can be assigned differently for each of the MBS control data channel (e.g., MBCCH) and the MBS user data channel (e.g., MBTCH). Furthermore, a different logical channel ID can be assigned for each MBS provided via the MBS user data channel. Each MBS's first or second ID can be configured or broadcast, and each logical channel ID corresponding to each MBS's first or second ID can be configured or broadcast in system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message), or MBS channel control messages (e.g., sent from the MBS control data channel). The first ID can indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID can indicate a more detailed session or MBS type. In DL-SCH, logical channel IDs that can be assigned to bearers of general data services (voice, internet, or video services) can be allocated using a specific bit combination (e.g., 6 bits) in a logical channel ID space generated in specific bits (e.g., 6 bits). The logical channel ID for each service of the MBS control data channel, MBS user data channel, or MBS user data channel can be allocated using a specific bit combination (e.g., 6 bits) in a first logical channel ID space. Alternatively, MBS control information (MAC CE, e.g., MAC CE for network indication of MBS suspension or for UE indication of MBS reception stop) or logical channel IDs for padding MBS data to support MBS can also be allocated in the first logical channel ID space using a specific bit combination (e.g., 6 bits). According to another method, to double the logical channel ID space, logical channel IDs for each service of the MBS control data channel, MBS user data channel, or MBS user data channel can be allocated in the new second logical channel ID space using a specific bit combination (e.g., 6 bits).Alternatively, MBS control information (MAC CE, e.g., MAC CE for network instruction of BMS suspension or for UE instruction of MBS reception to stop) used to support MBS, or logical channel IDs for padding MBS data to support MBS, can also be allocated in a new second logical channel ID space using specific bit combinations (e.g., 6 bits). The first and second logical channel ID spaces can be distinguished from each other in the MAC entity via MBS channels, DL-SCH channels, or transport resources (frequency, time transport resources, frequency information, BWP ID, BWP configuration information, dedicated carrier or dedicated SCell ID, or dedicated cell information), or they can be distinguished from each other by using different RNTIs. Therefore, when the UE's MAC entity receives MBS data via its MBS reception channel or transport resources, the MAC entity can identify or demultiplex the identified MBS data based on the received transport channel (e.g., MBCH, DL-SCH, BCH, etc.), BWP ID, SCell ID, logical channel ID, or RNTI, and send the data to the corresponding upper-layer entity. The MBS receiving method in section 2-1 can be applied to UEs in RRC connected mode, RRC inactive mode, or RRC idle mode.

[0230] - Method 2-2 for receiving MBS 1h-20: In Figure 1HIn method 2-2 of receiving MBS 1h-20, additional physical channels or transport channels (e.g., MBCH) of the MBS can be configured, and additional transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), or subcarrier spacing) can be configured or defined in system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or newly defined new RRC messages) or control messages of the MBS channels (e.g., sent from the MBS control data channel)). A MAC header can be appended to the MBS data sent for the MBS, and a logical channel ID included in the MAC header can be assigned differently to each of the MBS control data channel (e.g., MBCCH) and the MBS user data channel (e.g., MBTCH). Furthermore, a different logical channel ID can be assigned for each MBS provided via the MBS user data channel. Furthermore, RNTIs can be assigned differently for each of the MBS control data channels (e.g., MBCCH) and MBS user data channels (e.g., MBTCH). Additionally, different RNTIs can be assigned for each MBS provided in the MBS user data channels. Therefore, since each MBS provided in the MBS control data channels (e.g., MBCCH), MBS user data channels, or MBS user data channels can be identified by an RNTI, logical channel IDs can be assigned using the same logical channel ID for each MBS provided in the MBS control data channels, MBS user data channels, or MBS user data channels. According to another method, the same RNTI can be assigned to each MBS provided in the MBS control data channels (e.g., MBCCH), MBS user data channels, or MBS user data channels. Further specific identification can be performed by assigning different logical channel IDs to each MBS provided in the MBS control data channels (e.g., MBCCH), MBS user data channels, or MBS user data channels. The RNTI of the MBS can be configured differently from the RNTI of the DL-SCH (e.g., C-RNTI, MCS-C-RNTI, or CS-RNTI). According to another method, the RNTI of the MBS can be configured to be the same as the RNTI of the DL-SCH (e.g., C-RNTI, MCS-C-RNTI, or CS-RNTI), and further identification can be performed through the logical channel ID.Furthermore, for each MBS provided in the MBS user data channel, a first ID or a second ID for each MBS can be configured or broadcast, and can be configured or broadcast in system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message) or control messages of the MBS channel (e.g., sent from the MBS control data channel), for each logical channel ID or each RNTI corresponding to the first ID or second ID of each MBS. The first ID may indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID may indicate a more detailed session or the type of MBS. In DL-SCH, logical channel IDs that can be assigned to bearers of general data services (voice, Internet, or video services) can be allocated using a specific combination of bits (e.g., 6 bits) in a logical channel ID space generated in specific bits (e.g., 6 bits). The logical channel ID for each service of the MBS control data channel, MBS user data channel, or MBS user data channel can be allocated using a specific combination of bits (e.g., 6 bits) in a first logical channel ID space. Alternatively, MBS control information (MAC CE, e.g., MAC CE for network instruction of MBS suspension or for UE instruction of MBS reception stop) or logical channel IDs for padding MBS data to support MBS can also be allocated in the first logical channel ID space using a specific bit combination (e.g., 6 bits). According to another method, to double the logical channel ID space, logical channel IDs for each service of the MBS control data channel, MBS user data channel, or MBS user data channel can be allocated in the new second logical channel ID space using a specific bit combination (e.g., 6 bits). Alternatively, MBS control information (MAC CE, e.g., MAC CE for network instruction of MBS suspension or for UE instruction of MBS reception stop) or logical channel IDs for padding MBS data to support MBS can also be allocated in the new second logical channel ID space using a specific bit combination (e.g., 6 bits). The first logical channel ID space and the second logical channel ID space can be distinguished from each other in the MAC entity via the MBS channel, DL-SCH channel, or transmission resources (frequency, time transmission resources, frequency information, BWP ID, BWP configuration information, dedicated carrier or dedicated SCell ID, or dedicated cell information), or they can be distinguished from each other by using different RNTIs.Therefore, when the UE's MAC entity receives MBS data via the channel or transport resources through which it receives MBS, the MAC entity can identify or demultiplex the identified MBS data based on the received transport channel (e.g., MBCH, DL-SCH, BCH, etc.), BWP ID, SCell ID, logical channel ID, or RNTI, and send the data to the corresponding upper-layer entity. The MBS reception method in section 2-2 can be applied to UEs in RRC connected mode, RRC inactive mode, or RRC idle mode.

[0231] - Methods 2-3 for receiving MBS 1h-20: In Figure 1HIn the second and third methods of receiving MBS 1h-20, additional physical channels or transport channels (e.g., MBCH) of the MBS can be configured, and additional transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), or subcarrier spacing) can be configured or defined in system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or newly defined new RRC messages) or control messages of the MBS channels (e.g., sent from the MBS control data channel)). In the MBS data sent for the MBS, a MAC header may not be appended, and each of the MBS control data channel (e.g., MBCCH) and the MBS user data channel (e.g., MBTCH) can be identified differently based on the RNTI. Furthermore, different RNTIs can be assigned for each MBS provided in the MBS user data channel. Therefore, since each MBS provided in the MBS control data channel (e.g., MBCCH), MBS user data channel, or MBS user data channel can be identified by an RNTI, the logical channel ID does not need to be configured for each MBS provided in the MBS control data channel, MBS user data channel, or MBS user data channel, and the MAC header does not need to be included in the MBS data. Furthermore, for each MBS provided in the MBS user data channel, a first ID or a second ID for each MBS can be configured or broadcast, and each RNTI corresponding to the first ID or second ID of each MBS can be configured or broadcast in system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message), or control messages of the MBS channel (e.g., sent from the MBS control data channel). The first ID can indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID can indicate a more detailed session or type of MBS. Therefore, when the UE's MAC entity receives MBS data via the channel or transport resources through which it receives MBS, the MAC entity can identify or demultiplex the identified MBS data based on the received transport channel (e.g., MBCH, DL-SCH, BCH, etc.), BWPID, SCell ID, logical channel ID, or RNTI, and then send the data to the corresponding upper-layer entity. The MBS reception methods described in sections 2-3 can be applied to UEs in RRC connected mode, RRC inactive mode, or RRC idle mode.

[0232] Figure 1I This diagram illustrates a method for reusing the MBS data to be transmitted via a MAC entity when a UE in RRC connected mode, RRC inactive mode, or RRC idle mode transmits MBS data (e.g., MBS control data, MBS user data, or general data other than MBS data) via a multicast or unicast bearer supporting MBS, according to an embodiment of this disclosure.

[0233] refer to Figure 1I It is based on the above Figure 1G The bearer structure provided in the document, and the method for sending MBS data or the method for sending and multiplexing MBS data can use one or more of the following methods. According to another method, different methods among the following can be applied depending on whether the UE is in RRC connected mode, RRC inactive mode, or RRC idle mode.

[0234] - The first method for sending MBS 1i-01: when according to Figure 1H The method provided describes how a UE receiving MBS must send UL MBS data in response to a network request or as needed by the UE. The UE, or a UE in RRC connected mode, RRC inactive mode, or RRC idle mode, can send UL MBS data to a base station or network. The network or base station can send a network request to the UE by including a network request in the MBS data (e.g., MBS control data, MBS user data, RRC messages, RLC control data (RLC control PDU), PDCP control data (PDCP control PDU), MAC control data (MAC CE), or a newly defined message). It can also send or configure indications of the MBS status (e.g., suspending or resuming service) or information (or indicators) requesting a response to the MBS (e.g., whether the UE is receiving a specific MBS, whether the UE wants to receive a specific MBS, whether the UE is interested in a specific MBS, preferences between multicast and unicast bearers, or preferences for bearer switching (whether the UE wants to receive MBS via multicast or unicast bearer)). The base station or network can configure... Figure 1HThe system information, RRC messages (e.g., RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message) or MBS channel control messages (e.g., sent from the MBS control data channel) mentioned above, including additional DL channels, MBS physical channels, transport channels (e.g., MBCH), or additional transport resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), or subcarrier spacing), transmit MBS data including network requests so that UEs in RRC connected mode, RRC inactive mode, or RRC idle mode can receive MBS. As mentioned above, MBS data can be transmitted via a single transport resource, and multiple UEs can receive MBS data, thus preventing waste of transport resources and enabling efficient use of transport resources. According to another method, the base station or network can be configured in Figure 1HThe system information or RRC message described (e.g., RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message) uses the DL channel (e.g., DL-SCH, CCCH, or DDCH), additional transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID) or subcarrier spacing), SRB0 (CCCH), or SRB1 (DCCH) to send MBS data including network requests so that only UEs in RRC connected mode can receive MBS. UL MBS data can be MBS control data, MBS user data, RRC messages, RLC control data (RLC control PDU), PDCP control data (PDCP control PDU), MAC control data (MAC CE), or newly defined messages. In the first method of transmitting MBS, the UE can transmit UL MBS data by configuring additional UL channels, physical channels of MBS, transport channels (e.g., UL-MBCH) in system information, RRC messages (e.g., RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or newly defined new RRC messages) or control messages of the MBS channel (e.g., transmitted from the MBS control data channel), or additional transport resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), or subcarrier spacing). For example, the UE can include a MAC header in the UL MBS data, and can configure the logical channel ID in the MAC header to a logical channel ID (a logical channel ID configured or assigned for MBS control data (channel), MBS user data (channel), MBS user data (channel), SRB0 (CCCH), SRB1 (DCCH), DRB, or MAC control information) according to the purpose of the UL MBS data (MBS control data, MBS user data (channel), MBS user data (channel) for a specific MBS, SRB0 (CCCH), SRB1 (DCCH), DRB, or MAC control information) based on the purpose of the UL MBS data, and can transmit the UL MBS data. Figure 1GThe bearer structure configured in the provided bearer structure may also include an RLC header, a PDCP header, or an SDAP header. According to another method, the UE can transmit UL MBS data via an RNTI (an RNTI configured for MBS user data (channel) or MBS user data (channel) for a specific MBS) suitable for the purpose of UL MBS data (MBS control data, MBS user data, or MBS user data for a specific MBS), through UL transport resources indicated by the PDCCH. UL MBS data can be identified by the RNTI, therefore, a MAC header or logical channel ID may not be required. According to another method, UL MBS data may include a MAC header, the logical channel ID of which can be configured as a logical channel ID (configured or assigned for MBS control data (channel), MBS user data (channel), MBS user data (channel) for a specific MBS), SRB0 (CCCH), SRB1 (DCCH), DRB, or MAC control information, depending on the purpose of the UL MBS data (MBS control data (channel), MBS user data (channel), MBS user data (channel) for a specific MBS, SRB0 (CCCH), SRB1 (DCCH), DRB, or MAC control information) and the UL MBS data can be transmitted. Figure 1G The bearer structure provided in the configuration may also include an RLC header, a PDCP header, or an SDAP header.

[0235] - Second method for sending MBS 1i-01: when according to Figure 1H The method provided describes how a UE receiving MBS must respond to a network request or send UL MBS data as needed by the UE. Only UEs in RRC connection mode can send UL MBS data to the base station or network. The network or base station can send a network request to the UE by including a network request in the MBS data (e.g., MBS control data, MBS user data, RRC messages, RLC control data (RLC control PDU), PDCP control data (PDCP control PDU), MAC control data (MAC CE), or a newly defined message). It can also send or configure indications of the MBS status (e.g., suspending or resuming service) or information (or indicators) requesting a response to the MBS (e.g., whether the UE is receiving a specific MBS, whether the UE wants to receive a specific MBS, whether the UE is interested in a specific MBS, preferences between multicast and unicast bearers, or preferences for bearer switching (whether the UE wants to receive MBS via multicast or unicast bearer)). The base station or network can configure... Figure 1HThe system information, RRC messages (e.g., RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message) or MBS channel control messages (e.g., sent from the MBS control data channel) mentioned above, including additional DL channels, MBS physical channels, transport channels (e.g., MBCH), or additional transport resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), or subcarrier spacing), transmit MBS data including network requests so that UEs in RRC connected mode, RRC inactive mode, or RRC idle mode can receive MBS. By transmitting MBS data as described above, MBS data can be transmitted via a single transport resource, and multiple UEs can receive MBS data. Therefore, waste of transport resources can be prevented, and transport resources can be used efficiently. According to another method, the base station or network can be configured in Figure 1HThe system information or RRC message described (e.g., RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined RRC message) uses the DL channel (e.g., DL-SCH, CCCH, or DDCH), additional transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID) or subcarrier spacing), SRB0 (CCCH), or SRB1 (DCCH) to send MBS data including network requests so that only UEs in RRC connected mode can receive MBS. UL MBS data can be MBS control data, MBS user data, RRC messages, RLC control data (RLC control PDU), PDCP control data (PDCP control PDU), MAC control data (MAC CE), or newly defined messages. In the second method of transmitting MBS, a UE in RRC connection mode can transmit UL MBS data by configuring additional UL channels, physical channels of MBS, transport channels (e.g., UL-SCH, a channel for general data services), additional transport resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID) or subcarrier spacing) in system information, RRC messages (e.g., RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or newly defined new RRC messages) or control messages of the MBS channel (e.g., transmitted from the MBS control data channel), or transport resources allocated to PDCCH scrambled by RNTI (e.g., C-RNTI) allocated to a UE in RRC connection mode. When a UE in RRC connection mode transmits UL MBS data via transmission resources allocated to a PDCCH scrambled by an RNTI (e.g., C-RNTI) allocated to a UE in RRC connection mode, the UE in RRC connection mode can transmit UL MBS via SRB0 (CCH), SRB1 (DCCH), or DRB. For example, a UE in RRC connection mode can include a MAC header in the UL MBS data, and can configure the logical channel ID of the MAC header to a logical channel ID (a logical channel ID configured or allocated for MBS control data (channel), MBS user data (channel), MBS user data (channel), SRB0 (CCCH), SRB1 (DCCH), DRB, or MAC control information) depending on the purpose of the UL MBS data (MBS control data, MBS user data, or MBS user data for a specific MBS), and can transmit UL MBS data. Figure 1GThe bearer structure configured in the provided bearer structure may also include an RLC header, a PDCP header, or an SDAP header. According to another method, a UE in RRC connection mode can transmit UL MBS data via an RNTI (configured for MBS user data (channel) or MBS user data (channel) for a specific MBS) suitable for the purpose of UL MBS data (MBS control data, MBS user data, or MBS user data for a specific MBS), through UL transport resources indicated by the PDCCH. UL MBS data can be identified by the RNTI, therefore, a MAC header or logical channel ID may not be required. According to another method, UL MBS data may include a MAC header, the logical channel ID of which can be configured as a logical channel ID (configured or assigned for MBS control data (channel), MBS user data (channel), MBS user data (channel) for a specific MBS), SRB0 (CCCH), SRB1 (DCCH), DRB, or MAC control information, depending on the purpose of the UL MBS data (MBS control data (channel), MBS user data (channel), MBS user data (channel) for a specific MBS, SRB0 (CCCH), SRB1 (DCCH), DRB, or MAC control information) and the UL MBS data can be transmitted. Figure 1G The bearer structure provided in the configuration may also include an RLC header, a PDCP header, or an SDAP header.

[0236] Next, signaling procedures are provided according to this disclosure for a base station or network to support MBS to a UE and for a UE to receive MBS. As described below according to this disclosure, a base station may provide MBS to a UE, or a UE may receive MBS, through one of a variety of signaling procedures.

[0237] Figure 1J This is a diagram of the first signaling process supporting MBS according to an embodiment of this disclosure.

[0238] According to embodiments of this disclosure, the first signaling procedure for supporting MBS can support MBS to the UE based on system information.

[0239] refer to Figure 1J UE 1j-01 can perform cell selection or reselection in RRC idle mode or RRC inactive mode, select an appropriate cell, and camp on that cell. Then, UE 1j-01 can receive system information 1j-05 from gNB 1j-02 in RRC idle mode, RRC inactive mode, or RRC connected mode, and can identify some MBS configuration information from the system information. The MBS configuration information may include the following configuration information. That is, to support MBS, the network can send system information including some of the following configuration information.

[0240] - Whether MBS is supported.

[0241] - Configuration information for the physical channel of MBS or the DL or UL transport channel (e.g., MBCH, MBCCH, MBTCH, or DL-SCH).

[0242] Information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating transmission mode, etc.) is transmitted through these transmission resources by the physical channel or DL ​​or UL transmission channel (e.g., MBCH, MBCCH, or MBTCH).

[0243] - Configuration information regarding the MBS supported by the current cell. For example, a list of MBS or a first ID (e.g., Temporary Mobile Group Identifier (TMGI)) or second ID (e.g., session identifier) ​​for each MBS can be configured or broadcast, and information regarding the logical channel ID, bearer ID, or RNTI corresponding to the first or second ID of each MBS can be configured or broadcast. According to another method, the first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​or RNTI of an MBS can be configured or broadcast for each bearer (or bearer ID), each logical channel, each RLC configuration information segment, or each PDCP configuration information segment. The first ID can indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID can indicate a more detailed session or MBS type. In addition, the configuration information for MBS may include information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating transmission mode, etc.), through which each MBS is supported, broadcast, or transmitted.

[0244] The bearer can be configured as Figure 1GThe provided bearer structure is used to receive MBS. Furthermore, configuration information may include indicator configuration information indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; information about transmission resources used to send HARQ ACK or NACK; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; or indicator configuration information for whether PDCP non-sequential delivery is used. For each MBS or each bearer, configuration information may be provided indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; configuration information for RLC modes (TM, UM, or AM); configuration information for whether the function of segmented data is used in RLC entities; or indicator configuration information for whether PDCP non-sequential delivery is used. According to another method, the configuration information can be defined as the default configuration information, and in the absence of configuration information, the MBS bearer can be configured so that the UE has some of the described functions by default via the MBS bearer.

[0245] - Indicator configuration information indicating whether the bearer or bearer ID supporting (sending or receiving) MBS is a unicast bearer or a multicast bearer.

[0246] - Information about the MBS-specific carrier or cell (Cell, SCell, or PCell) (e.g., frequency, time resources, or cell ID).

[0247] - MBS-specific BWP information (e.g., DL BWP information or UL BWP information) or BWP ID information.

[0248] - Configure indicator information for header compression functionality or procedures for bearers supporting MBS (in this disclosure, header compression procedures (e.g., Robust Header Compression (ROHC), Ethernet Header Compression (EHC), or data compression procedures may be configured and supported), or configuration information for header compression procedures or data compression procedures (e.g., indicators indicating whether header compression context is further used)).

[0249] - In the configuration information above, the length of the PDCP serial number or RLC serial number can also be configured, and according to another method, the default length of the RLC serial number or PDCP serial number can be defined.

[0250] - In the above configuration information, you can also configure an indicator that indicates whether the RLC entity supporting MBS supports or allows one-way communication or supports or allows two-way communication.

[0251] When the configuration information of the MBS in the camped cell is not broadcast via system information, the UE can send a message or indicator to the base station, cell, or network requesting the broadcast of the system information of the MBS in the camped cell. When the base station or network receives the message or indicator, it can broadcast or send the MBS configuration information using the system information. By doing so, the base station can prevent the waste of transmission resources that might occur when MBS-related system information is broadcast unnecessarily and continuously.

[0252] The UE receiving system information 1j-05 can store or apply MBS configuration information, search for or determine MBS that the UE is interested in or wants to receive, and receive MBS data (MBS control data or MBS user data) through transmission resources. These transmission resources are used to send MBS control data channels or MBS user data channels for MBS that the UE is interested in. When the UE receives system information, intends to receive a service of interest, has a service of interest, or determines a system of interest, when the UE is in or enters a cell or domain that supports MBS as indicated in the system information, when an MBS (or session) is configured or connected, or when MBS configuration information or bearer configuration information is received or broadcast via system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message), or MBS channel control messages (e.g., sent from the MBS control data channel), the UE can configure unicast bearers, multicast bearers, or MBS bearers to receive MBS with the provided bearer structure.

[0253] The UE can receive MBS configuration data (1j-10) by receiving MBS data (e.g., MBS control data) through the MBCCH or transport resources of the MBS that the UE is interested in.

[0254] MBS configuration information can be sent by including some of the following configuration information that supports MBS.

[0255] - Whether MBS is supported.

[0256] - Configuration information regarding the physical channel of MBS or the DL or UL transport channel (e.g., MBCH, MBCCH, MBTCH, or DL-SCH).

[0257] Information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating transmission mode, etc.) is transmitted through these transmission resources by the physical channel or DL ​​or UL transmission channel (e.g., MBCH, MBCCH, or MBTCH).

[0258] - Configuration information regarding MBS supported by the current cell. For example, a list of MBS or a first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​for each MBS can be configured or broadcast, and information about the logical channel ID, bearer ID, or RNTI corresponding to the first or second ID of each MBS can be configured or broadcast. According to another method, the first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​or RNTI of an MBS can be configured or broadcast for each bearer (or bearer ID), each logical channel, each RLC configuration information segment, or each PDCP configuration information segment. The first ID can indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID can indicate a more detailed session or the type of MBS. Furthermore, the configuration information for MBS can include information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating the transmission mode, etc.) through which each MBS is supported, broadcast, or transmitted.

[0259] The bearer can be configured as Figure 1GThe provided bearer structure is used to receive MBS. Furthermore, configuration information may include indicator configuration information indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; information about transmission resources used to send HARQ ACK or NACK; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; or indicator configuration information for whether PDCP non-sequential delivery is used. For each MBS or each bearer, configuration information may be provided indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; configuration information for RLC modes (TM, UM, or AM); configuration information for whether the function of segmented data is used in RLC entities; or indicator configuration information for whether PDCP non-sequential delivery is used. According to another method, the configuration information can be defined as the default configuration information, and in the absence of configuration information, the MBS bearer can be configured so that the UE has some of the described functions by default via the MBS bearer.

[0260] - Indicator configuration information indicating whether the bearer or bearer ID supporting (sending or receiving) MBS is a unicast bearer or a multicast bearer.

[0261] - Information about the MBS-specific carrier or cell (Cell, SCell, or PCell) (e.g., frequency, time resources, or cell ID).

[0262] - MBS-specific BWP information (e.g., DL BWP information or UL BWP information) or BWP ID information.

[0263] - Configure indicator information for header compression functionality or procedures for bearers that support MBS (in this disclosure, header compression procedures (e.g., ROHC, EHC, or data compression procedures may be configured and supported), or configuration information for header compression procedures or data compression procedures (e.g., indicators indicating whether header compression context is further used)).

[0264] - In the configuration information above, the length of the PDCP serial number or RLC serial number can also be configured, and according to another method, the default length of the RLC serial number or PDCP serial number can be defined.

[0265] - In the above configuration information, you can also configure an indicator that indicates whether the RLC entity supporting MBS supports or allows one-way communication or supports or allows two-way communication.

[0266] When the UE receives MBS configuration information, in order to receive the MBS that the UE is interested in or wants to receive, the UE can identify the first ID, second ID, RNTI, or logical channel ID configured or allocated for the MBS that the UE is interested in or wants to receive. By using the identified ID, the UE can receive MBS data through the MBS user data channel and apply the principles of this disclosure. Figure 1G Alternatively, the method provided in 1H can be used to receive MBS (1j-15).

[0267] Figure 1K This is a diagram of a second signaling process supporting MBS according to an embodiment of this disclosure.

[0268] In the second signaling process supporting MBS according to this disclosure, the UE can identify the MBS it is interested in or that has been broadcast based on system information, establish a connection with the network, and indicate to the base station (or network) the MBS it is interested in or that it wants to receive, or its intention to receive the MBS. It then receives MBS-related configuration information from the base station (or network) and receives the MBS. During the second signaling process, the UE can remain in RRC idle mode, RRC connected mode, or RRC inactive mode (e.g., the UE can receive the MBS without switching RRC modes). According to another method, the UE can enter RRC connected mode from RRC idle mode or RRC inactive mode to indicate to the base station (or network) the MBS it is interested in or that it wants to receive, or its intention to receive the MBS, and receive MBS configuration information from the base station (or network). Alternatively, after receiving the MBS configuration information, the UE can receive the MBS in RRC connected mode, or it can receive the MBS in RRC idle mode or RRC inactive mode.

[0269] refer to Figure 1K UE 1k-01 can perform cell selection or reselection in RRC idle mode or RRC inactive mode, select an appropriate cell, and camp on that cell. Then, UE 1k-01 can receive system information 1k-05 from gNB 1k-02 in RRC idle mode, RRC inactive mode, or RRC connected mode, and can receive some MBS configuration information from the system information. The MBS configuration information may include the following configuration information. That is, to support MBS, the network can send system information including some of the following configuration information.

[0270] - Whether MBS is supported.

[0271] - Configuration information for the physical channel of MBS or the DL or UL transport channel (e.g., MBCH, MBCCH, MBTCH, or DL-SCH).

[0272] Information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating transmission mode, etc.) is transmitted through these transmission resources by the physical channel or DL ​​or UL transmission channel (e.g., MBCH, MBCCH, or MBTCH).

[0273] - Configuration information regarding MBS supported by the current cell. For example, a list of MBS or a first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​for each MBS can be configured or broadcast, and information about the logical channel ID, bearer ID, or RNTI corresponding to the first or second ID of each MBS can be configured or broadcast. According to another method, the first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​or RNTI of an MBS can be configured or broadcast for each bearer (or bearer ID), each logical channel, each RLC configuration information segment, or each PDCP configuration information segment. The first ID can indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID can indicate a more detailed session or the type of MBS. Furthermore, the configuration information for MBS can include information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating the transmission mode, etc.) through which each MBS is supported, broadcast, or transmitted.

[0274] The bearer can be configured as Figure 1GThe provided bearer structure is used to receive MBS. Furthermore, configuration information may include indicator configuration information indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; information about transmission resources used to send HARQ ACK or NACK; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; or indicator configuration information for whether PDCP non-sequential delivery is used. For each MBS or each bearer, configuration information may be provided indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; configuration information for RLC modes (TM, UM, or AM); configuration information for whether the function of segmented data is used in RLC entities; or indicator configuration information for whether PDCP non-sequential delivery is used. According to another method, the configuration information can be defined as the default configuration information, and in the absence of configuration information, the MBS bearer can be configured so that the UE has some of the described functions by default via the MBS bearer.

[0275] - Indicator configuration information indicating whether the bearer or bearer ID supporting (sending or receiving) MBS is a unicast bearer or a multicast bearer.

[0276] - Information about the MBS-specific carrier or cell (Cell, SCell, or PCell) of the MBS (e.g., frequency, time resources, or cell ID).

[0277] - MBS-specific BWP information (e.g., DL BWP information or UL BWP information) or BWP ID information.

[0278] - Configure indicator information for header compression functionality or procedures for bearers that support MBS (in this disclosure, header compression procedures (e.g., ROHC, EHC, or data compression procedures may be configured and supported), or configuration information for header compression procedures or data compression procedures (e.g., indicators indicating whether header compression context is further used)).

[0279] - In the configuration information above, the length of the PDCP serial number or RLC serial number can also be configured, and according to another method, the default length of the RLC serial number or PDCP serial number can be defined.

[0280] - In the above configuration information, you can also configure an indicator that indicates whether the RLC entity supporting MBS supports or allows one-way communication or supports or allows two-way communication.

[0281] When the configuration information of the MBS in the camped cell is not broadcast via system information, the UE can send a message or indicator to the base station, cell, or network requesting the broadcast of the system information of the MBS in the camped cell. When the base station or network receives the message or indicator, it can broadcast or send the MBS configuration information using the system information. By doing so, the base station can prevent the waste of transmission resources that might occur when MBS-related system information is broadcast unnecessarily and continuously.

[0282] A UE that receives or identifies MBS-related information via system information, a UE that identifies an MBS of interest to the UE that is being broadcast in the current cell via system information, or a UE that requests an MBS of interest from the network, may perform a random access procedure and send a first RRC message to the network. The first RRC message may be a newly defined RRC message for the MBS, or it may be defined as an RRCSetupRequest message, an RRCResumeRequest message, other previous RRC messages, MAC control information, RLC control information, or PDCP control information. The UE may include in the first RRC message an indicator indicating that it wants to receive the MBS, an indicator indicating that it wants to receive the MBS to establish an RRC connection with the network, or the first ID, second ID, logical channel ID, RNTI, or bearer ID of the MBS of interest to the UE or that the UE wants to receive. The UE may include in the first RRC message an indicator indicating the type of bearer (e.g., unicast or multicast bearer) or bearer structure used for MBS application, establishment, or use, or a preferred bearer type (e.g., unicast or multicast bearer) or preferred bearer structure, or an indicator indicating in which RRC mode (RRC connected mode, RRC idle mode, or RRC inactive mode) the UE wants to receive MBS. Alternatively, the UE may send the first RRC message by including an indicator for MBS that the UE is no longer interested in, that the UE wants to stop receiving, or that the UE has already stopped receiving, or an indicator indicating that the MBS is switched to another MBS. The indicators included by the UE in the first RRC message may be determined or indicated based on system information received in 1k-05. Furthermore, the first RRC message may include UE capability information. For example, when the UE wants to receive MBS, the UE may include configuration information about functions or configurations supported by the UE's capabilities, or configuration information about functions or configurations implemented in the UE, in the first RRC message, and may send the first RRC message to notify the base station. When a UE has previously configured a connection, stored a UE ID assigned from the network, or been indicated with a UE ID by an upper-layer entity (e.g., a NAS entity or an RRC entity), the UE may include the UE ID in a first RRC message and send the first RRC message so that the network can distinguish or identify the UE. For example, a base station or network may identify the UE based on the UE ID included in the first RRC message, by retrieving UE capability information from the core network, or by retrieving UE configuration information from a base station to which the UE previously connected. When the UE receives system information indicating that it will receive a service of interest, has a service of interest, or has identified a system of interest, when the UE is in or enters a cell or domain that supports MBS in the system information, or when MBS (or a session) is configured or connected, the UE may configure a connection with the network and send a first RRC message (1k-10).

[0283] During the 1k-10 process, when the base station receives the first RRC message, the base station can identify the MBS or UE capability information that the UE is interested in or wants to receive.

[0284] The base station or network can send a second RRC message 1k-15 to the UE to support or configure MBS (1k-15) for the UE. The second RRC message can be a newly defined RRC message for MBS, or it can be defined as an RRC Reconfiguration message, an RRC Reconfiguration message, or another previous RRC message.

[0285] The second RRC message may include MBS configuration information, MBS configuration information or bearer configuration information indicated by the UE in the first RRC message, or configuration information about unicast bearers, multicast bearers, or MBS bearers used to receive MBS.

[0286] The second RRC message can be sent by including some of the following configuration information that supports MBS.

[0287] - Whether MBS is supported.

[0288] - Configuration information regarding the physical channel of MBS or the DL or UL transport channel (e.g., MBCH, MBCCH, MBTCH, or DL-SCH).

[0289] Information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating transmission mode, etc.) is transmitted through these transmission resources by the physical channel or DL ​​or UL transmission channel (e.g., MBCH, MBCCH, or MBTCH).

[0290] - Configuration information regarding MBS supported by the current cell. For example, a list of MBS or a first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​for each MBS can be configured or broadcast, and information about the logical channel ID, bearer ID, or RNTI corresponding to the first or second ID of each MBS can be configured or broadcast. According to another method, the first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​or RNTI of an MBS can be configured or broadcast for each bearer (or bearer ID), each logical channel, each RLC configuration information segment, or each PDCP configuration information segment. The first ID can indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID can indicate a more detailed session or the type of MBS. Furthermore, the configuration information for MBS can include information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating the transmission mode, etc.) through which each MBS is supported, broadcast, or transmitted.

[0291] The bearer can be configured as Figure 1G The provided bearer structure is used to receive MBS. Furthermore, configuration information may include indicator configuration information indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; information about transmission resources used to send HARQ ACK or NACK; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; or indicator configuration information for whether PDCP non-sequential delivery is used. For each MBS or each bearer, configuration information may be provided indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; configuration information for RLC modes (TM, UM, or AM); configuration information for whether the function of segmented data is used in RLC entities; or indicator configuration information for whether PDCP non-sequential delivery is used. According to another method, the configuration information can be defined as the default configuration information, and in the absence of configuration information, the MBS bearer can be configured so that the UE has some of the described functions by default via the MBS bearer.

[0292] - Indicator configuration information indicating whether the bearer or bearer ID supporting (sending or receiving) MBS is a unicast bearer or a multicast bearer.

[0293] - Indicators or configuration information indicating the transition to RRC idle mode, RRC inactive mode, or RRC connected mode.

[0294] - MBS configuration information or bearer configuration information provided for receiving MBS in RRC idle mode.

[0295] - MBS configuration information or bearer configuration information provided for receiving MBS in RRC inactive mode.

[0296] - Information about the MBS-specific carrier or cell (Cell, SCell, or PCell) (e.g., frequency, time resources, or cell ID).

[0297] - MBS-specific BWP information (e.g., DL BWP information or UL BWP information) or BWP ID information.

[0298] - Information regarding the configuration of an indicator for a header compression function or process for a bearer supporting MBS (in this disclosure, a header compression process (e.g., ROHC, EHC, or data compression process may be configured and supported), or configuration information for the header compression process or data compression process (e.g., an indicator indicating whether a header compression context is further used)).

[0299] - In the configuration information above, the length of the PDCP serial number or RLC serial number can also be configured, and according to another method, the default length of the RLC serial number or PDCP serial number can be defined.

[0300] - In the above configuration information, you can also configure an indicator that indicates whether the RLC entity supporting MBS supports or allows one-way communication or supports or allows two-way communication.

[0301] The UE receiving the second RRC message can store or apply MBS-related configuration information, search for or determine MBS that the UE is interested in or wants to receive, and receive MBS data (MBS control data or MBS user data) through transmission resources. These transmission resources are used to send MBS control data channels or MBS user data channels for MBS that the UE is interested in. When the UE receives system information indicating it is about to receive a service of interest, has a service of interest, or has determined a system of interest; when the UE is in or enters a cell or domain that supports MBS according to the system information; when an MBS (or session) is configured or connected; or when MBS configuration information or bearer configuration information is received or broadcast via system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message), or MBS channel control messages (e.g., sent from the MBS control data channel), the UE can configure unicast bearers, multicast bearers, or MBS bearers to receive MBS with the provided bearer structure.

[0302] The UE can receive MBS configuration data via the received MBS data (e.g., MBS control data) through the MBCCH or transport resources of the MBS that the UE is interested in.

[0303] When the UE receives MBS configuration information, in order to receive the MBS that the UE is interested in or wants to receive, the UE can identify the first ID, second ID, RNTI, or logical channel ID configured or assigned for the MBS that the UE is interested in or wants to receive. By using the identified ID, the UE can receive MBS data through the MBS user data channel and apply the principles of this disclosure. Figure 1G Alternatively, the method provided in 1H can be used to receive MBS (1k-20).

[0304] It is possible to omit ciphering or integrity protection processing from the first or second RRC message. According to another method, to enhance security, it is possible to omit ciphering or integrity protection processing from the first or second RRC message, and it is also possible to apply ciphering or integrity protection processing to the first or second RRC message. According to another method, to further enhance security, it is possible to apply ciphering or integrity protection processing to the first or second RRC message, and it is also possible to apply ciphering or integrity protection processing to the first or second RRC message.

[0305] Figure 1L This is a diagram of a third signaling process supporting MBS according to an embodiment of this disclosure.

[0306] In the third signaling process supporting MBS according to this disclosure, the UE can identify the MBS it is interested in or that has been broadcast based on system information, establish a connection with the network, and indicate to the base station (or network) the MBS it is interested in or that it wants to receive, or its intention to receive the MBS. It then receives MBS-related configuration information from the base station (or network) and receives the MBS. During the third signaling process, the UE can remain in RRC idle mode, RRC connected mode, or RRC inactive mode. According to another method, the UE can enter RRC connected mode from RRC idle mode or RRC inactive mode to indicate to the base station (or network) the MBS it is interested in or that it wants to receive, or its intention to receive the MBS, and receive MBS configuration information from the base station (or network). Alternatively, after receiving the MBS configuration information, the UE can receive the MBS in RRC connected mode, or it can receive the MBS in RRC idle mode or RRC inactive mode.

[0307] refer to Figure 1L UE 1l-01 can perform cell selection or reselection in RRC idle mode or RRC inactive mode, select an appropriate cell, and camp on that cell. Then, UE 1l-01 can receive system information 1l-05 from gNB 1l-02 in RRC idle mode, RRC inactive mode, or RRC connected mode, and can receive some MBS configuration information from the system information. The MBS configuration information may include some of the following configuration information. That is, to support MBS, the network can send system information including some of the following configuration information.

[0308] - Whether MBS is supported.

[0309] - Configuration information for the physical channel of MBS or the DL or UL transport channel (e.g., MBCH, MBCCH, MBTCH, or DL-SCH).

[0310] Information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating transmission mode, etc.) is transmitted through these transmission resources by the physical channel or DL ​​or UL transmission channel (e.g., MBCH, MBCCH, or MBTCH).

[0311] - Configuration information regarding MBS supported by the current cell. For example, a list of MBS or a first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​for each MBS can be configured or broadcast, and information about the logical channel ID, bearer ID, or RNTI corresponding to the first or second ID of each MBS can be configured or broadcast. According to another method, the first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​or RNTI of an MBS can be configured or broadcast for each bearer (or bearer ID), each logical channel, each RLC configuration information segment, or each PDCP configuration information segment. The first ID can indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID can indicate a more detailed session or the type of MBS. Furthermore, the configuration information for MBS can include information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating the transmission mode, etc.) through which each MBS is supported, broadcast, or transmitted.

[0312] The bearer can be configured as Figure 1G The provided bearer structure is used to receive MBS. Furthermore, configuration information may include indicator configuration information indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; information about transmission resources used to send HARQ ACK or NACK; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; or indicator configuration information for whether PDCP non-sequential delivery is used. For each MBS or each bearer, configuration information may be provided indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; configuration information for RLC modes (TM, UM, or AM); configuration information for whether the function of segmented data is used in RLC entities; or indicator configuration information for whether PDCP non-sequential delivery is used. According to another method, the configuration information can be defined as the default configuration information, and in the absence of configuration information, the MBS bearer can be configured so that the UE has some of the described functions by default via the MBS bearer.

[0313] - Indicator configuration information indicating whether the bearer or bearer ID supporting (sending or receiving) MBS is a unicast bearer or a multicast bearer.

[0314] - Information about the MBS-specific carrier or cell (Cell, SCell, or PCell) (e.g., frequency, time resources, or cell ID).

[0315] - MBS-specific BWP information (e.g., DL BWP information or UL BWP information) or BWP ID information.

[0316] - Configure indicator information for header compression functionality or procedures for bearers that support MBS (in this disclosure, header compression procedures (e.g., ROHC, EHC, or data compression procedures may be configured and supported), or configuration information for header compression procedures or data compression procedures (e.g., indicators indicating whether header compression context is further used)).

[0317] - In the configuration information above, the length of the PDCP serial number or RLC serial number can also be configured, and according to another method, the default length of the RLC serial number or PDCP serial number can be defined.

[0318] - In the above configuration information, you can also configure an indicator that indicates whether the RLC entity supporting MBS supports or allows one-way communication or supports or allows two-way communication.

[0319] When the configuration information of the MBS in the camped cell is not broadcast via system information, the UE can send a message or indicator to the base station, cell, or network requesting the broadcast of the system information of the MBS in the camped cell. When the base station or network receives the message or indicator, it can broadcast or send the MBS configuration information using the system information. By doing so, the base station can prevent the waste of transmission resources that might occur when MBS-related system information is broadcast unnecessarily and continuously.

[0320] A UE that receives or identifies MBS-related information via system information, a UE that identifies an MBS of interest to the UE that is being broadcast in the current cell via system information, or a UE that requests an MBS of interest to the network from the network, can perform a random access procedure and send a first RRC message to the network. The first RRC message can be a newly defined RRC message for the MBS, or it can be defined as an RRCSetupRequest message, an RRCResumeRequest message, or other previous RRC messages. The UE can include an indicator in the first RRC message indicating that it wants to receive the MBS or an indicator indicating that receiving the MBS is necessary to establish an RRC connection with the network. Alternatively, when the UE previously configured a connection, when the UE stores a UE ID assigned from the network (e.g., a UE ID assigned from the core network (5G-S-TMSI) or a UE ID assigned from the base station for restoring an RRC connection (short I-RNTI or I-RNTI)), or when the UE ID is indicated by an upper-layer entity (e.g., a NAS entity or an RRC entity), the UE can send the first RRC message by including the UE ID so that the network can distinguish or identify the UE. For example, a base station or network can identify a UE based on the UE ID included in the first RRC message, by retrieving UE capability information from the core network, or by retrieving UE configuration information from base stations to which the UE previously connected. When a UE receives system information indicating that it will receive a service of interest, has a service of interest, or has identified a system of interest, when the UE is in or enters a cell or domain that supports MBS as stated in the system information, or when MBS (or a session) is configured or connected, the UE can configure its connection to the network and send the first RRC message.

[0321] During the 1l-10 process, when the base station receives the first RRC message, the base station can identify the MBS or UE capability information that the UE is interested in or wants to receive.

[0322] The base station or network can send a second RRC message 11-15 to the UE to support or configure MBS for the UE. The second RRC message can be a newly defined RRC message for MBS, or it can be defined as an RRC Release message, an RRC Reconfiguration message, or another previous RRC message.

[0323] The second RRC message may include MBS configuration information, MBS configuration information or bearer configuration information indicated by the UE in the first RRC message, or configuration information about unicast bearers, multicast bearers, or MBS bearers used to receive MBS.

[0324] The second RRC message can be sent by including some of the following configuration information that supports MBS.

[0325] - Whether MBS is supported.

[0326] - Configuration information regarding the physical channel of MBS or the DL or UL transport channel (e.g., MBCH, MBCCH, MBTCH, or DL-SCH).

[0327] Information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating transmission mode, etc.) is transmitted through these transmission resources by the physical channel or DL ​​or UL transmission channel (e.g., MBCH, MBCCH, or MBTCH).

[0328] - Configuration information regarding MBS supported by the current cell. For example, a list of MBS or a first ID (e.g., Temporary Mobile Group Identifier (TMGI)) or second ID (e.g., session identifier) ​​for each MBS can be configured or broadcast, and information regarding the logical channel ID, bearer ID, or RNTI corresponding to the first or second ID of each MBS can be configured or broadcast. According to another method, the first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​or RNTI of an MBS can be configured or broadcast for each bearer (or bearer ID), each logical channel, each RLC configuration information segment, or each PDCP configuration information segment. The first ID may indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID may indicate a more detailed session or the type of MBS. Furthermore, the configuration information for MBS may include information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating the transmission mode, etc.) through which each MBS is supported, broadcast, or transmitted.

[0329] The bearer can be configured as Figure 1GThe provided bearer structure is used to receive MBS. Furthermore, configuration information may include indicator configuration information indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; information about transmission resources used to send HARQ ACK or NACK; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; or indicator configuration information for whether PDCP non-sequential delivery is used. For each MBS or each bearer, configuration information may be provided indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; configuration information for RLC modes (TM, UM, or AM); configuration information for whether the function of segmented data is used in RLC entities; or indicator configuration information for whether PDCP non-sequential delivery is used. According to another method, the configuration information can be defined as the default configuration information, and in the absence of configuration information, the MBS bearer can be configured so that the UE has some of the described functions by default via the MBS bearer.

[0330] - Indicator configuration information indicating whether the bearer or bearer ID supporting (sending or receiving) MBS is a unicast bearer or a multicast bearer.

[0331] - Information about the MBS-specific carrier or cell (Cell, SCell, or PCell) of the MBS (e.g., frequency, time resources, or cell ID).

[0332] - MBS-specific BWP information (e.g., DL BWP information or UL BWP information) or BWP ID information.

[0333] - Information regarding the configuration of an indicator for a header compression function or process for a bearer supporting MBS (in this disclosure, a header compression process (e.g., ROHC, EHC, or data compression process may be configured and supported), or configuration information for the header compression process or data compression process (e.g., an indicator indicating whether a header compression context is further used)).

[0334] - In the configuration information above, the length of the PDCP serial number or RLC serial number can also be configured, and according to another method, the default length of the RLC serial number or PDCP serial number can be defined.

[0335] - In the above configuration information, you can also configure an indicator that indicates whether the RLC entity supporting MBS supports or allows one-way communication or supports or allows two-way communication.

[0336] When a UE receives system information indicating that it will receive a service of interest, has a service of interest, or has identified a system of interest, when the UE is in or enters a cell or domain that supports MBS as indicated in the system information, when MBS (or session) is configured or connected, or when MBS configuration information or bearer configuration information is received or broadcast via system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message), or control messages of the MBS channel (e.g., sent from the MBS control data channel), the UE can configure a unicast bearer, a multicast bearer, or an MBS bearer to receive an MBS with the provided bearer structure.

[0337] When the UE receives the second RRC message, the UE can apply the configuration information included in the second RRC message, and in response, can send a third RRC message (e.g., RRCSetupComplete or RRCResumecomplete) to the base station or network (1l-20).

[0338] The UE may include in the third RRC message an indicator indicating that the UE wants to receive MBS, an indicator indicating that the UE wants to receive MBS to establish an RRC connection with the network, or the first ID, second ID, logical channel ID, RNTI, or bearer ID of the MBS that the UE is interested in or wants to receive.

[0339] The UE may include in the first or third RRC message an indicator indicating the bearer type (e.g., unicast or multicast bearer) or bearer structure used for the MBS application, establishment, or use, or a preferred bearer type (e.g., unicast or multicast bearer) or preferred bearer structure, or an indicator indicating in which RRC mode (RRC connected mode, RRC idle mode, or RRC inactive mode) the UE wants to receive the MBS. Alternatively, the UE may send the first or third RRC message by including in the first or third RRC message an indicator for an MBS that the UE is no longer interested in, that the UE wants to stop receiving, or that the UE has already stopped receiving, or an indicator indicating that the MBS is switched to another MBS. The indicators included by the UE in the first or third RRC message may be determined or indicated based on system information received in 1l-05.

[0340] The base station may send a fourth RRC message (e.g., RRCReconfiguration 11-30) to the UE based on preferences reported by the UE, indicators indicated by the UE, or the base station's implementation details, to support MBS, configure or reconfigure the bearer through which the UE receives the MBS, or configure or reconfigure MBS-related configuration information. For example, the fourth RRC message may include configuration information for changing the bearer type (e.g., an indicator for converting a unicast bearer to a multicast bearer, an indicator for converting a multicast bearer to a unicast bearer, or corresponding bearer configuration information), or logical channel ID information, RNTI information, or first ID or second ID information of the MBS to be changed or updated for each MBS.

[0341] The fourth RRC message includes some of the following information.

[0342] - Whether MBS is supported.

[0343] - Configuration information regarding the physical channel of MBS or the DL or UL transport channel (e.g., MBCH, MBCCH, MBTCH, or DL-SCH).

[0344] Information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating transmission mode, etc.) is transmitted through these transmission resources by the physical channel or DL ​​or UL transmission channel (e.g., MBCH, MBCCH, or MBTCH).

[0345] - Configuration information regarding MBS supported by the current cell. For example, a list of MBS or a first ID (e.g., Temporary Mobile Group Identifier (TMGI)) or second ID (e.g., session identifier) ​​for each MBS can be configured or broadcast, and information regarding the logical channel ID, bearer ID, or RNTI corresponding to the first or second ID of each MBS can be configured or broadcast. According to another method, the first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​or RNTI of an MBS can be configured or broadcast for each bearer (or bearer ID), each logical channel, each RLC configuration information segment, or each PDCP configuration information segment. The first ID may indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID may indicate a more detailed session or the type of MBS. Furthermore, the configuration information for MBS may include information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating the transmission mode, etc.) through which each MBS is supported, broadcast, or transmitted.

[0346] The bearer can be configured as Figure 1G The provided bearer structure is used to receive MBS. Furthermore, configuration information may include indicator configuration information indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; information about transmission resources used to send HARQ ACK or NACK; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; or indicator configuration information for whether PDCP non-sequential delivery is used. For each MBS or each bearer, configuration information may be provided indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; configuration information for RLC modes (TM, UM, or AM); configuration information for whether the function of segmented data is used in RLC entities; or indicator configuration information for whether PDCP non-sequential delivery is used. According to another method, the configuration information can be defined as the default configuration information, and in the absence of configuration information, the MBS bearer can be configured so that the UE has some of the described functions by default via the MBS bearer.

[0347] - Indicator configuration information indicating whether the bearer or bearer ID supporting (sending or receiving) MBS is a unicast bearer or a multicast bearer.

[0348] - Indicator configuration information indicating whether the bearer or bearer ID supporting (sending or receiving) MBS is a unicast bearer or a multicast bearer.

[0349] - Indicators or configuration information indicating the transition to RRC idle mode, RRC inactive mode, or RRC connected mode.

[0350] - MBS configuration information or bearer configuration information provided for receiving MBS in RRC idle mode.

[0351] - MBS configuration information or bearer configuration information provided for receiving MBS in RRC inactive mode.

[0352] - Information about the MBS-specific carrier or cell (Cell, SCell, or PCell) of the MBS (e.g., frequency, time resources, or cell ID).

[0353] - MBS-specific BWP information (e.g., DL BWP information or UL BWP information) or BWP ID information.

[0354] - Information regarding the configuration of an indicator for a header compression function or process for a bearer supporting MBS (in this disclosure, a header compression process (e.g., ROHC, EHC, or data compression process may be configured and supported), or configuration information for the header compression process or data compression process (e.g., an indicator indicating whether a header compression context is further used)).

[0355] - In the configuration information above, the length of the PDCP serial number or RLC serial number can also be configured, and according to another method, the default length of the RLC serial number or PDCP serial number can be defined.

[0356] - In the above configuration information, you can also configure an indicator that indicates whether the RLC entity supporting MBS supports or allows one-way communication or supports or allows two-way communication.

[0357] After the UE receives the fourth RRC message and stores or applies the MBS-related configuration information, the UE can configure a fifth RRC message (e.g., RRCReconfigurationComplete 1l-35) to indicate successful configuration or reconfiguration, and send the fifth RRC message to the base station.

[0358] When the UE receives MBS configuration information, in order to receive the MBS that the UE is interested in or wants to receive in RRC connection mode, the UE can identify the first ID, second ID, RNTI, or logical channel ID configured or assigned for the MBS that the UE is interested in or wants to receive. By using the identified ID, the UE can receive MBS data through the MBS user data channel and apply the principles of this disclosure. Figure 1G Alternatively, the method provided in 1H can be used to receive MBS (1l-40).

[0359] The UE can receive MBS configuration data by receiving MBS data (e.g., MBS control data) through the MBCCH or transport resources for the MBS that the UE is interested in.

[0360] When the base station needs to switch the UE to RRC inactive mode or RRC idle mode (e.g., according to the base station's embodiment, a request from the UE or an instruction from the UE), the base station can configure a sixth RRC message (e.g., RRC Release 11-45) and send the sixth RRC message to the UE to cause the UE to switch to RRC idle mode or RRC inactive mode. The sixth RRC message 11-45 may include one or more of the following information so that the UE can continue to receive MBS even in RRC idle mode or RRC inactive mode.

[0361] - Whether MBS is supported.

[0362] - Configuration information regarding the physical channel of MBS or the DL or UL transport channel (e.g., MBCH, MBCCH, MBTCH, or DL-SCH).

[0363] Information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating transmission mode, etc.) is transmitted through these transmission resources by the physical channel or DL ​​or UL transmission channel (e.g., MBCH, MBCCH, or MBTCH).

[0364] - Configuration information regarding MBS supported by the current cell. For example, a list of MBS or a first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​for each MBS can be configured or broadcast, and information about the logical channel ID, bearer ID, or RNTI corresponding to the first or second ID of each MBS can be configured or broadcast. According to another method, the first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​or RNTI of an MBS can be configured or broadcast for each bearer (or bearer ID), each logical channel, each RLC configuration information segment, or each PDCP configuration information segment. The first ID can indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID can indicate a more detailed session or the type of MBS. Furthermore, the configuration information for MBS can include information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating the transmission mode, etc.) through which each MBS is supported, broadcast, or transmitted.

[0365] The bearer can be configured as Figure 1GThe provided bearer structure is used to receive MBS. Furthermore, configuration information may include indicator configuration information indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; information about transmission resources used to send HARQ ACK or NACK; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; or indicator configuration information for whether PDCP non-sequential delivery is used. For each MBS or each bearer, configuration information may be provided indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; configuration information for RLC modes (TM, UM, or AM); configuration information for whether the function of segmented data is used in RLC entities; or indicator configuration information for whether PDCP non-sequential delivery is used. According to another method, the configuration information can be defined as the default configuration information, and in the absence of configuration information, the MBS bearer can be configured so that the UE has some of the described functions by default via the MBS bearer.

[0366] - Indicator configuration information indicating whether the bearer or bearer ID supporting (sending or receiving) MBS is a unicast bearer or a multicast bearer.

[0367] - Indicator configuration information indicating whether the bearer or bearer ID supporting (sending or receiving) MBS is a unicast bearer or a multicast bearer.

[0368] - Indicators or configuration information indicating the transition to RRC idle mode, RRC inactive mode, or RRC connected mode.

[0369] - MBS configuration information or bearer configuration information provided for receiving MBS in RRC idle mode.

[0370] - MBS configuration information or bearer configuration information provided for receiving MBS in RRC inactive mode.

[0371] - Information about the MBS-specific carrier or cell (Cell, SCell, or PCell) of the MBS (e.g., frequency, time resources, or cell ID).

[0372] - MBS-specific BWP information (e.g., DL BWP information or UL BWP information) or BWP ID information.

[0373] - Information regarding the configuration of an indicator for a header compression function or process for a bearer supporting MBS (in this disclosure, a header compression process (e.g., ROHC, EHC, or data compression process may be configured and supported), or configuration information for the header compression process or data compression process (e.g., an indicator indicating whether a header compression context is further used)).

[0374] - In the configuration information above, the length of the PDCP serial number or RLC serial number can also be configured, and according to another method, the default length of the RLC serial number or PDCP serial number can be defined.

[0375] - In the above configuration information, you can also configure an indicator that indicates whether the RLC entity supporting MBS supports or allows one-way communication or supports or allows two-way communication.

[0376] When the UE receives MBS configuration information, in order to receive the MBS that the UE is interested in or wants to receive in RRC idle mode or RRC inactive mode, the UE can identify the first ID, second ID, RNTI, or logical channel ID configured or assigned for the MBS that the UE is interested in or wants to receive. By using the identified ID, the UE can receive MBS data through the MBS user data channel and apply the principles of this disclosure. Figure 1G Alternatively, the method provided in 1H can be used to receive MBS (1l-50).

[0377] To receive MBS, the UE can send a first RRC message 11-10, receive a second RRC message 11-15, retransmit a third RRC message 11-20, receive a fourth RRC message, send a fifth RRC message, and receive MBS in RRC connected mode. Alternatively, the UE can subsequently receive a sixth RRC message 11-45 and receive MBS in RRC idle mode or RRC inactive mode.

[0378] According to another method, in order to receive MBS, the UE can send a first RRC message 1l-10, receive a second RRC message 1l-15 (convert to RRC connection mode), retransmit a third RRC message 1l-20, receive a sixth RRC message 1l-45, and convert to RRC idle mode or RRC inactive mode to receive MBS in RRC idle mode or RRC inactive mode.

[0379] Encryption or integrity protection may not be applied to the first or second RRC message. According to another method, to enhance security, encryption or integrity protection may not be applied to the first or second RRC message, and encryption or integrity protection may be applied to the first or second RRC message. According to another method, to further enhance security, encryption or integrity protection may be applied to the first or second RRC message, and encryption or integrity protection may be applied to the first or second RRC message. Encryption or integrity protection may be applied to the third RRC message. Furthermore, encryption or integrity protection may also be applied to the fourth, fifth, or sixth RRC message.

[0380] Figure 1M This is a diagram of a fourth signaling process supporting MBS according to an embodiment of the present disclosure.

[0381] In the fourth signaling process supporting MBS according to this disclosure, the UE can identify the MBS it is interested in or that has been broadcast based on system information, establish a connection with the network, and indicate to the base station (or network) the MBS it is interested in or that it wants to receive, or its intention to receive the MBS. It then receives MBS-related configuration information from the base station (or network) and receives the MBS. In the third signaling process, the UE can remain in RRC idle mode, RRC connected mode, or RRC inactive mode. According to another method, the UE can enter RRC connected mode from RRC idle mode or RRC inactive mode to indicate to the base station (or network) the MBS it is interested in or that it wants to receive, or its intention to receive the MBS, and receive MBS configuration information from the base station (or network). Alternatively, after receiving the MBS configuration information, the UE can receive the MBS in RRC connected mode, or it can receive the MBS in RRC idle mode or RRC inactive mode.

[0382] refer to Figure 1M UE 1m-01 can perform cell selection or reselection in RRC idle mode or RRC inactive mode, select an appropriate cell, and camp on that cell. Then, UE 1m-01 can receive system information 1m-05 from gNB 1m-02 in RRC idle mode, RRC inactive mode, or RRC connected mode, and can receive some MBS configuration information from the system information. The MBS configuration information may include one or more of the following configuration information segments. That is, to support MBS, the network can send system information including one or more of the following configuration information segments.

[0383] - Whether MBS is supported.

[0384] - Configuration information for the physical channel of MBS or the DL or UL transport channel (e.g., MBCH, MBCCH, MBTCH, or DL-SCH).

[0385] Information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating transmission mode, etc.) is transmitted through these transmission resources by the physical channel or DL ​​or UL transmission channel (e.g., MBCH, MBCCH, or MBTCH).

[0386] - Configuration information regarding MBS supported by the current cell. For example, a list of MBS or a first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​for each MBS can be configured or broadcast, and information about the logical channel ID, bearer ID, or RNTI corresponding to the first or second ID of each MBS can be configured or broadcast. According to another method, the first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​or RNTI of an MBS can be configured or broadcast for each bearer (or bearer ID), each logical channel, each RLC configuration information segment, or each PDCP configuration information segment. The first ID can indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID can indicate a more detailed session or the type of MBS. Furthermore, the configuration information for MBS can include information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating the transmission mode, etc.) through which each MBS is supported, broadcast, or transmitted.

[0387] The bearer can be configured as Figure 1GThe provided bearer structure is used to receive MBS. Furthermore, configuration information may include indicator configuration information indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; information about transmission resources used to send HARQ ACK or NACK; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; or indicator configuration information for whether PDCP non-sequential delivery is used. For each MBS or each bearer, configuration information may be provided indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; configuration information for RLC modes (TM, UM, or AM); configuration information for whether the function of segmented data is used in RLC entities; or indicator configuration information for whether PDCP non-sequential delivery is used. According to another method, the configuration information can be defined as the default configuration information, and in the absence of configuration information, the MBS bearer can be configured so that the UE has some of the described functions by default via the MBS bearer.

[0388] - Indicator configuration information indicating whether the bearer or bearer ID supporting (sending or receiving) MBS is a unicast bearer or a multicast bearer.

[0389] - Information about the MBS-specific carrier or cell (Cell, SCell, or PCell) (e.g., frequency, time resources, or cell ID).

[0390] - MBS-specific BWP information (e.g., DL BWP information or UL BWP information) or BWP ID information.

[0391] - Configure indicator information for header compression functionality or procedures for bearers that support MBS (in this disclosure, header compression procedures (e.g., ROHC, EHC, or data compression procedures may be configured and supported), or configuration information for header compression procedures or data compression procedures (e.g., indicators indicating whether header compression context is further used)).

[0392] - In the configuration information above, the length of the PDCP serial number or RLC serial number can also be configured, and according to another method, the default length of the RLC serial number or PDCP serial number can be defined.

[0393] - In the above configuration information, you can also configure an indicator that indicates whether the RLC entity supporting MBS supports or allows one-way communication or supports or allows two-way communication.

[0394] When the configuration information of the MBS in the camped cell is not broadcast via system information, the UE can send a message or indicator to the base station, cell, or network requesting the broadcast of the system information of the MBS in the camped cell. When the base station or network receives the message or indicator, it can broadcast or send the MBS configuration information using the system information. By doing so, the base station can prevent the waste of transmission resources that might occur when MBS-related system information is broadcast unnecessarily and continuously.

[0395] A UE that receives or identifies MBS-related information via system information, a UE that identifies an MBS of interest to the UE that is being broadcast in the current cell via system information, or a UE that requests an MBS of interest from the network, can perform a random access procedure and send a first RRC message (1m-10) to the network. The first RRC message can be a newly defined RRC message for the MBS, or it can be defined as an RRCSetupRequest message, an RRCResumeRequest message, or other previous RRC messages. The UE may include in the first RRC message an indicator indicating that it wants to receive the MBS, an indicator indicating that it wants to receive the MBS to establish an RRC connection with the network, or the first ID, second ID, logical channel ID, RNTI, or bearer ID of the MBS that the UE is interested in or wants to receive. The UE may include in the first RRC message an indicator indicating the type of bearer (e.g., unicast or multicast bearer) or bearer structure used for MBS application, establishment, or use, or a preferred bearer type (e.g., unicast or multicast bearer) or preferred bearer structure, or an indicator indicating in which RRC mode (RRC connected mode, RRC idle mode, or RRC inactive mode) the UE wants to receive MBS. Alternatively, the UE may send the first RRC message by including an indicator for an MBS that the UE is no longer interested in, that the UE wants to stop receiving, or that the UE has already stopped receiving, or an indicator indicating that the MBS is being switched to another MBS. The indicators included by the UE in the first RRC message may be determined or indicated based on system information received in 1m-05. Furthermore, the UE may report UE capability information for MBS to the base station or network via additional RRC messages. For example, when a base station sends an RRC message requesting UE capability information to a UE, the UE, in response to the RRC message, may include configuration information about functions or configurations supported by the UE's capabilities when the UE wants to receive MBS, or configuration information about functions or configurations implemented in the UE, in the UE capability response RRC message, and may send the UE capability response RRC message to the base station or network. When the UE previously configured a connection, when the UE stores a UE ID assigned from the network (e.g., a UE ID assigned from the core network (5G-S-TMSI) or a UE ID assigned from the base station for resuming RRC connection (short I-RNTI or I-RNTI)), or when the UE ID is indicated by an upper-layer entity (e.g., a NAS entity or an RRC entity), the UE may send a first RRC message by including the UE ID in the first RRC message so that the network can distinguish or identify the UE. For example, the base station or network may identify the UE based on the UE ID included in the first RRC message, may identify the UE by retrieving UE capability information from the core network, or may identify the UE by retrieving UE configuration information from the base station to which the UE previously connected.When a UE receives system information indicating that it will receive a service of interest, has a service of interest, or has identified a system of interest, when the UE is in or enters a cell or domain that supports MBS as indicated in the system information, or when MBS (or session) is configured or connected, the UE can configure its connection to the network and send a first RRC message.

[0396] During the 1m-10 process, when the base station receives the first RRC message, the base station can identify the MBS or UE capability information that the UE is interested in or wants to receive.

[0397] The base station or network can send a second RRC message 1m-15 to the UE to support or configure MBS (1m-15) for the UE. The second RRC message can be a newly defined RRC message for MBS, or it can be defined as an RRC Reconfiguration message, an RRC Reconfiguration message, or another previous RRC message.

[0398] The second RRC message may include MBS configuration information, MBS configuration information or bearer configuration information indicated by the UE in the first RRC message, or configuration information about unicast bearers, multicast bearers, or MBS bearers used to receive MBS.

[0399] The second RRC message can be sent by including one or more of the following configuration information segments that support MBS.

[0400] - Whether MBS is supported.

[0401] - Configuration information regarding the physical channel of MBS or the DL or UL transport channel (e.g., MBCH, MBCCH, MBTCH, or DL-SCH).

[0402] Information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating transmission mode, etc.) is transmitted through these transmission resources by the physical channel or DL ​​or UL transmission channel (e.g., MBCH, MBCCH, or MBTCH).

[0403] - Configuration information regarding MBS supported by the current cell. For example, a list of MBS or a first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​for each MBS can be configured or broadcast, and information about the logical channel ID, bearer ID, or RNTI corresponding to the first or second ID of each MBS can be configured or broadcast. According to another method, the first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​or RNTI of an MBS can be configured or broadcast for each bearer (or bearer ID), each logical channel, each RLC configuration information segment, or each PDCP configuration information segment. The first ID can indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID can indicate a more detailed session or the type of MBS. Furthermore, the configuration information for MBS can include information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating the transmission mode, etc.) through which each MBS is supported, broadcast, or transmitted.

[0404] The bearer can be configured as Figure 1G The provided bearer structure is used to receive MBS. Furthermore, configuration information may include indicator configuration information indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; information about transmission resources used to send HARQ ACK or NACK; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; or indicator configuration information for whether PDCP non-sequential delivery is used. For each MBS or each bearer, configuration information may be provided indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; configuration information for RLC modes (TM, UM, or AM); configuration information for whether the function of segmented data is used in RLC entities; or indicator configuration information for whether PDCP non-sequential delivery is used. According to another method, the configuration information can be defined as the default configuration information, and in the absence of configuration information, the MBS bearer can be configured so that the UE has some of the described functions by default via the MBS bearer.

[0405] - Indicator configuration information indicating whether the bearer or bearer ID supporting (sending or receiving) MBS is a unicast bearer or a multicast bearer.

[0406] - Information about the MBS-specific carrier or cell (Cell, SCell, or PCell) (e.g., frequency, time resources, or cell ID).

[0407] - MBS-specific BWP information (e.g., DL BWP information or UL BWP information) or BWP ID information.

[0408] - Information regarding the configuration of an indicator for a header compression function or process for a bearer supporting MBS (in this disclosure, a header compression process (e.g., ROHC, EHC, or data compression process may be configured and supported), or configuration information for the header compression process or data compression process (e.g., an indicator indicating whether a header compression context is further used)).

[0409] - In the configuration information above, the length of the PDCP serial number or RLC serial number can also be configured, and according to another method, the default length of the RLC serial number or PDCP serial number can be defined.

[0410] - In the above configuration information, you can also configure an indicator that indicates whether the RLC entity supporting MBS supports or allows one-way communication or supports or allows two-way communication.

[0411] The UE receiving the second RRC message can store or apply MBS-related configuration information, search for or determine MBS that the UE is interested in or wants to receive, and receive MBS data (MBS control data or MBS user data) through transmission resources. The MBS control data channel or MBS user data channel for the MBS that the UE is interested in is transmitted through these transmission resources. When the UE receives system information indicating that it will receive a service of interest, has a service of interest, or determines a system of interest, when the UE is in or enters a cell or domain that supports MBS according to the system information, when the MBS (or session) is configured or connected, or when the MBS configuration information or bearer configuration information is received or broadcast via system information, RRC messages (RRCSetup, RRCResume, RRCReconfiguration, RRCRelease, or a newly defined new RRC message), or MBS channel control messages (e.g., sent from the MBS control data channel), the UE can configure a unicast bearer, multicast bearer, or MBS bearer to receive MBS with the provided bearer structure.

[0412] When the UE receives the second RRC message, the UE can apply the configuration information included in the second RRC message, and in response, can send a third RRC message (e.g., RRCSetupComplete or RRCResumecomplete) to the base station or network (1m-20).

[0413] The UE can receive MBS configuration data by receiving MBS data (e.g., MBS control data) through the MBCCH or transport resources of the MBS that the UE is interested in.

[0414] When the UE receives MBS configuration information, in order to receive the MBS that the UE is interested in or wants to receive, the UE can identify the first ID, second ID, RNTI, or logical channel ID configured or assigned for the MBS that the UE is interested in or wants to receive. By using the identified ID, the UE can receive MBS data through the MBS user data channel and apply the principles of this disclosure. Figure 1G Alternatively, the method provided in 1H can be used to receive MBS (1m-25).

[0415] The base station may send a fourth RRC message (e.g., RRCReconfiguration 1m-30) to the UE based on preferences reported by the UE, indicators indicated by the UE, or the base station's implementation, to support MBS, configure or reconfigure the bearer through which the UE receives the MBS, or configure or reconfigure MBS-related configuration information. For example, the fourth RRC message may include configuration information for changing the bearer type (e.g., an indicator for converting a unicast bearer to a multicast bearer, an indicator for converting a multicast bearer to a unicast bearer, or corresponding bearer configuration information), or logical channel ID information, RNTI information, or first ID or second ID information of the MBS to be changed or updated for each MBS.

[0416] After the UE receives the fourth RRC message and stores or applies the MBS-related configuration information, the UE can configure a fifth RRC message to indicate successful reconfiguration (e.g., RRCReconfigurationComplete 1m-35) and send the fifth RRC message to the base station.

[0417] The UE can receive MBS configuration data by receiving MBS data (e.g., MBS control data) through the MBCCH or transport resources of the MBS that the UE is interested in.

[0418] When the UE receives MBS configuration information, in order to receive the MBS that the UE is interested in or wants to receive, the UE can identify the first ID, second ID, RNTI, or logical channel ID configured or allocated for the MBS that the UE is interested in or wants to receive. By using the identified ID, the UE can receive MBS data through the MBS user data channel and apply the principles of this disclosure. Figure 1G Alternatively, the method provided in 1H can be used to receive MBS (1m-40).

[0419] When the base station needs to switch the UE to RRC inactive mode or RRC idle mode (e.g., according to the base station's embodiment, a request from the UE, or an instruction from the UE), the base station can configure a sixth RRC message (e.g., RRC Release 1m-45) and send the sixth RRC message to the UE to switch the UE to RRC idle mode or RRC inactive mode. The sixth RRC message 1m-45 may include one or more of the following information so that the UE can continue to receive MBS (1m-50) even in RRC idle mode or RRC inactive mode.

[0420] - Whether MBS is supported.

[0421] - Configuration information regarding the physical channel of MBS or the DL or UL transport channel (e.g., MBCH, MBCCH, MBTCH, or DL-SCH).

[0422] Information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating transmission mode, etc.) is transmitted through these transmission resources by the physical channel or DL ​​or UL transmission channel (e.g., MBCH, MBCCH, or MBTCH).

[0423] - Configuration information regarding MBS supported by the current cell. For example, a list of MBS or a first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​for each MBS can be configured or broadcast, and information about the logical channel ID, bearer ID, or RNTI corresponding to the first or second ID of each MBS can be configured or broadcast. According to another method, the first ID (e.g., TMGI) or second ID (e.g., session identifier) ​​or RNTI of an MBS can be configured or broadcast for each bearer (or bearer ID), each logical channel, each RLC configuration information segment, or each PDCP configuration information segment. The first ID can indicate the PLMN providing the MBS, the type of MBS, or the session. The second ID can indicate a more detailed session or the type of MBS. Furthermore, the configuration information for MBS can include information about transmission resources (frequency, time resources, transmission period, BWP (or BWP ID), bandwidth, dedicated frequency (frequency information or SCell ID), subcarrier spacing, subframe number, ID indicating the transmission mode, etc.) through which each MBS is supported, broadcast, or transmitted.

[0424] The bearer can be configured as Figure 1G The provided bearer structure is used to receive MBS. Furthermore, configuration information may include indicator configuration information indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; information about transmission resources used to send HARQ ACK or NACK; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; or indicator configuration information for whether PDCP non-sequential delivery is used. For each MBS or each bearer, configuration information may be provided indicating HARQ reordering, HARQ retransmission, or whether HARQ ACK or NACK is used; indicator configuration information indicating whether RLC reordering is used; indicator configuration information indicating whether RLC sequential delivery is used; configuration information about RLC reordering timer values; configuration information for RLC modes (TM, UM, or AM); configuration information for whether the function of segmented data is used in RLC entities; or indicator configuration information for whether PDCP non-sequential delivery is used. According to another method, the configuration information can be defined as the default configuration information, and in the absence of configuration information, the MBS bearer can be configured so that the UE has some of the described functions by default via the MBS bearer.

[0425] - Indicator configuration information indicating whether the bearer or bearer ID supporting (sending or receiving) MBS is a unicast bearer or a multicast bearer.

[0426] - Indicator configuration information indicating whether the bearer or bearer ID supporting (sending or receiving) MBS is a unicast bearer or a multicast bearer.

[0427] - Indicators or configuration information indicating the transition to RRC idle mode, RRC inactive mode, or RRC connected mode.

[0428] - MBS configuration information or bearer configuration information provided for receiving MBS in RRC idle mode.

[0429] - MBS configuration information or bearer configuration information provided for receiving MBS in RRC inactive mode.

[0430] - Information about the MBS-specific carrier or cell (Cell, SCell, or PCell) of the MBS (e.g., frequency, time resources, or cell ID).

[0431] - MBS-specific BWP information (e.g., DL BWP information or UL BWP information) or BWP ID information.

[0432] - Information regarding the configuration of an indicator for a header compression function or process for a bearer supporting MBS (in this disclosure, a header compression process (e.g., ROHC, EHC, or data compression process may be configured and supported), or configuration information for the header compression process or data compression process (e.g., an indicator indicating whether a header compression context is further used).

[0433] - In the configuration information above, the length of the PDCP serial number or RLC serial number can also be configured, and according to another method, the default length of the RLC serial number or PDCP serial number can be defined.

[0434] - In the above configuration information, you can also configure an indicator that indicates whether the RLC entity supporting MBS supports or allows one-way communication or supports or allows two-way communication.

[0435] When the UE receives MBS configuration information, in order to receive the MBS that the UE is interested in or wants to receive, the UE can identify the first ID, second ID, RNTI, or logical channel ID configured or assigned for the MBS that the UE is interested in or wants to receive. By using the identified ID, the UE can receive MBS data through the MBS user data channel and apply the principles of this disclosure. Figure 1G Alternatively, the method provided in 1H can be used to receive MBS (1m-15).

[0436] To receive MBS, the UE can send a first RRC message 1m-10, receive a second RRC message 1m-15, retransmit a third RRC message 1m-20, receive a fourth RRC message, send a fifth RRC message, and receive MBS in RRC connected mode. Alternatively, the UE can subsequently receive a sixth RRC message 1m-45 and receive MBS in RRC idle mode or RRC inactive mode.

[0437] According to another method, in order to receive MBS, the UE can send a first RRC message 1m-10, receive a second RRC message 1m-15 (converted to RRC connection mode), retransmit a third RRC message 1m-20, receive a sixth RRC message 1m-45, and convert to RRC idle mode or RRC inactive mode to receive MBS in RRC idle mode or RRC inactive mode.

[0438] Encryption or integrity protection may not be applied to the first or second RRC message. According to another method, to enhance security, encryption or integrity protection may not be applied to the first or second RRC message, and encryption or integrity protection may be applied to the first or second RRC message. According to another method, to further enhance security, encryption or integrity protection may be applied to the first or second RRC message, and encryption or integrity protection may be applied to the first or second RRC message. Encryption or integrity protection may be applied to the third RRC message. Furthermore, encryption or integrity protection may also be applied to the fourth, fifth, or sixth RRC message.

[0439] In the next-generation mobile communication system according to this disclosure, a first signaling process, a second signaling process, a third signaling process, or a fourth signaling process provided in accordance with this disclosure may be supported.

[0440] Figure 1N This is a diagram illustrating a situation where, according to an embodiment of the present disclosure, when a UE receives general data service and MBS in RRC connection mode, the general data and MBS data conflict or overlap with each other.

[0441] refer to Figure 1N A UE in RRC connection mode that receives general data service or MBS can receive first scheduling information 1n-05 for general data service and second scheduling information 1n-10 for MBS data.

[0442] The first scheduling information 1n-05 can indicate the time or frequency resources for transmitting general data of DL by using the DCI of the PDCCH scrambled by the first RNTI (e.g., C-RNTI, which is the RNTI used for scheduling general data). According to another method, the first scheduling information can be indicated as time or frequency resources configured for transmitting general data of DL by using an RRC message. According to yet another method, the first scheduling information can be indicated as periodic time or frequency resources configured for transmitting general data of DL by using an RRC message, or the first scheduling information can be indicated by using the DCI of the PDCCH to activate or deactivate periodic time or frequency resources.

[0443] The second scheduling information can indicate the time or frequency resources for transmitting DL MBS data by using the DCI of the PDCCH scrambled with the second RNTI (e.g., MBS-RNTI, which is the RNTI used for scheduling MBS data or the RNTI for each MBS). According to another method, the second scheduling information can be indicated as configuring time or frequency resources for transmitting DL MBS data by using system information, RRC messages, control channels, or control messages of the MBS. According to yet another method, the second scheduling information can be indicated as configuring periodic time or frequency resources for transmitting DL MBS data by using system information, RRC messages, control channels, or control messages of the MBS, or the second scheduling information can be indicated by using the DCI of the PDCCH to activate or deactivate periodic time or frequency resources.

[0444] When the UE receives the first scheduling information and the second scheduling information (1n-15), and when the time resources or frequency resources of the DL indicated by the first scheduling information or the second scheduling information are the same, overlap or conflict with each other, the UE may need to process the first scheduling information and the second scheduling information.

[0445] Therefore, according to this disclosure, a method for processing the first scheduling information and the second scheduling information is provided as described above, when the UE receives the first scheduling information and the second scheduling information (1n-15) and when the time resources or frequency resources of the DL indicated by the first scheduling information or the second scheduling information are the same, overlap, or conflict with each other.

[0446] - First method: When the time resources or frequency resources indicated by the first scheduling information and the second scheduling information are the same, overlap, or conflict with each other, the UE can receive general data via the time resources or frequency resources according to the first scheduling information. Furthermore, the UE may not receive MBS data indicated by the second scheduling information, may ignore the MBS data indicated by the second scheduling information, or may disregard the second scheduling information. According to another method, when a transmission resource (e.g., PUCCH) through which HARQ ACK or NACK of DL MBS data indicated by the second scheduling information is configured, or is configured to transmit HARQ ACK or NACK, the UE can indicate a NACK indicating unsuccessful reception of MBS, and can request a retransmission, and can subsequently receive the unreceived DL MBS data through the retransmission.

[0447] - Second method: When the time resources or frequency resources indicated by the first scheduling information and the second scheduling information are the same, overlap, or conflict with each other, the UE can receive MBS data via the time resources or frequency resources according to the second scheduling information. Furthermore, the UE may choose not to receive the general data indicated by the first scheduling information, may ignore the general data indicated by the first scheduling information, or may disregard the first scheduling information. However, the UE can request a retransmission by indicating a NACK (HARQ ACK or NACK for general data relative to DL) through a transmission resource (e.g., PUCCH), and subsequently receive the unreceived general data of DL through the retransmission.

[0448] - Third method: When the UE is capable of receiving different data simultaneously via transmission resources with the same time or frequency resources, the UE can receive general data and MBS data indicated by the first scheduling information and the second scheduling information, respectively. For example, the third method can be applied when the UE includes multiple antennas or meets relatively more complex requirements, depending on the UE's capabilities.

[0449] - Fourth method: Whether the UE should perform the first method, the second method, or the third method can be configured or indicated by the base station through RRC messages or system information.

[0450] - Fifth Method: Through transmission resources with the same time or frequency resources, the base station can transmit different general data and MBS data by multiplexing different data into one type of data (e.g., MAC PDU). That is, via transmission resources with the same time or frequency resources, the UE can receive one type of data (e.g., MAC PDU), and this one type of data can include multiplexed general data and MBS data. Within this one type of data, each segment of general data can be identified based on a logical channel ID corresponding to each segment of general data (e.g., an ID included in the MAC header), and each segment of MBS data can be identified based on a logical channel ID corresponding to each segment of MBS data (e.g., an ID included in the MAC header). When the UE receives this one type of data and performs data processing on it, the UE can receive (or demultiplex) the data corresponding to the logical channel ID configured in the UE, and can send the data to the upper-layer entity corresponding to the logical channel ID (e.g., an RLC entity or an upper-layer entity), and can discard data corresponding to logical channel IDs not configured in the UE.

[0451] Figure 10 This is a diagram illustrating the signaling process for efficiently supporting MBS according to an embodiment of this disclosure.

[0452] For example, to support MBS, signaling procedures 1o-05 are provided in which the UE receiving MBS data sends feedback to the base station, signaling procedure 1o-10 is provided in which the UE receiving MBS data receives MBS-related control messages from the base station, or signaling procedures 1o-20 and 1o-25 are provided in which the base station sends MBS-related control messages to the UE and the UE sends a response to them.

[0453] refer to Figure 10 ,exist Figure 10 In signaling procedure 1o-05, the UE receiving MBS data can send feedback or indication information about the MBS to the network or base station. For example, when a predetermined event occurs, when there is a service the UE is interested in (or wants to receive), when the service the UE is interested in (or wants to receive) changes, when the UE wants to stop receiving the service the UE is interested in (or wants to receive), when the UE suspends MBS, or when the UE changes its method of receiving MBS or changes its RRC mode or bearer, the UE can send feedback or indication information about the MBS to the network or base station (1o-05). According to another method, when there is a request from the network (1o-03), the feedback or indication information can be sent by the UE. The information sent by the UE to the base station relative to the MBS may include some of the following:

[0454] - Information about the MBS that the UE is interested in or wants to receive (e.g., the first ID, second ID, logical channel ID, RNTI, or bearer ID for the MBS).

[0455] - When the UE receives or configures an MBS, the RRC connection state (e.g., RRC idle mode, RRC connected mode, or RRC inactive mode) is selected by the UE.

[0456] - When the UE receives or configures an MBS, the bearer structure or configuration information that the UE preferentially selects (e.g., unicast bearer, multicast bearer, ...) Figure 1G The description includes the preferred structure within the bearer structure, and the UE's preferred configuration of functions, etc.

[0457] - When the UE receives or configures an MBS, the service type that the UE preferentially selects (e.g., unicast service (dedicated service) or multicast service (multicast, broadcast or public service)).

[0458] - An indicator indicating the UE's intention to no longer receive MBS, an indicator indicating the intention to stop receiving MBS, an indicator indicating the intention to further receive MBS, an indicator requesting to change MBS to another MBS (or the first ID, second ID, logical channel ID, bearer ID, or RNTI for another MBS), or an indicator indicating the UE's interest in MBS.

[0459] - An indicator that shows whether the reception quality is good or bad from the UE's perspective relative to the MBS.

[0460] - Indicators that indicate whether MBS was successfully received or not, such as HARQ ACK or NACK feedback.

[0461] When a UE sends the aforementioned information regarding MBS to a base station, the UE can send this information only in RRC connection mode. For example, when requesting the aforementioned information from a base station, or when a UE needs to send the aforementioned information, a UE in RRC connection mode can configure and send the aforementioned information by using RRC messages, MAC control information, RLC control information, or PDCP control information through the configuration of the SRB, DRB, or MBS bearer (unicast or multicast bearer) for the UE in RRC connection mode. According to another method, when requesting the aforementioned information from a base station or when a UE needs to send the aforementioned information, a UE in RRC idle mode or RRC inactive mode can configure its connection to the network (triggering an RRC connection procedure or RRC connection recovery procedure), can switch from RRC idle mode or RRC inactive mode to RRC connection mode, and can configure and send the aforementioned information by using RRC messages, MAC control information, RLC control information, or PDCP control information through the configuration of the SRB, DRB, or MBS bearer (unicast or multicast bearer) for the UE in RRC connection mode. According to another method, when the UE sends the aforementioned information regarding MBS to the base station, the UE can send feedback or indication information in RRC connected mode, RRC inactive mode, or RRC idle mode, using transmission resources indicated in the system information, transmission resources configured using RRC messages, or transmission resources indicated by the PDCCH including the RNTI indicating MBS. When the UE sends feedback as described above, the base station can manage MBS resources relatively more efficiently.

[0462] refer to Figure 10 From 1o-10, the base station can send control information for the MBS to the UE receiving the MBS. The control information for the MBS can be sent through channels, transmission resources, RRC messages, MAC control information, RLC control information, or PDCP control information for the MBS (1o-10).

[0463] Control information for MBS may include some of the following.

[0464] - An indicator that requests a pause in MBS reception.

[0465] - An indicator that instructs the base station to suspend MBS or to stop receiving MBS.

[0466] - The ID of the MBS to be suspended or stopped from receiving. For example, this may include a first ID, a second ID, a logical channel ID, an RNTI, or a bearer ID corresponding to the MBS, to indicate to the UE in more detail which MBS should be suspended or which MBS the UE will stop receiving. According to another method, control information can be sent and indicated via a PDCCH scrambled with the RNTI corresponding to the MBS. According to yet another method, the first ID, logical channel ID, RNTI, or bearer ID can be included in a list and sent to support multiple MBS.

[0467] - To indicate in more detail which MBS should be paused or which MBS the UE should stop receiving, the first or second ID value of the MBS configured in the MBS list configured via system information or RRC message can be mapped to natural values ​​in ascending order, and the natural values ​​can be input or mapped to a bitmap so that the bitmap can indicate the MBS.

[0468] The start and stop times for receiving MBS, or the time for pausing MBS, can be indicated using time units (subframes, slots, or symbols). For example, it can indicate which time unit is in the cycle of transmitting MBS. Alternatively, it can indicate which time unit follows the start time of receiving control information.

[0469] When a base station sends control information for MBS to a UE, the base station can send the control information to the UE in RRC inactive mode, RRC idle mode, or RRC connected mode. For example, the base station can configure and send information to the UE in RRC inactive mode, RRC idle mode, or RRC connected mode by using RRC messages, MAC control information, RLC control information, or PDCP control information via SRB, DRB, or MBS bearer (unicast or multicast bearer). According to another method, the base station can send control information to the UE in RRC connected mode, RRC inactive mode, or RRC idle mode by using transmission resources indicated in system information, transmission resources configured in RRC messages, or transmission resources indicated by a PDCCH including an RNTI indicating MBS.

[0470] When the UE receives control information from the base station (1o-10), the UE can send corresponding feedback to the base station as... Figure 10 The described feedback or instruction information (1o-15).

[0471] When the UE receives control information from the base station (1o-10), and when the UE still has MBS of interest or when the UE still wants to receive MBS, the UE can re-receive such information. Figure 1K , 1LThe control information related to MBS (e.g., system information, RRC messages, or MBS control messages) described in 1M or 1N, or the execution (or triggering) of an RRC connection procedure or an RRC connection recovery procedure to receive or request configuration information from the base station for re-receiving MBS, can re-receive MBS configuration information, can reconfigure MBS configuration information, and can continuously receive MBS.

[0472] According to another method, when the UE receives control information from the base station (1o-10), if the UE is not in RRC connected mode and is in RRC idle mode or RRC inactive mode, or if the UE still has MBS of interest to the UE, or if the UE still wants to receive MBS, the UE can re-receive such information. Figure 1K , 1L The control information related to MBS (e.g., system information, RRC messages, or MBS control messages) described in 1M or 1N, or the execution (or triggering) of the RRC connection process or the RRC connection recovery process, can receive or request configuration information from the base station for re-receiving MBS, can re-receive MBS configuration information, can reconfigure MBS configuration information, and can continuously receive MBS.

[0473] As mentioned above, by sending control information to the UE, the base station can manage the resources of the MBS relatively more efficiently.

[0474] refer to Figure 10 In 1o-20 and 1o-25, to identify how many UEs have received MBS, the base station can configure and send a message requesting a response to indicate whether a UE receiving MBS data has received MBS or to count the number of UEs receiving MBS. A UE receiving the message requesting a response to indicate whether an MBS has been received or to count the number of UEs receiving MBS can configure and send the response message to the base station (1o-25).

[0475] A request message configured by the base station to indicate whether MBS has been received or to count the number of UEs receiving MBS can be sent to a UE in RRC idle mode, RRC inactive mode, or RRC connected mode, or a UE in RRC idle mode, RRC inactive mode, or RRC connected mode can receive the request message. Furthermore, when a UE is in RRC idle mode, RRC inactive mode, or RRC connected mode, the UE receiving the request message can configure a response message for the request message and can send the response message using RRC messages, MAC control information, RLC control information, or PDCP control information via the SRB, DRB, or MBS bearer (unicast or multicast bearer) configured for the UE. Additionally, the UE can send the response message via the transmission resources indicated in the system information, the transmission resources configured in the RRC message, or the transmission resources indicated by the PDCCH including the RNTI indicating MBS.

[0476] According to another method, a request message configured by the base station to indicate whether MBS has been received or to count the number of UEs receiving MBS can be sent to a UE in RRC idle mode, RRC inactive mode, or RRC connected mode, or a UE in RRC idle mode, RRC inactive mode, or RRC connected mode can receive the request message. Furthermore, UEs in RRC connected mode among those receiving the request message can configure a response message for the request message and can send the response message via SRB, DRB, or MBS bearer (unicast or multicast bearer) using RRC messages, MAC control information, RLC control information, or PDCP control information. Additionally, the UE can send the response message via transport resources indicated in the system information, transport resources configured in the RRC message, or transport resources indicated by the PDCCH including the RNTI indicating MBS. According to another method, a UE in RRC idle mode or RRC inactive mode among those receiving the request message can execute an RRC connection procedure or an RRC connection recovery procedure to convert the RRC idle mode or RRC inactive mode to an RRC connected mode. It can then send a response message using RRC messages, MAC control information, RLC control information, or PDCP control information via the SRB, DRB, or MBS bearer (unicast or multicast bearer) configured for the UE. Alternatively, the UE can send the response message using the transport resources indicated in the system information, the transport resources configured in the RRC message, or the transport resources indicated by the PDCCH including the RNTI indicating the MBS.

[0477] Figure 1P This is a diagram illustrating a method for instructing each of a plurality of MBS according to an embodiment of the present disclosure.

[0478] refer to Figure 1P As shown in 1p-05, each MBS can have a mapping relationship with the first ID, second ID, logical channel ID, RNTI, or bearer ID of the MBS, or each ID can be assigned to each MBS.

[0479] Based on the 1p-05 scheme, each MBS can be identified, and a specific MBS can be identified and indicated by an ID. However, the ID is very long, so indicating each MBS via a first ID, second ID, logical channel ID, RNTI, or bearer ID may not be an efficient method in terms of overhead.

[0480] In this disclosure, lists of supported MBS or configured MBS can be broadcast, agreed upon, or configured in system information, RRC messages, or MBS control messages, and integer values ​​can be assigned or mapped to each MBS configured in the list of MBS, as shown in 1p-10. According to another method, integer values ​​can be mapped or assigned in ascending (or descending) order for each ID value of the corresponding MBS included in the list of MBS. Furthermore, when indicating a specific MBS, the MBS can be indicated by integer values, thus reducing overhead. For example, when indicating multiple MBS, corresponding integer values ​​for multiple MBS can be included in a list to indicate multiple MBS.

[0481] According to another method, a list of supported MBSs or a list of configured MBSs can be broadcast, agreed upon, or configured in system information, RRC messages, or MBS control messages, and each bit of the bitmap can be assigned or mapped to each MBS configured in the list of MBSs, as shown in 1p-15. According to another method, each bit of the bitmap can be mapped or assigned in ascending (or descending) order of the ID values ​​of the corresponding MBS included in the list of MBSs. Furthermore, when indicating a specific MBS, the MBS can be indicated by each bit of the bitmap (e.g., each MBS can be indicated by a value of 1 or 0), thus reducing overhead. For example, when indicating multiple MBSs, the corresponding bit values ​​for the multiple MBSs can be configured in the bitmap to indicate the multiple MBSs.

[0482] Figure 1P The method of instructing each MBS can be based on an application or extension and can be applied to various signaling procedures according to this disclosure.

[0483] For example, when in Figure 10In 1o-20 and 1o-25, the base station configures and sends a message requesting a response to identify whether a UE receiving MBS data has received MBS or to count the number of UEs receiving MBS, so as to identify how many UEs have received MBS, and the UE receiving the request response message configures a response message and sends a response message to the base station. The following methods can be applied.

[0484] In detail, the request for a response message identifying whether a UE has received an MBS or for counting the number of UEs that have received an MBS, and the response message thereto, can be configured or generated by one of the following methods.

[0485] First method: such as Figure 1PAs shown in 1p-05, each MBS can be mapped to a first ID, second ID, logical channel ID, RNTI, or bearer ID of the MBS, or each ID can be assigned to each MBS. When the base station wants to know how many UEs have received MBS, the base station can configure the IDs corresponding to the MBS as shown in 1p-05, and can send a request message to the UE by including the list in a request message. The request message can be sent to the UE receiving the MBS, or the UE receiving the MBS can receive the request message, and the UE receiving the corresponding MBS included in the request message can respond to the request by configuring a response message that includes an indication in the response message whether the UE is interested in or receiving the MBS. According to another method, when the base station configures the request message, by applying the method in 1p-10, integer values ​​can be assigned or mapped to each MBS in the list of MBS configured using system information, RRC messages, or MBS control messages. For example, integer values ​​can be mapped or assigned in ascending (or descending) order for each ID value of the corresponding MBS included in the list of MBS. Furthermore, the mapped or assigned integer values ​​can be included in the request message or list to indicate how many UEs have received MBS. According to another method, by applying method 1p-15, when configuring the request message, the base station can assign or map each bit of the bitmap to each MBS in a list configured using system information, RRC messages, or MBS control messages. For example, each bit of the bitmap can be mapped or assigned in ascending (or descending) order for each ID value of the corresponding MBS included in the list for MBS. Furthermore, when identifying how many UEs have received MBS via the request message, the MBS can be indicated by each bit of the bitmap (e.g., each MBS can be indicated by a value of 1 or 0) to reduce overhead. Additionally, when indicating multiple MBS, corresponding bit values ​​for multiple MBS can be configured in the bitmap to indicate multiple MBS. UEs receiving the corresponding MBS included in the request message can respond to the request by configuring a response message that includes an indication of whether the UE is interested in or receiving the MBS. Because each MBS can have a mapping relationship with the first ID, second ID, logical channel ID, RNTI, or bearer ID of the MBS in the list included in the request message or in the list of MBS configured by using system information, RRC messages, or MBS control messages, when the UE configures the response message, the UE can configure the IDs corresponding to the MBS that the UE is interested in or wants to receive into a list by applying the 1p-05 method, and can send the response message to the base station by including the list in the response message.When the UE configures the response message, the UE can assign or map integer values ​​to each MBS in a list of MBS included in the request message, or in a list of MBS configured using system information, RRC messages, or MBS control messages, by applying the 1p-10 method. For example, integer values ​​can be mapped or assigned in ascending (or descending) order for each ID value of the corresponding MBS included in the list of MBS. Furthermore, when the UE indicates which MBS it is interested in or wants to receive via the response message, the UE can include the mapped or assigned integer values ​​in the response message or in the list so that the UE can indicate the MBS it is interested in or wants to receive to the base station. This reduces overhead. Additionally, when indicating multiple MBS, corresponding integer values ​​for multiple MBS can be included in the response message or in the list to indicate multiple MBS. According to another method, when the UE configures the response message by applying the 1p-15 method, the UE can assign or map each bit of the bitmap to each MBS in a list of MBS included in the request message or in a list of MBS configured using system information, RRC messages, or MBS control messages. For example, each bit of the bitmap can be mapped or assigned in ascending (or descending) order for each ID value of the corresponding MBS included in the list for the MBS. Furthermore, when indicating in a response message which MBS the UE is interested in or wants to receive, the MBS can be indicated by each bit of the bitmap (e.g., each MBS can be indicated by a value of 1 or 0), thus reducing overhead. For example, when indicating multiple MBS, the corresponding bit values ​​for the multiple MBS can be configured in the bitmap to indicate the multiple MBS.

[0486] The second method: The base station can configure a request message to request the UE to send a response message by configuring a response message for MBS that the UE is interested in or wants to receive, and can send the request message to the UE. The request message can be sent to the UE receiving the MBS, or the UE receiving the MBS can receive the request message, and the request message can include an indicator indicating whether the UE is interested in or wants to receive the MBS. The UE receiving the corresponding MBS included in the request message can respond to the request by including an indication in the response message regarding whether the UE is interested in or wants to receive the MBS. When the UE configures the response message, because each MBS in the list of MBS configured by using system information, RRC messages, or MBS control messages can have a mapping relationship with the first ID, second ID, logical channel ID, RNTI, or bearer ID of the MBS, the UE can configure a list of IDs corresponding to the MBS that the UE is interested in or wants to receive by applying the 1p-05 method, and can send the response message to the base station by including the list in the response message. According to another method, when the UE configures the response message, the UE can assign or map integer values ​​to each MBS in a list of MBS configured using system information, RRC messages, or MBS control messages by applying the 1p-10 method. For example, integer values ​​can be mapped or assigned in ascending (or descending) order for each ID value of the corresponding MBS included in the list of MBS. Furthermore, when the UE indicates an MBS it is interested in or wants to receive via the response message, the UE can include the mapped or assigned integer values ​​in the response message or in the list so that the UE can indicate the MBS it is interested in or wants to receive to the base station. This reduces overhead. Additionally, when indicating multiple MBS, corresponding integer values ​​for multiple MBS can be included in the response message or in the list to indicate multiple MBS. According to another method, by applying the 1p-15 method, when the UE configures the response message, the UE can assign or map each bit of the bitmap to each MBS in a list of MBS configured using system information, RRC messages, or MBS control messages. For example, each bit of the bitmap can be mapped or allocated in ascending (or descending) order for each ID value of the corresponding MBS included in the list for MBS. Furthermore, when the UE indicates in a response message which MBS it is interested in or wants to receive, the UE can indicate the MBS using each bit of the bitmap (e.g., by using a value of 1 or 0 to indicate each MBS), thus reducing overhead. For example, when indicating multiple MBS, the corresponding bit values ​​for multiple MBS can be configured in the bitmap to indicate multiple MBS.

[0487] According to this disclosure, Figure 1PMethods 1p-05, 1p-10, and 1p-15 for indicating MBS can be extended to apply when indicating MBS of interest or configuring MBS configuration information. For example, indicating Figure 1P Each MBS method in the model can be applied based on extensions. Figure 1J , 1K The methods provided in 1L, 1M or 1O.

[0488] The system information or configuration information configured in the RRC message according to this disclosure may include first discontinuous reception (DRX) configuration information for general data services (e.g., period, duration (on-call duration), offset, etc.). Therefore, based on the first DRX configuration information for general data services, the UE may monitor the PDCCH for a specific duration, or may not monitor the PDCCH for a specific duration, in order to save UE power.

[0489] The system information or configuration information for MBS disclosed herein (the configuration information of MBS is configured by using RRC messages or MBS control data) may include second discontinuous reception (DRX) configuration information for MBS (e.g., period, duration length (on-call duration), offset, etc.). Therefore, based on the second DRX configuration information of MBS, the UE can monitor PDCCH for a specific duration, or can choose not to monitor PDCCH for a specific duration to save UE power.

[0490] The base station can configure the UE with first DRX configuration information for general data services or second DRX configuration information for MBS. When the UE is configured with the first DRX configuration information or the second DRX configuration information, the UE can operate the first DRX and the second DRX respectively, and can send or receive data according to the operated first DRX or second DRX. For example, when the UE receives or sends general data, the UE can operate the first DRX based on the first DRX configuration information, and can or can not read the PDCCH to save power. Similarly, when the UE receives or sends MBS data, the UE can operate the second DRX based on the second DRX configuration information, and can or can not read the PDCCH to save power.

[0491] Figure 1Q This is a diagram illustrating a method for retransmitting MBS data according to an embodiment of this disclosure.

[0492] refer to Figure 1Q As mentioned above (for example, in Figure 1G , 1KIn 1L or 1M, when HARQ reordering, RLC reordering, HARQ ACK or NACK transmission, HARQ processing or HARQ retransmission is configured for MBS or MBS-supporting bearers using system information, RRC messages or MBS control messages, and when the UE does not successfully receive MBS data via transmission resources indicated by PDCCH (e.g., PDCCH scrambled by RNTI of MBS) or periodically configured transmission resources for MBS (i.e., transmission resources of MBS configured in system information or RRC messages, including time resources, frequency resources, period, offset or additional DRX configuration information of MBS (period, activation duration (on-call duration), duration (length) 1q-05 and 1q-10 for reading PDCCH, or offset)), the UE may indicate NACK via transmission resources indicated by PDCCH (e.g., PUCCH) or transmission resources configured using system information, RRC messages or MBS control messages. According to another method, when the UE successfully receives MBS data via a transmission resource indicated by the PDCCH (e.g., a PDCCH scrambled by the RNTI of the MBS) or a transmission resource periodically configured for the MBS, the UE can indicate an ACK.

[0493] According to another method, when a UE fails to successfully receive MBS data via transmission resources indicated by the PDCCH (e.g., a PDCCH scrambled by the RNTI of MBS) or periodically configured transmission resources, the UE may include an indicator or UE ID in the MAC control information, RLC control information, or PDCP control information, and may indicate to the base station which UE has failed to receive MBS data. According to another method, each UE may indicate NACK by using transmission resources pre-defined for each UE, thereby indicating to the base station which UE has failed to receive MBS data.

[0494] The base station can configure transmission resources that a UE can use to indicate successful reception of MBS data (ACK) or unsuccessful reception of MBS data (NACK) as common transmission resources for UEs receiving MBS. Furthermore, using these common transmission resources, the base station can retransmit MBS data when at least one UE indicates NACK or a predetermined UE indicates NACK. According to another method, when a UE fails to receive MBS data, and when a UE that has failed to receive MBS data is indicated to the base station, the base station can retransmit MBS data only to the corresponding UE.

[0495] The base station may apply one or a combination of the following methods to perform MBS data retransmission.

[0496] 1. First retransmission method (1q-01): The base station can transmit MBS data using transmission resources configured with system information, RRC messages, or MBS control data (time resources, frequency resources, subcarrier spacing, DRX configuration information, etc.) or through a configured period. Alternatively, it can transmit MBS data using transmission resources specified by a PDCCH scrambled with an RNTI indicating MBS data (1q-05, 1q-10, 1q-30, and 1q-35). The UE can receive MBS data using transmission resources configured with system information, RRC messages, or MBS control data (time resources, frequency resources, subcarrier spacing, DRX configuration information, etc.) or through a configured period. Alternatively, it can receive MBS data using transmission resources specified by a PDCCH scrambled with an RNTI indicating MBS data (1q-05, 1q-10, 1q-30, and 1q-35). When a UE fails to receive MBS data, it can indicate NACK using transmission resources indicated by the PDCCH (e.g., PUCCH) or by using transmission resources configured through system information, RRC messages, or MBS control messages. When a base station receives an indication from a specific UE that it has failed to receive MBS data, it can perform a retransmission. The base station can retransmit MBS data using transmission resources configured with system information, RRC information, or MBS control data (time resources, frequency resources, subcarrier spacing, DRX configuration information, etc.) or by a configured period. Alternatively, it can retransmit MBS data using transmission resources indicated by the PDCCH scrambled with the RNTI indicating MBS data. When the base station performs a retransmission, it can include indicators indicating retransmission (1q-35 and 1q-40) in the PDCCH, MBS control data, or RRC message indicating transmission resources. For example, retransmission can be indicated based on whether the New Data Indicator (NDI) has changed (indicating new transmission when NDI changes, or indicating retransmission when NDI does not change). According to another method, the base station can configure additional transmission resources for retransmission and can directly indicate retransmission via these transmission resources. According to yet another method, the base station can define an RNTI for retransmitting MBS data and can indicate retransmission using a PDCCH scrambled with the RNTI.When a UE receives MBS data using transmission resources configured by system information, RRC messages, or MBS control data (time resources, frequency resources, subcarrier spacing, DRX configuration information, etc.) or by a configured period, or when a UE is instructed to transmit MBS data via a PDCCH scrambled by an RNTI indicating MBS data, and when an indicator indicating retransmission is included in the indicated transmission resources or the indicated transmission resources indicate retransmission, the UE may receive the retransmitted MBS data if it has not successfully received the previous MBS data, or ignore the retransmitted MBS data if it has successfully received the previous MBS data, or not receive the retransmitted MBS data, or discard the retransmitted MBS data even after receiving the data (e.g., the retransmitted MBS data may be discarded via a duplicate detection process in the MAC entity, RLC entity, or PDCP entity).

[0497] 2. Second retransmission method (1q-02): The base station can transmit MBS data using transmission resources configured with system information, RRC messages, or MBS control data (time resources, frequency resources, subcarrier spacing, DRX configuration information, etc.) or through a configured period. Alternatively, it can transmit MBS data using transmission resources indicated by the PDCCH scrambled with the RNTI indicating MBS data (1q-05, 1q-10, 1q-30, and 1q-35). The UE can receive MBS data using transmission resources configured with system information, RRC messages, or MBS control data (time resources, frequency resources, subcarrier spacing, DRX configuration information, etc.) or through a configured period. Alternatively, it can receive MBS data using transmission resources configured with the RNTI indicating MBS data (1q-05, 1q-10, 1q-30, and 1q-35). When a UE fails to receive MBS data, the UE can indicate NACK using transmission resources indicated by the PDCCH (e.g., PUCCH) or by using transmission resources configured through system information, RRC messages, or MBS control messages. When the base station receives an indication from a specific UE that the UE has failed to receive MBS data, the base station can perform a retransmission. The base station can retransmit MBS data using transmission resources configured with system information, RRC information, or MBS control data (time resources, frequency resources, subcarrier spacing, DRX configuration information, etc.) or by using a configured period, or it can retransmit MBS data using transmission resources indicated by the PDCCH scrambled with the RNTI indicating MBS data. According to another method, the base station can transmit MBS data by using system information, RRC messages, or MBS control data (time resources, frequency resources, subcarrier spacing, DRX configuration information, etc.) configured transmission resources or by a configured period. Alternatively, when the base station can indicate the transmission resources of MBS by a PDCCH scrambled with an RNTI indicating MBS data, the base station can simultaneously indicate new MBS data and retransmitted MBS data by multiple PDCCHs (e.g., PDCCHs scrambled with an RNTI for new transmission or including an indicator indicating new transmission and PDCCHs scrambled with an RNTI for retransmission or including an indicator indicating retransmission), multiple RNTIs (e.g., indicators scrambled via an RNTI for new transmission or an indicator indicating new transmission and indicators scrambled via an RNTI for retransmission or an indicator indicating retransmission), or multiple segments of MBS control data (indicating new transmission or retransmission). Furthermore, the base station can indicate that the transmission resources through which new data is transmitted or the transmission resources through which retransmitted data are retransmitted are different from each other (1q-35, 1q-45, 1q-40, and 1q-50).When a base station performs a retransmission, it can include indicators (1q-35 and 1q-40) in the PDCCH, MBS control data, or RRC message indicating transmission resources. For example, retransmission can be indicated based on whether the New Data Indicator (NDI) has changed (indicating new transmission when the NDI changes, or indicating retransmission when the NDI does not change). According to another method, the base station can configure additional transmission resources for retransmission and can indicate retransmission directly via these resources. According to yet another method, the base station can define an RNTI for retransmitting MBS data and can indicate retransmission using a PDCCH scrambled with the RNTI. When a UE receives multiple MBS data segments via transmission resources configured using system information, RRC messages, or MBS control data (time resources, frequency resources, subcarrier spacing, DRX configuration information, etc.) or via a configured period, or when a UE is instructed to transmit MBS data via a PDCCH scrambled by an RNTI indicating multiple MBS data segments, and when an indicator indicating retransmission is included in the indicated transmission resource, an indicator indicating new transmission is included in the indicated transmission resource, the indicated transmission resource indicates retransmission, or the indicated transmission resource indicates new transmission, the UE may receive retransmitted MBS data if it has not successfully received previous MBS data, or it may also receive new data when a new transmission is indicated. Alternatively, when the UE successfully receives the previous MBS data, the UE may ignore the retransmitted data, may not receive the retransmitted data, or may discard the retransmitted data even after receiving the data (e.g., the retransmitted MBS data may be discarded via a duplicate detection process in the MAC entity, RLC entity, or PDCP entity), or may receive new data (1q-40 and 1q-50) when a new transmission is indicated.

[0498] 3. Third retransmission method (1q-03): The base station can transmit MBS data using transmission resources configured with system information, RRC messages, or MBS control data (time resources, frequency resources, subcarrier spacing, DRX configuration information, etc.) or through a configured period. Alternatively, it can transmit MBS data using transmission resources specified by a PDCCH scrambled with an RNTI indicating MBS data (1q-05, 1q-10, 1q-30, and 1q-35). The UE can receive MBS data using transmission resources configured with system information, RRC messages, or MBS control data (time resources, frequency resources, subcarrier spacing, DRX configuration information, etc.) or through a configured period. Alternatively, it can receive MBS data using transmission resources specified by a PDCCH scrambled with an RNTI indicating MBS data (1q-05, 1q-10, 1q-30, and 1q-35). When a UE fails to receive MBS data, the UE can indicate NACK through transmission resources indicated by the PDCCH (e.g., PUCCH) or through transmission resources configured using system information, RRC messages, or MBS control messages. When the base station receives an indication from a specific UE that the UE has failed to receive MBS data, the base station can perform a retransmission. Depending on the new data transmission procedure, MBS data can be transmitted through transmission resources configured using system information, RRC information, or MBS control data (time resources, frequency resources, subcarrier spacing, DRX configuration information, etc.) or through a configured period, or through transmission resources indicated by the PDCCH scrambled with the RNTI indicating MBS data, and data can be transmitted through these transmission resources (1q-05, 1q-10, 1q-35, and 1q-40). According to the retransmission process of retransmitted data, the transmission resources for retransmission can be configured using system information, RRC messages, or MBS control data, and MBS data can be transmitted using additionally configured transmission resources (time resources, frequency resources, subcarrier spacing, DRX configuration information, offset, period, transmission resources configured to indicate new data transmission resources, offset with period, or period (1q-15 and 1q-45)) or by configured period, or when the transmission resources of MBS data are indicated by using a PDCCH scrambled by an RNTI indicating MBS, the retransmitted MBS data can be indicated by using a retransmitted PDCCH (e.g., scrambled by an RNTI for retransmission or including an indicator indicating retransmission or a PDCCH scrambled by an RNTI for MBS), an RNTI (e.g., indicating scrambled by an RNTI for retransmission or an indicator indicating retransmission) or segments of MBS control data (indicating retransmission), and the transmission resources of the data retransmitted through it can be indicated (1q-20, 1q-25, and 1q-50).When a base station performs a retransmission, it can include indicators (1q-35 and 1q-40) in the PDCCH, MBS control data, or RRC message indicating transmission resources. For example, retransmission can be indicated based on whether the New Data Indicator (NDI) has changed (indicating new transmission when the NDI changes, or indicating retransmission when the NDI does not change). According to another method, the base station can configure additional transmission resources for retransmission and can indicate retransmission directly via these resources. According to yet another method, the base station can define an RNTI for retransmitting MBS data and can indicate retransmission using a PDCCH scrambled with the RNTI. When a UE receives MBS data using transmission resources configured by system information, RRC messages, or MBS control data (time resources, frequency resources, subcarrier spacing, DRX configuration information, etc.) or by a configured period, or when the UE is instructed to transmit MBS data via a PDCCH scrambled by an RNTI indicating MBS data, if the UE has not successfully received previous MBS data, the UE can indicate the retransmission of MBS data by configuring additional transmission resources (time resources, frequency resources, subcarrier spacing, DRX configuration information, offset, period, transmission resources configured to indicate new data transmission resources, periodic offset, or period (1q-15 and 1q-45)) or by a configured period using system information, RRC messages, or MBS control data, and can receive MBS data. Alternatively, the UE can indicate the transmission of new MBS data by configuring transmission resources for new transmissions, and can receive new MBS data. Alternatively, when the UE successfully receives previous MBS data, the UE may, by configuring additional transmission resources for retransmission, ignore, not receive, or discard even after receiving (e.g., discarded via a duplicate detection process in the MAC entity, RLC entity, or PDCP entity) indication or data, or may indicate a new transmission of new MBS data by configuring transmission resources for new transmission, and may receive new MBS data (1q-20, 1q-25, 1q-35, and 1q-40).

[0499] 4. Fourth Retransmission Method: To send new data, or using the first, second, or third retransmission method, multicast bearer or multicast MBS support, or unicast bearer or unicast MBS support, can be applied. According to another method, to send new data, or using the first, second, or third retransmission method, multicast bearer or multicast MBS support can be applied. According to yet another method, to send new data, multicast bearer or multicast MBS support can be applied, and to retransmit using the first, second, or third retransmission method, unicast bearer or unicast MBS support can be applied. For example, the retransmission process can be applied and performed only for UEs that have not successfully received MBS data.

[0500] Next, according to this disclosure, when a UE...

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: The configuration information for the Multicast Broadcast Service (MBS) is received via the Radio Resource Control (RRC) release message. Upon receiving the RRC release message, the system enters the RRC inactive state. as well as Based on the configuration information used for MBS, the MBS is received while the RRC is inactive. Wherein, the MBS is received via a multicast bearer used for the MBS, and Among them, at least one of the Packet Data Convergence Protocol (PDCP) entity, Radio Link Control (RLC) entity, Media Access Control (MAC) entity, Physical Layer entity, and Service Data Adaptation Protocol (SDAP) entity is configured for the multicast bearer of the MBS.

2. The method according to claim 1, in, The SDAP entity provides a mapping between Quality of Service (QoS) streams and multicast bearers for MBS.

3. The method according to claim 1, in, The PDCP entity provides header compression and decompression functions based on robust header compression (ROHC) or Ethernet header compression (EHC) and PDCP reordering.

4. The method according to claim 1, in, The RLC entity includes an RLC unacknowledged mode UM entity for multicast transmission.

5. The method according to claim 4, in, The MBS is scheduled using the Radio Network Temporary Identifier (RNTI) used for the multicast transmission.

6. A method performed by a base station in a wireless communication system, the method comprising: The configuration information for Multicast Broadcast Service (MBS) is sent to the User Equipment (UE) via a Radio Resource Control (RRC) release message. The RRC release message causes the UE to enter an RRC inactive state; and Based on the configuration information used for MBS, MBS is sent when RRC is inactive. Wherein, the MBS is transmitted via a multicast bearer used for the MBS, and Among them, at least one of the Packet Data Convergence Protocol (PDCP) entity, Radio Link Control (RLC) entity, Media Access Control (MAC) entity, Physical Layer entity, and Service Data Adaptation Protocol (SDAP) entity is configured for the multicast bearer of the MBS.

7. The method according to claim 6, in, The SDAP entity provides a mapping between Quality of Service (QoS) streams and multicast bearers for MBS.

8. The method according to claim 6, in, The PDCP entity provides header compression and decompression functions based on robust header compression (ROHC) or Ethernet header compression (EHC) and PDCP reordering.

9. The method according to claim 6, in, The RLC entity includes an RLC unacknowledged mode UM entity for multicast transmission.

10. The method according to claim 9, in, The MBS is scheduled using the Radio Network Temporary Identifier (RNTI) used for the multicast transmission.

11. A user equipment (UE) in a wireless communication system, the UE comprising: transceiver; and At least one processor is operatively connected to the transceiver and configured to: The configuration information for the Multicast Broadcast Service (MBS) is received via the Radio Resource Control (RRC) release message. Based on receiving the RRC release message, it enters the RRC inactive state, and Based on the configuration information used for MBS, the MBS is received while the RRC is inactive. Wherein, the MBS is received via a multicast bearer used for the MBS, and Among them, at least one of the Packet Data Convergence Protocol (PDCP) entity, Radio Link Control (RLC) entity, Media Access Control (MAC) entity, Physical Layer entity, and Service Data Adaptation Protocol (SDAP) entity is configured for the multicast bearer of the MBS.

12. The UE according to claim 11, in, The SDAP entity provides a mapping between Quality of Service (QoS) streams and multicast bearers for MBS.

13. The UE according to claim 11, in, The PDCP entity provides header compression and decompression functions based on robust header compression (ROHC) or Ethernet header compression (EHC) and PDCP reordering.

14. The UE according to claim 11, in, The RLC entity includes an RLC unacknowledged mode UM entity for multicast transmission.

15. The UE according to claim 14, in, The MBS is scheduled using the Radio Network Temporary Identifier (RNTI) used for the multicast transmission.

16. A base station in a wireless communication system, the base station comprising: transceiver; and At least one processor is operatively connected to the transceiver and configured to: The configuration information for Multicast Broadcast Service (MBS) is sent to the User Equipment (UE) via a Radio Resource Control (RRC) release message. The RRC release message causes the UE to enter an RRC inactive state, and Based on the configuration information used for MBS, MBS is sent when RRC is inactive. Wherein, the MBS is transmitted via a multicast bearer used for the MBS, and Among them, at least one of the Packet Data Convergence Protocol (PDCP) entity, Radio Link Control (RLC) entity, Media Access Control (MAC) entity, Physical Layer entity, and Service Data Adaptation Protocol (SDAP) entity is configured for the multicast bearer of the MBS.

17. The base station according to claim 16, in, The SDAP entity provides a mapping between Quality of Service (QoS) streams and multicast bearers for MBS.

18. The base station according to claim 16, in, The PDCP entity provides header compression and decompression functions based on robust header compression (ROHC) or Ethernet header compression (EHC) and PDCP reordering.

19. The base station according to claim 16, in, The RLC entity includes an RLC unacknowledged mode UM entity for multicast transmission.

20. The base station according to claim 19, in, The MBS is scheduled using the Radio Network Temporary Identifier (RNTI) used for the multicast transmission.

Images