Terminal device, base station device, method, and integrated circuit

Abstract

This terminal device is provided with a control unit for transitioning from a first state of a cell group to a second state thereof if instructed to enter the second state. The first state is a state in which a first BWP is activated in an SpCell of the cell group, a downstream link control channel (PDCCH) is monitored in the first BWP, and measurement of channel state information (CSI) with respect to the first BWP is performed. The second state is a state in which a second BWP is activated in the SpCell of the cell group, the PDCCH is not monitored in the second BWP, and measurement of the channel state information (CSI) with respect to the second BWP is performed.

Description

Technical Field

[0001] The present invention relates to a terminal device, a base station device, a method, and an integrated circuit. This application claims priority to Japanese Patent Application No. 2020-99022, filed on June 8, 2020, the content of which is incorporated herein by reference.

Background Art

[0002] The radio access method and radio network of cellular mobile communication (hereinafter referred to as “Long Term Evolution (LTE: registered trademark)”, or “Evolved Universal Terrestrial Radio Access: EUTRA”).) and a core network (hereinafter referred to as “Evolved Packet Core: EPC”) are being studied in the 3rd Generation Partnership Project (3GPP). EUTRA is also referred to as E-UTRA.

[0003] Also, in 3GPP, as radio access methods and radio network technologies for the 5th generation cellular system, technical studies and standardization of LTE-Advanced Pro, which is an extended technology of LTE, and NR (New Radio technology), which is a new radio access technology, are being carried out (Non-Patent Document 1). In addition, studies on 5GC (5 Generation Core Network), which is a core network for the 5th generation cellular system, are also being carried out (Non-Patent Document 2).

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Non-Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] As one of the NR technologies, in order to enable high-capacity data communication, there is a dual connectivity (also referred to as multi-connectivity) technology in which one or more base station devices and a terminal device communicate using a plurality of cell groups. In this dual connectivity, in order to perform communication in each cell group, the terminal device needs to monitor whether there is a message addressed to itself in each cell group. The terminal device always needs to monitor a plurality of cell groups so as to be able to communicate with low latency when high-capacity data communication occurs, and there is a problem of consuming a lot of power. Therefore, a technology for monitoring some cell groups less frequently or stopping (cell group dormant technology) has been started (Non-Patent Document 3).

[0006] In the cell group dormancy, how to handle the cell (SpCell) that is always in the active state at present is being studied, but it is also necessary to study cells other than the SpCell.

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

Means for Solving the Problems

[0008] To achieve the above object, one aspect of the present invention takes the following means. That is, the first embodiment of the present invention is a terminal device, which includes a control unit that transitions from a first state to a second state when instructed to enter the second state of the cell group. The first state is a state in which a first BWP is activated in the SpCell of the cell group, the downlink control channel (PDCCH) is monitored in the first BWP, and the channel state information (CSI) for the first BWP is measured. The second state is a state in which a second BWP is activated in the SpCell of the cell group, the PDCCH is not monitored in the second BWP, and the channel state information (CSI) for the second BWP is measured.

[0009] (2) The second embodiment of the present invention is a base station device that communicates with a terminal device, which includes a control unit that instructs the terminal device to enter the second state of the cell group, thereby causing the terminal device to transition from the first state to the second state. The first state is a state in which a first BWP is activated in the SpCell of the cell group, the downlink control channel (PDCCH) is monitored in the first BWP, and the channel state information (CSI) for the first BWP is measured. The second state is a state in which a second BWP is activated in the SpCell of the cell group, the PDCCH is not monitored in the second BWP, and the channel state information (CSI) for the second BWP is measured.

[0010] (3) A third embodiment of the present invention is a method applied to a terminal device, comprising a step of transitioning from a first state to a second state when instructed to enter the second state of a cell group. The first state is a state in which a first BWP is activated in the SpCell of the cell group, a downlink control channel (PDCCH) is monitored in the first BWP, and channel state information (CSI) measurement for the first BWP is performed. The second state is a state in which a second BWP is activated in the SpCell of the cell group, PDCCH is not monitored in the second BWP, and channel state information (CSI) measurement for the second BWP is performed.

[0011] (4) A fourth embodiment of the present invention is a method applied to a base station device communicating with a terminal device, comprising a step of transitioning the terminal device from a first state to a second state by instructing the terminal device to enter the second state of a cell group. The first state is a state in which a first BWP is activated in the SpCell of the cell group, a downlink control channel (PDCCH) is monitored in the first BWP, and channel state information (CSI) measurement for the first BWP is performed. The second state is a state in which a second BWP is activated in the SpCell of the cell group, PDCCH is not monitored in the second BWP, and channel state information (CSI) measurement for the second BWP is performed.

[0012] (5) A fifth embodiment of the present invention is an integrated circuit mounted on a terminal device, which causes the terminal device to transition from a first state to a second state when instructed to enter the second state of a cell group. The first state is a state in which a first BWP is activated in the SpCell of the cell group, a downlink control channel (PDCCH) is monitored in the first BWP, and channel state information (CSI) for the first BWP is measured. The second state is a state in which a second BWP is activated in the SpCell of the cell group, the PDCCH is not monitored in the second BWP, and channel state information (CSI) for the second BWP is measured.

[0013] (6) A sixth embodiment of the present invention is an integrated circuit mounted on a base station device that communicates with a terminal device, which causes the base station device to transition the terminal device from a first state to a second state by instructing the terminal device to enter the second state of a cell group. The first state is a state in which a first BWP is activated in the SpCell of the cell group, a downlink control channel (PDCCH) is monitored in the first BWP, and channel state information (CSI) for the first BWP is measured. The second state is a state in which a second BWP is activated in the SpCell of the cell group, the PDCCH is not monitored in the second BWP, and channel state information (CSI) for the second BWP is measured.

[0014] Note that these general or specific aspects may be implemented by a system, device, method, integrated circuit, computer program, or recording medium, or may be implemented by any combination of a system, device, method, integrated circuit, computer program, and recording medium.

Advantages of the Invention

[0015] According to one aspect of the present invention, a terminal device can realize efficient communication control processing.

Brief Description of the Drawings

[0016]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Embodiments for Carrying Out the Invention

[0017] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0018] LTE (and LTE-A Pro) and NR may be defined as different Radio Access Technologies (RATs). Also, LTE that can be connected with NR in Multi Radio Dual connectivity may be distinguished from conventional LTE. Also, LTE with a core network of 5GC may be distinguished from conventional LTE with a core network of EPC. This embodiment may be applied to NR, LTE, and other RATs. In the following description, terms related to LTE and NR are used for explanation, but this embodiment may also be applied to other technologies using other terms. Also, the term E-UTRA in this embodiment may be replaced with the term LTE, or the term LTE may be replaced with the term E-UTRA.

[0019] FIG. 1 is a schematic diagram of a communication system according to each embodiment of the present invention.

[0020] E-UTRA 100 is a radio access technology described in Non-Patent Document 4 or the like, and consists of a cell group (CG) composed of one or more frequency bands. eNB (E-UTRAN Node B) 102 is a base station device of E-UTRA 100. EPC (Evolved Packet Core) 104 is a core network described in Non-Patent Document 14 or the like, and is designed as a core network for E-UTRA 100. Interface 112 is an interface between eNB 102 and EPC 104, and there are a control plane (CP) through which control signals pass and a user plane (UP) through which its user data passes.

[0021] NR106 is a wireless access technology described in Non-Patent Document 5 etc., and consists of a cell group (CG) composed of one or more frequency bands. gNB (g Node B) 108 is a base station device of NR106. 5GC110 is a core network described in Non-Patent Document 2 etc., and is designed as a core network for NR106, but may also be used as a core network for E-UTRA100 having a function of connecting to 5GC110. Hereinafter, E-UTRA100 may include E-UTRA100 having a function of connecting to 5GC110.

[0022] Interface 114 is an interface between eNB102 and 5GC110, interface 116 is an interface between gNB108 and 5GC110, interface 118 is an interface between gNB108 and EPC104, interface 120 is an interface between eNB102 and gNB108, and interface 124 is an interface between EPC104 and 5GC110. Interfaces 114, 116, 118, 120, and 124 etc. may be interfaces that pass only CP, or only UP, or both CP and UP. Also, interfaces 114, 116, 118, 120, and 124 etc. may not exist depending on the communication system provided by the communication carrier.

[0023] UE122 is a terminal device corresponding to a part or all of E-UTRA100 and NR106. As described in part or all of Non-Patent Document 4 and Non-Patent Document 5, when UE122 connects to the core network via a part or all of E-UTRA100 and NR106, a logical path called a radio bearer (RB) is established between UE122 and a part or all of E-UTRA100 and NR106. The radio bearer used for CP is called a signaling radio bearer (SRB), and the radio bearer used for UP is called a data radio bearer (DRB).

[0024] Figure 2 is a protocol stack diagram of the user plane (UP) and control plane (CP) of the terminal device and the base station device in the E-UTRA radio access layer in each embodiment of the present invention.

[0025] Figure 2(A) is a protocol stack diagram of the UP used when the UE 122 communicates with the eNB 102 in the E-UTRA 100.

[0026] PHY (Physical layer) 200 is a radio physical layer that provides a transmission service to the upper layer using a physical channel. PHY 200 is connected to the upper MAC (Medium Access Control layer) 202 via a transport channel. Data moves between MAC 202 and PHY 200 via the transport channel. Data transmission and reception are performed between the PHYs of the UE 122 and the eNB 102 via a radio physical channel.

[0027] MAC 202 is a medium access control layer that maps various logical channels to various transport channels. MAC 202 is connected to the upper RLC (Radio Link Control layer) 204 described later via a logical channel. Logical channels are roughly divided according to the type of information to be transmitted, and are divided into a control channel for transmitting control information and a traffic channel for transmitting user information. MAC 202 may have functions such as controlling PHY 200 for performing discontinuous reception / transmission (DRX / DTX), executing a random access procedure, notifying transmission power information, and performing HARQ control. In addition, MAC 302 may have a function of controlling the active state of the cell set in the RRC layer (Non-Patent Document 6).

[0028] RLC 204 is a radio link control layer that segments the data received from the upper-layer PDCP (Packet Data Convergence Protocol Layer) 206, which will be described later, and adjusts the data size so that the lower layer can properly transmit the data.

[0029] PDCP 206 is a packet data convergence protocol layer for efficiently transmitting user data such as IP packets in a radio section. PDCP 206 may have a header compression function for compressing unnecessary control information. Also, PDCP 206 may have a data encryption function.

[0030] Note that the data processed in MAC 202, RLC 204, and PDCP 206 are called MAC PDU (Protocol Data Unit), RLC PDU, and PDCP PDU, respectively. Also, the data passed from the upper layer to MAC 202, RLC 204, and PDCP 206, or the data passed to the upper layer are called MAC SDU (Service Data Unit), RLC SDU, and PDCP SDU, respectively. Also, the segmented RLC SDU is called an RLC SDU segment.

