WO2024005010A1 - Terminal device, method, and integrated circuit - Google Patents

Abstract

An RRC processing unit of this terminal device notifies a MAC processing unit of activation of a secondary cell group (SCG) in response to reception of signaling information indicating that the SCG is to be activated, and if the RRC processing unit has given the notification indicating activation of the SCG and it is determined that a plurality of BFD-RS sets are set for a PSCell, the MAC processing unit of the terminal device notifies the RRC processing unit of a necessity to execute a random access procedure to activate the SCG on the basis of a determination that counter values associated with the respective plurality of BFD-RS sets set for the PSCell are all equal to or larger than a threshold value.

Description

Terminal devices, methods, and integrated circuits

The present invention relates to a terminal device, a method, and an integrated circuit.
This application claims priority to Japanese Patent Application No. 2022-104494 filed in Japan on June 29, 2022, the contents of which are incorporated herein.

The 3rd Generation Partnership Project (3GPP), which is a standardization project for cellular mobile communication systems, is conducting technical studies and standardization for cellular mobile communication systems, including wireless access, core networks, services, etc. There is.

For example, E-UTRA (Evolved Universal Terrestrial Radio Access) is a radio access technology (Radio Access Technology: RAT) for 3.9th and 4th generation cellular mobile communication systems that has started technical study and standard development in 3GPP. Ta. Currently, 3GPP is still conducting technical studies and standardization for E-UTRA expansion technology. Note that E-UTRA is also referred to as Long Term Evolution (LTE: registered trademark), and the extended technology is also referred to as LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).

In addition, NR (New Radio, or NR Radio access) is being studied and standardized as a radio access technology (RAT) for 5th Generation (5G) cellular mobile communication systems in 3GPP. started. Currently, 3GPP is still conducting technical studies and standardization for NR expansion technology.

In 3GPP, dual connectivity (also referred to as multi-connectivity) technology, in which one or more base station devices and terminal devices communicate using multiple cell groups, is being considered as an expansion technology for NR, and further expansion technology in dual connectivity is being considered. As one of the methods, secondary cell group deactivation (SCG deactivation) was investigated. Furthermore, data communication using multiple TRPs (Transmission Reception Points) is being considered, but efficient operation is not possible when cell groups are inactivated in terminal equipment that is configured with multiple TRPs. Not considered.

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

In order to achieve the above object, one embodiment of the present invention takes the following measures. That is, one aspect of the present invention is a terminal device that communicates with a base station device, which includes a PHY processing unit, a MAC processing unit that performs MAC layer processing, an RRC processing unit, and receiving signaling from the base station device. a receiving unit, the RRC processing unit notifying the MAC processing unit that the secondary cell group (SCG) is to be activated based on receiving the signaling indicating that the SCG is to be activated. , when the MAC processing unit is notified by the RRC processing unit that the SCG will be activated, the MAC processing unit transmits one or more reference signals for beam failure detection to the PSCell of the SCG. It is determined whether multiple BFD-RS sets are configured as a set (BFD-RS set), and when it is determined that multiple BFD-RS sets are configured for the PSCell, the It is determined whether the value of the counter associated with each of the BFD-RS sets set for the PSCell is greater than or equal to a threshold value, and Based on the determination that all the values of the counters linked to each are equal to or higher than the threshold, the RRC processing unit is notified that it is necessary to execute a random access procedure in order to activate the SCG, and the The PHY processing unit notifies the MAC processing unit of a beam failure instance for each set of BFD-RS, the counter is prepared for each BFD-RS set of the PSCell in which the BFD-RS set is configured, It is used to count beam failure instances notified from the PHY processing unit.

Further, one aspect of the present invention is a method for a terminal device communicating with a base station device, the method being applied to the terminal device communicating with the base station device, the method including the step of receiving signaling from the base station device. , as RRC layer processing, a step of notifying the MAC layer that the secondary cell group (SCG) is to be activated based on receiving the signaling indicating that the SCG is to be activated; and MAC layer processing. When the RRC layer notifies that the SCG will be activated, one set (BFD-RS set) of one or more reference signals for beam failure detection is sent to the PSCell of the SCG. ), a step of determining whether multiple BFD-RS sets are configured, and a step of determining whether multiple BFD-RS sets are configured for the PSCell; a step of determining whether the value of a counter associated with each of the BFD-RS sets set for the PSCell is equal to or greater than a threshold; a step of notifying the RRC layer that it is necessary to execute a random access procedure in order to activate the SCG based on the determination that all the values of the linked counters are equal to or higher than the threshold; The processing includes a step of notifying a MAC layer of a beam failure instance for each set of BFD-RS, and the counter is prepared for each BFD-RS set of the PSCell in which the BFD-RS set is configured. , is used to count beam failure instances notified from the PHY layer.

Further, one aspect of the present invention is an integrated circuit mounted on a terminal device communicating with a base station device, the integrated circuit mounted on a terminal device communicating with the base station device, the integrated circuit receiving signaling from the base station device. and a function of notifying the MAC layer to activate the secondary cell group (SCG) based on the reception of the signaling indicating that the secondary cell group (SCG) is to be activated as processing of the RRC layer. As a process of the MAC layer, when it is notified from the RRC layer that the SCG will be activated, one set of one or more reference signals for beam failure detection is sent to the PSCell of the SCG. (BFD-RS set), a function to determine whether or not multiple BFD-RS sets are configured, and when it is determined that multiple BFD-RS sets are configured for the PSCell, A function for determining whether the value of a counter associated with each of the BFD-RS sets set for the PSCell is equal to or greater than a threshold; A function that notifies the RRC layer that it is necessary to execute a random access procedure to activate the SCG based on the determination that all counter values associated with each RS set are equal to or higher than a threshold value. and a function of notifying the MAC layer of a beam failure instance for each set of BFD-RS as processing of the PHY layer, is prepared for each BFD-RS set, and is used to count beam failure instances notified from the PHY layer.

Note that these comprehensive or specific aspects may be realized by a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium. It may be realized by any combination of the following.

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

FIG. 1 is a schematic diagram of a communication system according to the present embodiment. FIG. 2 is a diagram illustrating an example of the E-UTRA protocol configuration according to the present embodiment. FIG. 3 is a diagram illustrating an example of the NR protocol configuration according to the present embodiment. FIG. 3 is a diagram illustrating an example of a flow of procedures for various settings in RRC according to the present embodiment. FIG. 2 is a block diagram showing the configuration of a terminal device in this embodiment. FIG. 2 is a block diagram showing the configuration of a base station device in this embodiment. An example of an ASN.1 description included in a message regarding resetting an RRC connection in NR in this embodiment. An example of an ASN.1 description included in a message regarding reconfiguration of an RRC connection in E-UTRA in this embodiment. An example of processing related to activation/inactivation of SCG in this embodiment.

Hereinafter, this embodiment will be described in detail with reference to the drawings.

LTE (and LTE-A, LTE-A Pro) and NR may be defined as different radio access technologies (RAT). Furthermore, LTE, which can be connected to NR using Multi-Radio Dual Connectivity (MR-DC), may be distinguished from conventional LTE. Furthermore, LTE that uses 5GC in the core network (Core Network: CN) may be distinguished from conventional LTE that uses EPC in the core network. Note that conventional LTE may be LTE that does not implement the technology standardized after Release 15 in 3GPP. This embodiment may be applied to NR, LTE and other RATs. Although the following description uses terms related to LTE and NR, the present embodiment may be applied to technologies using other terms and/or other radio access technologies. Furthermore, the term E-UTRA and the term LTE in this embodiment may be interchanged with each other.

Note that in this embodiment, the names of each node and entity and the processing in each node and entity will be explained when the radio access technology is E-UTRA or NR. However, this embodiment is applicable to other radio access technologies. may be applied. The names of each node and entity in this embodiment may be different names.

FIG. 1 is a schematic diagram of a communication system according to this embodiment. Note that the functions of each node, radio access technology, core network, interface, etc. explained using FIG. 1 are some functions closely related to this embodiment, and may have other functions.

E-UTRA100 may be a radio access technology. Further, the E-UTRA 100 may be an air interface between the UE 122 and the eNB 102. The air interface between UE 122 and eNB 102 may be referred to as a Uu interface. The eNB (E-UTRAN Node B) 102 may be a base station device of the E-UTRA 100. The eNB 102 may have the E-UTRA protocol described below. The E-UTRA protocol may be composed of the E-UTRA User Plane (UP) protocol, which will be described later, and the E-UTRA Control Plane (CP) protocol, which will be described later. The eNB 102 may terminate the E-UTRA user plane (UP) protocol and the E-UTRA control plane (CP) protocol for the UE 122. A radio access network composed of eNBs may be called E-UTRAN.

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 an S1 interface. The interface 112 may include 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) within EPC 104 . The user plane interface of interface 112 may terminate at a serving gateway (S-GW: not shown) within EPC 104 . The control plane interface of interface 112 may be referred to as the S1-MME interface. The user plane interface of interface 112 may be referred to as the S1-U interface.

Note that one or more eNBs 102 may be connected to the EPC 104 via the interface 112. An interface may exist between multiple eNBs 102 connected to the EPC 104 (not shown). The interface between the plurality of eNBs 102 connected to the EPC 104 may be referred to as an X2 interface.

NR106 may be a radio access technology. NR106 may also be an air interface between UE122 and gNB108. The air interface between UE 122 and gNB 108 may be referred to as a Uu interface. gNB (g Node B) 108 may be a base station device of NR106. gNB 108 may have the NR protocol described below. The NR protocol may be composed of the NR User Plane (UP) protocol, which will be described later, and the NR Control Plane (CP) protocol, which will be described later. The gNB 108 may terminate the NR User Plane (UP) protocol and the NR Control Plane (CP) protocol for the UE 122.

5GC110 may be a core network. Interface 116 is an interface between gNB 108 and 5GC 110, and may be called an NG interface. The interface 116 may include 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 terminate in an Access and Mobility Management Function (AMF: not shown) within 5GC 110. The user plane interface of interface 116 may terminate at a User Plane Function (UPF: not shown) within 5GC 110. The control plane interface of interface 116 may be referred to as an NG-C interface. The user plane interface of interface 116 may be referred to as an NG-U interface.

Note that one or more gNBs 108 may be connected to the 5GC 110 via the interface 116. An interface may exist between multiple gNBs 108 connected to 5GC 110 (not shown). The interface between multiple gNBs 108 connected to 5GC 110 may be called an Xn interface.

eNB102 may have the ability to connect to 5GC110. The eNB 102 that has the function of connecting to the 5GC 110 may be called an ng-eNB. Interface 114 is an interface between eNB 102 and 5GC 110, and may be called an NG interface. The interface 114 may include 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 terminate at an AMF within 5GC 110. The user plane interface of interface 114 may terminate at a UPF within 5GC 110. The control plane interface of interface 114 may be referred to as an NG-C interface. The user plane interface of interface 114 may be referred to as an NG-U interface. A radio access network composed of ng-eNBs or gNBs may be referred to as NG-RAN. NG-RAN, E-UTRAN, etc. may also be simply referred to as networks. Further, the network may include eNB, ng-eNB, gNB, and the like.

Note that one or more eNBs 102 may be connected to the 5GC 110 via the interface 114. An interface may exist between multiple eNBs 102 connected to 5GC 110 (not shown). The interface between multiple eNBs 102 connected to 5GC 110 may be called an Xn interface. Further, the eNB 102 connected to the 5GC 110 and the gNB 108 connected to the 5GC 110 may be connected through an interface 120. The interface 120 between the eNB 102 that connects to the 5GC 110 and the gNB 108 that connects to the 5GC 110 may be called an Xn interface.

gNB108 may have the function of connecting to EPC104. gNB 108 having the function of connecting to EPC 104 may be called en-gNB. Interface 118 is an interface between gNB 108 and EPC 104, and may be called an S1 interface. Interface 118 may include a user plane interface through which user data passes. The user plane interface of interface 118 may terminate at an S-GW (not shown) within EPC 104. The user plane interface of interface 118 may be referred to as the S1-U interface. Further, the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 may be connected through an interface 120. The interface 120 between the eNB 102 that connects to the EPC 104 and the gNB 108 that connects to the EPC 104 may be called an X2 interface.

The interface 124 is an interface between the EPC 104 and the 5GC 110, and may be an interface that passes only CP, only UP, or both CP and UP. Furthermore, some or all of the interfaces 114, 116, 118, 120, 124, etc. may not exist depending on the communication system provided by the communication carrier or the like.

The UE 122 may be a terminal device that can receive system information and paging messages transmitted from the eNB 102 and/or gNB 108. Further, the UE 122 may be a terminal device capable of wirelessly connecting with the eNB 102 and/or the gNB 108. Further, the UE 122 may be a terminal device that can simultaneously perform a wireless connection with the eNB 102 and a wireless connection with the gNB 108. UE 122 may have an E-UTRA protocol and/or an NR protocol. Note that the wireless connection may be a Radio Resource Control (RRC) connection.

Furthermore, the UE 122 may be a terminal device that can be connected to the EPC 104 and/or 5GC 110 via the eNB 102 and/or gNB 108. If the core network connected to eNB102 and/or gNB108 with which UE122 communicates is EPC104, each data radio bearer (DRB) established between UE122 and eNB102 and/or gNB108 (to be described later) ) may be uniquely associated with each EPS (Evolved Packet System) bearer passing through the EPC 104. 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 (registered trademark) frames that pass through the same EPS bearer.

Furthermore, if the core network connected to eNB102 and/or gNB108 with which UE122 communicates is 5GC110, each DRB established between UE122 and eNB102 and/or gNB108 is further established within 5GC110. It may be linked to one of the PDU (Packet Data Unit) sessions. There may be one or more QoS flows in each PDU session. Each DRB may be mapped with one or more QoS flows, or may not be mapped with any QoS flows. Each PDU session may be identified by a PDU session identifier (Identity, or ID). Further, each QoS flow may 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.

There may be no PDU sessions and/or QoS flows in the EPC 104. Also, 5GC110 does not need to have an EPS bearer. When the UE 122 is connected to the EPC 104, the UE 122 has information on the EPS bearer, but may not have information on the PDU session and/or QoS flow. Further, when the UE 122 is connected to the 5GC 110, the UE 122 has information on the PDU session and/or QoS flow, but does not need to have information on the EPS bearer.

