Terminal equipment, base station equipment, and method

Abstract

This terminal device, to which a master cell group and a secondary cell group are set, deems, on the basis of a specific value having been set for a first timer that is set by a base station device, that activation and / or deactivation of the secondary cell group initiated at the discretion of the terminal device is not permitted.

Description

Technical Field

[0001] The present invention relates to a terminal device, a base station device, and a method. This application claims priority to Japanese Patent Application No. 2021-62889, filed on April 1, 2021, the content of which is incorporated herein by reference.

Background Art

[0002] In the Third Generation Partnership Project (3GPP), which is a standardization project for cellular mobile communication systems, technical studies and standardization of cellular mobile communication systems, including radio access, core networks, services, etc., are being conducted.

[0003] For example, in 3GPP, E-UTRA (Evolved Universal Terrestrial Radio Access) was started for technical studies and standardization as a radio access technology (RAT) for cellular mobile communication systems for the 3.9th generation and 4th generation. Even now, in 3GPP, technical studies and standardization of extended technologies of E-UTRA are being conducted. Note that E-UTRA is also referred to as Long Term Evolution (LTE: registered trademark), and extended technologies may also be referred to as LTE-Advanced (LTE-A), LTE-Advanced Pro (LTE-A Pro). (Non-Patent Document 2, etc.)

[0004] Also, in 3GPP, NR (New Radio, or NR Radio access) was started for technical studies and standardization as a radio access technology (RAT) for cellular mobile communication systems for the 5th generation (5G). Even now, in 3GPP, technical studies and standardization of extended technologies of NR are being conducted. (Non-Patent Document 1, etc.)

Prior Art Documents

[0005] [Non-Patent Document 1] 3GPP TS 38.300 v16.2.0,"NR;NR and NG-RAN Overall description; Stage 2" pp10-134 [Non-Patent Document 2] 3GPP TS 36.300 v16.2.0,"Evolved Universal Terrestrial Radio Access (E-UTRA)and Evolved Universal Terrestrial Radio Access Network (E-UTRAN);Overall description; Stage 2" pp19-361 [Overview of the Initiative] [Problems that the invention aims to solve]

[0006] As an extension of NR (New Radio), dual connectivity (also called multi-connectivity) technology enables high-capacity data communication by using multiple cell groups, allowing one or more base station devices and terminal devices to communicate. In this dual connectivity, terminal devices need to monitor each cell group for the presence of messages addressed to them in order to communicate within each cell group. Terminal devices need to constantly monitor multiple cell groups to enable low-latency communication when high-capacity data communication occurs, which has the problem of consuming a lot of power. Therefore, technologies that allow monitoring of some cell groups to be performed at a low frequency or stopped (cell group deactivation technology) are being considered.

[0007] In addition to the operation of terminal devices in the inactive state of cell groups, the operation of terminal devices when they become active (recover) from the inactive state is also being investigated.

[0008] When a cell group is inactive, the terminal device must perform the necessary processing to enable communication as soon as the cell group becomes active.

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

[0010] To achieve the above objective, one aspect of the present invention employs the following means. That is, one aspect of the present invention is a terminal device for which a master cell group and a secondary cell group are set from a network, comprising: a receiving unit that receives an RRC message from the network including a value for a first timer; and a processing unit that processes based on the RRC message, wherein the processing unit determines that the activation and / or deactivation of the secondary cell group initiated by the terminal device is not permitted based on the setting of a specific value for the first timer, and based on the setting of a value other than the specific value for the second cell group, it starts or restarts the first timer, and based on the running of the first timer, it does not initiate the activation and / or deactivation of the second cell group initiated by the terminal device.

[0011] Furthermore, one aspect of the present invention is a method applied to a terminal device that configures a master cell group and a secondary cell group from a network, comprising the steps of receiving an RRC message from the network including a value for a first timer, and processing based on the RRC message, wherein the activation and / or deactivation of the secondary cell group initiated by the terminal device is deemed not permitted based on the setting of a specific value for the first timer, the first timer is started or restarted based on the setting of a value other than the specific value and the activation and / or deactivation of the secondary cell group, and the activation and / or deactivation of the secondary cell group initiated by the terminal device is not initiated based on the running of the first timer.

[0012] Another aspect of the present invention is an integrated circuit implemented in a terminal device that sets a master cell group and a secondary cell group from a network, wherein the terminal device is given the function of receiving an RRC message from the network including a value for a first timer and the function of processing based on the RRC message, and the activation and / or deactivation of the secondary cell group initiated by the terminal device is deemed not permitted based on the fact that a specific value is set for the first timer, and the activation and / or deactivation of the secondary cell group is to be performed based on the fact that a value other than the specific value is set for the first timer, and the activation and / or deactivation of the secondary cell group is to be performed, and the activation and / or deactivation of the secondary cell group initiated by the terminal device is not to be performed based on the fact that the first timer is running.

[0013] Another aspect of the present invention is a base station device that communicates with a terminal device, comprising a processing unit that generates an RRC message including a value of a first timer, and a transmitting unit that transmits the RRC message to the terminal device, wherein the processing unit indicates to the terminal device that it does not permit the activation and / or deactivation of a secondary cell group initiated by the terminal device, based on setting a specific value for the first timer.

[0014] Another aspect of the present invention is a method applied to a base station device that communicates with a terminal device, comprising the steps of generating an RRC message including a value for a first timer, and transmitting the RRC message to the terminal device, thereby indicating to the terminal device that it is not permitted to activate and / or deactivate a secondary cell group, which is initiated by the terminal device based on setting a specific value for the first timer.

[0015] Another aspect of the present invention relates to an integrated circuit implemented in a base station device that communicates with a terminal device, wherein the base station device is given the function of generating an RRC message including a value of a first timer and the function of transmitting the RRC message to the terminal device, and the terminal device is instructed not to allow the activation and / or deactivation of a secondary cell group initiated by the terminal device based on setting a specific value in the first timer.

[0016] These comprehensive or specific embodiments may be implemented as systems, devices, methods, integrated circuits, computer programs, or recording media, or as any combination of systems, devices, methods, integrated circuits, computer programs, and recording media. [Effects of the Invention]

[0017] According to one aspect of the present invention, terminal devices, base station devices, methods, and integrated circuits can realize efficient communication control processing. [Brief explanation of the drawing]

[0018] [Figure 1] Schematic diagram of a communication system according to an embodiment of the present invention. [Figure 2] Diagram of an example of an E-UTRA protocol configuration according to an embodiment of the present invention. [Figure 3] Diagram of an example of an NR protocol configuration according to an embodiment of the present invention. [Figure 4] Diagram showing an example of a flow of procedures for various settings in RRC according to an embodiment of the present invention. [Figure 5] Block diagram showing the configuration of a terminal device in an embodiment of the present invention. [Figure 6] Block diagram showing the configuration of a base station device in an embodiment of the present invention. [Figure 7] An example of an ASN.1 description included in a message related to reconfiguration of an RRC connection in NR in an embodiment of the present invention. [Figure 8] An example of an ASN.1 description included in a message related to reconfiguration of an RRC connection in E-UTRA in an embodiment of the present invention. [Figure 9] An example of an ASN.1 description of an RRC reconfiguration message in an embodiment of the present invention. [Figure 10] An example of an ASN.1 description of a cell group configuration information element in an embodiment of the present invention. [Figure 11] An example of an ASN.1 description of the configuration of a SpCell in an embodiment of the present invention. [Figure 12] An example of an ASN.1 description of a synchronization reconfiguration information element in an embodiment of the present invention. [Figure 13] An example of an ASN.1 description of a ServingCellConfigCommon information element in an embodiment of the present invention. [Figure 14] An example of an ASN.1 description of a SCell configuration information element in an embodiment of the present invention. [Figure 15] An example of the processing of a terminal device in an embodiment of the present invention. [Figure 16] An example of the processing of a terminal device in an embodiment of the present invention. [Figure 17] An example of processing by a terminal device in an embodiment of the present invention. [Modes for carrying out the invention]

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

[0020] LTE (and LTE-A, LTE-A Pro) and NR may be defined as different Radio Access Technologies (RATs). NR may also be defined as a technology included in LTE. Furthermore, LTE that can connect with NR via Multi Radio Dual connectivity (MR-DC) may be distinguished from conventional LTE. Furthermore, LTE using 5GC in the core network may be distinguished from conventional LTE using EPC in the core network. Conventional LTE may refer to LTE that does not implement technologies standardized in 3GPP Release 15 or later. Embodiments of the present invention may be applied to NR, LTE, and other RATs. The following description uses terms related to LTE and NR, but embodiments of the present invention may be applied to other technologies using other terms. Also, the term E-UTRA in embodiments of the present invention may be replaced with the term LTE, and the term LTE may be replaced with the term E-UTRA.

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

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

[0023] E-UTRA100 may be a wireless access technology. E-UTRA100 may also be an air interface between UE122 and eNB102. The air interface between UE122 and eNB102 may be called the Uu interface. eNB (E-UTRAN Node B)102 may be the base station equipment for E-UTRA100. eNB102 may have the E-UTRA protocol described below. The E-UTRA protocol may consist of the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol described below. eNB102 may terminate the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol to UE122. The wireless access network configured with eNB may be called E-UTRAN.

[0024] EPC (Evolved Packet Core) 104 may be a core network. Interface 112 is an interface between eNB 102 and EPC 104 and may be called an S1 interface. Interface 112 may have a control plane interface through which control signals pass, and / or a user plane interface through which user data passes. The control plane interface of interface 112 may terminate at a Mobility Management Entity (MME: not shown) in EPC 104. The user plane interface of interface 112 may terminate at a Serving Gateway (S-GW: not shown) in EPC 104. The control plane interface of interface 112 may be called an S1-MME interface. The user plane interface of interface 112 may be called an S1-U interface.

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

[0026] NR106 may be a wireless access technology. NR106 may also be an air interface between UE122 and gNB108. The air interface between UE122 and gNB108 may be called the Uu interface. gNB108 may be the base station equipment for NR106. gNB108 may have the NR protocol described below. The NR protocol may consist of the NR User Plane (UP) protocol and the NR Control Plane (CP) protocol described below. gNB108 may terminate the NR User Plane (UP) protocol and the NR Control Plane (CP) protocol to UE122.

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

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

[0029] eNB102 may have the function to connect to 5GC110. eNB102 having the function to connect to 5GC110 may be called ng-eNB. Interface 114 is the interface between eNB102 and 5GC110 and may be called NG interface. Interface 114 may have a control plane interface through which control signals pass, and / or a user plane interface through which user data passes. The control plane interface of interface 114 may be terminated at the Access and Mobility Management Function (AMF: not shown) in 5GC110. The user plane interface of interface 114 may be terminated at the User Plane Function (UPF: not shown) in 5GC110. The control plane interface of interface 114 may be called NG-C interface. The user plane interface of interface 114 may be called NG-U interface. A wireless access network consisting of ng-eNB or gNB may be called NG-RAN. NG-RAN, E-UTRAN, eNB, ng-eNB, and gNB may simply be called a network.

[0030] One or more eNB102s may be connected to the 5GC110 via interface 114. Interfaces may exist between multiple eNB102s connected to the 5GC110 (not shown). Interfaces between multiple eNB102s connected to the 5GC110 may be called Xn interfaces. Furthermore, an eNB102 connected to the 5GC110 and a gNB108 connected to the 5GC110 may be connected via interface 120. Interface 120 between an eNB102 connected to the 5GC110 and a gNB108 connected to the 5GC110 may be called Xn interfaces.

[0031] gNB108 may have the function of connecting to EPC104. gNB108 with the function of connecting to EPC104 may be called en-gNB. Interface 118 is the interface between gNB108 and EPC104 and may be called the S1 interface. Interface 118 may have a user plane interface through which user data passes. The user plane interface of interface 118 may be terminated at the S-GW (not shown) in EPC104. The user plane interface of interface 118 may be called the S1-U interface. Also, eNB102 connected to EPC104 and gNB108 connected to EPC104 may be connected by interface 120. Interface 120 between eNB102 connected to EPC104 and gNB108 connected to EPC104 may be called the X2 interface.

[0032] Interface 124 is the interface between EPC104 and 5GC110, and may be an interface that passes only CP, only UP, or both CP and UP. In addition, some or all of interfaces such as Interface 114, Interface 116, Interface 118, Interface 120, and Interface 124 may not exist depending on the communication system provided by the telecommunications carrier.

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

[0034] When UE122 communicates with eNB102 and / or gNB108, the wireless connection may be established by establishing a radio bearer (RB) between UE122 and eNB102 and / or gNB108. The radio bearer used for CP may be called a signaling radio bearer (SRB). The radio bearer used for UP may be called a data radio bearer (DRB). Each radio bearer may be assigned a radio bearer identifier (Identity: ID). The radio bearer identifier for SRB may be called an SRB identifier (SRB Identity or SRB ID). The radio bearer identifier for DRB may be called a DRB identifier (DRB Identity or DRB ID).

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

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

[0037] EPC104 does not need to have PDU sessions and / or QoS flows. Similarly, 5GC110 does not need to have an EPS bearer. When UE122 is connected to EPC104, UE122 will have information about the EPS bearer, but it does not need to have information about the PDU sessions and / or QoS flows. Similarly, when UE122 is connected to 5GC110, UE122 will have information about the PDU sessions and / or QoS flows, but it does not need to have information about the EPS bearer.

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

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

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

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

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

[0043] Figure 3(B) is a diagram of the NR control plane (CP) protocol configuration. As shown in Figure 3(B), in the NR CP protocol, the RRC308, which is the radio resource control layer, may be the protocol between the UE122 and the gNB108. That is, the RRC308 may be a protocol that terminates at the gNB108 on the network side. Also, in the E-UTRAN CP protocol, the NAS312, which is a non-AS layer, may be the protocol between the UE122 and the AMF. That is, the NAS312 may be a protocol that terminates at the AMF on the network side.

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

[0045] In the embodiments of the present invention, the E-UTRA protocol and the NR protocol are not distinguished below, and the terms PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) may be used. In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) may be the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the E-UTRA protocol, respectively, or the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the NR protocol. Furthermore, SDAP (SDAP layer) may be the SDAP (SDAP layer) of the NR protocol.

[0046] Furthermore, in embodiments of the present invention, when distinguishing between the E-UTRA protocol and the NR protocol, PHY200, MAC202, RLC204, PDCP206, and RRC208 may be referred to as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively. Also, PHY200, MAC202, RLC204, PDCP206, and RRC208 may be described as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively. Furthermore, when distinguishing between the E-UTRA protocol and the NR protocol, PHY300, MAC302, RLC304, PDCP306, and RRC308 are sometimes referred to as NR PHY, NR MAC, NR RLC, NR RLC, and NR RRC, respectively. Also, PHY200, MAC302, RLC304, PDCP306, and RRC308 may be described as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.

[0047] This section describes entities in the AS layer of E-UTRA and / or NR. Entities that possess some or all of the functions of the MAC layer may be called MAC entities. Entities that possess some or all of the functions of the RLC layer may be called RLC entities. Entities that possess some or all of the functions of the PDCP layer may be called PDCP entities. Entities that possess some or all of the functions of the SDAP layer may be called SDAP entities. Entities that possess some or all of the functions of the RRC layer may be called RRC entities. MAC entities, RLC entities, PDCP entities, SDAP entities, and RRC entities may be replaced with MAC, RLC, PDCP, SDAP, and RRC, respectively.

[0048] Furthermore, the data provided from MAC, RLC, PDCP, and SDAP to lower layers, and / or the data provided from lower layers to MAC, RLC, PDCP, and SDAP, may be referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Also, the data provided from higher layers to MAC, RLC, PDCP, and SDAP, and / or the data provided from MAC, RLC, PDCP, and SDAP to higher layers, may be referred to as MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. In addition, a segmented RLC SDU may be referred to as an RLC SDU segment.

[0049] An example of PHY functionality is described below. The terminal device's PHY may have the function of receiving data transmitted from the base station device's PHY via the Downlink (DL) physical channel. The terminal device's PHY may also have the function of transmitting data to the base station device's PHY via the Uplink (UL) physical channel. The PHY may be connected to a higher-level MAC via a Transport Channel. The PHY may transfer data to the MAC via the Transport Channel. The PHY may also receive data from the MAC via the Transport Channel. In the PHY, an RNTI (Radio Network Temporary Identifier) ​​may be used to identify various control information.

[0050] Now, let's discuss physical channels.

[0051] The following physical channels may be included in the physical channels used for wireless communication between terminal equipment and base station equipment.

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

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

[0054] Furthermore, in NR, PBCH may be used to announce the time index (SSB-Index) within the period of a block of synchronization signals (SS / PBCH block, also called SSB).

[0055] PDCCH may be used in downlink wireless communication (wireless communication from base station equipment to terminal equipment) to transmit (or carry) Downlink Control Information (DCI). Here, one or more DCIs (which may be called DCI formats) may be defined for the transmission of downlink control information. That is, fields for downlink control information may be defined as DCIs and mapped to information bits. PDCCH may be transmitted in PDCCH candidates. Terminal equipment may monitor a set of PDCCH candidates in a serving cell. Monitoring a set of PDCCH candidates may mean attempting to decode a PDCCH according to a certain DCI format. The DCI format may be used for scheduling PUSCHs in a serving cell. PUSCHs may be used for transmitting user data or RRC messages, as described later.

[0056] PUCCH may be used to transmit Uplink Control Information (UCI) in uplink wireless communication (wireless communication from terminal equipment to base station equipment). Here, Uplink Control Information may include Channel State Information (CSI), which is used to indicate the state of the downlink channel. Furthermore, Uplink Control Information may include a Scheduling Request (SR), which is used to request UL-SCH (Uplink Shared Channel) resources. Furthermore, Uplink Control Information may include HARQ-ACK (Hybrid Automatic Repeat Request ACKnowledgement).

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

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

[0059] PRACH may be used to send a random access preamble. PRACH may also be used to indicate the initial connection establishment procedure, handover procedure, connection re-establishment procedure, synchronization (timing adjustment) for uplink transmissions, and PUSCH (UL-SCH) resource request.

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

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

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

[0063] A Common Control Channel (CCCH) may be a logical channel for transmitting control information between a terminal device and a base station device. A CCCH may be used when a terminal device does not have an RRC connection. A CCCH may also be used between a base station device and multiple terminal devices.

