Method and apparatus for mitigating MCCH monitoring in wireless communication system

Abstract

The present disclosure relates to a method by which a terminal mitigates MCCH monitoring in a non-terrestrial network. The terminal: receives, from a base station, a notification of a change in multicast and broadcast service control channel (MCCH) information transmitted through a MCCH; receives a system information block (SIB) from the base station, the SIB including ISA information about an intended service area (ISA) of a broadcast service of a multicast and broadcast service (MBS); determines, on the basis of location information of the terminal and the ISA information, whether the terminal is located within a specific ISA related to the changed MBS broadcast service; and monitors the MCCH if the terminal is located within the specific ISA.

Description

Method and device for mitigating MCCH monitoring in a wireless communication system

[0001] The present disclosure relates to a method for mitigating MCCH monitoring of a terminal in a wireless communication system.

[0002] Multicast and Broadcast Service (MBS) is an efficient communication method that allows a single piece of data to be transmitted simultaneously to many terminals (user equipment: UE). In general communication (Unicast), the base station must send data to each terminal individually, whereas in MBS, the base station can transmit the same data to multiple terminals. In MBS, the base station can broadcast data to all terminals within a cell or multicast it to terminals belonging to a specific group. In MBS, the MBS Control Channel (MCCH) is the channel through which control information that the terminal receiving the MBS must read is transmitted, and the MBS Traffic Channel (MTCH) is the channel through which data delivered to the terminal is transmitted. The terminal can receive data from the MTCH based on the control information from the MCCH.

[0003] Meanwhile, in the field of mobile communications, research on non-terrestrial networks (NTNs) that utilize platforms not located on the ground, such as satellites, high-altitude platforms (HAPs), or unmanned aerial systems (UASs), as wireless access nodes is actively underway. NTNs can provide wider coverage compared to terrestrial networks (TNs), making them advantageous for providing communication services or mitigating dead zones in areas such as maritime or aerial sections where it is difficult to install base stations (BSs).

[0004] Recently, there has been consideration to extend the aforementioned MBS to NTN. This enables the provision of broadcast services in maritime, aerial, and remote areas where ground base stations cannot reach. However, in NTN, for instance, the coverage of a beam transmitted by a single satellite can be very extensive; therefore, transmitting a service that needs to be provided only to a specific area across the entire beam coverage of the satellite can be inefficient. Taking this into account, the concept of an intended service area (ISA) has been introduced. An ISA can refer to the logical or geographical area that a specific MBS broadcast service must actually reach.

[0005] Meanwhile, when a change occurs in the MBS, the network notifies the terminal of this through an MBS change notification. However, in conventional technology, when a terminal receives an MBS change notification, there is an inefficiency in that the terminal must perform MCCH monitoring even if it is outside the ISA where the MBS of interest is provided.

[0006] This invention aims to provide a method for mitigating MCCH monitoring of a terminal in a wireless communication system.

[0007] A method for mitigating MCCH monitoring of a terminal in a wireless communication system is provided. According to the method, the terminal receives a change notification of MCCH information transmitted through a multicast and broadcast service control channel (MCCH) from a base station and receives a System Information Block (SIB) from the base station, wherein the SIB includes ISA information regarding an Intended Service Area (ISA) of a broadcast service of a Multicast and Broadcast Service (MBS), and the terminal determines whether the terminal is located within a specific ISA associated with the changed MBS broadcast service based on the terminal's location information and the ISA information, and if the terminal is located within the specific ISA, the terminal monitors the MCCH.

[0008] In another aspect, a device, a chipset, and a computer-readable storage medium are provided for executing the above method.

[0009] According to the prior art, a terminal that receives an MCCH change notification must acquire new MCCH information regardless of the terminal's location. However, according to the method proposed in this disclosure, the terminal can compare its location with ISA information and skip MCCH monitoring for service changes in areas unrelated to itself, thereby preventing unnecessary reception operations and maximizing the battery efficiency of the terminal.

[0010] In environments with very wide beam coverage, such as satellite communication, the terminal can selectively process only the information valid for it in relation to MBS. In other words, it can reduce the processing load of decoding and analyzing control messages that the terminal does not need to receive.

[0011] Since the terminal determines whether to monitor based on its location information and ISA information, even if the satellite beam is provided over a wide area, the terminal can focus only on MBS services specialized for the area where it is located.

[0012] The effects obtainable from the embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by those skilled in the art to which the technical configuration of the present disclosure applies from the description of the embodiments of the present disclosure below. That is, unintended effects resulting from implementing the configuration described in the present disclosure can also be derived by those skilled in the art from the embodiments of the present disclosure.

[0013] FIG. 1 shows the structure of a New Radio (NR) system according to one embodiment of the present disclosure.

[0014] FIG. 2 shows a functional split between NG-RAN and 5GC according to one embodiment of the present disclosure.

[0015] FIG. 3 shows a radio protocol architecture according to one embodiment of the present disclosure.

[0016] FIG. 4 shows the structure of a wireless frame according to one embodiment of the present disclosure.

[0017] FIG. 5 shows a slot structure of a frame according to one embodiment of the present disclosure.

[0018] FIG. 6 shows an example of a BWP according to one embodiment of the present disclosure.

[0019] FIG. 7 shows a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure.

[0020] Figure 8 shows an example of a non-terrestrial network scenario.

[0021] Figure 9 shows another example of a non-terrestrial network scenario.

[0022] Figure 10 illustrates a type of NTN platform.

[0023] Figure 11 illustrates the TA components in NTN.

[0024] FIG. 12 illustrates an earth fixed cell and an earth moving cell.

[0025] Figure 13 illustrates the introduction of scheduling offsets K_offset and K_mac in an NTN environment.

[0026] FIG. 14 shows an example of a common TA (timing advance) and a terminal-specific TA according to an embodiment of the present disclosure.

[0027] FIG. 15 shows an example of an orbital parameter orbital format according to one embodiment of the present disclosure.

[0028] Figure 16 illustrates linear polarization and circular polarization.

[0029] Figure 17 illustrates a lower link transmission and reception communication.

[0030] FIG. 18 illustrates an example of upper link transmission and reception communication.

[0031] FIG. 19 illustrates a method of operation of a terminal according to one embodiment of the present disclosure.

[0032] FIG. 20 illustrates a case where a terminal receives a notification of change in SIB27 and MCCH information.

[0033] FIG. 21 illustrates a method of operation of a base station according to one embodiment of the present disclosure.

[0034] FIG. 22 illustrates signaling and operation between a base station and a terminal according to one embodiment of the present disclosure.

[0035] FIG. 23 shows a communication system (1) according to one embodiment of the present disclosure.

[0036] FIG. 24 shows a wireless device according to one embodiment of the present disclosure.

[0037] FIG. 25 shows a signal processing circuit for a transmission signal according to one embodiment of the present disclosure.

[0038] FIG. 26 shows a wireless device according to one embodiment of the present disclosure.

[0039] FIG. 27 shows a portable device according to one embodiment of the present disclosure.

[0040] FIG. 28 shows a vehicle or an autonomous vehicle according to one embodiment of the present disclosure.

[0041] FIG. 29 shows a vehicle according to one embodiment of the present disclosure.

[0042] FIG. 30 shows an XR (extended reality) device according to one embodiment of the present disclosure.

[0043] FIG. 31 shows a robot according to one embodiment of the present disclosure.

[0044] FIG. 32 shows an Artificial Intelligence (AI) device according to one embodiment of the present disclosure.

[0045] In the present disclosure, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in the present disclosure, "A or B" may be interpreted as "A and / or B." For example, in the present disclosure, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0046] A slash ( / ) or a comma used in the present disclosure may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0047] In the present disclosure, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in the present disclosure, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0048] Additionally, in the present disclosure, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Additionally, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0049] Additionally, parentheses used in the present disclosure may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, the "control information" of the present disclosure is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)," "PDCCH" may be proposed as an example of "control information."

[0050] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.

[0051] Technical features described individually within one drawing in this disclosure may be implemented individually or simultaneously.

[0052] In the present disclosure, a higher layer parameter may be a parameter that is set for the terminal, pre-set, or pre-defined. For example, a base station or a network may transmit the higher layer parameter to the terminal. For example, the higher layer parameter may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0053] In the present disclosure, "configured or defined" may be interpreted as being configured or pre-configured to a device through pre-defined signaling from a base station or network (e.g., SIB, MAC, RRC, DCI (downlink control information), etc.). In the present disclosure, "configured or defined" may be interpreted as being configured or pre-configured to a device through pre-defined signaling from another device (e.g., MAC, RRC, SCI (sidelink control information), control information signaled between devices, etc.). In the present disclosure, "configured or defined" may be interpreted as being pre-configured to a device.

[0054] In the present disclosure, user equipment (UE) may refer to a device, a portable device, a wireless device, etc. In the present disclosure, a base station (BS) may refer to a radio access network (RAN) node, a non-terrestrial network (NTN) cell / node, a transmission reception point (TRP), a network, an integrated access and backhaul (IAB) node, a device, a portable device, a wireless device, etc.

[0055] The technology proposed in this disclosure can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (institute of electrical and electronics engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

[0056] The technology proposed in this disclosure can be implemented as 6G wireless technology and can be applied to various 6G systems. For example, 6G systems may have key factors such as eMBB (enhanced mobile broadband), URLLC (ultra-reliable low latency communications), mMTC (massive machine-type communication), AI (artificial intelligence) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0057] FIG. 1 shows the structure of a New Radio (NR) system according to one embodiment of the present disclosure. The embodiment of FIG. 1 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0058] Referring to FIG. 1, the NG-RAN (Next Generation-Radio Access Network) may include one or more base stations (20) that provide protocol termination for the user plane and control plane to the terminal (10). The base stations (20) may include, for example, a gNB (next generation-Node B) and / or an eNB (evolved-Node B). The terminal (10) may be fixed or mobile and may be referred to as an MS (Mobile Station), UT (User Terminal), SS (Subscriber Station), MT (Mobile Terminal), or wireless device. The base station (20) may be a fixed station communicating with the terminal (10) and may be referred to as a BTS (Base Transceiver System) or an access point.

[0059] In one embodiment, FIG. 1 illustrates a configuration including a gNB, but is not limited thereto. A plurality of base stations (20) may be connected to each other via an Xn interface. Additionally, base stations (20) may be connected to a 5th generation core network (5G Core Network; 5GC) via an NG interface. More specifically, base stations (20) may be connected to an access and mobility management function (AMF) (30) via an NG-C interface and to a user plane function (UPF) (30) via an NG-U interface.

[0060] FIG. 2 illustrates a functional partition between NG-RAN and 5GC according to one embodiment of the present disclosure. The embodiment of FIG. 2 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0061] Referring to FIG. 2, the base station of the NG-RAN can perform functions such as, for example, inter-cell radio resource management (Inter-Cell RRM), radio bearer control (RB control), connection mobility control, radio admission control, measurement configuration and provision, and dynamic resource allocation.

[0062] In addition, 5GC can, for example, have an access and mobility management function (AMF) that can perform functions such as NAS (Non-Access Stratum) security and idle state mobility handling, a user plane function (UPF) that can perform functions such as mobility anchoring and PDU (protocol data unit) processing, and a session management function (SMF) that can perform functions such as IP address allocation and PDU session control.

[0063] Meanwhile, the layers of the radio interface protocol between the terminal and the network can be classified into L1 (Layer 1), L2 (Layer 2), and L3 (Layer 3) based on the lower layers of the Open System Interconnection (OSI) reference model. For example, the physical layer corresponding to L1 can provide information transfer services using a physical channel. Additionally, the Radio Resource Control (RRC) layer corresponding to L3 can support control operations including the configuration, reconfiguration, and release of radio resources between the terminal and the network, and RRC messages can be exchanged between the terminal and the base station for this purpose.

[0064] FIG. 3 illustrates a radio protocol architecture according to one embodiment of the present disclosure. The embodiment of FIG. 3 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0065] The embodiment of FIG. 3 can be combined with various embodiments of the present disclosure. Specifically, FIG. 3(a) shows a wireless protocol structure for a user plane, and FIG. 3(b) shows a wireless protocol structure for a control plane. The user plane is a protocol stack for user data transmission, and the control plane is a protocol stack for control signal transmission. FIG. 3(c) shows a wireless protocol stack of the user plane for device-to-device communication, and FIG. 3(d) shows a wireless protocol stack of the control plane for device-to-device communication.

[0066] Referring to FIG. 3, the physical layer can provide information transmission services to the upper layer using a physical channel. The physical layer is connected to the upper layer, the MAC layer, through a transmission channel. Data can move between the MAC layer and the physical layer through the transmission channel. Transmission channels can be classified according to how and with what characteristics data is transmitted through a wireless interface.

[0067] Data can travel between different physical layers, namely between the physical layers of a transmitter and a receiver, through a physical channel. This physical channel can be modulated using Orthogonal Frequency Division Multiplexing (OFDM) and can utilize time and frequency as wireless resources.

[0068] The MAC layer can provide services to the upper layer, the RLC (radio link control) layer, through logical channels. The MAC layer can provide mapping functions from multiple logical channels to multiple transmission channels. Additionally, the MAC layer can provide logical channel multiplexing functions through mapping from multiple logical channels to a single transmission channel. The MAC sublayer can provide data transmission services over logical channels.

[0069] The RLC layer can perform concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs). To ensure the various Quality of Service (QoS) required by the Radio Bearer (RB), the RLC layer can provide three modes of operation: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC can provide error correction through automatic repeat requests (ARQ).

[0070] The RRC (Radio Resource Control) layer is defined only in the control plane. The RRC layer is responsible for controlling logical channels, transmission channels, and physical channels in relation to the configuration, reconfiguration, and release of wireless bearers. RB refers to a logical path provided by the first layer (physical layer) and the second layer (MAC layer, RLC layer, and PDCP (Packet Data Convergence Protocol) layer) for data transmission between a terminal and a network.

