Terminal device, method, and integrated circuit

Abstract

A terminal device provided with a first cell group and a second cell group includes a detection unit that detects a radio link failure of the first cell group, and a control unit that starts a first procedure of reporting the radio link failure of the first cell group, the first procedure being started based on the fact that transmission of the first cell group and the second cell group is not suspended, the second cell group is not in a first state, and the radio link failure of the first cell group is detected, the first state being a state in which a first BWP is activated in a SpCell of the cell group, PDCCH is not monitored in the first BWP, and a measurement of channel state information (CSI) for the first BWP is performed.

Description

Technical Field

[0001] This invention relates to terminal devices, methods, and integrated circuits.

[0002] This application claims priority to Japanese Patent Application No. 2020-99021, filed in Japan on June 8, 2020, the contents of which are incorporated herein by reference. Background Technology

[0003] The 3rd Generation Partnership Project (3GPP) studied radio access methods and radio networks for cellular mobile communications (hereinafter referred to as "Long Term Evolution (LTE: registered trademark)" or "Evolved Universal Terrestrial Radio Access (EUTRA)") and core networks (hereinafter referred to as "Evolved Packet Core (EPC)"). EUTRA is also known as E-UTRA.

[0004] Furthermore, within 3GPP, technical research and standardization were conducted on LTE-Advanced Pro, an extension of LTE, and NR (New Radiotechnology), a new radio access technology, as radio access methods and wireless network technologies for fifth-generation cellular systems (Non-Patent Document 1). Additionally, research was also conducted on 5GC (5 Generation Core Network), the core network for fifth-generation cellular systems (Non-Patent Document 2).

[0005] Existing technical documents

[0006] Non-patent literature

[0007] Non-patent document 1: 3GPP RP-170855, "Work Item on New Radio (NR) Access Technology"

[0008] Non-patent document 2: 3GPP TS 23.501 v15.3.0, “System Architecture for the 5G System; Stage 2”

[0009] Non-patent document 3: 3GPP RP-182076, “WID on Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements”

[0010] Non-patent document 4: 3GPP TS 36.300, v15.3.0, "Evolved Universal Terestrial Radio Access (E-UTRA) and Evolved Universal Terestrial Radio Access Network (E-UTRAN); Overall description; Stage 2"

[0011] Non-patent literature 5: 3GPP TS 38.300v 15.3.0, "NR; NR and NG-RAN Overall description; Stage 2"

[0012] Non-patent document 6: 3GPP TS 36.321 v15.3.0, "Evolved Universal Terestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification"

[0013] Non-patent literature 7: 3GPP TS 38.321 v15.3.0, "NR; Medium Access Control (MAC) protocol specification"

[0014] Non-patent literature 8: 3GPP TS 36.331 v15.4.0, "Evolved Universal Terestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specifications"

[0015] Non-patent literature 9: 3GPP TS 38.331 v15.4.0, "NR; Radio Resource Control (RRC); Protocol specifications" Summary of the Invention

[0016] The problem the invention aims to solve

[0017] As a technology in NR (Radio Frequency I / O), to enable high-capacity data communication, there exists a dual-connectivity (also known as multi-connectivity) technology that uses multiple cell groups for communication between one or more base station devices and terminal devices. In this dual-connectivity technology, in order to communicate within each cell group, the terminal device needs to monitor each cell group for messages destined for itself. To ensure low-latency communication during high-capacity data communication, the terminal device constantly needs to monitor multiple cell groups, resulting in significant power consumption. Therefore, research began on a technology that monitors a portion of cell groups at a low frequency or stops monitoring (cell group dormant technology) (Non-Patent Document 3).

[0018] During the dormancy of a cell group, we studied how to handle cells (SpCell) that are always in the Activate state in the current state, but we also need to study cells other than SpCell.

[0019] One aspect of the present invention is made in view of the above circumstances, and one of its objectives is to provide a terminal device, base station device, method, and integrated circuit capable of efficiently performing communication control.

[0020] Technical solution

[0021] To achieve the above objectives, one embodiment of the present invention adopts the following approach. Specifically, a first embodiment of the present invention is a terminal device that sets up a first cell group and a second cell group. The terminal device includes: a detection unit that detects a radio link failure in the first cell group and / or the second cell group; and a control unit that initiates a first process for reporting a radio link failure in the first cell group. The first process is initiated based on the following: transmissions in the first cell group and the second cell group are not suspended; the second cell group is not in a first state; and a radio link failure in the first cell group is detected. The first state is a state in which a first BWP is activated in the SpCell of the cell group, the PDCCH is not monitored in the first BWP, and channel state information (CSI) measurement is performed for the first BWP.

[0022] (2) A second embodiment of the present invention is a method for a terminal device that has set a first cell group and a second cell group, the method comprising: a step of detecting a radio link failure of the first cell group and / or the second cell group; and a step of starting a first process of reporting a radio link failure of the first cell group, the first process being started based on the fact that transmissions of the first cell group and the second cell group are not suspended, the second cell group is not in a first state, and a radio link failure of the first cell group is detected, the first state being a state in which a first BWP is activated in the SpCell of the cell group, the PDCCH is not monitored in the first BWP, and a measurement of channel state information (CSI) for the first BWP is performed.

[0023] (3) A third embodiment of the present invention is an integrated circuit installed in a terminal device configured with a first cell group and a second cell group, the integrated circuit enabling the terminal device to perform the following functions: detecting radio link failures of the first cell group and / or the second cell group; and initiating a first process for reporting radio link failures of the first cell group, the first process being initiated based on the fact that transmissions of the first cell group and the second cell group are not suspended, the second cell group is not in a first state, and the radio link failure of the first cell group is detected, the first state being a state in which a first BWP is activated in the SpCell of the cell group, the PDCCH is not monitored in the first BWP, and the measurement of channel state information (CSI) for the first BWP is performed.

[0024] It should be noted that these specific solutions can be implemented by systems, devices, methods, integrated circuits, computer programs, or recording media, or by any combination of systems, devices, methods, integrated circuits, computer programs, and recording media.

[0025] Beneficial effects

[0026] According to one aspect of the present invention, the terminal device can achieve efficient communication control processing. Attached Figure Description

[0027] Figure 1 This is a schematic diagram of the communication system according to various embodiments of the present invention.

[0028] Figure 2 This is a protocol stack diagram of the UP and CP of the terminal device and the base station device in the E-UTRA of various embodiments of the present invention.

[0029] Figure 3 This is a protocol stack diagram of the UP and CP of the terminal device and the base station device in the NR of various embodiments of the present invention.

[0030] Figure 4 This is a diagram illustrating an example of the flow chart of various settings in RRC208 and / or RRC308 of various embodiments of the present invention.

[0031] Figure 5 This is a block diagram illustrating the configuration of the terminal device according to various embodiments of the present invention.

[0032] Figure 6 This is a block diagram illustrating the configuration of a base station device according to various embodiments of the present invention.

[0033] Figure 7 This is an example of an information element related to cell group settings in NR according to an embodiment of the present invention.

[0034] Figure 8 This is an example of an information element related to cell group settings in E-UTRA according to an embodiment of the present invention.

[0035] Figure 9 This is an example of a process related to the hibernation of an SCG in an embodiment of the present invention.

[0036] Figure 10 This is an example of a process related to the hibernation of an SCG in an embodiment of the present invention.

[0037] Figure 11 This is an example of a process related to the hibernation of an SCG in an embodiment of the present invention. Detailed Implementation

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

[0039] LTE (and LTE-A Pro) and NR can be defined as different Radio Access Technologies (RATs). Furthermore, LTE, which can connect to NR via Multi Radio Dual connectivity, is distinct from existing LTE. Additionally, LTE with a 5GC core network is distinct from existing LTE with an EPC core network. This implementation can be applied to NR, LTE, and other RATs. In the following description, terms associated with LTE and NR are used, but this implementation can also be applied to other technologies using other terms. Furthermore, the term E-UTRA in this implementation can be replaced with the term LTE, and vice versa.

[0040] Figure 1 This is a schematic diagram of the communication system according to various embodiments of the present invention.

[0041] E-UTRA100 is a radio access technology described in Non-Patent Document 4, etc., which includes a Cell Group (CG) consisting of one or more frequency bands. eNB (E-UTRAN Node B) 102 is the base station device of E-UTRA100. EPC (Evolved Packet Core) 104 is the core network described in Non-Patent Document 14, etc., designed as the core network for E-UTRA100. Interface 112 is the interface between eNB102 and EPC104, containing a control plane (CP) through which control signals pass and a user plane (UP) through which user data passes.

[0042] NR106 is a radio access technology described in Non-Patent Document 5, etc., comprising a Cell Group (CG) consisting of one or more frequency bands. gNB (g Node B) 108 is a base station device for NR106. 5GC110 is a core network described in Non-Patent Document 2, etc., designed for use with NR106, but can also be used as a core network for E-UTRA100 with the function of connecting to 5GC110. The following E-UTRA100 may include E-UTRA100 with the function of connecting to 5GC110.

[0043] Interface 114 is the interface between eNB102 and 5GC110; interface 116 is the interface between gNB108 and 5GC110; interface 118 is the interface between gNB108 and EPC104; interface 120 is the interface between eNB102 and gNB108; and interface 124 is the interface between EPC104 and 5GC110. Interfaces 114, 116, 118, 120, and 124 can be interfaces that connect only to the CP, only to the UP, or both the CP and UP. Furthermore, interfaces 114, 116, 118, 120, and 124 may not exist depending on the communication system provided by the telecommunications operator.

[0044] UE122 is a terminal device corresponding to some or all of E-UTRA100 and NR106. As described in some or all of Non-Patent Documents 4 and 5, when UE122 is connected to the core network via some or all of E-UTRA100 and NR106, a logical path called a Radio Bearer (RB) is established between UE122 and some 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).

[0045] Figure 2 This is a protocol stack diagram of the UP and CP of the terminal device and base station device of the E-UTRA Radio Access Layer in various embodiments of the present invention.

[0046] Figure 2 (A) is the protocol stack diagram of the UP used in E-UTRA100 when UE122 communicates with eNB102.

[0047] PHY (Physical layer) 200 is the radio physical layer, which provides transmission services to the upper layer using a physical channel. PHY 200 is connected to the upper-level MAC (Medium Access Control layer) 202 (described later) via a transport channel. Data moves between MAC 202 and PHY 200 via the transport channel. Data transmission and reception between the PHYs of UE122 and eNB102 are conducted via the radio physical channel.