Note that in the following description, the eNB 102 and/or gNB 108 will also be simply referred to as a base station device, and the UE 122 will also be simply referred to as a terminal device or UE.

FIG. 2 is a diagram of an example of the E-UTRA protocol architecture according to the present embodiment. Further, FIG. 3 is a diagram of an example of the NR protocol configuration according to the present embodiment. Note that the functions of each protocol explained using FIG. 2 and/or FIG. 3 are some functions closely related to this embodiment, and may have other functions. Note that in this embodiment, the uplink (UL) may be a link from a terminal device to a base station device. Furthermore, in this embodiment, the downlink (DL) may be a link from a base station device to a terminal device.

Figure 2(A) is a diagram of the E-UTRA user plane (UP) protocol stack. As shown in FIG. 2(A), the E-UTRA UP protocol may be a protocol between the UE 122 and the eNB 102. That is, the E-UTRA UP protocol may be a protocol that terminates at the eNB 102 on the network side. As shown in Figure 2(A), the E-UTRA user plane protocol stack consists of a wireless physical layer (PHY) 200, a medium access control layer (MAC) 200, and a medium access control layer (MAC). RLC (Radio Link Control) 204, which is a radio link control layer, and PDCP (Packet Data Convergence Protocol) 206, which is a packet data convergence protocol layer. It's okay to be.

Figure 3(A) is a diagram of the NR user plane (UP) protocol stack. As shown in FIG. 3(A), the NRUP protocol may be a protocol between the UE 122 and the gNB 108. That is, the NR UP protocol may be a protocol that terminates at the gNB 108 on the network side. As shown in Figure 3(A), the NR user plane protocol stack consists of PHY300, which is the radio physical layer, MAC302, which is the medium access control layer, RLC304, which is the radio link control layer, PDCP306, which is the packet data convergence protocol layer, and It may be configured from SDAP (Service Data Adaptation Protocol) 310, which is a service data adaptation protocol layer.

Figure 2(B) is a diagram of the E-UTRA control plane (CP) protocol configuration. As shown in FIG. 2(B), in the E-UTRA CP protocol, RRC (Radio Resource Control) 208, which is a radio resource control layer, may be a protocol between the UE 122 and the eNB 102. That is, RRC208 may be a protocol that terminates at eNB102 on the network side. Further, in the E-UTRA CP protocol, the NAS (Non Access Stratum) 210, which is a non-AS (Access Stratum) layer, may be a protocol between the UE 122 and the MME. That is, the NAS 210 may be a protocol that terminates with the MME on the network side.

Figure 3(B) is a diagram of the NR control plane (CP) protocol configuration. As shown in FIG. 3(B), in the NR CP protocol, RRC 308, which is a radio resource control layer, may be a protocol between UE 122 and gNB 108. That is, RRC308 may be a protocol that terminates at gNB108 on the network side. Further, in the NR CP protocol, the NAS 312, which is a non-AS layer, may be a protocol between the UE 122 and the AMF. That is, the NAS 312 may be a protocol that terminates with AMF on the network side.

Note that the AS (Access Stratum) layer may be a layer that terminates between the UE 122 and the eNB 102 and/or gNB 108. That is, the AS layer is a layer that includes some or all of PHY200, MAC202, RLC204, PDCP206, and RRC208, and/or a layer that includes some or all of PHY300, MAC302, RLC304, PDCP306, SDAP310, and RRC308. It's fine.

In this embodiment, the following does not distinguish between the E-UTRA protocol and the NR protocol, and uses PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), and RRC (RRC layer). , the term NAS (NAS layer) is sometimes used. In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) are the PHY (PHY layer) of the E-UTRA protocol. ), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), NAS (NAS layer). layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer). Further, the SDAP (SDAP layer) may be the SDAP (SDAP layer) of the NR protocol.

In addition, in this embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, PHY200, MAC202, RLC204, PDCP206, and RRC208 are respectively referred to as PHY for E-UTRA or PHY for LTE, MAC for E-UTRA, or It is also called MAC for LTE, RLC for E-UTRA or RLC for LTE, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE. and PHY200, MAC202, RLC204, PDCP206, and RRC208, respectively. It may also be written as LTE RRC. Also, when distinguishing between the E-UTRA protocol and the NR protocol, PHY300, MAC302, RLC304, PDCP306, and RRC308 are called PHY for NR, MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively. There are some things. PHY300, MAC302, RLC304, PDCP306, and RRC308 may also be written as NR PHY, NR MAC, NR RLC, NR PDCP, NR RRC, etc., respectively.

Entities in the AS layer of E-UTRA and/or NR will be explained. An entity that has some or all of the functions of the MAC layer may be called a MAC entity. An entity that has some or all of the functions of the RLC layer may be called an RLC entity. An entity that has some or all of the functions of the PDCP layer may be called a PDCP entity. An entity that has some or all of the functions of the SDAP layer may be called an SDAP entity. An entity that has some or all of the functions of the RRC layer may be called an RRC entity. The MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be replaced with MAC, RLC, PDCP, SDAP, and RRC, respectively.

Note that data provided from MAC, RLC, PDCP, and SDAP to lower layers and/or data provided from lower layers to MAC, RLC, PDCP, and SDAP are referred to as MAC PDU (Protocol Data Unit) and RLC, respectively. It can be called PDU, PDCP PDU, SDAP PDU. In addition, data provided from upper layers to MAC, RLC, PDCP, and SDAP and/or data provided from MAC, RLC, PDCP, and SDAP to upper layers are MAC SDU (Service Data Unit) and RLC SDU, respectively. , PDCP SDU, SDAP SDU. Furthermore, a segmented RLC SDU may be referred to as an RLC SDU segment.

Here, the base station device and the terminal device exchange (transmit and receive) signals in a higher layer. A higher layer may also be referred to as an upper layer, and may be interchanged with each other. For example, a base station device and a terminal device may transmit and receive an RRC message (also referred to as RRC signalling) in a radio resource control (RRC) layer. Further, the base station device and the terminal device may transmit and receive MAC control elements in the MAC (Medium Access Control) layer. Furthermore, the RRC layer of the terminal device acquires system information broadcast from the base station device. Here, the RRC message, system information, and/or MAC control element are also referred to as higher layer signals (higher layer signaling) or higher layer parameters (higher layer parameters). Each of the parameters included in the upper layer signal received by the terminal device may be referred to as an upper layer parameter. For example, in PHY layer processing, the upper layer means the upper layer seen from the PHY layer, so one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. It can mean that. For example, in MAC layer processing, the upper layer may mean one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, and the like.

Hereinafter, "A is given (provided) by the upper layer" and "A is given (provided) by the upper layer" mean the upper layers of the terminal device (mainly the RRC layer and MAC layer). etc.) may mean that A is received from the base station device, and the received A is given (provided) from an upper layer of the terminal device to the physical layer of the terminal device. For example, in a terminal device, being “provided with upper layer parameters” means that the upper layer parameter included in the received upper layer signal is received from the base station device, and the upper layer parameter included in the received upper layer signal is transmitted from the upper layer of the terminal device to the terminal device. It may also mean provided in layers. Setting upper layer parameters to a terminal device may mean that upper layer parameters are given (provided) to the terminal device. For example, setting upper layer parameters in a terminal device may mean that the terminal device receives an upper layer signal from a base station device and sets the received upper layer parameters in the upper layer. However, setting upper layer parameters to the terminal device may include setting default parameters given in advance to the upper layer of the terminal device. When explaining sending an RRC message from a terminal device to a base station device, the expression "submit" a message from the RRC entity of the terminal device to a lower layer may be used. . In a terminal device, "submitting a message to a lower layer" from an RRC entity may mean submitting a message to a PDCP layer. In a terminal device, "submitting a message from the RRC layer to a lower layer" means that RRC messages are sent using SRBs (SRB0, SRB1, SRB2, SRB3, etc.), so It may also mean submitting to the corresponding PDCP entity. When the RRC entity of the terminal device receives an indication from a lower layer, the lower layer may refer to one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, etc.

An example of the PHY function will be explained. The PHY of the terminal device may have a function of receiving data transmitted from the PHY of the base station device via a downlink (DL) physical channel. The PHY of the terminal device may have a function of transmitting data to the PHY of the base station device via an uplink (UL) physical channel. The PHY may be connected to the upper MAC via a transport channel. The PHY may pass data to the MAC via a transport channel. The PHY may also be provided with data from the MAC via a transport channel. In the PHY, RNTI (Radio Network Temporary Identifier) may be used to identify various control information.

Here, the physical channel will be explained. The physical channels used for wireless communication between the terminal device and the base station device may include the following physical channels.

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)

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

Furthermore, in NR, the PBCH may be used to broadcast a time index (SSB-Index) within the period of a synchronization signal block (SSB).

The PDCCH may be used to transmit (or carry) downlink control information (DCI) in downlink wireless communication (wireless communication from a base station device to a terminal device). Here, one or more DCIs (which may also be referred to as DCI formats) may be defined for transmission of downlink control information. That is, a field for downlink control information may be defined as DCI and mapped to information bits. PDCCH may be transmitted on PDCCH candidates. A terminal device 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. Additionally, the terminal device monitors PDCCH candidates in configured monitoring occasions within one or more configured control resource sets (CORESET) configured by the search space configuration. It's fine. The DCI format may be used for PUSCH scheduling in the serving cell. PUSCH may be used for transmitting user data, transmitting an RRC message, which will be described later, and the like.

PDCCH repetition may be operated by using two search space sets explicitly linked by the configuration provided by the upper layer (RRC layer). Two linked search space sets may also be associated with a corresponding CORESET. For PDCCH repetition, two linked search space sets may be configured in the terminal device with the same number of PDCCH candidates. Two PDCCH candidates existing in two linked search space sets may be linked by the same candidate index. When PDCCH repetition is scheduled to a terminal device, inter-slot repetition may be allowed, and each repetition consists of the same number of Control Channel Elements (CCEs) and coded bits. ), and may have the same DCI payload.

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

The PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer. Further, in the case of downlink, the PDSCH may be used to transmit system information (SI), random access response (RAR), and the like.

PUSCH may be used to transmit HARQ-ACK and/or CSI along with uplink data (UL-SCH: Uplink Shared CHannel) or uplink data from the MAC layer. Further, PUSCH may be used to transmit only CSI or only HARQ-ACK and CSI. That is, PUSCH may be used to transmit only UCI. Further, the PDSCH or PUSCH may be used to transmit an RRC message and a MAC CE, which will be described later. Here, in the PDSCH, the RRC message transmitted from the base station device may be common signaling to multiple terminal devices within the cell. Furthermore, the RRC message transmitted from the base station device may be dedicated signaling for a certain terminal device. That is, UE specific information may be transmitted to a certain terminal device using dedicated signaling. Further, PUSCH may be used to transmit UE Capability in the uplink.

PRACH may be used to transmit a random access preamble. PRACH is used to indicate initial connection establishment procedures, handover procedures, connection re-establishment procedures, synchronization (timing adjustment) for uplink transmission, and requests for UL-SCH resources. It's okay.

An example of the MAC function will be explained. MAC may also be called a MAC sublayer. The MAC may have a function of mapping various logical channels to corresponding transport channels. A logical channel may be identified by a logical channel identifier (Logical Channel Identity, or Logical Channel ID). The MAC may be connected to the upper RLC through a logical channel. Logical channels may be divided into control channels for transmitting control information and traffic channels for transmitting user information, depending on the type of information to be transmitted. Further, logical channels may be divided into uplink logical channels and downlink logical channels. The MAC may have a function of multiplexing MAC SDUs belonging to one or more different logical channels and providing the same to the PHY. The MAC may also have a function of demultiplexing the MAC PDUs provided from the PHY and providing them to the upper layer via the logical channel to which each MAC SDU belongs. The MAC may also have a 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 of performing priority processing between terminal devices using dynamic scheduling. Further, the MAC may have a function of performing priority processing between logical channels within one terminal device. The MAC may have a function to prioritize resources that overlap within one terminal device. E-UTRA MAC may have the function of identifying Multimedia Broadcast Multicast Services (MBMS). The NR MAC may also have a function of identifying multicast/broadcast service (MBS). The MAC may have the ability to select the transport format. MAC has the function of performing discontinuous reception (DRX) and/or discontinuous transmission (DTX), the function of performing random access (RA) procedure, the function of notifying information on transmittable power, and the power It may have a headroom report (PHR) function, a buffer status report (BSR) function that notifies information on the amount of data in the transmission buffer, etc. NR MAC may have a Bandwidth Adaptation (BA) function. Also, the MAC PDU format used in E-UTRA MAC and the MAC PDU format used in NR MAC may be different. The MAC PDU may also include a MAC control element (MAC control element: MAC CE), which is an element for controlling the MAC.

The logical channels for uplink (UL) and/or downlink (DL) used in E-UTRA and/or NR will be explained.

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

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

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

DCCH (Dedicated Control Channel) is a logical channel for transmitting dedicated control information in a point-to-point bidirectional manner between a terminal device and a base station device. It's good. The dedicated control information may be control information dedicated to each terminal device. DCCH may be used when the terminal device has an RRC connection.

DTCH (Dedicated Traffic Channel) may be a logical channel for transmitting user data on a one-to-one (point-to-point) basis between a terminal device and a base station device. DTCH may be a logical channel for transmitting dedicated user data. The dedicated user data may be user data dedicated to each terminal device. DTCH may exist on both uplink and downlink.

The mapping of uplink logical channels and transport channels in E-UTRA and/or NR will be explained.

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

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

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

The mapping of downlink logical channels and transport channels in E-UTRA and/or NR will be explained.

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

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

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

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

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