[0071] The functions of the PDCP layer in the user plane may include the delivery of user data, header compression, and ciphering. The functions of the PDCP layer in the control plane include the delivery of control plane data and encryption / integrity protection.

[0072] The SDAP (Service Data Adaptation Protocol) layer is defined only in the user plane. The SDAP layer can perform tasks such as mapping QoS flows between data wireless bearers and marking QoS flow identifiers (IDs) within downlink and uplink packets.

[0073] The establishment of an RB refers to the process of defining the characteristics of the wireless protocol layer and channel to provide specific services, and setting their respective specific parameters and operating methods. RBs can be further divided into two types: SRBs (Signaling Radio Bearers) and DRBs (Data Radio Bearers). SRBs are used as a channel for transmitting RRC messages in the control plane, while DRBs are used as a channel for transmitting user data in the user plane.

[0074] When an RRC connection is established between the RRC layer of the terminal and the RRC layer of the base station, the terminal is in the RRC_CONNECTED state; otherwise, it is in the RRC_IDLE state. For NR, the RRC_INACTIVE state is additionally defined, and a terminal in the RRC_INACTIVE state maintains a connection with the core network while being able to release the connection with the base station.

[0075] Downlink transmission channels for transmitting data from a network to a terminal include a Broadcast Channel (BCH) for transmitting system information and a Shared Channel (SCH) for transmitting user traffic or control messages. Traffic or control messages for downlink multicast or broadcast services may be transmitted via the Shared Channel (SCH) or via a separate Multicast Channel (MCH). Meanwhile, uplink transmission channels for transmitting data from a terminal to a network include a Random Access Channel (RACH) for transmitting initial control messages and a Shared Channel (SCH) for transmitting user traffic or control messages.

[0076] Logical channels that are above the transmission channel and mapped to the transmission channel include BCCH (Broadcast Control Channel), PCCH (Paging Control Channel), CCCH (Common Control Channel), MCCH (Multicast Control Channel), and MTCH (Multicast Traffic Channel).

[0077] A physical channel can be composed of multiple OFDM symbols in the time domain and multiple subcarriers in the frequency domain. A single subframe can be composed of multiple OFDM symbols in the time domain. A resource block is a resource allocation unit and can be composed of multiple OFDM symbols and multiple subcarriers. Additionally, each subframe may utilize specific subcarriers of specific OFDM symbols within that subframe for the Physical Downlink Control Channel (PDCCH), i.e., the L1 / L2 control channel. The Transmission Time Interval (TTI) is the unit time for subframe transmission.

[0078] FIG. 4 shows the structure of a wireless frame according to one embodiment of the present disclosure. The embodiment of FIG. 3 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0079] Referring to FIG. 4, radio frames may be used, for example, in uplink transmission, downlink transmission, and / or device-to-device transmission. For example, a radio frame may have a length of 10 ms and may be defined as two 5 ms half-frames (HF). For example, a half-frame may contain five 1 ms subframes (SF). For example, a subframe may be divided into one or more slots, and the number of slots within a subframe may be determined by the subcarrier spacing (SCS). For example, each slot may contain 12 or 14 OFDM(A) symbols according to the cyclic prefix (CP).

[0080] For example, when normal CP is used, each slot may contain 14 symbols. For example, when extended CP is used, each slot may contain 12 symbols. Here, for example, the symbols may include OFDM symbols (or CP-OFDM symbols) and SC-FDMA (single carrier-FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).

[0081] Table 1 below shows the number of symbols per slot (N) according to the SCS setting (u) when Normal CP or Extended CP is used. slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot ) exemplifies.

[0082] [Table 1]

[0083]

[0084] The following Table 2 illustrates the number of symbols per slot, the number of slots per frame, and the number of slots per subframe according to the SCS when an extended CP is used.

[0085] [Table 2]

[0086]

[0087] For example, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be configured differently among multiple cells merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., subframe, slot, or TTI (transmit time interval)) composed of the same number of symbols may be configured differently among the merged cells. For example, in the present disclosure, time resources such as subframes, slots, TTI, etc. may be referred to as time units.

[0088] For example, multiple numerologies or SCSs may be supported to support various services. For example, if the SCS is 15 kHz, a wide area in traditional cellular bands may be supported, and if the SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth may be supported. For example, if the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz may be supported to overcome phase noise.

[0089] The NR frequency band can be defined by two types of frequency ranges. The two types of frequency ranges may be FR1 and FR2. The numerical values ​​of the frequency ranges may change, for example, as shown in Table 3 below. Among the frequency ranges used in the NR system, FR1 may mean "sub 6GHz range" and FR2 may mean "above 6GHz range" and may be referred to as millimeter wave (mmW).

[0090] [Table 3]

[0091]

[0092] As described above, the numerical value of the frequency range of the NR system may change. For example, FR1 may include a band of 410 MHz to 7125 MHz as shown in Table 4 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, the frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, for example, for communication for vehicles (e.g., autonomous driving).

[0093] [Table 4]

[0094]

[0095] FIG. 5 shows a slot structure of a frame according to one embodiment of the present disclosure. The embodiment of FIG. 5 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0096] Referring to FIG. 5, for example, a slot may include multiple symbols in the time domain. For example, a carrier may include multiple subcarriers in the frequency domain. For example, a resource block (RB) may be defined as multiple consecutive subcarriers in the frequency domain. For example, a bandwidth part (BWP) may be defined as multiple consecutive (P)RBs ((physical) resource blocks) in the frequency domain and may correspond to a single numerology (e.g., SCS, CP length, etc.). For example, a carrier may include up to N BWPs (where N is a positive integer). For example, data communication may be performed through an active BWP. For example, each element may be referred to as a resource element (RE) in a resource grid and may be mapped to a single complex symbol.

[0097] Meanwhile, a wireless interface between terminals or a wireless interface between a terminal and a network may be composed of L1, L2, and L3 layers. In various embodiments of the present disclosure, L1 layer may refer to the physical layer. Additionally, for example, L2 layer may refer to at least one of the MAC layer, RLC layer, PDCP layer, and SDAP layer. Additionally, for example, L3 layer may refer to the RRC layer.

[0098] The Bandwidth Part (BWP) and Carrier are described below.

[0099] A BWP (Bandwidth Part) may be a continuous set of PRBs (physical resource blocks) in a given numerology. A PRB may be selected from a continuous subset of CRBs (common resource blocks) for a given numerology on a given carrier.

[0100] When Bandwidth Adaptation (BA) is used, the receiving bandwidth and transmitting bandwidth of the terminal may not need to be as large as the cell's bandwidth. In this case, the receiving bandwidth and transmitting bandwidth of the terminal can be adjusted. For example, the network (or base station) may notify the terminal of the bandwidth adjustment. For example, the terminal may receive information / settings for bandwidth adjustment from the network (or base station). In this case, the terminal may perform bandwidth adjustment based on the received information / settings. For example, the bandwidth adjustment may include reducing / expanding the bandwidth, changing the position of the bandwidth, or changing the subcarrier spacing of the bandwidth.

[0101] For example, bandwidth can be reduced during periods of low activity to save power. For example, the position of the bandwidth can be shifted in the frequency domain. For example, the position of the bandwidth can be shifted in the frequency domain to increase scheduling flexibility. For example, the subcarrier spacing of the bandwidth can be changed. For example, the subcarrier spacing of the bandwidth can be changed to allow different services. A subset of the total cell bandwidth of a cell can be referred to as a Bandwidth Part (BWP). BA can be performed by the network (or base station) setting the BWP for the terminal and by the network (or base station) notifying the terminal of the currently active BWP among the set BWPs.

[0102] For example, the BWP may be at least one of an active BWP, an initial BWP, and / or a default BWP. For example, the terminal may not monitor downlink radio link quality on DL BWPs other than the active DL BWP on the PCell (primary cell). For example, the terminal may not receive PDCCH, PDSCH, or CSI-RS (excluding RRM) outside of the active DL BWP. For example, the terminal may not trigger Channel State Information (CSI) reporting for inactive DL BWPs. For example, the terminal may not transmit Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH) outside of the active UL BWP. For example, in the case of a downlink, the initial BWP may be given as a successive set of RBs for the RMSI (remaining minimum system information) CORESET (control resource set) (set by the PBCH). For example, in the case of an uplink, the initial BWP may be given by the SIB (system information block) for random access procedures. For example, the default BWP may be set by the upper layer. For example, the initial value of the default BWP may be the initial DL BWP. To save power, if the terminal does not detect DCI (downlink control information) for a certain period, the terminal may switch the terminal's active BWP to the default BWP.

[0103] Meanwhile, a BWP can be defined for an SL (sidelink). The same SL BWP can be used for transmission and reception. For example, a transmitting terminal can transmit an SL channel or an SL signal over a specific BWP, and a receiving terminal can receive an SL channel or an SL signal over said specific BWP. In a licensed carrier, an SL BWP can be defined separately from a Uu BWP, and the SL BWP can have separate configuration signaling from the Uu BWP. For example, a terminal can receive a configuration for an SL BWP from a network (or base station). An SL BWP can be configured for out-of-coverage NR V2X terminals and RRC_IDLE terminals within the carrier. For a terminal in RRC_CONNECTED mode, at least one SL BWP can be activated within the carrier.

[0104] FIG. 6 illustrates an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 5 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted. In the embodiment of FIG. 5, it is assumed that there are three BWPs.

[0105] Referring to FIG. 6, for example, a common resource block (CRB) may be a carrier resource block numbered from one end of the carrier band to the other, and a resource block numbered within each BWP may be a resource block. For example, point A may indicate a common reference point for a resource block grid.

[0106] For example, BWP is point A, offset from point A (N start BWP) and bandwidth (N size BWP It can be set by ). For example, point A may be an external reference point of the PRB of a carrier where the subcarrier 0 of all numerologies (e.g., all numerologies supported by the network in that carrier) are aligned. For example, offset may be the PRB interval between the lowest subcarrier in a given numerology and point A. For example, bandwidth may be the number of PRBs in a given numerology.

[0107] FIG. 7 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure. The embodiment of FIG. 7 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0108] As core implementation technologies for 6G systems, technologies such as artificial intelligence (AI), THz (Terahertz) communication, optical wireless technology, free space optical transmission (FSO) backhaul networks, large-scale MIMO (multiple input multiple output) technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) can be adopted.

[0109] - Artificial Intelligence: Introducing AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. For example, AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in M2M, machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in Brain-Computer Interfaces (BCI). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0110] - THz Communication: Data transmission rates can be increased by expanding bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced large-scale MIMO technology. THz waves, also known as sub-millimeter radiation, generally refer to a frequency band between 0.1 THz and 10 THz with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz-300 GHz band range (Sub-THz band) is considered the primary portion of the THz band for cellular communication. Adding the Sub-THz band to the mmWave band increases 6G cellular communication capacity. Among the defined THz bands, the 300 GHz-3 THz band is located in the far-infrared (IR) frequency band. Although the 300 GHz-3 THz band is part of the optical band, it lies at the boundary of the optical band and immediately following the RF band. Therefore, this 300 GHz-3 THz band exhibits similarities to RF. Key characteristics of THz communication include (i) widely available bandwidth to support very high data transmission rates, and (ii) high path loss occurring at high frequencies (highly directional antennas are indispensable). The narrow beam width generated by highly directional antennas reduces interference. The small wavelength of THz signals allows a much larger number of antenna elements to be integrated into devices and BSs operating in this band. This enables the use of advanced adaptive array technologies that can overcome range limitations.

[0111] - Large-scale MIMO technology

[0112] - Hologram beamforming (HBF)

[0113] - Optical wireless technology

[0114] - Free Space Optical Transmission Backhaul Network (FSO backhaul network)

[0115] - Quantum communication

[0116] - Cell-free communication

[0117] - Integration of wireless information and power transmission

[0118] - Integration of wireless communication and sensing

[0119] - Integrated access and backhaul network

[0120] - Big data analysis

[0121] - Reconfigurable intelligent metasurface

[0122] - Metaverse

[0123] - blockchain

[0124] - Advanced Air Mobility (AAM): AAM can be a broad concept encompassing Urban Air Mobility (UAM), Regional Air Mobility (RAM), and Uncrewed Aerial Systems (UAS). For example, AAM may include UAM, RAM, UAS, and UAVs (uncrewed aerial vehicles).

[0125] - Autonomous driving (self-driving): V2X (vehicle to everything), a core element of building autonomous driving infrastructure, refers to technologies that enable vehicles to communicate and share with various elements on the road to perform autonomous driving, such as wireless communication between vehicles (vehicle to vehicle, V2V) and between vehicles and infrastructure (vehicle to infrastructure, V2I).

[0126] - Non-terrestrial Network (NTN): An NTN may refer to a network or network segment that utilizes RF (radio frequency) resources mounted on a satellite (or UAS platform). The use of NTN services may be considered to secure wider coverage or to provide wireless communication services in locations where the installation of wireless communication base stations is difficult.

[0127] - Integrated Sensing and Communication (ISAC): Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (range), etc., of an object, thereby obtaining information about the characteristics of the environment and / or objects within the environment.

[0128] - Reconfigurable Intelligent Surface (RIS): An RIS can be used to manipulate and enhance signal propagation in a wireless communication environment. For example, an RIS can be composed of many small antennas or metasurfaces arranged on a surface, each of which can actively control the phase, amplitude, polarization, etc., of the reflected signal. For instance, an RIS can improve signal reception by controlling the path, phase, and / or strength of the propagating signal. For instance, power consumption can be very low because power is consumed only for controlling the phase and amplitude of the small antennas. For instance, since an RIS can be reconfigured to suit various environments, it can meet diverse communication requirements and operate effectively in dynamic network environments.

[0129] The following describes non-terrestrial network (NTN) communication.

[0130] A non-ground network may refer to a network or a segment of networks that uses radio frequency resources on a satellite or an unmanned aerial system platform (UAS platform).