[0048] MAC202 is a medium access control layer that maps multiple logical channels to multiple transport channels. MAC202 connects to the higher-level RLC (Radio Link Control layer) 204 (described later) via logical channels. Logical channels are broadly classified according to the type of information transmitted, into control channels transmitting control information and service channels transmitting user information. MAC202 may have functions such as controlling PHY200 for intermittent transmit / receive (DRX / DTX), performing random access procedures, notifying transmit power information, and performing HARQ control. Furthermore, MAC302 may have the function of controlling the activation state of the cell set at the RRC layer (Non-Patent Document 6).

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

[0050] PDCP206 is a packet data convergence protocol layer used for efficient transmission of user data such as IP packets over wireless networks. PDCP206 can feature header compression to compress unnecessary control information. Furthermore, PDCP206 can also provide data encryption.

[0051] It should be noted that the data processed in MAC202, RLC204, and PDCP206 are respectively referred to as MAC PDU (Protocol Data Unit), RLC PDU, and PDCP PDU. Furthermore, the data transferred from the upper layer to MAC202, RLC204, or PDCP206, or transferred to the upper layer, are respectively referred to as MAC SDU (Service Data Unit), RLC SDU, and PDCP SDU. Additionally, the segmented RLC SDU is referred to as an RLC SDU segment.

[0052] Figure 2(B) is the protocol stack diagram of the CP used when UE122 communicates with eNB102 and MME (Mobility Management Entity), which is a logical node that provides authentication, mobility management and other functions, in E-UTRA100.

[0053] In the CP protocol stack, besides PHY200, MAC202, RLC204, and PDCP206, there are also RRC (Radio Resource Control layer) 208 and NAS (Non-Access Strarum) 210. RRC208 is a radio link control layer that handles RRC connection establishment, re-establishment, suspending, and resuming; RRC connection reconfiguration, such as the establishment, modification, and release of radio bearers (RBs) and cell groups; control of logical channels, transport channels, and physical channels; and handover and measurement settings. RBs can be divided into Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs). SRBs can be used as paths for sending RRC messages as control information. DRBs can be used as paths for sending user data. Each RB can be configured between eNB102 and UE122's RRC208. Furthermore, the portion of an RB consisting of RLC204 and a logical channel can be referred to as an RLC bearer. Additionally, for the NAS layer that transmits signals between the MME and UE122, some or all of the layers from PHY200, MAC202, RLC204, PDCP206, and RRC208 that transmit signals and data between UE122 and eNB102 can be referred to as the AS (Access Strarum) layer.

[0054] The functional classification of MAC202, RLC204, PDCP206, and RRC208 described above is an example; it is also possible to omit some or all of these functionalities. Furthermore, some or all of the functionalities of each layer can be included in other layers.

[0055] It should be noted that the IP layer and the layers above it, such as TCP (Transmission Control Protocol), UDP (User Datagram Protocol), and the application layer, are above the PDCP layer (not shown in the diagram). Furthermore, the RRC layer and the NAS (non-access cascade) layer are also above the PDCP layer (not shown in the diagram). In other words, the PDCP layer is below the RRC layer, the NAS layer, the IP layer, and the layers above it, such as TCP (Transmission Control Protocol), UDP (User Datagram Protocol), and the application layer.

[0056] Figure 3 This is a protocol stack diagram of the UP and CP of the terminal device and the base station device in the NR wireless access layer of various embodiments of the present invention.

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

[0058] PHY (Physical layer) 300 is the radio physical layer of NR, which can provide transmission services to the upper layer using a physical channel. PHY 300 can connect to the upper-level MAC (Medium Access Control layer) 302 (described later) via a transport channel. Data can move between MAC 302 and PHY 300 via the transport channel. Data can be sent and received between the PHY of UE122 and gNB108 via the radio physical channel.

[0059] Here, the physical channel will be explained.

[0060] The following physical channels can be used in wireless communication between terminal devices and base station devices.

[0061] PBCH (Physical Broadcast Channel)

[0062] PDCCH (Physical Downlink Control Channel)

[0063] PDSCH (Physical Downlink Shared Channel)

[0064] PUCCH (Physical Uplink Control Channel)

[0065] PUSCH (Physical Uplink Shared Channel)

[0066] PRACH (Physical Random Access Channel)

[0067] PBCH is used to broadcast system information required by the terminal device.

[0068] In addition, in NR, PBCH can be used as a time index (SSB-Index) within the period of a block of broadcast synchronization signals (also known as SS / PBCH block).

[0069] The PDCCH is used to transmit (or transport) Downlink Control Information (DCI) in downlink wireless communication (wireless communication from a base station device to a terminal device). Here, one or more DCIs (also called DCI formats) are defined for the transmission of downlink control information. That is, 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 the 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 can be used for scheduling PUSCH in the serving cell. PUSCH can be used for transmitting user data, transmitting RRC messages, etc.

[0070] PUCCH can 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) indicating the state of the downlink channel. Furthermore, the uplink control information may include a scheduling request (SR) for requesting UL-SCH resources. Additionally, the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat request ACK knowledgement).

[0071] PDSCH can be used to send downlink data from the MAC layer (DL-SCH: Downlink SharedCHannel). In addition, in the case of downlink, it is also used to send system information (SI), random access response (RAR), etc.

[0072] PUSCH can be used to send HARQ-ACK and / or CSI along with uplink data (UL-SCH: Uplink Shared Channel) or uplink data from the MAC layer. Additionally, PUSCH can be used to send only CSI or only HARQ-ACK and CSI. That is, PUSCH can also be used to send only UCI. Furthermore, PDSCH or PUSCH can also be used to send RRC signaling (also known as RRC messages) and MAC control elements (MAC CEs). Here, in PDSCH, the RRC signaling sent from the base station device can be signaling shared by multiple terminal devices within the cell. Furthermore, the RRC signaling sent from the base station device can also be signaling dedicated to a specific terminal device (also known as dedicated signaling). That is, dedicated signaling can be used to send terminal device-specific (UE-specific) information to a specific terminal device. Additionally, PUSCH can be used to send UE capabilities in the uplink.

[0073] PRACH can be used to send random access preambles. PRACH can be used to indicate the initial connection establishment process, the handover procedure, the connection re-establishment process, synchronization (timing adjustment) sent for the uplink, and requests for PUSCH (UL-SCH) resources.

[0074] MAC302 is a medium access control layer that maps multiple logical channels to multiple transport channels. MAC302 can connect to the higher-level RLC (Radio Link Control layer) 304 (described later) via logical channels. Logical channels can be broadly classified according to the type of information transmitted, into control channels transmitting control information and service channels transmitting user information. MAC302 may have functions such as controlling PHY300 for intermittent transmit / receive (DRX / DTX), executing random access procedures, notifying transmit power information, and performing HARQ control. Furthermore, MAC302 may have the function of controlling the activation state of the cell set at the RRC layer (Non-Patent Document 7).

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

[0076] PDCP306 is a packet data convergence protocol layer used for efficient transmission of user data such as IP packets over wireless networks. PDCP306 can feature header compression to compress unnecessary control information. Furthermore, PDCP306 can also provide data encryption and integrity protection.

[0077] SDAP (Service Data Adaptation Protocol) 310 is a Service Data Adaptation Protocol layer with the following functions: establishing (mapping) the correspondence between the downlink QoS flow sent from 5GC110 to the terminal device via the base station device and the DRB, and mapping the uplink QoS flow sent from the terminal device to 5GC110 via the base station device and the DRB, and storing mapping rule information.

[0078] It should be noted that the data processed in MAC302, RLC304, PDCP306, and SDAP310 are respectively referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU. Furthermore, the data transferred from the upper layer to MAC302, RLC304, PDCP306, and SDAP310, or transferred to the upper layer, are respectively referred to as MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU. Additionally, the segmented RLC SDU is referred to as an RLC SDU segment.

[0079] Figure 3 (B) is the protocol stack diagram of the CP used when UE122 communicates with gNB108 and AMF (Access and Mobility Management function), which is a logical node that provides authentication, mobility management and other functions, in NR106.

[0080] In the CP protocol stack, besides PHY300, MAC302, RLC304, and PDCP306, there are also RRC (Radio Resource Control layer) 308 and NAS (non-access strawrum) 312. RRC308 is a radio link control layer that handles RRC connection establishment, re-establishment, suspending, and resuming; RRC connection reconfiguration, such as establishing, changing, and releasing radio bearers (RBs) and cell groups; control of logical channels, transport channels, and physical channels; and handover and measurement settings. RBs can be divided into signaling radio bearers (SRBs) and data radio bearers (DRBs). SRBs can be used as paths for sending RRC messages as control information. DRBs can be used as paths for sending user data. The configuration of each RB can be performed between the gNB108 and UE122's RRC308. Furthermore, the portion of the RB consisting of RLC304 and the Logical Channel can also be referred to as the RLC bearer. Additionally, relative to the NAS layer that transports signals between the AMF and UE122, some or all of the layers among PHY300, MAC302, RLC304, PDCP306, RRC308, and SDAP310 that transport signals and data between UE122 and gNB108 can be referred to as the AS (Access Strarum) layer.

[0081] The functional classification of MAC302, RLC304, PDCP306, SDAP310, and RRC308 described above is an example; it is not necessary to implement only some or all of the functions. Furthermore, some or all of the functions of each layer can also be included in other layers.

[0082] It should be noted that, as described in Non-Patent Document 2, the layer above the AS layer (not shown) can also be referred to as the PDU layer. The PDU layer can include the IP layer and any or all of the layers above the IP layer, such as the TCP (Transmission Control Protocol) layer, the UDP (User Datagram Protocol) layer, and other layers. The application layer can be above the PDU layer or included within the PDU layer. It should be noted that the PDU layer can be the AS layer above the user plane. Furthermore, the RRC layer and the NAS (non-access straw) layer can also be any or all of the layers above the SDAP layer and the PDCP layer (not shown). In other words, any or all of the SDAP layer and the PDCP layer can be the lower layer of the RRC layer, the NAS layer, the IP layer, and any or all of the layers above the IP layer, such as the TCP (Transmission Control Protocol) layer, the UDP (User Datagram Protocol) layer, and the application layer.

[0083] It should be noted that the physical layer, MAC layer, RLC layer, PDCP layer, and SDAP layer of the terminal device can be established, configured, and controlled through the RRC layer of the terminal device, or all of them. Furthermore, the RRC layer of the terminal device can establish and / or configure the physical layer, MAC layer, RLC layer, PDCP layer, and SDAP layer based on the RRC messages sent from the RRC layer of the base station device. Alternatively, the MAC layer, RLC layer, PDCP layer, and SDAP layer can be referred to as MAC sublayer, RLC sublayer, PDCP sublayer, and SDAP sublayer, respectively.

