KR20220008210A - Method and Apparatus for SPS Operation for MBS Reception - Google Patents

Abstract

The present disclosure provides a method of operating a semi-persistent scheduling (SPS) operation for multicast and broadcast service (MBS) reception of a terminal, comprising: receiving a message instructing MBS SPS configuration and activation from a base station; storing resource allocation information and HARQ information for the MBS SPS in a MAC layer; performing initialization or re-initialization of resources configured for the MBS SPS in the MAC layer; and transmitting a confirmation message for the activation setting of the MBS SPS to the base station. According to the disclosed embodiment, resources can be efficiently used in a wireless communication system.

Description

Operation method and apparatus of SPS for MBS reception {Method and Apparatus for SPS Operation for MBS Reception}

The present disclosure relates to an SPS operation method and apparatus for MBS reception in a wireless communication system.

Efforts are being made to develop an improved 5G communication system or pre-5G communication system in order to meet the increasing demand for wireless data traffic after commercialization of the 4G communication system. For this reason, the 5G communication system or the pre-5G communication system is called a system after the 4G network (Beyond 4G Network) communication system or the LTE system after (Post LTE). In order to achieve a high data rate, the 5G communication system is being considered for implementation in a very high frequency (mmWave) band (such as, for example, a 60 gigabyte (80 GHz) band). In order to alleviate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, in the 5G communication system, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used. ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed. In addition, for network improvement of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud radio access network: cloud RAN), an ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and reception interference cancellation Technology development is underway. In addition, in the 5G system, the advanced coding modulation (ACM) methods FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), and advanced access technologies FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and sparse code multiple access (SCMA) are being developed.

On the other hand, the Internet is evolving from a human-centered connection network where humans create and consume information to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. Internet of Everything (IoE) technology, which combines big data processing technology through connection with cloud servers, etc. with IoT technology, is also emerging. In order to implement IoT, technology elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. , M2M), and MTC (Machine Type Communication) are being studied. In the IoT environment, an intelligent IT (Internet Technology) service that collects and analyzes data generated from connected objects and creates new values in human life can be provided. IoT is the field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliance, advanced medical service, etc. can be applied to

Accordingly, various attempts are being made to apply the 5G communication system to the IoT network. For example, technologies such as sensor network, machine to machine (M2M), and MTC (Machine Type Communication) are being implemented by 5G communication technologies such as beamforming, MIMO, and array antenna. . The application of cloud radio access network (cloud RAN) as the big data processing technology described above can be said to be an example of convergence of 3eG technology and IoT technology.

In order to provide various services according to the above-mentioned and the development of wireless communication systems, in particular, in order to efficiently use PDCCH (Physical Downlink Control Channel) resources, SPS (Semi-Persistent Scheduling) is implemented in periodic broadcast services. A method of use is required.

Disclosed embodiments are intended to provide an apparatus and method for efficiently using resources in a wireless communication system.

According to an embodiment of the present disclosure, there is provided a method of operating an SPS for receiving a Multicast and Broadcast Service (MBS) of a terminal, the method comprising: receiving a message instructing MBS Semi Persistent Scheduling (SPS) setup and activation from a base station; storing resource allocation information and HARQ information for the MBS SPS in a MAC layer; performing initialization or re-initialization of resources configured for the MBS SPS in the MAC layer; and transmitting a confirmation message for the activation setting of the MBS SPS to the base station, it is possible to provide a method.

According to the disclosed embodiment, it is possible to efficiently use resources in a wireless communication system.

1 is a diagram illustrating a method of operating Multicast and Broadcast Service (MBS) communication according to an embodiment of the present disclosure.
2 is a diagram illustrating a setup procedure for performing MBS communication according to an embodiment of the present disclosure.
3 is a diagram illustrating an operation of unicast semi-persistent scheduling (SPS) according to an embodiment of the present disclosure.
4 is a diagram illustrating an operation of an MBS SPS according to an embodiment of the present disclosure.
5 is a diagram illustrating an operation of an MBS SPS according to an embodiment of the present disclosure.
6 is a diagram illustrating an operation of an MBS SPS according to an embodiment of the present disclosure.
7 is a diagram illustrating a method of transmitting an MBS SPS activation and deactivation confirmation message according to an embodiment of the present disclosure.
8 is a diagram illustrating operations of a base station and a terminal when MBS SPS is activated according to an embodiment of the present disclosure.
9 is a diagram illustrating operations of a base station and a terminal when MBS SPS is deactivated according to an embodiment of the present disclosure.
10 is a diagram illustrating an operation according to MBS SPS deactivation of a terminal in an idle mode or an inactive mode according to an embodiment of the present disclosure.
11 is a diagram illustrating an operation of a terminal with respect to a retransmission resource of an MBS SPS according to an embodiment of the present disclosure.
12 is a diagram illustrating a structure in which MBS SPS is set according to an embodiment of the present disclosure.
13 is a diagram illustrating a structure in which an MBS SPS is configured according to an embodiment of the present disclosure.
14 is a diagram illustrating a structure of a base station according to an embodiment of the present disclosure.
15 is a diagram illustrating a structure of a terminal according to an embodiment of the present disclosure.
16 is a diagram illustrating operations of a base station and a terminal when MBS SPS is activated according to an embodiment of the present disclosure.
17 is a diagram illustrating operations of a base station and a terminal when MBS SPS is deactivated according to an embodiment of the present disclosure.
18 is a diagram illustrating a format of an activation or deactivation confirmation message of an MBS SPS according to an embodiment of the present disclosure.
19 is a diagram illustrating a format of an MBS SPS activation or deactivation confirmation message according to an embodiment of the present disclosure.
20 is a diagram illustrating a format of an activation or deactivation confirmation message of an MBS SPS according to an embodiment of the present disclosure.
21 is a diagram illustrating a format of an activation or deactivation confirmation message of an MBS SPS according to an embodiment of the present disclosure.

In the following description of the present disclosure, if it is determined that a detailed description of a related well-known function or configuration may unnecessarily obscure the subject matter of the present disclosure, the detailed description thereof will be omitted. In addition, the terms to be described later are terms defined in consideration of functions in the present disclosure, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout the present disclosure. A term for identifying an access node used in the following description, a term referring to network entities, a term referring to messages, a term referring to an interface between network objects, a term referring to various identification information and the like are exemplified for convenience of description. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

Hereinafter, the base station, as a subject performing resource allocation of the terminal, may be at least one of gNode B, eNode B, Node B, a base station (BS), a radio access unit, a base station controller, or a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. Also, the term terminal may refer to mobile phones, NB-IoT devices, sensors, as well as other wireless communication devices. Of course, the base station and the terminal are not limited to the above example.

For convenience of description, the present invention uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP) standard and/or 3rd Generation Partnership Project New Radio (NR). However, the present disclosure is not limited by the above terms and names.

In addition, the embodiment of the present disclosure will be described below using LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobile communication) system as an example, but the present disclosure also applies to other communication systems having a similar technical background or channel type An embodiment of can be applied. In addition, the embodiments of the present disclosure may be applied to other communication systems through some modifications within a range that does not significantly depart from the scope of the present disclosure as judged by a person having skilled technical knowledge. Hereinafter, an embodiment of the present disclosure will be described with reference to the accompanying drawings.

1 is a diagram illustrating an operation method of MBS communication according to an embodiment of the present disclosure. Multicast and Broadcast Service (MBS) communication refers to a method in which one transmitting device communicates with several receiving devices in a wireless communication system. Here, the transmitting apparatus may be a base station, and each receiving apparatus may be a terminal. However, the present invention is not limited thereto, and the transmitting device may be a terminal.

1 shows an example of performing MBS communication when the base station 110 is a transmitting device and the terminals 120, 130, 140, and 150 are receiving devices. MBS communication may be performed in a broadcast method for an unspecified number of people, or may be performed in a multicast method for a plurality of specific reception devices. If communication is performed in a multicast method, the base station may set a specific terminal to receive a corresponding multicast packet. To this end, a set of terminals to perform a specific multicast communication may be set, and in the embodiment of FIG. 1 , this is referred to as a multicast group 160 . Conversely, the method of performing one-to-one communication between the base station and the terminal is called unicast.

Terminals in the multicast group may receive data allocated for the corresponding G-RNTI by being allocated a Group-Radio Network Temporary Identity (G-RNTI), which is the same resource identifier for each multicast group. The G-RNTI is an RNTI shared by terminals in a multicast group, and the terminals receiving the G-RNTI may receive radio resources for the MBS service from the base station. In the embodiment of FIG. 1 , terminal 1 120 , terminal 2 130 , and terminal 3 140 are configured as one multicast group, and receive G-RNTI assignment to multicast data from the base station 110 . It is assumed to receive in this way. Since the terminal 4 150 is not included in the multicast group, it is not assigned a G-RNTI, and accordingly, the terminal 1 120 , the terminal 2 130 , and the terminal 3 140 transmit data received from the base station to the terminal 4 (150) cannot be received.

One or more multicast groups may be established within the coverage of the base station 110 , and each multicast group may be divided into a G-RNTI. One terminal may be allocated one or more G-RNTIs from the base station 110 . The terminal transmits multicast data using the G-RNTI value assigned in the connected mode not only in the connected mode (RRC (Radio Resource Control) CONNECTED MODE) but also in the idle mode (RRC IDLE MODE) or inactive mode (RRC INACTIVE MODE). can receive The G-RNTI may be included in at least one of an RRC reconfiguration message, an RRC setup message, and an RRC reestablishment message in the connected mode of the terminal. However, the present invention is not limited thereto, and the G-RNTI may be transmitted from the base station by being included in a system information block (SIB) as a G-RNTI value that the terminal can receive. The terminal having the G-RNTI value set may apply the G-RNTI value thereafter.

