WO2025173804A1 - User equipments, base stations and methods - Google Patents

Abstract

A user equipment (UE) is described. The UE may comprise reception circuitry, measurement circuitry and filtering circuitry. The filtering circuitry is configured to assume that a value of the filterCoefficient is set to 0 if the first measurement is performed within a certain period associated with a beam prediction.

Description

[DESCRIPTION]

[Title of Invention]

USER EQUIPMENTS, BASE STATIONS AND METHODS

[Technical Field]

[0001] The present invention relates to a user equipment, a base station and a method. [Background Art]

[0002] In the 3rd Generation Partnership Project (3GPP), a radio access method and a radio network for cellular mobile communications (hereinafter, referred to as Long Term Evolution, or Evolved Universal Terrestrial Radio Access) have been studied.

[0003] In the 3 GPP, the next generation standard (New Radio: NR) has been studied in order to make a proposal to the International-Mobile-Telecommunication-2020 (IMT- 2020) which is a standard for the next generation mobile communication system defined by the International Telecommunications Union (ITU). NR has been expected to satisfy a requirement considering three scenarios of enhanced Mobile BroadBand (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliable and Low Latency Communication (URLLC), in a single technology framework.

[0004] For example, wireless communication devices may communicate with one or more devices using a communication structure. However, the communication structure used may only offer limited flexibility and/or efficiency. As illustrated by this discussion, systems and methods that improve communication flexibility and/or efficiency may be beneficial.

[Brief Description of the Drawings]

[0005] Figure 1 is a conceptual diagram of a wireless communication system according to an aspect of the present embodiment; [0006] Figure 2 is an example showing the relationship between subcarrier-spacing configuration u, the number of OFDM symbols per slot N^sIot _symb, and the CP configuration according to an aspect of the present embodiment;

[0007] Figure 3 is a diagram showing an example of a method of configuring a resource grid according to an aspect of the present embodiment;

[0008] Figure 4 is a diagram showing a configuration example of a resource grid 3001 according to an aspect of the present embodiment;

[0009] Figure 5 is a schematic block diagram showing a configuration example of the base station device 3 according to an aspect of the present embodiment;

[0010] Figure 6 is a schematic block diagram showing a configuration example of the terminal device 1 according to an aspect of the present embodiment;

[0011] Figure 7 is an example of a functional framework details for Artificial Intelligence and/or Machine Learning (AI/ML) for NR air interface according to an aspect of the present embodiment;

[0012] Figure 8 is a diagram showing a configuration example of an SS/PBCH block according to an aspect of the present embodiment;

[0013] Figure 9 is an example configuration of a frame structure according to an aspect of the present embodiment;

[0014] Figure 10 is an example configuration of a slot configuration according to an aspect of the present embodiment;

[0015] Figure 11 is an example of the inference procedure (prediction procedure) for channel measurement(s) according to an aspect of the present embodiment; and

[0016] Figure 12 is an example of time resource restriction for the channel measurement(s) according to an aspect of the present embodiment. [Description of Embodiments]

[0017] A user equipment (UE) is described. The UE may comprise reception circuitry configured to receive a measurement configuration and a quantity configuration, the quantity configuration including an RRC parameter indicating a filterCoefficient, measurement circuitry configured to perform a first measurement based on the measurement configuration, and filtering circuitry configured to filter results of the first measurement based on the quantity configuration, wherein the filtering circuitry is configured to assume that a value of the filterCoefficient is set to 0 if the first measurement is performed within a certain period associated with a beam prediction.

[0018] A base station is described. The base station may comprise transmission circuitry configured to transmit a measurement configuration and a quantity configuration, the quantity configuration including an RRC parameter indicating a filterCoefficient, wherein the transmission circuitry is configured to set a value of the filterCoefficient to 0 if the measurement configuration and the quantity configuration are associated with a beam prediction.

[0019] A method for a user equipment (UE) is described. The method may comprise receiving a measurement configuration and a quantity configuration, the quantity configuration including an RRC parameter indicating a filterCoefficient, performing a first measurement based on the measurement configuration, and filtering a result of the first measurement based on the quantity configuration, wherein assuming that a value of the filterCoefficient is set to 0 if the first measurement is performed within a certain period associated with a beam prediction.

[0020] A wireless communication device may be an electronic device used to communicate voice and/or data to a base station, which in turn may communicate with a network of devices (e.g., public switched telephone network (PSTN), the Internet, etc.). In describing systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, a UE (User Equipment), an access terminal, a subscriber station, a mobile terminal, a remote station, a user terminal, a terminal, a subscriber unit, a mobile device, a relay node, etc. Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, industrial wireless sensors, video surveillance, wearables, vehicles, roadside units, infrastructure devices, etc. In 3GPP specifications, a wireless communication device is typically referred to as a UE. However, as the scope of the present disclosure should not be limited to the 3 GPP standards, the terms “UE” and “wireless communication device” may be used interchangeably herein to mean the more general term “wireless communication device”.

[0021] In LTE (Long Term Evolution), a base station device is also referred to as an evolved NodeB (eNodeB), and a terminal device is also referred to as a User Equipment (UE). LTE is a cellular communication system in which multiple areas are deployed in a cellular structure, with each of the multiple areas being covered by a base station device. A single base station device may manage multiple cells. Evolved Universal Terrestrial Radio Access is also referred as E-UTRA. In one aspect, LTE has been modified to provide support and specification (TS 38.331, 38.321, 38.300, 37.340, 37.213, 38.211, 38.212, 38.213, 38.214, etc.) for the New Radio Access (NR) and Next generation - Radio Access Network (NG-RAN).

[0022] In 3GPP specifications, a base station is typically referred to as a gNB, a Node B, an eNB, a home enhanced or evolved Node B (HeNB) or some other similar terminology. As the scope of the disclosure should not be limited to 3GPP standards, the terms “base station”, “gNB”, “Node B”, “eNB”, and “HeNB” may be used interchangeably herein to mean the more general term “base station.” Furthermore, one example of a “base station” is an access point. An access point may be an electronic device that provides access to a network (e.g., Local Area Network (LAN), the Internet, etc.) for wireless communication devices. The term “communication device” may be used to denote both a wireless communication device and/or a base station.

[0023] It should be noted that as used herein, a “cell” may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced (IMT-Advanced), IMT-2020 (5G) and all of it or a subset of it may be adopted by 3GPP as licensed bands (e.g., frequency bands) to be used for communication between a base station and a UE. It should also be noted that in NR, NG-RAN, E-UTRA and E-UTRAN overall description, as used herein, a “cell” may be defined as “combination of downlink and optionally uplink resources.” The linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information transmitted on the downlink resources.

[0024] “Configured cells” are those cells of which the UE is aware and is allowed by a base station to transmit or receive information. “Configured cell(s)” may be serving cell(s). The UE may receive system information and perform the required measurements on configured cells. “Configured cell(s)” for a radio connection may consist of a primary cell and/or no, one, or more secondary cell(s). “Activated cells” are those configured cells on which the UE is transmitting and receiving. That is, activated cells are those cells for which the UE monitors the physical downlink control channel (PDCCH) and in the case of a downlink transmission, those cells for which the UE decodes a physical downlink shared channel (PDSCH). “Deactivated cells” are those configured cells that the UE is not monitoring the transmission PDCCH. It should be noted that a “cell” may be described in terms of differing dimensions. For example, a “cell” may have temporal, spatial (e.g., geographical) and frequency characteristics.

[0025] The base station devices may be connected by the NG interface to the 5G - core network (5G-CN). 5G-CN may be called as to NextGen core (NGC), or 5G core (5GC). The base station devices may also be connected by the SI interface to the evolved packet core (EPC). For instance, the base station devices may be connected to a NextGen (NG) mobility management function by the NG-2 interface and to the NG core User Plane (UP) functions by the NG- 3 interface. The NG interface supports a many-to-many relation between NG mobility management functions, NG core UP functions and the base station devices. The NG-2 interface is the NG interface for the control plane and the NG-3 interface is the NG interface for the user plane. For instance, for EPC connection, the base station devices may be connected to a mobility management entity (MME) by the Sl- MME interface and to the serving gateway (S-GW) by the Sl-U interface. The SI interface supports a many-to-many relation between MMEs, serving gateways and the base station devices. The SI -MME interface is the SI interface for the control plane and the Sl-U interface is the SI interface for the user plane. The Uu interface is a radio interface between the UE and the base station for the radio protocol.

[0026] The radio protocol architecture may include the user plane and the control plane. The user plane protocol stack may include packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC) and physical (PHY) layers. A DRB (Data Radio Bearer) is a radio bearer that carries user data (as opposed to control plane signaling). For example, a DRB may be mapped to the user plane protocol stack. The PDCP, RLC, MAC and PHY sublayers (terminated at the base station device on the network) may perform functions (e.g., header compression, ciphering, scheduling, ARQ and HARQ) for the user plane. PDCP entities are located in the PDCP sublayer. RLC entities may be located in the RLC sublayer. MAC entities may be located in the MAC sublayer. The PHY entities may be located in the PHY sublayer.

[0027] The control plane may include a control plane protocol stack. The PDCP sublayer (terminated in base station on the network side) may perform functions (e.g., ciphering and integrity protection) for the control plane. The RLC and MAC sublayers (terminated in base station on the network side) may perform the same functions as for the user plane. The Radio Resource Control (RRC) (terminated in base station on the network side) may perform the following functions. The RRC may perform broadcast functions, paging, RRC connection management, radio bearer (RB) control, mobility functions, UE measurement reporting and control. The Non-Access Stratum (NAS) control protocol (terminated in MME on the network side) may perform, among other things, evolved packet system (EPS) bearer management, authentication, evolved packet system connection management (ECM)-IDLE mobility handling, paging origination in ECM-IDLE and security control.

[0028] Signaling Radio Bearers (SRBs) are Radio Bearers (RB) that may be used only for the transmission of RRC and NAS messages. Three SRBs may be defined. SRBO may be used for RRC messages using the common control channel (CCCH) logical channel. SRB1 may be used for RRC messages (which may include a piggybacked NAS message) as well as for NAS messages prior to the establishment of SRB2, all using the dedicated control channel (DCCH) logical channel. SRB2 may be used for RRC messages which include logged measurement information as well as for NAS messages, all using the DCCH logical channel. SRB2 has a lower priority than SRB1 and may be configured by a network (e.g., base station) after security activation. A broadcast control channel (BCCH) logical channel may be used for broadcasting system information. Some of BCCH logical channel may convey system information which may be sent from the network to the UE via BCH (Broadcast Channel) transport channel. BCH may be sent on a physical broadcast channel (PBCH). Some of BCCH logical channel may convey system information which may be sent from the network to the UE via DL-SCH (Downlink Shared Channel) transport channel. Paging may be provided by using paging control channel (PCCH) logical channel.

[0029] System information may be divided into the MasterlnformationBlock (MIB) and one or more SystemlnformationBlocks (SIBs).

[0030] The UE 1 may receive one or more RRC messages from the base station device 3 to obtain RRC configurations or parameters. The RRC layer of the UE 1 may configure RRC layer and/or lower layers (e.g., PHY layer, MAC layer, RLC layer, PDCP layer) of the UE 1 according to the RRC configurations or parameters which may be configured by the RRC messages, broadcasted system information, and so on. The base station device 3 may transmit one or more RRC messages to the UE 1 to cause the UE 1 to configure RRC layer and/or lower layers of the UE 1 according to the RRC configurations or parameters which may be configured by the RRC messages, broadcasted system information, and so on.

[0031] floor (CX) may be a floor function for real number CX. For example, floor (CX) may be a function that provides the largest integer within a range that does not exceed the real number CX. ceil (DX) may be a ceiling function to a real number DX. For example, ceil (DX) may be a function that provides the smallest integer within the range not less than the real number DX. mod (EX, FX) may be a function that provides the remainder obtained by dividing EX by FX. mod (EX, FX) may be a function that provides a value which corresponds to the remainder of dividing EX by FX, It is exp (GX) = e ^ GX. Here, e is Napier number. (HX) ^ (IX) indicates IX to the power of HX.

[0032] In a wireless communication system according to one aspect of the present embodiment, at least OFDM (Orthogonal Frequency Division Multiplex) is used. An OFDM symbol is a unit of time domain of the OFDM. The OFDM symbol includes at least one or more subcarriers. An OFDM symbol is converted to a time-continuous signal in baseband signal generation. In downlink, at least CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplex) is used. In uplink, either CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplex) is used. DFT-s-OFDM may be given by applying transform precoding to CP-OFDM. CP-OFDM is OFDM using CP (Cyclic Prefix).

[0033] Either DFT-s-OFDM or CP-OFDM may be given based on whether or not transform precoder (or transform precoding) is enabled. DFT-s-OFDM may be given if the transform precoder (or transform precoding) is enabled. CP-OFDM may be given if the transform precoder (or transform precoding) is disabled. E.g., either enabled transform precoder or disabled transform precoder for PUSCH may be indicated based on RRC parameters transformPrecoder in PUSCH-Config or ConfiguredGrantConfig and/or msg3 -transformPrecoder in RACH-ConfigCommon.

[0034] The RRC parameter transformPrecoder indicates the UE specific selection of the transform precoder for a PUSCH. If the transformPrecoder is absent/not configured, the UE applies the value of the msg3 -transformPrecoder to the transform precoder for the PUSCH. [0035] The msg3-transformPrecoder indicates that the UE enables the transform precoder for Msg3 transmission. If the msg3-transformPrecoder is provided/ configured, the UE enables the transform precoder for the Msg3 transmission. If the msg3- transformPrecoder is absent/not configured/not provided, the UE disables the transform precoder for Msg3 transmission.

[0036] The OFDM symbol may be a designation including a CP added to the OFDM symbol. That is, an OFDM symbol may be configured to include the OFDM symbol and a CP added to the OFDM symbol.