[0031] Figure 2(B) is a protocol stack diagram of the CP used when UE 122 communicates with eNB 102 and the MME (Mobility Management Entity), which is a logical node that provides functions such as authentication and mobility management, in E-UTRA 100.

[0032] In the protocol stack of the CP, in addition to PHY200, MAC202, RLC204, PDCP206, there are RRC (Radio Resource Control layer) 208 and NAS (non Access Strarum) 210. RRC208 performs processes such as establishment, re - establishment, suspension, and resume of RRC connections, as well as re - configuration of RRC connections, for example, establishment, change, release, etc. of radio bearers (RB) and cell groups. It also controls logical channels, transport channels, and physical channels, and performs settings for handover and measurement. It is a radio link control layer. RB may be divided into signaling radio bearer (SRB) and data radio bearer (DRB). SRB may be used as a path for transmitting RRC messages which are control information. DRB may be used as a path for transmitting user data. The settings of each RB may be performed between RRC208 of eNB102 and UE122. Also, the part of RB composed of RLC204 and logical channels may be referred to as RLC bearer. Also, for the NAS layer that carries signals between MME and UE122, some or all of the layers of PHY200, MAC202, RLC204, PDCP206, RRC208 that carry signals and data between UE122 and eNB102 may be referred to as AS (Access Strarum) layer (AS layer).

[0033] The above - mentioned functional classification of MAC202, RLC204, PDCP206, and RRC208 is an example, and some or all of each function may not be implemented. Also, some or all of the functions of each layer may be included in other layers.

[0034] Note that the IP layer, and the TCP (Transmission Control Protocol) layer (TCP layer), UDP (User Datagram Protocol) layer (UDP layer), application layer (application layer), etc. above the IP layer are the upper layers (upper layers) of the PDCP layer (not shown). Also, the RRC layer and NAS (non-Access Stratum) layer are also the upper layers of the PDCP layer (not shown). In other words, the PDCP layer is the lower layer (lower layer) of the RRC layer, NAS layer, IP layer, and the TCP (Transmission Control Protocol) layer, UDP (User Datagram Protocol) layer, and application layer above the IP layer.

[0035] Figure 3 is a protocol stack diagram of the UP and CP of the terminal device and the base station device in the NR radio access layer in each embodiment of the present invention.

[0036] Figure 3(A) is a protocol stack diagram of the UP used when UE122 communicates with gNB108 in NR106.

[0037] PHY (Physical layer) 300 is the radio physical layer of NR (radio physical layer), and may provide a transmission service to the upper layer using a physical channel. PHY 300 may be connected to the upper MAC (Medium Access Control layer) 302 described later via a transport channel. Data may move between MAC 302 and PHY 300 via the transport channel. Data transmission and reception may be performed via a radio physical channel between the PHYs of UE122 and gNB108.

[0038] Here, the physical channel will be described.

[0039] In the wireless communication between the terminal device and the base station device, the following physical channels may be used.

[0040] 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)

[0041] PBCH is used to notify the system information required by the terminal device.

[0042] Also, in NR, PBCH may be used to notify the time index (SSB-Index) within the period of the synchronization signal block (also referred to as SS / PBCH block).

[0043] The PDCCH is used to transmit (or carry) downlink control information (DCI) in downlink wireless communication (wireless communication from a base station device to a terminal device). Here, one or more DCIs (which may also be referred to as DCI formats) are defined for the transmission of downlink control information. That is, the fields for downlink control information are defined as DCIs and mapped to information bits. The PDCCH is transmitted in PDCCH candidates. The terminal device monitors a set of PDCCH candidates in the serving cell. Monitoring means attempting to decode the PDCCH according to a certain DCI format. A certain DCI format may be used for the scheduling of PUSCH in the serving cell. The PUSCH may be used for the transmission of user data, the transmission of RRC messages, etc.

[0044] The PUCCH may be used to transmit uplink control information (UCI) in uplink wireless communication (wireless communication from a terminal device to a base station device). Here, the uplink control information may include channel state information (CSI) used to indicate the state of a downlink channel. Also, the uplink control information may include a scheduling request (SR) used to request UL-SCH resources. Also, the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement).

[0045] The PDSCH may be used for transmitting downlink data (DL-SCH: Downlink Shared Channel) from the MAC layer. Also, in the case of downlink, it may also be used for transmitting system information (SI: System Information), random access response (RAR: Random Access Response), etc.

[0046] The PUSCH may be used for transmitting uplink data (UL-SCH: Uplink Shared Channel) from the MAC layer or for transmitting HARQ-ACK and / or CSI together with the uplink data. Also, the PUSCH may be used for transmitting only CSI, or only HARQ-ACK and CSI. That is, the PUSCH may be used for transmitting only UCI. Also, the PDSCH or PUSCH may be used for transmitting RRC signaling (also referred to as an RRC message) and MAC control elements (MAC CE). Here, in the PDSCH, the RRC signaling transmitted from the base station apparatus may be common signaling for a plurality of terminal apparatuses within a cell. Also, the RRC signaling transmitted from the base station apparatus may be dedicated signaling (also referred to as dedicated signaling) for a certain terminal apparatus. That is, UE-specific information may be transmitted using dedicated signaling for a certain terminal apparatus. Also, the PUSCH may be used for transmitting the capabilities of the UE (UE Capability) in the uplink.

[0047] The PRACH may be used for transmitting a random access preamble. The PRACH may be used for an initial connection establishment procedure, a handover procedure, a connection re-establishment procedure, synchronization for uplink transmission (timing adjustment), and for indicating a request for PUSCH (UL-SCH) resources.

[0048] MAC302 is a media access control layer (media access control layer) that maps various logical channels to various transport channels. MAC302 may be connected to the upper RLC (Radio Link Control layer) 304 described later via a logical channel. Logical channels can be broadly classified according to the type of information to be transmitted, and may be divided into a control channel for transmitting control information and a traffic channel for transmitting user information. MAC302 may have functions such as controlling the PHY300 for performing discontinuous reception / transmission (DRX / DTX), executing a random access procedure, notifying transmission power information, and performing HARQ control. In addition, MAC302 may have a function of controlling the active state of the cell set by the RRC layer (Non-Patent Document 7).

[0049] RLC304 is a radio link control layer (radio link control layer) that segments the data received from the upper PDCP (Packet Data Convergence Protocol Layer) 306 described later and adjusts the data size so that the lower layer can appropriately transmit the data.

[0050] PDCP306 is a packet data convergence protocol layer (packet data convergence protocol layer) that efficiently transmits user data such as IP packets (IP Packets) in the radio section. PDCP306 may have a header compression function for compressing unnecessary control information. In addition, PDCP306 may also have functions of encrypting data and protecting data integrity.

[0051] The SDAP (Service Data Adaptation Protocol) 310 is a service data adaptation protocol layer that performs the mapping of downlink QoS flows and DRBs sent from the 5GC 110 to the terminal device via the base station device, and the mapping of uplink QoS flows and DRBs sent from the terminal device to the 5GC 110 via the base station device, and stores mapping rule information.

[0052] Note that the data processed in MAC 302, RLC 304, PDCP 306, and SDAP 310 are called MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Also, the data passed from the upper layer to MAC 302, RLC 304, PDCP 306, and SDAP 310, or the data passed to the upper layer are called MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. Also, the segmented RLC SDU is called an RLC SDU segment.

[0053] Figure 3(B) is a protocol stack diagram of the CP used when the UE 122 communicates with the gNB 108 and the AMF (Access and Mobility Management function), which is a logical node that provides functions such as authentication and mobility management, in NR 106.

[0054] In the protocol stack of the CP, in addition to the PHY300, MAC302, RLC304, PDCP306, there are also the RRC (Radio Resource Control layer) 308 and the NAS (non-Access Strarum) 312. The RRC308 performs processes such as the establishment, re-establishment, suspension, and resume of the RRC connection, as well as the reconfiguration of the RRC connection, for example, the establishment, change, and release of radio bearers (RBs) and cell groups. It also controls logical channels, transport channels, and physical channels, and performs settings for handover and measurement. It is a radio link control layer. The RB may be divided into a signaling radio bearer (SRB) and a data radio bearer (DRB). The SRB may be used as a path for transmitting RRC messages, which are control information. The DRB may be used as a path for transmitting user data. The settings of each RB may be performed between the RRC308 of the gNB108 and the UE122. Also, the part of the RB composed of the RLC304 and the logical channel may be referred to as the RLC bearer. Also, for the NAS layer that carries signals between the AMF and the UE122, some or all of the layers of the PHY300, MAC302, RLC304, PDCP306, RRC308, and SDAP310 that carry signals and data between the UE122 and the gNB108 may be referred to as the AS (Access Strarum) layer.

[0055] The above functional classification of the MAC302, RLC304, PDCP306, SDAP310, and RRC308 is just an example, and some or all of each function may not be implemented. Also, some or all of the functions of each layer may be included in other layers.

[0056] Note that the upper layer of the AS layer (not shown) may also be referred to as the PDU layer (PDU layer) as described in Non-Patent Document 2. The PDU layer may include any one or all of the IP layer, the TCP (Transmission Control Protocol) layer above the IP layer, the UDP (User Datagram Protocol) layer, and other layers. The application layer may be the upper layer of the PDU layer or may be included in the PDU layer. Note that the PDU layer may be the upper layer with respect to the user plane of the AS layer. Also, the RRC layer and the NAS (non-Access Strarum) layer may also be the upper layer of any one or all of the SDAP layer and the PDCP layer (not shown). In other words, any one or all of the SDAP layer and the PDCP layer may be the lower layer of any one or all of the RRC layer, the NAS layer, the IP layer, the TCP (Transmission Control Protocol) layer above the IP layer, the UDP (User Datagram Protocol) layer, and the application layer.

[0057] Note that the physical layer, MAC layer, RLC layer, PDCP layer, and SDAP layer of the terminal device may be established, set, and / or controlled in any one or all by the RRC layer of the terminal device. Also, the RRC layer of the terminal device may establish and / or set the physical layer, MAC layer, RLC layer, PDCP layer, and SDAP layer according to the RRC message transmitted from the RRC layer of the base station device. Also, the MAC layer (MAC layer), RLC layer (RLC layer), PDCP layer (PDCP layer), and SDAP layer (SDAP layer) may be referred to as the MAC sublayer (MAC sublayer), RLC sublayer (RLC sublayer), PDCP sublayer (PDCP sublayer), and SDAP sublayer (SDAP sublayer), respectively.

