Terminal equipment, base station equipment, and method

Abstract

To provide a terminal device and a method applied to the terminal device that set an appropriate SCG state when performing RRC (Radio Resource Control) reconfiguration even if an RRC reconfiguration message is set, by determining whether the state of a secondary cell group (SCG) is to be activated, deactivated, or not changed, based on signaling notified from a base station device.SOLUTION: In a communication system, a terminal device determines whether information (first information) indicating whether to change the state of an SCG based on an scg-state is included in RRC signaling. If the first information is not included, the terminal device changes the state of the SCG based on whether the scg-state is included in the RRC signaling. If the first information is included, the terminal device does not change the state of the SCG based on whether the scg-state is included in the RRC signaling.SELECTED DRAWING: Figure 10

Description

Technical Field

[0001] The present invention relates to a terminal device, a base station device, and a method.

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 carried out.

[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 and 4th generations. Even now, in 3GPP, technical studies and standardization of extended technologies of E-UTRA are being carried out. 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) and LTE-Advanced Pro (LTE-A Pro).

[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 carried out.

Prior Art Documents

Non-Patent Documents

[0005]

Non-Patent Document 1

[0006] As an extension of NR technology, 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. In order for terminal devices to communicate with low latency when high-capacity data communication occurs, terminal devices need to constantly monitor multiple cell groups, which leads to the problem of consuming a lot of power. Therefore, consideration has been given to technologies that monitor some cell groups at a low frequency or stop them altogether (cell group deactivation technology).

[0007] Non-patent document 7 is a proposed revision of the specification for cell group activation. However, it does not reflect the consideration of conditional resetting when applying RRC reset messages, and in the future, terminal devices will not be able to perform efficient mobility in mobility based on conditional resetting that will be considered in NR Release 18 (also known as 5G Advanced) and beyond.

[0008] 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, and a communication method that can efficiently perform communication control. [Means for solving the problem]

[0009] 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 comprising a receiving unit for receiving RRC signaling and a processing unit, wherein the processing unit determines whether or not the RRC signaling includes information (first information) indicating whether or not to change the state of a secondary cell group based on information (scg-State) that instructs the setting of the state of a secondary cell group, and if the RRC signaling does not include the first information, the state of the secondary cell group is set to an inactive state based on the presence of scg-State in the RRC signaling, and the state of the secondary cell group is set to an active state based on the absence of scg-State in the RRC signaling, and if the RRC signaling does include the first information, the state of the secondary cell group is not changed based on whether or not the RRC signaling includes scg-State.

[0010] Another aspect of the present invention is a base station device that communicates with a terminal device, comprising a transmitting unit that transmits RRC signaling and a processing unit, wherein the RRC signaling does not include a first information but includes scg-State, and the base station device notifies the terminal device to set the state of the secondary cell group to an inactive state, and the RRC signaling does not include a first information but includes scg-State, and the base station device notifies the terminal device to set the state of the secondary cell group to an active state, and the RRC signaling includes a first information but notifies the terminal device not to change the state of the secondary cell group.

[0011] Furthermore, one aspect of the present invention is a method applied to a terminal device, comprising the steps of receiving RRC signaling and processing the RRC signaling, wherein it is determined whether the RRC signaling includes information (first information) indicating whether or not to change the state of a secondary cell group based on information (scg-State) that instructs the setting of the state of a secondary cell group, and if the RRC signaling does not include the first information, the state of the secondary cell group is set to an inactive state based on the presence of scg-State in the RRC signaling, and the state of the secondary cell group is set to an active state based on the absence of scg-State in the RRC signaling, and if the RRC signaling does include the first information, the state of the secondary cell group is not changed based on whether or not the RRC signaling includes scg-State.

[0012] Another aspect of the present invention is an integrated circuit mounted on a terminal device, which causes the terminal device to perform a function to receive RRC signaling and a function to process the RRC signaling, determines whether the RRC signaling includes information (first information) indicating whether or not to change the state of a secondary cell group based on information (scg-State) that instructs the setting of the state of the secondary cell group, if the RRC signaling does not include the first information, sets the state of the secondary cell group to an inactive state based on the presence of scg-State in the RRC signaling, sets the state of the secondary cell group to an active state based on the absence of scg-State in the RRC signaling, and if the RRC signaling includes the first information, does not change the state of the secondary cell group based on whether or not the RRC signaling includes scg-State.

[0013] 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.

Advantages of the Invention

[0014] According to one aspect of the present invention, a terminal device, a base station device, a method, and an integrated circuit can achieve efficient communication control processing.

Brief Description of the Drawings

[0015] [Figure 1] Schematic diagram of the communication system according to this embodiment. [Figure 2] Diagram of an example of the E-UTRA protocol configuration according to this embodiment. [Figure 3] Diagram of an example of the NR protocol configuration according to this embodiment. [Figure 4] Diagram showing an example of the flow of procedures for various settings in RRC according to this embodiment. [Figure 5] Block diagram showing the configuration of the terminal device in this embodiment. [Figure 6] Block diagram showing the configuration of the base station device in this embodiment. [Figure 7] Example of the ASN.1 description included in the message regarding the reconfiguration of the RRC connection in NR in this embodiment. [Figure 8] Example of the ASN.1 description included in the message regarding the reconfiguration of the RRC connection in E-UTRA in this embodiment. [Figure 9] Example of the process regarding the inactivation of the SCG in this embodiment. [Figure 10] Example of the process regarding the activation / inactivation of the SCG in this embodiment. [Figure 11] Example of the ASN.1 description of the RRC reconfiguration message in this embodiment. [Figure 12] Example of the ASN.1 description of the RRC reconfiguration message including the conditional reconfiguration information element in this embodiment. [Figure 13] Example of the ASN.1 description of the RRC reconfiguration message including the conditional reconfiguration information element in this embodiment. [Figure 14]An example of the process related to the activation / deactivation of SCG in this embodiment. [Figure 15] An example of the ASN.1 description for the RRC reset message in this embodiment. [Modes for carrying out the invention]

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

[0017] 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. Also, LTE using 5GC in the Core Network (CN) 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. This embodiment may be applied to NR, LTE, and other RATs. The following description uses terms related to LTE and NR, but this embodiment may be applied to other technologies using other terms. Also, the term E-UTRA in this embodiment may be replaced with the term LTE, and the term LTE may be replaced with the term E-UTRA.

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

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

[0020] 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.

[0021] The 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 the S1 interface. Interface 112 may have a control plane interface through which control signals pass, and / or a user plane interface through which user data passes. The control plane interface 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 the S1-MME interface. The user plane interface of interface 112 may be called the S1-U interface.

[0022] 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.

[0023] 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.

[0024] 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.

[0025] 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.

[0026] eNB102 may have the function of connecting to 5GC110. eNB102 having the function of connecting 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 AMF in 5GC110. The user plane interface of interface 114 may be terminated at the UPF in 5GC110. The control plane interface of interface 114 may be called NG-C interface. The user plane interface of interface 114 may be called NG-U interface. A radio access network consisting of ng-eNB or gNB may be called NG-RAN. NG-RAN, E-UTRAN, etc. may simply be called a network. Also, the network may include eNB, ng-eNB, and gNB, etc.

[0027] 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.

[0028] 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.

[0029] 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.

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

[0031] 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 Data Radio Bearer (DRB) established between UE122 and eNB102 and / or gNB108, as described below, 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.

[0032] 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, or ID). Each QoS flow may also be identified by a QoS flow identifier (Identity, or ID). Furthermore, the same QoS may be guaranteed for data such as IP packets and Ethernet frames passing through the same QoS flow.