[0037] Figure 1 is a conceptual diagram of a wireless communication system according to an aspect of the present embodiment. In Figure 1, the wireless communication system includes at least terminal device 1A to 1C and a base station device 3 (BS # 3: Base station # 3). Hereinafter, the terminal devices lA to 1C are also referred to as a terminal device 1 (UE # 1 : User Equipment # 1).

[0038] The base station device 3 may be configured to include one or more transmission devices (or transmission points, transmission devices, reception devices, transmission points, reception points). When the base station device 3 is configured by a plurality of transmission devices, each of the plurality of transmission devices may be arranged at a different position.

[0039] The base station device 3 may provide one or more serving cells. A serving cell may be defined as a set of resources used for wireless communication. A serving cell is also referred to as a cell.

[0040] A serving cell may be configured to include at least one downlink component carrier (downlink carrier) and/or one uplink component carrier (uplink carrier). A serving cell may be configured to include at least two or more downlink component carriers and/or two or more uplink component carriers. A downlink component carrier and an uplink component carrier are also referred to as component carriers (carriers).

[0041] For example, one resource grid may be provided for one component carrier. For example, one resource grid may be provided for one component carrier and a subcarrier-spacing configuration u. A subcarrier-spacing configuration u is also referred to as numerology. A resource grid includes N^{slze, u} _{grid, x}N^RB _sc subcarriers. The resource grid starts from a common resource block with index N^{start, u} _grid. The common resource block with the index N^{start, u} _grid is also referred to as a reference point of the resource grid. The resource grid includes N^subframe’ ^u _symb OFDM symbols. The subscript x indicates the transmission direction and indicates either downlink or uplink. One resource grid is provided for an antenna port p, a subcarrier-spacing configuration u, and a transmission direction x.

[0042] Resource grid is also referred to as carrier.

[0043] N^{start, u} _grid,x and N^start’ ^u _grid are given based at least on an RRC parameter (e.g. referred to as RRC parameter CarrierBandwidth). The RRC parameter is used to define one or more SCS (SubCarrier-Spacing) specific carriers. One resource grid corresponds to one SCS specific carrier. One component carrier may comprise one or more SCS specific carriers. The SCS specific carrier may be included in a system information block (SIB). For each SCS specific carrier, a subcarrier-spacing configuration u may be provided.

[0044] Figure 2 is an example showing the relationship between subcarrier-spacing configuration u, the number of OFDM symbols per slotN^slot _symb, and the CP configuration according to an aspect of the present embodiment. In Figure 2A, for example, when the subcarrier-spacing configuration u is set to 2 and the CP configuration is set to normal CP (normal cyclic prefix), N^slot _symb = 14, N^{frame, u} _slot = 40, N^{subframe, u} _slot = 4. Further, in Figure 2B, for example, when the subcarrier-spacing configuration u is set to 2 and the CP configuration is set to an extended CP (extended cyclic prefix), N^slot _symb = 12, N^frame’ ^u _slot = 40, N^{subframe, u} _slot = 4.

[0045] In the wireless communication system according to an aspect of the present embodiment, a time unit T_c may be used to represent the length of the time domain. The time unit T_c is T_c = 1 / (df_max * N_f). It is df_max = 480 kHz. It is N_f = 4096. The constant k is k = df_max * N_f / (df_refN_{f, ref}) = 64. df_ref is 15 kHz. N_f, ref is 2048.

[0046] Transmission of signals in the downlink and/or transmission of signals in the uplink may be organized into radio frames (system frames, frames) of length T_f. It is T_f = (df_max N_f / 100) * T_s = 10 ms. One radio frame is configured to include ten subframes. The subframe length is T_sf = (df_maxN_f / 1000) T_s = 1 ms. The number of OFDM symbols per subframe is N^subframe’ _symb = N^slot _symbN^subframe’ ^u _slot.

[0047] For a subcarrier-spacing configuration u, the number of slots included in a subframe and indexes may be given. For example, slot index n^u _s may be given in ascending order with an integer value ranging from 0 to N^subframe,u _slot -1 in a subframe. For subcarrier-spacing configuration u, the number of slots included in a radio frame and indexes of slots included in the radio frame may be given. Also, the slot index n^u _s, f may be given in ascending order with an integer value ranging from 0 to N^frame’^u _slot -1 in the radio frame. Consecutive N^slot _symb OFDM symbols may be included in one slot. It is N^slot _symb = 14.

[0048] Figure 3 is a diagram showing an example of a method of configuring a resource grid according to an aspect of the present embodiment. The horizontal axis in Figure 3 indicates frequency domain. Figure 3 shows a configuration example of a resource grid of subcarrier-spacing configuration u = ui in the component carrier 300 and a configuration example of a resource grid of subcarrier-spacing configuration u = U2 in a component carrier. One or more subcarrier-spacing configuration may be set for a component carrier. Although it is assumed in Figure 3 that ui = U2-I, various aspects of this embodiment are not limited to the condition of ui = U2-I .

[0049] The component carrier 300 is a band having a predetermined width in the frequency domain.

[0050] Point 3000 is an identifier for identifying a subcarrier. Point 3000 is also referred to as point A. The common resource block (CRB) set 3100 is a set of common resource blocks for the subcarrier-spacing configuration ui.

[0051] Among the common resource block-set 3100, the common resource block including the point 3000 (the block indicated by the upper right diagonal line in Figure 3) is also referred to as a reference point of the common resource block-set 3100. The reference point of the common resource block-set 3100 may be a common resource block with index 0 in the common resource block-set 3100.

[0052] The offset 3011 is an offset from the reference point of the common resource block-set 3100 to the reference point of the resource grid 3001. The offset 3011 is indicated by the number of common resource blocks which is relative to the subcarrier- spacing configuration ui. The resource grid 3001 includes N^size,u _grid1,x common resource blocks starting from the reference point of the resource grid 3001.

[0053] The offset 3013 is an offset from the reference point of the resource grid 3001 to the reference point (N^start,u _BWP,i1) of the BWP (BandWidth Part) 3003 of the index il.

[0054] Common resource block-set 3200 is a set of common resource blocks with respect to subcarrier-spacing configuration u₂. [0055] A common resource block including the point 3000 (a block indicated by a upper left diagonal line in Figure 3) in the common resource block-set 3200 is also referred to as a reference point of the common resource block-set 3200. The reference point of the common resource block-set 3200 may be a common resource block with index 0 in the common resource block-set 3200.

[0056] The offset 3012 is an offset from the reference point of the common resource block-set 3200 to the reference point of the resource grid 3002. The offset 3012 is indicated by the number of common resource blocks for subcarrier-spacing configuration u = u₂. The resource grid 3002 includes N^slze’^u _grid2,x common resource blocks starting from the reference point of the resource grid 3002.

[0057] The offset 3014 is an offset from the reference point of the resource grid 3002 to the reference point (N^start,u _BWP,i2) of the BWP 3004 with index 12.

[0058] Figure 4 is a diagram showing a configuration example of a resource grid 3001 according to an aspect of the present embodiment. In the resource grid of Figure 4, the horizontal axis indicates OFDM symbol index l_sym, and the vertical axis indicates the subcarrier index k_sc. The resource grid 3001 includes N^size,u _{grid, x} N^RB _SC subcarriers, and includes N^subframes’^u _symb OFDM symbols. A resource specified by the subcarrier index k_sc and the OFDM symbol index l_sym in a resource grid is also referred to as a resource element (RE).

[0059] A resource block (RB) includes N^RB _SC consecutive subcarriers. A resource block is a generic name of a common resource block, a physical resource block (PRB), and a virtual resource block (VRB). It is N^RB _SC = 12. [0060] A resource block unit is a set of resources that corresponds to one OFDM symbol in one resource block. That is, one resource block unit includes 12 resource elements which corresponds to one OFDM symbol in one resource block.

[0061] Common resource blocks for a subcarrier-spacing configuration u are indexed in ascending order from 0 in the frequency domain in a common resource block-set. The common resource block with index 0 for the subcarrier-spacing configuration u includes (or collides with, matches) the point 3000. The index n^u _CRB of the common resource block with respect to the subcarrier-spacing configuration u satisfies the relationship of n^u _CRB = ceil (k_sc / N^RB _SC). The subcarrier with k_sc = 0 is a subcarrier with the same center frequency as the center frequency of the subcarrier which corresponds to the point 3000.

[0062] Physical resource blocks for a subcarrier-spacing configuration u are indexed in ascending order from 0 in the frequency domain in a BWP. The index n^u _PRB of the physical resource block with respect to the subcarrier-spacing configuration u satisfies the relationship of n^u _CRB = n^u _PRB + N^start’^u _BWP,i. The N^start’^u _BWP,i indicates the reference point of BWP with index i,

[0063] A BWP is defined as a subset of common resource blocks included in the resource grid. The BWP includes N^size’ ^u _BWP,i. common resource blocks starting from the reference points N^start,u _BWP,i. A BWP for the downlink component carrier is also referred to as a downlink BWP. A BWP for the uplink component carrier is also referred to as an uplink BWP.

[0064] An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. For example, the channel may correspond to a physical channel. For example, the symbols may correspond to OFDM symbols. For example, the symbols may correspond to resource block units. For example, the symbols may correspond to resource elements.

[0065] Two antenna ports are said to be QCL (Quasi Co-Located) if the large-scale properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed. The large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters.

[0066] Carrier aggregation may be communication using a plurality of aggregated serving cells. Carrier aggregation may be communication using a plurality of aggregated component carriers. Carrier aggregation may be communication using a plurality of aggregated downlink component carriers. Carrier aggregation may be communication using a plurality of aggregated uplink component carriers.

[0067] Figure 5 is a schematic block diagram showing a configuration example of the base station device 3 according to an aspect of the present embodiment. As shown in Figure 5, the base station device 3 includes at least a part or all of the wireless transmission I reception unit (physical layer processing unit) 30 and the higher-layer processing unit 34. The wireless transmission / reception unit 30 includes at least a part or all of the antenna unit 31 , the RF unit 32 (Radio Frequency unit 32), and the baseband unit 33. The higher-layer processing unit 34 includes at least a part or all of the medium access control layer processing unit 35 and the radio resource control (RRC) layer processing unit 36.

[0068] The wireless transmission / reception unit 30 includes at least a part of or all of a wireless transmission unit 30a and a wireless reception unit 30b. The configuration of the baseband unit 33 included in the wireless transmission unit 30a and the configuration of the baseband unit 33 included in the wireless reception unit 30b may be the same or different. The configuration of the RF unit 32 included in the wireless transmission unit 30a and the configuration of the RF unit 32 included in the wireless reception unit 30b may be the same or different. The configuration of the antenna unit 31 included in the wireless transmission unit 30a and the configuration of the antenna unit 31 included in the wireless reception unit 30b may be the same or different.

[0069] The higher-layer processing unit 34 provides downlink data (a transport block) to the wireless transmission / reception unit 30 (or the wireless transmission unit 30a). The higher-layer processing unit 34 performs processing of a medium access control (MAC) layer, a packet data convergence protocol layer (PDCP layer), a radio link control layer (RLC layer) and/or an RRC layer.

[0070] The medium access control layer processing unit 35 included in the higher- layer processing unit 34 performs processing of the MAC layer.

[0071] The radio resource control layer processing unit 36 included in the higher- layer processing unit 34 performs the process of the RRC layer. The radio resource control layer processing unit 36 manages various configuration information / parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 36 configures an RRC parameter based on the RRC message received from the terminal device 1.

[0072] The wireless transmission / reception unit 30 (or the wireless transmission unit 30a) performs processing such as encoding and modulation. The wireless transmission / reception unit 30 (or the wireless transmission unit 30a) generates a physical signal by encoding and modulating the downlink data. The wireless transmission / reception unit 30 (or the wireless transmission unit 30a) converts OFDM symbols in the physical signal to a baseband signal by conversion to a time-continuous signal. The wireless transmission I reception unit 30 (or the wireless transmission unit 30a) transmits the baseband signal (or the physical signal) to the terminal device 1 via radio frequency. The wireless transmission / reception unit 30 (or the wireless transmission unit 30a) may arrange the baseband signal (or the physical signal) on a component carrier and transmit the baseband signal (or the physical signal) to the terminal device 1.

[0073] The wireless transmission / reception unit 30 (or the wireless reception unit 30b) performs processing such as demodulation and decoding. The wireless transmission / reception unit 30 (or the wireless reception unit 30b) separates, demodulates and decodes the received physical signal, and provides the decoded information to the higher-layer processing unit 34. The wireless transmission / reception unit 30 (or the wireless reception unit 30b) may perform the channel access procedure prior to the transmission of the physical signal.

[0074] The RF unit 32 demodulates the physical signal received via the antenna unit 31 into a baseband signal (down convert), and/or removes extra frequency components. The RF unit 32 provides the processed analog signal to the baseband unit 33.

[0075] The baseband unit 33 converts an analog signal (signals on radio frequency) input from the RF unit 32 into a digital signal (a baseband signal). The baseband unit 33 separates a portion which corresponds to CP (Cyclic Prefix) from the digital signal. The baseband unit 33 performs Fast Fourier Transformation (FFT) on the digital signal from which the CP has been removed. The baseband unit 33 provides the physical signal in the frequency domain.

[0076] The baseband unit 33 performs Inverse Fast Fourier Transformation (IFFT) on downlink data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a digital signal (baseband signal), and convert the digital signal into an analog signal. The baseband unit 33 provides the analog signal to the RF unit 32.

[0077] The RF unit 32 removes extra frequency components from the analog signal (signals on radio frequency) input from the baseband unit 33, up-converts the analog signal to a radio frequency and transmits it via the antenna unit 31. The RF unit 32 may have a function of controlling transmission power. The RF unit 32 is also referred to as a transmission power control unit.

[0078] At least one or more serving cells (or one or more component carriers, one or more downlink component carriers, one or more uplink component carriers) may be configured for the terminal device 1.

[0079] Each of the serving cells set for the terminal device 1 may be any of PCell (Primary cell), PSCell (Primary SCG cell), and SCell (Secondary Cell).

[0080] A PCell is a serving cell included in a MCG (Master Cell Group). A PCell is a cell (implemented cell) which performs an initial connection establishment procedure or a connection re-establishment procedure by the terminal device 1.

[0081] A PSCell is a serving cell included in a SCG (Secondary Cell Group). A PSCell is a serving cell in which random-access is performed by the terminal device 1 in a reconfiguration procedure with synchronization (Reconfiguration with synchronization). [0082] A SCell may be included in either an MCG or an SCG.

[0083] The serving cell group (cell group) is a designation including at least MCG and SCG. The serving cell group may include one or more serving cells (or one or more component carriers). One or more serving cells (or one or more component carriers) included in the serving cell group may be operated by carrier aggregation. [0084] One or more downlink BWPs may be configured for each serving cell (or each downlink component carrier). One or more uplink BWPs may be configured for each serving cell (or each uplink component carrier).

[0085] Among the one or more downlink BWPs set for the serving cell (or the downlink component carrier), one downlink BWP may be set as an active downlink BWP (or one downlink BWP may be activated). Among the one or more uplink BWPs set for the serving cell (or the uplink component carrier), one uplink BWP may be set as an active uplink BWP (or one uplink BWP may be activated).

[0086] A PDSCH, a PDCCH, and a CSI-RS may be received in the active downlink BWP. The terminal device 1 may receive the PDSCH, the PDCCH, and the CSI-RS in the active downlink BWP. A PUCCH and a PUSCH may be sent on the active uplink BWP. The terminal device 1 may transmit the PUCCH and the PUSCH in the active uplink BWP. The active downlink BWP and the active uplink BWP are also referred to as active BWP. [0087] The PDSCH, the PDCCH, and the CSI-RS may not be received in downlink BWPs (inactive downlink BWPs) other than the active downlink BWP. The terminal device 1 may not receive the PDSCH, the PDCCH, and the CSI-RS in the downlink BWPs which are other than the active downlink BWP. The PUCCH and the PUSCH do not need to be transmitted in uplink BWPs (inactive uplink BWPs) other than the active uplink BWP. The terminal device 1 may not transmit the PUCCH and the PUSCH in the uplink BWPs which is other than the active uplink BWP. The inactive downlink BWP and the inactive uplink BWP are also referred to as inactive BWP.

[0088] Downlink BWP switching deactivates an active downlink BWP and activates one of inactive downlink BWPs which are other than the active downlink BWP. The downlink BWP switching may be controlled by a BWP field included in a downlink control information. The downlink BWP switching may be controlled based on higher- layer parameters.

[0089] Uplink BWP switching is used to deactivate an active uplink BWP and activate any inactive uplink BWP which is other than the active uplink BWP. Uplink BWP switching may be controlled by a BWP field included in a downlink control information. The uplink BWP switching may be controlled based on higher-layer parameters.

[0090] Among the one or more downlink BWPs set for the serving cell, two or more downlink BWPs may not be set as active downlink BWPs. For the serving cell, one downlink BWP may be active at a certain time.

[0091] Among the one or more uplink BWPs set for the serving cell, two or more uplink BWPs may not be set as active uplink BWPs. For the serving cell, one uplink BWP may be active at a certain time.

[0092] Figure 6 is a schematic block diagram showing a configuration example of the terminal device 1 according to an aspect of the present embodiment. As shown in Figure 6, the terminal device 1 includes at least a part or all of the wireless transmission / reception unit (physical layer processing unit) 10 and the higher-layer processing unit 14. The wireless transmission / reception unit 10 includes at least a part or all of the antenna unit 11, the RF unit 12, and the baseband unit 13. The higher-layer processing unit 14 includes at least a part or all of the medium access control layer processing unit 15 and the radio resource control layer processing unit 16.

[0093] The wireless transmission / reception unit 10 includes at least a part of or all of a wireless transmission unit 10a and a wireless reception unit 10b. The configuration of the baseband unit 13 included in the wireless transmission unit 10a and the configuration of the baseband unit 13 included in the wireless reception unit 10b may be the same or different. The configuration of the RF unit 12 included in the wireless transmission unit 10a and the RF unit 12 included in the wireless reception unit 10b may be the same or different. The configuration of the antenna unit 11 included in the wireless transmission unit 10a and the configuration of the antenna unit 11 included in the wireless reception unit 10b may be the same or different.

[0094] The higher-layer processing unit 14 provides uplink data (a transport block) to the wireless transmission I reception unit 10 (or the wireless transmission unit 10a). The higher-layer processing unit 14 performs processing of a MAC layer, a packet data integration protocol layer, a radio link control layer, and/or an RRC layer.

[0095] The medium access control layer processing unit 15 included in the higher- layer processing unit 14 performs processing of the MAC layer.

[0096] The radio resource control layer processing unit 16 included in the higher- layer processing unit 14 performs the process of the RRC layer. The radio resource control layer processing unit 16 manages various configuration information / parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 16 configures RRC parameters based on the RRC message received from the base station device 3.

[0097] The wireless transmission / reception unit 10 (or the wireless transmission unit 10a) performs processing such as encoding and modulation. The wireless transmission I reception unit 10 (or the wireless transmission unit 10a) generates a physical signal by encoding and modulating the uplink data. The wireless transmission / reception unit 10 (or the wireless transmission unit 10a) converts OFDM symbols in the physical signal to a baseband signal by conversion to a time-continuous signal. The wireless transmission / reception unit 10 (or the wireless transmission unit 10a) transmits the baseband signal (or the physical signal) to the base station device 3 via radio frequency. The wireless transmission / reception unit 10 (or the wireless transmission unit 10a) may arrange the baseband signal (or the physical signal) on a BWP (active uplink BWP) and transmit the baseband signal (or the physical signal) to the base station device 3.

[0098] The wireless transmission / reception unit 10 (or the wireless reception unit 10b) performs processing such as demodulation and decoding. The wireless transmission

I reception unit 10 (or the wireless reception unit 10b) may receive a physical signal in a BWP (active downlink BWP) of a serving cell. The wireless transmission / reception unit 10 (or the wireless reception unit 10b) separates, demodulates and decodes the received physical signal, and provides the decoded information to the higher-layer processing unit 14. The wireless transmission / reception unit 10 (or the wireless reception unit 10b) may perform the channel access procedure prior to the transmission of the physical signal.

[0099] The RF unit 12 demodulates the physical signal received via the antenna unit

I I into a baseband signal (down convert), and/or removes extra frequency components. The RF unit 12 provides the processed analog signal to the baseband unit 13.

[0100] The baseband unit 13 converts an analog signal (signals on radio frequency) input from the RF unit 12 into a digital signal (a baseband signal). The baseband unit 13 separates a portion which corresponds to CP from the digital signal, performs fast Fourier transformation on the digital signal from which the CP has been removed, and provides the physical signal in the frequency domain.

[0101] The baseband unit 13 performs inverse fast Fourier transformation on uplink data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a digital signal (baseband signal), and convert the digital signal into an analog signal. The baseband unit 13 provides the analog signal to the RF unit 12. [0102] The RF unit 12 removes extra frequency components from the analog signal (signals on radio frequency) input from the baseband unit 13, up-converts the analog signal to a radio frequency and transmits it via the antenna unit 11. The RF unit 12 may have a function of controlling transmission power. The RF unit 12 is also referred to as a transmission power control unit.

[0103] Figure 7 is an example of a functional framework details for Artificial Intelligence and/or Machine Learning (AI/ML) for NR air interface according to an aspect of the present embodiment. The aim of this framework is to cover a general functional architecture addressing both model-ID-based life cycle management (LCM) and functionality-based LCM. Therefore, some of the functions or data/information/instruction flows (i.e., the arrows) shown in the Figure 7 might not always be relevant for a given LCM approach. As an illustrative example, consider a scenario where the network performs functionality-based LCM and where models are not identified in the network, while the UE concurrently performs model-level management (e.g., model selection/switching /(de-)activation). In this hypothetical case, the “Model Training” or “Model Storage” functions with their respective procedures, may be regarded as irrelevant from the network’s perspective.

[0104] The general framework for AI/ML for NR air interface may include part or all of “Data Collection”, “Model Training”, “Management”, “Inference”, and “Model Storage”.

[0105] Data Collection 7001 may be a function that provides input data to the Model Training, Management, and Inference functions. Here, Training Data may be Data needed as input for the AI/ML Model Training function. Monitoring Data may be Data needed as input for the Management of AI/ML models or AI/ML functionalities. Inference Data may be Data needed as input for the AI/ML Inference function.

[0106] Model Training 7002 may be a function that performs AI/ML model training, validation, and testing which may generate model performance metrics which can be used as part of the model testing procedure. The Model Training function may be also responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on Training Data delivered by a Data Collection function, if required. Here, Trained/Updated Model may be used to deliver trained, validated, and tested AI/ML models to the Model Storage function, or to deliver an updated version of a model to the Model Storage function in case of having a Model Storage function.

[0107] Management 7003 may be a function that oversees the operation (e.g., selection/(de)activation/switching/fallback) and monitoring (e.g., performance) of AI/ML models or AI/ML functionalities. This function may be also responsible for making decisions to ensure the proper inference operation based on data received from the Data Collection function and the Inference function. Here, Management Instruction may be Information needed as input to manage the Inference function. Concerning information may include selection/(de)activation/switching of AI/ML models or AI/ML-based functionalities, fallback to non-AI/ML operation (i.e., not relying on inference process). Model Transfer/Delivery Request may be used to request model(s) to the Model Storage function. Performance Feedback / Retraining Request may be information needed as input for the Model Training function, e.g., for model (re)training or updating purposes.

[0108] Inference 7004 may be a function that provides outputs from the process of applying AI/ML models or AI/ML functionalities, using the data that is provided by the Data Collection function (i.e., Inference Data) as an input. The Inference function is also responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on Inference Data delivered by a Data Collection function, if required. Here, Inference Output may be Data used by the Management function to monitor the performance of AI/ML models or AI/ML functionalities.

[0109] Model Storage 7005 may be a function responsible for storing trained/updated models that can be used to perform the Inference function. Here, Model Transfer/Delivery may be used to deliver an AI/ML model to the Inference function. It is noted that the Model Storage function in Figure 7 is only intended as a reference point (if any) when applicable for protocol terminations, model transfer/delivery, and related processes. It should be stressed that its purpose does not encompass restricting the actual storage locations of models. Therefore, the specification impact of all data/information/instruction flows (i.e., the arrows in Figure 7) to/from this function should be studied case by case.

[0110] The general framework(s) for the AI/ML may be applied for each unit illustrated in Figures 5 and 6, respectively if the capability for AI/ML is supported.

[0111] Hereinafter, terms associated with AI/ML feature will be described.

[0112] The AI/ML-enabled Feature may refer to a Feature where AI/ML may be used. [0113] The AI/ML model may be a data driven algorithm that applies AI/ML techniques to generate a set of outputs based on a set of inputs.

[0114] The AI/ML model delivery may be a generic term referring to delivery of an AI/ML model from one entity to another entity in any manner. Note: An entity could mean a network node/function (e.g., gNB, LMF, etc.), UE, proprietary server, etc.

[0115] The AI/ML model inference may be a process of using a trained AI/ML model to produce a set of outputs based on a set of inputs. [0116] The AI/ML model testing may be a process to train an AI/ML Model (by learning the input/output relationship) in a data driven manner and obtain the trained AI/ML Model for inference.

[0117] The AI/ML model transfer may be delivery of an AI/ML model over the air interface in a manner that is not transparent to 3GPP signalling, either parameters of a model structure known at the receiving end or a new model with parameters. Delivery may contain a full model or a partial model.

[0118] The AI/ML model validation may be a subprocess of training, to evaluate the quality of an AI/ML model using a dataset different from one used for model training, that helps selecting model parameters that generalize beyond the dataset used for model training.

[0119] The data collection may be a process of collecting data by the network nodes, management entity, or UE for the purpose of AI/ML model training, data analytics and inference.

[0120] The federated learning /federated training may be a machine learning technique that trains an AI/ML model across multiple decentralized edge nodes (e.g., UEs, gNBs) each performing local model training using local data samples. The technique requires multiple interactions of the model, but no exchange of local data samples.

[0121] The functionality identification may be a process/method of identifying an AI/ML functionality for the common understanding between the network (NW) and the UE. Note: Information regarding the AI/ML functionality may be shared during functionality identification. Where AI/ML functionality resides depends on the specific use cases and sub use cases. For example, the AI/ML functionality may include/correspond to one or more sets of RRC configuration(s) including one or more RRC parameters. The set of RRC configuration(s) at the UE 1 may be switched/changed based on switching the AI/ML functionalities.

[0122] The management instruction may be information needed to ensure proper inference operation. This information may include selection/(de)activation/switching of AI/ML models or AI/ML functionalities, fallback to non-AI/ML operation, etc.

[0123] The model activation may enable an AI/ML model for a specific AI/ML- enabled feature.

[0124] The model download may be model transfer from the network to UE.

[0125] The model identification may be a process/method of identifying an AI/ML model for the common understanding between the NW and the UE. Note: The process/method of model identification may or may not be applicable. Note: Information regarding the AI/ML model may be shared during model identification.

[0126] The model monitoring may be a procedure that monitors the inference performance of the AI/ML model.

[0127] The model parameter update may be a process of updating the model parameters of a model,

[0128] The model selection may be the process of selecting an AI/ML model for activation among multiple models for the same AI/ML enabled feature. Note: Model selection may or may not be carried out simultaneously with model activation.

[0129] The model switching may be deactivating a currently active AI/ML model and activating a different AI/ML model for a specific AI/ML-enabled feature.

[0130] The model update may be a process of updating the model parameters and/or model structure of a model.

[0131] The model upload may be a model transfer from UE to the network. [0132] The network side (AI/ML) model may be an AI/ML Model whose inference is performed entirely at the network,

[0133] The offline field data may be the data collected from field and used for offline training of the AI/ML model.

[0134] The offline training may be an AI/ML training process where the model is trained based on collected dataset, and where the trained model is later used or delivered for inference. Note: This definition only serves as a guidance. There may be cases that may not exactly conform to this definition but could still be categorized as offline training by commonly accepted conventions.

[0135] The online field data may be the data collected from field and used for online training of the AI/ML model.

[0136] The online training may be an AI/ML training process where the model being used for inference) is (typically continuously) trained in (near) real-time with the arrival of new training samples. Note: the notion of (near) real-time vs. non real-time is context- dependent and is relative to the inference time-scale. Note: This definition only serves as a guidance. There may be cases that may not exactly conform to this definition but could still be categorized as online training by commonly accepted conventions. Note: Fine- tuning/re-training may be done via online or offline training.