[0058] Each layer belonging to the AS layer or the functions of each layer set in any one or all of the terminal device and the base station device may also be referred to as an entity. That is, in any one or all of the terminal device and the base station device, the physical layer (PHY layer), MAC layer, RLC layer, PDCP layer, SDAP layer, and RRC layer in which any or all of establishment, setting, and control are performed, or the functions of each layer, may be referred to as a physical entity (PHY entity), MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity, respectively. Also, each layer may include one or more entities of each layer. Also, the PDCP entity and the RLC entity may perform any or all of establishment, setting, and control for each radio bearer. Also, the MAC entity may perform any or all of establishment, setting, and control for each cell group. Also, the SDAP entity may perform any or all of establishment, setting, and control for each PDU session.

[0059] Note that in each embodiment of the present invention, in order to distinguish the following E-UTRA protocol from the NR protocol, MAC202, RLC204, PDCP206, and RRC208 may also be referred to as MAC for E-UTRA or MAC for LTE, RLC for E-UTRA or RLC for LTE, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE, respectively. Also, MAC302, RLC304, PDCP306, and RRC308 may also be referred to as MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively. Or, it may also be described using a space such as E-UTRA PDCP or LTE PDCP, NR PDCP, etc.

[0060] Also, as shown in FIG. 1, eNB 102, gNB 108, EPC 104, and 5GC 110 may be connected via interface 112, interface 116, interface 118, interface 120, and interface 114. Therefore, to support various communication systems, RRC 208 in FIG. 2 may be replaced by RRC 308 in FIG. 3. Also, PDCP 206 in FIG. 2 may be replaced by PDCP 306 in FIG. 3. Further, RRC 308 in FIG. 3 may include the functions of RRC 208 in FIG. 2. Also, PDCP 306 in FIG. 3 may be PDCP 206 in FIG. 2. Also, in E-UTRA 100, even when UE 122 communicates with eNB 102, NR PDCP may be used as PDCP.

[0061] Next, the state transition of UE 122 in LTE and NR will be described. UE 122 connected to EPC or 5GC may be in the RRC_CONNECTED state when the RRC connection has been established. The state where the RRC connection has been established may include a state where UE 122 holds some or all of the UE context described later. Also, the state where the RRC connection has been established may include a state where UE 122 can transmit and / or receive unicast data. Also, UE 122 may be in the RRC_INACTIVE state when the RRC connection is suspended (if UE 122 is connected to 5GC). If not in those cases, UE 122 may be in the RRC_IDLE state.

[0062] Note that the UE 122 connected to the EPC does not have the RRC_INACTIVE state, but the suspension of the RRC connection may be initiated by the E-UTRAN. In this case, when the RRC connection is suspended, the UE 122 retains the UE's AS context and an identifier (resumeIdentity) used for resumption and transitions to the RRC_IDLE state. When the UE 122 retains the UE's AS context, and the resumption of the RRC connection is permitted by the E-UTRAN, and the UE 122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state, the resumption of the suspended RRC connection may be initiated by a higher layer (e.g., the NAS layer).

[0063] That is, the definition of suspension may be different between the UE 122 connected to the EPC and the UE 122 connected to the 5GC. Also, all or part of the procedures for the UE 122 to resume from suspension may be different between the case where the UE 122 is connected to the EPC (when suspended in the RRC_IDLE state) and the case where the UE 122 is connected to the 5GC (when suspended in the RRC_INACTIVE state).

[0064] Note that the states of RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE may be referred to as the connected mode, inactive mode, and idle mode, respectively, or as the RRC connected mode, RRC inactive mode, and RRC idle mode.

[0065] The AS context of the UE held by UE122 may be information including all or part of the current RRC configuration, the current security context, the PDCP state including the ROHC (RObust Header Compression) state, the C-RNTI (Cell Radio Network Temporary Identifier) used in the source PCell, the cell identity, and the physical cell identifier of the source PCell. Note that 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 may include information different from the information included in the AS context of the UE held by UE122.

[0066] FIG. 4 is a diagram showing an example of a flow of procedures for various settings in RRC208 and / or RRC308 in each embodiment of the present invention. FIG. 4 is an example of a flow when an RRC message is sent from a base station device (eNB102 and / or gNB108) to a terminal device (UE122).

[0067] In FIG. 4, the base station device creates an RRC message (step S400). The creation of the RRC message in the base station device may be performed when the base station device distributes system information (SI) or paging information, or when the base station device determines that it is necessary to cause a specific terminal device to perform processing. For example, when performing settings related to security, reconfiguration of the RRC connection (processing of radio bearers (establishment, change, release, etc.), processing of cell groups (establishment, addition, change, release, etc.), measurement settings, handover settings, etc.), or release of the RRC connection state. The RRC message contains information (parameters) for various information notifications and settings. In the specifications regarding RRC (Non-Patent Document 8, Non-Patent Document 9), these parameters are called fields and / or information elements and are described using a description method called ASN.1 (Abstract Syntax Notation One).

[0068] The RRC message may be created for other purposes. For example, the RRC message may be used for settings related to Dual Connectivity (DC) or Multi-Radio Dual Connectivity (MR-DC).

[0069] In FIG. 4, next, the base station device transmits the created RRC message to the terminal device (step S402). Next, if processing such as setting is required according to the received RRC message, the terminal device performs the processing (step S404).

[0070] Dual Connectivity (DC) may be a technology that performs data communication using the radio resources of both cell groups configured by two base station devices (nodes), namely, the master cell group (MCG) configured by the master node (MN) and the secondary cell group (SCG) configured by the secondary node (SN). Also, the master node and the secondary node may be the same node (the same base station device). Further, MR-DC may be a technology that groups cells of both RATs (Radio Access Technology) of E-UTRA and NR into cell groups for each RAT and assigns them to the UE, and performs data communication using the radio resources of both MCG and SCG. In MR-DC, the master node may be a base station having main RRC functions related to MR-DC, for example, functions such as addition of a secondary node, establishment, change, and release of RBs, addition, change, release, handover, etc. of MCG, and the secondary node may be a base station having some RRC functions, for example, functions such as change and release of SCG.

[0071] In MR-DC, the RRC of the RAT on the master node side may be used to configure both MCG and SCG. For example, in EN-DC (E-UTRA-NR Dual Connectivity), which is a type of MR-DC where the core network is EPC104 and the master node is eNB102 (also referred to as an enhanced eNB102), or in NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity), which is a type of MR-DC where the core network is 5GC110 and the master node is eNB102, the RRC message of E-UTRA may be transmitted and received between eNB102 and UE122. In this case, the RRC message may include not only the configuration information of LTE (E-UTRA) but also the configuration information of NR. Also, the RRC message transmitted from eNB102 to UE122 may be transmitted to UE122 via gNB108 from eNB102. Further, the configuration of this RRC message may be used in E-UTRA / 5GC where eNB102 (enhanced eNB) uses 5GC as the core network and is not MR-DC.

[0072] Conversely, in MR-DC, in NE-DC (NR-E-UTRA Dual Connectivity), which is a type of MR-DC where the core network is 5GC110 and the master node is gNB108, the RRC message of NR may be transmitted and received between gNB108 and UE122. In this case, the RRC message may include not only the configuration information of NR but also the configuration information of LTE (E-UTRA). Also, the RRC message transmitted from gNB108 to UE122 may be transmitted to UE122 via eNB102 from gNB108.

[0073] Note that not only when using MR-DC, the RRC message for E-UTRA transmitted from eNB102 to UE122 may include the RRC message for NR, or the RRC message for NR transmitted from gNB108 to UE122 may include the RRC message for E-UTRA.

[0074] FIG. 7 is an example of an ASN.1 description representing some or all of the fields and information elements related to cell group configuration included in the message regarding RRC connection reconfiguration in NR in FIG. 4. FIG. 8 is an example of an ASN.1 description representing some or all of the fields and information elements related to cell group configuration included in the message regarding RRC connection reconfiguration in E-UTRA in FIG. 4. Not limited to FIGS. 7 and 8, in the example of ASN.1 in the embodiment of the present invention, <abbreviation> and <omitted> do not represent a part of the ASN.1 notation, but indicate that other information is omitted. Even where there is no description of <abbreviation> or <omitted>, information elements may be omitted. Note that the example of ASN.1 in the embodiment of the present invention does not correctly follow the ASN.1 notation method, but represents an example of the parameters of the message regarding RRC connection reconfiguration in the embodiment of the present invention, and other names and other notations may be used. Also, the example of ASN.1 shows only an example related to the main information closely related to one form of the present invention in order to avoid complicated explanations. Note that the parameters described in ASN.1 may be referred to as information elements without distinguishing them into fields, information elements, etc. Also, in the embodiment of the present invention, the parameters of the fields, information elements, etc. described in ASN.1 included in the RRC message may be referred to as information. Note that the message regarding RRC connection reconfiguration may be an RRC reconfiguration message in NR or an RRC connection reconfiguration message in E-UTRA.

[0075] In FIG. 7, the radioBearerConfig included in the RRCReconfiguration message may include the configuration of radio bearers. The masterCellGroup may include the configuration regarding the MCG when the MCG is NR. The secondaryCellGroup may include the configuration regarding the SCG when notified from the cells of the SCG to the terminal device. The mrdc-SecondaryCellGroupConfig may include the configuration regarding the SCG when notified from the cells of the MCG to the terminal device.

[0076] The above masterCellGroup, secondaryCellGroup, and / or mrdc-SecondaryCellGroupConfig may include a CellGroupConfig information element as a value.

[0077] The CellGroupConfig information element may include settings related to the cell group. The cellGroupId included in the CellGroupConfig information element may include information on an identifier for identifying the cell group. The mac-CellGroupConfig may include settings related to the MAC layer of the cell group. The spCellConfig may include settings related to the SpCell. The sCellToAddModList may include settings related to the addition or modification of SCell belonging to the cell group. The sCellToReleaseList may include information related to the deletion of SCell belonging to the cell group.

[0078] In FIG. 8, the sCellToReleaseList-r10 included in the RRCConnectionReconfiguration message may include information regarding the deletion of SCell belonging to MCG. The sCellToAddModList-r10 may include settings regarding the addition or modification of SCell belonging to MCG. The scg-Configuration-r12 may include settings regarding SCG. The scg-ConfigPartSCG-r12 included in the scg-Configuration-r12 may include settings regarding the SpCell of SCG (such as pSCellToAddMod-r12), settings regarding the addition or modification of SCell belonging to the cell group (such as sCellToAddModListSCG-r12), and / or information regarding the deletion of SCell belonging to the cell group (such as sCellToReleaseListSCG-r12). Also, information indicating the initial state of the SCell may be included in the settings regarding the addition or modification of SCell during handover and / or the settings regarding the addition or modification of SCell when adding an SCell. For example, information indicating either the activated state or the dormant state may be included in the RRC message. When this information is included, the initial state of the SCell may be set to the activated state or the dormant state based on this information. When this information is not included, the initial state of the SCell may be set to the deactivated state.

[0079] Note that each of the above fields and information elements may not be limited to the above uses.

[0080] The terminal device that has received the RRC message including the above information performs the settings of the SpCell (PCell) of MCG, the SCell of MCG, the SpCell (PSCell) of SCG, and / or the SCell of SCG based on the information.