[0131] A typical scenario of an NTN providing access to a terminal is illustrated in detail in FIGS. 8 and FIGS. 9.

[0132] FIGS. 8 and 9 illustrate non-terrestrial network scenarios. The embodiments of FIGS. 8 and 9 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0133] Figure 8 shows an example of a non-terrestrial network scenario.

[0134] Figure 8 can illustrate, for example, a non-terrestrial network scenario based on a transparent payload.

[0135] Figure 9 shows another example of a non-terrestrial network scenario.

[0136] Figure 9 illustrates, for example, a non-terrestrial network scenario based on a regenerative payload. For example, a non-terrestrial network may generally include the following elements.

[0137] - One or more satellite gateways connecting non-terrestrial networks to public data networks

[0138] - Feeder link or wireless link between the satellite gateway and the satellite (or UAS platform)

[0139] - Service link or wireless link between user equipment and satellite (or UAS platform)

[0140] - A satellite (or UAS platform) capable of implementing transparent or regenerated (including onboard processing) payloads. For example, the satellite (or UAS platform) can generate multiple beams across a given service area, typically defined by a line of sight. For example, the beam footprint may typically be elliptical. For example, the line of sight of the satellite (or UAS platform) may vary depending on the onboard antenna diagram and the minimum elevation angle. For example, for a transparent payload, radio frequency filtering, frequency conversion, and amplification may be performed. Thus, the repeating waveform signal in the payload may not be altered. For example, for a regenerated payload, radio frequency filtering, frequency conversion, and amplification, as well as demodulation / decoding, switching and / or routing, and coding / modulation may be performed. This can effectively be equivalent to equipping the satellite (or UAS platform) with all base station functions.

[0141] - Optionally, inter-satellite links (ISL) may exist. In this case, regenerative payloads on the satellite may be required. ISL can operate at RF frequencies or optical bands.

[0142] - User equipment can be serviced by a satellite (or UAS platform) within the target service area.

[0143] FIG. 10 illustrates a type of NTN platform. An embodiment of FIG. 10 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0144] Referring to FIG. 10, NTN platforms may include Low-Earth Orbit (LEO) satellites, Medium-Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites, UAS platforms (including HAPS), or High Elliptical Orbit (HEO) satellites, and characteristics according to the type of NTN platform can be exemplified as shown in Table 5 below.

[0145] [Table 5]

[0146]

[0147] For example, the LEO satellite may have a satellite speed of 7.56 km / s based on LEO-600. Also, the maximum radio delay may be 25.77 ms based on LEO-600.

[0148] For example, the maximum propagation delay of an MEO satellite can be 95.19ms based on MEO-1000.

[0149] For example, GEO satellites can have a satellite speed of 3.1 km / s (negligible) and a maximum propagation delay of 541.46 ms.

[0150] For example, GEO satellites and UAS can be used to provide continental / regional / local services. Additionally, LEO and MEO satellite constellations can be used to provide services in both the Northern and Southern hemispheres, and in some cases, to provide global coverage including polar regions. This may require appropriate orbit inclination, sufficient beams generated, and inter-satellite links.

[0151] Below, NTN reference scenarios are described.

[0152] For example, NTNs that provide access to terminals can be considered in the following six standard scenarios.

[0153] i) Circular orbiting and notional station keeping platforms

[0154] ii) Highest RTD constraint

[0155] iii) Highest Doppler constraint

[0156] iv) Transparent Payload and Replay Payload

[0157] v) Cases with and without ISL (if inter-satellite link is present, a playback payload may be required)

[0158] vi) Where a moving or fixed beam footprint is formed on the ground depending on fixed or steerable beams

[0159] Regarding the six scenarios mentioned above, non-terrestrial networks providing access to terminals can be classified into GEO-based and LEO-based reference scenarios, and each scenario may include transparent satellites and regenerative satellites. In the GEO-based scenario, Scenario A (transparent satellite-based) and Scenario B (regenerative satellite-based) may be considered, while in the LEO-based scenario, Scenarios C1 / C2 and D1 / D2 may be considered depending on the operation of steerable beams or beams moving with the satellite. Details regarding this are shown in Table 6 below.

[0160] [Table 6]

[0161]

[0162] Additionally, GEO can be exemplified as a notional station keeping orbit at an altitude of 35,786 km, and LEO as a circular orbit at an altitude of 600 km or 1,200 km; service links may include bands below 6 GHz (e.g., 2 GHz) and above 6 GHz (e.g., DL 20 GHz, UL 30 GHz); and maximum channel bandwidths may be exemplified as 30 MHz below 6 GHz and 1 GHz above 6 GHz. Furthermore, ISL may be considered as Yes or No only in LEO regeneration scenarios, and the minimum elevation angle may be exemplified as 10° for both service and feeder links; and the maximum beam footprint, maximum round-trip delay (RTD), differential delay, and Doppler characteristics may be set differently depending on GEO / LEO. Detailed parameters related to the above six scenarios are shown in Table 7 below.

[0163] [Table 7]

[0164]

[0165]

[0166]

[0167]

[0168] In Table 7, it is assumed that each satellite has the ability to steer the beam to fixed points on the ground using beamforming technology. This is applicable during the period corresponding to the satellite's visibility time. Additionally, the maximum delay variation within a beam (earth fixed user equipment) can be calculated based on the min elevation angle for both the gateway and the user terminal (UE). Furthermore, the maximum differential delay within a beam can be calculated based on the maximum beam footprint diameter at the nadir.

[0169] The speed of light used in the delay calculations of Table 7 is 299,792,458 m / s.

[0170] In Table 7, the maximum beam footprint size for GEO is based on current state of the art GEO High Throughput systems and assumes spot beams at the edge of coverage (low elevation).

[0171] In Table 7, the maximum differential delay at the cell level can be calculated by considering the beam-level differential delay for the largest beam size. This does not exclude the possibility that the cell may contain one or more beams when the beam size is small or medium. However, the cumulated differential delay of all beams within the cell does not exceed the maximum differential delay at the cell level in the table above.

[0172] Below, the reference point and uplink synchronization maintenance (Uplink timing advance (TA) and frequency synchronization) in NTN will be explained.

[0173] With regard to uplink timing advance (TA) and frequency synchronization maintenance, enhancements to ensure timing and frequency synchronization performance for UL transmission may be considered by taking into account larger cell coverage, longer round tip time (RTT), and high Doppler.

[0174] In this specification, timing advance (TA) may refer to a time correction value (or a corresponding indication value) for aligning the uplink transmission timing by advancing it to match the reception time expected by the base station (or satellite) when a terminal transmits an uplink signal or channel (e.g., PRACH, PUSCH, PUCCH, etc.). For example, TA may be set by reflecting the propagation delay between the terminal and the receiving point, and, if necessary, common delay components and differential delay components per terminal. By adjusting the uplink transmission timing based on TA, the terminal can achieve uplink timing alignment and base station reception timing matching among terminals within the same cell or same beam coverage. Additionally, in non-terrestrial network environments, the delay components to be included in TA may vary depending on the link configuration and reference point settings; therefore, TA may be determined or corrected by taking into account these differences in reference paths.

[0175] FIG. 11 illustrates a TA component in NTN. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiment may be omitted. In FIG. 11, for simplification, the TA offset N TA offset It was expressed by omitting it.

[0176] First, based on the payload characteristics of the NTN platform, it can be classified into transparent payloads and regenerative payloads. Since transparent payloads perform radio frequency filtering, frequency conversion, and amplification, the waveform signal of the transmitted payload remains unchanged. Because regenerative payloads perform not only radio frequency filtering, frequency conversion, and amplification but also demodulation / decoding, switching and / or routing, and coding / modulation, they can be considered as having all or part of the base station functions installed on the satellite.

[0177] Referring to Fig. 11, for TA in initial access and subsequent TA maintenance, the following solutions can be derived with examples of term definitions presented in Fig. 10.

[0178] Option 1: A method in which the terminal autonomously acquires TA using its own location (UE known location) and satellite ephemeris.

[0179] In Option 1, the TA value required for uplink transmission (UL transmission) including PRACH (physical random access channel) can be calculated by the terminal. Adjustment for this can be performed using a terminal-specific differential TA (UE-specific differential TA) or a full TA (composed of a terminal-specific differential TA and a common TA).

[0180] If full TA compensation is performed at the terminal side, UL timing alignment between UEs within the same beam / cell and DL and UL frame timing at the network side can be achieved. However, in the case of satellites with a transparent payload, the method of handling the influence introduced by the feeder link may be discussed further later. Additionally, if the feeder link influence is not compensated at the UE, the need for the network to manage the timing offset between the DL and UL frame timings may be additionally considered.

[0181] When using only UE-specific differential TA, additional indications for a single reference point per beam / cell may need to be signaled to the terminals to align UL timings between terminals within the same beam / cell coverage. Additionally, regardless of the satellite payload type, the network may need to manage timing offsets between DL / UL frame timings.

[0182] Option 2: A method of adjusting TA based on network indication.

[0183] In this method, the common TA refers to the common component of the propagation delay shared by all terminals within the same satellite beam / cell coverage area, and the network can broadcast this on a per-satellite beam / cell basis. The network can calculate the common TA by assuming at least one reference point per beam / cell.

[0184] To satisfy greater coverage of NTN, it may be derived to explicitly or implicitly extend the range of TA instruction values ​​in RAR. Additionally, the network may instruct the terminal to a timing drift rate to enable terminal-side TA adjustment.

[0185] For the common TA calculation in the two options above, a single reference point per beam can be considered as the baseline.

[0186] Regarding UL frequency compensation in LEO systems, the following solution can be derived by considering post-compensation of the common frequency offset per beam on the network side.

[0187] Option 1: The terminal can perform estimation and pre-compensation of the terminal-specific frequency offset, and can acquire the value using Downlink (DL) reference signals, terminal location, and satellite ephemeris.

[0188] Option 2: At least in the LEO system, the network can instruct the terminal to a frequency offset required for uplink frequency compensation (UL frequency compensation), and the network can detect uplink signals (UL signals), such as a preamble, to obtain the corresponding value.

[0189] If the network performs frequency offset compensation on the upstream and / or downstream, indication of compensated frequency offset values ​​may also be supported. However, indication of the Doppler drift rate may not be necessary.

[0190] Below, a more delay-tolerant retransmission mechanism is described.

[0191] Regarding delay-tolerant retransmission mechanisms, two major aspects were studied: i) disabling of HARQ in NR NTN and ii) HARQ optimization in NR-NTN.

[0192] While the HARQ Round Trip Time (HARQ RTT) in NR is in the order of a few milliseconds, propagation delays in NTN can be longer from a few milliseconds to hundreds of milliseconds depending on the satellite orbit, and consequently, the HARQ RTT in NTN can be longer.

[0193] i) Disable HARQ in NR NTN.

[0194] If uplink HARQ feedback (UL HARQ feedback) is disabled, a problem may occur where the terminal fails to receive MAC CE and RRC signaling, or the terminal fails to properly receive downlink packets (DL packets) for an extended period without the base station being aware of it.

[0195] As a solution to this, new UCI feedback was discussed to indicate HARQ disabling, report DL transmission disruption, or request DL scheduling changes via the DCI's new / re-interpreted field.

[0196] In addition, regarding the slot-aggregation or blind repetitions problem, greater than 8 slot-aggregation, time-interleaved slot aggregation, and new MCS tables were discussed.

[0197] ii) HARQ optimization in NR-NTN.

[0198] Solutions to avoid peak data rate degradation in NTN were discussed. One solution is to increase the number of HARQ processes to accommodate longer satellite round-trip delays to avoid stop-and-waits, while another solution is to disable uplink HARQ feedback and rely on RLC ARQ for reliability to avoid stop-and-waits.

[0199] The observations regarding the effect of the number of HARQ processes on performance are as follows.

[0200] Case 1) When 16 HARQ processes were simulated with a TDL-D suburban channel, elevation angle 30 degrees, RLC ARQ block error rate target 1%, and 32 / 64 / 128 / 256 HARQ processes with block error rate targets 1% and 10%, no throughput gain was observed with increasing number of HARQ processes compared to RLC layer re-transmission at round-trip time delay (RTT) {32, 64, 128, 256} ms.

[0201] Case 2) Simulation of 16 HARQ processes at an RLC ARQ block error rate target of 0.1% and 32 HARQ processes at block error rate targets of 1% and 10% on a TDL-D suburban channel with an elevation angle of 30 degrees showed that at RTT=32 ms, the 32 HARQ processes showed an average throughput gain of 10% compared to the 16 HARQ processes.

[0202] Case 3) As a result of simulations performed under similar conditions at RTT=32 ms, under the assumption of TDL-D (delay spread / K-factor obtained from a system channel model with a suburban scenario and elevation angle of 30 degrees), no gain was observed for 32 HARQ processes compared to 16, but gain was observed in other channels, and in particular, under the assumption of TDL-A (suburban, elevation angle of 30°), a maximum spectral efficiency gain of 12.5% ​​was achieved. In addition, significant gain was observed when the number of HARQ processes was increased in simulations considering (i) additional MCS offset, (ii) lower efficiency-based MCS table, and (iii) slot aggregation with different BLER targets.

[0203] In other cases, system-level simulations were provided under conditions of Earth orbit 1200 km (LEO=1200 km), resource utilization 20%, 16 and 32 HARQ processes, 15 and 20 UEs per cell, proportional fair scheduling, and no frequency re-use. The spectral efficiency gain for the 32 HARQ processes depended on the number of terminals, and an average gain of 12% was observed at the 50% percentile for 15 UEs per beam, but no gain was observed for 20 UEs per cell.

[0204] In addition, the following options may be considered.

[0205] Option 1: For HARQ processes with UL HARQ feedback disabled via RRC, keep 16 HARQ process IDs and rely on RLC ARQ.

