WO2022210285A1 - Équipement terminal, procédé et circuit intégré - Google Patents

Équipement terminal, procédé et circuit intégré Download PDF

Info

Publication number
WO2022210285A1
WO2022210285A1 PCT/JP2022/014082 JP2022014082W WO2022210285A1 WO 2022210285 A1 WO2022210285 A1 WO 2022210285A1 JP 2022014082 W JP2022014082 W JP 2022014082W WO 2022210285 A1 WO2022210285 A1 WO 2022210285A1
Authority
WO
WIPO (PCT)
Prior art keywords
rrc
terminal device
bwp
scg
mac
Prior art date
Application number
PCT/JP2022/014082
Other languages
English (en)
Japanese (ja)
Inventor
秀和 坪井
昇平 山田
貴子 堀
恭輔 井上
Original Assignee
シャープ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by シャープ株式会社 filed Critical シャープ株式会社
Priority to JP2023511134A priority Critical patent/JPWO2022210285A1/ja
Publication of WO2022210285A1 publication Critical patent/WO2022210285A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/32—Hierarchical cell structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA

Definitions

  • the present invention relates to terminal devices, methods and integrated circuits.
  • This application claims priority to Japanese Patent Application No. 2021-62888 filed in Japan on April 1, 2021, the contents of which are incorporated herein.
  • 3GPP 3rd Generation Partnership Project
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • RAT radio access technology
  • 3GPP 3GPP is still conducting technical studies and establishing standards for extension technologies for E-UTRA.
  • E-UTRA is also called Long Term Evolution (LTE: registered trademark), and extended technologies are sometimes called LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • NR New Radio, or NR Radio access
  • RAT Radio Access Technology
  • 3GPP TS 38.300 v16.2.0 NR;NR and NG-RAN Overall description; Stage 2" pp10-134 3GPP TS 36.300 v16.2.0,”Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2" pp19-361
  • a dual connectivity (also called multi-connectivity) technology in which one or more base station devices and terminal devices communicate using multiple cell groups.
  • a terminal device in order to perform communication in each cell group, a terminal device needs to monitor whether there is a message addressed to itself in each cell group.
  • a terminal device needs to constantly monitor a plurality of cell groups so that communication can be performed with low delay when large-capacity data communication occurs, and there is a problem of consuming a lot of power. Therefore, a technique for performing or stopping monitoring of some cell groups at low frequency (cell group deactivation technique) is being studied.
  • the terminal equipment In the inactive state of the cell group, the terminal equipment needs to perform the processing necessary to promptly communicate when the cell group becomes active.
  • One aspect of the present invention has been made in view of the above circumstances, and one of the objects thereof is to provide a terminal device, a method, and an integrated circuit capable of efficiently performing communication control.
  • one aspect of the present invention takes the following measures. That is, one aspect of the present invention is a terminal device in which a master cell group and a secondary cell group are configured, comprising a MAC entity, wherein the MAC entity is based on the secondary cell group being deactivated, Abort a running random access procedure.
  • one aspect of the present invention is a method applied to a terminal device in which a master cell group and a secondary cell group are configured, wherein a MAC entity executes aborting the random access procedure in.
  • one aspect of the present invention is an integrated circuit implemented in a terminal device in which a master cell group and a secondary cell group are configured, wherein random The terminal device is caused to exhibit the function of aborting the access procedure.
  • the terminal device, method, and integrated circuit can realize efficient communication control processing.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the invention;
  • FIG. 3 is a diagram of an example of NR protocol configuration according to an embodiment of the present invention;
  • the block diagram which shows the structure of the terminal device in embodiment of this invention. 1 is a block diagram showing the configuration of a base station apparatus according to an embodiment of the present invention;
  • ASN.1 description included in a message regarding RRC connection reconfiguration in E-UTRA according to an embodiment of the present invention.
  • LTE (and LTE-A, LTE-A Pro) and NR may be defined as different Radio Access Technologies (RAT).
  • RAT Radio Access Technologies
  • NR may also be defined as a technology included in LTE.
  • LTE may also be defined as a technology included in NR.
  • LTE that can be connected by NR and Multi Radio Dual connectivity (MR-DC) may be distinguished from conventional LTE.
  • MR-DC Multi Radio Dual connectivity
  • LTE using 5GC for the core network may be distinguished from conventional LTE using EPC for the core network.
  • EPC Multi Radio Dual connectivity
  • conventional LTE may refer to LTE that does not implement the technology standardized after Release 15 of 3GPP.
  • Embodiments of the present invention may be applied to NR, LTE and other RATs.
  • LTE Long Term Evolution
  • LTE Long Term Evolution
  • each node and entity when the radio access technology is E-UTRA or NR, and the processing in each node and entity will be described. It may be used for other radio access technologies.
  • the name of each node or entity in the embodiment of the present invention may be another name.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present invention. It should be noted that the functions of each node, radio access technology, core network, interface, etc. described using FIG. 1 are part of the functions closely related to the embodiment of the present invention, and may have other functions.
  • E-UTRA100 may be a radio access technology.
  • E-UTRA 100 may also be the air interface between UE 122 and eNB 102 .
  • the air interface between UE 122 and eNB 102 may be called the 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 consist of an E-UTRA user plane (User Plane: UP) protocol described later and an E-UTRA control plane (Control Plane: CP) protocol described later.
  • eNB 102 may terminate E-UTRA User Plane (UP) and E-UTRA Control Plane (CP) protocols to 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 the interface between eNB 102 and EPC 104 and may be referred to as the S1 interface.
  • 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 .
  • MME Mobility Management Entity
  • S-GW serving gateway
  • the control plane interface of interface 112 may be called the S1-MME interface.
  • the user plane interface of interface 112 may be called the S1-U interface.
  • one or more eNBs 102 may be connected to the EPC 104 via the interface 112. Interfaces may exist between multiple eNBs 102 that connect to the EPC 104 (not shown). An interface between multiple eNBs 102 connected to an EPC 104 may be called an X2 interface.
  • NR106 may be a radio access technology.
  • NR 106 may also be the air interface between UE 122 and gNB 108 .
  • the air interface between UE 122 and gNB 108 may be called the Uu interface.
  • a gNB (g Node B) 108 may be a base station device of NR 106 .
  • gNB 108 may have the NR protocol described below.
  • the NR protocol may consist of an NR user plane (User Plane: UP) protocol, which will be described later, and an NR control plane (Control Plane: CP) protocol, which will be described later.
  • gNB 108 may terminate NR User Plane (UP) and NR Control Plane (CP) protocols to UE 122 .
  • UP NR user plane
  • CP NR Control Plane
  • 5GC110 may be a core network.
  • Interface 116 is the interface between gNB 108 and 5GC 110 and may be referred to as the NG interface.
  • 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 at the 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 the NG-C interface.
  • the user plane interface of interface 116 may be called the NG-U interface.
  • one or more gNBs 108 may be connected to the 5GC 110 via the interface 116. There may be interfaces between gNBs 108 that connect to the 5GC 110 (not shown). An interface between multiple gNBs 108 connected to a 5GC 110 may be called an Xn interface.
  • the eNB102 may have the function of connecting to the 5GC110.
  • the eNB 102 with the function of connecting to the 5GC 110 may be called ng-eNB.
  • Interface 114 is the interface between eNB 102 and 5GC 110 and may be called the NG interface.
  • 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 the Access and Mobility Management Function (AMF: not shown) within 5GC 110 .
  • the user plane interface of interface 114 may terminate at a User Plane Function (UPF: not shown) within 5GC 110 .
  • the control plane interface of interface 114 may be referred to as the NG-C interface.
  • the user plane interface of interface 114 may be called the NG-U interface.
  • a radio access network composed of ng-eNBs or gNBs may be referred to as NG-RAN.
  • NG-RAN, E-UTRAN, eNB, ng-eNB, gNB, etc. may simply be referred to as networks.
  • one or more eNBs 102 may be connected to the 5GC 110 via the interface 114. There may be interfaces between multiple eNBs 102 that connect to the 5GC 110 (not shown). An interface between multiple eNBs 102 connected to a 5GC 110 may be called an Xn interface. Also, eNB 102 connected to 5GC 110 and gNB 108 connected to 5GC 110 may be connected via interface 120 . The interface 120 between the eNB 102 connected to the 5GC 110 and the gNB 108 connected to the 5GC 110 may be referred to as the Xn interface.
  • gNB108 may have the ability to connect to EPC104.
  • a gNB 108 with the ability to connect to an EPC 104 may be called an en-gNB.
  • Interface 118 is the interface between gNB 108 and EPC 104 and may be referred to as the 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 called the S1-U interface.
  • the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 may be connected via 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 referred to as the X2 interface.
  • the interface 124 is the interface between the EPC 104 and the 5GC 110, and may be an interface through CP only, UP only, or both CP and UP. Also, some or all of interfaces 114, 116, 118, 120, 124, etc. may not be present depending on the communication system provided by the carrier.
  • UE122 may be a terminal device capable of receiving broadcast information and paging messages transmitted from eNB102 and/or gNB108. UE 122 may also be a terminal device capable of wireless connection with eNB 102 and/or gNB 108 . Also, the UE 122 may be a terminal device capable of simultaneously establishing wireless connection with the eNB 102 and wireless connection with the gNB 108 . UE 122 may have E-UTRA and/or NR protocols. Note that the wireless connection may be a Radio Resource Control (RRC) connection.
  • RRC Radio Resource Control
  • radio connection may be established by establishing a radio bearer (RB) between UE122 and eNB102 and/or gNB108.
  • a radio bearer used for the CP may be called a signaling radio bearer (SRB).
  • a radio bearer used for UP may also be called a data radio bearer (DRB Data Radio Bearer).
  • Each radio bearer may be assigned a radio bearer identity (ID).
  • the SRB radio bearer identifier may be called an SRB identity (SRB ID).
  • a DRB radio bearer identifier may be called a DRB identity (DRB ID).
  • UE 122 may be a terminal device capable of connecting with EPC 104 and/or 5GC 110 via eNB 102 and/or gNB 108.
  • EPC 104 When the connection destination core network of eNB 102 and/or gNB 108 with which UE 122 communicates is EPC 104, each DRB established between UE 122 and eNB 102 and/or gNB 108 further passes through EPC 104.
  • EPC 104 Evolved Packet System
  • Each EPS bearer may be identified by an EPS bearer identifier (Identity, or ID). Also, the same QoS may be guaranteed for data such as IP packets and Ethernet (registered trademark) frames passing through the same EPS bearer.
  • each DRB established between UE122 and eNB102 and/or gNB108 is further established within 5GC110.
  • Each DRB may be mapped to one or more QoS flows, or may not be mapped to any QoS flows.
  • Each PDU session may be identified with a PDU session identifier (Identity, Identifier, or ID).
  • Each QoS flow may also be identified by a QoS flow identifier (Identity, Identifier, or ID).
  • the same QoS may be guaranteed for data such as IP packets and Ethernet frames passing through the same QoS flow.
  • the EPC 104 does not need to have PDU sessions and/or QoS flows.
  • 5GC110 does not need to have an EPS bearer.
  • UE 122 When UE 122 is connected with EPC 104, UE 122 has information of EPS bearers, but may not have information within PDU sessions and/or QoS flows. Also, when the UE 122 is connected to the 5GC 110, the UE 122 may have information in PDU sessions and/or QoS flows, but not EPS bearer information.
  • eNB 102 and/or gNB 108 are also simply referred to as base station apparatuses, and UE 122 is simply referred to as terminal apparatus or UE.
  • FIG. 2 is a diagram of an example of E-UTRA protocol architecture according to an embodiment of the present invention.
  • FIG. 3 is a diagram of an example of the NR protocol configuration according to the embodiment of the present invention. Note that the functions of each protocol described using FIG. 2 and/or FIG. 3 are part of the functions closely related to the embodiment of the present invention, and may have other functions.
  • an uplink (UL) may be a link from a terminal device to a base station device.
  • the downlink (DL) may be a link from a base station apparatus to a terminal apparatus.
  • FIG. 2(A) is a diagram of the E-UTRA User Plane (UP) protocol stack.
  • the E-UTRAN UP protocol may be the protocol between UE 122 and eNB 102, as shown in FIG. 2(A). That is, the E-UTRANUP protocol may be a protocol that terminates at the eNB 102 on the network side.
  • the E-UTRA user plane protocol stack consists of a PHY (Physical layer) 200 that is a radio physical layer (radio physical layer), a MAC (Medium) that is a medium access control layer (medium access control layer). Access Control) 202, RLC (Radio Link Control) 204 which is a radio link control layer (radio link control layer), and PDCP (Packet Data Convergence Protocol) 206 which is a packet data convergence protocol layer may be configured.
  • PHY Physical layer
  • MAC Medium
  • Access Control 202
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • FIG. 3(A) is a diagram of the NR user plane (UP) protocol stack.
  • the NRUP protocol may be the protocol between UE 122 and gNB 108, as shown in FIG. 3(A). That is, the NR UP protocol may be a protocol that terminates at the gNB 108 on the network side.
  • the E-UTRA user plane protocol stack consists of PHY 300, which is a radio physical layer, MAC 302, which is a medium access control layer, RLC 304, which is a radio link control layer, and PDCP 306, which is a packet data convergence protocol layer. , and a service data adaptation protocol layer (SDAP) (Service Data Adaptation Protocol) 310 .
  • SDAP service data adaptation protocol layer
  • FIG. 2(B) is a diagram of the E-UTRA control plane (CP) protocol configuration.
  • RRC Radio Resource Control
  • NAS Non Access Stratum
  • NAS Non Access Stratum
  • non-AS Access Stratum
  • Fig. 3(B) is a diagram of the NR control plane (CP) protocol configuration.
  • RRC 308 which is a radio resource control layer, may be a protocol between UE 122 and gNB 108. That is, RRC 308 may be a protocol that terminates at gNB 108 on the network side.
  • the non-AS layer NAS 312 may be the protocol between the UE 122 and AMF. That is, the NAS 312 may be a protocol that terminates with AMF on the network side.
  • the AS (Access Stratum) layer may be a layer that terminates between UE 122 and eNB 102 and/or gNB 108. That is, the AS layer is a layer including part or all of PHY200, MAC202, RLC204, PDCP206 and RRC208 and/or a layer including part or all of PHY300, MAC302, RLC304, PDCP306, SDAP310 and RRC308. you can
  • PHY PHY layer
  • MAC MAC layer
  • RLC RLC layer
  • PDCP PDCP layer
  • RRC RRC layer
  • NAS NAS layer
  • PHY PHY layer
  • MAC MAC layer
  • RLC RLC layer
  • PDCP PDCP layer
  • RRC RRC layer
  • NAS NAS
  • SDAP may be the SDAP (SDAP layer) of the NR protocol.
  • PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208 are respectively defined as PHY for E-UTRA or PHY for LTE, E-UTRA MAC for LTE or MAC for LTE, RLC for E-UTRA or RLC for LTE, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE.
  • PHY200, MAC202, RLC204, PDCP206 and RRC208 respectively E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP and E-UTRA It may also be described as RRC or LTE RRC.
  • PHY 300, MAC 302, RLC 304, PDCP 306, and RRC 308 are called PHY for NR, MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively.
  • PHY 200, MAC 302, RLC 304, PDCP 306, and RRC 308 may also be described as NR PHY, NR MAC, NR RLC, NR PDCP, NR RRC, etc., respectively.
  • An entity that has some or all of the functionality of the MAC layer may be called a MAC entity.
  • An entity that has some or all of the functionality of the RLC layer may be called an RLC entity.
  • An entity that has some or all of the functionality of the PDCP layer may be called a PDCP entity.
  • An entity that has some or all of the functionality of the SDAP layer may be called an SDAP entity.
  • An entity that has some or all of the functionality 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.
  • the data provided from MAC, RLC, PDCP, SDAP to the lower layer and/or the data provided from the lower layer to MAC, RLC, PDCP, SDAP are respectively referred to as MAC PDU (Protocol Data Unit), RLC You may call them PDUs, PDCP PDUs, and SDAP PDUs.
  • MAC SDU Service Data Unit
  • RLC SDU refer to data provided from upper layers to MAC, RLC, PDCP, and SDAP and/or data provided from MAC, RLC, PDCP, and SDAP to upper layers, respectively.
  • PDCP SDU, and SDAP SDU A segmented RLC SDU may also be referred to as an RLC SDU segment.
  • 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.
  • a PHY may be connected to a high-level MAC via a Transport Channel.
  • the PHY may pass data to the MAC over transport channels.
  • the PHY may also be provided with data from the MAC over the transport channel.
  • RNTI Radio Network Temporary Identifier
  • 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
  • the PBCH may be used to broadcast system information required by terminal equipment.
  • the PBCH may be used to report the time index (SSB-Index) within the period of the synchronization signal block (SS/PBCH block, also called SSB).
  • SSB-Index time index within the period of the synchronization signal block
  • the PDCCH may be used to transmit (or carry) downlink control information (DCI) in downlink radio communication (radio communication from the base station device to the terminal device).
  • DCI downlink control information
  • 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.
  • a PDCCH may be sent in a PDCCH candidate.
  • a terminal may monitor a set of PDCCH candidates in a serving cell. Monitoring a set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format.
  • the DCI format may be used for PUSCH scheduling in the serving cell. PUSCH may be used for transmission of user data, transmission of RRC messages to be described later, and the like.
  • the PUCCH may be used to transmit uplink control information (UCI) in uplink radio communication (radio communication from a terminal device to a base station device).
  • the uplink control information may include channel state information (CSI: Channel State Information) used to indicate the state of the downlink channel.
  • CSI Channel State Information
  • the uplink control information may also include a scheduling request (SR: Scheduling Request) used to request UL-SCH (UL-SCH: Uplink Shared CHannel) resources.
  • SR Scheduling Request
  • UL-SCH Uplink Shared CHannel
  • 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. Also, in the case of downlink, it may be used for transmission of system information (SI: System Information), random access response (RAR: Random Access Response), and the like.
  • SI System Information
  • RAR Random Access Response
  • PUSCH may be used to transmit HARQ-ACK and/or CSI together with uplink data (UL-SCH: Uplink Shared CHannel) or uplink data from the MAC layer.
  • PUSCH may also be used to transmit CSI only, or HARQ-ACK and CSI only. That is, PUSCH may be used to transmit UCI only.
  • PDSCH or PUSCH may also be used to transmit RRC signaling (also referred to as RRC messages) and MAC Control Elements (MAC Control Elements: MAC CE).
  • RRC signaling transmitted from the base station apparatus may be signaling common to multiple terminal apparatuses within the cell.
  • the RRC signaling transmitted from the base station apparatus may be signaling dedicated to a certain terminal apparatus (also referred to as dedicated signaling). That is, terminal device-specific (UE-specific) information may be transmitted using signaling dedicated to a certain terminal device.
  • PUSCH may also be used to transmit UE Capability in the uplink.
  • the PRACH may be used to transmit random access preambles.
  • PRACH is used to indicate initial connection establishment procedures, handover procedures, connection re-establishment procedures, synchronization (timing adjustments) for uplink transmissions, and requests for PUSCH (UL-SCH) resources. may be used for
  • Uplink Uplink
  • DL Downlink
  • BCCH Broadcast Control Channel
  • SI System Information
  • a PCCH may be a downlink logical channel for carrying paging messages.
  • a 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 does not have an RRC connection.
  • CCCH may also be used between the base station apparatus and a plurality of terminal apparatuses.
  • DCCH Dedicated Control Channel
  • DCCH is a logical channel for transmitting dedicated control information in a one-to-one (point-to-point) bi-directional manner between a terminal device and a base station device. It's okay.
  • Dedicated control information may be control information dedicated to each terminal device.
  • DCCH may be used when a terminal device has an RRC connection.
  • a 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.
  • a DTCH may be a logical channel for transmitting dedicated user data.
  • Dedicated user data may be user data dedicated to each terminal device.
  • DTCH may exist in both uplink and downlink.
  • MTCH Multicast Traffic Channel
  • MTCH may be a point-to-multipoint downlink channel for transmitting data from base station devices to terminal devices.
  • MTCH may be a multicast logical channel.
  • MTCH may be used by the corresponding terminal only when the terminal receives MBMS.
  • a MCCH may be a point-to-multipoint downlink channel for sending MBMS control information for one or more MTCHs from a base station apparatus to a terminal apparatus.
  • MCCH may be a multicast logical channel. The MCCH may be used by the terminal only when the terminal receives MBMS or is interested in receiving MBMS.
  • SC-MTCH Single Cell Multicast Traffic Channel
  • SC-MTCH Single Cell Multicast Traffic Channel
  • SC-MTCH may be a multicast logical channel.
  • SC-MTCH may be used by the corresponding terminal device only when the terminal device receives MBMS using SC-PTM (Single Cell Point-To-Multipoint).
  • SC-MCCH Single Cell Multicast Control Channel
  • SC-MCCH is a point-to-multipoint downlink for sending MBMS control information for one or more SC-MTCH from the base station apparatus to the terminal apparatus.
  • SC-MCCH may be a multicast logical channel.
  • the SC-MCCH may be used by the terminal only when the terminal receives MBMS using SC-PTM or when the terminal is interested in receiving MBMS using SC-PTM.
  • CCCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.
  • UL-SCH Uplink Shared Channel
  • the DCCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.
  • UL-SCH Uplink Shared Channel
  • DTCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.
  • UL-SCH Uplink Shared Channel
  • BCCH may be mapped to BCH (Broadcast Channel), which is a downlink transport channel, and/or DL-SCH (Downlink Shared Channel).
  • BCH Broadcast Channel
  • DL-SCH Downlink Shared Channel
  • PCCH may be mapped to PCH (Paging Channel), which is a downlink transport channel.
  • PCH Packet Control Channel
  • CCCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.
  • DL-SCH Downlink Shared Channel
  • the DCCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.
  • DL-SCH Downlink Shared Channel
  • DTCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.
  • DL-SCH Downlink Shared Channel
  • MTCH may be mapped to MCH (Multicast Channel), which is a downlink transport channel.
  • MCH Multicast Channel
  • MCCH may be mapped to MCH (Multicast Channel), which is a downlink transport channel.
  • MCH Multicast Channel
  • SC-MTCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.
  • DL-SCH Downlink Shared Channel
  • SC-MTCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.
  • DL-SCH Downlink Shared Channel
  • a MAC may be referred to as a MAC sublayer.
  • the MAC may have the function of mapping various logical channels (Logical Channel) to the corresponding transport channels.
  • a logical channel may be identified by a logical channel identifier (Logical Channel Identity or Logical Channel ID).
  • a MAC may be connected to an upper RLC via a logical channel (logical channel).
  • Logical channels may be divided into control channels for transmitting control information and traffic channels for transmitting user information according to the type of information to be transmitted.
  • Logical channels may also be divided into uplink logical channels and downlink logical channels.
  • the MAC may have the ability to multiplex MAC SDUs belonging to one or more different logical channels and provide them to the PHY.
  • the MAC may also have the function of demultiplexing the MAC PDUs provided by the PHY and providing them to upper layers via the logical channel to which each MAC SDU belongs.
  • the MAC may also have a function to perform error correction through HARQ (Hybrid Automatic Repeat reQuest). Also, the MAC may have a function of performing priority processing between terminal devices using dynamic scheduling. Also, the MAC may have a function of performing priority processing between logical channels within one terminal device. The MAC may have a function of prioritizing overlapping resources within one terminal device.
  • HARQ Hybrid Automatic Repeat reQuest
  • E-UTRA MAC may have the ability to identify Multimedia Broadcast Multicast Services (MBMS).
  • MBMS Multimedia Broadcast Multicast Services
  • the NR MAC may also have a function of identifying Multicast/Broadcast Service (MBS).
  • MMS Multicast/Broadcast Service
  • MAC may have a function to select a transport format.
  • MAC has a function of performing discontinuous reception (DRX) and/or discontinuous transmission (DTX: discontinuous transmission), a function of executing random access (RA) procedure, notifying information of transmittable power, power It may have a power headroom reporting function, a buffer status reporting function that notifies the amount of data in the transmission buffer, and so on.
  • DRX discontinuous reception
  • DTX discontinuous transmission
  • RA random access
  • 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 performing control in MAC.
  • MAC control element MAC CE
  • the BSR procedure may be used to provide the serving gNB (base station equipment) with information about the uplink data volume within the MAC entity.
  • Each logical channel may be assigned to one logical channel group (Logical Channel Group: LCG) using a parameter (logicalChannelGroup) provided by RRC.
  • LCG Logical Channel Group
  • logicalChannelGroup a parameter provided by RRC.
  • the maximum number of LCGs can be eight.
  • the MAC entity of the terminal equipment shall calculate the amount of UL data available for a logical channel according to the data volume calculation procedure in RLC and PDCP. You can decide.
  • a BSR may be triggered based on meeting any of the following conditions (A) through (D).
  • BSR triggered by this condition may be a regular BSR.
  • BSR MAC CE buffer status report MAC CE plus its subheader
  • a BSR triggered by this condition may be a padding BSR.
  • C When the timer (retxBSR-Timer) used for BSR control expires and at least one of the logical channels belonging to the LCG contains uplink data. (The BSR triggered by this condition may be a regular BSR.)
  • D When the timer used to control the BSR (periodicBSR-Timer) expires. (BSRs triggered by this condition may be periodic BSRs.)
  • the MAC entity of the terminal shall indicate data available for transmission if more than one LCG has data available for transmission when the MAC PDU containing the BSR is constructed. May report Long BSR for all LCGs with For Regular BSR and Periodic BSR, the terminal MAC entity shall report Short BSR if two or more LCGs have no data available for transmission when the MAC PDU containing the BSR is constructed. good.
  • the MAC entity of the terminal device reports Short Truncated BSR, reports Long Truncated BSR, or reports Short BSR, based on the number of padding bits, the size of Short BSR, and the size of Long BSR. or report a Long BSR.
  • the MAC entity of the terminal device shall indicate when the BSR is triggered that the logical channel that triggered the BSR has the highest priority with data available for transmission. may be considered to be a logical channel of
  • the MAC entity of the terminal device indicates that at least one BSR has been triggered and that BSR has not been canceled, that UL-SCH resources are available for new transmissions, and that UL-SCH resources are assigned logical channel prioritization ( Some or all of the following (A) to (C) may be performed based on the fact that the BSR MAC CE and its subheaders can be accommodated as a result of logical channel prioritization.
  • B Generate one or more BSR MAC CEs or instruct other entities to generate one or more BSR MAC CEs
  • All generated BSRs are Long Truncated BSRs and Short Truncated BSRs Starts or restarts the periodicBSR-Timer, unless
  • C Starts or restarts the retxBSR-Timer
  • a MAC PDU may contain at most one BSR MAC CE, even when multiple BSRs are triggered by multiple events (conditions). Regular BSRs and Periodic BSRs may have priority over Padding BSRs.
  • the MAC entity of the terminal device may restart the retxBSR-Timer based on receiving a grant for transmission of new data on any UL-SCH.
  • the PHR procedure may be used to provide the serving gNB (base station equipment) with some or all of the information (A) to (C) below.
  • B The nominal UE maximum transmit power and others
  • C between the nominal UE maximum transmit power and the SRS transmit power per activated serving cell difference from estimate
  • the above information (A), (B), and (C) may be referred to as type 1 power headroom, type 2 power headroom, and type 3 power headroom, respectively. Also, information including part or all of (A) to (C) may be referred to as power headroom.
  • a MAC CE that contains only one set of information on the type of power headroom, the cell of interest, and the maximum transmission power in that cell may be referred to as a Single Entry PHR MAC CE.
  • a MAC CE that includes multiple sets of information on the power headroom type, target cell, and maximum transmission power in that cell may be referred to as Multiple Entry PHR MAC CE.
  • an uplink is set in a certain MAC entity, and the BWP indicated by the first downlink BWP identifier (firstActiveDownlinkBWP-Id) set in the RRC message is set to Dormant BWP.
  • the UE's MAC entity may trigger a PHR when a SCell that is not activated is activated. Also, when a PSCell is newly added or changed, the MAC entity of the UE may trigger PHR.
  • the UE's MAC entity shall May trigger PHR.
  • the above BWP change may be expressed as a BWP switch.
  • the MAC entity of the UE may perform some or all of (A) and (B) below. .
  • (A) If this uplink resource is the first since the last MAC reset, start a timer (phr-PeriodicTimer).
  • (B) If at least one PHR has been triggered by the PHR procedure and this trigger has not been canceled, and the assigned uplink resources are allocated for the PHR, taking into account the priority of the logical channels. Some or all of the following (B-1) to (B-5) are performed based on the ability to accommodate the MAC CE and its subheader.
  • (B-1) If the MAC CE to be accommodated is a Multiple Entry PHR MAC CE, perform some or all of the following (B-1-1) to (B-1-3) processing.
  • (B-1-1) Regarding each activated serving cell in which an uplink is configured, which is associated with an arbitrary MAC entity of the same UE and whose activated DL BWP is not a dormant (DL) BWP , obtains the type 1 or type 3 power headroom values for the uplink carriers associated with the NR serving cell and the E-UTRA serving cell, and if the MAC entity associating the serving cell is transmitting on this serving cell or another MAC entity of the same UE is configured and has uplink resources allocated for transmission on this serving cell and has uplink resources assigned for transmission on this serving cell.
  • DL dormant
  • the value of this maximum transmission power is obtained from the physical layer.
  • the UE may report type 2 power headroom for SpCells of another MAC entity of the same UE, if this MAC entity is an E-UTRA MAC entity If it is determined by higher layers to obtain the value of the Type 2 power headroom and then calculate the maximum transmit power based on the power used for actual transmission on this MAC entity's SpCell, Get the value of this maximum transmit power from the physical layer.
  • B-1-3 Generate and transmit a Multiple Entry PHR MAC CE based on the value reported from the physical layer after considering the priority of the logical channel.
  • B-2 If the accommodated MAC CE is a Single Entry PHR MAC CE, the type 1 power headroom value for the uplink carrier associated with the PCell and the associated maximum transmission. Power values are obtained from the physical layer, and a Single Entry PHR MAC CE is generated and transmitted based on these values, taking into account the priority of logical channels.
  • B-3) Start (Start) or restart (Restart) the timer (phr-PeriodicTimer).
  • B-4) Start or restart the timer (phr-ProhibitTimer).
  • B-5) Cancel all triggered PHRs.
  • a Scheduling Request may be used by a terminal device to request UL-SCH resources for a new transmission.
  • the MAC entity of the terminal device may be configured with zero, one, or multiple SR settings.
  • the SR configuration may include a set of PUCCH resources for different BWPs and cell-wide SRs. For one logical channel or beam failure recovery, PUCCH resources for at most one SR may be configured per BWP.
  • an SR When an SR is triggered, it may be considered pending (it is a Pending SR) until the SR is cancelled.
  • the MAC entity of the terminal device may consider that only the PUCCH resources of the BWP (Active BWP) that are activated when transmitting the SR are valid.
  • the MAC entity of the terminal equipment Based on the fact that at least one SR is pending and that it does not have a valid PUCCH resource configuration for the Pending SR, the MAC entity of the terminal equipment initiates a random access procedure in the SpCell to send the Pending SR. You can cancel.
  • RLC may be referred to as an RLC sublayer.
  • the E-UTRA RLC may have the function of segmenting and/or concatenating the data provided from the upper layer PDCP and providing it to the lower layer.
  • E-UTRA RLC may have the function of reassembling and re-ordering data provided from lower layers and providing it to upper layers.
  • NR RLC may have a function to add a sequence number independent of the sequence number added by PDCP to the data provided by PDCP in the upper layer. Also, the NR RLC may have a function of segmenting data provided from PDCP and providing it to lower layers. The NRRLC may also have a function of reassembling data provided from lower layers and providing the reassembled data to upper layers. The RLC may also have a data retransmission function and/or a retransmission request function (Automatic Repeat reQuest: ARQ).
  • ARQ Automatic Repeat reQuest
  • RLC may have a function to correct errors by ARQ.
  • the control information sent from the RLC receiver to the sender for ARQ indicating the data that needs to be retransmitted may be referred to as a status report.
  • a status report transmission instruction sent from the RLC transmitting side to the receiving side can be called a poll.
  • the RLC may also have the capability to detect data duplication.
  • RLC may also have a function of discarding data.
  • RLC may have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM).
  • TM Transparent Mode
  • UM Unacknowledged Mode
  • AM Acknowledged Mode
  • the TM does not divide the 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.
  • the UM divides and/or combines the data received from the upper layer, adds an RLC header, etc., but does not need to perform data retransmission control.
  • 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.
  • the AM may divide and/or combine the data received from the upper layer, add an RLC header, control data retransmission, etc.
  • the AM RLC entity is a bi-directional entity and may be configured as an AM RLC consisting of a transmitting side and a receiving side.
  • TMD PDU Data provided to the lower layer by TM and/or data provided from the lower layer may be called TMD PDU.
  • Data provided in UM to lower layers and/or data provided by lower layers may also be referred to as UMD PDUs.
  • UMD PDUs Data provided to lower layers by AM or data provided from lower layers.
  • AMD PDUs Data provided to lower layers by AM or data provided from lower layers.
  • RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC may differ.
  • RLC PDUs may also include RLC PDUs for data and RLC PDUs for control.
  • An RLC PDU for data may be called an RLC DATA PDU (RLC Data PDU).
  • the control RLC PDU may be called an RLC CONTROL PDU.
  • PDCP may be referred to as a PDCP sublayer.
  • PDCP may have a function to maintain sequence numbers. PDCP may also have a header compression/decompression function for efficiently transmitting user data such as IP packets and Ethernet frames over a wireless section.
  • a protocol used for IP packet header compression/decompression may be called ROHC (Robust Header Compression) protocol.
  • Ethernet frame header compression/decompression may be called the EHC (Ethernet (registered trademark) Header Compression) protocol.
  • PDCP may also have data encryption/decryption functions.
  • PDCP may have data integrity protection and integrity verification functions.
  • PDCP may also have a re-ordering function.
  • PDCP may also have a retransmission function for PDCP SDUs.
  • PDCP may also have a function of discarding data using a discard timer.
  • PDCP may also have a duplication function.
  • PDCP may also have a function of discarding duplicated received data.
  • a PDCP entity is a bi-directional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity.
  • the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different.
  • PDCP PDUs may include data PDCP PDUs and control PDCP PDUs.
  • a PDCP PDU for data may be called a PDCP DATA PDU (PDCP Data PDU).
  • the PDCP PDU for control may be called a PDCP CONTROL PDU (PDCP Control PDU).
  • the status of PDCP replication (either Activated or Deactivated) may be configured by RRC at the same time. After that setting, the state of PDCP replication may be dynamically controlled by MAC CE.
  • the original PDCP PDU and the replicated PDCP PDU may be sent on different carriers.
  • original PDCP PDUs and replicated PDCP PDUs may be transmitted in cells of different cell groups.
  • the RRC entity of the terminal device may set duplication for the radio bearer by means of an RRC message.
  • the RRC message may include a cell group identifier and/or a logical channel identifier as primary path information.
  • a primary path may be information that indicates the cell group identifier and logical channel identifier of the primary RLC entity.
  • PDCP duplication may also be referred to as PDCP duplication or PDCP multiplexing.
  • SDAP is the Service Data Adaptation Protocol Layer (Service Data Adaptation Protocol Layer).
  • SDAP is mapping between downlink QoS flows and data radio bearers (DRBs) sent from the 5GC 110 to the terminal device via the base station device, and/or from the terminal device via the base station device. It may have the ability to map uplink QoS flows sent to the 5GC 110 to the DRB. SDAP may also have the function of storing mapping rule information. SDAP may also have a function to mark QoS flow identifiers (QoS Flow ID: QFI).
  • SDAP PDUs may include data SDAP PDUs and control SDAP PDUs. A data SDAP PDU may be called an SDAP DATA PDU. A control SDAP PDU may also be called an SDAP CONTROL PDU. Note that one SDAP entity of the terminal device may exist for each PDU session.
  • RRC may have a broadcast function.
  • RRC may have call (paging) functionality from EPC 104 and/or 5GC 110 .
  • RRC may have a paging function from eNB102 connected to gNB108 or 5GC100.
  • RRC may also have an RRC connection management function.
  • RRC may also have a radio bearer control function.
  • RRC may also have a cell group control function.
  • RRC may also have a mobility control function.
  • RRC may also have terminal measurement reporting and terminal measurement reporting control functions.
  • RRC may also have QoS management functions.
  • RRC may also have radio link failure detection and recovery functionality.
  • RRC uses RRC messages for broadcasting, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal equipment measurement reporting and terminal equipment measurement reporting control, QoS management, radio link failure detection and recovery, etc. may be performed. Note that the RRC messages and parameters used in E-UTRA RRC may differ from the RRC messages and parameters used in NR RRC.
  • the RRC message may be sent using the logical channel's BCCH, may be sent using the logical channel's PCCH, may be sent using the logical channel's CCCH, or may be sent using the logical channel's DCCH. It may be sent using the MCCH of the logical channel.
  • the RRC message sent using BCCH may include, for example, a master information block (Master Information Block: MIB), each type of system information block (System Information Block: SIB) may be included, and others of RRC messages may be included.
  • RRC messages sent using the PCCH may include, for example, paging messages and other RRC messages.
  • RRC messages sent in the uplink (UL) direction using CCCH include, for example, RRC Setup Request, RRC Resume Request, RRC Reestablishment Request, RRC A system information request message (RRC System Info Request) may be included. Also, for example, RRC Connection Request, RRC Connection Resume Request, RRC Connection Reestablishment Request, 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, RRC Connection Setup, RRC Connection Reestablishment, RRC A connection re-establishment rejection message (RRC Connection Reestablishment Reject) may be included. Also, 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 messages sent in the uplink (UL) direction using DCCH include, for example, a Measurement Report message, an RRC Connection Reconfiguration Complete message, an RRC Connection Setup Complete message, An RRC Connection Reestablishment Complete message, a Security Mode Complete message, a UE Capability Information message, etc. may be included.
  • Measurement Report message 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 (UE Capability Information), and the like.
  • Other RRC messages may also be included.
  • RRC messages sent in the downlink (DL) direction using DCCH include, for example, RRC Connection Reconfiguration, RRC ConnectionRelease, Security Mode Command, UE Capabilities.
  • An inquiry message (UE Capability Inquiry) may be included.
  • RRC Reconfiguration message RRC Resume message, RRC Release message, RRC Reestablishment message, Security Mode Command message, UE Capability Inquiry message. (UE Capability Enquiry), etc. may be included.
  • Other RRC messages may also be included.
  • a NAS may have an authentication function. Also, the NAS may have a function of performing mobility management. The NAS may also have a security control function.
  • each layer may be included in another layer (layer).
  • an IP layer a TCP (Transmission Control Protocol) layer above the IP layer, a UDP (User Datagram Protocol) layer, and the like may exist in layers (not shown) above the AS layer of the terminal device.
  • An Ethernet layer may exist in a layer above the AS layer of the terminal device.
  • the layer above the AS layer of the terminal device may be called the PDU layer (PDU layer).
  • the PDU layers may include IP layer, TCP layer, UDP layer, Ethernet layer, and so on.
  • Application layers may exist in higher layers such as the IP layer, TCP layer, UDP layer, Ethernet layer, and PDU layer.
  • the application layer may include SIP (Session Initiation Protocol) and SDP (Session Description Protocol) used in IMS (IP Multimedia Subsystem), which is one of the service networks standardized by 3GPP.
  • the application layer may include protocols such as RTP (Real-time Transport Protocol) used for media communication and/or RTCP (Real-time Transport Control Protocol) and HTTP (HyperText Transfer Protocol) for media communication control.
  • the application layer may also include codecs for various media.
  • the RRC layer may be a higher layer than the SDAP layer.
  • UE 122 may be in RRC_CONNECTED state.
  • a state in which an RRC connection is established may include a state in which the UE 122 holds some or all of the UE contexts described below.
  • states in which an RRC connection is established may include states in which UE 122 is able to transmit and/or receive unicast data.
  • UE 122 may also be in RRC_INACTIVE state when the RRC connection is suspended.
  • UE 122 may be in RRC_INACTIVE state when UE 122 is connected to 5GC and the RRC connection is dormant.
  • a UE 122 may be in the RRC_IDLE state when the UE 122 is neither in the RRC_CONNECTED state nor in the RRC_INACTIVE state.
  • UE 122 may initiate dormancy of the RRC connection. If the UE 122 is connected to EPC, when the RRC connection is suspended, the UE 122 may retain the AS context of the UE and an identifier (resumeIdentity) used for resume and transition to the RRC_IDLE state.
  • a layer higher than the RRC layer of UE 122 (for example, NAS layer) confirms that UE 122 holds the AS context of the UE, and that the E-UTRAN permits recovery of the RRC connection, and that UE 122 exits the RRC_IDLE state. When it needs to transition to the RRC_CONNECTED state, it may initiate the resumption of a dormant RRC connection.
  • the UE 122 connected to the EPC 104 and the UE 122 connected to the 5GC 110 may have different definitions of pausing the RRC connection.
  • UE122 when UE122 is connected to EPC (when sleeping in RRC_IDLE state) and when UE122 is connected to 5GC (when sleeping in RRC_INACTIVE state), UE122 is not connected to RRC. All or part of the procedure for returning from hibernation may be different.
  • RRC_CONNECTED state may be called RRC connected mode, RRC inactive mode, and RRC idle mode, respectively, and may be misidentified. If there is no fear, it may simply be called connected mode, inactive mode, or idle mode.
  • the UE AS context held by UE 122 includes the current RRC settings, current security context, PDCP state including ROHC (RObust Header Compression) state, C-RNTI (Cell Radio Network Temporary Identifier), cell identifier (cellIdentity), and physical cell identifier of the connection source PCell, all or part of which may be information.
  • the UE AS context held by either or all of the eNB 102 and gNB 108 may contain the same information as the UE AS context held by the UE 122, or the information contained in the UE AS context held by the UE 122. may contain different information.
  • a security context consists of a cryptographic key at the AS level, NH (Next Hop parameter), NCC (Next Hop Chaining Counter parameter) used to derive the access key for the next hop, an identifier for the selected AS level encryption algorithm, and replay protection. may be information including all or part of the counters used for
  • a cell group that is set by the base station device for the terminal device will be explained.
  • a cell group may consist of only one special cell (Special Cell: SpCell).
  • a cell group may also consist of one SpCell and one or more secondary cells (SCells). That is, a cell group may consist of one SpCell and optionally one or more SCells.
  • the SpCell may mean the Primary Cell (PCell). Also, when the MAC entity is associated with a Secondary Cell Group (SCG), SpCell may mean a Primary SCG Cell (PSCell). SpCell may also mean PCell if the MAC entity is not associated with a cell group. PCell, PSCell and SCell are serving cells.
  • a SpCell may support PUCCH transmission and contention-based Random Access.
  • a SpCell may remain activated at all times.
  • a PCell may be a cell used for the RRC connection establishment procedure when a terminal device in the RRC idle state transitions to the RRC connected state. Also, the PCell may be a cell used for the RRC connection re-establishment procedure in which the terminal device re-establishes the RRC connection. Also, the PCell may be a cell used for a random access procedure during handover.
  • a PSCell may be a cell used in a random access procedure when adding a secondary node (SN), which will be described later.
  • the SpCell may be a cell that is used for purposes other than those described above.
  • a cell group consists of SpCells and one or more SCells, it can be said that carrier aggregation (CA) is configured for this cell group.
  • CA carrier aggregation
  • a cell that provides an additional radio resource to a SpCell for a terminal device in which CA is configured may mean an SCell.
  • TAG Timing Advance Group
  • PTAG Primary Timing Advance Group
  • STAG Secondary Timing Advance Group
  • a cell group may be added to the terminal device from the base station device.
  • DC is a technique of performing data communication using radio resources of cell groups respectively configured by a first base station apparatus (first node) and a second base station apparatus (second node).
  • MR-DC may be a technology involved in DC.
  • a first base station apparatus may add a second base station apparatus to perform DC.
  • the first base station device may be called a master node (Master Node: MN).
  • a cell group composed of master nodes may be called a master cell group (MCG).
  • MCG master cell group
  • SN secondary node
  • SCG secondary cell group
  • the master node and the secondary node may be configured within the same base station apparatus.
  • the cell group set in the terminal device may be called MCG.
  • SpCell configured in the terminal device may be PCell.
  • MR-DC may be a technology that performs DC using E-UTRA for MCG and NR for SCG. Also, MR-DC may be a technique of performing DC using NR for MCG and E-UTRA for SCG. MR-DC may also be a technique of performing DC using NR for both MCG and SCG. Examples of MR-DC using E-UTRA for MCG and NR for SCG include EN-DC (E-UTRA-NR Dual Connectivity) using EPC in the core network and NGEN-DC using 5GC in the core network. There may be DC (NG-RAN E-UTRA-NR Dual Connectivity).
  • an example of MR-DC that uses NR for MCG and E-UTRA for SCG may be NE-DC (NR-E-UTRA Dual Connectivity) that uses 5GC for the core network.
  • An example of MR-DC using NR for both MCG and SCG may be NR-DC (NR-NR Dual Connectivity) using 5GC for the core network.
  • one MAC entity may exist for each cell group.
  • the MAC entity for the MCG in the terminal device may always be established in the terminal device in all states (RRC idle state, RRC connected state, RRC inactive state, etc.). Also, 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.
  • the MAC entity for each cell group of the terminal device may be set by the terminal device receiving an RRC message from the base station device.
  • the MAC entity for MCG may be the E-UTRA MAC entity and the MAC entity for SCG may be the NR MAC entity.
  • the MAC entity for MCG may be the NR MAC entity and the MAC entity for SCG may be the E-UTRA MAC entity.
  • both MAC entities for MCG and SCG may be NR MAC entities.
  • one MAC entity for each cell group can be rephrased as one MAC entity for each SpCell.
  • one MAC entity for each cell group may be rephrased as one MAC entity for each SpCell.
  • 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 the SRB for RRC messages that are transmitted and/or received using the CCCH of the logical channel.
  • SRB1 may be the SRB for RRC messages and for NAS messages before the establishment of SRB2.
  • RRC messages sent and/or received using SRB1 may include piggybacked NAS messages. All RRC and NAS messages transmitted and/or received using SRB1 may use the DCCH of the logical channel.
  • SRB2 may be an SRB for NAS messages and for RRC messages containing logged measurement information. All RRC and NAS messages transmitted and/or received using SRB2 may use the DCCH of the logical channel. Also, SRB2 may have a lower priority than SRB1.
  • SRB3 may be an SRB for transmitting and/or receiving a specific RRC message when EN-DC, NGEN-DC, NR-DC, etc. are set in the terminal device. All RRC and NAS messages transmitted and/or received using SRB3 may use the DCCH of the logical channel. Other SRBs may also be provided for other uses.
  • a DRB may be a radio bearer for user data.
  • Logical channel DTCH may be used for RRC messages transmitted and/or received using DRB.
  • Radio bearers may include RLC bearers.
  • An RLC bearer may consist of one or two RLC entities and logical channels.
  • the RLC entity when there are two RLC entities in the RLC bearer may be a TM RLC entity and/or a transmitting RLC entity and a receiving RLC entity in a unidirectional UM mode RLC entity.
  • SRB0 may consist of one RLC bearer.
  • An SRB0 RLC bearer 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.).
  • SRB1 may be established and/or set in the terminal device by an RRC message 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.
  • SRB2 may be established and/or set in the terminal device by an RRC message received by the terminal device in the RRC connected state with AS security activated from the base station device.
  • SRB2 may consist of one PDCP entity and one or more RLC bearers.
  • An SRB2 RLC bearer may consist of an AM RLC entity and a logical channel. Note that PDCPs on the base station device side of SRB1 and SRB2 may be placed in the master node.
  • SRB3 is when a secondary node in EN-DC, NGEN-DC, or NR-DC is added, or when the secondary node is changed, the terminal device in the RRC connection state with AS security activated becomes the base station.
  • One may be established and/or configured in the terminal by RRC messages 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.
  • An SRB3 RLC bearer may consist of an AM RLC entity and a logical channel.
  • the PDCP on the base station device side of SRB3 may be placed in the secondary node.
  • One or more DRBs may be established and/or set in the terminal device by an RRC message received from the base station device by the terminal device in the RRC connected state with AS security activated.
  • 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.
  • the radio bearer in which PDCP is placed in the master node may be called the MN terminated (terminated) bearer.
  • a radio bearer in which PDCP is placed in a secondary node may be called an SN terminated (terminated) bearer.
  • a radio bearer in which the RLC bearer exists only in the MCG may be called an MCG bearer.
  • a radio bearer whose RLC bearer exists only in the SCG may be called an SCG bearer.
  • a radio bearer in which RLC bearers exist in both MCG and SCG may be called a split bearer.
  • the bearer types of SRB1 and SRB2 established/and configured in the terminal device may be MN-terminated MCG bearer and/or MN-terminated split bearer.
  • the SRB3 bearer type established/or configured in the terminal device may be an SN-terminated SCG bearer.
  • the DRB bearer type established/or configured in the terminal device may be any of all bearer types.
  • the RLC entity established and/or configured may be E-UTRA RLC.
  • the RLC entity established and/or configured may be NR RLC.
  • the PDCP entity established and/or configured for the MN-terminated MCG bearer may be either E-UTRA PDCP or NR PDCP.
  • bearer type radio bearers i.e. MN terminated split bearer, MN terminated SCG bearer, SN terminated MCG bearer, SN terminated split bearer and SN terminated SCG bearer, when EN-DC is configured in the terminal equipment.
  • the PDCP established and/or configured by the NR may be the NR PDCP.
  • the PDCP entity established and/or configured for radio bearers in all bearer types may be NR PDCP.
  • a DRB established and/or configured in a terminal device may be associated with one PDU session.
  • One SDAP entity may be established and/or configured for one PDU session in the terminal device.
  • Established and/or Configured in a Terminal An SDAP entity, a PDCP entity, an RLC entity, and a logical channel may be established and/or configured by an RRC message that the terminal receives from a base station.
  • a network configuration in which the master node is eNB 102 and EPC 104 is the core network may be called E-UTRA/EPC.
  • a network configuration in which the master node is eNB 102 and 5GC 110 is the core network may be called E-UTRA/5GC.
  • 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.
  • the master node described above may refer to a base station apparatus that communicates with terminal apparatuses.
  • a handover may be a process in which the UE 122 in the RRC connected state changes the serving cell. Handover may occur when UE 122 receives an RRC message from eNB 102 and/or gNB 108 indicating a handover.
  • the RRC message that instructs handover may be a message regarding reconfiguration of the RRC connection that includes a parameter that instructs handover (for example, an information element named MobilityControlInfo or an information element named ReconfigurationWithSync).
  • MobilityControlInfo described above may be rephrased as a mobility control setting information element, a mobility control setting, or mobility control information.
  • the above information element named ReconfigurationWithSync may be rephrased as reset information element with synchronization or reset with synchronization.
  • the RRC message instructing handover may be a message indicating movement to another RAT cell (for example, MobilityFromEUTRACommand or MobilityFromNRCommand).
  • handover can be rephrased as reconfiguration with sync.
  • the conditions under which UE 122 can perform handover include some or all of when AS security is activated, when SRB2 is established, and at least one DRB is established. good.
  • the terminal device may perform processing that does not change the serving cell based on the RRC message instructing handover. That is, the terminal device may perform a handover process with the same cell as the current serving cell as the target cell.
  • the uplink Time Alignment in the MAC entity of the terminal device will be explained.
  • the MAC entity of the terminal device may be configured with the following parameters for maintenance of uplink time alignment by RRC.
  • Per TAG time alignment timer timeAlignmentTimner: The MAC entity considers the uplink of the serving cell belonging to the TAG associated with this timer to be uplink time aligned (in other words, uplink synchronized). A timer used to control time.
  • the MAC entity of the terminal device performs some or all of (A) to (D) below in order to maintain uplink time alignment.
  • (A) receives a timing advance command MAC control element, and if the indicated TAG maintains a parameter (N_TA) indicating timing advance between downlink and uplink, then (1) this indicated (2) start or restart the time alignment timer associated with this indicated TAG;
  • (B) When a timing advance command is received in the random access response message for the serving cell belonging to a certain TAG or the MSGB for the SpCell, some of (B-1) to (B-3) below or You can do all.
  • (B-1) If the random access preamble is not selected by the MAC entity from contention-based random access preambles, the following (B-1-1) to (B-1- 2) is processed.
  • (B-1-1) Apply the timing advance command for this TAG.
  • (B-1-2) Start or restart the time alignment timer associated with this TAG.
  • (B-2) If the condition of (B-1) is not met and the time alignment timer associated with this TAG is not running, then (B-2-1) to (B-2-3) below process.
  • (B-2-1) Apply the timing advance command for this TAG.
  • (B-2-2) Start the time alignment timer associated with this TAG.
  • (B-2-3) HARQ feedback for MAC PDU containing UE contention resolution identifier (UE contention Resolution Identity) MAC control element, or when contention resolution in the random access procedure is deemed not successful , stop the time alignment timer associated with this TAG when the collision resolution for the SI request is deemed successful.
  • (B-3) If none of the conditions (B-1) and (B-2) are met, ignore the received timing advance command.
  • (C) When an Absolute timing advance command is received in reply to an MSGA transmission containing a C-RNTI MAC control element, (1) apply the timing advance command to the PTAG and (2) apply the timing advance command to the PTAG. Start or restart the time alignment timer.
  • (D-1) If the time alignment timer associated with the PTAG expires, some or all of the following processes (D-1-1) to (D-1-8) may be executed. .
  • (D-1-1) Flush all HARQ buffers of all serving cells.
  • D-1-2 If PUCCH is configured in any serving cell, notify the RRC entity of the terminal device that the PUCCH of all serving cells will be released.
  • (D-1-4) Clear all configured configured downlink assignments and configured uplink grants.
  • (D-1-5) Clear all PUSCH resources for semi-persistent CSI reporting.
  • (D-1-6) Assume that all running time alignment timers have expired.
  • (D-1-7) Maintain N_TA of all TAGs.
  • (D-1-8) If the time alignment timer of the PTAG of the deactivated secondary cell group expires, do not perform beam failure detection and/or recovery in cells of this secondary cell group.
  • (D-2) If the condition of (D-1) is not met and the time alignment timer associated with the STAG expires, for all serving cells belonging to this TAG, the following (D-2 Part or all of -1) to (D-2-6) may be performed.
  • (D-2-1) Flush all HARQ buffers.
  • D-2-2 If PUCCH has been set, notify the RRC entity of the terminal device that it will be released.
  • D-2-3) If SRS has been set, notify the RRC entity of the terminal device that it will be released.
  • D-2-4 Clear all configured downlink assignments and configured uplink grants.
  • D-2-5) Clear all PUSCH resources for semi-persistent CSI reporting.
  • D-2-6) Maintain N_TA of this TAG.
  • the MAC entity of the terminal device is When uplink transmission is stopped, it may be considered that the time alignment timer of the TAG associated with this SCell has expired.
  • the MAC entity of the terminal device When the time alignment timer associated with the TAG to which a certain SCell belongs is not running, the MAC entity of the terminal device does not perform transmission other than the random access preamble and MSGA transmission in this SCell. In addition, the MAC entity of the terminal does not perform any transmission other than the random access preamble and MSGA transmissions in the SpCell when the time alignment timer associated with the PTAG is not running.
  • FIG. 4 is a diagram showing an example flow of procedures for various settings in RRC according to the embodiment of the present invention.
  • FIG. 4 is an example flow when an RRC message is sent from the base station apparatus (eNB 102 and/or gNB 108) to the terminal apparatus (UE 122).
  • the base station device creates an RRC message (step S400).
  • the creation of the RRC message in the base station apparatus may be performed in order for the base station apparatus to distribute system information (SI) and paging information.
  • the creation of the RRC message in the base station apparatus may be performed so that the base station apparatus causes a specific terminal apparatus to perform processing.
  • the processing to be performed on a specific terminal device may include, for example, security-related settings, RRC connection reconfiguration, handover to a different RAT, RRC connection suspension, RRC connection release, and the like.
  • RRC connection reset processing includes, for example, radio bearer control (establishment, change, release, etc.), cell group control (establishment, addition, change, release, etc.), measurement setting, handover, security key update, etc. may be included.
  • the creation of the RRC message in the base station apparatus may be performed in response to the RRC message transmitted from the terminal apparatus.
  • the response to the RRC message sent from the terminal device may include, for example, a response to the RRC setup request, a response to the RRC reconnection request, a response to the RRC resume request, and the like.
  • the RRC message contains information (parameters) for various information notifications and settings. These parameters may be called fields and/or information elements and may be described using the ASN.1 (Abstract Syntax Notation One) notation scheme.
  • the base station device then transmits the created RRC message to the terminal device (step S402).
  • the terminal device performs processing such as setting according to the received RRC message, if necessary (step S404).
  • the terminal device that has performed the processing may transmit an RRC message for response to the base station device (not shown).
  • the RRC message is not limited to the above examples, and may be used for other purposes.
  • RRC on the master node side is used to transfer RRC messages for SCG side settings (cell group settings, radio bearer settings, measurement settings, etc.) to and from the terminal equipment. good.
  • SCG side settings cell group settings, radio bearer settings, measurement settings, etc.
  • E-UTRA RRC messages sent and received between eNB 102 and UE 122 may include NR RRC messages in the form of containers.
  • the NR RRC message transmitted and received between the gNB 108 and the UE 122 may include the E-UTRA RRC message in the form of a container.
  • RRC messages for SCG side configuration may be sent and received between the master node and the secondary node.
  • the RRC message for E-UTRA transmitted from eNB 102 to UE 122 may include the RRC message for NR, and the RRC message for NR transmitted from gNB 108 to UE 122 may be included.
  • the message may include an RRC message for E-UTRA.
  • Fig. 7 is an example of ASN.1 description representing fields and/or information elements related to radio bearer setup included in the message related to RRC connection reconfiguration in NR in Fig. 4.
  • Figure 8 is an example of ASN.1 description representing fields and/or information elements related to radio bearer setup included in the message related to RRC connection reconfiguration in E-UTRA in Figure 4.
  • ⁇ omitted> and ⁇ omitted> are not part of the ASN.1 notation, and other information is omitted. indicates that Information elements may be omitted even where there is no description of ⁇ omitted> or ⁇ omitted>.
  • the ASN.1 example in the embodiment of the present invention does not correctly follow the ASN.1 notation method.
  • the example of ASN.1 in the embodiment of the present invention is an example of notation of the parameters of the RRC message in the embodiment of the present invention, and other names and other notations may be used.
  • the ASN.1 example shows only examples of main information closely related to one aspect of the present invention in order to avoid complicating the explanation.
  • the parameters described in ASN.1 are all referred to as information elements without distinguishing between fields, information elements, etc. Further, in the embodiment of the present invention, fields described in ASN.1, information elements, etc. included in the RRC message may be called 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.
  • a master cell group (MCG) and a secondary cell group (SCG) are set by the above-described message regarding RRC connection reconfiguration.
  • MCG master cell group
  • SCG secondary cell group
  • Each cell group may consist of a special cell (SpCell) and zero or more other cells (secondary cells: SCells).
  • SpCell of MCG is also called PCell.
  • SpCell of SCG is also called PSCell.
  • Cell deactivation does not apply to SpCells, but may apply to SCells.
  • cell deactivation may not be applied to PCells, but may be applied to PSCells. In this case, cell deactivation may be performed differently for SpCells and SCells.
  • 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 by (A), (B), and/or (C) below.
  • C SCell state (sCellState) set for each SCell by an RRC message (SCell is activated based on the inclusion of the SCell state field in the SCell configuration)
  • the MAC entity of the terminal device may perform some or all of the following processing (AD) for each SCell set in the cell group.
  • AD processing
  • processing AD (1) If the RRC parameter (SCell state) is set to activated when the SCell is configured, or if a MAC CE that activates the SCell is received, the MAC entity of UE 122 processes (AD-1 )I do. Otherwise, if a MAC CE is received that deactivates the SCell, or if the SCell inactivity timer expires in an active SCell, the MAC entity of UE 122 takes action (AD-2).
  • the MAC entity of the terminal device may perform some or all of (1) to (3) below.
  • this SCell was in an inactive state before receiving a MAC CE that activates this SCell, or if the RRC parameters ( sCellState) is set to activated, the MAC entity of UE 122 performs processing (AD-1-1).
  • UE 122's MAC entity starts or restarts (if already started) the SCell inactivity timer associated with that SCell.
  • the Active DL BWP is not a Dormant BWP, the suspended Type 1 Configured Uplink Grant associated with this SCell according to the stored configuration. If present, the UE 122's MAC entity (re)initializes it. and) the MAC entity of UE 122 triggers the PHR.
  • the MAC entity of the terminal device may perform some or all of (1) to (3) below. (1) If the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) set in the RRC message for that SCell is not set to Dormant BWP, the MAC of UE 122 The entity performs processing (AD-1-1-1).
  • the MAC of UE 122 If the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) set in the RRC message for that SCell is set to Dormant BWP, the MAC of UE 122 The entity stops this serving cell's BWP-Inactivity Timer (bwp-InactivityTimer) if it is running. (3) The MAC entity of UE 122 receives the downlink BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) configured in the RRC message for that SCell and the first active uplink BWP identifier. Activate the uplink BWP indicated by (firstActiveUplinkBWP-Id).
  • the MAC entity of the terminal device may activate the SCell at predetermined timing and apply (execute) normal SCell operations including some or all of (A) to (E) below.
  • SRS Sounding Reference Signal
  • B Channel State Information
  • C PDCCH monitoring for this SCell
  • D PDCCH monitoring for this SCell (etc.) (if scheduling for this SCell is done in the serving cell of (E) If PUCCH is configured, PUCCH transmission on this SCell
  • the MAC entity of the terminal device may perform some or all of (A) to (D) below.
  • the MAC entity of the terminal device may perform some or all of (A) to (D) below.
  • A) Do not transmit SRS on this SCell.
  • B) Do not report CSI for this SCell.
  • C) Do not transmit PUCCH, UL-SCH and/or RACH on this SCell.
  • D) Do not monitor the PDCCH of this SCell and/or the PDCCH for this SCell.
  • the SCell is activated and deactivated by the processing (AD) performed by the MAC entity.
  • the initial state of the SCell may be set by an RRC message.
  • the SCell inactivity timer will be explained.
  • the value of the SCell inactivity timer (information regarding the time when the timer is considered to have expired) may be notified by the RRC message.
  • the time notified without stopping the timer after starting or restarting the timer in the above process (AD) (here 40ms) has elapsed, the timer is considered expired.
  • the SCell deactivation timer may also be a timer named sCellDeactivationTimer.
  • bandwidth part (BWP)
  • the BWP may be part or all of the bandwidth of the serving cell.
  • a BWP may also be called a carrier BWP.
  • a terminal device may be configured with one or more BWPs.
  • a certain BWP may be set by information included in the broadcast information associated with the synchronization signal detected in the initial cell search.
  • a certain BWP may be a frequency bandwidth associated with a frequency for initial cell search.
  • Some BWPs may also be configured with RRC signaling (eg Dedicated RRC signaling).
  • the downlink BWP (DL BWP) and the uplink BWP (UL BWP) may be set individually. Also, one or more uplink BWPs may be associated with one or more downlink BWPs. Further, the association between the uplink BWP and the downlink BWP may be a default association, may be an association by RRC signaling (for example, Dedicated RRC signaling), or may be associated by physical layer signaling (for example, downlink The association may be based on downlink control information (DCI) notified by a control channel, or a combination thereof.
  • DCI downlink control information
  • a BWP may consist of a group of consecutive physical radio blocks (PRB: Physical Resource Block). Also, parameters of the BWP (one or more BWPs) of each component carrier may be set for the terminal device in the connected state.
  • PRB Physical Resource Block
  • the BWP parameters for each component carrier include (A) the type of cyclic prefix, (B) the subcarrier spacing, (C) the frequency position of the BWP (e.g., the start position or center frequency position on the low frequency side of the BWP) (
  • the frequency position for example, ARFCN may be used, or an offset from a specific subcarrier of the serving cell may be used.
  • the offset unit may be a subcarrier unit or a resource block unit. 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.
  • the location frequency location, for example, ARFCN may be used, or an offset from a specific subcarrier of the serving cell may be used.
  • the offset unit may be a subcarrier unit or a resource block unit. Also, both ARFCN and offset may be set. ), may be included in part or in whole. Also, 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 transmit and receive in an active BWP (Active BWP) out of one or more set BWPs.
  • active BWP active BWP
  • BWP may be set.
  • the activated downlink BWP is also called Active DL BWP.
  • the activated uplink BWP is also called Active UL BWP.
  • One or more BWPs may be configured in one serving cell. BWP switching in the serving cell is used to activate deactivated BWPs (also referred to as inactive BWPs) and deactivate activated BWPs.
  • deactivated BWPs also referred to as inactive BWPs
  • BWP switching is controlled by the MAC entity itself for PDCCH indicating downlink assignment or uplink grant, BWP inactivity timer, RRC signaling, or initiation of random access procedures.
  • Active BWP of the serving cell is indicated by RRC or PDCCH.
  • a dormant BWP Entering a dormant BWP or leaving a dormant BWP is done by BWP switching. This control is performed by the PDCCH for each SCell or for each group called Dormancy SCell Group. Configuration of dormant SCell groups is indicated by RRC signaling. Also, in the current specification Dormant BWP applies only to SCells. Note that a dormant BWP does not change a certain BWP to a dormant state, but may be interpreted as one BWP set for dormancy among one or more BWPs set for the UE. . Also, there may be a plurality of BWPs set in the UE for sleep.
  • a certain BWP is a dormant BWP may be indicated by not including a specific parameter in the BWP configuration.
  • the PDCCH-Config information element which is an information element for setting UE-specific (Specific) PDCCH parameters, included in the configuration of the downlink BWP, it is determined that the BWP is a dormant BWP. can be shown.
  • some of the parameters included in the PDCCH-Config information element which is an information element for configuring UE-specific PDCCH parameters included in the downlink BWP configuration, are not configured (not included). ) to indicate that the BWP is a dormant BWP.
  • some or all of the search space settings that define where and/or how to search for PDCCH candidates are configured by the PDCCH-Config information element as a BWP configuration. Not set (not included) may indicate that the BWP is a dormant BWP.
  • SpCells such as PCells and PSCells and settings of dormant BWPs for PUCCH SCells that can transmit PUCCH may not be supported.
  • a UE that has received a PDCCH indicating to exit from a dormant BWP outside a certain set period (active time) in SpCell uses the downlink BWP indicated by the first downlink BWP identifier notified in advance by RRC signaling. Activate.
  • a UE that has received a PDCCH in SpCell indicating that it will leave a dormant BWP within a certain set period (active time) uses the downlink BWP indicated by the second downlink BWP identifier notified in advance by RRC signaling. Activate.
  • a UE that receives a PDCCH indicating entry into a dormant BWP activates the downlink BWP indicated by the third downlink BWP identifier (dormantDownlinkBWP-Id) previously notified by RRC signaling.
  • Entry into and exit from the above-mentioned dormant BWP is performed by BWP switching, and when activating a new BWP, the previously active BWP is deactivated. That is, when exiting a dormant BWP, the dormant BWP is deactivated, and when entering a dormant BWP, the dormant BWP is activated.
  • a UE configured with discontinuous reception (DRX) in SpCell may monitor PDCCH in Active BWP of SpCell to detect a certain DCI format (e.g. DCI format 2_6) outside DRX active time. good.
  • the DCI format CRC may be scrambled with a certain RNTI (eg PS-RNTI).
  • a UE with a dormant SCell group set determines whether to switch to Active DL BWP based on the bitmap information included in the DCI format 2_6 payload. For example, if a bit in the bitmap is associated with one dormant SCell group and the bit is 1, if the Active DL BWP is a dormant BWP, perform a BWP switch to another preset BWP, If an Active DL BWP is not a dormant BWP, it may stay on that BWP. A BWP switch may also be performed such that if the bit is 0, the Active DL BWP becomes the Dormant BWP.
  • UE does not have to monitor PDCCH for the purpose of detecting DCI format 2_6 during DRX active time.
  • a UE configured for discontinuous reception (DRX) in SpCell may monitor PDCCH in Active BWP of SpCell to detect certain DCI formats (for example, DCI formats 0_1 and 1_1) during DRX active time.
  • the DCI format CRC may be scrambled with an RNTI (eg, C-RNTI or MCS-C-RNTI).
  • RNTI eg, C-RNTI or MCS-C-RNTI.
  • a UE in which a dormant SCell group is set determines switching of Active DL BWP based on the bitmap information included in the payload of DCI format 0_1 or DCI format 1_1.
  • a bit in the bitmap is associated with one dormant SCell group and the bit is 1, if the Active DL BWP is a dormant BWP, perform a BWP switch to another preset BWP, If an Active DL BWP is not a dormant BWP, it may stay on that BWP.
  • a BWP switch may also be performed such that if the bit is 0, the Active DL BWP becomes the Dormant BWP.
  • the "another preset BWP" may be a BWP different from the "another preset BWP" used in the description of the DCI format 2_6.
  • the UE does not have to monitor PDCCH for the purpose of detecting DCI format 0_1 and DCI format 1_1 outside the DRX active time.
  • Monitoring the PDCCH indicating exiting the dormant BWP means monitoring the PDCCH for detection of DCI format 2_6 outside the DRX active time, and DCI format 0_1 and DCI format 1_1 during the DRX active time. monitoring of the PDCCH for the purpose of detecting
  • the MAC entity shall, if the BWP is activated (is an Active BWP) and that BWP is not a dormant BWP, any of (A) through (H) below: Or you can do it all.
  • A Transmit UL-SCH on that BWP.
  • B If a PRACH occasion is configured, send RACH on that BWP.
  • C Monitor the PDCCH on that BWP.
  • D If PUCCH is configured, transmit PUCCH on that BWP.
  • E Report CSI on its BWP.
  • SRS If SRS is configured, send SRS on that BWP.
  • G Receive DL-SCH on that BWP.
  • H Initialize configured uplink grants of grant type 1 that have been set and suspended in that BWP.
  • the MAC entity shall, if the BWP is activated (is an Active BWP) and that BWP is a dormant BWP, one of (A) through (G) below: You can do part or all.
  • A Stop the BWP inactivity timer for the serving cell of this BWP if it is running.
  • B Do not monitor PDCCH for that BWP.
  • C Do not monitor the PDCCH for that BWP.
  • D Do not receive DL-SCH on that BWP.
  • F Do not send SRS on that BWP.
  • G Do not transmit UL-SCH on that BWP.
  • the MAC entity may do some or all of (A) through (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 Do not report CSI on that BWP.
  • F Do not send SRS on that BWP.
  • G Do not receive DL-SCH on that BWP.
  • H Clear the configured uplink grant of grant type 2 set in that BWP.
  • I Suspend the configured uplink grant of grant type 1 for that deactivated BWP (inactive BWP).
  • the MAC entity may perform some or all of the following (A) through (E) on selected carriers of this serving cell.
  • (A) If the PRACH transmission resource (occasion) is not set for the Active UL BWP, (A1) switch the Active UL BWP to the BWP indicated by the RRC parameter (initialUplinkBWP), and (A2) If the serving cell is a SpCell, switch the Active UL BWP to the BWP indicated by the RRC parameter initialDownlinkBWP.
  • the MAC entity performs the following processing (A) for each activated serving cell for which the BWP inactivity timer is set.
  • the BWP inactivity timer may also be a timer named bwp-InactivityTimer.
  • A-1) if, in Active DL BWP, received PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant, or if for Active DL BWP received a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant, or if a MAC PDU was sent with a configured uplink grant or if a configured If a MAC PDU is received for downlink allocation, the MAC entity performs the following (A-1-1) processing.
  • A-1-1-1 If the random access procedure associated with this serving cell is not in progress, or if the random access procedure in progress associated with this serving cell is received by the PDCCH addressed to the C-RNTI Once successfully completed, start or restart the BWP inactivity timer associated with the Active DL BWP.
  • A-2) If the BWP inactivity timer associated with the Active DL BWP expires (Expire), the MAC entity performs the following processing (A-2-1).
  • A-2-1 If defaultDownlinkBWP-Id is set, BWP switching is performed to BWP indicated by this defaultDownlinkBWP-Id, otherwise BWP switching is performed to initialDownlinkBWP.
  • the MAC entity may perform the following processing (A).
  • A If the default downlink BWP identifier (defaultDownlinkBWP-Id) is set, 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 not the BWP indicated by Id, start or restart the BWP inactivity timer associated with the Active DL BWP.
  • defaultDownlinkBWP-Id defaultDownlinkBWP-Id
  • RLF Radio Link Failure
  • the terminal device receives the value (t310 or t313) of the timer (for example, T310 or T313) for detecting physical layer problems of the serving cell from the serving base station device, the value (t310 or t313), out of synchronization (OoS: out- of?sync) detection count thresholds N310 and N313, and synchronization (IS: in?sync) detection count thresholds N311 and N314, etc. are acquired from broadcast information and RRC messages for individual users. . Also, default values may be set for the timer value and the threshold for the number of times. Also, the name of the timer may be different between EUTRA and NR.
  • the threshold Qout is the block error rate of a hypothetical downlink control channel (PDCCH) transmission that the downlink radio link cannot reliably receive and also based on predetermined parameters.
  • (Block error rate) may be defined as the level at which the first specified percentage.
  • the threshold Qin is set so that the downlink radio link quality can be received more reliably than in a state of Qout when the downlink radio link quality is significantly higher, and furthermore, the block error rate of transmission of the hypothetical downlink control channel based on predetermined parameters is the second It may be defined as a level that is a specific percentage of two.
  • a plurality of block error rates may be defined based on the frequencies used, subcarrier intervals, service types, and the like.
  • the first specific percentage and/or the second specific percentage may be default values defined in the specification.
  • the first specific ratio and/or the second specific ratio may be values notified or broadcast from the base station apparatus to the terminal apparatus.
  • a terminal device may perform radio link monitoring using a certain type of reference signal (eg, cell-specific reference signal (CRS)) in a serving cell (eg, PCell and/or PSCell). Also, the terminal device receives from the base station device a configuration (radio link monitoring configuration: RadioLinkMonitoringConfig) indicating which reference signal is to be used for radio link monitoring in the serving cell (for example, PCell and/or PSCell), and sets one or Radio link monitoring may be performed using multiple reference signals (referred to herein as RLM-RS). Also, the terminal device may perform radio link monitoring using other signals.
  • the physical layer processing unit of the terminal device may notify the upper layer that synchronization is in progress when the conditions for being in synchronization are satisfied in the serving cell (for example, PCell and/or PSCell).
  • the monitoring setting: RadioLinkMonitoringConfig may be set for each downlink BWP.
  • a terminal device may perform radio link monitoring based on monitoring settings configured for a BWP that is an Active DL BWP.
  • a terminal device may perform radio link monitoring based on a monitoring setting set for a default BWP or a BWP designated by a base station device under specific conditions.
  • the radio link monitoring setting may include information indicating the purpose of monitoring and identifier information indicating the reference signal.
  • monitoring purposes may include monitoring radio link failures, beam failures, or both.
  • the identifier information indicating the reference signal may include information indicating the identifier (SSB-Index) of the synchronization signal block (SSB) of the cell. That is, the reference signal may include the synchronization signal.
  • identifier information indicating a reference signal may include information indicating an identifier associated with a channel state information reference signal (CSI-RS) configured in a terminal device.
  • CSI-RS channel state information reference signal
  • the RRC layer processing unit of the terminal device starts (Start) or restarts (Start) or restarts ( Restart).
  • the RRC layer processing unit of the terminal device may stop the timer (T310) when receiving the synchronizing signal continuously for a predetermined number of times (N311 times).
  • the timer (T310) expires, the RRC layer processing unit of the terminal device may transition to the idle state or execute the RRC connection re-establishment procedure.
  • the operation of the terminal device may differ depending on the AS Security establishment state. If AS Security has not been established, the terminal device transitions to the RRC IDLE state, and if AS Security has already been established, the terminal device may perform an RRC connection re-establishment procedure. Further, in determining whether to start or restart the timer T310, it may be added as a condition that none of a plurality of specific timers is running.
  • the RRC layer processing unit of the terminal device starts (Start) the timer (T313) when continuously receiving out of synchronization notified from the physical layer processing unit a predetermined number of times (N313 times) or It may be restarted.
  • the RRC layer processing unit of the terminal device may stop the timer (T313) when receiving synchronizing messages continuously for a predetermined number of times (N314 times).
  • the RRC layer processing unit of the terminal device may execute an SCG failure information procedure for notifying the network of the SCG failure when the timer (T313) expires.
  • SCG failure is also referred to as SCG failure.
  • the SCG failure information procedure is also referred to as the SCG failure information procedure.
  • the RRC layer processing unit of the terminal device when the RRC layer processing unit of the terminal device receives out of synchronization notified from the physical layer processing unit in each SpCell a predetermined number of times (N310 times) consecutively
  • the SpCell timer (T310) may be started (Start) or restarted (Restart).
  • the RRC layer processing section of the terminal device may stop the timer (T310) of the SpCell when receiving a predetermined number of consecutive times (N311 times) in each SpCell.
  • the RRC layer processing unit of the terminal device When the timer (T310) of each SpCell expires (Expire), the RRC layer processing unit of the terminal device, if the SpCell is a PCell, transitions to the idle state or performs a re-establishment procedure of the RRC connection. good too. Also, if the SpCell is a PSCell, an SCG failure information procedure for notifying the network of an SCG failure may be executed.
  • the RRC layer processing unit of the terminal device timer may be started.
  • the RRC layer processing unit of the terminal device may stop the timer (T314) if it receives a predetermined number of times (N311 times) consecutively while T314 is running.
  • the RLM-RS may be undefined if not explicitly or implicitly set from the network.
  • a terminal device may perform radio link monitoring using a reference signal that meets predetermined conditions when RLM-RS is not set by a network (for example, a base station device).
  • the RLM-RS is a reference signal used in radio link monitoring, and multiple RLM-RSs may be configured in the terminal device.
  • One RLM-RS resource may be one SS block or one CSI-RS resource (or port).
  • radio link monitoring using CRS may be performed in EUTRA cells and radio link monitoring using RLM-RS may be performed in NR cells, but the present invention is not limited to this.
  • the terminal device In the MCG, the terminal device is notified of a random access problem from the MAC layer of the MCG when the timer T310 expires, when the timer T312 expires, or when none of a plurality of specific timers is running. or when it is notified from the RLC layer of the MCG that the maximum number of retransmissions of the SRB or DRB has been reached, the terminal device determines that a radio link failure has been detected in the MCG.
  • the specific timers do not include timer T310 and timer T312.
  • the terminal device determines that a radio link failure has been detected in the SCG.
  • the specific timers do not include timer T310 and timer T312.
  • the problem of random access is that when the number of retransmissions of the random access preamble reaches a predetermined number in the MAC entity, if the random access preamble transmission is performed in the SpCell, the MAC entity of the cell group containing the SpCell to the higher layer (here the RRC entity).
  • the terminal device When the terminal device determines that a wireless link failure has been detected in the MCG, it stores various information as wireless link failure information. Then, if AS security is not activated, it sets the release reason to "Other" and starts the process of leaving RRC_CONNECTED. If AS security is activated, initiate the RRC connection re-establishment procedure.
  • the terminal device determines that a radio link failure has been detected in the SCG, and starts processing to report relevant information as an SCG radio link failure to the base station device.
  • beam failure recovery procedures may be configured by RRC for each serving cell. Beam failure is detected by counting beam failure instance notifications signaled to the MAC entity from lower layers (PHY layer). The MAC entity may perform some or all of (A), (B), and (C) below in each serving cell for beam failure detection.
  • A If a beam failure instance notification is received from the lower layer, start or restart a timer (beamFailureDetectionTimer) and increment a counter (BFI-COUNTER) by one. If the value of BFI_COUNTER is equal to or greater than the set threshold (beamFailureInstanceMaxCount), the following processing (A-1) is performed.
  • A-1) If the serving cell is a SCell, trigger beam failure recovery (BFR) for this serving cell, else initiate a random access procedure on the SpCell.
  • BFR beam failure recovery
  • B) Set BFI_COUNTER to 0 if the beamFailureDetectionTimer for this serving cell has expired or if the beamFailureDetectionTimer, beamFailureInstanceMaxCount, and/or the reference signal settings for beam failure detection have been changed by upper layers.
  • C If the serving cell is a SpCell and the random access procedure (procedure) is successfully completed, set BFI_COUNTER to 0 and stop the timer (beamFailureRecoveryTimer) to indicate that the beam failure recovery procedure has been successfully completed. I reckon.
  • the serving cell is a SCell and is addressed to a C-RNTI indicating a new uplink grant to transmit information for beam failure recovery of the SCell (e.g. information contained in the SCell BFR MAC CE)
  • a C-RNTI indicating a new uplink grant to transmit information for beam failure recovery of the SCell
  • the PDCCH is received or if the SCell is in inactive state, set BFI_COUNTER to 0, consider the beam failure recovery procedure to be successfully completed, and all beam failure recovery triggered for this serving cell ( BFR).
  • the MAC entity performs (A) below.
  • the UL-SCH resource can include the BFR MAC CE of the SCell and its subheader considering the priority of the logical channel, then the BFR MAC CE of the SCell and its subheader are included. Otherwise, if the UL-SCH resource can contain the SCell's truncated BFR MAC CE and its subheaders considering the logical channel priority, then the SCell's truncated BFR MAC CE and its Include subheaders. Otherwise, trigger a scheduling request for SCell beam failure recovery.
  • the SCell's dormancy is achieved by activating the dormant BWP in this SCell. Also, even when the SCell is in a dormant state, CSI measurement, automatic gain control (AGC), and beam control (beam management) including beam failure recovery may be performed in this SCell.
  • AGC automatic gain control
  • beam control beam management
  • FIG. 9 to 13 are examples of ASN.1 descriptions representing fields and/or information elements related to the addition of SCG PSCells and zero or more SCells, which are included in messages related to RRC connection reconfiguration in NR. .
  • the messages and/or information elements in each figure differ from the actual message structure and/or information element structure, and some structured fields and information elements are expanded. and/or omit fields or information elements not directly relevant to the description.
  • an RRC reconfiguration message may be used to add the SCG PSCell and zero or more SCells.
  • the RRC reconfiguration message may include some or all of the information (A) to (E) below. Also, the RRC reconfiguration message may include other information.
  • E RRC configuration of secondary cell group in MR-DC (mrdc-SecondaryCellGroupConfig)
  • the SCG setting may be notified by the above (C) setting of the RRC Reconfiguration message.
  • the SCG configuration is the RRC reconfiguration generated by the secondary node, included in the above (E) of the RRCReconfiguration message generated by the master node. May be notified by message.
  • the SCG setting may be notified by the above setting (C) included in the RRC reconfiguration message generated by the secondary node.
  • another message may be used for setting up the SCG.
  • the configuration of the above secondary cell group may be given in a cell group configuration information element (CellGroupConfigIE).
  • CellGroupConfigIE CellGroupConfig Information element
  • the cell group setting information element may include some or all of the following information (A) to (H). Also, the cell group setting information element may contain other information.
  • A Cell group identifier (cellGroupId)
  • B Settings for adding and/or modifying RLC bearers (rlc-BearerToAddModList)
  • C Setting for RLC bearer release (rlc-BearerToReleaseList)
  • D MAC configuration for this cell group (mac-CellGroupConfig)
  • E PHY configuration for this cell group (physicalCellGroupConfig)
  • F SpCell configuration (spCellConfig)
  • G Settings for adding and modifying SCells (sCellToAddModList)
  • H Setting for SCell release (sCellToReleaseList)
  • SpCells may be added and/or set by the SpCell settings in (F) above, and SCells may be added, modified, and/or released by the settings in (G) and (H) above. They may also be done by other messages.
  • the above SpCell settings may include some or all of the following information (A) to (D).
  • the SpCell configuration may also include other information.
  • the above information element of reset with synchronization may include some or all of the following information (A) to (D). Further, the reset information with synchronization may include other information.
  • A SpCell cell-specific parameter configuration (spCellConfigCommon)
  • B New terminal identifier (UE-Identity) value (newUE-Identity)
  • C Timer T304 value (t304)
  • D RACH terminal device specific parameter setting (rach-ConfigDedicated)
  • the setting of the RACH terminal device-specific parameters described above may include parameters (CFRA) used for contention-free random access. Note that if this CFRA is not included in the configuration, the terminal device may perform contention-based random access in a random access procedure. CFRA may include RA Occasion information used in collision-free random access.
  • the information element (ServingCellConfig IE) indicating the configuration of the SpCell terminal device-specific parameter may include some or all of the following information (A) to (C).
  • the above initial downlink BWP information is a setting for a terminal device-specific (UE-Specific) initial downlink BWP (BWP identifier #0). If any optional IE is included in this initial downlink BWP information and configured, the terminal device may consider BWP identifier #0 to be the BWP configured by RRC.
  • the identifier of the first active downlink BWP is activated when performing the RRC reconfiguration including this information (Upon performing the RRC reconfiguration). This is the identifier of the downlink BWP to be activated. Also, when the identifier information of the first active downlink BWP is set for the SCell, the downlink BWP indicated by this identifier information is activated when the SCell is activated. Also, when the identifier information of the first active downlink BWP is set for the SpCell, the downlink BWP of the SpCell indicated by this identifier information may be activated when the SCG is activated.
  • the identifier information of the first active uplink BWP may be set in the terminal device.
  • the identifier information of the first active downlink BWP may be configured in the terminal device in the same information element as the identifier information of the first active downlink BWP or in a different information element.
  • the BWP identifier set in the identifier information of the first active downlink BWP and the BWP identifier set in the identifier information of the first active uplink BWP may be the same value or may be different values.
  • the uplink BWP of the SpCell indicated by this identifier information may be activated when the SCG is activated.
  • the BWP identifier set in the identifier information of the first active downlink BWP and the BWP identifier set in the identifier information of the first active uplink BWP may have the same value.
  • the configuration of cell-specific parameters of the SpCell above may be given by an information element (ServingCellConfigCommon IE) used to configure the cell-specific parameters of the serving cell.
  • Information elements used to configure cell-specific parameters of the serving cell may include some or all of the following information (A) to (D), as shown in FIG. Other information may also be included in the information element used to configure cell-specific parameters for the serving cell.
  • A Physical cell identifier (physCellId)
  • B Common downlink parameters in cells (downlinkConfigCommon)
  • C Common uplink parameters in cells (uplinkConfigCommon)
  • D Configuration of SCell terminal device-specific parameters (including some cell-specific parameters)
  • sCellConfigDedicated (E) SSB subcarrier spacing information (ssbSubcarrierSpacing)
  • Downlink common parameters in a cell may include downlink frequency information (frequencyInfoDL) and/or initial downlink BWP information (initialDownlinkBWP).
  • the downlink frequency information may include information on the SSB frequency used in this serving cell.
  • SCellConfigIE SCell configuration information elements
  • the SCell configuration information element may include some or all of the following information (A) to (D). Also, the SCell configuration information element may include other information.
  • A Identifier for identifying SCell (sCellIndex)
  • B SCell cell-specific parameter configuration (sCellConfigCommon)
  • C Configuration of SCell terminal device-specific parameters (including some cell-specific parameters)
  • sCellConfigDedicated (D) Information indicating SCell activation/deactivation (sCellState-r16)
  • the RRC entity of the terminal device that has received the RRCReconfiguration message may perform some or all of (A) to (F) below.
  • a terminal device that receives the RRCReconfiguration message may perform other processing.
  • radioBearerConfig is included in RRCReconfiguration, configure radio bearers based on this radioBearerConfig.
  • D Set the content to be included in the RRC reconfiguration complete message.
  • the RRC entity of the terminal device may perform some or all of (A) to (G) below.
  • SCG transmission for all radio bearers is resumed if suspended.
  • C If the CellGroupConfig contains rlc-BearerToAddModList, perform RLC bearer addition and/or modification based on this rlc-BearerToAddModList.
  • D If CellGroupConfig contains mac-CellGroupConfig, configure the MAC entity of this cell group based on this mac-CellGroupConfig.
  • E If sCellToReleaseList is included in CellGroupConfig, release the SCell based on this sCellToReleaseList.
  • F If spCellConfig is included in CellGroupConfig, set SpCell based on this spCellConfig.
  • G If CellGroupConfig contains sCellToAddModList, then perform SCell addition and/or modification based on this sCellToAddModList.
  • the RRC entity of the terminal device may perform some or all of (A) to () below.
  • A) If AS security is not activated, execute processing to transition to RRC_IDLE and terminate the procedure.
  • B) Start timer T304 for the SpCell (to be configured) using the value of t304 included in reconfigurationWithSync.
  • C) If downlink frequency information (frequencyInfoDL) is included in reconfigurationWithSync, the cell indicated by the physical cell identifier (physCellId) included in reconfigurationWithSync in the SSB frequency indicated by frequencyInfoDL is the target SpCell. I judge.
  • D If downlink frequency information (frequencyInfoDL) is not included in reconfigurationWithSync, the cell indicated by the physical cell identifier (physCellId) included in reconfigurationWithSync in the SSB frequency of the original SpCell (Source SpCell), Determine that it is the target SpCell.
  • E Start downlink synchronization of the target SpCell.
  • F Acquire the MIB of the target SpCell.
  • G If no specific bearer (DAPS bearer) has been configured. Execute some or all of (1) to (4) below. (1) reset the MAC entity for this cell group; (2) If a SCell not included in SCellToAddModList is set in this cell group, this SCell is made inactive. (3) apply the value of newUE-Identity as the C-RNTI for this cell group; (4) Configure lower layers based on the received spCellConfigCommon.
  • timer T304 may exist for each cell group.
  • the RRC message may notify the value of a certain timer (here, timer T304) (time information when the timer expires). For example, if information indicating 1000ms as the value of the timer is notified by the RRC message, if the notified time (1000ms in this example) passes without stopping the timer after starting or restarting the timer, You can assume that the timer has expired.
  • the terminal device may start the timer T304 of the cell group to which the reconfigurationWithSync setting is applied based on the reception of the RRC reconfiguration message including reconfigurationWithSync.
  • the terminal device may stop the timer T304 of the cell group to which the reconfigurationWithSync setting is applied based on the successful completion of random access to the target SpCell indicated by reconfigurationWithSync.
  • the terminal device may stop the timer T304 of the SCG based on the release of the SCG.
  • the terminal device may execute the RRC connection re-establishment procedure if the MCG timer T304 expires and a specific bearer (DAPS bearer) is not set.
  • DAPS bearer a specific bearer
  • the terminal device may notify the network of the failure of reconfiguration with synchronization by starting the SCG failure information procedure when the SCG timer T304 expires.
  • the RRC entity of the terminal device performs the following processing (A) if the MCG transmission is not suspended, and performs the following processing (B ).
  • This procedure may be referred to as the SCG failure information procedure.
  • This procedure may be used to inform the E-UTRAN or NR master node about the SCG failure experienced by the terminal equipment.
  • the RRC entity of the terminal device initiates this procedure to report SCG failure when MCG or SCG transmission is not suspended and any of the following conditions (A) to (D) are met: You can (A) Detected SCG radio link failure (B) Detected failure of SCG configuration with synchronization (C) Detected failure of SCG configuration (D) Integrity check on SRB3 from lower layer of SCG check) failure was notified
  • the RRC entity of the terminal device initiating this procedure performs some or all of the following (A) to (E).
  • SCGFailureInformation SCG Failure Information
  • the RRC lower layer of the terminal device may transmit the SCG failure information (SCGFailureInformation) message to the base station device.
  • SCGFailureInformation SCG failure information
  • the base station apparatus uses an RRC reconfiguration message of RRC signaling (radio resource control signal) (included in the RRC reconfiguration message) to the terminal device to provide measurement configuration information.
  • Send elements also called measurement settings.
  • the terminal device performs measurement, event evaluation, and measurement reporting for the serving cell and neighboring cells (including listed cells and/or detected cells) according to the information included in the notified measurement configuration.
  • a list cell is a cell listed as a measurement object (a cell notified from the base station apparatus to the terminal apparatus as a neighboring cell list).
  • a detected cell is a cell that is detected by the terminal equipment at the frequency and subcarrier interval indicated by the measurement object but is not listed in the measurement object (the terminal equipment itself that is not notified as a neighbor cell list). detected cells).
  • the measurement configuration for the MCG is included in the first RRC reconfiguration message, and the field indicating information about the SCG of the MR-DC included in the first RRC reconfiguration message contains the encapsulated SCG
  • An RRC reconfiguration message (second RRC reconfiguration message) is included, and the second RRC reconfiguration message may include the measurement configuration for the SCG.
  • the first RRC reconfiguration message notifying the MCG measurement configuration and the first RRC reconfiguration message notifying the SCG measurement configuration may be the same RRC reconfiguration message, or at different timings. It may be a different RRC reconfiguration message to be notified.
  • the MCG measurement configuration may be notified in SRB1, and the SCG measurement configuration may be notified in SRB3.
  • the terminal device may have a variable VarMeasConfig to hold the notified measurement settings. Also, the terminal device may have a variable VarMeasReportList to hold the measurement information that meets the report conditions. The terminal device may be notified of the measurement configuration for each cell group.
  • a variable VarMeasConfig for holding each measurement setting set for each cell group (or for a cell group, or linked to a cell group) and for holding measurement information that matches the reporting conditions of each measurement setting. variables VarMeasReportList, and for each cell group.
  • Measurements include three types (intra-frequency measurements, inter-frequency measurements, inter-radio access technology measurements).
  • Intra-frequency measurements are measurements at the same subcarrier spacing as the serving cell in the serving cell's downlink frequency (downlink frequency).
  • Inter-frequency measurements are measurements at frequencies different from the downlink frequency of the serving cell, or at different subcarrier spacings on the same frequency.
  • Inter-radio access technology measurements are measurements in a different radio technology (eg UTRA, GERAN, CDMA2000, E-UTRA, etc.) than the radio technology (eg NR) of the serving cell.
  • Measurement configuration includes add and/or modify list of measurement identifiers (measId), delete list of measurement identifiers, add and/or modify list of measurement objects, delete list of measurement objects, and reporting configurations. , a list of deletions of reporting configurations, a quantity configuration (quantityConfig), a measurement gap configuration (measGapConfig), and a serving cell quality threshold (s-Measure) configuration.
  • the quantity configuration (quantityConfig) specifies the third layer filter coefficient (L3 filtering coefficient) when the measurement objects (Measurement objects) are NR and/or E-UTRA.
  • the third layer filter coefficient (L3 filtering coefficient) defines the ratio (percentage) between the latest measurement result and the past filtering measurement result.
  • the filtering result is used for event evaluation in the terminal device.
  • the measurement gap configuration (measGapConfig) includes information on the length and cycle of measurement gaps.
  • the measurement gap setting may be set independently for each terminal device or for each predetermined frequency range.
  • the measurement identifier (measId) is used to associate (or associate or link) measurement objects and reporting configurations, specifically, the measurement object identifier ( measObjectId) and the report configuration identifier (reportConfigId).
  • a measurement identifier (measId) is associated with one measurement object identifier (measObjectId) and one report configuration identifier (reportConfigId).
  • Measurement configurations can be added/modified/deleted in relation to measurement identifiers (measId), measurement objects (Measurement objects), and reporting configurations.
  • the measurement identifier deletion list included in the measurement configuration includes the measurement identifier list, and the terminal device performs the following (A) to (C) for each measurement identifier included in the measurement identifier deletion list. process.
  • (A) Delete the entry of this measurement identifier from the variable VarMeasConfig of the cell group subject to measurement configuration.
  • (B) Delete the measurement report entry for this measurement identifier from the variable VarMeasReportList of the cell group subject to measurement configuration, if it is included.
  • timer T321 is a timer that is started when a measurement configuration including a report configuration for the purpose of measuring the cell global identifier is received.
  • this timer is stopped when the identifier of the reporting configuration for the purpose of measuring the cell global identifier is included in the deletion list of the reporting configuration, which will be described later, or when the detected cell does not broadcast SIB1.
  • the measurement identifier addition and/or modification list included in the measurement configuration includes the measurement identifier list, and the terminal device shall perform the following for each measurement identifier included in the measurement identifier addition and/or modification list: Perform processing from (A) to (C). (A) If a measurement identifier entry matching this measurement identifier exists in the list of measurement identifiers contained in the variable VarMeasConfig of the cell group subject to the measurement configuration, the received value for this measurement identifier (the Replace the entry with the value received for this measId). Otherwise, add a new entry for this measurement identifier to the variable VarMeasConfig of the cell group subject to the measurement configuration.
  • the measurement object removal list (measObjectToRemoveList) included in the measurement configuration is a field containing information to remove the specified measurement object identifier (measObjectId) and the measurement objects corresponding to the specified measurement object identifier (measObjectId). is. At this time, all the measurement identifiers (measId) of the cell group subject to the measurement configuration associated with the specified measurement object identifier (measObjectId) may be deleted. This field can simultaneously specify multiple measurement object identifiers (measObjectId).
  • the measurement object addition and/or modification list (measObjectToAddModList) contained in the measurement configuration modifies the measurement objects specified by the measurement object identifier (measObjectId) or modifies the measurement objects specified by the measurement object identifier (measObjectId).
  • the report configuration deletion list (reportConfigToRemoveList) included in the measurement configuration is a field that contains information for deleting the specified reporting configuration identifier (reportConfigId) and the reporting configuration corresponding to the specified reporting configuration identifier (reportConfigId). is. At this time, all measurement identifiers (measId) associated with the specified report configuration identifier (reportConfigId) are deleted. This command can specify multiple report configuration identifiers (reportConfigId) at the same time.
  • the add and/or modify reporting configuration list modifies the reporting configurations specified by the reporting configuration identifier (reportConfigId) or modifies the reporting configurations specified by the reporting configuration identifier (reportConfigId).
  • the add and/or modify reporting configuration list modifies the reporting configurations specified by the reporting configuration identifier (reportConfigId) or modifies the reporting configurations specified by the reporting configuration identifier (reportConfigId).
  • the measurement identifier deletion list (measIdToRemoveList) is a command to delete the specified measurement identifier (measId).
  • the measurement target identifier (measObjectId)
  • the report configuration identifier (reportConfigId) associated with the specified measurement identifier (measId) are maintained without being deleted.
  • This command can specify multiple measurement identifiers (measId) at the same time.
  • the measurement identifier addition and/or modification list (measIdToAddModifyList) is modified to map the specified measurement identifier (measId) to the specified measurement object identifier (measObjectId) and the specified report configuration identifier (reportConfigId), or
  • This command associates the specified measurement object identifier (measObjectId) and the specified report configuration identifier (reportConfigId) with the specified measurement identifier (measId) and adds the specified measurement identifier (measId).
  • This command can specify multiple measurement identifiers (measId) at the same time.
  • Measurement objects are set (defined) for each RAT and frequency. Note that the measurement target may be set for each frequency and subcarrier interval when the RAT is NR. Also, reporting configurations may include a specification for NR and a specification for RAT other than NR.
  • Measurement objects include measurement object identifier (measObjectId), measurement object NR (measObjectNR) whose measurement object is NR, and measurement object EUTRA (measObjectEUTRA) whose measurement object is E-UTRA.
  • the measurement target is UTRA (measObjectUTRA) whose measurement target is UTRA, GERAN (measObjectGERAN) whose measurement target is GERAN, CDMA2000 (measObjectCDMA2000) whose measurement target is CDMA2000, and WLAN may include part or all of the WLAN to be measured (measObjectWLAN).
  • the measurement object identifier (measObjectId) is an identifier used to identify the settings of measurement objects.
  • the setting of measurement objects is specified for each radio access technology (RAT) and frequency, and for each subcarrier interval in NR, as described above. Measurement objects may be specified separately for E-UTRA, UTRA, GERAN, CDMA2000.
  • a measurement object NR (measObjectNR), which is a measurement object for NR, defines information that applies to the NR's serving cell and neighboring cells. It should be noted that which measurement target identifier corresponds to the serving cell is indicated by an information element (for example, serving cell configuration) included in the RRC message including the measurement configuration and/or the RRC message not including the measurement configuration. you can
  • Measurement object NR includes frequency information (ssbFrequency) of blocks (SSB) including synchronization signals, SSB subcarrier spacing (ssbSubcarrierSpacing), information on the list of cells to be measured, and information on the blacklist excluded from measurement. Some or all of the information, information about the whitelist to measure against, may be included.
  • Information on the list of cells to be measured includes information on event evaluations and cells subject to measurement reports.
  • the information about the list of cells to be measured includes physical cell IDs, cellIndividualOffsets (indicating measurement offset values applied to adjacent cells), and the like.
  • the reporting configurations include a reporting configuration identifier (reportConfigId) and a reporting configuration NR (reportConfigNR) associated with the reporting configuration identifier (reportConfigId).
  • a reporting configuration identifier is an identifier used to identify reporting configurations related to measurement.
  • the reporting configuration for measurement may include a specification for NR and a specification for RAT other than NR (part or all of UTRA, GERAN, CDMA2000, E-UTRA).
  • a reporting configuration NR (reportConfigNR), which is a reporting configuration for NR, defines event triggering criteria used for measurement reporting in NR.
  • the report configuration NR includes event identifier (eventId), trigger quantity (triggerQuantity), hysteresis (hysteresis), trigger time (timeToTrigger), report quantity (reportQuantity), maximum number of report cells (maxReportCells), report interval (reportInterval), the number of reports (reportAmount), part or all of them may be included.
  • event triggered reporting is a method of reporting measurements when event trigger conditions are met.
  • event triggered periodic reporting in which measurements are reported a certain number of times at regular intervals when event trigger conditions are met.
  • TriggerQuantity is the quantity used to evaluate the event trigger condition. That is, reference signal received power (RSRP) or reference signal received quality (RSRQ) is specified. That is, the terminal device measures the downlink synchronization signal using the quantity specified by this trigger quantity (triggerQuantity), and determines whether the event trigger condition specified by the event identifier (eventId) is satisfied. judge. Hysteresis is a parameter used in event trigger conditions. Trigger time (timeToTrigger) indicates the period in which the event trigger condition should be satisfied. ReportQuantity indicates the quantity reported in the measurement report.
  • RSRP reference signal received power
  • RSRQ reference signal received quality
  • the quantity specified by the trigger quantity (triggerQuantity), reference signal received power (RSRP) or reference signal received quality (RSRQ) is specified.
  • the maximum number of report cells (maxReportCells) indicates the maximum number of cells to be included in the measurement report.
  • the report interval (reportInterval) is used for periodic reporting or event triggered periodic reporting, and reports are performed periodically at intervals indicated by the report interval (reportInterval).
  • the number of reports (reportAmount) specifies the number of times that periodic reporting will be performed, if necessary.
  • threshold parameters and offset parameters (a1_Threshold, a2_Threshold, a3_Offset, a4_Threshold, a5_Threshold1, a5_Threshold2, a6_Offset, c1_Threshold, c2_Offset) used in the event trigger conditions are specified together with the event identifier (eventId) in the report configuration NR (reportConfigNR). , may be notified to the terminal device.
  • a plurality of event trigger conditions for measurement reports are defined, each of which has a joining condition and a leaving condition. That is, a terminal device that has satisfied the subscription condition for the event specified by the base station device transmits a measurement report to the base station device. Also, if the terminal device that has satisfied the leaving condition for the event specified by the base station device is set to trigger a report when the leaving condition is met by the base station device (if reportOnLeave is included in the report settings) ), a measurement report is transmitted to the base station apparatus.
  • reporting configuration InterRAT which is the reporting configuration for RATs other than NR, defines multiple event triggering criteria used for measurement reporting in RATs other than NR. For example, if the measurement result of neighboring cells (other RATs) is better than the threshold b1_Threshold set for each RAT after applying each parameter, event B1 occurs. In addition, if the PCell measurement result is worse than the threshold b2_Threshold1 after applying each parameter and the measurement result of the adjacent cell (other RAT) is better than the threshold b2_Threshold2 set for each RAT after applying each parameter, an event B2 occurs.
  • the base station apparatus may or may not notify the serving cell quality threshold (s-Measure).
  • a serving cell quality threshold (s-Measure) is set in the terminal device by the base station apparatus, and the quality (RSRP value) after Layer 3 filtering of the PCell, which is the serving cell, is higher than the serving cell quality threshold (s-Measure).
  • the serving cell quality threshold (s-Measure) is not set in the terminal apparatus by the base station apparatus, the terminal apparatus measures neighboring cells regardless of the quality (RSRP value) of the serving cell.
  • the terminal shall initiate the measurement reporting procedure when the event trigger condition is satisfied, when the first measurement result of the periodic report becomes available, when the timer for periodic reporting or timer T321 expires, etc. may start.
  • the purpose of the measurement report procedure is to transfer a measurement report from the terminal to the network.
  • the measurement report includes measurement results. A measurement result is set for each measurement identifier for which the measurement reporting procedure has been triggered.
  • a measurement result may include a measurement identifier (measId), a list of serving measurement target measurement results (measResultServingMO), and a neighboring cell measurement result (measResultNeighCellNR).
  • the neighbor cell measurement results may include either a list of NR measurement results or a list of E-UTRA measurement results.
  • the NR measurement result and the E-UTRA measurement result include some or all of the information of the physical cell identifier, the cell measurement result, and the cell global identifier.
  • the serving measurement object measurement result (measResultServingMO) is the measurement result of the measurement object associated with the serving cell, and may include some or all of the serving cell identifier, the serving cell measurement result, and the best neighbor cell measurement result. .
  • the measurement result as described above is set and SRB3 is set if the terminal is set to EN-DC. If yes, submit a measurement report message containing said measurement result to the lower layer for transmission through SRB3 and terminate the procedure; if SRB3 is not configured, send a measurement report message to the E-UTRA RRC message. It is encapsulated (embedded) and submitted to the lower layer through the E-UTRA MCG.
  • the terminal device is configured with NR-DC and the measurement configuration that triggered this measurement report is associated with SCG (Associated), including the measurement results through SRB3 for transmission if SRB3 is configured
  • SCG Associated
  • the measurement report message is submitted to the lower layer and the procedure ends, and if SRB3 is not set, the measurement report message is encapsulated in the NR MCG RRC message and sent to the lower layer through the NR MCG. Submit to layer.
  • the state in which the SCG is deactivated may be included as part of the RRC_CONNECTED state.
  • the state in which the SCG is deactivated means that the terminal device has the following (A) in the SpCell (PSCell) of the SCG, and / or in all cells of the SCG (J) may be implemented in part or in whole.
  • D Do not monitor the PDCCH for that cell and/or the PDCCH for that cell.
  • E the cell's PDCCH addressed to the C-RNTI, MCS-C-RNTI, and/or CS-RNTI indicating an uplink grant for UL-SCH transmission in that cell, and/or that cell; Do not monitor PDCCH for
  • F No Automatic Gain Control
  • G Do not perform beam management, including beam failure recovery, in that cell.
  • H Do not perform Radio Link Monitoring (RLM) in that cell.
  • RLM Radio Link Monitoring
  • the SCG when the SCG is in an inactive state, different processing may be performed while the time alignment timer is running in that SCG and while the time alignment timer is stopped (including the expired state). For example, while the SCG is inactive and the time alignment timer is running, CSI is reported in the SpCell of this SCG, and while the SCG is inactive and the time alignment timer is stopped, the SpCell of this SCG CSI reporting may not be implemented in Also, for example, while the SCG is inactive and the time alignment timer is running, RLM is performed in this SCG SpCell, and while the SCG is inactive and the time alignment timer is stopped, the SpCell of this SCG may not implement RLM.
  • the terminal device may not perform processing involving the start of the random access procedure when it is in the SCG inactive state.
  • the timer may be another timer that is started, for example, when the SCG is instructed to be deactivated or when the SCG is deactivated.
  • the timer may be a MAC entity managed timer.
  • entering the SCG inactive state may be referred to as entering an inactivated SCG.
  • the SCG inactive state may be a state in which the Active BWP of the SpCell of the SCG is a specific BWP.
  • the above-described SCG inactive state is a state in which the SCG to be described later transitions from an activated state (SCG active state) when an RRC entity instructs to enter an inactivated SCG. good too.
  • the SCG activated state may be included as part of the RRC_CONNECTED state.
  • the SCG activated state means that the terminal device is in the SCG SpCell (PSCell) and / or in any cell of the SCG from (A) below It may be in a state to implement part or all of (J).
  • SCG active state means that the terminal device is in the SCG SpCell (PSCell) and / or in any cell of the SCG from (A) below It may be in a state to implement part or all of (J).
  • (C) transmit PUCCH, UL-SCH and/or RACH on that cell;
  • (D) monitor the PDCCH for that cell and/or the PDCCH for that cell;
  • (G) Perform beam management, including beam failure recovery, in that cell.
  • (H) perform radio link monitoring (RLM) in the cell;
  • (J) Monitor the C-RNTI on the PDCCH in the activated BWP of that cell.
  • entering the SCG active state may be called entering the activated SCG.
  • the SCG active state may be a state in which the SCG SpCell and/or one or more SCell Active BWPs are not dormant BWPs.
  • the above-mentioned SCG inactive state is a state in which the SCG transitions from the inactivated state (SCG inactive state) when the RRC entity instructs to leave the deactivated SCG. may be
  • the terminal device may transition the SCG to an inactive state based on receiving part or all of (A) to (B) below (in other words, the SCG may be deactivated).
  • the messages and control elements (A) to (C) below may be notified to the terminal device from a cell group other than the SCG.
  • each piece of information may be notified to the terminal device using an RRC message, MAC control element, or physical control channel.
  • A) Information instructing deactivation of SCG (B) Information instructing deactivation of SpCell (C) Information instructing switching of Active BWP of SpCell to a specific BWP
  • the terminal device may transition the SCG from the active state to the inactive state based on the timer for deactivating the SCG. Also, the terminal device may transition the SCG from the active state to the inactive state based on a timer related to PSCell deactivation.
  • the terminal device may transition the SCG from the inactive state to the active state when starting a random access procedure by the MAC entity itself (for example, due to a scheduling request).
  • the MAC entity of the terminal device sends an instruction to activate the SCG, an instruction to wake up from the deactivated SCG, an instruction to wake up from SpCell dormancy, and/or other information to the RRC entity of the terminal device. may be obtained from
  • the terminal device may transition the SCG from the inactive state to the active state based on receiving some or all of (A) to (D) below (in other words , may activate the SCG).
  • the following messages (A) to (D) and control elements may be notified to the terminal device from a cell group other than the SCG. Also, each piece of information may be notified to the terminal device using an RRC message, MAC control element, or physical control channel.
  • A) Information instructing SCG activation (B) Information instructing SCG to resume from inactive state (C) Information instructing SpCell activation (D) SpCell inactive state information that instructs the return from
  • the terminal device may cause the SCG to transition from the inactive state to the active state based on the timer for deactivating the SCG. Also, the terminal device may transition the SCG from the inactive state to the active state based on a timer related to PSCell deactivation.
  • the terminal device may transition the SCG from the inactive state to the active state when starting a random access procedure caused by a scheduling request triggered to transmit a MAC PDU containing a MAC SDU. Also, the terminal device may transition the SCG from the inactive state to the active state when starting the random access procedure.
  • the terminal device may transition the SCG from the inactive state to the active state when starting a random access procedure caused by a scheduling request (in other words, initiated by the MAC entity itself).
  • the MAC entity of the terminal device sends an instruction to activate the SCG, an instruction to wake up from the deactivated SCG, an instruction to wake up from SpCell dormancy, and/or other information to the RRC entity of the terminal device. may be obtained from
  • Inactivation of the SCG may be referred to as entering the dormant SCG (Dormant SCG). Also, deactivation of the SCG may be activation of dormant BWPs of SpCells of the cell group. Inactivation of SCG may also be referred to as SCG dormant or SCG suspension.
  • All uplink transmissions may be stopped in the SCG when the SCG is deactivated and at least the time alignment timer is stopped.
  • information about that SCG may be sent in another cell group (eg, MCG).
  • the information about that SCG may be sent in that SCG that has left the deactivated state (activated SCG).
  • the random access procedure in the SpCell may be initiated in the deactivated SCG by triggering a scheduling request by the MAC entity to send a MAC PDU containing the MAC CE or directly by the MAC entity. good too. At this time, the MAC PDU may not contain the MAC SDU.
  • the SCG in which the random access procedure in the SpCell (PSCell) is deactivated by triggering a scheduling request to transmit a MAC PDU containing data (MAC SDU) from higher layers such as user data and RRC messages. may be started at
  • the return of the SCG from the inactivated state may be referred to as leaving the dormant SCG.
  • returning from the inactivated state of the SCG may be BWP switching from a dormant BWP to another (non-dormant BWP) BWP in the SpCell of the cell group.
  • SCG activation Activation of SCG
  • SCG Re-activation SCG re-activation
  • a terminal device that performs SCG deactivation may perform some or all of the following processes (A) to (Q) in the SCG.
  • E Ignore MAC CEs that activate SCells. For example, in the processing (AD), if MAC CE for activating SCell is received and SCG deactivation is not instructed (or SCG is not deactivated), processing ( AD-1) is performed.
  • (F) Execute the above process (AD-2). For example, when inactivation of SCG is instructed (or SCG is inactivated) in the processing (AD-2), processing (AD-2) is performed.
  • (G) Switch the Active BWP of a particular SCell to Dormant BWP (ie put this SCell to Dormant state).
  • a specific SCell may be an SCell designated by the base station apparatus, or an SCell in which a Dormant BWP is set.
  • (H) Switch the SpCell's Active BWP to a specific BWP.
  • the specific BWP may be the BWP designated by the base station apparatus, the BWP set as the First Active BWP, or the Initial BWP.
  • the BWP to be switched may be only the DL BWP, or both the DLBWP and the UL BWP.
  • (I) Deactivate all BWPs of SpCell. That is, when the SCell is deactivated, all BWPs of this SCell are deactivated, and the same process is performed on the SpCell.
  • (J) Abort the random access procedure in progress.
  • (K) Abort the random access procedure in progress and consider this random access procedure to be successfully completed.
  • (M) Do not suspend at least some SCG bearers (for example, DRB) set in the terminal device.
  • N When PDCP duplication is set and the PDCP duplication is activated, the deactivation of the PDCP duplication is notified to the upper layer (eg, RLC layer, PDCP layer) .
  • O Reset MAC.
  • P Stop the BSR-related timer (eg, periodicBSR-Timer and/or retxBSR-Timer) if it is running.
  • Q Re-establish the RLC corresponding to the SCG bearer.
  • a terminal device that restores an SCG from an inactivated state may execute some or all of the following processes (A) to (F) in the SCG.
  • A) Execute processing (AD-1) to activate all SCells.
  • B) Leave all SCells inactive. However, since it is not in an inactivated state, for example, in the processing (AD), when a MAC CE for activating SCell is received, deactivation of SCG is not instructed (or SCG is inactivated is not in the state of being completed), processing (AD-1) may be performed.
  • (F) Activate the BWP set as the SpCell's First Active BWP.
  • (G) Resume at least some SCG bearers (for example, SRB3) set in the terminal device.
  • SCG bearers for example, SRB3
  • H If PDCP duplication is set and the PDCP duplication is deactivated based on the deactivation of the SCG, the activation of the PDCP duplication is activated by the upper layer (for example, RLC layer, PDCP layer).
  • FIG. 5 is a block diagram showing the configuration of the terminal device (UE 122) according to the embodiment of the present invention. In order to avoid complicating the description, FIG. 5 shows only main components closely related to one embodiment of the present invention.
  • UE 122 shown in FIG. 5 includes a receiving unit 500 that receives an RRC message or the like from a base station device, a processing unit 502 that performs processing according to parameters included in the received message, and a transmitting unit that transmits the RRC message or the like to the base station device. consists of 504.
  • the base station apparatus described above may be eNB 102 or gNB 108 .
  • processing unit 502 may include some or all of the functionality of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer).
  • the processing unit 502 includes part or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP processing unit, RRC layer processing unit, and NAS layer processing unit. you can UE 122 may also include a measurement unit (not shown) for making measurements.
  • FIG. 6 is a block diagram showing the configuration of the base station apparatus according to the embodiment of the present invention. In order to avoid complicating the description, FIG. 6 shows only main components closely related to one embodiment of the present invention.
  • the base station apparatus described above may be eNB 102 or gNB 108 .
  • the base station apparatus shown in FIG. 6 includes a transmission unit 600 that transmits an RRC message and the like to UE 122, and a processing unit that creates an RRC message including parameters and transmits it to UE 122, thereby allowing processing unit 502 of UE 122 to perform processing. 602 and a receiver 604 that receives RRC messages and the like from the UE 122 .
  • processing unit 602 may include some or all of the functionality of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 602 includes part or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP processing unit, RRC layer processing unit, and NAS layer processing unit. you can
  • the "MAC entity” used in the following description shall be the MAC entity of the cell group to be activated/deactivated in the terminal device (UE 122) unless otherwise specified. Also, the “RRC entity” used in the following description shall be the RRC entity of the terminal device (UE 122) unless otherwise specified.
  • FIG. 15 is a diagram showing an example of processing of the terminal device according to the embodiment of the present invention.
  • the RRC entity of the terminal device receives a first notification from a lower layer entity (eg MAC entity, PHY entity) (step S1500).
  • a lower layer entity eg MAC entity, PHY entity
  • the RRC entity of the terminal device receives the first notification from the MAC entity of the cell group (for example, the secondary cell group) corresponding to the lower layer entity that notified the first notification. 1, it generates an RRC message requesting the network to activate the secondary cell group (step S1502). Note that if there is only one cell group to be deactivated in the UE 122, it is not necessary to identify which secondary cell it is in the above process.
  • the first notification may be notified by the MAC entity of UE122.
  • the MAC entity may be activated based on the MAC entity's cell group being deactivated and uplink data for any logical channel of the MAC entity's cell group becoming available. may notify the RRC entity of the first notification.
  • the MAC entity notifies the RRC entity of a first notification based on the MAC entity's cell group being deactivated and at least one scheduling request pending at the MAC entity. You may
  • the RRC entity instead of generating an RRC message requesting cell group activation, the RRC entity generates an RRC message containing information indicating that uplink data exists in an inactive cell group, for example. may generate a message.
  • the RRC entity may generate the RRC message in the process of Fig. 15 as an RRC message for the master node. Also, the RRC entity may generate the RRC message in FIG. 15 as the RRC message for the secondary node and include the generated RRC message in the container in the RRC message for the master node. The RRC entity may submit the generated RRC message to lower layers for transmission. RRC messages submitted to the lower layers may be transmitted by transmitter 504 of UE 122 to the base station apparatus.
  • the transmitted base station device may be a master node.
  • the receiving unit 604 of the base station device may receive the RRC message from the UE122.
  • the processing unit 602 of the base station apparatus may determine whether to activate the deactivated cell group based on the received RRC message.
  • FIG. 16 is a diagram showing an example of processing of the terminal device according to the embodiment of the present invention.
  • the RRC entity of the terminal device receives a second notification from a lower layer entity (eg MAC entity) (step S1600).
  • a lower layer entity eg MAC entity
  • the RRC entity of the terminal device receives the second notification from the cell group (for example, the MAC entity of the secondary cell group) corresponding to the lower layer entity that notified the second notification. 2, the secondary cell group) is considered to be activated (step S1602).
  • the cell group for example, the MAC entity of the secondary cell group
  • the secondary cell group is considered to be activated (step S1602).
  • the terminal device can activate the cell group at an appropriate timing.
  • the first notification may be notified by the MAC entity of UE122.
  • the MAC entity may indicate, for example, PUCCH transmission due to a scheduling request, initiation of a random access procedure (or successful completion of a random access procedure), and/or SpCell beam failure in a deactivated cell group.
  • a second notification may be sent to the RRC entity based on the initiation of the random access procedure for recovery (or the successful completion of the random access procedure).
  • the RRC entity may, for example, resume some bearers (for example, SRB3) that have been suspended based on the assumption that the cell group has been activated.
  • the RRC entity by considering that the cell group has been activated, for example, disabled measurement configuration (for example, part of the measurement target and / or part of the report configuration) It may be enabled autonomously.
  • FIG. 17 is a diagram showing an example of processing of the terminal device according to the embodiment of the present invention.
  • the MAC entity of the terminal device (UE 122) recognizes that the cell group will be deactivated (step S1700).
  • the MAC entity of the terminal device (UE 122) aborts (Aborts) the random access procedure being executed in the cell group based on the deactivation of the cell group. (Step S1702).
  • the MAC entity of UE 122 may recognize the deactivation of the cell group by notification from the RRC entity.
  • the MAC entity of UE 122 may recognize cell group deactivation by MAC CE received from the base station apparatus.
  • the MAC entity of UE 122 may recognize cell group deactivation based on the deactivation or expiration of a particular timer.
  • the MAC entity of UE 122 may recognize cell group deactivation based on the above combinations.
  • the MAC entity aborts the random access procedure running in the cell group based on the cell group being deactivated, and the random access procedure is successfully completed. may be considered to have
  • the MAC entity may also abort beam failure recovery procedures in progress in a cell group based on the cell group being deactivated. At that time, the beam failure recovery procedure may be considered successful.
  • the MAC entity may perform some or all of the following processes (A) to (F) based on the cell group being deactivated. .
  • F Cancel the beam failure recovery procedure if it has been triggered.
  • the terminal device may control activation/deactivation of the secondary cell group using a timer in the RRC entity and/or MAC entity.
  • a timer may be prepared for each cell group, or one timer may be prepared for each terminal device.
  • the value set in the timer may be reported from the base station apparatus using an RRC message (for example, an RRCReconfiguration message).
  • the value set in the timer may be reported from the base station apparatus.
  • the value set in the timer may be the default value described in the specification.
  • the terminal device may have a default value described in the specification as a default value, and use this default value when it is not set in the base station device.
  • the terminal device may start or restart a timer based on the secondary cell group being deactivated and activated. From the base station apparatus, autonomous (in other words, triggered and/or initiated by the determination of the terminal) secondary cell group activation by the terminal and/or autonomous (in other words, triggered and/or initiated by the determination of the terminal) / or is started), the terminal device that is allowed to deactivate the secondary cell group activates the secondary cell group based on this timer not running (that the timer has expired), and / Alternatively, inactivation may be performed.
  • the terminal device may start or restart the timer based on the deactivation of the secondary cell group.
  • a terminal device permitted to deactivate the secondary cell group activates and/or deactivates the secondary cell group based on the fact that this timer is not running (the timer has expired). You may do so.
  • the terminal device may start or restart a timer based on activation of the secondary cell group.
  • a terminal device permitted to deactivate the secondary cell group activates and/or deactivates the secondary cell group based on the fact that this timer is not running (the timer has expired). You may do so.
  • the terminal device when the value of the timer is set to 0, the terminal device is permitted to activate the autonomous secondary cell group and/or deactivate the autonomous secondary cell group from the base station device. You can judge that it is not. Also, for example, when the value of the timer is set to infinity, the terminal device activates the autonomous secondary cell group and/or deactivates the autonomous secondary cell group from the base station device may be determined not to be permitted. Further, for example, when the timer value is not set from the base station device, the terminal device receives autonomous secondary cell group activation and/or autonomous secondary cell group deactivation from the base station device. You may decide that it is not permitted.
  • the base station apparatus sets a specific value for the timer and notifies the terminal apparatus (or does not notify the timer value), thereby allowing the terminal apparatus to autonomously activate and/or deactivate the cell group. can be controlled. Note that whether or not the terminal device can autonomously activate and/or deactivate the cell group may be notified from the base station device to the terminal device using a parameter other than the timer.
  • the terminal device determines that the secondary cell group is deactivated. may suspend some or all of the SCG bearers (SRB and/or DRB where the RLC bearer resides only in the SCG) when the Further, for example, based on the fact that the base station device permits autonomous secondary cell group activation and/or autonomous secondary cell group deactivation, the terminal device deactivates the secondary cell group. may not suspend some or all of the SCG bearers (SRBs and/or DRBs whose RLC bearers are present only in the SCG).
  • the terminal device based on whether or not the base station device permits the activation of the autonomous secondary cell group and/or the deactivation of the autonomous secondary cell group, the terminal device, in the process of FIG. 17, It may be determined whether or not to abort the random access procedure being executed.
  • the terminal device in the process of FIG. 17, It may be determined whether or not to execute some or all of the following processes (A) to (F).
  • the network (base station device) to efficiently control the autonomous activation and/or deactivation of cell groups by terminal devices.
  • the activation of the autonomous secondary cell group by the terminal device described above is, for example, due to the presence of uplink data in the inactivated secondary cell group (for example, triggering a scheduling request). Activation of the secondary cell group may be initiated with Further, the aforementioned autonomous activation of the secondary cell group by the terminal device may be, for example, activation of the secondary cell group initiated based on the remaining battery level of the terminal device or the temperature of the terminal device. Note that the autonomous activation of the secondary cell group may be rephrased as activation of the secondary cell initiated by the terminal device (UE initiated SCG activation).
  • the above-described autonomous deactivation of the secondary cell group by the terminal device is, for example, deactivation of the secondary cell group that is started based on the absence of uplink data in the activated secondary cell group. It's okay. Further, the above-described autonomous deactivation of the secondary cell group by the terminal device is, for example, the remaining battery level of the terminal device or the deactivation of the secondary cell group that is started based on the temperature of the terminal device. good. Note that autonomous activation of a secondary cell group may be rephrased as deactivation of a secondary cell initiated by a terminal device (UE initiated SCG Deactivation).
  • the terminal device performs uplink transmission (for example, due to a scheduling request) in this secondary cell group based on the activation of the secondary cell group.
  • transmission of PUCCH or random access preamble may be started.
  • the terminal device may activate this secondary cell group based on uplink transmission in the deactivated secondary cell group (for example, PUCCH or random access preamble transmission resulting from a scheduling request).
  • the terminal device based on having transmitted a random access preamble (or having indicated the transmission of the random access preamble to the PHY entity) in a cell of the deactivated secondary cell group (eg, PSCell or PUCCH SCell), this The secondary cell group may be considered activated and start monitoring the PDCCH.
  • the terminal device may change the bearer setting to deactivate this secondary cell group. For example, when an SCG bearer is configured, the terminal device may change the bearer type of this SCG bearer to a split bearer based on deactivating the secondary cell group. Further, for example, when the terminal device has an SCG bearer configured, based on deactivating the secondary cell group, the bearer type of this SCG bearer is changed to a split bearer, and the PDCP entity sends the PDCP to the RLC entity of the MCG. May be set to submit PDUs. At this time, the bearer setting may be changed based on a predetermined rule, or the changed bearer setting may be notified in advance from the base station apparatus by an RRC message. In addition, when the secondary cell group is deactivated by the autonomous deactivation of the secondary cell group by the terminal device, the terminal device notifies the base station device that the secondary cell group has been deactivated, and then the bearer setting may be changed.
  • the MAC entity deactivates the PDCP duplication based on deactivating the secondary cell group ( Deactivation) may be notified to an upper layer (for example, PDCP layer). Also, at this time, if the primary path is set to a deactivated secondary cell group, the terminal device may reset the primary path to another cell group.
  • the cell group identifier of the reconfigured primary path may be, for example, the MCG identifier.
  • the cell group identifier of the reconfigured primary path may be, for example, a cell group identifier preconfigured in the terminal device by an RRC message.
  • the above process is suitable when the terminal device autonomously deactivates the secondary cell group (that is, when the terminal device triggers and starts deactivation of the secondary cell group). It is not limited and is also applicable in the case of network directed deactivation.
  • the terminal device when the secondary cell group is deactivated by the terminal device's autonomous deactivation of the secondary cell group, the terminal device notifies the base station device that the secondary cell group has been deactivated, and then Processing may be performed.
  • the terminal device autonomously deactivates the secondary cell group (that is, when the terminal device triggers and starts deactivation of the secondary cell group), one of (A) to (C) below Deactivation of secondary cell groups may be triggered and/or not initiated based on meeting some or all conditions. Also, if the network instructs to deactivate a secondary cell, the secondary cell group may be deactivated regardless of the following conditions.
  • A PDCP duplication is set and activated.
  • B PDCP duplication is set, the PDCP duplication is deactivated, and the primary path is set to this secondary cell group.
  • An SCG bearer is configured for this secondary cell group.
  • the radio bearer in the above description may be DRB, SRB, or both DRB and SRB.
  • SCG SpCell may be replaced with “PSCell”.
  • A may be rephrased as B” may include the meaning of rephrasing B as A in addition to rephrasing A as B.
  • C may be D
  • C may be E
  • F may be G
  • G may be H
  • F may be H
  • condition "B” is expressed as “other” condition of condition "A”.
  • a first embodiment of the present invention is a terminal device configured with a master cell group and a secondary cell group, comprising a MAC entity, wherein the MAC entity deactivates the secondary cell group. Aborts a running random access procedure based on what has been done.
  • a second embodiment of the present invention is a method applied to a terminal device in which a master cell group and a secondary cell group are configured, wherein the MAC entity is configured to terminating the running random access procedure based on the
  • a third embodiment of the present invention is an integrated circuit mounted in a terminal device in which a master cell group and a secondary cell group are set, wherein the secondary cell group is deactivated. Based on this, the terminal device is provided with the function of aborting the random access procedure being executed.
  • a program that runs on a device is a program that controls a Central Processing Unit (CPU) or the like to function a computer so as to realize the functions of the above-described embodiments according to one aspect of the present invention. There may be.
  • the program or information handled by the program is 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
  • RAM Random Access Memory
  • HDD Hard Disk Drive
  • part of the devices in the above-described embodiments may be realized by a computer.
  • a program for realizing this control function may be recorded in a computer-readable recording medium, and the program recorded in this recording medium may be read into a computer system and executed.
  • the "computer system” here is a computer system built in the device, and includes hardware such as an operating system and peripheral devices.
  • the "computer-readable recording medium” may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, and the like.
  • “computer-readable recording medium” means a medium that dynamically stores programs for a short period of time, such as a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line. , such as a volatile memory inside a computer system serving as a server or a client in that case, which holds the program for a certain period of time.
  • the program may be for realizing part of the functions described above, or may be capable of realizing the functions described above in combination with a program already recorded in the computer system.
  • each functional block or feature of the apparatus used in the embodiments described above may be implemented or performed in an electrical circuit, typically an integrated circuit or multiple integrated circuits.
  • Electrical circuits designed to perform the functions described herein may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof.
  • a general purpose processor may be a microprocessor, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • the general-purpose processor or each circuit described above may be composed of digital circuits or may be composed of analog circuits.
  • an integrated circuit technology that replaces current integrated circuits emerges due to advances in semiconductor technology, it is also possible to use integrated circuits based on this technology.
  • the present invention is not limited to the above-described embodiments.
  • an example of the device is described, but the present invention is not limited to this, and stationary or non-movable electronic devices installed indoors and outdoors, such as AV equipment, kitchen equipment, 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.
  • One aspect of the present invention is, 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), or a program, etc. be able to.
  • 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 etc. be able to.
  • E-UTRA 102 eNB 104 EPCs 106NR 108 gNB 110 5GC 112, 114, 116, 118, 120, 124 interfaces 122 UEs 200, 300 PHYs 202, 302 MACs 204, 304 RLC 206, 306 PDCP 208, 308 RRC 310 SDAP 210, 312 NAS 500, 604 Receiver 502, 602 processor 504, 600 transmitter

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un équipement terminal pour lequel un groupe de cellules maîtresses et un groupe de cellules secondaires sont définis, et qui comprend une entité MAC. Sur la base du groupe de cellules secondaires inactivé, l'entité MAC annule une procédure d'accès aléatoire qui est en cours d'exécution.
PCT/JP2022/014082 2021-04-01 2022-03-24 Équipement terminal, procédé et circuit intégré WO2022210285A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2023511134A JPWO2022210285A1 (fr) 2021-04-01 2022-03-24

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2021062888 2021-04-01
JP2021-062888 2021-04-01