An example of the RLC function will be explained. RLC may also be called an RLC sublayer. The E-UTRA RLC may have a function of segmenting and/or concatenating data provided from the upper layer PDCP and providing it to the lower layer. The E-UTRA RLC may have a function of reassembling and re-ordering data provided from lower layers and providing the data to upper layers. NR RLC may have a function of adding a sequence number independent of the sequence number added by PDCP to data provided from the upper layer PDCP. Furthermore, NR RLC may have a function of segmenting data provided from PDCP and providing it to lower layers. Further, the NR RLC may have a function of reassembling data provided from lower layers and providing the data to upper layers. RLC may also have a data retransmission function and/or a retransmission request function (AutomaticRepeat reQuest: ARQ). Additionally, RLC may have a function of performing error correction using ARQ. Control information indicating data that needs to be retransmitted, which is sent from the RLC receiving side to the transmitting side in order to perform ARQ, can be called a status report. Also, the status report transmission instruction sent from the RLC transmitting side to the receiving side can be referred to as a poll. The RLC may also have a function to detect data duplication. RLC may also have a data discard function. RLC may have three modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). The TM does not divide data received from the upper layer and does not need to add an RLC header. A TM RLC entity is a uni-directional entity and may be configured as a transmitting TM RLC entity or as a receiving TM RLC entity. In UM, data received from the upper layer is divided and/or combined, RLC headers are added, etc., but there is no need to control data retransmission. A UM RLC entity may be a unidirectional entity or a bi-directional entity. If the UM RLC entity is a unidirectional entity, the UM RLC entity may be configured as a transmitting UM RLC entity or as a receiving UM RLC entity. If the UM RLC entity is a bidirectional entity, the UM RRC entity may be configured as a UM RLC entity consisting of a transmitting side and a receiving side. In AM, division and/or combination of data received from the upper layer, addition of an RLC header, data retransmission control, etc. may be performed. The AM RLC entity is a bidirectional entity and may be configured as an AM RLC consisting of a transmitting side and a receiving side. Note that data provided by the TM to a lower layer and/or data provided from a lower layer may be referred to as a TMD PDU. Furthermore, data provided to lower layers in UM and/or data provided from lower layers may be referred to as UMD PDU. Additionally, data provided to lower layers in AM or data provided from lower layers may be referred to as AMD PDU. The RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC may be different. Further, the RLC PDU may include a data RLC PDU and a control RLC PDU. The RLC PDU for data may be called RLC DATA PDU (RLC Data PDU, RLC data PDU). Further, the control RLC PDU may be referred to as RLC CONTROL PDU (RLC Control PDU, RLC control PDU, RLC control PDU).

An example of the PDCP function will be explained. PDCP may be called a PDCP sublayer. PDCP may have a function to perform sequence number maintenance. Furthermore, PDCP may have a header compression/decompression function for efficiently transmitting user data such as IP packets and Ethernet frames over a wireless section. The protocol used to compress and decompress the header of IP packets can be called the ROHC (Robust Header Compression) protocol. Furthermore, the protocol used for compressing and decompressing Ethernet frame headers may be referred to as the EHC (Ethernet (registered trademark) Header Compression) protocol. Furthermore, PDCP may have data encryption/decryption functions. Furthermore, PDCP may have data integrity protection/integrity verification functions. PDCP may also have a re-ordering function. PDCP may also have a PDCP SDU retransmission function. Furthermore, PDCP may have a function of discarding data using a discard timer. Furthermore, PDCP may have a multiplexing (Duplication) function. Furthermore, PDCP may have a function of discarding data that has been received repeatedly. The PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. Further, the PDCP PDU may include a data PDCP PDU and a control PDCP PDU. The data PDCP PDU may be called a PDCP DATA PDU (PDCP Data PDU). Further, the control PDCP PDU may be called a PDCP CONTROL PDU (PDCP Control PDU, PDCP control PDU, PDCP control PDU).

An example of SDAP functionality will be explained. SDAP is a service data adaptation protocol layer. SDAP maps the downlink QoS flow sent from 5GC110 to the terminal device via the base station device and the data radio bearer (DRB), and/or the mapping from the terminal device to the terminal device via the base station device. It may have a function to map uplink QoS flows sent to 5GC110 and DRB. SDAP may also have a function of storing mapping rule information. SDAP may also have a function of marking a QoS flow identifier (QoS Flow ID: QFI). Note that the SDAP PDU may include a data SDAP PDU and a control SDAP PDU. SDAP PDU for data may be called SDAP DATA PDU (SDAP Data PDU, SDAP data PDU). Furthermore, the control SDAP PDU may be called an SDAP CONTROL PDU (SDAP Control PDU, SDAP control PDU, SDAP control PDU). Note that one SDAP entity of the terminal device may exist for a PDU session.

An example of the RRC function will be explained. RRC may have a broadcast function. The RRC may have a paging function from the EPC 104 and/or 5GC 110. The RRC may have a paging function from the eNB 102 that connects to the gNB 108 or 5GC 110. RRC may also have RRC connection management functionality. RRC may also have radio bearer control functionality. The RRC may also have a cell group control function. The RRC may also have mobility control functionality. The RRC may also have terminal device measurement reporting and terminal device measurement reporting control functions. RRC may also have QoS management functionality. RRC may also have radio link failure detection and recovery functionality. RRC uses RRC messages to perform broadcasting, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, radio link failure detection and recovery, etc. You may do so. Note that the RRC messages and parameters used in E-UTRA RRC may be different from the RRC messages and parameters used in NR RRC.

The RRC message may be sent using the BCCH of a logical channel, the PCCH of a logical channel, the CCCH of a logical channel, or the DCCH of a logical channel. May be sent. Furthermore, RRC messages sent using the DCCH are referred to as dedicated RRC signaling or RRC signaling.

The RRC message sent using the BCCH may include, for example, a master information block (MIB), each type of system information block (SIB), and other RRC messages may be included. RRC messages sent using the PCCH may include, for example, paging messages or other RRC messages.

RRC messages sent in the uplink (UL) direction using CCCH include, for example, RRC Setup Request message, RRC Resume Request message, RRC Reestablishment Request message, It may include an RRC system information request message (RRC System Info Request), etc. Further, for example, an RRC Connection Request message, an RRC Connection Resume Request message, an RRC Connection Reestablishment Request message, etc. may be included. Other RRC messages may also be included.

RRC messages sent in the downlink (DL) direction using CCCH include, for example, RRC Connection Reject message, RRC Connection Setup message, RRC Connection Reestablishment message, It may include an RRC Connection Reestablishment Reject message, etc. Further, for example, an RRC rejection message (RRC Reject), an RRC Setup message (RRC Setup), etc. may be included. Other RRC messages may also be included.

RRC signaling sent in the uplink (UL) direction using DCCH includes, for example, measurement report messages, RRC Connection Reconfiguration Complete messages, and RRC Connection Setup Complete messages. ), an RRC Connection Reestablishment Complete message, a Security Mode Complete message, a UE Capability Information message, and the like. Also, for example, measurement report message (Measurement Report), RRC Reconfiguration Complete message, RRC Setup Complete message, RRC Reestablishment Complete message, RRC Resume Complete message. ), a security mode complete message (Security Mode Complete), a UE Capability Information message, and the like may be included. Other RRC signaling may also be included.

RRC signaling sent in the downlink (DL) direction using DCCH includes, for example, RRC Connection Reconfiguration message, RRC Connection Release message, Security Mode Command message, It may include a UE Capability Inquiry message, etc. Also, for example, RRC Reconfiguration message, RRC Resume message, RRC Release message, RRC Reestablishment message, Security Mode Command message, UE capability inquiry message. (UE Capability Inquiry) etc. may be included. Other RRC signaling may also be included.

An example of a NAS function will be explained. The NAS may have an authentication function. The NAS may also have the ability to perform mobility management. The NAS may also have security control functions.

The functions of PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS described above are just examples, and some or all of the functions do not have to be implemented. Further, part or all of the functions of each layer may be included in other layers.

Next, the state transition of the UE 122 in LTE and NR will be explained. The UE 122 connecting to the EPC or 5GC may be in the RRC_CONNECTED state when the RRC connection has been established. The state in which the RRC connection is established may include a state in which the UE 122 holds some or all of the UE context described below. Further, the state in which the RRC connection is established may include a state in which the UE 122 can transmit and/or receive unicast data. Furthermore, when the RRC connection is suspended, the UE 122 may be in the RRC_INACTIVE state. Further, the UE 122 may enter the RRC_INACTIVE state when the UE 122 is connected to the 5GC and the RRC connection is suspended. When the UE 122 is neither in the RRC_CONNECTED state nor in the RRC_INACTIVE state, the UE 122 may be in the RRC_IDLE state.

Note that when the UE 122 is connected to the EPC, it does not have the RRC_INACTIVE state, but the E-UTRAN may start suspending the RRC connection. When the UE 122 is connected to the EPC and the RRC connection is suspended, the UE 122 may transition to the RRC_IDLE state while retaining the UE's AS context and an identifier (resumeIdentity) used for resuming. The layer above the RRC layer of the UE 122 (for example, the NAS layer) is configured such that the UE 122 maintains the UE's AS context, the E-UTRAN permits the return of the RRC connection, and the UE 122 leaves the RRC_IDLE state. When it is necessary to transition to the RRC_CONNECTED state, recovery of the suspended RRC connection may be initiated.

The definition of pause may be different between the UE 122 connecting to the EPC 104 and the UE 122 connecting to the 5GC 110. Also, when the UE122 is connected to the EPC (when the UE122 is inactive in the RRC_IDLE state) and when the UE122 is connected to the 5GC (when the UE122 is inactive in the RRC_INACTIVE state), the UE122 Some or all of the steps for returning from hibernation may be different.

Note that the RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state may be respectively referred to as connected state (connected mode), inactive state (inactive mode), and idle state (idle mode), and RRC connected state (RRC connected mode) , RRC inactive mode, and RRC idle mode.

The AS context of the UE held by the UE122 includes the current RRC settings, the current security context, the PDCP state including the ROHC (RObust Header Compression) state, and the C-RNTI (Cell Radio) used in the PCell of the connection source (Source). The information may include all or part of the Network Temporary Identifier, cell identifier (cellIdentity), and physical cell identifier of the connection source PCell. Note that the UE AS context held by any or all of eNB 102 and gNB 108 may include the same information as the UE AS context held by UE 122, or the information contained in the UE AS context held by UE 122. may contain information different from that.

The security context includes the encryption key at the AS level, 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 replay protection. The information may include all or part of the counters used for.

Next, the serving cell will be explained. In a terminal device in an RRC connected state in which a CA and/or DC, which will be described later, is not configured, a serving cell may be configured from one primary cell (PCell). In addition, in a terminal device in an RRC connected state in which CA and/or DC are configured, which will be described later, multiple serving cells include one or more special cells (Special Cell: SpCell) and one or more all secondary cells. It may mean a set of cells (set of cells) consisting of cells (Secondary Cell: SCell). The SpCell may support PUCCH transmission and contention-based Random Access (CBRA), and the SpCell may be activated at all times. The PCell may be a cell used in an RRC connection establishment procedure when a terminal device in an RRC idle state transitions to an RRC connected state. Further, the PCell may be a cell used in an RRC connection re-establishment procedure in which a terminal device re-establishes an RRC connection. Further, the PCell may be a cell used in a random access procedure during handover. The PSCell may be a cell used in a random access procedure when adding a secondary node, which will be described later. Further, SpCell may be a cell used for purposes other than those described above.

If the serving cell group configured for the terminal device is composed of an SpCell and one or more SCells, it may be considered that carrier aggregation (CA) is configured for the terminal device. . Further, for a terminal device in which CA is configured, a cell that provides additional radio resources to SpCell may mean SCell.

A cell group that is set from a base station device to a terminal device will be explained. A cell group may be composed of one SpCell. Further, a cell group may be composed of one SpCell and one or more SCells. That is, a cell group may be composed of one SpCell and optionally one or more SCells. Further, a cell group may be expressed as a set of cells.

Dual Connectivity (DC) means that a first base station device (first node) and a second base station device (second node) perform data communication using the radio resources of the cell groups that they configure. It can be technology. When DC or MR-DC, which will be described later, is performed, a cell group may be added to the terminal device from the base station device. In order to perform DC, the first base station device may add a second base station device. The first base station device may be called a master node (MN). Further, a cell group constituted by a master node may be referred to as a master cell group (MCG). The second base station device may be referred to as a secondary node (SN). Further, a cell group constituted by a secondary node may be referred to as a secondary cell group (SCG). Note that the master node and the secondary node may be configured within the same base station device.

Furthermore, when a DC is not configured, a cell group configured in a terminal device may be referred to as an MCG. Furthermore, when a DC is not set, the SpCell set in the terminal device may be a PCell. Furthermore, an NR without a DC configured may be called an NR standalone (NR SA).

Note that Multi-Radio Dual Connectivity (MR-DC) may be a technology that performs DC using E-UTRA for MCG and NR for SCG. Further, MR-DC may be a technique for performing DC using NR for MCG and E-UTRA for SCG. Furthermore, MR-DC may be a technology that performs DC using NR on both MCG and SCG. MR-DC may be a technology included in DC. As an example of MR-DC that uses E-UTRA for MCG and NR for SCG, there may be EN-DC (E-UTRA-NR Dual Connectivity) that uses EPC for the core network, and NGEN-DC that uses 5GC for the core network. There may be DC (NG-RAN E-UTRA-NR Dual Connectivity). Also, as an example of an MR-DC that uses NR for MCG and E-UTRA for SCG, there may be NE-DC (NR-E-UTRA Dual Connectivity) that uses 5GC for the core network. Further, as an example of MR-DC that uses NR for both MCG and SCG, there may be NR-DC (NR-NR Dual Connectivity) that uses 5GC for the core network.

Note that in the terminal device, one MAC entity may exist 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 MCG and one MAC entity for SCG. A MAC entity for MCG in a terminal device may always be established in the terminal device in all states (RRC idle state, RRC connected state, RRC inactive state, etc.). Further, the MAC entity for the SCG in the terminal device may be created by the terminal device when the SCG is configured in the terminal device. Further, the MAC entity for each cell group of the terminal device may be configured by the terminal device receiving RRC signaling from the base station device. When a MAC entity is associated with an MCG, SpCell may refer to PCell. Furthermore, when the MAC entity is associated with an SCG, SpCell may mean a primary SCG cell (Primary SCG Cell: PSCell). Also, if the MAC entity is not associated with a cell group, SpCell may mean PCell. PCell, PSCell, and SCell are serving cells. In EN-DC and NGEN-DC, the MAC entity for MCG may be an E-UTRA MAC entity, and the MAC entity for SCG may be an NR MAC entity. Further, in the 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. Further, in NR-DC, both the MAC entities for MCG and SCG may be NR MAC entities. Note that the fact that one MAC entity exists for each cell group may be translated into the fact that one MAC entity exists for each SpCell. Furthermore, one MAC entity for each cell group may be replaced with one MAC entity for each SpCell.