[0084] It should be noted that the AS layer or its functions, which are part or all of the AS layer configured in the terminal device and base station device, can also be referred to as entities. That is, the functions of the physical layer (PHY layer), MAC layer, RLC layer, PDCP layer, SDAP layer, and RRC layer, which are established, configured, and controlled in part or all of the terminal device and base station device, can be referred to as physical entities (PHY entities), MAC entities, RLC entities, PDCP entities, SDAP entities, and RRC entities, respectively. Furthermore, each layer may include one or more entities of that layer. Additionally, PDCP entities and RLC entities can be established, configured, and controlled on a per-radio-bearer basis, or all of them. Furthermore, MAC entities can be established, configured, and controlled on a per-cell-group basis, or all of them. Furthermore, SDAP entities can be established, configured, and controlled on a per-PDU-session basis, or all of them.

[0085] It should be noted that, in the various embodiments of the present invention, to distinguish between the E-UTRA protocol and the NR protocol, MAC202, RLC204, PDCP206, and RRC208 will be referred to as E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively. Furthermore, MAC302, RLC304, PDCP306, and RRC308 will be referred to as NR MAC, NR RLC, NR RLC, and NR RRC, respectively. Alternatively, spaces may be used to represent terms such as E-UTRA PDCP or LTE PDCP, NR PDCP, etc.

[0086] In addition, such as Figure 1 As shown, eNB102, gNB108, EPC104, and 5GC110 can be connected via interfaces 112, 116, 118, 120, and 114. Therefore, to accommodate various communication systems, Figure 2 RRC208 can be replaced with Figure 3 RRC308. In addition, Figure 2 PDCP206 can also be replaced with Figure 3 PDCP306. In addition... Figure 3 The RRC308 may include Figure 2 The functions of RRC208. In addition. Figure 3 PDCP306 can be Figure 2PDCP206. Furthermore, in E-UTRA100, even when UE122 is communicating with eNB102, NR PDCP can be used as the PDCP.

[0087] Next, the state transitions of UE122 in LTE and NR will be explained. When an RRC connection has been established, UE122 connected to the EPC or 5GC can be in the RRC_CONNECTED state. The state of having an RRC connection can include UE122 maintaining some or all of the UE context described later. Furthermore, the state of having an RRC connection can also include UE122 being able to send and / or receive unicast data. Additionally, UE122 can be in the RRC_INACTIVE state when the RRC connection is terminated (if UE122 is connected to the 5GC). If these conditions are not met, UE122 can be in the RRC_IDLE state.

[0088] It should be noted that UE122 connected to the EPC does not have the RRC_INACTIVE state, but it can initiate the termination of the RRC connection via E-UTRAN. In this case, when the RRC connection is terminated, UE122 retains the UE's AS context and the resumeIdentity for recovery and transitions to the RRC_IDLE state. If UE122 retains the UE's AS context and permits the recovery of the RRC connection via E-UTRAN, and UE122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state, the recovery of the terminated RRC connection can be initiated via a higher layer (e.g., the NAS layer).

[0089] That is, the definition of abort can be different for UE122 connected to EPC and UE122 connected to 5GC. In addition, the process of UE122 recovering from abort can be wholly or partially different in the case of UE122 connected to EPC (aborted in RRC_IDLE state) and the case of UE122 connected to 5GC (aborted in RRC_INACTIVE state).

[0090] It should be noted that the RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE states can be referred to as connected mode, inactive mode, and idle mode, respectively. They can also be referred to as RRC connected mode, RRC inactive mode, and RRC idle mode.

[0091] The AS context of the UE maintained by UE122 may include all or part of the following information: the current RRC settings, 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 PCell of the connection source, the cell identifier, and the physical cell identifier of the PCell of the connection source. It should be noted that the AS context of the UE maintained by either or both of eNB102 and gNB108 may include the same information as the AS context of the UE maintained by UE122, or it may include information different from the information included in the AS context of the UE maintained by UE122.

[0092] Figure 4 This is a diagram illustrating an example of the flow of procedures for various settings in RRC208 and / or (and / or) RRC308 of various embodiments of the present invention. Figure 4 This is an example of a procedure in which an RRC message is sent from a base station device (eNB102 and / or gNB108) to a terminal device (UE122).

[0093] exist Figure 4In step S400, the base station device generates an RRC message. The generation of the RRC message in the base station device can occur when the base station device distributes broadcast information (SI: System Information) or paging information, or when it is determined that the base station device needs to process a specific terminal device, such as security-related settings, resetting of the RRC connection (processing of wireless bearers (establishment, modification, release, etc.), processing of cell groups (establishment, addition, modification, release, etc.), determination settings, handover settings, etc.), and release of the RRC connection status. The RRC message includes information (parameters) used for various information notifications and settings. In specifications related to RRC (Non-Patent Document 8, Non-Patent Document 9), these parameters are referred to as fields and / or information elements, expressed using the ASN. 1 (Abstract Syntax Notation One) notation.

[0094] RRC messages can also be created for other purposes. For example, RRC messages can be used for settings related to Dual Connectivity (DC) and Multi-Radio Dual Connectivity (MR-DC).

[0095] exist Figure 4 Next, the base station device sends the created RRC message to the terminal device (step S402). Then, the terminal device processes the received RRC message if necessary (step S404).

[0096] Dual Connectivity (DC) can refer to the following technology: utilizing the radio resources of two cell groups (nodes) composed of two base station devices: a Master Cell Group (MCG) composed of a Master Node (MN) and a Secondary Cell Group (SCG) composed of Secondary Nodes (SN) for data communication. Furthermore, the Master Node and Secondary Node can be the same node (the same base station device). Additionally, MR-DC can refer to the following technology: cell grouping of cells in both E-UTRA and NR RATs (Radio Access Technology) according to each RAT and allocating them to the UE, utilizing the radio resources of both the MCG and SCG for data communication. In MR-DC, the Master Node can refer to a base station with the main RRC functions of MR-DC, such as adding secondary nodes, establishing, modifying, and releasing RBs, adding, modifying, releasing, and handover of MCGs, while the Secondary Node can refer to a base station with some RRC functions, such as modifying and releasing SCGs.

[0097] In MR-DC, the RRC of the RAT on the master node side can be used for both MCG and SCG configuration. For example, in the EN-DC (E-UTRA-NR Dual Connectivity) of MR-DC with core network EPC104 and master node eNB102 (also known as extended eNB102), and in the NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity) of MR-DC with core network 5GC110 and master node eNB102, E-UTRA RRC messages can be sent and received between eNB102 and UE122. In this case, the RRC message can include not only LTE (E-UTRA) configuration information but also NR configuration information. Furthermore, RRC messages sent from eNB102 to UE122 can also be sent from eNB102 to UE122 via gNB108. In addition, this RRC message can also be used for non-MR-DC, i.e., eNB102 (extended eNB) using 5GC as the core network for E-UTRA / 5GC.

[0098] Conversely, in MR-DC, specifically in NE-DC (NR-E-UTRA Dual Connectivity) where the core network is 5GC110 and the master node is gNB108, NR RRC messages can be sent and received between gNB108 and UE122. In this case, the RRC message can include not only NR configuration information but also LTE (E-UTRA) configuration information. Furthermore, RRC messages sent from gNB108 to UE122 can also be sent from gNB108 to UE122 via eNB102.

[0099] It should be noted that, not limited to the use of MR-DC, the E-UTRA RRC message sent from eNB102 to UE122 may include the NR RRC message, and the NR RRC message sent from gNB108 to UE122 may include the E-UTRA RRC message.

[0100] Figure 7 It means Figure 4 An example of a partial or complete representation of ASN.1 in a message related to RRC connection resetting in NR, including fields and information elements related to cell group settings. Furthermore, Figure 8 It means Figure 4 An example of some or all of the ASN.1 representations in the fields and information elements related to cell group settings included in a message relating to RRC connection resetting in E-UTRA. Not limited to... Figure 7 , Figure 8 In the examples of ASN.1 in the embodiments of the present invention, <omitted> and <omitted in the middle> indicate the omission of other information, rather than the omission of a part of the ASN.1 statement. It should be noted that information elements may also be omitted where there is no mention of <omitted> or <omitted in the middle>. It should be noted that in the embodiments of the present invention, the examples of ASN.1 do not correctly follow the ASN.1 representation method, but rather represent an example of parameters of a message related to the resetting of an RRC connection in the embodiments of the present invention, and other names and other expressions may also be used. In addition, in order to avoid complicating the description, the examples of ASN.1 only represent examples of key information closely related to one aspect of the present invention. It should be noted that sometimes the parameters expressed by ASN.1 are not distinguished from fields, information elements, etc., but are all referred to as information elements. In addition, in the embodiments of the present invention, the parameters such as fields and information elements included in the RRC message expressed by ASN.1 are sometimes referred to as information. It should be noted that the message related to the resetting of the RRC connection can refer to the RRC resetting message in NR or the RRC connection resetting message in E-UTRA.

[0101] exist Figure 7 In the RRCReconfiguration message, the radioBearerConfig can include radio bearer settings. The masterCellGroup can include MCG-related settings when the MCG is NR. The secondaryCellGroup can include SCG-related settings for notifications from the SCG cell to the terminal device. The mrdc-SecondaryCellGroupConfig can include SCG-related settings for notifications from the MCG cell to the terminal device.

[0102] The masterCellGroup, secondaryCellGroup, and / or mrdc-SecondaryCellGroupConfig mentioned above may include CellGroupConfig information elements as values.

[0103] The CellGroupConfig information element can include settings related to cell groups. The cellGroupId included in the CellGroupConfig information element can include information used to identify the cell group. mac-CellGroupConfig can include settings related to the MAC layer of the cell group. spCellConfig can include settings related to spCells. sCellToAddModList can include settings related to adding or changing SCells belonging to the cell group. sCellToReleaseList can include information related to deleting SCells belonging to the cell group.

[0104] exist Figure 8The RRCConnectionReconfiguration message includes the following: sCellToReleaseList-r10 may include information related to the deletion of SCells belonging to the MCG. sCellToAddModList-r10 may include settings related to the addition or modification of SCells belonging to the MCG. scg-Configuration-r12 may include settings related to the SCG. scg-ConfigPartSCG-r12, included in scg-Configuration-r12, may include settings related to the SCG's SpCells (pSCellToAddMod-r12, etc.), settings related to the addition or modification of SCells belonging to the cell group (sCellToAddModListSCG-r12, etc.), and / or information related to the deletion of SCells belonging to the cell group (sCellToReleaseListSCG-r12, etc.). Furthermore, settings related to the addition or modification of SCells during handover and / or the addition or modification of SCells when adding SCells may include information indicating the initial state of the SCell. For example, information indicating either an activated or dormant state can be included in the RRC message. With this information included, the initial state of the SCell can be set to either activated or dormant. Without this information, the initial state of the SCell can be set to deactivated.