[0206] Option 2: Consider greater than 16 HARQ process IDs with UL HARQ feedback enabled via RRC, and consider (a) UE capability if greater than 16 HARQ process IDs and (b) Keep 4-bit HARQ process ID field in DCI.

[0207] The following solutions can be considered to support more than 16 HARQ processes while maintaining a 4-bit HARQ process ID field in DCI.

[0208] i) Slot number based

[0209] ii) virtual process ID based with HARQ re-transmission timing restrictions

[0061]

[0210] iii) Reuse HARQ process ID within RTD (time window)

[0069]

[0211] iv) Re-interpretation of existing DCI fields using assistance information from higher layers

[0212] In addition, solutions where the HARQ process ID field is increased beyond 4 bits were also discussed.

[0213] The following options may be considered regarding HARQ enhancements for soft buffer management and stop-and-wait time reduction.

[0214] Option 1: Pre-active / pre-emptive HARQ to reduce stop-wait time

[0215] Option 2: Enabling / disabling of HARQ buffer usage configurable on a per UE and per HARQ process

[0216] Option 3: HARQ buffer status report from the UE

[0217] Discussions regarding the number of HARQ processes, including additional considerations such as HARQ feedback, HARQ buffer size, RLC feedback, and RLC ARQ buffer size, must be further conducted when specifications are developed.

[0218] Meanwhile, the use of NR non-terrestrial network or LTE non-terrestrial network services is being considered to secure wider coverage or to provide wireless communication services in locations where it is difficult to install wireless communication base stations. While existing terrestrial network (TN) services, such as NR and LTE services, provided services to terminals by installing base stations on the ground, NTN services refer to providing services to terminals by installing base stations in non-ground locations—such as artificial satellites (geostationary, low orbit, medium orbit, etc.), airplanes, unmanned airships, and drones—instead of installing them on the ground. Scenarios such as high-altitude platforms (HAPS) and air-to-ground (ATG) are also included. For NTN services, Frequency Division Duplex (FDD) is primarily considered, but Time Division Duplex (TDD) is not completely excluded. It is assumed that the terminal possesses GNSS capability.

[0219] FIG. 12 illustrates an earth fixed cell and an earth moving cell. An embodiment of FIG. 12 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0220] Referring to FIG. 12, depending on the cell type supported by the satellite, it can be classified into an earth fixed beam cell (a) of FIG. 12 and an earth moving cell (b) of FIG. 12. An earth fixed cell may mean that the cell is maintained permanently or for a specific service time within a specific surface location based on the satellite's beam steering function. An earth moving cell may mean that the cell within the surface continues to move by providing service with a fixed beam without using the satellite's beam steering function.

[0221] The frequency bands considered for NR NTN services are mainly the 2 GHz band (L-band: 1-2 GHz, S-band: 2-4 GHz) below 6 GHz, and the downlink 20 GHz and uplink 30 GHz bands (DL 20 GHz and UL 30 GHz) above 6 GHz (Ka-Band: 26.5~40 GHz). The NTN bands supported by Rel-17 may be i) S-band (n256): UL 1980-2010 MHz, DL 2170-2200 MHz ii) L-band (n255): UL 1626.5-1660.5 MHz, DL 1525-1559 MHz.

[0222] FIG. 13 illustrates the introduction of scheduling offsets K_offset and K_mac in an NTN environment. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0223] The maximum round trip-delay for each scenario is as shown in Table 7 above.

[0224] Referring to Table 7, it is necessary to effectively operate NTNs with very long round-trip time delays (RTT), and thus scheduling offsets K_offset and K_mac have been introduced.

[0225] Referring to FIG. 13, K_offset is an offset value representing the RTT of the uplink time synchronization reference point (RP), and represents the sum of the service link RTT and the common TA (if indicated). k_mac is an offset value representing the RTT between the RP and the gNB.

[0226] FIG. 14 illustrates an example of a common TA (timing advance) and a terminal-specific TA according to an embodiment of the present disclosure. The embodiment of FIG. 9 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0227] Referring to FIG. 14, a terminal-specific TA can be acquired to compensate for transmission delays on the service link, and a common TA can be acquired to compensate for transmission delays between the RP (reference point) and the satellite.

[0228] For example, in an NTN-based communication system, the terminal can calculate the TA based on the terminal's GNSS (global navigation satellite system) capabilities (e.g., terminal location) and orbit-related upper-layer parameters transmitted from the base station, and this is the terminal-specific TA (N UE TA,adjIt can be referred to as ). For example, if orbit-related upper-layer parameters are not received from the base station, the terminal-specific TA may be set to 0. For example, a TA obtained based on common TA parameters (e.g., TACommon, TACommonDrift, and / or TACommonDriftVariation), which are upper-layer parameters transmitted from the base station, is called the common TA(N common TA,adj It can be referred to as ). For example, if common TA parameters are not transmitted from the base station, the common TA can be set to 0. Accordingly, for example, in an NTN-based communication system, the total TA value (T TA ) is "(N TA + N TA,offset + N common TA,adj + N UE TA,adj )*T c It can be obtained as. For example, N TA,offset can refer to the TA offset value provided to the terminal per serving cell, and N TA can mean a value obtained based on the timing advance command.

[0229] For example, the terminal may receive satellite orbit information through system information and / or RRC signaling. For example, satellite orbit information may be implemented / supported in a position and velocity state vector orbit format and / or an orbital parameter orbit format. For example, the position and velocity state vector orbit format may be composed of less than 17 bytes (e.g., 132 bits). For example, the field size for position (x, y, z)(m) may be 78 bits, and the field size for velocity (vx, vy, vz)(m / s) may be 54 bits. For example, the orbital parameter orbit format may be composed of less than 21 bytes (e.g., 164 bits).

[0230] FIG. 15 illustrates an example of an orbital parameter orbital format according to one embodiment of the present disclosure. The embodiment of FIG. 15 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0231] Referring to Fig. 15, information related to the orbital parameter orbit format (e.g., ephemeral information) includes the semi-major axis "α" (e.g., 33 bits) [m], the eccentricity "e" (in an elliptical satellite orbit, 0 <e<1) (예, 20 비트), 근점 편각(argument of periapsis) "ω"(예, 28 비트) [rad], 승교점 경도(longitude of ascending node) "Ω" (예, 28 비트) [rad], (궤도) 경사(inclination) "i" (예, 27 비트) [rad], 및 / 또는 평균 근점 이각(mean anomaly) "M0" = 에포크 t0 [JD]에서 M(t0) (예, 28 비트) [rad] 중 적어도 어느 하나를 포함할 수 있다.

[0232] FIG. 16 illustrates linear polarization and circular polarization. An embodiment of FIG. 16 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0233] Referring to Fig. 16, linear polarization or circular polarization may be used as the polarization method for radio waves in satellite-based communication. Linear polarization is a polarization method in which the electric field vector vibrates in a constant direction, while circular polarization is a polarization method in which the electric field vector vibrates while rotating around the direction of propagation. Circular polarization can be classified into right-hand circular polarization (RHCP) or left-hand circular polarization (LHCP). In an NTN environment, since polarization matching can affect performance due to changes in the attitude of the satellite and terminal, changes in the propagation path, etc., the network may provide polarization type information applicable to the terminal as system information (SIB), and the terminal may perform transmission and reception operations based on the provided polarization type.

[0234] For example, in satellite-based communication, circular polarization is mainly used to increase the directivity of radio waves, and the satellite can provide the terminal with information on which polarization information is used through SIB signaling. In this case, the polarization types of the SIB signaling may include linear, RHCP (right-hand circular polarization), and LHCP (left-hand circular polarization).

[0235] FIG. 17 illustrates a downlink transmission and reception communication. An embodiment of FIG. 17 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0236] Referring to FIG. 17, the base station can schedule downlink transmissions such as frequency / time resources, a transport layer, a downlink precoder, an MCS, etc. (S1401). In particular, the base station can determine a beam for PDSCH transmission to a terminal through the scheduling operations.

[0237] The terminal can receive Downlink Control Information (DCI) from the base station on the PDCCH, that is, for downlink scheduling, i.e., scheduling information of the PDSCH (S1402). DCI format 1_0 or 1_1 may be used for downlink scheduling, and in particular, DCI format 1_1 may include the following information: DCI format identifier, Bandwidth part indicator, Frequency domain resource assignment, Time domain resource assignment, PRB bundling size indicator, Rate matching indicator, ZP CSI-RS trigger, Antenna port(s), Transmission configuration indication (TCI), SRS request, DMRS (Demodulation Reference Signal) sequence initialization.

[0238] In particular, the number of DMRS ports can be scheduled according to each state indicated in the antenna port(s) field, and SU (Single-user) / MU (Multi-user) transmission scheduling is also possible. Additionally, the TCI field can be composed of 3 bits, and the QCL for the DMRS can be dynamically indicated by indicating up to 8 TCI states according to the TCI field value.

[0239] The terminal can receive downlink data from the base station on the PDSCH (S1403). When the terminal detects a PDCCH containing DCI format 1_0 or 1_1, the terminal can decode the PDSCH according to instructions by the corresponding DCI.

[0240] Here, when the terminal receives a PDSCH scheduled by DCI format 1, the terminal may have a DMRS configuration type set by the upper layer parameter 'dmrs-Type', and the DMRS type may be used to receive the PDSCH. Additionally, the terminal may have a maximum number of front-loaded DMRA symbols for the PDSCH set by the upper layer parameter 'maxLength'.

[0241] For DMRS configuration type 1, if a terminal is scheduled with a single codeword and an antenna port mapped to an index of {2, 9, 10, 11, or 30} is assigned, or if a terminal is scheduled with two codewords, the terminal may assume that all remaining orthogonal antenna ports are not associated with PDSCH transmission to another terminal. Or, for DMRS configuration type 2, if a terminal is scheduled with a single codeword and an antenna port mapped to an index of {2, 10, or 23} is assigned, or if a terminal is scheduled with two codewords, the terminal may assume that all remaining orthogonal antenna ports are not associated with PDSCH transmission to another terminal.

[0242] When a terminal receives a PDSCH, the terminal may assume a precoding granularity P' as a consecutive resource block in the frequency domain, and P' may correspond to one of the values ​​{2, 4, broadband}. If P' is determined to be broadband, the terminal may assume that the same precoding is applied to the allocated resources, without expecting to be scheduled into non-contiguous PRBs. On the other hand, if P' is determined to be either {2, 4}, a Precoding Resource Block Group (PRG) may be divided into P' consecutive PRBs. The actual number of consecutive PRBs within each PRG may be one or more, and the terminal may assume that the same precoding is applied to consecutive downlink PRBs within the PRG.

[0243] In addition, to determine the modulation order, target code rate, and transport block size within the PDSCH, the terminal can first read the 5-bit MCD field within the DCI to determine the modulation order and target code rate. Subsequently, the terminal can read the redundancy version field within the DCI to determine the redundancy version. Then, the terminal can determine the transport block size using the number of layers and the total number of allocated PRBs before rate matching.

[0244] FIG. 18 illustrates an overhead link transmission and reception communication. An embodiment of FIG. 18 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiment may be omitted.

[0245] Referring to FIG. 18, the base station can schedule uplink transmissions such as frequency / time resources, a transport layer, an uplink precoder, an MCS, etc. (S1501). In particular, the base station can determine a beam for PUSCH transmission for the terminal through the scheduling operations.

[0246] The terminal can receive a DCI on the PDCCH that includes scheduling information for uplink scheduling, i.e., PUSCH, from the base station (S1502). DCI format 0_0 or 0_1 may be used for uplink scheduling, in particular DCI format 0_1 ​​may include the following information: DCI format identifier, UL / SUL (Supplementary uplink) indicator, Bandwidth part indicator, Frequency domain resource assignment, Time domain resource assignment, Frequency hopping flag, Modulation and coding scheme (MCS), SRS resource indicator (SRI), Precoding information and number of layers, Antenna port(s), SRS request, DMRS sequence initialization, UL-SCH (Uplink Shared Channel) indicator.

[0247] For example, the 'SRS resource indicator' field may indicate SRS resources configured within the SRS resource set associated with the parent parameter 'usage'. Additionally, 'spatialRelationInfo' can be configured for each SRS resource, and its value can be one of {CRI, SSB, SRI}.

[0248] The terminal can transmit uplink data to the base station over the PUSCH (S1503). When the terminal detects a PDCCH containing DCI format 0_0 or 0_1, the terminal can transmit the PUSCH according to instructions by the DCI.

[0249] For PUSCH transmission, two transmission methods can be supported: codebook-based transmission and non-codebook-based transmission.

[0250] (i) When the upper layer parameter 'txConfig' is set to 'codebook', the terminal can be configured for codebook-based transmission. Conversely, when the upper layer parameter 'txConfig' is set to 'nonCodebook', the terminal can be configured for non-codebook-based transmission. If the upper layer parameter 'txConfig' is not set, the terminal may not expect to be scheduled by DCI format 0_1. If PUSCH is scheduled by DCI format 0_0, the PUSCH transmission may be based on a single antenna port.

[0251] In the case of codebook-based transmission, PUSCH may be scheduled in DCI format 0_0, DCI format 0_1, or semi-statically. When PUSCH is scheduled in DCI format 0_1, the terminal may determine the PUSCH transmission precoder based on SRI, TPMI (Transmit Precoding Matrix Indicator), and transmission rank from the DCI, as indicated by the 'SRS resource indicator' field and the 'Precoding information and number of layers' field. TPMI may be used to indicate the precoder to be applied across the antenna port and may correspond to the SRS resource selected by SRI when multiple SRS resources are set. Alternatively, when a single SRS resource is set, TPMI may be used to indicate the precoder to be applied across the antenna port and may correspond to that single SRS resource. A transmission precoder may be selected from an uplink codebook having the same number of antenna ports as the upper layer parameter 'nrofSRS-Ports'. When the terminal is configured with the upper layer parameter 'txConfig' set to 'codebook', at least one SRS resource may be configured in the terminal. The SRI indicated in slot n may be associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS resource may precede the PDCCH (i.e., slot n) carrying the SRI.