[0033] 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 EPS bearer information, but not information within PDU sessions and / or QoS flows. Similarly, when UE122 is connected to 5GC110, UE122 will have information within PDU sessions and / or QoS flows, but not information within EPS bearers.

[0034] 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.

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

[0036] 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.

[0037] Figure 3(A) is a diagram of the NR user plane (UP) protocol stack. As shown in Figure 3(A), the NR UP 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.

[0038] 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.

[0039] 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.

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

[0041] In this embodiment, 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.

[0042] Furthermore, in this embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, PHY200, MAC202, RLC204, PDCP206, and RRC208 may also 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. Additionally, PHY200, MAC202, RLC204, PDCP206, and RRC208 may also 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.

[0043] 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.

[0044] 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.

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

[0046] 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.

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

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

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

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

[0051] 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 also 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. Terminal equipment may also use a CORESET (Control Resource Set) to monitor a set of PDCCH candidates. 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.

[0052] 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 Scheduling Requests (SR), which are used to request UL-SCH (Uplink Shared Channel) resources. Furthermore, Uplink Control Information may include HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement).

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

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

[0055] 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 requests for UL-SCH resources.

[0056] An example of MAC functionality is described below. MAC may be called a MAC sublayer. MAC may have the function of mapping various logical channels to corresponding transport channels. Logical channels may be identified by a Logical Channel Identity (Logical Channel ID). MAC may be connected to the higher-level RLC via logical channels. Logical channels may be divided into control channels that transmit control information and traffic channels that transmit user information, depending on the type of information being transmitted. Logical channels may also be divided into uplink logical channels and downlink logical channels. MAC may have the function of multiplexing MAC SDUs belonging to one or more different logical channels and providing them to the PHY. MAC may also have the function of demultiplexing MAC PDUs provided from the PHY and providing them to the higher layer via the logical channel to which each MAC SDU belongs. MAC may also have the function of performing error correction through HARQ (Hybrid Automatic Repeat reQuest). The MAC may also have a scheduling report (SR) function that reports scheduling information. The MAC may have a function to prioritize between terminal devices using dynamic scheduling. The MAC may also have a function to prioritize between logical channels within a single terminal device. The MAC may have a function to prioritize overlapping resources within a single terminal device. The E-UTRA MAC may have a function to identify Multimedia Broadcast Multicast Services (MBMS). The NR MAC may have a function to identify Multicast Broadcast Service (MBS). The MAC may have a function to select the transport format.A MAC may have functions for discontinuous reception (DRX) and / or discontinuous transmission (DTX), random access (RA) procedures, a power headroom report (PHR) function to notify information on available power, and a buffer status report (BSR) function to notify information on the amount of data in the transmit buffer. An NR MAC may have a bandwidth adaptation (BA) function. The MAC PDU format used in E-UTRA MACs and the MAC PDU format used in NR MACs may be different. A MAC PDU may also include MAC control elements (MAC CEs), which are elements for controlling the MAC.

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

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

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

[0060] 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.

[0061] 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.

[0062] 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.

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

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

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

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

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

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

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

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

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

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

[0073] An example of RLC functionality is described below. RLC may be called an RLC sublayer. E-UTRA RLC may have the function of segmenting and / or concatenating data provided from the upper layer PDCP and providing it to the lower layer. E-UTRA RLC may have the function of reassembling and reordering data provided from the lower layer and providing it to the upper layer. NR RLC may have the function of adding a sequence number to data provided from the upper layer PDCP that is independent of the sequence number added by the PDCP. NR RLC may also have the function of segmenting data provided from the PDCP and providing it to the lower layer. NR RLC may also have the function of reassembling data provided from 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. RLC may also have a function to perform error correction using ARQ. The control information sent from the receiver to the transmitter of RLC to perform ARQ, indicating data that needs to be retransmitted, may be called a status report. The instruction to send a status report sent from the transmitter to the receiver of 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. RLC may have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). In TM, data received from the upper layer is not split, and an RLC header does not need to be added. A TM RLC entity is a unidirectional entity and may be set as a transmitting TM RLC entity or a receiving TM RLC entity.UM performs data splitting and / or merging, adds RLC headers, etc., received from higher layers, 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 a transmitting UM RLC entity or a 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. AM performs data splitting and / or merging, adds RLC headers, and controls data retransmission, etc., received from higher layers. AM RLC entities are bidirectional entities and may be configured as AM RLC consisting of a transmitting side and a receiving side. Data provided to lower layers by TM, and / or data provided by lower layers, may be called TMD PDUs. Similarly, data provided to lower layers by UM, and / or data provided by lower layers, may be called UMD PDUs. Furthermore, data provided to lower layers by AM, or data provided by lower layers, may be called AMD PDUs. The RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC may be different. Also, there may be data RLC PDUs and control RLC PDUs. Data RLC PDUs may be called RLC DATA PDUs (RLC Data PDUs). Control RLC PDUs may be called RLC CONTROL PDUs (RLC Control PDUs).

[0074] This section describes some examples of PDCP functionality. PDCP may be referred to as the PDCP sublayer. 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 compressing and decompressing IP packet headers may be called the ROHC (Robust Header Compression) protocol. The protocol used for compressing and decompressing Ethernet frame headers may be called the EHC (Ethernet® Header Compression) protocol. PDCP may also have data encryption / decryption functions. PDCP may also have data integrity protection / verification functions. PDCP may also have a re-ordering function. 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 multiplexing function. Furthermore, PDCP may have a function to discard duplicate received data. A PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. The PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. In addition, there may be data PDCP PDUs and control PDCP PDUs. A data PDCP PDU may be called a PDCP DATA PDU (PDCP Data PDU). A control PDCP PDU may be called a PDCP CONTROL PDU (PDCP Control PDU).

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

[0076] An example of RRC functionality is described below. RRC may have broadcast functionality. RRC may have paging functionality from EPC104 and / or 5GC110. RRC may have paging functionality from eNB102 connected to gNB108 or 5GC110. RRC may also have RRC connection management functionality. RRC may also have wireless bearer control functionality. RRC may also have cell group control functionality. RRC may also have mobility control functionality. RRC may also have terminal device measurement reporting and terminal device measurement reporting control functionality. RRC may also have QoS management functionality. RRC may also have wireless link failure detection and recovery functionality. 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.

[0077] RRC messages may be sent using the logical channels BCCH, PCCH, CCCH, or DCCH. RRC messages sent using DCCH may also be referred to as dedicated RRC signaling or simply RRC signaling.

[0078] 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.

[0079] 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.

[0080] 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.

[0081] RRC signaling sent in the uplink (UL) direction using DCCH may include, for example, a Measurement Report message, an RRC Connection Reconfiguration Complete message, an RRC Connection Setup Complete message, an RRC Connection Reestablishment Complete message, a Security Mode Complete message, and an UE Capability Information message. It may also include, for example, a Measurement Report message, an RRC Reconfiguration Complete message, an RRC Setup Complete message, an RRC Reestablishment Complete message, an RRC Resume Complete message, a Security Mode Complete message, and an UE Capability Information message. Other RRC signaling may also be included.

[0082] RRC signaling 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. It may also include, for example, RRC Reconfiguration messages, RRC Resume messages, RRC Release messages, RRC Reestablishment messages, Security Mode Command messages, and UE Capability Enquiry messages. Other RRC signaling may also be included.

[0083] 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.

[0084] 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.

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

[0086] 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.

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

[0088] The RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state may be referred to as connected mode, inactive mode, and idle mode, respectively, or as RRC connected mode, RRC inactive mode, and RRC idle mode.