[0081] The terminal device may perform radio link monitoring using a certain type of reference signal (e.g., cell-specific reference signal (CRS)) in the serving cell (e.g., PCell and / or PSCell). Also, the terminal device may receive from the base station device a setting (radio link monitoring setting: RadioLinkMonitoringConfig) indicating which reference signal to use for radio link monitoring in the serving cell (e.g., PCell and / or PSCell), and perform radio link monitoring using the set one or more reference signals (referred to as RLM-RS here). Further, the terminal device may perform radio link monitoring using other signals. The physical layer processing unit of the terminal device may notify the upper layer that it is in synchronization when the conditions for being in synchronization in the serving cell (e.g., PCell and / or PSCell) are met.

[0082] The radio link monitoring setting may include information indicating the purpose of monitoring and identifier information indicating the reference signal. For example, the purpose of monitoring may include the purpose of monitoring radio link failure, the purpose of monitoring beam failure, or both purposes, etc. Also, for example, the identifier information indicating the reference signal may include information indicating the identifier (SSB-Index) of the synchronization signal block (SSB) of the cell. That is, the reference signal may include a synchronization signal. Also, for example, the identifier information indicating the reference signal may include information indicating the identifier associated with the channel state information reference signal (CSI-RS) set for the terminal device.

[0083] In a SpCell (PCell in MCG and PSCell in SCG), when the RRC layer processing unit of the terminal device continuously receives out-of-synchronization notified by the physical layer processing unit in each SpCell for a default number of times (N310 times), it may start (Start) or restart (Restart) the timer (T310) of the SpCell. Also, when the RRC layer processing unit of the terminal device continuously receives in-synchronization in each SpCell for a default number of times (N311 times), it may stop (Stop) the timer (T310) of the SpCell. When the timer (T310) of each SpCell expires, if the SpCell is a PCell, the RRC layer processing unit of the terminal device may perform a transition to the idle state or an RRC connection re-establishment procedure. Also, if the SpCell is a PSCell, it may execute an SCG failure information procedure for notifying the network of an SCG failure.

[0084] The above description is an example when discontinuous reception (DRX) is not set in the terminal device. When DRX is set in the terminal device, the RRC layer processing unit of the terminal device may set the physical layer processing unit so that the period for measuring the radio link quality and the notification interval to the upper layer take different values from those when DRX is not set. Note that even when DRX is set, when the above timer is running, the period for measuring the radio link quality for estimating in-synchronization and the notification interval to the upper layer may be set to the values when DRX is not set.

[0085] Also, the RLM-RS may be undefined when it is not set by the network explicitly or implicitly. That is, the terminal device may not perform radio link monitoring when the RLM-RS is not set by the network (for example, the base station device).

[0086] Also, radio link monitoring using CRS may be performed in a cell of EUTRA, and radio link monitoring using RLM-RS may be performed in a cell of NR, but it is not limited to this.

[0087] Describe the activation and deactivation of cells. The terminal device communicating with dual connectivity has the master cell group (MCG) and the secondary cell group (SCG) configured by the message regarding the reconfiguration of the aforementioned RRC connection. Each cell group may be composed of a special cell (SpCell) and zero or more other cells (secondary cells: SCell). The SpCell of the MCG is also referred to as the PCell. The SpCell of the SCG is also referred to as the PSCell. The deactivation of a cell is not applied to the SpCell and may be applied to the SCell.

[0088] Also, the deactivation of a cell is not applied to the PCell and may be applied to the PSCell. In this case, the deactivation of a cell may be different processing for the SpCell and the SCell.

[0089] As shown in Non-Patent Document 6 and Non-Patent Document 7, the activation and deactivation of cells may be processed by the MAC entity existing for each cell group. The SCell set in the terminal device may be activated and / or deactivated by the following (A) and / or (B). (A) Reception of a MAC CE indicating SCell activation / deactivation (B) A timer (sCellDeactivationTimer) set for each SCell for which PUCCH is not set

[0090] Specifically, the terminal device may perform the following processing (AD) on each SCell for which the MAC entity is set in the cell group.

[0091] (Processing AD) If a MAC CE for activating the SCell is received, perform process (AD-1). Otherwise, if a MAC CE for deactivating the SCell is received, or if the timer (sCellDeactivationTimer) expires in the active SCell, perform process (AD-2). If an uplink grant or a downlink allocation is notified by the PDCCH of the active SCell, or if an uplink grant or a downlink allocation for the active SCell is notified by the PDCCH of a serving cell, or if a MAC PDU is transmitted in the set uplink grant, or if a MAC PDU is received in the set downlink allocation, restart the timer (sCellDeactivationTimer) associated with that SCell. If the SCell becomes inactive, perform process (AD-3).

[0092] (Process AD-1)

[0093] Set the SCell to the active state and apply (perform) normal SCell operations (Operation) including some or all of the following (A) to (E). (A) Transmission of sounding reference signal (SRS) in this SCell (B) Reporting of channel state information (CSI) for this SCell (C) Monitoring of PDCCH in this SCell (D) Monitoring of PDCCH for this SCell (when scheduling for this SCell is performed in another serving cell) (E) If PUCCH is configured, PUCCH transmission in this SCell

[0094] Also, if in NR, this SCell was in the inactive state before receiving this MAC CE for activation, perform some or all of the following (A) to (B). Activate the BWP indicated by the identifier (firstActiveDownlinkBWP-Id) of the downlink BWP configured in the RRC message. Activate the BWP indicated by the identifier (firstActiveUplinkBWP-Id) of the uplink BWP configured in the RRC message.

[0095] Also, start or (if already started) restart the timer (sCellDeactivationTimer) associated with this SCell.

[0096] (Procedure AD-2)

[0097] Deactivate this SCell.

[0098] Also, stop the timer (sCellDeactivationTimer) associated with this SCell.

[0099] Deactivate all activated BWPs associated with this SCell.

[0100] Flush the HARQ buffer associated with this SCell.

[0101] (Procedure AD-3) Perform some or all of the following (A) to (D). (A) Do not transmit SRS on this SCell. (B) Do not report CSI for this SCell. (C) Do not transmit PUCCH, UL-SCH, and / or RACH on this SCell. (D) Do not monitor the PDCCH of this SCell and / or the PDCCH for this SCell.

[0102] As described above, by the MAC entity performing procedure (AD), activation and deactivation of the SCell are performed.

[0103] Also, when an SCell is added as described above, the initial state of the SCell may be set by an RRC message.

[0104] Here, the timer (sCellDeactivationTimer) will be described. For an SCell where PUCCH is not configured, the value of the timer (sCellDeactivationTimer) (information regarding the time when the timer is considered to have expired) may be notified by an RRC message. For example, when information indicating 40 ms is notified as the value of the timer (sCellDeactivationTimer) in an RRC message, in the above process (AD), when the time (here, 40 ms) notified without the timer stopping after starting or restarting the timer has elapsed, the timer is considered to have expired.

[0105] Here, the bandwidth part (BWP) will be described.

[0106] The BWP may be part or all of the bandwidth of the serving cell. Also, the BWP may be referred to as a Carrier BWP. One or more BWPs may be configured for the terminal device. A certain BWP may be configured by information included in the notification information associated with the synchronization signal detected in the initial cell search. Also, a certain BWP may be the frequency bandwidth associated with the frequency at which the initial cell search is performed. Also, a certain BWP may be configured by RRC signaling (e.g., Dedicated RRC signaling). Also, the downlink BWP (DL BWP) and the uplink BWP (UL BWP) may be configured separately. Also, one or more uplink BWPs may be associated with one or more downlink BWPs. Also, the association between the uplink BWP and the downlink BWP may be a default association, or may be an association by RRC signaling (e.g., Dedicated RRC signaling), or may be an association by physical layer signaling (e.g., association by downlink control information (DCI) notified on the downlink control channel), or may be a combination thereof.

[0107] A BWP may be composed of a group of consecutive Physical Resource Blocks (PRBs). Also, for a terminal device in the connected state, parameters of the BWP (one or more BWPs) of each component carrier may be set. The parameters of the BWP of each component carrier may include some or all of the following: (A) the type of cyclic prefix, (B) the subcarrier spacing, (C) the frequency position of the BWP (for example, the start position on the low-frequency side or the center frequency position of the BWP) (the frequency position may use, for example, an ARFCN, or an offset from a specific subcarrier of the serving cell may be used. Also, the unit of the offset may be in subcarrier units or resource block units. Also, both the ARFCN and the offset may be set.), (D) the bandwidth of the BWP (for example, the number of PRBs), (E) resource setting information of the control signal, (F) the center frequency position of the SS block (the frequency position may use, for example, an ARFCN, or an offset from a specific subcarrier of the serving cell may be used. Also, the unit of the offset may be in subcarrier units or resource block units. Also, both the ARFCN and the offset may be set.). Also, the resource setting information of the control signal may be included in the setting of at least a part or all of the BWP of the PCell and / or PSCell.

[0108] The terminal device may perform transmission and reception in the active BWP (Active BWP) among one or more set BWPs. For the terminal device, among one or more BWPs set for one serving cell, at a certain time, it may be set such that at most one uplink BWP and / or at most one downlink BWP become the active BWP. The activated downlink BWP is also referred to as the Acitve DL BWP. The activated uplink BWP is also referred to as the Active UL BWP.

[0109] Next, the inactivation of the BWP will be described. One serving cell may have one or more BWPs configured. BWP switching in a serving cell is used to activate an inactivated BWP (also referred to as an Inactive BWP) and inactivate the previously activated BWP.

[0110] BWP switching is controlled by the MAC entity itself for the start of a PDCCH indicating a downlink assignment or an uplink grant, a timer (bwp-InactivityTimer), RRC signaling, or a random access procedure. The Active BWP of a serving cell is indicated by the RRC or the PDCCH.

[0111] Next, the Dormant BWP will be described. Entering or Leaving the Dormant BWP is done by BWP switching. This control is performed by the PDCCH for each SCell or for each group called the Dormancy SCell Group. The configuration of the Dormancy SCell Group is indicated by RRC signaling. Also, in the current specification, the Dormant BWP is only applicable to SCell. Note that the Dormant BWP does not change a certain BWP to a dormant state, but may be interpreted as one of the one or more BWPs configured for the UE for dormancy. Also, there may be multiple BWPs configured for the UE for dormancy.

[0112] That a certain BWP is a dormant BWP may be indicated by the fact that specific parameters are not included in the BWP configuration. For example, that a certain BWP is a dormant BWP may be indicated by the fact that the PDCCH-Config information element, which is an information element for setting UE-specific PDCCH parameters included in the downlink BWP configuration, is not included. Also, for example, that a certain BWP is a dormant BWP may be indicated by the fact that some of the parameters included in the PDCCH-Config information element, which is an information element for setting UE-specific PDCCH parameters included in the downlink BWP configuration, are not set (not included). For example, as a configuration of a certain BWP, that a certain BWP is a dormant BWP may be indicated by the fact that some or all of the configuration regarding the search space that defines where and / or how to search for PDCCH candidates, which is set by the PDCCH-Config information element, is not set (not included).