2 is a diagram illustrating a setting procedure for performing MBS communication according to an embodiment of the present disclosure. In the case of the terminal 220 in which the base station 210 and the RRC (Radio Resource Control) setting are not in a connected state, in order to perform MBS communication, a base station to request the MBS service may be selected. In step 230, the terminal 220 may receive a synchronization signal transmitted from the base station and perform a cell selection or cell reselection procedure for selecting a base station having a strong received signal. In the embodiment of FIG. 2 , it is assumed that the terminal transitions to the idle mode or the inactive mode after the initial connection state performs a cell reselection operation for selecting a cell.

In step 235, the terminal 220 may receive a system information block (System Information Block, SIB) from the selected cell. At this time, if the terminal 220 wants to receive the MBS service, it may receive a system information block including MBS information among the system information blocks. The system information block including MBS information may include a list of MBS services that are already provided or may be provided by each serving cell.

A list of MBS services that are already provided or can be provided in each of these serving cells may be referred to as AvailableMBSList. AvailableMBSList may include MBS session information. The MBS session information may include a Temporary Mobile Group Identity (tmgi) value capable of identifying a group and an MBS session ID (sessionID). The tmgi value includes a Public Land Mobile Network (PLMN) ID (plmn-id) that can identify whether a service is provided by a telecommunication service provider and a service ID (serviceID) that can identify the service provided by the carrier. may include According to an embodiment of the present disclosure, AvailableMBSList may have a structure as in the following example.

- AvailableMBSList = MBSSessionInfoList

- Sequence of MBSSessionInfoList = (tmgi, sessionID)

- tmgi =(plmn-id, serviceID)

When all terminals request RRC configuration in order to receive all MBS services, the base station may instantaneously access many terminals, which may overload the base station. Therefore, an access control method for the MBS service may be required. For this, an access category value and uac-BarringForAccessIdentity for access control may be set for each tmgi. The base station may control the frequency at which the terminal requests access to the base station for each tmgi by using the access category and uac-BarringForAccessIdentity set for each tmgi. In the embodiment of FIG. 2 , it is assumed that the terminal 220 receives a system information block including MBS information, but various embodiments of the present disclosure are not limited to the embodiment of FIG. 2 , and MBS information transmits downlink information. (DL Information Transfer) can be transmitted by message.

The terminal 220 that has received the system information block including the MBS information in step 235 may identify the MBS service of interest from the list of MBS services that have already been provided or may be provided in each serving cell in step 240. have. The terminal 220 may determine which MBS service the terminal 220 is interested in according to whether it is an MBS service required by the application of the terminal 220 or other conditions. The criterion for the terminal 220 to identify the MBS service may be a tmgi unit. That is, the terminal 220 may check whether the tmgi of the MBS service that the terminal 220 wants to receive (or the terminal 220 is interested in) is included in the system information block including the MBS information. Specifically, the terminal 220 may check whether the tmgi of the MBS service that the terminal 220 wants to receive is included in the AvailableMBSList of the system information block including the MBS information. If the tmgi of the MBS service that the terminal 220 wants to receive is included in the system information block including the MBS information, the terminal 220 performs the step of establishing an RRC connection to receive the corresponding MBS service. can

In step 245, the terminal 220 may perform an access control operation in order to determine whether to start RRC connection establishment. The terminal 220 may perform access control based on the PLMN ID (plmn-ID) included in the tmgi of the MBS service to be received, using UAC-Barring information for the corresponding PLMN ID. The terminal 220 may determine whether access is permitted for the uac-BarringForAccessIdentity and the access category of the MBS service that the terminal 220 intends to receive the service from. If access to this MBS service is permitted, the terminal 220 may start a procedure for requesting an RRC connection.

If the terminal 220 is allowed access to receive the MBS service in step 250 , the terminal 220 may transmit an RRC Setup Request message to the base station 210 . However, the present disclosure is not limited to the UE 220 transmitting the RRC establishment request message, and the RRC Reestablishment Request message may also be used for the same purpose as the RRC establishment request message. Since the RRC establishment request message or RRC re-establishment request message is a general message that can be used for the terminal 220 to transition to the RRC CONNECTED MODE, for what purpose the terminal 220 intends to transition to the connected mode? It can include a Cause value for . If the terminal 220 wants to receive the MBS service, it may transmit an RRC establishment request or RRC re-establishment request message including a Cause value indicating that MBS configuration is desired to the base station 210 . However, if the RRC establishment request or RRC re-establishment request is not for the terminal 220 to receive the MBS service, the terminal 220 transmits the RRC establishment request or RRC re-establishment request message including the Cause value transmitted from the upper layer. can For example, the Cause value transmitted from the upper layer may include information related to the NAS (Non-Access Stratum) layer. In step 260 , the base station 210 may transmit an RRC Setup message to the terminal 220 in order to transition the terminal 220 to the connected mode. However, the present disclosure is not limited to the base station 210 transmitting the RRC establishment message, and the RRC reestablishment message may also be used for the same purpose as the RRC establishment message. When the terminal 220 receives the RRC establishment message or the RRC re-establishment message, SRB1 may be configured by the configuration information of Signaling Radio Bearer 1 (SRB1) included in the received message. SRB1 may be a radio bearer for exchanging RRC (Radio Resource Control) messages between the base station 210 and the terminal 220 .

In step 265, the terminal 220 applies the configuration information included in the RRC establishment message or the RRC re-establishment message, and transmits an RRC establishment complete message or RRC re-establishment complete message to the base station 210, from the base station 210 It can inform that the received setting has been applied successfully. In addition, the RRC establishment complete message or RRC re-establishment complete message transmitted in step 265 may include a list of MBS services that the terminal 220 wants to receive. The MBS service list included in the RRC establishment complete message or the RRC reestablishment complete message may be a list including a tmgi value corresponding to the MBS service that the terminal 220 wants to receive. At this time, the tmgi included in the MBS service list is the MBS service that is already provided or can be provided in each serving cell, included in the system information block or downlink information transfer message transmitted by the base station 210 in step 235. It can be any or all of the tmgi listed.

In step 270 , the base station 210 may transmit an RRC reconfiguration message to the terminal 220 . In step 265, since SRB1 is set and the list of MBS services that the terminal 220 wants to receive is delivered to the base station 210, the base station 210 determines that the terminal 220 is based on the set SRB1 and the list of MBS services. It can be set to receive MBS service. The MBS service for which reception of the terminal 220 is set by the base station 210 may be established using an RRC reconfiguration message transmitted by the base station 210 to the terminal 220 . The RRC reset message includes a Signaling Radio Bearer 2 (SRB2) used for transmission and reception of a NAS (Non-Access Stratum) message, a Data Radio Bearer (DRB) used for transmitting and receiving data, and a Point To Multipoint (PTM) used for multicast transmission. ) DRB configuration information, etc. may be included. The PTM DRB may be configured without distinction from the normal DRB, or may be configured by the received G-RNTI. In addition, based on the RRC reconfiguration message, an RLC (Radio Link Control) bearer to which an established radio bearer will be transmitted may be configured, and a radio bearer to which this RLC bearer will be connected may be configured. In the RRC reconfiguration message, a G-RNTI through which terminals belonging to a multicast group can receive multicast data may be configured.

The G-RNTI is an RNTI configured for reception of a transport block (TB) and may be used to indicate scheduling information for a physical downlink shared channel (PDSCH). This G-RNTI may be configured in units of MAC layer devices, but may be configured in units of BandWidth Part (BWP). If the G-RNTI is configured in units of BWP, the configured G-RNTI may be used only when receiving the PDSCH resource of the BWP. That is, the corresponding G-RNTI may not be used in other BWPs. To this end, the G-RNTI may be included in the downlink BWP configuration (BWP-Downlink configuration) field of the RRC message (eg, at least one of an RRC reconfiguration message, an RRC establishment message, and an RRC reestablishment message). In addition, a BWP ID to be used when the G-RNTI is set may be set. In another embodiment, the G-RNTI may be configured in units of cells. If the G-RNTI is configured on a cell-by-cell basis, the configured G-RNTI may be used only when receiving the PDSCH resource of the cell. That is, the corresponding G-RNTI may not be used in another cell. For this, the G-RNTI may be included in the cell configuration field of the RRC message. In addition, a cell ID to be used when the G-RNTI is configured may be configured.

In order to receive the MBS service, the BWP and the search space may be separately set. Information on the BWP and search space for receiving a specific MBS service may be configured from the base station 210 to the terminal 220, and the MBS BWP and the MBS search space may be included in this configuration information. The MBS BWP may mean a BWP to which the assigned G-RNTI is applied. According to an embodiment, the BWP including the G-RNTI in the BWP-Downlink configuration field may be the MBS BWP. The MBS search space may be a search space in which a Downlink Control Information (DCI) format for MBS reception is set in the search space configuration information, or a search space including an indicator indicating that it is a search space for MBS reception in the search space configuration information. For example, the search space setting information may include a 1-bit indicator indicating whether the corresponding search space is an MBS search space. If the indicator of the search space configuration information indicates that it is an MBS search space, the corresponding search space may be an MBS search space and may be used as a search space for monitoring the G-RNTI for MBS reception.

When the terminal applies the contents included in the RRC reconfiguration message transmitted from the base station 210 to the terminal 220 in step 270, in step 275, the terminal 220 sends an RRC reconfiguration complete message to the base station 210 can be transmitted to inform that the information of the RRC reconfiguration message has been applied. Based on the RRC reconfiguration complete message, in step 280 , the terminal 220 may receive a broadcast or multicast packet by performing MBS communication. The terminal 220 may receive the MBS service from the base station.