The terminal device may adjust the uplink transmission timing. For example, the terminal device may adjust the uplink transmission timing based on reception of a MAC TA command (Timing Advance command). A group of serving cells configured by RRC that uses the same timing reference cell and the same timing advance value for the cells to which uplinks are configured. It may be called a group (Timing Advance Group: TAG). Further, a TAG including SpCell of a MAC entity may be referred to as a primary timing advance group (PTAG). Further, TAGs other than the above-mentioned PTAG may be referred to as a secondary timing advance group (STAG). Note that one or more TAGs may be configured independently for each cell group, which will be described later. Further, as a TAG including SpCell, an additional TAG other than PTAG may be set in the terminal device. The additional TAG may be configured to be associated with a different physical cell identifier than the serving cell. Further, the additional TAG may be set in association with one of a plurality of TRPs set in a terminal device, which will be described later.

For example, by receiving a TA command (Timing advance command) for a certain TAG, the terminal device determines the uplink transmission timing for transmission of PUSCH, SRS, and/or PUCCH in some or all serving cells in that TAG. may be adjusted. The uplink transmission timing may be adjusted to be T_TA earlier than the timing of the beginning of the downlink frame with the same frame number. T_TA may be calculated based on N_TA and TA offset (N_TA,offset). N_TA may be set based on information included in the TA command. The TA offset (N_TA,offset) may be set based on the RRC parameter (n-TimingAdvanceOffset) set in the terminal device for each serving cell. Although N_TA,offset is set for each serving cell, N_TA,offset may take the same value in serving cells of the same TAG. Furthermore, for example, in the mTRP operation described later, an independent value of N_TA,offset may be taken for each TRP in a certain TAG. In this case, the uplink transmission timing may be different for each TRP in one TAG.

Additionally, in Dual Connectivity, cells in each cell group may belong to different TAGs. That is, the PTAG of the MCG and the PTAG of the SCG may be independent and different TAGs.

The RRC of the terminal device may set the value of a time alignment timer (timeAlignmentTimer) to the MAC in order to maintain uplink time alignment. The time adjustment timer may be used to control the time at which the MAC entity considers the uplink time of the serving cell belonging to the TAG associated with the time adjustment timer to be adjusted. The value of the time adjustment timer may be set from the base station device to the terminal device by RRC signaling.

The terminal device's MAC is determined based on the Timing Advance Command (TAC) MAC CE received and the N_TA of the TAG specified in the TAC MAC CE maintained. TAC may be applied to TAG. In addition, the MAC of the terminal device receives the Timing Advance Command (TAC) MAC CE, and based on the fact that the N_TA of the TAG specified by the TAC MAC CE is maintained, The time alignment timer (timeAlignmentTimer) associated with the specified TAG may be started, or restarted if already running.

The MAC of the terminal device may perform some or all of the following processes (A) to (G) when the time adjustment timer associated with the PTAG expires.
(A) Flush all HARQ buffers for all serving cells (in a cell group).
(B) If PUCCH is configured, notify RRC that it has released PUCCH for all serving cells.
(C) If SRS is configured, notify RRC that it has released SRS for all serving cells.
(D) Clear all Configured downlink assignments and Configured uplink grants.
(E) Clear all PUSCH for semi-persistent CSI reporting.
(F) All time adjustment timers, including STAG, are considered to have expired.
(G) Maintain N_TA of all TAGs.

When the time adjustment timer associated with a STAG expires, the MAC of the terminal device may perform some or all of the following processes (A) to (F) on all serving cells belonging to this STAG.
(A) Flush all HARQ buffers.
(B) If PUCCH is set, notify RRC that PUCCH has been released.
(C) If SRS is configured, notify RRC that SRS has been released.
(D) Clear all Configured downlink assignments and Configured uplink grants.
(E) Clear all PUSCH for semi-persistent CSI reporting.
(F) Maintain N_TA for this TAG.

Based on the expiration of the time adjustment timer associated with the PTAG, the terminal device performs uplink transmission in all serving cells except for random access preamble transmission in SpCell and MSGA transmission (in 2-step RACH). Not executed.

The multiple Transmit/Receive Point (also referred to as multi-TRP or mTRP) operation is explained.

In mTRP operation, a serving cell receives terminal equipment from multiple TRPs (Transmit/Receive Points) to provide better coverage, reliability, and/or data rate for PDSCH, PDCCH, PUSCH, and PUCCH. Good to be able to schedule.

There may be two different operation modes for the mTRP PDSCH transmission schedule. The two operation modes may be single-DCI and multi-DCI. Control of uplink and downlink operations for both modes may be performed at the PHY and MAC layers with settings configured by the RRC layer. In single-DCI mode, a terminal device may be scheduled for both TRPs by the same DCI. In multi-DCI mode, a terminal device may be scheduled for each TRP by an independent DCI.

Each TRP of mTRPs may be specified by TRP information. For example, the TRP information may be information for identifying one TRP among one or more TRPs. For example, the TRP information may be an index for identifying one TRP. For example, one TRP may be determined based on TRP information. For example, the TRP information may be information for identifying one or more TRPs. TRP information may be used to select one TRP. The TRP information may be a CORESET pool index. One CORESET pool index and one CORESET resource set identifier may be associated with one CORESET. The terminal device may transmit the PUSCH with the corresponding TRP based on the CORESET resource set identifier. TRP information may be associated with an index of a CORESET resource pool. For example, a first CORESET pool index may be associated with a first TRP, and a second CORESET pool index may be associated with a second TRP. TRP information may be associated with a TCI state pool (or a TCI state pool index). For example, a first TCI state pool (or pool index) may be associated with a first TRP, and a second TCI state pool (or pool index) may be associated with a second TRP.

There may be two different operation modes for the mTRP PDCCH transmission schedule. The two modes of operation may be PDCCH repetition and single frequency network (SFN) based PDCCH transmission. In both modes, the terminal device may receive each of the PDCCH transmissions carrying the same DCI from each TRP. In PDCCH repetition mode, the terminal device may receive two PDCCH transmissions carrying the same DCI from two linked search spaces, each associated with a different CORESET. In SFN-based PDCCH transmission mode, a terminal device can receive two PDCCH transmissions carrying the same DCI from a single search space/CORESET with different TCI states.

In the mTRP PUSCH repetition, the terminal equipment is associated with different spatial relations corresponding to the two TRPs by the indication by the configured uplink grant provided by the single DCI or RRC signaling. PUSCH transmission of the same content may be performed in the same beam direction.

In mTRP PUCCH repetition, the terminal device may perform PUCCH transmission of the same content in beam directions associated with different spatial relationships, corresponding to two TRPs.

In inter-cell mTRP operations, one or more TCI states in multi-DCI PDSCH transmission may be associated with a different PCI SSB than the serving cell's Physical Cell Identity (PCI). . Further, at most one TCI state associated with a PCI different from the serving cell may be activated at a time.

In the mTRP operation, uplink timing adjustment for each TRP may be performed. The terminal device may determine the uplink transmission timing based on at least some or all of the TA command, TA offset (Timing advance offset), and TRP information.

The timing advance (TA) may be determined based on at least the TA offset. The value of the TA offset may be provided by higher layer parameters (eg RRC layer or MAC layer parameters). One TA offset may be provided in one serving cell. Two TA offsets may be provided in one serving cell. If no upper layer parameters are provided, the terminal device may determine the value of the TA offset based on predefined rules. The terminal device may determine two TA offset values in one serving cell. Determining TA and adjusting uplink transmission timing may be synonymous.

When two TRPs are configured in one serving cell, one TA offset value may be applied to the uplink carrier of each TRP. When two TRPs are configured in one serving cell, two independent TA offset values may be applied to each TRP.

Let's explain the radio bearer. When a terminal device communicates with a base station device, a wireless connection may be established by establishing a radio bearer (RB) between the terminal device and the base station device. The radio bearer used for CP may be called a signaling radio bearer (SRB). Furthermore, the radio bearer used for UP may be called a data radio bearer (DRB). Each radio bearer may be assigned a radio bearer identity (ID). The radio bearer identifier for SRB may be called an SRB identity (SRB ID). The radio bearer identifier for DRB may be called a DRB identity (DRB ID). SRB0 to SRB2 may be defined as SRBs of E-UTRA, and SRBs other than these may be defined. SRB0 to SRB3 may be defined as SRBs of NR, and SRBs other than these may be defined. SRB0 may be an SRB for an RRC message that is transmitted and/or received using the CCCH of the logical channel. SRB1 may be an SRB for RRC signaling and for NAS signaling before the establishment of SRB2. RRC signaling transmitted and/or received using SRB1 may include piggybacked NAS signaling. The logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and/or received using SRB1. SRB2 may be an SRB for NAS signaling and for RRC signaling including logged measurement information. The logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and/or received using SRB2. Further, SRB2 may 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 in the terminal device. The logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and/or received using SRB3. Further, other SRBs may be prepared for other uses. DRB may be a radio bearer for user data. The logical channel DTCH may be used for RRC signaling that is transmitted and/or received using the DRB.

The radio bearer in the terminal device will be explained. Radio bearers may include RLC bearers. An RLC bearer may consist of one or two RLC entities and a logical channel. When there are two RLC entities in an RLC bearer, the RLC entity may be a TM RLC entity and/or a transmitting RLC entity and a receiving RLC entity in an RLC entity in unidirectional UM mode. SRB0 may consist of one RLC bearer. The RLC bearer of SRB0 may consist of a TM RLC entity and a logical channel. SRB0 may always be established in the terminal device in all states (RRC idle state, RRC connected state, RRC inactive state, etc.). One SRB1 may be established and/or configured 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 SRB1 RLC bearer may consist of an AM RLC entity and a logical channel. One SRB2 may be established and/or configured in a terminal device in an RRC connected state with AS security activated by RRC signaling received from the base station device. SRB2 may consist of one PDCP entity and one or more RLC bearers. The SRB2 RLC bearer may consist of an AM RLC entity and a logical channel. Note that the PDCP on the base station device side of SRB1 and SRB2 may be placed in the master node. In SRB3, when a secondary node in EN-DC, NGEN-DC, or NR-DC is added or changed, a terminal device in an RRC connection state with AS security activated connects to the base station. One may be established and/or configured in the terminal device by RRC signaling received from the device. SRB3 may be a direct SRB between the terminal device and the secondary node. SRB3 may consist of one PDCP entity and one or more RLC bearers. The SRB3 RLC bearer may consist of an AM RLC entity and a logical channel. PDCP on the base station device side of SRB3 may be placed in a secondary node. One or more DRBs may be established and/or configured in a terminal device in an RRC connected state with AS security activated by RRC signaling that the terminal device receives from the base station device. A DRB may consist of one PDCP entity and one or more RLC bearers. A DRB RLC bearer may consist of an AM or UM RLC entity and a logical channel.

Note that in MR-DC, a radio bearer in which PDCP is placed in the master node may be referred to as an MN terminated bearer. Further, in MR-DC, a radio bearer in which PDCP is placed in a secondary node may be referred to as an SN terminated bearer. Note that in MR-DC, a radio bearer in which the RLC bearer exists only in the MCG may be referred to as an MCG bearer. Furthermore, in MR-DC, a radio bearer in which the RLC bearer exists only in the SCG may be referred to as an SCG bearer. Furthermore, in the DC, a radio bearer in which the RLC bearer exists in both the MCG and the SCG may be referred to as a split bearer.

When MR-DC is configured in the terminal device, the bearer types of SRB1 and SRB2 established and/or configured in the terminal device may be MN-terminated MCG bearer and/or MN-terminated split bearer. Further, when MR-DC is configured in the terminal device, the bearer type of SRB3 established/and/or configured in the terminal device may be an SN termination SCG bearer. Further, when MR-DC is configured in the terminal device, the bearer type of the DRB established/and/or configured in the terminal device may be any one of all bearer types.

For an RLC bearer to be established and/or configured in a cell group configured with E-UTRA, the RLC entity to be established and/or configured may be E-UTRA RLC. Furthermore, for an RLC bearer to be established and/or configured in a cell group configured with NR, the RLC entity to be established and/or configured may be NR RLC. When EN-DC is configured in the terminal device, the PDCP entity established and/or configured for the MN terminating MCG bearer may be either E-UTRA PDCP or NR PDCP. In addition, when EN-DC is configured in the terminal device, other bearer types of radio bearers, namely MN-terminated split bearer, MN-terminated SCG bearer, SN-terminated MCG bearer, SN-terminated split bearer, and SN-terminated SCG bearer, are The PDCP established and/or configured may be NR PDCP. Additionally, if the terminal equipment is configured with NGEN-DC, NE-DC, or NR-DC, the PDCP entity established and/or configured for the radio bearer in all bearer types may be NR PDCP. .

Note that in NR, a DRB established and/or configured in a terminal device may be linked to one PDU session. One SDAP entity may be established and/or configured for one PDU session in a terminal device. Establishment and/or configuration of the SDAP entity, PDCP entity, RLC entity, and logical channel in the terminal device may be established and/or configured by RRC signaling that the terminal device receives from the base station device.

Note that regardless of whether MR-DC is configured, a network configuration in which the master node is eNB 102 and EPC 104 is the core network may be referred to as E-UTRA/EPC. Furthermore, a network configuration in which the master node is the eNB 102 and the 5GC 110 is the core network may be called E-UTRA/5GC. Furthermore, a network configuration in which the master node is gNB 108 and 5GC 110 is the core network may be called NR or NR/5GC. When MR-DC is not configured, the above-mentioned master node may refer to a base station device that communicates with a terminal device.

The flow of RRC signaling transmitted and received between the terminal device and the base station device will be explained. FIG. 4 is a diagram showing an example of a flow of procedures for various settings in RRC according to the present embodiment. FIG. 4 is an example of a flow when RRC signaling is sent from the base station device (eNB 102 and/or gNB 108) to the terminal device (UE 122).

In FIG. 4, the base station device creates an RRC message (step S400). The RRC message may be created in the base station device so that the base station device can distribute system information (SI) and paging messages. Further, the creation of the RRC message in the base station device may be performed so that the base station device can transmit RRC signaling to cause a specific terminal device to perform processing. The processing to be performed on a specific terminal device may include, for example, processing related to security, reconfiguration of an RRC connection, handover to a different RAT, suspension of an RRC connection, release of an RRC connection, and the like. RRC connection reconfiguration processing includes, for example, radio bearer control (establishment, change, release, etc.), cell group control (establishment, addition, change, release, etc.), measurement settings, handover, security key update, etc. may be included. Further, the creation of the RRC message in the base station device may be performed in response to RRC signaling transmitted from the terminal device. The response to RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC restart request, and the like. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be fields of RRC messages and/or information elements, or values of fields (including information elements). The structure of the RRC message may be described using a description method called ASN.1 (Abstract Syntax Notation One).