[0064] A DCCH (Dedicated Control Channel) may be a logical channel for transmitting dedicated control information in a point-to-point, bidirectional manner between a terminal device and a base station device. Dedicated control information may be control information specific to each terminal device. A DCCH may be used when the terminal device has an RRC connection.

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

[0066] A Multicast Traffic Channel (MTCH) may be a point-to-multipoint downlink channel for transmitting data from a base station to a terminal device. An MTCH may be a multicast logical channel. An MTCH may be used by a terminal device only when the terminal device receives MBMS.

[0067] An MCCH (Multicast Control Channel) may be a point-to-multipoint downlink channel for sending MBMS control information for one or more MTCHs from a base station device to a terminal device. An MCCH may be a multicast logical channel. An MCCH may be used by a terminal device only when the terminal device receives MBMS or is interested in receiving MBMS.

[0068] SC-MTCH (Single Cell Multicast Traffic Channel) may be a point-to-multipoint downlink channel for transmitting data from a base station to a terminal device using SC-PTM. SC-MTCH may be a multicast logical channel. SC-MTCH may be used by a terminal device only when the terminal device receives MBMS using SC-PTM (Single Cell Point-To-Multipoint).

[0069] SC-MCCH (Single Cell Multicast Control Channel) may be a point-to-multipoint downlink channel for sending MBMS control information for one or more SC-MCCHs from a base station device to a terminal device. SC-MCCH may be a multicast logical channel. SC-MCCH may be used by a terminal device only when the terminal device receives MBMS using SC-PTM, or when the terminal device is interested in receiving MBMS using SC-PTM.

[0070] This section describes the mapping between logical channels and transport channels for uplinks in E-UTRA and / or NR.

[0071] CCCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.

[0072] DCCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.

[0073] DTCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.

[0074] This section describes the mapping between logical channels and transport channels for downlinks in E-UTRA and / or NR.

[0075] BCCH may be mapped to a downlink transport channel, BCH (Broadcast Channel), and / or DL-SCH (Downlink Shared Channel).

[0076] The PCCH may be mapped to the PCH (Paging Channel), which is a downlink transport channel.

[0077] CCCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.

[0078] DCCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.

[0079] DTCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.

[0080] MTCH may be mapped to the downlink transport channel, which is the Multicast Channel (MCH).

[0081] MCCH may be mapped to MCH (Multicast Channel), which is a downlink transport channel.

[0082] SC-MTCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.

[0083] SC-MTCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.

[0084] Let's describe an example of MAC functionality. MAC can also be called a MAC sublayer.

[0085] A MAC may have the functionality to map various logical channels to corresponding transport channels. Logical channels may be identified by a Logical Channel Identity (Logical Channel ID). A MAC may be connected to a higher-level RLC via a logical channel. Logical channels may be divided into control channels that transmit control information and traffic channels that transmit user information, depending on the type of information being transmitted. Logical channels may also be divided into uplink logical channels and downlink logical channels. A MAC may have the functionality to multiplex MAC SDUs belonging to one or more different logical channels and provide them to the PHY. A MAC may also have the functionality to demultiplex MAC PDUs provided from the PHY and provide them to the higher layer via the logical channel to which each MAC SDU belongs.

[0086] MAC may also have a function to perform error correction through HARQ (Hybrid Automatic Repeat reQuest). MAC may also have a function to perform priority processing between terminal devices using dynamic scheduling. MAC may also have a function to perform priority processing between logical channels within a single terminal device. MAC may also have a function to perform priority processing for overlapping resources within a single terminal device.

[0087] The E-UTRA MAC may have the functionality to identify Multimedia Broadcast Multicast Services (MBMS). The NR MAC may also have the functionality to identify Multicast Broadcast Services (MBS).

[0088] MAC may have the ability to select the transport format. MAC may also have the ability to perform discontinuous reception (DRX) and / or discontinuous transmission (DTX), the ability to perform random access (RA) procedures, a power headroom reporting function that notifies information on available power, and a buffer status reporting function that notifies information on the amount of data in the transmit buffer.

[0089] NR MAC may have a Bandwidth Adaptation (BA) function. Furthermore, the MAC PDU format used in E-UTRA MAC and the MAC PDU format used in NR MAC may be different. Additionally, MAC PDU may include MAC control elements (MAC CE), which are elements for control within the MAC.

[0090] This section describes the Buffer Status Reporting Procedure (BSR procedure) and the Buffer Status Report (BSR). The BSR procedure may be used to provide a serving gNB (base station equipment) with information about the uplink data volume within a MAC entity.

[0091] Each logical channel may be assigned to a Logical Channel Group (LCG) using a parameter (logicalChannelGroup) provided by RLC. The maximum number of LCGs may be eight. The MAC entity of the terminal device may determine the amount of UL data available for a logical channel according to the data volume calculation procedure in RLC and PDCP.

[0092] A BSR may be triggered based on the fulfillment of any of the following conditions (A) through (D). (A) Uplink data for a logical channel belonging to a certain LCG becomes available to the MAC entity of a terminal device, and (1) this uplink data belongs to a logical channel with a higher priority than the logical channel containing available uplink data belonging to any LCG, or (2) none of the logical channels belonging to the LCG contain available uplink data. (The BSR triggered by this condition may be a regular BSR.) (B) When an uplink resource is allocated and the number of padding bits is equal to or greater than the number of subheaders added to the buffer status report MAC CE (BSR MAC CE). (The BSR triggered by this condition may be a padding BSR.) (C) When the timer used to control the BSR (retxBSR-Timer) expires and at least one of the logical channels belonging to the LCG contains uplink data. (The BSR triggered under this condition may be a regular BSR.) (D) When the timer used to control the BSR (periodicBSR-Timer) expires. (The BSR triggered under this condition may be a periodic BSR.)

[0093] For regular BSRs and periodic BSRs, the MAC entity of the terminal device may report a Long BSR for all LCGs that have data available for transmission when two or more LCGs have data available for transmission when the MAC PDU containing the BSR is constructed. For regular BSRs and periodic BSRs, the MAC entity of the terminal device may report a Short BSR if two or more LCGs do not have data available for transmission when the MAC PDU containing the BSR is constructed.

[0094] For a padding BSR, the MAC entity of the terminal device may decide whether to report a Short Truncated BSR, a Long Truncated BSR, a Short BSR, or a Long BSR, based on the number of padding bits, the size of the Short BSR, and the size of the Long BSR.

[0095] For BSRs triggered based on the expiration of the retxBSR-Timer, the MAC entity of the terminal device may consider the logical channel that triggered the BSR to be the highest-priority logical channel with data available for transmission when the BSR is triggered.

[0096] The MAC entity of the terminal device may perform some or all of the following processes (A) through (C) based on the condition that at least one BSR has been triggered and that BSR has not been canceled, that a UL-SCH resource is available for a new transmission, and that the UL-SCH resource can accommodate the BSR MAC CE and its subheaders as a result of logical channel prioritization. (A) Generate one or more BSR MAC CEs, or instruct other entities to generate one or more BSR MAC CEs. (B) Start or restart the periodicBSR-Timer unless all generated BSRs are Long Truncated BSRs and Short Truncated BSRs. (C) Start or restart the retxBSR-Timer

[0097] Even when multiple BSRs are triggered by multiple events (conditions), a MAC PDU may contain at most one BSR MAC CE. Regular BSRs and periodic BSRs may have a higher priority than padding BSRs.

[0098] The MAC entity of the terminal device may restart the retxBSR-Timer based on receiving a grant for sending new data on any UL-SCH.

[0099] This document describes the Power Headroom Reporting Procedure (PHR Procedure) and the Power Headroom Report (PHR). The PHR Procedure may be used to provide some or all of the information (A) through (C) below to the Serving gNB (Base Station Equipment). (A) Difference between the nominal UE's maximum transmit power and the estimated UL-SCH transmit power per activated serving cell. (B) The difference between the maximum transmit power of the nominal UE and the estimated transmit power of UL-SCH and / or PUCCH on the SpCell of other MAC entities. (C) Difference between the maximum transmit power of the nominal UE and the estimated transmit power of the SRS per activated serving cell.

[0100] The information described in (A), (B), and (C) above may be referred to as Type 1 power headroom, Type 2 power headroom, and Type 3 power headroom, respectively. Furthermore, information including some or all of (A) through (C) above may be referred to simply as power headroom.

[0101] A MAC CE containing only one set of information regarding the power headroom type, the target cell, and the maximum transmit power in that cell may be referred to as a Single Entry PHR MAC CE. Conversely, a MAC CE containing multiple sets of information regarding the power headroom type, the target cell, and the maximum transmit power in that cell may be referred to as a Multiple Entry PHR MAC CE.

[0102] For any MAC entity, a MAC entity in the UE may trigger a PHR if an uplink is configured in a MAC entity and a SCell is activated that is not set to a dormant BWP, and the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) configured in the RRC message is not set to a dormant BWP. Additionally, a MAC entity in the UE may trigger a PHR if a PSCell is newly added or modified.

[0103] For any MAC entity, the UE's MAC entity may trigger a PHR if the activated BWP of a SCell with an uplink configured in that MAC entity is changed from a dormant (DL) BWP to a non-dormant DL BWP. The above BWP change may also be represented as a BWP switch.

[0104] If a MAC entity has an uplink resource allocated for a new transmission, the MAC entity in the UE may perform some or all of the following actions (A) and (B). (A) If this uplink resource is the first one since the MAC was last reset, start the timer (phr-PeriodicTimer). (B) If the PHR procedure has triggered at least one PHR and this trigger has not been canceled, and based on the logical channel priority, the allocated uplink resource can accommodate the MAC CE and its subheader for the PHR, then some or all of the following processes (B-1) to (B-5) are performed. (B-1) If the MAC CE being received is a Multiple Entry PHR MAC CE, perform some or all of the following processes (B-1-1) through (B-1-3). (B-1-1) For each activated serving cell with an uplink configured and associated with any MAC entity in the same UE, where the activated DL BWP is not a dormant (DL) BWP, obtain the Type 1 or Type 3 power headroom value for the uplink carrier associated with the NR serving cell and E-UTRA serving cell. If the MAC entity associating the serving cell has uplink resources allocated for transmission on this serving cell, or if another MAC entity in the same UE is configured and has uplink resources allocated for transmission on this serving cell, and the higher layer has determined to calculate the maximum transmit power based on the power used for actual transmission on this serving cell, obtain this maximum transmit power value from the physical layer. (B-1-2) If the UE is allowed to report the type 2 power headroom for the SpCell of another MAC entity of the same UE, then retrieve the value of that type 2 power headroom if that MAC entity is an E-UTRA MAC entity, and if the higher layers have determined that the maximum transmit power should be calculated based on the power used for actual transmission in the SpCell of that MAC entity, then retrieve this maximum transmit power value from the physical layer. (B-1-3) After considering the priority of the logical channel, a Multiple Entry PHR MAC CE is generated and sent based on the values ​​reported from the physical layer. (B-2) If the MAC CE to be received is a Single Entry PHR MAC CE, the Type 1 power headroom value for the uplink carrier associated with the PCell and the associated maximum transmit power value are obtained from the physical layer, and a Single Entry PHR MAC CE is generated and transmitted based on these values, taking into account the priority of the logical channel. (B-3) Start or restart the timer (phr-PeriodicTimer). (B-4) Start or restart the timer (phr-ProhibitTimer). (B-5) Cancel all triggered PHRs.

[0105] A scheduling request (SR) may be used by a terminal device to request UL-SCH resources for a new transmission.

[0106] The MAC entity of a terminal device may have zero, one, or more SR settings. An SR setting may include a set of PUCCH resources for different BWPs and cell-wide SRs. For a single logical channel or beam failure recovery, up to one PUCCH resource for SR may be configured per BWP.

[0107] When an SR (Sentence Request) is triggered, it can be considered pending until it is canceled.

[0108] The MAC entity of a terminal device may be considered valid only if it has a PUCCH resource for an Active BWP (Active BWP) that is activated when sending an SR.

[0109] The MAC entity of a terminal device may initiate a random access procedure in SpCell to cancel a pending SR based on the fact that at least one SR is pending and it does not have a valid PUCCH resource setting for the pending SR.

[0110] Let's describe an example of RLC functionality. RLC can also be called an RLC sublayer.

[0111] E-UTRA RLC may have the functionality to segment and / or concatenate data provided from the upper layer PDCP and provide it to the lower layer. E-UTRA RLC may also have the functionality to reassemble and reorder data provided from the lower layer and provide it to the upper layer.

[0112] NR RLC may have the function of adding a sequence number to the data provided by the upper-layer PDCP that is independent of the sequence number added by the PDCP. NR RLC may also have the function of segmenting the data provided by the PDCP and providing it to the lower layer. Furthermore, NR RLC may have the function of reassembling the data provided by the lower layer and providing it to the upper layer. RLC may also have a data retransmission function and / or an automatic repeat request (ARQ) function.

[0113] RLC may also have a function to perform error correction using ARQ. The control information sent from the receiver to the transmitter of the RLC, indicating data that needs to be retransmitted, for the purpose of performing ARQ, may be called a status report. The instruction to send a status report, sent from the transmitter to the receiver of the RLC, may be called a poll. RLC may also have a function to detect data duplication. RLC may also have a function to discard data.

[0114] RLC can have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM).

[0115] In TM, data received from higher layers is not split, and RLC headers do not need to be added. TM RLC entities are unidirectional entities and may be configured as either transmitting TM RLC entities or receiving TM RLC entities.

[0116] UM performs operations such as splitting and / or joining data received from higher layers and adding RLC headers, but does not need to control data retransmission. UM RLC entities may be unidirectional or bidirectional. If a UM RLC entity is unidirectional, it may be configured as either a transmitting or receiving UM RLC entity. If a UM RLC entity is bidirectional, it may be configured as a UM RLC entity consisting of a transmitting side and a receiving side.

[0117] AM may perform operations such as splitting and / or combining data received from higher layers, adding RLC headers, and controlling data retransmission. The AM RLC entity is a bidirectional entity and may be configured as an AM RLC consisting of a transmitting side and a receiving side.

[0118] Furthermore, the data provided to lower layers by TM, and / or provided by lower layers, may be called TMD PDUs. Similarly, the data provided to lower layers by UM, and / or provided by lower layers, may be called UMD PDUs. Finally, the data provided to lower layers by AM, or provided by lower layers, may be called AMD PDUs.

[0119] The RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC may be different. Furthermore, there may be data RLC PDUs and control RLC PDUs. The data RLC PDU may be called an RLC DATA PDU (RLC Data PDU). The control RLC PDU may be called an RLC CONTROL PDU (RLC Control PDU).

[0120] Let's describe an example of PDCP functionality. PDCP can be referred to as a PDCP sublayer.

[0121] PDCP may have a function for maintaining sequence numbers. PDCP may also have a header compression / decompression function for efficiently transmitting user data such as IP packets and Ethernet frames over the wireless section. The protocol used for IP packet header compression / decompression may be called the ROHC (Robust Header Compression) protocol.

[0122] Furthermore, the protocol used for compressing and decompressing Ethernet frame headers may be called the EHC (Ethernet® Header Compression) protocol. PDCP may also have data encryption and decryption functions. PDCP may also have data integrity protection and integrity verification functions. PDCP may also have reordering functions. PDCP may also have a PDCP SDU retransmission function. PDCP may also have a data discard function using a discard timer. PDCP may also have a duplication function. PDCP may also have a function to discard duplicate received data.

[0123] A PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. The PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. Furthermore, there may be data PDCP PDUs and control PDCP PDUs. The data PDCP PDU may be called a PDCP DATA PDU (PDCP Data PDU). The control PDCP PDU may be called a PDCP CONTROL PDU (PDCP Control PDU).

[0124] This section describes PDCP duplication. When duplication to a wireless bearer is configured by RRC in a terminal device, at least one additional RLC entity (Secondary RLC entity) may be added to the wireless bearer in addition to the original RLC entity (Primary RLC entity) to process the duplicated PDCP PDU. In this case, all RLC entities (including the added RLC entity) may have the same RLC mode.

[0125] When replication to the DRB is configured, the RRC may simultaneously set the PDCP replication status (either Activated or Deactivated). After this setting, the PDCP replication status may be dynamically controlled by MAC CE.

[0126] When replication to the SRB is configured, the PDCP replication status is always Activated and does not need to be dynamically controlled.

[0127] When replication is activated, the original PDCP PDU and the replicated PDCP PDU may be transmitted on different carriers. For example, in a terminal device configured with MR-DC, the original PDCP PDU and the replicated PDCP PDU may be transmitted in cells of different cell groups.

[0128] Furthermore, the RRC entity of a terminal device may be configured for duplication to a wireless bearer via an RRC message. In this case, the RRC message may include the cell group identifier and / or logical channel identifier as primary path information. The primary path may be information indicating the cell group identifier and logical channel identifier of the primary RRC entity. PDCP duplication may also be referred to as PDCP duplication or PDCP multiplexing.

[0129] This section describes an example of SDAP functionality. SDAP is a Service Data Adaptive Protocol Layer (SAP).

[0130] SDAP may have the function of mapping downlink QoS flows sent from 5GC110 to terminal devices via base station equipment to data radio bearers (DRBs), and / or mapping uplink QoS flows sent from terminal devices to 5GC110 via base station equipment to DRBs. SDAP may also have the function of storing mapping rule information. SDAP may also have the function of marking QoS flow identifiers (QoS Flow ID: QFI). Note that there may be data SDAP PDUs and control SDAP PDUs. Data SDAP PDUs may be called SDAP DATA PDUs (SDAP Data PDUs). Control SDAP PDUs may be called SDAP CONTROL PDUs (SDAP Control PDUs). Note that there may be one SDAP entity for each PDU session in a terminal device.

[0131] This section describes an example of RRC's functionality.

[0132] The RRC may have a broadcast function. The RRC may have a paging function from the EPC104 and / or 5GC110. The RRC may have a paging function from the eNB102 connected to the gNB108 or 5GC100. The RRC may also have an RRC connection management function. The RRC may also have a wireless bearer control function.

[0133] Furthermore, the RRC may have cell group control functionality. The RRC may also have mobility control functionality. The RRC may also have terminal device measurement reporting and terminal device measurement reporting control functionality. Furthermore, the RRC may have QoS management functionality. Finally, the RRC may have wireless link failure detection and recovery functionality.

[0134] The RRC may use RRC messages to perform functions such as broadcasting, paging, RRC connection management, wireless bearer control, cell group control, mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, and wireless link failure detection and recovery. Note that the RRC messages and parameters used in E-UTRA RRC may differ from those used in NR RRC.