3 is a diagram illustrating a unicast SPS operation according to an embodiment of the present disclosure.

In unicast communication in which the base station performs one-to-one communication with each terminal, there are two methods for the base station to allocate a downlink radio resource (downlink grant) to the terminal: a dynamic grant and a semi-persistent scheduling (SPS) method. can exist. The dynamic grant is a method in which the base station changes the location and configuration of a resource for every radio resource and allocates it. The resource can be allocated in a Physical Downlink Control Channel (PDCCH) by C-RNTI or MCS-C-RNTI. Once a resource is allocated by this dynamic grant method, only the allocated resource is a valid one-shot resource. On the other hand, the resource allocated by the SPS method means a resource allocated semi-persistently once it is set.

The dynamic grant is inefficient because PDCCH resources are used to allocate resources using PDCCH resources, and when the same resource needs to be allocated periodically, PDCCH resources are repeatedly used. When it is necessary to periodically allocate resources of the same configuration, it is efficient to use the resources of the same configuration repeatedly without using PDCCH resources after setting and activation once, as it can reduce the consumption of PDCCH resources. have.

In step 300, the base station may configure the SPS resource by an RRC setup message or an RRC reconfiguration message transmitted to the terminal. The SPS configuration information may include essential information such as the period 320 of the SPS resource.

However, after the SPS is set, there is no need to activate the SPS resource. This is because it may be more efficient for the base station to use the SPS resource only when there is downlink data to be actually transmitted. Therefore, when the SPS resource is configured, the SPS resource may not be used immediately. In step 310, the base station and the terminal cannot use the SPS resource because the SPS resource is not activated. Although the location of the SPS resource that is not activated in step 310 is described as virtual in FIG. 3 , the specific location of the SPS resource can be applied by the SPS activation message, so unused SPS information (eg, of the SPS resource location information) is not possessed by the base station and the terminal. Thereafter, when the terminal receives the SPS activation 330 message transmitted from the base station to the terminal in step 330, the downlink radio resource is used using the actual SPS resource, and the terminal may receive downlink data.

In step 330, the SPS activation message may be transmitted from the base station to the terminal in the form of Downlink Control Information (DCI) of the PDCCH using a Configured Scheduling - Radio Network Temporary Identity (CS-RNTI). In this case, specific information of DCI may indicate activation of SPS. Since the DCI informs the MCS (Modulation & Coding Scheme) information to be used by the SPS resource or the exact location of the SPS resource, the terminal can accurately know the information of the SPS resource transmitted from the base station after receiving the SPS activation message. When the SPS is activated, resource allocation may be repeated every predetermined period 320 ( 311 , 312 , 313 ), and the PDCCH resource is not involved in the repeated resource allocation.

However, when successful transmission of data received by the terminal using the SPS resource fails, the terminal may notify the transmission failure by transmitting a Hybrid Automatic Repeat Request (HARQ) Non-acknowledgement (NACK) message to the base station. After receiving the HARQ NACK message, the base station may perform retransmission. The resource for retransmission of the SPS resource may be allocated one-time by the base station. In step 322, the retransmission resource may be allocated in the PDCCH using the CS-RNTI.

In step 340, the base station may deactivate the SPS when it no longer uses the SPS resource. The SPS deactivation message may be transmitted in the form of DCI of PDCCH using CS-RNTI. When the terminal receives the deactivation message of the SPS, in step 314, the terminal may delete the configuration information received from the activation message of the SPS received in step 330. However, the terminal does not delete the configuration information received from the SPS configuration message received in step 300, and can be used when the SPS is activated again later.

4 is a diagram illustrating an operation of an MBS SPS according to an embodiment of the present disclosure.

In multicast or broadcast communication in which the base station communicates with multiple terminals, there are two methods for the base station to allocate a downlink radio resource (downlink grant) to the terminal: a dynamic grant and a semi-persistent scheduling (SPS). A method may exist. The dynamic grant is a method in which the base station changes the location and configuration of a resource for every radio resource and allocates it. The resource can be allocated in a Physical Downlink Control Channel (PDCCH) by the G-RNTI shared by terminals receiving the MBS service. Once a resource is allocated by this dynamic grant method, only the allocated resource is a valid one-shot resource. On the other hand, the resource allocated by the SPS method means a resource allocated semi-persistently once it is set.

The dynamic grant is inefficient because PDCCH resources are used to allocate resources using PDCCH resources, and thus, when the same resource needs to be allocated periodically, PDCCH resources are repeatedly used. When it is necessary to periodically allocate resources of the same configuration, it is efficient to use the resources of the same configuration repeatedly without using PDCCH resources after setting and activation once, as it can reduce the consumption of PDCCH resources. have.

In step 400, the SPS resource for MBS (MBS SPS) may be set by an RRC setup message or a reconfiguration message transmitted from the base station to the terminal. However, according to an embodiment, the MBS SPS configuration information may be transmitted while being included in a system information block transmitted from the base station to the terminals. The MBS SPS configuration information may include essential information such as the period 420 of the SPS resource.

However, after the MBS SPS is set, there is no need to activate the MBS SPS resource. Since it may be more efficient to use the MBS SPS resource only when there is downlink data to be transmitted by the base station, the MBS SPS resource does not need to be activated immediately after the MBS SPS is set. Therefore, when the MBS SPS resource is configured, in step 410, the base station and the terminal cannot use the MBS SPS resource because the MBS SPS resource is not activated. In FIG. 4, the location of the MBS SPS resource that is not activated in step 410 is described as virtual, but the specific location of the MBS SPS resource can be applied by the MBS SPS activation message, so unused MBS SPS information (eg For example, location information of the MBS SPS resource) is not possessed by the base station and the terminal. Thereafter, when the terminal receives the MBS SPS activation message transmitted by the base station to the terminal in step 430, the downlink radio resource is used using the actual MBS SPS resource, and the terminal may receive downlink data.

In step 430, the MBS SPS activation message may be transmitted in the form of Downlink Control Information (DCI) of the PDCCH by using Group - Configured Scheduling - Radio Network Temporary Identity (G-CS-RNTI). In this case, specific information of DCI may indicate activation of MBS SPS. Since DCI informs the MCS (Modulation & Coding Scheme) information to be used by the MBS SPS resource or the exact location of the MBS SPS resource, after receiving the MBS SPS activation message, the terminal can accurately know the information of the MBS SPS resource transmitted from the base station. . When the MBS SPS is activated, resource allocation may be repeated every predetermined period 420 (411, 412, 413), and the PDCCH resource is not involved in the repeated resource allocation. According to an embodiment, the MBS SPS activation message may be transmitted in the form of MAC CE (Medium Access Control - Control Element) or RRC message. According to various embodiments of the present disclosure, regardless of the format, a message including MCS (Modulation & Coding Scheme) information to be used by the MBS SPS resource or a message including the exact location of the MBS SPS resource is transmitted, so that the terminal uses the MBS SPS resource. It can receive transmitted data.

However, when the successful transmission of data received by the terminal fails using the MBS SPS resource, the terminal transmits a Hybrid Automatic Repeat Request (HARQ) Non-acknowledgement (NACK) message to the base station to notify the transmission failure. After receiving the HARQ NACK message, the base station may perform retransmission. The resource for retransmission of the MBS SPS resource may be allocated by the base station on a one-time basis. In step 422, the retransmission resource may be allocated in the PDCCH using the G-CS-RNTI.

Only when the initial transmission resource 412 transmitted using the MBS SPS resource is not successfully received, the terminal may perform reception of the allocated resource using the G-CS-RNTI. If the initial transmission data transmitted using the MBS SPS resource is successfully received, there is no need to additionally perform reception of the resource allocated using the G-CS-RNTI. That is, if the previously transmitted data for the resource allocated using the G-CS-RNTI is successfully received, there is no need to perform the reception of the resource allocated using the G-CS-RNTI again. If the previously transmitted data for the resource allocated using G-CS-RNTI has not been successfully received (for example, if the MAC PDU (Protocol Data Unit) for the HARQ process has never been received, or the corresponding If the transport block for the HARQ process is not successfully decoded, etc.), the UE capable of receiving the MBS SPS resource may perform reception of the retransmission resource using the G-CS-RNTI.

Afterwards, when the base station no longer uses the MBS SPS resource, the base station may deactivate the MBS SPS in step 440 . The SPS deactivation message may be transmitted in the form of DCI of PDCCH using G-CS-RNTI. However, in another embodiment, the MBS SPS deactivation message may be transmitted in the form of MAC CE or may be transmitted as an RRC message. When the terminal receives the deactivation message of the MBS SPS, in step 414, the terminal may delete the configuration information received from the activation message of the corresponding SPS received in step 430. If the terminal receives the deactivation message for the MBS SPS that has already been deleted, since this message may be a message retransmitted by the base station due to the reason that the MBS SPS deactivation message is not successfully delivered to other terminals, the terminal receives this deactivation message can be ignored. However, the terminal does not delete the configuration information received from the MBS SPS configuration message received in step 400, and can be used when this SPS is activated again later.

5 is a diagram illustrating an operation of an MBS SPS according to an embodiment of the present disclosure.