[0137] The reinforcement learning (RL) may be a process of training an AI/ML model from input (a.k.a. state) and a feedback signal (a.k.a. reward) resulting from the model’s output (a.k.a. action) in an environment the model is interacting with.

[0138] The semi-supervised learning may be a process of training a model with a mix of labelled data and unlabelled data. [0139] The supervised learning may be a process of training a model from input and its corresponding labels.

[0140] The test encoder / decoder for TE (test equipment) may be AI/ML model for UE encoder/gNB decoder implemented by TE.

[0141] The two-sided (AI/ML) model may be a paired AI/ML Model(s) over which joint inference is performed, where joint inference comprises AI/ML Inference whose inference is performed jointly across the UE and the network, i.e., the first part of inference is firstly performed by UE and then the remaining part is performed by gNB, or vice versa.

[0142] The UE-side (AI/ML) model may be an AI/ML Model whose inference is performed entirely at the UE.

[0143] The unsupervised learning may be a process of training a model without labelled data.

[0144] The Proprietary-format models may be ML models of vendor-/device-specific proprietary format, from 3 GPP perspective. They are not mutually recognizable across vendors and hide model design information from other vendors when shared. Note: An example is a device-specific binary executable format.

[0145] The open-format models may be ML models of specified format that are mutually recognizable across vendors and allow interoperability, from 3GPP perspective. They are mutually recognizable between vendors and do not hide model design information from other vendors when shared.

[0146] The framework may be used for a use case of the CSI feedback enhancement(s), the beam management(s) and/or the positioning accuracy enhancement(s). The CSI feedback enhancement(s) may include spatial-frequency domain CSI compression using two-sided AI/ML model and/or time domain CSI prediction using UE side and/or NW side AI/ML model. The beam management(s) may include spatial domain DL beam prediction for Set A of beams based on measurement results of Set B of beams and/or temporal DL beam prediction for Set A of beams based on the historic measurement results of Set B of beams. The positioning accuracy enhancement(s) may include direct AI/ML positioning and/or AI/ML assisted positioning. [0147] Hereinafter, physical signals (signals) will be described.

[0148] Physical signal is a generic term for downlink physical channels, downlink physical signals, uplink physical channels, and uplink physical channels. The physical channel is a generic term for downlink physical channels and uplink physical channels.

[0149] An uplink physical channel may correspond to a set of resource elements that carry information originating from the higher-layer and/or uplink control information. The uplink physical channel may be a physical channel used in an uplink component carrier. The uplink physical channel may be transmitted by the terminal device 1. The uplink physical channel may be received by the base station device 3. In the wireless communication system according to one aspect of the present embodiment, at least part or all of PUCCH (Physical Uplink Control CHannel), PUSCH (Physical Uplink Shared CHannel), and PRACH (Physical Random Access CHannel) may be used.

[0150] A PUCCH may be used to transmit uplink control information (UCI). The PUCCH may be sent to deliver (transmission, convey) uplink control information. The uplink control information may be mapped to (or arranged in) the PUCCH. The terminal device 1 may transmit PUCCH in which uplink control information is arranged. The base station device 3 may receive the PUCCH in which the uplink control information is arranged. [0151] Uplink control information (uplink control information bit, uplink control information sequence, uplink control information type) includes at least part or all of channel state information (CSI), scheduling request (SR), and HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgem ent).

[0152] CSI is conveyed by using channel state information bits or a channel state information sequence. Scheduling request is also referred to as a scheduling request bit or a scheduling request sequence. HARQ-ACK information is also referred to as a HARQ-ACK information bit or a HARQ-ACK information sequence.

[0153] HARQ-ACK information may include HARQ-ACK status which corresponds to a transport block (TB). The HARQ-ACK status may indicate ACK (acknowledgement) or NACK (negative-acknowledgement) corresponding to the transport block. The ACK may indicate that the transport block has been successfully decoded. The NACK may indicate that the transport block has not been successfully decoded. The HARQ-ACK information may include a HARQ-ACK codebook that includes one or more HARQ- ACK status (or HARQ-ACK bits). Here, TB may be referred to as MAC PDU (Medium Access Control Protocol Data Unit), DL-SCH (Downlink-Shared Channel), UL-SCH (Uplink-Shared Channel), PDSCH, PUSCH, downlink data, uplink data.

[0154] For example, the correspondence between the HARQ-ACK information and the transport block may mean that the HARQ-ACK information and the PDSCH used for transmission of the transport block correspond.

[0155] HARQ-ACK status may indicate ACK or NACK which correspond to one CBG (Code Block Group) included in the transport block.