[0252] (ii) For non-codebook based transmission, PUSCH may be scheduled in DCI format 0_0, DCI format 0_1, or semi-statically. When multiple SRS resources are configured, the terminal may determine the PUSCH precoder and transmission rank based on a broadband SRI, where the SRI may be given by the SRS resource indicator within the DCI or by the upper layer parameter 'srs-ResourceIndicator'. The terminal may use one or multiple SRS resources for SRS transmission, where the number of SRS resources may be configured for simultaneous transmission within the same RB based on UE capabilities. Only one SRS port may be configured per SRS resource. Only one SRS resource may be configured with the upper layer parameter 'usage' set to 'nonCodebook'. The maximum number of SRS resources that may be configured for non-codebook based uplink transmission may be 4. The SRI indicated in slot n can be associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS transmission can precede the PDCCH (i.e., slot n) carrying the SRI.

[0253] In an embodiment of the present disclosure, a half-duplex operation may include the following.

[0254] First, the HD terminal (HD-UE) may not be expected to detect a DCI format that schedules reception for a set of symbols and a DCI format that schedules transmission at any symbol of the set of symbols.

[0255] Additionally, if PDCCH reception by a terminal includes two PDCCH candidates, the end of the later of the two PDCCH candidates may be the end of the PDCCH reception.

[0256] In addition, the HD-UE may not simultaneously expect to detect a dedicated higher layer parameter for setting reception for the symbol set and a DCI format for scheduling transmission at any symbol of the symbol set.

[0257] For example, reception of PDCCH, PDSCH, CSI-RS, and DL PRS configured by a higher layer can be performed when a DCI format instructing PUSCH, PUCCH, PRACH, and SRS transmission for at least one symbol in the symbol set is not detected.

[0258] For example, in the relationship between PUCCH and PUSCH configured by the upper layer and CSI-RS and PDSCH indicated by the DCI format, from the last symbol of the PDCCH reception for the DCI format, T proc,2 If the first symbols of the UL transmission exist within the period, the terminal may not cancel the UL transmission, and in other cases, it may cancel the UL transmission.

[0259] In addition, regarding the relationship between the SRS configured by the upper layer and the CSI-RS and PDSCH indicated by the DCI format, the terminal [determines] T from the last symbol of the PDCCH reception for the DCI format proc,2 SRS transmission within this period may not be cancelled, and SRS transmission of the remaining symbols may be cancelled.

[0260] At this time, T proc,2 neun, d 2,1 Assuming =1, and assuming that μ corresponds to the smallest SCS configuration between (i) the SCS configuration of the PDCCH carrying the DCI format and (ii) the SCS configuration of the SRS, PUCCH, and PUSCH, it may be the PUSCH preparation time for the UE processing capability.

[0261] HD-UE may not expect to receive a Type-0 / 0A / 1 / 2-PDCCH CSS set configuration in a set of symbols and a dedicated higher layer parameter configuring transmission in the set of symbols at the same time.

[0262] In the relationship between PUSCH and PUCCH set by the upper layer and the presence of an SSB within the DL BWP indicated by ssb-PositionInBurst in SIB1 or in ServingCellConfigCommon or by NonCellDefiningSSB, the following may be included.

[0263] For example, if the TX-RX switching time period is not guaranteed before the next earliest SSB (Synchronization Signal Block), PUSCH and PUCCH may not be transmitted.

[0264] For example, if the RX-TX switching time period is not guaranteed after the previous latest SSB, PUSCH and PUCCH may not be transmitted.

[0265] In the relationship where the SRS set by the upper layer and the existence of an SSB within a DL BWP is indicated by ssb-PositionInBurst or NonCellDefiningSSB in SIB1 or ServingCellConfigCommon, the following may be included.

[0266] For example, the SRS of a symbol that is not located before the TX-RX transition time interval from the next earliest SSB may not be transmitted.

[0267] For example, the SRS of a symbol that is not located after the RX-TX transition time interval from the previous latest SSB may not be transmitted.

[0268] In the case where the existence of an SSB within a DL BWP is indicated by PDCCH order-based PRACH, PUSCH, and PUCCH, or by ssb-PositionInBurst or NonCellDefiningSSB in SIB1 or ServingCellConfigCommon, UL transmission may not be performed if any symbol of the symbol duration of the SSB overlaps with UL transmission.

[0269] In this case, in relation to the SRS and the case where the existence of an SSB in the DL BWP is indicated by ssb-PositionInBurst or NonCellDefiningSSB in SIB1 or ServingCellConfigCommon, the SRS may not be transmitted in the symbol interval of the SSB.

[0270] In the relationship where PRACH or MsgA PUSCH triggered by an upper layer, reception of PDCCH, PDSCH, CSI-RS and DL PRS, and the presence of an SSB within a DL BWP is indicated by ssb-PositionInBurst or NonCellDefiningSSB in SIB1 or ServingCellConfigCommon, the following may be included.

[0271] For example, if symbol intervals overlap, it may depend on the terminal implementation.

[0272] For example, if the TX-RX or RX-TX switching period is not guaranteed, it may be up to UE implementation.

[0273] In the following, a method and apparatus for mitigating MCCH monitoring of a terminal during MBS service in a wireless communication system (e.g., a non-terrestrial network) are described.

[0274] In conventional standards (e.g., 3GPP release 17), NR-based multicast and broadcast service (MBS) technology was introduced. MBS can be used, for example, for public safety, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, group communication, etc.

[0275] In the current standardization process (e.g., 3GPP Release 19), discussions are underway to extend MBS support to NTN. This enables the provision of broadcast services in maritime, aerial, and remote areas where ground base stations cannot reach. However, in NTN, for instance, the coverage of a beam transmitted by a single satellite can be very extensive; therefore, transmitting services that need to be provided only to specific regions across the entire beam coverage of the satellite can be inefficient. Considering this, the concept of an Intended Service Area (ISA) has been introduced. An ISA can refer to the logical or geographical area that a specific MBS broadcast service must actually reach.

[0276] In other words, the discussion involves introducing the concept of an Intended Service Area (ISA) to support MBS services only in specific regions via NTN. For instance, instead of indiscriminately providing MBS services across all NTN service areas, the aim is to enhance network efficiency by allocating wireless resources only to the areas where the service is required.

[0277] Since an ISA is a geographical area intended to provide MBS services, it offers a high degree of freedom in configuration. Therefore, one or more ISAs may be configured within an NTN cell, or ISAs may not be configured in all areas of the NTN cell.

[0278] ISA information may be provided through a new system information block (e.g., SIB27) rather than an existing system information block (SIB), and based on the ISA information, the terminal can identify which ISA it is located in or which ISA it is not included in.

[0279] According to an embodiment, the terminal can identify an ISA that supports a specific MBS service through an MCCH (MBS control channel) that provides MBS-related information.

[0280] Meanwhile, when a change occurs in the MBS, the network notifies the terminal of this through an MBS change notification. However, in conventional technology, when a terminal receives an MBS change notification, there is an inefficiency in that the terminal must perform MCCH monitoring even if it is outside the ISA where the MBS of interest is provided.

[0281] Specific methods for solving these problems are described below. First, an overview of the method according to the present disclosure is described, and a detailed method of operation is described in proposed methods #1 and #2.

[0282] Terminals that support NR NTN can know their location information. Therefore, after checking ISA information through the new SIB, they can determine which ISA area they are in or outside of all ISA areas.

[0283] If a terminal is within a specific ISA area, it can monitor the MCCH to check the MBS services supported by the ISA to which it belongs. If the terminal does not belong to any ISA area, it means that it cannot receive MBS services, so the MCCH is not monitored. By reducing unnecessary MCCH monitoring in this way, unnecessary power consumption by the terminal can be reduced.

[0284] [Proposed Method #1] When the network issues a new MBS service or MBS modification (hereinafter referred to as a notification of change in MCCH information), the terminal can first determine through the new SIB whether it is within a specific ISA area or outside of all ISA areas. Based on the result, whether the terminal monitors the MCCH can be determined. For example, if the terminal is within a specific ISA area, it monitors the MCCH, and if the terminal does not belong to any ISA area, it may not monitor the MCCH.

[0285] For example, when an MBS service is changed or added, the network can change or add information about the ISA that supports the changed or added MBS service to the new SIB's ISA list.

[0286] According to an embodiment, for example, the network may include information about the time when the ISA list of the new SIB is changed or added in the new MBS service or instruction for MBS change (notification of change of MCCH information) so that the terminal can check the changed or added ISA list.

[0287] And / or, for example, when determining whether to monitor MCCH based on instructions for a new MBS service or MBS change (notification of change in MCCH information), the terminal may expect that a new SIB containing the changed or added ISA list will be provided from the network within a predefined and / or configured and / or indicated time window from the time of receiving the instructions (notification of change in MCCH information).

[0288] [Proposed Method #2] Even if the terminal receives instructions for a new MBS service (notification of change in MCCH information) and realizes through the new SIB that it is within a specific ISA area, it may not perform MCCH monitoring if there is no MBS service of interest when checking the Service Announcement.

[0289] The above service announcement may be a NAS message that provides essential information enabling the terminal to discover and connect to the MBS service.

[0290] MCCH information (i.e., information contained in messages transmitted via MCCH) can be transmitted periodically within a transmission window using a configurable repetition period. MCCH transmissions (and associated radio resources and MCS) can be directed via a PDCCH addressed by MCCH-RNTI. PDCCH monitoring opportunities for MCCH transmissions can be determined based on the common search space directed by searchspaceMCCH.

[0291] If searchspaceMCCH, a parameter used to determine the PDCCH monitoring opportunity for MCCH transmission, is set to 0, the PDCCH monitoring opportunity for receiving MCCH messages within the MCCH transmission window may be the same as the PDCCH monitoring opportunity for SIB1. If searchspaceMCCH is set to a non-zero value, the PDCCH monitoring opportunity for MCCH messages may be determined based on the search space indicated by searchspaceMCCH.

[0292] PDCCH monitoring opportunities for MCCH messages that do not overlap with uplink (UL) symbols can be numbered sequentially from 1 within the MCCH transmission window.

[0293] For example, within an MCCH transmission window, the [x*N + K]th PDCCH monitoring opportunity may correspond to the Kth transmitted SSB. Here, x can be 0, 1, ..., X-1 and K can be 1, 2, ..., N, where N is the number of actual transmitted SSBs determined by SIB1's ssb-PositionsInBurst (a parameter indicating the time-domain positions of the transmitted SS block). X is equal to CEIL(number of PDCCH monitoring opportunities within the transmission window / N). The actual transmitted SSBs are numbered sequentially starting from 1 in ascending order of SSB index. The terminal may assume that a PDCCH for an MCCH message is transmitted at at least one PDCCH monitoring opportunity corresponding to each transmitted SSB within the MCCH transmission window. In this case, the selection of an SSB for receiving an MCCH message may depend on the terminal implementation.

[0294] A terminal may apply an MCCH information acquisition procedure to obtain MBS broadcast configuration information broadcast by the network. This procedure may be applied to MBS-enabled terminals that are interested in or currently receiving MBS broadcast services, for example, terminals in the RRC_IDLE (waiting) state, RRC_INACTIVE (inactive) state, or RRC_CONNECTED (connected) state having an active BWP that includes a common search space set by searchSpaceMCCH.

[0295] When a terminal becomes interested in receiving MBS broadcast services, it may apply the MCCH information acquisition procedure. A terminal interested in receiving MBS broadcast services may apply the MCCH information acquisition procedure when, for example, when entering a cell providing SIB20 (e.g., when turning on power, after moving to a cell, etc.), when receiving SIB20 of a secondary cell (SCell) through dedicated signaling, and when receiving a notification that MCCH information has changed due to the start of new MBS service(s).

[0296] FIG. 19 illustrates a method of operation of a terminal according to one embodiment of the present disclosure.

[0297] Referring to FIG. 19, the terminal receives a change notification of MCCH information transmitted from a base station via a multicast and broadcast service control channel (MCCH) (S191).

[0298] The base station can notify the terminal of instructions for a new MBS service or MBS modification through a notification of change in MCCH information.

[0299] For example, when a network changes (part of) the MCCH information, it can notify terminals of the change through a PDCCH that schedules the MCCH. This can be referred to as a notification of change of MCCH information (hereinafter simply referred to as a change notification).

[0300] According to an embodiment, the change notification may be transmitted, for example, with a 2-bit bitmap. If the most significant bit (MSB) of the 2-bit bitmap is set to '1', it indicates the start of a new MBS service(s), and if the least significant bit (LSB) of the 2-bit bitmap is set to '1', it may indicate a change in MCCH information other than the start of a new MBS service (e.g., a change in the setting of an ongoing MBS session, the termination of an MBS session, or a change in adjacent cell information).

[0301] According to an embodiment, the change notification may include time information regarding the time when an ISA list reflecting the MBS change is included in a SIB (SIB27 described below) containing ISA information.

[0302] After that, the terminal receives a System Information Block (SIB) from a base station, wherein the SIB includes ISA information for an Intended Service Area (ISA) of a Multicast and Broadcast Service (MBS) (and / or Multicast; hereinafter, for convenience, the broadcast service of MBS is described as the main example, but this does not exclude the multicast of MBS, the broadcast of MBS, and the multicast of MBS) (S192). The SIB may be SIB27.

[0303] According to an embodiment, the terminal may receive the SIB within a specific time window based on the time indicated by the time information. Alternatively, according to an embodiment, the terminal may receive the SIB within a specific time window starting from the time of receiving the change notification.

[0304] To explain the S192 process in more detail, the existing system information blocks are explained first, and then SIB27 is explained.

[0305] Configuration information required to receive MCCH may be provided in SIB1 and SIB20. Here, SIB1 includes information relevant to evaluating whether a terminal is allowed to connect to a specific cell and defines the scheduling of other system information (other SI). Additionally, it may include wireless resource configuration information applicable to all terminals and barring information applicable to integrated access control.

[0306] Specifically, SIB1 includes SI-SchedulingInfo, which contains information necessary to obtain system information (SI) messages. SI-SchedulingInfo includes schedulingInfoList, which contains at least one SchedulingInfo. SchedulingInfo may include at least one of i) si-BroadcastStatus, which indicates whether an SI message is broadcast; ii) si-Periodicity, which indicates the period of an SI message in units of wireless frames; iii) sib-MappingInfo, which indicates which SIBs are included in an SI message; and iv) si-WindowPosition, which indicates the SI window position of the related SI message.