In multicast or broadcast communication in which the base station communicates with multiple terminals, there are two methods for the base station to allocate a downlink radio resource (downlink grant) to the terminal: dynamic grant and semi-persistent scheduling (SPS). A method may exist. The dynamic grant is a method in which the base station changes the location and configuration of a resource for every radio resource and allocates it by using the G-RNTI shared by terminals receiving the MBS service. have. Once a resource is allocated by this dynamic grant method, only the allocated resource is a valid one-shot resource. On the other hand, the resource allocated by the SPS method means a resource allocated semi-persistently once it is set.

The dynamic grant is inefficient because PDCCH resources are used to allocate resources using PDCCH resources, and thus, when the same resource needs to be allocated periodically, PDCCH resources are repeatedly used. When it is necessary to periodically allocate resources of the same configuration, it is efficient to use the resources of the same configuration repeatedly without using PDCCH resources after setting and activation once, as it can reduce the consumption of PDCCH resources. have.

In step 500, the SPS resource for MBS (MBS SPS) may be set by an RRC setup message or a reconfiguration message transmitted from the base station to the terminal. According to another embodiment, the MBS SPS configuration information may be transmitted while being included in a system information block transmitted from the base station to the terminals. According to an embodiment, the MBS SPS may be set and activated at the same time.

In the embodiment of FIG. 5 , the operation of the terminal successfully receiving the MBS SPS configuration message and applying the configuration may include an operation of activating the MBS SPS without receiving a separate MBS SPS activation message.

In the case of MBS SPS, since multiple terminals can use the MBS SPS resource at the same time, when the MBS SPS is configured for one terminal, it is highly likely that the MBS SPS resource is already activated and used. The information of the MBS SPS setting and activation message includes not only essential information such as the period 520 of the SPS resource, but also MCS (Modulation & Coding Scheme) information or the exact location of the MBS SPS resource. can receive After receiving the MBS SPS setup and activation message, the terminal can accurately know the information of the MBS SPS resource transmitted from the base station. And the MBS SPS activation indication message may include a reference SFN (System Frame Number) at which the MBS SPS starts to be configured, and the terminal uses the resource by applying an offset to the MBS SPS resource location based on this reference SFN. may be Thereafter, the UE may use the MBS SPS resources 510 , 511 , 512 , 513 , and 514 that are repeated every predetermined period 520 . The PDCCH resource is not involved in the UE repeatedly using the MBS SPS resource.

However, when the successful transmission of data received by the terminal fails using the MBS SPS resource, the terminal transmits a Hybrid Automatic Repeat Request (HARQ) Non-acknowledgement (NACK) message to the base station to notify the transmission failure. After receiving the HARQ NACK message, the base station may perform retransmission. The resource for retransmission of the MBS SPS resource may be allocated by the base station on a one-time basis. In step 522, the retransmission resource may be allocated by the PDCCH using the G-CS-RNTI. Only when the initial transmission resource 512 transmitted using the MBS SPS resource is not successfully received, the terminal may perform reception of the allocated resource using the G-CS-RNTI. If the initial transmission data transmitted using the MBS SPS resource has already been successfully received, there is no need to additionally perform reception of the resource allocated using the G-CS-RNTI. That is, if the previously transmitted data for the resource allocated using the G-CS-RNTI is successfully received, there is no need to perform the reception of the resource allocated using the G-CS-RNTI again. If the previously transmitted data for the resource allocated using G-CS-RNTI has not been successfully received (for example, if the MAC PDU for the corresponding HARQ process has not been received, or the transport for the corresponding HARQ process If the block is not successfully decoded, etc.), the terminal capable of receiving the MBS SPS resource may perform the reception of the retransmission resource using the G-CS-RNTI.

6 is a diagram illustrating an operation of an MBS SPS according to an embodiment of the present disclosure.

In multicast or broadcast communication in which the base station communicates with multiple terminals, there are two methods for the base station to allocate a downlink radio resource (downlink grant) to the terminal: dynamic grant and semi-persistent scheduling (SPS). A method may exist. The dynamic grant is a method in which the base station changes the location and configuration of a resource for every radio resource and allocates it. The resource can be allocated in a Physical Downlink Control Channel (PDCCH) by the G-RNTI shared by terminals receiving the MBS service. Once a resource is allocated by this dynamic grant method, only the allocated resource is a valid one-shot resource. On the other hand, the resource allocated by the SPS method means a resource allocated semi-persistently once it is set.

The dynamic grant is inefficient because PDCCH resources are used to allocate resources using PDCCH resources, and thus, when the same resource needs to be allocated periodically, PDCCH resources are repeatedly used. When it is necessary to periodically allocate resources of the same configuration, it is efficient to use the resources of the same configuration repeatedly without using PDCCH resources after setting and activation once, as it can reduce the consumption of PDCCH resources. have.

In step 600, the MBS SPS resource (MBS SPS) may be set by an RRC setup message or a reconfiguration message transmitted from the base station to the terminal. According to an embodiment, the MBS SPS configuration information may be transmitted while being included in a system information block transmitted by the base station to the terminals. According to an embodiment, MBS SPS may be set and activation may be indicated at the same time.

According to the embodiment shown in FIG. 6, the base station transmits an MBS SPS configuration message including an indicator indicating the activation of the MBS SPS, and the terminal includes an indicator indicating the activation of the MBS SPS is included in the MBS SPS configuration message. When there is, an operation of activating the MBS SPS may be performed.

In the case of MBS SPS, since multiple terminals can use the MBS SPS resource at the same time, when the MBS SPS is configured for one terminal, it is highly likely that the MBS SPS resource is already activated and used. The information of the message instructing the activation of the MBS SPS at the same time as the setting of the MBS SPS includes not only information essential for the setting of the MBS SPS such as the period of the SPS resource 620, but also the MCS information required for the activation of the MBS SPS or the correct MBS SPS resource. The location may be included, and information that allows the terminal to receive the MBS SPS resource immediately may be included. According to an embodiment, when the terminal receives information indicating the location of the MCS or MBS resource required for the activation of the MBS SPS instead of the indicator indicating the activation of the MBS SPS, the MBS SPS may be activated. After receiving the MBS SPS setup and activation message, the terminal can accurately know the information of the MBS SPS resource transmitted from the base station. In addition, the MBS SPS activation indication information may include a reference SFN (System Frame Number) from which the MBS SPS is configured, and the UE may use the resource by applying an offset to the MBS SPS resource location based on this reference SFN. . Thereafter, the UE may use the MBS SPS resources 610 , 611 , 612 , and 613 that are repeated every predetermined period 620 . The PDCCH resource is not involved in the UE repeatedly using the MBS SPS resource. If only the MBS SPS is set in step 600 and activation is not indicated, the MBS SPS may be activated later by the MBS SPS activation message transmitted in step 430 of FIG. 4 ).

However, when the successful transmission of data received by the terminal fails using the MBS SPS resource, the terminal transmits a Hybrid Automatic Repeat Request (HARQ) Non-acknowledgement (NACK) message to the base station to inform the transmission failure. After receiving the HARQ NACK message, the base station may perform retransmission. The resource for retransmission of the MBS SPS resource may be allocated by the base station on a one-time basis. In step 622, the retransmission resource may be allocated in the PDCCH using the G-CS-RNTI. Only when the initial transmission data 612 transmitted using the MBS SPS resource is not successfully received, the terminal may perform reception of the allocated resource using the G-CS-RNTI. If the initial transmission data transmitted using the MBS SPS resource has already been successfully received, there is no need to additionally perform reception of the resource allocated using the G-CS-RNTI. That is, if the previously transmitted data for the resource allocated using the G-CS-RNTI is successfully received, there is no need to perform the reception of the resource allocated using the G-CS-RNTI again. If the previously transmitted data for the resource allocated using G-CS-RNTI has not been successfully received (for example, if the MAC PDU for the corresponding HARQ process has not been received, or the transport for the corresponding HARQ process If the block is not successfully decoded, etc.), the terminal capable of receiving the MBS SPS resource may perform the reception of the retransmission resource using the G-CS-RNTI.

Afterwards, when the base station no longer uses the MBS SPS resource, in step 640, the base station may deactivate the MBS SPS. The MBS SPS deactivation message may be transmitted in the form of DCI of PDCCH using G-CS-RNTI. However, in another embodiment, the MBS SPS deactivation message may be transmitted in the form of MAC CE or may be transmitted as an RRC message. When the terminal receives the deactivation message of the MBS SPS, in step 614, the terminal may delete the configuration information received from the activation message of the corresponding SPS received in step 630. If the terminal receives the deactivation message for the MBS SPS that has already been deleted, since this message may be a message retransmitted by the base station due to the reason that the MBS SPS deactivation message is not successfully delivered to other terminals, the terminal receives this deactivation message can be ignored. However, the terminal does not delete the configuration information received from the MBS SPS configuration message received in step 600, and can be used when this SPS is activated again later.

7 is a diagram illustrating a method of transmitting an MBS SPS activation and deactivation confirmation message according to an embodiment of the present disclosure.

In step 730, the SPS resource for MBS (MBS SPS) may be set by an RRC setup message or an RRC reconfiguration message transmitted from the base station 710 to the terminal 720 . Essential information such as the period of the SPS resource may be set in the MBS SPS setting information. The terminal 720 that receives the message for setting the MBS SPS may apply the received message. After applying the message for setting the MBS SPS, in step 740, the terminal 720 may transmit an MBS setting complete message to inform the base station 710 that the message has been successfully received and applied. If the MBS SPS configuration message transmitted from the base station 710 in step 730 uses some configuration of the RRC message, the MBS SPS configuration complete message 740 transmitted from the terminal 720 in step 740 is an RRC message It may be an RRC setup complete message or an RRC reconfiguration complete message defined as .