[0135] RRC messages may be sent using logical channels BCCH, PCCH, CCCH, DCCH, or MCCH.

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

[0137] RRC messages sent in the uplink (UL) direction using CCCH may include, for example, RRC Setup Request, RRC Resume Request, RRC Reestablishment Request, and RRC System Info Request. They may also include, for example, RRC Connection Request, RRC Connection Resume Request, and RRC Connection Reestablishment Request. Other RRC messages may also be included.

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

[0139] RRC messages sent in the uplink (UL) direction using DCCH may include, for example, Measurement Report messages, RRC Connection Reconfiguration Complete messages, RRC Connection Setup Complete messages, RRC Connection Reestablishment Complete messages, Security Mode Complete messages, and UE Capability Information messages.

[0140] Other RRC messages may also be included, such as Measurement Report, RRC Reconfiguration Complete, RRC Setup Complete, RRC Reestablishment Complete, RRC Resume Complete, Security Mode Complete, and UE Capability Information.

[0141] RRC messages sent in the downlink (DL) direction using DCCH may include, for example, RRC Connection Reconfiguration messages, RRC Connection Release messages, Security Mode Command messages, and UE Capability Enquiry messages.

[0142] Furthermore, messages such as RRC Reconfiguration, RRC Resume, RRC Release, RRC Reestablishment, Security Mode Command, and UE Capability Enquiry may also be included. Other RRC messages may also be included.

[0143] This section describes some examples of NAS functionality. A NAS may have authentication capabilities. It may also have mobility management capabilities. Furthermore, a NAS may have security control capabilities.

[0144] The aforementioned PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS functions are merely examples, and some or all of each function may not be implemented. Furthermore, some or all of the functions of each layer may be included in other layers.

[0145] Furthermore, the layers above the AS layer of the terminal device (not shown) may include the IP layer, and above the IP layer, the TCP (Transmission Control Protocol) layer, UDP (User Datagram Protocol) layer, etc. Also, the Ethernet layer may be present above the AS layer of the terminal device.

[0146] The layer above the AS layer of a terminal device may be called the PDU layer. The PDU layer may include the IP layer, TCP layer, UDP layer, Ethernet layer, etc. An application layer may exist above the IP layer, TCP layer, UDP layer, Ethernet layer, PDU layer, etc.

[0147] The application layer may include SIP (Session Initiation Protocol) and SDP (Session Description Protocol), which are used in IMS (IP Multimedia Subsystem), one of the service networks standardized by 3GPP. The application layer may also include RTP (Real-time Transport Protocol) used for media communication, and / or protocols such as RTCP (Real-time Transport Control Protocol) and HTTP (HyperText Transfer Protocol) for media communication control. Furthermore, the application layer may include codecs for various media.

[0148] Furthermore, the RRC layer may be a higher layer than the SDAP layer.

[0149] Next, we will explain the states and state transitions of UE122 in LTE and NR.

[0150] A UE122 connected to an EPC or 5GC may be in the RRC_CONNECTED state when an RRC connection has been established. The state in which an RRC connection has been established may include a state in which the UE122 holds some or all of the UE context described below. The state in which an RRC connection has been established may also include a state in which the UE122 can send and / or receive unicast data. Furthermore, a UE122 may be in the RRC_INACTIVE state when the RRC connection is suspended. A UE122 may be in the RRC_INACTIVE state when it is connected to a 5GC and the RRC connection is suspended. When a UE122 is neither in the RRC_CONNECTED state nor the RRC_INACTIVE state, the UE122 may be in the RRC_IDLE state.

[0151] Note that if UE122 is connected to EPC, it does not have the RRC_INACTIVE state, but E-UTRAN may initiate the suspension of the RRC connection. When UE122 is connected to EPC and the RRC connection is suspended, UE122 may transition to the RRC_IDLE state, retaining the UE's AS context and the identifier (resumeIdentity) used for resuming. The upper layer of the UE122's RRC layer (e.g., the NAS layer) may initiate the resumption of the suspended RRC connection if UE122 retains the UE's AS context, E-UTRAN has permitted the resumption of the RRC connection, and UE122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state.

[0152] The definition of RRC connection pause may differ between UE122 connected to EPC104 and UE122 connected to 5GC110. Furthermore, all or part of the procedure for UE122 to resume from RRC connection pause may differ depending on whether UE122 is connected to EPC (paused in RRC_IDLE state) or UE122 is connected to 5GC (paused in RRC_INACTIVE state).

[0153] The RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state may be referred to as RRC connected mode, RRC inactive mode, and RRC idle mode, respectively. If there is no risk of misinterpretation, they may simply be referred to as connected mode, inactive mode, and idle mode.

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

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

[0156] This section describes cell groups, which are configured on terminal devices by base station equipment.

[0157] A cell group may consist of only one Special Cell (SpCell). Alternatively, a cell group may consist of one SpCell and one or more Secondary Cells (SCells). In other words, a cell group may consist of one SpCell and, optionally, one or more SCells.

[0158] Note that if a MAC entity is associated with a Master Cell Group (MCG), SpCell may mean a Primary Cell (PCell). Similarly, if a MAC entity is associated with a Secondary Cell Group (SCG), SpCell may mean a Primary SCG Cell (PSCell). If a MAC entity is not associated with a cell group, SpCell may mean a PCell. PCell, PSCell, and SCell are serving cells.

[0159] SpCell may support PUCCH transmission and contention-based random access. SpCell may be in an always-active state.

[0160] A PCell may be a cell used in the RRC connection establishment procedure when a terminal device in an RRC idle state transitions to an RRC connected state. A PCell may also be a cell used in the RRC connection re-establishment procedure when a terminal device re-establishes an RRC connection. A PCell may also be a cell used in the random access procedure during handover.

[0161] PSCell may be a cell used in the random access procedure when adding a secondary node (SN), as described later. SpCell may be a cell used for purposes other than those mentioned above.

[0162] Furthermore, if a cell group consists of a SpCell and one or more SCells, it can be said that carrier aggregation (CA) is configured for this cell group. Also, for terminal devices with CA configured, a cell that provides additional radio resources to a SpCell can be considered an SCell.

[0163] A group of serving cells configured by RRC that uses the same timing reference cell and the same timing advance value for cells with uplinks configured within that group may be called a Timing Advance Group (TAG). Furthermore, a TAG containing a MAC entity SpCell may represent a Primary Timing Advance Group (PTAG). In addition, a TAG other than a PTAG may represent a Secondary Timing Advance Group (STAG).

[0164] Furthermore, when Dual Connectivity (DC) or Multi-Radio Dual Connectivity (MR-DC) is implemented, cell groups may be added from the base station equipment to terminal equipment. DC may be a technology that uses the radio resources of cell groups configured by a first base station equipment (first node) and a second base station equipment (second node) to perform data communication. MR-DC may be a technology included in DC. In order to perform DC, the first base station equipment may add a second base station equipment. The first base station equipment may be called a Master Node (MN).

[0165] The cell group comprised of the master node may be called the Master Cell Group (MCG). The second base station device may be called the Secondary Node (SN). The cell group comprised of the Secondary Node may be called the Secondary Cell Group (SCG). Note that the master node and the secondary node may be configured within the same base station device.

[0166] Furthermore, when a DC is not configured, the cell group configured on the terminal device may be called an MCG. Also, when a DC is not configured, the SpCell configured on the terminal device may be a PCell.

[0167] Furthermore, MR-DC may be a technology that performs DC using E-UTRA for MCG and NR for SCG. Also, MR-DC may be a technology that performs DC using NR for MCG and E-UTRA for SCG. Also, MR-DC may be a technology that performs DC using NR for both MCG and SCG. Examples of MR-DC using E-UTRA for MCG and NR for SCG include EN-DC (E-UTRA-NR Dual Connectivity) which uses EPC for the core network, and NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity) which uses 5GC for the core network.

[0168] Furthermore, as an example of an MR-DC using NR for the MCG and E-UTRA for the SCG, there may be an NE-DC (NR-E-UTRA Dual Connectivity) that uses 5GC for the core network. Also, as an example of an MR-DC using NR for both the MCG and SCG, there may be an NR-DC (NR-NR Dual Connectivity) that uses 5GC for the core network.

[0169] In a terminal device, there may be one MAC entity for each cell group. For example, if a DC or MR-DC is configured in a terminal device, there may be one MAC entity for the MCG and one MAC entity for the SCG.

[0170] MAC entities for MCG in terminal devices may always be established in all states of the terminal device (RRC idle state, RRC connected state, and RRC inactive state, etc.). MAC entities for SCG in terminal devices may be created by the terminal device when SCG is configured on the terminal device.

[0171] Furthermore, the MAC entities for each cell group of a terminal device may be configured by the terminal device receiving an RRC message from the base station device. In EN-DC and NGEN-DC, the MAC entity for MCG may be an E-UTRA MAC entity, and the MAC entity for SCG may be an NR MAC entity. Also, in NE-DC, the MAC entity for MCG may be an NR MAC entity, and the MAC entity for SCG may be an E-UTRA MAC entity.

[0172] Furthermore, in NR-DC, MAC entities for both MCG and SCG may be NR MAC entities. Note that the statement that there is one MAC entity for each cell group can be rephrased as "there is one MAC entity for each SpCell." Similarly, the statement that there is one MAC entity for each cell group can be rephrased as "there is one MAC entity for each SpCell."

[0173] Let's explain wireless bearers. For E-UTRA, SRB0 through SRB2 may be defined, or other SRBs may be defined. For NR, SRB0 through SRB3 may be defined, or other SRBs may be defined.

[0174] SRB0 may be an SRB for RRC messages, which is transmitted and / or received using the logical channel CCCH.

[0175] SRB1 may be an SRB for RRC messages and for NAS messages before SRB2 is established. RRC messages transmitted and / or received using SRB1 may include piggybacked NAS messages. All RRC and NAS messages transmitted and / or received using SRB1 may use the DCCH logical channel.

[0176] SRB2 may be an SRB for NAS messages and for RRC messages containing logged measurement information. All RRC and NAS messages transmitted and / or received using SRB2 may use the logical channel DCCH. Furthermore, SRB2 may have a lower priority than SRB1.

[0177] SRB3 may be an SRB for transmitting and / or receiving specific RRC messages when EN-DC, NGEN-DC, NR-DC, etc., are configured on the terminal device. All RRC and NAS messages transmitted and / or received using SRB3 may use the logical channel DCCH. Other SRBs may be provided for other purposes. DRB may be a wireless bearer for user data. RRC messages transmitted and / or received using DRB may use the logical channel DTCH.

[0178] This section describes a wireless bearer in a terminal device. The wireless bearer may include an RLC bearer. An RLC bearer may consist of one or two RLC entities and a logical channel. If there are two RLC entities in an RLC bearer, the RLC entities may be a TM RLC entity and / or a transmit RLC entity and a receive RLC entity in a unidirectional UM mode RLC entity.

[0179] SRB0 may consist of a single RLC bearer. The RLC bearer of SRB0 may consist of the TM's RLC entity and logical channel. SRB0 may always be established in terminal devices in all states (RRC idle state, RRC connected state, and RRC inactive state, etc.).

[0180] SRB1 may be established and / or configured on a terminal device by an RRC message received from the base station device when the terminal device transitions from an RRC idle state to an RRC connected state. SRB1 may consist of one PDCP entity and one or more RLC bearers. The RLC bearers of SRB1 may consist of an AM RLC entity and a logical channel.

[0181] SRB2 may be established and / or configured on a terminal device by an RRC message received from the base station device by a terminal device in an RRC connection state with AS security activated. SRB2 may consist of one PDCP entity and one or more RLC bearers. The RLC bearers of SRB2 may consist of an AM RLC entity and a logical channel. Note that the PDCP on the base station side of SRB1 and SRB2 may be located on the master node.

[0182] SRB3 may be established and / or configured on a terminal device when a secondary node is added to or changed in an EN-DC, NGEN-DC, or NR-DC, by an RRC message received from the base station device by the terminal device in an RRC connection state with AS security activated. SRB3 may be a direct SRB between the terminal device and the secondary node. SRB3 may consist of one PDCP entity and one or more RLC bearers. The RLC bearers of SRB3 may consist of an AM RLC entity and a logical channel. The base station-side PDCP of SRB3 may be located on the secondary node.

[0183] One or more DRBs may be established and / or configured on a terminal device by RRC messages received from a base station device by a terminal device in an RRC connection state with AS security activated. A DRB may consist of one PDCP entity and one or more RLC bearers. The RLC bearers of a DRB may consist of AM or UM RLC entities and logical channels.

[0184] In MR-DC, a wireless bearer with a PDCP on the master node may be called an MN-terminated bearer. Similarly, a wireless bearer with a PDCP on the secondary node may be called an SN-terminated bearer. Furthermore, in MR-DC, a wireless bearer with an RLC bearer present only in the MCG may be called an MCG bearer. Similarly, a wireless bearer with an RLC bearer present only in the SCG may be called an SCG bearer. Finally, in a DC, a wireless bearer with an RLC bearer present in both the MCG and SCG may be called a split bearer.

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

[0186] For RLC bearers established and / or configured in cell groups composed of E-UTRA, the established and / or configured RLC entities may be E-UTRA RLC. Similarly, for RLC bearers established and / or configured in cell groups composed of NR, the established and / or configured RLC entities may be NR RLC.

[0187] When EN-DC is configured on a terminal device, the PDCP entity established and / or configured for an MN-terminated MCG bearer may be either an E-UTRA PDCP or an NR PDCP. Also, when EN-DC is configured on a terminal device, the PDCP established and / or configured for other bearer types of wireless bearers, namely MN-terminated split bearers, MN-terminated SCG bearers, SN-terminated MCG bearers, SN-terminated split bearers, and SN-terminated SCG bearers, may be an NR PDCP.

[0188] Furthermore, if NGEN-DC, NE-DC, or NR-DC is configured on the terminal device, the PDCP entities established and / or configured for wireless bearers of all bearer types may be NR PDCPs.

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

[0190] Regardless of whether MR-DC is configured or not, a network configuration with eNB102 as the master node and EPC104 as the core network may be called E-UTRA / EPC. Similarly, a network configuration with eNB102 as the master node and 5GC110 as the core network may be called E-UTRA / 5GC. Furthermore, a network configuration with gNB108 as the master node and 5GC110 as the core network may be called NR, or NR / 5GC. When MR-DC is not configured, the master node mentioned above may refer to the base station equipment that communicates with terminal devices.

[0191] Next, we will explain handover in LTE and NR.

[0192] A handover may be the process by which UE122, which is in an RRC connection state, changes the serving cell. A handover may occur when UE122 receives an RRC message from eNB102 and / or gNB108 that instructs a handover. An RRC message that instructs a handover may be a message concerning the reconfiguration of the RRC connection that includes a parameter instructing a handover (for example, an information element named MobilityControlInfo or an information element named ReconfigurationWithSync).

[0193] The information element named MobilityControlInfo mentioned above may be referred to as the mobility control setting information element, mobility control setting, or mobility control information. The information element named ReconfigurationWithSync mentioned above may be referred to as the synchronized reconfiguration information element, or synchronized reconfiguration. Furthermore, the RRC message that instructs a handover may be a message indicating the movement of another RAT to a cell (for example, MobilityFromEUTRACommand or MobilityFromNRCommand). Furthermore, handover may be referred to as reconfiguration with sync.

[0194] Furthermore, the conditions under which UE122 can perform a handover may include some or all of the following: AS security is activated, SRB2 is established, and at least one DRB is established.

[0195] Furthermore, the terminal device may perform a process that does not change the serving cell based on the RRC message instructing a handover. In other words, the terminal device may perform a handover process targeting the same cell as the current serving cell.

[0196] This document describes the Uplink Time Alignment in the MAC entity of a terminal device.

[0197] The MAC entity of the terminal device may have the following parameters set by RRC for maintaining uplink time matching (Maintenance): TAG-specific time alignment timer (timeAlignmentTimner): A timer used by MAC entities to control the time at which they consider the uplink of the serving cell belonging to the TAG associated with this timer to be time-aligned (in other words, the uplink to be synchronized).

[0198] The MAC entity of the terminal device performs some or all of the following (A) through (D) in order to maintain uplink time matching. (A) Upon receiving a timing advance command MAC control element, if the specified TAG maintains the parameter (N_TA) indicating timing advance between the downlink and uplink, (1) apply the timing advance command for this specified TAG, and (2) start or restart the time alignment timer associated with this specified TAG. (B) When a timing advance command is received in a random access response message for a serving cell belonging to a certain TAG, or in an MSGB for a SpCell, some or all of the following (B-1) to (B-3) may be performed. (B-1) If the random access preamble was not selected by the MAC entity from among contention-based random access preambles, then perform the following steps (B-1-1) through (B-1-2). (B-1-1) Apply the timing advance command to this TAG. (B-1-2) Start or restart the time-aligned timer associated with this TAG. If the conditions in (B-2)(B-1) are not met and the time-aligned timer associated with this TAG is not running, then the following processes (B-2-1) through (B-2-3) are performed. (B-2-1) Apply the timing advance command to this TAG. (B-2-2) Start the time-matching timer associated with this TAG. (B-2-3) When contention resolution in a random access procedure is deemed unsuccessful, or when contention resolution for an SI request is deemed successful after sending HARQ feedback for a MAC PDU containing a UE contention resolution identity MAC control element, the time-aligned timer associated with this TAG is stopped. If none of the conditions in (B-3)(B-1) and (B-2) are met, the received timing advance command is ignored. (C) When an Absolute timing advance command is received as a reply to an MSGA transmission containing a C-RNTI MAC control element, (1) the timing advance command is applied to the PTAG, and (2) the time-aligned timer associated with the PTAG is started or restarted. (D) When the time synchronization timer expires, some or all of the following (D-1) to (D-2) may be performed. (D-1) If the time-aligned timer associated with the PTAG has expired, some or all of the following processes (D-1-1) through (D-1-8) may be performed. (D-1-1) Flush all HARQ buffers in all serving cells. (D-1-2) If PUCCH is set on any serving cell, notify the RRC entity of the terminal device to release PUCCH on all serving cells. (D-1-3) If SRS is configured in any serving cell, notify the RRC entity of the terminal device to release SRS in all serving cells. (D-1-4) Clear all configured downlink assignments and configured uplink grants. (D-1-5) Clear all PUSCH resources for semi-persistent CSI reporting. (D-1-6) Assume that all running time-aligned timers have expired. (D-1-7) Maintain N_TA for all TAGs. (D-1-8) If the time-matching timer of the PTAG for an inactivated secondary cell group expires, beam failure detection and / or recovery will not be performed in the cells of that secondary cell group. If the conditions in (D-2)(D-1) are not met, and the time-aligned timer associated with the STAG has expired, then some or all of (D-2-1) through (D-2-6) below may be performed for all serving cells belonging to this TAG. (D-2-1) Flush all HARQ buffers. (D-2-2) If PUCCH is set, notify the RRC entity of the terminal device to release it. (D-2-3) If SRS is configured, notify the RRC entity of the terminal device to release it. (D-2-4) Clear all configured downlink assignments and configured uplink grants. (D-2-5) Clear all PUSCH resources for semi-persistent CSI reporting. (D-2-6) Maintain N_TA of this TAG.