[0307] SIB20 contains the information necessary to obtain the MCCH / MTCH settings for the MBS broadcast.

[0308] SIB27 can provide ISA information for the MBS broadcast service for the satellite network (NTN). In the aforementioned step S192, the SIB containing ISA information for the ISA of the MBS broadcast service may be, for example, the SIB27. SIB27 may have a period based on the si-Periodicity and may be transmitted periodically. The terminal may receive SIB27 after receiving the change notification (depending on the embodiment, the terminal may receive SIB27 before receiving the change notification. This will be described in detail later).

[0309] Table 8 illustrates SIB27. SIB27 includes the intended service area (ISA) information for the MBS broadcast service(s) provided in the NTN (non-terrestrial network) cell.

[0310] [Table 8]

[0311]

[0312] In Table 8, the intendedServiceAreaList includes a list of intended service areas (ISA) each associated with one or more MBS broadcast services (and / or multicast, hereinafter the same) provided by an NTN (non-terrestrial network, satellite communication) cell.

[0313] Such ISA lists may include information indicating at least one ISA that reflects a change in an MBS service (e.g., MBS broadcast service, MBS multicast, or MBS broadcast and multicast, hereinafter the same) in accordance with the change notification. For example, the SIB27 may include information (ISA list) about at least one ISA that supports the changed MBS broadcast service.

[0314] Based on the terminal's own location information and ISA information, the terminal determines whether the terminal is located within a specific ISA associated with a modified MBS broadcast service (S193). The modified MBS broadcast service may be an MBS service of interest to the terminal. Here, an MBS broadcast service is exemplified as the modified MBS service, but the modified MBS service may be an MBS multicast, or an MBS broadcast and multicast.

[0315] When the terminal is located within the specific ISA, the terminal monitors the MCCH (S194).

[0316] In conventional technology, upon receiving a notification of change in MCCH information, a terminal receiving or interested in receiving an MBS service transmitted via an MBS broadcast immediately performed MCCH monitoring to acquire new MCCH information starting from the same slot.

[0317] On the other hand, in the method according to the present disclosure, when a notification of change in MCCH information is received, the terminal determines whether it is within a specific ISA area or outside of all ISA areas through its location information and ISA information (e.g., ISA list) included in the SIB (e.g., the aforementioned SIB27) and decides whether to monitor the MCCH accordingly. For example, if the terminal is within a specific ISA area that provides the MBS service of interest to it, it monitors the MCCH, and if the terminal is located outside the said specific ISA area or does not belong to any ISA area, it does not monitor the MCCH. The fact that the terminal does not monitor the MCCH may also be expressed as "skip" the monitoring of the MCCH. For example, if the terminal does not belong to any of the ISAs indicated by the said ISA information, it may skip the monitoring of the MCCH.

[0318] According to the prior art, a terminal that receives an MCCH change notification must first acquire new MCCH information regardless of the terminal's location. However, according to the method proposed in this disclosure, the terminal can compare its location with ISA information and skip MCCH monitoring for service changes in areas unrelated to itself, thereby preventing unnecessary reception operations and maximizing the battery efficiency of the terminal, which is an advantageous effect.

[0319] Furthermore, according to the method proposed in this disclosure, in an environment with very wide beam coverage, such as satellite communication, the terminal can selectively process only the information valid for itself in relation to MBS. In other words, there is an advantageous effect of reducing the processing load of decoding and analyzing control messages that the terminal does not need to receive.

[0320] In addition, according to the method proposed in the present disclosure, since the terminal determines whether to monitor based on its location information and ISA information, even if the satellite beam is provided to a wide area, the terminal has the advantageous effect of being able to focus only on the MBS service specialized for the area where it is located.

[0321] According to an embodiment, as described in Proposed Method #2, the terminal may further receive a Non Access Stratum (NAS) message containing information for accessing a specific MBS service. In this case, the terminal may monitor the MCCH if it is located within the specific ISA and is interested in the specific MBS service. In other words, even if the terminal is located within the specific ISA, it may skip MCCH monitoring if it is not interested in the specific MBS service.

[0322] The terminal can receive the above change notification and the above SIB from a base station included in a Non-Terrestrial Network (NTN).

[0323] Meanwhile, although not illustrated in FIG. 19, the terminal may also perform an MBS Interest Indication procedure.

[0324] The MBS interest notification procedure may be for a terminal in the RRC_CONNECTED state to notify the network that it is receiving or is interested in receiving MBS broadcast service(s), and / or to notify the network of the priority of MBS broadcasts over unicast and multicast MRB reception.

[0325] A terminal may acquire an MBS broadcast only if it can acquire it without interrupting the reception of unicast, small data transmission (SDT), or MBS multicast data. For example, since individual communications (unicast) or already subscribed MBS multicasts may be more important to the terminal, the reception of an MBS broadcast may be performed without interfering with these existing communications.

[0326] MBS broadcast configuration information can be provided on the MCCH logical channel. The MCCH can carry an MBSBroadcastConfiguration message representing the MBS broadcast sessions provided by the cell and related scheduling information for those sessions.

[0327] According to an embodiment, the MBSBroadcastConfiguration message may include a list of adjacent cells that provide the same broadcast MBS service(s) as provided by the current cell.

[0328] FIG. 20 illustrates a case where a terminal receives a notification of change in SIB27 and MCCH information.

[0329] Referring to FIG. 20, SIB27 may be transmitted periodically with a specific period. Then, the terminal may receive an MCCH information change notification (which may also be referred to as an MBS modification indication) from the base station. In this case, SIB27 (2001) transmitted before the MCCH information change notification may include ISA list #A, and SIB27 (2002) transmitted after the MCCH information change notification may include ISA list #B. In this case, ISA list #B may include information indicating at least one ISA that reflects the change in the MBS service according to the MCCH information change notification.

[0330] The terminal does not perform MCCH monitoring immediately after receiving the above MCCH information change notification, but first receives SIB27 (2002) to determine whether the terminal is within a specific ISA area that provides the MBS service that the terminal is interested in, and then performs or skips MCCH monitoring accordingly.

[0331] According to an embodiment, the notification of change in MCCH information may include information indicating a specific region / area (ISA) where an MBS change has occurred, or information indicating whether an MBS change has occurred for each region / area (ISA). Hereinafter, the information indicating a specific region / area (ISA) where an MBS change has occurred or information indicating whether an MBS change has occurred for each region / area (ISA) may be abbreviated as identification information.

[0332] In other words, the change notification of the MCCH information may further include identification information for identifying at least one specific ISA in which an MBS change has occurred within the ISA list included in the ISA information of SIB27.

[0333] If the terminal is located within the at least one specific ISA indicated by the identification information, it monitors the MCCH, and otherwise, it skips MCCH monitoring.

[0334] For example, the identification information may include index information indicating the ISA in which an MBS change occurred within the ISA list.

[0335] According to an embodiment, the identification information includes bitmap information of m bits (m is a natural number) corresponding to the size of the ISA list, wherein each bit of the bitmap may indicate whether an MBS change has occurred in the corresponding ISA.

[0336] The following explains this in more detail.

[0337] For example, after receiving an ISA list through SIB27, the terminal may receive a notification of change in MCCH information that includes information indicating a specific area / region (ISA) where an MBS change has occurred, or information indicating whether an MBS change has occurred per area / region (ISA) (the aforementioned identification information). For example, if an MBS change has occurred in the nth ISA within the ISA list provided by SIB27, the notification of change in MCCH information may include information indicating the nth ISA.

[0338] If the change notification of MCCH information includes information (identification information) indicating whether MBS changes for each of the above-mentioned regions / regions (ISA), said identification information may be configured in the form of a bitmap. For example, if the size of the above-mentioned ISA list (or the number of ISAs included in the ISA list) is m, then each bit of a bitmap composed of m bits can indicate whether a change has occurred (or is occurring) for each ISA. As an example, in a bitmap composed of m bits, if the n-th bit is 1, it may indicate that an MBS change has occurred in the n-th ISA of the above-mentioned ISA list, and if the n-th bit is 0, it may indicate that an MBS change has not occurred in the n-th ISA of the above-mentioned ISA list (of course, an example is also possible where if the n-th bit is 1, it indicates that an MBS change has not occurred in the n-th ISA of the above-mentioned ISA list, and if the n-th bit is 0, it indicates that an MBS change has occurred in the n-th ISA of the above-mentioned ISA list).

[0339] In this case, since the terminal already has the above ISA list, it can identify the area / region (ISA) where the change occurred solely through the MCCH information change notification and determine whether the terminal itself is included in the said area / region (ISA). If the terminal belongs to the said area / region (ISA), it performs an MCCH reception operation to identify the relevant MBS change information, and if not, it skips the MCCH reception operation.

[0340] In summary, after the terminal receives an ISA list through SIB27, the network may provide the terminal with information on the area where the MBS change occurred (or information on whether the MBS change occurred by area) through a predefined first signaling (e.g., a notification of change in MCCH information (which may also be referred to as an MBS change notification)). If the terminal that receives the first signaling belongs to the area where the MBS change occurred (e.g., can determine whether it is included in a specific ISA based on the terminal's location information and the ISA list), it performs a reception operation of a predefined second signaling (e.g., MCCH) to identify the relevant MBS change information; otherwise, it skips the reception operation of the second signaling.

[0341] According to an embodiment, after receiving a notification of change in MCCH information that includes information indicating a specific area / region (ISA) where an MBS change has occurred or information indicating whether an MBS change has occurred per area / region (ISA) (identification information), the terminal may receive an ISA list through SIB27. In this case, for example, if the notification of change in MCCH information includes information indicating the nth ISA, this may mean that an MBS change has occurred (or occurred) in the nth ISA within the ISA list provided by SIB27.

[0342] In summary, the network provides the terminal with information on the area where an MBS change occurs (or information on whether an MBS change occurs by area) through a predefined first signaling (e.g., a notification of change in MCCH information (which may also be referred to as an MBS change notification)). Upon receiving the first signaling, the terminal determines whether it belongs to the area where the MBS change occurs based on the ISA list provided in the terminal's location information and system information (e.g., SIB27). If it belongs to the area, it performs a reception operation of a predefined second signaling (e.g., MCCH) to identify the relevant MBS change information; otherwise, it omits the reception operation of the second signaling.

[0343] As such, the method according to the present disclosure may be applied in cases where an MCCH information change notification is received after receiving a SIB27 containing an ISA list according to an embodiment, or in cases where an SIB27 containing an ISA list is received after receiving an MCCH information change notification. In other words, it is not necessarily limited to the signaling sequence / method of FIG. 20 and may be applied in various ways. In the signaling sequence / method of FIG. 20, the identification information included in the MCCH information change notification may be applied to at least one of SIB27 (2001) and SIB27 (2002), and specifically which one is applied to may be determined in advance or set / instructed by the network (base station). According to an embodiment, the method according to the present disclosure may be applied with only the reception of SIB27 (2001) and the reception of the MCCH information change notification, or the method according to the present disclosure may be applied with only the reception of the MCCH information change notification and the reception of SIB27 (2002).

[0344] FIG. 21 illustrates a method of operation of a base station according to one embodiment of the present disclosure.

[0345] Referring to FIG. 21, the base station transmits a change notification of MCCH information transmitted via MCCH to the terminal (S211). For example, such a change notification may be transmitted via a PDCCH that schedules MCCH.

[0346] After that, the base station transmits a system information block (e.g., the aforementioned SIB27) containing ISA information for the Intended Service Area (ISA) of the broadcast service of the MBS (S212). This SIB can be transmitted, for example, via PDSCH.

[0347] Subsequent terminal operations based on a system information block containing MCCH information change notifications and ISA information have been described above with reference to FIG. 19.

[0348] FIG. 22 illustrates signaling and operation between a base station and a terminal according to one embodiment of the present disclosure.

[0349] Referring to FIG. 22, the base station transmits a notification to the terminal regarding a change in MCCH information transmitted via MCCH (S221).

[0350] The base station transmits to the terminal a SIB (e.g., SIB27) containing ISA information for the intended service area (ISA) of the broadcast service of the MBS (S222).

[0351] Based on the terminal's location information and the ISA information, the terminal determines whether the terminal is located within a specific ISA associated with a changed MBS broadcast service (S223). The changed MBS broadcast service may be an MBS service associated with an MBS service added or modified according to the change notification and may be an MBS service that the terminal is interested in.

[0352] The base station transmits the MCCH to the terminal (S224), and the terminal monitors the MCCH when it is located within the specific ISA (S225). If the terminal is located outside the specific ISA or is not included in all ISAs based on the ISA information, it skips monitoring the MCCH.

[0353] FIG. 23 shows a communication system (1) according to one embodiment of the present disclosure. The embodiment of FIG. 23 can be combined with various embodiments of the present disclosure.

[0354] Referring to FIG. 23, a communication system (1) to which various embodiments of the present disclosure are applied includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Thing) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with wireless communication functions, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone) and / or an Aerial Vehicle (AV) (e.g., Advanced Air Mobility). The XR device includes an Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. The portable device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch, smart glasses), a computer (e.g., a laptop, etc.). The home appliance may include a TV, a refrigerator, a washing machine, etc. The IoT device may include a sensor, a smart meter, etc. For example, a base station and a network may be implemented as a wireless device, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.