However, after the MBS SPS is set, there is no need to activate the MBS SPS resource. This is because it may be more efficient to use the MBS SPS resource only when there is downlink data to be transmitted by the base station 710 . Therefore, when the MBS SPS resource is configured, the MBS SPS resource may not be used immediately.

Afterwards, in step 750, when the terminal 720 receives the MBS SPS activation message transmitted from the base station 710 to the terminal 720, the downlink radio resource is used using the actual MBS SPS resource, and the terminal 720 is downlinked. Link data can be received.

The MBS SPS activation message may be transmitted from the base station 710 to the terminal 720 in the form of Downlink Control Information (DCI) of the PDCCH using Group - Configured Scheduling - Radio Network Temporary Identity (G-CS-RNTI). In this case, specific information of DCI may indicate activation of MBS SPS. Since the DCI informs the MCS (Modulation & Coding Scheme) information to be used by the MBS SPS resource, or the exact location of the MBS SPS resource, the terminal 720 after receiving the MBS SPS activation message MBS SPS transmitted from the base station 710 You can get accurate information about resources. When the MBS SPS is activated, resource allocation may be repeated at regular intervals, and the PDCCH resource is not involved in the repeated resource allocation.

According to an embodiment, the MBS SPS activation message may be transmitted in the form of MAC CE (Medium Access Control - Control Element) or RRC message. According to various embodiments of the present disclosure, regardless of the format, a message including MCS (Modulation & Coding Scheme) information to be used by the MBS SPS resource or a message including the exact location of the MBS SPS resource is transmitted, thereby allowing the terminal 720 to use the MBS SPS resource. You can receive the transmitted data using

Since the MBS SPS activation message for the MBS SPS is transmitted in a multicast or broadcast manner, it is difficult for the base station 710 to know whether the MBS SPS activation is correctly performed for all terminals. In addition, it is difficult to assume that the MBS service is multicast or broadcast and always receives feedback on data transmitted using the MBS SPS. Therefore, in step 760, the terminal 720 may notify the base station 710 whether the MBS SPS has been activated. The operation of the terminal 720 notifying the base station 710 of whether the MBS SPS has been activated may be referred to as MBS SPS activation confirmation. The MBS SPS activation confirmation message may be generated after receiving an instruction to activate the MBS SPS from the base station 710 in step 750 and transmitted to the base station 710 . The activation confirmation message of the MBS SPS may be transmitted in the MAC CE format. In another embodiment, the activation confirmation message of the MBS SPS may be in the form of Uplink Control Information (UCI) of a Physical Uplink Control Channel (PUCCH). In another embodiment, the MBS SPS activation confirmation message may be in the form of an RRC message.

If activation of the MBS SPS is simultaneously indicated in the MBS SPS configuration message as shown in FIG. 6 , the terminal 720 may not transmit the MBS SPS activation confirmation message. The MBS SPS activation confirmation message may include an MBS SPS identifier (Identity) to identify which MBS SPS activation is confirmed. Alternatively, the MBS activation confirmation message may include a field corresponding to the setting of the MBS SPS and indicate whether an activation message of the corresponding MBS SPS has been received (or applied).

If the base station 710 no longer uses the MBS SPS resource after using the activated MBS SPS, the base station 710 may deactivate the MBS SPS in step 770 . This deactivation message may be transmitted in the form of DCI of PDCCH using G-CS-RNTI. However, in another embodiment, the MBS SPS deactivation message may be transmitted in the form of MAC CE or RRC message. When the terminal 720 receives the MBS SPS deactivation message, it may delete the received configuration information from the SPS activation message received in step 750 . If the terminal 720 receives the deactivation message for the MBS SPS that has already been deleted, this message may be a message retransmitted by the base station 710 for the reason that the MBS SPS deactivation message is not successfully delivered to other terminals. , the terminal 720 may ignore this message. However, the terminal 720 does not delete the configuration information received from the MBS SPS configuration message received in step 730, and can be used when the SPS is activated again later.

Since the MBS SPS deactivation message for the MBS SPS is transmitted in a multicast or broadcast manner, it is difficult for the base station 710 to know whether the deactivation of the MBS SPS has been accurately performed for all terminals. In addition, it is difficult to assume that the MBS service is multicast or broadcast and always receives feedback on data transmitted using the MBS SPS. Therefore, in step 780, the terminal 720 may notify the base station 710 whether the MBS SPS has been deactivated. The operation of the terminal 720 informing the base station 710 of whether the deactivation of the MBS SPS has been made may be referred to as MBS SPS deactivation confirmation. The MBS SPS deactivation confirmation message may be generated after receiving an instruction to deactivate the MBS SPS from the base station 710 in step 770 and transmitted to the base station 710 . The MBS SPS deactivation confirmation message may be transmitted in MAC CE format. In another embodiment, the deactivation confirmation message of the MBS SPS may be in the form of Uplink Control Information (UCI) of a Physical Uplink Control Channel (PUCCH). In another embodiment, the MBS SPS deactivation confirmation message may be in the form of an RRC message.

The deactivation confirmation message of the MBS SPS may include an identifier (Identity) of the MBS SPS to identify which MBS SPS deactivation is confirmed. Alternatively, the deactivation confirmation message of the MBS SPS may include a field corresponding to the setting of the MBS SPS and indicate whether the deactivation message of the corresponding MBS SPS is received (or applied). According to an embodiment, the MBS SPS activation confirmation message transmitted from the terminal 720 in step 760 and the MBS SPS deactivation confirmation message transmitted in step 780 may use the same message format. For example, the activation confirmation message of the MBS SPS or the deactivation confirmation message of the MBS SPS includes a field value corresponding to the identifier of the MBS SPS or the identifier of the MBS SPS, thereby indicating activation or deactivation of the MBS SPS.

8 is a diagram illustrating operations of a base station and a terminal when MBS SPS is activated according to an embodiment of the present disclosure.

In step 810 MBS SPS may be set and activated. According to the embodiment of FIG. 8 , as described with reference to steps 430, 500, 600, and 750, activation of the MBS SPS may be instructed from the base station to the terminal. Activation of the MBS SPS may be indicated by using the PDCCH resource by the G-CS-RNTI, and at this time, a New Data Indicator (NDI) value may be set to 0 to indicate that the MBS SPS is activated.

When the MBS SPS is activated, in step 820, the MAC layer apparatus of the terminal and the base station may store MBS SPS allocation information and HARQ information related to MBS SPS allocation information. The HARQ information may be at least one of HARQ process ID, MCS-related information, and TB size.

In step 830, the MAC layer device may perform initialization (Initialization) or re-initialization (Re-initialization) of resources configured for the MBS SPS. If the MBS SPS resource is activated while it is not activated, it may correspond to initialization, and if the MBS SPS resource that has already been activated is activated again, it may correspond to reactivation.

Thereafter, the terminal needs to receive the activation message of the MBS SPS and notify the base station that it has been applied. In step 840, the terminal may transmit a confirmation message for the activation of the MBS SPS. The activation confirmation message of the MBS SPS may be transmitted in the MAC CE format. In another embodiment, the activation confirmation message of the MBS SPS may be in the form of Uplink Control Information (UCI) of a Physical Uplink Control Channel (PUCCH). In another embodiment, the MBS SPS activation confirmation message may be in the form of an RRC message.

If activation of the MBS SPS is simultaneously indicated in the configuration message of the MBS SPS as shown in FIG. 6 , the UE may not transmit the MBS SPS activation confirmation message. The activation confirmation message of the MBS SPS may include an identifier (Identity) of the MBS SPS to identify which MBS SPS activation is confirmed. Alternatively, the MBS SPS activation confirmation message may include a field corresponding to the setting of the MBS SPS and indicate whether an activation message of the corresponding MBS SPS has been received (or applied). When the base station receives the MBS SPS activation message from the terminal, it may recognize that the MBS SPS has been successfully activated by the terminal. However, if the MBS SPS activation message is not received, the base station may recognize that the terminal fails to activate the corresponding MBS SPS, and may retransmit the MBS SPS activation message.

9 is a diagram illustrating operations of a base station and a terminal when MBS SPS is deactivated according to an embodiment of the present disclosure.

In step 910 MBS SPS may be deactivated. According to the embodiment of FIG. 9 , as described with reference to steps 440, 640, 770, and the like, deactivation of the MBS SPS may be instructed from the base station to the terminal. Deactivation of the MBS SPS may be indicated by using the PDCCH resource by the G-CS-RNTI. At this time, a New Data Indicator (NDI) value may be set to 0 to indicate deactivation of the MBS SPS.

When the MBS SPS is deactivated, in step 920, the MAC layer apparatus of the terminal and the base station may delete MBS SPS allocation information and HARQ information associated therewith. The HARQ information may be at least one of HARQ process ID, MCS-related information, and TB size.

Thereafter, the terminal needs to receive the MBS SPS deactivation message and notify the base station that it has been applied. Therefore, in step 930, the terminal may transmit a confirmation message for deactivation of the MBS SPS. The deactivation confirmation message of the MBS SPS may be transmitted in the MAC CE format. In another embodiment, the deactivation confirmation message of the MBS SPS may be in the form of Uplink Control Information (UCI) of a Physical Uplink Control Channel (PUCCH). In another embodiment, the MBS SPS deactivation confirmation message may be in the form of an RRC message. The deactivation confirmation message of the MBS SPS may include an identifier (Identity) of the MBS SPS to identify which MBS SPS deactivation is confirmed. Alternatively, the deactivation confirmation message of the MBS SPS may have a field corresponding to the setting of the MBS SPS and indicate whether the deactivation message of the corresponding MBS SPS is received (or applied).