[0089] 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.

[0090] 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.

[0091] Next, we will explain the Serving Cell. In terminal devices in an RRC connection state where the CA and / or DC described later are not set, the Serving Cell may consist of one Primary Cell (PCell). In terminal devices in an RRC connection state where the CA and / or DC described later are set, multiple Serving Cells may mean a set of multiple cells consisting of one or more Special Cells (SpCells) and one or more all Secondary Cells (SCells). SpCells may support PUCCH transmission and contention-based Random Access (CBRA). 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 connection state. A PCell may also be a cell used in the RRC connection re-establishment procedure when a terminal device re-establishes the RRC connection. A PCell may also be a cell used in the random access procedure during handover. A PSCell may be a cell used in the random access procedure when adding a secondary node, as described later. Both PCell and PSCell may be SpCells. Furthermore, a SpCell may be a cell used for purposes other than those described above.

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

[0093] A group of serving cells configured by RRC that use 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). A TAG containing a MAC entity SpCell may represent a Primary Timing Advance Group (PTAG). A TAG other than a PTAG may represent a Secondary Timing Advance Group (STAG). One or more of the aforementioned TAGs may be configured for each cell group, as described later.

[0094] This section describes a cell group, which is configured on a terminal device by a base station device. A cell group may consist of one SpCell. Alternatively, a cell group may consist of one SpCell and one or more SCells. In other words, a cell group may consist of one SpCell and, optionally, one or more SCells. A cell group may also be described as a set of cell(s).

[0095] Dual Connectivity (DC) is a technology that enables data communication using the radio resources of cell groups configured by a first base station device (first node) and a second base station device (second node). When DC or MR-DC (described later) is performed, cell groups may be added to terminal devices from the base station device. To perform DC, the first base station device may add a second base station device. The first base station device may be called the Master Node (MN). The cell group configured by 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 configured by the Secondary Node may be called the Secondary Cell Group (SCG). The Master Node and Secondary Node may be configured within the same base station device.

[0096] 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.

[0097] Furthermore, Multi-Radio Dual Connectivity (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. MR-DC may be a technology included in DC. Examples of MR-DC using E-UTRA for MCG and NR for SCG include EN-DC (E-UTRA-NR Dual Connectivity) using EPC for the core network, and NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity) using 5GC for the core network. Also, an example of MR-DC using NR for MCG and E-UTRA for SCG is NE-DC (NR-E-UTRA Dual Connectivity) using 5GC for the core network. Also, an example of MR-DC using NR for MCG and E-UTRA for SCG is NR-DC (NR-NR Dual Connectivity) using 5GC for the core network.

[0098] In a terminal device, there may be one MAC entity for each cell group. For example, when 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. The MAC entity for the MCG in a terminal device may always be established in all states of the terminal device (RRC idle state, RRC connected state, and RRC inactive state, etc.). The MAC entity for the SCG in a terminal device may be created by the terminal device when an SCG is configured in the terminal device. The MAC entities for each cell group in a terminal device may be established when the terminal device receives RRC signaling from the base station device. When a MAC entity is associated with an MCG, SpCell may mean PCell. When a MAC entity is associated with an SCG, SpCell may mean Primary SCG Cell (PSCell). When a MAC entity is not associated with a cell group, SpCell may mean PCell. PCell, PSCell, and SCell are serving cells. In EN-DC and NGEN-DC, the MAC entity for MCG may be an E-UTRA MAC entity, and the MAC entity for SCG may be an NR MAC entity. Similarly, 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. Furthermore, in NR-DC, both the MAC entities for 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."

[0099] This section describes radio bearers. When a terminal device communicates with a base station device, a radio connection may be established between the terminal device and the base station device by establishing a radio bearer (RB). A radio bearer used in CP may be called a signaling radio bearer (SRB). A radio bearer used in UP may be called a data radio bearer (DRB). Each radio bearer may be assigned a radio bearer identifier (Identity: ID). The radio bearer identifier for SRBs may be called an SRB identifier (SRB Identity, or SRB ID). The radio bearer identifier for DRBs may be called a DRB identifier (DRB Identity, or DRB ID). For E-UTRA, SRB0 to SRB2 may be defined, and other SRBs may also be defined. For NR, SRB0 to SRB3 may be defined, and other SRBs may also be defined. SRB0 may be an SRB for RRC messages, transmitted and / or received using the logical channel CCCH. SRB1 may be an SRB for RRC signaling and for NAS signaling before SRB2 is established. RRC signaling transmitted and / or received using SRB1 may include piggybacked NAS signaling. All RRC and NAS signaling transmitted and / or received using SRB1 may use the logical channel DCCH. SRB2 may be an SRB for NAS signaling and for RRC signaling including logged measurement information. All RRC and NAS signaling transmitted and / or received using SRB2 may use the logical channel DCCH. SRB2 may also have a lower priority than SRB1. SRB3 may be an SRB for transmitting and / or receiving specific RRC signaling when EN-DC, NGEN-DC, NR-DC, etc., are configured on the terminal device.All RRC signaling and NAS signaling transmitted and / or received using SRB3 may use the logical channel DCCH. Other SRBs may be provided for other purposes. The DRB may be a wireless bearer for user data. RRC signaling transmitted and / or received using the DRB may use the logical channel DTCH.

[0100] This section describes the wireless bearer in the 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 the RLC bearer, the RLC entities may be a TM RLC entity and / or a transmit RLC entity and a receive RLC entity in unidirectional UM mode. SRB0 may consist of one RLC bearer. The RLC bearer of SRB0 may consist of the RLC entity of TM and a logical channel. SRB0 may always be established in the terminal device in all states (RRC idle state, RRC connected state, and RRC inactive state, etc.). SRB1 may be established and / or set in the terminal device by RRC signaling received from the base station device when the terminal device transitions from the RRC idle state to the RRC connected state. SRB1 may consist of one PDCP entity and one or more RLC bearers. The RLC bearer of SRB1 may consist of an AM RLC entity and a logical channel. SRB2 may be established and / or configured on a terminal device by RRC signaling 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 bearer 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. SRB3 may be established and / or configured on a terminal device by RRC signaling received from the base station device by a terminal device in an RRC connection state with AS security activated when a secondary node is added or when a secondary node is changed in an EN-DC, NGEN-DC, or NR-DC. 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 bearer of SRB3 may consist of AM RLC entities and logical channels. The PDCP on the base station equipment side of SRB3 may be located on a secondary node.One or more DRBs may be established and / or configured on a terminal device by RRC signaling 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.

[0101] 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.

[0102] 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.

[0103] For RLC bearers established and / or configured in a cell group 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 a cell group composed of NR, the established and / or configured RLC entities may be NR RLC. When EN-DC is configured on a terminal device, the PDCP entities established and / or configured for MN-terminated MCG bearers may be either E-UTRA PDCP or NR PDCP. Also, when EN-DC is configured on a terminal device, the PDCPs 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 NR PDCP. Furthermore, when NGEN-DC, NE-DC, or NR-DC is configured on a terminal device, the PDCP entities established and / or configured for wireless bearers of all bearer types may be NR PDCP.

[0104] 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 signaling received by the terminal device from the base station device.

[0105] Regardless of whether MR-DC is configured or not, a network configuration where the master node is eNB102 and the core network is EPC104 may be called E-UTRA / EPC. Similarly, a network configuration where the master node is eNB102 and the core network is 5GC110 may be called E-UTRA / 5GC. Furthermore, a network configuration where the master node is gNB108 and the core network is 5GC110 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.