[0355] Here, the wireless communication technology implemented in the wireless devices (100a to 100f) of this specification may include LTE, NR, and 6G, as well as Narrowband Internet of Things for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless devices (100a to 100f) of this specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless devices (100a to 100f) of this specification may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0356] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). Artificial Intelligence (AI) technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) through the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0357] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base station (200) and base station (200) / base station (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and inter-base station communication (150c) (e.g., relay, IAB (Integrated Access Backhaul)). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various proposals of the present disclosure, at least some of the following may be performed: various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc.

[0358] FIG. 24 shows a wireless device according to one embodiment of the present disclosure. The embodiment of FIG. 24 may be combined with various embodiments of the present disclosure.

[0359] Referring to FIG. 24, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} may correspond to {wireless device (100x), base station (200)} and / or {wireless device (100x), wireless device (100x)} of FIG. 23.

[0360] The first wireless device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memory (104) and / or transceivers (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts of operation disclosed in this document. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and then store information obtained from the signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals through one or more antennas (108). The transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be combined with an RF (Radio Frequency) unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0361] The first wireless device (100) may be a terminal and includes at least one transceiver (106), at least one memory (104), and at least one processor (102) operably coupled with the at least one memory (104) and the at least one transceiver (106). The at least one memory (104) includes instructions that are executed by the at least one processor (102) to cause the at least one processor (102) to perform operations, wherein the operations include receiving a change notification of MCCH information transmitted from a base station through a multicast and broadcast service control channel (MCCH) and receiving a System Information Block (SIB) from the base station, wherein the SIB includes ISA information regarding an Intended Service Area (ISA) of a broadcast service of a Multicast and Broadcast Service (MBS), and, based on the location information of the terminal and the ISA information, determining whether the terminal is located within a specific ISA associated with the changed MBS broadcast service, and if the terminal is located within the specific ISA, monitoring the MCCH.

[0362] The second wireless device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or transceivers (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). Memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with an RF unit. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0363] The second wireless device (200) may be a base station and includes at least one transceiver (206), at least one memory (204), and at least one processor (202) operably coupled with the at least one memory (204) and the at least one transceiver (206). The at least one memory (204) includes instructions that are executed by the at least one processor (202) to cause the at least one processor (202) to perform operations, wherein the operations include transmitting a change notification of MCCH information transmitted to a terminal via MCCH and transmitting a system information block (e.g., the aforementioned SIB27) containing ISA information for the Intended Service Area (ISA) of the broadcast service of the MBS.

[0364] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document.

[0365] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be contained in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0366] One or more processors (102, 202) may be implemented as at least one computer-readable medium (CRM) containing instructions based on being executed by at least one processor.

[0367] For example, at least one computer-readable medium (CRM) containing instructions that perform operations based on execution by at least one processor receives a notification of change in MCCH information transmitted via MCCH from a base station and receives a system information block (SIB) from the base station, wherein the SIB includes ISA information regarding an intended service area (ISA) of a broadcast service of MBS, and based on the location information of the terminal and the ISA information, determines whether the terminal is located within a specific ISA associated with the changed MBS broadcast service and, if it is located within the specific ISA, performs an operation of monitoring the MCCH.

[0368] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0369] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of this document to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc., disclosed in this document from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document through one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

[0370] FIG. 25 shows a signal processing circuit for a transmission signal according to one embodiment of the present disclosure. The embodiment of FIG. 25 can be combined with various embodiments of the present disclosure.

[0371] Referring to FIG. 25, the signal processing circuit (1000) may include a scrambler (1010), a modulator (1020), a layer mapper (1030), a precoder (1040), a resource mapper (1050), and a signal generator (1060). Although not limited thereto, the operation / function of FIG. 25 may be performed in the processor (102, 202) and / or transceiver (106, 206) of FIG. 24. The hardware elements of FIG. 25 may be implemented in the processor (102, 202) and / or transceiver (106, 206) of FIG. 24. For example, blocks 1010 through 1060 may be implemented in the processor (102, 202) of FIG. 24. Additionally, blocks 1010 to 1050 may be implemented in the processor (102, 202) of FIG. 24, and block 1060 may be implemented in the transceiver (106, 206) of FIG. 24.

[0372] The codeword can be converted into a wireless signal through the signal processing circuit (1000) of FIG. 25. Here, the codeword is an encoded bit sequence of an information block. The information block may include a transmission block (e.g., UL-SCH transmission block, DL-SCH transmission block). The wireless signal can be transmitted through various physical channels (e.g., PUSCH, PDSCH).

[0373] Specifically, a codeword can be converted into a scrambled bit sequence by a scrambler (1010). The scrambled sequence used for scrambling is generated based on an initialization value, which may include ID information of a wireless device, etc. The scrambled bit sequence can be modulated into a modulation symbol sequence by a modulator (1020). The modulation method may include pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), m-QAM (m-Quadrature Amplitude Modulation), etc. The complex modulation symbol sequence can be mapped to one or more transmission layers by a layer mapper (1030). The modulation symbols of each transmission layer can be mapped to the corresponding antenna port(s) by a precoder (1040) (precoding). The output z of the precoder (1040) can be obtained by multiplying the output y of the layer mapper (1030) by an N*M precoding matrix W. Here, N is the number of antenna ports and M is the number of transmission layers. Here, the precoder (1040) can perform precoding after performing transform precoding (e.g., DFT transform) on the complex modulation symbols. Additionally, the precoder (1040) can perform precoding without performing transform precoding.

[0374] A resource mapper (1050) can map the modulation symbols of each antenna port to a time-frequency resource. The time-frequency resource may include multiple symbols (e.g., CP-OFDMA symbols, DFT-s-OFDMA symbols) in the time domain and multiple subcarriers in the frequency domain. A signal generator (1060) generates a radio signal from the mapped modulation symbols, and the generated radio signal can be transmitted to another device through each antenna. To this end, the signal generator (1060) may include an Inverse Fast Fourier Transform (IFFT) module, a Cyclic Prefix (CP) inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

[0375] The signal processing process for a received signal in a wireless device can be configured as the inverse of the signal processing process (1010–1060) of FIG. 25. For example, a wireless device (e.g., 100, 200 in FIG. 24) can receive a wireless signal from the outside through an antenna port / transceiver. The received wireless signal can be converted into a baseband signal through a signal restorer. To this end, the signal restorer may include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a Fast Fourier Transform (FFT) module. Subsequently, the baseband signal can be restored into a codeword through a resource de-mapper process, a postcoding process, a demodulation process, and a de-scrambling process. The codeword can be restored into the original information block through decoding. Accordingly, a signal processing circuit (not shown) for a received signal may include a signal restorer, a resource de-mapper, a postcoder, a demodulator, a de-scrambler, and a decoder.

[0376] FIG. 26 illustrates a wireless device according to one embodiment of the present disclosure. The wireless device may be implemented in various forms depending on the use-example / service (see FIG. 23). The embodiment of FIG. 26 may be combined with various embodiments of the present disclosure.

[0377] Referring to FIG. 26, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 24 and may be composed of various elements, components, units / parts, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 24. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 24. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and additional elements (140) and controls the general operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on a program / code / command / information stored in the memory unit (130). Additionally, the control unit (120) may transmit information stored in the memory unit (130) to an external (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external (e.g., another communication device) via a wireless / wired interface through the communication unit (110) in the memory unit (130).

[0378] The additional element (140) can be configured in various ways depending on the type of wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 23, 100a), a vehicle (Fig. 23, 100b-1, 100b-2), an XR device (Fig. 23, 100c), a portable device (Fig. 23, 100d), a home appliance (Fig. 23, 100e), an IoT device (Fig. 23, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device (Fig. 23, 400), a base station (Fig. 23, 200), a network node, etc. Wireless devices can be used in a movable or fixed location depending on the use—e.g., service.

[0379] In FIG. 26, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least a portion may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and the first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). Additionally, each element, component, unit / part, and / or module within the wireless device (100, 200) may include one or more additional elements. For example, the control unit (120) may be composed of one or more sets of processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an Electronic Control Unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory and / or a combination thereof.

[0380] Hereinafter, an implementation example of FIG. 26 will be described in more detail with reference to the drawings.

[0381] FIG. 27 illustrates a portable device according to one embodiment of the present disclosure. The portable device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch, smart glasses), a portable computer (e.g., a laptop, etc.). The portable device may be referred to as an MS (Mobile Station), UT (User Terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), or WT (Wireless Terminal). The embodiment of FIG. 27 may be combined with various embodiments of the present disclosure.

[0382] Referring to FIG. 27, the portable device (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a memory unit (130), a power supply unit (140a), an interface unit (140b), and an input / output unit (140c). The antenna unit (108) may be configured as part of the communication unit (110). Blocks 110 to 130 / 140a to 140c each correspond to blocks 110 to 130 / 140 of FIG. 26.

[0383] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with other wireless devices and base stations. The control unit (120) can perform various operations by controlling the components of the portable device (100). The control unit (120) may include an AP (Application Processor). The memory unit (130) can store data / parameters / programs / code / commands required for the operation of the portable device (100). Additionally, the memory unit (130) can store input / output data / information, etc. The power supply unit (140a) supplies power to the portable device (100) and may include wired / wireless charging circuits, batteries, etc. The interface unit (140b) can support the connection between the portable device (100) and other external devices. The interface unit (140b) may include various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit (140c) can receive or output video information / signals, audio information / signals, data, and / or information input from a user. The input / output unit (140c) may include a camera, a microphone, a user input unit, a display unit (140d), a speaker and / or a haptic module, etc.

[0384] For example, in the case of data communication, the input / output unit (140c) acquires information / signals (e.g., touch, text, voice, image, video) input from the user, and the acquired information / signals can be stored in the memory unit (130). The communication unit (110) converts the information / signals stored in the memory into wireless signals and can directly transmit the converted wireless signals to another wireless device or to a base station. Additionally, the communication unit (110) can receive wireless signals from another wireless device or base station and then restore the received wireless signals to their original information / signals. The restored information / signals can be stored in the memory unit (130) and then output in various forms (e.g., text, voice, image, video, haptic) through the input / output unit (140c).

[0385] FIG. 28 illustrates a vehicle or autonomous vehicle according to one embodiment of the present disclosure. The vehicle or autonomous vehicle may include a mobile robot, a vehicle, a train, an aerial vehicle (AV), or a ship. The embodiment of FIG. 28 may be combined with various embodiments of the present disclosure.

[0386] Referring to FIG. 28, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140a), a power supply unit (140b), a sensor unit (140c), and an autonomous driving unit (140d). The antenna unit (108) may be configured as part of the communication unit (110). Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 of FIG. 26, respectively.

[0387] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, roadside base stations (Roadside unit), etc.), and servers. The control unit (120) can perform various operations by controlling elements of the vehicle or autonomous vehicle (100). The control unit (120) may include an Electronic Control Unit (ECU). The driving unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The driving unit (140a) may include an engine, motor, power train, wheels, brakes, steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and may include wired / wireless charging circuits, batteries, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, an inclination sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / reverse sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit (140d) may implement a technology for maintaining the driving lane, a technology for automatically adjusting speed such as Adaptive Cruise Control (ACC), a technology for automatically driving along a set path, and a technology for automatically setting a path and driving when a destination is set.

[0388] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving path and a driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or the autonomous vehicle (100) moves along the autonomous driving path according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can acquire the latest traffic information data from an external server non-periodically and can acquire surrounding traffic information data from surrounding vehicles. Additionally, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving path and the driving plan based on the newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving path, driving plan, etc. to an external server. An external server can predict traffic information data in advance using AI technology, etc., based on information collected from vehicles or autonomous vehicles, and can provide the predicted traffic information data to vehicles or autonomous vehicles.

[0389] FIG. 29 shows a vehicle according to one embodiment of the present disclosure. The vehicle may include a means of transport, a train, an aircraft, or a ship. The embodiment of FIG. 29 may be combined with various embodiments of the present disclosure.

[0390] Referring to FIG. 29, the vehicle (100) may include a communication unit (110), a control unit (120), a memory unit (130), an input / output unit (140a), and a position measurement unit (140b). Here, blocks 110 to 130 / 140a to 140b correspond to blocks 110 to 130 / 140 of FIG. 26, respectively.

[0391] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles or base stations. The control unit (120) can control the components of the vehicle (100) to perform various operations. The memory unit (130) can store data / parameters / programs / codes / commands that support various functions of the vehicle (100). The input / output unit (140a) can output AR / VR objects based on information within the memory unit (130). The input / output unit (140a) may include a HUD. The position measurement unit (140b) can acquire position information of the vehicle (100). The position information may include absolute position information of the vehicle (100), position information within the driving line, acceleration information, position information relative to surrounding vehicles, etc. The position measurement unit (140b) may include GPS and various sensors.

[0392] For example, the communication unit (110) of the vehicle (100) can receive map information, traffic information, etc. from an external server and store it in the memory unit (130). The location measurement unit (140b) can acquire vehicle location information through GPS and various sensors and store it in the memory unit (130). The control unit (120) creates a virtual object based on map information, traffic information, and vehicle location information, etc., and the input / output unit (140a) can display the created virtual object on the glass window inside the vehicle (1410, 1420). In addition, the control unit (120) can determine whether the vehicle (100) is operating normally within the driving line based on the vehicle location information. If the vehicle (100) deviates abnormally from the driving line, the control unit (120) can display a warning on the glass window inside the vehicle through the input / output unit (140a). Additionally, the control unit (120) can broadcast a warning message regarding a driving abnormality to surrounding vehicles through the communication unit (110). Depending on the situation, the control unit (120) can transmit the vehicle's location information and information regarding the driving / vehicle abnormality to relevant authorities through the communication unit (110).