[0199] When a MAC entity of a terminal device stops transmitting via SCell as a result of exceeding the upper limit due to the maximum difference in uplink timing between the TAGs of this MAC, or the maximum difference in uplink timing between the TAGs of any MAC entity of the terminal device, the time matching timer for the TAG associated with this SCell may be considered to have expired.

[0200] The MAC entity of a terminal device will not perform any transmissions other than the transmission of the random access preamble and MSGA in a given SCell if the time-aligned timer associated with the TAG to which the SCell belongs is not running. Furthermore, the MAC entity of a terminal device will not perform any transmissions other than the transmission of the random access preamble and MSGA in a SpCell if the time-aligned timer associated with the PTAG is not running.

[0201] The flow of RRC messages transmitted and received between a terminal device and a base station device is described below. Figure 4 is a diagram showing an example of the flow of procedures for various settings in RRC according to an embodiment of the present invention. Figure 4 is an example of the flow when an RRC message is sent from a base station device (eNB102, and / or gNB108) to a terminal device (UE122).

[0202] In Figure 4, the base station device creates an RRC message (step S400). The creation of an RRC message by the base station device may be done in order for the base station device to distribute broadcast information (SI: System Information) or paging information. Alternatively, the creation of an RRC message by the base station device may be done in order for the base station device to perform processing on a specific terminal device. Processing to be performed on a specific terminal device may include, for example, security settings, RRC connection reconfiguration, handover to a different RAT, suspension of RRC connection, and release of RRC connection.

[0203] The RRC connection reconfiguration process may include, for example, control of radio bearers (establish, change, release, etc.), control of cell groups (establish, add, change, release, etc.), measurement setting, handover, security key update, etc. The creation of RRC messages in the base station equipment may be performed in response to RRC messages sent from terminal equipment. Responses to RRC messages sent from terminal equipment may include, for example, responses to RRC setup requests, responses to RRC reconnection requests, and responses to RRC restart requests.

[0204] RRC messages contain various information notifications and configuration information (parameters). These parameters may be called fields and / or information elements and may be described using the ASN.1 (Abstract Syntax Notation One) notation scheme.

[0205] In Figure 4, the base station device then transmits the created RRC message to the terminal device (step S402). The terminal device then performs any necessary processing, such as configuration, according to the received RRC message (step S404). The terminal device that has performed the processing may send a response RRC message to the base station device (not shown).

[0206] RRC messages may be used for purposes other than those mentioned above.

[0207] In MR-DC, the RRC on the master node side may be used to transfer RRC messages for SCG side settings (cell group settings, wireless bearer settings, measurement settings, etc.) to and from terminal devices. For example, in EN-DC or NGEN-DC, the RRC message for E-UTRA transmitted and received between eNB102 and UE122 may contain the RRC message for NR in the form of a container. Similarly, in NE-DC, the RRC message for NR transmitted and received between gNB108 and UE122 may contain the RRC message for E-UTRA in the form of a container. RRC messages for SCG side settings may be transmitted and received between the master node and secondary nodes.

[0208] Furthermore, not only when using MR-DC, the RRC message for E-UTRA sent from eNB102 to UE122 may include an RRC message for NR, and the RRC message for NR sent from gNB108 to UE122 may include an RRC message for E-UTRA.

[0209] This section describes an example of parameters included in an RRC message regarding the reconfiguration of an RRC connection.

[0210] Figure 7 is an example of an ASN.1 description representing the fields and / or information elements related to the radio bearer configuration included in the message regarding the reconfiguration of the RRC connection in NR, as shown in Figure 4.

[0211] Figure 8 is an example of an ASN.1 description representing the fields and / or information elements related to the radio bearer configuration included in the message regarding the reconfiguration of the RRC connection in E-UTRA, as shown in Figure 4.

[0212] In the examples of ASN.1 in embodiments of the present invention, not limited to Figures 7 and 8, <omitted> and <omitted> indicate that other information is omitted, not part of the ASN.1 notation. Information elements may also be omitted where <omitted> or <omitted> is not present. The examples of ASN.1 in embodiments of the present invention do not strictly follow the ASN.1 notation method. The examples of ASN.1 in embodiments of the present invention are examples of RRC message parameters in embodiments of the present invention, and other names or notations may be used. Furthermore, to avoid making the explanation complicated, only examples of main information closely related to one embodiment of the present invention are shown.

[0213] In addition, parameters described in ASN.1 are sometimes referred to as "information elements" without distinguishing between fields, information elements, etc. Also, in embodiments of the present invention, fields, information elements, etc. described in ASN.1 included in the RRC message may be referred to as "information" or as "parameters." The message relating to the resetting of the RRC connection may be an RRC reset message in NR or an RRC connection reset message in E-UTRA.

[0214] This section describes cell activation and deactivation. In terminal devices communicating via dual connectivity, the master cell group (MCG) and secondary cell group (SCG) are configured by the message regarding the reconfiguration of the RRC connection mentioned above. Each cell group may consist of a special cell (SpCell) and zero or more other cells (secondary cells: SCell). The SpCell of the MCG is also called a PCell. The SpCell of the SCG is also called a PSCell. Cell deactivation does not apply to SpCells, but may apply to SCells.

[0215] Furthermore, cell deactivation may not be applied to PCell but may be applied to PSCell. In this case, the cell deactivation process may differ between SpCell and SCell.

[0216] Cell activation and deactivation may be handled by MAC entities present in each cell group. SCells configured on a terminal device may be activated and / or deactivated by (A), (B), and / or (C) below. (A) Reception of MAC CE indicating SCell activation / inactivation (B) A SCell deactivation timer is set for each SCell that does not have PUCCH configured (the SCell is deactivated when the timer expires). (C) SCell state (sCellState) is set for each SCell by the RRC message (SCells are activated based on the fact that the SCell configuration includes a field for SCell state).

[0217] Specifically, the MAC entity of the terminal device may perform some or all of the following processes (AD) for each SCell configured in the cell group.

[0218] (Processing AD) (1) If the RRC parameter (SCell state) is set to activated when the SCell is set, or if a MAC CE that activates the SCell is received, the MAC entity of UE122 performs action (AD-1). Otherwise, if a MAC CE that deactivates the SCell is received, or if the SCell deactivation timer expires for an activated SCell, the MAC entity of UE122 performs action (AD-2). (2) If an uplink grant or downlink assignment is notified by the PDCCH of an active SCell, or if an uplink grant or downlink assignment is notified by the PDCCH of a serving cell for an active SCell, or if a MAC PDU is sent for a configured uplink grant, or if a MAC PDU is received for a configured downlink assignment, the MAC entity of UE122 restarts the SCell inactive timer associated with that SCell. (3) If SCell becomes inactive, the MAC entity of UE122 performs the action (AD-3).

[0219] (Process AD-1) The MAC entity of the terminal device may perform some or all of the following (1) to (3): (1) If, in NR, this SCell was inactive before receiving a MAC CE to activate it, or if the RRC parameter (sCellState) set for that SCell during SCell configuration was set to activated, the MAC entity of UE122 performs processing (AD-1-1). (2) The MAC entity of UE122 starts or restarts the SCell deactivation timer associated with its SCell (if it has already started). (3) If the Active DL BWP is not a Dormant BWP, and there is a suspended Type 1 configured uplink grant associated with this SCell according to the stored configuration, the MAC entity of UE122 will (re)initialize it. The MAC entity of UE122 will then trigger a PHR.

[0220] (Process AD-1-1) The MAC entity of the terminal device may perform some or all of the following (1) to (3): (1) If the BWP indicated by the first Active Downlink BWP-Id set in the RRC message for that SCell is not set as a Dormant BWP, the MAC entity of UE122 performs processing (AD-1-1-1). (2) If the BWP indicated by the first Active Downlink BWP-Id set in the RRC message for that SCell is set to Dormant BWP, the MAC entity of UE122 stops the BWP Inactivity Timer (bwp-InactivityTimer) for this serving cell, if it is running. (3) The MAC entity of UE122 activates the downlink BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) and the uplink BWP indicated by the first active uplink BWP identifier (firstActiveUplinkBWP-Id), which are set in the RRC message for its SCell.

[0221] (Process AD-1-1-1) The MAC entity of the terminal device may activate SCell at a predetermined time and apply (perform) normal SCell operations, including some or all of the following (A) through (E). (A) Transmission of sounding reference signal (SRS) in this SCell (B) Reporting of channel status information (CSI) for this SCell (C) Monitoring of PDCCH in this SCell (D) Monitoring of PDCCH for this SCell (if scheduling is performed for this SCell in other serving cells) (E) If PUCCH is set, PUCCH transmission in this SCell

[0222] (Process AD-2) The MAC entity of the terminal device may perform some or all of the following (A) through (D): (A) Deactivate this SCell at the default timing. (B) Stop the SCell deactivation timer associated with this SCell. (C) Deactivate all Active BWPs associated with this SCell. (D) Flushes the HARQ buffer associated with this SCell.

[0223] (Process AD-3) The MAC entity of the terminal device may perform some or all of the following (A) through (D): (A) Do not send SRS with this SCell. (B) Do not report a CSI for this SCell. (C) Do not send PUCCH, UL-SCH, and / or RACH with this SCell. (D) Do not monitor the PDCCH of this SCell, and / or the PDCCH for this SCell.

[0224] As described above, the MAC entity performs processing (AD) to activate and deactivate SCells.

[0225] Furthermore, as mentioned above, when a SCell is added, its initial state may be set by an RRC message.

[0226] Here, we will explain the SCell deactivation timer. For SCells for which PUCCH is not set, the value of the SCell deactivation timer (information about the time at which the timer is considered to have expired) may be notified by an RRC message. For example, if the RRC message notifies that the value of the SCell deactivation timer is 40ms, then in the above process (AD), the timer will be considered to have expired when the notified time (40ms in this case) has elapsed since the timer was started or restarted without the timer stopping. The SCell deactivation timer may also be named a timer called sCellDeactivationTimer.

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

[0228] A BWP may be part or all of the bandwidth of a serving cell. A BWP may also be referred to as a Carrier BWP. A terminal device may have one or more BWPs configured. A BWP may be configured by information contained in broadcast information associated with a synchronization signal detected during an initial cell search. Another BWP may be a frequency bandwidth associated with the frequency at which the initial cell search is performed. A third BWP may be configured by RRC signaling (e.g., Dedicated RRC signaling).

[0229] Furthermore, the downlink BWP (DL BWP) and the uplink BWP (UL BWP) may be configured separately. Also, one or more uplink BWPs may be associated with one or more downlink BWPs. The association between uplink BWPs and downlink BWPs may be a default association, an association by RRC signaling (e.g., Dedicated RRC signaling), an association by physical layer signaling (e.g., an association by downlink control information (DCI) notified on the downlink control channel), or a combination of these.

[0230] A BWP may consist of a group of consecutive Physical Resource Blocks (PRBs). Furthermore, parameters for each component carrier's BWP (one or more BWPs) may be set for a connected terminal device.

[0231] The BWP parameters for each component carrier include: (A) the type of cyclic prefix, (B) the subcarrier spacing, (C) the frequency position of the BWP (e.g., the starting position or central frequency position of the low-frequency side of the BWP) (the frequency position may be, for example, an ARFCN, or an offset from a specific subcarrier of the serving cell. The unit of the offset may be in subcarrier units or resource block units. Both ARFCN and offset may be set.), (D) the bandwidth of the BWP (e.g., the number of PRBs), (E) resource setting information for the control signal, and (F) the center frequency position of the SS block (the frequency position may be, for example, an ARFCN, or an offset from a specific subcarrier of the serving cell.

[0232] Furthermore, the offset unit may be subcarrier units or resource block units. Also, both ARFCN and offset may be set. ), some or all of the following may be included. In addition, the resource setting information of the control signals may be included in the BWP settings of at least some or all of PCell and / or PSCell.

[0233] A terminal device may transmit and receive data using the active BWP (Active BWP) among one or more configured BWPs. A terminal device may be configured such that, at any given time, a maximum of one uplink BWP and / or one downlink BWP among the one or more BWPs configured for a single serving cell associated with it are active. An activated downlink BWP is also referred to as an Active DL BWP. An activated uplink BWP is also referred to as an Active UL BWP.

[0234] Next, we will explain BWP deactivation. One or more BWPs may be set in a single serving cell. BWP switching in a serving cell is used to activate an inactive BWP (also called an inactive BWP) and deactivate an activated BWP.

[0235] BWP switching is controlled by the MAC entity itself for a PDCCH indicating downlink allocation or uplink grant, a BWP inactivity timer, RRC signaling, or the initiation of a random access procedure. The active BWP of a serving cell is indicated by the RRC or PDCCH.

[0236] Next, we will explain dormant BWPs. Entering or leaving a dormant BWP is done by switching BWPs. This control is performed by PDCCH for each SCell or for groups called Dormancy SCell Groups. The setting of dormant SCell Groups is indicated by RRC signaling. Also, in the current specification, dormant BWPs apply only to SCells. It should be understood that a dormant BWP is not a BWP that is changed into a dormant state, but rather one BWP set for dormancy among one or more BWPs set for the UE. Furthermore, there may be multiple BWPs set for dormancy on the UE.

[0237] A BWP may be dormant if its configuration does not include certain parameters. For example, a BWP may be dormant if it does not include the PDCCH-Config information element, which is an information element for setting UE-specific PDCCH parameters included in the configuration of a downlink BWP. Alternatively, a BWP may be dormant if some of the parameters included in the PDCCH-Config information element, which is an information element for setting UE-specific PDCCH parameters included in the configuration of a downlink BWP, are not set (not included). For example, a BWP may be dormant if its configuration does not include some or all of the settings for the search space, which are set by the PDCCH-Config information element and define where and / or how to search for PDCCH candidates.

[0238] Additionally, in certain settings, the setting of a dormant BWP for SpCells such as PCell and PSCell, as well as PUCCH SCells capable of sending PUCCH signals, may be disabled.

[0239] When a UE receives a PDCCH via SpCell indicating that it is exiting a dormant BWP outside of a set period (active time), it activates the downlink BWP indicated by the first downlink BWP identifier previously notified via RRC signaling.

[0240] When a UE receives a PDCCH via SpCell indicating that it will exit a dormant BWP within a set period (active time), it activates the downlink BWP indicated by a second downlink BWP identifier previously notified via RRC signaling.

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

[0242] The above-mentioned entry into and exit from dormant BWPs are performed by switching BWPs, and when a new BWP is activated, the BWP that was previously active is deactivated. In other words, when exiting a dormant BWP, the dormant BWP is deactivated, and when entering a dormant BWP, the dormant BWP is activated.

[0243] Here, we will explain PDCCH, which indicates entering a dormant BWP, and PDCCH, which indicates exiting a dormant BWP.

[0244] For example, a UE configured for intermittent reception (DRX) in SpCell may monitor the PDCCH in SpCell's Active BWP outside of the DRX active time to detect a certain DCI format (e.g., DCI format 2_6). The CRC of the DCI format may be scrambled with a certain RNTI (e.g., PS-RNTI).

[0245] A UE with a dormant SCell group configured determines the switching of the Active DL BWP based on the bitmap information contained in the DCI format 2_6 payload. For example, if a bit in the bitmap is associated with a dormant SCell group, and the bit is 1, the UE may perform a BWP switch to another pre-configured BWP if the Active DL BWP is a dormant BWP, or remain in that BWP if the Active DL BWP is not a dormant BWP. Alternatively, if the bit is 0, the UE may perform a BWP switch so that the Active DL BWP becomes a dormant BWP.

[0246] During the DRX's active time, the UE does not need to monitor the PDCCH for the purpose of detecting DCI format 2_6.

[0247] A UE configured for intermittent reception (DRX) in SpCell may monitor the PDCCH with the SpCell's Active BWP during the DRX active time to detect a certain DCI format (e.g., DCI formats 0_1 and 1_1). The CRC of the DCI format may be scrambled with a certain RNTI (e.g., C-RNTI or MCS-C-RNTI). A UE configured for a dormant SCell group will determine the switching of the Active DL BWP based on the bitmap information contained in the DCI format 0_1 ​​or DCI format 1_1 payload.

[0248] For example, a certain bit in a bitmap is associated with one dormant SCell group. When the bit is 1, if the Active DL BWP is a dormant BWP, a BWP switch may be executed to another pre-configured BWP; if the Active DL BWP is not a dormant BWP, it may remain in that BWP. Also, when the bit is 0, a BWP switch may be executed so that the Active DL BWP becomes a dormant BWP. Further, the "another pre-configured BWP" may be a BWP different from the "another pre-configured BWP" used in the description of DCI format 2_6.

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

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

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

[0252] In each serving cell where the BWP is configured and activated, the MAC entity may perform some or all of the following (A) to (G) if the BWP is activated (is an Active BWP) and if that BWP is a dormant BWP. (A) Stop the BWP inactive timer of the serving cell of this BWP if it is running. (B) Do not monitor the PDCCH of that BWP. (C) Do not monitor the PDCCH for that BWP. (D) Do not receive the DL-SCH in that BWP. (F) Do not transmit the SRS in that BWP. (G) Do not transmit the UL-SCH in that BWP. (H) Do not transmit the RACH in that BWP. (I) Do not transmit the PUCCH in that BWP. (J) Clear the configured downlink assignment and the configured grant type 2 configured uplink grant associated with that SCell, respectively. (K) Suspend the configured grant type 1 configured uplink grant associated with that SCell. (L) If a setting related to beam failure is set, detect beam failure, and if beam failure is detected, perform beam failure recovery.