[0106] Next, we will explain handover in LTE and NR. Handover may be the process by which UE122 in an RRC connection state changes the serving cell from source SpCell to target SpCell. Handover may occur when UE122 receives RRC signaling instructing handover from eNB102 and / or gNB108. RRC signaling instructing handover may be a message regarding the reconfiguration of the RRC connection that includes parameters instructing handover (for example, an information element named MobilityControlInfo or an information element named ReconfigurationWithSync). The information element named MobilityControlInfo may be referred to as a mobility control setting information element, mobility control setting, or mobility control information. The information element named ReconfigurationWithSync may be referred to as a synchronized reconfiguration information element, or synchronized reconfiguration. Furthermore, the RRC signaling that instructs a handover may be a message indicating the movement of another RAT to a cell (e.g., MobilityFromEUTRACommand or MobilityFromNRCommand). The term handover may also be rephrased as reconfiguration with sync. 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.

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

[0108] In Figure 4, the base station device creates an RRC message (step S400). The creation of an RRC message by the base station device may be performed to distribute system information (SI) or paging messages. The creation of an RRC message by the base station device may also be performed to send an RRC signaling to a specific terminal device to perform an action. The actions to be performed by 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. RRC connection reconfiguration processes may include, for example, control of radio bearers (establish, change, release, etc.), control of cell groups (establish, add, change, release, etc.), measurement settings, handover, security key update, etc. The creation of an RRC message by the base station device may also be performed in response to an RRC signaling sent from a terminal device. Responses to RRC signaling transmitted from terminal devices may include, for example, responses to RRC setup requests, RRC reconnection requests, and RRC restart requests. RRC messages contain various informational 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.

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

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

[0111] In MR-DC, the RRC signaling for SCG-side settings (cell group settings, wireless bearer settings, measurement settings, etc.) may be transmitted between the master node and the terminal device using the master node's RRC. For example, in EN-DC or NGEN-DC, the RRC signaling for NR may be included in the information element for SCG-side settings (nr-SecondaryCellGroupConfig) of the E-UTRA RRC signaling transmitted and received between eNB102 and UE122 in the form of a container. Similarly, in NE-DC, the RRC signaling for NR may be included in the information element for SCG-side settings (MRDC-SecondaryCellGroupConfig) of the NR RRC signaling transmitted and received between gNB108 and UE122 in the form of a container. The RRC signaling for SCG-side settings may be transmitted and received between the master node and the secondary node. Furthermore, in NR-DC, the NR RRC signaling transmitted and received between gNB108 and UE122 may be included in the information element for SCG-side configuration (MRDC-SecondaryCellGroupConfig) as a container. The RRC signaling for SCG-side configuration may be transmitted and received between the master node and the secondary node.

[0112] Furthermore, not only when using MR-DC, the RRC signaling for E-UTRA transmitted from eNB102 to UE122 may include RRC signaling for NR, and the RRC signaling for NR transmitted from gNB108 to UE122 may include RRC signaling for E-UTRA.

[0113] This section describes an example of parameters included in a message regarding the resetting of an RRC connection. Figure 7 is an example of an ASN.1 description representing a cell group setting field and / or information element included in a message regarding the resetting of an RRC connection in NR, as shown in Figure 4. Figure 8 is also an example of an ASN.1 description representing a cell group setting field and / or information element included in a message regarding the resetting of an RRC connection in E-UTRA, as shown in Figure 4. In the examples of ASN.1 in this embodiment, not limited to Figures 7 and 8, <omitted> and <omitted> indicate that other information has been omitted, not part of the ASN.1 notation. Information elements may also be omitted where there is no <omitted> or <omitted> notation. Note that the examples of ASN.1 in this embodiment do not strictly follow the ASN.1 notation method. The examples of ASN.1 in this embodiment represent an example of the parameters for RRC signaling in this embodiment, and other names or notations may be used. Furthermore, to avoid making the explanation complicated, only examples of the main information closely related to this embodiment are shown. In addition, parameters described in ASN.1 are sometimes referred to as "information elements" without distinguishing between fields, information elements, etc. Also, in this embodiment, fields, information elements, etc. described in ASN.1 included in RRC signaling may be referred to as "information" or as "parameters." The message regarding the resetting of the RRC connection may be an RRC reset message in NR or an RRC connection reset message in E-UTRA.

[0114] In Figure 7, the information element named CellGroupConfig may be an information element used for setting, changing, releasing, etc., cell groups of MCG or SCG in NR. The information element named CellGroupConfig may include the TCI information element described later. The information element named CellGroupConfig may be referred to as the cell group setting information element or cell group setting. Also, when the information element named CellGroupConfig is used for setting cell groups of SCG in NR, this information element named CellGroupConfig may be referred to as the SCG setting. The information element named SpCellConfig, which is included in the information element named CellGroupConfig, may be an information element used for setting special cells (SpCell). The information element named SpCellConfig may be referred to as the SpCell setting information element or SpCell setting. The information element named DeactivatedSCG-Config-r17, which is included in the information element named SpCellConfig, may be an information element that is set in the SCG deactivation described later. The information element named "DeactivatedSCG-Config-r17" can be rephrased as the setting for deactivating the SCG.

[0115] This section describes cell activation and deactivation. In terminal devices communicating via Dual Connectivity, the settings of the master cell group (MCG) and secondary cell group (SCG) are notified from the base station device via the message regarding the reconfiguration of the RRC connection mentioned above. Each cell group may consist of an SpCell and zero or more SCells. The SpCell of the MCG is also called a PCell. The SpCell of the SCG is also called a PSCell.

[0116] Cell deactivation may not apply to PCell but may apply to PSCell. In this case, cell deactivation may be performed differently for SpCell and SCell.

[0117] 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 some or all of (A) to (C) below. (A) Receiving MAC CE to activate / deactivate SCell (B) The SCell inactivity timer set for each SCell expires (the SCell may be limited to SCells for which PUCCH is not set). (C) RRC parameter (sCellState) set for each SCell configured on the terminal device.

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

