Terminal equipment, base station equipment, and method

Abstract

This invention provides terminal equipment, base station equipment, and methods for achieving efficient communication control regarding reporting of event-triggered Layer 1 measurements. [Solution] In a communication system, a terminal device UE that communicates with a base station device comprises a receiving unit, a processing unit, and a transmitting unit. The receiving unit receives settings for one or more measurements from the base station device. The processing unit measures a certain beam measurement item once or multiple times based on the settings. Based on the determination that the measurement item satisfies one condition, the processing unit includes the measurement results of one or more beams that satisfy the condition and the measurement results of one or more beams that do not satisfy the condition in the MAC CE. The beams that do not satisfy the condition are beams associated with the same cell as the beams that satisfy the condition. The transmitting unit transmits the MAC CE to the base station device.

Description

[Technical Field]

[0001] The present invention relates to terminal equipment, base station equipment, and methods. [Background technology]

[0002] The third-generation partnership project is a standardization project for cellular mobile communication systems. In the 3rd Generation Partnership Project (3GPP®), wireless accessories Technical studies and standards development are underway for cellular mobile communication systems, including the network, core network, and services.

[0003] For example, E-UTRA (Evolved Universal Terrestrial Radio Access) was initiated by 3GPP as a Radio Access Technology (RAT) for 3.9th and 4th generation cellular mobile communication systems, with technical review and standards development underway. Currently, 3GPP is also reviewing and developing standards for extensions to E-UTRA. E-UTRA is also known as Long Term Evolution (LTE: registered trademark), and its extensions are sometimes referred to as LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).

[0004] Furthermore, NR (New Radio, or NR Radio Access) has been initiated by 3GPP as a Radio Access Technology (RAT) for 5th Generation (5G) cellular mobile communication systems, with technical consideration and standards development underway. Currently, 3GPP is also working on extensions of NR. Technical reviews and standards development are underway. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 38.300 v18.2.0,"NR;NR and NG-RAN Overall description; Stage 2" pp103-105 [Non-Patent Document 2] 3GPP TS 38.214 v18.3.0," NR;Physical layer measurements" pp9-10 [Non-Patent Document 3] 3GPP TS 38.215 v18.3.0,"NR;NR and NG-RAN Overall description; Stage 2"pp98-101 [Non-Patent Document 4] 3GPP TS 38.331 v18.2.0,"NR;Radio Resource Control (RRC);Protocol specifications" pp43-458 [Overview of the Initiative] [Problems that the invention aims to solve]

[0006] Current Layer 1 measurements are limited to reporting periodic, non-periodic, and semi-permanent data. Therefore, consideration has been given to supporting event-triggered reporting.

[0007] One aspect of the present invention has been made in view of the above circumstances, and one of its objectives is to provide a terminal device, a base station device, a communication method, and an integrated circuit that can efficiently perform communication control. [Means for solving the problem]

[0008] To achieve the above objective, one aspect of the present invention employs the following means. That is, one aspect of the present invention is a terminal device that communicates with a base station device, comprising a receiving unit, a processing unit, and a transmitting unit, wherein the receiving unit transmits settings for one or more measurements to the base station device. receive, and the processing unit measures the measurement items of a certain beam once or multiple times based on the setting, and based on determining that the measurement items satisfy one condition, satisfy the condition Include the measurement results of one or more beams that satisfy the condition and the measurement results of one or more beams that do not satisfy the condition in the MAC CE. The beam that does not satisfy the condition is a beam associated with the same cell as the cell with which the beam that satisfies the condition is associated. The transmitting unit transmits the MAC CE to the base station device. Terminal device.

[0009] Also, one aspect of the present invention is a base station device that communicates with a terminal device, including a transmitting unit that transmits RRC (Radio Resource Control) signaling to the terminal device, and a processing unit. The processing The unit includes settings related to one or more measurements in the RRC signaling, and by applying the RRC signaling to the terminal device, the terminal device measures the measurement items of a certain beam once or multiple times based on the setting, and determines that the measurement items satisfy one condition Based on this, include the measurement results of one or more beams that satisfy the condition and the measurement results of one or more beams that do not satisfy the condition in the MAC CE. The beam that does not satisfy the condition is a beam associated with the same cell as the cell with which the beam that satisfies the condition is associated. The transmitting unit causes the base station device to transmit the MAC CE. Base station device. Include the measurement results of one or more beams that satisfy the condition and the measurement results of one or more beams that do not satisfy the condition in the MAC CE. The beam that does not satisfy the condition is a beam associated with the same cell as the cell with which the beam that satisfies the condition is associated. The transmitting unit causes the base station device to transmit the MAC CE. Base station device. Based on this, include the measurement results of one or more beams that satisfy the condition and the measurement results of one or more beams that do not satisfy the condition in the MAC CE. The beam that does not satisfy the condition is a beam associated with the same cell as the cell with which the beam that satisfies the condition is associated. The transmitting unit causes the base station device to transmit the MAC CE. Base station device.

[0010] Also, one aspect of the present invention is a method for a terminal device that communicates with a base station device, including receiving settings related to one or more measurements from the base station device, measuring the measurement items of a certain beam once or multiple times based on the setting, and based on determining that the measurement items satisfy one condition Based on this, include the measurement results of one or more beams that satisfy the condition and the measurement results of one or more beams that do not satisfy the condition. The beam that does not satisfy the condition is a beam associated with the same cell as the cell with which the beam that satisfies the condition is associated. The transmitting unit transmits the MAC CE to the base station device. Terminal device. Based on this, include the measurement results of one or more beams that satisfy the condition and the measurement results of one or more beams that do not satisfy the condition. The beam that does not satisfy the condition is a beam associated with the same cell as the cell with which the beam that satisfies the condition is associated. The transmitting unit transmits the MAC CE to the base station device. Terminal device. Include the measurement results of one or more beams that do not meet the conditions in the MAC CE. A method of transmitting the MAC CE to the base station device, wherein the beam is a beam associated with the same cell as the cell associated with the beam that meets the conditions.

[0011] These general or specific aspects may be implemented in a system, device, method, integrated circuit, computer program, or recording medium, or may be implemented in any combination of a system, device, method, integrated circuit, computer program, and recording medium.

Advantages of the Invention

[0012] According to one aspect of the present invention, a terminal device, method, and integrated circuit can realize efficient communication control processing.

Brief Description of the Drawings

[0013] [Figure 1] Schematic diagram of a communication system according to this embodiment. [Figure 2] Diagram of an example of the E-UTRA protocol configuration according to this embodiment. [Figure 3] Diagram of an example of the NR protocol configuration according to this embodiment. [Figure 4] Diagram showing an example of the flow of procedures for various settings in RRC according to this embodiment. [Figure 5] Block diagram showing the configuration of a terminal device in this embodiment. [Figure 6] Block diagram showing the configuration of a base station device in this embodiment. [Figure 7] Example of an ASN.1 description included in a message related to the reconfiguration of an RRC connection in NR in this embodiment. [Figure 8] Example of an ASN.1 description representing fields and / or information elements related to the ServingCellConfigCommon information element in this embodiment. [Figure 9]An example of processing by the terminal device in this embodiment. [Modes for carrying out the invention]

[0014] This embodiment will now be described in detail with reference to the drawings.

[0015] LTE (and LTE-A, LTE-A Pro) and NR may be defined as different Radio Access Technologies (RATs). Alternatively, NR may be defined as a technology included in LTE. Furthermore, LTE may be defined as a technology included in NR. Also, LTE that can connect with NR via Multi-Radio Dual Connectivity (MR-DC) may be distinguished from conventional LTE. Furthermore, LTE that uses 5GC for the core network (CN) may be distinguished from conventional LTE that uses EPC for the core network. Conventional LTE refers to technologies standardized in 3GPP Release 15 and later. This may refer to LTE that does not implement the technology. This embodiment is applicable to NR, LTE and other RATs. It is acceptable to use the following terms, which are related to LTE and NR. The terminology may be applied to other technologies using other terms. Furthermore, the term E-UTRA in this embodiment may be replaced with the term LTE, and the term LTE may be replaced with the term E-UTRA.

[0016] In this embodiment, the names of each node and entity, and the processing at each node and entity, will be described when the wireless access technology is E-UTRA or NR. However, this embodiment may be used with other wireless access technologies. The names of each node and entity in this embodiment may be different.

[0017] Figure 1 is a schematic diagram of the communication system according to this embodiment. The functions of each node, wireless access technology, core network, interface, etc., described using Figure 1 are only some of the functions closely related to this embodiment, and other functions may also be present.

[0018] E-UTRA100 may be a wireless access technology. Also, E-UTRA100 is between UE122 and eNB102. It may be an air interface. The air interface between UE122 and eNB102 may be called the Uu interface. eNB (E-UTRAN Node B)102 may be a base station device. eNB102 may have the E-UTRA protocol described below. The E-UTRA protocol may consist of the E-UTRA User Plane (UP) protocol described below and the E-UTRA Control Plane (CP) protocol described below. eNB102 communicates the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol to UE122. The rotocol may be terminated. A wireless access network composed of eNBs may be called E-UTRAN.

[0019] The EPC (Evolved Packet Core) 104 may be the core network. Interface 112 is the interface between eNB 102 and EPC 104, and may be called the S1 interface. Interface 112 may have a control plane interface through which control signals pass, and / or a user plane interface through which user data passes. The control plane interface may terminate at the Mobility Management Entity (MME: not shown) within EPC104. The user plane interface of interface 112 is within the service within EPC104. The interface may be terminated at a junction gateway (S-GW: not shown). The control plane interface of interface 112 may be called the S1-MME interface. User plane of interface 112 The interface can be called the S1-U interface.

[0020] One or more eNB102s may be connected to the EPC104 via interface 112. Interfaces may exist between multiple eNB102s connected to the EPC104 (not shown). Interfaces between multiple eNB102s connected to the EPC104 may be called X2 interfaces.

[0021] NR106 may be a wireless access technology. Also, NR106 is an air connection between UE122 and gNB108. It may be an air interface. The air interface between UE122 and gNB108 may be called the Uu interface. gNB (g Node B)108 may be a base station device. gNB108 may have the NR protocol described below. The NR protocol consists of the NR User Plane (UP) protocol and the NR Control Plane (CP) protocol described below. The configuration may be configured such that the gNB108 terminates the NR User Plane (UP) protocol and the NR Control Plane (CP) protocol to the UE122.

[0022] 5GC110 may be the core network. Interface 116 is the interface between gNB108 and 5GC110. It is an interface and may be called an NG interface. Interface 116 has a control plane interface through which control signals pass, and / or a user plane interface through which user data passes. A control plane interface may exist. Interface 116 control plane interface This may be terminated in the Access and Mobility Management Function (AMF: not shown) within 5GC110. The user plane interface of interface 116 may be terminated by a User Plane Function (UPF: not shown) in 5GC110. The control plane interface of interface 116 is NG-C It can be called an interface. The user plane interface of interface 116 is NG-U It can be called an interface.

[0023] One or more gNB108s may be connected to the 5GC110 via interface 116. Interfaces may exist between multiple gNB108s connected to the 5GC110 (not shown). The interfaces between multiple gNB108s connected to the 5GC110 may be called Xn interfaces.

[0024] eNB102 may have the function to connect to 5GC110. An eNB102 that has the function to connect to 5GC110 may be called ng-eNB. Interface 114 is the interface between eNB102 and 5GC110, NG It can be called an interface. The control plane through which control signals pass is the interface 114. There exists an interface, and / or a user plane interface through which user data passes. The control plane interface of interface 114 may be terminated at the AMF in 5GC110. The user plane interface of interface 114 may be terminated at the UPF in 5GC110. The control plane interface of interface 114 may be called the NG-C interface. Let's call the user plane interface of interface 114 the NG-U interface. A wireless access network consisting of ng-eNB or gNB may be called NG-RAN. NG-RAN, E-UTRAN, etc., may simply be called a network. Furthermore, the network may include eNB. This may include ng-eNB and gNB, among others.

[0025] One or more eNB102s may be connected to the 5GC110 via interface 114. Interfaces may exist between multiple eNB102s connected to the 5GC110 (not shown). Interfaces between multiple eNB102s connected to the 5GC110 may be called Xn interfaces. Also, the eNB102 connected to the 5GC110 and the gNB108 connected to the 5GC110 are connected via interface 120. Good. The interface 120 between eNB102 connected to 5GC110 and gNB108 connected to 5GC110 is It can be called the Xn interface.

[0026] gNB108 may have the function to connect to EPC104. A gNB108 that has the function to connect to EPC104 may be called an en-gNB. Interface 118 is the interface between gNB108 and EPC104, S1 It can be called an interface. Interface 118 is a user interface through which user data passes. A lane interface may exist. User plane interface of interface 118 The line may be terminated at the S-GW (not shown) in EPC104. User plane of interface 118 The interface may be called the S1-U interface. Furthermore, the eNB102 connected to EPC104 and the gNB108 connected to EPC104 may be connected via interface 120. eNB102 connected to EPC104 And the interface 120 between the EPC104 and the gNB108 is called the X2 interface. stomach.

[0027] Interface 124 is the interface between EPC104 and 5GC110, and is either CP only or UP only. or it may be an interface that passes through both CP and UP. Also, interface 114, Some or all of the interfaces, such as interface 116, interface 118, interface 120, and interface 124, are configured according to the communication system provided by the telecommunications carrier, etc. It is acceptable for it not to exist.

[0028] UE122 may be a terminal device capable of receiving system information and paging messages transmitted from eNB102 and / or gNB108. UE122 may also be a terminal device capable of wireless connection with eNB102 and / or gNB108. Furthermore, UE122 may be a terminal device capable of simultaneously establishing wireless connections with eNB102 and gNB108. UE122 may have the E-UTRA protocol and / or the NR protocol. Note that the wireless connection may be a Radio Resource Control (RRC) connection.

[0029] Furthermore, UE122 is connected to EPC104 and / or 5GC110 via eNB102 and / or gNB108. Any capable terminal device may be used. If the core network to which the eNB102 and / or gNB108 communicates with the UE122 is connected is the EPC104, then each Data Radio Bearer (DRB) established between the UE122 and the eNB102 and / or gNB108, as described below, may be uniquely associated with each EPS (Evolved Packet System) bearer passing through the EPC104. Each EPS bearer may be identified by an EPS bearer identifier (Identity, or ID). Furthermore, the same QoS may be guaranteed for data such as IP packets and Ethernet® frames passing through the same EPS bearer.

[0030] Furthermore, if the core network to which UE122 communicates with eNB102 and / or gNB108 is connected is 5GC110, then each DRB established between UE122 and eNB102 and / or gNB108 will be further established within 5GC110. It may be associated with one of the Packet Data Unit (PDU) sessions. Each PDU session may have one or more QoS flows. Each DRB may be associated with one or more QoS flows. Each PDU session may be mapped, or it may not be mapped to any QoS flow. Each QoS flow may be identified by a PDU session identifier (Identity, or ID). Each QoS flow may also be identified by a QoS flow identifier (Identity, or ID). Furthermore, the same QoS may be guaranteed for data such as IP packets and Ethernet frames passing through the same QoS flow.

[0031] EPC104 does not need to have a PDU session and / or QoS flow. Also, 5GC110 does not need to have an EPS bearer. When UE122 is connected to EPC104, UE122 does not have information about the EPS bearer. It will have information, but it does not need to have information within the PDU session and / or QoS flow. Also, when UE122 is connected to 5GC110, UE122 will have information within the PDU session and / or QoS flow, but it does not need to have information about the EPS bearer.

[0032] In the following description, eNB102 and / or gNB108 will also be simply referred to as base station equipment, and UE122 will also be simply referred to as terminal equipment or UE.

[0033] Figure 2 is a diagram of an example of the E-UTRA protocol architecture according to this embodiment. Figure 3 is a diagram of an example of the NR protocol architecture according to this embodiment. Note that Figure 2 and / or The functions of each protocol described using Figure 3 are some of the functions closely related to this embodiment. It may also have other functions. In this embodiment, the uplink (UL) and This may be a link from a terminal device to a base station device. In this embodiment, the downlink (DL) may be a link from a base station device to a terminal device.

[0034] Figure 2(A) is a diagram of the E-UTRA user plane (UP) protocol stack. As shown in Figure 2(A), the E-UTRA UP protocol may be a protocol between UE122 and eNB102. That is, the E-UTRA UP protocol may be a protocol that terminates on the network side at eNB102. Figure 2(A) As shown, the E-UTRA user plane protocol stack may consist of a radio physical layer (PHY) 200, a medium access control layer (MAC) 202, a radio link control layer (RLC) 204, and a packet data convergence protocol layer (PDCP) 206.

[0035] Figure 3(A) is a diagram of the NR user plane (UP) protocol stack. As shown in Figure 3(A), NR The UP protocol may be the protocol between UE122 and gNB108. That is, the NR UP protocol. This protocol may terminate at gNB108 on the network side. As shown in Figure 3(A), the NR user plane protocol stack may consist of the wireless physical layer PHY300, the media access control layer MAC302, the wireless link control layer RLC304, the packet data convergence protocol layer PDCP306, and the service data adaptation protocol layer (service data adaptation protocol layer) SDAP (Service Data Adaptation Protocol)310.

[0036] Figure 2(B) is a diagram of the E-UTRA control plane (CP) protocol configuration. As shown in Figure 2(B), in the E-UTRA CP protocol, the Radio Resource Control (RRC) 208, which is the radio resource control layer, may be a protocol between the UE122 and the eNB102. That is, the RRC 208 may be a protocol that terminates at the eNB102 on the network side. In Tokol, the NAS (Non-Access Stratum) 210, which is a non-AS (Access Stratum) layer, may be a protocol between UE122 and MME. That is, NAS210 may be a protocol that terminates at MME on the network side.

[0037] Figure 3(B) is a diagram of the NR control plane (CP) protocol configuration. As shown in Figure 3(B), the NR CP In Rotokol, the RRC308, which is the wireless resource control layer, is the protocol between UE122 and gNB108. It may be a protocol that terminates with gNB108 on the network side. Also, in the NR CP protocol, the non-AS layer NAS312 is a protocol that connects UE122 and AMF. It can be a protocol. That is, the NAS312 is a protocol that terminates with AMF on the network side. It's okay to have it.

[0038] The AS (Access Stratum) layer may be a layer that terminates between UE122 and eNB102 and / or gNB108. That is, the AS layer is a part of PHY200, MAC202, RLC204, PDCP206, and RRC208 or The layer containing all of them, and / or one of PHY300, MAC302, RLC304, PDCP306, SDAP310, and RRC308 It may be a layer that includes part or all of it.