In FIG. 4, the base station device then transmits the created RRC signaling to the terminal device (step S402). Next, the terminal device performs processing such as setting, if necessary, according to the above-mentioned received RRC signaling (step S404). The terminal device that has performed the processing may transmit RRC signaling for response to the base station device (not shown).

RRC signaling is not limited to the above example and may be used for other purposes.

Note that in MR-DC, RRC on the master node side is used to transfer RRC signaling for settings on the SCG side (cell group settings, radio bearer settings, measurement settings, etc.) to and from the terminal device. good. For example, in EN-DC or NGEN-DC, NR RRC signaling may be included in the form of a container in E-UTRA RRC signaling transmitted and received between eNB 102 and UE 122. Further, in the NE-DC, E-UTRA RRC signaling may be included in the form of a container in the NR RRC signaling transmitted and received between the gNB 108 and the UE 122. RRC signaling for SCG side configuration may be transmitted and received between the master node and the secondary nodes.

Note that, not only when using MR-DC, NR RRC signaling may be included in E-UTRA RRC signaling transmitted from eNB 102 to UE 122, and NR RRC signaling transmitted from gNB 108 to UE 122. The signaling may include RRC signaling for E-UTRA.

An example of parameters included in a message regarding resetting an RRC connection will be explained. FIG. 7 is an example of an ASN.1 description representing fields and/or information elements related to cell group configuration included in a message related to reconfiguration of an RRC connection in NR in FIG. 4. Further, FIG. 8 is an example of an ASN.1 description representing fields and/or information elements related to cell group configuration included in a message related to reconfiguration of an RRC connection in E-UTRA in FIG. 4. In examples of ASN.1 in this embodiment, not limited to FIGS. 7 and 8, <omitted> and <omitted> are not part of the notation of ASN.1, and indicate that other information is omitted. shows. Note that information elements may be omitted even in places where there is no description of <omitted> or <omitted>. Note that in this embodiment, the example of ASN.1 does not correctly follow the ASN.1 notation method. In this embodiment, the example ASN.1 represents an example of the RRC signaling parameters in this embodiment, and other names and other representations may be used. Further, in the example of ASN.1, in order to avoid complicating the explanation, only an example related to main information closely related to this embodiment will be shown. Note that the parameters described in ASN.1 are sometimes referred to as information elements, without distinguishing them into fields, information elements, etc. Further, in this embodiment, fields, information elements, etc. described in ASN.1 and included in RRC signaling may be translated into information or parameters. Note that the message regarding RRC connection reconfiguration may be an RRC reconfiguration message in NR or an RRC connection reconfiguration message in E-UTRA.

In FIG. 7, the information element named CellGroupConfig may be an information element used for setting, changing, releasing, etc. a cell group of MCG or SCG in NR. The information element named CellGroupConfig may include the TCI information element described below. The information element named CellGroupConfig may be referred to as a cell group configuration information element or cell group configuration. Furthermore, when an information element named CellGroupConfig is used to configure a cell group of the SCG in NR, this information element named CellGroupConfig may be referred to as the configuration on the SCG side. An information element named SpCellConfig included in an information element named CellGroupConfig may be an information element used for configuring SpCell. The information element named SpCellConfig may be rephrased as SpCell configuration information element or SpCell configuration. The information element named DeactivatedSCG-Config-r17 included in the information element named SpCellConfig may be an information element set in SCG deactivation described later. The information element named DeactivatedSCG-Config-r17 can be rephrased as the setting for deactivating the SCG. The information element named DeactivatedSCG-Config-r17 indicates whether or not to perform BFD and/or RLM (described later) using PSCell on the terminal device when the SCG is deactivated, as indicated by bfd-and-RLM. A parameter may be included to indicate whether the The information element named spCellConfigDedicated, which is included in the information element named SpCellConfig, may be an information element indicating SpCell-specific settings set in this SpCellConfig. The information element named spCellConfigDedicated may be rephrased as SpCellConfigDedicated or SpCell dedicated configuration. Note that the information element named spCellConfigDedicated may include a parameter of a BWP identifier named first active downlink BWP identifier (firstActiveDownlinkBWP-Id), which will be described later.

Next, we will explain Radio Link Monitoring (RLM).

In the RRC connected state, the terminal device may execute RLM in the Active BWP described below or in a BWP designated as a BWP that performs wireless link monitoring. RLM may be performed based on a reference signal (eg, CRS in E-UTRA, SSB/CSI-RS in NR) and a signal quality threshold. The reference signal may include SSB. The signal quality threshold may be set by the network or a predefined threshold may be used. The SSB-based RLM may be performed based on the SSB associated with the initial DL BWP described below. An SSB-based RLM may be configured for an initial DL BWP and one or more DL BWPs containing SSBs associated with the initial DL BWP. For other DL BWPs, CSI-RS based RLM may be performed.

In RLM, a terminal device may declare a radio link failure (RLF) based on any of the following criteria (A) to (D) being met.
(A) The radio problem timer expires, which starts based on in-sync and out-of-sync notifications from the PHY. (B) While the radio problem timer is running. A timer that starts based on the triggering of a measurement report for a specific measurement identifier has expired. (C) A random access procedure has failed. (D) An RLC failure has been detected.

A terminal device that has declared RLF in the MCG may remain in the RRC connected state, select the most suitable cell and start the re-establishment procedure. Furthermore, if a DC is set, the terminal device that declared RLF may remain in the RRC connection state and notify the RLF to the network.

The terminal device may be configured with a reference signal used for RLM from the network through RRC signaling. A radio link monitoring configuration (RadioLinkMonitoringConfig) may be used for RRC signaling. A terminal device may perform RLM using one or more reference signals (referred to as RLM-RS) configured by radio link monitoring settings. Furthermore, if RLM-RS is not specified, the terminal device may perform RLM using a default reference signal. The wireless link monitoring settings may be set in the terminal device for each DL BWP. The wireless link monitoring configuration may be configured for the DL BWP of the PCell and/or the PSCell. The PHY of the terminal device may notify the upper layer (RRC layer) that the terminal device is in synchronization when the conditions for in-sync are satisfied. If the PHY of the terminal device satisfies the conditions for out-of-sync, it may notify the higher layer (RRC, etc.) of the out-of-sync.

The wireless link monitoring settings may include information indicating the purpose of monitoring and identifier information indicating a reference signal. For example, monitoring purposes may include monitoring wireless link failures, beam failures, or both. Further, for example, the identifier information indicating the reference signal may include information indicating the SSB-Index of the SSB of the cell. Further, for example, the identifier information indicating the reference signal may include information indicating an identifier linked to a channel state information reference signal (CSI-RS) set in the terminal device.

If the terminal equipment is not provided with RLM-RS and is provided with TCI state(s) for PDCCH reception, including one or more CSI-RSs, then the terminal equipment is provided with the following (A) ) to (B) in part or in full.
(A) If the activated TCI state for PDCCH reception includes only one reference signal, use the reference signal provided in the activated TCI state for radio link monitoring (B) PDCCH reception If the activated TCI state for contains two reference signals, expect one reference signal to have its QCL type set to type D; Use reference signals for wireless link monitoring

If a plurality of DL BWPs (described later) are configured in a certain serving cell, the terminal device may perform RLM using a reference signal corresponding to RLM-RS in the Active DL BWP (described later). In addition, if multiple downlink BWPs (described later) are configured in a certain serving cell, and RLM-RS is not provided to the Active DL BWP (described later), the terminal device will transmit the PDCCH using the CORESET of that Active DL BWP. RLM may be performed using reference signal(s) provided in an activated TCI state for reception. When the terminal device executes RLM, it may be said that the PHY of the terminal device measures radio link quality. Further, the PHY may notify an upper layer (RRC, etc.) of out-of-sync when the measured radio link quality becomes worse than a set threshold.

Next, BFD (beam failure detection) will be explained.

For BFD, the base station device may set a BFD reference signal (SSB or CSI-RS) to the terminal device. The BFD reference signal is also referred to as BFD-RS. The end device declares a beam failure when the number of beam failure instances notified from the end device's PHY to the upper layer (e.g. MAC) reaches a configured threshold before the configured timer expires. You may (declare) it.

For BFD in mTRP, the base station device may configure a BFD-RS set associated with TRP in the terminal device. The BFD-RS set may be set from the base station device to the terminal device according to the radio link monitoring settings. When multiple TRPs are configured in a terminal device, one BFD-RS set may be configured for each TRP. That is, when two TRPs are configured in the terminal device, two BFD-RS sets may be configured in the terminal device. Each of the BFD-RS sets may include an identifier (bfdRSSetId) for identifying the BFD-RS set and one or more BFD-RS settings. The terminal device determines the number of beam failure instances corresponding to the BFD-RS set associated with a certain TRP, which is notified from the PHY of the terminal device to a higher layer (e.g., MAC), before the configured timer expires. When a set threshold is reached, a beam failure for that TRP may be declared.

SSB-based BFD may be performed based on the SSB associated with the initial DL BWP. An SSB-based BFD may be configured for an initial DL BWP and one or more DL BWPs containing SSBs associated with the initial DL BWP. For other DL BWPs, CSI-RS-based BFD may be performed.

After a beam failure is detected in the PCell, the terminal device may trigger beam failure recovery (BFR) by starting a random access procedure in the PCell. The terminal device may select the optimal beam to perform BFR. If contention-based random access (CBRA) is used in the random access procedure for BFR, the terminal device may fail the beam at PCell in the MAC CE used for BFR (BFR MAC CE). You may include information indicating that you have done so. The terminal device may consider that the BFR for the PCell is completed based on the completion of the random access procedure.

In mTRP operation, after a beam failure for one TRP of the serving cell is detected, the terminal device may trigger BFR by starting the transmission of BFR MAC CE for this TRP. The terminal device may select an optimal beam for this TRP if it exists. The terminal device may include in the BFR MAC CE information indicating that the beam has failed for this TRP and information indicating whether the optimal beam for this TRP has been found. The terminal equipment determines that the BFR for this TRP is complete based on receiving a PDCCH indicating an uplink grant for new transmission for the HARQ process used to transmit the BFR MAC CE for this TRP. It may be considered.

In mTRP operation, after beam failure for both TRPs of a PCell is detected, the terminal device may trigger BFR by starting a random access procedure on the PCell. The terminal device may select the optimal beam for each beam-failed TRP, if one exists. The terminal device may include in the BFR MAC CE information indicating that a beam has failed for each TRP and information indicating whether an optimal beam for each TRP has been found. The terminal device may consider that the BFR for both TRPs of the PCell is completed based on the completion of the random access procedure.

At the MAC entity, beam failure recovery procedures may be configured by RRC for each serving cell. The beam failure recovery procedure specifies that when a beam failure is detected on one or more SSBs and/or CSI-RS of the serving cell, a new SSB or CSI is sent to the serving gNB (base station equipment communicating with the terminal equipment). -May be used to signal RS. Beam failure is detected by counting beam failure instance notifications notified from the lower layer (PHY layer) to the MAC entity. Furthermore, if the SCG is inactivated, the MAC entity may perform BFD in the PSCell using one or more reference signals (referred to as BFD-RS) configured by the radio link monitoring configuration. Furthermore, if BFD-RS is not specified, the terminal device may perform BFD using a default reference signal. Radio link monitoring settings may be set in the terminal device for each DL BWP. Radio link monitoring settings may be configured for DL BWP of PCell and/or PSCell. The MAC entity of the terminal device may perform some or all of the following procedures (A), (B), and (C) in each serving cell for beam failure detection.
(A) If a beam failure instance notification is received from the lower layer (PHY layer), start or restart the beam failure detection timer (beamFailureDetectionTimer) and add 1 to the beam failure counter (BFI_COUNTER) for this serving cell. If the value of BFI_COUNTER is greater than or equal to the set threshold (beamFailureInstanceMaxCount), perform (A-1) below.
(A-1) If the serving cell is an SCell, trigger beam failure recovery (BFR) for this serving cell; otherwise, perform (A-2) below.
(A-2) If the serving cell is a PSCell and the SCG is inactivated, perform (A-3) below; otherwise, start a random access procedure with the SpCell.
(A-3) If the SCG has not notified the upper layer of the beam failure of the PSCell since it was deactivated, or if the If the beam failure in the PSCell has not been notified to the upper layer (RRC layer), the beam failure in the PSCell is notified to the upper layer (RRC layer).
(B) If the beamFailureDetectionTimer for this serving cell has expired, or if beamFailureDetectionTimer, beamFailureInstanceMaxCount, and/or the reference signal for beam failure detection (BFD-RS) is set by an upper layer (RRC entity, etc.) Once changed, set BFI_COUNTER to 0 for this serving cell.
(C) If the serving cell is a SpCell and the random access procedure is completed successfully, set the BFI_COUNTER for this serving cell to 0 and stop the beam failure recovery timer (beamFailureRecoveryTimer) if it is configured and running. , the beam failure recovery procedure is considered successfully completed. Otherwise, if the serving cell is an SCell, a new uplink grant is required to transmit information for beam failure recovery of the SCell (e.g. information included in the BFR MAC CE of the SCell or the truncated BFR MAC CE of the SCell). If a PDCCH addressed to a C-RNTI indicating Cancel all Beam Failure Recovery (BFR) triggered for the serving cell.

The MAC entity performs (A) below if at least one beam failure recovery (BFR) has been triggered by the beam failure recovery procedure and has not been cancelled.
(A) If the UL-SCH resource can include the SCell BFR MAC CE and its subheader after considering the priority of the logical channel, include the SCell BFR MAC CE and its subheader. Otherwise, if the UL-SCH resource can include the SCell's truncated BFR MAC CE and its subheaders, considering the priority of the logical channel, the SCell's truncated BFR MAC CE and its Include subheaders. Otherwise, trigger a scheduling request for SCell beam failure recovery.