[0119] Processing (AD) (1) If the RRC parameter (sCellState) set for SCell during SCell configuration is set to activated, or if a MAC CE to activate SCell is received, the MAC entity of the terminal device executes some or all of the processes (1) to (3) of process (AD-1). Otherwise, if a MAC CE to deactivate SCell is received, or if the SCell deactivation timer expires for an activated SCell, the MAC entity of the terminal device executes process (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 the terminal device performs the process (AD-3).

[0120] Processing (AD-1) (1) If, in NR, this SCell was inactive before receiving a MAC CE to activate it, or if the RRC parameter (sCellState) set for the SCell during SCell setup is set to activated, the MAC entity of the terminal device performs some or all of the processes (1) through (3) of process (AD-1-1). (2) The MAC entity of the terminal device starts the SCell deactivation timer associated with its SCell, or restarts it (if the SCell deactivation timer 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 the terminal device (re)initializes it. The MAC entity of the terminal device then triggers the PHR.

[0121] Processing (AD-1-1) (1) If the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) set in the RRC message for that SCell is not set as a dormant BWP, the MAC entity of the terminal device 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 the terminal device stops the BWP Inactivity Timer (bwp-InactivityTimer) for this serving cell, if it is running. (3) The MAC entity of the terminal device 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.

[0122] Processing (AD-1-1-1) The MAC entity of the terminal device activates SCell at a predetermined time and applies normal SCell operations, including some or all of the following (A) through (E). (A) This SCell transmits a sounding reference signal (SRS). (B) Report the CSI for this SCell. (C) Monitor the PDCCH of this SCell. (D) Monitor PDCCH for this SCell. (If scheduling is performed for this SCell in other serving cells) (E) If PUCCH is set, send PUCCH with this SCell.

[0123] Processing (AD-2) The MAC entity of the terminal device performs some or all of the following (A) through (F). (A) Inactivate this SCell. (B) Stop the SCell deactivation timer associated with this SCell. (C) Deactivate all Active BWPs associated with this SCell. (D) Clear all configured downlink assignments and / or all configured uplink grants of grant type 2 associated with this SCell. (E) Suspend all Grant Type 1 configured uplink grants associated with this SCell. (F) Flushes the HARQ buffer associated with this SCell.

[0124] Processing (AD-3) The MAC entity of the terminal device performs 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.

[0125] As described above, the MAC entity performs processing (AD) which activates and deactivates SCells.

[0126] Furthermore, as mentioned above, when an SCell is added, the initial state of the SCell may be set by RRC signaling.

[0127] 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 RRC signaling. For example, if information indicating 40ms as the value of the SCell deactivation timer is notified by RRC signaling, in the above process (AD), the timer will be considered to have expired when the notified time (40ms in this case) has elapsed without the timer stopping after the timer has been started or restarted. The SCell deactivation timer may also be named a timer called sCellDeactivationTimer.

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

[0129] 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 system 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). Furthermore, downlink BWPs (DL BWPs) and uplink BWPs (UL BWPs) may be configured separately. One or more uplink BWPs may also be associated with one or more downlink BWPs. Furthermore, the mapping between the uplink BWP and the downlink BWP may be a default mapping, a mapping by RRC signaling (e.g., Dedicated RRC signaling), a mapping by physical layer signaling (e.g., downlink control information (DCI) notified via the downlink control channel), or a combination of these. Additionally, a CORESET may be set in the downlink BWP.

[0130] 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. The BWP parameters for each component carrier may include some or all of the following: (A) the type of cyclic prefix, (B) the subcarrier spacing, (C) the frequency position of the BWP (e.g., the starting position or center frequency position on the lower frequency side of the BWP) (the frequency position may be, for example, an ARFCN or an offset from a specific subcarrier of the serving cell. The unit of the offset may be 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 configuration information for the control signals, 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. The unit of the offset may be in subcarrier units or resource block units. Both ARFCN and offset may be set). Additionally, resource configuration information for the control signals may be included in the BWP settings for at least some or all of the PCell and / or PSCell.

[0131] A terminal device may perform transmission and reception using one or more configured BWPs, specifically the Active BWP. One or more BWPs may be configured in a single serving cell associated with a terminal device. Of the one or more BWPs configured for a single serving cell associated with a terminal device, at any given time, up to one uplink BWP and / or up to one downlink BWP may be configured to be the Active BWP. The downlink Active BWP is also referred to as the Active DL BWP. The uplink Active BWP is also referred to as the Active UL BWP. In addition, one or more BWPs configured in a terminal device that are not the Active BWP may be referred to as the Inactive BWP.

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

[0133] 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.

[0134] Next, we will explain the BWP Inactivity Timer. For each activated serving cell on which the BWP Inactivity Timer is set, the MAC entity performs some or all of the following processes (1) to (2) of the DB.

[0135] Processing (DB) (1) If a default downlink BWP identifier (defaultDownlinkBWP-Id) is set and the Active DL BWP is not the BWP indicated by defaultDownlinkBWP-Id and the Active DL BWP is not the BWP indicated by the dormant BWP identifier (dormantBWP-Id), or if the defaultDownlinkBWP-Id for the default downlink BWP is not set and the Active DL BWP is not the initial downlink BWP and the Active DL BWP is not the BWP indicated by dormantBWP-Id, then the MAC entity of the terminal device performs (1) and (2) of the following process (DB-A). (2) If the MAC entity of the terminal device receives a PDCCH for BWP switching and switches the Active DL BWP, it performs the following process (DB-B).

[0136] Processing (DB-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 of the terminal device performs the following action (DB-A-1): (2) If the BWP inactivity timer associated with the Active DL BWP expires, the MAC entity of the terminal device performs the following action (DB-A-2).

[0137] Processing (DB-A-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 (if the BWP inactivity timer is already running) the BWP inactivity timer associated with the Active DL BWP.

[0138] Processing (DB-A-2) If a defaultDownlinkBWP-Id is set, the BWP will be switched to the BWP indicated by this defaultDownlinkBWP-Id; otherwise, the BWP will be switched to initialDownlinkBWP.

[0139] Processing (DB-B) If defaultDownlinkBWP-Id is set, and the switched Active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id, then the BWP inactivity timer associated with the Active DL BWP is started or restarted (if the BWP inactivity timer has already started).

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

[0141] If BWP is deactivated, the MAC entity of the terminal device shall perform some or all of the following (A) through (I): (A) Do not send UL-SCH with that BWP. (B) Do not send RACH with that BWP. (C) Do not monitor PDCCH with that BWP. (D) Do not send a PUCCH with that BWP. (E) Do not report CSI in that BWP. (F) Do not send SRS with that BWP. (G) Do not receive DL-SCH with that BWP. (H) Clear all configured downlink assignments and / or all configured uplink grants of grant type 2 that are set in that BWP. (I) Suspend all Grant Type 1 configured uplink grants of that Inactive BWP.

[0142] Next, we will explain the deactivation and activation of SCG.

[0143] Deactivation of SCG may mean inactivating SCG. Deactivation of SCG may also mean that MAC entities are associated with SCG and the cell group corresponding to said MAC entities is inactivated. Deactivation of SCG may also mean deactivating PSCell (SpCell of SCG), or inactivating PSCell. Activation of SCG may mean activating SCG. Activation of SCG may also mean that MAC entities are associated with SCG and the cell group corresponding to said MAC entities is activated. Activation of SCG may also mean activating PSCell (SpCell of SCG), or activating PSCell.

[0144] In LTE and / or NR, the inactive state of the SCG may mean a state in which the terminal device performs some or all of the following processes (A) to (P) of (SD-1) in its SCG's PSCell (SpCell). Alternatively, the inactive state of the SCG may mean a state in which the SCG is deactivated.

[0145] Processing (SD-1) (A) Do not send SRS with this PSCell. (B) Measure the CSI for this PSCell. (C) Do not report CSI for this PSCell. (D) Do not send PUCCH with this PSCell. (E) Do not send UL-SCH with this PSCell. (F) Do not send RACH with this PSCell. (G) Do not monitor the PDCCH of this PSCell. (H) Do not monitor PDCCH for this PSCell. (I) Inactivate the Active BWP in this PSCell. (J) This PSCell will perform intermittent reception (DRX). (K) Do not monitor the PDCCH of this PSCell and / or the PDCCH for this PSCell, addressed to C-RNTI, MCS-C-RNTI, and / or CS-RNTI, which indicate the uplink grant for UL-SCH transmission on this PSCell. (L) The BWP is activated on this PSCell, and the PDCCH of this PSCell, and / or the PDCCH for this PSCell, addressed to C-RNTI, MCS-C-RNTI, and / or CS-RNTI, which indicate the uplink grant in the aforementioned BWP, are not monitored. (M) This PSCell performs Automatic Gain Control (AGC), Beam Failure Detection (BFD) including beam failure recovery, and / or Radio Link Monitoring (RLM). (N) Suspend some or all of the configured uplink grants of Grant Type 1 associated with this PSCell. (O) Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) containing this PSCell. (P) Cause the MAC entity of SCG to perform a partial MAC reset.

[0146] The (M) step in the above process (SD-1) may be performed based on the fact that the SCG settings include the parameter bfd-and-RLM.

[0147] The (P) of the above process (SD-1) may include some or all of the (A) through (O) of the above process (SD-1).

[0148] In LTE and / or NR, the active state of the SCG may mean a state in which the terminal device performs some or all of the following processes (A) to (O) of (SA-1) in its SCG's PSCell (SpCell). Alternatively, the active state of the SCG may mean a state in which the SCG is activated.

[0149] Processing (SA-1) (A) Send SRS using this PSCell. (B) Measure the CSI for this PSCell. (C) Report CSI for this PSCell (D) Send a PUCCH using this PSCell. (E) Send UL-SCH using this PSCell. (F) Send RACH using this PSCell. (G) Monitor the PDCCH of this PSCell. (H) Monitor PDCCH for this PSCell. (I) Activate the inactive BWP in this PSCell. (J) This PSCell will perform intermittent reception (DRX). (K) Monitor the PDCCH of this PSCell and / or the PDCCH for this PSCell, addressed to C-RNTI, MCS-C-RNTI, and / or CS-RNTI, which indicate the uplink grant for UL-SCH transmission on this PSCell. (L) The BWP is activated in this PSCell, and the PDCCH of this PSCell, and / or the PDCCH for this PSCell, are monitored, addressed to C-RNTI, MCS-C-RNTI, and / or CS-RNTI, which indicate the uplink grant in the aforementioned BWP. (M) This PSCell performs Automatic Gain Control (AGC), Beam Failure Detection (BFD) including beam failure recovery, and / or Radio Link Monitoring (RLM). (N) Initialize some or all suspended Type 1 configured uplink grants associated with this PSCell according to the stored configuration, if any. (O) Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) containing this PSCell.