[0393] FIG. 30 illustrates an extended reality (XR) device according to one embodiment of the present disclosure. The XR device may include an HMD, a HUD equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, and a robot. The embodiment of FIG. 30 may be combined with various embodiments of the present disclosure.

[0394] Referring to FIG. 30, the XR device (100a) may include a communication unit (110), a control unit (120), a memory unit (130), an input / output unit (140a), a sensor unit (140b), and a power supply unit (140c). Here, blocks 110 to 130 / 140a to 140c correspond to blocks 110 to 130 / 140 of FIG. 26, respectively.

[0395] The communication unit (110) can transmit and receive signals (e.g., media data, control signals, etc.) with external devices such as other wireless devices, mobile devices, or media servers. The media data may include video, images, sound, etc. The control unit (120) can perform various operations by controlling the components of the XR device (100a). For example, the control unit (120) may be configured to control and / or perform procedures such as video / image acquisition, (video / image) encoding, metadata generation, and processing. The memory unit (130) may store data / parameters / programs / code / commands required for driving the XR device (100a) or creating an XR object. The input / output unit (140a) acquires control information, data, etc. from the outside and can output the created XR object. The input / output unit (140a) may include a camera, microphone, user input unit, display unit, speaker and / or haptic module, etc. The sensor unit (140b) can obtain XR device status, surrounding environment information, user information, etc. The sensor unit (140b) may include a proximity sensor, an illuminance sensor, an accelerometer, a magnetic sensor, a gyroscope, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone and / or radar, etc. The power supply unit (140c) supplies power to the XR device (100a) and may include a wired / wireless charging circuit, a battery, etc.

[0396] For example, the memory unit (130) of the XR device (100a) may contain information (e.g., data, etc.) necessary for creating an XR object (e.g., AR / VR / MR object). The input / output unit (140a) may receive a command to operate the XR device (100a) from a user, and the control unit (120) may operate the XR device (100a) according to the user's operation command. For example, if a user intends to watch a movie, news, etc. through the XR device (100a), the control unit (120) may transmit content request information to another device (e.g., a mobile device (100b)) or a media server through the communication unit (130). The communication unit (130) may download / stream content such as a movie, news, etc. from another device (e.g., a mobile device (100b)) or a media server to the memory unit (130). The control unit (120) controls and / or performs procedures such as video / image acquisition, (video / image) encoding, and metadata generation / processing for the content, and can generate / output an XR object based on information about the surrounding space or real object acquired through the input / output unit (140a) / sensor unit (140b).

[0397] Additionally, the XR device (100a) is wirelessly connected to the mobile device (100b) through the communication unit (110), and the operation of the XR device (100a) can be controlled by the mobile device (100b). For example, the mobile device (100b) can act as a controller for the XR device (100a). To this end, the XR device (100a) can acquire three-dimensional position information of the mobile device (100b), and then generate and output an XR object corresponding to the mobile device (100b).

[0398] FIG. 31 shows a robot according to one embodiment of the present disclosure. Robots may be classified into industrial, medical, household, military, etc., depending on the purpose or field of use. The embodiment of FIG. 31 may be combined with various embodiments of the present disclosure.

[0399] Referring to FIG. 31, the robot (100) may include a communication unit (110), a control unit (120), a memory unit (130), an input / output unit (140a), a sensor unit (140b), and a driving unit (140c). Here, blocks 110 to 130 / 140a to 140c correspond to blocks 110 to 130 / 140 of FIG. 26, respectively.

[0400] The communication unit (110) can transmit and receive signals (e.g., driving information, control signals, etc.) with external devices such as other wireless devices, other robots, or control servers. The control unit (120) can control the components of the robot (100) to perform various operations. The memory unit (130) can store data / parameters / programs / codes / commands that support various functions of the robot (100). The input / output unit (140a) can acquire information from outside the robot (100) and output information to outside the robot (100). The input / output unit (140a) may include a camera, microphone, user input unit, display unit, speaker and / or haptic module, etc. The sensor unit (140b) can obtain internal information of the robot (100), surrounding environment information, user information, etc. The sensor unit (140b) may include a proximity sensor, an illuminance sensor, an accelerometer, a magnetic sensor, a gyroscope, an inertial sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone, a radar, etc. The driving unit (140c) may perform various physical movements, such as moving robot joints. Additionally, the driving unit (140c) may enable the robot (100) to travel on the ground or fly in the air. The driving unit (140c) may include an actuator, a motor, a wheel, a brake, a propeller, etc.

[0401] FIG. 32 illustrates an Artificial Intelligence (AI) device according to one embodiment of the present disclosure. The AI ​​device may include a stationary device or a movable device such as a TV, projector, smartphone, PC, laptop, digital broadcasting terminal, tablet PC, wearable device, set-top box (STB), radio, washing machine, refrigerator, digital signage, robot, vehicle, etc. The embodiment of FIG. 32 may be combined with various embodiments of the present disclosure.

[0402] Referring to FIG. 32, the AI ​​device (100) may include a communication unit (110), a control unit (120), a memory unit (130), an input / output unit (140a / 140b), a learning processor unit (140c), and a sensor unit (140d). Blocks 110 to 130 / 140a to 140d each correspond to blocks 110 to 130 / 140 of FIG. 26.

[0403] The communication unit (110) can transmit and receive wired and wireless signals (e.g., sensor information, user input, learning model, control signal, etc.) with external devices such as other AI devices (e.g., 100x, 200, 400 in FIG. 23) or AI servers (e.g., 400 in FIG. 23) using wired and wireless communication technology. To do this, the communication unit (110) can transmit information within the memory unit (130) to an external device or transmit signals received from an external device to the memory unit (130).

[0404] The control unit (120) can determine at least one executable operation of the AI ​​device (100) based on information determined or generated using a data analysis algorithm or a machine learning algorithm. The control unit (120) can perform the determined operation by controlling the components of the AI ​​device (100). For example, the control unit (120) can request, search, receive, or utilize data from the learning processor unit (140c) or the memory unit (130), and can control the components of the AI ​​device (100) to execute a predicted operation or an operation determined to be desirable among at least one executable operation. Additionally, the control unit (120) can collect historical information, including the operation content of the AI ​​device (100) or user feedback regarding the operation, and store it in the memory unit (130) or the learning processor unit (140c), or transmit it to an external device such as an AI server (Fig. 23, 400). The collected historical information can be used to update the learning model.

[0405] The memory unit (130) can store data that supports various functions of the AI ​​device (100). For example, the memory unit (130) can store data obtained from the input unit (140a), data obtained from the communication unit (110), output data from the learning processor unit (140c), and data obtained from the sensing unit (140). Additionally, the memory unit (130) can store control information and / or software code required for the operation / execution of the control unit (120).

[0406] The input unit (140a) can acquire various types of data from outside the AI ​​device (100). For example, the input unit (140a) can acquire training data for model training and input data to which the training model is applied. The input unit (140a) may include a camera, a microphone and / or a user input unit, etc. The output unit (140b) can generate output related to visual, auditory, or tactile senses, etc. The output unit (140b) may include a display unit, a speaker and / or a haptic module, etc. The sensing unit (140) can obtain at least one of internal information of the AI ​​device (100), surrounding environment information of the AI ​​device (100), and user information using various sensors. The sensing unit (140) may include a proximity sensor, an illuminance sensor, an accelerometer, a magnetic sensor, a gyroscope, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone and / or radar, etc.

[0407] The learning processor unit (140c) can train a model composed of an artificial neural network using training data. The learning processor unit (140c) can perform AI processing together with the learning processor unit of the AI ​​server (Fig. 23, 400). The learning processor unit (140c) can process information received from an external device through the communication unit (110) and / or information stored in the memory unit (130). Additionally, the output value of the learning processor unit (140c) can be transmitted to an external device through the communication unit (110) and / or stored in the memory unit (130).

[0408] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method.

Claims

1. Regarding the method, The terminal receives a change notification of MCCH information transmitted from the base station via the multicast and broadcast service control channel (MCCH); The terminal receives a System Information Block (SIB) from the base station, wherein the SIB includes ISA information regarding an Intended Service Area (ISA) of a broadcast service of a Multicast and Broadcast Service (MBS); Based on the location information of the terminal and the ISA information, the terminal determines whether the terminal is located within a specific ISA associated with a changed MBS broadcast service; and A method characterized in that the terminal monitors the MCCH when the terminal is located within the specific ISA.

2. The method of claim 1, wherein the SIB comprises an ISA list for at least one ISA that supports the modified MBS broadcast service.

3. A method according to claim 2, wherein the change notification includes time information regarding the time when the ISA list is included in the SIB.

4. A method according to claim 3, wherein the terminal receives the SIB within a specific time window based on the time indicated by the time information.

5. A method according to claim 1, characterized in that the terminal receives the SIB within a specific time window from the time of receiving the change notification.

6. A method according to claim 1, characterized in that the terminal further receives a Non Access Stratum (NAS) message containing information for accessing a specific MBS service.

7. A method according to claim 6, characterized in that the terminal monitors the MCCH when it is located within the specific ISA and is interested in the specific MBS service.

8. A method according to claim 1, wherein the terminal receives the change notification and the SIB from the base station included in the Non-Terrestrial Network (NTN).

9. A method according to claim 1, characterized in that the monitoring of the MCCH is skipped when the terminal is located outside the specific ISA.

10. A method according to claim 1, characterized in that the terminal skips monitoring of the MCCH when it does not belong to any of the ISAs indicated by the ISA information.

11. A method according to claim 1, wherein the change notification of the MCCH information further includes identification information for identifying at least one specific ISA in which an MBS change has occurred within the ISA list included in the ISA information.

12. In Paragraph 11, A method characterized by monitoring the MCCH when the terminal is located within the at least one specific ISA indicated by the identification information.

13. A method according to claim 11, wherein the identification information includes index information indicating an ISA in which an MBS change has occurred within the ISA list.

14. A method according to claim 11, wherein the identification information comprises bitmap information of m (where m is a natural number) bits corresponding to the size of the ISA list, wherein each bit of the bitmap indicates whether an MBS change has occurred in the corresponding ISA.

15. The terminal, At least one transceiver; At least one memory; and The above includes at least one memory and at least one processor operably coupled with the above at least one transceiver, The above at least one memory includes instructions that are executed by the at least one processor and cause the at least one processor to perform operations, wherein The above operations are: Receive a change notification of MCCH information transmitted from a base station via a multicast and broadcast service control channel (MCCH); A System Information Block (SIB) is received from the base station, wherein the SIB includes ISA information regarding the Intended Service Area (ISA) of the broadcast service of the Multicast and Broadcast Service (MBS); Based on the location information of the terminal and the ISA information, determining whether the terminal is located within a specific ISA associated with a changed MBS broadcast service; and A terminal characterized by including monitoring the MCCH when located within the above-mentioned specific ISA.

16. A terminal according to claim 11, wherein the SIB comprises an ISA list for at least one ISA that supports the modified MBS broadcast service.

17. A terminal according to claim 12, wherein the change notification includes time information regarding the time when the ISA list is included in the SIB.

18. In claim 13, the terminal is characterized by receiving the SIB within a specific time window based on the time indicated by the time information.

19. A terminal according to claim 11, characterized in that the terminal receives the SIB within a specific time window from the time of receiving the change notification.

20. A terminal according to claim 11, characterized in that the terminal further receives a Non Access Stratum (NAS) message containing information for accessing a specific MBS service.

21. The terminal according to claim 16, characterized in that the terminal monitors the MCCH when it is located within the specific ISA and is interested in the specific MBS service.

22. A terminal according to claim 11, characterized in that the terminal receives the change notification and the SIB from a non-terrestrial network (NTN).

23. A terminal according to claim 11, characterized in that it skips monitoring of the MCCH when the terminal is located outside the specific ISA.

24. A terminal according to claim 11, characterized in that it skips monitoring of the MCCH when the terminal does not belong to any of the ISAs indicated by the ISA information.

25. A terminal according to claim 15, wherein the notification of change of MCCH information further includes identification information for identifying at least one specific ISA in which an MBS change has occurred within the ISA list included in the ISA information.

26. In Paragraph 25, A terminal characterized by monitoring an MCCH when the terminal is located within at least one specific ISA indicated by the identification information.

27. A terminal according to claim 25, wherein the identification information includes index information indicating an ISA in which an MBS change has occurred within the ISA list.

28. A terminal according to claim 25, wherein the identification information comprises bitmap information of m (where m is a natural number) bits corresponding to the size of the ISA list, wherein each bit of the bitmap indicates whether an MBS change has occurred in the corresponding ISA.

29. A processing device, At least one memory; and It includes at least one processor operably coupled to the above at least one memory, wherein The above at least one memory includes instructions that are executed by the above at least one processor to perform operations, wherein The above operations are: Receive a change notification of MCCH information transmitted from a base station via a multicast and broadcast service control channel (MCCH); A System Information Block (SIB) is received from the base station, wherein the SIB includes ISA information regarding the Intended Service Area (ISA) of the broadcast service of the Multicast and Broadcast Service (MBS); Based on the location information of the processing device and the ISA information, determining whether the processing device is located within a specific ISA associated with a changed MBS broadcast service; and A processing device characterized by including monitoring the MCCH when located within the above-mentioned specific ISA.

30. At least one computer-readable storage medium (CRM) comprising instructions that are executed by at least one processor to perform operations, The above operations are: Receive a change notification of MCCH information transmitted from a base station via a multicast and broadcast service control channel (MCCH); A System Information Block (SIB) is received from the base station, wherein the SIB includes ISA information regarding the Intended Service Area (ISA) of the broadcast service of the Multicast and Broadcast Service (MBS); Based on the location information of the terminal and the ISA information, determining whether the terminal is located within a specific ISA associated with a changed MBS broadcast service; and A computer-readable storage medium characterized by including monitoring the MCCH when located within the specific ISA mentioned above.

Images