[0253] The MAC entity may perform some or all of the following (A) to (I) if the BWP is deactivated. (A) Do not transmit the UL-SCH in that BWP. (B) Do not transmit the RACH in that BWP. (C) Do not monitor PDCCH with that BWP. (D) Do not send a PUCCH with that BWP. (E) Do not report CSI in that BWP. (F) Do not send SRS with that BWP. (G) Do not receive DL-SCH with that BWP. (H) Clear the Grant Type 2 Configured Ascending Link Grant set in that BWP. (I) Suspend the configured uplink grant of the inactive BWP (Inactive BWP) Grant Type 1.

[0254] Next, we will describe the random access procedure in a UE with a BWP configured. When a random access procedure is initiated in a serving cell, the MAC entity may perform some or all of the following operations (A) through (E) on the selected carrier of that serving cell. (A) If the resource (occasion) sending PRACH is not configured for the Active UL BWP, (A1) the Active UL BWP is switched to the BWP indicated by the RRC parameter (initialUplinkBWP), and (A2) if the serving cell is a SpCell, the Active UL BWP is switched to the BWP indicated by the RRC parameter initialDownlinkBWP. (B) If the resource (occasion) that sends PRACH is configured for the Active UL BWP, and the serving cell is a SpCell, and the Active DL BWP and Active UL BWP do not have the same identifier (bwp-Id), then the Active DL BWP is switched to a BWP with the same identifier as the Active UL BWP. (C) If the BWP inactivity timer associated with this serving cell's Active DL BWP is running, stop this timer. (D) If the serving cell is SCell, and if the BWP inactivity timer associated with the SpCell's Active DL BWP is running, stop this timer. (E) Execute a random access procedure on the Active DL BWP of SpCell and the Active UL BWP of this serving cell.

[0255] Next, we will explain the BWP inactivity timer. For each activated serving cell on which a BWP inactivity timer is set, the MAC entity performs the following (A) action. The BWP inactivity timer may also be named a timer called bwp-InactivityTimer. (A) If the default downlink BWP identifier (defaultDownlinkBWP-Id) is set and the Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), or if the default downlink BWP identifier (defaultDownlinkBWP-Id) is not set, the Active DL BWP is not initialDownlinkBWP, and the Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), then the MAC entity performs the following actions (A-1) and (A-2). (A-1) If an Active DL BWP receives a PDCCH addressed to C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant, or if an Active DL BWP receives a PDCCH addressed to C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant, or if a MAC PDU is sent in a configured uplink grant, or if a MAC PDU is received in a configured downlink assignment, the MAC entity performs the following (A-1-1): (A-1-1) If no random access procedure associated with this serving cell is currently running, or if a running random access procedure associated with this serving cell is successfully completed by receiving a PDCCH addressed to C-RNTI, start or restart the BWP inactivity timer associated with the Active DL BWP. (A-2) If the BWP inactivity timer associated with the Active DL BWP expires, the MAC entity performs the following action (A-2-1). (A-2-1) If defaultDownlinkBWP-Id is set, the BWP will be switched to the BWP indicated by defaultDownlinkBWP-Id; otherwise, the BWP will be switched to initialDownlinkBWP.

[0256] Furthermore, if the MAC entity receives a PDCCH for BWP switching and switches the Active DL BWP, it may perform the following (A) process. (A) If a default downlink BWP identifier (defaultDownlinkBWP-Id) is set, and the switched Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), and if the switched Active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id, then start or restart the BWP inactivity timer associated with the Active DL BWP.

[0257] This section describes an example of the behavior related to Radio Link Failure (RLF) in terminal devices connected via RRC.

[0258] The terminal device obtains information from the base station device located within its service area, such as the values ​​of timers (e.g., T310 and T313) for detecting physical layer problems in the serving cell (t310 and t313), the threshold values ​​for the number of out-of-sync detections (OoS) (N310 and N313), and the threshold values ​​for the number of in-sync detections (IS) (N311 and N314), through broadcast information and RRC messages to individual users. The timer values ​​and threshold values ​​may be set to default values. Furthermore, the timer names may differ between EUTRA and NR.

[0259] For wireless link monitoring, the physical layer processing unit of a terminal device notifies the higher-layer RRC layer processing unit of "out-of-sync" when it estimates that the serving cell's wireless link quality is worse than a specific threshold (Qout) for a certain period (e.g., TEvaluate_Qout=200ms) or longer, based on information such as the received power of the received reference signal and / or the received power of the synchronization signal and / or the packet error rate. Furthermore, the physical layer processing unit notifies the higher-layer RRC layer processing unit of "in-sync" when it estimates that the serving cell's wireless link quality is worse than a specific threshold (Qin) for a certain period (e.g., TEvaluate_Qin=100ms) or longer, based on information such as the received power of the received reference signal and / or the received power of the synchronization signal and / or the packet error rate. The physical layer processing unit may also set a specific interval (e.g., TReport_sync=10ms or longer) between notifications of out-of-sync or in-sync to the higher layer.

[0260] Here, for example, threshold Qout may be defined as the level at which the downlink radio link cannot be reliably received, and the hypothetical block error rate of the downlink control channel (PDCCH) transmission, based on default parameters, is a first specific percentage. Alternatively, for example, threshold Qin may be defined as the level at which the downlink radio link quality can be reliably received more reliably than the Qout state, and the hypothetical block error rate of the downlink control channel transmission, based on default parameters, is a second specific percentage. Furthermore, multiple block error rates (levels of threshold Qout and threshold Qin) may be defined based on the frequency used, subcarrier spacing, type of service, etc. The first specific percentage and / or the second specific percentage may be default values ​​specified in the specification. Also, the first specific percentage and / or the second specific percentage may be values ​​notified or broadcast from the base station equipment to the terminal equipment.

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

[0262] The aforementioned monitoring setting (RadioLinkMonitoringConfig) may be set for each downlink BWP. The terminal device may perform radio link monitoring based on the monitoring setting configured for the BWP that is the Active DL BWP. The terminal device may also perform radio link monitoring based on the monitoring setting configured for the default BWP or the BWP designated by the base station device under specific conditions.

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

[0264] In the primary cell, the RRC layer processing unit of the terminal device may start or restart the timer (T310) if it receives a predetermined number of (N310) consecutive "out of synchronization" notifications from the physical layer processing unit. The RRC layer processing unit of the terminal device may also stop the timer (T310) if it receives a predetermined number of (N311) consecutive "synchronizing" notifications. The RRC layer processing unit of the terminal device may also perform a transition to an idle state or a procedure to re-establish the RRC connection when the timer (T310) expires. For example, the operation of the terminal device may differ depending on the establishment status of AS Security. If AS Security is not established, the terminal device transitions to the RRC IDLE state; if AS Security is established, the terminal device may perform a procedure to re-establish the RRC connection. Furthermore, in the decision to start or restart the timer T310, the condition that none of a specific set of timers are running may be added.

[0265] Furthermore, in a primary secondary cell, the RRC layer processing unit of a terminal device may start or restart the timer (T313) if it receives a predetermined number of (N313) consecutive "out of synchronization" notifications from the physical layer processing unit. The RRC layer processing unit of a terminal device may also stop the timer (T313) if it receives a predetermined number of (N314) consecutive "synchronizing." When the timer (T313) expires, the RRC layer processing unit of a terminal device may execute an SCG failure information procedure to notify the network of an SCG failure. Note that an SCG failure is also referred to as an SCG failure. The SCG failure information procedure is also referred to as an SCG failure information procedure.

[0266] Furthermore, in SpCell (PCell in MCG, and PSCell in SCG), the RRC layer processing unit of the terminal device may start or restart the timer (T310) of each SpCell if it receives a predetermined number of consecutive (N310) out-of-synchronization notifications from the physical layer processing unit. Also, the RRC layer processing unit of the terminal device may stop the timer (T310) of each SpCell if it receives a predetermined number of consecutive (N311) synchronization in progress. When the timer (T310) of each SpCell expires, the RRC layer processing unit of the terminal device may, if the SpCell is a PCell, perform a procedure to transition to an idle state or to re-establish the RRC connection. Also, if the SpCell is a PSCell, it may execute the SCG failure information procedure to notify the network of an SCG failure.

[0267] Furthermore, for example, in order to detect an early physical layer problem, the RRC layer processing unit of the terminal device may start a timer (T314) if it receives a predetermined number of consecutive early synchronization outages (N310 times) notified by the physical layer processing unit. Also, while T314 is running, the RRC layer processing unit of the terminal device may stop the timer (T314) if it receives a predetermined number of consecutive synchronization in progress (N311 times).

[0268] Furthermore, the RLM-RS may be undefined if it is not explicitly or implicitly configured from the network. If the RLM-RS is not configured from the network (e.g., base station equipment), the terminal device may perform wireless link monitoring using a reference signal that meets the default conditions.

[0269] Furthermore, RLM-RS is a reference signal used for wireless link monitoring, and multiple RLM-RS signals may be configured on the terminal device. The resource of one RLM-RS may be one SS block or one CSI-RS resource (or port).

[0270] Furthermore, wireless link monitoring using CRS may be performed in EUTRA cells, and wireless link monitoring using RLM-RS may be performed in NR cells, but is not limited to this.

[0271] This section describes the detection of wireless link failures based on wireless link monitoring.

[0272] The terminal device determines that a wireless link failure has been detected in the MCG when timer T310 expires, or when timer T312 expires, or when a random access problem is notified from the MAC layer of the MCG when none of several specific timers are running, or when the RLC layer of the MCG notifies that the maximum number of retransmissions for SRB or DRB has been reached. The aforementioned specific timers do not include timer T310 and timer T312.

[0273] The terminal device determines that a wireless link failure has been detected in the SCG when timer T310 expires in the SCG, when timer T312 expires in the SCG, when a random access problem is notified from the MAC layer of the SCG when none of several specific timers are running, or when the RLC layer of the SCG notifies that the maximum number of retransmissions for SRB or DRB has been reached. The aforementioned specific timers do not include timer T310 and timer T312.

[0274] The random access issue can be addressed in a MAC entity when the number of retries for a random access preamble reaches a predetermined number. If the random access preamble was sent via a SpCell, the MAC entity of the cell group containing that SpCell may notify the higher layer (in this case, the RRC entity).

[0275] When the terminal device determines that a wireless link failure has been detected in the MCG, it stores various information as wireless link failure information. If AS security is not activated, it sets the release reason to "Other" and starts the process of leaving RRC_CONNECTED. If AS security is activated, it starts the procedure to re-establish the RRC connection.

[0276] When Timer T313 expires, or when a random access problem is reported from the SCG's MAC layer, or when the SCG's RLC layer reports that the maximum number of retransmissions has been reached, the terminal device determines that a radio link failure has been detected in the SCG and begins processing to report the relevant information as an SCG radio link failure to the base station device.

[0277] Next, we will describe the procedures for detecting and recovering beam failures.

[0278] In a MAC entity, a beam failure recovery procedure may be configured by the RRC for each serving cell. Beam failures are detected by counting beam failure instance notifications sent from lower layers (PHY layers) to the MAC entity. The MAC entity may perform some or all of the following processes (A), (B), and (C) in each serving cell for beam failure detection. (A) If a beam failure instance notification is received from a lower layer, the timer (beamFailureDetectionTimer) is started or restarted and the counter (BFI-COUNTER) is incremented by one. If the value of BFI_COUNTER is greater than or equal to the set threshold (beamFailureInstanceMaxCount), the process in (A-1) below is performed. (A-1) If the serving cell is an SCell, trigger beam failure recovery (BFR) for this serving cell; otherwise, initiate a random access procedure on the SpCell. (B) If the beamFailureDetectionTimer for this serving cell expires, or if the settings for beamFailureDetectionTimer, beamFailureInstanceMaxCount, and / or the reference signal for beam failure detection are changed by a higher layer, set BFI_COUNTER to 0. (C) If the serving cell is a SpCell and the random access procedure is successfully completed, set BFI_COUNTER to 0, stop the timer (beamFailureRecoveryTimer), and consider the beam failure recovery procedure to have been successfully completed. Otherwise, if the serving cell is an SCell and receives a PDCCH addressed to C-RNTI indicating a new uplink grant to transmit information for beam failure recovery of the SCell (e.g., information contained in the SCell BFR MAC CE), or if the SCell is inactive, set BFI_COUNTER to 0, consider the beam failure recovery procedure to have been successfully completed, and cancel all beam failure recoveries (BFRs) triggered for this serving cell.

[0279] The MAC entity performs the following action (A) based on the fact that at least one beam failure recovery (BFR) has been triggered by the beam failure recovery procedure and has not been canceled. (A) If the UL-SCH resource can include the SCell's BFR MAC CE and its subheaders, taking into account the logical channel priority, then include the SCell's BFR MAC CE and its subheaders. Otherwise, if the UL-SCH resource can include the SCell's truncated BFR MAC CE and its subheaders, taking into account the logical channel priority, then include the SCell's truncated BFR MAC CE and its subheaders. Otherwise, trigger a scheduling request for SCell beam failure recovery.

[0280] SCell dormancy is achieved by activating the dormant BWP within the SCell. Furthermore, even when an SCell is dormant, beam management, including CSI measurement, automatic gain control (AGC), and beam failure recovery, may be performed within the SCell.

[0281] Next, we will explain how to add SCG PSCells and zero or more SCells to a terminal device.

[0282] The addition of a PSCell and zero or more SCells to an SCG may be performed by an RRC message regarding the reconfiguration of the RRC connection. Figures 9 to 13 are examples of ASN.1 descriptions representing fields and / or information elements related to the addition of a PSCell and zero or more SCells to an SCG, as included in an RRC connection reconfiguration message in NR.

[0283] To avoid making the explanation too complicated, the messages and / or information elements in each diagram may differ from the actual message structure and / or information element structure, with some structured fields and information elements being expanded and / or fields and information elements not directly related to the explanation being omitted.

[0284] As shown in Figure 9, an RRCReconfiguration message may be used to add a PSCell and zero or more SCells to the SCG. The RRCReconfiguration message may include some or all of the information (A) through (E) below. In addition, the RRCReconfiguration message may include other information. (A) RRC transaction identifier (rrc-TransactionIdentifier) (B) Settings for adding, modifying, and releasing wireless bearers (radioBearerConfig) (C) Secondary Cell Group Settings (D) Master Cell Group Settings (masterCellGroup) (E) RRC settings for secondary cell groups in MR-DC (mrdc-SecondaryCellGroupConfig)

[0285] When an RRC reconfiguration message is sent to a terminal device via SRB3, the SCG setting may be notified by the setting in (C) above in the RRCReconfiguration message. Also, when an RRC reconfiguration message is sent to a terminal device via SRB1, the SCG setting may be notified by an RRC reconfiguration message generated by a secondary node, which is included in (E) above in the RRCReconfiguration message generated by the master node. In this case, the SCG setting may be notified by the setting in (C) above included in the RRC reconfiguration message generated by the secondary node. Alternatively, a different message may be used for SCG setting.

[0286] The settings for the secondary cell group described above may be provided by the CellGroupConfigIE element. As shown in Figure 10, the CellGroupConfigIE element may include some or all of the information (A) through (H) below. In addition, the CellGroupConfigIE element may include other information. (A) Cell group identifier (cellGroupId) (B) Settings for adding and / or modifying RLC bearers (rlc-BearerToAddModList) (C) RLC Bearer release settings (rlc-BearerToReleaseList) (D) MAC settings for this cell group (mac-CellGroupConfig) (E) PHY settings for this cell group (physicalCellGroupConfig) (F) SpCell settings (spCellConfig) (G) Settings for adding and modifying SCells (sCellToAddModList) (H) Settings for releasing SCells (sCellToReleaseList)

[0287] The SpCell settings in (F) above may add and / or configure SpCells, and the settings in (G) and (H) above may add, modify, and / or release SCells. These actions may also be performed by other messages.

[0288] The SpCell settings described above may include some or all of the information (A) through (D) below, as shown in Figure 11. The SpCell settings may also include other information. (A) An index (servCellIndex) for identifying serving cells from one another. (B) Reconfiguration with Sync (C) Information on timer values ​​and constants used for determining wireless link failures, etc. (rlf-TimersAndConstants) (D) Setting of terminal device-specific parameters for SpCell (spCellConfigDedicated)

[0289] The synchronized reset information elements described above may include some or all of the information (A) through (D) below, as shown in Figure 12. Furthermore, the synchronized reset information may also include other information. (A) Setting cell-specific parameters for SpCell (spCellConfigCommon) (B) The value of the new terminal identifier (UE-Identity) (newUE-Identity) (C) Timer T304 value (t304) (D) Setting terminal device-specific parameters for RACH (rach-ConfigDedicated)

[0290] The terminal device-specific parameters for RACH described above may include parameters used for continuation-free random access (CFRA). If CFRA is not included in the settings, the terminal device may perform contition-based random access in the random access procedure. CFRA may include information on RA occasions used in continuation-free random access.

[0291] The information element (ServingCellConfig IE) that indicates the settings of terminal device-specific parameters for the SpCell described above may include some or all of the information from (A) to (C) below. (A) Information on the initial downlink BWP (initialDownlinkBWP) (B) Information on adding / modifying downlink BWPs (downlinkBWP-ToAddModList) (C) Identifier information for the first active downlink BWP (firstActiveDownlinkBWP-Id)