[0150] In LTE and / or NR, a terminal device may determine that an SCG is inactive based on some or all of the following conditions (SD-2) (A) through (H). The signaling and control elements described in conditions (SD-2) (A) through (F) may be communicated from the base station device to the terminal device via the SCG. In addition to or instead of the above, the signaling and control elements described in conditions (SD-2) (A) through (F) may be communicated from the base station device to the terminal device via a cell group other than the SCG (MCG, SCG other than the SCG, etc.).

[0151] Condition (SD-2) (A) Receipt of RRC signaling instructing the deactivation of the SCG. (B) Receipt of MAC CE instructing to deactivate SCG (C) Reception of RRC signaling instructing PSCell to be deactivated. (D) Receiving a MAC CE instructing the PSCell to be deactivated. (E) Reception of other RRC signaling (F) Other MAC CE reception (G) Expiration of the deactivation timer for SCG (H) Expiration of the PSCell's inactivity timer

[0152] The RRC signaling in (A), (C), and (E) of the above condition (SD-2) may include a parameter such as scg-State. If scg-State is included in the RRC signaling, it may indicate SCG deactivation, and if scg-State is not included in the RRC signaling, it may indicate SCG activation. Also, scg-State may be included in the RRC connection reset message, the RRC reset message, and / or the RRC restart message. Furthermore, the RRC signaling may be generated by MN. Also, scg-State may not be included in the RRC signaling generated by SN. In this case, the determination of SCG activation / deactivation based on whether or not scg-State is included in the RRC signaling may not be made for the RRC signaling generated by SN.

[0153] In LTE and / or NR, a terminal device may determine that an SCG is active based on some or all of the following conditions (SA-2) (A) through (K). The signaling and control elements of the following conditions (SA-2) (A) through (F) may be notified from the base station device to the terminal device via the SCG. In addition to or instead of the above, the signaling and control elements of the following conditions (SA-2) (A) through (F) may be notified from the base station device to the terminal device via a cell group other than the SCG (MCG, SCG other than the SCG, etc.). An SCG being active may also mean that the SCG does not become inactive.

[0154] Condition (SA-2) (A) Receipt of RRC signaling instructing the activation of the SCG. (B) Receiving a MAC CE instructing the SCG to activate. (C) Receiving RRC signaling that instructs PSCell to activate. (D) Receiving a MAC CE instructing the PSCell to activate. (E) Reception of other RRC signaling (F) Other MAC CE reception (G)SCG inert timer (H)PSCell Inactive Timer (i) Initiation of a random access procedure resulting from a scheduling request triggered to send a MAC PDU containing a MAC SDU. (J) Starting the random access procedure (K) Initiation of a random access procedure resulting from a scheduling request (in other words, initiated by the MAC entity itself)

[0155] The RRC signaling in conditions (A), (C), and (E) of the above condition (SA-2) may be such that, for example, the parameter scg-State is not included in the RRC reset message and / or RRC restart message. Furthermore, the RRC signaling may be generated by MN.

[0156] The terminal device for inactivating the SCG may perform some or all of the following processes (A) to (I) of (SD-3) in the SCG.

[0157] Processing (SD-3) (A) Consider that SCG will be inactivated. (B) Instruct lower layers (such as MAC entities) to deactivate SCG. (C) If the terminal device is in the RRC_CONNECTED state and the SCG was activated before receiving a signaling instructing it to deactivate, and if the SRB3 was configured before receiving the RRC reconfiguration message or RRC connection reconfiguration message and the SRB3 is not released according to any RRC signaling for radio bearer configuration (RadioBearerConfig) contained in the RRC reconfiguration message or RRC connection reconfiguration message, the PDCP entity of the SRB3 is triggered to perform SDU discarding, and in addition to or instead of doing so, the RLC entity of the SRB3 is re-established. (D) Deactivate all SCells. (E) Assume that all SCell deactivation timers associated with active SCells have expired. (F) Assume that all SCell inactivity timers associated with dormant SCells have expired. (G) Do not start or restart the SCell inactive timer associated with any SCell. (H) Ignore MAC CEs that activate SCell. For example, in the process (AD), if a MAC CE that activates SCell is received and the SCG is not inactivated (or the SCG is not in an inactive state), then process (AD-1) is performed. (I) Perform the above process (AD-2). For example, if the process (AD) is instructed to deactivate the SCG (or the SCG becomes inactive), perform the process (AD-2).

[0158] If a higher layer (such as an RRC entity) instructs the MAC entity of a terminal device to deactivate the SCG based on (B) of the above process (SD-3), the MAC entity may deactivate all SCells in the SCG, and in addition to or instead of doing so, deactivate PSCells based on the above process (SD-1).

[0159] The terminal device that activates the SCG may perform some or all of the following processes (A) to (D) of (SA-3) in the SCG.

[0160] Processing (SA-3) (A) Assume that SCG is activated. (B) If the SCG was inactive before the terminal device received a signal instructing it to activate the SCG, it instructs the lower layer (MAC entity, etc.) to activate the SCG. (C) Perform the process (AD-1) to activate all SCells. (D) When SCG activation is performed based on RRC signaling, if this RRC signaling includes parameters related to random access to a PSCell (SpCell), a random access procedure is initiated in this PSCell based on the notified parameters.

[0161] If a higher layer (such as an RRC entity) instructs the MAC entity of a terminal device to activate the SCG based on (B) of the above process (SA-3), the MAC entity may activate the SCG based on the above process (SA-1).

[0162] Figure 9 shows an example of an embodiment. In Figure 9, UE122 receives a message (RRC signaling, MAC CE, etc.) from eNB102 or gNB108 notifying it to deactivate the SCG (step S900). Based on the above notification, UE122 controls the SCG to be in an inactive state (step S902). Also in Figure 9, UE122 receives a message (RRC signaling, MAC CE, etc.) from eNB102 or gNB108 notifying it to activate the SCG (step S900). Based on the above notification, UE122 controls the SCG to be in an active state (step S902).