[0105] It should be noted that the above fields and information elements may also be used for purposes other than those described above.

[0106] The terminal device that receives the RRC message containing the above information from the base station device sets the SpCell (PCell) of the MCG, the SCell of the MCG, the SpCell (PSCell) of the SCG, and / or the SCell of the SCG based on the information.

[0107] The terminal device can use a certain type of reference signal (e.g., cell-specific reference signal (CRS)) in the serving cell (e.g., PCell and / or PSCell) for radio link monitoring. Furthermore, the terminal device can receive a setting (RadioLinkMonitoringConfig) from the base station indicating which reference signal to use for radio link monitoring in the serving cell (e.g., PCell and / or PSCell), and use one or more of the set reference signals (here referred to as RLM-RS) for radio link monitoring. Alternatively, the terminal device can also use other signals for radio link monitoring. The physical layer processing unit of the terminal device can notify the upper layer of synchronization if the conditions for synchronization are met in the serving cell (e.g., PCell and / or PSCell).

[0108] The wireless link monitoring settings may include information indicating the purpose of monitoring and identifier information indicating reference signals. For example, the purpose of monitoring may include monitoring for wireless link failures, monitoring for beam failures, or bilateral objectives. Furthermore, for example, the identifier information indicating reference signals may include information indicating the identifier (SSB-Index) of the cell's Synchronization Signal Block (SSB). That is, the reference signal may include a synchronization signal. Additionally, for example, the identifier information indicating reference signals may include information indicating an identifier associated with the Channel State Information Reference Signal (CSI-RS) set on the terminal device.

[0109] In each SpCell (PCell in MCG and PSCell in SCG), the RRC layer processing unit of the terminal device can start or restart the timer (T310) of that SpCell if it receives a synchronization notification from the physical layer processing unit a predetermined number of times (N310 times) consecutively. Furthermore, the RRC layer processing unit of the terminal device can stop the timer (T310) of that SpCell if it receives synchronization notification a predetermined number of times (N311 times) consecutively. When the timer (T310) of each SpCell expires, if the SpCell is a PCell, the RRC layer processing unit of the terminal device can perform a transition to an idle state or a re-establishment of the RRC connection. Furthermore, if the SpCell is a PSCell, an SCG failure information procedure can be executed to notify the network of SCG failures.

[0110] The above description is an example of the case where DRX (Discrete Reception Optimization) is not set for the terminal device. When DRX is set for the terminal device, the RRC layer processing unit of the terminal device can set the period for measuring radio link quality and the notification interval to the upper layer for the physical layer processing unit to take values ​​different from those when DRX is not set. It should be noted that even when DRX is set, while the timer mentioned above is running, the period for measuring radio link quality used to estimate synchronization and the notification interval to the upper layer can be set to the values ​​when DRX is not set.

[0111] Furthermore, the RLM-RS can be undefined if it is not explicitly or implicitly configured by the network. That is, if the RLM-RS is not configured by the network (e.g., a base station device), the terminal device may not perform radio link monitoring.

[0112] In addition, wireless link monitoring using CRS can be performed in EUTRA cells, and wireless link monitoring using RLM-RS can be performed in NR cells, but it is not limited to these.

[0113] The activation and deactivation of cells are explained. Terminal devices communicating via dual connectivity configure the primary cell group (MCG) and secondary cell group (SCG) using messages related to the reconfiguration of the RRC connection described above. Each cell group can consist of a special cell (SpCell) and zero or more other cells (SCells). The SpCell of an MCG is also called a PCCell. The SpCell of an SCG is also called a PSCell. Cell deactivation does not apply to SpCells but can apply to SCells.

[0114] Furthermore, cell disabling does not apply to PCCells but can be applied to PSCells. In this case, cell disabling can be handled differently in SpCells and SCells.

[0115] As shown in Non-Patent Documents 6 and 7, cell activation and deactivation can be handled by a MAC entity existing in each cell group. SCells configured on the terminal device can be activated and / or deactivated by (A) and / or (B) as described below.

[0116] (A) indicates the reception of the MAC CE that is activated / disabled in SCell.

[0117] (B) Timer set per SCell without a PUCCH (sCellDeactivationTimer)

[0118] Specifically, the terminal device can perform the following processing (AD) for each SCell set by the MAC entity in the cell group.

[0119] (Processing AD)

[0120] If a MAC CE is received to activate the SCell, proceed (AD-1). Otherwise, if a MAC CE is received to disable the SCell, or if the timer (sCellDeactivationTimer) in an active SCell expires, proceed (AD-2). If uplink grant or downlink allocation is notified via the PDCCH of an active SCell, or uplink grant or downlink allocation for an active SCell is notified via the PDCCH of a serving cell, or a MAC PDU is sent in an established uplink grant, or a MAC PDU is received in an established downlink allocation, then the timer (sCellDeactivationTimer) associated with that SCell is restarted. If the SCell is disabled, proceed (AD-3).

[0121] (Process AD-1)

[0122] To make the SCell active, apply (implement) some or all of the usual SCell operations described in (A) through (E) below.

[0123] (A) Transmit the probe reference signal (SRS) in the SCell.

[0124] (B) Report the Channel State Information (CSI) used for this SCell.

[0125] (C) Monitor the PDCCH in this SCell

[0126] (D) Monitor the PDCCH for this SCell (the scheduling of this SCell in other serving cells).

[0127] (E) If PUCCH is set, send the PUCCH in this SCell.

[0128] In addition, if the SCell is disabled in the NR before the active MAC CE is received, then some or all of (A) to (B) below shall be implemented.

[0129] (A) Activate the BWP represented by the identifier (firstActiveDownlinkBWP-Id) of the downlink BWP set via RRC message.

[0130] (B) Activate the BWP represented by the identifier (firstActiveUplinkBWP-Id) of the uplink BWP set via RRC message.

[0131] In addition, a timer (sCellDeactivationTimer) is established for starting or (if already started) restarting the SCell.

[0132] (Process AD-2)

[0133] Disable the SCell.

[0134] In addition, the timer (sCellDeactivationTimer) corresponding to this SCell is stopped.

[0135] Disable all active BWPs associated with this SCell.

[0136] The buffer corresponding to the HARQ established with the SCell is refreshed.

[0137] (Processing AD-3)

[0138] Implement some or all of (A) through (D) below.

[0139] (A) No SRS is sent in this SCell.

[0140] (B) Do not report CSI for this SCell.

[0141] (C) Do not send PUCCH, UL-SCH and / or RACH in this SCell.

[0142] (D) Do not monitor the PDCCH of the SCell and / or the PDCCH for the SCell.

[0143] As described above, the MAC entity performs processing (AD), thereby activating and disabling the SCell.

[0144] In addition, as mentioned above, the initial state of an SCell can be set via an RRC message when appending an SCell.

[0145] Here, we will explain the timer (sCellDeactivationTimer). For SCells without a PUCCH, the value of the timer (sCellDeactivationTimer) (information related to the time considered to have expired) can be notified via an RRC message. For example, if the information indicating that 40ms is the value of the timer (sCellDeactivationTimer) is notified via an RRC message, in the above processing (AD), if the timer has not stopped after the notified time (in this case, 40ms) has elapsed after starting or restarting the timer, it is considered to have expired.

[0146] Here, we will explain the partial bandwidth (BWP).

[0147] A BWP can be a portion or the entire frequency band of the serving cell. Furthermore, a BWP can be called a carrier BWP. One or more BWPs can be configured on a terminal device. A particular BWP can be configured using information included in the broadcast information corresponding to the synchronization signal detected by the initial cell search. Alternatively, a particular BWP can be configured with a frequency bandwidth corresponding to the frequency used for the initial cell search. Furthermore, a particular BWP can be configured using RRC signaling (e.g., dedicated RRC signaling). Additionally, downlink BWPs (DL BWPs) and uplink BWPs (ULBWPs) can be configured individually. Furthermore, one or more uplink BWPs can correspond to one or more downlink BWPs. Moreover, the correspondence between uplink and downlink BWPs can be a predetermined correspondence, a correspondence implemented by RRC signaling (e.g., dedicated RRC signaling), a correspondence implemented by physical layer signaling (e.g., downlink control information (DCI) notified by the downlink control channel), or a combination of these.

[0148] A BWP can be composed of a group of consecutive Physical Resource Blocks (PRBs). Furthermore, parameters of the BWPs (one or more BWPs) for each component carrier can be configured for a connected terminal device. The parameters of the BWPs for each component carrier can include some or all of the following: (A) the type of cyclic prefix; (B) the subcarrier spacing; (C) the frequency position of the BWP (e.g., the start position or center frequency position of the low-frequency side of the BWP) (the frequency position can be, for example, an ARFCN, or an offset from a specific subcarrier of the serving cell. Furthermore, the unit of the offset can be a subcarrier unit or a resource block unit. Additionally, both the ARFCN and the offset may be configured); (D) the bandwidth of the BWP (e.g., the number of PRBs); (E) resource setting information for control signals; and (F) the center frequency position of the SS block (the frequency position can be, for example, an ARFCN, or an offset from a specific subcarrier of the serving cell. Furthermore, the unit of the offset can be a subcarrier unit or a resource block unit. Additionally, both the ARFCN and the offset may be configured). In addition, the resource setting information for the control signals can be included in at least some or all of the BWP settings in the PCell and / or PSCell.

[0149] The terminal device can transmit and receive data using one or more active BWPs among a set of configured BWPs. The terminal device can be configured to have at most one uplink BWP and / or at most one downlink BWP active at any given time among one or more BWPs configured for a serving cell. The active downlink BWP is called an Active DL BWP. The active uplink BWP is called an Active UL BWP.

[0150] Next, the disabling of BWPs will be explained. A serving cell can have one or more BWPs configured. BWP switching of a serving cell is used to activate disabled BWPs (also known as inactive BWPs) and disable activated BWPs.

[0151] BWP handover is controlled by the MAC entity itself and is used to indicate the start of downlink allocation or uplink authorization via PDCCH, timer (bwp-InactivityTimer), RRC signaling, or random access procedure. Activation of the serving cell's BWP is indicated by RRC or PDCCH.