[0113] Also, in the current specification, the setting of a dormant BWP to a PUCCH SCell where transmission of SpCell such as PCell and PSCell and PUCCH can be performed is not supported.

[0114] A UE that receives a PDCCH indicating exit from a dormant BWP outside a certain set period (active time) on the SpCell activates the downlink BWP indicated by the first downlink BWP identifier notified in advance by RRC signaling.

[0115] A UE that receives a PDCCH indicating exit from a dormant BWP within a certain set period (active time) on the SpCell activates the downlink BWP indicated by the second downlink BWP identifier notified in advance by RRC signaling.

[0116] Upon receiving a PDCCH indicating entry into a dormant BWP, the UE activates the downlink BWP indicated by a third downlink BWP identifier (dormantDownlinkBWP-Id) notified in advance by RRC signaling.

[0117] Entry into and exit from the above-mentioned dormant BWP are performed by BWP switching. When activating a new BWP, the BWP that was active until then is deactivated. That is, when exiting the dormant BWP, the dormant BWP is deactivated, and when entering the dormant BWP, the dormant BWP is activated.

[0118] Here, the PDCCH indicating entry into the dormant BWP and the PDCCH indicating exit from the dormant BWP will be described.

[0119] For example, a UE with discontinuous reception (DRX) configured in the SpCell may monitor the PDCCH in the Active BWP of the SpCell to detect a certain DCI format (e.g., DCI format 2_6) outside the active time of DRX. The CRC of the said DCI format may be scrambled with a certain RNTI (e.g., PS-RNTI). A UE with a dormant SCell group configured determines the switching of the Active DL BWP based on the bitmap information included in the payload of DCI format 2_6. For example, a certain bit of the bitmap is associated with one dormant SCell group. If the bit is 1 and the Active DL BWP is the dormant BWP, BWP switching may be executed to another pre-configured BWP, and if the Active DL BWP is not the dormant BWP, it may remain in that BWP. Also, if the bit is 0, BWP switching may be executed so that the Active DL BWP becomes the dormant BWP.

[0120] The UE does not have to monitor the PDCCH for the purpose of detecting DCI format 2_6 during the active time of DRX.

[0121] For a UE with discontinuous reception (DRX) configured in the SpCell, during the active time of DRX, it may monitor the PDCCH in the Active BWP of the SpCell to detect a certain DCI format (e.g., DCI format 0_1 and 1_1). The CRC of the said DCI format may be scrambled with a certain RNTI (e.g., C-RNTI or MCS-C-RNTI). For a UE with a dormant SCell group configured, it determines the switching of the Active DL BWP based on the bitmap information included in the payload of DCI format 0_1 or DCI format 1_1. For example, a certain bit of the bitmap is associated with a dormant SCell group. When the bit is 1, if the Active DL BWP is the dormant BWP, it may perform a BWP switch to another pre-configured BWP, and if the Active DL BWP is not the dormant BWP, it may stay in that BWP. Also, when the bit is 0, it may perform a BWP switch so that the Active DL BWP becomes the dormant BWP. Also, the "another pre-configured BWP" may be a BWP different from the "another pre-configured BWP" used in the description of DCI format 2_6.

[0122] Outside the active time of DRX, the UE may not monitor the PDCCH for the purpose of detecting DCI format 0_1 and DCI format 1_1.

[0123] Monitoring the PDCCH indicating exiting the dormant BWP may mean monitoring the PDCCH for the purpose of detecting DCI format 2_6 outside the active time of DRX and monitoring the PDCCH for the purpose of detecting DCI format 0_1 and DCI format 1_1 during the active time of DRX.

[0124] In each activated serving cell where a BWP is configured, if the BWP is activated (is an Active BWP) and is not a dormant BWP, the MAC entity performs some or all of the following (A) to (H). (A) Transmit UL-SCH on that BWP. (B) If a PRACH occasion is configured, transmit RACH on that BWP. (C) Monitor PDCCH on that BWP. (D) If PUCCH is configured, transmit PUCCH on that BWP. (E) Report CSI on that BWP. (F) If SRS is configured, transmit SRS on that BWP. (G) Receive DL-SCH on that BWP. (H) Initialize the configured grant type 1 uplink grant that is configured and suspended on that BWP.

[0125] In each activated serving cell where a BWP is configured, if the BWP is activated (is an Active BWP) and is a dormant BWP, the MAC entity performs some or all of the following (A) to (G). (A) Stop the timer (bwp-InactivityTimer) of the serving cell of this BWP if it is running. (B) Do not monitor the PDCCH of that BWP. (C) Do not monitor the PDCCH for that BWP. (D) Do not receive DL-SCH on that BWP. (E) If CSI measurement is configured, perform CSI measurement on that BWP. (F) Stop all uplink behavior. That is, stop uplink transmission, suspend the configured grant type 1 uplink grant associated with that cell, and clear the configured grant type 2 uplink grant associated with that cell. (G) If the setting for beam failure is configured, detect beam failure, and if beam failure is detected, execute beam failure recovery.

[0126] If the BWP is deactivated, the MAC entity performs some or all of the following (A) to (I). (A) Do not transmit UL-SCH on that BWP. (B) Do not transmit RACH on that BWP. (C) Do not monitor PDCCH on that BWP. (D) Do not transmit PUCCH on that BWP. (E) Do not report CSI on that BWP. (F) Do not transmit SRS on that BWP. (G) Do not receive DL-SCH on that BWP. (H) Clear the configured grant type 2 configured uplink grant set for that BWP. (I) Suspend the configured grant type 1 configured uplink grant of that deactivated BWP (inactive BWP).

[0127] Next, the random access procedure in a UE with a configured BWP will be described. When starting a random access procedure in a serving cell, the MAC entity performs some or all of the following (A) to (E) in the selected carrier of this serving cell. (A) If the resource (occasion) for transmitting PRACH is not configured for the Active UL BWP, (A1) switch the Active UL BWP to the BWP indicated by the RRC parameter (initialUplinkBWP), and (A2) if the serving cell is a SpCell, switch the Active UL BWP to the BWP indicated by the RRC parameter (initialDownlinkBWP). (B) If the resource (occasion) for transmitting the PRACH is configured for the Active UL BWP, and if the serving cell is the SpCell and the Active DL BWP and the Active UL BWP do not have the same identifier (bwp-Id), then switch the Active DL BWP to the BWP with the same identifier as that of the Active UL BWP. (C) If the timer (bwp-InactivityTimer) associated with the Active DL BWP of this serving cell is running, then stop this timer. (D) If the serving cell is an SCell, and if the timer (bwp-InactivityTimer) associated with the Active DL BWP of the SpCell is running, then stop this timer. (E) Execute the random access procedure on the Active DL BWP of the SpCell and the Active UL BWP of this serving cell.

[0128] Next, the timer (bwp-InactivityTimer) will be described. For each Activated Serving Cell for which the timer (bwp-InactivityTimer) is configured, the MAC entity performs the following process (A). (A) If the identifier of the default downlink BWP (defaultDownlinkBWP-Id) is configured and the Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), or if the identifier of the default downlink BWP (defaultDownlinkBWP-Id) is not configured, the Active DL BWP is not the initialDownlinkBWP, and the Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), then perform the following processes (B) and (D). (B) If a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink assignment or an uplink grant is received in the Active DL BWP, or if a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink assignment or an uplink grant for the Active DL BWP is received, or if a MAC PDU is transmitted with a configured uplink grant or a MAC PDU is received with a configured downlink assignment, then perform the following processing in (C). (C) If the random access procedure associated with this serving cell is not in progress, or if the ongoing random access procedure associated with this serving cell has been successfully completed by receiving a PDCCH addressed to the C-RNTI, then start or restart the bwp-InactivityTimer associated with the Active DL BWP. (D) If the bwp-InactivityTimer associated with the Active DL BWP has expired, then perform the following processing in (E). (E) If the defaultDownlinkBWP-Id is set, perform a BWP switch to the BWP indicated by this defaultDownlinkBWP-Id; otherwise, perform a BWP switch to the initialDownlinkBWP.

[0129] Also, if the MAC entity receives a PDCCH for BWP switching and switches the Active DL BWP, then perform the following processing in (A). (A) If the identifier of the default downlink BWP (defaultDownlinkBWP-Id) is set and the switched Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), and if the switched Active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id, then start or restart the bwp-InactivityTimer associated with the Active DL BWP.

[0130] Next, the procedures for beam failure detection and recovery will be described.

[0131] The MAC entity may have the beam failure recovery procedure set by the RRC for each serving cell. Beam failure is detected by counting the beam failure instance notifications notified from the lower layer (PHY layer) to the MAC entity. The MAC entity may perform some or all of the following processes (A), (B), and (C) for each serving cell for beam failure detection. (A) If a beam failure instance notification is received from the lower layer, start or restart the timer (beamFailureDetectionTimer) and increment the counter (BFI-COUNTER) by 1. If the value of BFI_COUNTER is greater than or equal to the set threshold (beamFailureInstanceMaxCount), perform the process of (A-1) below. (A-1) If the serving cell is an SCell, trigger beam failure recovery (BFR) for this serving cell; otherwise, start the random access procedure in the SpCell. (B) If the beamFailureDetectionTimer for this serving cell expires, or if the beamFailureDetectionTimer, beamFailureInstanceMaxCount, and / or the configuration of the reference signal for beam failure detection are changed by the upper layer, set BFI_COUNTER to 0. (C) If the serving cell is the SpCell and the random access procedure is successfully completed, set BFI_COUNTER to 0, stop the timer (beamFailureRecoveryTimer), and consider the beam failure recovery procedure to be successfully completed. Otherwise, if the serving cell is an SCell and a PDCCH addressed to the C-RNTI indicating a new uplink grant for transmitting information for SCell beam failure recovery (e.g., information included in the SCell BFR MAC CE) is received, or if the SCell is in the inactive state, set BFI_COUNTER to 0, consider the beam failure recovery procedure to be successfully completed, and cancel all beam failure recoveries (BFR) triggered for this serving cell.

[0132] If at least one beam failure recovery (BFR) is triggered by the beam failure recovery procedure and it has not been cancelled, the MAC entity performs the following processing in (A). (A) If the UL-SCH resource can include the SCell BFR MAC CE and its sub-header considering the logical channel priority, include the SCell BFR MAC CE and its sub-header. Otherwise, if the UL-SCH resource can include the truncated SCell BFR MAC CE and its sub-header considering the logical channel priority, include the truncated SCell BFR MAC CE and its sub-header. Otherwise, trigger a scheduling request for SCell beam failure recovery.