When the base station receives the MBS SPS deactivation message from the terminal, the base station may recognize that the terminal has successfully deactivated the MBS SPS. However, if the MBS SPS deactivation message is not received, the base station may recognize that the terminal has failed to deactivate the corresponding MBS SPS and retransmit the MBS SPS deactivation message.

According to an embodiment, the terminal in the idle mode or the inactive mode may receive MBS SPS data in an activated state by setting the MBS SPS. When the terminal that was receiving the MBS SPS data receives an instruction to deactivate the corresponding MBS SPS from the base station, the terminal may transition to the connected mode. The terminal may transition to the connected mode, and may transmit to the base station a confirmation message indicating that the deactivation message of the MBS SPS has been received and applied. However, according to one embodiment, only when the terminal in the idle mode or inactive mode can no longer receive the MBS service of interest due to the deactivation of the corresponding MBS SPS, the terminal transitions to the connected mode and provides the MBS service of interest to the base station information can be transmitted. Thereafter, the base station may provide the MBS service again for the corresponding terminal.

10 is a diagram illustrating an operation according to MBS SPS deactivation of a terminal in an idle mode or an inactive mode according to an embodiment of the present disclosure.

A terminal in an idle mode or an inactive mode may not perform direct communication in a state in which the connection with the base station is released. The terminal may periodically receive a paging message from the base station, and may transition to the connected mode by determining whether there is a downlink message to be transmitted to the terminal by the paging message. However, the terminal in the idle mode or the inactive mode may receive the MBS service from the base station. This may be possible through the MBS service configuration information to be used in the idle mode or inactive mode in the RRC release message received before the terminal transitions from the connected mode to the idle mode or the inactive mode, or a system information block that can be received from the base station. have. In this case, the information of the MBS service may include information on setting and activation of the MBS SPS.

According to the embodiment of FIG. 10 , the MBS SPS may be deactivated while the terminal in the idle mode or the inactive mode is receiving the MBS service through the MBS SPS in step 1010 . The base station can know that the terminal in the connected mode receives the MBS SPS, but it is difficult to know exactly that the idle mode or the inactive mode terminal receives the MBS SPS. Therefore, when the base station deactivates the MBS SPS that has provided the MBS service, there may exist an idle mode or an inactive mode terminal that needs to provide the MBS service using the MBS SPS resource.

In step 1020, when the MBS SPS, which was provided with the MBS service in the idle mode or the inactive mode, is deactivated, the terminal may transition to the connected mode. In addition, the idle mode or inactive mode terminal may transition to the connected mode even when the MBS SPS that has been provided with the MBS service is released. According to an embodiment, tmgi receiving the MBS service through the MBS SPS resource may be configured. The UE may transition to the connected mode only when the MBS SPS for the service of interest or for the tmgi receiving the service is deactivated or released.

To transition from the idle mode to the connected mode, the UE may transmit an RRC connection request message to the base station to transition to the connected mode. To transition from the inactive mode to the connected mode, the UE may transmit an RRC connection resumption message to the base station to transition to the connected mode.

When the terminal transitions to the connected mode, in step 1030, the terminal may inform the base station that it is no longer receiving the MBS service being received by using the MBS SPS resource. According to an embodiment, the notification that the MBS service cannot be received may be in the form of an MBS SPS deactivation confirmation message. According to another embodiment, the notification that the MBS service cannot be received is included in the RRC message transmitted to the base station when transitioning to the connected mode, and the list of MBS services that were being received but cannot now be received (eg, of tmgi) list) can be transmitted. According to this information, the base station may provide the MBS service to the terminal again.

11 is a diagram illustrating an operation of a terminal with respect to a retransmission resource of an MBS SPS according to an embodiment of the present disclosure.

When the initial transmission using the MBS SPS fails, at least one terminal may transmit feedback such as a NACK to the base station. In step 1110, the base station may allocate the retransmission resource of the MBS SPS resource to the terminal based on the feedback. The terminal may be allocated a retransmission resource for the MBS SPS by the base station. The retransmission resource may be transmitted in the form of Downlink Control Information (DCI) of the PDCCH by using the G-CS-RNTI. In this case, the base station may set the NDI value included in the transmitted information to 1 to inform that the transmitted information is information indicating the retransmission resource of the MBS SPS.

In step 1120, the terminal, by the initial transmission or previous retransmission of the MBS SPS resource, the data of the TB (or the corresponding MAC PDU) for the HARQ process has already been successfully decoded (or successfully received) Whether to check whether have.

If it is not already successfully transmitted, the terminal needs to receive a retransmission resource. Accordingly, in step 1130, the UE may perform an operation for retransmission by considering that the NDI for the HARQ process is not toggled. Thereafter, in step 1140, the UE may notify the HARQ device that there is a downlink resource (retransmission resource) allocated and transmit related HARQ information.

On the other hand, if the data of the TB for the HARQ process has already been successfully decoded in step 1120, the MAC layer device may ignore this PDCCH in step 1150 and may not receive it. Since step 1150 assumes that the MBS service is provided in a multicast or broadcast manner for transmitting to multiple terminals, the terminal has already successfully received the data, but it can be performed when the base station retransmits it for another terminal. .

12 is a diagram illustrating a structure in which an MBS SPS is configured according to an embodiment of the present disclosure.

One MBS SPS may be set for one BWP (BandWidth Part). Therefore, the setting of the MBS SPS may be set depending on the downlink BWP setting (BWP-Downlink) 1210 . Each downlink BWP may be divided by a BWP-ID 1220 that is an identifier of the BWP and configured under the serving cell configuration. The downlink BWP setting may be divided into common BWP information 1230 and specific BWP information 1240 . The common BWP information 1230 may include the location and bandwidth of the BWP, whether to use SubCarrier Spacing (SCS), Extended Cyclic Prefix (CP), and common configuration information of the PDCCH and the PDSCH. The specific BWP information 1240 may include not only PDCCH and PDSCH configuration but also unicast SPS configuration information and MBS SPS configuration information.

MBS SPS setting information includes G-CS-RNTI value used for MBS SPS, number of HARQ processes used (nofHARQ-Processes), offset of HARQ process (harq-ProcID-Offset), cycle of MBS SPS, MBS SPS At least one of an identifier for identifying the MBS and a list (tmgi) of MBS services provided by the corresponding MBS SPS may be included.

Unicast SPS and MBS SPS may be simultaneously configured in a specific BWP downlink. According to an embodiment, in order to identify the unicast SPS and the MBS SPS, a delimiter indicating that the SPS is an MBS SPS may be included in the SPS configuration information. If the identifier included in the SPS configuration information is set to True, this SPS may indicate that it is an MBS SPS. Data for the MBS SPS may correspond to a Point-To-Multipoint (PTM) bearer. If the delimiter included in the SPS configuration information is set to false, this SPS may indicate that it is a unicast SPS. According to an embodiment, when the G-CS-RNTI or the provided MBS service list (eg, tmgi list) is included in the SPS configuration information, the SPS may be classified as an MBS SPS.

Since a plurality of MBS SPSs may be configured within the corresponding BWP or within the corresponding terminal, an identifier (Identity) for identifying the MBS SPS may be set. The identifier of the MBS SPS may be distinguished from the MBS SPS by using the same SPS configuration ID as the unicast SPS and by a delimiter indicating the MBS SPS. The downlink BWP configuration (BWP-Downlink) including the MBS SPS configuration may be transmitted by an RRC message or transmitted by a system information block and configured to the terminal.

13 is a diagram illustrating a structure in which an MBS SPS is configured according to an embodiment of the present disclosure.

Since the MBS SPS is a type of resource providing the MBS service, the MBS SPS may be configured in units of cells or cell groups configured in the UE. 13 shows a case where MBS SPS configuration (MBS SPS-Config) is used separately. The MBS SPS configuration 1310 may indicate in which BWP the MBS SPS is configured by including the cell ID and the BWP ID 1320 in which the corresponding MBS SPS is configured. And since a plurality of MBS SPS can be configured within the BWP or within the terminal, the MBS SPS configuration 1310 may include an identifier (Identity) for identifying the MBS SPS. The identifier for identifying the MBS SPS may be named MBS SPS Configuration Index 1330 . In addition, the MBS SPS configuration 1310 may include detailed information 1340 for the MBS SPS. These details include G-CS-RNTI value used for MBS SPS, number of HARQ processes used (nofHARQ-Processes), offset of HARQ process (harq-ProcID-Offset), cycle of MBS SPS, identify MBS SPS At least one of an identifier for performing an MBS and a list of MBS services provided by the corresponding MBS SPS (eg, a tmgi list) may be included. Data for the MBS SPS may correspond to a Point-To-Multipoint (PTM) bearer. This MBS SPS configuration may be transmitted by an RRC message or transmitted by a system information block and configured to the terminal.

14 is a diagram illustrating a structure of a base station according to an embodiment of the present disclosure.

Referring to FIG. 14 , the base station may include a transceiver 1410 , a processor 1420 , and a memory 1430 . In the present disclosure, the processor 1420 may be a circuit or an application-specific integrated circuit, and may be at least one processor. Various embodiments of the present disclosure are not limited to the example illustrated in FIG. 14 , and the base station may include more or fewer configurations than the configuration of FIG. 14 . In addition, the transceiver 1410 , the processor 1420 , and the memory 1430 may be implemented in the form of a single chip.