[0152] Next, the Dormant BWP will be explained. Entering or leaving a Dormant BWP is accomplished by BWP switching. This control is performed via PDCCH on a per-SCell basis or on a per-group basis called a Dormant SCell Group. The Dormant SCell Group is set by RRC signaling. Furthermore, in the existing specification, the Dormant BWP only applies to a SCell. It should be noted that a Dormant BWP can be interpreted as not changing a specific BWP into a Dormant state, but rather as one of one or more BWPs configured for the UE that is set for Dormant use. Moreover, there can be multiple BWPs configured for Dormant use by the UE.

[0153] A dormant BWP can be indicated by omitting specific parameters in its settings. For example, a dormant BWP can be indicated by omitting the PDCCH-Config information element, which is included in the downlink BWP settings as an information element for setting UE-specific PDCCH parameters. Alternatively, a dormant BWP can be indicated by omitting (or not omitting) a portion of the parameters included in the PDCCH-Config information element, which is included in the downlink BWP settings as an information element for setting UE-specific PDCCH parameters. For example, a dormant BWP can also be indicated by omitting (or not omitting) some or all of the settings related to the search space for where and / or how to search for PDCCH candidates, which are set by the PDCCH-Config information element as a BWP setting.

[0154] Furthermore, the existing specifications do not support setting a sleep BWP for PCell, PSCell, and other SpCells, as well as PUCCH SCells that can send PUCCH messages.

[0155] The UE activation signal received via SpCell indicates that it has exited the dormant BWP outside of a pre-defined period (activation time) and is represented by the first downlink BWP identifier, which is pre-notified via RRC signaling.

[0156] The UE activation signal received via SpCell indicates that it has exited the dormant BWP during a pre-defined period (activation time) and is represented by the second downlink BWP identifier, which is pre-notified via RRC signaling.

[0157] Upon receiving a PDCCH indicating that it has entered a dormant BWP, the UE activates the downlink BWP represented by the third downlink BWP identifier (dormantDownlinkBWP-Id) that was previously notified via RRC signaling.

[0158] The aforementioned entry and exit from a dormant BWP is performed through BWP switching. When activating a new BWP, the previously active BWP is disabled. That is, when exiting a dormant BWP, the dormant BWP is disabled, and when entering a dormant BWP, the dormant BWP is activated.

[0159] Here, we will explain the PDCCH that indicates entering a hibernation BWP and the PDCCH that indicates exiting a hibernation BWP.

[0160] For example, a UE configured with Intermittent Receive (DRX) in the SpCell can monitor the PDCCH through the Active BWP of the SpCell to detect a certain DCI format (e.g., DCI format 2_6) outside the DRX activation time. The CRC of the DCI format can be scrambled using a certain RNTI (e.g., PS-RNTI). A UE configured with a dormant SCell group determines the handover of the Active DL BWP based on the bitmap information included in the payload of DCI format 2_6. For example, a bit of the bitmap can be associated with a dormant SCell group. When the bit is 1, if the Active DL BWP is a dormant BWP, a BWP handover is performed on other pre-configured BWPs; if the Active DL BWP is not a dormant BWP, it remains in that BWP. Alternatively, a BWP handover can be performed when the bit is 0, so that the Active DL BWP becomes a dormant BWP.

[0161] The UE may also perform PDCCH monitoring for the purpose of DCI format 2_6 detection without the DRX activation time.

[0162] UEs configured with Intermittent Receive (DRX) in the SpCell can monitor the PDCCH through the Active BWP of the SpCell, used to detect a specific DCI format (e.g., DCI formats 0_1 and 1_1) during the DRX activation time. The CRC of the DCI format can be scrambled using a specific RNTI (e.g., C-RNTI or MCS-C-RNTI). UEs configured with a dormant SCell group determine the handover 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 bit of the bitmap can be associated with a dormant SCell group. When the bit is 1, if the Active DL BWP is a dormant BWP, a BWP handover is performed on other pre-configured BWPs; if the Active DL BWP is not a dormant BWP, it remains in that BWP. Alternatively, a BWP handover can be performed when the bit is 0, making the Active DL BWP a dormant BWP. Furthermore, the “pre-defined other BWP” may be a different BWP from the “pre-defined other BWP” used in the description of DCI format 2_6.

[0163] The UE may also perform PDCCH monitoring for the purpose of detecting DCI format 0_1 ​​and DCI format 1_1 outside of the DRX activation time.

[0164] Monitoring the PDCCH that exits the dormant BWP can refer to monitoring the PDCCH for the purpose of detection in DCI format 2_6 outside the DRX activation time, or monitoring the PDCCH for the purpose of detection in DCI format 0_1 ​​and DCI format 1_1 during the DRX activation time.

[0165] In each active serving cell where a BWP is configured, if the BWP is activated (as an Active BWP) and is not a dormant BWP, the MAC entity performs some or all of the following (A) to (H).

[0166] (A) Send UL-SCH via this BWP.

[0167] (B) If a PRACH timing is set, then RACH is sent through this BWP.

[0168] (C) Monitor PDCCH through this BWP.

[0169] (D) If PUCCH is set, then PUCCH is sent through this BWP.

[0170] (E) Report to CSI via this BWP.

[0171] (F) If SRS is set, then SRS is sent through this BWP.

[0172] (G) Receive DL-SCH through the BWP.

[0173] (H) Initialize the configured uplink license of license type 1 that is suspended by this BWP setting.

[0174] In each active serving cell where a BWP is configured, if the BWP is activated (as an Active BWP) or is a dormant BWP, the MAC entity performs some or all of the following (A) to (G).

[0175] (A) If the timer (bwp-InactivityTimer) of the serving cell of the BWP is running, stop it.

[0176] (B) Do not monitor the PDCCH of this BWP.

[0177] (C) The PDCCH used for this BWP is not monitored.

[0178] (D) Do not receive DL-SCH in this BWP.

[0179] (E) If a CSI measurement is set, the CSI measurement is performed through this BWP.

[0180] (F) Stop all uplink behavior. That is, stop uplink transmission, suspend the configured uplink licenses of license type 1 associated with the cell, and clear the configured uplink licenses of license type 2 associated with the cell.

[0181] (G) If settings related to beam failure are set, then beam failure is detected. If beam failure is detected, then beam failure recovery is performed.

[0182] If BWP is disabled, the MAC entity performs some or all of the following (A) to (I).

[0183] (A) Do not send UL-SCH in this BWP.

[0184] (B) Do not send RACH in this BWP.

[0185] (C) PDCCH is not monitored in this BWP.

[0186] (D) Do not send PUCCH in this BWP.

[0187] (E) CSI is not reported in this BWP.

[0188] (F) Do not send SRS in this BWP.

[0189] (G) Do not receive DL-SCH in this BWP.

[0190] (H) Clear the configured uplink authorization for authorization type 2 set in this BWP.

[0191] (I) Suspend the configured uplink license of license type 1 for the disabled BWP (inactive BWP).

[0192] Next, the random access procedure for a UE with BWP configured will be described. When the random access procedure begins in a serving cell, the MAC entity performs some or all of the following processes (A) to (E) on the carrier selected in that serving cell.

[0193] (A) If no resource (timing) for sending PRACH is set for the Active UL BWP, then (A1) the Active ULBWP is switched to the BWP represented by the RRC parameter (initialUplinkBWP), and (A2) if the serving cell is SpCell, the Active UL BWP is switched to the BWP represented by the RRC parameter (initialDownlinkBWP).

[0194] (B) If a resource (timing) for sending PRACH is set for the Active UL BWP, then if the serving cell is SpCell and the Active DL BWP and Active UL BWP do not have the same identifier (bwp-Id), the Active DLBWP will be switched to a BWP with the same identifier as the Active UL BWP.

[0195] (C) If a corresponding timer (bwp-InactivityTimer) is running with the Active DL BWP of the serving cell, then stop the timer.

[0196] (D) If the serving cell is SCell, then if a corresponding timer (bwp-InactivityTimer) established with the Active DL BWP of the SpCell is running, then stop the timer.

[0197] (E) Perform a random access procedure on the Active DL BWP of SpCell and the Active UL BWP of the serving cell.

[0198] Next, the timer (bwp-InactivityTimer) will be explained. The MAC entity performs the following (A) processing for each activated serving cell for which the timer (bwp-InactivityTimer) has been set.

[0199] (A) If the identifier of the default downlink BWP (defaultDownlinkBWP-Id) is set, and the Active DLBWP is not the BWP represented by the identifier (dormantDownlinkBWP-Id), or if the identifier of the default downlink BWP (defaultDownlinkBWP-Id) is not set, and the Active DL BWP is not the initialDownlinkBWP, then if the Active DL BWP is not the BWP represented by the identifier (dormantDownlinkBWP-Id), then the following processing (B) and (D) are performed.

[0200] (B) If a PDCCH addressing to C-RNTI or CS-RNTI representing downlink assignment or uplink grant is received via Active DL BWP, or if a PDCCH addressing to C-RNTI or CS-RNTI representing downlink assignment or uplink grant is received for Active DL BWP, or if a MAC PDU is sent via configured uplink grant, or if a MAC PDU is received via configured downlink assignment, then the following (C) processing is performed.

[0201] (C) If a random access procedure associated with the serving cell is not in progress, or if a random access procedure associated with the serving cell is in progress and is successfully completed by receiving a PDCCH addressed to the C-RNTI, then start or restart the bwp-InactivityTimer associated with the Active DL BWP.

[0202] (D) If the bwp-InactivityTimer associated with Active DL BWP expires, then proceed with the following (E) process.

[0203] (E) If defaultDownlinkBWP-Id is set, then BWP switching is performed on the BWP represented by defaultDownlinkBWP-Id; otherwise, BWP switching is performed on initialDownlinkBWP.

[0204] In addition, if the MAC entity receives a PDCCH for BWP switching and switches the Active DL BWP, the following (A) process is performed.

[0205] (A) If a default downlink BWP identifier (defaultDownlinkBWP-Id) is set, and the switched Active DL BWP is not represented by the identifier (dormantDownlinkBWP-Id), then start or restart the bwp-InactivityTimer associated with the Active DLBWP.

[0206] Next, the process of detecting and recovering beam failure will be explained.

[0207] The MAC entity can configure the beam failure recovery procedure for each serving cell via RRC. Beam failures are detected by counting beam failure instance notifications sent to the MAC entity from the lower layer (PHY layer). To detect beam failures, the MAC entity can perform some or all of the following processes (A), (B), and (C) in each serving cell.