[0133] The dormancy of the SCell is performed by activating the dormant BWP in this SCell. Even when the SCell is in a dormant state, measurements of CSI, automatic gain control (AGC), and beam control (beam management) including beam failure recovery may be performed in this SCell.

[0134] Next, the dormancy of the SCG will be described.

[0135] In LTE and / or NR, the state in which the SCG is dormant may be included in the RRC_CONNECTED state.

[0136] In LTE and / or NR, the state in which the SCG is dormant may be a state in which the terminal device performs some or all of the following (A) to (E) in the SpCell (PSCell) of the SCG. (A) Do not transmit SRS in this SpCell. (B) Do not report CSI for this SpCell. (C) Do not transmit PUCCH, UL-SCH, and / or RACH in this SpCell. (D) Do not monitor the PDCCH of this SpCell and / or the PDCCH for this SpCell. (E) Perform discontinuous reception (DRX) in this SpCell.

[0137] Also, the state in which the SCG is dormant may be a state in which some or all of the processes of the above (A) to (E) and the following (F) to (H) are performed. (F) Set the BWP set to the dormant BWP in this SpCell as the activated BWP (Active BWP). (G) Monitor only the PDCCH indicating exiting the dormant BWP in the activated dormant BWP of this SpCell. (H) Do not monitor the C-RNTI with the PDCCH in the activated dormant BWP of this SpCell.

[0138] In LTE and / or NR, the terminal device may determine and / or execute the suspension of the SCG based on some or all of the following (A) to (H). Note that the messages and control elements in the following (A) to (F) may be notified to the terminal device from a cell group other than the SCG.

[0139] The suspension of the SCG may also be referred to as entering the Dormant SCG. Also, the suspension of the SCG may mean that the dormant BWP of the SpCell of the cell group is activated. (A) Receiving an RRC message indicating the suspension of the SCG (B) Receiving a MAC control element indicating the suspension of the SCG (C) Receiving an RRC message indicating the suspension of the SpCell (D) Receiving a MAC control element indicating the suspension of the SpCell (E) Receiving other RRC messages (F) Receiving other MAC control elements (G) Expiration of a timer related to the suspension of the SCG (H) Expiration of a timer related to the suspension of the PSCell

[0140] In LTE and / or NR, the terminal device may determine and / or execute the resumption from the suspended state of the SCG based on some or all of the following (A) to (H). Note that the messages and control elements in the following (A) to (F) may be notified to the terminal device from a cell group other than the SCG.

[0141] The resumption from the suspended state of the SCG may also be referred to as leaving the Dormant SCG. Also, the resumption from the suspended state of the SCG may mean that the BWP switches from the dormant BWP to another (non-dormant BWP) BWP in the SpCell of the cell group. (A) Receiving an RRC message indicating the resumption from the suspended state of the SCG (B)Receiving a MAC control element that instructs the return from the dormant state of the SCG (C)Receiving an RRC message that instructs the return from the dormant state of the SpCell (D)Receiving a MAC control element that instructs the return from the dormant state of the SpCell (E)Receiving other RRC messages (F)Receiving other MAC control elements (G)Timer related to the dormancy of the SCG (H)Timer related to the dormancy of the PSCell

[0142] The terminal device that executes the dormancy of the SCG may execute some or all of the following processes (A) to (F) in the SCG. (A)Set all SCell to the inactive state. (B)Consider that all timers (sCellDeactivationTimer) associated with the active SCell have expired. (C)Consider that all timers (sCellDeactivationTimer) associated with the dormant SCell have expired. (D)Do not start or restart the timer (sCellDeactivationTimer) associated with all SCell. (E)Ignore the MAC CE that activates the SCell. For example, in the above processes (AD), when receiving the MAC CE that activates the SCell and not being instructed to enter the dormancy of the SCG (or not in the dormant state of the SCG), perform process (AD-1). (F)Execute the above process (AD-2). For example, in the above processes (AD), when being instructed to enter the dormancy of the SCG (or entering the dormant state of the SCG), perform process (AD-2).

[0143] The terminal device that executes the return from the dormant state of the SCG may execute some or all of the following processes (A) to (C) in the SCG. (A)Execute process (AD-1) to set all SCell to the active state. (B) Keep all SCell in an inactive state. However, since it is not in a dormant state, for example, in the above process (AD), if a MAC CE for activating the SCell is received, since the SCG is not instructed to be dormant (or is not in a dormant state of the SCG), the process (AD-1) may be performed. (C) When performing the return from the dormant state of the SCG based on the RRC message, if this RRC message includes parameters related to random access for some or all of the SCell, start the random access procedure in the target SCell based on the notified parameters.

[0144] FIG. 9 is a diagram showing an example of an embodiment. In FIG. 9, the UE 122 receives a message (RRC message) notifying it to put the SCG into a dormant state (first state) from the eNB 102 or the gNB 108 (step S902). Based on the above notification, the UE 122 controls the cells other than the SpCell (second cell) of the SCG (i.e., SCell) to be in an inactive state.

[0145] By the above operations, in the process of putting the SCG into a dormant state, an efficient state change can be achieved without independently transmitting a MAC CE for changing the state of the SCell of the SCG to an inactive state. Also, when the dormancy of the SCG is performed based on an RRC message, conventionally, the initial state was set in the RRC layer and the state change was performed in the MAC layer. However, by the above operations, it is possible to efficiently change the state of the SCG while avoiding a mismatch between the instructions of the RRC layer and the MAC layer.

[0146] Here, the PDCCH indicating exiting the dormant BWP will be described.

[0147] For example, when the SpCell is in the dormant state (the state where the dormant BWP is activated), the UE may monitor the PDCCH in the Active BWP of the SpCell to detect a certain DCI format (e.g., DCI format 2_6). The CRC of the DCI format may be scrambled with a certain RNTI (e.g., PS-RNTI). The UE with a configured dormant SCell group determines the switching of the Active DL BWP based on the bitmap information included in the payload of DCI format 2_6. For example, a certain bit of the bitmap is associated with a dormant SCell group. If the bit is 1 and the Active DL BWP is the dormant BWP, the BWP switching may be executed to another pre-configured BWP; if the Active DL BWP is not the dormant BWP, it may remain in that BWP. Also, if the bit is 0, the BWP switching may be executed so that the Active DL BWP becomes the dormant BWP.

[0148] If, in the dormant state of the SpCell, it is a system where discontinuous reception is configured in the SpCell, the UE may not need to monitor the PDCCH for the purpose of detecting DCI format 2_6 during the active time of DRX.

[0149] If, in the dormant state of the SpCell, it is a system in which discontinuous reception is configured in the SpCell, a UE with discontinuous reception (DRX) configured in the SpCell may monitor the PDCCH in the Active BWP of the SpCell to detect a certain DCI format (for example, DCI format 0_1 and 1_1) during the active time of DRX. The CRC of the said DCI format may be scrambled with a certain RNTI (for example, C-RNTI or MCS-C-RNTI). A UE with a dormant SCell group configured determines the switching of the Active DL BWP based on the bitmap information included in the payload of DCI format 0_1 or DCI format 1_1. For example, a certain bit of the bitmap is associated with one dormant SCell group. When the bit is 1, if the Active DL BWP is the dormant BWP, perform BWP switching to another pre-configured BWP, and if the Active DL BWP is not the dormant BWP, it may remain in that BWP. Also, when the bit is 0, BWP switching may be performed so that the Active DL BWP becomes the dormant BWP. Also, the "another pre-configured BWP" may be a BWP different from the "another pre-configured BWP" used in the description of DCI format 2_6.

[0150] Outside the active time of DRX, the UE may not monitor the PDCCH for the purpose of detecting DCI format 0_1 and DCI format 1_1.

[0151] Monitoring the PDCCH indicating exiting the dormant BWP may be monitoring the PDCCH for the purpose of detecting DCI format 2_6. In that case, it may not be necessary to monitor the PDCCH for the purpose of detecting other DCI formats.

[0152] If, in the case of a system where discontinuous reception is configured for the SpCell in the dormant state of the SpCell, monitoring the PDCCH indicating exiting the dormant BWP may mean monitoring the PDCCH for detecting DCI format 2_6 outside the active time of DRX, and monitoring the PDCCH for detecting DCI format 0_1 and DCI format 1_1 during the active time of DRX. In this case, it may not be necessary to monitor the PDCCH for detecting other DCI formats.

[0153] When the SCG is in the dormant state, all uplink transmissions in the SCG may be stopped. In this case, the information regarding that SCG may be transmitted in another cell group (e.g., MCG). Or, the information regarding that SCG may be transmitted in that SCG which has exited the dormant state. Also, when the SCG is in the dormant state, some or all uplink transmissions in the SCG may be permitted. Here, an example of performing uplink transmission in the SCG when the SCG is in the dormant state will be described.

[0154] For example, beam failure recovery in the case where beam control (beam management) including beam failure recovery is performed in the SpCell of the dormant SCG will be described.

[0155] The MAC entity may have beam failure recovery procedures set by the RRC for each serving cell. Note that in the dormant SCG, the beam failure recovery procedures may be set and / or performed only in the SpCell, or in the dormant SCG, the beam failure recovery procedures may be set and / or performed in the SpCell and some or all of the SCells. Beam failure is detected by counting beam failure instance notifications notified from the lower layer (PHY layer) to the MAC entity. The MAC entity may perform some or all of the following processes (A), (B), and (C) in each serving cell for beam failure detection. (A) If a beam failure instance notification is received from a lower layer, start or restart the timer (beamFailureDetectionTimer), and increment the counter (BFI-COUNTER) by 1. If the value of BFI_COUNTER is greater than or equal to the set threshold (beamFailureInstanceMaxCount), perform the following process (A-1). (A-1) If the serving cell is an SCell, trigger beam failure recovery (BFR) for this serving cell; otherwise, start the random access procedure in the SpCell. Note that if beam recovery is not triggered in the SCell, it may not be necessary to trigger beam failure recovery for the SCell here. That is, only when the serving cell is an SpCell, the process of starting the random access procedure in the SpCell may be performed. (B) If the beamFailureDetectionTimer for this serving cell expires, or if the beamFailureDetectionTimer, beamFailureInstanceMaxCount, and / or the configuration of the reference signal for beam failure detection are changed by the upper layer, set BFI_COUNTER to 0. (C) If the serving cell is an SpCell and the random access procedure is successfully completed, set BFI_COUNTER to 0, stop the timer (beamFailureRecoveryTimer), and consider that the beam failure recovery procedure is successfully completed. Otherwise, if the serving cell is an SCell and a PDCCH addressed to the C-RNTI indicating a new uplink grant for transmitting information for SCell beam failure recovery (e.g., information included in the SCell BFR MAC CE) is received, or if the SCell is in an inactive state, set BFI_COUNTER to 0, consider that the beam failure recovery procedure is successfully completed, and cancel all beam failure recoveries (BFR) triggered for this serving cell.