The transceiver 1410 may transmit/receive signals to and from other network entities. The transceiver 1410 may transmit, for example, system information to the terminal, and may transmit a synchronization signal or a reference signal. In addition, the signal transmitted and received with the terminal or network entity may include control information and data. To this end, the transceiver 1410 may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts a received signal. However, this is only an exemplary embodiment of the transceiver 1410 , and components of the transceiver 1410 are not limited to the RF transmitter and the RF receiver. In addition, the transceiver 1410 may receive a signal through a wireless channel, output it to the processor 1420 , and transmit a signal output from the processor 1420 through a wireless channel.

The processor 1420 may control the overall operation of the base station according to the embodiment proposed in the present disclosure. For example, the processor 1420 may control a signal flow between blocks to perform the operation of the base station described above with reference to FIGS. 1 to 13 .

The memory 1430 may store at least one of information transmitted/received through the transceiver 1410 and information generated through the processor 1420 . The memory 1430 may store programs and data necessary for the operation of the base station. Also, the memory 1430 may store control information or data included in a signal obtained from a network entity. The memory 1430 may be configured as a storage medium or a combination of storage media, such as ROM, RAM, hard disk, CD-ROM, and DVD. Also, the number of memories 1430 may be plural.

15 is a diagram illustrating a structure of a terminal according to an embodiment of the present disclosure.

Referring to FIG. 15 , the terminal may include a transceiver 1510 , a processor 1520 , and a memory 1530 . In the present disclosure, the processor 1520 may be a circuit or an application-specific integrated circuit, and may be at least one processor. Various embodiments of the present disclosure are not limited to the example illustrated in FIG. 15 , and the terminal may include more or fewer configurations than those of FIG. 15 . In addition, the transceiver 1510 , the processor 1520 , and the memory 1530 may be implemented in the form of a single chip.

The transceiver 1510 may transmit/receive signals to and from other network entities. The transceiver 1510 may receive, for example, system information from a base station, and may receive a synchronization signal or a reference signal. In addition, the signal transmitted and received with the base station or the network entity may include control information and data. To this end, the transceiver 1510 may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal, and an RF receiver for low-noise amplifying and down-converting a received signal. However, this is only an example of the transceiver 1510, and components of the transceiver 1510 are not limited to the RF transmitter and the RF receiver. In addition, the transceiver 1510 may receive a signal through a wireless channel, output it to the processor 1520 , and transmit a signal output from the processor 1520 through a wireless channel.

The processor 1520 may control the overall operation of the terminal according to the embodiment proposed in the present disclosure. For example, the processor 1520 may control a signal flow between blocks to perform the operation of the terminal described above with reference to FIGS. 1 to 13 .

The memory 1530 may store at least one of information transmitted/received through the transceiver 1510 and information generated through the processor 1520 . The memory 1530 may store programs and data necessary for the operation of the terminal. Also, the memory 1530 may store control information or data included in a signal obtained from the terminal. The memory 1530 may be configured of a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media. Also, the number of memories 1530 may be plural.

16 is a diagram illustrating operations of a base station and a terminal when MBS SPS is activated according to an embodiment of the present disclosure.

In step 1610 MBS SPS may be set and activated. According to the embodiment of FIG. 16 , as described with reference to steps 430, 500, 600, 750, and the like, activation of the MBS SPS may be instructed from the base station to the terminal. Activation of the MBS SPS may be indicated by using the PDCCH resource by the G-CS-RNTI, and at this time, a New Data Indicator (NDI) value may be set to 0 to indicate that the MBS SPS is activated.

If this MBS SPS is already being transmitted to other terminals and a certain terminal needs to receive it from the middle of the MBS SPS, the activation of the MBS SPS is based on the CS-RNTI that can be used for one terminal, not the G-CS-RNTI. may be indicated by using the PDCCH resource. When the MBS SPS is activated, the MAC layer apparatus of the terminal and the base station may store allocation information of the MBS SPS and HARQ information related to the allocation information of the MBS SPS. The HARQ information may be at least one of HARQ process ID, MCS-related information, and TB size. The MAC layer device may perform initialization (Initialization) or re-initialization (Re-initialization) of resources configured for the MBS SPS. If the MBS SPS resource is activated while it is not activated, it may correspond to initialization, and if the MBS SPS resource that has already been activated is activated again, it may correspond to reactivation.

The base station may instruct the terminal to activate the MBS SPS, but if the terminal fails to decode the PDCCH and thus fails to activate (or re-activate) the MBS SPS, the base station may instruct the activation of the MBS SPS again or change the setting. can However, if there is no feedback (response) of the terminal or the information transmitted by the feedback is limited, it is difficult for the base station to know whether the terminal actually applied the activation of the MBS SPS. In order to prevent this, the terminal may perform an operation of notifying the base station that the activation of the MBS SPS has been applied. However, if the terminal is set to give feedback on the reception of the MBS SPS, the base station can know the MBS SPS activation of the terminal when the feedback of the terminal is sent.

When the MBS SPS is activated, in step 1620, the MAC layer device of the UE may check whether ACK/NACK feedback for the downlink MBS SPS for which activation is indicated is set. The ACK/NACK feedback indicates that the UE gives feedback on whether it has successfully received (ACK, Acknowledgment) or failed reception (NACK, Non-Acknowledgment) for every MBS SPS resource allocated to it. This feedback typically means feedback transmitted through a Physical Uplink Control Channel (PUCCH) physical channel.

If the ACK/NACK feedback for the MBS SPS is set, in step 1630, the UE attempts to receive the downlink MBS SPS resource instructed for activation, and if the reception is successful depending on whether the reception is successful, the ACK is transmitted and received In case of failure, NACK may be transmitted. The UE may transmit this ACK/NACK feedback using the Uplink Control Information (UCI) format of the PUCCH physical channel. If the base station successfully receives this ACK/NACK feedback, the base station can know that the terminal has applied the activation of the MBS SPS.

If the ACK / NACK feedback for the MBS SPS is not configured, the terminal is set to a NACK-only feedback that transmits a NACK only when the MBS SPS resource is not successfully received, or the terminal does not transmit the feedback of the MBS SPS at all It may mean that it is set not to.

At this time, in step 1640, the terminal needs to receive the MBS SPS activation message and notify the base station that it has been applied. In step 1640, the terminal may transmit a confirmation message for the activation of the MBS SPS. The activation confirmation message of the MBS SPS may be transmitted in the MAC CE format. In another embodiment, the activation confirmation message of the MBS SPS may be in the form of Uplink Control Information (UCI) of a Physical Uplink Control Channel (PUCCH). In another embodiment, the MBS SPS activation confirmation message may be in the form of an RRC message.

If activation of the MBS SPS is simultaneously indicated in the configuration message of the MBS SPS as shown in FIG. 6 , the UE may not transmit the MBS SPS activation confirmation message. The activation confirmation message of the MBS SPS may include an identifier (Identity) of the MBS SPS to identify which MBS SPS activation is confirmed. Alternatively, the MBS SPS activation confirmation message may include a field corresponding to the configuration of the MBS SPS and indicate whether the terminal has received (or applied) the activation message of the corresponding MBS SPS. When the base station receives the MBS SPS activation confirmation message from the terminal, it may recognize that the MBS SPS has been successfully activated by the terminal. However, when the base station does not receive the MBS SPS activation confirmation message, the base station may recognize that the terminal fails to activate the corresponding MBS SPS, and may retransmit the MBS SPS activation message.

17 is a diagram illustrating operations of a base station and a terminal when MBS SPS is deactivated according to an embodiment of the present disclosure.

In step 1710, the MBS SPS may be deactivated. According to the embodiment of FIG. 17 , as described with reference to steps 440, 640, 770, and the like, deactivation of the MBS SPS may be instructed from the base station to the terminal. Deactivation of the MBS SPS may be indicated by using the PDCCH resource by the G-CS-RNTI. At this time, a New Data Indicator (NDI) value may be set to 0 to indicate deactivation of the MBS SPS. If this MBS SPS is being transmitted to multiple terminals and the base station wants to deactivate the reception of the MBS SPS to only one specific terminal, the deactivation of the MBS SPS can be used for one terminal other than the G-CS-RNTI. It may be indicated by using the PDCCH resource by the CS-RNTI. When the MBS SPS is deactivated, the MAC layer apparatus of the terminal and the base station may delete MBS SPS allocation information and HARQ information related thereto. The HARQ information may be at least one of HARQ process ID, MCS-related information, and TB size.

The base station may instruct the terminal to deactivate the MBS SPS, but if the terminal fails to decode the PDCCH and thus cannot deactivate the MBS SPS, the base station again instructs the deactivation of the MBS SPS or may have to change the configuration. However, if there is no feedback (response) of the terminal or the information transmitted by the feedback is limited, it is difficult for the base station to know whether the terminal has actually applied the deactivation of the MBS SPS. In order to prevent this, the terminal may perform an operation of notifying the base station that the deactivation of the MBS SPS has been applied. However, if the terminal is set to give feedback on the reception of the MBS SPS, the base station can know the MBS SPS deactivation of the terminal when the feedback of the terminal is sent.

When the MBS SPS is deactivated, in step 1720, the MAC layer device of the UE may check whether ACK/NACK feedback for the downlink MBS SPS for which deactivation is indicated is set. The ACK/NACK feedback indicates that the UE gives feedback on whether it has successfully received (ACK, Acknowledgment) or failed reception (NACK, Non-Acknowledgment) for every MBS SPS resource allocated to it. This feedback typically means feedback transmitted through a Physical Uplink Control Channel (PUCCH) physical channel.

If the ACK/NACK feedback for the MBS SPS is set, in step 1730, the UE may transmit an ACK message that is feedback indicating that the MBS SPS has been deactivated to the base station. The ACK message may use the ACK/NACK feedback format of the MBS SPS, and the UE may transmit the ACK message using the Uplink Control Information (UCI) format of the PUCCH physical channel. If the base station successfully receives this ACK feedback, the base station can know that the terminal has applied the deactivation of the MBS SPS.