[0156] The SR may at least be used to request PUSCH (or UL-SCH) resources for new transmission. The SR may be used to indicate either a positive SR or a negative SR. The fact that the scheduling request indicates a positive SR is also referred to as "a positive SR is sent". The positive SR may indicate that the PUSCH (or UL-SCH) resource for initial transmission is requested by the terminal device 1. A positive SR may indicate that a higher-layer is to trigger an SR. The positive SR may be sent when the higher-layer instructs to send a scheduling request. The fact that the SR bit indicates a negative SR is also referred to as "a negative SR is sent". A negative SR may indicate that the PUSCH (or UL-SCH) resource for initial transmission is not requested by the terminal device 1. A negative SR may indicate that the higher-layer does not trigger a scheduling request. A negative SR may be sent if the higher-layer is not instructed to send a scheduling request. [0157] The CSI may include at least part or all of a channel quality indicator (CQI), a precoder matrix indicator (PMI), and a rank indicator (RI). CQI is an indicator related to channel quality (e.g., propagation quality) or physical channel quality, and PMI is an indicator related to a precoder. RI is an indicator related to transmission rank (or the number of transmission layers).

[0158] CSI may be provided at least based on receiving one or more physical signals (e.g., one or more CSI-RSs) used at least for channel measurement. The channel state information may be selected by the terminal device 1 at least based on receiving one or more physical signals used for channel measurement. Channel measurements may include interference measurements.

[0159] A PUCCH may correspond to a PUCCH format. A PUCCH may be a set of resource elements used to convey a PUCCH format. A PUCCH may include a PUCCH format. A PUCCH format may include UCI.

[0160] A PUSCH may be used to transmit uplink data (a transport block) and/or uplink control information. A PUSCH may be used to transmit uplink data (a transport block) corresponding to a UL-SCH and/or uplink control information. A PUSCH may be used to convey uplink data and/or uplink control information. A PUSCH may be used to convey uplink data corresponding to a UL-SCH and/or uplink control information. Uplink data may be arranged in a PUSCH. Uplink data corresponding to UL-SCH may be arranged in a PUSCH. Uplink control information may be arranged to a PUSCH. The terminal device 1 may transmit a PUSCH in which uplink data and/or uplink control information is arranged. The base station device 3 may receive a PUSCH in which uplink data and/or uplink control information is arranged.

[0161] A PRACH may be used to transmit a random-access preamble. The PRACH may be used to convey a random-access preamble. The sequence x_u, _v (n) of the PRACH is defined by x_{u, v} (n) = x_u (mod (n + C_v, L_RA)). The x_u may be a ZC sequence (Zadoff- Chu sequence). The x_u may be defined by x_u “ exp (-jpui (i + 1) / L_RA). The j is an imaginary unit. The pui is the circle ratio. The C_v corresponds to cyclic shift of the PRACH. L_RA corresponds to the length of the PRACH. The L_RA may be 839 or 139 or another value. The i is an integer in the range of 0 to L_RA-1. The u is a sequence index for the PRACH. The terminal device 1 may transmit the PRACH. The base station device 3 may receive the PRACH.

[0162] For a given PRACH opportunity, 64 random-access preambles are defined. The random-access preamble is specified (determined, given) at least based on the cyclic shift C_v of the PRACH and the sequence index u for the PRACH.

[0163] An uplink physical signal may correspond to a set of resource elements. The uplink physical signal may not carry information generated in the higher-layer. The uplink physical signal may be a physical signal used in the uplink component carrier. The terminal device 1 may transmit an uplink physical signal. The base station device 3 may receive the uplink physical signal. In the radio communication system according to one aspect of the present embodiment, at least a part or all of UL DMRS (UpLink Demodulation Reference Signal), SRS (Sounding Reference Signal), UL PTRS (UpLink Phase Tracking Reference Signal) may be used.

[0164] UL DMRS is a generic name of a DMRS for a PUSCH and a DMRS for a PUCCH.

[0165] A set of antenna ports of a DMRS for a PUSCH (a DMRS associated with a PUSCH, a DMRS included in a PUSCH, a DMRS which corresponds to a PUSCH) may be given based on a set of antenna ports for the PUSCH. That is, the set of DMRS antenna ports for the PUSCH may be the same as the set of antenna ports for the PUSCH.

[0166] Transmission of a PUSCH and transmission of a DMRS for the PUSCH may be indicated (or scheduled) by one DCI format. The PUSCH and the DMRS for the PUSCH may be collectively referred to as a PUSCH. Transmission of the PUSCH may be transmission of the PUSCH and the DMRS for the PUSCH.

[0167] A PUSCH may be estimated from a DMRS for the PUSCH. That is, propagation path of the PUSCH may be estimated from the DMRS for the PUSCH.

[0168] A set of antenna ports of a DMRS for a PUCCH (a DMRS associated with a PUCCH, a DMRS included in a PUCCH, a DMRS which corresponds to a PUCCH) may be identical to a set of antenna ports for the PUCCH.

[0169] Transmission of a PUCCH and transmission of a DMRS for the PUCCH may be indicated (or triggered) by one DCI format. The arrangement of the PUCCH in resource elements (resource element mapping) and/or the arrangement of the DMRS in resource elements for the PUCCH may be provided at least by one PUCCH format. The PUCCH and the DMRS for the PUCCH may be collectively referred to as PUCCH. Transmission of the PUCCH may be transmission of the PUCCH and the DMRS for the PUCCH.

[0170] A PUCCH may be estimated from a DMRS for the PUCCH. That is, propagation path of the PUCCH may be estimated from the DMRS for the PUCCH.

[0171] A downlink physical channel may correspond to a set of resource elements that carry information originating from the higher-layer and/or downlink control information. The downlink physical channel may be a physical channel used in the downlink component carrier. The base station device 3 may transmit the downlink physical channel. The terminal device 1 may receive the downlink physical channel. In the wireless communication system according to one aspect of the present embodiment, at least a part or all of PBCH (Physical Broadcast Channel), PDCCH, and PDSCH may be used.

[0172] The PBCH may be used to transmit a MIB (Master Information Block) and/or physical layer control information. The physical layer control information is a kind of downlink control information. The PBCH may be sent to deliver the MIB and/or the physical layer control information. A BCH may be mapped (or corresponding) to the PBCH. The terminal device 1 may receive the PBCH. The base station device 3 may transmit the PBCH. The physical layer control information is also referred to as a PBCH payload and a PBCH payload related to timing. The MIB may include one or more higher- layer parameters.

[0173] Physical layer control information includes 8 bits. The physical layer control information may include at least part or all of 0A to 0D. The 0A is radio frame information The 0B is half radio frame information (half system frame information). The 0C is SS/PBCH block index information. The OD is subcarrier offset information. [0174] The radio frame information is used to indicate a radio frame in which the PBCH is transmitted (a radio frame including a slot in which the PBCH is transmitted). The radio frame information is represented by 4 bits. The radio frame information may be represented by 4 bits of a radio frame indicator. The radio frame indicator may include 10 bits. For example, the radio frame indicator may at least be used to identify a radio frame from index 0 to index 1023.

[0175] The half radio frame information is used to indicate whether the PBCH is transmitted in first five subframes or in second five subframes among radio frames in which the PBCH is transmitted. Here, the half radio frame may be configured to include five subframes. The half radio frame may be configured by five subframes of the first half of ten subframes included in the radio frame. The half radio frame may be configured by five subframes in the second half of ten subframes included in the radio frame.

[0176] The SS/PBCH block index information is used to indicate an SS/PBCH block index. The SS/PBCH block index information may be represented by 3 bits. The SS/PBCH block index information may consist of 3 bits of an SS/PBCH block index indicator. The SS/PBCH block index indicator may include 6 bits. The SS/PBCH block index indicator may at least be used to identify an SS/PBCH block from index 0 to index 63 (or from index 0 to index 3, from index 0 to index 7, from index 0 to index 9, from index 0 to index 19, etc.).

[0177] The subcarrier offset information is used to indicate subcarrier offset. The subcarrier offset information may be used to indicate the difference between the first subcarrier in which the PBCH is arranged and the first subcarrier in which the control resource set with index 0 is arranged. [0178] A PDCCH may be used to transmit downlink control information (DCI). A PDCCH may be transmitted to deliver downlink control information. Downlink control information may be mapped to a PDCCH. The terminal device 1 may receive a PDCCH in which downlink control information is arranged. The base station device 3 may transmit the PDCCH in which the downlink control information is arranged.

[0179] Downlink control information may correspond to a DCI format. Downlink control information may be included in a DCI format. Downlink control information may be arranged in each field of a DCI format.

[0180] DCI format is a generic name for DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1. Uplink DCI format is a generic name of the DCI format 0_0 and the DCI format 0_1. Downlink DCI format is a generic name of the DCI format 1_0 and the DCI format 1_1.

[0181] The DCI format 0_0 is at least used for scheduling a PUSCH for a cell (or a PUSCH arranged on a cell). For example, the DCI format 0_0 may include at least a part or all of certain fields. For example, one of the certain fields may be a DCI format identification field (Identifier field for DCI formats). For example, one of the certain fields may be a frequency domain resource assignment field. For example, one of the certain fields may be a time domain resource assignment field. For example, one of the certain fields may be a frequency-hopping flag field. For example, one of the certain fields may be an MCS field (Modulation-and-Coding-Scheme field).

[0182] Frequency domain resource assignment field may be referred to as FDRA field or FDRA information field.

[0183] Time domain resource assignment field may be referred to as TDRA field or TDRA information field. [0184] The DCI format identification field may indicate whether the DCI format including the DCI format identification field is an uplink DCI format or a downlink DCI format. The DCI format identification field included in the DCI format 0_0 may indicate 0 (or may indicate that the DCI format 0_0 is an uplink DCI format).

[0185] The frequency domain resource assignment field included in the DCI format 0_0 may be at least used to indicate the assignment (allocation) of frequency resources for a PUSCH. The frequency domain resource assignment field included in the DCI format 0_0 may be at least used to indicate the assignment (allocation) of frequency resources for a PUSCH scheduled by the DCI format 0_0.

[0186] The time domain resource assignment field included in the DCI format 0_0 may be at least used to indicate the assignment of time resources for a PUSCH. The time domain resource assignment field included in the DCI format 0_0 may be at least used to indicate the assignment of time resources for a PUSCH scheduled by the DCI format 0_0. [0187] The frequency-hopping flag field may be at least used to indicate whether frequency-hopping is applied to a PUSCH. The frequency-hopping flag field may be at least used to indicate whether frequency-hopping is applied to a PUSCH scheduled by the DCI format 0_0.

[0188] The MCS field included in the DCI format 0_0 may be at least used to indicate a modulation scheme for a PUSCH and/or a part or all of a target coding rate for the PUSCH. The MCS field included in the DCI format 0_0 may be at least used to indicate a modulation scheme for a PUSCH scheduled by the DCI format 0_0 and/or a part or all of a target coding rate for the PUSCH. A size of a transport block (TBS: Transport Block Size) of a PUSCH may be given based at least on a target coding rate and a part or all of a modulation scheme for the PUSCH. The modulation scheme may include at least one of modulation order, target code rate and spectral efficiency.

[0189] The DCI format 0_0 may not include fields used for a CSI request. That is, CSI may not be requested by the DCI format 0_0.

[0190] The DCI format 0_0 may not include a carrier indicator field. An uplink component carrier on which a PUSCH scheduled by the DCI format 0_0 is arranged may be the same as an uplink component carrier on which a PDCCH including the DCI format 0_0 is arranged.

[0191] The DCI format 0_0 may not include a BWP field. An uplink BWP on which a PUSCH scheduled by the DCI format 0_0 is arranged may be the same as an uplink BWP on which a PDCCH including the DCI format 0_0 is arranged.

[0192] The DCI format 0_1/0_2 is at least used for scheduling of a PUSCH for a cell (or arranged on a cell). The DCI format 0_1/0_2 includes at least a part or all of fields 2A to 2H, respectively. The 2A is a DCI format identification field. The 2B is a frequency domain resource assignment field. The 2C is a time domain resource assignment field. The 2D is a frequency-hopping flag field. The 2E is an MCS field. The 2F is a CSI request field. The 2G is a BWP field. The 2H is a carrier indicator field.

[0193] The DCI format 1_0 is at least used for scheduling of a PDSCH for a cell (arranged on a cell). The DCI format 1_0 includes at least a part or all of fields 3A to 3F. The 3A is a DCI format identification field. The 3B is a frequency domain resource assignment field. The 3C is a time domain resource assignment field. The 3D is an MCS field. The 3E is a PDSCH-to-HARQ-feedback indicator field. The 3F is a PUCCH resource indicator field. [0194] The DCI format 1_0 may not include the carrier indicator field. A downlink component carrier on which a PDSCH scheduled by the DCI format 1_0 is arranged may be the same as a downlink component carrier on which a PDCCH including the DCI format 1_0 is arranged.

[0195] The DCI format 1_0 may not include the BWP field. A downlink BWP on which a PDSCH scheduled by a DCI format 1_0 is arranged may be the same as a downlink BWP on which a PDCCH including the DCI format I_0 is arranged.

[0196] The DCI format 1_1 is at least used for scheduling of a PDSCH for a cell (or arranged on a cell). The DCI format 1_1 includes at least a part or all of fields 4A to 4H. The 4A is a DCI format identification field. The 4B is a frequency domain resource assignment field. The 4C is a time domain resource assignment field. The 4D is an MCS field. The 4E is a PDSCH-to-HARQ-feedback indicator field. The 4F is a PUCCH resource indicator field. The 4G is a BWP field. The 4H is a carrier indicator field.

[0197] The DCI format identification field included in the DCI format 1_1 may indicate 1 (or may indicate that the DCI format 1_1 is a downlink DCI format).

[0198] The frequency domain resource assignment field included in the DCI format 1_1 may be at least used to indicate the assignment of frequency resources for a PDSCH. The frequency domain resource assignment field included in the DCI format 1_0 may be at least used to indicate the assignment of frequency resources for a PDSCH scheduled by the DCI format 1_1.

[0199] The time domain resource assignment field included in the DCI format 1_1 may be at least used to indicate the assignment of time resources for a PDSCH. The time domain resource assignment field included in the DCI format 1_1 may be at least used to indicate the assignment of time resources for a PDSCH scheduled by the DCI format 1_1. [0200] The MCS field included in the DCI format 1_1 may be at least used to indicate a modulation scheme for a PDSCH and/or a part or all of a target coding rate for the PDSCH. The MCS field included in the DCI format 1_1 may be at least used to indicate a modulation scheme for a PDSCH scheduled by the DCI format 1_1 and/or a part or all of a target coding rate for the PDSCH.

[0201] When the DCI format 1_1 includes a PDSCH-to-HARQ-feedback timing indicator field, the PDSCH-to-HARQ-feedback timing indicator field indicates an offset (KI) from a slot including the last OFDM symbol of a PDSCH scheduled by the DCI format 1_1 to another slot including the first OFDM symbol of a PUCCH triggered by the DCI format 1_1. When the DCI format 1_1 does not include the PDSCH-to-HARQ- feedback timing indicator field, an offset from a slot in which the last OFDM symbol of a PDSCH scheduled by the DCI format 1_1 is included to another slot in which the first OFDM symbol of a PUCCH triggered by the DCI format 1_1 is identified by a higher- layer parameter.

[0202] When the DCI format 1_1 includes the BWP field, the BWP field may be used to indicate a downlink BWP on which a PDSCH scheduled by the DCI format 1_1 is arranged. When the DCI format 1_1 does not include the BWP field, a downlink BWP on which a PDSCH is arranged may be the active downlink BWP. When the number of downlink BWPs configured in the terminal device 1 in a downlink component carrier is two or more, the number of bits for the BWP field included in the DCI format 1_1 used for scheduling a PDSCH arranged on the downlink component carrier may be one or more. When the number of downlink BWPs configured in the terminal device 1 in a downlink component carrier is one, the number of bits for the BWP field included in the DCI format 1_1 used for scheduling a PDSCH arranged on the downlink component carrier may be zero.