[0208] (A) If a beam failure instance notification is received from the lower layer, start or restart the timer (beamFailureDetectionTimer) to increment the counter (BFI-COUNTER) by 1. If the value of BFI_COUNTER is above the set threshold (beamFailureInstanceMaxCount), then perform the following (A-1) processing.

[0209] (A-1) If the serving cell is SCell, then beam failure recovery (BFR) is triggered for that serving cell; otherwise, the random access procedure is started via SpCell.

[0210] (B) If the beamFailureDetectionTimer for the serving cell expires or if the settings of beamFailureDetectionTimer, beamFailureInstanceMaxCount and / or the reference signal used for beam failure detection are changed by the upper layer, then BFI_COUNTER is set to 0.

[0211] (C) If the serving cell is SpCell and the random access procedure is successfully completed, then BFI_COUNTER is set to 0, the beamfailureRecoveryTimer is stopped, and the beamfailure recovery procedure is considered to have been successfully completed. Otherwise, if the serving cell is SCell, and the PDCCH addressing the C-RNTI indicating a new uplink grant is disabled when receiving information for sending beamfailure recovery for the SCell (e.g., information included in the SCell BFR MACCE), then BFI_COUNTER is set to 0, the beamfailure recovery procedure is considered to have been successfully completed, and all beamfailure recoveries (BFRs) triggered for that serving cell are cancelled.

[0212] If at least one beam failure recovery (BFR) is triggered by the beam failure recovery process and is not canceled, the MAC entity performs the following (A) procedure.

[0213] (A) If the UL-SCH resource can include the SCell's BFR MAC CE and the sub-header based on the logical channel priority, then include the SCell's BFR MAC CE and the sub-header. Otherwise, if the UL-SCH resource can include the truncated SCell's BFR MAC CE and the sub-header based on the logical channel priority, then include the truncated SCell's BFR MAC CE and the sub-header. Otherwise, trigger a scheduling request for SCell beam failure recovery.

[0214] SCell hibernation is achieved by activating the hibernation BWP within that SCell. Furthermore, even when the SCell is in hibernation mode, CSI measurements, Automatic Gain Control (AGC), and beam control (beam management), including beam failure recovery, can still be performed within that SCell.

[0215] Next, the dormant function of SCG will be explained.

[0216] In LTE and / or NR, the state in which the SCG is in sleep mode can be included in the RRC_CONNECTED state.

[0217] In LTE and / or NR, the sleep state of an SCG can be a state in which the terminal device implements some or all of the states described in (A) to (E) below in the SpCell (PSCell) of that SCG.

[0218] (A) SRS is not sent in this SpCell.

[0219] (B) Do not report CSI for this SpCell.

[0220] (C) Do not send PUCCH, UL-SCH and / or RACH on the SpCell.

[0221] (D) Do not monitor the PDCCH of the SpCell and / or the PDCCH for the SpCell.

[0222] (E) No intermittent reception (DRX) is performed on this SpCell.

[0223] Furthermore, the SCG's dormant state can be a state in which some or all of the processes described in (A) to (E) and (F) to (H) below are being implemented.

[0224] (F) Set the BWP that is set to dormant in this SpCell to an active BWP.

[0225] (G) In the active hibernation BWP of this SpCell, only monitor the PDCCH indicating exiting the hibernation BWP.

[0226] (H) C-RNTI is not monitored via PDCCH in the active dormant BWP of this SpCell.

[0227] In LTE and / or NR, the terminal device can determine and / or execute SCG sleep mode based on some or all of the following (A) to (H). It should be noted that the messages and control elements in (A) to (F) below can be notified to the terminal device from a cell group outside the SCG.

[0228] The hibernation of an SCG can be referred to as entering a dormant SCG. Furthermore, the hibernation of an SCG can refer to the activation of a dormant BWP in the SpCell of that cell group.

[0229] (A) Receive an RRC message indicating that the SCG is in hibernation.

[0230] (B) Receive MAC control element indicating SCG to hibernate

[0231] (C) Receive an RRC message indicating that SpCell is in hibernation.

[0232] (D) Receive MAC control element indicating SpCell to hibernate

[0233] (E) Receive other RRC messages

[0234] (F) Receive other MAC control elements

[0235] (G) Timer related to SCG's hibernation expires

[0236] (H) Timer related to PSCell hibernation expires

[0237] In LTE and / or NR, the terminal device may determine and / or perform a resume from the SCG's sleep state based on some or all of the following (A) to (H). It should be noted that the messages and control elements in (A) to (F) below can be notified to the terminal device from a cell group outside the SCG.

[0238] Resuming from the dormant state of an SCG can also be referred to as leaving a dormant SCG. Furthermore, resuming from the dormant state of an SCG can refer to a BWP handover from a dormant BWP to another BWP (not a dormant BWP) within the SpCell of that cell group.

[0239] (A) Receive an RRC message indicating resumption from the SCG's hibernation state.

[0240] (B) Receive MAC control element indicating resumption from SCG's sleep state

[0241] (C) Receive an RRC message indicating resumption from the SpCell's hibernation state.

[0242] (D) Receive MAC control element indicating resumption from the SpCell's hibernation state

[0243] (E) Receive other RRC messages

[0244] (F) Receive other MAC control elements

[0245] (G) Timers related to SCG sleep mode

[0246] (H) Timers related to PSCell hibernation

[0247] The terminal device that is in hibernation while executing the SCG may perform some or all of the following processes (A) to (F) within the SCG.

[0248] (A) Disable all SCells.

[0249] (B) It is assumed that all timers (sCellDeactivationTimer) associated with the active SCell have expired.

[0250] (C) It is assumed that all timers (sCellDeactivationTimer) associated with the dormant SCell have expired.

[0251] (D) Do not start or restart all timers associated with SCell (sCellDeactivationTimer).

[0252] (E) Ignore the MAC CE that activates the SCell. For example, in the process (AD), if a MAC CE that activates the SCell is received, and the SCG is not in a sleep state (or is not in a sleep state of the SCG), the process (AD-1) is performed.

[0253] (F) Perform the process (AD-2). For example, in the process (AD), the process (AD-2) is performed when the SCG is instructed to hibernate (or is in a hibernation state).

[0254] The terminal device that performs the recovery from the hibernation state of the SCG can perform some or all of the following processes (A) to (C) in the SCG.

[0255] (A) To make all SCells active, perform process (AD-1).

[0256] (B) Set all SCells to remain disabled. Since they are not in a dormant state, for example, in the process (AD) described above, if a MAC CE is received that activates a SCell, the SCG is not indicated to be in a dormant state (or is not in a dormant state), so process (AD-1) can be performed.

[0257] (C) In the case of resuming from the dormant state of the SCG based on an RRC message, if the RRC message includes parameters related to random access for some or all of the SCells, then a random access procedure is initiated in the SCell of the target based on the parameters notified.

[0258] Figure 9 This is a diagram illustrating one example of an implementation method. Figure 9 In step S900, UE122 receives a message (RRC message) from eNB102 or gNB108 notifying SCG to be set to a dormant state (first state). Based on the notification, UE122 performs control to disable cells other than SpCell (second cell) of SCG (i.e., SCell).

[0259] Through the above actions, efficient state changes can be performed during the process of putting an SCG to sleep, without independently sending a MAC CE to change the state of the SCG's SCell to the disabled state. Furthermore, in the case of putting an SCG to sleep based on RRC messages, previously the initial state setting was performed at the RRC layer and the state change at the MAC layer. However, through the above actions, mismatches between the RRC layer indications and the MAC layer indications can be avoided, and SCG state changes can be performed efficiently.

[0260] Here, we will explain the PDCCH that indicates the exit of the hibernation BWP.

[0261] For example, when the SpCell is in a dormant state (the dormant BWP is active), the UE can monitor the PDCCH through the Active BWP of the SpCell to detect a certain DCI format (e.g., DCI format 2_6). The CRC of the DCI format can be scrambled using a certain RNTI (e.g., PS-RNTI). UEs with a dormant SCell group set up determine the handover 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 can be associated with a dormant SCell group. When the bit is 1, if the Active DL BWP is a dormant BWP, a BWP handover is performed on other pre-set BWPs; if the Active DL BWP is not a dormant BWP, it remains in that BWP. Alternatively, a BWP handover can be performed when the bit is 0, so that the Active DL BWP becomes a dormant BWP.

[0262] If the system is configured to receive intermittently via SpCell while in the SpCell sleep state, the UE can perform PDCCH monitoring for the purpose of DCI format 2_6 detection without the DRX activation time.

[0263] If a system with intermittent reception configured via the SpCell is in sleep mode, a UE with intermittent reception (DRX) configured in the SpCell can monitor the PDCCH via the Active BWP of the SpCell during the DRX activation time to detect a specific DCI format (e.g., DCI formats 0_1 and 1_1). The CRC of the DCI format can be scrambled using a specific RNTI (e.g., C-RNTI or MCS-C-RNTI). A UE with a sleep SCell group configured determines the handover 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 bit of the bitmap can be associated with a sleep SCell group. When the bit is 1, if the Active DL BWP is a sleep BWP, a BWP handover is performed on other pre-configured BWPs; if the Active DL BWP is not a sleep BWP, it remains in that BWP. Alternatively, a BWP handover can be performed when the bit is 0, making the Active DL BWP a sleep BWP. Furthermore, the “pre-defined other BWP” may be a different BWP from the “pre-defined other BWP” used in the description of DCI format 2_6.

[0264] The UE may also perform PDCCH monitoring for the purpose of detecting DCI format 0_1 ​​and DCI format 1_1 outside of the DRX activation time.

[0265] Monitoring the PDCCH that indicates the exit from dormant BWP can refer to monitoring the PDCCH for the purpose of detecting DCI format 2_6. In this case, monitoring the PDCCH for the purpose of detecting other DCI formats is not required.

[0266] If a system is configured for intermittent reception via the SpCell while the SpCell is in sleep mode, monitoring the PDCCH indicating the exit from sleep mode can refer to monitoring the PDCCH for DCI format 2_6 outside of the DRX activation time, and monitoring the PDCCH for DCI format 0_1 ​​and DCI format 1_1 during the DRX activation time. In this case, monitoring the PDCCH for other DCI formats is not required.

[0267] When an SCG is in a dormant state, all uplink transmissions can be stopped within that SCG. In this case, information related to that SCG can be transmitted in other cell groups (e.g., MCGs). Alternatively, information related to that SCG can be transmitted in the SCG that has exited the dormant state. Furthermore, when an SCG is in a dormant state, some or all uplink transmissions can be allowed within that SCG. An example of uplink transmission within an SCG when it is in a dormant state will be described here.