If the ACK / NACK feedback for the MBS SPS is not set, the terminal is set to a NACK-only feedback that transmits a NACK only when the MBS SPS resource is not successfully received, or the terminal receives the feedback of the MBS SPS It may mean that it is set not to transmit at all.

At this time, in step 1740, the terminal may transmit a confirmation message for deactivation of the MBS SPS. The deactivation confirmation message of the MBS SPS may be transmitted in the MAC CE format. In another embodiment, the deactivation confirmation message of the MBS SPS may be in the form of Uplink Control Information (UCI) of a Physical Uplink Control Channel (PUCCH). In another embodiment, the MBS SPS deactivation confirmation message may be in the form of an RRC message. The deactivation confirmation message of the MBS SPS may include an identifier (Identity) of the MBS SPS to identify which MBS SPS deactivation is confirmed. Alternatively, the deactivation confirmation message of the MBS SPS may have a field corresponding to the configuration of the MBS SPS and indicate whether the terminal has received (or applied) the deactivation message of the corresponding MBS SPS.

When the base station receives the MBS SPS deactivation confirmation message from the terminal, the base station may recognize that the terminal has successfully deactivated the MBS SPS. However, when the base station does not receive the MBS SPS deactivation confirmation message, the base station may recognize that the terminal has failed to deactivate the corresponding MBS SPS and retransmit the MBS SPS deactivation message.

According to an embodiment, the terminal in the idle mode or the inactive mode may receive MBS SPS data in an activated state by setting the MBS SPS. When the terminal that was receiving the MBS SPS data receives an instruction to deactivate the corresponding MBS SPS from the base station, the terminal may transition to the connected mode. The terminal may transition to the connected mode, and may transmit to the base station a confirmation message indicating that the deactivation message of the MBS SPS has been received and applied. However, according to an embodiment, only when the terminal in the idle mode or inactive mode can no longer receive the MBS service of interest due to the deactivation of the corresponding MBS SPS, the terminal transitions to the connected mode and provides the MBS service of interest to the base station information can be transmitted. Thereafter, the base station may provide the MBS service again for the corresponding terminal.

In the embodiment of FIG. 17 , a confirmation message informing of deactivation of the MBS SPS may use the same format as the confirmation message informing of the activation of the MBS SPS described in FIG. 16 . In some embodiments, a single message format informing that the terminal has applied activation or deactivation of the MBS SPS (that the activation/deactivation instruction of the MBS SPS has been received) regardless of whether the MBS SPS is activated/deactivated may be used. have. In this case, the acknowledgment message has a zero-byte MAC CE format to minimize the size of the message, and transmitting the zero-byte MAC CE may mean that the indicated activation or deactivation is applied.

18 is a diagram illustrating a format of an activation or deactivation confirmation message of an MBS SPS according to an embodiment of the present disclosure.

In the embodiment of FIG. 18, a confirmation message of activation or deactivation of the MBS SPS is transmitted in the format of the MAC CE. This MBS SPS activation or deactivation confirmation message may be composed of a reserved (R, Reserved) field 1810 and an SPS index field 1820 for matching byte units (8 bits). When the terminal sends an activation or deactivation confirmation message of the MBS SPS to the base station, the reserved field may set a previously promised value of 0 or 1 and transmit it to the base station, and the SPS index field applies activation or deactivation of any MBS SPS It can be set as an identifier (Identity) that identifies whether or not In the embodiment of FIG. 18 , the identifier of the MBS SPS may use an SPS index value set in the MAC device. For example, when an MBS SPS having an index value of 1 in the MAC device of the MBS SPS is instructed to activate or deactivate, the MBS SPS confirmation message of FIG. 18 may set the SPS index value to 1 and transmit it to the base station. Upon receiving this message, the base station can know that the terminal has applied activation or deactivation of the MBS SPS having the SPS index value of 1.

19 is a diagram illustrating a format of an MBS SPS activation or deactivation confirmation message according to an embodiment of the present disclosure.

In the embodiment of FIG. 19 , a confirmation message of activation or deactivation of the MBS SPS is transmitted in the format of the MAC CE. This MBS SPS activation or deactivation confirmation message consists of a reserved (R, Reserved) field 1910, an A/D field 1920, and an SPS index field 1930 for aligning byte units (8 bits). can When the terminal sends an activation or deactivation confirmation message of the MBS SPS to the base station, the reserved field may transmit to the base station by setting a previously promised value of 0 or 1, and in the A/D field, the terminal applies the activation of the MBS SPS If it is done, a bit corresponding to A (Activation) is set, and if deactivation of MBS SPS is applied, a bit corresponding to D (Deactivation) can be set and transmitted. The SPS index field may be set as an identifier for identifying which MBS SPS activation or deactivation is applied. 19, the identifier of the MBS SPS may use the SPS index value set in the MAC device. For example, when an MBS SPS having an index value of 1 in the MAC device of the MBS SPS is instructed to activate or deactivate, the MBS SPS confirmation message of FIG. 19 may set the SPS index value to 1 and transmit it to the base station. Upon receiving this message, the base station can know that the terminal has applied activation or deactivation of the MBS SPS having the SPS index value of 1.

20 is a diagram illustrating a format of an activation or deactivation confirmation message of an MBS SPS according to an embodiment of the present disclosure.

In the embodiment of FIG. 20, a confirmation message of activation or deactivation of the MBS SPS is transmitted in the format of the MAC CE. This MBS SPS activation or deactivation confirmation message may consist of a cell ID field 2010 and an SPS index field 2020. When the UE sends an activation or deactivation confirmation message of the MBS SPS to the base station, the cell ID field may be set to the cell ID (Cell Index) of the MBS SPS to which the UE has applied activation or deactivation, and the SPS index field indicates the activation of any MBS SPS. Alternatively, it may be set as an identifier that identifies whether deactivation is applied. In the embodiment of FIG. 20, the identifier of the MBS SPS may use the SPS index value set in the BWP (Bandwidth Part), and in combination with the cell ID, it may be known which cell's MBS SPS is the MBS SPS set in the Active BWP. For example, when the MBS SPS having an index value of 1 in the BWP of the MBS SPS is instructed to activate or deactivate, the MBS SPS confirmation message of FIG. 20 may set the SPS index value to 1 and transmit it to the base station. In combination with the cell ID, the base station receiving this message can know that the MBS SPS having the SPS index value of 1 in the Active BWP of the cell ID indicated by the UE has been activated or deactivated.

21 is a diagram illustrating a format of an activation or deactivation confirmation message of an MBS SPS according to an embodiment of the present disclosure.

In the embodiment of FIG. 21 , a confirmation message of activation or deactivation of the MBS SPS is transmitted in the format of the MAC CE. This MBS SPS activation or deactivation confirmation message may have an SPSi (i is an integer greater than or equal to 0) field corresponding to each MBS SPS. In this case, i of SPSi may be an SPS index value of MBS SPS, and this SPS index may be an SPS index set in the MAC device. If the terminal transmits a confirmation message of the MBS SPS after being instructed to activate or deactivate a specific MBS SPS, if the format of FIG. 21 is used, the SPSi field value corresponding to the MBS SPS applied after being instructed to activate or deactivate the specific MBS SPS is set to 1 It can be set to and transmitted to the base station. The SPSi field for the MBS SPS not applied because the UE is not instructed to activate or deactivate the MBS SPS may be set to 0. In this way, the base station can know which MBS SPS is activated or deactivated.

Methods according to the embodiments described in the claims or specifications of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium are configured to be executable by one or more processors in an electronic device (device). One or more programs include instructions for causing an electronic device to execute methods according to embodiments described in a claim or specification of the present disclosure.

Such programs (software modules, software) include random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable ROM (EEPROM: Electrically Erasable Programmable Read Only Memory), magnetic disc storage device, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or any other form of It may be stored in an optical storage device or a magnetic cassette. Alternatively, it may be stored in a memory composed of a combination of some or all thereof. In addition, a plurality of each configuration memory may be included.

In addition, the program accesses through a communication network composed of a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. It may be stored in an attachable storage device that can be accessed. Such a storage device may be connected to a device implementing an embodiment of the present disclosure through an external port. In addition, a separate storage device on the communication network may be connected to the device implementing the embodiment of the present disclosure.

In the specific embodiments of the present disclosure described above, elements included in the disclosure are expressed in the singular or plural according to the specific embodiments presented. However, the singular or plural expression is appropriately selected for the context presented for convenience of description, and the present invention is not limited to the singular or plural element, and even if the element is expressed in plural, it is composed of the singular or singular. Even an expressed component may be composed of a plurality of components.

Meanwhile, although specific embodiments have been described in the detailed description of the present invention, various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments and should be defined by the claims described below as well as the claims and equivalents. For example, an embodiment of the present disclosure and parts of another embodiment may be combined to operate a base station and a terminal. In addition, the embodiments of the present disclosure are applicable to other communication systems, and other modifications based on the technical spirit of the embodiments may also be implemented.

Claims (1)

In the SPS operation method for MBS reception of the terminal,
Receiving a message instructing a Multicast and Broadcast Service (MBS) Semi-Persistent Scheduling (SPS) setup and activation from a base station;
storing resource allocation information and HARQ information for the MBS SPS in a MAC layer;
performing initialization or re-initialization of resources configured for the MBS SPS in the MAC layer; and
Comprising the step of transmitting a confirmation message for the activation setting of the MBS SPS to the base station, the method.

Images