[0203] If the DCI format 1_1 includes the carrier indicator field, the carrier indicator field may be used to indicate a downlink component carrier (or a serving cell) on which a PDSCH is arranged. When the DCI format 1_1 does not include the carrier indicator field, a downlink component carrier (or a serving cell) on which a PDSCH is arranged may be the same as a downlink component carrier (or a serving cell) on which a PDCCH including the DCI format 1_1 used for scheduling of the PDSCH is arranged. When the number of downlink component carriers (or the number of serving cells) configured in the terminal device 1 in a serving cell group is two or more (when downlink carrier aggregation is operated in a serving cell group), or when cross-carrier scheduling is configured for the serving cell group, the number of bits for the carrier indicator field included in the DCI format 1_1 used for scheduling a PDSCH arranged on the serving cell group may be one or more (e.g., 3). When the number of downlink component carriers (or the number of serving cells) configured in the terminal device 1 in a serving cell group is one (or when downlink carrier aggregation is not operated in a serving cell group), or when the cross-carrier scheduling is not configured for the serving cell group, the number of bits for the carrier indicator field included in the DCI format 1_1 used for scheduling of a PDSCH arranged on the serving cell group may be zero.

[0204] A PDSCH may be used to transmit one or more transport blocks. A PDSCH may be used to transmit one or more transport blocks which corresponds to a DL-SCH. A PDSCH may be used to convey one or more transport blocks. A PDSCH may be used to convey one or more transport blocks which corresponds to a DL-SCH. One or more transport blocks may be arranged in a PDSCH. One or more transport blocks which corresponds to a DL-SCH may be arranged in a PDSCH. The base station device 3 may transmit a PDSCH. The terminal device 1 may receive the PDSCH.

[0205] Downlink physical signals may correspond to a set of resource elements. The downlink physical signals may not carry the information generated in the higher-layer. The downlink physical signals may be physical signals used in the downlink component carrier. A downlink physical signal may be transmitted by the base station device 3. The downlink physical signal may be transmitted by the terminal device 1. In the wireless communication system according to one aspect of the present embodiment, at least a part or all of an SS (Synchronization signal), DLDMRS (DownLink DeModulation Reference Signal), CSI-RS (Channel State Information-Reference Signal), and DL PTRS (DownLink Phase Tracking Reference Signal) may be used.

[0206] The synchronization signal may be used at least for the terminal device 1 to synchronize in the frequency domain and/or time domain for downlink. The synchronization signal is a generic name of PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal).

[0207] Figure 8 is a diagram showing a configuration example of an SS/PBCH block according to an aspect of the present embodiment. In Figure 8 the horizontal axis indicates time domain (OFDM symbol index l_Sym), and the vertical axis indicates frequency domain. The shaded blocks indicate a set of resource elements for a PSS. The blocks of grid lines indicate a set of resource elements for an SSS. Also, the blocks in the horizontal line indicate a set of resource elements for a PBCH and a set of resource elements for a DMRS for the PBCH (DMRS related to the PBCH, DMRS included in the PBCH, DMRS which corresponds to the PBCH). [0208] As shown in Figure 8, the SS/PBCH block includes a PSS, an SSS, and a PBCH, The SS/PBCH block includes 4 consecutive OFDM symbols. The SS/PBCH block includes 240 subcarriers. The PSS is allocated to the 57th to 183rd subcarriers in the first OFDM symbol. The SSS is allocated to the 57th to 183rd subcarriers in the third OFDM symbol. The first to 56th subcarriers of the first OFDM symbol may be set to zero. The 184th to 240th subcarriers of the first OFDM symbol may be set to zero. The 49th to 56th subcarriers of the third OFDM symbol may be set to zero. The 184th to 192nd subcarriers of the third OFDM symbol may be set to zero. In the first to 240th subcarriers of the second OFDM symbol, the PBCH is allocated to subcarriers in which the DMRS for the PBCH is not allocated. In the first to 48th subcarriers of the third OFDM symbol, the PBCH is allocated to subcarriers in which the DMRS for the PBCH is not allocated. In the 193rd to 240th subcarriers of the third OFDM symbol, the PBCH is allocated to subcarriers in which the DMRS for the PBCH is not allocated. In the first to 240th subcarriers of the 4th OFDM symbol, the PBCH is allocated to subcarriers in which the DMRS for the PBCH is not allocated.

[0209] The antenna ports of a PSS, an SSS, a PBCH, and a DMRS for the PBCH in an SS/PBCH block may be identical.

[0210] A PBCH may be estimated from a DMRS for the PBCH .For the DM-RS for the PBCH, the channel over which a symbol for the PBCH on an antenna port is conveyed can be inferred from the channel over which another symbol for the DM-RS on the antenna port is conveyed only if the two symbols are within a SS/PBCH block transmitted within the same slot, and with the same SS/PBCH block index.

[0211] DL DMRS is a generic name of DMRS for a PBCH, DMRS for a PDSCH, and DMRS for a PDCCH. [0212] A set of antenna ports for a DMRS for a PDSCH (a DMRS associated with a PDSCH, a DMRS included in a PDSCH, a DMRS which corresponds to a PDSCH) may be given based on the set of antenna ports for the PDSCH. The set of antenna ports for the DMRS for the PDSCH may be the same as the set of antenna ports for the PDSCH.

[0213] Transmission of a PDSCH and transmission of a DMRS for the PDSCH may be indicated (or scheduled) by one DCI format. The PDSCH and the DMRS for the PDSCH may be collectively referred to as PDSCH. Transmitting a PDSCH may be transmitting a PDSCH and a DMRS for the PDSCH.

[0214] A PDSCH may be estimated from a DMRS for the PDSCH. For a DM-RS associated with a PDSCH, the channel over which a symbol for the PDSCH on one antenna port is conveyed can be inferred from the channel over which another symbol for the DM-RS on the antenna port is conveyed only if the two symbols are within the same resource as the scheduled PDSCH, in the same slot, and in the same PRG (Precoding Resource Group).

[0215] Antenna ports for a DMRS for a PDCCH (a DMRS associated with a PDCCH, a DMRS included in a PDCCH, a DMRS which corresponds to a PDCCH) may be the same as an antenna port for the PDCCH.

[0216] A PDCCH may be estimated from a DMRS for the PDCCH. For a DM-RS associated with a PDCCH, the channel over which a symbol for the PDCCH on one antenna port is conveyed can be inferred from the channel over which another symbol for the DM-RS on the same antenna port is conveyed only if the two symbols are within resources for which the UE may assume the same precoding being used (i.e. within resources in a REG bundle). [0217] A BCH, a UL-SCH and a DL-SCH are transport channels. A channel used in the MAC layer is called a transport channel. A unit of transport channel used in the MAC layer is also called transport block (TB) or MAC PDU (Protocol Data Unit). In the MAC layer, control of HARQ (Hybrid Automatic Repeat request) is performed for each transport block. The transport block is a unit of data delivered by the MAC layer to the physical layer. In the physical layer, transport blocks are mapped to codewords and modulation processing is performed for each codeword.

[0218] One UL-SCH and one DL-SCH may be provided for each serving cell. BCH may be given to PCell. BCH may not be given to PSCell and SCell.

[0219] A BCCH (Broadcast Control Channel), a CCCH (Common Control Channel), and a DCCH (Dedicated Control Channel) are logical channels. The BCCH is a channel of the RRC layer used to deliver MIB or system information. The CCCH may be used to transmit a common RRC message in a plurality of terminal devices 1. The CCCH may be used for the terminal device 1 which is not connected by RRC. The DCCH may be used at least to transmit a dedicated RRC message to the terminal device 1. The DCCH may be used for the terminal device 1 that is in RRC-connected mode.

[0220] The RRC message may include one or more RRC parameters (information elements, higher layer parameters). For example, the RRC message may include a master information block (MIB). For example, the RRC message may include system information (e.g., system information block (SIB)). SIB is a generic name for various type of SIBs (e.g., SIB1, SIB2, ...). For example, the RRC message may include a message which corresponds to a CCCH. For example, the RRC message may include a message which corresponds to a DCCH. RRC message is a general term for common RRC message and dedicated RRC message. [0221] The BCCH in the logical channel may be mapped to the BCH or the DL-SCH in the transport channel. The CCCH in the logical channel may be mapped to the DL- SCH or the UL-SCH in the transport channel. The DCCH in the logical channel may be mapped to the DL-SCH or the UL-SCH in the transport channel.

[0222] The UL-SCH in the transport channel may be mapped to a PUSCH in the physical channel. The DL-SCH in the transport channel may be mapped to a PDSCH in the physical channel. The BCH in the transport channel may be mapped to a PBCH in the physical channel.

[0223] A higher-layer parameter is a parameter included in an RRC message or a MAC CE (Medium Access Control Control Element). The higher-layer parameter is a generic name of information included in a MIB, system information, a message which corresponds to CCCH, a message which corresponds to DCCH, and a MAC CE. A higher- layer parameter may be referred to as an RRC parameter or an RRC configuration if the higher-layer parameter is the parameter included in the RRC message.

[0224] A higher-layer parameter may be a cell-specific parameter or a UE-specific parameter. A cell-specific parameter is a parameter including a common configuration in a cell. A UE-specific parameter is a parameter including a configuration that may be configured differently for each UE.

[0225] The base station device may indicate change of cell-specific parameters by reconfiguration with random-access. The UE may change cell-specific parameters before triggering random-access. The base station device may indicate change of UE-specific parameters by reconfiguration with or without random-access. The UE may change UE- specific parameters before or after random-access. [0226] The procedure performed by the terminal device 1 includes at least a part or all of the following 5 A to 5C. The 5 A is cell search. The 5B is random-access. The 5C is data communication.

[0227] The cell search is a procedure used by the terminal device 1 to synchronize with a cell in the time domain and/or the frequency domain and to detect a physical cell identity. The terminal device 1 may detect the physical cell ID by performing synchronization of time domain and/or frequency domain with a cell by the cell search.

[0228] A sequence of a PSS is given based at least on a physical cell ID. A sequence of an SSS is given based at least on the physical cell ID.

[0229] An SS/PBCH block candidate indicates a resource for which transmission of the SS/PBCH block may exist. An SS/PBCH block may be transmitted at a resource indicated as the SS/PBCH block candidate. The base station device 3 may transmit an SS/PBCH block at an SS/PBCH block candidate. The terminal device 1 may receive (detect) the SS/PBCH block at the SS/PBCH block candidate.

[0230] A set of SS/PBCH block candidates in a half radio frame is also referred to as an SS-burst-set. The SS-burst-set is also referred to as a transmission window, a SS transmission window, or a DRS transmission window (Discovery Reference Signal transmission window). The SS-burst-set is a generic name that includes at least a first SS- burst-set and a second SS-burst-set.

[0231] The base station device 3 transmits SS/PBCH blocks of one or more indexes at a predetermined cycle. The terminal device 1 may detect an SS/PBCH block of at least one of the SS/PBCH blocks of the one or more indexes. The terminal device 1 may attempt to decode the PBCH included in the SS/PBCH block. [0232] Data communication is a generic term for downlink communication and uplink communication.

[0233] In data communication, the terminal device 1 attempts to detect a PDCCH (attempts to monitor a PDCCH, monitors a PDCCH). in a resource identified at least based on one or all of a control resource set and a search-space-set. It’s also called as “the terminal device 1 attempts to detect a PDCCH in a control resource set”, “the terminal device 1 attempts to detect a PDCCH in a search-space-set”, “the terminal device 1 attempts to detect a PDCCH candidate in a control resource set”, “the terminal device 1 attempts to detect a PDCCH candidate in a search-space-set”, “the terminal device 1 attempts to detect a DCI format in a control resource set”, or “the terminal device 1 attempts to detect a DCI format in a search-space-set”. Monitoring a PDCCH may be equivalent as monitoring a DCI format in the PDCCH.

[0234] The control resource set is a set of resources configured by the number of resource blocks and a predetermined number of OFDM symbols in a slot.

[0235] The set of resources for the control resource set may be indicated by higher- layer parameters. The number of OFDM symbols included in the control resource set may be indicated by higher-layer parameters.

[0236] A PDCCH may be also called as a PDCCH candidate.

[0237] A search-space-set is defined as a set of PDCCH candidates. A search-space- set may be a Common Search Space (CSS) set or a UE-specific Search Space (USS) set. [0238] The CSS set is a generic name of a type-0 PDCCH common search-space-set, a type-Oa PDCCH common search-space-set, a type-1 PDCCH common search-space-set, a type-2 PDCCH common search-space-set, and a type-3 PDCCH common search-space- set, The USS set may be also called as UE-specific PDCCH search-space-set. [0239] The type-0 PDCCH common search-space-set may be used as a common search-space-set with index 0. The type-0 PDCCH common search-space-set may be an common search-space-set with index 0.

[0240] The type-0 PDCCH common search-space-set may be at least used for a DCI format with a cyclic redundancy check (CRC) sequence scrambled by an SI-RNTI (System Information-Radio Network Temporary Identifier).

[0241] The type-Oa PDCCH common search-space-set may be used at least for a DCI format with a cyclic redundancy check sequence scrambled by an SI-RNTI.

[0242] The type-1 PDCCH common search-space-set may be used at least for a DCI format with a CRC sequence scrambled by an RA-RNTI (Random Access-Radio Network Temporary Identifier) or a CRC sequence scrambled by a TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).

[0243] The type-2 PDCCH common search-space-set may be used for a DCI format with a CRC sequence scrambled by P-RNTI (Paging-Radio Network Temporary Identifier).

[0244] The type-3 PDCCH common search-space-set may be used for a DCI format with a CRC sequence scrambled by a C-RNTI (Cell-Radio Network Temporary Identifier).

[0245] The UE-specific search-space-set may be used at least for a DCI format with a CRC sequence scrambled by a C-RNTI.

[0246] In downlink communication, the terminal device 1 may detect a downlink DCI format. The detected downlink DCI format is at least used for resource assignment for a PDSCH. The detected downlink DCI format is also referred to as downlink assignment. The terminal device 1 attempts to receive the PDSCH. Based on a PUCCH resource indicated based on the detected downlink DCI format, an HARQ-ACK corresponding to the PDSCH (HARQ-ACK corresponding to a transport block included in the PDSCH) may be reported to the base station device 3.

[0247] In uplink communication, the terminal device 1 may detect an uplink DCI format. The detected uplink DCI format is at least used for resource assignment for a PUSCH. The detected uplink DCI format is also referred to as uplink grant. The terminal device 1 transmits the PUSCH.

[0248] PUSCH transmission(s) can be dynamically scheduled by an UL grant in a DCI, or the transmission can correspond to a configured grant Type 1 or Type 2. The configured grant Type 1 PUSCH transmission is semi-statically configured to operate upon the reception of higher layer parameter of configuredGrantConfig including rrc- ConfiguredUplinkGrant without the detection of an UL grant in a DCI. The configured grant Type 2 PUSCH transmission is semi-persistently scheduled by an UL grant in a valid activation DCI according to those procedure(s) after the reception of higher layer parameter configuredGrantConfig not including rrc-ConfiguredUplinkGrant. If configuredGrantConfigToAddModList is configured, more than one configured grant configuration of configured grant Type 1 and/or configured grant Type 2 may be active at the same time on an active BWP of a serving cell.