[0156] If at least one beam failure recovery (BFR) is triggered by the beam failure recovery procedure and has not been cancelled, the MAC entity of the SCG triggers a scheduling request for SCell beam failure recovery if necessary.

[0157] When the scheduling request is triggered, if there is no valid PUCCH resource for the pending scheduling request configured in the MAC entity of the SCG, the random access procedure is initiated in the SpCell.

[0158] As described above, the random access procedure in the SpCell (PSCell) may be initiated in the dormant SCG either by the trigger of a scheduling request for transmitting a MAC PDU including a MAC CE by the MAC entity or directly by the MAC entity. At this time, the MAC PDU may not include a MAC SDU.

[0159] On the other hand, the random access procedure in the SpCell (PSCell) may also be initiated in the dormant SCG by the trigger of a scheduling request for transmitting a MAC PDU including data (MAC SDU) from upper layers such as user data and RRC messages.

[0160] Here, in the SpCell of a certain cell group, the state in which UL-SCH transmission and RACH transmission are possible is defined as the first state. The first state may be a state in which, in the SpCell of the cell group, RACH transmission is possible and / or PDCCH addressed to a C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating an uplink grant for UL-SCH transmission is monitored. Also, the first state may be a state in which the first BWP is activated in the SpCell of the cell group, and PDCCH addressed to a C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating an uplink grant in the first BWP is monitored. Furthermore, the first state may be a state in which channel state information (CSI) measurement for the first BWP is performed. Also, the first state may be a state in which discontinuous reception (DRX) is set.

[0161] The state of monitoring PDCCH addressed to a C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating an uplink grant for UL-SCH transmission may include the state where the Active BWP of the SpCell of the cell group is not a dormant BWP. Also, the first state may be a state in which the cell group (SCG) has returned from a dormant state. Also, the first state may be a state in which the cell group (SCG) is not in a dormant state.

[0162] Also, for example, the first state may be a state that transitions from the second state when a random access procedure is initiated due to a scheduling request triggered to transmit a MAC PDU containing a MAC SDU. Also, for example, the first state may be a state that transitions from the second state when the RRC entity is instructed to resume from a dormant state. Also, for example, the first state may be a state in which PDCCH indicating exiting the dormant BWP (exiting from the dormant BWP) is not monitored.

[0163] In the SpCell of a certain cell group, the state where UL-SCH transmission and RACH transmission are stopped is defined as the second state. The second state may be a state where, in the SpCell of the cell group, RACH is not transmitted and / or PDCCH addressed to C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating an uplink grant for UL-SCH transmission is not monitored. Also, the second state may be a state where the second BWP is activated in the SpCell of the cell group, and in the second BWP, PDCCH addressed to C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating an uplink grant for UL-SCH transmission and PDCCH indicating exiting the dormant BWP are not monitored. Further, the second state may be a state where the second BWP is activated in the SpCell of the cell group, and in the second BWP, only the PDCCH indicating exiting the dormant BWP is monitored. Additionally, the second state may be a state where channel state information (CSI) measurement for the second BWP is performed.

[0164] The second state may be a state where the Active BWP of the SpCell is the dormant BWP.

[0165] In the SpCell of a certain cell group, the state where limited UL-SCH transmission and RACH transmission are possible is defined as the third state. The third state may be a state where, in the SpCell of the cell group, RACH transmission is possible, and for limited UL-SCH transmission, PDCCH addressed to C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating an uplink grant is monitored. The third state may be a part of the first state when the cell group (SCG) resumes from the dormant state, or may be a state different from the first state when the cell group (SCG) resumes from the dormant state.

[0166] For example, the third state may be a state that transitions from the second state when a random access procedure triggered by a MAC entity is started. Also, for example, the third state may be a state that transitions from the second state when the value of BFI_COUNTER becomes equal to or greater than a set threshold value. Also, for example, the third state may be a state that transitions from the second state when the value of BFI_COUNTER becomes equal to or greater than a set threshold value and a random access procedure is started at the PSCell. Also, for example, the third state may be a state that transitions from the second state when the value of BFI_COUNTER becomes equal to or greater than a set threshold value and a BFR is triggered at the SCell.

[0167] Also, the third state may be a state in which a third BWP is activated in the SpCell of the cell group, and in the third BWP, a PDCCH indicating exiting the dormant BWP is monitored. Further, the third state may be a state in which, in the third BWP, a PDCCH addressed to a C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating an uplink grant is not monitored. Further, the third state may be a state in which channel state information (CSI) measurement for the third BWP is performed. When the UE receives a PDCCH indicating exiting the dormant BWP for its own station in the third BWP, the BWP may be switched to a preset BWP (for example, the first BWP).

[0168] Also, for example, the third state may be a state that transitions from the second state when a random access procedure triggered to transmit a MAC PDU not including a MAC SDU is started. Also, for example, the third state may be a state that transitions from the second state when a random access procedure triggered to transmit a MAC PDU including a specific MAC CE is started. The specific MAC CE may include a BFR MAC CE. Also, for example, the third state may be a state that transitions from the second state when a MAC PDU including a specific MAC CE does not include a MAC SDU.

[0169] For example, as shown in FIG. 10, the UE determines whether to start a random access procedure in the dormant SCG (step S1000), and if it starts the random access, it may switch the Active BWP to another BWP (for example, the third BWP) (step S1002).

[0170] Also, for example, the third state may be a state that transitions from the second state when performing a random access procedure to request an uplink grant.

[0171] For the UE, the BWP (first BWP) that becomes Active when returning from the dormant state of the SCG to the first state, the BWP (second BWP) that becomes Active in the second state, and the BWP (third BWP) that becomes Active in the third state may be set independently. Also, one or more BWPs may be set for each of the first to third BWPs. Also, each of the first to third BWPs may be composed of a downlink BWP and / or an uplink BWP.

[0172] Transitioning to the first state may have the same meaning as the first BWP becoming Active. Transitioning to the second state may have the same meaning as the second BWP becoming Active. Transitioning to the third state may have the same meaning as the third BWP becoming Active.

[0173] Transitioning to the first state may have the same meaning as the BWPs other than the first BWP becoming deactivated BWPs. Transitioning to the second state may have the same meaning as the BWPs other than the second BWP becoming activated BWPs. Transitioning to the third state may have the same meaning as the BWPs other than the third BWP becoming activated BWPs.

[0174] Some or all of the first to third BWPs may be set for the UE by an RRC message. The setting of the second BWP may not include some or all of the parameters necessary for monitoring the PDCCH as described above. The setting of the second BWP may not include the setting of the uplink BWP. The setting of the third BWP may include the parameters necessary for monitoring the PDCCH for receiving at least the random access preamble response (random access response). The setting of the third BWP may include the setting of the uplink BWP. The setting of the uplink BWP may include the information necessary for transmitting the random access preamble.

[0175] Also, as another example, the dormant state of the SCG may be the above third state. That is, entering the dormant state of the SCG may have the same meaning as transitioning to the third state. In this case, the second state may be defined as another state different from the dormant state of the SCG, or the second state may not exist.

[0176] This makes it possible to trigger the necessary uplink transmission even in the dormant state of the SCG. Also, in the dormant state of the SCG, power saving is possible by monitoring only the necessary signals.

[0177] Describe the MCG failure. The purpose of this procedure may be to notify the network of the MCG failure (i.e., MCG radio link failure) encountered by the UE. A UE in RRC_CONNECTED with the AS layer security of SRB2 active and at least one DRB set up may initiate a fast MCG link recovery procedure to maintain the RRC connection without re-establishment.

[0178] As shown in Figure 11, a UE with split SRB1 or SRB3 configured may start the procedure for reporting an MCG failure (step S1102) when some or all of the conditions from (A) to (D) below are satisfied and the condition of (E) is satisfied (step S1100). (A) Transmissions of both MCG and SCG are not suspended (B) Timer T316 is configured (C) SCG is not in the fourth state (D) The active BWP of the SpCell of SCG is not a dormant BWP (E) When an MCG radio link failure is detected while timer T316 is not running

[0179] Note that when the procedure for reporting an MCG failure is started, MCG transmissions for all SRBs and DRBs other than SRB0 are suspended. Also, when the procedure for reporting an SCG failure is started, SCG transmissions for all SRBs and DRBs are suspended.

[0180] Timer T316 is a timer that is started when transmitting an MCG failure information message, and this timer stops when MCG transmissions resume, when an RRCRelease message is received, or when a re-establishment procedure is started.

[0181] The fourth state may be a state in which the fourth BWP is activated in the SpCell of the cell group, and in the fourth BWP, only the PDCCH indicating exiting the dormant BWP is monitored, and the channel state information (CSI) for the fourth BWP is measured. Further, the fourth state may be a state in which the fourth BWP is activated in the SpCell of the cell group, and in the fourth BWP, the C-RNTI is not monitored by the PDCCH, and the channel state information (CSI) for the fourth BWP is measured. Further, the fourth state may be the aforementioned third state.

[0182] When the procedure for reporting MCG failure is started, the UE suspends MCG transmission for all SRBs and DRBs other than SRB0, resets the MCG MAC, and starts transmitting the MCG failure information message.

[0183] Thereby, considering the dormant state of the SCG, the procedure for reporting MCG failure can be controlled.

[0184] Also, another example of MCG failure is described. In this example, the UE considers that the transmission of the SCG is suspended when the active BWP of the SpCell of the SCG is the dormant BWP.

[0185] A UE in which split SRB1 or SRB3 is configured may transition to the third state or the first state and start the procedure for reporting MCG failure when some or all of the conditions from (A) to (B) below are satisfied and the condition of (C) is satisfied. (A) Transmissions of both MCG and SCG are not suspended (B) Timer T316 is configured (C) When a radio link failure of the MCG is detected while timer T316 is not running

[0186] Thereby, the procedure for reporting MCG failure can be controlled without adding new conditions.

[0187] FIG. 5 is a block diagram showing the configuration of the terminal device (UE122) in each embodiment of the present invention. In order to avoid complication of the description, FIG. 5 shows only the main components closely related to one embodiment of the present invention.

[0188] The UE122 shown in FIG. 5 includes a receiving unit 500 that receives RRC messages and the like from the base station device, and a processing unit 502 that performs processing according to some or all of the setting information among various information elements (IEs: Information Elements), various fields, and various conditions included in the received messages, and a transmitting unit 504 that transmits RRC messages and the like to the base station device. The above-mentioned base station device may be the eNB102 or the gNB108. Further, the processing unit 502 may include some or all of the functions of various layers (for example, the physical layer, the MAC layer, the RLC layer, the PDCP layer, the RRC layer, and the NAS layer). That is, the processing unit 502 may include some or all of the physical layer processing unit, the MAC layer processing unit, the RLC layer processing unit, the PDCP layer processing unit, the RRC layer processing unit, and the NAS layer processing unit.