[0292] The above initial downlink BWP information is a setting for the terminal device-specific (UE-Specific) initial downlink BWP (BWP identifier #0). The terminal device may consider BWP identifier #0 to be the BWP set in RRC if any optional IE is included in the information of this initial downlink BWP.

[0293] The identifier of the first active downlink BWP is the identifier of the downlink BWP that is activated when RRC reconfiguration is performed, if identifier information for the first active downlink BWP is set for the SpCell. Similarly, if identifier information for the first active downlink BWP is set for an SCell, the downlink BWP indicated by this identifier information is activated when the SCell is activated. Furthermore, if identifier information for the first active downlink BWP is set for an SpCell, the downlink BWP of the SpCell indicated by this identifier information may be activated when the SCG is activated. In the same manner, identifier information for the first active uplink BWP may be set on the terminal device. The identifier information for the first active uplink BWP may be set on the terminal device using the same or different information elements as the identifier information for the first active downlink BWP. The BWP identifier set in the identifier information for the first active downlink BWP and the BWP identifier set in the identifier information for the first active uplink BWP may be the same value or may be different values. If identifier information for the first active uplink BWP is set for a SpCell, the uplink BWP of the SpCell indicated by this identifier information may be activated when the SCG is activated. In this case, the BWP identifier set in the identifier information for the first active downlink BWP and the BWP identifier set in the identifier information for the first active uplink BWP may be the same value.

[0294] The cell-specific parameters of the SpCell described above may be provided by an information element (ServingCellConfigCommon IE) used to set the cell-specific parameters of a serving cell. The information element used to set the cell-specific parameters of a serving cell may include some or all of the information (A) to (D) below, as shown in Figure 13. In addition, the information element used to set the cell-specific parameters of a serving cell may include other information. (A) Physical cell identifier (physCellId) (B) Common parameters for downlinks in cells (downlinkConfigCommon) (C) Common parameters for uplinks in cells (uplinkConfigCommon) (D) Setting of SCell terminal device-specific parameters (including some cell-specific parameters) (sCellConfigDedicated) (E) SSB subcarrier spacing information (ssbSubcarrierSpacing)

[0295] Common parameters for downlinks in a cell may include downlink frequency information (frequencyInfoDL) and / or initial downlink BWP information (initialDownlinkBWP). Downlink frequency information may include the SSB frequency information used in this serving cell.

[0296] The settings for adding or modifying the above SCell may be provided by one or more SCell configuration information elements (SCellConfigIE). As shown in Figure 14, the SCell configuration information elements may include some or all of the information (A) through (D) below. Furthermore, the SCell configuration information elements may also include other information. (A) Identifier that identifies a SCell (sCellIndex) (B) Setting cell-specific parameters for SCell (sCellConfigCommon) (C) Setting of SCell terminal device-specific parameters (including some cell-specific parameters) (sCellConfigDedicated) (D) Information indicating SCell activation / inactivation (sCellState-r16)

[0297] As an example, the procedure for adding a PSCell and zero or more SCells to an SCG using the above-mentioned RRC message and information elements is described below. Note that the RRC message and information elements used in this description are examples only, and the names and structures used in actual implementation are not limited to these examples.

[0298] The RRC entity of a terminal device that receives an RRCReconfiguration message may perform some or all of the following actions (A) through (F). The terminal device that receives an RRCReconfiguration message may perform other actions. (A) If RRCReconfiguration includes masterCellGroup, process (BD-1) is performed on the master cell group based on this masterCellGroup. (B) If RRCReconfiguration includes a secondaryCellGroup, process (BD-1) is performed on the secondary cell group based on this secondaryCellGroup. (C) If RRCReconfiguration includes radioBearerConfig, configure the radio bearer based on this radioBearerConfig. (D) Set the content to be included in the RRC reset completion message. (E) If the SpCell configuration (spCellConfig) of the received secondary cell group configuration includes reconfigurationWithSync, start the random access procedure in that SpCell. (F) If the SpCell configuration (spCellConfig) of the MCG or SCG includes reconfigurationWithSync, and the above random access procedure is successfully completed in the NR cell group, the timer T304 for that cell group is stopped.

[0299] (Process BD-1) The RRC entity of the terminal device may perform some or all of the following (A) through (G): (A) If CellGroupConfig contains spCellConfig which includes reconfigurationWithSync, the RRC entity of the terminal device performs some or all of the following (1) to (3): (1) Execute process (BD-2). (2) Resume all suspended radio bearers. (3) Reactivate SCG transmission to all radio bearers if it has been suspended. (B) If CellGroupConfig contains rlc-BearerToReleaseList, the RLC bearer release will be performed based on this rlc-BearerToReleaseList. (C) If CellGroupConfig contains rlc-BearerToAddModList, add and / or modify RLC bearers based on this rlc-BearerToAddModList. (D) If CellGroupConfig contains mac-CellGroupConfig, set the MAC entity for this cell group based on this mac-CellGroupConfig. (E) If CellGroupConfig contains sCellToReleaseList, the SCell release will be performed based on this sCellToReleaseList. (F) If CellGroupConfig contains spCellConfig, configure SpCell based on this spCellConfig. (G) If CellGroupConfig contains sCellToAddModList, perform SCell additions and / or modifications based on this sCellToAddModList.

[0300] (Processing BD-2) The RRC entity of the terminal device may perform some or all of the actions in parentheses from (A) below. (A) If AS security is not activated, the procedure terminates after executing the process to transition to RRC_IDLE. (B) Start timer T304 for the SpCell (the one to be configured) using the value of t304 included in reconfigurationWithSync. (C) If the downlink frequency information (frequencyInfoDL) is included in reconfigurationWithSync, the cell indicated by the physical cell identifier (physCellId) included in reconfigurationWithSync at the SSB frequency indicated by frequencyInfoDL will be determined to be the target SpCell. (D) If the downlink frequency information (frequencyInfoDL) is not included in reconfigurationWithSync, the cell indicated by the physical cell identifier (physCellId) included in reconfigurationWithSync at the SSB frequency of the original SpCell (Source SpCell) is determined to be the target SpCell. (E) Start downlink synchronization of the target SpCell. (F) Obtain the MIB of the target SpCell (Acquire). (G) If no specific bearer (DAPS bearer) is configured, perform some or all of the following steps (1) through (4). (1) Reset the MAC entity for this cell group. (2) If this cell group contains a SCell that is not included in SCellToAddModList, set this SCell to an inactive state. (3) Apply the value of newUE-Identity as the C-RNTI for this cell group. (4) Configure the lower layer based on the received spCellConfigCommon.

[0301] Next, let's discuss Timer T304. Timer T304 may exist for each cell group. Additionally, the value of a timer (in this case, Timer T304) (information about the time at which the timer expires) may be notified via RRC messages. For example, if an RRC message indicates that the timer value is 1000ms, the timer may be considered to have expired if the notified time (1000ms in this example) has elapsed without the timer stopping after it has been started or restarted.

[0302] Based on receiving an RRC reconfiguration message including reconfigurationWithSync, the terminal device may start timer T304 for the cell group to which the reconfigurationWithSync setting is applied.

[0303] The terminal device may stop timer T304 of the cell group to which the reconfigurationWithSync setting is applied, based on the successful completion of random access to the target SpCell indicated by reconfigurationWithSync.

[0304] The terminal device may stop the timer T304 of the SCG based on the fact that the SCG has been released.

[0305] The terminal device may perform the RRC connection re-establishment procedure if the MCG timer T304 has expired and no specific bearer (DAPS bearer) has been configured.

[0306] The terminal device may notify the network of the failure of the synchronized reconfiguration by initiating the SCG failure information procedure once the SCG timer T304 has expired.

[0307] Further explanation will be given regarding the operation of the terminal device when the SCG timer T304 expires.

[0308] If the timer T304 of the secondary cell group expires, the RRC entity of the terminal device will perform the following process (A) if MCG transmission is not suspended, and the following process (B) if MCG transmission is suspended. (A) If a terminal device-specific preamble provided by trach-ConfigDedicated is set, release it and start the SCG failure information procedure to report the failure of the SCG synchronized reconfiguration. (B) Initiate the procedure to re-establish the RRC connection.

[0309] Next, we will explain the procedure for SCG failure information. This procedure may also be called the SCG failure information procedure.

[0310] This procedure may be used to notify the E-UTRAN or NR master node of an SCG failure experienced by a terminal device.

[0311] The RRC entity of the terminal device may initiate this procedure to report an SCG failure if MCG or SCG transmission is not suspended and any of the following conditions (A) through (D) are met: (A) Detected a wireless link failure in the SCG. (B) Detected a failure in the synchronized configuration of the SCG. (C)SCG configuration failure detected. (D) A failure in the integrity check for SRB3 was reported from a lower layer of SCG.

[0312] The RRC entity of the terminal device initiating this procedure performs some or all of the following (A) through (E): (A) Suspend SCG transmissions for all SRBs and DRBs. (B) Reset the SCG MAC. (C) If timer T304 in this SCG is running, stop it. (D) If a conditional reset for PSCell modification is set, stop this evaluation. (E) Configure the content to be included in the SCG Failure Information (SCGFailureInformation) message and submit it to the lower layer to send this message.

[0313] The lower layer of the RRC in the terminal device may transmit the above-mentioned SCG failure information (SCGFailureInformation) message to the base station device.

[0314] The measurement process is described below. The base station equipment transmits measurement configuration information elements (also called measurement settings) to the terminal equipment using the RRC Reconfiguration message of RRC signaling (radio resource control signals) (included in the RRC Reconfiguration message). The terminal equipment performs measurements, event evaluations, and measurement reports for the serving cell and adjacent cells (including listed cells and / or detected cells) according to the information contained in the notified measurement settings. Listed cells are cells listed in the Measurement object (cells notified to the terminal equipment as an adjacent cell list from the base station equipment). Detected cells are cells detected by the terminal equipment at the frequency and subcarrier interval indicated by the Measurement object, but which are not listed in the Measurement object (cells detected by the terminal equipment itself that are not notified as an adjacent cell list).

[0315] For example, (A) the first RRC reset message may include the measurement settings for the MCG, and the field indicating information about the MR-DC's SCG included in the first RRC reset message may include an encapsulated SCG RRC reset message (second RRC reset message), and this second RRC reset message may include the measurement settings for the SCG. In this case, the first RRC reset message notifying the MCG measurement settings and the first RRC reset message notifying the SCG measurement settings may be the same RRC reset message, or they may be different RRC reset messages notified at different times. Alternatively, (B) the MCG measurement settings may be notified by SRB1 and the SCG measurement settings may be notified by SRB3.

[0316] The terminal device may have a variable VarMeasConfig to hold the notified measurement settings. The terminal device may also have a variable VarMeasReportList to hold measurement information that matches the reporting conditions. The terminal device may be notified of measurement settings for each cell group. For each cell group (or for a cell group, or associated with a cell group), the terminal device may have a variable VarMeasConfig to hold each measurement setting and a variable VarMeasReportList to hold measurement information that matches the reporting conditions for each measurement setting.

[0317] Measurements include three types: intra-frequency measurements, inter-frequency measurements, and inter-RAT measurements. Intra-frequency measurements are taken at the serving cell's downlink frequency (downlink frequency) and with the same subcarrier spacing as the serving cell. Inter-frequency measurements are taken at a different frequency than the serving cell's downlink frequency, or at the same frequency but with a different subcarrier spacing. Inter-RAT measurements are taken using a different radio technology (e.g., UTRA, GERAN, CDMA2000, E-UTRA, etc.) than the serving cell's radio technology (e.g., NR).

[0318] Measurement settings may include some or all of the following: lists for adding and / or modifying measurement identifiers (measId), lists for deleting measurement identifiers, lists for adding and / or modifying measurement objects, lists for deleting measurement objects, lists for adding and / or modifying reporting configurations, lists for deleting reporting configurations, quantity settings (quantityConfig), measurement gap settings (measGapConfig), and serving cell quality threshold settings (s-Measure).

[0319] <Quantity configuration (quantityConfig)> The quantityConfig setting specifies the L3 filtering coefficient when the measurement objects are NR and / or E-UTRA. The L3 filtering coefficient defines the ratio (percentage) between the most recent measurement result and past filtered measurement results. The filtered results are used for event evaluation on the terminal device.

[0320] <Measurement Gap Settings (measGapConfig)> The measurement gap setting (measGapConfig) includes information about the length and period of the measurement gap. The measurement gap setting may be configured independently for each terminal device or for each predetermined frequency range.

[0321] <Measurement Identifier (measId)> Here, the measurement identifier (measId) is used to associate (or map, or link) measurement objects with reporting configurations, specifically linking the measurement object identifier (measObjectId) with the reporting configuration identifier (reportConfigId). Each measurement identifier (measId) is associated with one measurement object identifier (measObjectId) and one reporting configuration identifier (reportConfigId). Measurement configurations can be added, modified, or deleted in relation to the relationship between the measurement identifier (measId), measurement objects, and reporting configurations.

[0322] The deletion list for measurement identifiers included in the measurement settings contains a list of measurement identifiers, and the terminal device performs the following (A) to (C) operations for each measurement identifier included in the deletion list for measurement identifiers: (A) Delete the entry for this measurement identifier from the variable VarMeasConfig of the cell group targeted by the measurement settings. (B) If included, delete the entry for the measurement report for this measurement identifier from the variable VarMeasReportList of the cell group targeted by the measurement settings. (C) Stop the timer or timer T321 used for periodic reporting for this measurement identifier if the timer is started, and reset the associated information for this measurement identifier. Note that timer T321 is a timer that is started when a measurement setting that includes a report setting for measuring a cell global identifier is received. This timer is also stopped if the deletion list for report settings, which will be described later, contains an identifier for a report setting aimed at measuring a cell global identifier, or if the detected cell has not reported SIB1.

[0323] The list of measurement identifiers to add and / or modify included in the measurement settings contains a list of measurement identifiers, and the terminal device performs the following (A) to (C) for each measurement identifier included in the list of measurement identifiers to add and / or modify: (A) If an entry for a measurement identifier that matches this measurement identifier exists in the list of measurement identifiers contained in the variable VarMeasConfig of the cell group subject to the measurement settings, replace the entry with the value received for this measurement identifier. Otherwise, add a new entry for this measurement identifier to the variable VarMeasConfig of the cell group subject to the measurement settings. (B) If present, remove the measurement report entry for this measurement identifier from the variable VarMeasReportList of the cell group subject to the measurement settings. (C) If the timer or timer T321 used for periodic reporting for this measurement identifier is started, stop the timer and reset the associated information for this measurement identifier.

[0324] The `measObjectToRemoveList` field in the measurement settings contains information on how to delete a specified measurement object identifier (`measObjectId`) and the measurement objects corresponding to that identifier. In this case, all measurement identifiers (`measId`) in the cell group targeted by the measurement setting, associated with the specified measurement object identifier (`measObjectId`), may be deleted. This field allows for the specification of multiple measurement object identifiers (`measObjectId`) simultaneously.

[0325] The measObjectToAddModList field in the measurement settings is a field that contains information about modifying or adding measurement objects specified by a measObjectId. Multiple measObjectIds can be specified in this field simultaneously.

[0326] The `reportConfigToRemoveList` field contains information about deleting the specified reporting configuration identifier (`reportConfigId`) and the reporting configurations associated with that identifier. In this process, all measurement identifiers (`measId`) associated with the specified reporting configuration identifier (`reportConfigId`) are also deleted. This command allows specifying multiple reporting configuration identifiers (`reportConfigId`) simultaneously.

[0327] The reportConfigToAddModList field contains information about modifying or adding reporting configurations specified by reportConfigId. Multiple reportConfigIds can be specified in this field simultaneously.

[0328] The `measIdToRemoveList` command deletes the specified measurement identifier (measId). However, the measurement object identifier (measObjectId) and report configuration identifier (reportConfigId) associated with the specified measurement identifier (measId) are retained and not deleted. This command allows specifying multiple measurement identifiers (measId) simultaneously.

[0329] The Add and / or Modify List (measIdToAddModifyList) command modifies a specified measurement identifier (measId) to map to a specified object identifier (measObjectId) and a specified report configuration identifier (reportConfigId), or maps a specified object identifier (measObjectId) and a specified report configuration identifier (reportConfigId) to a specified measurement identifier (measId) and adds the specified measurement identifier (measId). This command allows specifying multiple measurement identifiers (measId) simultaneously.

[0330] <Measurement objects> Measurement objects are defined for each RAT and frequency. Furthermore, if the RAT is NR (Noise Reduction), measurement objects may be defined for each frequency and subcarrier interval. Reporting configurations may also exist for NR and for non-NR RATs.

[0331] Measurement objects may include measurement objects NR (measObjectNR), which are measurement objects associated with a measurement object identifier (measObjectId), and measurement objects EUTRA (measObjectEUTRA), which are measurement objects E-UTRA. Furthermore, measurement objects may include some or all of measurement objects UTRA (measObjectUTRA), which are measurement objects UTRA, measurement objects GERAN (measObjectGERAN), which are measurement objects GERAN, measurement objects CDMA2000 (measObjectCDMA2000), and measurement objects WLAN (measObjectWLAN).

[0332] The measObjectId is an identifier used to identify the settings of measurement objects. The settings of measurement objects are defined for each radio access technology (RAT) and frequency, and for NRs, for each subcarrier interval, as described above. Measurement objects may be specified separately for E-UTRA, UTRA, GERAN, and CDMA2000. The measObjectNR, which is the measurement object for an NR, defines the information applicable to the NR's serving cell and adjacent cells. Note that whether a measurement object indicated by a measObjectId corresponds to a serving cell may be indicated by information elements (e.g., serving cell settings) included in RRC messages containing measurement settings and / or RRC messages without measurement settings.

[0333] The measObjectNR may include some or all of the following: frequency information of the block containing the synchronization signal (SSB) (ssbFrequency), subcarrier spacing of the SSB (ssbSubcarrierSpacing), information about the list of cells to be measured, information about the blacklist to be excluded from measurement, and information about the whitelist to be measured.

[0334] Information regarding the list of cells to be measured includes event evaluation and information about the cells to be included in the measurement report. This information includes the physical cell ID and the cell individual offset (indicating the measurement offset value applied to adjacent cells).

[0335] <Reporting configurations> Reporting configurations include a reporting configuration identifier (reportConfigId) and associated reporting configuration NRs (reportConfigNRs), among other things.

[0336] The report configuration identifier (reportConfigId) is an identifier used to identify reporting configurations related to measurements. As mentioned above, reporting configurations related to measurements may include provisions for NRs and provisions for RATs other than NRs (UTRA, GERAN, CDMA2000, E-UTRA, some or all of them). The report configuration NR (reportConfigNR), which is a reporting configuration for NRs, defines the triggering criteria for events used to report measurements in NRs.

[0337] Furthermore, the reportConfigNR may include some or all of the following: event identifier (eventId), trigger quantity (triggerQuantity), hysteresis, trigger time (timeToTrigger), report quantity (reportQuantity), maximum number of report cells (maxReportCells), report interval (reportInterval), and report amount (reportAmount).

[0338] Next, we will explain the report configuration NR (reportConfigNR). The event identifier (eventId) is used to select the criteria for event-triggered reporting. Here, event-triggered reporting is a method of reporting measurements when event trigger conditions are met. In addition, there is also event-triggered periodic reporting, which reports measurements a certain number of times at regular intervals when event trigger conditions are met.

[0339] When the event trigger condition specified by the event identifier (eventId) is met, the terminal device sends a measurement report to the base station device. The trigger quantity is the quantity used to evaluate the event trigger condition. Specifically, the reference signal received power (RSRP) or reference signal received quality (RSRQ) is specified. In other words, the terminal device uses the quantity specified by this trigger quantity to measure the synchronization signal of the downlink and determines whether or not the event trigger condition specified by the event identifier (eventId) is met. Hysteresis is a parameter used in the event trigger condition. The trigger time (timeToTrigger) indicates the period during which the event trigger condition should be met. The report quantity indicates the quantity to be reported in the measurement report. Here, the quantity specified by the trigger quantity (triggerQuantity), or the reference signal received power (RSRP) or reference signal received quality (RSRQ) is specified. The maximum number of reportable cells (maxReportCells) indicates the maximum number of cells to include in the measurement report. The reportInterval is used for periodic reporting or event-triggered periodic reporting, and reports are made at the interval indicated by the reportInterval. The reportAmount specifies the number of times periodic reporting will be performed, if necessary.

[0340] Furthermore, the threshold parameters and offset parameters (a1_Threshold, a2_Threshold, a3_Offset, a4_Threshold, a5_Threshold1, a5_Threshold2, a6_Offset, c1_Threshold, c2_Offset) used in the event trigger conditions may be notified to the terminal device along with the event identifier (eventId) in the report configuration NR (reportConfigNR).

[0341] <About event trigger conditions> Multiple event trigger conditions are defined for sending measurement reports, each with its own join and leave conditions. Specifically, a terminal device that meets the join conditions for an event specified by the base station device sends a measurement report to the base station device. Conversely, a terminal device that meets the leave conditions for an event specified by the base station device sends a measurement report to the base station device if it is configured to trigger a report when the leave conditions are met (i.e., if the report setting includes reportOnLeave).

[0342] Furthermore, the reporting configuration for non-NR RATs, called InterRAT (reportConfigInterRAT), defines multiple triggering criteria for events used to report measurements in non-NR RATs. For example, if the measurement results of an adjacent cell (another RAT) are better than the threshold b1_Threshold set for each RAT after applying each parameter, event B1 occurs. Also, if the measurement results of PCell are worse than the threshold b2_Threshold1 after applying each parameter, AND the measurement results of an adjacent cell (another RAT) are better than the threshold b2_Threshold2 set for each RAT after applying each parameter, event B2 occurs.

[0343] Note that the base station equipment may or may not notify the serving cell quality threshold (s-Measure). When the serving cell quality threshold (s-Measure) is set on the terminal equipment by the base station equipment, and the quality of the serving cell (PCell) after Layer 3 filtering (RSRP value) is lower than the serving cell quality threshold (s-Measure), the terminal equipment will perform measurements of adjacent cells at the frequency and RAT specified by the measurement target. On the other hand, if the serving cell quality threshold (s-Measure) is not set on the terminal equipment by the base station equipment, the terminal equipment will perform measurements of adjacent cells regardless of the quality of the serving cell (RSRP value).

[0344] <Measurement Resultについて> The terminal device may initiate the measurement reporting procedure when an event trigger condition is met, when the first measurement result of the periodic report becomes available, or when the periodic report timer or timer T321 expires. The purpose of the measurement reporting procedure is to transmit the measurement report from the terminal device to the network. The measurement report includes the measurement result. A measurement result is set for each measurement identifier for which the measurement reporting procedure was triggered.

[0345] The measurement results may include a measurement identifier (measId), a list of serving measurement results (measResultServingMO), and neighboring cell measurement results (measResultNeighCellNR). The neighboring cell measurement results may include either a list of NR measurement results or a list of E-UTRA measurement results. The NR measurement results and E-UTRA measurement results include some or all of the information on the physical cell identifier, the cell measurement result, and the cell global identifier. The serving measurement results (measResultServingMO) are the measurement results of the measurement target associated with the serving cell, and may include some or all of the serving cell identifier, the serving cell measurement result, and the measurement result of the best neighboring cell.

[0346] In the measurement report procedure, the measurement results described above are set for each measurement identifier that triggered the measurement report procedure. If the terminal device is configured as EN-DC, and SRB3 is configured, the procedure is terminated by submitting a measurement report message containing the measurement results to the lower layer via SRB3 for transmission. If SRB3 is not configured, the measurement report message is encapsulated (embedded) in the E-UTRA RRC message and submitted to the lower layer via the E-UTRA MCG. If the terminal device is configured as NR-DC and the measurement setting that triggered this measurement report is associated with SCG (Associated), and SRB3 is configured, the procedure is terminated by submitting a measurement report message containing the measurement results to the lower layer via SRB3 for transmission. If SRB3 is not configured, the measurement report message is encapsulated (embedded) in the NR MCG RRC message and submitted to the lower layer via the NR MCG.

[0347] Next, we will describe an example of SCG activation and deactivation.

[0348] In LTE and / or NR, the SCG deactivated state (SCG deactivated state) may be included as part of the RRC_CONNECTED state.

[0349] In LTE and / or NR, an inactive SCG state (SCG inactive state) is a state in which a terminal device performs some or all of the following (A) to (J) in its SCG SpCell (PSCell) and / or all cells of its SCG. (A) Do not send SRS in that cell. (B) Do not report a CSI for that cell, and / or do not report a CSI in that cell. (C) Do not send PUCCH, UL-SCH, and / or RACH from that cell. (D) Do not monitor the PDCCH of that cell, and / or the PDCCH for that cell. (E) Do not monitor the PDCCH for that cell, and / or the PDCCH for that cell, addressed to C-RNTI, MCS-C-RNTI, and / or CS-RNTI, which indicate the uplink grant for UL-SCH transmission in that cell. (F) Automatic Gain Control (AGC) is not performed in that cell. (G) No beam control (beam management), including beam failure recovery, is performed in that cell. (H) Do not perform Radio Link Monitoring (RLM) in that cell. (I) In that cell, the BWP that was set to dormant BWP is set to activated BWP (Active BWP). (J) Do not monitor C-RNTI with PDCCH in the activated BWP of that cell. (K) Put SRB3 into a suspended state.

[0350] Furthermore, when the SCG is inactive, different processing may be performed depending on whether the time-aligned timer is running or stopped (including expired). For example, while the SCG is inactive and the time-aligned timer is running, the SpCell of this SCG may report a CSI, and while the SCG is inactive and the time-aligned timer is stopped, the SpCell of this SCG may not report a CSI. Alternatively, for example, while the SCG is inactive and the time-aligned timer is running, the SpCell of this SCG may perform an RLM, and while the SCG is inactive and the time-aligned timer is stopped, the SpCell of this SCG may not perform an RLM. Terminal devices may refrain from performing processing that involves initiating a random access procedure when the SCG is inactive. The timer may also be another timer that starts, for example, when the SCG is inactive or when it is deactivated. The timer may be a timer managed by a MAC entity.

[0351] Furthermore, the state of becoming an inactive SCG may be referred to as "entering" an inactive SCG. The inactive SCG state may also be a state in which the Active BWP of an SCG SpCell is a specific BWP. Additionally, the aforementioned inactive SCG state may be a state transitioned from the activated SCG state (SCG active state), described later, when entry into an inactive SCG is instructed by an RRC entity.

[0352] In LTE and / or NR, the state in which the SCG is activated (SCG activated state) may be included as part of the RRC_CONNECTED state.

[0353] In LTE and / or NR, an activated SCG state (SCG activated state) is a state in which a terminal device performs some or all of the following (A) to (J) in its SCG's SpCell (PSCell) and / or any cell of its SCG. (A) Send an SRS in that cell. (B) Report the CSI for that cell. (C) Send PUCCH, UL-SCH, and / or RACH from that cell. (D) Monitor the PDCCH of that cell and / or the PDCCH for that cell. (E) Monitor the PDCCH for that cell and / or the PDCCH for that cell, addressed to C-RNTI, MCS-C-RNTI, and / or CS-RNTI, which indicate the uplink grant for UL-SCH transmission in that cell. (F) Automatic Gain Control (AGC) is performed in that cell. (G) In that cell, beam control (beam management), including beam failure recovery, is performed. (H) Perform Radio Link Monitoring (RLM) in that cell. (I) In that cell, do not set BWPs as dormant BWPs (Active BWPs). (J) Monitor C-RNTI in the activated BWP of that cell using PDCCH.

[0354] Furthermore, the process of becoming an SCG active state may also be referred to as "entering" an activated SCG. The SCG active state may also be a state in which the Active BWPs of the SCG's SpCells and / or one or more SCells are not dormant BWPs. Additionally, the aforementioned SCG inactive state may be a state to which the SCG transitions from an inactive state (SCG inactive state) when an RRC entity instructs it to leave the inactive SCG.

[0355] In LTE and / or NR, a terminal device may transition the SCG to an inactive state (in other words, deactivate the SCG) based on receiving some or all of (A) to (B) below. Note that the messages and control elements in (A) to (C) below may also be notified to the terminal device from cell groups other than the SCG in question. Furthermore, each piece of information may be notified to the terminal device via RRC messages, MAC control elements, or physical control channels. (A) Information indicating the inactivation of SCG (B) Information indicating the inactivation of SpCell (C) Information instructing SpCell to switch its Active BWP to a specific BWP.

[0356] Furthermore, the terminal device may transition the SCG from an active state to an inactive state based on a timer for SCG deactivation. Alternatively, the terminal device may transition the SCG from an active state to an inactive state based on a timer for PSCell deactivation.

[0357] Furthermore, the terminal device may transition the SCG from an inactive state to an active state when the MAC entity itself initiates a random access procedure (for example, resulting from a scheduling request). The MAC entity of the terminal device may also obtain instructions to activate the SCG, instructions to return from an inactive SCG, instructions to return from a dormant state of SpCell, and / or other information from the RRC entity of the terminal device.

[0358] In LTE and / or NR, a terminal device may transition the SCG from an inactive state to an active state (in other words, activate the SCG) based on receiving some or all of (A) through (D) below. Note that the messages and control elements in (A) through (D) below may also be notified to the terminal device from cell groups other than the SCG in question. Furthermore, each piece of information may be notified to the terminal device via RRC messages, MAC control elements, or physical control channels. (A) Information that instructs the activation of SCG (B) Information instructing the SCG to resume from its deactivated state. (C) Information instructing the activation of SpCell (D) Information instructing SpCell to recover from the inactive state.

[0359] Furthermore, the terminal device may transition the SCG from an inactive state to an active state based on a timer for SCG deactivation. Alternatively, the terminal device may transition the SCG from an inactive state to an active state based on a timer for PSCell deactivation.

[0360] Furthermore, the terminal device may transition the SCG from an inactive state to an active state when initiating a random access procedure resulting from a scheduling request triggered to transmit a MAC PDU containing a MAC SDU.

[0361] Furthermore, the terminal device may transition the SCG from an inactive state to an active state when initiating a random access procedure resulting from a scheduling request (in other words, initiated by the MAC entity itself). The MAC entity of the terminal device may also obtain instructions to activate the SCG, instructions to return from an inactive SCG, instructions to return from a dormant state of SpCell, and / or other information from the RRC entity of the terminal device.

[0362] SCG inactivation may also be referred to as entering a dormant SCG. Alternatively, SCG inactivation may refer to the activation of a dormant BWP in the SpCell of the cell group in question. Furthermore, SCG inactivation may also be referred to as SCG dormancy or SCG suspension.

[0363] When an SCG is inactive and at least the time-matching timer is stopped, all uplink transmissions in the SCG may be stopped. In this case, information about that SCG may be transmitted in other cell groups (e.g., MCG). Alternatively, information about that SCG may be transmitted in the SCG that has left the inactive state (an activated SCG).

[0364] A random access procedure in a SpCell (PSCell) may be initiated in an inactive SCG, either by a scheduling request from a MAC entity to send a MAC PDU containing a MAC CE, or directly by a MAC entity. In this case, the MAC PDU may not contain a MAC SDU.

[0365] On the other hand, a scheduling request to send a MAC PDU containing data from higher layers, such as user data and RRC messages (MAC SDU), may trigger the random access procedure in the SpCell (PSCell) in an inactive SCG.

[0366] The recovery of an SCG from an inactive state (activation of SCG) may also be referred to as leaving a dormant SCG. Furthermore, the recovery of an SCG from an inactive state may also refer to a BWP switch in the SpCell of the cell group in question, where a dormant BWP is replaced by another (non-dormant) BWP.

[0367] Furthermore, the recovery of SCG from an inactivated state may be referred to as SCG activation. Also, SCG activation may be referred to as SCG reactivation.

[0368] A terminal device that performs SCG deactivation may perform some or all of the following processes (A) to (Q) in the SCG. (A) Set all SCells to an inactive state. (B) Assume that all SCell deactivation timers associated with active SCells have expired. (C) All SCell inactivity timers associated with dormant SCells are considered to have expired. (D) Do not start or restart the SCell inactive timer associated with any SCell. (E) Ignore MAC CEs that activate SCell. For example, in the process (AD), if a MAC CE that activates SCell is received and SCG deactivation is not instructed (or SCG is not in an inactive state), then process (AD-1) is performed. (F) The above process (AD-2) is performed. For example, if the process (AD) is instructed to deactivate the SCG (or the SCG is in an inactivated state), the process (AD-2) is performed. (G) Switch the Active BWP of a specific SCell to a Dormant BWP (i.e., put this SCell into a dormant state). The specific SCell may be a SCell instructed by the base station equipment, or a SCell on which a Dormant BWP has been set. (H) Switch the Active BWP of the SpCell to a specific BWP. The specific BWP may be a BWP designated by the base station equipment, a BWP set as the First Active BWP, or the Initial BWP. The BWP to be switched to may be only the DL BWP, or both the DL BWP and the UL BWP. (I) Deactivate all BWPs in the SpCell. That is, perform the same process on the SpCell as when the SCell is deactivated, which deactivates all BWPs in that SCell. (J) Abort the running random access procedure. (K) Abort the running random access procedure and consider it to have completed successfully. (L) Suspend at least some SCG bearers (e.g., SRB3) configured on the terminal device. (M) Do not suspend at least some SCG bearers (e.g., DRB) configured on the terminal device. (N) If PDCP duplication is configured and activated, the system notifies higher layers (e.g., RLC layer, PDCP layer) to deactivate the PDCP duplication. (O) Reset the MAC. If any timers associated with (P)BSR (e.g., periodicBSR-Timer and / or retxBSR-Timer) are running, stop them. (Q) Re-establish RLC corresponding to SCG bearer.

[0369] A terminal device that performs the recovery of an SCG from an inactive state may perform some or all of the following processes (A) to (F) in the SCG. (A) Perform procedure (AD-1) to activate all SCells. (B) All SCells are left in an inactive state. However, since they are not in an inactive state, for example, if a MAC CE that activates SCells is received in the above process (AD), the SCG is not inactive (or the SCG is not in an inactive state), so the process (AD-1) may be performed. (C)When the SCG is restored from an inactive state based on an RRC message, if the RRC message contains parameters for random access to some or all of the SCells, the random access procedure is initiated on the target SCells based on the notified parameters. (D) When restoring the SCG from an inactive state based on an RRC message, if the RRC message contains information specifying the state of the SCell, the system will determine whether to activate or deactivate each SCell based on that information. (E) Switch the Active BWP of SpCell to a specific BWP. The specific BWP may be a BWP designated by the base station equipment, or it may be a BWP set as the First Active BWP. (F)Activates the BWP that is set as the First Active BWP of SpCell. (G) Resume at least some SCG bearers (e.g., SRB3) that are configured on the terminal device. (H) If PDCP duplication is configured and has been deactivated based on SCG deactivation, the activation of that PDCP duplication is notified to the higher layer (e.g., RLC layer, PDCP layer).

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

[0371] Figure 5 is a block diagram showing the configuration of a terminal device (UE122) in an embodiment of the present invention. Note that, to avoid complicating the explanation, Figure 5 shows only the main components closely related to one embodiment of the present invention.

[0372] The UE122 shown in Figure 5 consists of a receiving unit 500 that receives RRC messages etc. from a base station device, a processing unit 502 that processes according to the parameters contained in the received message, and a transmitting unit 504 that transmits RRC messages etc. to the base station device. The base station device mentioned above may be an eNB102 or a gNB108. Furthermore, the processing unit 502 may include some or all of the functions of various layers (for example, the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 502 may include some or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP layer processing unit, RRC layer processing unit, and NAS layer processing unit. The UE122 may also be equipped with a measuring unit (not shown) for performing measurements.

[0373] Figure 6 is a block diagram showing the configuration of a base station device in an embodiment of the present invention. To avoid a complicated explanation, Figure 6 shows only the main components closely related to one embodiment of the present invention. The base station device described above may be either an eNB102 or a gNB108.

[0374] The base station device shown in Figure 6 consists of a transmitting unit 600 that sends RRC messages, etc., to the UE 122, a processing unit 602 that creates an RRC message including parameters and sends it to the UE 122, causing the processing unit 502 of the UE 122 to perform processing, and a receiving unit 604 that receives RRC messages, etc., from the UE 122. Furthermore, the processing unit 602 may include some or all of the functions of various layers (for example, the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 602 may include some or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP layer processing unit, RRC layer processing unit, and NAS layer processing unit.

[0375] The following describes various examples of processing by the terminal device in embodiments of the present invention.

[0376] In the following description, "MAC entity" refers to the MAC entity of the cell group subject to activation / deactivation on the terminal device (UE122), unless otherwise specified. Furthermore, in the following description, "RRC entity" refers to the RRC entity of the terminal device (UE122), unless otherwise specified.

[0377] Figure 15 shows an example of processing by a terminal device in an embodiment of the present invention.

[0378] The RRC entity of the terminal device (UE122) receives a first notification from a lower-layer entity (e.g., MAC entity, PHY entity) (step S1500).

[0379] The RRC entity of the terminal device (UE122), upon receiving the first notification, generates an RRC message requesting the network to activate the cell group corresponding to the lower-layer entity that issued the first notification (for example, the secondary cell group if the first notification was received from the MAC entity of a secondary cell group) (step S1502). Note that if there is only one cell group to be deactivated in UE122, it is not necessary to specifically identify which secondary cell it is in the above process.

[0380] This allows RRC entities to request the network to activate cell groups at the appropriate time, such as when uplink data is generated in an inactive cell group.

[0381] In the process shown in Figure 15, the first notification may be notified by the MAC entity of UE122. For example, the MAC entity may notify the RRC entity of the first notification based on the fact that its cell group is deactivated and that uplink data has become available for any of the logical channels in its cell group. For example, the MAC entity may notify the RRC entity of the first notification based on the fact that its cell group is deactivated and that at least one scheduling request is pending in its MAC entity.

[0382] Furthermore, in the process shown in Figure 15, instead of generating an RRC message requesting activation of the cell group, the RRC entity may generate an RRC message that includes, for example, information indicating that upstream link data exists in an inactive cell group.

[0383] The RRC entity may generate the RRC message in the process shown in Figure 15 as an RRC message to the master node. Alternatively, the RRC entity may generate the RRC message in Figure 15 as an RRC message to a secondary node and include the generated RRC message in a container within the RRC message to the master node. The RRC entity may submit the generated RRC message to a lower layer for transmission. The RRC message submitted to the lower layer may be transmitted to the base station device by the transmission unit 504 of UE122. The base station device to which the message is transmitted may be the master node.

[0384] The receiving unit 604 of the base station device (eNB102 or gNB108) may receive the RRC message from UE122. The processing unit 602 of the base station device may determine whether or not to reactivate the deactivated cell group based on the received RRC message.

[0385] Figure 16 shows an example of processing by a terminal device in an embodiment of the present invention.

[0386] The RRC entity of the terminal device (UE122) receives a second notification from a lower-layer entity (e.g., a MAC entity) (step S1600).

[0387] Based on receiving the second notification, the RRC entity of the terminal device (UE122) deems that the cell group corresponding to the lower-layer entity that notified the second notification (for example, the secondary cell group if the second notification was received from the MAC entity of a secondary cell group) has been activated (step S1602).

[0388] This allows the terminal device to activate the cell group at the appropriate time, such as when uplink data is generated in an inactive cell group.

[0389] In the process shown in Figure 16, the first notification may be notified by the MAC entity of UE122. For example, the MAC entity may notify the RRC entity of a second notification in an inactivated cell group based on, for example, a PUCCH transmission resulting from a scheduling request or the initiation (or successful completion) of a random access procedure, and / or the initiation (or successful completion) of a random access procedure for beam failure recovery of a SpCell.

[0390] In the process shown in Figure 16, the RRC entity may, based on the assumption that the cell group has been activated, resume some bearers that were previously suspended (e.g., SRB3). Alternatively, the RRC entity may, based on the assumption that the cell group has been activated, autonomously enable some measurement settings that were previously disabled (e.g., some of the measurement targets and / or some of the reporting settings).

[0391] Figure 17 shows an example of processing by a terminal device in an embodiment of the present invention.

[0392] The MAC entity of the terminal device (UE122) recognizes that the cell group is being deactivated (step S1700).

[0393] The MAC entity of the terminal device (UE122) aborts the random access procedure running in the cell group based on the deactivation of that cell group. (Step S1702).

[0394] This prevents unnecessary initiation of procedures that report SCG failures in deactivated cell groups.

[0395] In the process shown in Figure 17, for example, the MAC entity of UE122 may recognize the deactivation of a cell group by notification from the RRC entity. For example, the MAC entity of UE122 may recognize the deactivation of a cell group by a MAC CE received from the base station equipment. For example, the MAC entity of UE122 may recognize the deactivation of a cell group based on the stopping or expiring of a specific timer. For example, the MAC entity of UE122 may recognize the deactivation of a cell group based on a combination of the above.

[0396] In the process shown in Figure 17, the MAC entity may, based on the deactivation of the cell group, abort any random access procedures running on that cell group and consider those procedures to have successfully completed. Alternatively, the MAC entity may, based on the deactivation of the cell group, abort any beam failure recovery procedures running on that cell group and consider those beam failure recovery procedures to have successfully completed.

[0397] Furthermore, in the process shown in Figure 17, based on the deactivation of the cell group, the MAC entity may perform some or all of the following processes (A) through (F). (A) Flush the Msg3 buffer. (B) Flushe the MSGA buffer. (C) If a scheduling request has been triggered, cancel it. (D) If the buffer status reporting procedure has been triggered, cancel it. (E) If the power head reporting procedure has been triggered, cancel it. (F) If the beam failure recovery procedure has been triggered, cancel it.

[0398] The terminal device (UE122) may control the activation / deactivation of secondary cell groups using a timer in the RRC entity and / or MAC entity.

[0399] For example, a timer may be provided for each cell group, or one may be provided for each terminal device. The value set for the timer may be notified from the base station device via an RRC message (e.g., an RRCReconfiguration message). Alternatively, the value set for the timer may be broadcast from the base station device. The value set for the timer may also be a default value specified in the specifications. Furthermore, the terminal device may have a default value specified in the specifications, and may use this default value if it is not set in the base station device.

[0400] For example, a terminal device may start or restart a timer based on the deactivation and activation of a secondary cell group. A terminal device authorized by the base station device to autonomously activate (in other words, triggered and / or initiated by the terminal device) a secondary cell group, and / or autonomously deactivate (in other words, triggered and / or initiated by the terminal device) a secondary cell group, may activate and / or deactivate the secondary cell group based on the fact that this timer is not running (the timer has expired).

[0401] For example, a terminal device may start or restart a timer based on the deactivation of a secondary cell group. A terminal device authorized by the base station device to autonomously (in other words, triggered and / or initiated by the terminal device) activate and / or deactivate a secondary cell group may activate and / or deactivate the secondary cell group based on the fact that this timer is not running (the timer has expired).

[0402] For example, a terminal device may start or restart a timer based on the activation of a secondary cell group. A terminal device authorized by the base station device to autonomously (in other words, triggered and / or initiated by the terminal device) activate and / or deactivate a secondary cell group may activate and / or deactivate the secondary cell group based on the fact that this timer is not running (the timer has expired).

[0403] This makes it possible to suppress frequent activation and deactivation transitions of cell groups.

[0404] For example, if the timer value is set to 0, the terminal device may determine that it is not permitted by the base station device to autonomously activate and / or deactivate the secondary cell group. For example, if the timer value is set to infinity, the terminal device may determine that it is not permitted by the base station device to autonomously activate and / or deactivate the secondary cell group. For example, if the timer value is not set by the base station device, the terminal device may determine that it is not permitted by the base station device to autonomously activate and / or deactivate the secondary cell group. The base station device may control whether the terminal device can autonomously activate and / or deactivate the cell group by setting a specific value for the timer and notifying the terminal device (or not notifying the timer value). Note that whether the terminal device can autonomously activate and / or deactivate the cell group may also be notified from the base station device to the terminal device using parameters other than the timer.

[0405] For example, based on the fact that the base station equipment does not permit autonomous activation and / or deactivation of secondary cell groups, the terminal equipment may suspend some or all of the SCG bearers (SRBs and / or DRBs where RLC bearers exist only in SCGs) when a secondary cell group is deactivated. For example, based on the fact that the base station equipment permits autonomous activation and / or deactivation of secondary cell groups, the terminal equipment may prevent some or all of the SCG bearers (SRBs and / or DRBs where RLC bearers exist only in SCGs) from suspending when a secondary cell group is deactivated.

[0406] Alternatively, for example, the terminal device may determine whether to abort the running random access procedure in the process shown in Figure 17 based on whether the base station device has authorized the autonomous activation and / or deactivation of the secondary cell group.

[0407] Alternatively, for example, the terminal device may determine whether to perform some or all of the following processes (A) to (F) in the process shown in Figure 17, based on whether or not the base station device has authorized the autonomous activation and / or deactivation of the secondary cell group. (A) Flush the Msg3 buffer. (B) Flushe the MSGA buffer. (C) If a scheduling request has been triggered, cancel it. (D) If the buffer status reporting procedure has been triggered, cancel it. (E) If the power head reporting procedure has been triggered, cancel it. (F) If the beam failure recovery procedure has been triggered, cancel it.

[0408] This allows the network (base station equipment) to efficiently control the autonomous activation and / or deactivation of cell groups by terminal devices.

[0409] Furthermore, the autonomous activation of secondary cell groups by the terminal device described above may be, for example, an activation of a secondary cell group initiated by the presence of uplink data in an inactive secondary cell group (e.g., triggering a scheduling request). Alternatively, the autonomous activation of secondary cell groups by the terminal device may be an activation of a secondary cell group initiated based on, for example, the battery level of the terminal device or the temperature of the terminal device. The autonomous activation of secondary cell groups may also be rephrased as secondary cell activation initiated by the terminal device (UE-initiated SCG Activation).

[0410] Furthermore, the aforementioned autonomous deactivation of secondary cell groups by the terminal device may, for example, be a deactivation of a secondary cell group initiated based on the absence of uplink data in an activated secondary cell group. Also, the aforementioned autonomous deactivation of secondary cell groups by the terminal device may, for example, be a deactivation of a secondary cell group initiated based on the terminal device's battery level or temperature. Furthermore, the autonomous activation of secondary cell groups may be rephrased as deactivation of secondary cells initiated by the terminal device (UE-initiated SCG Deactivation).

[0411] Furthermore, in the autonomous activation of a secondary cell group by the terminal device described above, the terminal device may, for example, initiate uplink transmission (e.g., transmission of PUCCH or random access preamble resulting from a scheduling request) in the secondary cell group based on the activation of the secondary cell group.

[0412] Furthermore, for example, a terminal device may activate a secondary cell group based on an uplink transmission in the deactivated secondary cell group (e.g., transmission of a PUCCH or random access preamble resulting from a scheduling request). For example, a terminal device may consider a secondary cell group to be activated and begin monitoring PDCCH based on the transmission of a random access preamble in a cell of the deactivated secondary cell group (e.g., a PSCell or PUCCH SCell) (or the transmission of a random access preamble being indicated to the PHY entity).

[0413] Furthermore, the terminal device may change the bearer settings to deactivate the secondary cell group. For example, if an SCG bearer is configured, the terminal device may change the bearer type of this SCG bearer to a split bearer in order to deactivate the secondary cell group. Alternatively, if an SCG bearer is configured, the terminal device may change the bearer type of this SCG bearer to a split bearer in order to deactivate the secondary cell group and configure the PDCP entity to submit PDCP PDUs to the MCG's RLC entity. In this case, the change in bearer settings may be made based on default rules, or the changed bearer settings may be notified in advance by the base station device via an RRC message. Note that if the secondary cell group is deactivated by the autonomous deactivation of the secondary cell group by the terminal device, the terminal device may change the bearer settings after notifying the base station device that the secondary cell group has been deactivated.

[0414] This allows for appropriate control of the wireless bearer settings configured on terminal devices based on the deactivation of cell groups.

[0415] For example, if PDCP duplication is configured and activated, the MAC entity may notify a higher layer (e.g., the PDCP layer) of the deactivation of the PDCP duplication based on the deactivation of the secondary cell group. In this case, if the primary path is configured to the secondary cell group to be deactivated, the terminal device may reconfigure the primary path to a different cell group. The cell group identifier of the reconfigured primary path may be, for example, an MCG identifier. The cell group identifier of the reconfigured primary path may be, for example, a cell group identifier pre-configured to the terminal device by an RRC message. The above process is preferred when the terminal device autonomously deactivates the secondary cell group (i.e., when the terminal device triggers and initiates the deactivation of the secondary cell group), but is not limited to this and can also be applied to deactivation instructed by the network. When a secondary cell group is deactivated by autonomous deactivation by the terminal device, the terminal device may perform the above process after notifying the base station device that the secondary cell group has been deactivated.

[0416] This allows for efficient control of cell group deactivation by the terminal device based on the wireless bearer settings configured on the terminal device.

[0417] Furthermore, for example, if a terminal device autonomously deactivates a secondary cell group (i.e., if the terminal device triggers and initiates the deactivation of a secondary cell group), the deactivation of the secondary cell group may not be triggered and / or initiated based on the satisfaction of some or all of the following conditions (A) to (C). Also, if the deactivation of a secondary cell is instructed by the network, the secondary cell group may be deactivated regardless of the following conditions. (A) PDCP duplication is configured and activated. (B) PDCP duplication is configured, deactivated, and the primary path is set to this secondary cell group. (C) An SCG bearer is configured for this secondary cell group.

[0418] This allows for efficient control of autonomous cell group deactivation by the terminal device based on the wireless bearer settings configured on the terminal device.

[0419] In the above description, unless otherwise specified, the wireless bearer may be a DRB, an SRB, or both a DRB and an SRB.

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

[0421] Furthermore, in the above explanation, "SCG's SpCell" may be replaced with "PSCell".

[0422] In the above explanation, "dormant state" and "inactive state" may be interchangeable, and "state after recovery from dormancy" and "active state" may be interchangeable. Also, in the above explanation, "activation, inactivation" and "active state, inactive state" may be interchangeable.

[0423] In the above explanation, "activated BWP" and "Active BWP" can be used interchangeably.

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

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

[0426] Furthermore, in the above explanation, if condition "A" and condition "B" cannot be satisfied simultaneously, condition "B" may be expressed as an "other" condition of condition "A".

[0427] The following describes various embodiments of the terminal device and method according to the present invention.

[0428] (1) A first embodiment of the present invention is a terminal device in which a master cell group and a secondary cell group are set from a network, comprising a receiving unit that receives an RRC message from the network including a value for a first timer, and a processing unit that processes based on the RRC message, wherein the processing unit determines that the activation and / or deactivation of the secondary cell group initiated by the terminal device is not permitted based on the fact that a specific value is set for the first timer, and based on the fact that the secondary cell group is to be activated and / or deactivated, it starts or restarts the first timer, and based on the fact that the first timer is running, it does not start the activation and / or deactivation of the secondary cell group initiated by the terminal device.

[0429] (2) A second embodiment of the present invention is a method applied to a terminal device on which a master cell group and a secondary cell group are configured from a network, comprising the steps of receiving an RRC message from the network including a value for a first timer, and processing based on the RRC message, wherein the activation and / or deactivation of the secondary cell group initiated by the terminal device is deemed not permitted based on the fact that a specific value is set for the first timer, the first timer is started or restarted based on the fact that a value other than the specific value is set for the second cell group and the activation and / or deactivation of the second cell group is to be performed, and the activation and / or deactivation of the second cell group initiated by the terminal device is not started based on the fact that the first timer is running.

[0430] (3) A third embodiment of the present invention is an integrated circuit implemented in a terminal device that sets a master cell group and a secondary cell group from a network, wherein the terminal device is given the function of receiving an RRC message from the network including a value of a first timer and the function of processing based on the RRC message, and the activation and / or deactivation of the secondary cell group initiated by the terminal device is deemed not permitted based on the fact that a specific value is set in the first timer, and the activation and / or deactivation of the secondary cell group is to be performed based on the fact that a value other than the specific value is set in the first timer, and the activation and / or deactivation of the secondary cell group is to be performed, and the activation and / or deactivation of the secondary cell group initiated by the terminal device is not to be performed based on the fact that the first timer is running.

[0431] (4) A fourth embodiment of the present invention is a base station device that communicates with a terminal device, comprising a processing unit that generates an RRC message including a value of a first timer, and a transmitting unit that transmits the RRC message to the terminal device, wherein the processing unit indicates to the terminal device that it does not permit the activation and / or deactivation of a secondary cell group initiated by the terminal device, based on setting a specific value for the first timer.

[0432] (5) A fifth embodiment of the present invention is a method applied to a base station device communicating with a terminal device, comprising the steps of generating an RRC message including a value for a first timer, and transmitting the RRC message to the terminal device, thereby indicating to the terminal device that it is not permitted to activate and / or deactivate a secondary cell group, which is initiated by the terminal device based on setting a specific value for the first timer.

[0433] (6) A sixth embodiment of the present invention is an integrated circuit implemented in a base station device that communicates with a terminal device, which causes the base station device to perform the function of generating an RRC message including a value of a first timer and the function of transmitting the RRC message to the terminal device, and which indicates to the terminal device that it does not permit the activation and / or deactivation of a secondary cell group initiated by the terminal device based on setting a specific value in the first timer.

[0434] A program that operates in a device according to one aspect of the present invention may be a program that controls a Central Processing Unit (CPU), etc., to make the computer function in order to realize the functions of the above-described embodiment according to one aspect of the present invention. The program or information handled by the program is temporarily loaded into volatile memory such as Random Access Memory (RAM) during processing, or stored in non-volatile memory such as flash memory or a Hard Disk Drive (HDD), and read, modified, and written by the CPU as needed.

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

[0436] Furthermore, "computer-readable recording media" may include those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or communication lines such as telephone lines, as well as those that hold programs for a certain period of time, such as volatile memory within the computer system acting as a server or client in such cases. In addition, the above-mentioned program may be for the purpose of realizing some of the functions described above, and may also be a program that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

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

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

[0439] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like that do not depart from the gist of this invention are also included. Furthermore, various modifications are possible within the scope of the claims for one aspect of the present invention, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. In addition, configurations in which elements described in the above embodiments that produce similar effects are substituted for each other are also included. [Industrial applicability]

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

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

Claims

1. A terminal device in which a master cell group and a secondary cell group are configured from the network, A receiving unit that receives an RRC message from the network containing the value of a first timer, The system comprises a processing unit that performs processing based on the RRC message, The aforementioned processing unit, Based on the fact that a specific value is set in the first timer, it is deemed that the activation and deactivation of the secondary cell group initiated by the terminal device is not permitted. Based on the fact that a value other than the specified value is set for the first timer, and that the secondary cell group is activated or deactivated, the first timer is started or restarted. Based on the fact that the first timer is running, the activation and deactivation of the secondary cell group, which are initiated by the terminal device, are not initiated. If it is detected that a secondary cell group is to be deactivated, the random access procedure currently running on the secondary cell group is terminated, and the random access procedure is deemed to have completed successfully. When the secondary cell group is deactivated, the active bandwidth portion of the PSCell of the secondary cell group is switched to the bandwidth portion specified in the RRC message. Terminal device.

2. A base station device that communicates with terminal devices, A processing unit that generates an RRC message including the value of the first timer, The system includes a transmitting unit that transmits the RRC message to the terminal device, The aforementioned processing unit, Based on setting a specific value in the first timer, the terminal device is not permitted to activate or deactivate the secondary cell group, which is initiated by the terminal device's judgment. Furthermore, the RRC message is set to include information regarding the bandwidth portion used in the PSCell of the secondary cell group when the secondary cell group is deactivated. Base station equipment.

3. A method applicable to a base station device that communicates with a terminal device, A step of generating an RRC message containing the value of the first timer, The step of transmitting the RRC message to the terminal device is included, Based on setting a specific value in the first timer, the terminal device is not permitted to activate or deactivate the secondary cell group, which is initiated by the terminal device's judgment. Furthermore, the RRC message is set to include information regarding the bandwidth portion used in the PSCell of the secondary cell group when the secondary cell group is deactivated. method.

Images