[0268] For example, beam failure recovery will be described in the case of beam control (beam management) including beam failure recovery in the SpCell of an SCG in a dormant state.

[0269] The MAC entity can configure the beam failure recovery procedure for each serving cell via RRC. It should be noted that in a dormant SCG, the beam failure recovery procedure can be configured and / or performed only in the SpCell; alternatively, it can be configured and / or performed in both the SpCell and some or all of the SCells. Beam failures are detected by counting beam failure instance notifications sent to the MAC entity from the lower layer (PHY layer). To detect beam failures, the MAC entity can perform some or all of the processes described in (A), (B), and (C) in each serving cell.

[0270] (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) to 1. If the value of BFI_COUNTER is above the set threshold (beamFailureInstanceMaxCount), then perform the following processing (A-1).

[0271] (A-1) If the serving cell is SCell, beam failure recovery (BFR) is triggered for that serving cell; otherwise, the random access procedure begins via SpCell. It should be noted that if beam failure recovery is not triggered at the SCell, beam failure recovery for the SCell may not be triggered here. That is, the process of starting the random access procedure at SpCell can be performed only if the serving cell is SpCell.

[0272] (B) If the beamFailureDetectionTimer for the serving cell expires or if the settings of beamFailureDetectionTimer, beamFailureInstanceMaxCount and / or the reference signal used for beam failure detection are changed by the upper layer, then BFI_COUNTER is set to 0.

[0273] (C) If the serving cell is SpCell and the random access procedure is successfully completed, then BFI_COUNTER is set to 0, the beamfailureRecoveryTimer is stopped, and the beamfailure recovery procedure is considered to have been successfully completed. Otherwise, if the serving cell is SCell, and the PDCCH addressing the C-RNTI indicating a new uplink grant is disabled when receiving information for sending beamfailure recovery for the SCell (e.g., information included in the SCell BFR MACCE), then BFI_COUNTER is set to 0, the beamfailure recovery procedure is considered to have been successfully completed, and all beamfailure recoveries (BFRs) triggered for that serving cell are cancelled.

[0274] If at least one beam failure recovery (BFR) is triggered through the beam failure recovery process and is not canceled, the MAC entity triggers a scheduling request for SCell beam failure recovery as needed.

[0275] When a scheduling request is triggered, if no valid PUCCH resource is set for a pending scheduling request, the MAC entity of the SCG begins a random access procedure in the SpCell.

[0276] As mentioned above, sometimes a random access procedure for a SpCell (PSCell) is initiated either by a scheduling request implemented by the MAC entity to send a MAC PDU including a MAC CE, or directly by the MAC entity in a dormant SCG. In this case, the MAC PDU may not include a MAC SDU.

[0277] In addition, on the other hand, sometimes the random access procedure of the SpCell (PSCell) can be started in the dormant SCG by triggering a scheduling request for a MAC PDU used to send data from the upper layer (MAC SDU), including user data, RRC messages, etc.

[0278] Here, in a SpCell of a certain cell group, the state capable of transmitting UL-SCH and RACH is set to a first state. The first state can be the state capable of transmitting RACH and / or monitoring PDCCHs addressed to C-RNTI, MCS-C-RNTI, and / or CS-RNTI representing uplink grants for UL-SCH transmission in the SpCell of the cell group. Alternatively, the first state can be the state where a first BWP is activated in the SpCell of the cell group, and PDCCHs addressed to C-RNTI, MCS-C-RNTI, and / or CS-RNTI representing uplink grants are monitored in the first BWP. Furthermore, the first state can also be the state where Channel State Information (CSI) measurement is performed for the first BWP. Additionally, the first state can also be the state where Intermittent Receive (DRX) is set.

[0279] Monitoring the status of the PDCCH addressed to the C-RNTI, MCS-C-RNTI, and / or CS-RNTI representing uplink grants for UL-SCH transmission can include a state where the Active BWP of the SpCell of the cell group is not a dormant BWP. Alternatively, the first state can also be a state where the cell group (SCG) has resumed from a dormant state. Furthermore, the first state can also be a state where the cell group (SCG) is not in a dormant state.

[0280] Furthermore, for example, the first state can be a state that transitions from the second state upon initiation of a random access procedure triggered by a scheduling request for sending a MAC PDU including a MAC SDU. Furthermore, for example, the first state can also be a state that transitions from the second state upon indication of resumption from a dormant state by an RRC entity. Furthermore, for example, the first state can be a state where the PDCCH indicating exit from the dormant BWP (exiting from the dormant BWP) is not monitored.

[0281] In a SpCell of a certain cell group, the state of stopping the transmission of UL-SCH and RACH is set to a second state. The second state can be a state where RACH is not transmitted in the SpCell of the cell group and / or where PDCCHs addressed to C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating uplink grants for UL-SCH transmission are not monitored. Alternatively, the second state can be a state where a second BWP is activated in the SpCell of the cell group, and in the second BWP, PDCCHs addressed to C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating uplink grants for UL-SCH transmission, as well as PDCCHs indicating exiting a dormant BWP, are not monitored. Furthermore, the second state can be a state where a second BWP is activated in the SpCell of the cell group, and in the second BWP, only PDCCHs indicating exiting a dormant BWP are monitored. Moreover, the second state can also be a state where Channel State Information (CSI) measurements are performed for the second BWP.

[0282] The second state can be that the SpCell's Active BWP is in a dormant BWP state.

[0283] In a SpCell of a cell group, the state in which limited UL-SCH and RACH transmissions can be performed is designated as the third state. The third state may be the state in which RACH transmissions can be performed in the SpCell of the cell group, and the PDCCH addressed to C-RNTI, MCS-C-RNTI, and / or CS-RNTI representing uplink grants is monitored for limited UL-SCH transmissions. The third state may be part of the first state in which the cell group (SCG) recovers from a dormant state, or it may be a different state from the first state in which the cell group (SCG) recovers from a dormant state.

[0284] For example, the third state could be a transition from the second state when a random access procedure triggered by a MAC entity begins. Furthermore, for example, the third state could also be a transition from the second state when the value of BFI_COUNTER exceeds a set threshold. Additionally, for example, the third state could be a transition from the second state when the value of BFI_COUNTER exceeds a set threshold and a random access procedure begins in the PSCell. Furthermore, for example, the third state could be a transition from the second state when the value of BFI_COUNTER exceeds a set threshold and a BFR is triggered in the SCell.

[0285] Furthermore, the third state can also be a state where a third BWP is activated in the SpCell of the cell group, and the state of the PDCCH indicating the exit from the dormant BWP is monitored in the third BWP. Moreover, the third state can also be a state where the PDCCH addressing the C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating uplink grant is not monitored in the third BWP. Furthermore, the third state can also be a state where Channel State Information (CSI) measurement is performed for the third BWP. If the UE receives a PDCCH indicating the exit from the dormant BWP for its local station in the third BWP, it can switch the BWP to a pre-set BWP (e.g., the first BWP).

[0286] Furthermore, for example, the third state could be a state transitioning from the second state upon the commencement of a random access procedure triggered by a scheduling request for transmitting a MAC PDU that does not include a MAC SDU. Furthermore, for example, the third state could also be a state transitioning from the second state upon the commencement of a random access procedure triggered by a scheduling request for transmitting a MAC PDU that includes a specific MAC CE. The specific MAC CE may include a BFR MAC CE. Furthermore, for example, the third state could also be a state transitioning from the second state when the MAC PDU including the specific MAC CE does not include a MAC SDU.

[0287] For example, such as Figure 10 As shown, the UE can determine whether to start the random access procedure in the SCG in the dormant state (step S1000), and if the random access procedure is started, switch the Active BWP to another BWP (e.g., the third BWP) (step S1002).

[0288] Furthermore, for example, the third state could be a state transitioned from the second state during a random access procedure for requesting uplink authorization.

[0289] The UE can independently configure a BWP (first BWP) that becomes active when recovering from the SCG's sleep state to the first state, a BWP that becomes active in the second state (second BWP), and a BWP that becomes active in the third state (third BWP). Furthermore, more than one BWP can be configured for each of the first, second, and third BWPs. Additionally, the first, second, and third BWPs can each be composed of downlink BWPs and / or uplink BWPs.

[0290] Transitioning to the first state and the first BWP becoming active can mean the same thing. Transitioning to the second state and the second BWP becoming active can mean the same thing. Transitioning to the third state and the third BWP becoming active can mean the same thing.

[0291] Transitioning to the first state can mean the same thing as a BWP other than the first BWP becoming disabled. Transitioning to the second state can mean the same thing as a BWP other than the second BWP becoming active. Transitioning to the third state can mean the same thing as a BWP other than the third BWP becoming active.

[0292] Some or all of the first to third BWPs can be configured for the UE via RRC messages. As mentioned above, the configuration of the second BWP may not include some or all of the parameters required for PDCCH monitoring. The configuration of the second BWP may also not include the configuration of the uplink BWP. The configuration of the third BWP may at least include the parameters required for PDCCH monitoring for receiving the response to the random access preamble (random access response). The configuration of the third BWP may include the configuration of the uplink BWP. The configuration of the uplink BWP may include the information required for the transmission of the random access preamble.

[0293] Furthermore, as another example, the SCG's dormant state can be the third state described above. That is, the SCG entering a dormant state and transitioning to the third state can be the same thing. In this case, the second state can be defined as another state different from the SCG's dormant state, or there may not be a second state.

[0294] Therefore, the required uplink transmissions can be triggered even when the SCG is in sleep mode. Furthermore, power can be saved by monitoring only the necessary signals while the SCG is in sleep mode.

[0295] This section explains the process of MCG failure. The purpose of this procedure may be to notify the network of the MCG failure encountered by the UE (i.e., MCG radio link failure). With SRB2's AS layer security active, a UE configured with at least one DRB and RRC_CONNECTED can initiate a high-speed MCG link recovery process to maintain the RRC connection without re-establishing it.

[0296] like Figure 11 As shown, a UE with a gap SRB1 or SRB3 set can start the process of reporting MCG failure (step S1102) when some or all of the following conditions (A) to (D) are met and condition (E) is met (step S1100).

[0297] (A) The transmissions of both MCG and SCG were not suspended.

[0298] (B) Timer T316 is set.

[0299] (C) SCG is not the fourth state

[0300] (D) The active BWP of SCG's SpCell is not a dormant BWP.

[0301] (E) When a wireless link failure of the MCG is detected while timer T316 is not running.