[0249] More details of resource allocation in time domain for PUSCH scheduled by a DCI format is described. When the UE (terminal device 1) is scheduled to transmit a transport block and no CSI report, or the UE is scheduled to transmit a transport block and a CSI report(s) on PUSCH by a DCI, the 'Time domain resource assignment' field value m of the DCI may provide a row index m + 1 to an allocated table. The determination of the used resource allocation table may be pre-defined and/or defined in RRC configuration. The indexed row of the resource allocation table may define the slot offset K2, the start and length indicator SLIV, or directly the start symbol S and the allocation length L, the PUSCH mapping type, and the number of repetitions (if RRC parameter numberOfRepetitions is present in the resource allocation table) to be applied in the PUSCH transmission. It is noted that RRC parameter is a kind of high-layer parameter.

[0250] A UE may not expect to be scheduled to transmit a PUCCH or a PUSCH with smaller priority index that would overlap in time with a PUCCH of larger priority index with HARQ-ACK information only in response to a PDSCH reception without a corresponding PDCCH. A UE may not expect to be scheduled to transmit a PUCCH of smaller priority index that would overlap in time with a PUSCH of larger priority index with SP-CSI report(s) without a corresponding PDCCH.

[0251] If a UE multiplexes aperiodic CSI in a PUSCH and the UE would multiplex UCI that includes HARQ-ACK information in a PUCCH that overlaps with the PUSCH and the timing conditions for overlapping PUCCHs and PUSCHs are fulfilled, the UE may multiplex only the HARQ-ACK information in the PUSCH and does not transmit the PUCCH.

[0252] Figure 9 is an example configuration of a frame structure according to an aspect of the present embodiment. In Figure 9, a horizontal axis indicates time domain. In the time domain, slots are numbered from slot#n (slot with index n) in ascending order. Each line in the time domain indicates a slot boundary. 9001 indicates a downlink region. 9002 indicates a flexible region. 9003 indicates an uplink region.

[0253] Region indicated by 9000 includes a set of region 9001, 9002 and 9003. Region 9000 may be configured based on a slot configuration. For example, a slot configuration may include at least a downlink region, a flexible region and an uplink region. For example, a slot configuration may be configured such that the slot configuration starts at one UL-to-DL switching point. Further, the slot configuration may be configured such that the slot configuration ends at another UL-to-DL switching point. For example, a UL-to-DL switching point may be a point where a uplink region ends and a downlink region starts.

[0254] For example, a slot configuration may be repeated in the time domain. In Figure 9, a slot configuration comprising 3 downlink slots, one special slot and 1 uplink slot is repeated. Region 9000 is an instance of the slot configuration starting at slot#n and a Region 9010 is an instance of the slot configuration starting at slot#n+5. In Figure 9, repetition cycle of the slot configuration is 5 slots.

[0255] 9011 indicates a downlink region. Further, 9012 indicates a flexible region.

Further, 9013 indicates an uplink region.

[0256] For example, a slot configuration may be represented by a combination of ‘D’, ‘U’ and ‘S’. ‘D’ indicates that a slot is a downlink slot. A downlink slot is a slot with downlink region. In Figure 9, slot#n, slot#n+l, slot#n+2, slot#n+5, slot#n+6 and slot#n+7 are downlink slots.

[0257] U’ indicates that a slot is an uplink slot. An uplink slot is a slot with uplink region. In Figure 9, slot#n+4 and slot#n+9 are uplink slots.

[0258] ^!S ’ indicates that a slot is a special slot. A special slot is a slot with at least two or more of a downlink region, a flexible region and an uplink region. In Figure 9, slot#n+3 and slot#n+8 are special slots. [0259] In Figure 9, the slot configuration may be also referred to as “DDDSU”. “DDDSU” means that the slot configuration comprises 3 downlink slots, 1 special slot and 1 uplink slot.

[0260] A configuration of special slot may be represented by “XDYFZU”. Here, X is the number of downlink symbols, Y is the number of flexible symbols and Z is the number of uplink symbols. For example, “10D2F2U” indicates that a special slot comprises 10 downlink symbols, 2 flexible symbols and 2 uplink symbols.

[0261] A downlink symbol is an OFDM symbol in a downlink region. A flexible symbol is an OFDM symbol in a flexible region. An uplink symbol is an OFDM symbol in an uplink region.

[0262] A slot configuration may be provided by RRC parameters. For example, a slot configuration may be configured by a common parameter included in system information such as SIB1. The common parameter may be also referred to as tdd-UL-DL- ConfigurationCommon.

[0263] For example, terminal device 1 may determine a reference subcarrier-spacing configuration u_ref and a first TDD pattern from the common parameter. The first TDD pattern includes one or more of T1 to T5. T1 is a configuration period P in milliseconds provided by referenceSubcarrierSpacing. T2 is the number d_slots of slots indicating consecutive downlink slots provided by nrofDownlinkSlots. T3 is the number d_sym of consecutive downlink symbols provided by nrofDownlinkSymbols. T4 is the number u_slots of consecutive uplink slots provided by nrofUplinkSlots. T5 is the number u_sym of consecutive uplink symbols provided by nrofUplinkSymbols.

[0264] Figure 10 is an example configuration of a slot configuration according to an aspect of the present embodiment. In Figure 10, a horizontal axis indicates time domain. In the time domain, slots are numbered from slot#n (slot with index n) in ascending order. Each line in the time domain indicates a slot boundary. 10000 indicates a slot configuration. In the slot configuration, first d_slots=2 slots as indicated by Region 10001 are configured as downlink slots. In the slot configuration, last u_slots=l slot as indicated by Region 10002 is configured as an uplink slot. In the slot configuration, first d_sym OFDM symbols starting at first OFDM symbol in a slot with index n+d_slots as indicated by Region 10003 is configured as downlink symbols. In the slot configuration, last u_sym OFDM symbols before first OFDM symbol in a slot with index n+S-u_slots as indicated by Region 10004 is configured as uplink symbols. In the slot configuration, the remaining OFDM symbols not indicated as either downlink region or uplink region as indicated by Region 1005 are flexible symbols.

[0265] A slot configuration may be modified by a UE-specific parameter. The UE- specific parameter may be also referred to as tdd-UL-DL-ConfigurationDedicated.

[0266] If the UE-specific parameter is provided to terminal device 1 , the UE-specific parameter may modify (or reconfigure) the slot configuration provided by the common parameter. For example, the UE-specific parameter may modify (or reconfigure) flexible region in the slot configuration.

[0267] For example, terminal device 1 may determine a list including a set of slot reconfigurations by the UE-specific parameter. In each slot reconfiguration in the set, at least one or both of an index of a slot and an indication of TDD pattern of the slot may be provided. The indication may indicate one out of ‘all DL’, ‘all UL’ and ‘explicit’. In a case that ‘all DL’ is indicated for the slot, the slot configuration in the slot is reconfigured as downlink region. In a case that ‘all UL’ is indicated for the slot, the slot configuration in the slot is reconfigured as uplink region. In a case that ‘explicit’ is indicated for the slot, the slot configuration in the slot is reconfigured by explicit indication corresponding to ‘explicit’. Indication ‘explicit’ corresponds to information indicating a TDD pattern in a slot. The information includes information indicating the number of downlink symbols starting at the beginning of the slot and information indicating the number of uplink symbols ending at the end of the slot. The remaining OFDM symbols between downlink symbols and uplink symbols are flexible symbols.

[0268] Terminal device 1 may receive a physical signal if terminal device 1 is configured by a higher layer or indicated by a DO format to receive the physical signal in the downlink region.

[0269] Terminal device 1 may transmit a physical signal if terminal device 1 is configured by a higher layer or indicated by a DCI format to transmit the physical signal in the uplink region.

[0270] Figure 11 is an example of the inference procedure (prediction procedure) for channel measurement(s) according to an aspect of the present embodiment. For generating the input of prediction model for channel measurement, it may need some further pre-processing on the measured channel. For the output of the prediction model, some further post-processing may also be applied.

[0271] If the channel measurement is used for computing the CSI value, for the evaluation of the AI/ML based CSI prediction, the UE 1 may report the structure of the AI/ML model and/or the input CSI type and/or the output CSI type and/or the Data pre- processing/post-processing and/or Loss function.

[0272] The structure of the AI/ML model may include any of raw channel matrix, eigenvector(s) of the raw channel matrix, feedback CSI information. [0273] The input CSI type may include raw channel matrices and/or the eigenvector(s).

[0274] If the inference procedure for the channel measurement is used for beam management for BM-Casel and/or BM-Case2, the UE may perform measurements based on Set B of beams are used as model input. In other words, the inference procedure may be used for beam prediction. Here, beam prediction may include any of DL Tx beam prediction, DL Rx beam prediction, and/or beam pair prediction. In addition, beam ID information may be also provided as input to the AI/ML model. Based on model output (e.g., probability of each beam in Set A to be the Top-1 beam, predicted LI -RSRPs), Top- l/N beam(s) among Set A of beams may be predicted and/or potentially with predicted LI -RSRPs (depending on the labeling) (i.e., measurement result prediction, RSRP prediction). In the evaluation, for BM-Case 1, the measurements of Set B (otherwise stated) are used as model input to predict Top-l/N beams from Set A, and for BM-Case2, the measurements from historic time instance(s) are used as model input for temporal DL beam prediction of beams from Set A. In the evaluation, the cases that Set A and Set B are different (Set B is NOT a subset of Set A), and Set B is a subset of Set A for both BM- Casel and BM-Case2, and case that Set A and Set B are the same for BM-Case2 are considered. And the performance of DL Tx beam prediction and DL Tx-Rx beam pair prediction is evaluated. For both BM-Casel and BM-Case2, the UE 1 may report the prediction result to NW based on the output of a UE-side model, or NW may predict the Top-l/N beam(s) based on the reported measurements of Set B for a NW-side model.

[0275] The BM-Casel may be a case of spatial-domain DL beam prediction for Set A of beams based on measurement results of Set B of beams. [0276] The BM-Case2 may be a case of temporal DL beam prediction for Set A of beams based on the historic measurement results of Set B of beams.

[0277] If Set A and Set B are different (e.g., Set B is NOT a subset of Set A), resource types or beamwidths for Set A and Set B may be different. For example, a resource type for Set A may be a CSI-RS, and a resource type for Set B may be an SSB.

[0278] If Set A and Set B are same (e.g., Set B is a subset of Set A), resource types or beamwidths for Set A and Set B may be same.

[0279] Hereinafter, for the UE 1 and/or the network (including the gNB 3) being capable of the AI/ML, the measurement reporting procedure(s) based on the predicted value for channel measurement will be described.

[0280] The network may configure an RRC_CONNECTED UE to perform measurements. The network may configure the UE to report them in accordance with the measurement configuration or perform conditional reconfiguration evaluation in accordance with the conditional reconfiguration. The measurement configuration is provided by means of dedicated signalling i.e. using the RRCReconfiguration or RRCResume.

[0281] The network may configure the UE to perform the following types of measurements: NR measurements; Inter-RAT measurements of E-UTRA frequencies; Inter-RAT measurements of UTRA-FDD frequencies; and NR sidelink measurements of L2 U2N Relay UEs.

[0282] The network may configure the UE to report the following measurement information based on SS/PBCH block(s): Measurement results per SS/PBCH block; Measurement results per cell based on SS/PBCH block(s); and SS/PBCH block(s) indexes. [0283] The network may configure the UE to report the following measurement information based on CSI-RS resources: Measurement results per CSI-RS resource; Measurement results per cell based on CSI-RS resource(s); and CSI-RS resource measurement identifiers.

[0284] The network may configure the UE to report the following CLI measurement information based on SRS resources: Measurement results per SRS resource; and SRS resource(s) indexes.

[0285] The network may configure the UE to report the following CLI measurement information based on CLLRSSI resources: Measurement results per CLI-RSSI resource; and CLI-RSSI resource(s) indexes.

[0286] The network may configure the UE to report the following Rx-Tx time difference measurement information based on CSI-RS for tracking or PRS: UE Rx-Tx time difference measurement result.

[0287] The measurement configuration may include parameters associated with measurement objects, reporting configurations, measurement identities, quantity configurations and measurement gaps.

[0288] The measurement objects may be indicated by a list of objects on which the UE shall perform the measurements.

[0289] The reporting configurations may be indicated by a list of reporting configurations where there can be one or multiple reporting configurations per measurement object.

[0290] The measurement identities may be indicated by a list of measurement identities where each measurement identity links one measurement object with one reporting configuration, for measurement reporting. By configuring multiple measurement identities, it is possible to link more than one measurement object to the same reporting configuration, as well as to link more than one reporting configuration to the same measurement object. The measurement identity is also included in the measurement report that triggered the reporting, serving as a reference to the network. For conditional reconfiguration triggering, one measurement identity links to exactly one conditional reconfiguration trigger configuration. And up to 2 measurement identities can be linked to one conditional reconfiguration execution condition.

[0291] The quantity configurations may define the measurement filtering configuration used for all event evaluation and related reporting, and for periodical reporting of that measurement. For NR measurements, the network may configure up to 2 quantity configurations with a reference in the NR measurement object to the configuration that is to be used. In each configuration, different filter coefficients can be configured for different measurement quantities, for different RS types, and for measurements per cell and per beam.

[0292] The measurement gaps may be used as periods that the UE may use to perform measurements.

[0293] An RRC_CONNECTED UE shall derive cell measurement results by measuring one or multiple beams associated per cell as configured by the network. For all cell measurement results, except for RSSI, and CLI measurement results in RRC_CONNECTED, the UE applies the layer 3 filtering, before using the measured results for evaluation of reporting criteria, measurement reporting or the criteria to trigger conditional reconfiguration execution. For cell measurements, the network can configure RSRP, RSRQ, SINR, RSCP or EcNO as trigger quantity. For CLI measurements, the network can configure SRS-RSRP or CLI-RSSI as trigger quantity. For cell and beam measurements, reporting quantities can be any combination of quantities (i.e. , only RSRP; only RSRQ; only SINR; RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ and SINR; only RSCP; only EcNO; RSCP and EcNO), irrespective of the trigger quantity, and for CLI measurements, reporting quantities can be either SRS-RSRP or CLI- RSSI. For conditional reconfiguration execution, the network can configure up to 2 quantities, both using same RS type. The UE does not apply the layer 3 filtering to derive the CBR measurements. The UE does not apply the layer 3 filtering to derive the Rx-Tx time difference measurements.

[0294] The network may also configure the UE to report measurement information per beam (which can either be measurement results per beam with respective beam identifier(s) (beam ID) or only beam identifier(s)). If beam measurement information is configured to be included in measurement reports, the UE applies the layer 3 beam filtering. On the other hand, the exact LI filtering of beam measurements used to derive cell measurement results is implementation dependent.

[0295] The network may configure the UE in RRC_CONNECTED to derive RSRP, RSRQ and SINR measurement results per cell associated to NR measurement objects based on parameters configured in the measObject (e.g., maximum number of beams to be averaged and beam consolidation thresholds) and in the reportConfig (rsType to be measured, SS/PBCH block or CSI-RS).

[0296] The network may configure the UE in RRC_IDLE or in RRC_INACTIVE to derive RSRP and RSRQ measurement results per cell associated to NR carriers based on parameters configured in measIdleCarrierListNR within VarMeasIdleConfig for measurements performed. [0297] The UE may derive each configured beam measurement quantity based on SS/PBCH block and apply layer 3 (L3) beam filtering for each layer 3 beam filtered measurement quantity to be derived based on SS/PBCH block. The UE may derive each configured beam measurement quantity based on CSI-RS and apply layer 3 beam filtering for each layer 3 beam filtered measurement quantity to be derived based on CSI-RS.