Publications (1)

Publication Number Publication Date
WO2022210285A1 true WO2022210285A1 (fr) 2022-10-06

Family

ID=83458811

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/014082 WO2022210285A1 (fr) 2021-04-01 2022-03-24 Équipement terminal, procédé et circuit intégré

Country Status (2)

Country Link
JP (1) JPWO2022210285A1 (fr)
WO (1) WO2022210285A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024096097A1 (fr) * 2022-11-02 2024-05-10 シャープ株式会社 Dispositif terminal, procédé, et circuit intégré

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 38.321, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V16.7.0, 23 December 2021 (2021-12-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 158, XP052083421 *
KDDI CORPORATION: "Considerations on Time Alignment Timer for SCG deactivation", 3GPP DRAFT; R2-2100647, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20210125 - 20210205, 14 January 2021 (2021-01-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051972711 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024096097A1 (fr) * 2022-11-02 2024-05-10 シャープ株式会社 Dispositif terminal, procédé, et circuit intégré

Also Published As

Publication number Publication date
JPWO2022210285A1 (fr) 2022-10-06

Similar Documents

Publication Publication Date Title
EP4224914A1 (fr) Dispositif terminal, procédé de communication et dispositif station de base
WO2022210285A1 (fr) Équipement terminal, procédé et circuit intégré
WO2022145403A1 (fr) Équipement terminal, dispositif de station de base, et procédé
WO2022085663A1 (fr) Procédé et circuit intégré
WO2022080306A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2022080419A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2022210234A1 (fr) Dispositif terminal, procédé, et circuit intégré
WO2022210163A1 (fr) Dispositif terminal, dispositif station de base et procédé
WO2022145409A1 (fr) Dispositif terminal, dispositif de station de base, et procédé
WO2022145402A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2022196550A1 (fr) Dispositif terminal, dispositif station de base, et procédé
WO2023063345A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2023063342A1 (fr) Dispositif terminal, dispositif de station de base, et procédé
WO2023008043A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023042752A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2023042747A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2023106315A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2023013292A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2022080341A1 (fr) Équipement terminal, dispositif de station de base et procédé
WO2023112531A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023189963A1 (fr) Équipement terminal, procédé et circuit intégré
WO2023112792A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2024009884A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023153410A1 (fr) Dispositif terminal, procédé, et circuit intégré
WO2024005069A1 (fr) Dispositif terminal, procédé et circuit intégré

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22780499

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023511134

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22780499

Country of ref document: EP

Kind code of ref document: A1