[0039] In this embodiment, the following terms may be used without distinguishing between the E-UTRA protocol and the NR protocol, and may include PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer). In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), NAS (NAS The layers may be PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the E-UTRA protocol, or PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the NR protocol. Also, SDAP (SDAP layer) is NR It can be the SDAP (SDAP layer) of the protocol.

[0040] Furthermore, in this embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, PHY200, MAC202, RLC204, PDCP206, and RRC208 are referred to as the PHY for E-UTRA or the PHY for LTE, the MAC for E-UTRA or the MAC for LTE, the RLC for E-UTRA or the RLC for LTE, the PDCP for E-UTRA or the PDCP for LTE, and It is also sometimes referred to as the RRC for E-UTRA or the RRC for LTE. Furthermore, PHY200, MAC202, RLC204, PDCP206, and RRC208 may be described as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively. Yes. Also, when distinguishing between the E-UTRA protocol and the NR protocol, PHY300, MAC302, RLC304, PDCP306, and RRC308 are sometimes referred to as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively. Furthermore, PHY300, MAC302, RLC304, PDCP306, and RRC308 are sometimes written as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.

[0041] This section describes entities in the AS layer of E-UTRA and / or NR. An entity that possesses some or all of the functions of the RLC layer may be called a MAC entity. An entity that possesses some or all of the functions of the RLC layer may be called an RLC entity. Functions of the PDCP layer An entity possessing some or all of the functions of the SDAP layer may be called a PDCP entity. An entity possessing some or all of the functions of the SDAP layer may be called an SDAP entity. Functions of the RRC layer An entity that possesses some or all of the characteristics may be called an RRC entity. MAC entities, RLC entities, PDCP entities, SDAP entities, and RRC entities may be replaced with MAC, RLC, PDCP, SDAP, and RRC, respectively.

[0042] Furthermore, the data provided from MAC, RLC, PDCP, and SDAP to lower layers, and / or the data provided to MAC, RLC, PDCP, and SDAP from lower layers, may be referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. This refers to the data provided, and / or the data provided to higher layers from MAC, RLC, PDCP, and SDAP. These can be called MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. Furthermore, a segmented RLC SDU can be referred to as an RLC SDU segment.

[0043] Here, the base station equipment and the terminal equipment exchange signals (send and receive) at the higher layer. For example, the base station equipment and the terminal equipment communicate via Radio Resource Control (RRC). At the Radio Resource Control (RRC) layer, RRC messages (also called RRC messages, RRC information, or RRC signalling) may be sent and received. Furthermore, the base station equipment and terminal equipment may send and receive MAC control elements at the MAC (Medium Access Control) layer. Good. Also, the RRC layer of the terminal device acquires system information broadcast from the base station device. Here, RRC messages, system information, and / or MAC control elements are also referred to as higher layer signals (higher layer signaling) or higher layer parameters (higher layer parameters). Each parameter included in the higher layer signal received by the terminal device may also be referred to as a higher layer parameter. In PHY layer processing, the higher layer refers to the layer above the PHY layer, and therefore may refer to one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. For example, in MAC layer processing, the upper layers include the RRC layer, RLC layer, PDCP layer, NAS layer, etc. "Ta" can also mean plural. Below, the meaning of "A is given (provided) at the upper layer" or "A is given (provided) by the upper layer" refers to the upper layer (mainly the RRC layer) of the terminal device. The MAC layer, etc., receives A from the base station equipment, and the received A is sent from the upper layer of the terminal equipment to the terminal. It may also mean that the parameters are provided to the physical layer of the terminal device. For example, "being provided with upper layer parameters" in a terminal device may mean that the terminal device receives an upper layer signal from the base station device, and the upper layer parameters contained in the received upper layer signal are provided from the upper layer of the terminal device to the physical layer of the terminal device. Setting upper layer parameters in a terminal device may also mean that the upper layer parameters are provided to the terminal device. For example, setting upper layer parameters in a terminal device may mean that the terminal device receives an upper layer signal from the base station device and sets the received upper layer parameters in the upper layer. However, setting upper layer parameters in a terminal device may also include setting default parameters that are pre-provided in the upper layer of the terminal device. When explaining this, the expression "submitting a message from the RRC entity of the terminal device to the lower layer" is sometimes used. When an entity "submits a message to a lower layer," it may mean submitting a message to the PDCP layer. In a terminal device, when the RRC layer "submits a message to a lower layer," it may mean submitting the RRC message to the PDCP entity corresponding to each SRB (SRB0, SRB1, SRB2, SRB3, etc.), since the RRC message is transmitted using an SRB. When the RRC entity of a terminal device receives an indication from a lower layer, that lower layer This may mean one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, etc.

[0044] An example of PHY functionality is described below. The PHY of the terminal device receives downlink from the PHY of the base station device. Downlink (DL) receives data transmitted via the Physical Channel. It may have the function. The PHY of the terminal device is related to the PHY of the base station device, and is an uplink (UL) device. The PHY may have the function of transmitting data via a transport channel. The PHY may be connected to the higher-level MAC via a transport channel. The PHY may transfer data to the MAC via the transport channel. The PHY may also transfer data from the MAC via the transport channel. Data may be provided. In the PHY, RNTI (Radio Network Temporary Identifier) ​​may be used to identify various control information.

[0045] Now, let's explain physical channels. The following physical channels may be included in the physical channels used for wireless communication between terminal equipment and base station equipment.

[0046] PBCH (Physical Broadcast Channel) PDCCH (Physical Downlink Control Channel) PDSCH (Physical Downlink Shared Channel) PUCCH (Physical Uplink Control Channel) PUSCH (Physical Uplink Shared Channel) PRACH (Physical Random Access Channel)

[0047] PBCH may be used to broadcast system information required by terminal devices.

[0048] Furthermore, in NR, the PBCH may be used to announce the time index (SSB-Index) within the period of the Synchronization Signal Block (SSB).

[0049] PDCCH is used in downlink wireless communication (wireless communication from base station equipment to terminal equipment). It may be used to transmit (or carry) Downlink Control Information (DCI). Here, for the transmission of Downlink Control Information, one or more DCIs (DCI A format (which may also be called a format) may be defined. That is, for downlink control information The field may be defined as DCI and mapped to information bits. PDCCH is a PDCCH candidate. It may be transmitted in the candidate. The terminal device may monitor a set of PDCCH candidates in the serving cell. Monitoring a set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format. The terminal device may also use a CORESET (Control Resource Set) to monitor a set of PDCCH candidates. The DCI format may be used for scheduling PUSCH in the serving cell. PUSCH may be used for sending user data or sending RRC messages, as described later. stomach.

[0050] PUCCH is used in uplink wireless communication (wireless communication from terminal equipment to base station equipment), It may be used to transmit Uplink Control Information (UCI). Here, the uplink control information may include Channel State Information (CSI), which is used to indicate the state of the downlink channel. The control information may include scheduling requests (SRs) used to request UL-SCH (UL-SCH: Uplink Shared Channel) resources. The link control information includes HARQ-ACK (Hybrid Automatic Repeat request ACK knowledgement). It's okay to be born.

[0051] PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared Channel) from the MAC layer. In the case of downlinks, PDSCH may also be used to transmit system information (SI) and random access responses (RAR).

[0052] PUSCH may be used to transmit uplink data (UL-SCH: Uplink Shared Channel) from the MAC layer, or to transmit HARQ-ACK and / or CSI along with uplink data. Alternatively, PUSCH may be used to transmit CSI only, or HARQ-ACK and CSI only. In other words, PUSCH may be used to transmit only UCI. Also, PDSCH or PUSCH may be used to transmit RRC signaling (also called RRC messages) and MAC CE. Here, in PDSCH, the RRC signaling transmitted from the base station equipment may be a common signaling for multiple terminal devices within a cell. Also, the RRC signaling transmitted from the base station equipment may be a dedicated signaling (also called dedicated signaling) for a particular terminal device. That is, terminal device-specific (UE-specific) The information in (k) may be transmitted to a terminal device using dedicated signaling. Furthermore, PUSCH may be used to transmit UE Capability on the uplink.

[0053] PRACH may be used to send a random access preamble. PRACH is used in the initial connection establishment procedure, handover procedure, connection re-establishment procedure, and above It may be used to indicate synchronization (timing adjustment) for relink transmissions and requests for UL-SCH resources.

[0054] An example of MAC functionality is described below. MAC may be called a MAC sublayer. MAC may have the function of mapping various logical channels to corresponding transport channels. Logical channels may be identified by a Logical Channel Identity (Logical Channel ID). MAC may be connected to the higher-level RLC via logical channels. Logical channels may be divided into control channels that transmit control information and traffic channels that transmit user information, depending on the type of information being transmitted. Logical channels may also be divided into uplink logical channels and downlink logical channels. MAC may have one or more different logical channels. MAC may have the function of multiplexing MAC SDUs belonging to a logical channel and providing them to the PHY. MAC may also have the function of demultiplexing MAC PDUs provided by the PHY and providing them to the higher layer via the logical channel to which each MAC SDU belongs. MAC may also have the function of performing error correction through HARQ (Hybrid Automatic Repeat request). MAC may also have the function of reporting scheduling information. MAC has the function of prioritizing processing between terminal devices using dynamic scheduling. Good. Also, MAC has the function of prioritizing between logical channels within a single terminal device. MAC has the ability to prioritize the processing of overlapping resources within a single terminal device. That's fine. E-UTRA MAC is a device that identifies Multimedia Broadcast Multicast Services (MBMS). It may have the ability to identify a Multicast Broadcast Service (MBS). The MAC is a transport format. MAC may have a function to select a set. MAC has the function to perform intermittent reception (DRX) and / or intermittent transmission (DTX), and random access (Random Access:RA) Function to execute procedures, notify information on transmittable power, power headroom The Power Headroom Report (PHR) function notifies users of data volume information for the transmission buffer. It may have a Buffer Status Report (BSR) function, etc. NR MAC may have a Bandwidth Adaptation (BA) function. Also used in E-UTRA MAC The MAC PDU format used by [unspecified] and the MAC PDU format used by NR MAC may be different. Furthermore, a MAC PDU may contain MAC control elements (MAC control elements), which are elements used for control within the MAC. The element (MAC CE) may be included.

[0055] This section describes the logical channels used for uplink (UL) and / or downlink (DL) in E-UTRA and / or NR.

[0056] BCCH (Broadcast Control Channel) may be a downlink logical channel for broadcasting control information, such as system information (SI).

[0057] A PCCH (Paging Control Channel) may be a downlink logical channel for carrying paging messages.

[0058] CCCH (Common Control Channel) may be a logical channel for transmitting control information between terminal equipment and base station equipment. CCCH is used when terminal equipment does not have RRC connection. It may be used. Furthermore, CCCH may be used between a base station device and multiple terminal devices.

[0059] DCCH (Dedicated Control Channel) is a logical channel for transmitting dedicated control information bidirectionally (point-to-point) between terminal equipment and base station equipment. That is fine. Dedicated control information may be control information specific to each terminal device. DCCH may be used when the terminal device has an RRC connection.

[0060] A DTCH (Dedicated Traffic Channel) may be a logical channel for transmitting user data one-to-one (point-to-point) between a terminal device and a base station device. It may be a logical channel for transmitting data. Dedicated user data may be user data specific to each terminal device. DTCH may exist on both the uplink and downlink.

[0061] Logical channel and transport channel of the uplink in E-UTRA and / or NR Let's explain mapping.

[0062] CCCH is an uplink transport channel, UL-SCH (Uplink Shared Channel). It can be mapped to this.

[0063] DCCH is an uplink transport channel, also known as UL-SCH (Uplink Shared Channel). It can be mapped to this.

[0064] DTCH is an uplink transport channel, UL-SCH (Uplink Shared Channel). It can be mapped to this.

[0065] Logical channel and transport channel of the downlink in E-UTRA and / or NR Let's explain mapping.

[0066] BCCH is a downlink transport channel, also known as BCH (Broadcast Channel), and / or This may be mapped to DL-SCH (Downlink Shared Channel).

[0067] PCCH is mapped to PCH (Paging Channel), which is a downlink transport channel. That's fine.

[0068] CCCH is a Downlink Shared Channel (DL-SCH), which is a downlink transport channel. It can be mapped to this.

[0069] DCCH is a Downlink Shared Channel (DL-SCH), which is a downlink transport channel. It can be mapped to this.

[0070] DTCH stands for Downlink Shared Channel (DL-SCH), which is a downlink transport channel. It can be mapped to this.

[0071] An example of RLC functionality is described below. RLC may be called an RLC sublayer. E-UTRA RLC may have the function of segmenting and / or concatenating data provided from the upper layer PDCP and providing it to the lower layer. E-UTRA RLC The NR RLC may have the function of reassembling and reordering the data provided from the lower layer and providing it to the upper layer. The NR RLC provides the data from the PDCP of the upper layer with a sequence number independent of the sequence number added by the PDCP. It may have a function to add numbers. Furthermore, the NR RLC may have a function to segment the data provided by the PDCP and provide it to lower layers. The NR RLC may also have a function to reassemble the data provided by lower layers and provide it to higher layers. The RLC may also have a data retransmission function and / or retransmission request function (Automatic Repeat Request: ARQ). Furthermore, the RLC may have a function to perform error correction using ARQ. To perform this, control information indicating the data that needs to be retransmitted is sent from the RLC receiver to the transmitter. This can be called a status report. Also, the status is sent from the RLC transmitter to the receiver. The instruction to send a task report can be called a "poll." RLC also detects data duplication. It may have a function to perform the following. RLC may also have a data discard function. RLC has Transparent Mode (TM), Unacknowledged Mode (UM), and There can be three response modes (AM: Acknowledged Mode). In TM, it receives from the upper layer. The data will not be split, and the RLC header does not need to be added. TM RLC entities are single A unidirectional entity, and the terminal device uses the TM RLC entity. As a transmitting™ RLC entity, or as a receiving™ RLC entity It may be set as such. UM performs splitting and / or joining of data received from higher layers, adds RLC headers, etc., but does not need to perform data retransmission control. UM RLC entities may be unidirectional or bidirectional entities. If a UM RLC entity is unidirectional, the terminal device may set it as a transmitting UM RLC entity or a receiving UM RLC entity. If a UM RLC entity is bidirectional, the terminal device may set the UM RLC entity as a UM RLC entity consisting of a transmitting side and a receiving side. It can be set as an entity. AM splits and / or combines the data received from the upper layer. In addition, RLC headers may be added, and data retransmission control may be performed. AM RLC entities are bidirectional. The entity is such that the terminal device may configure the AM RLC entity as an AM RLC consisting of a transmitting side and a receiving side. The data provided to lower layers, and / or provided by lower layers, may be called TMD PDU. Similarly, the data provided to lower layers, and / or provided by lower layers, in UM, may be called UMD. It may be called a PDU. Furthermore, data provided to lower layers in AM, or data provided by lower layers, may be called an AMD PDU. The RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC may be different. Also, RLC PDUs include data RLC PDUs and... It is acceptable to have RLC PDUs for specific purposes. A data RLC PDU may be called an RLC DATA PDU (RLC Data PDU). Similarly, a control RLC PDU may be called an RLC CONTROL PDU (RLC Control PDU). It can be called a troll PDU (or RLC-controlled PDU).

[0072] This section describes an example of PDCP functionality. PDCP may be referred to as the PDCP sublayer. PDCP may have the function of maintaining sequence numbers. Furthermore, PDCP efficiently transmits user data such as IP packets and Ethernet frames over the wireless section. It may have a header compression / decompression function for this purpose. The protocol used for compressing and decompressing IP packet headers may be called the ROHC (Robust Header Compression) protocol. The protocol used for compressing and decompressing Ethernet frame headers is EHC (Ethernet(registered trademark)). It may be called the Header Compression (PDCP) protocol. Furthermore, PDCP may have data encryption / decryption capabilities. Furthermore, PDCP may have data integrity protection / integrity verification capabilities. Furthermore, PDCP may have reordering capabilities. Furthermore, PDCP is P DCP SDU may have a retransmission function. PDCP may also have a data discard function using a discard timer. Furthermore, PDCP may have a duplication function. Furthermore, PDCP may have a function to discard duplicate received data. A PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. Furthermore, a PDCP PDU may include: There may be both a data PDCP PDU and a control PDCP PDU. The data PDCP PDU may be called a PDCP DATA PDU (PDCP Data PDU). The control PDCP PDU may be called a PDCP CONTROL PDU (PDCP Control PDU).

[0073] This section describes an example of SDAP functionality. SDAP is a Service Data Adaptive Protocol Layer (SAP). SDAP is a 5GC110 (Data Adaptive Protocol Layer) that transmits data from the base station equipment to the terminal. Mapping the downlink QoS flow sent to the device with the data radio bearer (DRB) (map SDAP may have the function of mapping (mapping) and / or mapping the uplink QoS flow sent from the terminal device to the 5GC110 via the base station device to the DRB. SDAP may also have the function of storing mapping rule information. SDAP may also have the function of marking QoS flow identifiers (QoS Flow ID: QFI). Note that there may be data SDAP PDUs and control SDAP PDUs. Data SDAP PDUs may be called SDAP DATA PDUs (SDAP Data PDUs). Control SDAP PDUs may be called SDAP CONTROL PDUs (SDAP Control PDUs). Note that there may be one SDAP entity for each PDU session of the terminal device.

[0074] An example of RRC functionality is described below. RRC may have broadcast functionality. RRC may have paging functionality from EPC104 and / or 5GC110. It may have. The RRC may have a paging function from the eNB102 connected to the gNB108 or 5GC110. The RRC may also have an RRC connection management function. The RRC may also have a wireless base It may have an error control function. The RRC may also have a cell group control function. Furthermore, the RRC may have a mobility control function. The RRC may also have terminal device measurement reporting. The RRC may also have a terminal device measurement reporting control function. Furthermore, the RRC may have a QoS management function. The RRC may also have a wireless link failure detection and recovery function. The RRC may also have an RRC Me Using messages, broadcasting, paging, RRC connection management, wireless bearer control, and cell group management are performed. You may perform mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, wireless link failure detection and recovery, etc. Note that E-UTRA RRC may use The RRC messages and parameters used may differ from those used in NR RRC.

[0075] RRC messages may be sent using the logical channel BCCH, or the logical channel PCCH. It may be sent using the logical channel CCCH, or it may be sent using the logical channel DCCH. Furthermore, RRC messages sent using DCCH may be referred to as dedicated RRC signaling or RRC signaling.

[0076] RRC messages sent using BCCH may include, for example, a Master Information Block (MIB), a System Information Block (SIB) of each type, or other RRC messages. RRC messages sent using PCCH may include, for example, a paging message or other RRC messages.

[0077] RRC messages sent in the uplink (UL) direction using CCCH include, for example, RRC Setup Request messages, RRC Resume Request messages, RRC Reestablishment Request messages, and RRC System Information Request messages. This may include messages such as Sage (RRC System Info Request). It may also include messages such as RRC Connection Request, RRC Connection Resume Request, and RRC Connection Reestablishment Request. Other RRC messages may also be included.

[0078] RRC messages sent in the downlink (DL) direction using CCCH may include, for example, RRC Connection Reject messages, RRC Connection Setup messages, RRC Connection Reestablishment messages, and RRC Connection Reestablishment Reject messages. Messages such as "RRC Setup" may be included. Other RRC messages may also be included.

[0079] RRC signaling transmitted in the uplink (UL) direction using DCCH includes, for example, measurement reports. Messages such as Measurement Report, RRC Connection Reconfiguration Complete, RRC Connection Setup Complete, RRC Connection Reestablishment Complete, Security Mode Complete, and UE Capability Information may be included. Regular reporting message (Measurement Report), RRC Reconfiguration Complete message, RRC Setup Complete message, RRC Re-establishment Complete message This may include messages such as RRC Reestablishment Complete, RRC Resume Complete, Security Mode Complete, and UE Capability Information. Other RRC signaling may also be included.

[0080] RRC signaling sent in the downlink (DL) direction using DCCH includes, for example, RRC Connection Reconfiguration messages and RRC Connection Release messages. This may include messages such as RRC Connection Release, Security Mode Command, and UE Capability Enquiry. It may also include, for example, RRC Reconfiguration, RRC Resume, RRC Release, RRC Reestablishment, and security messages. This may include Security Mode Command messages, UE Capability Enquiry messages, and other RRC signaling.

[0081] Let's explain an example of NAS functionality. A NAS may have authentication functionality. Also, a NAS can be mobile... It may have a mobility management function. Furthermore, the NAS may have security control functions. You may have it.

[0082] The aforementioned functions of PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS are just examples, and some of each function may be present. Not all of these features need to be implemented. Also, some or all of the functionality of each layer may be included in other layers.

[0083] Next, we will explain the state transitions of UE122 in LTE and NR. When a UE122 connected to an EPC or 5GC has an RRC connection, it may be in the RRC_CONNECTED state. The state of having an RRC connection may include the state in which UE122 holds some or all of the UE context described below. The state of having an RRC connection may also include the state in which UE122 can send and / or receive unicast data. Furthermore, when the RRC connection is suspended, UE122 may be in the RRC_INACTIVE state. Also, UE122 may be in the RRC_INACTIVE state when it is connected to a 5GC and the RRC connection is suspended. When neither in the RRC_INACTIVE state nor the RRC_INACTIVE state, UE122 may be in the RRC_IDLE state.

[0084] Note that when UE122 is connected to EPC, it does not have the RRC_INACTIVE state, but E-UTRAN The RRC connection may be put into a pause state. If UE122 is connected to EPC, when the RRC connection is put into a pause state, UE122 may transition to the RRC_IDLE state, retaining the UE's AS context and the identifier (resumeIdentity) used for resuming. The upper layer of the UE122's RRC layer (e.g., the NAS layer) will, when UE122 retains the UE's AS context, E-UTRAN has permitted the resumption of the RRC connection, and UE122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state, then the paused RRC connection You may begin your recovery.

[0085] The definition of hibernation may differ between UE122 connected to EPC104 and UE122 connected to 5GC110. Also, the definition of hibernation may differ depending on whether UE122 is connected to EPC (when UE122 is hibernating in the RRC_IDLE state) or UE122 is connected to 5GC (when UE122 is hibernating in the RRC_INACTIVE state). The procedure for resuming from hibernation may be entirely or partially different.

[0086] Note that the RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state are referred to as the connection state. These can be called connected mode, inactive mode, or idle mode, or RRC connected mode, RRC inactive mode, or RRC idle mode.

[0087] The UE context held by UE122 may include all or part of the following: PDU session context, security key, UE radio capability information, and UE security capability information. Any or all of the UE contexts held are the same as the UE contexts held by UE122. It may include the same information, or it may contain information different from the information contained in the UE context held by UE122. This may include information. Furthermore, the UE context may include all or part of the AS context of the UE, as described below.

[0088] The AS context of the UE held by UE122 may include all or part of the following information: the current RRC settings, the current security context, the PDCP status including the ROHC (RObust Header Compression) status, the C-RNTI (Cell Radio Network Temporary Identifier) ​​used by the source PCell, the cell identifier, and the physical cell identifier of the source PCell. The AS context of the UE held by any or all of eNB102 and gNB108 may include the same information as the AS context of the UE held by UE122, or it may include information different from the information included in the AS context of the UE held by UE122.

[0089] The security context may include all or part of the following at the AS level: the encryption key, the NH (Next Hop parameter), the NCC (Next Hop Chaining Counter parameter) used to derive the next hop access key, the identifier of the selected AS-level encryption algorithm, and the counter used for replay protection.

[0090] Next, we will explain the Serving Cell. The CA and / or DC described later... In terminal devices with an unconfigured RRC connection, the serving cell may consist of one primary cell (PCell). Furthermore, the CA and / or DC described later may be configured. In a terminal device in an RRC connection state, multiple serving cells may mean a set of multiple cells consisting of one or more special cells (SpCells) and one or more all secondary cells (SCells). SpCells may support PUCCH transmission and contention-based random access (CBRA), and SpCells may always be activated. PCells are RRC idle. It may be a cell used in the RRC connection establishment procedure when a terminal device transitions to an RRC connection state. Furthermore, the PCell may be used in the RRC connection re-establishment procedure when the terminal device re-establishes the RRC connection. It may be a cell. Also, PCell is used in the random access procedure during handover. It may be a cell used for purposes other than those mentioned above. PSCell may be a cell used in the random access procedure when adding a secondary node, as described later. SpCell may be a cell used for purposes other than those mentioned above.

[0091] If a group of serving cells configured by a terminal device consists of a SpCell and one or more SCells, it may be considered that the terminal device is configuring carrier aggregation (CA). Furthermore, for a terminal device configuring CA, a cell providing additional radio resources to a SpCell may be considered an SCell.

[0092] A group of serving cells configured by a terminal device in RRC, where the terminal device is the uplink For the cell where the link is set, the same timing reference cell and the same A group of serving cells that use Timing Advance values ​​may be called a Timing Advance Group (TAG). A TAG containing a MAC entity SpCell may represent a Primary Timing Advance Group (PTAG). A TAG other than a PTAG may represent a Secondary Timing Advance Group (STAG). One or more of the aforementioned TAGs may be configured for each cell group, as described later.

[0093] This section explains cell groups, which are configured by terminal devices at higher layers (such as RRC). A cell group may consist of one SpCell. Alternatively, a cell group may consist of one SpCell and one or more SCells. That is, a cell group may consist of one SpCell and, if necessary... A cell group may optionally consist of one or more SCells. A cell group may also be described as a set of cell(s).

[0094] Dual Connectivity (DC) is a technology that enables data communication using the radio resources of cell groups configured by a first base station device (first node) and a second base station device (second node). It may be a technique. When DC or MR-DC (described later) is performed, the base station equipment can communicate with the terminal equipment. Cell groups may be added. To perform DC (Data Center) operations, the first base station device may add a second base station device. The first base station device is called the Master Node (MN). Furthermore, the cell group formed by the master node may be called the Master Cell Group (MCG). The second base station device is called the Secondary Node (SN). It is acceptable to refer to it as such. Furthermore, the cell group formed by the secondary node may be called a Secondary Cell Group (SCG). Note that the master node and secondary node may be configured within the same base station equipment.

[0095] Furthermore, when a terminal device does not set a DC, the cell group that the terminal device sets may be called an MCG. The SpCell set by can be a PCell. Also, the terminal device can set an NR that does not have a DC set. It can be called a standalone device.

[0096] Furthermore, Multi-Radio Dual Connectivity (MR-DC) may be defined as a technology that performs DC using E-UTRA for MCG and NR for SCG. It is acceptable. Furthermore, MR-DC is a technology that performs DC using NR in both MCG and SCG. Good. MR-DC can be a technology included in DC. An example of MR-DC using E-UTRA in the MCG and NR in the SCG is EN-DC (E-UTRA-NR Dual Connectivity) which uses EPC in the core network, and An NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity) using 5GC in the A network is acceptable. Also, as an example of an MR-DC using NR in the MCG and E-UTRA in the SCG, there is an NE-DC (NR-E-UTRA Du) using 5GC in the core network. (Al Connectivity) is acceptable. Also, as an example of MR-DC using NR for both MCG and SCG, It is acceptable to have NR-DC (NR-NR Dual Connectivity) using 5GC in the core network.

[0097] In a terminal device, there may be one MAC entity for each cell group. For example, when a terminal device sets up DC or MR-DC, there may be one MAC entity for MCG and one MAC entity for SCG. The MAC entity for MCG in the terminal device can represent all states (RRC idle state, RRC connected state, and RRC inactive state). In terminal devices such as the above, the MAC entity for the SCG in the terminal device may always be established. In addition, the MAC entity for each cell group in the terminal device may be created by the terminal device when the terminal device sets up the SCG. In addition, the MAC entity for each cell group in the terminal device may always be established by the terminal device Configuration may be performed by receiving RRC signaling from a local station. If the MAC entity is associated with MCG, SpCell may mean PCell. Also, MAC entity If associated with an SCG, SpCell may mean Primary SCG Cell (PSCell). Also, if the MAC entity is not associated with a cell group, SpCell may mean PCell. PCell, PSCell, and SCell are serving cells. In EN-DC and NGEN-DC, the MAC entity for MCG is the E-UTRA MAC entity. It is acceptable for the MAC entity for SCG to be an NR MAC entity. Also, in NE-DC, the MAC entity for MCG may be an NR MAC entity, and the MAC entity for SCG may be an E-UTRA MAC entity. Also, in NR-DC, MCG The MAC entities for both and SCG may be NR MAC entities. The fact that there is one entity for each cell group can be rephrased as saying that there is one MAC entity for each SpCell. This can be rephrased as one MAC entity for each SpCell.

[0098] This section explains radio bearers. When a terminal device communicates with a base station device, a radio bearer (RB) is established between the terminal device and the base station device to establish a wireless connection. Good. The radio bearer used in CP may be called a Signaling Radio Bearer (SRB). The radio bearer used in UP may be called a Data Radio Bearer (DRB). Each radio bearer may be assigned a radio bearer identifier (Identity: ID). The radio bearer identifier for SRBs may be called an SRB identifier (SRB Identity, or SRB ID). The radio bearer identifier for DRBs may be called a DRB identifier (DRB Identity, or DRB ID). For E-UTRA, SRB0 to SRB2 may be defined, or other SRBs may be defined. For NR, SRB0 to SRB3 may be defined, or other SRBs may be defined. SRB0 may be an SRB for RRC messages transmitted and / or received using the logical channel CCCH. SRB1 is for RRC signaling and NAS before SRB2 is established. It may be an SRB for signaling. RRC signaling transmitted and / or received using SRB1 may include piggybacked NAS signaling. All RRC signaling and NAS signaling transmitted and / or received using SRB1 have a logical channel. DCCH of the RU may be used. SRB2 is for NAS signaling and for recording measurement information (logged It may be an SRB for RRC signaling that includes measurement information. All RRC signaling and NAS signaling transmitted and / or received includes logical chips. The DCCH of the channel may be used. Also, SRB2 may have a lower priority than SRB1. SRB3 may be an SRB for transmitting and / or receiving specific RRC signaling when a terminal device sets EN-DC, NGEN-DC, NR-DC, etc. Transmitting and / or receiving using SRB3 All RRC signaling and NAS signaling may use the DCCH of the logical channel. Other SRBs may be provided for other purposes. The DRB may be a wireless bearer for user data. RRC signaling transmitted and / or received using the DRB A logical channel (DTCH) may be used for the junction.

[0099] This section describes wireless bearers in terminal devices. Wireless bearers include RLC bearers. Good. An RLC bearer may consist of one or two RLC entities and a logical channel. When a bearer has two RLC entities, the RLC entity is the TM RLC entity. and / or in a unidirectional UM mode RLC entity, this may be a transmitting RLC entity and a receiving RLC entity. SRB0 may consist of one RLC bearer. RLC bearer of SRB0 SRB0 may consist of TM's RLC entities and logical channels. SRB0 may always be established in terminal devices in all states (RRC idle state, RRC connected state, and RRC inactive state, etc.). SRB1 may be established and / or configured by the terminal device in RRC when the terminal device transitions from the RRC idle state to the RRC connected state, based on RRC signaling received from the base station device. SRB1 consists of one PDCP entity and one or more RLC bearers. The RLC bearer of SRB1 may consist of the AM's RLC entity and logical channel. SRB2 receives from the base station equipment a terminal device in an RRC connection state with AS security activated. RRC signaling enables one connection to a terminal device and / or the terminal device to be configured with RRC. SRB2 may consist of one PDCP entity and one or more RLC bearers. The RLC bearers of SRB2 may consist of an AM RLC entity and a logical channel. Note that the PDCP on the base station device side of SRB1 and SRB2 may be located on the master node. SRB3 is established when a secondary node is added or changed in EN-DC, NGEN-DC, or NR-DC, and terminal devices with AS security enabled and RRC connection status are connected from the base station device. The received RRC signaling may establish and / or configure one RRC on the terminal device. SRB3 may be a direct SRB between the terminal device and the secondary node. SRB3 may consist of one PDCP entity and one or more RLC bearers. The array may consist of AM RLC entities and logical channels. SRB3 base station equipment The PDCP on the side may be located on the secondary node. The DRB may be established and / or configured on the terminal device by RRC signaling received from the base station device by the terminal device in an RRC connection state with AS security activated. The DRB is one PDCP entity and 1 It may consist of one or more RLC bearers. The RLC bearer of the DRB may consist of an AM or UM RLC entity and a logical channel.

[0100] In MR-DC, a wireless bearer on the master node where PDCP is located can be called an MN-terminated bearer. Also, in MR-DC, a secondary node A wireless bearer on which a PDCP is placed is called an SN-terminated bearer. That's fine. Furthermore, in MR-DC, a wireless bearer where the RLC bearer exists only in the MCG can be called an MCG bearer. Also, in MR-DC, if the RLC bearer exists only in the SCG... A wireless bearer that has both an MCG and an SCG can be called an SCG bearer. Also, in a DC, a wireless bearer that has both an RLC bearer and an SCG can be called a split bearer.

[0101] When a terminal device configures MR-DC, the bearer types of SRB1 and SRB2 established and / or configured by the terminal device may be MN-terminated MCG bearers and / or MN-terminated split bearers. Also, when a terminal device configures MR-DC, the bearer type of SRB3 established and / or configured by the terminal device may be SN-terminated SCG bearers. Also, when a terminal device configures MR-DC, the bearer type of DRB established and / or configured by the terminal device may be any of all bearer types.

[0102] For RLC bearers established and / or configured by a terminal device in a cell group composed of E-UTRA, the RLC entities established and / or configured by the terminal device may be E-UTRA RLC. Similarly, for RLC bearers established and / or configured by a terminal device in a cell group composed of NR, the RLC entities established and / or configured by the terminal device may be NR RLC. When a terminal device configures EN-DC, the PDCP entities established and / or configured by the terminal device for the MN termination MCG bearer may be E-UTRA RLC. The PT can be either E-UTRA PDCP or NR PDCP. Also, the terminal device sets EN-DC. In this case, the terminal device will be a wireless bearer of other bearer types, i.e., an MN termination split bearer. R, MN-terminated SCG bearer, SN-terminated MCG bearer, SN-terminated split bearer, and SN-terminated SCG bearer The PDCP established and / or set for R may be an NR PDCP. Also, when the terminal device sets NGEN-DC, NE-DC, or NR-DC, the terminal device sets all bearer types The PDCP entity established and / or configured for the wireless bearer may be an NR PDCP.

[0103] In NR, the DRB established and / or configured by the terminal device may be associated with one PDU session. The terminal device establishes and / or configures one SDAP entity for one PDU session. The SDAP entities, PDCP entities, RLC entities, and logical channels established and / or configured by the terminal device may be established and / or configured by the terminal device through RRC signaling received from the base station device.

[0104] Note that regardless of whether the terminal device configures MR-DC or not, the master node is eNB102. A network configuration with EPC104 as the core network may be called E-UTRA / EPC. A network configuration with eNB102 as the master node and 5GC110 as the core network may be called E-UTRA / 5GC. A network configuration with gNB108 as the master node and 5GC110 as the core network may be called NR, or NR / 5GC. When terminal devices do not configure MR-DC, the above master nodes... This can refer to a base station device that communicates with terminal devices.

[0105] This section describes the RRC signaling flow transmitted and received between terminal equipment and base station equipment. Figure 4 shows the flowchart for the various settings in the RRC according to this embodiment. This is a diagram illustrating an example. Figure 4 shows an example of the flow when RRC signaling is sent from the base station equipment (eNB102, and / or gNB108) to the terminal equipment (UE122).

[0106] In Figure 4, the base station device creates an RRC message (step S400). The creation of an RRC message by the base station device may be performed in order for the base station device to distribute system information (SI) or paging messages. The creation of a data entry involves the base station sending RRC signaling to a specific terminal device to perform a specific action. This may be done for the purpose of trust. Processes performed on a specific terminal device include, for example, security settings, RRC connection reconfiguration, handover to a different RAT, and RRC connection reconfiguration. This may include processes such as pausing the session and releasing the RRC connection. RRC connection resetting may include, for example, control of wireless bearers (establish, change, release, etc.) and control of cell groups (establish, add (Addition, modification, release, etc.), measurement settings, handover, security key updates, etc. Processing may be included. Also, the creation of RRC messages in the base station equipment is done by sending from the terminal equipment. This may be done in response to transmitted RRC signaling. Responses to RRC signaling transmitted from a terminal device may include, for example, responses to RRC setup requests, responses to RRC reconnection requests, and responses to RRC restart requests. RRC messages contain various informational and configuration information (parameters). These parameters are fields and / or information elements. You can call it that, and it is written using the ASN.1 (Abstract Syntax Notation One) notation method. You may do so.

[0107] In Figure 4, the base station device then transmits the created RRC signaling to the terminal device (S Step S402). Next, the terminal device performs any necessary processing, such as configuration, according to the RRC signaling it has received (Step S404). The terminal device that has performed the processing may send an RRC signaling response to the base station device (not shown).

[0108] RRC signaling may be used for purposes other than those mentioned above.

[0109] In MR-DC, the RRC signaling for SCG settings (cell group settings, wireless bearer settings, measurement settings, etc.) may be transmitted between the master node and the terminal device. For example, in EN-DC or NGEN-DC, the RRC signaling transmitted between eNB102 and UE122 is used. The RRC signaling for E-UTRA may include the RRC signaling for NR in the form of a container. Similarly, in NE-DC, the RRC signaling for NR transmitted and received between gNB108 and UE122 may include the RRC signaling for E-UTRA in the form of a container. RRC signaling for SCG-side configuration may be transmitted and received between the master node and the secondary node.

[0110] Note that the RRC signature for E-UTRA sent from eNB102 to UE122 is not limited to cases where MR-DC is used. The signaling may include RRC signaling for NR, and the RRC signaling for NR transmitted from gNB108 to UE122 may include RRC signaling for E-UTRA.

[0111] Next, we will explain handover in LTE and NR. Handover may be the process by which a terminal device in an RRC-connected state changes the serving cell from the source SpCell to the target SpCell. Handover may be part of the mobility control performed by the RRC. In this context, the handover is indicated by an RRC signal that receives a handover from the base station equipment. It may be done based on the signaling. RRC signaling that indicates a handover is, A message regarding the reconfiguration of an RRC connection, including an information element containing parameters that instruct the user (e.g., a MobilityControlInfo information element or a ReconfigurationWithSync information element). It may be so. Note that the MobilityControlInfo information element is a mobility control setting information element. This may be referred to as mobility control settings or mobility control information. The ReconfigurationWithSync information element may also be referred to as a synchronized reconfiguration information element. In addition to that, or Instead, the RRC signaling that instructs a handover is a message indicating the movement of another RAT to a cell (e.g., MobilityFromEUTRACommand or MobilityFromNRCommand). It is also acceptable for the handover to be triggered by RRC. The conditions for performing the operation include, among others, that AS security is activated, that the terminal device has established an SRB2, and that at least one DRB is established. Or all conditions may be included.

[0112] This section explains an example of parameters included in the message regarding the reconfiguration of the RRC connection. Figure 7 shows the message regarding the reconfiguration of the RRC connection in NR, as shown in Figure 4. This is an example of an ASN.1 description representing a field and / or information element. This is not limited to Figure 7. In the example of ASN.1 in the embodiment, <omitted> indicates that other information is omitted, not part of the ASN.1 notation. Information elements may also be omitted where <omitted> is not present. In this embodiment, the example of ASN.1 represents an example of the RRC signaling parameters in this embodiment, and other names or notations may be used. Furthermore, the example of ASN.1 is used in the description. To avoid complexity, only examples of key information closely related to this embodiment are shown. In each embodiment, the parameters described in ASN.1 are referred to as fields and information. In some cases, all information elements are referred to as "information elements" without distinction. Furthermore, in each embodiment, the fields and / or information elements included in the RRC signaling, as described in ASN.1, are: This can be rephrased as "information," or in addition to or instead of information, it can be rephrased as "parameters." The message regarding the resetting of the RRC connection may be the RRC resetting message in NR. Furthermore, the message regarding the resetting of the RRC connection may be the RRC connection resetting message in E-UTRA.

[0113] In Figure 7, the message regarding the reconfiguration of the RRC connection may include information elements used for security key updates (MasterKeyUpdate information elements). The MasterKeyUpdate information elements may include some or all of the following: information elements indicating whether or not to derive a new security key (keySetChangeIndicator information elements), information elements indicating NCC parameters (nextHopChainingCount information elements), and information elements indicating fields for transferring UE-specific NAS layer information between the network and the terminal device (nas-Container information elements). It may include a section.

[0114] In Figure 7, the message regarding the reconfiguration of the RRC connection contains information elements (CellGroupConfig information elements) used for setting, changing, releasing, etc., of the NR's MCG or SCG cell group. It may be included. Messages regarding the reconfiguration of RRC connections may independently include CellGroupConfig information elements for MCG configuration and CellGroupConfig information elements for SCG configuration. It is acceptable to include it. The CellGroupConfig information element is a cell group setting information element, or cell group It may also be called a loop setting.

[0115] The CellGroupConfig information element contains identifier information to identify this cell group as follows: The cellGroupId information element may be included.

[0116] The CellGroupConfig information element may include the RLC-BearerConfig information element as information used to configure the RLC entity.

[0117] The CellGroupConfig information element may include the MAC-CellGroupConfig information element, which is used to set the MAC parameters for that cell group.

[0118] The CellGroupConfig information element may include the PhysicalCellGroupConfig information element, which is used to set the PHY(L1) parameters specific to that cell group.

[0119] The CellGroupConfig information element contains the parameter settings for the SpCell of that cell group. The information used may include SpCellConfig information elements. SpCellConfig information elements may also be called SpCell configuration information elements or SpCell configurations.

[0120] The CellGroupConfig information element may include a SCellConfig information element for each SCell, which is used to set parameters for one or more SCells in that cell group. The SCellConfig information element may also be called a SCell setting information element or SCell setting.

[0121] The MAC-CellGroupConfig information element may include a TAG-Config information element as information used to set parameters related to TAGs. The TAG-Config information element may include identifiers (TAG-Id) of one or more TAGs set by the terminal device and the value of the time adjustment timer corresponding to the identifier of that TAG.

[0122] The SpCellConfig information element contains terminal device-specific (UE-specific) parameters related to SpCell. The ServingCellConfig information element may be included as information used for setting the SCell. Furthermore, the SCellConfig information element may include this ServingCellConfig information element as information used for setting terminal device-specific (UE specific) parameters related to the SCell. The CellGroupConfig information element is used for setting terminal device-specific parameters related to the SpCell and each SCell. Each serving cell may contain a ServingCellConfig information element. Each ServingCellConfig information element may contain a TAG identifier (TAG-Id) indicating which TAG within the cell group the serving cell belongs to. In addition, the ServingCellConfig information element may contain terminal device-specific information. In addition to parameters, cell-specific parameters may also be included.

[0123] Each ServingCellConfig information element may include an initialDownlinkBWP, which indicates the BWP-DownlinkDedicated information element, as a terminal device-specific setting for the initial downlink BWP. The BWP-DownlinkDedicated information element is also referred to as a downlink BWP-specific setting. In addition to or instead of the above, each ServingCellConfig information element may include some or all of the first active downlink BWP identifier (firstActiveDownlinkBWP-Id), the BWP inactivity timer (bwp-InactivityTimer), and the default downlink BWP identifier (defaultDownlinkBWP-Id).

[0124] The ServingCellConfig information element, used for setting terminal device-specific parameters for each SCell, may include a DormantBWP-Config information element as a setting for a dormant BWP for the SCell. The DormantBWP-Config information element is also referred to as the dormant BWP setting. For example, the DormantBWP-Config information element may include a dormant BWP identifier (dormantBWP-Id).

[0125] The SCellConfig information element may include an RRC parameter (sCellState) that indicates whether SCell is activated or not during SCell configuration. sCellState is also referred to as the SCell state setting. Example For example, if the SCellConfig information element contains sCellState, or instead, The RRC entity of the terminal device sets the sCellState contained in the SCellConfig information element to activate. If configured, the MAC entity of the terminal device may activate the SCell, and in addition to or instead, the RRC layer of the terminal device may configure its lower layers (such as the MAC entity) to consider that the SCell is activated. Alternatively, for example, if the SCellConfig information element does not contain sCellState In addition, the MAC entity of the terminal device may deactivate the SCell, or, in addition to or instead of doing so, the RRC layer of the terminal device may configure its lower layers (such as the MAC entity) to consider that the SCell is deactivated.

[0126] The ServingCellConfig information element for setting terminal-specific parameters for each SCell that the terminal device has not set PUCCH may include an SCell inactivity timer.

[0127] Each ServingCellConfig information element has an UplinkConfig information element as an uplink setting. It may include the following. The UplinkConfig information element is also called the uplink setting. The UplinkConfig information element includes terminal device-specific settings for the initial uplink BWP (initial uplink BWP). The BWP-UplinkDedicated information element may include initialUplinkBWP. The BWP-UplinkDedicated information element is also referred to as the uplink BWP-only setting. In addition to or instead Furthermore, the UplinkConfig information element may include the first active uplink BWP identifier (firstActiveUplinkBWP-Id).

[0128] The SpCellConfig information element may include a ReconfigurationWithSync information element, which contains information necessary for the process of asynchronous reconfiguration from a source SpCell to a target SpCell. The ReconfigurationWithSync information element is as described above. This may be a synchronized reconfiguration information element. If the MCG's SpCellConfig information element includes a ReconfigurationWithSync information element, the synchronized reconfiguration process for the target SpCell may be a handover. If the SCG's SpCellConfig information element includes a ReconfigurationWithSync information element, the synchronized reconfiguration process for the target SpCell may be a PSCell addition or PSCell modification.

[0129] The ReconfigurationWithSync information element and the SCellConfig information element may include a ServingCellConfigCommon information element, which is used to set cell-specific parameters for a serving cell. The ServingCellConfigCommon information element may include parameters typically obtained from the cell's SSB, MIB, or one or more SIBs when a terminal device accesses the cell from an idle state.

[0130] The ReconfigurationWithSync information element includes, for example, the cell group of the target SpCell. The information element of ReconfigurationWithSync may include information about the C-RNTI value used. For example, it may include information about the parameters of timer T304, which will be described later. The ReconfigurationWithSync information element may include, for example, the contention criterion randomizer in the target SpCell. Contention-based Random Access (CBRA) procedure or contention-free access The RACH-ConfigDedicated information element may be included as information necessary for executing a contention-free Random Access (CFRA) procedure. This is also called a dedicated setting.

[0131] Figure 8 shows the SCellConfig information element and the ServingCellConfigCommon information element contained within the ReconfigurationWithSync information element within the SpCellConfig information element in Figure 7. This is an example of an ASN.1 description representing a world and / or information element.

[0132] The ServingCellConfigCommon information element includes the physical cell identifier (physCellId) of that cell. It's okay to be born.

[0133] The ServingCellConfigCommon information element contains cell-specific (cell-common) downlink parameters. The information provided may include the DownlinkConfigCommon information element. The DownlinkConfigCommon information element is also referred to as the common downlink settings.

[0134] The ServingCellConfigCommon information element contains cell-specific (cell-common) uplink parameters. The information provided may include the UplinkConfigCommon information element. The UplinkConfigCommon information element is also referred to as the common uplink settings.

[0135] The ServingCellConfigCommon information element contains information for all uplink transmissions in that cell. The value of N_{TA, offset} to which it is applied may be included.

[0136] The DownlinkConfigCommon information element may include the FrequencyInfoDL information element as basic information about the downlink carrier and transmissions on that downlink carrier. The FrequencyInfoDL information element may include SSB frequency information.

[0137] The DownlinkConfigCommon information element contains the initial downlink BWP (initial downlink) for that cell. The BWP setting includes initialDownlinkBWP, which indicates the BWP-DownlinkCommon information element. That's fine. In addition, or instead, the DownlinkConfigCommon information element may include initialDownlinkBWP-RedCap, which indicates the BWP-DownlinkCommon information element that one or more performance-limited terminals (RedCap UEs) use instead of initialDownlinkBWP. The BWP-DownlinkCommon information element is also referred to as the downlink BWP common setting.

[0138] The BWP-DownlinkCommon information element may include BWP information elements as information for the terminal device to set generic parameters of BWP.

[0139] The BWP-DownlinkCommon information element may include the PDCCH-ConfigCommon information element, which provides information for the terminal device to set cell-specific parameters for the PDCCH of this BWP. The PDCCH-ConfigCommon information element is also referred to as the PDCCH common settings.

[0140] The BWP-DownlinkCommon information element may include the PDSCH-ConfigCommon information element, which provides information for the terminal device to set cell-specific parameters for the PDSCH of this BWP. The PDSCH-ConfigCommon information element is also referred to as the PDSCH common settings.

[0141] The PDCCH-ConfigCommon information element may include a SearchSpaceZero information element as information for the terminal device to set the parameters of the common search space (CSS) #0. This SearchSpaceZero information element may be included in the PDCCH-ConfigCommon information element only if the BWP is the initial downlink BWP.

[0142] The PDCCH-ConfigCommon information element contains information for a terminal device to set the parameters of the common CORESET#0 used in one or more common search spaces and one or more UE-specific search spaces, Co The ControlResourceSetZero information element may be included. This ControlResourceSetZero information element may be included in the PDCCH-ConfigCommon information element only if the BWP is the initial downlink BWP.

[0143] The PDCCH-ConfigCommon information element contains additional common CORESET parameters set by the terminal device. The ControlResourceSet information element may be included as information for determining the value.

[0144] The PDCCH-ConfigCommon information element may contain a list of information elements (SearchSpace information elements) (commonSearchSpaceList) that indicate one or more additional CSS settings.

[0145] The PDCCH-ConfigCommon information element contains information (searchSpaceSIB1) indicating which CSS setting in the commonSearchSpaceList corresponds to the search space setting for system information (SIB1). It may be included.

[0146] The PDCCH-ConfigCommon information element may include information (searchSpaceOtherSystemInformation) indicating which CSS setting in the commonSearchSpaceList corresponds to the search space setting for system information (SIB2 and later).

[0147] The PDCCH-ConfigCommon information element may include information (pagingSearchSpace) indicating which CSS setting in commonSearchSpaceList is responsible for setting the search space for paging messages.

[0148] The UplinkConfigCommon information element may include the FrequencyInfoUL information element, which sets the absolute uplink frequency and lists multiple virtual carriers specific to each subcarrier. For example, the FrequencyInfoUL information element may include the maximum transmission frequency. It may include information indicating power consumption.

[0149] The UplinkConfigCommon information element may include an initialUplinkBWP, which indicates the BWP-UplinkCommon information element, as the initial uplink BWP setting for that cell. In addition to or instead of the above, the UplinkConfigCommon information element may contain the BWP-UplinkCommon information that one or more performance-limited terminals (RedCap UEs) use instead of initialUplinkBWP. The initialUplinkBWP-RedCap element may be included to indicate the element. The BWP-UplinkCommon information element is above This is also called the BWP common settings for linking.

[0150] The BWP-UplinkCommon information element may include BWP information elements as information for the terminal device to set generic parameters of the BWP.

[0151] The BWP-UplinkCommon information element may include the PUCCH-ConfigCommon information element, which provides information for the terminal device to set cell-specific parameters for PUCCH of this BWP. The PUCCH-ConfigCommon information element is also referred to as the PUCCH common settings.

[0152] The BWP-UplinkCommon information element may include the PUSCH-ConfigCommon information element, which provides information for the terminal device to set cell-specific parameters for the BWP's PUSCH function. The PUSCH-ConfigCommon information element is also referred to as the PUSCH common settings.

[0153] The BWP-UplinkCommon information element may include the RACH-ConfigCommon information element as information for terminal devices to set cell-specific random access parameters. The RACH-ConfigCommon information element is also referred to as the RACH common setting.

[0154] Note that each of the above information elements may include other information besides the information described.

[0155] This document describes the RRC reset procedure. The RRC reset procedure involves the terminal device resetting the RRC connection. Based on the message regarding the reconfiguration, modify the RRC connection. The procedure may be any of the following. Furthermore, the purpose of the RRC reset procedure may be some or all of (A) through (F) below. (A) Establish, modify, and / or release a wireless bearer. (B) Perform a reconfiguration with synchronization. (C) Set up, modify, and / or release the measurement. and (D) Adding, modifying, and / or releasing SCells and cell groups. (E) Add, modify, and / or release conditional handover (CHO) settings. (F) Adding, modifying, and / or releasing conditional PSCell change (CPC) or conditional PSCell addition (CPA) settings.

[0156] The base station equipment (Network) may initiate the RRC reset procedure for terminal devices in the RRC_CONNECTED state. "Initiating the sequence" means "the base station equipment will initiate the RRC connection reconfiguration process with the terminal equipment." This can be rephrased as "send a message."

[0157] When the terminal device receives a message regarding the reconfiguration of the RRC connection, When performing a conditional reset (CHO, CPA, or CPC), some or all of the following RRP processes (A) through (D) may be performed. (Processing RRP) (A) If the message regarding the reconfiguration of the RRC connection includes the MCG cell group settings If so, the cell group settings are used to configure the cell group. In addition, if the cell group settings include a SpCell setting that contains synchronized reconfiguration information elements, a synchronized reconfiguration is performed. (B) If the message regarding the reconfiguration of the RRC connection includes the SCG cell group settings If so, the cell group settings are used to configure the cell group. In addition, if the cell group settings include a SpCell setting with synchronized reconfiguration information elements, a synchronized reconfiguration is performed. (C) If the message regarding the reconfiguration of the RRC connection contains information about conditional reconfiguration, the conditional reconfiguration process will be performed using that information. (D) To transmit using the new settings, an RRC reconfiguration completion message is submitted to the lower layers of the terminal device (PHY, MAC, etc.).

[0158] The terminal device may perform some or all of the following RWS processes (A) through (G) in order to execute a synchronized reconfiguration. This can be rephrased as "perform the configuration" or "trigger a reconfiguration with synchronization." (Processing RWS) (A) If this procedure is performed for MCG, or if this procedure is performed for RRC Connect The message regarding the reset of the system includes an embedded E-UTRA or NR RRC signal. If performed for an SCG that has not been notified of deactivation within the ring, the synchronized reset information The value of timer T304, described later, included in the information element is set, and timer T304 for the corresponding SpCell is started. (B) If the synchronized reset information element contains a frequencyInfoDL information element, it is determined that the target SpCell is the cell indicated by the physical cell identifier included in the synchronized reset information element, which is located at the SSB frequency indicated by the frequencyInfoDL information element. If the information element does not contain the frequencyInfoDL information element, the target SpCell will This is indicated by the physical cell identifier included in the synchronized reset information element, which is on the same SSB frequency as the SpCell. Determine that it is the cell to be processed. (C) Start downlink synchronization to the target SpCell. (D) If the timing information required for the random access procedure is not held, obtain the MIB of the target SpCell. (E) Reset the MAC entity of the cell group to be subject to synchronization reset. (F) Apply the value of the new UE identifier (newUE-Identity) included in the synchronization reset information element as the C-RNTI for the cell group to be subject to synchronization reset. (G) Configure the lower layer (PHY, etc.) of RRC according to the SpCell common configuration.

[0159] Conditional reconfiguration will be described. The terminal device receives one or more conditional reconfiguration information elements from the network, and thereby the terminal device sets candidate target SpCells respectively associated with the conditional reconfiguration information elements received from the network. The terminal device evaluates the states of the set candidate target SpCells. The terminal device performs the evaluation and applies one of the conditional RRC reconfiguration information elements included in the conditional reconfiguration information element associated with one or more candidate target SpCells that satisfy the execution conditions. Also, the terminal device may hold a list of entries (VarConditionalReconfig) described later for conditional reconfiguration.

[0160] When the candidate target SpCell is the SpCell of the MCG (i.e., the PCell), the conditional reconfiguration may be referred to as conditional handover. Also, when the candidate target SpCell is the SpCell of the SCG (i.e., the PSCell), the conditional reconfiguration may be referred to as conditional PSCell addition and / or conditional PSCell change.

[0161] ​​​​​The terminal device processes information regarding conditional resetting (for example, conditions) as part of the conditional resetting setting process. Based on the receipt of the conditional reset information element, the conditional reset information is attempted to If the row condition reset information element (attemptCondReconfig) is included, then in the cell selection during the RRC connection re-establishment procedure described below, if the selected cell is a target candidate cell (e.g., candidate target SpCell) and the cell selection is the first cell selection after a conditional reset failure (e.g., expiration of timer T304), then a conditional reset may be performed.

[0162] As part of the conditional reset setting process, if the information regarding the conditional reset includes an entry deletion list (condReconfigToRemoveList), the terminal device may remove the conditional reset setting specified in the entry deletion list from the settings held by the terminal device. Specifically, if an entry identifier (condReconfigId) included in the entry deletion list is included in the list of entries held by the terminal device, the terminal device may delete the entry corresponding to the entry identifier from the list of entries held by the terminal device.

[0163] In the following explanation, the list of conditional reset entries held by the terminal device will also be simply referred to as the entry list. That is, unless otherwise specified, "entry list" in the following explanation refers to the list of conditional reset entries held by the terminal device. The conditional reset entry list may also be a variable named VarConditionalReconfig. The entry identifier will also be simply referred to as the entry identifier.

[0164] As part of the conditional reset configuration process, if the information regarding the conditional reset includes an entry addition / modification list (condReconfigToAddModList), the terminal device may add or modify the conditional reset settings included in the entry addition / modification list to the settings held by the terminal device. The entry addition / modification list may be a list of one or more conditional reset information elements. The terminal device may configure each entry with a conditional reset information element. The conditional reset information element may include an entry identifier, an execution condition, and a conditional RRC reset information element. stomach.

[0165] Specifically, if each entry identifier included in the entry addition / modification list exists in an entry in the entry list, the terminal device may perform the following processes (A) and / or (B). (A) If an entry in the Addition / Modification List of an entry contains an execution condition (condExecutionCond), replace the execution condition of the entry in the entry list that matches the entry identifier of that entry with the execution condition contained in the Addition / Modification List of that entry. (B) If an entry in the additional modification list of entries contains a conditional RRC reset information element (condRRCReconfig), then the entry identifier of this entry matches the entry entry Replace the conditional RRC reset information element of the entry with the conditional RRC reset information element included in the additional modification list for that entry.

[0166] Furthermore, if an entry identifier included in the entry addition / modification list is not included in the entry list, the terminal device may add a new entry to the entry list corresponding to the entry identifier that is not included in the entry list.

[0167] The entry deletion list may be a list of one or more entry identifiers to be deleted. Each entry included in the entry addition / modification list includes an entry identifier and may also include execution conditions and / or conditional RRC reset information elements. Each entry may be associated with one of one or more candidate target SpCells. The entry identifier is used to identify each CHO, CPA, and CPC entry. The identifier may be one or more entries. The entry list may contain one entry identifier, one or more execution conditions, and one conditional RRC reset information element. The entry list held by the terminal device is an entry If not included, the terminal device may maintain an empty list. Execution conditions may be any conditions that must be met to trigger the execution of conditional reset. Conditional RRC reset information required. The term "basic" refers to the mechanism for resetting the RRC connection that is applied when the aforementioned execution conditions are met. It may be a message. The message regarding the reconfiguration of the RRC connection is a candidate message. This message may be used to connect to GetSpCell.

[0168] A terminal device may evaluate the execution conditions of entries included in the entry list it holds. If the entry list held by the terminal device is empty or if it does not hold an entry list, it does not need to evaluate the execution conditions.

[0169] Conditional resetting is performed when a terminal device evaluates the execution conditions of an entry in the entry list it holds, and if one or more execution conditions are met, applies the conditional RRC resetting information element contained in the entry containing those execution conditions. Applying a conditional RRC reset information element means executing an RRC reset procedure using that conditional RRC reset information element.

[0170] If there are multiple entries that satisfy the execution conditions, the terminal device selects one entry from among the multiple entries that satisfy the execution conditions and performs a conditional RRC rerun of the selected entry. You may apply the configuration information elements.

[0171] The MAC entity of the terminal device is reset from a higher layer (e.g., RRC). If a reset of the MAC entity is requested, the following processing of MR (A) The MAC entity may perform some or all of (A) through (N). The MAC entity of the terminal device may perform some or all of the following processes MR if a partial reset of the MAC entity is requested from a higher layer (e.g., RRC). A partial reset of the terminal device may simply be called a partial MAC reset. The process performed in a partial MAC reset may be a process in which only a portion of the process performed in a MAC reset is performed. The process performed in a partial MAC reset may be a process in which some of the process performed in a MAC reset is not performed. The MAC entity of a terminal device may perform a MAC reset based on an instruction from T to the MAC entity of the terminal device. In addition to or instead of this, the MAC entity of a terminal device may perform a partial MAC reset based on an instruction from the RRC entity of the terminal device to the MAC entity of the terminal device.

[0172] (Processing MR) (A) Initialize the parameter Bj set by the terminal device for each logical channel to 0. (B) Except for some timers including at least the time adjustment timer, stop all running timers. (C) Set the value of the New Data Indicator (NDI) of all uplink HARQ processes to 0. (D) If there is an ongoing random access procedure, stop that random access procedure. (E) If there are explicitly signalled resources for contention-free random access (CFRA) of the 4-step and 2-step RA types, discard those resources. (F) Flash the buffer of Msg3. (G) Flash the buffer of MSGA. (H) If there is a triggered Scheduling Request (SR) procedure, cancel that SR procedure. (I) If there is a triggered Buffer Status Reporting (BSR) procedure, cancel that BSR procedure. (J) If there is a triggered Power Headroom Reporting (PHR) procedure, cancel that PHR procedure. (K) Flash the soft buffers of all downlink HARQ processes. (L) If there is a triggered Beam Failure Reporting (BFR), cancel that BFR. (M) If there is a Temporary C-RNTI, release that Temporary C-RNTI. (N) Reset all BFI_COUNTERs.

[0173] This document explains the procedure for re-establishing an RRC connection. An establishment procedure may be a procedure for a terminal device to re-establish an RRC connection based on an RRC re-establishment message. The RRC connection re-establishment procedure may also be called an RRC re-establishment procedure. In an RRC connection re-establishment procedure, the terminal device may send an RRC re-establishment request message to the base station device (Network), and then, based on receiving an RRC re-establishment message from the base station device, determine that the re-establishment of the RRC connection was successful and send an RRC re-establishment complete message to the base station device. The terminal device determines that the re-establishment of the RRC connection was successful, and the base station device is informed that the RRC connection has been re-established. The order in which the connection establishment completion message is sent does not matter. Furthermore, a terminal device in the RRC_CONNECTED state may initiate the above procedure to continue the RRC connection. Re-establishing the RRC connection. The base station device finds a valid UE context (the UE context held by the terminal device) It succeeds if it can be verified that it is a kill. Or, if the UE context If a strike cannot be obtained, the base station equipment will respond using an RRC setup message. You may do so.

[0174] When initiating the RRC connection re-establishment procedure, the terminal device may perform some or all of the following RRI processes (A) through (C). (Processing RRI) (A) If it is running, stop timer T304. (B) If the terminal device has not set the attempt condition reset information element (attemptCondReconfig), perform some or all of the following processes (B-1) to (B-5). (C) Perform cell selection and if a suitable NR cell is selected, perform some or all of the following processes (C-1) to (C-2).

[0175] (B-1) Reset the MAC entity. (B-2) If the terminal device has configured it, release the SpCell configuration. (B-3) Suspend all radio bearers except SRB0. (B-4) If the terminal device has configured it, release one or more SCells of the MCG. (B-5) If the terminal device has MR-DC configured, perform an MR-DC release.

[0176] (C-1) Essential system information that is valid and up-to-date. To ensure that one possesses it. (C-2) If cell selection is triggered by detection of MCG radio link failure, MCG synchronization reset failure (i.e., expiration of timer T304), Furthermore, the terminal device has set the attempt condition reset information element (attemptCondReconfig), and The selected cell is included in the MCG conditional reset entry list (VarConditionalReconfig) If it is one of the candidate cells for the synchronized reconfiguration information element, the terminal device applies the conditional RRC reconfiguration information element (condRRCReconfig) associated with the selected cell and performs part or all of the above RRP process; otherwise, it performs part or all of the following processes (C-2-1) to (C-2-4); and if the terminal device has set an attempt conditional reconfiguration information element (attemptCondReconfig), it performs part or all of the following processes (C-2-5) to (C-2-7). The department will be implemented.

[0177] (C-2-1) Apply the values ​​of default L1 parameters other than those provided in SIB1 as the values ​​specified in the corresponding physical layer specification. (C-2-2) Apply the default MAC cell group configuration. (C-2-3) Apply the CCCH settings. (C-2-4) Start sending the RRC re-establishment request message.

[0178] (C-2-5) Reset the MAC entity. (C-2-6) If the terminal device has configured it, release the SpCell configuration. (C-2-7) If the terminal device is configured, release one or more SCells of the MCG To release.

[0179] The aforementioned timer T304 is triggered when the terminal device resets the RRC connection, which includes a synchronized reset information element. The process may start upon receiving a message regarding the settings and stop upon successful completion of the random access procedure on the SpCell corresponding to the synchronized reconfiguration information element. Furthermore, if the timer T304 described above expires, the terminal device may perform the RRC connection re-establishment procedure. It may be started. In addition to or instead of the above, the timer T304 shall notify that the LTM cell switching process described below has been triggered from a lower layer (such as the MAC layer), and / or It may start based on the execution (performance) of the LTM cell switching process after cell selection. In addition to or instead of this, the timer T304 described above may stop for the same HARQ process based on the reception of a PDCCH addressed to C-RNTI after the initial uplink transmission, in the case of an LTM cell switching that does not involve the execution of a random access procedure.

[0180] Now, let's explain the bandwidth portion (BWP).

[0181] The BWP may be part or all of the serving cell's bandwidth. The BWP may also be called a Carrier BWP. A terminal device may configure one or more BWPs. The terminal device associates a BWP with a synchronization signal detected during the initial cell search. It may also be set by the information contained in the stem information. In addition, some BWPs perform an initial cell search. The frequency bandwidth may correspond to the frequency at which the operation is performed. Alternatively, the terminal device may receive a BWP from the base station device via RRC signaling (e.g., Dedicated RRC signaling) and set the received BWP using RRC. Furthermore, the terminal device may set downlink BWPs (DL BWP) and uplink BWPs (UL BWP) individually. Also, one or more uplink BWPs may be associated with one or more downlink BWPs. The association between uplink BWPs and downlink BWPs may be a default association, an association via RRC signaling (e.g., Dedicated RRC signaling), or an association via physical layer signaling (e.g., an association via downlink control information (DCI) notified on the downlink control channel). A combination of these may also be used. Furthermore, the terminal device may set CORESET in the BWP of the downlink.

[0182] A BWP may consist of a group of consecutive Physical Resource Blocks (PRBs). Furthermore, a connected terminal device may have one or more BWPs for each component carrier. You may set the BWP parameters for each component carrier. (A) Type of cyclic prefix, (B) Subcarrier spacing, (C) Frequency position of BWP ( For example, the starting position or center frequency position on the lower frequency side of the BWP (the frequency position may be, for example, an ARFCN, or an offset from a specific subcarrier of the serving cell. The unit of the offset may be a subcarrier unit or a resource block unit. The terminal device may set both an ARFCN and an offset.) (D) the bandwidth of the BWP (e.g., the number of PRBs), (E) resource setting information for the control signals, and (F) some or all of the center frequency position of the SS block (the frequency position may be, for example, an ARFCN, or an offset from a specific subcarrier of the serving cell. The unit of the offset may be in subcarrier units or resource block units. The terminal device may set both the ARFCN and the offset). The resource setting information for the control signals may also be included in the BWP settings of at least some or all of the PCell and / or PSCell.

[0183] The terminal device will select one or more configured BWPs, and the Active BWP will be... The terminal device may send and receive data in one of its associated serving cells. You may set one or more BWPs. The terminal device has one associated service Of the one or more BWPs set for a moving cell, at a given time, a maximum of 1 One uplink BWP and / or up to one downlink BWP may be configured to be the Active BWP. The downlink Active BWP is also called the Active DL BWP. Active BWP is also referred to as Active UL BWP. Furthermore, among the BWPs configured by a terminal device (one or more), BWPs that are not Active BWPs may be referred to as Inactive BWPs.

[0184] Next, we will explain BWP activation / deactivation. BWP activation can mean activating a BWP, or activating an inactive BWP. BWP deactivation can mean deactivating a BWP, or inactivating an active BWP. BWP switching in a serving cell is used to activate an inactive BWP and deactivate an active BWP.

[0185] BWP switching is indicated by PDCCH, BWP inactivity timer, RRC signaling, or MAC for initiating a random access procedure, indicating a downlink assignment or uplink grant. The entity is controlled by itself. The Active BWP of a serving cell is indicated by RRC or PDCCH.

[0186] Next, we will explain the BWP inactivation timer. For each activated serving cell for which the terminal device has set the BWP inactivation timer, the MAC entity... The following (A) will be performed. Also, the BWP inactivity timer will be named bwp-InactivityTimer. A timer would also work. (A) If any of the following conditions (A-1) through (A-4) are met, the MAC entity performs (B) and (D) below. (A-1) The UE sets the identifier for the default downlink BWP (defaultDownlinkBWP-Id) Furthermore, the Active DL BWP is not the BWP indicated by defaultDownlinkBWP-Id, and the Active DL BWP is not the BWP indicated by the dormant BWP identifier (dormantBWP-Id). (A-2) Identification that the UE is not a performance-limited terminal (RedCap UE) and that the UE is the default downlink BWP. No child (defaultDownlinkBWP-Id) is set, the Active DL BWP is not initialDownlinkBWP, and the Active DL BWP is not the BWP indicated by the dormant BWP identifier (dormantBWP-Id). (A-3) The UE is a performance-limited terminal (RedCap UE), and the UE is identified as the default downlink BWP. If a child (defaultDownlinkBWP-Id) is not set, the UE will be the initial downlink for performance-limited devices. The BWP (initialDownlinkBWP-RedCap) is not set, and the Active DL BWP is not initialDownlinkBWP. (A-4) The UE is a performance-limited terminal (RedCap UE), and the UE is identified as the default downlink BWP. If a child (defaultDownlinkBWP-Id) is not set, the UE will be the initial downlink for performance-limited devices. The BWP (initialDownlinkBWP-RedCap) is set, and the Active DL BWP is not initialDownlinkBWP-RedCap. (B) If Active BWP is assigned to a downlink or uplink If a PDCCH addressed to C-RNTI or CS-RNTI indicating a grant is received, or if a PDCCH addressed to C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant for an Active BWP is received, or if a MAC PDU is sent with a configured uplink grant, or if a configured downlink If a MAC PDU is received via signing, the MAC entity performs (C) below. (C) If the random access procedure associated with this serving cell is not running or, the running random access procedure associated with this serving cell has been successfully completed by receiving a PDCCH addressed to C-RNTI. Then, start or restart the BWP inactivity timer associated with Active DL BWP. (D) If the BWP deactivation timer associated with Active DL BWP expires The MAC entity then performs (E) below. (E) If the UE has set defaultDownlinkBWP-Id, the BWP will be switched to the BWP indicated by this defaultDownlinkBWP-Id; otherwise, the MAC entity will do the following (F) implement. (F) If the UE is a performance-limited terminal (RedCap UE) and the UE has configured an initial downlink BWP for performance-limited terminals (initialDownlinkBWP-RedCap), then the BWP switch will be performed to this initialDownlinkBWP-RedCap; otherwise, the BWP will be switched to initialDownlinkBWP. To do so.

[0187] Furthermore, if the MAC entity receives a PDCCH for BWP switching and switches the Active DL BWP, it performs (A) below. (A) If any of the following conditions (A-1) through (A-4) are met, start or restart the BWP inactivity timer associated with the Active DL BWP. (A-1) The UE sets the identifier for the default downlink BWP (defaultDownlinkBWP-Id) Furthermore, the MAC entity switches to a BWP for a downlink that is not indicated in either defaultDownlinkBWP-Id or dormantBWP identifier (dormantBWP-Id). (A-2) Identification that the UE is not a performance-limited terminal (RedCap UE) and that the UE is the default downlink BWP. Switch to a downlink BWP that does not have a child (defaultDownlinkBWP-Id), whose MAC entity is not initialDownlinkBWP, and is not indicated by a dormant BWP identifier (dormantBWP-Id). (A-3) The UE is a performance-limited terminal (RedCap UE), and the UE is identified as the default downlink BWP. If a child (defaultDownlinkBWP-Id) is not set, the UE will be the initial downlink for performance-limited devices. If BWP (initialDownlinkBWP-RedCap) is not set, and the MAC entity switches to a BWP for a downlink that is not initialDownlinkBWP. (A-4) The UE is a performance-limited terminal (RedCap UE), and the UE is identified as the default downlink BWP. If a child (defaultDownlinkBWP-Id) is not set, the UE will be the initial downlink for performance-limited devices. The BWP (initialDownlinkBWP-RedCap) is set, and the MAC entity switches to a BWP for a downlink that is not initialDownlinkBWP-RedCap.

[0188] In each activated serving cell where a UE has set up a BWP, the MAC entity shall perform some or all of the following (A) through (H): if the BWP is activated (an Active BWP) and the Active DL BWP in that serving cell is not a dormant BWP. (A) Send UL-SCH with that BWP. (B) If the UE has set up a PRACH occasion, send RACH (PRACH) in that BWP. (C) Monitor the PDCCH with that BWP. (D) If the UE has set PUCCH, send PUCCH with that BWP. (E) Report the CSI using that BWP. (F) If the UE has configured SRS, send SRS using that BWP. (G) Receive DL-SCH with that BWP. (H) If any, initialize all suspended configured uplink grants of grant type 1 that the UE has configured in its Active BWP, according to the stored configuration.

[0189] If a BWP is activated (is an Active BWP) and the Active DL BWP in its serving cell is a dormant BWP, the MAC entity performs some or all of the following (A) through (L): (A) If the BWP inactivity timer for this serving cell is running, it will stop. (B) Do not monitor PDCCH with that BWP. (C) Do not monitor PDCCH for that BWP. (D) DL-SCH will not be received in that BWP. (E) No CSI is reported in that BWP, and CSIs excluding aperiodic CSIs are excluded from that BWP. I will report this. (F) Do not send SRS with that BWP. (G) Do not send UL-SCH with that BWP. (H) Do not send RACH with that BWP. (I) Do not send a PUCCH with that BWP. (J) Clear all configured downlink assignments and / or all configured uplink grants of grant type 2 associated with that SCell. (K) All Grant Type 1 configured above that SCell Suspend Relink Grant. (L) If a beam failure is detected, perform beam failure detection and beam failure recovery for that SCell.

[0190] If the BWP is deactivated, the MAC entity will perform some or all of the following actions (A) through (I). (A) Do not send UL-SCH with that BWP. (B) Do not send RACH with that BWP. (C) Do not monitor PDCCH with that BWP. (D) Do not send a PUCCH with that BWP. (E) Do not report CSI in that BWP. (F) Do not send SRS with that BWP. (G) Do not receive DL-SCH with that BWP. (H)UE clears all configured downlink assignments and / or all configured uplink grants of grant type 2 that it has set up in its BWP. (I) All grant type 1 configurations of the Inactive BWP The geared uphill link grant is suspended.

[0191] Next, we will explain the Central Unit (CU) and the Distributed Unit (DU). The Central Unit may be a logical node that hosts the RRC layer, SDAP layer, and PDCP layer of the base station equipment. The Distributed Unit is the RRC layer of the base station equipment. This may refer to a logical node that hosts the MAC layer and the PHY layer. The aggregation unit may control the operation of one or more distributed units. A unit may support one or more cells. A single cell may be supported by only one distributed unit. Furthermore, some of the functions of an aggregated unit may be implemented in a distributed unit. Also, some of the functions of a distributed unit may be implemented in an aggregated unit.

[0192] Next, Layer 1 / Layer 2 triggered mobility (L1 / L2-triggered mobility: LTM) in this embodiment will be described.

[0193] LTM refers to the one or more L1 measurement reports (described later) that a base station device receives from a terminal device. Based on this, the procedure may involve the base station device switching the serving cell of the terminal device by a cell switching command signaled via MAC CE. The cell switching command is prepared in advance by the base station device and transmitted to the terminal device via RRC signaling. Specify the LTM candidate settings that were provided. The terminal device then follows the cell switching command. You may then apply the target settings.

[0194] For example, the RRC layer of the terminal device includes an RRC signaling that includes one or more LTM candidate settings. The terminal device may receive a signal from the base station device. The RRC layer of the terminal device receives the signal. It may store multiple LTM candidate information elements. Also, the MAC layer of the terminal device may receive cell switching commands from the base station device via MAC CE. The RRC layer of the terminal device The target settings may be applied according to the aforementioned cell switching command. The replacement command may include a target setting identifier indicating the target setting. The MAC layer of the terminal device that receives the cell switching command may notify the RRC layer of the terminal device (a layer higher than the MAC layer) that the LTM cell switching procedure has been triggered and the target setting identifier. When the RRC layer receives a notification from the MAC layer (a layer lower than the RRC layer), it triggers a cell switching procedure. The target identifier may be used to identify one or more LTM candidate information elements One of the LTM candidate settings may be applied. The target setting identifier may be an identifier used to identify a certain LTM candidate setting. The target setting may be an LTM candidate setting indicated by the target setting identifier. The cell switching command is the terminal The command (MAC CE) may be a command that triggers the device to perform an LTM cell switching procedure. The NET identifier may be associated with the LTM candidate identifier described later.

[0195] In LTM, the base station equipment receives the measurement report provided by the terminal equipment. The target setting may be determined based on this. The measurement report is transmitted from the terminal device via PUSCH. The transmitted CSI report may be a CSI report transmitted via PUCCH from the terminal device. In addition to or instead of the CSI report, the measurement report may be a CSI report transmitted via PUCCH from the terminal device. It may be a measurement report message. In addition to or instead of the measurement report, the measurement report information transmitted as MAC CE from the terminal device may be measurement report information. The measurement report may also be other information.

[0196] Furthermore, MAC CE can be rephrased as Layer 2 signaling. Also, the above measurements are, Layer 1 (PHY layer), Layer 2 (MAC layer), and / or Layer 3 (RRC layer) This may be done. Furthermore, the above measurement report may be performed by Layer 1 (PHY layer), Layer 2 (MAC layer), and / or Layer 3 (RRC layer).

[0197] The aforementioned cell switching command may be signaled by MAC CE. The MAC CE is LTM It may also be called the cell switching command MAC CE, and can be used interchangeably with the term cell switching command. In other words, sending and receiving cell switching commands is equivalent to LTM cells. This can be rephrased as sending or receiving a MAC CE switching command. The cell switching command may include multiple fields, and these multiple fields may include the following information, as well as other information. (a) Target setting identifier corresponding to LTM candidate identifier (b) TA command (c) Identifier indicating the TCI state in the SpCell (target cell) of the target setting. (d) Identifying the uplink TCI state in the target cell (SpCell) for target setting. Besshi (e) Information indicating the existence of CFRA resources (f) Information indicating the uplink carrier that transmits the CFRA PRACH. (g) Preamble index of CFRA resources (h) Show the SSB used to determine the RACH occasion for CFRA PRACH transmission. information (i) Information indicating a RACH occasion related to the SSB indicated by the information indicating the SSB

[0198] One or more LTM candidate information elements may be included in the LTM setting, and the LTM setting may be included in the RRC reset message. The RRC reset message may be RRC signaling. The LTM candidate information elements include an LTM candidate identifier, an LTM candidate cell identifier, an LTM-SSB setting, and LTM Candidate setting, LTM full setting indicator, early UL synchronization setting, early SUL synchronization setting, LTM reset judgment indicator The LTM candidate identifier may include B, LTM-UE criterion TA measurement identifier B, and other information. The child was an identifier used to identify the LTM candidate setting and the LTM candidate information element. The information element may be named ltm-CandidateId. The LTM candidate cell identifier is an identifier that indicates the physical cell identifier (PCI) of the SpCell of the setting included in the LTM candidate setting, and may be an information element named ltm-CandidatePCI. The LTM-SSB setting indicates the setting of the SS / PBCH block used for L1 measurement and TCI status, and is an information element named ltm-SSB-Config. It may be an element. The aforementioned LTM candidate setting is an RRC setting used to set LTM candidate cells. The setting includes a fixed value and may be an information element named ltm-CandidateConfig. The LTM complete setting indicator indicates whether the RRC reconfiguration included in the LTM candidate setting is a complete setting and may be an information element named ltm-ConfigComplete. The early UL synchronization setting is a setting used to execute the early UL synchronization procedure on the UL carrier and may be an information element named ltm-EarlyUL-SyncConfig. The early SUL synchronization setting is a setting used to execute the early UL synchronization procedure on the SUL carrier and may be an information element named ltm-EarlyUL-SyncConfigSUL It may be an information element. The LTM reset judgment identifier B is an identifier used to determine whether or not an L2 reset is performed when the LTM cell switching procedure is triggered for an LTM candidate cell, and may be an information element named ltm-NoResetID. The LTM-UE reference TA measurement Identifier B is an identifier used to determine whether or not to perform UE-based TA measurement on an LTM candidate cell, and may be an information element named ltm-UE-MeasuredTA-ID.

[0199] The LTM configuration may include LTM reference settings, an LTM candidate setting release list, an LTM candidate setting addition / modification list, an LTM reset decision identifier A, an LTM-UE criterion TA measurement identifier A, an LTM-CSI resource setting release list, an LTM-CSI resource setting addition / modification list, and other information. The LTM reference settings are settings used to configure reference settings for LTM, and may be an information element named ltm-ReferenceConfiguration. The LTM candidate setting release list is a list indicating LTM candidate settings to be released, and may be an information element named ltm-CandidateToReleaseList. It may exist. The LTM candidate setting release list contains the LTM candidate identification corresponding to the LTM candidate setting to be released. It may also be a list of children. The LTM candidate settings add / modify list is added and / or modified. The LTM CandidateToAddModList is a list of LTM candidate settings, which may be an information element named ltm-CandidateToAddModList. The LTM Reset Decision Identifier A is an identifier used to determine whether an L2 reset is performed when an LTM cell switching procedure is triggered for an LTM candidate cell, which may be an information element named ltm-ServingCellNoResetID. The LTM-UE Criteria TA Measurement Identifier A is an identifier used to determine whether or not to perform a UE criteria TA measurement for an LTM candidate cell, which may be an information element named ltm-ServingCellUE-MeasuredTA-ID. The LTM-CSI Resource Setting Release List is a list indicating the LTM CSI resource settings to be released, which may be an information element named ltm-CSI-ResourceConfigToReleaseList. The LTM-CSI Resource Setting Release List may be a list of LTM-CSI resource setting identifiers corresponding to the LTM-CSI resource settings to be released. The LTM-CSI Resource Setting Addition and Modification List is a list of additions and also This is a list of LTM-CSI resource settings to be modified, and may be an information element named ltm-CSI-ResourceConfigToAddModList. An LTM-CSI resource setting may be a setting that defines a group of one or more CSI resources for one or more LTM candidate settings. Each LTM-CSI resource setting may be identified by an LTM-CSI resource setting identifier.

[0200] When a terminal device receives an RRC reconfiguration message that includes the LTM setting, it uses the received LTM setting as a basis. The following actions may be performed: (A) If the received LTM setting includes LTM reset decision identifier A, and the current UE variable-LTM reset decision identifier includes LTM reset decision identifier A, the value of LTM reset decision identifier A included in the UE variable-LTM reset decision identifier may be replaced with the received LTM reset decision identifier A; and if the received LTM setting includes LTM reset decision identifier A, and the current UE variable-LTM reset decision identifier does not include LTM reset decision identifier A, the received LTM reset decision identifier A may be replaced with the UE variable-LTM reset (B) If the received LTM setting includes LTM-UE criterion TA measurement identifier A, and the current UE variable -LTM -UE criterion TA measurement identifier is LTM-UE criterion TA measurement identifier A If it includes, the LTM-UE reference TA measurement identifier A included in the UE variable-LTM-UE reference TA measurement identifier The received value may be replaced with the LTM-UE reference TA measurement identifier A, and the received LTM setting If the LTM-UE reference TA measurement identifier A is included, and the current UE variable-LTM-UE reference TA measurement identifier A is not included, the received LTM-UE reference TA measurement identifier A may be stored in the UE variable-LTM-UE reference TA measurement identifier. (C) If the received LTM setting includes an LTM candidate setting release list, the operation of the terminal device that received the LTM candidate setting release list described below shall be (D) If the received LTM setting includes an LTM candidate setting addition / modification list, the following steps are permitted. The terminal device that received the aforementioned LTM candidate setting addition / modification list may perform the operation. The variable -LTM reset determination identifier determines whether an L2 reset is required during the LTM cell switching procedure. The UE variable-LTM-UE-criteria-TA measurement identifier may be used to store the identifier of a serving cell that serves as a criterion for the terminal device to determine whether or not UE-criteria-TA measurement is necessary, and may be a UE variable named VarLTM-ServingCellUE-MeasuredTA-ID. Note that a UE variable may be a variable stored internally within the terminal device.

[0201] When a terminal device receives the LTM candidate setting addition / modification list, it performs the following processing for each LTM candidate identifier included in the LTM candidate setting addition / modification list: (A) When it determines that the current terminal device setting includes an LTM candidate information element that contains an LTM candidate identifier with the same value as the LTM candidate identifier: In other words, the LTM candidate information element (included in the terminal device settings) may be reconfigured according to the received LTM candidate information element, and if not (i.e., if it is not determined that the current terminal device settings include an LTM candidate information element containing an LTM candidate identifier with the same value as the LTM candidate identifier), the received LTM candidate information element may be added to the terminal device settings. (B) The above The LTM candidate information element, which includes the received LTM candidate identifier, includes the LTM-UE reference TA measurement identifier B. If so, further, (C) if it is determined that the value of the LTM-UE standard TA measurement identifier B is equal to the value of the LTM-UE standard TA measurement identifier A included in the UE variable-LTM-UE standard TA measurement identifier, it is notified to the lower layer that a UE standard TA measurement has been set for this LTM candidate information element, and if not, ( That is, the value of the LTM-UE reference TA measurement identifier B and the UE variable included in the LTM-UE reference TA measurement identifier If the value of the LTM-UE standard TA measurement identifier A is not determined to be equal, this LTM candidate information element Therefore, it is possible to inform the lower layer that UE-based TA measurement is not set. Note that the LTM candidate information element including the received LTM candidate identifier does not include the LTM-UE-based TA measurement identifier B. If not, the lower layer will indicate that the UE criterion TA measurement is not set for this LTM candidate information element. It's okay to inform them.

[0202] Upon receiving the LTM candidate setting release list, the terminal device performs the following processing on each LTM candidate identifier included in the LTM candidate setting release list: (A) It may delete the LTM candidate information element corresponding to the LTM candidate identifier.

[0203] Furthermore, if NR-DC is configured on the terminal device, the terminal device can receive two independent LTM settings. That is, (1) the MCG is included in the RRC reset message received via SRB1. (2) The associated LTM settings and the RRC received via SRB3 or SRB1. The terminal device can receive two LTM settings associated with the SCG, which are included in the RRC reconfiguration message embedded in the configuration message. If the terminal device receives two independent LTM settings, the terminal device may maintain the two independent LTM settings, and the terminal device may receive two Independent UE variable-LTM-UE reference TA measurement identifiers may be maintained, and the terminal device may maintain two independent The UE variable-LTM reset decision identifier may be maintained, and the terminal device may perform all procedures independently for each LTM setting, UE variable-LTM-UE reference TA measurement identifier, and UE variable-LTM reset decision identifier unless otherwise explicitly instructed.

[0204] In LTM, some or all of the following mobility scenarios (A) through (J) are supported. It is acceptable to include other mobility scenarios, and other mobility scenarios may also be supported. (A) Mobility within base station distributed units (intra-gNB-DU) (B) Mobility between base station distribution units within a base station aggregation unit (intra-gNB-CU inter-gNB-DU) (C) Inter-frequency mobility (including mobility to inter-frequency cells that are not currently serving cells) (D) Intra-frequency mobility (E) PCell modification in terminal devices where CA and DC are not configured. (F) Changing PCell and one or more SCells in terminal devices where CA is configured. (G) Changes to PCell and MCG SCell(s) in terminal devices where DC is configured, changes to PSCell and SCG SCell(s) without MN involvement (H) Inter-cell beam management (not considered as a prerequisite for using Layer 1 / Layer 2 trigger mobility) (I) Mobility between base station aggregation units (inter-gNB-CU) (J) Conditional mobility

[0205] Next, the RSRP in this embodiment will be described. The RSRP may be SS-RSRP (SS reference signal received power), CSI-RSRP (CSI reference signal received power), or other types of RSRP. SS-RSRP is defined as the linear average of the power contributions of resource elements carrying one or more SSSs (secondary synchronization signals). It may also be used. CSI-RSRP is a resource element of an antenna port that carries one or more CSI-RSs. It may also be defined as the linear average of the power contributions of the elements.

[0206] Next, we will explain TCI. The terminal device has a list of up to M TCI state settings configured. It is also possible that the TCI state settings exist in PDSCH-Config. PDSCH-Config may also be the settings for decoding PDSCH. M may be set in maxNumberConfiguredTCIstates-PerCC, which is an RRC parameter. Each TCI state may include a TCI state ID (TCI state identifier). Each TCI state may include parameters for setting QCL (Quasi-co-Location). It may include the following. The QCL may indicate the relationship between one or two downlink reference signals and the DMRS port of the PDSCH, or the relationship between one or two downlink reference signals and the DMRS port of the PDCCH It may also be shown, or the reference signal of one or two downlinks and the CSI-RS of one CSI-RS resource. The port relationships may also be shown. The QCL relationship may be set by the RRC parameter qcl-Type1 for the reference signal of the first downlink, and for the reference signal of the second downlink. This may be set by the RRC parameter qcl-Type2. QCL can also be rephrased as QCL relationship. When showing the relationship between two downlink reference signals and the DMRS port of a PDSCH, the DMRS port of a PDCCH, or the CSI-RS port of one CSI-RS, the QCL type must be the same regardless of whether the two reference signals are the same downlink reference signals or different reference signals. The QCL type corresponding to each downlink reference signal is the RRC parameter QCL-Info It may also be given by qcl-type within {}. For example, the value of qcl-type may be one of typeA, typeB, typeC, or typeD, or it may be any other value. Each type may mean the following relationships, or it may mean that the physical quantities / parameters within {} can be considered to be the same. ·typeA{Doppler shift, Doppler spread, average delay, delay spread} ·typeB{Doppler shift, Doppler spread} ·typeC{Doppler shift, average delay} ·typeD{Spatial Rx parameters}

[0207] The terminal device may have a list of up to 128 TCI states configured. The TCI state settings may reside in the dlOrJointTCI-StateList within the PDSCH-Config, which is an RRC parameter. For example, the TCI state settings may provide a reference signal for the QCL for the DMRS of the PDSCH, or a reference signal for the QCL for the DMRS of the PDCCH, or a reference signal for the QCL for the CSI-RS. You may provide illumination signals, and the UL Tx spatial filter is for PUSCH and PUCCH resources and SRS. It may also be something else.

[0208] The TCI state may also refer to the RRC parameter TCI-state.

[0209] If a TCI-state or TCI-UL-state setting does not exist in the BWP where the component carrier resides, the terminal device may apply the TCI-state or TCI-UL-state setting of the reference BWP where the reference component carrier configured by unifiedTCI-stateRef resides. If the terminal device is configured with dl-OrJointTCI-StateList or ul-TCI-StateList In this case, the terminal device does not need to expect to be set by tci-StatesToAddModList, SpatialRelationInfo, or PUCCH-SpatialRelationInfo. When the terminal device is set by tci-StateToAddModList of any component carrier among the component carriers set by simultaneousTCI-UpdateList-r16, simultaneousTCI-UpdatedList2-r16, simultaneousSpatial-UpdatedList1-r16, or simultaneousSpatial-UpdatedList2-r16, it may be assumed that it is not set by dl-OrJointTCI-StateList or ul-TCI-StateList within that component carrier.

[0210] The terminal device may receive TCI activation commands. Receiving an activation command may also be receiving a MAC CE. The activation command may be used to map up to eight TCI states or up to eight pairs of TCI states to components of a DCI field. For example, the DCI field The field may be Transmission Configuration Indication. One TCI state may be for one downlink physical channel. One TCI state may be for one uplink It may also be for a physical channel. The activation command may be used to map a set of up to eight TCI states to code points in the DCI field. For example, each set of TCI states can consist of up to two downlinks and up to two uplinks. It may be configured in a TCI state for this purpose.

[0211] When the RRC parameter tci-PresentInDCI is set, or tci-PresentDCI-1-2 is set for CORESET, a terminal device configured with a dl-OrJoint-StateList or an activated TCI-UL-StateList with an activated TCI-state is indicated. You may receive DCI format 1_1 / 1_2 / 1_3 which provides the TCI state. If applicable If applicable, DCI format 1_1 / 1_2 may have downlink assignments. If applicable, DCI format 1_1 / 1_2 may not have downlink assignments. If DCI format 1_1 / 1_2 does not have downlink assignments, the terminal device may assume certain conditions. These conditions include using CS-RNTI to scramble the CRC for DCI. It may be that all RVs in the DCI field are 1, or DCI The MCS of all fields may be 1, or the NDI of the DCI field may be 0. This could be the case, or it could be that all FDRA values ​​in the DCI field are 0, or any other condition.

[0212] When a terminal device receives a dl-OrJointTCI-StateList, which is an initial higher layer configuration with one or more TCI-states, and before applying the indicated TCI state from the configured TCI state, the terminal device may consider the PDSCH DMRS, PDCCH DMRS, and CSI-RS to which the indicated TCI state will be applied to be the SS / PBCH block and QCL recognized by the terminal device during the initial access.

[0213] The terminal device has an RRC parameter called dl-OrJointTCI-StateList which has one TCI-UL-state. When received, the TCI-state may be used as the indicated TCI state. When a terminal device receives dl-OrJointTCI-StateList, which is an RRC parameter with one TCI-UL-state. The terminal device may obtain a QCL assumption from its configured TCI state.

[0214] When a terminal device receives an RRC parameter called ul-TCI-StateList that has one TCI-UL-state, that TCI-state may be used as the indicated TCI state.

[0215] If the specified TCI state is different from the previously specified TCI state, And either or both of TCI-UL-State may be applied from a slot. A slot may apply at least the beamAppTime symbol after the last symbol of PUSCH or PUCCH. It's fine even if it's the first slot, which comes later.

[0216] The terminal device is configured with dl-OrJointTCI-StateList, and the unifiedTCI-StateType of the terminal device is set to 'separate', and the terminal device is one of {TCI-State,TCI-UL-State}. When a mapped TCI code point is received, the terminal device may update one of the indicated {TCI-State, TCI-UL-State}. For example, the terminal device may maintain the other {TCI-State, TCI-UL-State} that is not updated by the received TCI code point.

[0217] The terminal device has dl-OrJointTCI-StateList configured, and two specified TCI-states When a terminal device has a TCI code point to which a subset of the first and second TCI-States and one or both subsets of the first and second TCI-UL-States are mapped, the terminal device may update the first or second TCI-State and either the first or second TCI-UL-State mapped to that TCI code point. The terminal device may maintain previously indicated TCI states that are not updated by the TCI code point. For example, the TCI states may be the first and second TCI-states.

[0218] The terminal device is configured with SSB-MTC-AdditionalPCI, and there is a different ControlResourceSet. When a PDCCH-Config containing the value coresetPoolIndex is configured, the terminal device may receive an activation command. This activation command may be for the CORESET associated with each coresetPoolIndex. When a set of TCI state IDs is activated for a coresetPoolIndex, one coresetPoolIndex corresponds The activated TCI state may be associated with the serving cell physical cell ID. The computer ID may be PCI.

[0219] The terminal device has a code point in the DCI field 'Transmission Configuration Induction' When two TCI states are indicated within the terminal, the terminal device receives the activation command. You may believe it. The activation command may be used to map one or two combinations of up to eight TCI states. The terminal device will use the activation command to map eight You do not need to expect to receive more than one TCI state.

[0220] If the DCI field 'Transmission Configuration Indication' exists in DCI format 1_2, and the number of code points S in the DCI field 'Transmission Configuration Indication' is less than the number of TCI code points activated by the activation command, then only the first S code points that were activated may be applied to DCI format 1_2.

[0221] The terminal device may have the RRC parameter tci-PresentInDCI set. tci-PresentInDCI may be set to enable for CORESET to schedule the PDSCH. In this case, the terminal device may assume that the TCI field exists in the DCI format 1_1 or 1_3 of the PDCCH sent over CORESET.

[0222] The terminal device has the RRC parameter tci-Pre for CORESET, which schedules PDSCH. sentInDCI-1-2 may be set. In that case, the terminal device will send PDCCH on CORESET. It may be assumed that a TCI field exists within the DCI format 1_2. The size of that TCI field may be indicated by tci-PresentInDCI-1-2.

[0223] The terminal device may be configured with both sfnSchemePDCCH and sfnSchemePDSCH. The offset time between the reception of the downlink DCI and the reception of the corresponding PDSCH may be greater than or equal to the threshold timeDuraionForQCL. The terminal device may support sfn-DefaultDL-BeamSetup-r17 for DCIs scheduled without a TCI field. In that case, the terminal device will have a TCI state or QCL assumption for the PDSCH, regardless of the number of active TCIs in the CORESET, while serving. Suitable for CORESET, which is used for receiving DCI on the downlink within the active BWP. It may be assumed that the TCI state used matches the QCL assumption. The terminal device may have two TCI states activated in its CORESET state.

[0224] The terminal device may be configured with both sfnSchemePDCCH and sfnSchemePDSCH. The offset time between the reception of the downlink DCI and the reception of the corresponding PDSCH may be greater than or equal to the threshold timeDuraionForQCL. The terminal device does not need to support sfn-DefaultDL-BeamSetup-r17 for DCI scheduled without a TCI field. In that case, the terminal device does not need to expect the TCI field to be present when scheduled in DCI format 1_1 or 1_2.

[0225] If neither sfnSchemePDCCH nor sfnSchemePDSCH is configured on the terminal device, and the DCI format If scheduled in set 1_1 or 1_2, and the offset time between the reception of the downlink DCI and the reception of the corresponding PDSCH is greater than or equal to the threshold timeDuraionForQCL, the terminal device may expect the TCI field to be present.

[0226] The terminal device may set sfnSchemePDCCH to 'sfnschemeA'. In that case, the terminal device does not need to set sfnSchemePDSCH. In that case, activation for PDSCH A TCI code point with two TCI states within a command does not necessarily have to exist. If the offset time between the reception of the downlink DCI and the reception of the corresponding PDSCH is greater than or equal to the threshold timeDuraionForQCL, and the CORESET scheduling the PDSCH is indicated with two TCI states, the terminal device may assume that the TCI state or QCL assumption for the PDSCH is the same as the first TCI state or QCL assumption applied for the CORESET used for PDCCH transmission.

[0227] If PDSCH is scheduled by DCI format 1_0 / 1_1 / 1_2, and SFN method A is set on the terminal device for PDCCH, and SFN is not set on the terminal device for PDSCH, and there are no TCI code points (code points in the TCI field) with two TCI states, and the time offset is greater than or equal to a threshold, and the CORESET that schedules PDSCH is indicated by two TCI states, then the TCI state or QCL assumption for PDSCH may be the same as the first TCI state and first QCL assumption applied for CORESET. Setting SFN method A for PDCCH means that sfnSchemePdcch is set to 'sfnSchemeA'. It is also acceptable to do so.

[0228] If the unifiedTCI state is not set on the terminal device, the time offset is less than the threshold, and at least one set TCI state includes a qcl-Type with typeD set, then the DMRS port of the PDSCH may be RS and QCL with respect to a certain QCL parameter. The meter may be used for the PDCCH QCL indication of a certain CORESET. A certain CORESET is the latest In a slot, one or more CORESETs monitored by the terminal device may be the CORESET associated with the search area with the lowest CORESET ID (controlResourceSetId). .

[0229] The terminal device is set to a unifiedTCI state, the time offset is less than the threshold, and at least one of the set TCI states includes a qcl-Type to which typeD is set, If the indicated TCI state is related to the PCI (Physical Cell ID) of the serving cell, the indicated TCI state may be applied to PDSCH reception. A unifiedTCI state is set, the time offset is less than the threshold, and at least one set TCI state is set to typeD. If the specified qcl-Type is included and the indicated TCI state is related to a PCI (Physical Cell ID) other than the serving cell, the DMRS port of the PDSCH in the serving cell may be a reference signal and QCL related to the CORESET QCL parameter associated with the lowest CORESET ID. Setting the unifiedTCI state may also mean setting the parameter dl-OrJointTCI-StateList, which is an RRC parameter.

[0230] If a primary capability is indicated to the terminal device, the terminal device may determine a spatial domain filter. The spatial domain filter may be used while performing applicable channel access procedures before UL transmission on the channel. If an SRI corresponding to UL transmission is indicated In this case, the terminal device will use the same spatial domain filter as the indicated SRI and associated spatial domain filter. You may use a terminal. The terminal device receives a DL reference signal related to the indicated TCI state. The same spatial domain filter used for receiving the DL reference signal may be used for receiving the signal. For example, when a TCI-State or TCI-UL-State is set, the terminal device may use the same spatial domain filter used for receiving the DL reference signal associated with the indicated TCI state. The first terminal capability may be beamCorrespondenceWithoutUL-BeamSweeping, which is set to '1'.

[0231] When SFN method A is set on the terminal device for PDCCH and CORESET is activated in two TCI states, the DMRS port of PDCCH in CORESET may be DL RS (downlink reference signal) and QCL in the two TCI states. When SFN method B is set on the terminal device for PDCCH and CORESET is activated in two TCI states, the DMRS port of PDCCH in CORESET may be DL RS and QCL in the two TCI states, and the second TCI state is the QCL parameter {Doppler}. It is not necessary to include {shift, Doppler spread}. SFN method A is set for PDCCH. Setting up SFN method B for PDCCH may also mean setting up sfnSchemePdcch with 'sfnSchemeA'.

[0232] Regardless of the settings for tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, if dl-OrJointTCI-StateList-r17 is not provided to the terminal device, and the offset between receiving the downlink DCI corresponding to the PDSCH is less than timeDurationForQCL, then at least 1 One of the configured TCI states may include a qcl-Type set to `typeD`. In that case, the terminal device may assume that the DMRS port of the PDSCH is RS and QCL used for the PDCCH. Good. The PDCCH is the lowest controlResourceSetId in the latest slot among one or more CORESETs in the active BWP of the serving cell monitored by the terminal device. Based on the CORESET associated with the monitored search space and the QCL instructions of the CORESET associated with it. You may do so.

[0233] The terminal device may also be configured with enableDefaultTCI-StatePerCoresetPoolIndex. The configuration may be set by the RRC parameter PDCCH-Config. PDCCH-Config may contain two different coresetPoolIndex values ​​in different ControlResourceSets. In that case, the terminal device may assume that the DMRS ports of the PDSCH associated with the coresetPoolIndex value of the serving cell are the RS and QCL used for the PDCCH. That PDCCH may be the PDCCH that schedules the PDSCH in the active BWP of the serving cell monitored by the terminal device. Often, the lowest controlResourceSetId among CORESETs and the monitored search space are used. You may also base your settings on the associated CORESET QCL instructions.

[0234] The terminal device may have enableTwoDefaultTCI-States set. In that case, at least one TCI code point may indicate two TCI states. The terminal device has a PDSCH DMRS port. The PDSCH transmission opportunity of the terminal or serving cell includes a TCI code point containing two different TCI states. It may be assumed that the RS and QCL states are associated with the TCI state corresponding to the lowest code point between the points.

[0235] The terminal device may be set to the RRC parameter repetitionScheme. repetitionScheme may be set to tdmSchemeA. In that case, or when set to the RRC parameter repetitionNumber, and the offset between the first PDSCH transmitter and the reception of the downlink DCI is less than the threshold timeDurationForQCL, the mapping of the TCI state to the PDSCH transmitter opportunity may be determined by a certain method.

[0236] If the TCI status set for the serving cell of a scheduled PDSCH is not all set to type-D, the terminal device will be instructed to do so for that scheduled PDSCH. You may also obtain other QCL assumptions from the TCI state.

[0237] Regardless of the settings for tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, the terminal device may be given dl-OrJointTCI-StateList-r17. In that case, when the offset between the DCI of the downlink and the corresponding PDSCH is smaller than timeDurationForQCL, regardless of the setting of followUnifiedTCI-State, at least one configured TCI state is set to typeD. It may include a qcl-Type. In this case, if the indicated TCI state is that serving cell When associated with PCI, the indicated TCI state may be applied to PDSCH reception.

[0238] Regardless of the settings for tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, the terminal device may be given dl-OrJointTCI-StateList-r17. In that case, when the offset between the DCI of the downlink and the corresponding PDSCH is smaller than timeDurationForQCL, regardless of the setting of followUnifiedTCI-State, at least one configured TCI state is set to typeD. It may include a qcl-Type. In this case, if the indicated TCI state is different serving When linked to PCI, the terminal device has a DMRS port on the PDSCH of the serving cell. It may be assumed that the RS and QCL states used are the most important among one or more CORESETs in the active BWP of the serving cell monitored by the terminal device. It may also be based on the lowest controlResourceSetId within the new slot and the CORESET instruction associated with the monitored search space. In the case of CA, each component within a band If the 'QCL-TypeD' of the component carrier's PDSCH DMRS is different, the assumption of the component carrier's PDSCH DMRS 'QCL-TypeD' for the lowest component carrier ID in that band may apply to all PDSCH DMRS of that component carrier in that band. stomach.

[0239] The terminal device may hold the instructed terminal capability beamCorrespondenceWithoutUL-BeamSweeping. beamCorrespondenceWithoutUL-BeamSweeping is set to 'supported'. This is also possible. In that case, the terminal device may determine the spatial filter to be used during the channel access procedure before a certain uplink transmission. The terminal device may be instructed on the SRI. If the terminal device is instructed by an SRI corresponding to uplink transmission, it may use the same spatial filter as the spatial filter associated with the instructed SRI. The terminal device may be configured with SRS-spatialRelationInfo for uplink transmission. In that case, the terminal device may use the same spatial filter as the spatial filter associated with referenceSignal in the corresponding SRS-spatialRelationInfo. You may use a terminal. The terminal device may have either a TCI-state in dl-OrJointTCI-StateList or a TCI-UL-State in ul-TCI-StateList set. In that case, the terminal device will have a certain spatial function Filters may be used. A certain spatial filter is associated with the specified TCI state (see downlink). It may be the same as the receiving spatial filter used to receive the signal.

[0240] The reception of a PDCCH may include two PDCCHs from two separate search spaces. In this case, a PDCCH candidate that terminates later in time may be used for the purpose of determining the time offset between the reception of the corresponding PDSCH and the downlink DCI. The reception of a PDCCH may include two PDCCH candidates from two separate search spaces. In this case, for the setting of tci-PresentInDCI or tci-PresentDCI-1-2, the terminal device may expect the same setting in the first and second CORESETs associated with the two PDCCH candidates. The PDSCH may be scheduled by a DCI format that does not have a TCI field. In this case, and the schedule If the Eühring offset is greater than or equal to timeDurationForQCL, the QCL assumption for PDSCH is two PDCCHs. It is determined based on the CORESET with the lowest ID among the first and second CORESETs associated with the candidate. That's good too.

[0241] CSI-RS resources within NZP-CSI-RS-resourceSet may be set periodically. Within NZP-CSI-RS-resourceSet, which is set by the RRC parameter trs-Info, periodically For CSI-RS resources, the terminal device may expect a TCI-state to indicate a QCLtype. A QCLtype may be SSB and type C. A QCLtype may be the same SSB and type D. The SSB may have a different PCI than the PCI of its serving cell. The placement is an SSB with different PCIs for that serving cell, and the SSB of that serving cell, and the central circumference It can be assumed that the wavenumber, subcarrier spacing, and SFN offset are the same. A certain QCLtype is a CSI-RS in the NZP-CSI-RS-resourceSet, which is set by the RRC parameter repetition. Resources and typeD may also be used. The SSB may have a PCI different from that of its serving cell. The terminal device has an SSB that has a PCI different from that of its serving cell and the SSB of that serving cell. We can assume that the center frequency, subcarrier spacing, and SFN offset are the same.

[0242] CSI-RS may be set to periodic or semi-persistent. Or, for semi-periodic CSI-RS, if the terminal device is configured with dl-OrJointTCI-StateList It may be assumed that the TCI-state instructed by the terminal device is not applied.

[0243] The CSI-RS resources in NZP-CSI-RS-resourceSet are configured aperiodicly. This is also acceptable. The NZP-CSI-RS-resourceSet may be set by the RRC parameter trs-Info. For non-periodic CSI-RS resources in the NZP-CSI-RS-resourceSet set by the RRC parameter trs-Info, the terminal device may expect the TCI-state to indicate that the periodic CSI-RS resources in the NZP-CSI-RS-resourceSet are qcl-Type 'typeA'. For non-periodic CSI-RS resources in the NZP-CSI-RS-resourceSet, which is set in trs-Info, the terminal device's TCI-state is set to the periodic CSI-RS resources in the NZP-CSI-RS-resourceSet. You can expect this to indicate that it is a qcl-Type 'typeD'.

[0244] For CSI-RS resources within the NZP-CSI-RS-resourceSet that are not set by the RRC parameter trs-Info and are not set by the RRC parameter repetition, the terminal device may expect the TCI-state to indicate a certain QCLtype. That certain QCLtype is the CSI-RS resource within the NZP-CSI-RS-resourceSet that is set by the RRC parameter trs-Info and is type A. This is also acceptable. For example, it could be the same CSI-RS resource and typeD.

[0245] For CSI-RS resources within the NZP-CSI-RS-resourceSet that are not set by the RRC parameter trs-Info and are not set by the RRC parameter repetition, the terminal device may expect the TCI-state to indicate a certain QCLtype. That certain QCLtype is the CSI-RS resource within the NZP-CSI-RS-resourceSet that is set by the RRC parameter trs-Info and is type A. It may also be SSB and typeD. That SSB is its serving The terminal device may have a different PCI than the serving cell. The terminal device may assume that the SSB with a different PCI than the serving cell and the SSB of the serving cell have the same center frequency, SFN offset, and subcarrier spacing.

[0246] For CSI-RS resources within the NZP-CSI-RS-resourceSet that are not set by the RRC parameter trs-Info and are not set by the RRC parameter repetition, the terminal device may expect the TCI-state to indicate a certain QCLtype. That certain QCLtype is the CSI-RS resource within the NZP-CSI-RS-resourceSet that is set by the RRC parameter trs-Info and is type A. This is also possible. For example, it could be a CSI-RS resource and typeD within the NZP-CSI-RS-resourceSet, which is set by the RRC parameter repetition.

[0247] For CSI-RS resources in an NZP-CSI-RS-resourceSet that are not set by the RRC parameter trs-Info and are not set by the RRC parameter repetition, the terminal device may expect the TCI-state to indicate a certain QCLtype. This certain QCLtype is the one set by the RRC parameter trs-Info in the NZP-CSI-RS-resourceSet when typeD is not applicable. The internal CSI-RS resource may be of type B.

[0248] The CSI-RS resource set in NZP-CSI-RS-resourceSet is configured by the RRC parameter repetition. For the source, the terminal device may expect the TCI-state to indicate a QCLtype. A QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet, set by the RRC parameter trs-Info, and type A. For example, it may also be a similar CSI-RS resource and type D.

[0249] The CSI-RS resource set in NZP-CSI-RS-resourceSet is configured by the RRC parameter repetition. For the source, the terminal device may expect the TCI-state to indicate a QCLtype. A QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet, set by the RRC parameter trs-Info, and type A. For example, it may also be a CSI-RS resource in the NZP-CSI-RS-resourceSet, set by the RRC parameter repetition, and type D.

[0250] The CSI-RS resource set in NZP-CSI-RS-resourceSet is configured by the RRC parameter repetition. For the source, the terminal device can be expected to indicate a QCLtype in which the TCI-state is. Some QCLtype may be SSB and type C. For example, it may be SSB and type D. This may also be the case, and the reference signal may be an SSB with a PCI different from that of the serving cell. The terminal device may assume that the SSB with a different PCI from that of the serving cell has the same center frequency, subcarrier spacing, and SFN offset as the SSB of the serving cell.

[0251] For PDCCH's DMRS, if dl-OrJointTCI-StateList is not set on the terminal device, the terminal device may be expected to indicate a QCLtype in which the TCI-state is located. A QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet, set by the RRC parameter trs-Info, that is type A. For example, it may also be a similar CSI-RS resource that is type D.

[0252] For PDCCH's DMRS, if dl-OrJointTCI-StateList is not set on the terminal device, the terminal device may be expected to indicate a QCLtype in which the TCI-state is located. A certain QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet, set by the RRC parameter trs-Info, that is type A. For example, it may also be a CSI-RS resource in the NZP-CSI-RS-resourceSet, set by the RRC parameter repetition, that is type D.

[0253] For PDCCH's DMRS, if dl-OrJointTCI-StateList is not set on the terminal device, the terminal The device may be expected to indicate a QCLtype in which the TCI-state is set. A certain QCLtype is not set by the RRC parameter trs-Info and is not set by the RRC parameter repetition. Alternatively, the CSI-RS resource within NZP-CSI-RS-resourceSet can be of type A. For example, it could be a similar CSI-RS resource and type D.

[0254] If the terminal device is configured with sfnSchemepdcch set with 'sfnshemeA' and CORESET is activated in two TCI states, the terminal device may assume that the DMRS port of its CORESET PDCCH is the downlink reference signal and QCL in two TCI states. If the terminal device is configured with sfnSchemePdcch set with 'sfnchemeB' and CORESET is activated in two TCI states When activated, the terminal device may indicate that the DMRS port of the PDCCH is QCL and the downlink reference signal for two TCI states, excluding {Doppler shift, Doppler spread} for the second indicated TCI state.

[0255] The terminal device may have the RRC parameter cjtScheme set. A parameter called dl-OrJointTCI-StateList may be set. The terminal device may possess terminal capability A. Terminal capability A may support two joint TCI states for PDSCH-CJT, or it may be [support for two joint TCI states for PDSCH].

[0256] If both the RRC parameters cjtScheme and dl-OrJoingTCIList are set on the terminal device, When two TCI states are indicated for PDSCH reception and terminal capability A is reported, if the terminal is configured with cjtSchemeA, the DMRS port of the PDSCH may be assumed to be QCL with respect to QCL-TypeA, with respect to the downlink reference signal of both indicated TCI states.

[0257] If both the RRC parameters cjtScheme and dl-OrJointTCIList are set on the terminal device, When two TCI states are indicated for PDSCH reception and terminal capability A is reported, if the terminal is configured with cjtSchemeB, the downlink reference signals of both indicated TCI states on the DMRS port of the PDSCH and QCL-type A may be assumed to be QCL, except for the second indicated joint TCI state {Doppler Shift, Doppler Spread}.

[0258] For PDSCH's DMRS, if dl-OrJointTCI-StateList is not set on the terminal device, the terminal device may be expected to indicate a QCLtype in which the TCI-State is located. A QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet set by the RRC parameter trs-Info and be type A. For example, it may be a CSI-RS resource in the NZP-CSI-RS-resourceSet set by the RRC parameter repetition and be type D.

[0259] For PDSCH's DMRS, if dl-OrJointTCI-StateList is not set on the terminal device, the terminal device can be expected to indicate a QCLtype in which TCI-State exists. A certain QCLtype is not set in the RRC parameter trs-Info, and is not set in the RRC parameter repetition. It may also be a CSI-RS resource within NZP-CSI-RS-resourceSet that is not configured, and type A. For example, it could be a similar CSI-RS resource and type D.

[0260] For DMRS in PDCCH, if dl-OrJointTCI-StateList is set on the terminal device, the terminal device may expect the indicated TCI-State to indicate a certain QCLtype. This QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet, set by the RRC parameter trs-Info, and could be type A. For example, it could be a similar CSI-RS resource and type D.

[0261] For PDCCH's DMRS, if dl-OrJointTCI-StateList is configured on the terminal device, the terminal device may expect the indicated TCI-State to indicate a certain QCLtype. ype may be a CSI-RS resource within NZP-CSI-RS-resourceSet, set by the RRC parameter trs-Info, and typeA. For example, it may be a CSI-RS resource within NZP-CSI-RS-resourceSet, set by the RRC parameter repetition, and typeD.

[0262] For PDSCH's DMRS, if dl-OrJointTCI-StateList is set on the terminal device, the terminal device may expect the indicated TCI-State to indicate a certain QCLtype. This QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet, set by the RRC parameter trs-Info, and could be type A. For example, it could be a similar CSI-RS resource and type D.

[0263] For PDSCH's DMRS, if a terminal device is configured with dl-OrJointTCI-StateList, the terminal device may expect the indicated TCI-State to indicate a certain QCLtype. This QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet, configured with the RRC parameter trs-Info, and type A. For example, it may be a CSI-RS resource in the NZP-CSI-RS-resourceSet, configured with the RRC parameter repetition, and type D.

[0264] The terminal device may be configured with sfnSchemePDSCH. sfnSchemePDSCH may be set to 'sfnSchemeA'. The terminal device has two TCI states in the DCI field code points. It may be indicated by . The DCI field may be 'Transmission Configuration Indication'. When the terminal device is set with sfnSchemePDSCH set with 'sfnSchemeA' and is indicated with two TCI states by the code point of the DCI field 'Transmission Configuration Indication', the terminal device will have the DMRS port of the PDSCH in the downlink of the two TCI states It can be assumed that the reference signal and QCL are the same.

[0265] The terminal device may be configured with sfnSchemePDSCH. sfnSchemePDSCH may be set to 'sfnSchemeA'. The terminal device has two TCI states in the DCI field code points. It may be indicated as follows. The DCI field may be 'Transmission Configuration Indication'. When a terminal device is set with sfnSchemePDSCH set with 'sfnSchemeB' and is indicated with two TCI states by the code point of the DCI field 'Transmission Configuration Indication', the terminal device may assume that the DMRS port of the PDSCH is the downlink reference signal and QCL with two TCI states, except for the second indicated TCI state {Doppler shift, Doppler spread}.

[0266] The terminal device may be configured with TCI-UL-State. The terminal device may also be configured with the RRC parameter PDCCH-Config. PDCCH-Config may contain two different coresetPoolIndex values ​​in ControlResourceSet. The specified TCI state is fixed to the coresetPoolIndex value. It may be present. The terminal device has TCI-Ul-State or dl-OrJointTCI-StateList set. Furthermore, the terminal device has two different coresetPoolIndex values ​​in ControlResourceSet. When configured by the RRC parameter PDCCH-Config, and when the terminal device is indicated by the DCI format 'Transmission Configuration Indication' in DCI format 1_1 / 1_2, which is related to the value of coresetPoolIndex, the indicated TCI state may be specific to the value of coresetPoolIndex.

[0267] A terminal device may hold two specified TCI-states. A terminal device is configured with dl-OrJointTCI-StateList to hold two TCI-states, and the terminal device is a terminal in a certain frequency range. Failure to report capability, and reception of activated or scheduled PDSCH, When the offset time between receiving DCI formats 1_0 / 1_1 / 1_2 scheduled or activated is less than timeDurationForQCL in a certain frequency range, the terminal equipment may apply the first indicated TCI-state to activate or receive the scheduled PDSCH. A certain terminal capability may be frequency range 2 or FR2. [Two default beams S-DCI based MTRP] or single DCI based MTRP It may also be possible to set up two default beams for transmission.

[0268] When a terminal device is configured with dl-OrJointTCI-StateList and configured by PDCCH-Config, which is an RRC parameter containing two different coresetPoolIndexes in ControlResourceSet, A terminal device does not need to report a terminal capability in a certain frequency range. A terminal capability may be [default beam per coresetPoolIndex for M-DCI based MTRP]. A terminal capability may determine a default beam per coresetPoolIndex for multi-DCI based MTRP. It may also be the ability to do so. A terminal capability may be the ability to set a default beam for each coresetPoolIndex for multi-DCI based MTRP.

[0269] When a terminal device is configured with do-JointTCI-StateList and configured by PDCCH-Config, which is an RRC parameter containing two different coresetPoolIndexes in ControlResourceset, If a terminal device does not report terminal capability at a certain frequency, the offset between the reception of a scheduled or activated PDSCH and the reception of DCI format 1_0 / 1_1 / 1_2 in CORESET, associated with a coresetPoolIndex value of 0, is in a certain frequency domain [timeDurationForQCL] If the value is smaller, the terminal device may apply the specified joint / downlink TCI state, which is specific to a coresetPoolIndex value of 0, to the reception of the scheduled or activated PDSCH.

[0270] When a terminal device is configured with do-JointTCI-StateList and configured by PDCCH-Config, which is an RRC parameter containing two different coresetPoolIndexes in ControlResourceset, If the terminal device does not report terminal capability at a certain frequency, the terminal device receives the scheduled or activated PDSCH and the coresetPoolIndex value is 1 in the associated CORESET. You do not need to expect that the offset between receiving DCI formats 1_0 / 1_1 / 1_2 will be less than [timedomainForQCL] in a certain frequency domain.

[0271] Set dl-OnJointTCI-StateList on the terminal device and maintain the two specified TCI-states. It may be held. Regardless of the offset between the reception of the scheduled or activated PDSCH and the reception of DCI format 1_0 / 1_1 / 1_2, the terminal device operates in frequency range 1. You may make it.

[0272] Set dl-OrJointTCI-State on the terminal device and maintain two specified TCI-states. It is also possible that, regardless of the offset between the reception of a scheduled or activated PDSCH and the reception of DCI format 1_0 / 1_1 / 1_2, the terminal device may report to the base station device the terminal capability of [two default beams for S-DCI based MTRP] in frequency range 2.

[0273] If a terminal device does not report a terminal capability at a certain frequency, the offset between the reception of a scheduled or activated PDSCH and the reception of DCI format 1_0 / 1_1 / 1_2 may be greater than [TimeDurationForQCL].

[0274] The terminal device may be configured by the RRC parameter applyIndicatedTCIState. applyIndicatedTCIState is configured in DCI format 1_0 to activate or schedule It may indicate whether the first, second, or both of the indicated TCI-states apply to the scheduled PDSCH transmission. If the terminal device is set to cjt-Scheme-PDSCH and reports twoTCI-StatePDSCH-CJTTxScheme, or if the terminal device is set to sfnScheme, applyIndicatedTCI-StateDCI-1-0 may be set to both values, and the terminal device may apply both of the indicated TCI-states to PDSCH receptions scheduled or activated by DCI format 1_0 in search spaces other than the search space above CORESET#0.

[0275] If the terminal device is not set with applyIndicatedTCIState, the first indicated TCI-state However, this may be applied to the reception of a PDSCH. That PDSCH may be a PDSCH scheduled or activated by DCI format 1_0.

[0276] The terminal device may be configured with tciSelection-PresentInDCI. The configuration with tciSelection-PresentInDCI may be configured for both DCI format 1_1 and DCI format 1_2. The terminal device may receive DCI format 1_1 / 1_2. DCI format 1_1 / 1_2 may schedule or activate a PDSCH. When the terminal device is configured with tciSelection-PresentInDCI and receives DCI format 1_1 / 1_2 for which the terminal device schedules or activates a PDSCH, the terminal device may determine the indicated joint / downlink TCI state according to TCI selection method A for receiving the PDSCH.

[0277] TCI selection method A may involve the terminal device applying one of two indicated joint / downlink TCI states to the PDSCH reception when DCI format 1_1 / 1_2 indicates a code point. The code point may be "00", "01", "10", or "11". The code point may be for the TCI selection field. The TCI state is applied to the PDSCH reception. This may apply to all DMRS ports of PDSCHs corresponding to PDSCH transmission opportunities. PDSCH transmission opportunities are scheduled according to DCI format 1_1 / 1_2, or This could also be an opportunity to activate a PDSCH. A single TCI state could be a first TCI state, a second TCI state, or both the first and second TCI states.

[0278] TCI selection method A uses the DCI format 1_1 / 1_2 for the [TCI selection field], and the code When point “00” is indicated, the terminal device, according to DCI format 1_1 / 1_2, will send all PDSCH DMRS ports corresponding to the PDSCH transmission opportunity to be activated or scheduled. The first specified joint / downlink TCI condition may be applied.

[0279] TCI selection method A is for DCI format 1_1 / 1_2 for [TCI selection field] code When point "01" is indicated, the terminal device, according to DCI format 1_1 / 1_2, will activate or schedule all PDSCH DMRS ports corresponding to PDSCH transmission opportunities. Alternatively, the second specified joint / downlink TCI condition may be applied.

[0280] TCI selection method A is for DCI format 1_1 / 1_2 for [TCI selection field] code When point “10” is indicated, the terminal device may apply two indicated joint / downlink TCI states to all PDSCH DMRS ports corresponding to PDSCH transmission opportunities that are activated or scheduled, according to DCI format 1_1 / 1_2.

[0281] If tciSelection-PresentInDCI is not set on the terminal device, and the terminal device receives DCI format 1_1 / 1_2, the terminal device will schedule the reception of the PDSCH to reflect the instructed TCI state. It may apply to both activation and deactivation.

[0282] Next, we will explain CSI. The time-frequency resources used to report CSI may be controlled by the base station equipment. CSI consists of CQI (Channel Quality Indicator), PMI (Precoder Matrix Indicator), CRI (CSI-RS resource indicator), SSBRI (SS / PBCH Block Resource Indicator), LI (Layer Indicator), and RI (Rank Indicator). It may consist of some or all of the following: L1-RSRP (Layer 1-Signal-to-Interferance), L1-SINR (Layer 1-Signal-to-Interference-plus-Noise Ratio), CapabilityIndex, and TDCP (Time-Domain Channel Properties). CQI, PMI, SSBRI, LI, RI, L1-RSRP, Capa The bilityIndex and TDCP may also be referred to as CSI parameters.

[0283] A terminal device may have one or more CSI reporting settings configured. A CSI reporting setting may be the RRC parameter CSI-ReportConfig. A terminal device may have X LTM-CSI reporting settings configured. An LTM-CSI reporting setting may be the RRC parameter LTM-CSI-ReportConfig.

[0284] A terminal device may have M CSI resource settings configured. A CSI resource setting may be the RRC parameter CSI-ResourceConfig. A terminal device may have Y LTM-CSI resource settings configured. An LTM-CSI resource setting may be the RRC parameter LTM-CSI-ResourceConfig.

[0285] The terminal device may have one or two trigger states set in its list. The list of trigger states may be one or both of the RRC parameters CSI-AperiodicTriggerStateList and CSI-SemiPersistentOnPUSCH-TriggerList. The list of trigger states may contain one or more trigger states. Each The rig status may include a list of CSI reporting settings and a list of LTM-CSI reporting settings. CSI Report The list of settings may indicate one or more resource set IDs. Each trigger state in the list of trigger states for aperiodic CSI may include a list of CSI report settings. Each trigger state in the list of trigger states for semi-persistent CSI may include one CSI report setting.

[0286] Each CSI reporting configuration (CSI-ReportConfig) may be associated with one downlink BWP. A downlink BWP may be indicated by a BWP ID (BWP-ID, which is an RRC parameter). A downlink BWP may be provided in the CSI resource configuration. Each CSI reporting configuration (CSI-ReportConfig) includes codebook settings, time-domain behavior, and CQI and PMI configurations. This may include frequency granularity, measurement restriction configuration, and CSI-related quantity settings. The CSI-related items may also be LI, L1-RSRP, L1-SINR, CRI, SSBRI, CapabilityIndex, and TDCP.

[0287] Each LTM-CSI reporting setting (Reporting Setting LTM-CSI-ReportConfig) is used for channel measurement. Each LTM-CSI resource setting may be associated with a single LTM-CSI resource setting. Additionally, each LTM-CSI reporting setting (Reporting Setting LTM-CSI-ReportConfig) has an LTM-ReportConfigType. Time-domain operation is determined by nrOfReportedCells, the number of cells is determined by nrOfReportedCells, and the number of reported cells is determined by nrOfReportedCells. The number of reference signals per candidate cell may be included by nrOfReportedRS-PerCell. If spCellInclusion is set in each LTM-CSI reporting setting (Reporting Setting LTM-CSI-ReportConfig), that LTM-CSI reporting setting (Reporting Setting LTM-CSI-ReportConfig) may consist of L1 measurement results related to the current SpCell.

[0288] Time-domain behavior is specified by the report configuration type (reportConfigType), which is an RRC parameter. The time-domain operation may be set to 'aperiodic', 'semiPersistentOnPUCCH', 'semiPersistentOnPUSCH', or 'periodic'. If the time-domain operation is set to 'aperiodic', the CSI reporting setting may be the CSI reporting setting for aperiodic CSI. If the time-domain operation is set to 'semiPersistentOnPUCCH' or 'semiPersistentOnPUSCH', the CSI reporting setting may be the CSI reporting setting for semi-persistent CSI. i. If 'periodic' is set for time-domain operation, the CSI reporting setting may be the CSI reporting setting for periodic CSI.

[0289] For periodic CSI and semi-persistent CSI reporting, the period and slot offset are set. This may be done. For periodic CSI and semi-permanent CSI, CSI reporting corresponds to the submission of CSI reports. In the numerology of the BWP uplink, even if the period and slot offset are applied, stomach.

[0290] Each CSI reporting setting may include a report quantity setting. The report quantity may be a CSI-related item, an L1-RSRP-related item, an L1-SINR-related item, a CapabilityIndex-related item, or a TDCP-related item. You may specify related items. Frequency granularity is the reporting frequency setting (reportFreqConfiguration). It may include the following. PMI and CQI reports may correspond to wideband and sub-band. For example, the frequency granularity of PMI and CQI may be wideband or sub-band, respectively. Measurement limit settings may be time limits. Time limits may be set for either or both channel measurements and interference measurements. Codebook settings may be Type 1, Type 2, Extended Type 2-CSI, Super Extended Type 2-CSI, Super Extended Type 2-Port Selection, Super Extended Type 2-CJT, Super Extended Type 2-Port Selection CJT, Extended Type 2-Predictive PMI, or Super Extended Type 2- Port selection may include predicted PMI. Codebook settings may include codebook subset restrictions. Codebook settings may include group-based reporting settings.

[0291] The time-domain behavior of the LTM-CSI reporting configuration (LTM-CSI-ReportConfig) may be indicated by the LTM-ReportConfigType. The time-domain behavior of the LTM-CSI reporting configuration (LTM-CSI-ReportConfig) may be set to 'aperiodic', 'semiPersistentOnPUCCH', 'semiPersistentOnPUSCH', or 'periodic'. If the LTM-ReportConfigType (ltm-ReportConfigType) is set to 'periodic', 'semiPersistentOnPUCCH', or 'semiPersistentOnPUSCH', the period and slot offset may be set. If the LTM-ReportConfigType (ltm-ReportConfigType) is set to 'periodic', 'semiPersistentOnPUCCH', or 'semiPersistentOnPUSCH', in the numerology of the uplink BWP corresponding to the transmission of the CSI report, Period and slot offset may be applied.

[0292] Each CSI resource configuration (CSI-ResourceConfig) consists of S CSI resource sets (CSI-RS resource). It may contain a list of NZP CSI-RS resource sets. The list may be given by the RRC parameter csi-RS-ResourceSetList. The list may contain NZP CSI-RS resource sets It may include references to one or both of the SS / PBCH block sets. One list may include references to the CSI-IM (CSI-Interference Measurement) resource set. Each CSI-resource setting may be associated with one downlink BWP. A BWP may have the same downlink BWP. One or more CSI resource settings may be linked to one CSI reporting setting. For example, one or more CSIs with the same downlink BWP Source settings can be one or linked to CSI report settings.

[0293] Each CSI resource configuration may contain one or more CSI resource sets. Each CSI-RS The source set may be an NZP CSI-RS resource set. Each CSI-RS resource set may be an SS / PBCH block set. Each CSI-RS resource set may be a CSI-IM resource set It may also be a set. Each CSI-RS resource set contains one or more CSI-RS resources. However, each NZP CSI-RS resource set may contain one or more NZP CSI-RS resources. That's good too.

[0294] The time-domain behavior of a CSI-RS resource in a single CSI resource configuration may be indicated by the RRC parameter (resourceType). Time-domain behavior is asynchronous. The setting may be periodic, periodic, or semi-permanent. For periodic and semi-permanent CSIs, the CSI resource setting may include one CSI-RS resource set. For periodic CSIs and semi-persistent CSIs, group-based reporting is configured in the CSI resource settings. If so, the CSI resource configuration may include two or fewer CSI-RS resource sets.

[0295] In CSI resource settings for periodic CSI and semi-persistent CSI, the period and time offset ( A lot offset may be set. In periodic CSI and semi-persistent CSI, even if the period and time offset are given in the numerology of the downlink BWP given by BWPID good.

[0296] If multiple CSI resource configurations contain the same NZP-CSI-RS resource (or the same NZP CSI-RS resource ID), the same time-domain behavior may be configured for all multiple CSI resource configurations. The same time-domain operation may be configured for multiple CSI resource configurations. All CSI resource settings linked to a resource setting may share the same time domain.

[0297] Each LTM-CSI resource configuration (LTM-CSI-ReportConfig) may also include an LTM-CSI-SSB ResourceSet configuration. The LTM-CSI-SSB ResourceSet contains a list of Z SSB / PBCH block indices and Z LTM candidate cells that reference the candidate cells associated with the SS / PBCH block indices. It may consist of a list of supplementary identifiers (LTM-CandidateId). For each candidate cell, terminal The device may determine the time-domain operation of the SS / PBCH block from ssb-Periodicity and ssb-PositionslnBurst. For each candidate cell, the UE determines the frequency from subcarrierSpacing and ssbFrequency. The operation in the wavenumber domain may be determined.

[0298] The reports configured in the CSI reporting settings may be aperiodic, periodic, or semi-permanent. CSI-RS resource allocation may be periodic, semi-persistent, or periodic. A CSI report may be triggered for each CSI resource setting. The combination of CSI report settings and CSI resource settings may be determined by time-domain behavior. Periodic CSI-RS may be set by the upper layer. Semi-persistent CSI-RS may be activated and deactivated. Aperiodic CSI-RS may be set, activated, and triggered.

[0299] Periodic CSI-RS can be combined with any of the periodic, semi-permanent, or aperiodic CSI reporting configurations. They may be combined. Semi-persistent CSI-RS is either semi-persistent or aperiodic CSI reporting configuration. It may be combined with the following. Non-periodic CSI-RS may be combined with any of the semi-periodic reporting settings. For semi-persistent CSI reporting, in the case of reporting in PUCCH, the terminal device may receive an activation command. For semi-persistent CSI reporting, in the case of reporting in PUSCH, the terminal device may receive a triggering (trigger state) in DCI. Non-periodic CSI reporting may be triggered by DCI. Non-periodic CSI reporting may be triggered by MAC CE (e.g., a subset indication).

[0300] A terminal device configured with LTM-CSI reporting settings may specify the ResourceSetting for L1-RSRP measurement as the ltm-ChannelMeasurement resource. The ResourceSetting may be associated with aperiodic, semi-persistent, or periodic CSIs.

[0301] If a terminal device configured with LTM-CSI reporting settings (LTM-CSI-ReportConfig) is configured using spCellInclusion, the terminal device will have the current SpCell and nrOfReportedRSPseCell - For each candidate cell, a single reporting instance may report nrOfReportedRSPerCell different SSBRIs. If a terminal device configured with LTM-CSI reporting settings (LTM-CSI-ReportConfig) is not configured using spCellInclusion, the terminal device will report nrOfReportedRS-PerCell for each of the nrOfReportedCell candidate cells in a single reporting instance. Individual different SSBRIs may be reported. SSBRI k (k≧0) may correspond to the (k+1)th entry set in the ltm-CSI-SSBResourceSet associated with the corresponding LTM-CSI-SSB-ResourceSet.

[0302] This section explains the CSI processing criteria. Simultaneous CSI-ReportPerCC or simultaneousCSI-SubReportsPerCC-r18 is a method where terminal devices simultaneously process data within the component carrier. The number of CSIs to be calculated (N cc ) may be indicated. simultaneousCSI-ReportsPerCC or simultaneousCSI-SubReportsAllCC-r18 is used when a terminal device is simultaneously counting within all component carriers. The number of CSIs to be calculated may be indicated. At least one CSI report is within the component carrier. Terminal devices configured with sub-settings may use the RRC parameter simultaneousCSI-SubReportPerCC-r18 within the component carrier. Terminal devices for which CSI reporting is not configured with sub-settings within the component carrier may use the RRC parameter simultaneousCSI-ReportCC within the component carrier. Any component carrier A terminal device with at least one CSI reporting setting configured with subconfiguration is RRC The parameter simultaneousCSI-SubReportAllCC-r18 may be set. Terminal devices for which subconfiguration is not set on any component carrier may have the RRC parameter simultaneousCSI-ReportAllCC set. CPU If supporting simultaneous CPU computations, the terminal will be N CPU It can also be expressed as having a number of CPUs. Within a given OFDM symbol When L CPUs (CSI Processing Unit) are occupied for the calculation of CSI reports, the terminal device may have N CPU - L unoccupied CPUs. In the terminal device, N CSI reports start to occupy each of the CPU - L unoccupied CPUs on the same OFDM symbol. In this case, the terminal device may not update the CSI report requested with the lowest priority. Here, each CSI report (n = 0, 1,..., N - 1) is associated with the following Equation 1. Here, M is the following where Equation 2 ≤ N CPU may be the maximum number.

[0303]

Number

[0304]

Number

[0305] The terminal device may not be configured with an aperiodic CSI trigger state including N CPU or more report settings. The processing of CSI reports may occupy the CPU for the number of symbols as follows. · For a CSI report where the reported amount is set to none in the CSI report setting and the RRC parameter trs - info is set in the CSI - RS - ResourceSet, O = 0 may be valid. CPU = 0 may be valid. · For a CSI report according to the LTM - CSI report setting, O CPU = 1 may be valid. For a CSI report according to the CSI report setting, when the reported amount, which is an RRC parameter, is set to 'csi - RSRP','ssb - Index - RSRP', 'cri - SINR','ssb - Index - SINR', 'cri - RSRP - Index', 'cri - SINR - Index','ssb - Index - SINR - Index', or 'none', O CPUIt is acceptable for the answer to be 1. • The reporting amount of the RRC parameter is set to "tdcp", and the delay is set by the RRC parameter Y. In the case of a CSI report with a number Y, the value of X ∈ {1, 2} is reported by the Capability of the terminal device, O CPU =(Y+1)·X is acceptable. If the CSI reporting setting has the RRC parameter 'cri-RI-PMI-CQI', 'cri-RI-i1-CQI', 'cri-RI-CQI', or 'cri-RI-LI-PMI-CQI', then proceed as follows: When max{μPDCCH,μCSI-RS,μUL}≦3 and L=0 CPUs are occupied, Sending a PUSCH that includes either a sport block or a HARQ-ACK, or both. In cases where CSI reports are triggered aperiodically, O CPU =N CPU This may also apply. Here, CSI corresponds to a single CSI with wideband frequency granularity, and within a single resource without CRI reporting. Supports up to four CSI-RS ports, and the codebookType is set to 'typeI-SinglePanel'. Alternatively, reportQuantity may be set to 'csi-RI-CQI'. • CSI reporting settings are configured with codebookType set to 'typeI-SinglePanel'. The corresponding CSI-RS resource set for channel measurement consists of two resource groups and N resources. If it consists of a source pair, O CPU It may also be =X·N+M, where X is the number of CPUs occupied by pairs of CMRs following mTRP-CSInumCPU-r17, and M may be defined separately.

[0306] This section explains the priority rules for CSI reporting. For two duplicate PUSCHs, the terminal device will be prioritized if: the terminal device does not have sTx-2Panel configured; the terminal device has PDCCH-Config configured, which is an RRC parameter containing two different values ​​of coresetPoolIndex in different ControlResourceSets within the active DL BWP; or the terminal device has sTx-2Panel configured and there are two duplicates. If a PUSCH is associated with the same value in coresetPoolIndex, then the same priority index will be used. For physical channels with a priority, the priority rules described below may be applied. CSI reports are based on priority. iCSI It may be associated with Pri iCSI (y,k,c,s) = 2 × N cells ×M s ×y+N cells ×M s ×k+M s It can also be written as ×c+s. Here, For non-periodic CSI reports transmitted via PUSCH, y=0 may be set. For semi-permanent CSI reports transmitted via PUSCH, y=1 may be set. For semi-permanent CSI reports transmitted via PUCCH, y=2 may be set. For periodic CSI reports transmitted via PUCCH, y=3 may be set. • For CSI reports that report L1-RSRP or L1-SINR, k=0 may be set. In the case of a CSI report that does not report L1-SINR, K=1 may be used. c may be the index of the serving cell. cells c may be the value of the RRC parameter maxNrofServingCells. If LTM-CSI measurement reporting is set up, c is This could also be the index of the serving cell for which measurement reports are set. ·s may be the measurement setting ID (reportConfigID). smay be the value of the RRC parameter maxNrofCSI-ReportConfigurations. If LTM-CSI measurement reporting is configured, s may be LTM-CSI-ReportConfigConfigID, and M s This may be the value of the RRC parameter maxNrofLTM-CSI-ReportConfiguration. ·Pri iCSI If the value of (y,k,c,s) is lower in the first report than in the second report, then the first CSI The report takes precedence over the second CSI report. The time occupancy of the physical channel scheduled to send the CSI report overlaps with at least one OFDM symbol, and the same key When transmitted via carrier, two CSI reports can be described as colliding. If conflicting reports are set and y differs between the two CSI reports, unless the value of y is 2 for one and 3 for the other, Pri iCSI CSI reports with high (y,k,c,s) values ​​do not need to be sent by the terminal device. CSI reports configured in LTM-CSI-Reporting Settings are CSI reports configured in CSI Reporting Settings If it conflicts with the report, Pri iCSI (y,k,c,s) has a higher priority than all other CSI reports. It is also acceptable. A semi-persistent CSI report transmitted via PUSCH may have one or more OFDM symbols on the same carrier. The PUSCH data transmission overlaps in time with the N2+d signal, and the earliest symbol of these PUSCH channels follows the last symbol of the DCI that schedules the PUSCH. 2,1 Earlier than the symbol If not initiated, the CSI report does not need to be sent by the UE. Otherwise, If the imline requirement is not met, this will be an error case. The terminal device may expect that the above timing requirement is met for PUSCH transmissions that overlap in time, if at least one of the first or second PUSCH transmissions is in response to DCI format detection by the terminal device.

[0307] Based on the above description, various embodiments will be explained. Note that any processes omitted in the following description may be replaced by the processes described above.

[0308] Figure 5 is a block diagram showing the configuration of the terminal device (UE122) in this embodiment. Note that, to avoid making the explanation complicated, Figure 5 shows only the main components closely related to this embodiment. To show.

[0309] The UE122 shown in Figure 5 consists of a receiving unit 500 that receives control information (DCI, MAC CE, RRC signaling, etc.) from the base station equipment, and a processing unit that performs processing according to the parameters contained in the received control information. It consists of a unit 502 and a transmission unit 504 that transmits control information (UCI, RRC signaling, etc.) to a base station device. The above-mentioned base station device may be an eNB102 or a gNB108. Furthermore, the processing unit 502 has various layers (for example, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, etc.) The functions of the physical layer (and NAS layer) may be included in some or all of them. That is, the processing unit 502 includes physical layer processing The receiver 500 may include some or all of the processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP layer processing unit, RRC layer processing unit, and NAS layer processing unit. In addition to or instead of these, the receiver 500 may include some or all of the functions of various layers (e.g., physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the receiver 500 may include some or all of the physical layer receiver, MAC layer receiver, RLC layer receiver, PDCP layer receiver, SDAP layer receiver, RRC layer receiver, and NAS layer receiver.

[0310] Figure 6 is a block diagram showing the configuration of the base station equipment in this embodiment. To avoid sloppiness, Figure 6 shows only the main components closely related to this embodiment. As shown above, the base station device may be eNB102 or gNB108.

[0311] The base station device shown in Figure 6 consists of a transmitting unit 600 that transmits control information (DCI, MAC CE, RRC signaling, etc.) to the UE 122, a processing unit 602 that creates control information (DCI, RRC signaling including parameters, etc.) and transmits it to the UE 122, causing the processing unit 502 of the UE 122 to perform processing, and a receiving unit 604 that receives control information (UCI, RRC signaling, etc.) from the UE 122. Furthermore, the processing unit 602 may include some or all of the functions of various layers (for example, the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 602 includes the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP layer processing unit, RRC layer processing unit, and NAS layer processing unit. It may include some or all of the above. In addition to or instead of the above, the transmitting unit 600 may include various The transmitter 600 may include some or all of the functions of various layers (for example, the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the transmitter 600 may include some of the functions of the physical layer transmitter, MAC layer transmitter, RLC layer transmitter, PDCP layer transmitter, SDAP layer transmitter, RRC layer transmitter, and NAS layer transmitter. Or it may include all of them.

[0312] An example of the processing of the terminal device (UE122) in this embodiment will be explained using Figure 9. In this embodiment, the processing unit 502 of UE122 is configured to perform RRC processing, PDCP processing, RLC processing, MAC processing, and PHY processing. It may include a PHY processing unit.

[0313] Figure 9 shows an example of the processing of UE122 in this embodiment. The processing unit 502 of UE122 makes a conditional judgment (step S900) and operates based on the judgment (step S902).

[0314] UE122 may receive the measurement settings from the base station equipment via RRC messages. The measurement settings may be received via MAC CE, DCI, or other means. It is permissible to receive it by law.

[0315] UE122 may perform measurements of beam measurement items (measurement quantities) based on the settings for the measurement. The measurement item may be RSRP or SINR. Or, other measurement items may be used. The beam may be a beam associated with a serving cell, a beam associated with a cell that is not a serving cell, or any other beam. The measurement of the measurement items of the beam is for one beam. The measurement may be performed on multiple beams, or on multiple beams. The beams may be SSB, CSI-RS, or other signals. In addition to this, Alternatively, the beam may be an SSB or CSI-RS resource set. It may be associated with measurement in this context.

[0316] The UE122 measures the beam measurement quantity based on other settings. That's fine.

[0317] UE122 may determine whether the measurement item satisfies certain conditions. The conditions below may apply, or other conditions may apply as well. (a) The measurement parameters of the beams that make up the current serving cell are greater than the threshold. (b) The measurement parameters of the beams that make up the current serving cell are smaller than the threshold. (c) The measurement parameters of the beams constituting the candidate cell are the same as those of the beams constituting the current serving cell. The value is greater than the value obtained by adding an offset to the measurement item of M. (d) The measurement parameters of the beams constituting the candidate cell are greater than the threshold. (e) The measurement parameters of the beams currently constituting the SpCell are smaller than the first threshold, and the candidate cell The measurement parameters of the constituent beam are greater than the second threshold. (f) During the period indicated by the TimeToTrigger value, the measurement parameters of the beams constituting the current serving cell are greater than the threshold. (g) During the period indicated by the TimeToTrigger value, the measurement parameters of the beams constituting the current serving cell are less than the threshold. (h) During the period indicated by the TimeToTrigger value, the measurement parameters of the beams constituting the candidate cell are greater than the measurement parameters of the beams constituting the current serving cell plus an offset. (i) During the period indicated by the TimeToTrigger value, the measurement parameters of the beams constituting the candidate cell are greater than the threshold. (j) During the period indicated by the TimeToTrigger value, the measurement parameters of the beams constituting the current SpCell are less than the first threshold, and the measurement parameters of the beams constituting the candidate cell are greater than the second threshold. A measurement value greater than the threshold can be rephrased as the quality being better than the threshold, and conversely, a measurement value smaller than the threshold can be rephrased as the quality being worse than the threshold.

[0318] The aforementioned conditions may be included in the settings related to the measurement, or they may be included in other settings. The value of TimeToTrigger may be included in the settings related to the measurement, or they may be included in other settings. It may be included.

[0319] MAC CE may consist of one or more fields. For example, one of the one or more fields may be a field for a set of information elements indicating the measurement result. In addition to or instead of, for example, one or more of the above. One of the fields may be a field for setting information elements for identifying the beam. In addition to or instead of the above, for example, the 1 One of the one or more fields may be a field for setting information elements to identify the cell to which the beam is associated. In addition to or instead of that, for example, one of the one or more fields This may be a field for setting an information element indicating whether or not the measurement result of a beam satisfies the aforementioned conditions. In addition to or instead of this, for example, one or more of the above may be used. Among the numerical fields, one field may be a field for setting other information elements. The field for setting information elements for identifying the beam may be associated with a field for setting information elements indicating the measurement result, or with a field for setting information elements for identifying the cell to which the beam is associated, or with a field for setting information elements indicating whether the measurement result of a certain beam satisfies the conditions, or with a field for setting other information elements.

[0320] Based on the determination that the measurement results of the measurement items satisfy the conditions, UE122 proceeds to the previous The measurement results of one or more beams that satisfy the specified conditions are set in the field of the MAC CE. Alternatively, a beam that satisfies the above conditions may be a beam that satisfies the above conditions and has a measurement result greater than the threshold, or a beam that satisfies the above conditions and has a measurement result less than the threshold. Alternatively, the UE122 may be Based on the determination that the measurement results of the measurement items satisfy the conditions, the measurement results of one or more beams that do not satisfy the conditions may be set in the MAC CE field. i. In addition to or instead of the above, beams that do not satisfy the above conditions may be beams that do not satisfy the above conditions but whose measurement result is greater than the threshold, or beams that do not satisfy the above conditions but whose measurement result is less than the threshold. The number of beam measurement results to be set in the MAC CE field may be any integer value in the range of 1 to 32, and relating to the measurement It may be any integer value in the range of 1 to 32 determined based on the settings, or any other integer. It may also be a value.

[0321] The value of the threshold may be included in the settings related to the measurement, or it may be included in other settings.

[0322] The UE122 outputs the measurement results of beams that satisfy the above conditions, and beams that do not satisfy the above conditions. The measurement results of the beam may be set in the MAC CE field in priority to the measurement results of the beam. In addition or in lieu thereof, the UE122 may set the measurement results of the beam that does not meet the above conditions in the above clause. The measurement results of beams that satisfy the criteria may be set in the MAC CE field with priority over beams that have a high measurement result for the measurement item, or beams with a low measurement result for the measurement item may be set in the MAC CE field with priority over beams with a high measurement result for the measurement item, or the measurement results of beams may be set in the MAC CE field by other means.

[0323] A beam that does not satisfy the above conditions may be a beam associated with the same cell as a beam that satisfies the above conditions. In addition to or instead of the above, a beam that does not satisfy the above conditions may be a beam associated with a different cell than the one associated with a beam that satisfies the above conditions, a beam associated with the same cell as the beam that does not satisfy the above conditions, a beam associated with a different cell than the one associated with a beam that does not satisfy the above conditions, or any other beam.

[0324] The UE122 may set an information element in the MAC CE field indicating whether the measurement results of one or more beams set in the MAC CE field satisfy the conditions. In addition or alternatively, the information element may be associated with each measurement result set in the MAC CE field. In addition or alternatively, the UE122 may, Based on the determination that the measurement result of a certain beam satisfies the above conditions, the MAC CE field may be set to 1 as the information element associated with the measurement result, or Based on the determination that the measurement result of the beam does not satisfy the above conditions, the MAC CE field may be set to 0 as the information element associated with the measurement result. Based on the determination that the measurement result of a certain beam satisfies the above conditions, the MAC CE field may be set to 0 as the information element associated with the measurement result. Based on the determination that the measurement result of a certain beam does not satisfy the above conditions, the MAC CE field may be set to 1 as the information element associated with the measurement result. In addition to or instead of the above, the UE122 is set in the field of the MAC CE Information indicating which of the one or more measurement results satisfies the above conditions The information may be set as the information element in the field of the MAC CE. For example, the MAC CE Of the one or more measurement results set in the field, any of the measurement results The information indicating whether the condition is met may be an index represented by a 4-bit binary number, or it may be a value with a different number of bits. For example, the bit associated with the 5th measurement result Based on the measurement results of the system satisfying the above conditions, the UE122 will use the information element You can also set index #4.

[0325] UE122 may set one or more of the measurement results in the MAC CE field along with the beam identifier and the cell identifier, or include them in the RRC message, or in the UCI, or in other messages transmitted to the base station equipment.

[0326] The measurement result may be the value of the measured measurement item, the average value of the measurement item for each beam of multiple beams, or the time average value of a single beam over a certain period. Alternatively, the value may be calculated by another method from one or more measurement items. The measurement items for the beam in the above-mentioned measurement may be measurement items measured with a single beam, The measurement items may be measured using multiple beams, or they may be measured using cells that make up the beams.

[0327] The value of the beam identifier may be the value of the SSB identifier if the beam is an SSB, or it may be the value of the SSB identifier plus an offset value. The value may be calculated by another method based on the aforementioned SSB value. The maximum value obtained may be 63, 64, 191, 192, or any other natural number, or any other value. Furthermore, if the beam is a CSI-RS, the value of the beam identifier may be the value of the CSI-RS identifier, or the value of the CSI-RS plus one or more offset values. Furthermore, the value may be calculated by another method based on the CSI-RS value. By using the offset to represent the beam identifier, the same identifier can be used for SSB and CSI-RS. , it can be identified. The offset value may be 64 or 192. Furthermore, it may be any natural number n, or any other value. Also, the identification of the beam The child may be represented in binary, in the form of a bitmap, or in other ways. It may also be represented as follows. By using the bitmap, the size of MAC CE can be reduced. The TCI state identifier may be used as the beam identifier. Furthermore, the identifier of the TCI state may be represented in binary, in the form of a bitmap, or by any other method. This allows us to associate the TCI identifier with the measurement results.

[0328] The offset may be set in the UE122 by RRC signaling from the base station equipment, by MAC CE, by DCI, or by other means. The UE122 may be determined by default, or it may be calculated by the base station equipment from a value set by RRC signaling, or the UE122 may be determined by other means.

[0329] UE122 may transmit a MAC CE containing the measurement results to the base station device, or the measurement results The RRC message containing the measurement results may be transmitted to the base station device, or the UCI containing the measurement results may be transmitted to the base station device, or other forms of messages containing the measurement results may be transmitted to the base station device.

[0330] UE122 may transmit the measurement results based on a method set by the base station equipment. You don't have to.

[0331] The MAC CE may include any, some, or all of the following information. Alternatively, the UCI used for reporting may include the following information. The report may include any of the information, some of the information, all of it, or any other information. Instead of the MAC CE mentioned above, the RRC message used in the report may be used. The message may include any, some, all, or any other information from the following sources. Other messages used for reporting in place of the aforementioned MAC CE may include any, some, all, or any other information from the following sources. • Information showing the measurement results of the measured items. • Information indicating the type of measurement item • Information indicating the RS identifier used for the measurement results. • Information indicating the type of RS used for the measurement results. • Information indicating the cell identifier associated with the RS used for the measurement results. • Information showing the measurement results of the cells associated with the RS used for the measurement results. • Information regarding the conditions that triggered the measurement report.

[0332] The cell identifier may be an identifier for identifying a cell, an identifier for the cell to which the beam containing the measurement results is associated with the MAC CE, a cell-specific identifier, a PCI (Physical Cell ID), a GCI (Global Cell ID), or any other identifier.

[0333] The aforementioned RS (Reference Signal) may refer to a reference signal or an SSB. It could be CSI-RS, or any other signal.

[0334] The embodiments described above may be combined with each other. In addition to or instead of the above, the RRC resetting procedures in each embodiment may be performed independently in each current serving cell.

[0335] In the example of this embodiment described above, the terminal device can appropriately report the measurement results of each beam to the base station device by including in the MAC CE field the measurement results of beams associated with the same cell as the beam that satisfies the conditions, in addition to the measurement results of beams that satisfy the conditions.

[0336] In the example of this embodiment described above, when the MAC CE field transmitted from the terminal device to the base station device includes both the measurement results of beams that satisfy the conditions and the measurement results of beams that do not satisfy the conditions, the inclusion of the information element in the MAC CE field allows the base station device to know which measurement results satisfy the conditions.

[0337] Furthermore, unless otherwise specified, the term "wireless bearer" in the above description may refer to a DRB, an SRB, or both a DRB and an SRB.

[0338] Furthermore, in the above explanation, terms such as "user plane," "user plane protocol," and "user plane interface" may be used interchangeably.

[0339] Furthermore, in the above explanation, expressions such as "terminal device variable," "terminal variable," and "variable" may be interchangeable.

[0340] Furthermore, unless otherwise specified, the serving cell change described above may refer to a change in a Layer 1 or Layer 2 serving cell.

[0341] Furthermore, in the above explanation, expressions such as "provided," "signaled," and "selected" may be interchangeable.

[0342] Furthermore, in the above explanation, expressions such as "LTM candidate target identifier" and "LTM candidate target entry identifier" may be interchangeable.

[0343] Furthermore, in the above explanation, expressions such as "to be notified" and "to be pointed out" may be used interchangeably.

[0344] Furthermore, in the above explanation, expressions such as "link," "correspond," and "associate" may be used interchangeably.

[0345] Furthermore, in the above explanation, expressions such as "included," "included," and "was included" may be interchangeable.

[0346] Furthermore, in the above explanation, "the aforementioned..." may be replaced with "the aforementioned...".

[0347] Also, in the above explanation, the phrases "~ has been confirmed," "~ is set," and "~ is included" are used. These expressions may be interchangeable.

[0348] Furthermore, in the above explanation, expressions such as "beam judged to meet the conditions," "beam judged to have met the conditions," "beam that meets the conditions," and "beam that met the conditions" may be interchanged with each other, and expressions such as "beam judged not to meet the conditions," "beam judged not to have met the conditions," "beam that does not meet the conditions," and "beam that did not meet the conditions" may also be interchanged with each other.

[0349] Furthermore, in the above explanation, "prioritize A over B" can be rephrased as "prioritize A before B."

[0350] Furthermore, in the examples of processes or process flows described above, some or all of the steps may not be executed. Also, in the examples of processes or process flows described above, the order of the steps may differ. Furthermore, in the examples of processes or process flows described above, some or all of the processes within each step may not be executed. Furthermore, in the examples of processes or process flows described above, the order of the processes within each step may differ. Also, in the above description, "perform B based on the fact that A is true" may be rephrased as "perform B." That is, "performing B" is equivalent to "being true A." It may be executed independently.

[0351] Furthermore, in the above explanation, "A may be replaced with B" may include not only replacing A with B, but also replacing B with A. Also, in the above explanation, if it states "C may be D" and "C may be E", it may also include "D may be E". Also, in the above explanation, if it states "F may be G" and "G may be H", it may also include "F may be H".

[0352] Furthermore, in the above explanation, if condition "A" and condition "B" are contradictory conditions, condition "B" may be expressed as an "other" condition of condition "A".

[0353] Furthermore, in the above explanation, expressions such as "set A to the MAC CE field," "include A to the MAC CE field," and "include A to MAC CE" can be used interchangeably. In this context, expressions such as "MAC CE contains A," "A is set in MAC CE," "MAC CE contains A in its field," and "MAC CE has A in its field" are interchangeable.

[0354] The program running on the device according to this embodiment may be a program that controls the Central Processing Unit (CPU), etc., to make the computer function in order to realize the functions of this embodiment. The program or the information handled by the program may be temporarily loaded into volatile memory such as Random Access Memory (RAM) or flashed during processing. It is stored in non-volatile memory such as RAM or a Hard Disk Drive (HDD), and the CPU processes it as needed. This is how data is read, modified, and written.

[0355] Furthermore, some parts of the apparatus in the above-described embodiment may be implemented using a computer. In that case, the program for implementing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into a computer system and executed. The term "computer system" here refers to a computer system built into the apparatus, and includes hardware such as an operating system and peripheral devices. The "computer-readable recording medium" may be any of the following: a semiconductor recording medium, an optical recording medium, a magnetic recording medium, etc.

[0356] Furthermore, "computer-readable recording media" includes not only those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs over networks like the Internet or communication lines like telephone lines, but also those that hold programs for a fixed period of time, such as the volatile memory inside computer systems that act as servers or clients in such cases. That's fine. Also, the above program may be for the purpose of implementing some of the functions mentioned above, and may also be a program that already has the aforementioned functions recorded in the computer system. It is also acceptable if it can be achieved in combination with the above.

[0357] Furthermore, each functional block or feature of the apparatus used in the embodiments described above may be implemented or executed by an electrical circuit, typically an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), and field-programmable circuits. This may include a multi-gate array (FPGA), other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, a conventional processor, controller, microcontroller, or state machine. The general-purpose processor, or each of the aforementioned circuits, may consist of digital or analog circuits. Furthermore, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, integrated circuits using such technologies may also be used.

[0358] It should be noted that this embodiment is not limited to the embodiments described above. Although the embodiments describe an example of a device, this embodiment is not limited to this and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0359] Although this embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like that do not depart from the gist of this embodiment are also included. Furthermore, this embodiment can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this embodiment. In addition, configurations in which elements described in the above embodiment that produce similar effects are substituted for each other are also included. [Explanation of Symbols]

[0360] 100 E-UTRA 102 eNB 104 EPC 106 NR 108 gNB 110 5GC 112, 114, 116, 118, 120, 124 Interfaces 122 UE 200, 300 PHY 202, 302 MAC 204, 304 RLC 206, 306 PDCP 208, 308 RRC 310 SDAP 210, 312 NAS 500, 604 Receiver 502, 602 processing unit 504, 600 Transmitter

Claims

1. A terminal device that communicates with a base station device, It comprises a receiving unit, a processing unit, and a transmitting unit. The receiving unit is The base station device receives settings for one or more measurements, The aforementioned processing unit, Based on the above settings, measure a certain beam's measurement item once or multiple times. Based on the determination that the aforementioned measurement item satisfies one condition, Measurement results of one or more beams that satisfy the above conditions, The measurement results of one or more beams that do not meet the above conditions Included in MAC CE, A beam that does not satisfy the above conditions is a beam associated with the same cell as a beam that satisfies the above conditions, The aforementioned transmitting unit The MAC CE is transmitted to the base station device. Terminal device.

2. A base station device that communicates with terminal devices, A transmitting unit that transmits RRC (Radio Resource Control) signaling to the terminal device, A processing unit, and The processing unit includes settings for one or more measurements in the RRC signaling, By applying the RRC signaling to the terminal device, the terminal device will be able to set Based on this, one or more measurement parameters of a beam are measured, and if the measurement parameters meet one condition Based on the determination that the conditions are met, the measurement results of one or more beams that satisfy the above conditions The results, along with the measurement results of one or more beams that do not meet the above conditions, are included in MAC CE. A beam that does not satisfy the above conditions is a beam associated with the same cell as a beam that satisfies the above conditions, and the transmitting unit causes the base station device to transmit the MAC CE. Base station equipment.

3. A method implemented in a terminal device that communicates with a base station device, The base station device receives settings for one or more measurements, Based on the above settings, measure a certain beam's measurement item once or multiple times. Based on the determination that the aforementioned measurement item satisfies one condition, Measurement results of one or more beams that satisfy the above conditions, The measurement results of one or more beams that do not meet the above conditions Included in MAC CE, A beam that does not satisfy the above conditions is a beam associated with the same cell as a beam that satisfies the above conditions, The MAC CE is transmitted to the base station device. method.

Images