[0189] FIG. 6 is a block diagram showing the configuration of the base station device in each embodiment of the present invention. In order to avoid complication of the description, FIG. 6 shows only the main components closely related to one aspect of the present invention. The above-mentioned base station device may be the eNB102 or the gNB108.

[0190] The base station apparatus shown in FIG. 6 includes a transmission unit 600 that transmits RRC messages and the like to the UE 122, and a processing unit 602 that creates an RRC message including some or all of the setting information among various information elements (IEs: Information Elements), various fields, and various conditions, and causes the processing unit 502 of the UE 122 to perform processing by transmitting it to the UE 122, and a reception unit 604 that receives RRC messages and the like from the UE 122. Further, the processing unit 602 may include some or all of the functions of various layers (for example, the physical layer, the MAC layer, the RLC layer, the PDCP layer, the RRC layer, and the NAS layer). That is, the processing unit 602 may include some or all of the physical layer processing unit, the MAC layer processing unit, the RLC layer processing unit, the PDCP layer processing unit, the RRC layer processing unit, and the NAS layer processing unit.

[0191] Also, in the examples of each process or the examples of the flow of each process in the above description, some or all of the steps may not be executed. Also, in the examples of each process or the examples of the flow of each process in the above description, the order of the steps may be different. Also, in the examples of each process or the examples of the flow of each process in the above description, some or all of the processes within each step may not be executed. Also, in the examples of each process or the examples of the flow of each process in the above description, the order of the processes within each step may be different.

[0192] Hereinafter, various aspects of the terminal device in the embodiments of the present invention will be described.

[0193] (1) The first embodiment of the present invention is a terminal device, comprising a control unit that transitions from a first state to a second state when instructed to enter the second state of a cell group. The first state is a state in which a first BWP is activated in the SpCell of the cell group, the downlink control channel is monitored in the first BWP, and the channel state information (CSI) for the first BWP is measured. The second state is a state in which a second BWP is activated in the SpCell of the cell group, only the PDCCH indicating exiting the dormant BWP is monitored in the second BWP, and the channel state information (CSI) for the second BWP is measured.

[0194] (2) The second embodiment of the present invention is a base station device that communicates with a terminal device, comprising a control unit that instructs the terminal device to enter the second state of the cell group, thereby causing the terminal device to transition from the first state to the second state. The first state is a state in which a first BWP is activated in the SpCell of the cell group, the downlink control channel is monitored in the first BWP, and the channel state information (CSI) for the first BWP is measured. The second state is a state in which a second BWP is activated in the SpCell of the cell group, only the PDCCH indicating exiting the dormant BWP is monitored in the second BWP, and the channel state information (CSI) for the second BWP is measured.

[0195] (3) A third embodiment of the present invention is a method applied to a terminal device, comprising a step of transitioning from a first state to a second state when instructed to enter the second state of a cell group. The first state is a state in which a first BWP is activated in the SpCell of the cell group, a downlink control channel is monitored in the first BWP, and channel state information (CSI) measurement for the first BWP is performed. The second state is a state in which a second BWP is activated in the SpCell of the cell group, only a PDCCH indicating exiting a dormant BWP is monitored in the second BWP, and channel state information (CSI) measurement for the second BWP is performed.

[0196] (4) A fourth embodiment of the present invention is a method applied to a base station device communicating with a terminal device, comprising a step of transitioning the terminal device from a first state to a second state by instructing the terminal device to enter the second state of a cell group. The first state is a state in which a first BWP is activated in the SpCell of the cell group, a downlink control channel is monitored in the first BWP, and channel state information (CSI) measurement for the first BWP is performed. The second state is a state in which a second BWP is activated in the SpCell of the cell group, only a PDCCH indicating exiting a dormant BWP is monitored in the second BWP, and channel state information (CSI) measurement for the second BWP is performed.

[0197] (5) A fifth embodiment of the present invention is an integrated circuit implemented in a terminal device, which causes the terminal device to transition from a first state to a second state when instructed to enter the second state of a cell group. The first state is a state in which a first BWP is activated in the SpCell of the cell group, a downlink control channel is monitored in the first BWP, and channel state information (CSI) measurement for the first BWP is performed. The second state is a state in which a second BWP is activated in the SpCell of the cell group, only a PDCCH indicating exiting a dormant BWP is monitored in the second BWP, and channel state information (CSI) measurement for the second BWP is performed.

[0198] (6) A sixth embodiment of the present invention is an integrated circuit implemented in a base station device that communicates with a terminal device, which causes the base station device to transition the terminal device from a first state to a second state by instructing the terminal device to enter the second state of a cell group. The first state is a state in which a first BWP is activated in the SpCell of the cell group, a downlink control channel is monitored in the first BWP, and channel state information (CSI) measurement for the first BWP is performed. The second state is a state in which a second BWP is activated in the SpCell of the cell group, only a PDCCH indicating exiting a dormant BWP is monitored in the second BWP, and channel state information (CSI) measurement for the second BWP is performed.

[0199] A program that operates on a device according to an aspect of the present invention may be a program that controls a Central Processing Unit (CPU) or the like to function a computer so as to realize the functions of the above-described embodiments according to an aspect of the present invention. The program or the information handled by the program is temporarily read into a volatile memory such as a Random Access Memory (RAM) during processing, or stored in a non-volatile memory such as a flash memory or a Hard Disk Drive (HDD), and is read by the CPU as necessary for correction and writing.

[0200] Note that a part of the device in the above-described embodiment may be realized by a computer. In that case, a program for realizing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to realize it. Here, the "computer system" means a computer system built in the device and including hardware such as an operating system and peripheral devices. Further, the "computer-readable recording medium" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, and the like.

[0201] Furthermore, the "computer-readable recording medium" includes those that hold a program dynamically for a short time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and those that hold a program for a certain time, such as a volatile memory inside a computer system serving as a server or a client in that case. Also, the above program may be for realizing a part of the above-described functions, and may further be realizable in combination with a program already recorded in the computer system for realizing the above-described functions.

[0202] Furthermore, each functional block or various features of the apparatus used in the above-described embodiments can be implemented or executed by an electric circuit, that is, typically an integrated circuit or a plurality of integrated circuits. The electric circuit designed to execute the functions described in this specification may include a general-purpose use processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or a combination thereof. The general-purpose use processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller, or a state machine. The general-purpose use processor or each of the above-described circuits may be composed of a digital circuit or an analog circuit. Also, when an integrated circuit technology that replaces the current integrated circuit appears due to the progress of semiconductor technology, it is also possible to use the integrated circuit according to the technology.

[0203] Note that the invention of the present application is not limited to the above-described embodiments. In the embodiments, an example of the apparatus is described, but the invention of the present application is not limited thereto, and it can also be applied to stationary or non-mobile electronic devices installed indoors and outdoors, for example, terminal devices or communication devices such as AV devices, kitchen devices, cleaning and washing devices, air conditioning devices, office devices, vending machines, and other household devices.

[0204] As described above, the embodiments of the present invention have been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and design changes and the like within the scope not departing from the gist of the present invention are also included. Also, one aspect of the present invention can be variously modified within the scope shown in the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Also, a configuration in which elements described in the above embodiments and having the same effects are replaced with each other is included.

Industrial Applicability

[0205] One aspect of the present invention can be used, for example, in a communication system, communication equipment (such as a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (such as a communication chip), or a program, etc.

Description of Reference Numerals

[0206] 100 E-UTRA 102 eNB 104 EPC 106 NR 108 gNB 110 5GC 112, 114, 116, 118, 120, 124 Interface 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, comprising a control unit that transitions from a first state to a second state when instructed to enter the second state of the cell group, The first state is the first BWP is activated in the SpCell of the cell group, monitoring the downlink control channel (PDCCH) in the first BWP, and performing measurement of channel state information (CSI) for the first BWP, The second state is the second BWP is activated in the SpCell of the cell group, all SCells of the cell group are deactivated, not monitoring the PDCCH in the second BWP, and performing measurement of channel state information (CSI) for the second BWP. Terminal device.

2. A base station device that communicates with a terminal device, comprising a control unit that causes the terminal device to transition from a first state to a second state by instructing the terminal device to enter the second state of the cell group, The first state is the first BWP is activated in the SpCell of the cell group, monitoring the downlink control channel (PDCCH) in the first BWP, and performing measurement of channel state information (CSI) for the first BWP. The second state is the second BWP is activated in the SpCell of the cell group, all SCells of the cell group are deactivated, not monitoring the PDCCH in the second BWP, and is in a state of performing measurement of channel state information (CSI) for the second BWP Base station device.

3. A method applied to a terminal device, comprising: a step of transitioning from a first state to a second state when instructed to enter a second state of a cell group; The first state is a first BWP is activated in the SpCell of the cell group, monitoring a downlink control channel (PDCCH) in the first BWP, and is in a state of performing measurement of channel state information (CSI) for the first BWP; The second state is a second BWP is activated in the SpCell of the cell group, all SCells of the cell group are deactivated, not monitoring a PDCCH in the second BWP, and is in a state of performing measurement of channel state information (CSI) for the second BWP. Method.

4. A method applied to a base station device communicating with a terminal device, comprising: a step of causing the terminal device to transition from a first state to a second state by instructing the terminal device to enter a second state of a cell group; The first state is a first BWP is activated in the SpCell of the cell group, monitoring a downlink control channel (PDCCH) in the first BWP, and is in a state of performing measurement of channel state information (CSI) for the first BWP; The second state is a second BWP is activated in the SpCell of the cell group, all SCells of the cell group are deactivated, In the second BWP, without monitoring the PDCCH, and being in a state of performing measurement of channel state information (CSI) for the second BWP. Method.

5. An integrated circuit implemented in a terminal device, causing the terminal device to exhibit a function of transitioning from a first state to a second state when instructed to enter the second state of a cell group, The first state is in which a first BWP is activated in the SpCell of the cell group, monitoring a downlink control channel (PDCCH) in the first BWP, and being in a state of performing measurement of channel state information (CSI) for the first BWP. The second state is in which a second BWP is activated in the SpCell of the cell group, all SCells of the cell group are deactivated, without monitoring the PDCCH in the second BWP, and being in a state of performing measurement of channel state information (CSI) for the second BWP. Integrated circuit.

6. An integrated circuit implemented in a base station device that communicates with a terminal device, causing the base station device to exhibit a function of transitioning the terminal device from a first state to a second state by instructing the terminal device to enter the second state of a cell group, The first state is in which a first BWP is activated in the SpCell of the cell group, monitoring a downlink control channel (PDCCH) in the first BWP, and being in a state of performing measurement of channel state information (CSI) for the first BWP. The second state is The second BWP is activated in the SpCell of the cell group, in the second BWP, the PDCCH is not monitored, all SCells of the cell group are deactivated, and it is in a state of performing measurement of channel state information (CSI) for the second BWP, Integrated circuit.

Images