Here, beamFailureRecoveryTimer (beam failure recovery timer) will be explained. If a random access procedure is initiated for the SpCell's BFR and the beam failure recovery configuration (beamFailureRecoveryConfig) is set to Active UL BWP, the MAC entity may start the beamFailureRecoveryTimer. Additionally, if beamFailureRecoveryTimer is not running or configured, the terminal device may use contention-free Random Access (CFRA) for BFR. Also, if the beamFailureRecoveryTimer has expired or is not running, the terminal device may not use CFRA for BFR, but may instead use, for example, CBRA.

In each BWP in one serving cell, one or more reference signals (reference signal for detecting beam failure and/or radio link failure: BFD-RS described below) are provided for detecting beam failure and/or radio link failure. A plurality of BFD-RS sets may be provided to a terminal device as one set (BFD-RS set). The BFD-RS may be a periodic CSI-RS, an SSB, or another reference signal. The PHY of the terminal device may assess radio link quality based on the BFD-RS set. Additionally, the PHY may provide a notification to an upper layer (such as MAC) if the measured radio link quality becomes worse than a set threshold.

Cell activation and cell deactivation will be explained. In a terminal device that communicates with Dual Connectivity, a master cell group (MCG) and a secondary cell group (SCG) are configured by the above-mentioned message regarding reconfiguration of an RRC connection. Each cell group may include a special cell (SpCell) and zero or more other cells (secondary cells: SCell). MCG's SpCell is also called PCell. SpCell of SCG is also called PSCell.

Cell inactivation may not be applied to SpCell, but may be applied to SCell. Furthermore, cell inactivation may not be applied to PCell, but may be applied to PSCell. In this case, cell inactivation may be performed differently for SpCell and SCell.

Cell activation and deactivation may be handled by a MAC entity that exists for each cell group. The SCell configured in the terminal device may be activated and/or deactivated based on some or all of (A) to (C) below.
(A) Reception of MAC CE that activates/deactivates the SCell (B) Expiration of the SCell inactivity timer set for each SCell for which PUCCH is not set (C) For each SCell set in the terminal device Reception of RRC signaling including configured RRC parameters (sCellState)

Specifically, the MAC entity of the terminal device may perform the following processing AD for each SCell configured in the cell group.

(Processing AD)
If the RRC parameter (sCellState) set in the SCell is set to activated during SCell configuration, or if a MAC CE that activates the SCell is received, the MAC entity of the UE 122 performs processing (AD-1). I do. Otherwise, if a MAC CE that deactivates the SCell is received or the SCell deactivation timer expires in an activated SCell, the MAC entity of the UE 122 performs processing AD-2. If an uplink grant or downlink assignment is notified by the PDCCH of an activated SCell, or if an uplink grant or downlink assignment for an activated SCell is notified by the PDCCH of a certain serving cell, or When a MAC PDU is transmitted in a configured uplink grant or a MAC PDU is received in a configured downlink assignment, the MAC entity of UE 122 restarts the SCell inactivity timer associated with that SCell. If the SCell is deactivated, the MAC entity of the UE 122 performs processing AD-3.

(Processing AD-1)
In NR, if this SCell was inactivated before receiving the MAC CE that activates this SCell, or if the RRC parameter (sCellState) set for that SCell is set to activated during SCell configuration. If so, the MAC entity of UE 122 performs processing AD-1A or processing AD-1B.
Additionally, the MAC entity of the UE 122 starts or restarts the SCell inactivity timer associated with the SCell (if it has already been started).
If the Active DL BWP is not a Dormant BWP (described below), the MAC entity of the UE 122 performs some or all of (A) to (B) below.
(A) (Re)initialize all suspended configured uplink grants of grant type 1 associated with this SCell according to the stored configuration, if any.
(B) Trigger PHR.
If a MAC CE that activates an SCell is received, and the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) configured in RRC signaling for that SCell is set to a dormant (Dormant) BWP. If not, the MAC entity of UE 122 performs processing AD-1A. If a MAC CE that activates an SCell is received, and the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) configured in RRC signaling for that SCell is set to a dormant (Dormant) BWP. If so, the MAC entity of UE 122 performs processing AD-1B. Additionally, the MAC entity of the UE 122 implements some or all of (A) to (B) below.
(A) Activate the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) set in RRC signaling (B) Activate the BWP indicated by the first active uplink BWP identifier (firstActiveUplinkBWP-Id) set in RRC signaling Activate the BWP indicated by Id)

(Processing AD-1A)
The MAC entity of the UE 122 activates the SCell and implements some or all of (A) to (E) below.
(A) Transmit a sounding reference signal (SRS) with this SCell.
(B) Report the CSI for this SCell.
(C) Monitor the PDCCH of this SCell.
(D) Monitor the PDCCH for this SCell. (When scheduling for this SCell is done in another serving cell)
(E) If PUCCH is set, transmit PUCCH with this SCell.

(Processing AD-1B)
The UE 122's MAC entity stops this serving cell's BWP inactivity timer if it is running.

(Processing AD-2)
The MAC entity of UE 122 implements some or all of (A) to (F) below.
(A) Inactivate this SCell.
(B) Stop the SCell inactivity timer associated with this SCell.
(C) Inactivate all Active BWPs associated with this SCell.
(D) Clear all configured downlink assignments and/or all grant type 2 configured uplink grants associated with this SCell.
(E) Suspend all grant type 1 configured uplink grants associated with this SCell.
(F) Flush the HARQ buffer associated with this SCell.

(Processing AD-3)
The MAC entity of UE 122 implements some or all of (A) to (D) below.
(A) Do not send SRS with this SCell.
(B) Do not report CSI for this SCell.
(C) Do not transmit PUCCH, UL-SCH, and/or RACH on this SCell.
(D) Do not monitor the PDCCH of this SCell and/or the PDCCH for this SCell.

As described above, the SCell is activated or deactivated by the MAC entity performing processing AD.

Furthermore, when an SCell is added as described above, the initial state of the SCell (whether to activate or deactivate the SCell) may be set by RRC signaling.

Here, the SCell inactivity timer will be explained. For SCells for which PUCCH is not set, the value of the SCell inactivity timer (information regarding the time when the timer is considered to have expired) may be notified by RRC signaling. For example, if information indicating 40ms is notified as the value of the SCell inactivity timer through RRC signaling, in the above process AD, the timer is started or restarted and the timer is notified without stopping (here, 40ms). ) has elapsed, the timer is considered to have expired. Further, the SCell inactivation timer may be a timer named sCellDeactivationTimer.

Here, the bandwidth part (BWP) will be explained.

BWP may be part or all of the serving cell's band. Further, the BWP may be referred to as a carrier BWP. One or more BWPs may be configured in a terminal device. A certain BWP may be set based on information included in system information associated with a synchronization signal detected in the initial cell search. Further, a certain BWP may be a frequency bandwidth (initial downlink BWP: initial DL BWP) that is associated with a frequency for performing an initial cell search. Also, a certain BWP may be configured with RRC signaling (eg, Dedicated RRC signaling). Further, downlink BWP (DL BWP) and uplink BWP (UL BWP) may be set separately. Furthermore, one or more uplink BWPs may be associated with one or more downlink BWPs. Furthermore, the association between uplink BWP and downlink BWP may be a predetermined association, may be an association based on RRC signaling (e.g. Dedicated RRC signaling), or may be based on physical layer signaling (e.g. downlink The association may be based on downlink control information (DCI) notified via a control channel, or a combination thereof. Additionally, CORESET may be set in DL BWP.

A BWP may be composed of a group of consecutive physical radio blocks (PRBs: Physical Resource Blocks). Furthermore, parameters of the BWP (one or more BWPs) of each component carrier may be set for the terminal device in the connected state. The parameters of BWP for each component carrier include (A) cyclic prefix type, (B) subcarrier spacing, (C) frequency position of BWP (e.g., starting position or center frequency position on the low frequency side of BWP) ( For example, ARFCN may be used as the frequency position, or an offset from a specific subcarrier of the serving cell may be used. Also, the offset may be in units of subcarriers or in units of resource blocks. (Also, both ARFCN and offset may be set.), (D) BWP bandwidth (e.g. number of PRBs), (E) control signal resource configuration information, (F) SS block center frequency. Position (For example, ARFCN may be used as the frequency position, or an offset from a specific subcarrier of the serving cell may be used. Also, the unit of offset may be subcarrier unit, or resource block (Also, both ARFCN and offset may be set.) may be included in part or in full. Further, the resource configuration information of the control signal may be included in the BWP configuration of at least some or all of the PCell and/or PSCell.

A terminal device may perform transmission and reception using an Active BWP among one or more configured BWPs. One or more BWPs may be configured in one serving cell associated with a terminal device. At a certain time, at most one uplink BWP and/or at most one downlink BWP is configured for one serving cell associated with a terminal device. It may be set to be Active BWP. Downlink Active BWP is also referred to as Acitve DL BWP. Uplink Active BWP is also referred to as Active UL BWP. Furthermore, among the BWPs set in one or more BWPs in a terminal device, a BWP that is not an Active BWP may be referred to as an Inactive BWP.

Next, activation/inactivation of BWP will be explained. Activating a BWP may mean activating a BWP or activating an Inactive BWP. Furthermore, inactivation of BWP may mean inactivation of BWP or inactivation of Active BWP. BWP switching in the serving cell may be used to activate Inactive BWPs and deactivate Active BWPs.

BWP switching may be controlled by the MAC entity itself due to PDCCH indicating downlink allocation or uplink grant, BWP inactivity timer, RRC signaling, or initiation of random access procedure. Active BWP of the serving cell may be indicated by RRC or PDCCH.

By RRC signaling (RRC reconfiguration message, RRC connection reconfiguration message, etc.), the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) and/or the first active uplink BWP identifier (firstActiveUplinkBWP-Id) is (re) The MAC entity may perform the following (A) and/or (B) for the configured serving cell.
(A) If the serving cell is not a PSCell of a cell group in which the SCG described below is inactivated, the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) and/or the first active uplink BWP identifier (firstActiveUplinkBWP-Id) Let the downlink BWP and/or uplink BWP shown respectively be Active BWP.
(B) When the serving cell is a PSCell of a cell group in which the SCG described below is inactivated, the downlink BWP is switched to the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id).

Next, we will explain the BWP inactivity timer. The MAC entity performs the following (A) for each activated serving cell for which the BWP inactivity timer is set. Further, the BWP inactivity timer may be a timer named bwp-InactivityTimer.
(A) If the default downlink BWP identifier (defaultDownlinkBWP-Id) is set and the Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), or if the default downlink BWP identifier (defaultDownlinkBWP-Id) ) is not set, the Active DL BWP is not initialDownlinkBWP, and the Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), then the MAC entity performs the following (B) and (D).
(B) If the Active DL BWP receives a PDCCH addressed to C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant; A PDCCH addressed to C-RNTI or CS-RNTI is received, indicating a downlink assignment or uplink grant, or if a MAC PDU is sent with a configured uplink grant, or a configured downlink Once a MAC PDU is received in the assignment, the MAC entity performs the following (C).
(C) If the random access procedure associated with this serving cell is not running, or if the running random access procedure associated with this serving cell is successfully completed by reception of the PDCCH addressed to C-RNTI; (Successfully completed), start or restart the BWP inactivity timer associated with the Active DL BWP.
(D) If the BWP inactivity timer associated with the Active DL BWP expires, the MAC entity performs the following (E).
(E) If defaultDownlinkBWP-Id is set, perform BWP switching to the BWP indicated by this defaultDownlinkBWP-Id, otherwise perform BWP switching to initialDownlinkBWP.

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

In each activated serving cell where BWP is configured, the MAC entity performs the following actions if the BWP is activated (Active BWP) and the Active DL BWP in that serving cell is not a dormant BWP. Perform some or all of (A) to (H) of Processing BA.

(Processing BA)
(A) Transmit UL-SCH with that BWP.
(B) If the PRACH occasion is set, send RACH on that BWP.
(C) Monitor PDCCH with that BWP.
(D) If PUCCH is set, transmit PUCCH in that BWP.
(E) Report the CSI in that BWP.
(F) If SRS is configured, send SRS with that BWP.
(G) Receive DL-SCH on that BWP.
(H) (Re)initialize all suspended configured uplink grants of grant type 1 configured in that Active BWP according to the stored configuration, if any.

The MAC entity performs some or all of (A) to (I) below if the BWP is deactivated.
(A) Do not transmit UL-SCH on that BWP.
(B) Do not send RACH on that BWP.
(C) Do not monitor PDCCH on that BWP.
(D) Do not transmit PUCCH on that BWP.
(E) Not reporting CSI in that BWP.
(F) Do not send SRS with that BWP.
(G) DL-SCH is not received on that BWP.
(H) Clear all configured downlink assignments and/or all grant type 2 configured uplink grants configured in that BWP.
(I) Suspend all grant type 1 configured uplink grants of that Inactive BWP.

Next, SCG deactivation and SCG activation will be explained.

Inactivation of SCG may mean inactivating SCG. Furthermore, deactivating an SCG may mean deactivating a cell group in which a MAC entity is associated with the SCG and corresponds to the MAC entity. Further, inactivation of SCG may include inactivation of PSCell (SpCell of SCG) or inactivation of PSCell. Activating the SCG may mean activating the SCG. Furthermore, activation of an SCG may mean activating a cell group in which a MAC entity is associated with the SCG and corresponds to the MAC entity. Furthermore, activation of SCG may mean activation of PSCell (SpCell of SCG) or activation of PSCell.

In LTE and/or NR, the terminal device may determine that the SCG is to be inactivated based on some or all of (A) to (H) of the following process SD-1. Note that the signaling and control elements (A) to (F) of Process SD-1 below may be notified from the base station device to the terminal device via the SCG. In addition to or in place of that, the signaling and control elements of (A) to (F) of Processing SD-1 below are transmitted to the base station via a cell group other than the relevant SCG (MCG, SCG other than the relevant SCG, etc.). The notification may be sent from the device to the terminal device.
(Processing SD-1)
(A) Reception of RRC signaling instructing to deactivate SCG (B) Reception of MAC CE instructing to deactivate SCG (C) Reception of RRC signaling instructing to deactivate PSCell (D ) Reception of MAC CE instructing to deactivate PSCell (E) Reception of other RRC signaling (F) Reception of other MAC CE (G) Expiration of SCG inactivity timer (H) PSCell inactivity timer expiry of