[0163] The above operation enables efficient state changes in the process of deactivating the SCG without the UE122's transmitter 504 having to independently transmit a MAC CE to change the state of the SCG cell to an inactive state. Furthermore, when SCG deactivation is performed based on RRC signaling, conventionally, the initial state was set at the RRC layer and the state change was performed at the MAC layer. However, the above operation allows for efficient state changes of the SCG while avoiding mismatches between instructions from the RRC layer and the MAC layer.

[0164] Conditional Reconfiguration is described below. The network may configure one or more candidate target SpCells for a terminal device. The configuration parameters for each candidate target SpCell may be included in the ConditionalReconfiguration IE element of the RRC message and notified from the base station device to the terminal device. The terminal device evaluates whether the associated execution condition for each configured candidate target SpCell is met. The terminal device may apply the conditional reconfiguration associated with one of the candidate target SpCells that meets the execution condition.

[0165] The conditional reset information element included in the RRC reset message may configure one or more pairs of information (condExecutionCond or condExecutionCondSN) indicating the execution conditions that must be met to trigger the execution of the conditional reset, and information (condRRCReconfig) indicating the RRC reset message to be applied when those execution conditions are met. The condRRCReconfig may be an RRC message (RRC reset message) that includes configuration parameters for accessing a candidate target SpCell. In addition, the conditional reset information element may include an identifier (CondReconfigId) associated with each of the one or more pairs that can identify each pair.

[0166] Furthermore, if a PSCell is changed to a candidate target SpCell of the same SN as the current SN (intra-SN CPC: intra-SN Conditional PSCell Change), and the MN is not involved in the PSCell change, the RRC reconfiguration message that is notified by condRRCReconfig and applied when the execution conditions are met may be an RRC reconfiguration message generated by the SN.

[0167] Furthermore, if an SN is not currently set and an inter-SN Conditional PSCell Addition (inter-SN CPA) is performed to add a PSCell to a candidate target SpCell of the SN, or if an inter-SN Conditional PSCell Change (inter-SN CPC) is performed to change a PSCell to a candidate target SpCell of a different SN than the current SN, or if an intra-SN CPC is performed and the MN is involved in the PSCell change, the RRC reconfiguration message that is notified by condRRCReconfig and applied when the execution conditions are met may be an RRC reconfiguration message generated by the MN. In this case, the configuration parameters for accessing the candidate target SpCell may be included in the information element (MRDC-SecondaryCellGroupConfig) within the RRC reconfiguration message generated by the MN. Also, even if an intra-SN CPC is performed and the MN is not involved in the PSCell change, the RRC reconfiguration message that is notified by condRRCReconfig and applied when the execution conditions are met may be an RRC reconfiguration message generated by the MN.

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

[0169] Based on the above description, various embodiments will be explained. Note that the processes described above may be applied to any processes that are omitted in the following description.

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