[0302] It should be noted that when the process of reporting MCG failures begins, MCG transmissions for all SRBs and DRBs except SRB0 are suspended. Similarly, when the process of reporting SCG failures begins, SCG transmissions for all SRBs and DRBs are suspended.

[0303] Timer T316 refers to a timer that starts when an MCG failure message is sent and stops when transmission resumes in the MCG, when an RRRCRelease message is received, or when the re-establishment process begins.

[0304] The fourth state can be a state in which a fourth BWP is activated in the SpCell of the cell group, and in which only the PDCCH indicating the exit of the dormant BWP is monitored, and the Channel State Information (CSI) measurement for the fourth BWP is performed. Alternatively, the fourth state can also be a state in which a fourth BWP is activated in the SpCell of the cell group, and in which C-RNTI is not monitored via PDCCH, and the Channel State Information (CSI) measurement for the fourth BWP is performed. Furthermore, the fourth state can be the third state described above.

[0305] When the process of reporting MCG failure begins, the UE will suspend the MCG transmission for all SRBs and DRBs except SRB0, reset the MAC of the MCG, and begin sending MCG failure information messages.

[0306] Therefore, the sleep state of the SCG can be considered to control the process of reporting MCG failures.

[0307] Furthermore, another example of MCG failure is illustrated. In this example, when the UE's active BWP for the SCG's SpCell is a dormant BWP, the transmission of the SCG is considered suspended.

[0308] When a UE with a set gap SRB1 or SRB3 meets some or all of the following conditions (A) to (B) and meets condition (C), it can transition to the third state or the first state to begin the process of reporting MCG failure.

[0309] (A) The transmissions of both MCG and SCG were not suspended.

[0310] (B) Timer T316 is set.

[0311] (C) When a wireless link failure of the MCG is detected while timer T316 is not running.

[0312] Therefore, the process of reporting MCG failures can be controlled without adding new conditions.

[0313] Figure 5 This is a block diagram illustrating the configuration of the terminal device (UE122) according to various embodiments of the present invention. It should be noted that, to avoid unnecessary detail, in... Figure 5 Only the main components closely related to one aspect of the invention are shown.

[0314] Figure 5 The UE122 shown comprises a receiving unit 500 that receives RRC messages from a base station device, a processing unit 502 that processes some or all of the setting information, such as various information elements, fields, and conditions included in the received messages, and a transmitting unit 504 that sends RRC messages to the base station device. The base station device mentioned above sometimes refers to eNB102 and sometimes to gNB108. Furthermore, the processing unit 502 may include some or all of the functions of various layers (e.g., physical layer, MAC layer, RLC layer, PDCP layer, RRC layer, and NAS layer). That is, the processing unit 502 may include some or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, RRC layer processing unit, and NAS layer processing unit.

[0315] Figure 6 This is a block diagram illustrating the configuration of a base station apparatus according to various embodiments of the present invention. It should be noted that, to avoid unnecessary detail, in... Figure 6 Only the main components closely related to one aspect of the invention are shown. The aforementioned base station device sometimes refers to eNB102 and sometimes to gNB108.

[0316] Figure 6The base station apparatus shown includes: a transmitting unit 600 that transmits RRC messages to UE 122; a processing unit 602 that generates RRC messages containing some or all of the configuration information including various information elements, fields, and conditions, and transmits them to UE 122 for processing by the processing unit 502 of UE 122; and a receiving unit 604 that receives RRC messages from UE 122. Furthermore, the processing unit 602 may include some or all of the functions of various layers (e.g., physical layer, MAC layer, RLC layer, PDCP layer, RRC layer, and NAS layer). That is, the processing unit 602 may include some or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, RRC layer processing unit, and NAS layer processing unit.

[0317] Furthermore, in the examples of processes or processes described above, some or all of the steps may not be performed. Furthermore, the order of the steps may differ in the examples of processes or processes described above. Furthermore, in the examples of processes or processes described above, some or all of the processes in each step may not be performed. Furthermore, the order of the processes in each step may differ in the examples of processes or processes described above.

[0318] Hereinafter, various embodiments of the terminal device according to the present invention will be described.

[0319] (1) A first embodiment of the present invention is a terminal device that sets a first cell group and a second cell group, the terminal device comprising: a detection unit that detects a radio link failure of the first cell group and / or the second cell group; and a control unit that starts a first process of reporting a radio link failure of the first cell group, the first process being started based on the fact that the transmission of the first cell group and the second cell group is not suspended, the second cell group is not in a first state, and the radio link failure of the first cell group is detected, the first state being a state in which a first BWP is activated in the SpCell of the cell group, and in the first BWP only the PDCCH indicating the exit of the dormant BWP is monitored and the measurement of channel state information (CSI) for the first BWP is performed.

[0320] (2) A second embodiment of the present invention is a method for a terminal device that has set a first cell group and a second cell group, the method comprising: a step of detecting a radio link failure of the first cell group and / or the second cell group; and a step of starting a first process of reporting a radio link failure of the first cell group, the first process being started based on the fact that transmissions of the first cell group and the second cell group are not suspended, the second cell group is not in a first state, and a radio link failure of the first cell group is detected, the first state being a state in which a first BWP is activated in the SpCell of the cell group, and in the first BWP only the PDCCH indicating the exit of the dormant BWP is monitored and the measurement of channel state information (CSI) for the first BWP is performed.

[0321] (3) A third embodiment of the present invention is an integrated circuit installed in a terminal device configured with a first cell group and a second cell group, the integrated circuit enabling the terminal device to perform the following functions: detecting radio link failures of the first cell group and / or the second cell group; and initiating a first process for reporting radio link failures of the first cell group, the first process being initiated based on the fact that transmissions of the first cell group and the second cell group are not suspended, the second cell group is not in a first state, and the radio link failure of the first cell group is detected, the first state being that a first BWP is activated in the SpCell of the cell group, and that only the PDCCH indicating the exit of the dormant BWP is monitored in the first BWP and a measurement of channel state information (CSI) for the first BWP is performed.

[0322] In one embodiment of the present invention, the program operating in the apparatus may be a program that controls the Central Processing Unit (CPU) or similar components to achieve the functions described in the above-described embodiments of the present invention, thereby enabling the computer to perform its functions. During processing, the program or the information processed by the program is temporarily read into volatile memory such as Random Access Memory (RAM) or stored in non-volatile memory such as Flash Memory or Hard Disk Drive (HDD), and is read, modified, or written by the CPU as needed.

[0323] It should be noted that a portion of the device described in the above embodiments can be implemented using a computer. In this case, the program for implementing the control function can be recorded on a computer-readable recording medium, and the control function can be implemented by reading the program recorded on the recording medium into a computer system and executing it. Here, "computer system" refers to a computer system built into the device, and is configured to include hardware such as an operating system and peripherals. Furthermore, the "computer-readable recording medium" can be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, etc.

[0324] Furthermore, a "computer-readable recording medium" can include: a medium that dynamically stores a program for a short period of time, such as a communication line in the case of transmitting a program via a network such as the Internet or a communication line such as a telephone line; or a medium that stores a program for a fixed period of time, such as volatile memory within a computer system that serves as a server or client in this case. In addition, the program can be a program used to implement the functions described above, or it can be a program that can implement the functions described above by combining with programs already recorded in the computer system.

[0325] Furthermore, the functional blocks or features of the apparatus used in the above embodiments can be implemented or executed by circuits, typically by integrated circuits or multiple integrated circuits. Circuits designed to perform the functions described in this specification may include: general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic elements, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general-purpose processor may be a microprocessor, or alternatively, a conventional processor, controller, microcontroller, or state machine. The general-purpose processor or the circuits described above may be constructed from digital circuits or analog circuits. Furthermore, in cases where advancements in semiconductor technology have led to the development of integrated circuit technologies that replace existing integrated circuits, integrated circuits based on such technologies may also be used.

[0326] It should be noted that the invention described in this application is not limited to the embodiments described above. While one example of the device is described in the embodiments, the invention is not limited thereto and can be applied to fixed or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other terminal devices or communication devices in daily life.

[0327] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the specific configuration is not limited to these embodiments, and design changes that do not depart from the spirit of the present invention are also included. Furthermore, various modifications can be made to one aspect of the present invention within the scope shown in the technical solution. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included within the technical scope of the present invention. In addition, configurations obtained by replacing elements that have the same effect as those described in the above embodiments are also included.

[0328] Industrial availability

[0329] One aspect of the present invention can be used, for example, in communication systems, communication devices (e.g., mobile phone devices, base station devices, wireless LAN devices, or sensor devices), integrated circuits (e.g., communication chips), or programs.

[0330] Explanation of reference numerals in the attached figures

[0331] 100 E-UTRA

[0332] 102 eNB

[0333] 104 EPC

[0334] 106 NR

[0335] 108 gNB

[0336] 110 5GC

[0337] 112, 114, 116, 118, 120, 124 interfaces

[0338] 122 UE

[0339] 200, 300 PHY

[0340] 202, 302 MAC

[0341] 204, 304 RLC

[0342] 206, 306 PDCP

[0343] 208, 308 RRC

[0344] 310 SDAP

[0345] 210, 312 NAS

[0346] 500, 604 Receiving Section

[0347] 502 and 602 processing departments

[0348] 504, 600 Sending Department.

Claims

1. A terminal device configured to communicate with a base station device using a primary cell group (MCG) and a secondary cell group (SCG), the terminal device comprising: The detection unit detects a wireless link failure between the MCG and the SCG; and The control unit initiates the first procedure for reporting the wireless link failure of the MCG, in which... The first process begins based on the assumption that the transmission of the MCG and the SCG is not suspended, the SCG is not in the first state, and the wireless link failure of the MCG is detected while timer T316 is not running. The SCG consists of primary and secondary cells (PSCells) and zero or more secondary cells (SCells). The first state is the following: All SCells of the SCG are disabled. The first BWP is activated in the PSCell of the SCG, and The physical downlink control channel is not monitored in the first BWP of the PSCell.

2. A communication method for a terminal device, the terminal device being configured to communicate with a primary cell group (MCG) and a secondary cell group (SCG), the method comprising: The steps for detecting wireless link failures in the MCG and SCG; and The steps of the first procedure to begin reporting the radio link failure of the MCG, wherein The first process begins based on the assumption that the transmission of the MCG and the SCG is not suspended, the SCG is not in the first state, and the wireless link failure of the MCG is detected while timer T316 is not running. The SCG consists of primary and secondary cells (PSCells) and zero or more secondary cells (SCells). The first state is the following: All SCells of the SCG are disabled. The first BWP is activated in the PSCell of the SCG, and The physical downlink control channel is not monitored in the first BWP of the PSCell.

Images