The RRC signaling of (A), (C), and (E) of processing SD-1 may include, for example, a parameter called scg-State. Inclusion of scg-State in RRC signaling may indicate that SCG is inactivated. The fact that scg-State is not included in RRC signaling may indicate that SCG is activated. The RRC signaling including an instruction to activate the SCG may mean that the RRC signaling does not include an instruction to deactivate the SCG. Not including an instruction to inactivate the SCG in RRC signaling may mean that scg-State is not included in RRC signaling. Including an instruction to deactivate the SCG in RRC signaling may mean that a parameter called scg-State is included in RRC signaling. Furthermore, the parameter scg-State may be information that instructs inactivation of the SCG. Additionally, scg-State may be included in the RRC reconfiguration message or the RRC resume message. Further, the RRC signaling may be generated by the MN.

The terminal device that deactivates the SCG may perform part or all of the following processing SD-2 (A) to (I) in the SCG.
(Processing SD-2)
(A) The RRC entity considers the SCG to be inactivated.
(B) The RRC entity notifies the lower layer (MAC entity, etc.) that the SCG will be deactivated.
(C) If the RRC parameter bfd-and-RLM value is set to true, the RRC entity performs RLM on the SCG to be deactivated and the lower layers (such as the MAC entity and/or the PHY entity) Notify BFD to run.
(D) If the terminal device is in the RRC_CONNECTED state and said SCG was activated before receiving the signaling instructing to deactivate the SCG, the RRC entity sends an RRC reconfiguration message or an RRC connection. If the SRB3 is configured before receiving the reconfiguration message, and the SRB3 is not released, triggers the PDCP entity of the SRB3 to perform SDU discard and, in addition or alternatively, re-establishes the RLC entity of the SRB3.
(E)MAC entity deactivates all SCells.
(F) The MAC entity considers that all SCell inactivity timers associated with the activated SCell have expired.
(G) The MAC entity considers that all SCell inactivity timers associated with the dormant SCell have expired.
(H) The MAC entity does not start or restart the SCell inactivity timer associated with all SCells.

Based on process SD-2 (B) above, when the MAC entity of the terminal device is notified that the SCG will be deactivated from the upper layer (RRC entity, etc.), it deactivates all SCells of the said SCG. In addition to or in place of this, the above process SD-1 may be executed to inactivate the PSCell.

The terminal device may reset the MAC based on the SCG being deactivated. Upon MAC reset, the terminal device does not have to stop the beam failure detection timer and timeAlignmentTimer (if running) associated with the PSCell, if it is configured to perform BFD with a deactivated SCG. good. On a MAC reset, the terminal device resets all timers (including the beam failure detection timer and timeAlignmentTimer) associated with the PSCell (unless it is configured to perform BFD with the SCG being deactivated) case) There is no need to stop it.

In LTE and/or NR, if the SCG is inactivated, the terminal device performs some or all of the following processing SD-3 (A) to (I) in the PSCell (SpCell) of the SCG. It's fine.

(Processing SD-3)
(A) Do not send SRS on this PSCell.
(B) Do not report CSI for this PSCell.
(C) Do not transmit UL-SCH on this PSCell.
(D) Do not transmit PUCCH on this PSCell.
(E) Do not monitor PDCCH for this PSCell.
(F) Do not trigger random access on this PSCell.
(G) Do not monitor PDCCH on this PSCell.
(H) Perform beam failure detection (BFD) and/or radio link monitoring (RLM) with this PSCell.
(I) Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) that includes this PSCell.

In process SD-3 (H), the terminal device performs BFD and/or RLM in the deactivated SCG based on the RRC parameters (for example, bfd-and-RLM) notified from the base station device. You can decide whether or not. For example, if the value of the RRC parameter (bfd-and-RLM) is set to true, it may be assumed that the terminal device is required to perform RLM and/or BFD in the PSCell of the deactivated SCG. . For example, if the value of the RRC parameter (bfd-and-RLM) is set to false, it may be assumed that the terminal device is not required to perform RLM and/or BFD in the PSCell of the deactivated SCG. Furthermore, whether or not to perform RLM on the PSCell of the inactivated SCG and whether or not to perform BFD on the PSCell may be set independently. Furthermore, the value of the parameter being set to True may mean that RLM and BFD are set to be performed on the PSCell of the inactivated SCG, or the value of the parameter being set to false. Being set to may mean that RLM and BFD are not set to be performed on the PSCell of the inactivated SCG.

In LTE and/or NR, the terminal device may determine that the SCG is activated based on some or all of (A) to (F) of processing SA-1 below. Note that the signaling and control elements in (A) to (F) of processing SA-1 below are notified from the base station device to the terminal device via a cell group other than the relevant SCG (MCG, SCG other than the relevant SCG, etc.) may be done.
(Processing SA-1)
(A) Reception of RRC signaling instructing to activate SCG (B) Reception of MAC CE instructing to activate SCG (C) Reception of RRC signaling instructing to activate PSCell (D) Reception of RRC signaling instructing to activate PSCell Reception of MAC CE instructing activation (E) Reception of other RRC signaling (F) Reception of other MAC CE

The RRC signaling of (A), (C), and (E) of the above processing SA-1 may include a parameter called scg-State, for example. Inclusion of scg-State in RRC signaling may indicate that SCG is inactivated. The fact that scg-State is not included in RRC signaling may indicate that SCG is activated. The RRC signaling including an instruction to activate the SCG may mean that the RRC signaling does not include an instruction to deactivate the SCG. Not including an instruction to inactivate the SCG in RRC signaling may mean that scg-State is not included in RRC signaling. Including an instruction to deactivate the SCG in RRC signaling may mean that a parameter called scg-State is included in RRC signaling. Furthermore, the parameter scg-State may be information that instructs inactivation of the SCG. Additionally, scg-State may be included in the RRC reconfiguration message or the RRC resume message. Further, the RRC signaling may be generated by the MN.

The terminal device that activates the SCG may execute part or all of the following processing SA-2 (A) to (D) in the SCG.
(Processing SA-2)
(A) The RRC entity considers the SCG to be activated.
(B) If the SCG has been deactivated before receiving the signaling instructing to activate the SCG, the RRC entity notifies the lower layer (such as the MAC entity) that the SCG will be activated. .
(C) Processing AD-1 is performed to activate the SCell specified by RRC signaling.
(D) When SCG activation is performed based on RRC signaling, if this RRC signaling includes parameters related to random access to the PSCell (SpCell), the random access procedure is performed in this PSCell based on the notified parameters. Start.

The MAC entity of the terminal device executes process SA-3 when an upper layer (RRC entity, etc.) instructs the MAC entity to activate the SCG based on process SA-2 (B) above. You can activate the SCG by

In LTE and/or NR, if an SCG is activated, the terminal device performs normal processing including some or all of the following processing SA-3 (A) to (F) in the PSCell (SpCell) of that SCG. May conduct SCG operations.

(Processing SA-3)
(A) Send SRS on this PSCell.
(B) Report the CSI for this PSCell.
(C) Monitor PDCCH on this PSCell.
(D) Transmit PUCCH on this PSCell.
(E) If random access is triggered on this PSCell, execute random access.
(F) Initialize the parameter Bj of each logical channel associated with the SCG to 0.

Next, the SCG failure information procedure will be explained.

This procedure may be used to notify the E-UTRAN or NR master node about the SCG failure experienced by the terminal.

The terminal equipment RRC entity initiates this procedure to report an SCG failure when MCG or SCG transmission is not suspended and any of the following conditions (A) to (E) are met: You may do so.
(A) Detected SCG radio link failure (B) Detected beam failure in PSCell while SCG was deactivated (C) Detected SCG configuration failure with synchronization (D) SCG configuration Failure detected (E) A failure of the SRB3 integrity check was notified from the SCG lower layer.

The RRC entity of the terminal device that initiates this procedure performs some or all of the following (A) to (E).
(A) If this procedure was not initiated based on detecting a beam failure in a PSCell while the SCG was deactivated, suspend SCG transmission for all SRBs and DRBs. )do.
(B) If this procedure was not initiated based on detecting a beam failure in a PSCell while the SCG was deactivated, reset the SCG MAC.
(C) If timer T304 in this SCG is running, stop it.
(D) If conditional reconfiguration for changing PSCell is set, stop this evaluation.
(E) Generate content to be included in the SCG failure information (SCGFailureInformation) message, and submit this message to the lower layer in order to transmit it.

The lower layer of RRC of the terminal device may transmit the above SCG failure information message to the base station device. The SCG failure information message may include the type of SCG failure and/or the measurement result.

Based on the above description, various embodiments will be described. Note that each of the above-mentioned processes may be applied to the processes omitted in the following description.

FIG. 5 is a block diagram showing the configuration of the terminal device (UE 122) in this embodiment. Note that in order to avoid complicating the explanation, FIG. 5 shows only the main components closely related to this embodiment.

The UE 122 shown in FIG. 5 includes a receiving unit 500 that receives control information (DCI, MAC control element, RRC signaling, etc.) from a base station device, a processing unit 502 that performs processing according to parameters included in the received control information, and a base station device. It includes a transmitter 504 that transmits control information (UCI, MAC control element, RRC signaling, etc.) to the station device. This base station device may be eNB102 or gNB108. Further, the processing unit 502 may include some or all of the functions of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 502 includes a physical layer processing unit (PHY processing unit), a MAC layer processing unit (MAC processing unit), an RLC layer processing unit (RLC processing unit), a PDCP layer processing unit (PDCP processing unit), and an SDAP processing unit. (SDAP processing section), RRC layer processing section (RRC processing section), and NAS layer processing section (NAS processing section).

FIG. 6 is a block diagram showing the configuration of the base station device in this embodiment. Note that in order to avoid complicating the explanation, FIG. 6 shows only the main components closely related to this embodiment. This base station device may be eNB102 or gNB108.

The base station device shown in FIG. , a processing unit 602 that causes the processing unit 502 of the UE 122 to perform processing, and a receiving unit 604 that receives control information (UCI, RRC signaling, etc.) from the UE 122. Further, the processing unit 602 may include some or all of the functions of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing section 602 includes some or all of the physical layer processing section, MAC layer processing section, RLC layer processing section, PDCP layer processing section, SDAP processing section, RRC layer processing section, and NAS layer processing section. It's fine.

An example of the processing of the terminal device in this embodiment will be explained using FIG. 9.

FIG. 9 is a diagram showing an example of processing of the terminal device in this embodiment. The processing unit 502 of the UE 122 determines whether the SCG is activated (step S900). The determination may be made based on process SA-1. The processing unit 502 of the UE 122 performs an operation based on the determination (step S902).

An example of the operation of the UE 122 in step S902 will be described. The processing unit 502 of the UE 122 determines whether a plurality of BFD-RS sets are configured in the PSCell as the MAC entity processing in step S902. When the processing unit 502 of the UE 122 determines that a plurality of BFD-RS sets are configured in the PSCell, the processing unit 502 may execute the following process MM-1 as the process of the MAC entity. Further, when the processing unit 502 of the UE 122 determines that a plurality of BFD-RS sets are not configured in the PSCell, the processing unit 502 may execute the following process MS-1 as the process of the MAC entity. Note that the determination as to whether a plurality of BFD-RS sets are configured in a PSCell may be replaced with the determination as to whether two BFD-RS sets are configured in a PSCell.

(Processing MM-1)
The MAC entity determines whether the value of each BFI_COUNTER corresponding to each BFD-RS set of PSCell of the SCG to be activated is greater than or equal to the set threshold. The MAC entity also determines whether the timer (timeAlignmentTimer) associated with the PTAG of the SCG to be activated is running. The MAC entity determines that the respective BFI_COUNTER values corresponding to each BFD-RS set of PSCells of the SCG to be activated are all greater than or equal to the configured threshold, or Based on the determination that the timer is not running, the upper layer (RRC entity) may be notified that a random access procedure is required for SCG activation. The MAC entity determines that any of the BFI_COUNTER values corresponding to each BFD-RS set of PSCells of the SCG to be activated is less than the configured threshold, and Based on the determination that the timer is running, the SCG may be activated directly without notifying the upper layer (RRC entity) that a random access procedure is required for activation of the SCG. good.

(Processing MS-1)
The MAC entity determines whether the value of BFI_COUNTER corresponding to the PSCell of the SCG to be activated is greater than or equal to the set threshold. The MAC entity also determines whether the timer (timeAlignmentTimer) associated with the PTAG of the SCG to be activated is running. The MAC entity determines that the value of BFI_COUNTER corresponding to the PSCell of the SCG to be activated is greater than or equal to the configured threshold, or that the timer associated with the PTAG of the SCG to be activated is not running. Based on this, the upper layer (RRC entity) may be notified that a random access procedure is required for SCG activation. The MAC entity determines that the value of BFI_COUNTER corresponding to the PSCell of the SCG to be activated is less than the configured threshold, and that the timer associated with the PTAG of the SCG to be activated is running. Based on this, the SCG may be activated directly, without informing the upper layer (RRC entity) that a random access procedure is required for the activation of the SCG.

Another example of the operation of the UE 122 in step S902 will be described. The processing unit 502 of the UE 122 determines whether a plurality of BFD-RS sets are configured in the PSCell as the MAC entity processing in step S902. When the processing unit 502 of the UE 122 determines that a plurality of BFD-RS sets are configured in the PSCell, the processing unit 502 may execute the following process MM-2 as the process of the MAC entity. Further, when the processing unit 502 of the UE 122 determines that multiple BFD-RS sets are not configured in the PSCell, the processing unit 502 may execute the above process MS-1 as the process of the MAC entity. Note that the determination as to whether a plurality of BFD-RS sets are configured in a PSCell may be replaced with the determination as to whether two BFD-RS sets are configured in a PSCell.

(Processing MM-2)
The MAC entity determines whether the value of each BFI_COUNTER corresponding to each BFD-RS set of the PSCell of the SCG to be activated is greater than or equal to the set threshold. The MAC entity also determines whether timers (timeAlignmentTimer) respectively associated with one or more timing advance groups (TAGs) corresponding to the PSCell of the SCG to be activated are running. The MAC entity determines that the respective BFI_COUNTER values corresponding to each BFD-RS set of PSCells in the SCG to be activated are all greater than or equal to the configured threshold, or The upper layer ( RRC entity). The MAC entity determines that any of the BFI_COUNTER values corresponding to each BFD-RS set of PSCells in the SCG to be activated is less than the configured threshold, and The SCG may be activated directly based on determining that any of the timers respectively associated with the corresponding one or more timing advance groups (TAGs) are running; There is no need to notify the upper layer (RRC entity) that a random access procedure is required.