[0171] The UE122 shown in Figure 5 consists of a receiving unit 500 that receives control information (DCI, MAC CE, RRC signaling, etc.) from a base station device, a processing unit 502 that processes according to the parameters included in the received control information, and a transmitting unit 504 that transmits control information (UCI, MAC CE, RRC signaling, 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.

[0172] Figure 6 is a block diagram showing the configuration of the base station device in this embodiment. To avoid a complicated explanation, Figure 6 shows only the main components closely related to this embodiment. The base station device mentioned above may be eNB102 or gNB108.

[0173] The base station device shown in Figure 6 consists of a transmitting unit 600 that transmits control information (DCI, MAC CE, RRC signaling, etc.) to the UE 122, a processing unit 602 that creates control information (DCI, MAC CE, RRC signaling, etc.) and transmits it to the UE 122, causing the processing unit 502 of the UE 122 to perform processing, and a receiving unit 604 that receives control information (UCI, MAC CE, RRC signaling, etc.) from the UE 122. Furthermore, the processing unit 602 may include some or all of the functions of various layers (for example, the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 602 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.

[0174] An example of the processing of the terminal device in this embodiment will be explained using Figure 10.

[0175] Figure 10 shows an example of the processing of the terminal device in this embodiment. The processing unit 502 of UE122 determines whether the received RRC reset message contains information (first information) indicating whether or not to change the state of the SCG based on information instructing the state setting of the secondary cell group (referred to here as scg-State) (step S1000). The processing unit 502 of UE122 sets the state of the SCG to an inactive state if the RRC reset message does not contain the first information, or if the RRC reset message contains scg-State, and sets the state of the SCG to an active state if the RRC reset message does not contain scg-State (step S1002). The processing unit 502 of UE122 does not change the state of the SCG based on whether or not the RRC reset message contains scg-State if the RRC reset message contains the first information (step S1004).

[0176] Figure 11 shows an example of ASN.1 for an RRC reconfiguration message. As shown in Figure 11, an RRC reconfiguration message (RRCReconfiguration) may include scg-State and / or a first piece of information (referred to here as keepScgState). The first piece of information may be of type ENUMERATED and have multiple values. In this case, the terminal device may determine whether a specific value is set for the first piece of information and, based on this determination, decide whether or not to change the state of the SCG based on whether or not scg-State is included. The first piece of information may also be of type BOOLEAN and have true or false values. In this case, the terminal device may determine whether or not the first piece of information is true or false and, based on this determination, decide whether or not to change the state of the SCG based on whether or not scg-State is included.

[0177] Furthermore, "not changing the state of the SCG" in step S1004 may mean that UE122 decides to activate the SCG when it is in an active state before receiving the RRC reset message containing the first information. In addition to or instead of the above, "not changing the state of the SCG" in step S1004 may mean that UE122 decides to deactivate the SCG when it is in an inactive state before receiving the RRC reset message.

[0178] Furthermore, the first information may also be information included in the conditional reset information element for conditional reset. For example, the first information may be information associated with each CondReconfigId. In this case, when the first information associated with a CondReconfigId exists, the RRC reset message associated with that CondReconfigId, which is applied when the execution conditions are met, can be considered to contain the first information.

[0179] Figure 12 shows an example of an ASN.1 of an RRC reconfiguration message that includes a conditional reconfiguration information element for conditional reconfiguration. As shown in Figure 12, an RRC reconfiguration message (RRCReconfiguration) may include a conditional reconfiguration information element (CondationalReconfiguration information element). The ConditionalReconfiguration information element may include a CondReconfigToAddModList information element. The CondReconfigToAddModList information element may be a list of conditional reconfigurations (CondReconfigToAddMod information elements) for adding or modifying an entry consisting of a condReconfigId, and a condExecutionCond (or condExecutionCondSN) and condRRCReconfig associated with that condReconfigId. The CondReconfigToAddMod information element may include a condReconfigId, and a condExecutionCond (or condExecutionCondSN) and condRRCReconfig associated with that condReconfigId. Furthermore, the CondReconfigToAddMod information element may include a first piece of information (in this case, keepScgState). The first piece of information may be of type ENUMERATED. In this case, the terminal device may determine whether the CondReconfigToAddMod information element contains the first piece of information, and based on this determination, determine whether to change the state of the SCG based on whether or not scg-State is included when applying condRRCReconifg contained in this CondReconfigToAddMod information element. The first piece of information may also be of type BOOLEAN, which has a true or false value. In this case, the terminal device may determine whether the first piece of information is true or false, and based on this determination, determine whether or not to change the state of the SCG based on whether or not scg-State is included when applying condRRCReconifg contained in this CondReconfigToAddMod information element.

[0180] Alternatively, the first piece of information may be a list of some or all CondReconfigIds. In this case, the first piece of information may be considered to be included in the RRC reconfiguration message that is applied when the execution conditions are met, which is associated with the CondReconfigIds included in the list. Alternatively, one may determine that the first piece of information is not included in the RRC reconfiguration message that is applied when the execution conditions are met, which is associated with the CondReconfigIds included in the list.

[0181] Figure 13 shows an example of an ASN.1 of an RRC reconfiguration message that includes a conditional reconfiguration information element for conditional reconfiguration. As shown in Figure 13, an RRC reconfiguration message (RRCReconfiguration) may include a conditional reconfiguration information element (ConditionalReconfiguration information element). The ConditionalReconfiguration information element may include a CondReconfigToAddModList information element. The CondReconfigToAddModList information element may be a list of conditional reconfigurations (CondReconfigToAddMod information elements) for adding or modifying entries consisting of a condReconfigId, and condExecutionCond (or condExecutionCondSN) and condRRCReconfig associated with that condReconfigId. The CondReconfigToAddMod information element may include a condReconfigId, and condExecutionCond (or condExecutionCondSN) and condRRCReconfig associated with that condReconfigId. Furthermore, the ConditionalReconfiguration information element may include a first piece of information (in this case, the KeepScgStateList information element). The first piece of information may be a list of CondReconfigIds. In this case, when the terminal device applies the condRRCReconfigifg contained in the CondReconfigToAddMod information element, it may determine whether the CondReconfigId of this CondReconfigToAddMod information element is an identifier contained in the KeepScgStateList information element, and based on this determination, it may decide whether or not to change the state of the SCG based on whether or not scg-State is included.

[0182] Furthermore, the aforementioned RRC reconfiguration message may be an RRC connection reconfiguration message or other RRC signaling.

[0183] Thus, in this embodiment, the UE122 determines whether or not to change the state of the SCG based on the signaling notified from the base station equipment. This allows the UE122 to set an appropriate SCG state when performing RRC reset, even if, for example, an RRC reset message is pre-configured in the UE122 during conditional resetting.

[0184] An example of the processing of the terminal device in this embodiment will be explained using Figure 14.

[0185] Figure 14 shows an example of the processing of the terminal device in this embodiment. The processing unit 502 of UE122 receives an RRC reset message (step S1400). If the RRC reset message contains information instructing the setting of the secondary cell group state (referred to here as scg-State), the processing unit 502 of UE122 sets the SCG state to an inactive state if the value of scg-State indicates a first value (e.g., deactivated), and does not change the SCG state if the value of scg-State indicates a second value (e.g., keep). If the RRC reset message does not contain scg-State, the processing unit 502 of UE122 sets the SCG state to an active state (step S1402).

[0186] Other conditions may be considered in step S1402. For example, step S1402 may be executed if the information is not included in any of the following: the information element for setting the SCG side (MRDC-SecondaryCellGroup), the E-UTRA RRC connection reconfiguration message (RRCConnectionReconfiguration), and the E-UTRA RRC connection resume message (RRCConnectionResume).

[0187] Furthermore, "not changing the state of the SCG" in step S1402 may mean that UE122 decides to activate the SCG if it is in an active state before receiving this RRC reset message. In addition to or instead of the above, "not changing the state of the SCG" in step S1402 may mean that UE122 decides to deactivate the SCG if it is in an inactive state before receiving this RRC reset message.

[0188] Figure 15 shows an example of ASN.1 for an RRC reconfiguration message. As shown in Figure 15, an RRC reconfiguration message (RRCReconfiguration) may include scg-State. The terminal device may decide not to change the state of the SCG based on the presence of scg-State and its value being "keep," or to set the SCG state to inactive based on its value being "deactivated." Alternatively, the terminal device may decide to set the SCG state to active based on the absence of scg-State.

[0189] The aforementioned RRC reset message may be an RRC connection reset message or other RRC signaling. Furthermore, the aforementioned conditional reset information elements may be communicated to the terminal device as multiple independent parameters. For example, the aforementioned conditional reset information elements may be set on the terminal device as any combination of (A) a setting to perform a conditional reset to change a PCell (i.e., a Conditional Reset Over), (B) a setting to perform a conditional reset to add or change a PSCell (i.e., a Conditional PSCell addition / change), or (C) a setting to perform a conditional reset to add or change a PSCell that will be used continuously (i.e., a Continious Conditional PSCell addition / change), or all of these.

[0190] Thus, in this embodiment, the UE122 determines whether to activate, deactivate, or leave the SCG state unchanged based on the signaling notified from the base station device. This allows the UE122 to set an appropriate SCG state when performing RRC reset, even when an RRC reset message is pre-configured in the UE122, such as in a conditional reset.

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

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

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

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

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

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

[0197] Furthermore, in the above explanation, expressions such as "it has been confirmed that...", "it is set that...", and "it includes..." can be used interchangeably.

[0198] In the above explanation, "dormant state" may be replaced with "inactive state," and "state after recovering from dormancy" may be replaced with "active state." Also, in the above explanation, "activation" and "inactivation" may be replaced with "active state" and "inactive state," respectively.

[0199] In the above explanation, "transition from X to Y" can be rephrased as "become X to Y". Also, in the above explanation, "cause a transition" can be rephrased as "determine a transition".

[0200] 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 the fact that A is true" may be rephrased as "perform B." That is, "performing B" may be performed independently of "being true A."

[0201] 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".

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

[0203] The program running in the device according to this embodiment may be a program that controls the Central Processing Unit (CPU), etc., to make the computer function in order to realize the functions of this embodiment. The program or the information handled by the program 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.

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

[0205] 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 inside computer systems that act as servers or clients in such cases. In addition, the above-mentioned programs may be for the purpose of realizing some of the functions described above, and may also be programs that can realize the above-mentioned functions in combination with programs already recorded in the computer system.

[0206] 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 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.

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

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

[0209] 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. terminal device A receiving unit that receives RRC signaling, A processing unit, and The aforementioned processing unit, It is determined whether the RRC signaling includes information (first information) indicating whether or not to change the state of the secondary cell group based on information (scg-State) that instructs the setting of the state of the secondary cell group, If the RRC signaling does not include the first information, Based on the RRC signaling including the scg-State, the state of the secondary cell group is set to an inactive state, and based on the RRC signaling not including the scg-State, the state of the secondary cell group is set to an active state. If the RRC signaling includes the first information, The state of the secondary cell group will not be changed based on whether or not the RRC signaling includes the scg-State. Terminal device.

2. A base station device that communicates with terminal devices. A transmitting unit that transmits RRC signaling, A processing unit, and Based on the fact that the RRC signaling does not include the first information but includes scg-State, the terminal device is notified to set the state of the secondary cell group to an inactive state. Based on the fact that the RRC signaling does not include the first information and does not include the scg-State, the terminal device is notified to set the state of the secondary cell group to an active state. Based on including the first information in the RRC signaling, the terminal device is notified that the status of the secondary cell group will not be changed. Base station equipment.

3. A method applicable to terminal devices. The steps include receiving RRC signaling and The step of processing the RRC signaling is included, It is determined whether the RRC signaling includes information (first information) indicating whether or not to change the state of the secondary cell group based on information (scg-State) that instructs the setting of the state of the secondary cell group, If the RRC signaling does not include the first information, Based on the RRC signaling including the scg-State, the state of the secondary cell group is set to an inactive state, and based on the RRC signaling not including the scg-State, the state of the secondary cell group is set to an active state. If the RRC signaling includes the first information, The state of the secondary cell group will not be changed based on whether or not the RRC signaling includes the scg-State. method.

Images