[0298] If the UE supports a capable of the AI/ML, the UE may derive measurement quantity corresponding to a beam prediction and/or a measurement prediction and apply layer 3 filtering for the measurement quantity.

[0299] The UE may filter the measured result, before using for evaluation of reporting criteria by the following formula: F_n = (1 - a)*F_n-1 + a*M_n, where M_n is the latest received measurement result from the physical layer, F_n is the updated filtered measurement result, that is used for evaluation of reporting criteria, for measurement reporting, F_n-1 is the old filtered measurement result, where F₀ is set to M₁ when the first measurement result from the physical layer is received; and for MeasObjectNR, a = 1/2^(ki/4), where k_i is the filterCoefficient for the corresponding measurement quantity of the i-th QuantityConfigNR in quantityConfigNR-List, and i is indicated by quantityConfiglndex in MeasObjectNR-, for other measurements, a = 1/2^(k/ ₄₎, where k is the filterCoefficient for the corresponding measurement quantity received by the quantityConfig,- for UTRA-FDD, a = 1/2^(k/ ₄₎’ where k is the filterCoefficient for the corresponding measurement quantity received by quantityConfigUTRA-FDD in the QuantityConfig.

[0300] The UE may adapt the filter such that the time characteristics of the filter are preserved at different input rates, observing that the filterCoefficient k assumes a sample rate equal to X ms. The value of X is equivalent to one intra-frequency L1 measurement period assuming non-DRX operation and depends on frequency range. [0301] If k is set to 0, no layer 3 filtering may be applicable.

[0302] The filtering may be performed in the same domain as used for evaluation of reporting criteria, for measurement reporting i.e., logarithmic filtering for logarithmic measurements.

[0303] The filter input rate may be implementation dependent, to fulfil the performance requirements.

[0304] For CLI-RSSI measurement, it may be up to UE implementation whether to reset filtering upon BWP switch.

[0305] The quantityConfiglndex may be used for indicating the n-th element of quantityConfigNR-List provided in MeasConfig.

[0306] The MeasConfig may be used for specifying measurements to be performed by the UE, and covers intra-frequency, inter-frequency and inter-RAT mobility as well as configuration of measurement gaps.

[0307] The MeasObjectNR may be used for specifying information applicable for SS/PBCH block(s) intra/inter-frequency measurements and/or CSI-RS intra/inter- frequency measurements.

[0308] If the UE supports a capable of the AI/ML, the UE may assume that the k is set to 0, for one or more time resources within a certain period applying predicted value(s) obtained by a beam prediction and/or a measurement prediction. The UE may not perform layer 3 filtering in this case. The UE may not consider the old filtered measurement result in this case.

[0309] Alternatively or additionally, if the UE supports a capable of the AI/ML and the UE is configured with an RRC parameter filterCoefficient and/or quantityConfig (QuantityConfig') associated with a beam prediction and/or a measurement prediction, the UE may assume that the k is set based on the filterCoefficient and/or quantity Config associated with a beam prediction and/or a measurement prediction, for one or more time resources within a certain period applying predicted value(s) obtained by a beam prediction and/or a measurement prediction.

[0310] The gNB may provide RRC parameter filterCoefficient and/or quantity Config associated with a beam prediction and/or a measurement prediction for the UE supporting a capable of the AI/ML. The gNB may set the RRC parameter filterCoefficient to 0 if the RRC parameter filterCoefficient and/or quantityConfig are associated with a beam prediction and/or a measurement prediction.

[0311] This filtered RSRP may be referred to as higher layer filtered RSRP (layer 3 filtered RSRP). This filtered measurement result may be referred to as higher layer filtered measurement result (layer 3 filtered measurement result).

[0312] The QuantityConfig may be used for specifying the measurement quantities and layer 3 filtering coefficients for NR and inter-RAT measurements. The QuantityConfig may include quantityConfigCell and quantityConfigRS-Index. The quantityConfigCell may specify layer 3 filter configurations for cell measurement results for the configurable RS Types (e.g., SS/PBCH block and CSI-RS) and the configurable measurement quantities (e.g., RSRP, RSRQ and SINR). The quantityConfigRS-Index may specify layer 3 filter configurations for measurement results per RS index for the configurable RS Types (e.g., SS/PBCH block and CSI-RS) and the configurable measurement quantities (e.g., RSRP, RSRQ and SINR).

[0313] The filterCoefficient may be used for specifying the measurement filtering coefficient (e.g., layer 3 filter configurations for RSRP, RSRQ and SINR measurement results from the layer 1 (L1) filter(s)). [0314] The UE may initiate the measurement reporting procedure in a case that one or more conditions are fulfilled. For example, if a measurement result for a serving cell becomes better than a threshold (i.e., Event Al), the UE may initiate the measurement reporting procedure. For example, if a measurement result for a serving cell becomes worse than a threshold (i.e., Event A2), the UE may initiate the measurement reporting procedure. For example, if a measurement result for a neighbour cell becomes amount of offset better than a measurement result for PCell/SCell (i.e., Event A3), the UE may initiate the measurement reporting procedure. For example, if a measurement result for a neighbour cell becomes better than a threshold (i.e., Event A4), the UE may initiate the measurement reporting procedure. For example, if a measurement result for a neighbour cell becomes worse than a threshold, the UE may initiate the measurement reporting procedure. For example, if a measurement result for an SpCell becomes worse than a first threshold and a measurement result for a neighbour cell becomes better than a second threshold (i.e., Event A5), the UE may initiate the measurement reporting procedure. In other words, if the UE is satisfied with one or more certain condition for an Event, the UE may initiate the measurement reporting procedure. If the UE is configured with an RRC parameter ReportInterval indicating a report interval included in a report configuration, the UE may initiate the measurement reporting procedure periodically according to the report interval.

[0315] The RRC parameter Reportinterval may indicate the interval between periodical reports. The Reportinterval is applicable if the UE performs periodical reporting (i.e., when reportAmount exceeds 1) when reportType is set to either eventTriggered, periodical, cli-EventTriggered or cli-Periodical. [0316] The purpose of the measurement reporting procedure is to transfer measurement results from the UE to the network. The UE may initiate this procedure only after successful AS security activation. For the measld for which the measurement reporting procedure was triggered, the UE may set the measResults within the MeasurementReport message including certain information.

[0317] A UE 1 does not expect to be configured with a CSI-ReportConfig that is linked to a CSI-ResourceConfig containing an NZP-CSI-RS-ResourceSet configured with trs-Info and with the CSI-ReportConfig configured with the RRC layer parameter timeRestrictionForChannelMeasurements set to 'configured.

[0318] If the RRC layer parameter timeRestrictionForChannelMeasurements in CSI- ReportConfig is set to "notConfigured" , the UE 1 may derive the channel measurements for computing Ll-RSRP value reported in uplink slot n based on only the SS/PBCH or NZP CSI-RS, no later than the CSI reference resource, associated with the CSI resource setting.

[0319] If the RRC layer parameter timeRestrictionForChannelMeasurements in CSI- ReportConfig is set to "configured" , the UE 1 may derive the channel measurements for computing Ll-RSRP reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of SS/PBCH or NZP CSI-RS associated with the CSI resource setting.

[0320] When one or two resource settings are configured for Ll-SINR measurement, if the RRC layer parameter timeRestrictionForChannelMeasurements in CSI- ReportConfig is set to ’notConfigured' , the UE 1 may derive the channel measurements for computing Ll-SINR reported in uplink slot n based on only the SSB or NZP CSI-RS, no later than the CSI reference resource associated with the CSI resource seting. [0321] When one or two resource settings are configured for Ll-SINR measurement, if the RRC layer parameter timeRestrictionForChannelMeasurements in CSI- ReportConfig is set to 'configured', the UE 1 may derive the channel measurements for computing Ll-SINR reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of SSB or NZP CSI-RS associated with the CSI resource setting.

[0322] When one or two resource settings are configured for Ll-SINR measurement, if the RRC layer parameter timeRestrictionForlnterferenceMeasurements in CS1- ReportConfig is set to 'notConfigured' , the UE 1 may derive the interference measurements for computing Ll-SINR reported in uplink slot n based on only the CSI- IM or NZP CSI-RS for interference measurement or NZP CSI-RS for channel and interference measurement no later than the CSI reference resource associated with the CSI resource setting.

[0323] When one or two resource settings are configured for Ll-SINR measurement, if the RRC layer parameter timeRestrictionForlnterferenceMeasurements in CSI- ReportConfig is set to 'configured', the UE 1 may derive the interference measurements for computing the Ll-SINR reported in uplink slot n based on the most recent, no later than the CSI reference resource, occasion of CSI-IM or NZP CSI-RS for interference measurement or NZP CSI-RS for channel and interference measurement associated with the CSI resource setting.

[0324] If the RRC layer parameter timeRestrictionForChannelMeasurements is set to

"notConfigured” , the UE 1 may derive the channel measurements for computing CSI value reported in uplink slot n based on only the NZP CSI-RS, no later than the CSI reference resource associated with the CSI resource setting. [0325] If the RRC layer parameter timeRestrictionForChannelMeasurements in CSI- ReportConfig is set to "configured" , the UE 1 may derive the channel measurements for computing CSI reported in uplink slot n based on only the most recent, no later than the CSI reference resource, in cell discontinuous transmission (DTX) active time if cell DTX is activated, occasion of NZP CSI-RS associated with the CSI resource setting.

[0326] If the RRC layer parameter timeRestrictionForlnterferenceMeasurements is set to "notConfigured" , the UE 1 may derive the interference measurements for computing CSI value reported in uplink slot n based on only the CSI-IM and/or NZP CSI- RS for interference measurement no later than the CSI reference resource associated with the CSI resource setting.

[0327] If the RRC layer parameter timeRestrictionForlnterferenceMeasurements in CSI-ReportConfig is set to "configured" , the UE 1 may derive the interference measurements for computing the CSI value reported in uplink slot n based on the most recent, no later than the CSI reference resource, in cell DTX active time if cell DTX is activated, occasion of CSI-IM and/or NZP CSI-RS for interference measurement associated with the CSI resource setting.

[0328] The information element CSI-ReportConfig may be used to configure a periodic or semi-persistent report sent on PUCCH on the cell in which the CSI- ReportConfig is included, or to configure a semi-persistent or aperiodic report sent on PUSCH triggered by DCI received on the cell in which the CSI-ReportConfig is included (in this case, the cell on which the report is sent is determined by the received DCI).

[0329] For L1-RSRP computation, the UE 1 may be configured with CSI-RS resources, SS/PBCH Block resources or both CSI-RS and SS/PBCH block resources, when resource-wise quasi co-located with 'type C and 'typeD^' when applicable. And then the UE 1 may be configured with CSI-RS resource setting up to 16 CSI-RS resource sets having up to 64 resources within each set. The total number of different CSI-RS resources over all resource sets is no more than 128.

[0330] SS reference signal received power (SS-RSRP) is defined as the linear average over the power contributions (in [W]) of the resource elements that carry secondary synchronization signals. The measurement time resource(s) for SS-RSRP are confined within SS/PBCH Block Measurement Time Configuration (SMTC) window duration. If SS-RSRP is used for Ll-RSRP as configured by reporting configurations, the measurement time resources(s) restriction by SMTC window duration is not applicable.

[0331] CSI reference signal received power (CSI-RSRP), is defined as the linear average over the power contributions (in [W]) of the resource elements of the antenna port(s) that carry CSI reference signals configured for RSRP measurements within the considered measurement frequency bandwidth in the configured CSI-RS occasions. For CSI-RSRP determination CSI reference signals transmitted on antenna port 3000 may be used. If CSI-RSRP is used for Ll-RSRP, CSI reference signals transmitted on antenna ports 3000, 3001 can be used for CSI-RSRP determination.

[0332] For Ll-SINR computation, for channel measurement the UE 1 may be configured with NZP CSI-RS resources and/or SS/PBCH Block resources, for interference measurement the UE may be configured with NZP CSI-RS or CSI-IM resources.

[0333] SS signal-to-noise and interference ratio (SS-SINR), is defined as the linear average over the power contribution (in [W]) of the resource elements carrying secondary synchronization signals divided by the linear average of the noise and interference power contribution (in [W]). If SS-SINR is used for L1-SINR reporting with dedicated interference measurement resources, the interference and noise is measured over resource(s) indicated by higher layers. Otherwise, the interference and noise are measured over the resource elements carrying secondary synchronization signals within the same frequency bandwidth. The measurement time resource(s) for SS-SINR are confined within SS/PBCH Block Measurement Time Configuration (SMTC) window duration. If SS-SINR is used for Ll-SINR as configured by reporting configurations, the measurement time resources(s) restriction by SMTC window duration is not applicable.

[0334] CSI signal-to-noise and interference ratio (CSI-SINR), is defined as the linear average over the power contribution (in [W]) of the resource elements carrying CSI reference signals divided by the linear average of the noise and interference power contribution (in [W]). If CSI-SINR is used for Ll-SINR reporting with dedicated interference measurement resources, the interference and noise is measured over resource(s) indicated by higher layers. Otherwise, the interference and noise are measured over the resource elements carrying CSI reference signals within the same frequency bandwidth. For CSI-SINR determination CSI reference signals transmitted on antenna port 3000 may be used. If CSI-SINR is used for Ll-SINR, CSI reference signals transmitted on antenna ports 3000, 3001 may be used for CSI-SINR determination.

[0335] The RRC parameter timeRestrictionForChannelMeasurements may be used for performing time domain measurement restriction for the channel (signal) measurements. For channel measurement, the UE 1 may be configured with CSI-RS resource setting with up to 16 resource sets, with a total of up to 64 CSLRS resources or up to 64 SS/PBCH Block resources.

[0336] The RRC parameter timeRestrictionForlnterferenceMeasurements may be used for performing time domain measurement restriction for interference measurements. [0337] If the network including gNB 3 has a network side AI/ML model or two sided AI/ML model (i.e., the network supports a capability of the AI/ML), the network may set the RRC parameter timeRestrictionForChannelMeasurements to “notConfigured” or “configured” based on probability/accuracy of the predicted value obtained/reported by using the AI/ML model(s).

[0338] If the network including gNB 3 has a network side AI/ML model or two sided AI/ML model, the network may set the RRC parameter timeRestrictionForlnterferenceMeasurements to “notConfigured” or “configured” based on probability/accuracy of the predicted value obtained/reported by using the AI/ML model(s).

[0339] If the network including gNB 3 has a network side AI/ML model or two sided AI/ML model and the UE 1 is capable of at least time resource restriction for the channel measurement(s), the network may add a new DCI field for indicating whether or not perform the time resource restriction to a certain DCI format.

[0340] Figure 12 is an example of time resource restriction for the channel measurement(s) according to an aspect of the present embodiment. Figure 12(a) is an example of time resources for the channel measurement configured based on the configured first RRC parameter. Figure 12(b) is an example of time resource restriction applied within a certain period of the configured first time resources (i.e., a part of the configured first time resources). Figure 12(c) is an example of time resource periodicity applying time resource restriction for the channel measurement(s) based on the configured second RRC parameter. The UE 1 may not perform channel measurements for the time resources of the blacked portion because of performing predictions for the time resources. The UE 1 may predict result(s) of channel measurement for the time resources using result(s) of the channel measurement for the configured first and/or second time resource(s).

[0341] In Figure 12(a), the UE 1 may be configured with time resources for the channel measurement(s) based on received first RRC parameter. The UE 1 may perform the channel measurements using the time resources and report the results of the channel measurement(s) to the gNB 3.

[0342] Figure 12(b) is an example of time resource restriction for the channel measurement(s) within a certain period. In Figure 12(b), for example, if probability/accuracy of the predicted value for the channel measurement(s) becomes better than the threshold, the UE may restrict time resources for the channel measurement(s) and/or stop the channel measurement(s) during a certain period. The duration of the certain period may be provided by a certain RRC parameter different/ other than the first RRC parameter and/or the second RRC parameter for setting the time resources. If probability/accuracy of the predicted value for the channel measurement(s) becomes worse than the threshold, the UE 1 may not restrict time resources for the channel measurement(s). In this case, the UE 1 may perform the channel measurement(s) for time resources as described in Figure 12(a).

[0343] Figure 12(c) is an example of a case that the UE 1 is configured with second RRC parameter indicating a configuration of the time resource restriction for the channel measurement(s). In Figure 12(c), for example, if probability/accuracy of the predicted value for the channel measurement(s) becomes better than the threshold, the UE 1 may restrict time resources for the channel measurement(s) and perform the channel measurement(s) for the time resources configured based on the second RRC parameter. [0344] The UE 1 may determine whether or not the UE 1 restricts the time resource(s) for the channel measurement based on the result of the predicted value using the AI/ML model if the UE 1 supports the capability of the AI/ML (i.e ., the UE 1 has UE side AI/ML model or two sided AI/ML model). For example, the UE 1 may determine to restrict the time resource(s) for the channel measurement if the result of the predicted value becomes better than the certain threshold. For example, the UE 1 may determine to maintain the time resource(s) for the channel measurement if the result of the predicted value becomes worse than the certain threshold. In other words, the UE 1 supporting the capability of the AI/ML may change/switch/select the number/periodicity/frequency of the time resource(s) for the channel measurement based on the predicted value of the channel measurement. If the changed/switched/selected the number/periodicity/frequency of the time resource(s) for the channel measurement is applied within a certain period, before next certain period, the UE 1 may re-predict the result of the channel measurement using the AI/ML model, evaluate the re-predicted value and determine to whether or not restrict the time resource(s) for the channel measurement based on the result of the predicted value. The AI/ML model training may be performed for using the result of channel measurement when the UE 1 predicts the result of channel measurement (e.g., CSI value, Ll-RSRP value and/or Ll-SINR value) within a certain time instance (e.g., a certain period).

[0345] Alternatively or additionally, at the UE 1 supporting the capability of the AI/ML (i.e., the UE1 having the UE AI/ML model), if the UE 1 is configured with a time resource configuration for the channel measurement(s) (e.g., first time resource configuration, first RRC parameter for time resources) and a second time resource configuration when the predicted value is applied for the channel measurement(s) (e.g., second time resource configuration, second RRC parameter for time resources), the UE 1 may select any of two time resource configurations for the channel measurement(s) based on probability/accuracy of the predicted value and being configured with the second time resource configuration. In other words, if the UE 1 is configured with at least two time resource configurations for the channel measurement(s), one may be used as a regular time resource configuration, and another may be used for restricted time resource configuration for reducing the frequency of the channel measurement(s) or increasing measurement period/interval for the channel measurement(s). The result of the channel measurement(s) for the time resources provided by the second time resource configuration may be used for computing the predicted value for the channel measurement(s).

[0346] From the perspective of the gNB 3, if the UE supports a capability of AI/ML, the gNB 3 may provide first RRC parameter and second RRC parameter for time resources for the channel measurement(s) to the UE 1. The gNB 3 may transmit DCI format including a first DCI field for switching the time resources for the channel measurement(s) in this case. In other words, in this case, the UE 1 may assume that the first DCI field may be included in a certain DCI format, and the UE 1 may perform a reception procedure.

[0347] Alternatively or additionally, at the UE 1 supporting the capability of the AI/ML (i.e., the UE1 having the UE AI/ML model), if probability/accuracy of the predicted value for the channel measurement becomes worse than the threshold, the UE may derive the channel measurements for computing Ll-RSRP value reported in uplink slot n based on only the SS/PBCH or NZP CSI-RS, no later than the CSI reference resource, associated with the CSI resource setting. [0348] Alternatively or additionally, at the UE 1 supporting the capability of the AI/ML, if probability/accuracy of the predicted value for the channel measurement becomes better than the threshold, the UE 1 may derive the channel measurements for computing Ll-RSRP reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of SS/PBCH or NZP CSI-RS associated with the CSI resource setting.

[0349] When one or two resource settings are configured for Ll-SINR measurement, at the UE 1 supporting the capability of the AI/ML, if probability/accuracy of the predicted value for the channel measurement becomes worse than the threshold, the UE 1 may derive the channel measurements for computing Ll-SINR reported in uplink slot n based on only the SSB or NZP CSI-RS, no later than the CSI reference resource associated with the CSI resource setting.

[0350] Alternatively or additionally, when one or two resource settings are configured for Ll-SINR measurement, at the UE 1 supporting the capability of the AI/ML, if probability/accuracy of the predicted value for the channel measurement becomes better than the threshold, the UE 1 may derive the channel measurements for computing Ll- SINR reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of SSB or NZP CSI-RS associated with the CSI resource setting.

[0351] Alternatively or additionally, at the UE 1 supporting the capability of the AI/ML, if probability/accuracy of the predicted value for the channel measurement becomes worse than the threshold, the UE 1 may derive the channel measurements for computing CSI value reported in uplink slot n based on only the NZP CSI-RS, no later than the CSI reference resource associated with the CSI resource setting. [0352] Alternatively or additionally, at the UE 1 supporting the capability of the AI/ML, if probability/ accuracy of the predicted value for the channel measurement becomes better than the threshold, the UE 1 may derive the channel measurements for computing CSI reported in uplink slot n based on only the most recent, no later than the CSI reference resource, in cell DTX active time if cell DTX is activated, occasion of NZP CSI-RS associated with the CSI resource setting.

[0353] Here, the Ll-RSRP may be referred to as Ll-RSRP of Top-l/K beam(s) in Set A and/or Set B.

[0354] If the UE 1 supports a capability associated with the AI/ML and the UE 1 is configured with performing a beam prediction and/or a measurement prediction, the UE 1 may predict one or more measurement results within a certain period using a UE side AI/ML model and/or two sided AI/ML model (e.g., bean prediction, measurement result prediction, RSRP prediction). The UE may compare predicted result(s) with actual measurement result(s), for one or more time resource within the certain period. In other words, at the UE 1 supporting a capability associated with the AI/ML, if the UE 1 performs a first measurement, the UE 1 may perform a beam prediction and/or measurement prediction for a certain period based on a result of the first measurement, if the UE 1 is configured with performing a second measurement for a time resource within the certain period, the UE 1 may compare a result of the prediction(s) with actual result(s) of the second measurement. The UE 1 may or may not initiate a measurement reporting procedure based on the compared result(s).

[0355] Alternatively or additionally, at the UE 1 supporting the capability of the AI/ML, if the predicted result(s) and the actual measurement result(s) do not match significantly (i.e., worse than the expected range/result), the UE 1 may initiate a measurement reporting procedure.

[0356] Alternatively or additionally, at the UE 1 supporting the capability of the AI/ML, if difference between the predicted result(s) and the actual measurement result(s) becomes worse than a certain threshold, the UE 1 may initiate a measurement reporting procedure.

[0357] Alternatively or additionally, at the UE 1 supporting the capability of the AI/ML, if probability/accuracy of the predicted result(s) becomes worse than a certain threshold, the UE 1 may initiate a measurement reporting procedure.

[0358] In above cases, at the UE 1 supporting the capability of the AI/ML, if the UE 1 initiates measurement reporting procedure, the UE 1 may perform a measurement report including the predicted result(s) and the actual measurement result(s). Also, the UE 1 may report AI/ML model ID(s) and/or AI/ML functionality identification(s). Also, the UE 1 may request identification/(re-)selection/activation/switching/deactivation/fallback of AI/ML functionalities or AI/ML model(s) using the measurement report. Also, the UE 1 may request training/monitoring/deliver/transfer/inference/update of AI/ML model.

[0359] In above cases, the gNB 3 may perform a beam prediction for transmission(s) within a certain period using AI/ML model and/or functionality. The gNB 3 may transmit a PDSCH using a beam (beam ID) predicted based on the measurement report. The gNB 3 may perform identification/(re-)selection/activation/switching/deactivation/fallback of AI/ML functionalities or AI/ML model(s) based on the measurement report and provide configured AI/ML functionalities or AI/ML model(s). The gNB 3 may perform training/monitoring/deliver/transfer/inference/update of AI/ML model(s) based on the measurement report and provide configured AI/ML model(s). [0360] Alternatively or additionally, at the UE 1 supporting the capability of the AI/ML, if the predicted result(s) and the actual measurement result(s) do not match slightly or match, the UE 1 may or may not initiate a measurement reporting procedure.

[0361] Alternatively or additionally, at the UE 1 supporting the capability of the AI/ML, if difference between the predicted result(s) and the actual measurement result(s) becomes better than a certain threshold, the UE 1 may or may not initiate a measurement reporting procedure.

[0362] Alternatively or additionally, at the UE 1 supporting the capability of the AI/ML, if probability/accuracy of the predicted result(s) becomes better than a certain threshold, the UE 1 may or may not initiate a measurement reporting procedure.

[0363] Here, if two or more certain thresholds having different values/levels are provided, each of the two or more certain thresholds may be used for determining re- selection/activation/switching/deactivation of AI/ML functionalities or AI/ML model(s). For example, if a first certain threshold and a second threshold are provided, the first certain threshold may be used for determining re-selection or switching of AI/ML functionalities or AI/ML model(s) and the second certain threshold may be used for determining activation/deactivation of AI/ML functionalities or AI/ML model(s). For example, the first certain threshold may be used for determining deactivation and reselection of AI/ML functionalities or AI/ML model(s) and the second certain threshold may be used for determining activation of AI/ML functionalities or AI/ML model(s). In other words, each certain threshold may be applied for different use case.

[0364] If probability/accuracy of the predicted value for the channel measurement becomes better than the threshold, the UE 1/gNB 3 may reduce the number/frequency of the AI/ML model training for a prediction of the channel measurement(s) and/or increase the interval of the AI/ML model training.

[0365] If probability/accuracy of the predicted value for the channel measurement becomes worse than the threshold, the UE 1/gNB 3 may maintain the number/frequency of the AI/ML model training for a prediction of the channel measurement(s) and/or shorten the interval of the AI/ML model training.

[0366] Above procedures may be performed if the UE supports a capability of AI/ML associated with LCM.

[0367] Each of a program running on the base station device and the terminal device according to an aspect of the present invention may be a program that controls a Central Processing Unit (CPU) and the like, such that the program causes a computer to operate in such a manner as to realize the functions of the above-described embodiment according to the present invention. The information handled in these devices is transitorily stored in a Random- Access-Memory (RAM) while being processed. Thereafter, the information is stored in various types of Read-Only-Memory (ROM) such as a Flash ROM and a Hard- Disk-Drive (HDD), and when necessary, is read by the CPU to be modified or rewritten. [0368] Note that the terminal device 1 and the base station device 3 according to the above-described embodiment may be partially achieved by a computer. In this case, this configuration may be realized by recording a program for realizing such control functions on a computer-readable recording medium and causing a computer system to read the program recorded on the recording medium for execution.

[0369] Note that it is assumed that the "computer system" mentioned here refers to a computer system built into the terminal device 1 or the base station device 3, and the computer system includes an OS and hardware components such as a peripheral device. Furthermore, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, and the like, and a storage device built into the computer system such as a hard disk.

[0370] Moreover, the "computer-readable recording medium" may include a medium that dynamically retains a program for a short period of time, such as a communication line that is used to transmit the program over a network such as the Internet or over a communication line such as a telephone line, and may also include a medium that retains a program for a fixed period of time, such as a volatile memory within the computer system for functioning as a server or a client in such a case. Furthermore, the program may be configured to realize some of the functions described above, and also may be configured to be capable of realizing the functions described above in combination with a program already recorded in the computer system.

[0371] Furthermore, the base station device 3 according to the above-described embodiment may be achieved as an aggregation (an device group) including multiple devices. Each of the devices configuring such an device group may include some or all of the functions or the functional blocks of the base station device 3 according to the above-described embodiment. The device group may include each general function or each functional block of the base station device 3. Furthermore, the terminal device 1 according to the above-described embodiment can also communicate with the base station device as the aggregation.

[0372] Furthermore, the base station device 3 according to the above-described embodiment may serve as an Evolved Universal Terrestrial Radio Access Network (E- UTRAN) and/or NG-RAN (Next Gen RAN, NR-RAN). Furthermore, the base station device 3 according to the above-described embodiment may have some or all of the functions of a node higher than an eNodeB or the gNB.

[0373] Furthermore, some or all portions of each of the terminal device 1 and the base station device 3 according to the above-described embodiment may be typically achieved as an LSI which is an integrated circuit or may be achieved as a chip set. The functional blocks of each of the terminal device 1 and the base station device 3 may be individually achieved as a chip, or some or all of the functional blocks may be integrated into a chip. Furthermore, a circuit integration technique is not limited to the LSI, and may be realized with a dedicated circuit or a general-purpose processor. Furthermore, in a case that with advances in semiconductor technology, a circuit integration technology with which an LSI is replaced appears, it is also possible to use an integrated circuit based on the technology.

[0374] Furthermore, at least some aspects of the systems and methods disclosed herein may be described in relation to the 3 GPP LTE, LTE-Advanced (LTE-A), LTE- Advanced Pro, New Radio Access (NR), and other 3G/4G/5G standards (e.g., 3GPP Releases 8, 9, 10, 11 , 12, 13, 14, 15, 16, 17, and/or 18, and/or Narrow Band-Internet of Things (NB-IoT)). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be utilized in other types of wireless communication systems.

[0375] Furthermore, according to the above-described embodiment, the terminal device has been described as an example of a communication device, but the present invention is not limited to such a terminal device, and is applicable to a terminal device or a communication device of a fixed-type or a stationary-type electronic device installed indoors or outdoors, for example, such as an Audio-Video (AV) device, a kitchen device, a cleaning or washing machine, an air-conditioning device, office equipment, a vending machine, and other household devices,

[0376] The embodiments of the present invention have been described in detail above referring to the drawings, but the specific configuration is not limited to the embodiments and includes, for example, an amendment to a design that falls within the scope that does not depart from the gist of the present invention. Furthermore, various modifications are possible within the scope of one aspect of the present invention defined by claims, and embodiments that are made by suitably combining technical means disclosed according to the different embodiments are also included in the technical scope of the present invention. Furthermore, a configuration in which constituent elements, described in the respective embodiments and having mutually the same effects, are substituted for one another is also included in the technical scope of the present invention.

Claims

[CLAIMS]

1. A user equipment (UE) comprising: reception circuitry configured to receive a measurement configuration and a quantity configuration, the quantity configuration including an RRC parameter indicating a filterCoefficient; measurement circuitry configured to perform a first measurement based on the measurement configuration; and filtering circuitry configured to filter results of the first measurement based on the quantity configuration, wherein the filtering circuitry is configured to assume that a value of the filterCoefficient is set to 0 if the first measurement is performed within a certain period associated with a beam prediction.

2. A base station comprising: transmission circuitry configured to transmit a measurement configuration and a quantity configuration, the quantity configuration including an RRC parameter indicating a filterCoefficient, wherein the transmission circuitry is configured to set a value of the filterCoefficient to 0 if the measurement configuration and the quantity configuration are associated with a beam prediction.

3. A method for a user equipment, the method comprising: receiving a measurement configuration and a quantity configuration, the quantity configuration including an RRC parameter indicating a filterCoefficient; performing a first measurement based on the measurement configuration; and filtering a result of the first measurement based on the quantity configuration, wherein assuming that a value of the filterCoefficient is set to 0 if the first measurement is performed within a certain period associated with a beam prediction.