WO2023189798A1 - Dispositif terminal, dispositif de station de base et procédé - Google Patents

Dispositif terminal, dispositif de station de base et procédé Download PDF

Info

Publication number
WO2023189798A1
WO2023189798A1 PCT/JP2023/010810 JP2023010810W WO2023189798A1 WO 2023189798 A1 WO2023189798 A1 WO 2023189798A1 JP 2023010810 W JP2023010810 W JP 2023010810W WO 2023189798 A1 WO2023189798 A1 WO 2023189798A1
Authority
WO
WIPO (PCT)
Prior art keywords
scg
rrc
pscell
terminal device
base station
Prior art date
Application number
PCT/JP2023/010810
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 シャープ株式会社
Publication of WO2023189798A1 publication Critical patent/WO2023189798A1/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/28—Cell structures using beam steering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0457—Variable allocation of band or rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/231—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling
    • 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 a terminal device, a base station device, and a method.
  • This application claims priority to Japanese Patent Application No. 2022-61681 filed in Japan on April 1, 2022, the contents of which are incorporated herein.
  • the 3rd Generation Partnership Project (3GPP) which is a standardization project for cellular mobile communication systems, is conducting technical studies and standardization for cellular mobile communication systems, including wireless access, core networks, services, etc. There is.
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • RAT Radio Access Technology
  • 3GPP 3GPP is still conducting technical studies and standardization for E-UTRA expansion technology.
  • E-UTRA is also referred to as Long Term Evolution (LTE: registered trademark), and the extended technology is also referred to as LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • NR New Radio, or NR Radio access
  • 5G 5th Generation
  • NR As an extension technology for NR, there is a dual connectivity (also called multi-connectivity) technology in which one or more base station devices and terminal devices communicate using multiple cell groups in order to enable large-capacity data communication. .
  • the terminal device in order to communicate in each cell group, the terminal device needs to monitor whether there is a message addressed to it in each cell group.
  • the terminal device In order for the terminal device to communicate with low delay when large-capacity data communication occurs, the terminal device must constantly monitor multiple cell groups, which poses the problem of consuming a large amount of power. For this reason, studies have begun on technology to monitor some cell groups at a low frequency or to stop monitoring (cell group deactivated technology).
  • Non-Patent Documents 7 and 8 are CR (Change Request) drafts of RRC and MAC specifications created based on specification details agreed upon so far. However, based on the current CR proposal, in order to activate a cell group, the MAC may have to start a random access procedure other than when necessary, which may result in unnecessary signaling.
  • CR Change Request
  • One aspect of the present invention has been made in view of the above circumstances, and one of the objects is to provide a terminal device, a base station device, a communication method, and an integrated circuit that can efficiently control communication. .
  • one embodiment of the present invention takes the following measures. That is, one aspect of the present invention is a terminal device that communicates with a base station device, comprising a processing unit that communicates using an MCG and an SCG, and a receiving unit that receives signaling from the base station device, includes at least a PSCell, and the processing unit activates the SCG based on receiving signaling including an instruction to activate the SCG from the base station device, and the processing unit activates the SCG based on receiving signaling including an instruction to activate the SCG.
  • the SCG is inactivated immediately before receiving from the base station device, it is determined whether or not there is a beam failure in the PSCell, and at least it is determined that the beam has not failed in the PSCell. Based on the determination that the beam has failed in at least the PSCell, the lower layer is not notified to start the random access procedure.
  • one aspect of the present invention is a base station device that communicates with a terminal device, and includes a processing unit that communicates using an MCG and an SCG, and a transmitting unit that transmits signaling to the terminal device, wherein the SCG is a base station device that communicates with a terminal device.
  • the processing unit includes at least a PSCell, and the processing unit activates the SCG by transmitting signaling including an instruction to activate the SCG to the terminal device, and transmits the signaling including the instruction to activate the SCG to the terminal device.
  • the terminal device is made to determine whether or not the beam has failed in the PSCell, and at least determines that the beam has not failed in the PSCell. By doing so, the random access procedure is not started, but the random access procedure is started by determining that the beam has failed in at least the PSCell.
  • one aspect of the present invention is a method for a terminal device to communicate with a base station device, in which the terminal device communicates using an MCG and an SCG, and receives signaling from the base station device, the SCG includes at least a PSCell, and the terminal device communicates using an MCG and an SCG.
  • the SCG is activated, and the SCG is activated immediately before receiving the signaling including the instruction to activate the SCG from the base station device.
  • the lower layer determines whether or not the beam has failed in the PSCell, and starts a random access procedure based on the determination that at least the beam has not failed in the PSCell. Based on the determination that the beam has failed at least in the PSCell, the lower layer is notified to start a random access procedure.
  • a terminal device, a base station device, and a method can realize efficient communication control processing.
  • FIG. 1 is a schematic diagram of a communication system according to the present embodiment.
  • FIG. 2 is a diagram illustrating an example of the E-UTRA protocol configuration according to the present embodiment.
  • FIG. 3 is a diagram illustrating an example of the NR protocol configuration according to the present embodiment.
  • FIG. 3 is a diagram illustrating an example of a flow of procedures for various settings in RRC according to the present embodiment.
  • FIG. 2 is a block diagram showing the configuration of a terminal device in this embodiment.
  • FIG. 2 is a block diagram showing the configuration of a base station device in this embodiment.
  • LTE and LTE-A, LTE-A Pro
  • NR may be defined as different radio access technologies (RAT).
  • RAT radio access technologies
  • LTE may be defined as a technology included in LTE.
  • LTE may be defined as a technology included in NR.
  • LTE which can be connected to NR using Multi-Radio Dual Connectivity (MR-DC)
  • MR-DC Multi-Radio Dual Connectivity
  • LTE that uses 5GC in the core network Core Network: CN
  • CN Core Network
  • conventional LTE may be LTE that does not implement the technology standardized after Release 15 in 3GPP.
  • This embodiment may be applied to NR, LTE and other RATs.
  • E-UTRA in this embodiment may be replaced with the term LTE
  • LTE may be replaced with the term E-UTRA.
  • each node and entity and the processing in each node and entity will be explained when the radio access technology is E-UTRA or NR. However, this embodiment is applicable to other radio access technologies. May be used. The names of each node and entity in this embodiment may be different names.
  • FIG. 1 is a schematic diagram of a communication system according to this embodiment. Note that the functions of each node, radio access technology, core network, interface, etc. explained using FIG. 1 are some functions closely related to this embodiment, and may have other functions.
  • E-UTRA100 may be a wireless access technology. Further, the E-UTRA 100 may be an air interface between the UE 122 and the eNB 102. The air interface between UE 122 and eNB 102 may be referred to as a Uu interface.
  • the eNB (E-UTRAN Node B) 102 may be a base station device of the E-UTRA 100.
  • the eNB 102 may have the E-UTRA protocol described below.
  • the E-UTRA protocol may be composed of an E-UTRA User Plane (UP) protocol, which will be described later, and an E-UTRA Control Plane (CP) protocol, which will be described later.
  • the eNB 102 may terminate the E-UTRA user plane (UP) protocol and the E-UTRA control plane (CP) protocol for the UE 122.
  • a radio access network composed of eNBs may be called E-UTRAN.
  • the EPC (Evolved Packet Core) 104 may be a core network.
  • Interface 112 is an interface between eNB 102 and EPC 104, and may be called an S1 interface.
  • the interface 112 may include a control plane interface through which control signals pass, and/or a user plane interface through which user data passes.
  • the control plane interface of interface 112 may terminate at a Mobility Management Entity (MME: not shown) within EPC 104 .
  • MME Mobility Management Entity
  • S-GW serving gateway
  • the control plane interface of interface 112 may be referred to as the S1-MME interface.
  • the user plane interface of interface 112 may be referred to as the S1-U interface.
  • one or more eNBs 102 may be connected to the EPC 104 via the interface 112.
  • An interface may exist between multiple eNBs 102 connected to the EPC 104 (not shown).
  • the interface between the plurality of eNBs 102 connected to the EPC 104 may be referred to as an X2 interface.
  • NR106 may be a radio access technology.
  • NR106 may also be an air interface between UE122 and gNB108.
  • the air interface between UE 122 and gNB 108 may be referred to as a Uu interface.
  • gNB (g Node B) 108 may be a base station device of NR106.
  • gNB 108 may have the NR protocol described below.
  • the NR protocol may include an NR user plane (UP) protocol, which will be described later, and an NR control plane (CP) protocol, which will be described later.
  • the gNB 108 may terminate the NR User Plane (UP) protocol and the NR Control Plane (CP) protocol for the UE 122.
  • UP NR user plane
  • CP NR control plane
  • 5GC110 may be a core network.
  • Interface 116 is an interface between gNB 108 and 5GC 110, and may be called an NG interface.
  • the interface 116 may include a control plane interface through which control signals pass and/or a user plane interface through which user data passes.
  • the control plane interface of interface 116 may terminate in an Access and Mobility Management Function (AMF: not shown) within 5GC 110.
  • AMF Access and Mobility Management Function
  • the user plane interface of interface 116 may terminate at a User Plane Function (UPF: not shown) within 5GC 110.
  • the control plane interface of interface 116 may be referred to as an NG-C interface.
  • the user plane interface of interface 116 may be referred to as an NG-U interface.
  • one or more gNBs 108 may be connected to the 5GC 110 via the interface 116.
  • An interface may exist between multiple gNBs 108 connected to 5GC 110 (not shown).
  • the interface between multiple gNBs 108 connected to 5GC 110 may be called an Xn interface.
  • eNB102 may have the ability to connect to 5GC110.
  • the eNB 102 that has the function of connecting to the 5GC 110 may be called an ng-eNB.
  • Interface 114 is an interface between eNB 102 and 5GC 110, and may be called an NG interface.
  • the interface 114 may include a control plane interface through which control signals pass and/or a user plane interface through which user data passes.
  • the control plane interface of interface 114 may terminate at an AMF within 5GC 110.
  • the user plane interface of interface 114 may terminate at a UPF within 5GC 110.
  • the control plane interface of interface 114 may be referred to as an NG-C interface.
  • the user plane interface of interface 114 may be referred to as an NG-U interface.
  • a radio access network composed of ng-eNBs or gNBs may be referred to as NG-RAN.
  • NG-RAN, E-UTRAN, etc. may also be simply referred to as networks.
  • the network may include eNB, ng-eNB, gNB, and the like.
  • one or more eNBs 102 may be connected to the 5GC 110 via the interface 114.
  • An interface may exist between multiple eNBs 102 connected to 5GC 110 (not shown).
  • the interface between the plurality of eNBs 102 connected to the 5GC 110 may be referred to as an Xn interface.
  • the eNB 102 connected to the 5GC 110 and the gNB 108 connected to the 5GC 110 may be connected through an interface 120.
  • the interface 120 between the eNB 102 that connects to the 5GC 110 and the gNB 108 that connects to the 5GC 110 may be called an Xn interface.
  • gNB108 may have the function of connecting to EPC104.
  • gNB 108 having the function of connecting to EPC 104 may be called en-gNB.
  • Interface 118 is an interface between gNB 108 and EPC 104, and may be called an S1 interface.
  • Interface 118 may include a user plane interface through which user data passes.
  • the user plane interface of interface 118 may terminate at an S-GW (not shown) within EPC 104.
  • the user plane interface of interface 118 may be referred to as the S1-U interface.
  • the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 may be connected through an interface 120.
  • the interface 120 between the eNB 102 that connects to the EPC 104 and the gNB 108 that connects to the EPC 104 may be called an X2 interface.
  • the interface 124 is an interface between the EPC 104 and the 5GC 110, and may be an interface that passes only CP, only UP, or both CP and UP. Furthermore, some or all of the interfaces 114, 116, 118, 120, 124, etc. may not exist depending on the communication system provided by the communication carrier or the like.
  • the UE 122 may be a terminal device that can receive system information and paging messages transmitted from the eNB 102 and/or gNB 108. Further, the UE 122 may be a terminal device that can be wirelessly connected to the eNB 102 and/or the gNB 108. Further, the UE 122 may be a terminal device that can simultaneously perform a wireless connection with the eNB 102 and a wireless connection with the gNB 108. UE 122 may have an E-UTRA protocol and/or an NR protocol. Note that the wireless connection may be a Radio Resource Control (RRC) connection.
  • RRC Radio Resource Control
  • the UE 122 may be a terminal device that can be connected to the EPC 104 and/or 5GC 110 via the eNB 102 and/or gNB 108.
  • each data radio bearer (DRB) established between UE122 and eNB102 and/or gNB108 (to be described later) ) may be uniquely associated with each EPS (Evolved Packet System) bearer passing through the EPC 104.
  • EPS Evolved Packet System
  • Each EPS bearer may be identified by an EPS bearer identifier (Identity, or ID).
  • the same QoS may be guaranteed for data such as IP packets and Ethernet (registered trademark) frames that pass through the same EPS bearer.
  • each DRB established between UE122 and eNB102 and/or gNB108 is further established within 5GC110. It may be linked to one of the PDU (Packet Data Unit) sessions. There may be one or more QoS flows in each PDU session. Each DRB may be mapped to one or more QoS flows, or may not be mapped to any QoS flows.
  • Each PDU session may be identified by a PDU session identifier (Identity, or ID). Further, each QoS flow may be identified by a QoS flow identifier (Identity or ID). Furthermore, the same QoS may be guaranteed for data such as IP packets and Ethernet frames passing through the same QoS flow.
  • the EPC 104 There may be no PDU sessions and/or QoS flows in the EPC 104. Also, 5GC110 does not need to have an EPS bearer. When the UE 122 is connected to the EPC 104, the UE 122 has information on the EPS bearer, but may not have information on the PDU session and/or QoS flow. Further, when the UE 122 is connected to the 5GC 110, the UE 122 has information on the PDU session and/or QoS flow, but does not need to have information on the EPS bearer.
  • the eNB 102 and/or gNB 108 will also be simply referred to as a base station device, and the UE 122 will also be simply referred to as a terminal device or UE.
  • FIG. 2 is a diagram of an example of the E-UTRA protocol architecture according to the present embodiment.
  • FIG. 3 is a diagram of an example of the NR protocol configuration according to the present embodiment. Note that the functions of each protocol explained using FIG. 2 and/or FIG. 3 are some functions closely related to this embodiment, and may have other functions.
  • the 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 device to a terminal device.
  • FIG. 2(A) is a diagram of the E-UTRA user plane (UP) protocol stack.
  • the E-UTRA UP protocol may be a protocol between the UE 122 and the eNB 102. That is, the E-UTRA UP protocol may be a protocol that terminates at the eNB 102 on the network side.
  • the E-UTRA user plane protocol stack consists of a wireless physical layer (PHY) 200, a medium access control layer (MAC) 200, and a medium access control layer (MAC).
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • Figure 3(A) is a diagram of the NR user plane (UP) protocol stack.
  • the NRUP protocol may be a protocol between the UE 122 and the gNB 108. That is, the NR UP protocol may be a protocol that terminates at the gNB 108 on the network side.
  • the NR user plane protocol stack includes a radio physical layer PHY300, a medium access control layer MAC302, a radio link control layer RLC304, a packet data convergence protocol layer PDCP306, and It may be configured from SDAP (Service Data Adaptation Protocol) 310, which is a service data adaptation protocol layer.
  • SDAP Service Data Adaptation Protocol
  • FIG. 2(B) is a diagram of the E-UTRA control plane (CP) protocol configuration.
  • RRC Radio Resource Control
  • NAS Non Access Stratum
  • the NAS 210 may be a protocol that terminates with the MME on the network side.
  • Figure 3(B) is a diagram of the NR control plane (CP) protocol configuration.
  • RRC 308 which is a radio resource control layer
  • RRC308 may be a protocol that terminates at gNB108 on the network side.
  • the NAS 312, which is a non-AS layer may be a protocol between the UE 122 and the AMF. That is, the NAS 312 may be a protocol that terminates with AMF on the network side.
  • the AS (Access Stratum) layer may be a layer that terminates between the UE 122 and the eNB 102 and/or gNB 108. That is, the AS layer is a layer that includes some or all of PHY200, MAC202, RLC204, PDCP206, and RRC208, and/or a layer that includes some or all of PHY300, MAC302, RLC304, PDCP306, SDAP310, and RRC308. It's fine.
  • the following does not distinguish between the E-UTRA protocol and the NR protocol, and uses PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), and RRC (RRC layer).
  • NAS NAS layer
  • PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) are the PHY (PHY layer) of the E-UTRA protocol.
  • the SDAP (SDAP layer) may be the SDAP (SDAP layer) of the NR protocol.
  • PHY200, MAC202, RLC204, PDCP206, and RRC208 are respectively defined as PHY for E-UTRA or PHY for LTE, MAC for E-UTRA, or It is also called MAC for LTE, RLC for E-UTRA or RLC for LTE, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE.
  • PHY200, MAC202, RLC204, PDCP206, and RRC208 are 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 written as RRC or LTE RRC.
  • PHY300, MAC302, RLC304, PDCP306, and RRC308 are called PHY for NR, MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively. There are some things.
  • PHY300, MAC302, RLC304, PDCP306, and RRC308 are sometimes written as NR PHY, NR MAC, NR RLC, NR PDCP, NR RRC, etc., respectively.
  • Entities in the AS layer of E-UTRA and/or NR will be explained.
  • An entity that has some or all of the functions of the MAC layer may be called a MAC entity.
  • An entity that has some or all of the functions of the RLC layer may be called an RLC entity.
  • An entity that has some or all of the functions of the PDCP layer may be called a PDCP entity.
  • An entity that has some or all of the functions of the SDAP layer may be called an SDAP entity.
  • An entity that has some or all of the functions of the RRC layer may be called an RRC entity.
  • the MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be replaced with MAC, RLC, PDCP, SDAP, and RRC, respectively.
  • MAC PDU Protocol Data Unit
  • RLC Network Data Unit
  • RLC Physical Location
  • SDAP Secure Protocol
  • data provided from the upper layer to MAC, RLC, PDCP, and SDAP, and/or data provided from MAC, RLC, PDCP, and SDAP to the upper layer are MAC SDU (Service Data Unit) and RLC SDU, respectively.
  • MAC SDU Service Data Unit
  • RLC SDU Service Data Unit
  • PDCP SDU Secure Data Unit
  • SDAP SDU Secure Data Unit
  • a segmented RLC SDU may be referred to as an RLC SDU segment.
  • the base station device and the terminal device exchange (transmit and receive) signals in a higher layer.
  • the base station device and the terminal device may transmit and receive RRC messages (also referred to as RRC messages, RRC information, and RRC signaling) in a radio resource control (RRC) layer.
  • RRC radio resource control
  • the base station device and the terminal device may transmit and receive MAC control elements in the MAC (Medium Access Control) layer.
  • the RRC layer of the terminal device acquires system information broadcast from the base station device.
  • the RRC message, system information, and/or MAC control element is also referred to as a higher layer signal (higher layer signal) or a higher layer parameter (higher layer parameter).
  • upper layer refers to the upper layer seen from the PHY layer, so it refers to one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. Good too.
  • the upper layer may mean one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, and the like.
  • A is given (provided) by the upper layer” and “A is given (provided) by the upper layer” mean the upper layers of the terminal device (mainly the RRC layer and MAC layer).
  • A is received from the base station device, and the received A is given (provided) from an upper layer of the terminal device to the physical layer of the terminal device.
  • being “provided with upper layer parameters” means that the upper layer parameter included in the received upper layer signal is received from the base station device, and the upper layer parameter included in the received upper layer signal is transmitted from the upper layer of the terminal device to the terminal device.
  • Setting upper layer parameters to a terminal device may mean that upper layer parameters are given (provided) to the terminal device.
  • setting upper layer parameters in a terminal device may mean that the terminal device receives an upper layer signal from a base station device and sets the received upper layer parameters in the upper layer.
  • setting upper layer parameters to the terminal device may include setting default parameters given in advance to the upper layer of the terminal device.
  • the expression "submit" a message from the RRC entity of the terminal device to a lower layer may be used.
  • "submitting a message to a lower layer” from an RRC entity may mean submitting a message to a PDCP layer.
  • "submitting a message from the RRC layer to a lower layer” means that RRC messages are sent using SRBs (SRB0, SRB1, SRB2, SRB3, etc.), so It may also mean submitting to the corresponding PDCP entity.
  • the lower layer may refer to one or more of a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and the like.
  • the PHY of the terminal device may have a function of receiving data transmitted from the PHY of the base station device via a downlink (DL) physical channel.
  • the PHY of the terminal device may have a function of transmitting data to the PHY of the base station device via an uplink (UL) physical channel.
  • the PHY may be connected to the upper MAC via a transport channel.
  • the PHY may pass data to the MAC via a transport channel.
  • the PHY may also be provided with data from the MAC via a transport channel.
  • 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
  • PBCH may be used to broadcast system information required by terminal devices.
  • the PBCH may be used to broadcast a time index (SSB-Index) within the period of a synchronization signal block (SSB).
  • SSB-Index time index within the period of a synchronization signal block
  • the PDCCH may be used to transmit (or carry) downlink control information (DCI) in downlink wireless communication (wireless communication from a base station device to a terminal device).
  • 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.
  • PDCCH may be transmitted on PDCCH candidates.
  • a terminal device may monitor a set of PDCCH candidates in a serving cell. Monitoring a set of PDCCH candidates may mean attempting to decode a PDCCH according to a certain DCI format. Furthermore, the terminal device may use CORESET (Control Resource Set) to monitor the set of PDCCH candidates.
  • the DCI format may be used for PUSCH scheduling in the serving cell. PUSCH may be used for transmitting user data, transmitting an RRC message, which will be described later, and the like.
  • the PUCCH may be used to transmit uplink control information (UCI) in uplink wireless communication (wireless communication from a terminal device to a base station device).
  • the uplink control information may include channel state information (CSI) used to indicate the state of a downlink channel.
  • the uplink control information may also include a scheduling request (SR) used to request UL-SCH (Uplink Shared CHannel) resources.
  • SR scheduling request
  • the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement).
  • the PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer. Further, in the case of the downlink, the PDSCH may be used to transmit system information (SI), random access response (RAR), and the like.
  • SI system information
  • RAR random access response
  • PUSCH may be used to transmit HARQ-ACK and/or CSI along with uplink data (UL-SCH: Uplink Shared CHannel) or uplink data from the MAC layer. Further, PUSCH may be used to transmit only CSI or only HARQ-ACK and CSI. That is, PUSCH may be used to transmit only UCI. Additionally, the PDSCH or PUSCH may be used to transmit RRC signaling (also referred to as RRC message) and MAC CE.
  • RRC signaling also referred to as RRC message
  • the RRC signaling transmitted from the base station device may be common signaling to multiple terminal devices within the cell. Further, the RRC signaling transmitted from the base station device may be dedicated signaling (also referred to as dedicated signaling) for a certain terminal device. That is, terminal device-specific (UE-specific) information may be transmitted to a certain terminal device using dedicated signaling. Further, PUSCH may be used to transmit UE Capability in the uplink.
  • PRACH may be used to transmit a random access preamble.
  • PRACH is used to indicate initial connection establishment procedures, handover procedures, connection re-establishment procedures, synchronization (timing adjustment) for uplink transmission, and requests for UL-SCH resources. It's okay.
  • MAC may be called a MAC sublayer.
  • the MAC may have a function of mapping various logical channels to corresponding transport channels.
  • a logical channel may be identified by a logical channel identifier (Logical Channel Identity or Logical Channel ID).
  • Logical channels may be divided into control channels for transmitting control information and traffic channels for transmitting user information, depending on the type of information to be transmitted. Further, logical channels may be divided into uplink logical channels and downlink logical channels.
  • the MAC may have a function of multiplexing MAC SDUs belonging to one or more different logical channels and providing the same to the PHY.
  • the MAC may also have a function of demultiplexing the MAC PDUs provided from the PHY and providing them to the upper layer via the logical channel to which each MAC SDU belongs.
  • the MAC may also have a function of performing error correction through HARQ (Hybrid Automatic Repeat reQuest).
  • the MAC may also have a scheduling report (SR) function that reports scheduling information.
  • the MAC may have a function of performing priority processing between terminal devices using dynamic scheduling. Further, the MAC may have a function of performing priority processing between logical channels within one terminal device.
  • the MAC may have a function to prioritize resources that overlap within one terminal device.
  • E-UTRA MAC may have the function of identifying MultimediaBroadcast Multicast Services (MBMS).
  • MBMS MultimediaBroadcast Multicast Services
  • the NR MAC may also have a function of identifying multicast/broadcast service (MBS).
  • the MAC may have the ability to select the transport format.
  • MAC has a function to perform discontinuous reception (DRX) and/or discontinuous transmission (DTX), a function to perform random access (RA) procedure, and a power function that notifies information on transmittable power. It may have a headroom report (Power Headroom Report: PHR) function, a buffer status report (Buffer Status Report: BSR) function that notifies information on the amount of data in the transmission buffer, etc.
  • NR MAC may have a Bandwidth Adaptation (BA) function.
  • BA Bandwidth Adaptation
  • the MAC PDU format used in E-UTRA MAC and the MAC PDU format used in NR MAC may be different.
  • the MAC PDU may also include a MAC control element (MAC control element: MAC CE), which is an element for controlling the MAC.
  • MAC control element MAC control element
  • the BCCH (Broadcast Control Channel) may be a downlink logical channel for broadcasting control information such as system information (SI).
  • SI system information
  • PCCH Packet Control Channel
  • PCCH Packet Control Channel
  • CCCH Common Control Channel
  • CCCH may be a logical channel for transmitting control information between a terminal device and a base station device.
  • CCCH may be used when the terminal device does not have an RRC connection. Further, CCCH may be used between a base station device and multiple terminal devices.
  • DCCH Dedicated Control Channel
  • the dedicated control information may be control information dedicated to each terminal device.
  • DCCH may be used when the terminal device has an RRC connection.
  • DTCH (Dedicated Traffic Channel) may be a logical channel for transmitting user data on a one-to-one (point-to-point) basis between a terminal device and a base station device.
  • DTCH may be a logical channel for transmitting dedicated user data.
  • the dedicated user data may be user data dedicated to each terminal device.
  • DTCH may exist on both uplink and downlink.
  • 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 a 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
  • the BCCH may be mapped to a BCH (Broadcast Channel), which is a downlink transport channel, and/or a DL-SCH (Downlink Shared Channel).
  • BCH Broadcast Channel
  • DL-SCH Downlink Shared Channel
  • the PCCH may be mapped to a 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 a 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
  • RLC may be referred to as an RLC sublayer.
  • the E-UTRA RLC may have a function of segmenting and/or concatenating data provided from the upper layer PDCP and providing it to the lower layer.
  • the E-UTRA RLC may have a function of reassembling and re-ordering data provided from lower layers and providing the data to upper layers.
  • NR RLC may have a function of adding a sequence number independent of the sequence number added by PDCP to data provided from the upper layer PDCP.
  • NR RLC may have a function of segmenting data provided from PDCP and providing it to lower layers.
  • the NR RLC may have a function of reassembling data provided from lower layers and providing the data to upper layers.
  • RLC may also have a data retransmission function and/or a retransmission request function (Automatic Repeat reQuest: ARQ). Additionally, RLC may have a function of performing error correction using ARQ. Control information indicating data that needs to be retransmitted, which is sent from the RLC receiving side to the transmitting side in order to perform ARQ, can be called a status report. Also, the status report transmission instruction sent from the RLC transmitting side to the receiving side can be referred to as a poll. The RLC may also have a function to detect data duplication. RLC may also have a data discard function. RLC may have three modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM).
  • TM transparent mode
  • UM unacknowledged mode
  • AM acknowledged mode
  • the TM does not divide data received from the upper layer and does not need to add an RLC header.
  • a TM RLC entity is a uni-directional entity and may be configured as a transmitting TM RLC entity or as a receiving TM RLC entity.
  • data received from the upper layer is divided and/or combined, RLC headers are added, etc., but there is no need to control data retransmission.
  • a UM RLC entity may be a unidirectional entity or a bi-directional entity. If the UM RLC entity is a unidirectional entity, the UM RLC entity may be configured as a transmitting UM RLC entity or as a receiving UMRLC entity.
  • the UM RRC entity may be configured as a UM RLC entity consisting of a transmitting side and a receiving side.
  • the AM RLC entity is a bidirectional entity and may be configured as an AM RLC consisting of a transmitting side and a receiving side.
  • data provided to a lower layer by a TM and/or data provided from a lower layer may be referred to as a TMD PDU.
  • data provided to lower layers in UM and/or data provided from lower layers may be referred to as UMD PDU.
  • data provided to lower layers in AM or data provided from lower layers may be referred to as AMD PDU.
  • the RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC may be different.
  • the RLC PDU may include a data RLC PDU and a control RLC PDU.
  • the RLC PDU for data may be called RLC DATA PDU (RLC Data PDU, RLC data PDU).
  • the control RLC PDU may be referred to as RLC CONTROL PDU (RLC Control PDU, RLC control PDU, RLC control PDU).
  • PDCP may be called a PDCP sublayer.
  • PDCP may have a function to perform sequence number maintenance.
  • PDCP may have a header compression/decompression function for efficiently transmitting user data such as IP packets and Ethernet frames over a wireless section.
  • the protocol used to compress and decompress the header of IP packets can be called the ROHC (Robust Header Compression) protocol.
  • the protocol used for compressing and decompressing Ethernet frame headers may be referred to as the EHC (Ethernet (registered trademark) Header Compression) protocol.
  • EHC Errnet (registered trademark) Header Compression
  • PDCP may have data encryption/decryption functions.
  • PDCP may have data integrity protection/integrity verification functions.
  • PDCP may also have a re-ordering function.
  • PDCP may also have a PDCP SDU retransmission function.
  • PDCP may have a function of discarding data using a discard timer.
  • PDCP may have a multiplexing (Duplication) function.
  • PDCP may have a function of discarding data that has been received repeatedly.
  • the PDCP entity is a bidirectional entity and may include 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.
  • the PDCP PDU may include a data PDCP PDU and a control PDCP PDU.
  • the data PDCP PDU may be called a PDCP DATA PDU (PDCP Data PDU).
  • the control PDCP PDU may be called a PDCP CONTROL PDU (PDCP Control PDU, PDCP control PDU, PDCP control PDU).
  • SDAP is a service data adaptation protocol layer.
  • SDAP maps the downlink QoS flow sent from 5GC110 to the terminal device via the base station device and the data radio bearer (DRB), and/or the mapping from the terminal device to the terminal device via the base station device. It may have a function to map uplink QoS flows sent to 5GC110 and DRB.
  • SDAP may also have a function of storing mapping rule information.
  • SDAP may also have a function of marking a QoS flow identifier (QoS Flow ID: QFI).
  • QFI QoS flow ID
  • the SDAP PDU may include a data SDAP PDU and a control SDAP PDU.
  • SDAP PDU for data may be called SDAP DATA PDU (SDAP Data PDU, SDAP data PDU).
  • control SDAP PDU may be called an SDAP CONTROL PDU (SDAP Control PDU, SDAP control PDU, SDAP control PDU). Note that one SDAP entity of the terminal device may exist for a PDU session.
  • RRC may have a broadcast function.
  • the RRC may have a paging function from the EPC 104 and/or 5GC 110.
  • the RRC may have a paging function from the eNB 102 that connects to the gNB 108 or 5GC 110.
  • RRC may also have RRC connection management functionality.
  • RRC may also have radio bearer control functionality.
  • the RRC may also have a cell group control function.
  • the RRC may also have mobility control functionality.
  • the RRC may also have terminal device measurement reporting and terminal device measurement reporting control functions.
  • RRC may also have QoS management functionality.
  • RRC may also have radio link failure detection and recovery functionality.
  • RRC uses RRC messages to perform broadcasting, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, radio link failure detection and recovery, etc. You may do so. Note that the RRC messages and parameters used in E-UTRA RRC may be different from the RRC messages and parameters used in NR RRC.
  • the RRC message may be sent using the BCCH of a logical channel, the PCCH of a logical channel, the CCCH of a logical channel, or the DCCH of a logical channel. May be sent. Furthermore, the RRC message sent using the DCCH may be referred to as dedicated RRC signaling or RRC signaling.
  • the RRC message sent using the BCCH may include, for example, a master information block (MIB), each type of system information block (SIB), and other RRC messages may be included.
  • RRC messages sent using the PCCH may include, for example, paging messages or other RRC messages.
  • RRC messages sent in the uplink (UL) direction using CCCH include, for example, RRC Setup Request message, RRC Resume Request message, RRC Reestablishment Request message, It may include an RRC system information request message (RRC System Info Request), etc. Further, for example, an RRC Connection Request message, an RRC Connection Resume Request message, an RRC Connection Reestablishment Request message, etc. may be included. Other RRC messages may also be included.
  • RRC messages sent in the downlink (DL) direction using CCCH include, for example, RRC Connection Reject message, RRC Connection Setup message, RRC Connection Reestablishment message, It may include an RRC Connection Reestablishment Reject message, etc. Further, for example, an RRC rejection message (RRC Reject), an RRC Setup message (RRC Setup), etc. may be included. Other RRC messages may also be included.
  • RRC signaling sent in the uplink (UL) direction using DCCH includes, for example, measurement report messages, RRC Connection Reconfiguration Complete messages, and RRC Connection Setup Complete messages. ), an RRC Connection Reestablishment Complete message, a Security Mode Complete message, a UE Capability Information message, and the like. Also, for example, measurement report message (Measurement Report), RRC Reconfiguration Complete message, RRC Setup Complete message, RRC Reestablishment Complete message, RRC Resume Complete message. ), a security mode complete message (Security Mode Complete), a UE Capability Information message, and the like may be included. Other RRC signaling may also be included.
  • RRC signaling sent in the downlink (DL) direction using DCCH includes, for example, RRC Connection Reconfiguration message, RRC Connection Release message, Security Mode Command message, It may include a UE Capability Inquiry message, etc. Also, for example, RRC Reconfiguration message, RRC Resume message, RRC Release message, RRC Reestablishment message, Security Mode Command message, UE capability inquiry message. (UE Capability Inquiry) etc. may be included. Other RRC signaling may also be included.
  • the NAS may have an authentication function.
  • the NAS may also have the ability to perform mobility management.
  • the NAS may also have security control functions.
  • the UE 122 connecting to the EPC or 5GC may be in the RRC_CONNECTED state when the RRC connection has been established.
  • the state in which the RRC connection is established may include a state in which the UE 122 holds some or all of the UE context described below.
  • the state in which the RRC connection is established may include a state in which the UE 122 can transmit and/or receive unicast data.
  • the UE 122 when the RRC connection is suspended, the UE 122 may be in the RRC_INACTIVE state. Further, the UE 122 may enter the RRC_INACTIVE state when the UE 122 is connected to the 5GC and the RRC connection is suspended.
  • the UE 122 may be in the RRC_IDLE state.
  • the E-UTRAN may start suspending the RRC connection.
  • the UE 122 may transition to the RRC_IDLE state while retaining the UE's AS context and an identifier (resumeIdentity) used for resuming.
  • the layer above the RRC layer of the UE 122 (for example, the NAS layer) is configured such that the UE 122 maintains the UE's AS context, the E-UTRAN permits the return of the RRC connection, and the UE 122 leaves the RRC_IDLE state.
  • recovery of the suspended RRC connection may be initiated.
  • the definition of pause may be different between the UE 122 connecting to the EPC 104 and the UE 122 connecting to the 5GC 110. Also, when the UE122 is connected to the EPC (when the UE122 is inactive in the RRC_IDLE state) and when the UE122 is connected to the 5GC (when the UE122 is inactive in the RRC_INACTIVE state), the UE122 All or part of the procedure for returning from hibernation may be different.
  • RRC_CONNECTED state may be respectively called connected state (connected mode), inactive state (inactive mode), and idle state (idle mode), and RRC connected state (RRC connected mode). , RRC inactive mode, and RRC idle mode.
  • the AS context of the UE held by the UE122 includes the current RRC settings, the current security context, the PDCP state including the ROHC (RObust Header Compression) state, and the C-RNTI (Cell Radio) used in the PCell of the connection source (Source).
  • the information may include all or part of the Network Temporary Identifier, cell identifier (cellIdentity), and physical cell identifier of the connection source PCell.
  • the UE AS context held by any or all of eNB 102 and gNB 108 may include the same information as the UE AS context held by UE 122, or the information contained in the UE AS context held by UE 122. may contain information different from that.
  • the security context includes the encryption key at the AS level, the NH (Next Hop parameter), the NCC (Next Hop Chaining Counter parameter) used to derive the next hop access key, the identifier of the selected AS-level encryption algorithm, and replay protection.
  • the information may include all or part of the counter used for
  • the serving cell In a terminal device in an RRC connected state in which CA and/or DC, which will be described later, are not configured, the serving cell may be configured from one primary cell (PCell).
  • multiple serving cells include one or more special cells (Special Cell: SpCell) and one or more all secondary cells. It may mean a set of cells (set of cells) consisting of cells (Secondary Cell: SCell).
  • the SpCell may support PUCCH transmission and contention-based Random Access (CBRA), and the SpCell may be activated at all times.
  • CBRA contention-based Random Access
  • the PCell may be a cell used in an RRC connection establishment procedure when a terminal device in an RRC idle state transitions to an RRC connected state. Further, the PCell may be a cell used in an RRC connection re-establishment procedure in which a terminal device re-establishes an RRC connection. Further, the PCell may be a cell used in a random access procedure during handover. The PSCell may be a cell used in a random access procedure when adding a secondary node, which will be described later. Further, SpCell may be a cell used for purposes other than those described above.
  • the serving cell group configured for the terminal device is composed of an SpCell and one or more SCells, it may be considered that carrier aggregation (CA) is configured for the terminal device.
  • CA carrier aggregation
  • a cell that provides additional radio resources to SpCell for a terminal device in which CA is configured may mean SCell.
  • TAG timing advance group
  • the TAG including SpCell of the MAC entity may mean a primary timing advance group (PTAG).
  • TAGs other than the above-mentioned PTAG may mean secondary timing advance group (STAG). Note that one or more TAGs may be configured for each cell group, which will be described later.
  • a cell group that is set from a base station device to a terminal device will be explained.
  • a cell group may be composed of one SpCell.
  • a cell group may be composed of one SpCell and one or more SCells. That is, a cell group may be composed of one SpCell and optionally one or more SCells. Further, a cell group may be expressed as a set of cells.
  • Dual Connectivity means that a first base station device (first node) and a second base station device (second node) perform data communication by using the radio resources of the cell groups they respectively configure. It can be technology.
  • a cell group may be added to the terminal device from the base station device.
  • the first base station device may add a second base station device.
  • the first base station device may be called a master node (Master Node: MN).
  • MN master node
  • MCG master cell group
  • the second base station device may be referred to as a secondary node (SN).
  • a cell group configured by a secondary node may be referred to as a secondary cell group (SCG).
  • the master node and the secondary node may be configured within the same base station device.
  • a cell group configured in a terminal device may be referred to as an MCG.
  • the SpCell set in the terminal device may be a PCell.
  • an NR without a DC configured may be called an NR standalone.
  • Multi-Radio Dual Connectivity may be a technology that performs DC using E-UTRA for MCG and NR for SCG. Further, MR-DC may be a technique for performing DC using NR for MCG and E-UTRA for SCG. Further, MR-DC may be a technology that performs DC using NR on both MCG and SCG. MR-DC may be a technology included in DC. As an example of MR-DC that uses E-UTRA for MCG and NR for SCG, there may be EN-DC (E-UTRA-NR Dual Connectivity) that uses EPC for the core network, and NGEN-DC that uses 5GC for the core network. There may be DC (NG-RAN E-UTRA-NR Dual Connectivity).
  • NR-DC that uses NR for MCG and E-UTRA for SCG
  • NE-DC NR-E-UTRA Dual Connectivity
  • NR-DC NR-NR Dual Connectivity
  • one MAC entity may exist for each cell group.
  • a DC or MR-DC when configured in a terminal device, there may be one MAC entity for MCG and one MAC entity for SCG.
  • a MAC entity for MCG in a terminal device may always be established in the terminal device in all states (RRC idle state, RRC connected state, RRC inactive state, etc.).
  • 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 configured by the terminal device receiving RRC signaling from the base station device.
  • SpCell When a MAC entity is associated with an MCG, SpCell may refer to PCell.
  • SpCell may mean a primary SCG cell (Primary SCG Cell: PSCell). Also, if the MAC entity is not associated with a cell group, SpCell may mean PCell. PCell, PSCell, and SCell are serving cells.
  • the MAC entity for MCG may be an E-UTRA MAC entity
  • the MAC entity for SCG may be an NR MAC entity.
  • the MAC entity for MCG may be an NR MAC entity
  • the MAC entity for SCG may be an E-UTRA MAC entity.
  • both the MAC entities for MCG and SCG may be NR MAC entities. Note that the existence of one MAC entity for each cell group can be translated into the existence of one MAC entity for each SpCell. Furthermore, one MAC entity for each cell group may be translated as one MAC entity for each SpCell.
  • a wireless connection may be established by establishing a radio bearer (RB) between the terminal device and the base station device.
  • the radio bearer used for CP may be called a signaling radio bearer (SRB).
  • the radio bearer used for UP may be called a data radio bearer (DRB).
  • Each radio bearer may be assigned a radio bearer identity (ID).
  • the radio bearer identifier for SRB may be called an SRB identity (SRB ID).
  • the radio bearer identifier for DRB may be called a DRB identity (DRB ID).
  • SRB0 to SRB2 may be defined as SRBs of E-UTRA, and SRBs other than these may be defined.
  • SRB0 to SRB3 may be defined as SRBs of NR, and SRBs other than these may be defined.
  • SRB0 may be an SRB for an RRC message that is transmitted and/or received using the CCCH of the logical channel.
  • SRB1 may be an SRB for RRC signaling and for NAS signaling before the establishment of SRB2.
  • RRC signaling transmitted and/or received using SRB1 may include piggybacked NAS signaling.
  • the logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and/or received using SRB1.
  • SRB2 may be an SRB for NAS signaling and for RRC signaling including logged measurement information.
  • the logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and/or received using SRB2.
  • SRB2 may have a lower priority than SRB1.
  • SRB3 may be an SRB for transmitting and/or receiving specific RRC signaling when EN-DC, NGEN-DC, NR-DC, etc. are configured in the terminal device.
  • the logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and/or received using SRB3. Also, other SRBs may be prepared for other uses.
  • DRB may be a radio bearer for user data.
  • the logical channel DTCH may be used for RRC signaling that is transmitted and/or received using the DRB.
  • Radio bearers may include RLC bearers.
  • An RLC bearer may consist of one or two RLC entities and a logical channel. When there are two RLC entities in an RLC bearer, the RLC entities may be a TM RLC entity and/or a transmitting RLC entity and a receiving RLC entity in an RLC entity in unidirectional UM mode.
  • SRB0 may consist of one RLC bearer.
  • the RLC bearer of SRB0 may consist of a TM RLC entity and a logical channel. SRB0 may always be established in the terminal device in all states (RRC idle state, RRC connected state, RRC inactive state, etc.).
  • One SRB1 may be established and/or configured in the terminal device by RRC signaling received from the base station device when the terminal device transitions from the RRC idle state to the RRC connected state.
  • SRB1 may consist of one PDCP entity and one or more RLC bearers.
  • the SRB1 RLC bearer may consist of an AM RLC entity and a logical channel.
  • One SRB2 may be established and/or configured in a terminal device in an RRC connected state with AS security activated by RRC signaling received from the base station device.
  • SRB2 may consist of one PDCP entity and one or more RLC bearers.
  • the SRB2 RLC bearer may consist of an AM RLC entity and a logical channel.
  • the PDCP on the base station device side of SRB1 and SRB2 may be placed in the master node.
  • SRB3 when a secondary node in EN-DC, NGEN-DC, or NR-DC is added or changed, a terminal device in an RRC connection state with AS security activated connects to the base station. One may be established and/or configured in the terminal device by RRC signaling received from the device.
  • SRB3 may be a direct SRB between the terminal device and the secondary node.
  • SRB3 may consist of one PDCP entity and one or more RLC bearers.
  • the SRB3 RLC bearer may consist of an AM RLC entity and a logical channel.
  • PDCP on the base station device side of SRB3 may be placed in a secondary node.
  • One or more DRBs may be established and/or configured in a terminal device in an RRC connected state with AS security activated by RRC signaling that the terminal device receives from the base station device.
  • a DRB may consist of one PDCP entity and one or more RLC bearers.
  • a DRB RLC bearer may consist of an AM or UM RLC entity and a logical channel.
  • the radio bearer in which PDCP is placed in the master node may be referred to as an MN terminated bearer.
  • a radio bearer in which PDCP is placed in a secondary node may be referred to as an SN terminated bearer.
  • a radio bearer in which the RLC bearer exists only in the MCG may be referred to as an MCG bearer.
  • a radio bearer in which the RLC bearer exists only in the SCG may be referred to as an SCG bearer.
  • a radio bearer in which the RLC bearer exists in both the MCG and the SCG may be referred to as a split bearer.
  • the bearer types of SRB1 and SRB2 established/and/or configured in the terminal device may be MN-terminated MCG bearer and/or MN-terminated split bearer.
  • the bearer type of SRB3 established/and/or configured in the terminal device may be an SN termination SCG bearer.
  • the bearer type of the DRB established/and/or configured in the terminal device may be any one of all bearer types.
  • the RLC entity to be established and/or configured may be E-UTRA RLC.
  • the RLC entity to be established and/or configured may be NR RLC.
  • EN-DC is configured in the terminal device
  • the PDCP entity established and/or configured for the MN terminating MCG bearer may be either E-UTRA PDCP or NR PDCP.
  • the PDCP established and/or configured may be NR PDCP.
  • the PDCP entity established and/or configured for the radio bearer in all bearer types may be NR PDCP.
  • a DRB established and/or configured in a terminal device may be linked to one PDU session.
  • One SDAP entity may be established and/or configured for one PDU session at the terminal device.
  • Establishment and/or configuration of the SDAP entity, PDCP entity, RLC entity, and logical channel in the terminal device may be established and/or configured by RRC signaling that the terminal device receives from the base station device.
  • a network configuration in which the master node is eNB 102 and EPC 104 is the core network may be referred to as E-UTRA/EPC.
  • a network configuration in which the master node is the eNB 102 and the 5GC 110 is the core network may be called E-UTRA/5GC.
  • 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 above-mentioned master node may refer to a base station device that communicates with the terminal device.
  • Handover may be a process in which the UE 122 in the RRC connected state changes the serving cell from the source SpCell to the target SpCell. Handover may be performed when UE 122 receives RRC signaling from eNB 102 and/or gNB 108 instructing handover.
  • RRC signaling that instructs handover may be a message regarding reconfiguration of an RRC connection that includes a parameter that instructs handover (for example, an information element named MobilityControlInfo or an information element named ReconfigurationWithSync).
  • a parameter that instructs handover for example, an information element named MobilityControlInfo or an information element named ReconfigurationWithSync.
  • MobilityControlInfo may be referred to as a mobility control setting information element, mobility control setting, or mobility control information.
  • RRC signaling instructing handover may be a message (eg, MobilityFromEUTRACommand or MobilityFromNRCommand) indicating movement to a cell of another RAT.
  • Handover can also be referred to as reconfiguration with sync.
  • the conditions under which the UE 122 can perform handover include some or all of the following: when AS security is activated, when SRB2 is established, and when at least one DRB is established. good.
  • FIG. 4 is a diagram showing an example of a flow of procedures for various settings in RRC according to the present embodiment.
  • FIG. 4 is an example of a flow when RRC signaling is sent from the base station device (eNB 102 and/or gNB 108) to the terminal device (UE 122).
  • the base station device creates an RRC message (step S400).
  • the RRC message may be created in the base station device so that the base station device can distribute system information (SI) and paging messages. Further, the creation of the RRC message in the base station device may be performed so that the base station device can transmit RRC signaling to cause a specific terminal device to perform processing.
  • the processing to be performed on a specific terminal device may include, for example, processing related to security, reconfiguration of an RRC connection, handover to a different RAT, suspension of an RRC connection, release of an RRC connection, and the like.
  • RRC connection reconfiguration processing includes, for example, radio bearer control (establishment, change, release, etc.), cell group control (establishment, addition, change, release, etc.), measurement setting, handover, security key update, etc. may be included.
  • the creation of an RRC message in the base station device may be performed in response to RRC signaling transmitted from the terminal device.
  • the response to RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC restart request, and the like.
  • the RRC message includes information (parameters) for various information notifications and settings. These parameters may be called fields and/or information elements, and may be described using a description method called ASN.1 (Abstract Syntax Notation One).
  • the base station device then transmits the created RRC signaling to the terminal device (step S402).
  • the terminal device performs processing such as setting, if necessary, according to the above-mentioned received RRC signaling (step S404).
  • the terminal device that has performed the processing may transmit RRC signaling for response to the base station device (not shown).
  • RRC signaling is not limited to the above example and may be used for other purposes.
  • RRC on the master node side is used to transfer RRC signaling for settings on the SCG side (cell group settings, radio bearer settings, measurement settings, etc.) to and from the terminal device. good.
  • NR RRC signaling may be included in the form of a container in E-UTRA RRC signaling transmitted and received between eNB 102 and UE 122.
  • E-UTRA RRC signaling may be included in the form of a container in the NR RRC signaling transmitted and received between the gNB 108 and the UE 122.
  • RRC signaling for SCG side configuration may be transmitted and received between the master node and the secondary nodes.
  • NR RRC signaling may be included in E-UTRA RRC signaling transmitted from eNB 102 to UE 122, and NR RRC signaling transmitted from gNB 108 to UE 122.
  • the signaling may include RRC signaling for E-UTRA.
  • FIG. 7 is an example of an ASN.1 description representing fields and/or information elements related to cell group configuration included in a message related to reconfiguration of an RRC connection in NR in FIG. 4.
  • FIG. 8 is an example of an ASN.1 description representing fields and/or information elements related to cell group configuration included in a message related to reconfiguration of an RRC connection in E-UTRA in FIG. 4.
  • ⁇ omitted> and ⁇ omitted> are not part of the notation of ASN.1, and indicate that other information is omitted. shows.
  • the example of ASN.1 does not correctly follow the ASN.1 notation method.
  • the example ASN.1 represents an example of the RRC signaling parameters in this embodiment, and other names and other representations may be used.
  • the parameters described in ASN.1 are sometimes referred to as information elements, without distinguishing them into fields, information elements, etc.
  • fields, information elements, etc. described in ASN.1 and included in RRC signaling may be translated into information or parameters.
  • the message regarding RRC connection reconfiguration may be an RRC reconfiguration message in NR or an RRC connection reconfiguration message in E-UTRA.
  • the information element named CellGroupConfig may be an information element used for setting, changing, releasing, etc. a cell group of MCG or SCG in NR.
  • the information element named CellGroupConfig may include the TCI information element described below.
  • the information element named CellGroupConfig may be referred to as a cell group configuration information element or cell group configuration.
  • this information element named CellGroupConfig may be referred to as the configuration on the SCG side.
  • An information element named SpCellConfig included in an information element named CellGroupConfig may be an information element used for configuring a special cell (SpCell).
  • the information element named SpCellConfig may be rephrased as SpCell configuration information element or SpCell configuration.
  • the information element named DeactivatedSCG-Config-r17 included in the information element named SpCellConfig may be an information element set in SCG deactivation described later.
  • the information element named DeactivatedSCG-Config-r17 can be rephrased as the setting for deactivating the SCG.
  • the information element named DeactivatedSCG-Config-r17 instructs the terminal device whether or not to perform BFD and/or RLM (described later) using PSCell in the inactive state of the SCG, indicated by bfd-and-RLM.
  • the information element named TCI-Info included in the information element named SpCellConfig may be an information element indicating the TCI status.
  • the information element named TCI-Info may be called a TCI information element. Note that the information element named TCI-Info includes a parameter of a BWP identifier, which will be described later, and is indicated by BWP-Id.
  • RLM Radio Link Monitoring
  • a terminal device may perform radio link monitoring using a certain type of reference signal (cell-specific reference signal (CRS), etc.) in a serving cell (PCell and/or PSCell, etc.).
  • the terminal device receives a configuration (radio link monitoring configuration: RadioLinkMonitoringConfig) indicating which reference signal is used for radio link monitoring in the serving cell (PCell and/or PSCell, etc.) from the base station device, and selects the configured one or Radio link monitoring may be performed using multiple reference signals (herein referred to as RLM-RS).
  • RLM-RS multiple reference signals
  • the terminal device may perform wireless link monitoring using other signals.
  • the physical layer processing unit of the terminal device may notify the upper layer that the synchronization is in progress when the serving cell (PCell and/or PSCell, etc.) satisfies the conditions for the synchronization to be in progress.
  • the wireless link monitoring settings may include information indicating the purpose of monitoring and identifier information indicating a 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 SSB-Index of the SSB of the cell. That is, the reference signal may include a synchronization signal.
  • the identifier information indicating the reference signal may include information indicating an identifier linked to a channel state information reference signal (CSI-RS) set in the terminal device.
  • CSI-RS channel state information reference signal
  • a master cell group (MCG) and a secondary cell group (SCG) are configured by the above-mentioned message regarding reconfiguration of an RRC connection.
  • MCG master cell group
  • SCG secondary cell group
  • Each cell group may include a special cell (SpCell) and zero or more other cells (secondary cells: SCell).
  • SpCell special cell
  • SCell secondary cells
  • MCG's SpCell is also called PCell.
  • SpCell of SCG is also called PSCell.
  • Cell inactivation may not be applied to SpCell, but may be applied to SCell.
  • cell inactivation may not be applied to PCell, but may be applied to PSCell. In this case, cell inactivation may be performed differently for SpCell and SCell.
  • Cell activation and deactivation may be handled by a MAC entity that exists for each cell group.
  • the SCell set in the terminal device may be activated and/or deactivated by some or all of (A) to (C) below.
  • (A) Reception of MAC CE that activates/deactivates SCell (B) SCell inactivity timer set for each SCell for which PUCCH is not set (C) SCell inactivity timer set for each SCell set on the terminal device RRC parameters (sCellState)
  • the MAC entity of the terminal device may perform the following processing (AD) for each SCell configured in the cell group.
  • Processing AD If the RRC parameter (sCellState) set in the SCell is set to activated during SCell configuration, or if a MAC CE that activates the SCell is received, the MAC entity of the UE 122 performs processing (AD-1). I do. Otherwise, if a MAC CE that deactivates the SCell is received or the SCell deactivation timer expires in an active SCell, the MAC entity of the UE 122 performs processing (AD-2).
  • an uplink grant or downlink assignment is notified by the PDCCH of an active SCell, or if an uplink grant or downlink assignment is notified by the PDCCH of a serving cell. If a MAC PDU is transmitted in the uplink grant or received in the configured downlink assignment, the MAC entity of UE 122 restarts the SCell inactivity timer associated with that SCell. If the SCell becomes inactive, the MAC entity of the UE 122 performs processing (AD-3).
  • (A) (Re)initialize all suspended configured uplink grants of grant type 1 associated with this SCell according to the stored configuration, if any.
  • (B) Trigger PHR. If a MAC CE that activates an SCell is received, and the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) configured in RRC signaling for that SCell is set to a dormant (Dormant) BWP. If not, the MAC entity of the UE 122 performs processing (AD-1A).
  • MAC CE that activates an SCell is received, and the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) configured in RRC signaling for that SCell is set to a dormant (Dormant) BWP. If so, the MAC entity of the UE 122 performs processing (AD-1B). Additionally, the MAC entity of the UE 122 implements some or all of (A) to (B) below.
  • the MAC entity of the UE 122 activates the SCell and implements some or all of (A) to (E) below.
  • A) Transmit a sounding reference signal (SRS) with this SCell.
  • B) Report the CSI for this SCell.
  • C) Monitor the PDCCH of this SCell.
  • D) Monitor the PDCCH for this SCell. (When scheduling for this SCell is done in another serving cell)
  • E) If PUCCH is set, transmit PUCCH with this SCell.
  • the UE 122's MAC entity stops this serving cell's BWP inactivity timer if it is running.
  • the MAC entity of UE 122 implements some or all of (A) to (F) below.
  • A Inactivate this SCell.
  • B Stop the SCell inactivity timer associated with this SCell.
  • C Inactivate all Active BWPs associated with this SCell.
  • D Clear all configured downlink assignments and/or all grant type 2 configured uplink grants associated with this SCell.
  • E Suspend all grant type 1 configured uplink grants associated with this SCell.
  • the MAC entity of UE 122 implements some or all of (A) to (D) below.
  • A) Do not send SRS with this SCell.
  • B) Do not report CSI for this SCell.
  • C Do not transmit PUCCH, UL-SCH, and/or RACH on this SCell.
  • D Do not monitor the PDCCH of this SCell and/or the PDCCH for this SCell.
  • the MAC entity performs processing (AD) to activate and deactivate SCell.
  • the initial state of the SCell may be set by RRC signaling.
  • 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 RRC signaling.
  • the timer is started or restarted and the time notified without stopping (here The timer is considered to have expired when the timer (40ms) has elapsed.
  • the SCell inactivation timer may be a timer named sCellDeactivationTimer.
  • timeAlignmentTimer set in RRC to maintain time alignment in uplink (UL)
  • timeAlignmentTimer may be set for each TAG.
  • the timeAlignmentTimer may also control the period during which the MAC entity considers the serving cells belonging to the associated TAG to be synchronized with the UL time.
  • timeAlignmentTimer is also referred to as TAT.
  • the MAC entity performs some or all of (A) through (E) below.
  • PT (A) Flush the HARQ buffers for all serving cells belonging to the PTAG.
  • B Inform the RRC to release the PUCCH for all serving cells belonging to the PTAG, if any.
  • C Inform the RRC to release the SRS for all serving cells belonging to the PTAG, if any.
  • D Clear all configured downlink assignments and/or all configured uplink grants.
  • E Consider all running timeAlignmentTimers to have expired.
  • the MAC entity performs some or all of (A) to (D) below for all serving cells belonging to this TAG.
  • Inactivation of SCG may mean inactivating SCG.
  • deactivating an SCG may mean deactivating a cell group in which a MAC entity is associated with the SCG and corresponds to the MAC entity.
  • inactivation of SCG may mean inactivation of PSCell (SpCell of SCG) or inactivation of PSCell.
  • Activating the SCG may mean activating the SCG.
  • activation of an SCG may mean activating a cell group in which a MAC entity is associated with the SCG and corresponds to the MAC entity.
  • activation of SCG may mean activation of PSCell (SpCell of SCG) or activation of PSCell.
  • the inactive state of an SCG may be a state in which a terminal device implements some or all of the following (A) to (P) in the PSCell (SpCell) of the SCG. Furthermore, the inactive state of the SCG may mean a state in which the SCG is inactivated (a state in which the SCG is dormant).
  • SD-1 (A) Do not send SRS with this PSCell.
  • B Do not measure CSI for this PSCell.
  • C Do not report CSI for this PSCell.
  • D Do not transmit PUCCH with this PSCell.
  • E Do not transmit UL-SCH with this PSCell.
  • (L) BWP is activated in this PSCell, and PDCCH of this PSCell addressed to C-RNTI, MCS-C-RNTI, and/or CS-RNTI indicating uplink grant in the above-mentioned BWP, and /Or do not monitor PDCCH for this PSCell.
  • M This PSCell performs automatic amplification control (AGC), beam failure detection (BFD) including beam failure recovery, and/or radio link monitoring (Radio Link Monitoring: RLM).
  • (N) Suspend some or all configured uplink grants of grant type 1 associated with this PSCell.
  • TAT timeAlignmentTimer
  • (M) in (SD-1) above may be implemented based on the parameters bfd-and-RLM included in the settings on the SCG side.
  • (P) in (SD-1) above may include part or all of (A) to (O) in (SD-1) above. Furthermore, (P) in (SD-1) above may include part or all of (P-1) to (P-15) below.
  • (P-1) Initialize the parameter Bj set for each logical channel to 0.
  • P-2) All timers associated with the PSCell, except for the timer (beamFailureDetectionTimer) and timeAlignmentTimer (TAT) used to perform BFD, are stopped if they are running.
  • (P-3) Set the New Data Indicator (NDI) value of all uplink HARQ processes to 0.
  • P-5) Destroy explicitly signaled 4-step and 2-step RA type contention-free random access (CFRA) resources, if any.
  • P-6) Flush the Msg3 buffer.
  • P-7) Flush the MSGA buffer.
  • P-8) Cancel the triggered SR procedure, if any.
  • P-9) Cancel the triggered BSR procedure, if any.
  • P-10) Cancel the triggered PHR procedure, if any.
  • P-11 Cancel the triggered configured uplink grant confirmation, if any.
  • P-12 Flush the soft buffers of all downlink HARQ processes.
  • P-13) In each downlink HARQ process, consider the next received transmission for a certain transport block (TB) to be the very first transmission.
  • P-14 If available, release Temporary C-RNTI.
  • P-15 Reset all BFI_COUNTERs, except for the counter (BFI_COUNTER) used to perform BFD, which is associated with the PSCell.
  • the active state of an SCG may be a state in which a terminal device implements some or all of the following (A) to (O) in the PSCell (SpCell) of the SCG. Furthermore, the active state of the SCG may mean a state in which the SCG is activated (a state in which the SCG is not dormant).
  • SA-1 (A) Send SRS with this PSCell.
  • B Measure the CSI for this PSCell.
  • C Report the CSI for this PSCell.
  • D Transmit PUCCH with this PSCell.
  • E Transmit UL-SCH with this PSCell.
  • F Send RACH with this PSCell.
  • G Monitor the PDCCH of this PSCell.
  • This PSCell performs automatic amplification control (AGC), beam failure detection (BFD) including beam failure recovery, and/or radio link monitoring (Radio Link Monitoring: RLM).
  • AGC automatic amplification control
  • BFD beam failure detection
  • RLM Radio Link Monitoring: RLM.
  • N (Re)initialize some or all suspended configured uplink grants of grant type 1 associated with this PSCell according to the stored configuration, if any. .
  • O Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) that includes this PSCell.
  • TAT timeAlignmentTimer
  • a terminal device may determine that the SCG is in an inactive state based on some or all of (A) to (H) below.
  • the signaling and control elements (A) to (F) below may be notified from the base station device to the terminal device via the SCG.
  • the following signaling and control elements (A) to (F) are notified from the base station device to the terminal device via a cell group other than the relevant SCG (MCG, SCG other than the relevant SCG, etc.) It's okay to be.
  • SD-2 (A) Reception of RRC signaling instructing to deactivate SCG (B) Reception of MAC CE instructing to deactivate SCG (C) Reception of RRC signaling instructing to deactivate PSCell (D ) Reception of MAC CE instructing to deactivate PSCell (E) Reception of other RRC signaling (F) Reception of other MAC CE (G) Expiration of SCG inactivity timer (H) PSCell inactivity timer expiry of
  • the RRC signaling of (A), (C), and (E) in (SD-2) above may include, for example, a parameter called scg-State.
  • Inclusion of scg-State in RRC signaling may indicate that SCG is inactivated.
  • the fact that scg-State is not included in RRC signaling may indicate that SCG is activated.
  • the RRC signaling including an instruction to activate the SCG may mean that the RRC signaling does not include an instruction to deactivate the SCG.
  • the fact that the RRC signaling does not include an instruction to deactivate the SCG may mean that the parameter called scg-State is not included in the RRC signaling.
  • Including an instruction to deactivate the SCG in RRC signaling may mean that the parameter called scg-State is included in RRC signaling. Further, the parameter scg-State may be information instructing inactivation of the SCG. Additionally, scg-State may be included in the RRC reconfiguration message or the RRC restart message. Further, the RRC signaling may be generated by the MN.
  • FIG. 11 is a diagram showing an example of an embodiment.
  • the processing unit 502 of the UE 122 determines that the SCG is in an inactive state based on (SD-2) above (step S1100). Further, the processing unit 502 of the UE 122 deactivates the SCG based on the determination, and performs the operation shown in (SD-1) above in the inactive state of the SCG (step S1102).
  • a terminal device may determine that the SCG is active based on some or all of (A) to (K) below.
  • the signaling and control elements (A) to (F) below may be notified from the base station device to the terminal device via the SCG.
  • the following signaling and control elements (A) to (F) are notified from the base station device to the terminal device via a cell group other than the relevant SCG (MCG, SCG other than the relevant SCG, etc.) It's okay to be.
  • the SCG being in an active state may mean that the SCG is not in an inactive state.
  • SA-2 (A) Reception of RRC signaling instructing to activate SCG (B) Reception of MAC CE instructing to activate SCG (C) Reception of RRC signaling instructing to activate PSCell (D) Reception of RRC signaling instructing to activate PSCell Reception of MAC CE instructing activation (E) Reception of other RRC signaling (F) Reception of other MAC CE (G) SCG inactivity timer (H) PSCell inactivity timer (I) MAC SDU (J) Initiation of a random access procedure due to a scheduling request triggered to send the included MAC PDU (K) Random (in other words initiated by the MAC entity itself) resulting from a scheduling request Starting the access procedure
  • the parameter scg-State is not included in the RRC reconfiguration message and/or the RRC restart message. good. Further, the RRC signaling may be generated by the MN.
  • FIG. 10 is a diagram showing an example of an embodiment.
  • the processing unit 502 of the UE 122 determines that the SCG is in the active state based on (SA-2) above (step S1000). Furthermore, the processing unit 502 of the UE 122 activates the SCG based on the determination, and performs the operation shown in (SA-1) above in the active state of the SCG (step S1002).
  • a terminal device that deactivates an SCG may implement some or all of the following (A) to (I) in the SCG.
  • SD-3 (A) Consider that SCG is inactivated. (B) Instruct the lower layer (MAC entity, etc.) to deactivate the SCG. (C) If the terminal device is in the RRC_CONNECTED state and the SCG was activated before receiving the signaling instructing to deactivate the SCG, it sends an RRC reconfiguration message or an RRC connection reconfiguration message.
  • the SRB3 is configured before the reception, and the SRB3 is released according to the RRC signaling (RadioBearerConfig) for radio bearer configuration included in the RRC reconfiguration message or the RRC connection reconfiguration message.
  • the process (AD) if a MAC CE that activates the SCell is received, and there is no instruction to deactivate the SCG (or the SCG is not in an inactive state), the process (AD- Do 1).
  • AD- 2 Execute the above process (AD-2).
  • the process (AD-2) is performed.
  • the MAC entity of the terminal device deactivates all of the SCG.
  • PSCell may be inactivated based on (SD-1) above.
  • a terminal device that activates an SCG may implement some or all of the following (A) to (D) in the SCG.
  • SA-3 (A) Consider that the SCG is activated.
  • B If an inactive SCG is set before the terminal device receives the signaling instructing to activate the SCG, it instructs the lower layer (MAC entity, etc.) to activate the SCG.
  • C Perform processing (AD-1) to activate all SCells.
  • D When SCG activation is performed based on RRC signaling, if this RRC signaling includes parameters related to random access to the PSCell (SpCell), the random access procedure is performed in this PSCell based on the notified parameters. Start.
  • the MAC entity of the terminal device shall ) may be used to activate the SCG.
  • the RRC entity of the terminal device shall A layer (such as a MAC entity) may be instructed to start a random access procedure in the PSCell of the SCG.
  • EN-DC or NGEN-DC is configured on the terminal device, and the RRC reconfiguration message is sent from E-UTRA's SRB1 or E-UTRA's RRC connection reconfiguration message (from NR standalone (NG ) the SCG is not deactivated, according to the RRC signaling of the E-UTRA received via (handover to EN-DC) and containing an RRC reconfiguration message in the form of a container for configuration on the SCG side;
  • the following (A-1) or (A-2) must be met.
  • (A-1) Reconfiguration with synchronization was included in the SCG SpCell configuration.
  • (A-2) Before receiving the E-UTRA RRC signaling containing the RRC reconfiguration message for SCG side configuration in the form of a container, the SCG is inactivated, as described in (A). And, it satisfies at least one or more of the following (A-2-1) to (A-2-4).
  • a wireless link failure is detected in the SCG.
  • A-2-2 It is set to perform RLM on the PSCell in the inactive state of the SCG, and a special notification (indication #A) is notified from the lower layer (MAC entity, etc.).
  • A-2-3) A special notification (indication #B) is notified from a lower layer (MAC entity, etc.).
  • A-2-4 PSCell is not set to perform RLM in the inactive state of SCG.
  • a special notification is notified from a lower layer (MAC entity, etc.).
  • A-2-3 may be replaced with the following (A-2-3').
  • a special notification (indication #B) has been notified from a lower layer (such as a MAC entity), and the indication #B has not been canceled.
  • (B) NR-DC is configured in the terminal device, the RRC reconfiguration message is received via SRB1 of the SCG, and the RRC signaling of the NR includes the RRC reconfiguration message for configuration on the SCG side in the form of a container. According to the above, SCG is not inactivated and the following (B-1) or (B-2) is satisfied.
  • (B-1) Reconfiguration with synchronization was included in the SCG SpCell configuration.
  • (B-2) Before receiving the NR RRC signaling containing the RRC reconfiguration message for SCG side configuration in the form of a container as described in (B), the SCG is inactivated, and Satisfies at least one of (A-2-1) to (A-2-4) above.
  • Whether or not RLM is set to be performed on the PSCell in the inactive state of the SCG may be set using the parameter bfd-and-RLM in FIG. 7.
  • the above-mentioned setting to perform RLM in the PSCell in the inactive state of the SCG means that the parameter indicates that the RLM is performed in the PSCell in the inactive state of the SCG, or The parameters may be included in the settings on the SCG side.
  • the above-mentioned "not set to perform RLM in the PSCell in the inactive state of the SCG" means that the parameter indicates that the RLM is not performed in the inactive state of the SCG in the PSCell, or The parameter may not be included in the settings on the SCG side.
  • FIG. 9 is a diagram showing an example of an embodiment.
  • the UE 122 receives signaling (RRC signaling, MAC CE, etc.) instructing to deactivate the SCG from the eNB 102 or gNB 108 (step S900). Based on the notification, the UE 122 controls some or all of the cells of the SCG to be inactive (step S902).
  • signaling RRC signaling, MAC CE, etc.
  • the transmitting unit 504 of the UE 122 does not need to independently transmit a MAC CE for changing the cell state of the SCG to an inactive state, and an efficient state can be achieved. Changes are possible. Additionally, when SCG deactivation is performed based on RRC signaling, conventionally the initial state was set at the RRC layer and the state changed at the MAC layer. It is possible to efficiently change the SCG state while avoiding mismatches between instructions and MAC layer instructions.
  • FIG. 5 is a block diagram showing the configuration of the terminal device (UE 122) in this embodiment. Note that in order to avoid complicating the explanation, FIG. 5 shows only the main components closely related to this embodiment.
  • the UE 122 shown in FIG. 5 includes a receiving unit 500 that receives control information (DCI, RRC signaling, etc.) from a base station device, a processing unit 502 that performs processing according to parameters included in the received control information, and a base station device. It consists of a transmitter 504 that transmits control information (UCI, RRC signaling, etc.).
  • the above-mentioned base station device may be eNB102 or gNB108.
  • the processing unit 502 may include some or all of the functions of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 502 includes some 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. It's fine.
  • FIG. 6 is a block diagram showing the configuration of the base station device in this embodiment. Note that in order to avoid complicating the explanation, FIG. 6 shows only the main components closely related to this embodiment.
  • the above-mentioned base station device may be eNB102 or gNB108.
  • the base station device shown in FIG. a processing unit 602 that causes the processing unit 502 of the UE 122 to perform processing, and a reception unit 604 that receives control information (UCI, RRC signaling, etc.) from the UE 122.
  • the processing unit 602 may include some or all of the functions of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing section 602 includes some or all of the physical layer processing section, MAC layer processing section, RLC layer processing section, PDCP layer processing section, SDAP processing section, RRC layer processing section, and NAS layer processing section. It's fine.
  • FIG. 10 is a diagram showing an example of the processing of the terminal device in this embodiment.
  • the processing unit 502 of the UE 122 may determine that the SCG is in the active state based on (SA-2) above (step S1000). Furthermore, the processing unit 502 of the UE 122 may perform an operation in the active state based on the determination (step S1002).
  • the UE 122 may perform part or all of the processing shown in (SA-1) above in each of the PSCell and/or one or more SCells of a certain cell group.
  • the active state may be a state in which the SCG is activated. Furthermore, the above-mentioned active state may be a state in which the SCG returns from a dormant state. Moreover, the above-mentioned active state may be a state in which the above-mentioned SCG is not in a dormant state. Additionally, the active state described above may be a state that transitions from the inactive state when a random access procedure is initiated due to a scheduling request triggered to transmit a MAC PDU containing the MAC SDU. . Furthermore, the above-mentioned active state may be a state that transitions from an inactive state when a return from a dormant state is instructed by an RRC entity.
  • step S1000 the processing unit 502 of the UE 122 may determine that the SCG has transitioned from the inactive state to the active state, as shown in (SA-2) above.
  • the UE 122 may transition the SCG from an inactive state to an active state (in other words, it may activate the SCG). Furthermore, upon receiving information instructing the SCG to resume from the dormant state, the UE 122 may cause the SCG to transition from the inactive state to the active state. Furthermore, upon receiving information instructing the PSCell to return from the dormant state, the UE 122 may transition the SCG from the inactive state to the active state. Further, upon receiving other information, the UE 122 may transition the SCG from the inactive state to the active state. Further, the UE 122 may cause the SCG to transition from an inactive state to an active state based on a timer related to sleep of the SCG.
  • the UE 122 may transition the SCG from an inactive state to an active state based on a timer related to sleep of the PSCell.
  • the UE 122 may also transition the SCG from the inactive state to the active state when initiating a random access procedure due to a scheduling request triggered to transmit a MAC PDU including the MAC SDU.
  • the UE 122 may transition the SCG from an inactive state to an active state.
  • the UE 122 may also transition the SCG from the inactive state to the active state when starting a random access procedure resulting from a scheduling request (in other words, initiated by the MAC entity itself).
  • the MAC entity of the UE 122 may also obtain an instruction to activate the SCG, an instruction to wake up from a dormant SCG, an instruction to wake up a PSCell from a dormant state, and/or other information from the RRC entity of the UE 122. . Further, after the MAC entity obtains the information from the RRC entity, the UE 122 determines that the SCG is in the active state, as shown in (SA-2) above, and changes the SCG from the inactive state to the active state. You may also make a transition. The UE 122 may perform the process shown in (SA-3) above when transitioning the SCG from the inactive state to the active state.
  • FIG. 11 is a diagram showing an example of the processing of the terminal device in this embodiment.
  • the processing unit 502 of the UE 122 may determine that the SCG is in an inactive state based on (SD-2) above (step S1100). Further, the processing unit 502 of the UE 122 may perform an operation in an inactive state based on the above determination (step S1102).
  • the UE 122 may perform part or all of the processing shown in (SD-1) above in each of the PSCell and/or one or more SCells of a certain cell group.
  • the inactive state may be a state in which SCG is inactivated. Furthermore, the above-mentioned inactive state may be entering a dormant SCG. Moreover, the above-mentioned inactive state may be the above-mentioned dormant state of the SCG. Furthermore, the inactive state may be a state in which the PSCell of the SCG and/or the Active BWP of one or more SCells are dormant BWPs. Furthermore, the above-mentioned inactive state may be a state that transitions from the active state when an RRC entity instructs entry to the dormant state.
  • step S1100 the processing unit 502 of the UE 122 may determine that the SCG has transitioned from the active state to the inactive state, as shown in (SD-2) above.
  • the UE 122 may transition the SCG from the active state to the inactive state. Furthermore, upon receiving information instructing entry into a dormant SCG, the UE 122 may cause the SCG to transition from an active state to an inactive state. Furthermore, upon receiving information instructing sleep of the PSCell, the UE 122 may transition the SCG from the active state to the inactive state. Furthermore, upon receiving other information, the UE 122 may transition the SCG from the active state to the inactive state. Further, the UE 122 may cause the SCG to transition from an active state to an inactive state when a timer related to sleep of the SCG expires.
  • the UE 122 may cause the SCG to transition from the active state to the inactive state when a timer related to sleep of the PSCell expires.
  • the MAC entity of the UE 122 may also obtain instructions to deactivate the SCG, instructions to enter a dormant SCG, instructions to sleep the PSCell, and/or other information from the RRC entity of the UE 122. Further, after the MAC entity obtains the above information from the RRC entity, the UE 122 determines that the SCG is in the inactive state, as shown in (SD-2) above, and changes the SCG from the active state to the inactive state. You may also transition to . The UE 122 may perform the process shown in (SD-3) above when transitioning the SCG from the active state to the inactive state.
  • FIGS. 12 and 14 An example of the processing of the terminal device in this embodiment will be explained using FIGS. 12 and 14.
  • FIG. 12 is a diagram showing an example of processing of the terminal device in this embodiment.
  • the UE 122 receives signaling from the base station device, and the RRC entity of the UE 122 makes a decision based on the signaling (step S1200), and operates based on the decision (step S1202).
  • the determination in step S1200 means that, for example, the UE 122 starts resetting the RRC connection based on receiving RRC signaling from the base station device, and based on the fact that the signaling includes an instruction to activate the SCG. Then, the SCG may be activated, and (1) a notification from a lower layer is received, and (2) it may be determined whether a beam has failed in a PSCell included in the SCG.
  • the operation in step S1202 is, for example, if it is determined that the lower layer has not notified that a random access procedure is necessary for TAT expiration, and if it is determined that there is no beam failure in the PSCell, then the random It may not notify the lower layer to start the access procedure, and if it determines that the lower layer has notified that the random access procedure is necessary due to TAT expiration, or there is a beam failure in the said PSCell. If it is determined that this is the case, the lower layer may be notified to start a random access procedure.
  • the determination in step S1200 means that, for example, the UE 122 starts resetting the RRC connection based on receiving RRC signaling from the base station device, and based on the fact that the signaling includes an instruction to activate the SCG. Then, the SCG may be activated, and (1) a notification from a lower layer is received, and (2) it may be determined whether a beam has failed in a PSCell included in the SCG.
  • the operation in step S1202 is, for example, if it is determined that the lower layer has notified that TAT is running, and if it is determined that there is no beam failure in the PSCell included in the SCG, a random access procedure is started.
  • the SCG If it is determined that the lower layer has not been notified that the TAT is running, or if it has been determined that the lower layer has notified that the TAT is running, the SCG If it is determined that a beam has failed in the included PSCell, the lower layer may be notified to start a random access procedure.
  • the determination in step S1200 means that, for example, the UE 122 starts resetting the RRC connection based on receiving RRC signaling from the base station device, and based on the fact that the signaling includes an instruction to activate the SCG. Then, activate the SCG and determine whether or not the BFD-RS for the PSCell included in the SCG has been changed in (1) notification from the lower layer and (2) reconfiguration of the RRC connection. It may be something you do.
  • the operation in step S1202 is, for example, when it is determined that the lower layer has not notified that random access is necessary, or when it has been determined that the lower layer has not notified that a random access procedure is necessary due to a beam failure.
  • the lower layer may not be notified to start the random access procedure, If it is determined that the lower layer has notified that a random access procedure is necessary because the TAT is not running, or that the lower layer has notified that a random access procedure is necessary because of a beam failure, and In resetting the RRC connection, if it is determined that the BFD-RS for the PSCell included in the SCG has not been changed, the lower layer may be notified to start a random access procedure.
  • step S1200 means that, for example, the UE 122 starts resetting the RRC connection based on receiving RRC signaling from the base station device, and that the signaling includes an instruction to activate the SCG.
  • the method may include activating the SCG and determining whether the signaling includes an instruction to change the BFD-RS for the PSCell included in the SCG.
  • the operation in step S1202 is, for example, when it is determined that the signaling includes an instruction to change the BFD-RS for the PSCell included in the SCG, the BFD-RS for the PSCell included in the SCG is The SCG may be activated after changing the RS, and if it is determined that the signaling does not include an instruction to change the BFD-RS for the PSCell included in the SCG, the SCG may be activated after changing the RS.
  • the method may be to activate the SCG without changing the BFD-RS for the PSCell that is to be sent.
  • the determination in step S1200 means that, for example, the UE 122 starts resetting the RRC connection based on receiving RRC signaling from the base station device, and that the signaling includes an instruction to activate the SCG.
  • the method may be based on activating the SCG and determining whether or not a beam has failed in a PSCell included in the SCG.
  • the operation in step S1202 may be not to notify the lower layer to start a random access procedure based on the determination that there is no beam failure in at least the PSCell included in the SCG, and at least the SCG The lower layer may be notified to start a random access procedure based on the determination that a beam has failed in a PSCell included in the PSCell.
  • the determination in step S1200 means that, for example, the UE 122 starts resetting the RRC connection based on receiving RRC signaling from the base station device, and that the signaling includes an instruction to activate the SCG.
  • the method may include activating the SCG and determining whether the signaling includes an instruction to change the BFD-RS for the PSCell included in the SCG.
  • the operation in step S1202 means that, for example, if it is determined that the signaling includes an instruction to change the BFD-RS for the PSCell included in the SCG, the lower layer or if it is determined that the signaling does not include an instruction to change the BFD-RS for the PSCell included in the SCG.
  • the lower layer may not be notified that an instruction to change the BFD-RS for the PSCell included in the SCG is included. Note that instead of notifying that the instruction to change the BFD-RS is included, the BFD-RS included in the signaling may be notified.
  • the determination in step S1200 means that, for example, the UE 122 starts resetting the RRC connection based on receiving RRC signaling from the base station device, and that the signaling includes an instruction to activate the SCG.
  • the method may include activating the SCG and determining whether the signaling includes an instruction to change the BFD-RS for the PSCell included in the SCG.
  • the operation in step S1202 means that, for example, if it is determined that the signaling includes an instruction to change the BFD-RS for the PSCell included in the SCG, the lower layer or if it is determined that the signaling does not include an instruction to change the BFD-RS for the PSCell included in the SCG.
  • the lower layer may be notified that an instruction to change the BFD-RS for the PSCell included in the SCG is not included. Note that instead of notifying that the instruction to change the BFD-RS is included, the BFD-RS included in the signaling may be notified.
  • ⁇ doing'' may include ⁇ determining whether or not the BFD-RS for the PSCell included in the SCG has been changed in reconfiguring the RRC connection based on signaling that includes an instruction to activate the SCG.'' good.
  • the RRC signaling may include a message regarding reconfiguration of an RRC connection.
  • the RRC entity may determine that the beam has failed in the PSCell based on some or all of the following conditions.
  • PSCell beam failure was notified from the lower layer between T1400 and T1404.
  • the signaling including the instruction to activate the SCG received in S1404 does not include the instruction to change the BFD-RS for the PSCell.
  • BFD-RS for PSCell is not changed between T1402 and T1404.
  • the RRC entity may determine that there is no beam failure in the PSCell based on some or all of the following conditions.
  • PSCell beam failure is not notified from the lower layer between T1400 and T1404.
  • the signaling including the instruction to activate the SCG received in S1404 includes the instruction to change the BFD-RS for the PSCell.
  • BFD-RS for PSCell was changed between T1402 and T1404.
  • determining whether or not a beam has failed in the PSCell may be one or a combination of the following determinations.
  • (b) Determine whether the signaling including the instruction to activate the SCG received in S1404 includes an instruction to change the BFD-RS for the PSCell.
  • (c) Determine whether the BFD-RS for the PSCell has been changed between T1402 and T1404.
  • FIGS. 13 and 14 An example of the processing of the terminal device in this embodiment will be explained using FIGS. 13 and 14.
  • FIG. 13 is a diagram showing an example of the processing of the terminal device in this embodiment.
  • the UE 122 receives signaling from the base station device, and the MAC entity of the UE 122 is instructed to activate the SCG from the upper layer, makes a decision based on the notification from the upper layer (step S1300), and performs an operation based on the decision. (Step S1302).
  • the determination is, for example, whether the MAC entity of the UE 122 has been notified from the upper layer that the signaling from the base station device includes an instruction to change the BFD-RS for the PSCell included in the SCG. It may be a matter of determining whether In this case, in step S1302, the operation means, for example, determining that the upper layer has notified that the signaling from the base station device includes at least an instruction to change the BFD-RS for the PSCell included in the SCG. Based on that, the BFD-RS for the PSCells included in the SCG may be changed without notifying upper layers that a random access procedure is required for activation of the SCG.
  • the upper layer is informed that a random access procedure is necessary for activation of the SCG. It may be to notify.
  • the upper level informs that the signaling from the base station device includes an instruction to change the BFD-RS for the PSCell included in the SCG. It may be determined that the notification was received from the layer.
  • the determination may be, for example, that the MAC entity of the UE 122 determines whether the TAT associated with the TAG (PTAG) of the SpCell included in the SCG is running.
  • the operation is, for example, when it is determined that the TAT associated with the PTAG is running, notifying the upper layer that a random access procedure is required for activation of the SCG. and if it is determined that the TAT associated with the PTAG is not running, it may notify upper layers that a random access procedure is required for activation of the SCG. good.
  • the determination may be, for example, that the MAC entity of the UE 122 determines whether the TAT associated with the TAG (PTAG) of the SpCell included in the SCG is running.
  • the operation may be, for example, when it is determined that the TAT associated with the PTAG is running, to notify the upper layer that the TAT is running; If it is determined that the TAT associated with is not running, the upper layer may not be notified that the TAT is running.
  • the determination is, for example, whether the MAC entity of the UE 122 is running the TAT associated with the TAG (PTAG) of the SpCell included in the SCG, and whether there is a beam failure in the PSCell included in the SCG. It may be to judge whether or not.
  • the operation is, for example, when it is determined that the TAT associated with the PTAG is not running, notifying the upper layer that a random access procedure is necessary because the TAT is not running.
  • the upper layer may be notified that a random access procedure is required due to the beam failure. If it is determined that the TAT associated with the PTAG is running and it is determined that there is no beam failure in the PSCell included in the SCG, the upper layer may not be notified that a random access procedure is required.
  • BFD-RS may be a reference signal used for beam failure detection (BFD).
  • BFD-RS also means that in a wireless link monitoring setting that includes identifier information indicating a reference signal, information indicating the purpose of monitoring includes information indicating that the purpose is to monitor beam failures, or information indicating that the wireless link failures are being monitored.
  • the reference signal may be set with information indicating that the signal is used for both monitoring purposes and beam failure monitoring purposes.
  • the "instruction to change BFD-RS" may be "radio link monitoring settings related to BFD-RS included in the message related to RRC reconfiguration". Reconfiguring BFD-RS according to the radio link monitoring settings for BFD-RS included in the message regarding RRC reconfiguration may be referred to as changing BFD-RS.
  • Radio link monitoring settings for BFD-RS include information indicating the purpose of monitoring, information indicating that the purpose is to monitor beam failure, or information indicating the purpose of monitoring wireless link failure and beam failure monitoring. It may refer to a wireless link monitoring setting in which information indicating that both are set is set.
  • the MAC entity of the UE configured to perform BFD for the PSCell included in the inactive SCG receives a beam failure instance notification from the lower layer, it starts the beam failure timer (beamFailureTimer). , or restarts, counts up the beam failure counter (BFI_COUNTER), and notifies the upper layer of the beam failure based on at least the beam failure counter exceeding the beam failure counter threshold (beamFailureInstanceMaxCounter).
  • the beam failure notification by the MAC entity may be the notification in S1402 in FIG. 14.
  • the fact that the beam failure counter exceeds the beam failure counter threshold may be referred to as a beam failure.
  • the value of the beam failure counter may be set to 0 if the beam failure timer expires, or if the beam failure timer, beam failure counter threshold, or BFD-RS is reset by upper layers.
  • the RRC entity notifying the lower layer to start the random access procedure may also mean starting the random access procedure by the MAC entity. Also, the RRC entity not notifying the lower layer to start the random access procedure may be informing the lower layer not to start the random access procedure.
  • the MAC entity may initiate the random access procedure based on at least being notified by an upper layer to initiate the random access procedure.
  • the MAC entity may also not initiate the random access procedure based on at least the fact that the upper layer has not been notified to initiate the random access procedure.
  • the MAC entity may also initiate the random access procedure based on other factors (ie, the MAC entity's decision) even if the upper layer has not been notified to initiate the random access procedure.
  • step S1400 the UE 122 may receive signaling including an instruction to deactivate the SCG from the base station apparatus, and deactivate the SCG. Further, the RRC entity may notify the MAC entity that the SCG will be deactivated, based on signaling received from the base station apparatus and including an instruction to deactivate the SCG (S1400a). Further, in step S1404, the UE 122 may receive signaling including an instruction to activate the SCG from the base station apparatus, and activate the SCG.
  • the RRC entity may notify the MAC entity that the SCG will be activated based on the signaling that includes the instruction to activate the SCG received from the base station device (S1404a).
  • the SCG may be inactivated from time T1400 until the UE activates the SCG in S1404.
  • the state of the SCG from T1400 until the UE activates the SCG in S1404 may be referred to as the inactive state of the SCG.
  • Time T1402 may be the time when the beam failure was last notified from the MAC entity to the RRC entity at time T1404.
  • the MAC entity may notify the RRC entity in case of beam failure (step S1402). Additionally, the MAC entity may notify the RRC entity of beam failure multiple times between T1400 and T1402.
  • the UE 122 may receive signaling including an instruction to activate the SCG from the base station apparatus, activate the SCG, and perform the determinations in S1200 and S1300, and may perform the operations in S1202 and S1302.
  • Non-Patent Document 7 and Non-Patent Document 8 when the UE receives signaling including an instruction to activate the SCG and an instruction to change the BFD-RS from the base station device when the SCG is deactivated, , when the UE activates the SCG, it starts a random access procedure based on the beam failure at least at the time of receiving the signaling.
  • the RRC, MAC entity of the UE determines whether the instruction to activate the SCG and the instruction to change the BFD-RS are included in the same signaling, so that the RRC and MAC entities of the UE can Even if a beam failure occurs, it can be appropriately determined whether random access is required when activating the SCG.
  • the RRC entity can efficiently perform necessary signaling by instructing the MAC entity to start a random access procedure only when necessary.
  • the MAC entity of the UE may determine some or all of the following (A) to (C), and may notify the RRC entity of indication #A based on those determinations.
  • B The SCG is in an inactive state
  • C Setting to perform RLM on the SCG's PSCell in the SCG's inactive state notification from the RRC entity that the
  • the MAC entity of the UE determines some or all of the following (A) to (C), and based on those determinations, notifies the RRC entity of indication #B. You may do so.
  • the SCG is inactive
  • B Detection of beam failure (BF) in the PSCell
  • C The PSCell of the SCG is configured to perform BFD
  • indication #A may be a notification (signaling) indicating (A) and/or (B) below. In addition to or in place of that, indication #A may be a notification (signaling) indicating something other than (A) or (B) below.
  • A A random access procedure is required when activating the SCG.
  • B The TAT associated with the TAG (PTAG) containing the SCG's PSCell has expired.
  • indication #B may be a notification (signaling) indicating the following (A) and/or (B). In addition to or in place of that, indication #B may be a notification (signaling) indicating something other than (A) or (B) below.
  • A A random access procedure is required when activating the SCG.
  • B A beam failure was detected in the SCG's PSCell.
  • the RRC entity of the UE may cancel indication #B based on some or all of the following (A) to (C). Additionally or alternatively, the RRC entity of the UE may cancel indication #B based on any of the following (A) to (C).
  • BFD RS reference signal used for BFD has been changed.
  • the beam failure detected by the SCG PSCell has been recovered.
  • the random access procedure in the above description may be the random access procedure described in part or all of (I) to (K) of (SA-2) above.
  • radio bearer in the above description may be a DRB, an SRB, or a DRB and an SRB, unless otherwise specified.
  • SpCell of SCG may be replaced with "PSCell”.
  • condition "A” and the condition “B” are contradictory conditions, the condition “B” may be expressed as an “other” condition of the condition "A”. good.
  • the program that runs on the device related to this embodiment may be a program that controls a Central Processing Unit (CPU) or the like to make the computer function so as to realize the functions of this embodiment.
  • Programs or information handled by programs are temporarily read into volatile memory such as Random Access Memory (RAM) during processing, or stored in non-volatile memory such as flash memory or Hard Disk Drive (HDD), and are stored as needed.
  • RAM Random Access Memory
  • HDD Hard Disk Drive
  • the program for realizing this control function may be realized by recording it on a computer-readable recording medium and causing the computer system to read and execute the program recorded on this recording medium.
  • the "computer system” herein refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices.
  • the "computer-readable recording medium” may be any of semiconductor recording media, optical recording media, magnetic recording media, and the like.
  • a "computer-readable recording medium” refers to a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In that case, it may also include something that retains a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client. Further, the above-mentioned program may be one for realizing a part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system. .
  • each functional block or feature of the device used in the embodiments described above may be implemented or executed in an electrical circuit, typically an integrated circuit or multiple integrated circuits.
  • An electrical circuit designed to perform the functions described herein may be a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof.
  • a general purpose processor may be a microprocessor, or in the alternative, the processor may be a conventional processor, controller, microcontroller, or state machine.
  • the general-purpose processor or each of the circuits described above may be configured with a digital circuit or an analog circuit. Further, if an integrated circuit technology that replaces the current integrated circuit emerges due to advances in semiconductor technology, it is also possible to use an integrated circuit based on this technology.
  • this embodiment is not limited to the above-described embodiment.
  • the present embodiment is not limited to this, and can be applied to stationary or non-movable electronic equipment installed indoors or outdoors, such as AV equipment, kitchen equipment, etc. It can be applied to terminal devices or communication devices such as cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household equipment.
  • the present invention can be used in, for example, a communication system, a communication device (e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (e.g., a communication chip), or a program. .
  • 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
  • program e.g., a program.
  • E-UTRA 102eNB 104EPC 106NR 108 gNB 110 5GC 112, 114, 116, 118, 120, 124 interface 122 U.E. 200, 300 PHY 202, 302 MAC 204, 304 RLC 206, 306 PDCP 208, 308 RRC 310 SDAP 210, 312 NAS 500, 604 Receiving section 502, 602 processing section 504, 600 transmitter

Landscapes

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

Abstract

L'invention concerne un dispositif terminal qui communique avec un dispositif de station de base et qui comprend une unité de traitement qui communique avec un groupe MCG à l'aide d'un groupe SCG, et une unité de réception qui reçoit une signalisation en provenance du dispositif de station de base. Le groupe SCG comprend au moins une cellule PSCell. L'unité de traitement active le groupe SCG sur la base de la réception, en provenance du dispositif de station de base, d'une signalisation comprenant une instruction pour activer le groupe SCG, et, lorsque le groupe SCG est désactivé Immédiatement avant que la signalisation comprenant l'instruction d'activation du SCG ne soit reçue du dispositif de station de base, il est déterminé si une défaillance de faisceau s'est produite dans la cellule PSCell. Sur la base d'une détermination selon laquelle au moins une défaillance de faisceau n'a pas eu lieu dans la cellule PSCell, une couche inférieure n'est pas avertie de façon à démarrer une procédure d'accès aléatoire. Sur la base d'une détermination selon laquelle au moins une défaillance de faisceau s'est produite dans la cellule PSCell, une couche inférieure est avertie de façon à démarrer une procédure d'accès aléatoire.
PCT/JP2023/010810 2022-04-01 2023-03-20 Dispositif terminal, dispositif de station de base et procédé WO2023189798A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2022061681 2022-04-01
JP2022-061681 2022-04-01

Publications (1)

Publication Number Publication Date
WO2023189798A1 true WO2023189798A1 (fr) 2023-10-05

Family

ID=88201084

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/010810 WO2023189798A1 (fr) 2022-04-01 2023-03-20 Dispositif terminal, dispositif de station de base et procédé

Country Status (1)

Country Link
WO (1) WO2023189798A1 (fr)

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "UE behaviour while SCG is deactivated", 3GPP DRAFT; R2-2203184, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic; 20220221 - 20220303, 15 February 2022 (2022-02-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052114977 *

Similar Documents

Publication Publication Date Title
WO2022071234A1 (fr) Dispositif terminal, procédé de communication et dispositif station de base
WO2022085663A1 (fr) Procédé et circuit intégré
WO2022210285A1 (fr) Équipement terminal, procédé et circuit intégré
WO2022080419A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2022080306A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2023189798A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2023204307A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023189963A1 (fr) Équipement terminal, procédé et circuit intégré
WO2023238820A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023243571A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023153410A1 (fr) Dispositif terminal, procédé, et circuit intégré
JP2023102794A (ja) 端末装置、方法、および、集積回路
WO2023136231A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023042747A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2023042752A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2024005069A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2024005010A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023063342A1 (fr) Dispositif terminal, dispositif de station de base, et procédé
WO2023132370A1 (fr) Dispositif de terminal, procédé et circuit intégré
WO2024009884A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023100981A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023063345A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2023013292A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2023112531A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023112792A1 (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: 23779814

Country of ref document: EP

Kind code of ref document: A1