Another example of the operation of the UE 122 in step S902 will be explained. The processing unit 502 of the UE 122 determines whether a plurality of BFD-RS sets are configured in the PSCell as the MAC entity processing in step S902. When the processing unit 502 of the UE 122 determines that a plurality of BFD-RS sets are configured in the PSCell, the processing unit 502 may execute the following process MM-3 as the process of the MAC entity. Further, when the processing unit 502 of the UE 122 determines that multiple BFD-RS sets are not configured in the PSCell, the processing unit 502 may execute the above process MS-1 as the process of the MAC entity. Note that the determination as to whether a plurality of BFD-RS sets are configured in a PSCell may be replaced with the determination as to whether two BFD-RS sets are configured in a PSCell.

(Processing MM-3)
The MAC entity determines whether the value of each BFI_COUNTER corresponding to each BFD-RS set of the PSCell of the SCG to be activated is greater than or equal to the set threshold. The MAC entity also determines whether the timer (timeAlignmentTimer) associated with the PTAG of the SCG to be activated is running. The MAC entity determines that either the value of each BFI_COUNTER corresponding to each BFD-RS set of the PSCell of the SCG to be activated is greater than or equal to the configured threshold, or Based on determining that the associated timer is not running, the upper layer (RRC entity) may be notified that a random access procedure is required for activation of the SCG. In addition to the need for a random access procedure to activate the SCG, the MAC entity also determines in which TRP BFD is detected (is the BFI_COUNTER value greater than or equal to the configured threshold)? /Or information indicating which TRP requires a random access procedure may be notified to the upper layer (RRC entity). The MAC entity determines that all of the BFI_COUNTER values corresponding to each BFD-RS set of PSCells in the SCG to be activated are less than the configured threshold, and The SCG may be activated directly based on a determination that any of the timers associated with one or more timing advance groups (TAGs) are running, whereupon a random access procedure is used to activate the SCG. There is no need to notify the upper layer (RRC entity) of the necessity. The information may be the above-mentioned TRP information. Furthermore, the information may be an identifier that identifies a BFD-RS set. Furthermore, the information may be an identifier that identifies the TRP.

Another example of the operation of the UE 122 in step S902 will be explained. The processing unit 502 of the UE 122 determines whether a plurality of BFD-RS sets are configured in the PSCell as the MAC entity processing in step S902. When the processing unit 502 of the UE 122 determines that a plurality of BFD-RS sets are configured in the PSCell, the processing unit 502 may execute the following process MM-4 as the process of the MAC entity. Further, when the processing unit 502 of the UE 122 determines that multiple BFD-RS sets are not configured in the PSCell, the processing unit 502 may execute the above process MS-1 as the process of the MAC entity. Note that the determination as to whether a plurality of BFD-RS sets are configured in a PSCell may be replaced with the determination as to whether two BFD-RS sets are configured in a PSCell.

(Processing MM-4)
The MAC entity determines whether the value of each BFI_COUNTER corresponding to each BFD-RS set of the PSCell of the SCG to be activated is greater than or equal to the set threshold. The MAC entity also determines whether a timer (timeAlignmentTimer) associated with one or more timing advance groups (TAGs) corresponding to the PSCell of the SCG to be activated is running. The MAC entity determines that either the value of each BFI_COUNTER corresponding to each BFD-RS set of the PSCell of the SCG to be activated is greater than or equal to the configured threshold, or Based on determining that all the timers associated with the corresponding one or more timing advance groups (TAGs) are not running, the upper layer ( RRC entity). In addition to the need for a random access procedure to activate the SCG, the MAC entity also determines in which TRP BFD is detected (is the BFI_COUNTER value greater than or equal to the configured threshold)? /Or information indicating which TRP requires a random access procedure may be notified to the upper layer (RRC entity). The MAC entity determines that all of the BFI_COUNTER values corresponding to each BFD-RS set of PSCells in the SCG to be activated are less than the configured threshold, and The SCG may be activated directly based on a determination that any of the timers associated with one or more timing advance groups (TAGs) are running, whereupon a random access procedure is used to activate the SCG. There is no need to notify the upper layer (RRC entity) of the necessity. The information may be the above-mentioned TRP information. Furthermore, the information may be an identifier that identifies a BFD-RS set. Furthermore, the information may be an identifier that identifies the TRP.

In addition, the execution of the processing MM-1, the processing MM-2, the processing MM-3, and the processing MM-4 includes determining that multiple BFD-RS sets are set in the PSCell. This may be done based on specific parameters being set. The specified parameters suggest that in a deactivated SCG, multiple BFD-RS sets are considered when determining whether a random access procedure is required for activation of the SCG. May be a parameter. The specific parameters may be notified to the terminal device through RRC signaling from the base station device. Further, the specific parameter may be indicated by the RRC parameter bfd-and-RLM. For example, the value of bfd-and-RLM is not a binary value of true/false, but the value of bfd-and-RLM is a ternary value of true/false/true (considering multiple BFD-RS sets). It's okay. In this case, the terminal device may consider that a specific parameter is set when the value of bfd-and-RLM is true (taking into account multiple BFD-RS sets). The values of bfd-and-RLM above are examples, and include information related to determining whether or not to execute the processing MM-1, the processing MM-2, and the processing MM-3. It's fine if you can. Further, the above bfd-and-RLM may be included in the RRC message as a different parameter from the conventional (binary) bfd-and-RLM.

Furthermore, in the processing MM-1, the processing MM-2, the processing MM-3, and the processing MM-4, the RRC entity of the terminal device requires a random access procedure to activate the SCG. may notify the MAC entity to start a random access procedure in the SpCell of the SCG based on the notification from the MAC entity.

In addition, in the processing MM-1, the processing MM-2, the processing MM-3, and the processing MM-4, when the SCG is directly activated, the MAC entity of the terminal device, for example, When there are valid PUCCH resources, PUCCH transmission may be performed without performing random access procedures.

In addition, in the processing MM-2 and the processing MM-4, it is determined that all timers associated with one or more timing advance groups (TAG) corresponding to the PSCell of the SCG to be activated are not running. Based on this, the upper layer (RRC entity) is notified that a random access procedure is required for SCG activation. Based on the determination that any or all of the timers associated with one or more timing advance groups (TAGs) are not running, the upper layer ( RRC entity).

Furthermore, in the above description, the BWP that measures the radio link quality may be the Active DL BWP in the activated SCG PSCell. The BWP for measuring the radio link quality may be a BWP used by the PHY 300 of the UE 122 to measure the radio link quality in the PSCell of the deactivated SCG. In addition, the radio link quality may be measured for beam failure detection (BFD), radio link monitoring (RLM), or other measurements ( measurement).

Furthermore, in the above description, once a timer (beam failure detection timer, etc.) is started, it runs until it is stopped or expires. A timer may be considered not running when it expires. A timer is always started (if the timer is stopped) or restarted (if the timer is running) from its initial value. The period from when the timer is started or restarted to when it expires is not updated until the timer is stopped or expires. If the MAC entity sets the timer expiration period after starting or restarting to zero, then the timer may expire as soon as it starts, unless other conditions are specified.

Furthermore, the radio bearer in the above description may be a DRB, an SRB, or a DRB and an SRB, unless otherwise specified.

Furthermore, in the above description, expressions such as "link to", "corresponding to", and "associate with" may be used interchangeably.

Furthermore, in the above description, expressions such as "A has been determined", "A has been set", and "A is included" may be used interchangeably.

In the above description, "transitioning from X to Y" may be rephrased as "transitioning from X to Y." Furthermore, in the above description, "transitioning" may be rephrased as "determining transition."

Further, in the examples of each process or the example of the flow of each process in the above description, some or all of the steps may not be executed. Further, in the example of each process or the example of the flow of each process in the above description, the order of steps may be different. Further, in the example of each process or the example of the flow of each process in the above description, some or all of the processes in each step may not be executed.

Note that in the above description, "A may be replaced with B" may include the meaning of replacing A with B, as well as replacing B with A. Furthermore, in the above description, when "C may be D" and "C may be E" are stated, "D may be E" may also be included. Furthermore, in the above description, when "F may be G" and "G may be H" are stated, "F may be H" may also be included.

The program that runs on the device related to this embodiment may be a program that controls a Central Processing Unit (CPU) or the like to make the computer function so as to realize the functions of this embodiment. Programs or information handled by programs are temporarily read into volatile memory such as Random Access Memory (RAM) during processing, or stored in non-volatile memory such as flash memory or Hard Disk Drive (HDD), and are stored as needed. The data is read, modified, and written by the CPU accordingly.

Note that a part of the apparatus in the embodiment described above may be realized by a computer. In that case, the program for realizing this control function may be realized by recording it on a computer-readable recording medium and causing the computer system to read and execute the program recorded on this recording medium. . The "computer system" herein refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices. Furthermore, the "computer-readable recording medium" may be any of semiconductor recording media, optical recording media, magnetic recording media, and the like.

Furthermore, a "computer-readable recording medium" refers to a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In that case, it may also include something that retains a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client. Further, the above-mentioned program may be one for realizing a part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system. .

Additionally, each functional block or feature of the device used in the embodiments described above may be implemented or executed in an electrical circuit, typically an integrated circuit or multiple integrated circuits. An electrical circuit designed to perform the functions described herein may be a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general purpose processor may be a microprocessor, or in the alternative, the processor may be a conventional processor, controller, microcontroller, or state machine. The general-purpose processor or each of the circuits described above may be configured with a digital circuit or an analog circuit. Further, if an integrated circuit technology that replaces the current integrated circuit emerges due to advances in semiconductor technology, it is also possible to use an integrated circuit based on this technology.

Note that this embodiment is not limited to the above-described embodiment. Although an example of the device has been described in the embodiment, the present embodiment is not limited to this, and can be applied to stationary or non-movable electronic equipment installed indoors or outdoors, such as AV equipment, kitchen equipment, etc. It can be applied to terminal devices or communication devices such as cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household equipment.

Although this embodiment has been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and may include design changes without departing from the gist of this embodiment. Further, this embodiment can be modified in various ways within the scope shown in the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments also fall within the technical scope of this embodiment. include. Also included are configurations in which the elements described in the above embodiments are replaced with each other and have similar effects.

One embodiment of the present invention is used in, for example, a communication system, a communication device (e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (e.g., a communication chip), a program, or the like. be able to.

100 E-UTRA
102eNB
104EPC
106NR
108 gNB
110 5GC
112, 114, 116, 118, 120, 124 interface
122 U.E.
200, 300 PHY
202, 302 MAC
204, 304 RLC
206, 306 PDCP
208, 308 RRC
310 SDAP
210, 312 NAS
500, 604 Receiving section
502, 602 processing section
504, 600 transmitter

Claims (3)

1. A terminal device that communicates with a base station device,
   PHY processing section,
   a MAC processing unit that performs MAC layer processing;
   RRC processing section,
   a receiving unit that receives signaling from the base station device,
   The RRC processing unit is
   Notifying a MAC processing unit that the SCG is to be activated based on receiving the signaling indicating that the SCG is to be activated;
   The MAC processing unit includes:
   When the RRC processing unit notifies that the SCG will be activated,
   Determining whether or not multiple BFD-RS sets are set for the PSCell of the SCG, with one or more reference signals for beam failure detection as one set (BFD-RS set),
   When it is determined that multiple BFD-RS sets are configured for the PSCell,
   Determine whether the value of the counter associated with each of the BFD-RS sets set for the PSCell is greater than or equal to a threshold, and determine whether the BFD-RS set set for the PSCell Notifying the RRC processing unit that it is necessary to execute a random access procedure in order to activate the SCG based on determining that the values of the counters linked to each of the are all equal to or higher than the threshold;
   The PHY processing section is
   Notifying the MAC processing unit of a beam failure instance for each set of BFD-RS;
   The counter is prepared for each BFD-RS set of the PSCell in which the BFD-RS set is configured, and is used to count beam failure instances notified from the PHY processing unit.
2. A method applied to a terminal device communicating with a base station device, the method comprising:
   receiving signaling from the base station device;
   As RRC layer processing,
   Notifying a MAC layer to activate a secondary cell group (SCG) based on receiving the signaling indicating to activate the SCG;
   As MAC layer processing,
   When it is notified from the RRC layer that the SCG will be activated,
   A step of determining whether a plurality of BFD-RS sets are set for the PSCell of the SCG, with one or more reference signals for beam failure detection as one set (BFD-RS set). and,
   When it is determined that multiple BFD-RS sets are configured for the PSCell,
   determining whether a value of a counter associated with each of the BFD-RS sets set for the PSCell is equal to or greater than a threshold;
   Executing a random access procedure to activate the SCG based on determining that the values of the counters associated with each of the BFD-RS sets set for the PSCell are all equal to or higher than a threshold value. notifying the RRC layer that the
   As PHY layer processing,
   and notifying a MAC layer of a beam failure instance for each set of BFD-RS,
   The counter is provided for each BFD-RS set of the PSCell in which the BFD-RS set is configured, and is used to count beam failure instances notified from the PHY layer.
3. An integrated circuit implemented in a terminal device that communicates with a base station device,
   a function of receiving signaling from the base station device;
   As RRC layer processing,
   A function of notifying a MAC layer to activate a secondary cell group (SCG) based on receiving the signaling indicating that the SCG is to be activated;
   As MAC layer processing,
   When it is notified from the RRC layer that the SCG will be activated,
   A function to determine whether multiple BFD-RS sets are set for the PSCell of the SCG, with one or more reference signals for beam failure detection as one set (BFD-RS set). and,
   When it is determined that multiple BFD-RS sets are configured for the PSCell,
   a function of determining whether a value of a counter associated with each of the BFD-RS sets set for the PSCell is equal to or greater than a threshold;
   Executing a random access procedure to activate the SCG based on determining that the values of the counters associated with each of the BFD-RS sets set for the PSCell are all equal to or higher than a threshold value. A function to notify the RRC layer that
   As PHY layer processing,
   causing the terminal device to exhibit a function of notifying the MAC layer of a beam failure instance for each set of BFD-RS,
   The counter is provided for each BFD-RS set of the PSCell in which the BFD-RS set is configured, and is used to count beam failure instances notified from the PHY layer.

Images