WO2023013292A1 - Terminal device, base station device, and method - Google Patents
Terminal device, base station device, and method Download PDFInfo
- Publication number
- WO2023013292A1 WO2023013292A1 PCT/JP2022/025375 JP2022025375W WO2023013292A1 WO 2023013292 A1 WO2023013292 A1 WO 2023013292A1 JP 2022025375 W JP2022025375 W JP 2022025375W WO 2023013292 A1 WO2023013292 A1 WO 2023013292A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- rrc
- cell group
- scg
- terminal device
- mac
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 59
- 238000012545 processing Methods 0.000 claims abstract description 115
- 230000005540 biological transmission Effects 0.000 claims abstract description 50
- 238000004891 communication Methods 0.000 abstract description 26
- 230000001360 synchronised effect Effects 0.000 abstract description 7
- 210000004027 cell Anatomy 0.000 description 151
- 230000006870 function Effects 0.000 description 70
- 230000007704 transition Effects 0.000 description 38
- 238000005516 engineering process Methods 0.000 description 23
- 238000010586 diagram Methods 0.000 description 20
- 230000008569 process Effects 0.000 description 20
- 230000009849 deactivation Effects 0.000 description 18
- 230000011664 signaling Effects 0.000 description 14
- 238000005259 measurement Methods 0.000 description 12
- 101001055444 Homo sapiens Mediator of RNA polymerase II transcription subunit 20 Proteins 0.000 description 11
- 102100026165 Mediator of RNA polymerase II transcription subunit 20 Human genes 0.000 description 11
- 230000004913 activation Effects 0.000 description 11
- 238000012544 monitoring process Methods 0.000 description 11
- 101100150275 Caenorhabditis elegans srb-3 gene Proteins 0.000 description 10
- 230000009977 dual effect Effects 0.000 description 10
- 238000007726 management method Methods 0.000 description 10
- 108091005487 SCARB1 Proteins 0.000 description 9
- 102100037118 Scavenger receptor class B member 1 Human genes 0.000 description 9
- 230000004044 response Effects 0.000 description 8
- 230000006835 compression Effects 0.000 description 6
- 238000007906 compression Methods 0.000 description 6
- 230000005059 dormancy Effects 0.000 description 6
- 230000003213 activating effect Effects 0.000 description 5
- 230000006978 adaptation Effects 0.000 description 5
- 230000008859 change Effects 0.000 description 5
- 238000013507 mapping Methods 0.000 description 5
- 238000011084 recovery Methods 0.000 description 5
- 238000009482 thermal adhesion granulation Methods 0.000 description 5
- 230000001960 triggered effect Effects 0.000 description 5
- 230000001413 cellular effect Effects 0.000 description 4
- 230000000415 inactivating effect Effects 0.000 description 4
- 230000002779 inactivation Effects 0.000 description 4
- 230000000977 initiatory effect Effects 0.000 description 4
- 238000010295 mobile communication Methods 0.000 description 4
- 239000000725 suspension Substances 0.000 description 4
- 230000006837 decompression Effects 0.000 description 3
- 238000001514 detection method Methods 0.000 description 3
- 230000014509 gene expression Effects 0.000 description 3
- 230000007958 sleep Effects 0.000 description 3
- 101000652482 Homo sapiens TBC1 domain family member 8 Proteins 0.000 description 2
- 102100030302 TBC1 domain family member 8 Human genes 0.000 description 2
- 230000009471 action Effects 0.000 description 2
- 230000002457 bidirectional effect Effects 0.000 description 2
- 238000012937 correction Methods 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 210000001956 EPC Anatomy 0.000 description 1
- 101150071746 Pbsn gene Proteins 0.000 description 1
- 241000700159 Rattus Species 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000004378 air conditioning Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000020411 cell activation Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000008094 contradictory effect Effects 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 238000013524 data verification Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000002618 waking effect Effects 0.000 description 1
- 238000005406 washing Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
- H04W16/24—Cell structures
- H04W16/32—Hierarchical cell structures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/15—Setup of multiple wireless link connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
Definitions
- the present invention relates to a terminal device, base station device and method.
- This application claims priority to Japanese Patent Application No. 2021-128736 filed in Japan on August 5, 2021, the contents of which are incorporated herein.
- 3GPP 3rd Generation Partnership Project
- E-UTRA Evolved Universal LTE Terrestrial Radio Access
- RAT radio access technology
- 3GPP is still conducting technical studies and establishing standards for extension technologies for E-UTRA.
- E-UTRA is also called Long Term Evolution (LTE: registered trademark), and extended technologies are sometimes called LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).
- NR New Radio or NR Radio access
- RAT Radio Access Technology
- a dual connectivity also called multi-connectivity
- one or more base station devices and terminal devices communicate using a plurality of cell groups.
- a terminal device needs to monitor whether there is a message addressed to itself in each cell group.
- the terminal device In order to enable the terminal device to perform low-delay communication when a large volume of data communication occurs, the terminal device must always monitor a plurality of cell groups, and there has been a problem of consuming a lot of power. Therefore, techniques for monitoring some cell groups infrequently or stopping them (deactivated cell group) technology) was started.
- One aspect of the present invention has been made in view of the circumstances described above, and one object thereof is to provide a terminal device, a base station device, a method, and an integrated circuit capable of efficiently performing communication control.
- one aspect of the present invention takes the following measures. That is, one aspect of the present invention is a terminal device that communicates with a base station device, comprising: a receiving unit that receives an RRC message from the base station device; group and a second cell group are used to communicate, the RRC message includes a first configuration for configuring a special cell included in the second cell group, and the processing unit performs the first includes synchronous reconfiguration, and the processing unit includes an instruction for deactivating the second cell group in the RRC message.
- the processing unit causes the RRC message to: if the instruction to deactivate the second cell group is included, do not resume some suspended radio bearers and resume transmission in said second cell group for some radio bearers; It is a terminal device that does not resume.
- one aspect of the present invention is a base station apparatus that communicates with a terminal device, comprising: a transmission unit that transmits an RRC message to the terminal device; and a second cell group, wherein the RRC message includes a first setting for setting a special cell included in the second cell group, and the processing unit performs communication using the first
- the terminal device is caused to perform reconfiguration with synchronization, and the processing unit includes an instruction for deactivating the second cell group in the RRC message.
- the processing unit comprising: By including an instruction for deactivating the second cell group in the RRC message, the terminal device is prevented from resuming some suspended radio bearers and for some radio bearers.
- the base station apparatus does not restart transmission in the second cell group.
- One aspect of the present invention is a method for a terminal device that communicates with a base station device, which receives an RRC message from the base station device and performs communication using a first cell group and a second cell group. and the RRC message includes a first configuration that configures a special cell included in the second cell group, and based on the fact that the first configuration includes reconfiguration with synchronization, and if the RRC message does not include an instruction to deactivate the second cell group, resume all suspended radio bearers, and some suspended radio bearers if the RRC message includes an instruction to deactivate the second cell group; and not restarting transmission in the second cell group for some radio bearers.
- the terminal device, base station device, method, and integrated circuit can realize efficient communication control processing.
- FIG. 1 is a schematic diagram of a communication system according to an embodiment of the invention
- the figure of an example of the NR protocol structure based on embodiment of this invention.
- the block diagram which shows the structure of the terminal device in embodiment of this invention. 1 is a block diagram showing the configuration of a base station apparatus according to an embodiment of the present invention;
- FIG. 1 is an example of ASN.1 description included in a message regarding RRC connection reconfiguration in E-UTRA according to an embodiment of the present invention.
- An example of processing related to inactivation of SCG in the embodiment of the present invention An example of processing related to activation of SCG in the embodiment of the present invention.
- An example of processing related to inactivation of SCG in the embodiment of the present invention An example of processing related to reconfiguration with synchronization and deactivation of SCG in the embodiment of the present invention.
- LTE (and LTE-A, LTE-A Pro) and NR may be defined as different Radio Access Technologies (RAT).
- RAT Radio Access Technologies
- NR may also be defined as a technology included in LTE.
- LTE may also be defined as a technology included in NR.
- LTE that can be connected by NR and Multi Radio Dual connectivity (MR-DC) may be distinguished from conventional LTE.
- MR-DC Multi Radio Dual connectivity
- LTE using 5GC for the core network may be distinguished from conventional LTE using EPC for the core network.
- EPC Multi Radio Dual connectivity
- Embodiments of the present invention may be applied to NR, LTE and other RATs.
- the term E-UTRA in the embodiments of the present invention may be replaced with the term LTE
- LTE may be replaced with the term E-UTRA.
- each node and entity when the radio access technology is E-UTRA or NR, and the processing in each node and entity will be described. It may be used for other radio access technologies.
- the name of each node or entity in the embodiment of the present invention may be another name.
- FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present invention. It should be noted that the functions of each node, radio access technology, core network, interface, etc. described using FIG. 1 are part of the functions closely related to the embodiment of the present invention, and may have other functions.
- E-UTRA100 may be a radio access technology.
- E-UTRA 100 may also be the air interface between UE 122 and eNB 102 .
- the air interface between UE 122 and eNB 102 may be called Uu interface.
- the eNB (E-UTRAN Node B) 102 may be a base station device for the E-UTRA 100.
- the eNB 102 may have the E-UTRA protocol described below.
- the E-UTRA protocol may consist of an E-UTRA user plane (User Plane: UP) protocol described later and an E-UTRA control plane (Control Plane: CP) protocol described later.
- eNB 102 may terminate E-UTRA User Plane (UP) and E-UTRA Control Plane (CP) protocols to UE 122 .
- a radio access network composed of eNBs may be called E-UTRAN.
- EPC (Evolved Packet Core) 104 may be a core network.
- Interface 112 is the interface between eNB 102 and EPC 104 and may be referred to as the S1 interface.
- Interface 112 may include a control plane interface through which control signals pass, and/or a user plane interface through which user data passes.
- the control plane interface of interface 112 may terminate at a Mobility Management Entity (MME; not shown) within EPC 104 .
- MME Mobility Management Entity
- a user plane interface of interface 112 may terminate at a serving gateway (S-GW; not shown) within EPC 104 .
- the control plane interface of interface 112 may be called the S1-MME interface.
- the user plane interface of interface 112 may be called the S1-U interface.
- one or more eNBs 102 may be connected to EPC 104 via interface 112 . There may be an interface between multiple eNBs 102 that connect to the EPC 104 (not shown). An interface between multiple eNBs 102 connected to an EPC 104 may be called an X2 interface.
- NR106 may be a radio access technology.
- NR 106 may also be the air interface between UE 122 and gNB 108 .
- the air interface between UE 122 and gNB 108 may be called the Uu interface.
- the gNB (g Node B) 108 may be the base station equipment of the NR 106.
- gNB108 may have the NR protocol described below.
- the NR protocol may consist of an NR User Plane (UP) protocol, described below, and an NR Control Plane (CP) protocol, described below.
- gNB 108 may terminate NR User Plane (UP) and NR Control Plane (CP) protocols to UE 122 .
- UP NR User Plane
- CP NR Control Plane
- Interface 116 is the interface between gNB 108 and 5GC 110 and may be called the NG interface.
- Interface 116 may include a control plane interface through which control signals pass, and/or a user plane interface through which user data passes.
- the control plane interface of interface 116 may terminate at the Access and Mobility Management Function (AMF: not shown) within 5GC 110 .
- the user plane interface of interface 116 may terminate at a User Plane Function (UPF: not shown) within 5GC 110 .
- the control plane interface of interface 116 may be called the NG-C interface.
- the user plane interface of interface 116 may be called the NG-U interface.
- one or more gNBs 108 may be connected to the 5GC 110 via interface 116. There may be interfaces between gNBs 108 that connect to the 5GC 110 (not shown). An interface between multiple gNBs 108 connected to a 5GC 110 can be called an Xn interface.
- the eNB102 may have the function of connecting to the 5GC110.
- the eNB 102 that has the function of connecting to the 5GC 110 can be called ng-eNB.
- Interface 114 is an interface between eNB 102 and 5GC 110 and may be called an NG interface.
- Interface 114 may include a control plane interface through which control signals pass, and/or a user plane interface through which user data passes.
- the control plane interface of interface 114 may terminate at the Access and Mobility Management Function (AMF: not shown) within 5GC 110 .
- the user plane interface of interface 114 may terminate at a User Plane Function (UPF: not shown) within 5GC 110 .
- the control plane interface of interface 114 may be called the NG-C interface.
- the user plane interface of interface 114 may be called the NG-U interface.
- a radio access network composed of ng-eNBs or gNBs may be referred to as NG-RAN.
- NG-RAN, E-UTRAN, eNB, ng-eNB, gNB, etc. may simply be referred to as networks.
- one or more eNBs 102 may be connected to the 5GC 110 via an interface 114. There may be an interface between multiple eNBs 102 that connect to the 5GC 110 (not shown). An interface between multiple eNBs 102 connected to a 5GC 110 may be called an Xn interface. Also, the eNB 102 connected to the 5GC 110 and the gNB 108 connected to the 5GC 110 can be connected via an interface 120 . The interface 120 between the eNB 102 connected to the 5GC 110 and the gNB 108 connected to the 5GC 110 can be called the Xn interface.
- the gNB108 may have the ability to connect to the EPC104.
- a gNB 108 with the ability to connect to an EPC 104 may be called an en-gNB.
- Interface 118 is the interface between gNB 108 and EPC 104 and may be referred to as the S1 interface.
- Interface 118 may include a user plane interface through which user data passes.
- a user plane interface of interface 118 may terminate at an S-GW (not shown) within EPC 104 .
- the user plane interface of interface 118 may be called the S1-U interface.
- the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 can be connected by an interface 120 .
- the interface 120 between the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 may be called the X2 interface.
- the interface 124 is the interface between the EPC 104 and the 5GC 110, and can be an interface through CP only, UP only, or both CP and UP. Also, some or all of interfaces 114, 116, 118, 120, 124, etc. may not be present depending on the communication system provided by the carrier.
- UE122 may be a terminal device capable of receiving broadcast information and paging messages transmitted from eNB102 and/or gNB108. Also, UE 122 may be a terminal device capable of wireless connection with eNB 102 and/or gNB 108 . Also, the UE 122 may be a terminal device capable of establishing a wireless connection with the eNB 102 and a wireless connection with the gNB 108 at the same time. UE 122 may have E-UTRA and/or NR protocols. Note that the wireless connection may be a Radio Resource Control (RRC) connection.
- RRC Radio Resource Control
- radio connection may be established by establishing a radio bearer (RB) between UE122 and eNB102 and/or gNB108.
- a radio bearer used for the CP may be called a signaling radio bearer (SRB).
- a radio bearer used for UP may also be called a data radio bearer (DRB Data Radio Bearer).
- Each radio bearer can be assigned a radio bearer identity (ID).
- the SRB radio bearer identifier may be called an SRB identity (SRB ID).
- a DRB radio bearer identifier may be called a DRB identity (DRB ID).
- UE 122 may be a terminal device capable of connecting to EPC 104 and/or 5GC 110 via eNB 102 and/or gNB 108.
- EPC 104 When the connection destination core network of eNB 102 and/or gNB 108 with which UE 122 communicates is EPC 104, each DRB established between UE 122 and eNB 102 and/or gNB 108 further passes through EPC 104.
- EPC 104 Evolved Packet System
- Each EPS bearer can be identified by an EPS bearer identifier (Identity, or ID). Also, the same QoS may be guaranteed for data such as IP packets and Ethernet (registered trademark) frames passing through the same EPS bearer.
- each DRB established between UE122 and eNB102 and/or gNB108 is further established within 5GC110.
- Each DRB may be mapped to one or more QoS flows or not to any QoS flows.
- Each PDU session can be identified with a PDU session identifier (Identity, Identifier, or ID).
- Each QoS flow may also be identified with a QoS flow identifier (Identity, Identifier, or ID).
- the same QoS may be guaranteed for data such as IP packets and Ethernet frames passing through the same QoS flow.
- the EPC 104 does not have to have PDU sessions and/or QoS flows.
- 5GC110 does not need to have an EPS bearer.
- UE 122 When UE 122 is connected to EPC 104, UE 122 has information of EPS bearers, but may not have information within PDU sessions and/or QoS flows. Also, when the UE 122 is connected to the 5GC 110, the UE 122 may have information in PDU sessions and/or QoS flows, but not EPS bearer information.
- eNB 102 and/or gNB 108 are also simply referred to as base station apparatuses, and UE 122 is simply referred to as terminal apparatus or UE.
- FIG. 2 is a diagram of an example of E-UTRA protocol architecture according to an embodiment of the present invention.
- FIG. 3 is a diagram of an example of the NR protocol configuration according to the embodiment of the present invention. Note that the functions of each protocol described using FIG. 2 and/or FIG. 3 are part of the functions closely related to the embodiment of the present invention, and may have other functions.
- an uplink (UL) may be a link from a terminal device to a base station device.
- the downlink (DL) may be a link from the base station apparatus to the terminal apparatus.
- FIG. 2(A) is a diagram of the E-UTRA User Plane (UP) protocol stack.
- the E-UTRAN UP protocol may be the protocol between UE 122 and eNB 102, as shown in FIG. 2(A). That is, the E-UTRANUP protocol may be a protocol that terminates at the eNB 102 on the network side.
- the E-UTRA user plane protocol stack consists of a PHY (Physical layer) 200 that is a radio physical layer (radio physical layer), a MAC (Medium) that is a medium access control layer (medium access control layer). Access Control) 202, RLC (Radio Link Control) 204 as a radio link control layer (radio link control layer), and PDCP (Packet Data Convergence Protocol) 206 as a packet data convergence protocol layer.
- PHY Physical layer
- MAC Medium access control layer
- Access Control 202
- RLC Radio Link Control
- PDCP Packet Data Convergence Protocol
- FIG. 3(A) is a diagram of the NR user plane (UP) protocol stack.
- the NRUP protocol may be the protocol between UE 122 and gNB 108, as shown in FIG. 3(A). That is, the NR UP protocol may be a protocol that terminates at the gNB 108 on the network side.
- the E-UTRA user plane protocol stack consists of PHY 300, which is a radio physical layer, MAC 302, which is a medium access control layer, RLC 304, which is a radio link control layer, and PDCP 306, which is a packet data convergence protocol layer.
- 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
- NAS Non Access Stratum
- non-AS Access Stratum
- the NAS 210 may be a protocol that terminates at the MME on the network side.
- Fig. 3(B) is a diagram of the NR control plane (CP) protocol configuration.
- RRC 308 which is the radio resource control layer, may be the protocol between UE 122 and gNB 108. That is, RRC 308 may be a protocol that terminates at gNB 108 on the network side.
- the non-AS layer NAS 312 may be the protocol between the UE 122 and AMF. That is, the NAS 312 may be a protocol that terminates with AMF on the network side.
- the AS (Access Stratum) layer may be a layer that terminates between UE 122 and eNB 102 and/or gNB 108. That is, the AS layer is a layer including part or all of PHY200, MAC202, RLC204, PDCP206 and RRC208 and/or a layer including part or all of PHY300, MAC302, RLC304, PDCP306, SDAP310 and RRC308. good
- PHY PHY layer
- MAC MAC layer
- RLC RLC layer
- PDCP PDCP layer
- RRC RRC layer
- NAS NAS layer
- PHY PHY layer
- MAC MAC layer
- RLC RLC layer
- PDCP PDCP layer
- RRC RRC layer
- NAS NAS
- SDAP may be the SDAP (SDAP layer) of the NR protocol.
- PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208 are respectively defined as PHY for E-UTRA or PHY for LTE, E-UTRA MAC for LTE or MAC for LTE, RLC for E-UTRA or RLC for LTE, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE.
- PHY200, MAC202, RLC204, PDCP206 and RRC208 respectively E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP and E-UTRA It may also be described as RRC or LTE RRC.
- PHY 300, MAC 302, RLC 304, PDCP 306, and RRC 308 are called PHY for NR, MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively. There is also a thing.
- PHY 200, MAC 302, RLC 304, PDCP 306, and RRC 308 may also be described as NR PHY, NR MAC, NR RLC, NR PDCP, NR RRC, etc., respectively.
- An entity that has some or all of the functionality of the MAC layer may be called a MAC entity.
- An entity that has some or all of the functionality of the RLC layer may be called an RLC entity.
- An entity that has some or all of the functions of the PDCP layer may be called a PDCP entity.
- An entity that has some or all of the functionality of the SDAP layer may be called an SDAP entity.
- An entity that has some or all of the functionality of the RRC layer may be called an RRC entity.
- the MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be replaced with MAC, RLC, PDCP, SDAP, and RRC, respectively.
- the data provided from MAC, RLC, PDCP, SDAP to the lower layer and/or the data provided from the lower layer to MAC, RLC, PDCP, SDAP shall be MAC PDU (Protocol Data Unit), RLC respectively. You can call them PDUs, PDCP PDUs, SDAP PDUs.
- MAC SDU Service Data Unit
- RLC SDU Service Data Unit
- RLC SDU for data provided from upper layers to MAC, RLC, PDCP, and SDAP and/or data provided from MAC, RLC, PDCP, and SDAP to upper layers, respectively , PDCP SDU, SDAP SDU.
- a segmented RLC SDU may also be called an RLC SDU segment.
- the PHY of the terminal device may have a function of receiving data transmitted from the PHY of the base station device via a downlink (DL) physical channel.
- the PHY of the terminal device may have the capability of transmitting data to the PHY of the base station device via an uplink (UL) physical channel.
- a PHY may be connected to a high-level MAC via a Transport Channel.
- the PHY may pass data to the MAC over transport channels.
- the PHY can also be provided with data from the MAC over the transport channel.
- a Radio Network Temporary Identifier (RNTI) can be used in the PHY to identify various control information.
- RNTI Radio Network Temporary Identifier
- the physical channels used for wireless communication between the terminal device and the base station device may include the following physical channels.
- PBCH Physical Broadcast CHannel
- PDCCH Physical Downlink Control CHannel
- PDSCH Physical Downlink Shared CHannel
- PUCCH Physical Uplink Control CHannel
- PUSCH Physical Uplink Shared CHannel
- PRACH Physical Random Access CHannel
- the PBCH may be used to broadcast system information required by terminal equipment.
- the PBCH may be used to report the time index (SSB-Index) within the period of a block of synchronization signals (also called SS/PBCH block).
- SSB-Index time index within the period of a block of synchronization signals
- the PDCCH can be used to transmit (or carry) downlink control information (DCI) in downlink radio communication (radio communication from the base station device to the terminal device).
- DCI downlink control information
- one or more DCIs may be defined for transmission of downlink control information. That is, a field for downlink control information can be defined as DCI and mapped to information bits.
- a PDCCH can be sent in a PDCCH candidate.
- a terminal can monitor a set of PDCCH candidates in a serving cell. Monitoring the set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format.
- the DCI format may be used for PUSCH scheduling in the serving cell. PUSCH may be used for transmission of user data, transmission of RRC messages to be described later, and the like.
- the PUCCH may be used to transmit uplink control information (UCI) in uplink radio communication (radio communication from a terminal device to a base station device).
- the uplink control information may include channel state information (CSI: Channel State Information) used to indicate the state of the downlink channel.
- the uplink control information may include a scheduling request (SR: Scheduling Request) used to request UL-SCH (UL-SCH: Uplink Shared CHannel) resources.
- SR Scheduling Request
- UL-SCH Uplink Shared CHannel
- the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement).
- the PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer.
- PDSCH may be used for transmission of system information (SI: System Information), random access response (RAR: Random Access Response), etc. in the case of downlink.
- SI System Information
- RAR Random Access Response
- PUSCH may be used to transmit HARQ-ACK and/or CSI together with uplink data (UL-SCH: Uplink Shared CHannel) or uplink data from the MAC layer.
- PUSCH may also be used to transmit CSI only, or HARQ-ACK and CSI only. That is, PUSCH may be used to transmit UCI only.
- PDSCH or PUSCH may also be used to transmit RRC signaling (also referred to as RRC messages) and MAC control elements.
- RRC signaling transmitted from the base station apparatus may be signaling common to multiple terminal apparatuses within the cell.
- the RRC signaling transmitted from the base station apparatus may be signaling dedicated to a certain terminal apparatus (also referred to as dedicated signaling). That is, terminal device-specific (UE-specific) information may be transmitted using signaling dedicated to a certain terminal device.
- PUSCH may also be used to transmit UE Capability in the uplink.
- the PRACH may be used to transmit random access preambles.
- PRACH is used to indicate initial connection establishment procedures, handover procedures, connection re-establishment procedures, synchronization (timing adjustments) for uplink transmissions, and requests for UL-SCH resources.
- a MAC may be referred to as a MAC sublayer.
- the MAC may have functionality for mapping various logical channels (Logical Channels) to corresponding transport channels.
- a logical channel may be identified by a Logical Channel Identity (or Logical Channel ID).
- the MAC may be connected with the upper RLC by a logical channel (logical channel).
- Logical channels can be divided into control channels for transmitting control information and traffic channels for transmitting user information according to the type of information to be transmitted.
- Logical channels may also be divided into uplink logical channels and downlink logical channels.
- the MAC may be capable of multiplexing MAC SDUs belonging to one or more different logical channels and providing them to the PHY.
- the MAC may also have the function of demultiplexing the MAC PDUs provided by the PHY and providing them to upper layers via the logical channel to which each MAC SDU belongs. Also, the MAC may 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 the ability to prioritize between terminals using dynamic scheduling. Also, the MAC may have a function of performing priority processing between logical channels within one terminal device. The MAC may have the capability of prioritizing overlapping resources within one terminal device. E-UTRA MAC may have the ability to identify Multimedia Broadcast Multicast Services (MBMS).
- MBMS Multimedia Broadcast Multicast Services
- NR MAC may have a function to identify Multicast/Broadcast Service (MBS).
- MMS Multicast/Broadcast Service
- a MAC may have the ability to select a transport format.
- MAC has a function of performing discontinuous reception (DRX) and / or discontinuous transmission (DTX: discontinuous transmission), a function of executing random access (RA) procedure, notifying information of transmittable power, power It is good to have a headroom report (Power Headroom Report: PHR) function, a buffer status report (BSR) function that notifies the amount of data in the transmission buffer, and so on.
- 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 performing control in MAC.
- uplink Uplink
- DL Downlink
- E-UTRA E-UTRA
- NR NR
- BCCH Broadcast Control Channel
- SI System Information
- PCCH Packet Control Channel
- PCCH Packet Control Channel
- a CCCH (Common Control Channel) may be a logical channel for transmitting control information between a terminal device and a base station device.
- CCCH may be used when the terminal does not have an RRC connection.
- CCCH may also be used between a base station and multiple terminals.
- DCCH Dedicated Control Channel
- DCCH is a logical channel for transmitting dedicated control information in a one-to-one (point-to-point) bi-directional manner between a terminal device and a base station device. It's fine.
- Dedicated control information may be control information dedicated to each terminal device.
- DCCH may be used when a terminal device has an RRC connection.
- a DTCH (Dedicated Traffic Channel) may be a logical channel for transmitting user data on a one-to-one (point-to-point) basis between a terminal device and a base station device.
- a DTCH may be a logical channel for transmitting dedicated user data.
- Dedicated user data may be user data dedicated to each terminal device.
- DTCH may exist in both uplink and downlink.
- CCCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.
- UL-SCH Uplink Shared Channel
- the DCCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.
- UL-SCH Uplink Shared Channel
- DTCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.
- UL-SCH Uplink Shared Channel
- BCCH may be mapped to BCH (Broadcast Channel) and/or DL-SCH (Downlink Shared Channel), which are downlink transport channels.
- BCH Broadcast Channel
- DL-SCH Downlink Shared Channel
- PCCH may be mapped to PCH (Paging Channel), which is a downlink transport channel.
- PCH Packet Control Channel
- CCCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.
- DL-SCH Downlink Shared Channel
- the DCCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.
- DL-SCH Downlink Shared Channel
- DTCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.
- DL-SCH Downlink Shared Channel
- RLC may be referred to as an RLC sublayer.
- the E-UTRA RLC may have the function of segmenting and/or concatenating data provided from the upper layer PDCP and providing it to the lower layer.
- E-UTRA RLC may have the capability to reassemble and re-order data provided by lower layers and provide it to upper layers.
- the NR RLC may have a function of adding a sequence number independent of the sequence number added by PDCP to the data provided by PDCP of the upper layer.
- 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 reassembled data to upper layers.
- the RLC may also have a data retransmission function and/or a retransmission request function (Automatic Repeat reQuest: ARQ). Also, RLC may have a function of performing error correction by ARQ.
- the control information sent from the RLC receiving side to the transmitting side in order to perform ARQ, indicating data that needs to be retransmitted, can be called a status report. Also, the status report transmission instruction sent from the RLC transmitting side to the receiving side can be called a poll.
- RLC may also have a function to detect data duplication. RLC may also have a function of data discarding. RLC may have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM).
- the TM does not divide the data received from the upper layer, and does not need to add an RLC header.
- a TM RLC entity is a uni-directional entity and may be configured as a transmitting TM RLC entity or as a receiving TM RLC entity.
- the UM divides and/or combines the data received from the upper layer, adds an RLC header, etc., but does not need to perform data retransmission control.
- a UM RLC entity may be a unidirectional entity or a bi-directional entity. If the UM RLC entity is a unidirectional entity, the UM RLC entity may be configured as a transmitting UM RLC entity or as a receiving UM RLC entity.
- the UM RRC entity may be configured as a UM RLC entity consisting of a transmitting side and a receiving side.
- the AM may divide and/or combine data received from the upper layer, add an RLC header, control data retransmission, and the like.
- 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 lower layers by TM and/or data provided from lower layers may be called TMD PDU.
- Data provided by UM to lower layers and/or data provided by lower layers may be referred to as UMD PDUs.
- Data provided to the lower layer by AM or data provided from the lower layer may be called AMD PDU.
- RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC can be different.
- RLC PDUs may include RLC PDUs for data and RLC PDUs for control.
- An RLC PDU for data may be called an RLC DATA PDU (RLC Data PDU).
- the control RLC PDU may be called an RLC CONTROL PDU.
- PDCP may be referred to as a PDCP sublayer.
- PDCP may have a function to maintain sequence numbers.
- PDCP may also have a header compression/decompression function for efficiently transmitting user data such as IP packets and Ethernet frames over a wireless section.
- the protocol used for IP packet header compression/decompression may be called the ROHC (Robust Header Compression) protocol.
- the protocol used for Ethernet frame header compression/decompression may be called EHC (Ethernet (registered trademark) Header Compression) protocol.
- PDCP may also have a data encryption/decryption function.
- PDCP may also have the function of integrity protection and integrity verification of data.
- PDCP may also have a re-ordering function.
- PDCP may also have a retransmission function for PDCP SDUs.
- PDCP may also have a function of discarding data using a discard timer.
- PDCP may also have a duplication function.
- PDCP may have a function of discarding duplicated received data.
- the PDCP entity is a bi-directional entity and can consist of a transmitting PDCP entity and a receiving PDCP entity.
- the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different.
- PDCP PDUs may include data PDCP PDUs and control PDCP PDUs.
- a PDCP PDU for data may be called a PDCP DATA PDU (PDCP Data PDU).
- the control PDCP PDU may be called a PDCP CONTROL PDU.
- SDAP is the Service Data Adaptation Protocol Layer (Service Data Adaptation Protocol Layer).
- SDAP is a mapping between a downlink QoS flow and a data radio bearer (DRB) sent from the 5GC 110 to the terminal device via the base station device, and/or from the terminal device via the base station device. It may have the ability to map uplink QoS flows sent to the 5GC 110 to the DRB.
- SDAP may also have a function to store mapping rule information.
- SDAP may also have a function for marking QoS flow identifiers (QoS Flow ID: QFI).
- SDAP PDUs may include SDAP PDUs for data and SDAP PDUs for control.
- a data SDAP PDU may be called an SDAP DATA PDU.
- a control SDAP PDU may also be called an SDAP CONTROL PDU. Note that one SDAP entity of the terminal device may exist for each PDU session.
- RRC may have a broadcast function.
- RRC may have a paging function from EPC 104 and/or 5GC 110 .
- RRC may have paging capabilities from eNB 102 connected to gNB 108 or 5GC 100 .
- RRC may also have an RRC connection management function.
- RRC may also have a radio bearer control function.
- RRC may also have a cell group control function.
- RRC may also have a mobility control function.
- RRC may also have terminal measurement reporting and terminal measurement reporting control functions.
- RRC may have a QoS management function.
- RRC may also have radio link failure detection and recovery capabilities.
- RRC uses RRC messages for broadcasting, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal equipment measurement reporting and terminal equipment measurement reporting control, QoS management, radio link failure detection and recovery, etc. good to go
- the RRC messages and parameters used in E-UTRA RRC may differ from the RRC messages and parameters used in NR RRC.
- the RRC message may be sent using the logical channel's BCCH, may be sent using the logical channel's PCCH, may be sent using the logical channel's CCCH, or may be sent using the logical channel's DCCH. good to be sent
- An RRC message sent using BCCH may include, for example, a Master Information Block (MIB), each type of System Information Block (SIB), and others. Good RRC messages included.
- RRC messages sent using the PCCH may include, for example, paging messages and may include other RRC messages.
- RRC messages sent in the uplink (UL) direction using CCCH include, for example, RRC Setup Request, RRC Resume Request, RRC Reestablishment Request, RRC A system information request message (RRC System Info Request) may be included. Also, for example, an RRC Connection Request message, an RRC Connection Resume Request message, an RRC Connection Reestablishment Request message, etc. may be included. Also other RRC messages may be included.
- RRC messages sent in the downlink (DL) direction using CCCH include, for example, RRC Connection Reject, RRC Connection Setup, RRC Connection Reestablishment, RRC A connection re-establishment rejection message (RRC Connection Reestablishment Reject) may be included. Also, for example, an RRC rejection message (RRC Reject), an RRC setup message (RRC Setup), etc. may be included. Also other RRC messages may be included.
- RRC messages sent in the uplink (UL) direction using DCCH include, for example, a measurement report message, an RRC connection reconfiguration complete message (RRC Connection Reconfiguration Complete), and an RRC connection setup complete message (RRC Connection Setup Complete). , RRC Connection Reestablishment Complete message, Security Mode Complete message, UE Capability Information message, and the like. Also for example Measurement Report message, RRC Reconfiguration Complete message, RRC Setup Complete message, RRC Reestablishment Complete message, RRC Resume Complete message ), Security Mode Complete message, UE Capability Information message, etc. may be included. Also other RRC messages may be included.
- RRC messages sent in the downlink (DL) direction using DCCH include, for example, RRC Connection Reconfiguration, RRC Connection Release, Security Mode Command, UE A capability inquiry message (UE Capability Inquiry) may be included. 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. Also other RRC messages may be included.
- NAS may have an authentication function. Also, the NAS may have a function to perform mobility management. Also, the NAS may have a security control function.
- each layer may be included in another layer (layer).
- UE 122 may be in RRC_CONNECTED state.
- a state in which an RRC connection is established may include a state in which the UE 122 holds some or all of the UE contexts described below.
- states in which an RRC connection is established may include states in which UE 122 is able to transmit and/or receive unicast data.
- UE 122 may also be in RRC_INACTIVE state when the RRC connection is suspended. Also, the UE 122 may enter the RRC_INACTIVE state when the UE 122 is connected to the 5GC and the RRC connection is dormant.
- a UE 122 may be in the RRC_IDLE state when the UE 122 is neither in the RRC_CONNECTED state nor in the RRC_INACTIVE state.
- UE 122 may initiate dormancy of the RRC connection. If the UE 122 is connected to EPC, when the RRC connection is suspended, the UE 122 may retain the UE's AS context and resumeIdentity and transition to the RRC_IDLE state. A layer higher than the RRC layer of UE 122 (for example, NAS layer) confirms that UE 122 holds the AS context of the UE, and that the E-UTRAN permits recovery of the RRC connection, and that UE 122 exits the RRC_IDLE state. When it needs to transition to the RRC_CONNECTED state, it may initiate the resumption of a dormant RRC connection.
- RRC_CONNECTED the RRC_CONNECTED
- the UE 122 connected to the EPC 104 and the UE 122 connected to the 5GC 110 may have different definitions of dormancy. Also, when UE122 is connected to EPC (when UE122 is dormant in RRC_IDLE state) and when UE122 is connected to 5GC (when UE122 is dormant in RRC_INACTIVE state), UE122 all or part of the procedure for waking up from sleep may be different.
- the RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state may be called connected mode, inactive mode, and idle mode, respectively, and RRC connected mode. , RRC inactive mode, and RRC idle mode.
- the UE AS context held by UE 122 includes the current RRC settings, current security context, PDCP state including ROHC (RObust Header Compression) state, C-RNTI (Cell Radio Network Temporary Identifier), cell identifier (cellIdentity), and physical cell identifier of the connection source PCell, all or part of which may be information.
- the UE AS context held by either or all of the eNB 102 and gNB 108 may contain the same information as the UE AS context held by the UE 122, or the information contained in the UE AS context held by the UE 122. may contain different information.
- a security context consists of a cryptographic key at the AS level, NH (Next Hop parameter), NCC (Next Hop Chaining Counter parameter) used to derive the access key for the next hop, an identifier for the selected AS level encryption algorithm, and replay protection. may be information including all or part of the counters used for
- a cell group that is set by the base station device for the terminal device will be explained.
- a cell group may consist of one special cell (Special Cell: SpCell).
- a cell group may consist of one SpCell and one or more Secondary Cells (SCells). That is, a cell group may consist of one SpCell and optionally one or more SCells.
- a cell group may also be expressed as a set of cell(s). Note that when a MAC entity is associated with a Master Cell Group (MCG), SpCell may mean a Primary Cell (PCell). Also, when the MAC entity is associated with a Secondary Cell Group (SCG), SpCell may mean a Primary SCG Cell (PSCell).
- MCG Master Cell Group
- SCG Secondary Cell Group
- PSCell Primary SCG Cell
- SpCell may also mean PCell if the MAC entity is not associated with a cell group.
- PCell, PSCell and SCell are serving cells.
- a SpCell may support PUCCH transmission and contention-based Random Access, and may be always activated.
- a PCell may be a cell used for an RRC connection establishment procedure when a terminal device in the RRC idle state transitions to the RRC connected state.
- the PCell may be a cell used for the RRC connection re-establishment procedure in which the terminal device re-establishes the RRC connection.
- the PCell may be a cell used for random access procedures during handover.
- a PSCell may be a cell used in a random access procedure when adding a secondary node (SN), which will be described later.
- SN secondary node
- the SpCell may be a cell that is used for purposes other than those described above.
- a cell group configured for a terminal device is composed of an SpCell and one or more SCells is regarded as a carrier aggregation (CA) configured for the terminal device.
- CA carrier aggregation
- a cell that provides an additional radio resource to a SpCell for a terminal device in which CA is configured may mean an SCell.
- TAG Timing Advance Group
- PTAG Primary Timing Advance Group
- STAG Secondary Timing Advance Group
- a cell group may be added to the terminal device from the base station device.
- DC is a technique of performing data communication using radio resources of cell groups respectively configured by a first base station apparatus (first node) and a second base station apparatus (second node).
- MR-DC can be a technology included in DC.
- a first base station device can add a second base station device to perform DC.
- the first base station device may be called a master node (Master Node: MN).
- MCG master cell group
- the second base station device may be called a secondary node (SN).
- a cell group configured by a secondary node may be called a secondary cell group (SCG).
- the master node and the secondary node may be configured within the same base station apparatus.
- the cell group set in the terminal device may be called MCG.
- SpCell configured in the terminal device may be PCell.
- MR-DC may be a technology that performs DC using E-UTRA for MCG and NR for SCG. Also, MR-DC may be a technique of performing DC using NR for MCG and E-UTRA for SCG. Also, MR-DC may be a technique of performing DC using NR for both MCG and SCG. Examples of MR-DC that uses E-UTRA for MCG and NR for SCG include EN-DC (E-UTRA-NR Dual Connectivity) that uses EPC in the core network, and NGEN-DC that uses 5GC in the core network. DC (NG-RAN E-UTRA-NR Dual Connectivity) is good.
- NE-DC NR-E-UTRA Dual Connectivity
- 5GC 5GC for the core network
- NR-DC NR-NR Dual Connectivity
- one MAC entity may exist for each cell group.
- the MAC entity for the MCG in the terminal may always be established in the terminal in all states (RRC idle, RRC connected, RRC inactive, etc.).
- the MAC entity for the SCG in the terminal may be created by the terminal when the SCG is configured in the terminal.
- the MAC entity for each cell group of the terminal device may be set by the terminal device receiving an RRC message from the base station apparatus.
- the MAC entity for MCG may be the E-UTRA MAC entity and the MAC entity for SCG may be the NR MAC entity.
- the MAC entity for MCG may be the NR MAC entity, and the MAC entity for SCG may be the E-UTRA MAC entity.
- both MAC entities for MCG and SCG may be NR MAC entities. Note that one MAC entity exists for each cell group can be rephrased as one MAC entity exists for each SpCell. Also, one MAC entity for each cell group can be rephrased as one MAC entity for each SpCell.
- SRB0 to SRB2 may be defined as SRBs of E-UTRA, and SRBs other than these may be defined.
- SRB0 to SRB3 may be defined as SRBs of NR, and SRBs other than these may be defined.
- SRB0 may be the SRB for RRC messages transmitted and/or received using the CCCH of the logical channel.
- SRB1 may be the SRB for RRC messages and for NAS messages before the establishment of SRB2.
- RRC messages sent and/or received using SRB1 can include piggybacked NAS messages. All RRC and NAS messages sent and/or received using SRB1 can use the DCCH of the logical channel.
- SRB2 may be the SRB for NAS messages and for RRC messages containing logged measurement information.
- All RRC and NAS messages sent and/or received using SRB2 can use the DCCH of the logical channel.
- SRB2 may have a lower priority than SRB1.
- SRB3 may be an SRB for transmitting and/or receiving a specific RRC message when EN-DC, NGEN-DC, NR-DC, etc. are configured in the terminal device. All RRC and NAS messages sent and/or received using SRB3 can use the DCCH of the logical channel. Other SRBs may also be provided for other uses.
- a DRB may be a radio bearer for user data.
- Logical channel DTCH may be used for RRC messages transmitted and/or received using DRB.
- Radio bearers can include RLC bearers.
- An RLC bearer may consist of one or two RLC entities and logical channels.
- the RLC entity when there are two RLC entities in the RLC bearer can be a TM RLC entity and/or a transmitting RLC entity and a receiving RLC entity in a unidirectional UM mode RLC entity.
- SRB0 may consist of one RLC bearer.
- An SRB0 RLC bearer can consist of a TM RLC entity and a logical channel. SRB0 may always be established in the terminal 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 an RRC message received from the base station device when the terminal device transitions from the RRC idle state to the RRC connected state.
- SRB1 may consist of one PDCP entity and one or more RLC bearers.
- An SRB1 RLC bearer can consist of an AM RLC entity and a logical channel.
- One SRB2 may be established and/or configured in the terminal device by an RRC message received from the base station device by the terminal device in the RRC connected state with AS security activated.
- SRB2 may consist of one PDCP entity and one or more RLC bearers.
- An SRB2 RLC bearer can consist of an AM RLC entity and a logical channel.
- SRB3 is when a secondary node in EN-DC, NGEN-DC, or NR-DC is added, or when the secondary node is changed, the terminal device in the RRC connection state with AS security activated is the base station.
- One may be established and/or configured in a terminal device by RRC messages received from the device.
- SRB3 may be a direct SRB between the terminal device and the secondary node.
- SRB3 may consist of one PDCP entity and one or more RLC bearers.
- An SRB3 RLC bearer can consist of an AM RLC entity and a logical channel.
- the PDCP on the base station device side of SRB3 can be placed in the secondary node.
- One or more DRBs may be established and/or configured in a terminal device by RRC messages received from the base station device by the terminal device in RRC connected state with AS security activated.
- a DRB may consist of one PDCP entity and one or more RLC bearers.
- a DRB RLC bearer may consist of an AM or UM RLC entity and a logical channel.
- the radio bearer in which PDCP is placed in the master node can be called the MN terminated (terminated) bearer.
- a radio bearer in which PDCP is placed in a secondary node may be called an SN terminated (terminated) bearer.
- a radio bearer in which the RLC bearer exists only in the MCG may be called an MCG bearer.
- a radio bearer whose RLC bearer exists only in the SCG may be called an SCG bearer.
- a radio bearer in which RLC bearers exist in both MCG and SCG may be called a split bearer.
- the bearer types of SRB1 and SRB2 established/and configured in the terminal device may be MN-terminated MCG bearers and/or MN-terminated split bearers.
- the bearer type of SRB3 established/or configured in the terminal device may be an SN-terminated SCG bearer.
- the DRB bearer type established/and configured in the terminal device may be any of all bearer types.
- the RLC entity established and/or configured may be E-UTRA RLC.
- the RLC entity to be established and/or configured may be NR RLC.
- the terminal is configured with EN-DC
- the PDCP entity established and/or configured for the MN-terminated MCG bearer can be either E-UTRA PDCP or NR PDCP.
- bearer type radio bearers i.e.
- MN terminated split bearer MN terminated SCG bearer, SN terminated MCG bearer, SN terminated split bearer and SN terminated SCG bearer, when EN-DC is configured in the terminal equipment.
- the PDCP established and/or configured by the NR may be the NR PDCP.
- the PDCP entity established and/or configured for radio bearers in all bearer types may be NR PDCP. .
- DRBs established and/or configured in terminal equipment can be associated with one PDU session.
- One SDAP entity may be established and/or configured for one PDU session in a terminal device.
- Established and/or Configured in Terminal The SDAP entity, PDCP entity, RLC entity, and logical channels can be established and/or configured by the RRC messages that the terminal receives from the base station.
- a network configuration in which the master node is eNB 102 and EPC 104 is the core network can be called E-UTRA/EPC.
- a network configuration in which the master node is eNB 102 and 5GC 110 is the core network can 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 apparatus that communicates with terminal apparatuses.
- Handover may be the process by which a UE 122 in RRC Connected state changes its serving cell from a source SpCell to a target SpCell. Handover can occur when UE 122 receives an RRC message from eNB 102 and/or gNB 108 indicating a handover.
- the RRC message instructing handover may be a message regarding reconfiguration of the RRC connection that includes a parameter instructing handover (for example, an information element named MobilityControlInfo or an information element named ReconfigurationWithSync).
- the information element named MobilityControlInfo described above may be rephrased as a mobility control setting information element, a mobility control setting, or mobility control information.
- the above information element named ReconfigurationWithSync may be rephrased as a reset information element with synchronization or a reset with synchronization.
- the RRC message instructing handover may be a message indicating movement to another RAT cell (for example, MobilityFromEUTRACommand or MobilityFromNRCommand).
- Handover can also be rephrased as reconfiguration with sync.
- the conditions under which UE 122 can perform handover include some or all of the following: when AS security is activated, when SRB2 is established, and at least one DRB is established. good.
- FIG. 4 is a diagram showing an example flow of procedures for various settings in RRC according to the embodiment of the present invention.
- FIG. 4 is an example flow when an RRC message is sent from the base station apparatus (eNB 102 and/or gNB 108) to the terminal apparatus (UE 122).
- the base station device creates an RRC message (step S400).
- the creation of the RRC message in the base station apparatus may be performed in order for the base station apparatus to distribute system information (SI) and paging information.
- the creation of the RRC message in the base station apparatus may be performed so that the base station apparatus causes a specific terminal apparatus to perform processing.
- the processing that a particular terminal device is caused to perform may include, for example, security-related configuration, RRC connection reconfiguration, handover to a different RAT, RRC connection suspension, RRC connection release, and the like.
- RRC connection reset processing includes, for example, radio bearer control (establishment, change, release, etc.), cell group control (establishment, addition, change, release, etc.), measurement setting, handover, security key update, etc. Good to include.
- the creation of the RRC message in the base station device may be performed in response to the RRC message transmitted from the terminal device.
- Responses to RRC messages sent from the terminal may include, for example, responses to RRC setup requests, responses to RRC reconnection requests, responses to RRC resume requests, and the like.
- the RRC message contains information (parameters) for various information notifications and settings. These parameters may be called fields and/or information elements and may be described using the ASN.1 (Abstract Syntax Notation One) notation scheme.
- the base station device then transmits the created RRC message to the terminal device (step S402).
- the terminal device performs processing such as setting according to the received RRC message, if necessary (step S404).
- the terminal device that has performed the processing may transmit an RRC message for response to the base station device (not shown).
- RRC messages are not limited to the above examples, and may be used for other purposes.
- RRC on the master node side is used to transfer RRC messages for SCG side settings (cell group settings, radio bearer settings, measurement settings, etc.) to and from terminal devices.
- SCG side settings cell group settings, radio bearer settings, measurement settings, etc.
- E-UTRA RRC messages sent and received between eNB 102 and UE 122 may include NR RRC messages in the form of containers.
- NR RRC messages sent and received between the gNB 108 and the UE 122 may include E-UTRA RRC messages in the form of containers.
- RRC messages for SCG side configuration can be sent and received between the master and secondary nodes.
- the RRC message for E-UTRA transmitted from eNB 102 to UE 122 may include the RRC message for NR, and the RRC message for NR transmitted from gNB 108 to UE 122 may be included.
- the message may contain an RRC message for E-UTRA.
- FIG. 7 is an example of ASN.1 description representing fields and/or information elements related to cell group setting included in a message related to RRC connection reconfiguration in NR in FIG.
- FIG. 8 is an example of ASN.1 description representing fields and/or information elements related to cell group setting included in the message related to RRC connection reconfiguration in E-UTRA in FIG.
- ⁇ omitted> and ⁇ omitted> are not part of the ASN.1 notation, and other information is omitted. indicates that Information elements may be omitted even where there is no description of ⁇ omitted> or ⁇ omitted>.
- the ASN.1 example in the embodiment of the present invention does not correctly follow the ASN.1 notation method.
- the example of ASN.1 represents an example of the parameters of the RRC message in the embodiment of the present invention, and other names and other representations may be used.
- the ASN.1 example shows only examples of main information closely related to one aspect of the present invention in order to avoid complicating the explanation.
- all parameters described in ASN.1 may be referred to as information elements without distinguishing between fields, information elements, and the like.
- the fields described in ASN.1, information elements, etc. included in the RRC message may be rephrased as 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 in FIG. 7 may be an information element used for setting, changing, releasing, etc. of MCG or SCG cell groups in NR.
- the information element named CellGroupConfig may contain the reconfiguration with synchronization information element described below.
- the information element named CellGroupConfig may be rephrased as a cell group configuration information element or cell group configuration.
- this information element named CellGroupConfig can be rephrased as configuration on the SCG side.
- An information element named SpCellConfig contained in an information element named CellGroupConfig may be an information element used to configure a particular cell (SpCell).
- the information element named SpCellConfig may be rephrased as SpCell configuration information element or SpCell configuration.
- An information element named ReconfigurationWithSync included in the information element named SpCellConfig may be an information element indicating reconfiguration with synchronization.
- the information element named ReconfigurationWithSync may be rephrased as a reconfiguration with synchronization information element or a reconfiguration with synchronization. Note that the information element named ReconfigurationWithSync includes a parameter for the period of a timer T304, which will be described later, indicated by t304. Also, an information element named ReconfigurationWithSync may contain parameters for performing a random access procedure indicated by RACH-ConfigDedicated.
- the UE 122 may perform some or all of (A) and/or (B) below.
- (B) If instructions for inactivating SCG are not included, then treatment (WS-1) is performed.
- the UE 122 executes reconfiguration with sync including some or all of (A) to (F) below.
- F Get the MIB of the target SpCell.
- timer T310 may be a timer that starts when an out-of-sync instruction is received from the lower layer in SpCell a certain number of times in succession.
- the lower layer mentioned above may be the physical layer.
- Timer T312 may also be a timer that starts, if timer T310 described above is running, when a measurement report is triggered. Parameters for triggering the measurement reports described above can be included in the measurement settings.
- a radio bearer being suspended may refer to a state in which no RRC message or NAS message is transmitted and/or received using this radio bearer.
- the suspension of transmission in the SCG for the radio bearer may be a state in which all RRC messages and NAS messages are not transmitted and/or received in the SCG using this radio bearer.
- the UE 122 may suspend transmission in the SCG based on some or all of the factors (A) to (D) below.
- A) Detection of radio link failure for SCG (B) Failure of reconfiguration with synchronization of SCG (C) Failure of SCG setup (D) Completeness from lower layers (PDCP) on SCG side considering SRB3 Sex check failure notification
- a master cell group (MCG) and a secondary cell group (SCG) are set by the above-described message regarding RRC connection reconfiguration.
- MCG master cell group
- SCG secondary cell group
- Each cell group may consist of a special cell (SpCell) and zero or more other cells (secondary cells: SCells).
- SpCell of MCG is also called PCell.
- SpCell of SCG is also called PSCell.
- Cell deactivation does not apply to SpCells, but may apply to SCells.
- cell deactivation may not be applied to PCells, but may be applied to PSCells. In this case, cell deactivation may be performed differently for SpCells and SCells.
- Cell activation and deactivation may be handled by a MAC entity that exists for each cell group.
- the SCell configured in the terminal device may be activated and/or deactivated by some or all of (A) to (C) below.
- (A) Reception of MAC CE indicating SCell activation/deactivation (B) SCell inactivity timer set for each SCell in which PUCCH is not set (C) Set for each SCell set in the terminal device RRC parameter (sCellState)
- the MAC entity of the terminal device may perform the following processing (AD) for each SCell set in the cell group.
- processing AD If the RRC parameter (sCellState) set in the SCell when setting the SCell is set to activated, or if a MAC CE that activates the SCell is received, the MAC entity of UE 122 processes (AD-1) I do. Otherwise, if a MAC CE is received to deactivate the SCell or if the SCell inactivity timer expires in an active SCell, the MAC entity of UE 122 performs processing (AD-2).
- an uplink grant or downlink allocation for an active SCell is signaled by the PDCCH of an active SCell, or if an uplink grant or downlink allocation for an active SCell is signaled by the PDCCH of a serving cell, or Once a MAC PDU has been sent on a new uplink grant or received on a configured downlink allocation, the MAC entity of UE 122 restarts the SCell inactivity timer associated with that SCell. If the SCell becomes inactive, the MAC entity of UE 122 performs processing (AD-3).
- this SCell was in an inactive state before receiving the MAC CE that activates this SCell, or if the RRC parameter (sCellState) set in that SCell when setting up the SCell is set to activated If so, the MAC entity of UE 122 performs processing (AD-1A) or processing (AD-1B). The MAC entity of UE 122 also starts or restarts (if already started) the SCell inactivity timer associated with that SCell. If the Active DL BWP is not a dormant BWP (Dormant BWP) described later, the MAC entity of UE 122 performs some or all of (A) to (B) below.
- Dormant BWP dormant BWP
- (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 for activating a SCell is received, and the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) set in the RRC message for that SCell is set to a dormant BWP. If not, the MAC entity of UE 122 takes action (AD-1A).
- the MAC entity of UE 122 takes action (AD-1B). Also, the MAC entity of UE 122 implements some or all of (A) to (B) below.
- the MAC entity of UE 122 activates the SCell and applies (performs) normal SCell operations including some or all of (A) to (E) below.
- SRS Sounding Reference Signal
- B Channel State Information
- C PDCCH monitoring for this SCell
- D PDCCH monitoring for this SCell (etc.) (if scheduling for this SCell is done in the serving cell of (E) If PUCCH is configured, PUCCH transmission on this SCell
- the MAC entity of UE 122 performs some or all of (A) through (F) below.
- A Inactivating this SCell.
- B Stop the SCell inactivity timer associated with this SCell.
- C Inactivate all activated 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 configured uplink grants of grant type 1 associated with this SCell.
- the MAC entity of UE 122 performs some or all of (A) through (D) below.
- A) Do not transmit SRS on this SCell.
- B) Do not report CSI for this SCell.
- C Do not transmit PUCCH, UL-SCH and/or RACH on this SCell.
- D Do not monitor the PDCCH of this SCell and/or the PDCCH for this SCell.
- the SCell is activated and deactivated by the processing (AD) performed by the MAC entity.
- the initial state of the SCell may be set by the RRC message.
- the SCell inactivity timer will be explained.
- the value of the SCell inactivity timer (information regarding the time when the timer is considered to have expired) may be notified by the RRC message.
- the time notified without stopping the timer after starting or restarting the timer in the above process (AD) (here 40ms) has elapsed, the timer is considered expired.
- the SCell deactivation timer may also be a timer named sCellDeactivationTimer.
- bandwidth part (BWP)
- the BWP may be part or all of the bandwidth of the serving cell.
- a BWP may also be called a carrier BWP.
- a terminal device may be configured with one or more BWPs.
- a certain BWP may be set by information included in the broadcast information associated with the synchronization signal detected in the initial cell search.
- a certain BWP may be a frequency bandwidth associated with a frequency for initial cell search.
- Some BWPs may also be configured with RRC signaling (eg Dedicated RRC signaling).
- the downlink BWP (DL BWP) and the uplink BWP (UL BWP) may be configured separately.
- one or more uplink BWPs may be associated with one or more downlink BWPs.
- the association between the uplink BWP and the downlink BWP may be a default association, may be an association by RRC signaling (for example, Dedicated RRC signaling), or may be associated by physical layer signaling (for example, downlink The association may be based on downlink control information (DCI) notified by a control channel, or a combination thereof.
- DCI downlink control information
- a BWP may consist of a group of consecutive physical radio blocks (PRB: Physical Resource Block). Also, parameters of the BWP (one or more BWPs) of each component carrier may be set for the terminal device in the connected state.
- the BWP parameters for each component carrier include (A) the type of cyclic prefix, (B) the subcarrier spacing, (C) the frequency position of the BWP (for example, the start position or center frequency position on the low frequency side of the BWP) ( For the frequency position, for example, ARFCN may be used, or an offset from a specific subcarrier of the serving cell may be used.
- the offset unit may be a subcarrier unit or a resource block unit.
- both ARFCN and offset may be set.), (D) BWP bandwidth (e.g. number of PRBs), (E) control signal resource configuration information, (F) SS block center frequency.
- ARFCN may be used, or an offset from a specific subcarrier of the serving cell may be used.
- the offset unit may be a subcarrier unit, or a resource block unit, and both ARFCN and offset may be set.
- the resource configuration information of the control signal may be included in the BWP configuration of at least some or all of the PCell and/or PSCell.
- a terminal device may transmit and receive in an active BWP (Active BWP) out of one or more set BWPs.
- Active BWP active BWP
- at most one uplink BWP and/or at most one downlink BWP is active at a given time. It may be set to be BWP.
- the activated downlink BWP is also called Active DL BWP.
- the activated uplink BWP is also called Active UL BWP.
- One or more BWPs may be configured in one serving cell. BWP switching in the serving cell is used to activate deactivated BWPs (also referred to as inactive BWPs) and deactivate activated BWPs.
- deactivated BWPs also referred to as inactive BWPs
- BWP switching is controlled by the MAC entity itself for PDCCH indicating downlink assignment or uplink grant, BWP inactivity timer, RRC signaling, or initiation of random access procedures.
- Active BWP of the serving cell is indicated by RRC or PDCCH.
- the MAC entity performs the following processing (A) for each activated serving cell for which the BWP inactivity timer is set.
- the BWP inactivity timer may also be a timer named bwp-InactivityTimer.
- C if no random access procedure associated with this serving cell is in progress, or an ongoing random access procedure associated with this serving cell is successfully completed upon receipt of a PDCCH addressed to C-RNTI; Once (Successfully completed), start or restart the BWP inactivity timer associated with the Active DL BWP.
- D If the BWP inactivity timer associated with the Active DL BWP expires, the MAC entity performs the following (E).
- E If defaultDownlinkBWP-Id is set, perform BWP switching to the BWP indicated by this defaultDownlinkBWP-Id; otherwise, perform BWP switching to initialDownlinkBWP.
- the MAC entity receives the PDCCH for BWP switching and switches the Active DL BWP, it performs the following processing (A).
- A If the default downlink BWP identifier (defaultDownlinkBWP-Id) is set, the switched Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), and if the switched Active DL BWP is dormantDownlinkBWP- If not the BWP indicated by Id, start or restart the BWP inactivity timer associated with the Active DL BWP.
- defaultDownlinkBWP-Id defaultDownlinkBWP-Id
- Inactivating the SCG may mean inactivating the 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.
- Activation of SCG may mean activation of SCG.
- activating an SCG may mean activating a cell group in which a MAC entity is associated with the SCG and corresponds to the MAC entity.
- the state in which the SCG is inactivated means that the terminal device performs one of the following (A) to (K) in the SCG SpCell (PSCell). It may be in a state of implementing part or all.
- SD-1 Do not transmit SRS on this SpCell.
- B Measure CSI for this SpCell.
- C Do not report CSI for this SpCell.
- D Do not transmit PUCCH, UL-SCH and/or RACH on this SpCell.
- E Do not monitor the PDCCH for this SpCell and/or the PDCCH for this SpCell.
- F Perform discontinuous reception (DRX) in this SpCell.
- TAT timeAlignmentTimer
- the state in which the SCG is activated means that the terminal device performs part of (A) to (K) below in the SCG SpCell (PSCell) Or it may be in a state of implementing all.
- SA-1 Send SRS on this SpCell.
- B Measure CSI for this SpCell.
- C Report CSI for this SpCell.
- D Transmit PUCCH, UL-SCH and/or RACH on this SpCell.
- E Monitor the PDCCH for this SpCell and/or the PDCCH for this SpCell.
- F Perform discontinuous reception (DRX) in this SpCell.
- AGC Automatic Gain Control
- beam management including beam failure recovery, and/or radio link monitoring (Radio Link Monitoring) in this SpCell Monitoring: RLM).
- RLM Radio Link Monitoring
- the terminal device may determine that the SCG will be deactivated based on some or all of (A) to (H) below. Note that the messages and control elements (A) to (F) below may be notified to the terminal device from a cell group other than the SCG.
- SD-2 (A) Reception of RRC message instructing deactivation of SCG (B) Reception of MAC control element instructing deactivation of SCG (C) Reception of RRC message instructing deactivation of SpCell (D) SpCell (E) Receipt of other RRC messages (F) Reception of other MAC control elements (G) Expiration of SCG inactivity timer (H) Expiration of PSCell inactivity timer expiration
- FIG. 11 is a diagram showing an example of an embodiment.
- the processing unit 502 of the UE 122 determines that the SCG becomes inactive based on (SD-2) above (step S1100). Also, the processing unit 502 of the UE 122 operates in the inactive state based on the determination (step S1102).
- the terminal device may determine that the SCG is not deactivated based on some or all of (A) to (K) below. Note that the messages and control elements (A) to (F) below may be notified to the terminal device from a cell group other than the SCG. The fact that the SCG is not in an inactive state may mean that the SCG is in an active state.
- SA-2 (A) Reception of RRC message instructing activation of SCG (B) Reception of MAC control element instructing activation of SCG (C) Reception of RRC message instructing activation of SpCell (D) Activation of SpCell (E) Receipt of other RRC messages (F) Reception of other MAC Control elements (G) SCG inactivity timer (H) PSCell inactivity timer (I) MAC SDU included (J) Initiation of a random access procedure due to a scheduling request triggered to send a MAC PDU to be sent (K) Random access due to a scheduling request (in other words, initiated by the MAC entity itself) Start of procedure
- FIG. 10 is a diagram showing an example of an embodiment.
- processing unit 502 of UE 122 determines that the SCG is not inactive based on (SA-2) above (step S1000). Also, the processing unit 502 of the UE 122 operates in the active state based on the determination (step S1002).
- a terminal device that performs SCG deactivation may perform some or all of the following processes (A) to (F) in the SCG.
- SD-3 (A) All SCells are inactivated.
- B Assume that all of the SCell inactivity timers associated with the active SCell have expired.
- C Assume that all SCell inactivity timers associated with the dormant SCell have expired.
- D Do not start or restart the SCell inactivity timers associated with all SCells.
- E Ignore MAC CEs that activate SCells. For example, in the processing (AD), when MAC CE for activating SCell is received and SCG deactivation is not instructed (or SCG is not inactive), processing (AD-1 )I do.
- AD-2 Execute the above process (AD-2). For example, when SCG is instructed to be inactivated (or SCG becomes inactive) in the processing (AD-2), processing (AD-2) is performed.
- a terminal device that activates an SCG may perform the following processes (A) and/or (B) in the SCG.
- SA-3 (A) Execute processing (AD-1) to activate all SCells.
- AD-1 Execute processing
- B If the activation of the SCG is performed based on the RRC message, if this RRC message contains parameters related to random access to SpCell (PSCell), based on the notified parameters, the random access procedure in this SpCell Start.
- FIG. 9 is a diagram showing an example of an embodiment.
- UE 122 receives a message (RRC message) notifying that SCG is to be inactive (dormant state) from eNB 102 or gNB 108 (step S900). Based on the notification, the UE 122 controls some or all of the cells (that is, SCells) other than the SCG SpCell (second cell) to be inactive (step S902).
- the transmission unit 504 of the UE 122 transmits independently the MAC CE for changing the SCell state of the SCG to the inactive state, and an efficient state change is possible. Further, when deactivation of the SCG is performed based on the RRC message, conventionally, the initial state is set in the RRC layer, and the state change is performed in the MAC layer. It is possible to efficiently change the state of the SCG while avoiding a mismatch between the instruction and the MAC layer instruction.
- FIG. 5 is a block diagram showing the configuration of the terminal device (UE 122) according to the embodiment of the present invention. In order to avoid complicating the description, FIG. 5 shows only main components closely related to one embodiment of the present invention.
- UE 122 shown in FIG. 5 includes a receiving unit 500 that receives an RRC message or the like from a base station device, a processing unit 502 that performs processing according to parameters included in the received message, and a transmitting unit that transmits the RRC message or the like to the base station device. 504, consisting of The base station apparatus described above may be eNB 102 or gNB 108 .
- processing unit 502 may include some or all of the functionality of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 502 includes part or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP processing unit, RRC layer processing unit, and NAS layer processing unit. you can
- FIG. 6 is a block diagram showing the configuration of the base station apparatus according to the embodiment of the present invention. In order to avoid complicating the description, FIG. 6 shows only main components closely related to one embodiment of the present invention.
- the base station apparatus described above may be eNB 102 or gNB 108 .
- the base station apparatus shown in FIG. 6 includes a transmission unit 600 that transmits an RRC message and the like to UE 122, and a processing unit that creates an RRC message including parameters and transmits it to UE 122, thereby allowing processing unit 502 of UE 122 to perform processing. 602 and a receiver 604 that receives RRC messages and the like from the UE 122 .
- processing unit 602 may include some or all of the functionality of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 602 includes part or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP processing unit, RRC layer processing unit, and NAS layer processing unit. you can
- FIG. 10 An example of the processing of the terminal device according to the embodiment of the present invention will be described using FIG.
- the terminal device does not need to monitor a plurality of cell groups and power consumption can be reduced. be done.
- FIG. 10 is a diagram showing an example of processing of the terminal device according to the embodiment of the present invention.
- the processing unit 502 of the UE 122 may determine that the SCG will not become inactive based on (SA-2) above (step S1000). Also, the processing unit 502 of the UE 122 may operate in the active state based on the determination (step S1002).
- the UE 122 in the active state, may perform part or all of the processing shown in (SA-1) above in each of the SpCells and/or one or more SCells of a certain cell group.
- the active state may be a state in which the SCG is activated. Also, the active state described above may be a state in which the SCG has resumed from a dormant state. Also, the active state described above may be a state in which the SCG described above is not in a dormant state. Also, the active state described above may be the state transitioned from the inactive state when a random access procedure due to a scheduling request triggered to transmit a MAC PDU containing a MAC SDU is initiated. . Further, the active state described above may be a state that transitions from the inactive state when the RRC entity instructs to return from the dormant state.
- step S1000 the processing unit 502 of the UE 122 may determine the transition when the SCG completes the transition from the inactive state to the active state. Also, the processing unit 502 of the UE 122 may determine the transition while the SCG transitions from the inactive state to the active state.
- the UE 122 may transition the SCG from the inactive state to the active state (in other words, activate the SCG). Also, upon receiving information instructing the SCG to return from the dormant state (Resume), the UE 122 may cause the SCG to transition from the inactive state to the active state. Also, upon receiving information instructing the SpCell to return from the dormant state, the UE 122 may cause the SCG to transition from the inactive state to the active state. UE 122 may also transition the SCG from the inactive state to the active state upon receiving other information. Also, the UE 122 may transition the SCG from the inactive state to the active state based on the SCG dormancy timer.
- the UE 122 may transition the SCG from the inactive state to the active state based on the PSCell sleep timer. 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 send a MAC PDU containing a MAC SDU. Also, the UE 122 may transition the SCG from the inactive state to the active state when starting the random access procedure. The UE 122 may also transition the SCG from inactive to active when initiating a random access procedure resulting from a scheduling request (in other words, initiated by the MAC entity itself).
- the MAC entity of UE 122 may also obtain an indication to activate an SCG, an indication to wake from a dormant SCG, an indication to wake SpCell from dormancy, and/or other information from the RRC entity of UE 122. .
- UE 122 determines that the SCG does not become inactive as shown in (SA-2) above, and changes the SCG from inactive to active. You can transition to The UE 122 may perform the processing shown in (SA-3) above when making the SCG transition from the inactive state to the active state.
- FIG. 1 An example of the processing of the terminal device according to the embodiment of the present invention will be described using FIG.
- FIG. 11 is a diagram showing an example of processing of the terminal device according to the embodiment of the present invention.
- the processing unit 502 of the UE 122 may determine that the SCG becomes inactive based on (SD-2) above (step S1100). Also, the processing unit 502 of the UE 122 may operate in the inactive state based on the determination (step S1102).
- UE 122 may perform some or all of the processing as indicated in (SD-1) above in an SpCell and/or one or more SCells of a cell group.
- the inactive state may be a state in which the SCG is inactivated. Also, the inactive state described above may be Entering a dormant SCG. Also, the inactive state described above may be the dormant state of the SCG described above. The inactive state may also be a state in which the SpCell of the SCG and/or the Active BWP of one or more SCells are dormant BWPs. Also, the inactive state described above may be a state that transitions from the active state when a random access procedure due to a scheduling request triggered to transmit a MAC PDU containing a MAC SDU is initiated. . Also, the inactive state described above may be a state transitioned from the active state when the RRC entity instructs to enter the dormant state.
- step S1100 the processing unit 502 of the UE 122 may determine the transition when the SCG completes the transition from the active state to the inactive state. Also, the processing unit 502 of the UE 122 may determine the transition while the SCG transitions from the active state to the inactive state.
- the UE 122 may transition the SCG from the active state to the inactive state. Also, upon receiving information instructing entry into the dormant SCG, the UE 122 may transition the SCG from the active state to the inactive state. Also, upon receiving information instructing SpCell dormancy, the UE 122 may transition the SCG from the active state to the inactive state. UE 122 may also transition the SCG from the active state to the inactive state upon receiving other information. Also, the UE 122 may cause the SCG to transition from the active state to the inactive state when the SCG dormancy timer expires.
- the UE 122 may transition the SCG from the active state to the inactive state when the PSCell sleep timer expires.
- the MAC entity of UE 122 may also obtain an indication to deactivate an SCG, an indication to enter a dormant SCG, an indication to dormant SpCells, and/or other information from the RRC entity of UE 122.
- UE 122 determines that the SCG becomes inactive as shown in (SD-2) above, and changes the SCG from active to inactive state. You can transition.
- the UE 122 may perform the processing shown in (SD-3) above when making the SCG transition from the active state to the inactive state.
- FIG. 1 An example of processing of the terminal device according to the embodiment of the present invention will be described using FIG.
- FIG. 12 is a diagram showing an example of processing of the terminal device according to the embodiment of the present invention.
- the processing unit 502 of the UE 122 may perform reconfiguration with synchronization when the SpCell configuration information element of the SCG in the message regarding reconfiguration of the RRC connection received by the UE 122 includes reconfiguration with synchronization (step S1200). (Step S1202). Also, the processing unit 502 of the UE 122 may resume all suspended radio bearers when the message regarding reconfiguration of the RRC connection does not include an instruction to deactivate the SCG (step S1200). If suspended, transmissions on the SCG for the radio bearers may be resumed.
- the processing unit 502 of the UE 122 does not restart some suspended radio bearers, Transmission on the SCG for the bearer may not resume (step S1204).
- the SpCell configuration information element of the SCG described above may be SpCellConfig included in CellGroupConfig that configures the SCG shown in FIG.
- an instruction to deactivate the SCG described above may be included in the RRC message.
- the above-mentioned SCG deactivation instruction may be identified by the type of RRC message (the RRC message itself).
- the above-mentioned SCG deactivation instruction may be included in the cell group configuration information element or the SpCell configuration information element in the RRC reconfiguration message.
- the instruction to deactivate the SCG described above may be included in an information element other than the cell group configuration information element or the SpCell configuration information element in the RRC reconfiguration message.
- the radio bearers described above may include RLC bearers and/or radio bearers other than RLC bearers.
- the above-mentioned radio bearers may include some or all of MCG bearers, SCG bearers, and split bearers.
- step S1202 An example of the process of resetting with synchronization in step S1202 will be described. If the message regarding RRC connection reconfiguration received by UE 122 in step S1200 includes reconfiguration with synchronization, UE 122 performs the processing shown in (WS) above when performing reconfiguration with synchronization. You can
- radio bearer processing in step S1204 will be described. If the message regarding reconfiguration of the RRC connection received by UE 122 in step S1200 includes an instruction to deactivate the SCG, the processing unit 502 of UE 122 does not restart some or all of the suspended radio bearers. , may not restart transmissions on the SCG for some or all radio bearers. Further, when the message regarding reconfiguration of the RRC connection received by UE 122 in step S1200 includes an instruction to deactivate the SCG, the processing unit 502 of UE 122 resumes some or all of the suspended radio bearers. and may resume transmission on the SCG for all radio bearers if suspended.
- processing unit 502 of UE 122 resumes all suspended radio bearers, Transmission on the SCG for some or all radio bearers may not be restarted. If the message regarding reconfiguration of the RRC connection received by UE 122 in step S1200 does not contain an instruction to deactivate the SCG, processing unit 502 of UE 122 resumes all suspended radio bearers, and resumes all radio bearers. Transmission on the SCG for the bearer may be resumed if suspended. Note that the suspension and/or resumption of radio bearers may be performed for each cell group, or may be performed regardless of the cell group. Also, suspension and/or resumption of transmission in the SCG for radio bearers may be performed for each cell group, or may be performed regardless of the cell group.
- the radio bearers in the above description may be DRB, SRB, or both DRB and SRB.
- SCG SpCell may be replaced with “PSCell”.
- the "dormant state” may be replaced with the “inactive state”
- the "state recovered from the dormant state” may be replaced with the “active state”.
- activation and “inactivation” may be replaced with “active state” and “inactive state”, respectively.
- transition from X to Y can be rephrased as “transition from X to Y”.
- make a transition may be rephrased as “determine a transition”.
- activated BWP may be replaced with “Active BWP”.
- A may be rephrased as B” may include the meaning of rephrasing B as A in addition to rephrasing A as B.
- C may be D
- C may be E
- D may be E
- F may be G
- G may be H
- F may be H
- condition "A” and the condition “B” are contradictory conditions, the condition “B” may be expressed as the “other” condition of the condition "A”. good.
- a first embodiment of the present invention is a terminal device that communicates with a base station device, comprising: a receiving unit that receives an RRC message from the base station device; performs communication using a first cell group and a second cell group, wherein the RRC message includes a first configuration for configuring a special cell included in the second cell group; The unit performs synchronous reconfiguration based on the synchronous reconfiguration being included in the first configuration, and the processing unit deactivates the second cell group in the RRC message.
- a second embodiment of the present invention is a base station apparatus that communicates with a terminal device, comprising: a transmission unit that transmits an RRC message to the terminal device; , communicating using a first cell group and a second cell group, wherein the RRC message includes a first configuration for configuring a special cell included in the second cell group, the processing unit causes the terminal device to perform synchronous reconfiguration by including synchronous reconfiguration in the first configuration, and the processing unit deactivates the second cell group in the RRC message.
- the processing unit includes an instruction for deactivating the second cell group in the RRC message, so that the terminal device does not resume some suspended radio bearers, is a base station apparatus that does not restart transmission in the second cell group for the radio bearer of the second cell group.
- a third embodiment of the present invention is a method for a terminal device that communicates with a base station device, receiving an RRC message from the base station device, Communication is performed using a group, the RRC message includes a first configuration for configuring a special cell included in the second cell group, and the first configuration includes reconfiguration with synchronization. performing reconfiguration with synchronization based on the fact that the RRC message does not contain an indication to deactivate the second cell group, resuming all suspended radio bearers; If the RRC message includes an instruction to resume transmission in the second cell group for all radio bearers if suspended and deactivate the second cell group, then: a method of not resuming some suspended radio bearers and not resuming transmission in the second cell group for some radio bearers.
- a program that runs on a device is a program that controls a Central Processing Unit (CPU) or the like to function a computer so as to realize the functions of the above-described embodiments according to one aspect of the present invention. It can be.
- the program or information handled by the program is temporarily read into volatile memory such as Random Access Memory (RAM) during processing, or stored in non-volatile memory such as flash memory or Hard Disk Drive (HDD), and
- RAM Random Access Memory
- HDD Hard Disk Drive
- part of the devices in the above-described embodiments may be realized by a computer.
- the program for realizing this control function may be recorded in a computer-readable recording medium, and the program recorded in this recording medium may be read into a computer system and executed.
- the "computer system” here is a computer system built in the device, and includes hardware such as an operating system and peripheral devices.
- the "computer-readable recording medium” may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, and the like.
- “computer-readable recording medium” means a medium that dynamically stores programs for a short period of time, such as a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line. , it may also include something that holds the program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in that case. Further, the program may be for realizing a part of the functions described above, or may be capable of realizing the functions described above in combination with a program already recorded in the computer system. .
- each functional block or feature of the apparatus used in the embodiments described above may be implemented or performed in an electrical circuit, typically an integrated circuit or multiple integrated circuits.
- Electrical circuits designed to perform the functions described herein may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof.
- a general purpose processor may be a microprocessor, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
- the general-purpose processor or each circuit described above may be composed of digital circuits or may be composed of analog circuits.
- an integrated circuit technology that replaces current integrated circuits emerges due to advances in semiconductor technology, it is also possible to use integrated circuits based on this technology.
- one aspect of the present invention is not limited to the above-described embodiments. Although an example of the apparatus has been described in the embodiment, one aspect of the present invention is not limited to this, and is a stationary or non-movable electronic device installed indoors or outdoors, such as an AV device, It can be applied to terminal devices or communication devices such as kitchen equipment, cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household equipment.
- One aspect of the present invention is, for example, a communication system, a communication device (e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (e.g., a communication chip), or a program, etc. be able to.
- a communication device e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device
- an integrated circuit e.g., a communication chip
- a program etc. be able to.
- E-UTRA 102 eNB 104 EPCs 106NR 108 gNB 110 5GC 112, 114, 116, 118, 120, 124 interfaces 122 UEs 200, 300 PHYs 202, 302 MACs 204, 304 RLC 206, 306 PDCP 208, 308 RRC 310 SDAP 210, 312 NAS 500, 604 Receiver 502, 602 processor 504, 600 transmitter
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A processing unit of this terminal device performs communication by using a first cell group and a second cell group, and an RRC message includes a first configuration for configuring a special cell included in the second cell group. The processing unit carries out synchronous reconfiguration on the basis of the first configuration including synchronous reconfiguration. When the RRC message does not include an instruction for deactivating the second cell group, all suspended radio bearers are reopened, and transmission in the second cell group for all radio bearers is reopened if suspended. When the RRC message includes an instruction for deactivating the second cell group, a portion of the suspended radio bearers are not reopened, and transmission in the second cell group for a portion of the radio bearers is not reopened.
Description
本発明は、端末装置、基地局装置および、方法に関する。
本願は、2021年8月5日に日本に出願された特願2021-128736号について優先権を主張し、その内容をここに援用する。 The present invention relates to a terminal device, base station device and method.
This application claims priority to Japanese Patent Application No. 2021-128736 filed in Japan on August 5, 2021, the contents of which are incorporated herein.
本願は、2021年8月5日に日本に出願された特願2021-128736号について優先権を主張し、その内容をここに援用する。 The present invention relates to a terminal device, base station device and method.
This application claims priority to Japanese Patent Application No. 2021-128736 filed in Japan on August 5, 2021, the contents of which are incorporated herein.
セルラ移動通信システムの標準化プロジェクトである、第3世代パートナーシッププロジェクト(3rd Generation Partnership Project:3GPP)において、無線アクセス、コアネットワーク、サービス等を含む、セルラ移動通信システムの技術検討及び規格策定が行われている。
In the 3rd Generation Partnership Project (3GPP), a standardization project for cellular mobile communication systems, technical studies and standardization of cellular mobile communication systems, including radio access, core networks, services, etc., are being conducted. there is
例えば、E-UTRA(Evolved UniversaLTErrestrial Radio Access)は、3GPPにおいて、第3.9世代および第4世代向けセルラ移動通信システム向け無線アクセス技術(Radio Access Technology:RAT)として、技術検討及び規格策定が開始された。現在も3GPPにおいて、E-UTRAの拡張技術の技術検討及び規格策定が行われている。なお、E-UTRAは、Long Term Evolution(LTE:登録商標)とも称し、拡張技術をLTE-Advanced(LTE-A)、LTE-Advanced Pro(LTE-A Pro)と称する事もある。
For example, E-UTRA (Evolved Universal LTE Terrestrial Radio Access) is a radio access technology (RAT) for 3.9th and 4th generation cellular mobile communication systems. . At present, 3GPP is still conducting technical studies and establishing standards for extension technologies for E-UTRA. E-UTRA is also called Long Term Evolution (LTE: registered trademark), and extended technologies are sometimes called LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).
また、NR(New Radio、またはNR Radio access)は、3GPPにおいて、第5世代(5th Generation:5G)向けセルラ移動通信システム向け無線アクセス技術(Radio Access Technology:RAT)として、技術検討及び規格策定が開始された。現在も3GPPにおいて、NRの拡張技術の技術検討及び規格策定が行われている。
In addition, NR (New Radio or NR Radio access) is under technical review and standardization as Radio Access Technology (RAT) for 5th Generation (5G) cellular mobile communication systems at 3GPP. started. At present, 3GPP is still conducting technical studies and establishing standards for NR extension technology.
NRの拡張技術として大容量のデータ通信を可能とするために、複数のセルグループを用いて一つまたは複数の基地局装置と端末装置とが通信するデュアルコネクティビティ(マルチコネクティビティとも称する)技術がある。このデュアルコネクティビティでは、それぞれのセルグループで通信を行うために、端末装置はそれぞれのセルグループにおいて自分宛のメッセージの有無をモニタする必要がある。大容量のデータ通信が発生したときに端末装置が低遅延で通信できるように、端末装置は常に複数のセルグループのモニタを行う必要があり、多くの電力を消費する問題があった。そのため、一部のセルグループのモニタを低頻度で行う、または停止する技術(セルグループの不活性化(Deactivated)
技術)の検討が開始された。 In order to enable large-capacity data communication as an NR extension technology, there is a dual connectivity (also called multi-connectivity) technology in which one or more base station devices and terminal devices communicate using a plurality of cell groups. . In this dual connectivity, in order to perform communication in each cell group, a terminal device needs to monitor whether there is a message addressed to itself in each cell group. In order to enable the terminal device to perform low-delay communication when a large volume of data communication occurs, the terminal device must always monitor a plurality of cell groups, and there has been a problem of consuming a lot of power. Therefore, techniques for monitoring some cell groups infrequently or stopping them (deactivated cell group)
technology) was started.
技術)の検討が開始された。 In order to enable large-capacity data communication as an NR extension technology, there is a dual connectivity (also called multi-connectivity) technology in which one or more base station devices and terminal devices communicate using a plurality of cell groups. . In this dual connectivity, in order to perform communication in each cell group, a terminal device needs to monitor whether there is a message addressed to itself in each cell group. In order to enable the terminal device to perform low-delay communication when a large volume of data communication occurs, the terminal device must always monitor a plurality of cell groups, and there has been a problem of consuming a lot of power. Therefore, techniques for monitoring some cell groups infrequently or stopping them (deactivated cell group)
technology) was started.
本発明の一態様は、上記した事情に鑑みてなされたもので、通信制御を効率的に行うことができる端末装置、基地局装置、方法、集積回路を提供することを目的の一つとする。
One aspect of the present invention has been made in view of the circumstances described above, and one object thereof is to provide a terminal device, a base station device, a method, and an integrated circuit capable of efficiently performing communication control.
上記の目的を達成するために、本発明の一態様は、以下のような手段を講じた。すなわち本発明の一態様は、基地局装置と通信する端末装置であって、前記基地局装置から、RRCメッセージを受信する受信部と、処理部とを備え、前記処理部は、第1のセルグループと第2のセルグループを使用して通信を行い、前記RRCメッセージは、前記第2のセルグループに含まれる特別なセルを設定する第1の設定を含み、前記処理部は、前記第1の設定に同期付再設定が含まれていることに基づいて、同期付再設定を実施し、前記処理部は、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示が含まれていない場合、すべてのサスペンドされた無線ベアラを再開し、すべての無線ベアラのための前記第2のセルグループにおける送信を、サスペンドされていたら再開し、前記処理部は、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示が含まれていた場合、一部のサスペンドされた無線ベアラを再開せず、一部の無線ベアラのための前記第2のセルグループにおける送信を再開しない端末装置である。
In order to achieve the above object, one aspect 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 receiving unit that receives an RRC message from the base station device; group and a second cell group are used to communicate, the RRC message includes a first configuration for configuring a special cell included in the second cell group, and the processing unit performs the first includes synchronous reconfiguration, and the processing unit includes an instruction for deactivating the second cell group in the RRC message. If not, resume all suspended radio bearers, resume transmission in the second cell group for all radio bearers if suspended, and the processing unit causes the RRC message to: if the instruction to deactivate the second cell group is included, do not resume some suspended radio bearers and resume transmission in said second cell group for some radio bearers; It is a terminal device that does not resume.
また本発明の一態様は、端末装置と通信する基地局装置であって、前記端末装置に、RRCメッセージを送信する送信部と、処理部とを備え、前記処理部は、第1のセルグループと第2のセルグループを使用して通信を行い、前記RRCメッセージは、前記第2のセルグループに含まれる特別なセルを設定する第1の設定を含み、前記処理部は、前記第1の設定に同期付再設定を含めることによって、前記端末装置に対し、同期付再設定を実施させ、前記処理部は、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示を含めないことによって、前記端末装置に対し、すべてのサスペンドされた無線ベアラを再開させ、すべての無線ベアラのための前記第2のセルグループにおける送信を、サスペンドされていたら再開させ、前記処理部は、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示を含めることによって、前記端末装置に対し、一部のサスペンドされた無線ベアラを再開させず、一部の無線ベアラのための前記第2のセルグループにおける送信を再開させない基地局装置である。
Further, one aspect of the present invention is a base station apparatus that communicates with a terminal device, comprising: a transmission unit that transmits an RRC message to the terminal device; and a second cell group, wherein the RRC message includes a first setting for setting a special cell included in the second cell group, and the processing unit performs communication using the first By including reconfiguration with synchronization in configuration, the terminal device is caused to perform reconfiguration with synchronization, and the processing unit includes an instruction for deactivating the second cell group in the RRC message. causing the terminal to resume all suspended radio bearers and to resume transmission in the second cell group for all radio bearers if suspended, the processing unit comprising: By including an instruction for deactivating the second cell group in the RRC message, the terminal device is prevented from resuming some suspended radio bearers and for some radio bearers. The base station apparatus does not restart transmission in the second cell group.
本発明の一態様は、基地局装置と通信する端末装置の方法であって、前記基地局装置から、RRCメッセージを受信し、第1のセルグループと第2のセルグループを使用して通信を行い、前記RRCメッセージは、前記第2のセルグループに含まれる特別なセルを設定する第1の設定を含み、前記第1の設定に同期付再設定が含まれていることに基づいて、同期付再設定を実施し、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示が含まれていない場合、すべてのサスペンドされた無線ベアラを再開し、すべての無線ベアラのための前記第2のセルグループにおける送信を、サスペンドされていたら再開し、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示が含まれていた場合、一部のサスペンドされた無線ベアラを再開せず、一部の無線ベアラのための前記第2のセルグループにおける送信を再開しない方法である。
One aspect of the present invention is a method for a terminal device that communicates with a base station device, which receives an RRC message from the base station device and performs communication using a first cell group and a second cell group. and the RRC message includes a first configuration that configures a special cell included in the second cell group, and based on the fact that the first configuration includes reconfiguration with synchronization, and if the RRC message does not include an instruction to deactivate the second cell group, resume all suspended radio bearers, and some suspended radio bearers if the RRC message includes an instruction to deactivate the second cell group; and not restarting transmission in the second cell group for some radio bearers.
なお、これらの包括的または具体的な態様は、システム、装置、方法、集積回路、コンピュータプログラム、または、記録媒体で実現されてもよく、システム、装置、方法、集積回路、コンピュータプログラムおよび記録媒体の任意な組み合わせで実現されてもよい。
In addition, these generic or specific aspects may be realized by systems, devices, methods, integrated circuits, computer programs, or recording media. may be realized by any combination of
本発明の一態様によれば、端末装置、基地局装置、方法、および集積回路は、効率的な通信制御処理を実現することができる。
According to one aspect of the present invention, the terminal device, base station device, method, and integrated circuit can realize efficient communication control processing.
以下、本発明の実施の形態について、図面を参照して詳細に説明する。
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
LTE(およびLTE-A、LTE-A Pro)とNRは、異なる無線アクセス技術(Radio Access Technology:RAT)として定義されてよい。またNRは、LTEに含まれる技術として定義されてもよい。またLTEは、NRに含まれる技術として定義されてもよい。また、NRとMulti Radio Dual connectivity(MR-DC)で接続可能なLTEは、従来のLTEと区別されてよい。また、コアネットワークに5GCを用いるLTEは、コアネットワークにEPCを用いる従来のLTEと区別されてよい。なお従来のLTEとは、3GPPにおけるリリース15以降に規格化された技術を実装していないLTEの事であって良い。本発明の実施形態はNR、LTEおよび他のRATに適用されてよい。以下の説明では、LTEおよびNRに関連する用語を用いて説明するが、本発明の実施形態は他の用語を用いる他の技術において適用されてもよい。また本発明の実施形態でのE-UTRAという用語は、LTEという用語に置き換えられて良いし、LTEという用語はE-UTRAという用語に置き換えられて良い。
LTE (and LTE-A, LTE-A Pro) and NR may be defined as different Radio Access Technologies (RAT). NR may also be defined as a technology included in LTE. LTE may also be defined as a technology included in NR. Also, LTE that can be connected by NR and Multi Radio Dual connectivity (MR-DC) may be distinguished from conventional LTE. Also, LTE using 5GC for the core network may be distinguished from conventional LTE using EPC for the core network. Note that conventional LTE may be LTE that does not implement the technology standardized after Release 15 of 3GPP. Embodiments of the present invention may be applied to NR, LTE and other RATs. Although the following description uses terminology related to LTE and NR, embodiments of the present invention may be applied in other technologies using other terminology. Also, the term E-UTRA in the embodiments of the present invention may be replaced with the term LTE, and the term LTE may be replaced with the term E-UTRA.
なお、本発明の実施の形態において、無線アクセス技術がE-UTRA又はNRである場合の各ノードやエンティティの名称、及び各ノードやエンティティにおける処理等について説明するが、本発明の実施の形態は他の無線アクセス技術に用いられて良い。本発明の実施の形態における各ノードやエンティティの名称は、別の名称であって良い。
In addition, in the embodiment of the present invention, the name of each node and entity when the radio access technology is E-UTRA or NR, and the processing in each node and entity will be described. It may be used for other radio access technologies. The name of each node or entity in the embodiment of the present invention may be another name.
図1は本発明の実施の形態に係る通信システムの概略図である。なお図1を用いて説明する各ノード、無線アクセス技術、コアネットワーク、インタフェース等の機能は、本発明の実施形態に密接に関わる一部の機能であり、他の機能を持って良い。
FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present invention. It should be noted that the functions of each node, radio access technology, core network, interface, etc. described using FIG. 1 are part of the functions closely related to the embodiment of the present invention, and may have other functions.
E-UTRA100は無線アクセス技術であって良い。またE-UTRA100は、UE122とeNB102との間のエアインタフェース(air interface)であって良い。UE122とeNB102との間のエアインタフェースをUuインタフェースと呼んで良い。eNB(E-UTRAN Node B)102は、E-UTRA100の基地局装置であって良い。eNB102は、後述のE-UTRAプロトコルを持って良い。E-UTRAプロトコルは、後述のE-UTRAユーザプレーン(User Plane:UP)プロトコル、及び後述のE-UTRA制御プレーン(Control Plane:CP)プロトコルから構成されても良い。eNB102は、UE122に対し、E-UTRAユーザプレーン(User Plane:UP)プロトコル、及びE-UTRA制御プレーン(Control Plane:CP)プロトコルを終端して良い。eNBで構成される無線アクセスネットワークをE-UTRANと呼んでもよい。
E-UTRA100 may be a radio access technology. E-UTRA 100 may also be the air interface between UE 122 and eNB 102 . The air interface between UE 122 and eNB 102 may be called Uu interface. The eNB (E-UTRAN Node B) 102 may be a base station device for the E-UTRA 100. The eNB 102 may have the E-UTRA protocol described below. The E-UTRA protocol may consist of an E-UTRA user plane (User Plane: UP) protocol described later and an E-UTRA control plane (Control Plane: CP) protocol described later. eNB 102 may terminate E-UTRA User Plane (UP) and E-UTRA Control Plane (CP) protocols to UE 122 . A radio access network composed of eNBs may be called E-UTRAN.
EPC(Evolved Packet Core)104は、コア網であって良い。インタフェース112はeNB102とEPC104の間のインタフェース(interface)であり、S1インタフェースと呼ばれて良い。インタフェース112には、制御信号が通る制御プレーンインタフェース、及び/又は(and/or)ユーザデータが通るユーザプレーンインタフェースが存在して良い。インタフェース112の制御プレーンインタフェースはEPC104内のMobility Management Entity(MME:不図示)で終端して良い。インタフェース112のユーザプレーンインタフェースはEPC104内のサービングゲートウェイ(S-GW:不図示)で終端して良い。インタフェース112の制御プレーンインタフェースをS1-MMEインタフェースと呼んで良い。インタフェース112のユーザプレーンインタフェースをS1-Uインタフェースと呼んで良い。
EPC (Evolved Packet Core) 104 may be a core network. Interface 112 is the interface between eNB 102 and EPC 104 and may be referred to as the S1 interface. Interface 112 may include a control plane interface through which control signals pass, and/or a user plane interface through which user data passes. The control plane interface of interface 112 may terminate at a Mobility Management Entity (MME; not shown) within EPC 104 . A user plane interface of interface 112 may terminate at a serving gateway (S-GW; not shown) within EPC 104 . The control plane interface of interface 112 may be called the S1-MME interface. The user plane interface of interface 112 may be called the S1-U interface.
なお、1つ又は複数のeNB102がEPC104にインタフェース112を介して接続されて良い。EPC104に接続する複数のeNB102の間に、インタフェースが存在して良い(不図示)。EPC104に接続する複数のeNB102間のインタフェースを、X2インタフェースと呼んで良い。
Note that one or more eNBs 102 may be connected to EPC 104 via interface 112 . There may be an interface between multiple eNBs 102 that connect to the EPC 104 (not shown). An interface between multiple eNBs 102 connected to an EPC 104 may be called an X2 interface.
NR106は無線アクセス技術であって良い。またNR106は、UE122とgNB108との間のエアインタフェース(air interface)であって良い。UE122とgNB108との間のエアインタフェースをUuインタフェースと呼んで良い。gNB(g Node B)108は、NR106の基地局装置であって良い。gNB108は、後述のNRプロトコルを持って良い。NRプロトコルは、後述のNRユーザプレーン(User Plane:UP)プロトコル、及び後述のNR制御プレーン(Control Plane:CP)プロトコルから構成されて良い。gNB108は、UE122に対し、NRユーザプレーン(User Plane:UP)プロトコル、及びNR制御プレーン(Control Plane:CP)プロトコルを終端して良い。
NR106 may be a radio access technology. NR 106 may also be the air interface between UE 122 and gNB 108 . The air interface between UE 122 and gNB 108 may be called the Uu interface. The gNB (g Node B) 108 may be the base station equipment of the NR 106. gNB108 may have the NR protocol described below. The NR protocol may consist of an NR User Plane (UP) protocol, described below, and an NR Control Plane (CP) protocol, described below. gNB 108 may terminate NR User Plane (UP) and NR Control Plane (CP) protocols to UE 122 .
5GC110は、コア網であって良い。インタフェース116はgNB108と5GC110の間のインタフェース(interface)であり、NGインタフェースと呼ばれて良い。インタフェース116には、制御信号が通る制御プレーンインタフェース、及び/又はユーザデータが通るユーザプレーンインタフェースが存在して良い。インタフェース116の制御プレーンインタフェースは5GC110内のAccess and mobility Management Function(AMF:不図示)で終端して良い。インタフェース116のユーザプレーンインタフェースは5GC110内のUser Plane Function(UPF:不図示)で終端して良い。インタフェース116の制御プレーンインタフェースをNG-Cインタフェースと呼んで良い。インタフェース116のユーザプレーンインタフェースをNG-Uインタフェースと呼んで良い。
5GC110 may be the core network. Interface 116 is the interface between gNB 108 and 5GC 110 and may be called the NG interface. Interface 116 may include a control plane interface through which control signals pass, and/or a user plane interface through which user data passes. The control plane interface of interface 116 may terminate at the Access and Mobility Management Function (AMF: not shown) within 5GC 110 . The user plane interface of interface 116 may terminate at a User Plane Function (UPF: not shown) within 5GC 110 . The control plane interface of interface 116 may be called the NG-C interface. The user plane interface of interface 116 may be called the NG-U interface.
なお、1つ又は複数のgNB108が5GC110にインタフェース116を介して接続されて良い。5GC110に接続する複数のgNB108の間に、インタフェースが存在して良い(不図示)。5GC110に接続する複数のgNB108間のインタフェースをXnインタフェースと呼んで良い。
Note that one or more gNBs 108 may be connected to the 5GC 110 via interface 116. There may be interfaces between gNBs 108 that connect to the 5GC 110 (not shown). An interface between multiple gNBs 108 connected to a 5GC 110 can be called an Xn interface.
eNB102は5GC110に接続する機能を持って良い。5GC110に接続する機能をもつeNB102を、ng-eNBと呼んで良い。インタフェース114はeNB102と5GC110の間のインタフェースで、NGインタフェースと呼ばれて良い。インタフェース114には、制御信号が通る制御プレーンインタフェース、及び/又はユーザデータが通るユーザプレーンインタフェースが存在して良い。インタフェース114の制御プレーンインタフェースは5GC110内のAccess and mobility Management Function(AMF:不図示)で終端して良い。インタフェース114のユーザプレーンインタフェースは5GC110内のUser Plane Function(UPF:不図示)で終端して良い。インタフェース114の制御プレーンインタフェースをNG-Cインタフェースと呼んで良い。インタフェース114のユーザプレーンインタフェースをNG-Uインタフェースと呼んで良い。ng-eNBまたはgNBで構成される無線アクセスネットワークをNG-RANと称してもよい。NG-RAN、E-UTRAN、eNB、ng-eNBおよびgNBなどを単にネットワークと称してもよい。
The eNB102 may have the function of connecting to the 5GC110. The eNB 102 that has the function of connecting to the 5GC 110 can be called ng-eNB. Interface 114 is an interface between eNB 102 and 5GC 110 and may be called an NG interface. Interface 114 may include a control plane interface through which control signals pass, and/or a user plane interface through which user data passes. The control plane interface of interface 114 may terminate at the Access and Mobility Management Function (AMF: not shown) within 5GC 110 . The user plane interface of interface 114 may terminate at a User Plane Function (UPF: not shown) within 5GC 110 . The control plane interface of interface 114 may be called the NG-C interface. The user plane interface of interface 114 may be called the NG-U interface. A radio access network composed of ng-eNBs or gNBs may be referred to as NG-RAN. NG-RAN, E-UTRAN, eNB, ng-eNB, gNB, etc. may simply be referred to as networks.
なお、1つ又は複数のeNB102が5GC110にインタフェース114を介して接続されて良い。5GC110に接続する複数のeNB102の間に、インタフェースが存在して良い(不図示)。5GC110に接続する複数のeNB102の間のインタフェースを、Xnインタフェースと呼んで良い。また5GC110に接続するeNB102と、5GC110に接続するgNB108は、インタフェース120で接続されて良い。5GC110に接続するeNB102と、5GC110に接続するgNB108の間のインタフェース120は、Xnインタフェースと呼ばれて良い。
Note that one or more eNBs 102 may be connected to the 5GC 110 via an interface 114. There may be an interface between multiple eNBs 102 that connect to the 5GC 110 (not shown). An interface between multiple eNBs 102 connected to a 5GC 110 may be called an Xn interface. Also, the eNB 102 connected to the 5GC 110 and the gNB 108 connected to the 5GC 110 can be connected via an interface 120 . The interface 120 between the eNB 102 connected to the 5GC 110 and the gNB 108 connected to the 5GC 110 can be called the Xn interface.
gNB108はEPC104に接続する機能を持って良い。EPC104に接続する機能をもつgNB108を、en-gNBと呼んで良い。インタフェース118はgNB108とEPC104の間のインタフェースで、S1インタフェースと呼ばれて良い。インタフェース118には、ユーザデータが通るユーザプレーンインタフェースが存在して良い。インタフェース118のユーザプレーンインタフェースはEPC104内のS-GW(不図示)で終端して良い。インタフェース118のユーザプレーンインタフェースをS1-Uインタフェースと呼んで良い。またEPC104に接続するeNB102と、EPC104に接続するgNB108は、インタフェース120で接続されて良い。EPC104に接続するeNB102と、EPC104に接続するgNB108の間のインタフェース120はX2インタフェースと呼ばれて良い。
The gNB108 may have the ability to connect to the EPC104. A gNB 108 with the ability to connect to an EPC 104 may be called an en-gNB. Interface 118 is the interface between gNB 108 and EPC 104 and may be referred to as the S1 interface. Interface 118 may include a user plane interface through which user data passes. A user plane interface of interface 118 may terminate at an S-GW (not shown) within EPC 104 . The user plane interface of interface 118 may be called the S1-U interface. Also, the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 can be connected by an interface 120 . The interface 120 between the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 may be called the X2 interface.
インタフェース124はEPC104と5GC110間のインタフェースであり、CPのみ、又はUPのみ、又はCP及びUP両方を通すインタフェースであって良い。また、インタフェース114、インタフェース116、インタフェース118、インタフェース120、及びインタフェース124等のうちの一部又は全てのインタフェースは、通信事業者等が提供する通信システムに応じて存在しない場合があって良い。
The interface 124 is the interface between the EPC 104 and the 5GC 110, and can be an interface through CP only, UP only, or both CP and UP. Also, some or all of interfaces 114, 116, 118, 120, 124, etc. may not be present depending on the communication system provided by the carrier.
UE122はeNB102、及び/又はgNB108から送信される報知情報や、ページングメッセージを受信する事が可能な端末装置であって良い。またUE122は、eNB102、及び/又はgNB108との無線接続が可能な端末装置であって良い。またUE122は、eNB102との無線接続、及びgNB108と無線接続を同時に行う事が可能な端末装置であって良い。UE122はE-UTRAプロトコル、及び/又はNRプロトコルを持って良い。なお、無線接続とは、Radio Resource Control(RRC)接続であって良い。
UE122 may be a terminal device capable of receiving broadcast information and paging messages transmitted from eNB102 and/or gNB108. Also, UE 122 may be a terminal device capable of wireless connection with eNB 102 and/or gNB 108 . Also, the UE 122 may be a terminal device capable of establishing a wireless connection with the eNB 102 and a wireless connection with the gNB 108 at the same time. UE 122 may have E-UTRA and/or NR protocols. Note that the wireless connection may be a Radio Resource Control (RRC) connection.
UE122が、eNB102、及び/又はgNB108と通信する場合、UE122と、eNB102、及び/又はgNB108との間に無線ベアラ(RB:Radio Bearer)を確立する事により、無線接続を行って良い。CPに用いられる無線ベアラは、シグナリング無線ベアラ(SRB:Signaling Radio Bearer)と呼ばて良い。またUPに用いられる無線ベアラは、データ無線ベアラ(DRB Data Radio Bearer)と呼ばれて良い。各無線ベアラには、無線ベアラ識別子(Identity:ID)が割り当てられて良い。SRB用無線ベアラ識別子は、SRB識別子(SRB Identity、またはSRB ID)と呼ばれて良い。DRB用無線ベアラ識別子は、DRB識別子(DRB Identity、またはDRB ID)と呼ばれて良い。
When UE122 communicates with eNB102 and/or gNB108, radio connection may be established by establishing a radio bearer (RB) between UE122 and eNB102 and/or gNB108. A radio bearer used for the CP may be called a signaling radio bearer (SRB). A radio bearer used for UP may also be called a data radio bearer (DRB Data Radio Bearer). Each radio bearer can be assigned a radio bearer identity (ID). The SRB radio bearer identifier may be called an SRB identity (SRB ID). A DRB radio bearer identifier may be called a DRB identity (DRB ID).
またUE122は、eNB102及び/又はgNB108を介して、EPC104、及び/又は5GC110との接続が可能な端末装置であって良い。UE122が通信を行うeNB102、及び/又はgNB108の接続先コア網がEPC104である場合、UE122と、eNB102、及び/又はgNB108との間に確立された各DRBは、更にEPC104内を経由する各EPS(Evolved Packet System)ベアラと一意に紐づけられて良い。各EPSベアラは、EPSベアラ識別子(Identity、またはID)で識別されて良い。また同一のEPSベアラを通るIPパケットや、イーサネット(登録商標)フレーム等のデータには同一のQoSが保証されて良い。
Also, UE 122 may be a terminal device capable of connecting to EPC 104 and/or 5GC 110 via eNB 102 and/or gNB 108. When the connection destination core network of eNB 102 and/or gNB 108 with which UE 122 communicates is EPC 104, each DRB established between UE 122 and eNB 102 and/or gNB 108 further passes through EPC 104. (Evolved Packet System) May be uniquely associated with the bearer. Each EPS bearer can be identified by an EPS bearer identifier (Identity, or ID). Also, the same QoS may be guaranteed for data such as IP packets and Ethernet (registered trademark) frames passing through the same EPS bearer.
また、UE122が通信を行うeNB102、及び/又はgNB108の接続先コア網が5GC110である場合、UE122と、eNB102、及び/又はgNB108との間に確立された各DRBは、更に5GC110内に確立されるPDU(Packet Data Unit)セッションの一つに紐づけられて良い。各PDUセッションには、一つ又は複数のQoSフローが存在して良い。各DRBは、一つ又は複数のQoSフローと対応付け(map)されて良いし、どのQoSフローと対応づけられなくて良い。各PDUセッションは、PDUセッション識別子(Identity、Identifier、またはID)で識別されて良い。また各QoSフローは、QoSフロー識別子(Identity、Identifier、またはID)で識別されて良い。また同一のQoSフローを通るIPパケットや、イーサネットフレーム等のデータに同一のQoSが保証されて良い。
In addition, when the connection destination core network of eNB102 and/or gNB108 with which UE122 communicates is 5GC110, each DRB established between UE122 and eNB102 and/or gNB108 is further established within 5GC110. may be associated with one of the PDU (Packet Data Unit) sessions. There may be one or multiple QoS flows in each PDU session. Each DRB may be mapped to one or more QoS flows or not to any QoS flows. Each PDU session can be identified with a PDU session identifier (Identity, Identifier, or ID). Each QoS flow may also be identified with a QoS flow identifier (Identity, Identifier, or ID). Also, the same QoS may be guaranteed for data such as IP packets and Ethernet frames passing through the same QoS flow.
EPC104には、PDUセッション及び/又はQoSフローは存在しなくて良い。また5GC110にはEPSベアラは存在しなくて良い。UE122がEPC104と接続している際、UE122はEPSベアラの情報を持つが、PDUセッション及び/又はQoSフローの内の情報は持たなくて良い。またUE122が5GC110と接続している際、UE122はPDUセッション及び/又はQoSフローの内の情報を持つが、EPSベアラの情報は持たなくて良い。
The EPC 104 does not have to have PDU sessions and/or QoS flows. Also, 5GC110 does not need to have an EPS bearer. When UE 122 is connected to EPC 104, UE 122 has information of EPS bearers, but may not have information within PDU sessions and/or QoS flows. Also, when the UE 122 is connected to the 5GC 110, the UE 122 may have information in PDU sessions and/or QoS flows, but not EPS bearer information.
なお、以下の説明において、eNB102および/またはgNB108を単に基地局装置とも称し、UE122を単に端末装置又はUEとも称する。
In the following description, eNB 102 and/or gNB 108 are also simply referred to as base station apparatuses, and UE 122 is simply referred to as terminal apparatus or UE.
図2は本発明の実施形態に係るE-UTRAプロトコル構成(protocol architecture)の一例の図である。また図3は本発明の実施形態に係るNRプロトコル構成の一例の図である。なお図2及び/又は図3を用いて説明する各プロトコルの機能は、本発明の実施形態に密接に関わる一部の機能であり、他の機能を持っていて良い。なお、本発明の実施の形態において、上りリンク(uplink:UL)とは端末装置から基地局装置へのリンクであって良い。また本発明の実施の形態において、下りリンク(downlink:DL)とは基地局装置から端末装置へのリンクであって良い。
FIG. 2 is a diagram of an example of E-UTRA protocol architecture according to an embodiment of the present invention. Also, FIG. 3 is a diagram of an example of the NR protocol configuration according to the embodiment of the present invention. Note that the functions of each protocol described using FIG. 2 and/or FIG. 3 are part of the functions closely related to the embodiment of the present invention, and may have other functions. In addition, in the embodiment of the present invention, an uplink (UL) may be a link from a terminal device to a base station device. Also, in the embodiments of the present invention, the downlink (DL) may be a link from the base station apparatus to the terminal apparatus.
図2(A)はE-UTRAユーザプレーン(UP)プロトコルスタックの図である。図2(A)に示す通り、E-UTRAN UPプロトコルは、UE122とeNB102の間のプロトコルであって良い。即ちE-UTRANUPプロトコルは、ネットワーク側ではeNB102で終端するプロトコルであって良い。図2(A)に示す通り、E-UTRAユーザプレーンプロトコルスタックは、無線物理層(無線物理レイヤ)であるPHY(Physical layer)200、媒体アクセス制御層(媒体アクセス制御レイヤ)であるMAC(Medium Access Control)202、無線リンク制御層(無線リンク制御レイヤ)であるRLC(Radio Link Control)204、及びパケットデータ収束プロトコル層(パケットデータ収束プロトコルレイヤ)であるPDCP(Packet Data Convergence Protocol)206から構成されて良い。
Figure 2(A) is a diagram of the E-UTRA User Plane (UP) protocol stack. The E-UTRAN UP protocol may be the protocol between UE 122 and eNB 102, as shown in FIG. 2(A). That is, the E-UTRANUP protocol may be a protocol that terminates at the eNB 102 on the network side. As shown in Figure 2(A), the E-UTRA user plane protocol stack consists of a PHY (Physical layer) 200 that is a radio physical layer (radio physical layer), a MAC (Medium) that is a medium access control layer (medium access control layer). Access Control) 202, RLC (Radio Link Control) 204 as a radio link control layer (radio link control layer), and PDCP (Packet Data Convergence Protocol) 206 as a packet data convergence protocol layer. good to be
図3(A)はNRユーザプレーン(UP)プロトコルスタックの図である。図3(A)に示す通り、NRUPプロトコルは、UE122とgNB108の間のプロトコルであって良い。即ちNR UPプロトコルは、ネットワーク側ではgNB108で終端するプロトコルであって良い。図3(A)に示す通り、E-UTRAユーザプレーンプロトコルスタックは、無線物理層であるPHY300、媒体アクセス制御層であるMAC302、無線リンク制御層であるRLC304、パケットデータ収束プロトコル層である、PDCP306、及びサービスデータ適応プロトコル層(サービスデータ適応プロトコルレイヤ)であるSDAP(Service Data Adaptation Protocol)310であるから構成されて良い。
Figure 3(A) is a diagram of the NR user plane (UP) protocol stack. The NRUP protocol may be the protocol between UE 122 and gNB 108, as shown in FIG. 3(A). That is, the NR UP protocol may be a protocol that terminates at the gNB 108 on the network side. As shown in FIG. 3(A), the E-UTRA user plane protocol stack consists of PHY 300, which is a radio physical layer, MAC 302, which is a medium access control layer, RLC 304, which is a radio link control layer, and PDCP 306, which is a packet data convergence protocol layer. , and SDAP (Service Data Adaptation Protocol) 310, which is a service data adaptation protocol layer.
図2(B)はE-UTRA制御プレーン(CP)プロトコル構成の図である。図2(B)に示す通り、E-UTRAN CPプロトコルにおいて、無線リソース制御層(無線リソース制御レイヤ)であるRRC(Radio Resource Control)208は、UE122とeNB102の間のプロトコルであって良い。即ちRRC208は、ネットワーク側ではeNB102で終端するプロトコルであって良い。またE-UTRAN CPプロトコルにおいて、非AS(Access Stratum)層(非ASレイヤ)であるNAS(Non Access Stratum)210は、UE122とMMEとの間のプロトコルであって良い。即ちNAS210は、ネットワーク側ではMMEで終端するプロトコルであって良い。
Figure 2(B) is a diagram of the E-UTRA control plane (CP) protocol configuration. As shown in FIG. 2(B), in the E-UTRAN CP protocol, RRC (Radio Resource Control) 208, which is a radio resource control layer, may be a protocol between UE 122 and eNB 102. That is, RRC 208 may be a protocol that terminates at eNB 102 on the network side. Also, in the E-UTRAN CP protocol, NAS (Non Access Stratum) 210, which is a non-AS (Access Stratum) layer (non-AS layer), may be a protocol between UE 122 and MME. That is, the NAS 210 may be a protocol that terminates at the MME on the network side.
図3(B)はNR制御プレーン(CP)プロトコル構成の図である。図3(B)に示す通り、NR CPプロトコルにおいて、無線リソース制御層であるRRC308は、UE122とgNB108の間のプロトコルであって良い。即ちRRC308は、ネットワーク側ではgNB108で終端するプロトコルであって良い。またE-UTRAN CPプロトコルにおいて、非AS層であるNAS312は、UE122とAMFとの間のプロトコルであって良い。即ちNAS312は、ネットワーク側ではAMFで終端するプロトコルであって良い。
Fig. 3(B) is a diagram of the NR control plane (CP) protocol configuration. As shown in FIG. 3(B), in the NR CP protocol, RRC 308, which is the radio resource control layer, may be the protocol between UE 122 and gNB 108. That is, RRC 308 may be a protocol that terminates at gNB 108 on the network side. Also in the E-UTRAN CP protocol, the non-AS layer NAS 312 may be the protocol between the UE 122 and AMF. That is, the NAS 312 may be a protocol that terminates with AMF on the network side.
なおAS(Access Stratum)層とは、UE122とeNB102及び/又はgNB108との間で終端する層であって良い。即ちAS層とは、PHY200、MAC202、RLC204、PDCP206、及びRRC208の一部又は全てを含む層、及び/又はPHY300、MAC302、RLC304、PDCP306、SDAP310、及びRRC308の一部又は全てを含む層であって良い。
The AS (Access Stratum) layer may be a layer that terminates between UE 122 and eNB 102 and/or gNB 108. That is, the AS layer is a layer including part or all of PHY200, MAC202, RLC204, PDCP206 and RRC208 and/or a layer including part or all of PHY300, MAC302, RLC304, PDCP306, SDAP310 and RRC308. good
なお本発明の実施の形態において、以下E-UTRAのプロトコルとNRのプロトコルを区別せず、PHY(PHY層)、MAC(MAC層)、RLC(RLC層)、PDCP(PDCP層)、RRC(RRC層)、NAS(NAS層)と言う用語を用いる場合がある。この場合、PHY(PHY層)、MAC(MAC層)、RLC(RLC層)、PDCP(PDCP層)、RRC(RRC層)、NAS(NAS層)は其々E-UTRAプロトコルのPHY(PHY層)、MAC(MAC層)、RLC(RLC層)、PDCP(PDCP層)、RRC(RRC層)、NAS(NAS層)であって良いし、NRプロトコルの、PHY(PHY層)、MAC(MAC層)、RLC(RLC層)、PDCP(PDCP層)、RRC(RRC層)、NAS(NAS層)であって良い。またSDAP(SDAP層)は、NRプロトコルのSDAP(SDAP層)であって良い。
In the embodiments of the present invention, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC ( RRC layer) and NAS (NAS layer) are sometimes used. In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) are the PHY (PHY layer) of the E-UTRA protocol. ), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), NAS (NAS layer), NR protocol, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), NAS (NAS layer). Also, the SDAP (SDAP layer) may be the SDAP (SDAP layer) of the NR protocol.
また本発明の実施の形態において、以下E-UTRAのプロトコルとNRのプロトコルを区別する場合、PHY200、MAC202、RLC204、PDCP206、及びRRC208を、それぞれE-UTRA用PHY又はLTE用PHY、E-UTRA用MAC又はLTE用MAC、E-UTRA用RLC又はLTE用RLC、E-UTRA用PDCP又はLTE用PDCP、及びE-UTRA用RRC又はLTE用RRCと呼ぶ事もある。またPHY200、MAC202、RLC204、PDCP206、及びRRC208を、それぞれE-UTRA PHY又はLTE PHY、E-UTRA MAC又はLTE MAC、E-UTRA RLC又はLTE RLC、E-UTRA PDCP又はLTE PDCP、及びE-UTRA RRC又はLTE RRCなどと記述する場合もある。また、E-UTRAのプロトコルとNRのプロトコルを区別する場合、PHY300、MAC302、RLC304、PDCP306、RRC308を、それぞれNR用PHY、NR用MAC、NR用RLC、NR用RLC、及びNR用RRCと呼ぶ事もある。またPHY200、MAC302、RLC304、PDCP306、及びRRC308を、それぞれNR PHY、NR MAC、NR RLC、NR PDCP、NR RRCなどと記述する場合もある。
Further, in the embodiment of the present invention, when distinguishing between E-UTRA protocol and NR protocol, PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208 are respectively defined as PHY for E-UTRA or PHY for LTE, E-UTRA MAC for LTE or MAC for LTE, RLC for E-UTRA or RLC for LTE, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE. PHY200, MAC202, RLC204, PDCP206 and RRC208 respectively E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP and E-UTRA It may also be described as RRC or LTE RRC. Also, when distinguishing between the E-UTRA protocol and the NR protocol, PHY 300, MAC 302, RLC 304, PDCP 306, and RRC 308 are called PHY for NR, MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively. There is also a thing. PHY 200, MAC 302, RLC 304, PDCP 306, and RRC 308 may also be described as NR PHY, NR MAC, NR RLC, NR PDCP, NR RRC, etc., respectively.
E-UTRA及び/又はNRのAS層におけるエンティティ(entity)について説明する。MAC層の機能の一部又は全てを持つエンティティの事をMACエンティティと呼んで良い。RLC層の機能の一部又は全てを持つエンティティの事をRLCエンティティと呼んで良い。PDCP層の機能の一部又は全てを持つエンティティの事をPDCPエンティティと呼んで良い。SDAP層の機能の一部又は全てを持つエンティティの事をSDAPエンティティと呼んで良い。RRC層の機能の一部又は全てを持つエンティティの事をRRCエンティティと呼んで良い。MACエンティティ、RLCエンティティ、PDCPエンティティ、SDAPエンティティ、RRCエンティティを、其々MAC、RLC、PDCP、SDAP、RRCと言い換えて良い。
Explain the entities in the AS layer of E-UTRA and/or NR. An entity that has some or all of the functionality of the MAC layer may be called a MAC entity. An entity that has some or all of the functionality of the RLC layer may be called an RLC entity. An entity that has some or all of the functions of the PDCP layer may be called a PDCP entity. An entity that has some or all of the functionality of the SDAP layer may be called an SDAP entity. An entity that has some or all of the functionality of the RRC layer may be called an RRC entity. The MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be replaced with MAC, RLC, PDCP, SDAP, and RRC, respectively.
なお、MAC、RLC、PDCP、SDAPから下位層に提供されるデータ、及び/又はMAC、RLC、PDCP、SDAPに下位層から提供されるデータの事を、それぞれMAC PDU(Protocol Data Unit)、RLC PDU、PDCP PDU、SDAP PDUと呼んで良い。また、MAC、RLC、PDCP、SDAPに上位層から提供されるデータ、及び/又はMAC、RLC、PDCP、SDAPから上位層に提供するデータの事を、それぞれMAC SDU(Service Data Unit)、RLC SDU、PDCP SDU、SDAP SDUと呼んで良い。また、セグメントされたRLC SDUの事をRLC SDUセグメントと呼んで良い。
The data provided from MAC, RLC, PDCP, SDAP to the lower layer and/or the data provided from the lower layer to MAC, RLC, PDCP, SDAP shall be MAC PDU (Protocol Data Unit), RLC respectively. You can call them PDUs, PDCP PDUs, SDAP PDUs. In addition, MAC SDU (Service Data Unit) and RLC SDU for data provided from upper layers to MAC, RLC, PDCP, and SDAP and/or data provided from MAC, RLC, PDCP, and SDAP to upper layers, respectively , PDCP SDU, SDAP SDU. A segmented RLC SDU may also be called an RLC SDU segment.
PHYの機能の一例について説明する。端末装置のPHYは基地局装置のPHYから、下りリンク(Downlink:DL)物理チャネル(Physical Channel)を介して伝送されたデータを受信する機能を有して良い。端末装置のPHYは基地局装置のPHYに対し、上りリンク(Uplink:UL)物理チャネルを介してデータを送信する機能を有して良い。PHYは上位のMACと、トランスポートチャネル(Transport Channel)で接続されて良い。PHYはトランスポートチャネルを介してMACにデータを受け渡して良い。またPHYはトランスポートチャネルを介してMACからデータを提供されて良い。PHYにおいて、様々な制御情報を識別するために、RNTI(Radio Network Temporary Identifier)が用いられて良い。
I will explain an example of PHY functions. 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 the capability of transmitting data to the PHY of the base station device via an uplink (UL) physical channel. A PHY may be connected to a high-level MAC via a Transport Channel. The PHY may pass data to the MAC over transport channels. The PHY can also be provided with data from the MAC over the transport channel. A Radio Network Temporary Identifier (RNTI) can be used in the PHY to identify various control information.
ここで、物理チャネルについて説明する。
Here, the physical channel will be explained.
端末装置と基地局装置との無線通信に用いられる物理チャネルには、以下の物理チャネルが含まれてよい。
The physical channels used for wireless communication between the terminal device and the base station device may include the following physical channels.
PBCH(物理報知チャネル:Physical Broadcast CHannel)
PDCCH(物理下りリンク制御チャネル:Physical Downlink Control CHannel)
PDSCH(物理下りリンク共用チャネル:Physical Downlink Shared CHannel)
PUCCH(物理上りリンク制御チャネル:Physical Uplink Control CHannel)
PUSCH(物理上りリンク共用チャネル:Physical Uplink Shared CHannel)
PRACH(物理ランダムアクセスチャネル:Physical Random Access CHannel) PBCH (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)
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 (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は、端末装置が必要とするシステム情報を報知するために用いられて良い。
The PBCH may be used to broadcast system information required by terminal equipment.
また、NRにおいて、PBCHは、同期信号のブロック(SS/PBCHブロックとも称する)の周期内の時間インデックス(SSB-Index)を報知するために用いられてよい。
Also, in NR, the PBCH may be used to report the time index (SSB-Index) within the period of a block of synchronization signals (also called SS/PBCH block).
PDCCHは、下りリンクの無線通信(基地局装置から端末装置への無線通信)において、下りリンク制御情報(Downlink Control Information:DCI)を送信する(または運ぶ)ために用いられて良い。ここで、下りリンク制御情報の送信に対して、一つまたは複数のDCI(DCIフォーマットと称してもよい)が定義されて良い。すなわち、下りリンク制御情報に対するフィールドがDCIとして定義され、情報ビットへマップされて良い。PDCCHは、PDCCH候補(candidate)において送信されて良い。端末装置は、サービングセルにおいてPDCCH候補のセットをモニタして良い。PDCCH候補のセットをモニタするとは、あるDCIフォーマットに応じてPDCCHのデコードを試みることを意味して良い。DCIフォーマットは、サービングセルにおけるPUSCHのスケジューリングのために用いられてもよい。PUSCHは、ユーザデータの送信や、後述するRRCメッセージの送信などのために使われてよい。
The PDCCH can be used to transmit (or carry) downlink control information (DCI) in downlink radio communication (radio communication from the base station device to the terminal device). Here, one or more DCIs (which may be referred to as DCI formats) may be defined for transmission of downlink control information. That is, a field for downlink control information can be defined as DCI and mapped to information bits. A PDCCH can be sent in a PDCCH candidate. A terminal can monitor a set of PDCCH candidates in a serving cell. Monitoring the set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format. The DCI format may be used for PUSCH scheduling in the serving cell. PUSCH may be used for transmission of user data, transmission of RRC messages to be described later, and the like.
PUCCHは、上りリンクの無線通信(端末装置から基地局装置への無線通信)において、上りリンク制御情報(Uplink Control Information:UCI)を送信するために用いられてよい。ここで、上りリンク制御情報には、下りリンクのチャネルの状態を示すために用いられるチャネル状態情報(CSI:Channel State Information)が含まれてもよい。また、上りリンク制御情報には、UL-SCH(UL-SCH:Uplink Shared CHannel)リソースを要求するために用いられるスケジューリング要求(SR:Scheduling Request)が含まれてもよい。また、上りリンク制御情報には、HARQ-ACK(Hybrid Automatic Repeat reQuest ACKnowledgement)が含まれてもよい。
The PUCCH may be used to transmit uplink control information (UCI) in uplink radio communication (radio communication from a terminal device to a base station device). Here, the uplink control information may include channel state information (CSI: Channel State Information) used to indicate the state of the downlink channel. Also, the uplink control information may include a scheduling request (SR: Scheduling Request) used to request UL-SCH (UL-SCH: Uplink Shared CHannel) resources. Also, the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement).
PDSCHは、MAC層からの下りリンクデータ(DL-SCH:Downlink Shared CHannel)の送信に用いられてよい。またPDSCHは、下りリンクの場合にはシステム情報(SI:System Information)やランダムアクセス応答(RAR:Random Access Response)などの送信に用いられて良い。
The PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer. In addition, PDSCH may be used for transmission of system information (SI: System Information), random access response (RAR: Random Access Response), etc. in the case of downlink.
PUSCHは、MAC層からの上りリンクデータ(UL-SCH:Uplink Shared CHannel)または上りリンクデータと共にHARQ-ACKおよび/またはCSIを送信するために用いられてもよい。またPUSCHは、CSIのみ、または、HARQ-ACKおよびCSIのみを送信するために用いられてもよい。すなわちPUSCHは、UCIのみを送信するために用いられてもよい。また、PDSCHまたはPUSCHは、RRCシグナリング(RRCメッセージとも称する)、およびMACコントロールエレメントを送信するために用いられてもよい。ここで、PDSCHにおいて、基地局装置から送信されるRRCシグナリングは、セル内における複数の端末装置に対して共通のシグナリングであってもよい。また、基地局装置から送信されるRRCシグナリングは、ある端末装置に対して専用のシグナリング(dedicated signalingとも称する)であってもよい。すなわち、端末装置固有(UEスペシフィック)の情報は、ある端末装置に対して専用のシグナリングを用いて送信されてもよい。また、PUSCHは、上りリンクにおいてUEの能力(UE Capability)の送信に用いられてもよい。
PUSCH may be used to transmit HARQ-ACK and/or CSI together with uplink data (UL-SCH: Uplink Shared CHannel) or uplink data from the MAC layer. PUSCH may also be used to transmit CSI only, or HARQ-ACK and CSI only. That is, PUSCH may be used to transmit UCI only. PDSCH or PUSCH may also be used to transmit RRC signaling (also referred to as RRC messages) and MAC control elements. Here, in the PDSCH, RRC signaling transmitted from the base station apparatus may be signaling common to multiple terminal apparatuses within the cell. Also, the RRC signaling transmitted from the base station apparatus may be signaling dedicated to a certain terminal apparatus (also referred to as dedicated signaling). That is, terminal device-specific (UE-specific) information may be transmitted using signaling dedicated to a certain terminal device. PUSCH may also be used to transmit UE Capability in the uplink.
PRACHは、ランダムアクセスプリアンブルを送信するために用いられてもよい。PRACHは、初期コネクション確立(initial connection establishment)プロシージャ、ハンドオーバプロシージャ、コネクション再確立(connection re-establishment)プロシージャ、上りリンク送信に対する同期(タイミング調整)、およびUL-SCHリソースの要求を示すために用いられてもよい。
The PRACH may be used to transmit random access preambles. PRACH is used to indicate initial connection establishment procedures, handover procedures, connection re-establishment procedures, synchronization (timing adjustments) for uplink transmissions, and requests for UL-SCH resources. may
MACの機能の一例について説明する。MACは、MAC副層(サブレイヤ)と呼ばれて良い。MACは、多様な論理チャネル(ロジカルチャネル:Logical Channel)を、対応するトランスポートチャネルに対してマッピングを行う機能を持って良い。論理チャネルは、論理チャネル識別子(Logical Channel Identity、又はLogical Channel ID)によって識別されて良い。MACは上位のRLCと、論理チャネル(ロジカルチャネル)で接続されて良い。論理チャネルは、伝送される情報の種類によって、制御情報を伝送する制御チャネルと、ユーザ情報を伝送するトラフィックチャネルに分けられて良い。また論理チャネルは、上りリンク論理チャネルと、下りリンク論理チャネルに分けられて良い。MACは、一つ又は複数の異なる論理チャネルに所属するMAC SDUを多重化(multiplexing)して、PHYに提供する機能を持って良い。またMACは、PHYから提供されたMAC PDUを逆多重化(demultiplexing)し、各MAC SDUが所属する論理チャネルを介して上位レイヤに提供する機能を持って良い。またMACは、HARQ(Hybrid Automatic Repeat reQuest)を通して誤り訂正を行う機能を持って良い。またMACは、スケジューリング情報(scheduling information)をレポートする、スケジューリングレポート(Scheduling Report:SR)機能を持って良い。MACは、動的スケジューリングを用いて、端末装置間の優先処理を行う機能を持って良い。またMACは、一つの端末装置内の論理チャネル間の優先処理を行う機能を持って良い。MACは、一つの端末装置内でオーバーラップしたリソースの優先処理を行う機能を持って良い。E-UTRA MACはMultimedia Broadcast Multicast Services(MBMS)を識別する機能を持って良い。またNR MACは、マルチキャスト/ブロードキャストサービス(Multicast Broadcast Service:MBS)を識別する機能を持って良い。MACは、トランスポートフォーマットを選択する機能を持って良い。MACは、間欠受信(DRX:Discontinuous Reception)及び/又は間欠送信(DTX:Discontinuous Transmission)を行う機能、ランダムアクセス(Random Access:RA)手順を実行する機能、送信可能電力の情報を通知する、パワーヘッドルームレポート(Power Headroom Report:PHR)機能、送信バッファのデータ量情報を通知する、バッファステイタスレポート(Buffer Status Report:BSR)機能、などを持って良い。NR MACは帯域適応(Bandwidth Adaptation:BA)機能を持って良い。またE-UTRA MACで用いられるMAC PDUフォーマットとNR MACで用いられるMAC PDUフォーマットは異なって良い。またMAC PDUには、MACにおいて制御を行うための要素である、MAC制御要素(MACコントロールエレメント:MAC CE)が含まれて良い。
I will explain an example of MAC functions. A MAC may be referred to as a MAC sublayer. The MAC may have functionality for mapping various logical channels (Logical Channels) to corresponding transport channels. A logical channel may be identified by a Logical Channel Identity (or Logical Channel ID). The MAC may be connected with the upper RLC by a logical channel (logical channel). Logical channels can be divided into control channels for transmitting control information and traffic channels for transmitting user information according to the type of information to be transmitted. Logical channels may also be divided into uplink logical channels and downlink logical channels. The MAC may be capable of multiplexing MAC SDUs belonging to one or more different logical channels and providing them to the PHY. The MAC may also have the function of demultiplexing the MAC PDUs provided by the PHY and providing them to upper layers via the logical channel to which each MAC SDU belongs. Also, the MAC may 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 the ability to prioritize between terminals using dynamic scheduling. Also, the MAC may have a function of performing priority processing between logical channels within one terminal device. The MAC may have the capability of prioritizing overlapping resources within one terminal device. E-UTRA MAC may have the ability to identify Multimedia Broadcast Multicast Services (MBMS). Also, NR MAC may have a function to identify Multicast/Broadcast Service (MBS). A MAC may have the ability to select a transport format. MAC has a function of performing discontinuous reception (DRX) and / or discontinuous transmission (DTX: discontinuous transmission), a function of executing random access (RA) procedure, notifying information of transmittable power, power It is good to have a headroom report (Power Headroom Report: PHR) function, a buffer status report (BSR) function that notifies the amount of data in the transmission buffer, and so on. NR MAC may have a Bandwidth Adaptation (BA) function. Also, the MAC PDU format used in E-UTRA MAC and the MAC PDU format used in NR MAC may be different. The MAC PDU may also include a MAC control element (MAC control element: MAC CE), which is an element for performing control in MAC.
E-UTRA及び/又はNRで用いられる、上りリンク(UL:Uplink)、及び/又は下りリンク(DL:Downlink)用論理チャネルについて説明する。
Explains the uplink (UL: Uplink) and/or downlink (DL: Downlink) logical channels used in E-UTRA and/or NR.
BCCH(Broadcast Control Channel)は、システム情報(SI:System Information)等の、制御情報を報知(broadcast)するための下りリンク論理チャネルであって良い。
BCCH (Broadcast Control Channel) may be a downlink logical channel for broadcasting control information such as system information (SI: System Information).
PCCH(Paging Control Channel)は、ページング(Paging)メッセージを運ぶための下りリンク論理チャネルであって良い。
PCCH (Paging Control Channel) may be a downlink logical channel for carrying paging messages.
CCCH(Common Control Channel)は、端末装置と基地局装置との間で制御情報を送信するための論理チャネルであって良い。CCCHは、端末装置が、RRC接続を有しない場合に用いられて良い。またCCCHは基地局装置と複数の端末装置との間で使われて良い。
A CCCH (Common Control Channel) may be a logical channel for transmitting control information between a terminal device and a base station device. CCCH may be used when the terminal does not have an RRC connection. CCCH may also be used between a base station and multiple terminals.
DCCH(Dedicated Control Channel)は、端末装置と基地局装置との間で、1対1(point-to-point)の双方向(bi-directional)で、専用制御情報を送信するための論理チャネルであって良い。専用制御情報とは、各端末装置専用の制御情報であって良い。DCCHは、端末装置が、RRC接続を有する場合に用いられて良い。
DCCH (Dedicated Control Channel) is a logical channel for transmitting dedicated control information in a one-to-one (point-to-point) bi-directional manner between a terminal device and a base station device. It's fine. Dedicated control information may be control information dedicated to each terminal device. DCCH may be used when a terminal device has an RRC connection.
DTCH(Dedicated Traffic Channel)は、端末装置と基地局装置との間で、1対1(point-to-point)で、ユーザデータを送信するための論理チャネルであって良い。DTCHは専用ユーザデータを送信するための論理チャネルであって良い。専用ユーザデータとは、各端末装置専用のユーザデータであって良い。DTCHは上りリンク、下りリンク両方に存在して良い。
A DTCH (Dedicated Traffic Channel) may be a logical channel for transmitting user data on a one-to-one (point-to-point) basis between a terminal device and a base station device. A DTCH may be a logical channel for transmitting dedicated user data. Dedicated user data may be user data dedicated to each terminal device. DTCH may exist in both uplink and downlink.
E-UTRA及び/又はNRにおける上りリンクの、論理チャネルとトランスポートチャネルのマッピングについて説明する。
Explains the uplink mapping of logical channels and transport channels in E-UTRA and/or NR.
CCCHは、上りリンクトランスポートチャネルである、UL-SCH(Uplink Shared Channel)にマップされて良い。
CCCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.
DCCHは、上りリンクトランスポートチャネルである、UL-SCH(Uplink Shared Channel)にマップされて良い。
The DCCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.
DTCHは、上りリンクトランスポートチャネルである、UL-SCH(Uplink Shared Channel)にマップされて良い。
DTCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.
E-UTRA及び/又はNRにおける下りリンクの、論理チャネルとトランスポートチャネルのマッピングについて説明する。
Explains the mapping of downlink logical channels and transport channels in E-UTRA and/or NR.
BCCHは、下りリンクトランスポートチャネルであるBCH(Broadcast Channel)、及び/又はDL-SCH(Downlink Shared Channel)にマップされて良い。
BCCH may be mapped to BCH (Broadcast Channel) and/or DL-SCH (Downlink Shared Channel), which are downlink transport channels.
PCCHは、下りリンクトランスポートチャネルであるPCH(Paging Channel)にマップされて良い。
PCCH may be mapped to PCH (Paging Channel), which is a downlink transport channel.
CCCHは、下りリンクトランスポートチャネルであるDL-SCH(Downlink Shared Channel)にマップされて良い。
CCCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.
DCCHは、下りリンクトランスポートチャネルであるDL-SCH(Downlink Shared Channel)にマップされて良い。
The DCCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.
DTCHは、下りリンクトランスポートチャネルであるDL-SCH(Downlink Shared Channel)にマップされて良い。
DTCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.
RLCの機能の一例について説明する。RLCは、RLC副層(サブレイヤ)と呼ばれて良い。E-UTRA RLCは、上位レイヤのPDCPから提供されたデータを、分割(Segmentation)及び/又は結合(Concatenation)し、下位層(下位レイヤ)に提供する機能を持って良い。E-UTRA RLCは、下位レイヤから提供されたデータに対し、再組立て(reassembly)及びリオーダリング(re-ordering)を行い、上位レイヤに提供する機能を持って良い。NR RLCは、上位レイヤのPDCPから提供されたデータに、PDCPで付加されたシーケンス番号とは独立したシーケンス番号を付加する機能を持って良い。またNR RLCは、PDCPから提供されたデータを分割(Segmentation)し、下位レイヤに提供する機能を持って良い。またNR RLCは、下位レイヤから提供されたデータに対し、再組立て(reassembly)を行い、上位レイヤに提供する機能を持って良い。またRLCは、データの再送機能及び/又は再送要求機能(Automatic Repeat reQuest:ARQ)を持って良い。またRLCは、ARQによりエラー訂正を行う機能を持って良い。ARQを行うために、RLCの受信側から送信側に送られる、再送が必要なデータを示す制御情報を、ステータスレポートと言って良い。またRLCの送信側から受信側に送られる、ステータスレポート送信指示の事をポール(poll)と言って良い。またRLCは、データ重複の検出を行う機能を持って良い。またRLCはデータ破棄の機能を持って良い。RLCには、トランスパレントモード(TM:Transparent Mode)、非応答モード(UM:Unacknowledged Mode)、応答モード(AM:Acknowledged Mode)の3つのモードがあって良い。TMでは上位層から受信したデータの分割は行わず、RLCヘッダの付加は行わなくて良い。TM RLCエンティティは単方向(uni-directional)のエンティティであって、送信(transmitting)TM RLCエンティティとして、又は受信(receiving)TM RLCエンティティとして設定されて良い。UMでは上位層から受信したデータの分割及び/又は結合、RLCヘッダの付加等は行うが、データの再送制御は行わなくて良い。UM RLCエンティティは単方向のエンティティであっても良いし双方向(bi-directional)のエンティティであっても良い。UM RLCエンティティが単方向のエンティティである場合、UM RLCエンティティは送信UM RLCエンティティとして、又は受信UM RLCエンティティとして設定されて良い。UM RLCエンティティが双方向のエンティティである場合、UM RRCエンティティは送信(transmitting)サイド及び受信(receiving)サイドから構成されるUM RLCエンティティとして設定されて良い。AMでは上位層から受信したデータの分割及び/又は結合、RLCヘッダの付加、データの再送制御等を行って良い。AM RLCエンティティは双方向のエンティティであって、送信(transmitting)サイド及び受信(receiving)サイドから構成されるAM RLCとして設定されて良い。なお、TMで下位層に提供するデータ、及び/又は下位層から提供されるデータの事をTMD PDUと呼んで良い。またUMで下位層に提供するデータ、及び/又は下位層から提供されるデータの事をUMD PDUと呼んで良い。またAMで下位層に提供するデータ、又は下位層から提供されるデータの事をAMD PDUと呼んで良い。E-UTRA RLCで用いられるRLC PDUフォーマットとNR RLCで用いられるRLC PDUフォーマットは異なって良い。またRLC PDUには、データ用RLC PDUと制御用RLC PDUがあって良い。データ用RLC PDUを、RLC DATA PDU(RLC Data PDU、RLCデータPDU)と呼んで良い。また制御用RLC PDUを、RLC CONTROL PDU(RLC Control PDU、RLCコントロールPDU、RLC制御PDU)と呼んで良い。
Explain an example of RLC functions. RLC may be referred to as an RLC sublayer. The E-UTRA RLC may have the function of segmenting and/or concatenating data provided from the upper layer PDCP and providing it to the lower layer. E-UTRA RLC may have the capability to reassemble and re-order data provided by lower layers and provide it to upper layers. The NR RLC may have a function of adding a sequence number independent of the sequence number added by PDCP to the data provided by PDCP of the upper layer. Also, NR RLC may have a function of segmenting data provided from PDCP and providing it to lower layers. Also, the NR RLC may have a function of reassembling data provided from lower layers and providing the reassembled data to upper layers. The RLC may also have a data retransmission function and/or a retransmission request function (Automatic Repeat reQuest: ARQ). Also, RLC may have a function of performing error correction by ARQ. The control information sent from the RLC receiving side to the transmitting side in order to perform ARQ, indicating data that needs to be retransmitted, can be called a status report. Also, the status report transmission instruction sent from the RLC transmitting side to the receiving side can be called a poll. RLC may also have a function to detect data duplication. RLC may also have a function of data discarding. RLC may have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The TM does not divide the data received from the upper layer, and does not need to add an RLC header. A TM RLC entity is a uni-directional entity and may be configured as a transmitting TM RLC entity or as a receiving TM RLC entity. The UM divides and/or combines the data received from the upper layer, adds an RLC header, etc., but does not need to perform data retransmission control. A UM RLC entity may be a unidirectional entity or a bi-directional entity. If the UM RLC entity is a unidirectional entity, the UM RLC entity may be configured as a transmitting UM RLC entity or as a receiving UM RLC entity. If the UM RLC entity is a bidirectional entity, the UM RRC entity may be configured as a UM RLC entity consisting of a transmitting side and a receiving side. The AM may divide and/or combine data received from the upper layer, add an RLC header, control data retransmission, and the like. 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 lower layers by TM and/or data provided from lower layers may be called TMD PDU. Data provided by UM to lower layers and/or data provided by lower layers may be referred to as UMD PDUs. Data provided to the lower layer by AM or data provided from the lower layer may be called AMD PDU. The RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC can be different. Also, RLC PDUs may include RLC PDUs for data and RLC PDUs for control. An RLC PDU for data may be called an RLC DATA PDU (RLC Data PDU). Also, the control RLC PDU may be called an RLC CONTROL PDU.
PDCPの機能の一例について説明する。PDCPは、PDCP副層(サブレイヤ)と呼ばれて良い。PDCPは、シーケンス番号のメンテナンスを行う機能を持って良い。またPDCPは、IPパケット(IP Packet)や、イーサネットフレーム等のユーザデータを無線区間で効率的に伝送するための、ヘッダ圧縮・解凍機能を持ってもよい。IPパケットのヘッダ圧縮・解凍に用いられるプロトコルをROHC(Robust Header Compression)プロトコルと呼んで良い。またイーサネットフレームヘッダ圧縮・解凍に用いられるプロトコルをEHC(Ethernet(登録商標)Header Compression)プロトコルと呼んで良い。また、PDCPは、データの暗号化・復号化の機能を持ってもよい。また、PDCPは、データの完全性保護・完全性検証の機能を持ってもよい。またPDCPは、リオーダリング(re-ordering)の機能を持って良い。またPDCPは、PDCP SDUの再送機能を持って良い。またPDCPは、破棄タイマー(discard timer)を用いたデータ破棄を行う機能を持って良い。またPDCPは、多重化(Duplication)機能を持って良い。またPDCPは、重複受信したデータを破棄する機能を持って良い。PDCPエンティティは双方向のエンティティであって、送信(transmitting)PDCPエンティティ、及び受信(receiving)PDCPエンティティから構成されて良い。またE-UTRA PDCPで用いられるPDCP PDUフォーマットとNR PDCPで用いられるPDCP PDUフォーマットは異なって良い。またPDCP PDUには、データ用PDCP PDUと制御用PDCP PDUがあって良い。データ用PDCP PDUを、PDCP DATA PDU(PDCP Data PDU、PDCPデータPDU)と呼んで良い。また制御用PDCP PDUを、PDCP CONTROL PDU(PDCP Control PDU、PDCPコントロールPDU、PDCP制御PDU)と呼んで良い。
An example of PDCP functions will be explained. PDCP may be referred to as a PDCP sublayer. PDCP may have a function to maintain sequence numbers. PDCP may also have a header compression/decompression function for efficiently transmitting user data such as IP packets and Ethernet frames over a wireless section. The protocol used for IP packet header compression/decompression may be called the ROHC (Robust Header Compression) protocol. Also, the protocol used for Ethernet frame header compression/decompression may be called EHC (Ethernet (registered trademark) Header Compression) protocol. PDCP may also have a data encryption/decryption function. PDCP may also have the function of integrity protection and integrity verification of data. PDCP may also have a re-ordering function. PDCP may also have a retransmission function for PDCP SDUs. PDCP may also have a function of discarding data using a discard timer. PDCP may also have a duplication function. In addition, PDCP may have a function of discarding duplicated received data. The PDCP entity is a bi-directional entity and can consist of a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. PDCP PDUs may include data PDCP PDUs and control PDCP PDUs. A PDCP PDU for data may be called a PDCP DATA PDU (PDCP Data PDU). Also, the control PDCP PDU may be called a PDCP CONTROL PDU.
SDAPの機能の一例について説明する。SDAPは、サービスデータ適応プロトコル層(サービスデータ適応プロトコルレイヤ)である。SDAPは、5GC110から基地局装置を介して端末装置に送られるダウンリンクのQoSフローとデータ無線ベアラ(DRB)との対応付け(マッピング:mapping)、及び/又は端末装置から基地局装置を介して5GC110に送られるアップリンクのQoSフローと、DRBとのマッピングを行う機能を持って良い。またSDAPはマッピングルール情報を格納する機能を持って良い。またSDAPはQoSフロー識別子(QoS Flow ID:QFI)のマーキングを行う機能を持って良い。なお、SDAP PDUには、データ用SDAP PDUと制御用SDAP PDUがあって良い。データ用SDAP PDUをSDAP DATA PDU(SDAP Data PDU、SDAPデータPDU)と呼んで良い。また制御用SDAP PDUをSDAP CONTROL PDU(SDAP Control PDU、SDAPコントロールPDU、SDAP制御PDU)と呼んで良い。なお端末装置のSDAPエンティティは、PDUセッションに対して一つ存在して良い。
An example of SDAP functions will be explained. SDAP is the Service Data Adaptation Protocol Layer (Service Data Adaptation Protocol Layer). SDAP is a mapping between a downlink QoS flow and a data radio bearer (DRB) sent from the 5GC 110 to the terminal device via the base station device, and/or from the terminal device via the base station device. It may have the ability to map uplink QoS flows sent to the 5GC 110 to the DRB. SDAP may also have a function to store mapping rule information. SDAP may also have a function for marking QoS flow identifiers (QoS Flow ID: QFI). SDAP PDUs may include SDAP PDUs for data and SDAP PDUs for control. A data SDAP PDU may be called an SDAP DATA PDU. A control SDAP PDU may also be called an SDAP CONTROL PDU. Note that one SDAP entity of the terminal device may exist for each PDU session.
RRCの機能の一例について説明する。RRCは、報知(ブロードキャスト:broadcast)機能を持って良い。RRCは、EPC104及び/又は5GC110からの呼び出し(ページング:Paging)機能を持って良い。RRCは、gNB108又は5GC100に接続するeNB102からの呼び出し(ページング:Paging)機能を持って良い。またRRCは、RRC接続管理機能を持って良い。またRRCは、無線ベアラ制御機能を持って良い。またRRCは、セルグループ制御機能を持って良い。またRRCは、モビリティ(mobility)制御機能を持って良い。またRRCは端末装置測定レポーティング及び端末装置測定レポーティング制御機能を持って良い。またRRCは、QoS管理機能を持って良い。またRRCは、無線リンク失敗の検出及び復旧の機能を持って良い。RRCは、RRCメッセージを用いて、報知、ページング、RRC接続管理、無線ベアラ制御、セルグループ制御、モビリティ制御、端末装置測定レポーティング及び端末装置測定レポーティング制御、QoS管理、無線リンク失敗の検出及び復旧等を行って良い。なお、E-UTRA RRCで用いられるRRCメッセージやパラメータは、NR RRCで用いられるRRCメッセージやパラメータと異なって良い。
I will explain an example of RRC functions. RRC may have a broadcast function. RRC may have a paging function from EPC 104 and/or 5GC 110 . RRC may have paging capabilities from eNB 102 connected to gNB 108 or 5GC 100 . RRC may also have an RRC connection management function. RRC may also have a radio bearer control function. RRC may also have a cell group control function. RRC may also have a mobility control function. RRC may also have terminal measurement reporting and terminal measurement reporting control functions. Also, RRC may have a QoS management function. RRC may also have radio link failure detection and recovery capabilities. RRC uses RRC messages for broadcasting, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal equipment measurement reporting and terminal equipment measurement reporting control, QoS management, radio link failure detection and recovery, etc. good to go Note that the RRC messages and parameters used in E-UTRA RRC may differ from the RRC messages and parameters used in NR RRC.
RRCメッセージは、論理チャネルのBCCHを用いて送られて良いし、論理チャネルのPCCHを用いて送られて良いし、論理チャネルのCCCHを用いて送られて良いし、論理チャネルのDCCHを用いて送られて良い。
The RRC message may be sent using the logical channel's BCCH, may be sent using the logical channel's PCCH, may be sent using the logical channel's CCCH, or may be sent using the logical channel's DCCH. good to be sent
BCCHを用いて送られるRRCメッセージには、例えばマスター情報ブロック(Master Information Block:MIB)が含まれて良いし、各タイプのシステム情報ブロック(System Information Block:SIB)が含まれて良いし、他のRRCメッセージが含まれて良い。PCCHを用いて送られるRRCメッセージには、例えばページングメッセージが含まれて良いし、他のRRCメッセージが含まれて良い。
An RRC message sent using BCCH may include, for example, a Master Information Block (MIB), each type of System Information Block (SIB), and others. Good RRC messages included. RRC messages sent using the PCCH may include, for example, paging messages and may include other RRC messages.
CCCHを用いてアップリンク(UL)方向送られるRRCメッセージには、例えばRRCセットアップ要求メッセージ(RRC Setup Request)、RRC再開要求メッセージ(RRC Resume Request)、RRC再確立要求メッセージ(RRC Reestablishment Request)、RRCシステム情報要求メッセージ(RRC System Info Request)などが含まれて良い。また例えばRRC接続要求メッセージ(RRC Connection Request)、RRCコネクション再開要求メッセージ(RRC Connection Resume Request)、RRC接続再確立要求メッセージ(RRC Connection Reestablishment Request)などが含まれて良い。また他のRRCメッセージが含まれて良い。
RRC messages sent in the uplink (UL) direction using CCCH include, for example, RRC Setup Request, RRC Resume Request, RRC Reestablishment Request, RRC A system information request message (RRC System Info Request) may be included. Also, for example, an RRC Connection Request message, an RRC Connection Resume Request message, an RRC Connection Reestablishment Request message, etc. may be included. Also other RRC messages may be included.
CCCHを用いてダウンリンク(DL)方向送られるRRCメッセージには、例えばRRC接続拒絶メッセージ(RRC Connection Reject)、RRC接続セットアップメッセージ(RRC Connection Setup)、RRCコネクション再確立メッセージ(RRC Connection Reestablishment)、RRCコネクション再確立拒絶メッセージ(RRC Connection Reestablishment Reject)などが含まれて良い。また例えばRRC拒絶メッセージ(RRC Reject)、RRCセットアップメッセージ(RRC Setup)などが含まれて良い。また他のRRCメッセージが含まれて良い。
RRC messages sent in the downlink (DL) direction using CCCH include, for example, RRC Connection Reject, RRC Connection Setup, RRC Connection Reestablishment, RRC A connection re-establishment rejection message (RRC Connection Reestablishment Reject) may be included. Also, for example, an RRC rejection message (RRC Reject), an RRC setup message (RRC Setup), etc. may be included. Also other RRC messages may be included.
DCCHを用いてアップリンク(UL)方向送られるRRCメッセージには、例えば測定報告メッセージ(Measurement Report)、RRCコネクション再設定完了メッセージ(RRC Connection Reconfiguration Complete)、RRC接続セットアップ完了メッセージ(RRC Connection Setup Complete)、RRC接続再確立完了メッセージ(RRC Connection Reestablishment Complete)、セキュリティモード完了メッセージ(Security Mode Complete)、UE能力情報メッセージ(UE Capability Information)などが含まれて良い。また例えば測定報告メッセージ(Measurement Report)、RRC再設定完了メッセージ(RRC Reconfiguration Complete)、RRCセットアップ完了メッセージ(RRC Setup Complete)、RRC再確立完了メッセージ(RRC Reestablishment Complete)、RRC再開完了メッセージ(RRC Resume Complete)、セキュリティモード完了メッセージ(Security Mode Complete)、UE能力情報メッセージ(UE Capability Information)などが含まれて良い。また他のRRCメッセージが含まれて良い。
RRC messages sent in the uplink (UL) direction using DCCH include, for example, a measurement report message, an RRC connection reconfiguration complete message (RRC Connection Reconfiguration Complete), and an RRC connection setup complete message (RRC Connection Setup Complete). , RRC Connection Reestablishment Complete message, Security Mode Complete message, UE Capability Information message, and the like. Also for example Measurement Report message, RRC Reconfiguration Complete message, RRC Setup Complete message, RRC Reestablishment Complete message, RRC Resume Complete message ), Security Mode Complete message, UE Capability Information message, etc. may be included. Also other RRC messages may be included.
DCCHを用いてダウンリンク(DL)方向送られるRRCメッセージには、例えばRRC接続再設定メッセージ(RRC Connection Reconfiguration)、RRC接続解放メッセージ(RRC Connection Release)、セキュリティモードコマンドメッセージ(Security Mode Command)、UE能力照会メッセージ(UE Capability Enquiry)などが含まれて良い。また例えRRC再設定メッセージ(RRC Reconfiguration)、RRC再開メッセージ(RRC Resume)、RRC解放メッセージ(RRC Release)、RRC再確立メッセージ(RRC Reestablishment)、セキュリティモードコマンドメッセージ(Security Mode Command)、UE能力照会メッセージ(UE Capability Enquiry)などが含まれて良い。また他のRRCメッセージが含まれて良い。
RRC messages sent in the downlink (DL) direction using DCCH include, for example, RRC Connection Reconfiguration, RRC Connection Release, Security Mode Command, UE A capability inquiry message (UE Capability Inquiry) may be included. 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. Also other RRC messages may be included.
NASの機能の一例について説明する。NASは、認証機能を持って良い。またNASは、モビリティ(mobility)管理を行う機能を持って良い。またNASは、セキュリティ制御の機能を持って良い。
An example of NAS functions will be explained. NAS may have an authentication function. Also, the NAS may have a function to perform mobility management. Also, the NAS may have a security control function.
前述のPHY、MAC、RLC、PDCP、SDAP、RRC、NASの機能は一例であり、各機能の一部あるいは全てが実装されなくてもよい。また、各層(各レイヤ)の機能の一部あるいは全部が他の層(レイヤ)に含まれてもよい。
The above PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS functions are examples, and some or all of the functions may not be implemented. Also, part or all of the functions of each layer (each layer) may be included in another layer (layer).
次にLTE及びNRにおけるUE122の状態遷移について説明する。EPC、又は5GCに接続するUE122は、RRC接続が設立されている(RRC connection has been established)とき、UE122はRRC_CONNECTED状態であってよい。RRC接続が設立されている状態とは、UE122が、後述のUEコンテキストの一部又は全てを保持している状態を含んで良い。またRRC接続が設立されている状態とは、UE122がユニキャストデータを送信、及び/又は受信できる状態を含んで良い。またUE122は、RRC接続が休止(サスペンド:suspend)しているとき、UE122はRRC_INACTIVE状態であってよい。また、UE122がRRC_INACTIVE状態になるのは、UE122が5GCに接続している場合で、RRC接続が休止しているときであって良い。UE122が、RRC_CONNECTED状態でも、RRC_INACTIVE状態でも無いとき、UE122はRRC_IDLE状態であってよい。
Next, state transitions of UE 122 in LTE and NR will be explained. For UE 122 connecting to EPC or 5GC, when RRC connection has been established, UE 122 may be in RRC_CONNECTED state. A state in which an RRC connection is established may include a state in which the UE 122 holds some or all of the UE contexts described below. Also, states in which an RRC connection is established may include states in which UE 122 is able to transmit and/or receive unicast data. UE 122 may also be in RRC_INACTIVE state when the RRC connection is suspended. Also, the UE 122 may enter the RRC_INACTIVE state when the UE 122 is connected to the 5GC and the RRC connection is dormant. A UE 122 may be in the RRC_IDLE state when the UE 122 is neither in the RRC_CONNECTED state nor in the RRC_INACTIVE state.
なお、UE122がEPCに接続している場合、RRC_INACTIVE状態を持たないが、E-UTRANによってRRC接続の休止が開始されてもよい。UE122がEPCに接続している場合、RRC接続が休止されるとき、UE122はUEのASコンテキストと復帰(リジューム:resume)に用いる識別子(resumeIdentity)を保持してRRC_IDLE状態に遷移して良い。UE122のRRCレイヤの上位レイヤ(例えばNASレイヤ)は、UE122がUEのASコンテキストを保持しており、かつE-UTRANによってRRC接続の復帰が許可(Permit)されており、かつUE122がRRC_IDLE状態からRRC_CONNECTED状態に遷移する必要があるとき、休止されたRRC接続の復帰を開始してもよい。
Note that if UE 122 is connected to EPC, it does not have the RRC_INACTIVE state, but E-UTRAN may initiate dormancy of the RRC connection. If the UE 122 is connected to EPC, when the RRC connection is suspended, the UE 122 may retain the UE's AS context and resumeIdentity and transition to the RRC_IDLE state. A layer higher than the RRC layer of UE 122 (for example, NAS layer) confirms that UE 122 holds the AS context of the UE, and that the E-UTRAN permits recovery of the RRC connection, and that UE 122 exits the RRC_IDLE state. When it needs to transition to the RRC_CONNECTED state, it may initiate the resumption of a dormant RRC connection.
EPC104に接続するUE122と、5GC110に接続するUE122とで、休止の定義が異なってよい。また、UE122がEPCに接続している場合(UE122がRRC_IDLE状態で休止している場合)と、UE122が5GCに接続している場合(UE122がRRC_INACTIVE状態で休止している場合)とで、UE122が休止から復帰する手順のすべてあるいは一部が異なってよい。
The UE 122 connected to the EPC 104 and the UE 122 connected to the 5GC 110 may have different definitions of dormancy. Also, when UE122 is connected to EPC (when UE122 is dormant in RRC_IDLE state) and when UE122 is connected to 5GC (when UE122 is dormant in RRC_INACTIVE state), UE122 all or part of the procedure for waking up from sleep may be different.
なお、RRC_CONNECTED状態、RRC_INACTIVE状態、RRC_IDLE状態の事をそれぞれ、接続状態(connected mode)、不活性状態(inactive mode)、アイドル状態(idle mode)と呼んで良いし、RRC接続状態(RRC connected mode)、RRC不活性状態(RRC inactive mode)、RRCアイドル状態(RRC idle mode)と呼んで良い。
The RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state may be called connected mode, inactive mode, and idle mode, respectively, and RRC connected mode. , RRC inactive mode, and RRC idle mode.
UE122が保持するUEのASコンテキストは、現在のRRC設定、現在のセキュリティコンテキスト、ROHC(RObust Header Compression)状態を含むPDCP状態、接続元(Source)のPCellで使われていたC-RNTI(Cell Radio Network Temporary Identifier)、セル識別子(cellIdentity)、接続元のPCellの物理セル識別子、のすべてあるいは一部を含む情報であってよい。なお、eNB102およびgNB108の内のいずれかまたは全ての保持するUEのASコンテキストは、UE122が保持するUEのASコンテキストと同じ情報を含んでもよいし、UE122が保持するUEのASコンテキストに含まれる情報とは異なる情報が含まれてもよい。
The UE AS context held by UE 122 includes the current RRC settings, current security context, PDCP state including ROHC (RObust Header Compression) state, C-RNTI (Cell Radio Network Temporary Identifier), cell identifier (cellIdentity), and physical cell identifier of the connection source PCell, all or part of which may be information. Note that the UE AS context held by either or all of the eNB 102 and gNB 108 may contain the same information as the UE AS context held by the UE 122, or the information contained in the UE AS context held by the UE 122. may contain different information.
セキュリティコンテキストとは、ASレベルにおける暗号鍵、NH(Next Hop parameter)、次ホップのアクセス鍵導出に用いられるNCC(Next Hop Chaining Counter parameter)、選択されたASレベルの暗号化アルゴリズムの識別子、リプレイ保護のために用いられるカウンター、のすべてあるいは一部を含む情報であってよい。
A security context consists of a cryptographic key at the AS level, NH (Next Hop parameter), NCC (Next Hop Chaining Counter parameter) used to derive the access key for the next hop, an identifier for the selected AS level encryption algorithm, and replay protection. may be information including all or part of the counters used for
端末装置に対し基地局装置から設定される、セルグループ(Cell Group)について説明する。セルグループは、1つのスペシャルセル(Special Cell:SpCell)で構成されて良い。またセルグループは、1つのSpCellと、1つ又は複数のセカンダリセル(Secondary Cell:SCell)から構成されて良い。即ちセルグループは、1つのSpCellと、必要に応じて(optionally)1つ又は複数のSCellから構成されて良い。またセルグループは、セルの集合(set of cell(s))と表現されてよい。なおMACエンティティがマスターセルグループ(Master Cell Group:MCG)に関連付けられている場合、SpCellはプライマリセル(Primary Cell:PCell)を意味して良い。またMACエンティティがセカンダリセルグループ(Secondary Cell Group:SCG)に関連付けられている場合、SpCellはプライマリSCGセル(Primary SCG Cell:PSCell)を意味して良い。またMACエンティティがセルグループに関連付けられていない場合、SpCellはPCellを意味して良い。PCell、PSCellおよびSCellはサービングセルである。SpCellはPUCCH送信およびコンテンション基準ランダムアクセス(contention-based Random Access)をサポートして良いし、またSpCellは常に活性化されても良い。PCellはRRCアイドル状態の端末装置がRRC接続状態に遷移する際の、RRC接続確立手順に用いられるセルであって良い。またPCellは、端末装置がRRC接続の再確立を行う、RRC接続再確立手順に用いられるセルであって良い。またPCellは、ハンドオーバの際のランダムアクセス手順に用いられるセルであって良い。PSCellは、後述するセカンダリノード(Secondary Node:SN)追加の際に、ランダムアクセス手順に用いられるセルであって良い。またSpCellは、上述の用途以外の用途に用いられるセルであって良い。なお、端末装置に対して設定されたセルグループが、SpCell及び1つ以上のSCellから構成されることは、端末装置に対してキャリアアグリゲーション(carrier aggregation:CA)が設定されているとみなされて良い。また、CAが設定されている端末装置に対して、SpCellに対して追加の無線リソースを提供しているセルはSCellを意味して良い。
A cell group that is set by the base station device for the terminal device will be explained. A cell group may consist of one special cell (Special Cell: SpCell). Also, a cell group may consist of one SpCell and one or more Secondary Cells (SCells). That is, a cell group may consist of one SpCell and optionally one or more SCells. A cell group may also be expressed as a set of cell(s). Note that when a MAC entity is associated with a Master Cell Group (MCG), SpCell may mean a Primary Cell (PCell). Also, when the MAC entity is associated with a Secondary Cell Group (SCG), SpCell may mean a Primary SCG Cell (PSCell). SpCell may also mean PCell if the MAC entity is not associated with a cell group. PCell, PSCell and SCell are serving cells. A SpCell may support PUCCH transmission and contention-based Random Access, and may be always activated. A PCell may be a cell used for an RRC connection establishment procedure when a terminal device in the RRC idle state transitions to the RRC connected state. Also, the PCell may be a cell used for the RRC connection re-establishment procedure in which the terminal device re-establishes the RRC connection. Also, the PCell may be a cell used for random access procedures during handover. A PSCell may be a cell used in a random access procedure when adding a secondary node (SN), which will be described later. Also, the SpCell may be a cell that is used for purposes other than those described above. In addition, the fact that a cell group configured for a terminal device is composed of an SpCell and one or more SCells is regarded as a carrier aggregation (CA) configured for the terminal device. good. Also, a cell that provides an additional radio resource to a SpCell for a terminal device in which CA is configured may mean an SCell.
RRCによって設定されているサービングセルのグループで、その中の上りリンクが設定されているセルに対し同じタイミング参照セル(timing reference cell)および同じタイミングアドバンスの値を使用しているセルグループの事をタイミングアドバンスグループ(Timing Advance Group:TAG)と呼んで良い。またMACエンティティのSpCellを含むTAGはプライマリタイミングアドバンスグループ(Primary Timing Advance Group:PTAG)を意味して良い。また上記PTAG以外のTAGはセカンダリタイミングアドバンスグループ(Secondary Timing Advance Group:STAG)を意味して良い。
A group of serving cells configured by RRC that uses the same timing reference cell and the same timing advance value for the cells in which uplink is configured. You can call it the Advance Group (Timing Advance Group: TAG). Also, the TAG containing the SpCell of the MAC entity may mean the Primary Timing Advance Group (PTAG). Also, TAGs other than the above PTAG may mean Secondary Timing Advance Group (STAG).
またDual Connectivity(DC)や、Multi-Radio Dual Connectivity(MR-DC)が行われる場合、端末装置に対し基地局装置からセルグループの追加が行われて良い。DCとは、第1の基地局装置(第1のノード)と第2の基地局装置(第2のノード)がそれぞれ構成するセルグループの無線リソースを利用してデータ通信を行う技術であって良い。MR-DCはDCに含まれる技術であって良い。DCを行うために、第1の基地局装置が第2の基地局装置を追加して良い。第1の基地局装置の事をマスターノード(Master Node:MN)と呼んで良い。またマスターノードが構成するセルグループをマスターセルグループ(Master Cell Group:MCG)と呼んで良い。第2の基地局装置の事をセカンダリノード(Secondary Node:SN)と呼んで良い。またセカンダリノードが構成するセルグループをセカンダリセルグループ(Secondary Cell Group:SCG)と呼んで良い。なお、マスターノードとセカンダリノードは同じ基地局装置内に構成されていても良い。
Also, when Dual Connectivity (DC) or Multi-Radio Dual Connectivity (MR-DC) is performed, a cell group may be added to the terminal device from the base station device. DC is a technique of performing data communication using radio resources of cell groups respectively configured by a first base station apparatus (first node) and a second base station apparatus (second node). good. MR-DC can be a technology included in DC. A first base station device can add a second base station device to perform DC. The first base station device may be called a master node (Master Node: MN). Also, a cell group configured by a master node may be called a master cell group (MCG). The second base station device may be called a secondary node (SN). Also, a cell group configured by a secondary node may be called a secondary cell group (SCG). Note that the master node and the secondary node may be configured within the same base station apparatus.
また、DCが設定されていない場合において、端末装置に設定されるセルグループの事をMCGと呼んで良い。また、DCが設定されていない場合において、端末装置に設定されるSpCellはPCellであって良い。
Also, when DC is not set, the cell group set in the terminal device may be called MCG. Also, when DC is not configured, SpCell configured in the terminal device may be PCell.
なお、MR-DCとは、MCGにE-UTRA、SCGにNRを用いたDCを行う技術であって良い。またMR-DCとは、MCGにNR、SCGにE-UTRAを用いたDCを行う技術であっても良い。またMR-DCとは、MCG及びSCGの両方に、NRを用いたDCを行う技術であっても良い。MCGにE-UTRA、SCGにNRを用いるMR-DCの例として、コア網にEPCを用いるEN-DC(E-UTRA-NR Dual Connectivity)があって良いし、コア網に5GCを用いるNGEN-DC(NG-RAN E-UTRA-NR Dual Connectivity)があって良い。またMCGにNR、SCGにE-UTRAを用いるMR-DCの例として、コア網に5GCを用いるNE-DC(NR-E-UTRA Dual Connectivity)があって良い。またMCG及びSCGの両方にNRを用いるMR-DCの例として、コア網に5GCを用いるNR-DC(NR-NR Dual Connectivity)があって良い。
MR-DC may be a technology that performs DC using E-UTRA for MCG and NR for SCG. Also, MR-DC may be a technique of performing DC using NR for MCG and E-UTRA for SCG. Also, MR-DC may be a technique of performing DC using NR for both MCG and SCG. Examples of MR-DC that uses E-UTRA for MCG and NR for SCG include EN-DC (E-UTRA-NR Dual Connectivity) that uses EPC in the core network, and NGEN-DC that uses 5GC in the core network. DC (NG-RAN E-UTRA-NR Dual Connectivity) is good. As an example of MR-DC using NR for MCG and E-UTRA for SCG, NE-DC (NR-E-UTRA Dual Connectivity) using 5GC for the core network may be used. An example of MR-DC using NR for both MCG and SCG may be NR-DC (NR-NR Dual Connectivity) using 5GC for the core network.
なお端末装置において、MACエンティティは各セルグループに対して1つ存在して良い。例えば端末装置にDC又はMR-DCが設定される場合において、MCGに対する1つのMACエンティティ、及びSCGに対する1つのMACエンティティが存在して良い。端末装置におけるMCGに対するMACエンティティは、全ての状態(RRCアイドル状態、RRC接続状態、及びRRC不活性状態など)の端末装置において、常に確立されていて良い。また端末装置におけるSCGに対するMACエンティティは、端末装置にSCGが設定される際、端末装置によってクリエイト(create)されて良い。また端末装置の各セルグループに対するMACエンティティは、端末装置が基地局装置からRRCメッセージを受け取る事により設定が行われて良い。EN-DC、及びNGEN-DCにおいて、MCGに対するMACエンティティはE-UTRA MACエンティティであっても良く、SCGに対するMACエンティティはNR MACエンティティであって良い。また、NE-DCにおいて、MCGに対するMACエンティティはNR MACエンティティであっても良く、SCGに対するMACエンティティはE-UTRA MACエンティティであって良い。またNR-DCにおいて、MCG及びSCGに対するMACエンティティは共にNR MACエンティティであって良い。なお、MACエンティティが各セルグループに対して1つ存在する事を、MACエンティティは各SpCellに対して1つ存在すると言い換えて良い。また、各セルグループに対する1つのMACエンティティを、各SpCellに対する1つのMACエンティティと言い換えて良い。
Note that in the terminal device, one MAC entity may exist for each cell group. For example, when DC or MR-DC is configured in the terminal device, there may be one MAC entity for MCG and one MAC entity for SCG. The MAC entity for the MCG in the terminal may always be established in the terminal in all states (RRC idle, RRC connected, RRC inactive, etc.). Also, the MAC entity for the SCG in the terminal may be created by the terminal when the SCG is configured in the terminal. Also, the MAC entity for each cell group of the terminal device may be set by the terminal device receiving an RRC message from the base station apparatus. In EN-DC and NGEN-DC, the MAC entity for MCG may be the E-UTRA MAC entity and the MAC entity for SCG may be the NR MAC entity. Also, in NE-DC, the MAC entity for MCG may be the NR MAC entity, and the MAC entity for SCG may be the E-UTRA MAC entity. Also, in NR-DC, both MAC entities for MCG and SCG may be NR MAC entities. Note that one MAC entity exists for each cell group can be rephrased as one MAC entity exists for each SpCell. Also, one MAC entity for each cell group can be rephrased as one MAC entity for each SpCell.
無線ベアラについて説明する。E-UTRAのSRBにはSRB0からSRB2が定義されて良いし、これ以外のSRBが定義されて良い。NRのSRBにはSRB0からSRB3が定義されてよいし、これ以外のSRBが定義されて良い。SRB0は、論理チャネルのCCCHを用いて送信、及び/又は受信が行われる、RRCメッセージのためのSRBであってよい。SRB1は、RRCメッセージのため、及びSRB2の確立前のNASメッセージのためのSRBであって良い。SRB1を用いて送信、及び/又は受信が行われるRRCメッセージには、ピギーバックされたNASメッセージが含まれて良い。SRB1を用いて送信、及び/又は受信される全てのRRCメッセージやNASメッセージには、論理チャネルのDCCHが用いられて良い。SRB2は、NASメッセージのため、及び記録測定情報(logged measurement information)を含むRRCメッセージのためのSRBであってよい。SRB2を用いて送信、及び/又は受信される全てのRRCメッセージやNASメッセージには、論理チャネルのDCCHが用いられて良い。また、SRB2はSRB1よりも低い優先度であってよい。SRB3は、端末装置に、EN-DC、NGEN-DC、NR-DCなどが設定されているときの特定のRRCメッセージを送信、及び/又は受信するためのSRBであって良い。SRB3を用いて送信、及び/又は受信される全てのRRCメッセージやNASメッセージには、論理チャネルのDCCHが用いられて良い。また、その他の用途のために他のSRBが用意されてもよい。DRBは、ユーザデータのための無線ベアラであって良い。DRBを用いて送信、及び/又は受信が行われるRRCメッセージには、論理チャネルのDTCHが用いられても良い。
I will explain the radio bearer. SRB0 to SRB2 may be defined as SRBs of E-UTRA, and SRBs other than these may be defined. SRB0 to SRB3 may be defined as SRBs of NR, and SRBs other than these may be defined. SRB0 may be the SRB for RRC messages transmitted and/or received using the CCCH of the logical channel. SRB1 may be the SRB for RRC messages and for NAS messages before the establishment of SRB2. RRC messages sent and/or received using SRB1 can include piggybacked NAS messages. All RRC and NAS messages sent and/or received using SRB1 can use the DCCH of the logical channel. SRB2 may be the SRB for NAS messages and for RRC messages containing logged measurement information. All RRC and NAS messages sent and/or received using SRB2 can use the DCCH of the logical channel. Also, SRB2 may have a lower priority than SRB1. SRB3 may be an SRB for transmitting and/or receiving a specific RRC message when EN-DC, NGEN-DC, NR-DC, etc. are configured in the terminal device. All RRC and NAS messages sent and/or received using SRB3 can use the DCCH of the logical channel. Other SRBs may also be provided for other uses. A DRB may be a radio bearer for user data. Logical channel DTCH may be used for RRC messages transmitted and/or received using DRB.
端末装置における無線ベアラについて説明する。無線ベアラにはRLCベアラが含まれて良い。RLCベアラは1つ又は2つのRLCエンティティと論理チャネルで構成されて良い。RLCベアラにRLCエンティティが2つ存在する場合のRLCエンティティはTM RLCエンティティ、及び/又は単方向UMモードのRLCエンティティにおける、送信RLCエンティティ及び受信RLCエンティティであって良い。SRB0は1つのRLCベアラから構成されて良い。SRB0のRLCベアラはTMのRLCエンティティ、及び論理チャネルから構成されて良い。SRB0は全ての状態(RRCアイドル状態、RRC接続状態、及びRRC不活性状態など)の端末装置において、常に確立されていて良い。SRB1は端末装置がRRCアイドル状態からRRC接続状態に遷移する際、基地局装置から受信するRRCメッセージにより、端末装置に1つ確立及び/又は設定されて良い。SRB1は1つのPDCPエンティティ、及び1つ又は複数のRLCベアラから構成されて良い。SRB1のRLCベアラはAMのRLCエンティティ、及び論理チャネルから構成されて良い。SRB2はASセキュリティが活性化されたRRC接続状態の端末装置が基地局装置から受信するRRCメッセージにより、端末装置に1つ確立及び/又は設定されて良い。SRB2は1つのPDCPエンティティ、及び1つ又は複数のRLCベアラから構成されて良い。SRB2のRLCベアラはAMのRLCエンティティ、及び論理チャネルから構成されて良い。なお、SRB1及びSRB2の基地局装置側のPDCPはマスターノードに置かれて良い。SRB3はEN-DC、又はNGEN-DC、又はNR-DCにおけるセカンダリノードが追加される際、又はセカンダリノードが変更される際に、ASセキュリティが活性化されたRRC接続状態の端末装置が基地局装置から受信するRRCメッセージにより、端末装置に1つ確立及び/又は設定されて良い。SRB3は端末装置とセカンダリノードとの間のダイレクトSRBであって良い。SRB3は1つのPDCPエンティティ、及び1つ又は複数のRLCベアラから構成されて良い。SRB3のRLCベアラはAMのRLCエンティティ、及び論理チャネルから構成されて良い。SRB3の基地局装置側のPDCPはセカンダリノードに置かれて良い。DRBはASセキュリティが活性化されたRRC接続状態の端末装置が基地局装置から受信するRRCメッセージにより、端末装置に1つ又は複数確立及び/又は設定されて良い。DRBは1つのPDCPエンティティ、及び1つ又は複数のRLCベアラから構成されて良い。DRBのRLCベアラはAM又はUMのRLCエンティティ、及び論理チャネルから構成されて良い。
The radio bearer in the terminal device will be explained. Radio bearers can include RLC bearers. An RLC bearer may consist of one or two RLC entities and logical channels. The RLC entity when there are two RLC entities in the RLC bearer can be a TM RLC entity and/or a transmitting RLC entity and a receiving RLC entity in a unidirectional UM mode RLC entity. SRB0 may consist of one RLC bearer. An SRB0 RLC bearer can consist of a TM RLC entity and a logical channel. SRB0 may always be established in the terminal 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 an RRC message received from the base station device when the terminal device transitions from the RRC idle state to the RRC connected state. SRB1 may consist of one PDCP entity and one or more RLC bearers. An SRB1 RLC bearer can consist of an AM RLC entity and a logical channel. One SRB2 may be established and/or configured in the terminal device by an RRC message received from the base station device by the terminal device in the RRC connected state with AS security activated. SRB2 may consist of one PDCP entity and one or more RLC bearers. An SRB2 RLC bearer can consist of an AM RLC entity and a logical channel. Note that the PDCP on the base station device side of SRB1 and SRB2 may be placed in the master node. SRB3 is when a secondary node in EN-DC, NGEN-DC, or NR-DC is added, or when the secondary node is changed, the terminal device in the RRC connection state with AS security activated is the base station. One may be established and/or configured in a terminal device by RRC messages received from the device. SRB3 may be a direct SRB between the terminal device and the secondary node. SRB3 may consist of one PDCP entity and one or more RLC bearers. An SRB3 RLC bearer can consist of an AM RLC entity and a logical channel. The PDCP on the base station device side of SRB3 can be placed in the secondary node. One or more DRBs may be established and/or configured in a terminal device by RRC messages received from the base station device by the terminal device in RRC connected state with AS security activated. A DRB may consist of one PDCP entity and one or more RLC bearers. A DRB RLC bearer may consist of an AM or UM RLC entity and a logical channel.
なお、MR-DCにおいて、マスターノードにPDCPが置かれる無線ベアラの事を、MN終端(ターミネティド:terminated)ベアラと呼んで良い。また、MR-DCにおいて、セカンダリノードにPDCPが置かれる無線ベアラの事を、SN終端(ターミネティド:terminated)ベアラと呼んで良い。なお、MR-DCにおいて、RLCベアラがMCGにのみ存在する無線ベアラの事を、MCGベアラ(MCG bearer)と呼んで良い。また、MR-DCにおいて、RLCベアラがSCGにのみ存在する無線ベアラの事を、SCGベアラ(SCG bearer)と呼んで良い。またDCにおいて、RLCベアラがMCG及びSCG両方に存在する無線ベアラの事を、スプリットベアラ(split bearer)と呼んで良い。
In addition, in MR-DC, the radio bearer in which PDCP is placed in the master node can be called the MN terminated (terminated) bearer. Also, in MR-DC, a radio bearer in which PDCP is placed in a secondary node may be called an SN terminated (terminated) bearer. In MR-DC, a radio bearer in which the RLC bearer exists only in the MCG may be called an MCG bearer. Also, in MR-DC, a radio bearer whose RLC bearer exists only in the SCG may be called an SCG bearer. Also, in DC, a radio bearer in which RLC bearers exist in both MCG and SCG may be called a split bearer.
端末装置にMR-DCが設定される場合、端末装置に確立/及び又は設定されるSRB1及びSRB2のベアラタイプは、MN終端MCGベアラ及び/又はMN終端スプリットベアラであって良い。また端末装置にMR-DCが設定される場合、端末装置に確立/及び又は設定されるSRB3のベアラタイプは、SN終端SCGベアラであって良い。また端末装置にMR-DCが設定される場合、端末装置に確立/及び又は設定されるDRBのベアラタイプは、全てのベアラタイプのうちの何れかであって良い。
When MR-DC is configured in the terminal device, the bearer types of SRB1 and SRB2 established/and configured in the terminal device may be MN-terminated MCG bearers and/or MN-terminated split bearers. Also, when MR-DC is configured in the terminal device, the bearer type of SRB3 established/or configured in the terminal device may be an SN-terminated SCG bearer. Also, when MR-DC is configured in the terminal device, the DRB bearer type established/and configured in the terminal device may be any of all bearer types.
E-UTRAで構成されるセルグループに確立及び/又は設定されるRLCベアラに対し、確立及び/又は設定されるRLCエンティティは、E-UTRA RLCであって良い。またNRで構成されるセルグループに確立及び/又は設定されるRLCベアラに対し、確立及び/又は設定されるRLCエンティティは、NR RLCであって良い。端末装置にEN-DCが設定され場合、MN終端MCGベアラに対し確立及び/又は設定されるPDCPエンティティは、E-UTRA PDCP又はNR PDCPの何れかであって良い。また端末装置にEN-DCが設定される場合、その他のベアラタイプの無線ベアラ、即ちMN終端スプリットベアラ、MN終端SCGベアラ、SN終端MCGベアラ、SN終端スプリットベアラ、及びSN終端SCGベアラ、に対して確立及び/又は設定されるPDCPは、NR PDCPであって良い。また端末装置にNGEN-DC、又はNE-DC、又はNR-DCが設定される場合、全てのベアラタイプにおける無線ベアラに対して確立及び/又は設定されるPDCPエンティティは、NR PDCPであって良い。
For an RLC bearer established and/or configured in a cell group configured with E-UTRA, the RLC entity established and/or configured may be E-UTRA RLC. Also, for an RLC bearer established and/or configured in a cell group configured with NR, the RLC entity to be established and/or configured may be NR RLC. If the terminal is configured with EN-DC, the PDCP entity established and/or configured for the MN-terminated MCG bearer can be either E-UTRA PDCP or NR PDCP. For other bearer type radio bearers, i.e. MN terminated split bearer, MN terminated SCG bearer, SN terminated MCG bearer, SN terminated split bearer and SN terminated SCG bearer, when EN-DC is configured in the terminal equipment. The PDCP established and/or configured by the NR may be the NR PDCP. Also, when NGEN-DC, NE-DC, or NR-DC is configured in the terminal device, the PDCP entity established and/or configured for radio bearers in all bearer types may be NR PDCP. .
なおNRにおいて、端末装置に確立及び/又は設定されるDRBは1つのPDUセッションに紐づけられ良い。端末装置において1つのPDUセッションに対し、1つのSDAPエンティティが確立及び/又は設定されて良い。端末装置に確立及び/又は設定SDAPエンティティ、PDCPエンティティ、RLCエンティティ、及び論理チャネルは、端末装置が基地局装置から受信するRRCメッセージにより確立及び/又は設定されて良い。
In addition, in NR, DRBs established and/or configured in terminal equipment can be associated with one PDU session. One SDAP entity may be established and/or configured for one PDU session in a terminal device. Established and/or Configured in Terminal The SDAP entity, PDCP entity, RLC entity, and logical channels can be established and/or configured by the RRC messages that the terminal receives from the base station.
なお、MR-DCが設定されるか否かに関わらず、マスターノードがeNB102であり、EPC104をコア網とするネットワーク構成を、E-UTRA/EPCと呼んで良い。またマスターノードがeNB102であり、5GC110をコア網とするネットワーク構成を、E-UTRA/5GCと呼んで良い。またマスターノードがgNB108で5GC110をコア網とするネットワーク構成をNR、又はNR/5GCと呼んで良い。MR-DCが設定されない場合において、上述のマスターノードとは、端末装置と通信を行う基地局装置の事を指して良い。
Regardless of whether or not MR-DC is set, a network configuration in which the master node is eNB 102 and EPC 104 is the core network can be called E-UTRA/EPC. A network configuration in which the master node is eNB 102 and 5GC 110 is the core network can 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. When MR-DC is not configured, the above-mentioned master node may refer to a base station apparatus that communicates with terminal apparatuses.
次にLTE及びNRにおけるハンドオーバについて説明する。ハンドオーバとはRRC接続状態のUE122がサービングセルをソースSpCellからターゲットSpCellへ変更する処理であって良い。ハンドオーバは、UE122がeNB102、及び/又はgNB108より、ハンドオーバを指示するRRCメッセージを受信した時に行われて良い。ハンドオーバを指示するRRCメッセージとは、ハンドオーバを指示するパラメータ(例えばMobilityControlInfoという名称の情報要素、又はReconfigurationWithSyncという名称の情報要素)を含むRRCコネクションの再設定に関するメッセージの事であって良い。なお上述のMobilityControlInfoという名称の情報要素の事を、モビリティ制御設定情報要素、又はモビリティ制御設定、又はモビリティ制御情報と言い換えて良い。なお上述のReconfigurationWithSyncという名称の情報要素の事を同期付再設定情報要素、又は同期付再設定と言い換えて良い。またハンドオーバを指示するRRCメッセージとは、他のRATのセルへの移動を示すメッセージ(例えばMobilityFromEUTRACommand、又はMobilityFromNRCommand)の事であって良い。またハンドオーバの事を同期付再設定(reconfiguration with sync)と言い換えて良い。またUE122がハンドオーバを行う事ができる条件に、ASセキュリティが活性化されている時、SRB2が確立されている時、少なくとも一つのDRBが確立している事のうちの一部又は全てを含んで良い。
Next, handover in LTE and NR will be explained. Handover may be the process by which a UE 122 in RRC Connected state changes its serving cell from a source SpCell to a target SpCell. Handover can occur when UE 122 receives an RRC message from eNB 102 and/or gNB 108 indicating a handover. The RRC message instructing handover may be a message regarding reconfiguration of the RRC connection that includes a parameter instructing handover (for example, an information element named MobilityControlInfo or an information element named ReconfigurationWithSync). The information element named MobilityControlInfo described above may be rephrased as a mobility control setting information element, a mobility control setting, or mobility control information. Note that the above information element named ReconfigurationWithSync may be rephrased as a reset information element with synchronization or a reset with synchronization. Also, the RRC message instructing handover may be a message indicating movement to another RAT cell (for example, MobilityFromEUTRACommand or MobilityFromNRCommand). Handover can also be rephrased as reconfiguration with sync. Also, the conditions under which UE 122 can perform handover include some or all of the following: when AS security is activated, when SRB2 is established, and at least one DRB is established. good.
端末装置と基地局装置との間で送受信される、RRCメッセージのフローについて説明する。図4は、本発明の実施の形態に係るRRCにおける、各種設定のための手順(procedure)のフローの一例を示す図である。図4は、基地局装置(eNB102、及び/又はgNB108)から端末装置(UE122)にRRCメッセージが送られる場合のフローの一例である。
Explain the flow of RRC messages that are transmitted and received between the terminal device and the base station device. FIG. 4 is a diagram showing an example flow of procedures for various settings in RRC according to the embodiment of the present invention. FIG. 4 is an example flow when an RRC message is sent from the base station apparatus (eNB 102 and/or gNB 108) to the terminal apparatus (UE 122).
図4において、基地局装置はRRCメッセージを作成する(ステップS400)。基地局装置におけるRRCメッセージの作成は、基地局装置が報知情報(SI:System Information)やページング情報を配信するため行われて良い。また基地局装置におけるRRCメッセージの作成は、基地局装置が特定の端末装置に対して処理を行わせるために行われて良い。特定の端末装置に対して行わせる処理は、例えばセキュリティに関する設定、RRC接続の再設定、異なるRATへのハンドオーバ、RRC接続の休止、RRC接続の解放などの処理を含んで良い。RRC接続の再設定処理には、例えば無線ベアラの制御(確立、変更、解放など)、セルグループの制御(確立、追加、変更、解放など)、メジャメント設定、ハンドオーバ、セキュリティ鍵更新、などの処理が含まれて良い。また基地局装置におけるRRCメッセージの作成は、端末装置から送信されたRRCメッセージへの応答のために行われて良い。端末装置から送信されたRRCメッセージへの応答は、例えばRRCセットアップ要求への応答、RRC再接続要求への応答、RRC再開要求への応答などを含んで良い。RRCメッセージには各種情報通知や設定のための情報(パラメータ)が含まれる。これらのパラメータは、フィールド及び/又は情報要素と呼ばれて良く、ASN.1(Abstract Syntax Notation One)という記述方式を用いて記述されて良い。
In FIG. 4, the base station device creates an RRC message (step S400). The creation of the RRC message in the base station apparatus may be performed in order for the base station apparatus to distribute system information (SI) and paging information. Also, the creation of the RRC message in the base station apparatus may be performed so that the base station apparatus causes a specific terminal apparatus to perform processing. The processing that a particular terminal device is caused to perform may include, for example, security-related configuration, RRC connection reconfiguration, handover to a different RAT, RRC connection suspension, RRC connection release, and the like. RRC connection reset processing includes, for example, radio bearer control (establishment, change, release, etc.), cell group control (establishment, addition, change, release, etc.), measurement setting, handover, security key update, etc. Good to include. Also, the creation of the RRC message in the base station device may be performed in response to the RRC message transmitted from the terminal device. Responses to RRC messages sent from the terminal may include, for example, responses to RRC setup requests, responses to RRC reconnection requests, responses to RRC resume requests, and the like. The RRC message contains information (parameters) for various information notifications and settings. These parameters may be called fields and/or information elements and may be described using the ASN.1 (Abstract Syntax Notation One) notation scheme.
図4において、次に基地局装置は、作成したRRCメッセージを端末装置に送信する(ステップS402)。次に端末装置は受信した上述のRRCメッセージに従って、設定などの処理が必要な場合には処理を行う(ステップS404)。処理を行った端末装置は、基地局装置に対し、応答のためのRRCメッセージを送信して良い(不図示)。
In FIG. 4, the base station device then transmits the created RRC message to the terminal device (step S402). Next, the terminal device performs processing such as setting according to the received RRC message, if necessary (step S404). The terminal device that has performed the processing may transmit an RRC message for response to the base station device (not shown).
RRCメッセージは、上述の例に限らず、他の目的に使われて良い。
RRC messages are not limited to the above examples, and may be used for other purposes.
なおMR-DCにおいて、SCG側の設定(セルグループ設定、無線ベアラ設定、測定設定など)のためのRRCメッセージを、端末装置との間で転送するのに、マスターノード側のRRCが用いられて良い。例えばEN-DC、又はNGEN-DCにおいて、eNB102とUE122との間で送受信されるE-UTRAのRRCメッセージに、NRのRRCメッセージがコンテナの形で含まれて良い。またNE-DCにおいて、gNB108とUE122との間で送受信されるNRのRRCメッセージに、E-UTRAのRRCメッセージがコンテナの形で含まれて良い。SCG側の設定のためのRRCメッセージは、マスターノードとセカンダリノードの間で送受信されて良い。
Note that in MR-DC, RRC on the master node side is used to transfer RRC messages for SCG side settings (cell group settings, radio bearer settings, measurement settings, etc.) to and from terminal devices. good. For example, in EN-DC or NGEN-DC, E-UTRA RRC messages sent and received between eNB 102 and UE 122 may include NR RRC messages in the form of containers. Also, in the NE-DC, NR RRC messages sent and received between the gNB 108 and the UE 122 may include E-UTRA RRC messages in the form of containers. RRC messages for SCG side configuration can be sent and received between the master and secondary nodes.
なお、MR-DCを利用する場合に限らず、eNB102からUE122に送信されるE-UTRA用RRCメッセージに、NR用RRCメッセージが含まれていて良いし、gNB108からUE122に送信されるNR用RRCメッセージに、E-UTRA用RRCメッセージが含まれていて良い。
In addition, not only when using MR-DC, the RRC message for E-UTRA transmitted from eNB 102 to UE 122 may include the RRC message for NR, and the RRC message for NR transmitted from gNB 108 to UE 122 may be included. The message may contain an RRC message for E-UTRA.
RRCコネクションの再設定に関するメッセージに含まれる、パラメータの一例を説明する。図7は、図4において、NRでのRRCコネクションの再設定に関するメッセージに含まれる、セルグループ設定に関するフィールド、及び/又は情報要素を表すASN.1記述の一例である。また図8は、図4において、E-UTRAでのRRCコネクションの再設定に関するメッセージに含まれる、セルグループ設定に関するフィールド、及び/又は情報要素を表すASN.1記述の一例である。図7、図8に限らず、本発明の実施の形態におけるASN.1の例で、<略>及び<中略>とは、ASN.1の表記の一部ではなく、他の情報を省略している事を示す。なお<略>又は<中略>という記載の無い所でも、情報要素が省略されていて良い。なお本発明の実施の形態においてASN.1の例はASN.1表記方法に正しく従ったものではない。本発明の実施の形態においてASN.1の例は、本発明の実施形態におけるRRCメッセージのパラメータの一例を表記したものであり、他の名称や他の表記が用いられて良い。またASN.1の例は、説明が煩雑になることを避けるために、本発明の一形態と密接に関連する主な情報に関する例のみを示す。なお、ASN.1で記述されるパラメータを、フィールド、情報要素等に区別せず、全て情報要素と言う場合がある。また本発明の実施の形態において、RRCメッセージに含まれる、ASN.1で記述されるフィールド、情報要素等は、情報と言い換えられても良く、パラメータと言い換えられても良い。なおRRCコネクションの再設定に関するメッセージとは、NRにおけるRRC再設定メッセージであって良いし、E-UTRAにおけるRRCコネクション再設定メッセージであって良い。
An example of the parameters included in the message regarding RRC connection reconfiguration will be explained. FIG. 7 is an example of ASN.1 description representing fields and/or information elements related to cell group setting included in a message related to RRC connection reconfiguration in NR in FIG. FIG. 8 is an example of ASN.1 description representing fields and/or information elements related to cell group setting included in the message related to RRC connection reconfiguration in E-UTRA in FIG. Not limited to FIGS. 7 and 8, in the examples of ASN.1 in the embodiments of the present invention, <omitted> and <omitted> are not part of the ASN.1 notation, and other information is omitted. indicates that Information elements may be omitted even where there is no description of <omitted> or <omitted>. Note that the ASN.1 example in the embodiment of the present invention does not correctly follow the ASN.1 notation method. In the embodiment of the present invention, the example of ASN.1 represents an example of the parameters of the RRC message in the embodiment of the present invention, and other names and other representations may be used. In addition, the ASN.1 example shows only examples of main information closely related to one aspect of the present invention in order to avoid complicating the explanation. Note that all parameters described in ASN.1 may be referred to as information elements without distinguishing between fields, information elements, and the like. Further, in the embodiment of the present invention, the fields described in ASN.1, information elements, etc. included in the RRC message may be rephrased as information or parameters. Note that the message regarding RRC connection reconfiguration may be an RRC reconfiguration message in NR or an RRC connection reconfiguration message in E-UTRA.
図7においてCellGroupConfigという名称の情報要素は、NRでのMCG又はSCGのセルグループの設定、変更、解放等に使われる情報要素であって良い。CellGroupConfigという名称の情報要素は、後述の同期付再設定情報要素を含んで良い。CellGroupConfigという名称の情報要素を、セルグループ設定情報要素、又はセルグループ設定と言い換えて良い。またCellGroupConfigという名称の情報要素がNRでのSCGのセルグループの設定に使われる場合、このCellGroupConfigという名称の情報要素を、SCG側の設定と言い換えて良い。CellGroupConfigという名称の情報要素に含まれる、SpCellConfigという名称の情報要素は、特別なセル(SpCell)の設定に使われる情報要素であって良い。SpCellConfigという名称の情報要素を、SpCell設定情報要素、又はSpCell設定と言い換えて良い。SpCellConfigという名称の情報要素に含まれる、ReconfigurationWithSyncという名称の情報要素は、同期付再設定を示す情報要素であって良い。ReconfigurationWithSyncという名称の情報要素を、同期付再設定情報要素、又は同期付再設定と言い換えて良い。なおReconfigurationWithSyncという名称の情報要素には、t304で示される後述のタイマーT304の期間のパラメータが含まれる。またReconfigurationWithSyncという名称の情報要素には、RACH-ConfigDedicatedで示されるランダムアクセス手順を行うためのパラメータが含まれて良い。
The information element named CellGroupConfig in FIG. 7 may be an information element used for setting, changing, releasing, etc. of MCG or SCG cell groups in NR. The information element named CellGroupConfig may contain the reconfiguration with synchronization information element described below. The information element named CellGroupConfig may be rephrased as a cell group configuration information element or cell group configuration. In addition, when an information element named CellGroupConfig is used for SCG cell group configuration in NR, this information element named CellGroupConfig can be rephrased as configuration on the SCG side. An information element named SpCellConfig contained in an information element named CellGroupConfig may be an information element used to configure a particular cell (SpCell). The information element named SpCellConfig may be rephrased as SpCell configuration information element or SpCell configuration. An information element named ReconfigurationWithSync included in the information element named SpCellConfig may be an information element indicating reconfiguration with synchronization. The information element named ReconfigurationWithSync may be rephrased as a reconfiguration with synchronization information element or a reconfiguration with synchronization. Note that the information element named ReconfigurationWithSync includes a parameter for the period of a timer T304, which will be described later, indicated by t304. Also, an information element named ReconfigurationWithSync may contain parameters for performing a random access procedure indicated by RACH-ConfigDedicated.
同期付再設定におけるUE122の動作の一例について説明する。受信したセルグループ設定情報要素に同期付再設定を持つSpCell設定が含まれている場合、UE122は、下記(A)及び/又は(B)の一部または全部を実施して良い。
(A)処理(WS)を行う。
(B)もし、SCGを不活性化させるための指示が含まれていなければ、処理(WS-1)を行う。 An example of the operation ofUE 122 in reconfiguration with synchronization will be described. If the received cell group configuration information element includes an SpCell configuration with reconfiguration with synchronization, the UE 122 may perform some or all of (A) and/or (B) below.
(A) Perform processing (WS).
(B) If instructions for inactivating SCG are not included, then treatment (WS-1) is performed.
(A)処理(WS)を行う。
(B)もし、SCGを不活性化させるための指示が含まれていなければ、処理(WS-1)を行う。 An example of the operation of
(A) Perform processing (WS).
(B) If instructions for inactivating SCG are not included, then treatment (WS-1) is performed.
(処理WS-1)
すべてのサスペンドされた無線ベアラを再開(resume)し、すべての無線ベアラのためのSCGにおける送信を、サスペンドされていたら再開する。 (Processing WS-1)
Resume all suspended radio bearers and resume transmission on the SCG for all radio bearers if suspended.
すべてのサスペンドされた無線ベアラを再開(resume)し、すべての無線ベアラのためのSCGにおける送信を、サスペンドされていたら再開する。 (Processing WS-1)
Resume all suspended radio bearers and resume transmission on the SCG for all radio bearers if suspended.
(処理WS)
UE122は、下記(A)から(F)の一部または全部を含む同期付再設定(reconfiguration with sync)を実施(execute)する。
(A)対応するSpCellのためのタイマーT310が走っているなら止める。
(B)対応するSpCellのためのタイマーT312が走っているなら止める。
(C)対応するSpCellのためのタイマーT304を開始する。
(D)ターゲットSpCellのダウンリンクの同期を開始する。
(E)ターゲットSpCellのための特定のBCCHの設定を適用する。
(F)ターゲットSpCellのMIBを取得する。 (processing WS)
TheUE 122 executes reconfiguration with sync including some or all of (A) to (F) below.
(A) Stop timer T310 for the corresponding SpCell if it is running.
(B) Stop timer T312 for the corresponding SpCell if it is running.
(C) Start timer T304 for the corresponding SpCell.
(D) Start downlink synchronization of the target SpCell.
(E) Apply specific BCCH settings for the target SpCell.
(F) Get the MIB of the target SpCell.
UE122は、下記(A)から(F)の一部または全部を含む同期付再設定(reconfiguration with sync)を実施(execute)する。
(A)対応するSpCellのためのタイマーT310が走っているなら止める。
(B)対応するSpCellのためのタイマーT312が走っているなら止める。
(C)対応するSpCellのためのタイマーT304を開始する。
(D)ターゲットSpCellのダウンリンクの同期を開始する。
(E)ターゲットSpCellのための特定のBCCHの設定を適用する。
(F)ターゲットSpCellのMIBを取得する。 (processing WS)
The
(A) Stop timer T310 for the corresponding SpCell if it is running.
(B) Stop timer T312 for the corresponding SpCell if it is running.
(C) Start timer T304 for the corresponding SpCell.
(D) Start downlink synchronization of the target SpCell.
(E) Apply specific BCCH settings for the target SpCell.
(F) Get the MIB of the target SpCell.
なおタイマーT310とは、SpCellにおいて下位レイヤから同期外(out-of-sync)の指示が一定回数連続で受信されると開始するタイマーであって良い。上述の下位レイヤは、物理レイヤであって良い。またタイマーT312とは、メジャメントレポート(measurement report)がトリガされると上述のタイマーT310が走っているなら開始するタイマーであって良い。上述のメジャメントレポートをトリガするためのパラメータは、メジャメント設定に含まれて良い。
Note that the timer T310 may be a timer that starts when an out-of-sync instruction is received from the lower layer in SpCell a certain number of times in succession. The lower layer mentioned above may be the physical layer. Timer T312 may also be a timer that starts, if timer T310 described above is running, when a measurement report is triggered. Parameters for triggering the measurement reports described above can be included in the measurement settings.
なお無線ベアラがサスペンドされているとは、全てのRRCメッセージやNASメッセージが、この無線ベアラを用いて送信、及び/又は受信されない状態のことであって良い。また無線ベアラのためのSCGにおける送信がサスペンドされているとは、全てのRRCメッセージやNASメッセージが、この無線ベアラを用いてSCGにおいて送信、及び/又はSCGにおいて受信されない状態のことであって良い。また、UE122は、MCG及びSCGにおける送信がサスペンドされていない場合、下記(A)から(D)の一部または全部の要因に基づいて、SCGにおける送信をサスペンドして良い。
(A)SCGのための無線リンク失敗を検出
(B)SCGの同期付再設定の失敗
(C)SCGの設定の失敗
(D)SRB3を考慮した、SCG側の下位レイヤ(PDCP)からの完全性チェックの失敗の通知 Note that a radio bearer being suspended may refer to a state in which no RRC message or NAS message is transmitted and/or received using this radio bearer. Also, the suspension of transmission in the SCG for the radio bearer may be a state in which all RRC messages and NAS messages are not transmitted and/or received in the SCG using this radio bearer. . Also, if transmissions in the MCG and SCG are not suspended, theUE 122 may suspend transmission in the SCG based on some or all of the factors (A) to (D) below.
(A) Detection of radio link failure for SCG (B) Failure of reconfiguration with synchronization of SCG (C) Failure of SCG setup (D) Completeness from lower layers (PDCP) on SCG side considering SRB3 Sex check failure notification
(A)SCGのための無線リンク失敗を検出
(B)SCGの同期付再設定の失敗
(C)SCGの設定の失敗
(D)SRB3を考慮した、SCG側の下位レイヤ(PDCP)からの完全性チェックの失敗の通知 Note that a radio bearer being suspended may refer to a state in which no RRC message or NAS message is transmitted and/or received using this radio bearer. Also, the suspension of transmission in the SCG for the radio bearer may be a state in which all RRC messages and NAS messages are not transmitted and/or received in the SCG using this radio bearer. . Also, if transmissions in the MCG and SCG are not suspended, the
(A) Detection of radio link failure for SCG (B) Failure of reconfiguration with synchronization of SCG (C) Failure of SCG setup (D) Completeness from lower layers (PDCP) on SCG side considering SRB3 Sex check failure notification
セルの活性化(Activation)および不活性化(Deactivation)について説明する。デュアルコネクティビティで通信する端末装置において、前述のRRCコネクションの再設定に関するメッセージによって、マスターセルグループ(MCG)の設定とセカンダリセルグループ(SCG)が設定される。各セルグループは、特別なセル(SpCell)とそれ以外の0個以上のセル(セカンダリセル:SCell)とで構成されてよい。MCGのSpCellはPCellとも称する。SCGのSpCellはPSCellとも称する。セルの不活性化は、SpCellには適用されず、SCellに適用されてよい。
Explain the activation and deactivation of cells. In a terminal device that communicates with dual connectivity, a master cell group (MCG) and a secondary cell group (SCG) are set by the above-described message regarding RRC connection reconfiguration. Each cell group may consist of a special cell (SpCell) and zero or more other cells (secondary cells: SCells). SpCell of MCG is also called PCell. SpCell of SCG is also called PSCell. Cell deactivation does not apply to SpCells, but may apply to SCells.
また、セルの不活性化は、PCellには適用されず、PSCellには適用されてもよい。この場合、セルの不活性化は、SpCellとSCellとで異なる処理であってもよい。
Also, cell deactivation may not be applied to PCells, but may be applied to PSCells. In this case, cell deactivation may be performed differently for SpCells and SCells.
セルの活性化および不活性化はセルグループ毎に存在するMACエンティティで処理されてよい。端末装置に設定されたSCellは下記(A)から(C)の一部または全部によって活性化および/または不活性化されてよい。
(A)SCell活性化/不活性化を示すMAC CEの受信
(B)PUCCHが設定されていないSCellごとに設定されるSCell不活性タイマー
(C)端末装置に設定されたSCell毎に設定されているRRCパラメータ(sCellState) Cell activation and deactivation may be handled by a MAC entity that exists for each cell group. The SCell configured in the terminal device may be activated and/or deactivated by some or all of (A) to (C) below.
(A) Reception of MAC CE indicating SCell activation/deactivation (B) SCell inactivity timer set for each SCell in which PUCCH is not set (C) Set for each SCell set in the terminal device RRC parameter (sCellState)
(A)SCell活性化/不活性化を示すMAC CEの受信
(B)PUCCHが設定されていないSCellごとに設定されるSCell不活性タイマー
(C)端末装置に設定されたSCell毎に設定されているRRCパラメータ(sCellState) Cell activation and deactivation may be handled by a MAC entity that exists for each cell group. The SCell configured in the terminal device may be activated and/or deactivated by some or all of (A) to (C) below.
(A) Reception of MAC CE indicating SCell activation/deactivation (B) SCell inactivity timer set for each SCell in which PUCCH is not set (C) Set for each SCell set in the terminal device RRC parameter (sCellState)
具体的には、端末装置のMACエンティティはセルグループに設定されている各SCellに対して以下の処理(AD)をおこなってよい。
Specifically, the MAC entity of the terminal device may perform the following processing (AD) for each SCell set in the cell group.
(処理AD)
もし、SCell設定の際にSCellに設定されているRRCパラメータ(sCellState)がactivatedに設定されている、またはSCellを活性化させるMAC CEを受信した場合、UE122のMACエンティティは処理(AD-1)を行う。そうでなく、もし、SCellを不活性化させるMAC CEを受信した、または、活性状態のSCellにおいてSCell不活性タイマーが満了したら、UE122のMACエンティティは処理(AD-2)を行う。もし、活性状態のSCellのPDCCHによって上りリンクグラントまたは下りリンク割り当てが通知されたら、または、あるサービングセルのPDCCHによって、活性状態のSCellに対する上りリンクグラントまたは下りリンク割り当てが通知されたら、または、設定された上りリンクグラントにおいてMAC PDUが送信された、または、設定された下りリンク割り当てにおいてMAC PDUが受信されたら、UE122のMACエンティティはそのSCellに関連付けられたSCell不活性タイマーを再スタートする。もし、SCellが不活性状態となったら、UE122のMACエンティティは処理(AD-3)を行う。 (processing AD)
If the RRC parameter (sCellState) set in the SCell when setting the SCell is set to activated, or if a MAC CE that activates the SCell is received, the MAC entity ofUE 122 processes (AD-1) I do. Otherwise, if a MAC CE is received to deactivate the SCell or if the SCell inactivity timer expires in an active SCell, the MAC entity of UE 122 performs processing (AD-2). If an uplink grant or downlink allocation for an active SCell is signaled by the PDCCH of an active SCell, or if an uplink grant or downlink allocation for an active SCell is signaled by the PDCCH of a serving cell, or Once a MAC PDU has been sent on a new uplink grant or received on a configured downlink allocation, the MAC entity of UE 122 restarts the SCell inactivity timer associated with that SCell. If the SCell becomes inactive, the MAC entity of UE 122 performs processing (AD-3).
もし、SCell設定の際にSCellに設定されているRRCパラメータ(sCellState)がactivatedに設定されている、またはSCellを活性化させるMAC CEを受信した場合、UE122のMACエンティティは処理(AD-1)を行う。そうでなく、もし、SCellを不活性化させるMAC CEを受信した、または、活性状態のSCellにおいてSCell不活性タイマーが満了したら、UE122のMACエンティティは処理(AD-2)を行う。もし、活性状態のSCellのPDCCHによって上りリンクグラントまたは下りリンク割り当てが通知されたら、または、あるサービングセルのPDCCHによって、活性状態のSCellに対する上りリンクグラントまたは下りリンク割り当てが通知されたら、または、設定された上りリンクグラントにおいてMAC PDUが送信された、または、設定された下りリンク割り当てにおいてMAC PDUが受信されたら、UE122のMACエンティティはそのSCellに関連付けられたSCell不活性タイマーを再スタートする。もし、SCellが不活性状態となったら、UE122のMACエンティティは処理(AD-3)を行う。 (processing AD)
If the RRC parameter (sCellState) set in the SCell when setting the SCell is set to activated, or if a MAC CE that activates the SCell is received, the MAC entity of
(処理AD-1)
もし、NRにおいて、このSCellを活性化させるMAC CEを受信する前にこのSCellが不活性状態であった、またはSCell設定の際にそのSCellに設定されているRRCパラメータ(sCellState)がactivatedに設定されているならば、UE122のMACエンティティは処理(AD-1A)または処理(AD-1B)を行う。
また、UE122のMACエンティティはそのSCellに対応付けられたSCell不活性タイマーをスタート、または(すでにスタートしている場合は)再スタートする。
もし、Active DL BWPが後述の休眠BWP(Dormant BWP)でない場合、UE122のMACエンティティは下記(A)から(B)の一部または全部を実施する。
(A)もしあれば貯蓄された設定(stored configuration)に従って、このSCellに対応付けられている、グラントタイプ1のサスペンドされたすべてのコンフィギュアード上りリンクグラントを(再び)初期化する。
(B)PHRをトリガする。
もし、SCellを活性化させるMAC CEを受信し、そのSCellに対してRRCメッセージで設定されている第1アクティブ下りリンクBWP識別子(firstActiveDownlinkBWP-Id)で示されるBWPが休眠(Dormant)BWPに設定されていない場合、UE122のMACエンティティは処理(AD-1A)を行う。もし、SCellを活性化させるMAC CEを受信し、そのSCellに対してRRCメッセージで設定されている第1アクティブ下りリンクBWP識別子(firstActiveDownlinkBWP-Id)で示されるBWPが休眠(Dormant)BWPに設定されている場合、UE122のMACエンティティは処理(AD-1B)を行う。また、UE122のMACエンティティは下記(A)から(B)の一部または全部を実施する。
(A)RRCメッセージで設定されている第1アクティブ下りリンクBWP識別子(firstActiveDownlinkBWP-Id)で示されるBWPを活性化する
(B)RRCメッセージで設定されている第1アクティブ上りリンクBWP識別子(firstActiveUplinkBWP-Id)で示されるBWPを活性化する (Processing AD-1)
If, in NR, this SCell was in an inactive state before receiving the MAC CE that activates this SCell, or if the RRC parameter (sCellState) set in that SCell when setting up the SCell is set to activated If so, the MAC entity ofUE 122 performs processing (AD-1A) or processing (AD-1B).
The MAC entity ofUE 122 also starts or restarts (if already started) the SCell inactivity timer associated with that SCell.
If the Active DL BWP is not a dormant BWP (Dormant BWP) described later, the MAC entity ofUE 122 performs some or all of (A) to (B) below.
(A) (re)initialize all suspended configured uplink grants ofgrant type 1 associated with this SCell according to the stored configuration, if any;
(B) Trigger PHR.
If a MAC CE for activating a SCell is received, and the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) set in the RRC message for that SCell is set to a dormant BWP. If not, the MAC entity ofUE 122 takes action (AD-1A). If a MAC CE for activating a SCell is received, and the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) set in the RRC message for that SCell is set to a dormant BWP. If so, the MAC entity of UE 122 takes action (AD-1B). Also, the MAC entity of UE 122 implements some or all of (A) to (B) below.
(A) Activate the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) set in the RRC message (B) The first active uplink BWP identifier (firstActiveUplinkBWP-Id) set in the RRC message Activate the BWP indicated by Id)
もし、NRにおいて、このSCellを活性化させるMAC CEを受信する前にこのSCellが不活性状態であった、またはSCell設定の際にそのSCellに設定されているRRCパラメータ(sCellState)がactivatedに設定されているならば、UE122のMACエンティティは処理(AD-1A)または処理(AD-1B)を行う。
また、UE122のMACエンティティはそのSCellに対応付けられたSCell不活性タイマーをスタート、または(すでにスタートしている場合は)再スタートする。
もし、Active DL BWPが後述の休眠BWP(Dormant BWP)でない場合、UE122のMACエンティティは下記(A)から(B)の一部または全部を実施する。
(A)もしあれば貯蓄された設定(stored configuration)に従って、このSCellに対応付けられている、グラントタイプ1のサスペンドされたすべてのコンフィギュアード上りリンクグラントを(再び)初期化する。
(B)PHRをトリガする。
もし、SCellを活性化させるMAC CEを受信し、そのSCellに対してRRCメッセージで設定されている第1アクティブ下りリンクBWP識別子(firstActiveDownlinkBWP-Id)で示されるBWPが休眠(Dormant)BWPに設定されていない場合、UE122のMACエンティティは処理(AD-1A)を行う。もし、SCellを活性化させるMAC CEを受信し、そのSCellに対してRRCメッセージで設定されている第1アクティブ下りリンクBWP識別子(firstActiveDownlinkBWP-Id)で示されるBWPが休眠(Dormant)BWPに設定されている場合、UE122のMACエンティティは処理(AD-1B)を行う。また、UE122のMACエンティティは下記(A)から(B)の一部または全部を実施する。
(A)RRCメッセージで設定されている第1アクティブ下りリンクBWP識別子(firstActiveDownlinkBWP-Id)で示されるBWPを活性化する
(B)RRCメッセージで設定されている第1アクティブ上りリンクBWP識別子(firstActiveUplinkBWP-Id)で示されるBWPを活性化する (Processing AD-1)
If, in NR, this SCell was in an inactive state before receiving the MAC CE that activates this SCell, or if the RRC parameter (sCellState) set in that SCell when setting up the SCell is set to activated If so, the MAC entity of
The MAC entity of
If the Active DL BWP is not a dormant BWP (Dormant BWP) described later, the MAC entity of
(A) (re)initialize all suspended configured uplink grants of
(B) Trigger PHR.
If a MAC CE for activating a SCell is received, and the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) set in the RRC message for that SCell is set to a dormant BWP. If not, the MAC entity of
(A) Activate the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) set in the RRC message (B) The first active uplink BWP identifier (firstActiveUplinkBWP-Id) set in the RRC message Activate the BWP indicated by Id)
(処理AD-1A)
UE122のMACエンティティはSCellを活性状態にして、下記(A)から(E)の一部または全部を含む通常のSCell動作(Operation)を適用(実施)する。
(A)このSCellにおけるサウンディング参照信号(SRS)の送信
(B)このSCellのためのチャネル状態情報(CSI)の報告
(C)このSCellにおけるPDCCHのモニタ
(D)このSCellに対するPDCCHのモニタ(他のサービングセルにおいてこのSCellに対するスケジュールが行われる場合)
(E)もしPUCCHが設定されていれば、このSCellにおけるPUCCH送信 (Processing AD-1A)
The MAC entity ofUE 122 activates the SCell and applies (performs) normal SCell operations including some or all of (A) to (E) below.
(A) Sounding Reference Signal (SRS) transmission for this SCell (B) Channel State Information (CSI) reporting for this SCell (C) PDCCH monitoring for this SCell (D) PDCCH monitoring for this SCell (etc.) (if scheduling for this SCell is done in the serving cell of
(E) If PUCCH is configured, PUCCH transmission on this SCell
UE122のMACエンティティはSCellを活性状態にして、下記(A)から(E)の一部または全部を含む通常のSCell動作(Operation)を適用(実施)する。
(A)このSCellにおけるサウンディング参照信号(SRS)の送信
(B)このSCellのためのチャネル状態情報(CSI)の報告
(C)このSCellにおけるPDCCHのモニタ
(D)このSCellに対するPDCCHのモニタ(他のサービングセルにおいてこのSCellに対するスケジュールが行われる場合)
(E)もしPUCCHが設定されていれば、このSCellにおけるPUCCH送信 (Processing AD-1A)
The MAC entity of
(A) Sounding Reference Signal (SRS) transmission for this SCell (B) Channel State Information (CSI) reporting for this SCell (C) PDCCH monitoring for this SCell (D) PDCCH monitoring for this SCell (etc.) (if scheduling for this SCell is done in the serving cell of
(E) If PUCCH is configured, PUCCH transmission on this SCell
(処理AD-1B)
UE122のMACエンティティはこのサービングセルのBWP不活性タイマーが走っているなら止める。 (Processing AD-1B)
UE 122's MAC entity stops the BWP inactivity timer for this serving cell if it is running.
UE122のMACエンティティはこのサービングセルのBWP不活性タイマーが走っているなら止める。 (Processing AD-1B)
(処理AD-2)
UE122のMACエンティティは下記(A)から(F)の一部または全部を実施する。
(A)このSCellを不活性化する。
(B)このSCellに対応付けられたSCell不活性タイマーを停止する。
(C)このSCellに対応付けられたすべての活性化されたBWPを不活性化する。
(D)このSCellに対応付けられたすべての設定された下りリンク割り当ておよび/またはすべてのグラントタイプ2のコンフィギュアード上りリンクグラントをクリアする。
(E)このSCellに対応付けられたすべてのグラントタイプ1のコンフィギュアード上りリンクグラントをサスペンドする。
(F)このSCellに対応付けられたHARQのバッファをフラッシュする。 (Processing AD-2)
The MAC entity ofUE 122 performs some or all of (A) through (F) below.
(A) Inactivating this SCell.
(B) Stop the SCell inactivity timer associated with this SCell.
(C) Inactivate all activated 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 configured uplink grants ofgrant type 1 associated with this SCell.
(F) Flush the HARQ buffer associated with this SCell.
UE122のMACエンティティは下記(A)から(F)の一部または全部を実施する。
(A)このSCellを不活性化する。
(B)このSCellに対応付けられたSCell不活性タイマーを停止する。
(C)このSCellに対応付けられたすべての活性化されたBWPを不活性化する。
(D)このSCellに対応付けられたすべての設定された下りリンク割り当ておよび/またはすべてのグラントタイプ2のコンフィギュアード上りリンクグラントをクリアする。
(E)このSCellに対応付けられたすべてのグラントタイプ1のコンフィギュアード上りリンクグラントをサスペンドする。
(F)このSCellに対応付けられたHARQのバッファをフラッシュする。 (Processing AD-2)
The MAC entity of
(A) Inactivating this SCell.
(B) Stop the SCell inactivity timer associated with this SCell.
(C) Inactivate all activated 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 configured uplink grants of
(F) Flush the HARQ buffer associated with this SCell.
(処理AD-3)
UE122のMACエンティティは下記(A)から(D)の一部または全部を実施する。
(A)このSCellでSRSを送信しない。
(B)このSCellのためのCSIを報告しない。
(C)このSCellでPUCCH、UL-SCH、および/またはRACHを送信しない。
(D)このSCellのPDCCH、および/またはこのSCellに対するPDCCHのモニタをしない。 (Processing AD-3)
The MAC entity ofUE 122 performs some or all of (A) through (D) below.
(A) Do not transmit SRS on this SCell.
(B) Do not report CSI for this SCell.
(C) Do not transmit PUCCH, UL-SCH and/or RACH on this SCell.
(D) Do not monitor the PDCCH of this SCell and/or the PDCCH for this SCell.
UE122のMACエンティティは下記(A)から(D)の一部または全部を実施する。
(A)このSCellでSRSを送信しない。
(B)このSCellのためのCSIを報告しない。
(C)このSCellでPUCCH、UL-SCH、および/またはRACHを送信しない。
(D)このSCellのPDCCH、および/またはこのSCellに対するPDCCHのモニタをしない。 (Processing AD-3)
The MAC entity of
(A) Do not transmit SRS on this SCell.
(B) Do not report CSI for this SCell.
(C) Do not transmit PUCCH, UL-SCH and/or RACH on this SCell.
(D) Do not monitor the PDCCH of this SCell and/or the PDCCH for this SCell.
上記のように、MACエンティティが処理(AD)を行うことにより、SCellの活性化および不活性化が行われる。
As described above, the SCell is activated and deactivated by the processing (AD) performed by the MAC entity.
また前述のようにSCellが追加される場合に、RRCメッセージによってSCellの初期状態が設定されてもよい。
Also, when the SCell is added as described above, the initial state of the SCell may be set by the RRC message.
ここで、SCell不活性タイマーについて説明する。PUCCHが設定されないSCellに対しては、RRCメッセージによって、SCell不活性タイマーの値(タイマーが満了したとみなされる時間に関する情報)が通知されてよい。例えば、RRCメッセージでSCell不活性タイマーの値として40msを示す情報が通知された場合、上記処理(AD)において、タイマーをスタートまたは再スタートしてからタイマーが停止することなく通知された時間(ここでは40ms)が経過したしたときに、タイマーが満了したとみなされる。また、SCell不活性タイマーは、sCellDeactivationTimerという名称のタイマーであってもよい。
Here, the SCell inactivity timer will be explained. For SCells for which PUCCH is not configured, the value of the SCell inactivity timer (information regarding the time when the timer is considered to have expired) may be notified by the RRC message. For example, when information indicating 40 ms is notified as the value of the SCell inactivity timer in the RRC message, the time notified without stopping the timer after starting or restarting the timer in the above process (AD) (here 40ms) has elapsed, the timer is considered expired. The SCell deactivation timer may also be a timer named sCellDeactivationTimer.
ここで、帯域部分(BWP)について説明する。
Here, the bandwidth part (BWP) will be explained.
BWPはサービングセルの帯域の一部あるいは全部の帯域であってよい。また、BWPはキャリアBWP(Carrier BWP)と呼称されてもよい。端末装置には、1つまたは複数のBWPが設定されてよい。あるBWPは初期セルサーチで検出された同期信号に対応づけられた報知情報に含まれる情報によって設定されてもよい。また、あるBWPは初期セルサーチを行う周波数に対応づけられた周波数帯域幅であってもよい。また、あるBWPはRRCシグナリング(例えばDedicated RRC signaling)で設定されてもよい。また、下りリンクのBWP(DL BWP)と上りリンクのBWP(UL BWP)とが個別に設定されてもよい。また、1つまたは複数の上りリンクのBWPが1つまたは複数の下りリンクのBWPと対応づけられてよい。また、上りリンクのBWPと下りリンクのBWPとの対応づけは既定の対応づけであってもよいし、RRCシグナリング(例えばDedicated RRC signaling)による対応付けでもよいし、物理層のシグナリング(例えば下りリンク制御チャネルで通知される下りリンク制御情報(DCI)による対応付けであってもよいし、それらの組み合わせであってもよい。
The BWP may be part or all of the bandwidth of the serving cell. A BWP may also be called a carrier BWP. A terminal device may be configured with one or more BWPs. A certain BWP may be set by information included in the broadcast information associated with the synchronization signal detected in the initial cell search. Also, a certain BWP may be a frequency bandwidth associated with a frequency for initial cell search. Some BWPs may also be configured with RRC signaling (eg Dedicated RRC signaling). Also, the downlink BWP (DL BWP) and the uplink BWP (UL BWP) may be configured separately. Also, one or more uplink BWPs may be associated with one or more downlink BWPs. Further, the association between the uplink BWP and the downlink BWP may be a default association, may be an association by RRC signaling (for example, Dedicated RRC signaling), or may be associated by physical layer signaling (for example, downlink The association may be based on downlink control information (DCI) notified by a control channel, or a combination thereof.
BWPは連続する物理無線ブロック(PRB:Physical Resource Block)のグループで構成されてよい。また、接続状態の端末装置に対して、各コンポーネントキャリアのBWP(1つまたは複数のBWP)のパラメータが設定されてよい。各コンポーネントキャリアのBWPのパラメータには、(A)サイクリックプレフィックスの種類、(B)サブキャリア間隔、(C)BWPの周波数位置(例えば、BWPの低周波数側の開始位置または中心周波数位置)(周波数位置は例えば、ARFCNが用いられてもよいし、サービングセルの特定のサブキャリアからのオフセットが用いられてもよい。また、オフセットの単位はサブキャリア単位であってもよいし、リソースブロック単位でもよい。また、ARFCNとオフセットの両方が設定されるかもしれない。)、(D)BWPの帯域幅(例えばPRB数)、(E)制御信号のリソース設定情報、(F)SSブロックの中心周波数位置(周波数位置は例えば、ARFCNが用いられてもよいし、サービングセルの特定のサブキャリアからのオフセットが用いられてもよい。また、オフセットの単位はサブキャリア単位であってもよいし、リソースブロック単位でもよい。また、ARFCNとオフセットの両方が設定されるかもしれない。)、の一部あるいは全部が含まれてよい。また、制御信号のリソース設定情報が、少なくともPCellおよび/またはPSCellの一部あるいは全部のBWPの設定に含まれてもよい。
A BWP may consist of a group of consecutive physical radio blocks (PRB: Physical Resource Block). Also, parameters of the BWP (one or more BWPs) of each component carrier may be set for the terminal device in the connected state. The BWP parameters for each component carrier include (A) the type of cyclic prefix, (B) the subcarrier spacing, (C) the frequency position of the BWP (for example, the start position or center frequency position on the low frequency side of the BWP) ( For the frequency position, for example, ARFCN may be used, or an offset from a specific subcarrier of the serving cell may be used.In addition, the offset unit may be a subcarrier unit or a resource block unit. Also, both ARFCN and offset may be set.), (D) BWP bandwidth (e.g. number of PRBs), (E) control signal resource configuration information, (F) SS block center frequency. For the position (frequency position, for example, ARFCN may be used, or an offset from a specific subcarrier of the serving cell may be used.In addition, the offset unit may be a subcarrier unit, or a resource block unit, and both ARFCN and offset may be set.), may be included. Also, the resource configuration information of the control signal may be included in the BWP configuration of at least some or all of the PCell and/or PSCell.
端末装置は、1つまたは複数の設定されたBWPのうち、アクティブなBWP(Active BWP)において送受信をおこなってよい。端末装置に関連付けられている一つのサービングセルに対して設定された1つまたは複数のBWPのうち、ある時間において、最大で1つの上りリンクBWP、および/または最大で1つの下りリンクBWPがアクティブなBWPとなるように設定されてもよい。活性化された下りリンクのBWPをAcitve DL BWPとも称する。活性化された上りリンクBWPをActive UL BWPとも称する。
A terminal device may transmit and receive in an active BWP (Active BWP) out of one or more set BWPs. Among one or more BWPs configured for one serving cell associated with a terminal device, at most one uplink BWP and/or at most one downlink BWP is active at a given time. It may be set to be BWP. The activated downlink BWP is also called Active DL BWP. The activated uplink BWP is also called Active UL BWP.
次にBWPの不活性化について説明する。1つのサービングセルにおいて、1つまたは複数のBWPが設定されてよい。サービングセルにおけるBWP切り替え(BWP switching)は、不活性化されたBWP(インアクティブ(Inactive)BWPとも称する)を活性化して、活性化されていたBWPを不活性化するために用いられる。
Next, I will explain the inactivation of BWP. One or more BWPs may be configured in one serving cell. BWP switching in the serving cell is used to activate deactivated BWPs (also referred to as inactive BWPs) and deactivate activated BWPs.
BWP切り替えは、下りリンク割り当てまたは上りリンクグラントを示すPDCCH、BWP不活性タイマー、RRCシグナリング、またはランダムアクセス手順の開始のためにMACエンティティそれ自身によって制御される。サービングセルのActive BWPは、RRCまたはPDCCHによって示される。
BWP switching is controlled by the MAC entity itself for PDCCH indicating downlink assignment or uplink grant, BWP inactivity timer, RRC signaling, or initiation of random access procedures. Active BWP of the serving cell is indicated by RRC or PDCCH.
次にBWP不活性タイマーについて説明する。BWP不活性タイマーが設定された、活性化されたサービングセル(Activated Serving Cell)の各々に対してMACエンティティは、次の(A)の処理をおこなう。また、BWP不活性タイマーは、bwp-InactivityTimerという名称のタイマーであってもよい。
(A)もしデフォルト下りリンクBWPの識別子(defaultDownlinkBWP-Id)が設定されており、Active DL BWPが識別子(dormantDownlinkBWP-Id)で示されるBWPでない、または、もしデフォルト下りリンクBWPの識別子(defaultDownlinkBWP-Id)が設定されておらず、Active DL BWPがinitialDownlinkBWPでなく、Active DL BWPが識別子(dormantDownlinkBWP-Id)で示されるBWPでないなら、MACエンティティは次の(B)および(D)の処理をおこなう。
(B)もし、Active DL BWPで、下りリンク割り当て(Assignment)または上りリンクグラントを示す、C-RNTIまたはCS-RNTIにアドレスされたPDCCHを受信した、または、もし、Active DL BWPのための、下りリンク割り当てまたは上りリンクグラントを示す、C-RNTIまたはCS-RNTIにアドレスされたPDCCHを受信した、または、もし、コンフィギュアード上りリンクグラントでMAC PDUが送信された、またはコンフィギュアード下りリンク割り当てでMAC PDUが受信されたなら、MACエンティティは次の(C)の処理をおこなう。
(C)もし、このサービングセルに関連付けられたランダムアクセス手順が実行中でない、または、このサービングセルに関連付けられた実行中のランダムアクセス手順が、C-RNTIにアドレスされたPDCCHの受信によって成功裏に完了(Successfully completed)したら、Active DL BWPに関連付けられたBWP不活性タイマーをスタートまたは再スタートする。
(D)もし、Active DL BWPに関連付けられたBWP不活性タイマーが満了(Expire)したら、MACエンティティは次の(E)の処理をおこなう。
(E)もし、defaultDownlinkBWP-Idが設定されていたら、このdefaultDownlinkBWP-Idで示されるBWPにBWP切り替えをおこない、そうでないなら、initialDownlinkBWPにBWP切り替えをおこなう。 Next, the BWP inactivity timer will be described. The MAC entity performs the following processing (A) for each activated serving cell for which the BWP inactivity timer is set. The BWP inactivity timer may also be a timer named bwp-InactivityTimer.
(A) If the default downlink BWP identifier (defaultDownlinkBWP-Id) is configured and the Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), or if the default downlink BWP identifier (defaultDownlinkBWP-Id ) is not set, the Active DL BWP is not the initialDownlinkBWP, and the Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), the MAC entity performs the following processing (B) and (D).
(B) if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received in Active DL BWP, or if for Active DL BWP, Received PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant or if MAC PDU was sent with configured uplink grant or configured downlink If a MAC PDU is received for assignment, the MAC entity performs the following (C).
(C) if no random access procedure associated with this serving cell is in progress, or an ongoing random access procedure associated with this serving cell is successfully completed upon receipt of a PDCCH addressed to C-RNTI; Once (Successfully completed), start or restart the BWP inactivity timer associated with the Active DL BWP.
(D) If the BWP inactivity timer associated with the Active DL BWP expires, the MAC entity performs the following (E).
(E) If defaultDownlinkBWP-Id is set, perform BWP switching to the BWP indicated by this defaultDownlinkBWP-Id; otherwise, perform BWP switching to initialDownlinkBWP.
(A)もしデフォルト下りリンクBWPの識別子(defaultDownlinkBWP-Id)が設定されており、Active DL BWPが識別子(dormantDownlinkBWP-Id)で示されるBWPでない、または、もしデフォルト下りリンクBWPの識別子(defaultDownlinkBWP-Id)が設定されておらず、Active DL BWPがinitialDownlinkBWPでなく、Active DL BWPが識別子(dormantDownlinkBWP-Id)で示されるBWPでないなら、MACエンティティは次の(B)および(D)の処理をおこなう。
(B)もし、Active DL BWPで、下りリンク割り当て(Assignment)または上りリンクグラントを示す、C-RNTIまたはCS-RNTIにアドレスされたPDCCHを受信した、または、もし、Active DL BWPのための、下りリンク割り当てまたは上りリンクグラントを示す、C-RNTIまたはCS-RNTIにアドレスされたPDCCHを受信した、または、もし、コンフィギュアード上りリンクグラントでMAC PDUが送信された、またはコンフィギュアード下りリンク割り当てでMAC PDUが受信されたなら、MACエンティティは次の(C)の処理をおこなう。
(C)もし、このサービングセルに関連付けられたランダムアクセス手順が実行中でない、または、このサービングセルに関連付けられた実行中のランダムアクセス手順が、C-RNTIにアドレスされたPDCCHの受信によって成功裏に完了(Successfully completed)したら、Active DL BWPに関連付けられたBWP不活性タイマーをスタートまたは再スタートする。
(D)もし、Active DL BWPに関連付けられたBWP不活性タイマーが満了(Expire)したら、MACエンティティは次の(E)の処理をおこなう。
(E)もし、defaultDownlinkBWP-Idが設定されていたら、このdefaultDownlinkBWP-Idで示されるBWPにBWP切り替えをおこない、そうでないなら、initialDownlinkBWPにBWP切り替えをおこなう。 Next, the BWP inactivity timer will be described. The MAC entity performs the following processing (A) for each activated serving cell for which the BWP inactivity timer is set. The BWP inactivity timer may also be a timer named bwp-InactivityTimer.
(A) If the default downlink BWP identifier (defaultDownlinkBWP-Id) is configured and the Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), or if the default downlink BWP identifier (defaultDownlinkBWP-Id ) is not set, the Active DL BWP is not the initialDownlinkBWP, and the Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), the MAC entity performs the following processing (B) and (D).
(B) if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received in Active DL BWP, or if for Active DL BWP, Received PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant or if MAC PDU was sent with configured uplink grant or configured downlink If a MAC PDU is received for assignment, the MAC entity performs the following (C).
(C) if no random access procedure associated with this serving cell is in progress, or an ongoing random access procedure associated with this serving cell is successfully completed upon receipt of a PDCCH addressed to C-RNTI; Once (Successfully completed), start or restart the BWP inactivity timer associated with the Active DL BWP.
(D) If the BWP inactivity timer associated with the Active DL BWP expires, the MAC entity performs the following (E).
(E) If defaultDownlinkBWP-Id is set, perform BWP switching to the BWP indicated by this defaultDownlinkBWP-Id; otherwise, perform BWP switching to initialDownlinkBWP.
また、MACエンティティは、もし、BWP切り替えのためのPDCCHを受信し、Active DL BWPを切り替えたら、次の(A)の処理をおこなう。
(A)もしデフォルト下りリンクBWPの識別子(defaultDownlinkBWP-Id)が設定されており、切り替えたActive DL BWPが識別子(dormantDownlinkBWP-Id)で示されるBWPでない、かつ、もし切り替えたActive DL BWPがdormantDownlinkBWP-Idで示されるBWPでないなら、Active DL BWPに関連付けられたBWP不活性タイマーをスタートまたは再スタートする。 Also, if the MAC entity receives the PDCCH for BWP switching and switches the Active DL BWP, it performs the following processing (A).
(A) If the default downlink BWP identifier (defaultDownlinkBWP-Id) is set, the switched Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), and if the switched Active DL BWP is dormantDownlinkBWP- If not the BWP indicated by Id, start or restart the BWP inactivity timer associated with the Active DL BWP.
(A)もしデフォルト下りリンクBWPの識別子(defaultDownlinkBWP-Id)が設定されており、切り替えたActive DL BWPが識別子(dormantDownlinkBWP-Id)で示されるBWPでない、かつ、もし切り替えたActive DL BWPがdormantDownlinkBWP-Idで示されるBWPでないなら、Active DL BWPに関連付けられたBWP不活性タイマーをスタートまたは再スタートする。 Also, if the MAC entity receives the PDCCH for BWP switching and switches the Active DL BWP, it performs the following processing (A).
(A) If the default downlink BWP identifier (defaultDownlinkBWP-Id) is set, the switched Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), and if the switched Active DL BWP is dormantDownlinkBWP- If not the BWP indicated by Id, start or restart the BWP inactivity timer associated with the Active DL BWP.
次にSCGの不活性化(Deactivation)について説明する。
Next, I will explain the deactivation of SCG.
SCGの不活性化とは、SCGを不活性化することを意味して良い。また、SCGの不活性化とは、MACエンティティがSCGに関連付けられていて、かつ前記MACエンティティに対応するセルグループを不活性化することを意味して良い。SCGの活性化とは、SCGを活性化することを意味して良い。また、SCGの活性化とは、MACエンティティがSCGに関連付けられていて、かつ前記MACエンティティに対応するセルグループを活性化することを意味して良い。
Inactivating the SCG may mean inactivating the SCG. Also, 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. Activation of SCG may mean activation of SCG. Also, activating an SCG may mean activating a cell group in which a MAC entity is associated with the SCG and corresponds to the MAC entity.
LTEおよび/またはNRにおいて、SCGが不活性化されている状態(SCGが休眠している状態)とは、端末装置が、そのSCGのSpCell(PSCell)において下記(A)から(K)の一部または全部を実施する状態であってよい。
(SD-1)
(A)このSpCellでSRSを送信しない。
(B)このSpCellのためのCSIを測定する。
(C)このSpCellのためのCSIを報告しない。
(D)このSpCellでPUCCH、UL-SCH、および/またはRACHを送信しない。
(E)このSpCellのPDCCH、および/またはこのSpCellに対するPDCCHをモニタしない。
(F)このSpCellで間欠受信(DRX)を行う。
(G)このSpCellでのUL-SCH送信のための上りリンクグラントを示すC-RNTI、MCS-C-RNTI、および/またはCS-RNTIにアドレスされた、このSpCellのPDCCH、および/またはこのSpCellに対するPDCCHをモニタしない。
(H)このSpCellでBWPが活性化されており、上述のBWPにおいて上りリンクグラントを示すC-RNTI、MCS-C-RNTI、および/またはCS-RNTIにアドレスされた、このSpCellのPDCCH、および/またはこのSpCellに対するPDCCHをモニタしない。
(I)このSpCellで自動増幅制御(Automatic Gain Control:AGC)、ビーム失敗回復を含むビーム制御(ビームマネジメント)、および/または無線リンクモニタリング(Radio Link
Monitoring:RLM)を行う。
(J)このSpCellに対応付けられている、グラントタイプ1の一部またはすべてのコンフィギュアード上りリンクグラントをサスペンドのままにする。
(K)このSpCellを含むTAG(PTAG)に関連付けられたtimeAlignmentTimer(TAT)を維持する。 In LTE and/or NR, the state in which the SCG is inactivated (the state in which the SCG is dormant) means that the terminal device performs one of the following (A) to (K) in the SCG SpCell (PSCell). It may be in a state of implementing part or all.
(SD-1)
(A) Do not transmit SRS on this SpCell.
(B) Measure CSI for this SpCell.
(C) Do not report CSI for this SpCell.
(D) Do not transmit PUCCH, UL-SCH and/or RACH on this SpCell.
(E) Do not monitor the PDCCH for this SpCell and/or the PDCCH for this SpCell.
(F) Perform discontinuous reception (DRX) in this SpCell.
(G) PDCCH for this SpCell and/or addressed to C-RNTI, MCS-C-RNTI and/or CS-RNTI indicating uplink grant for UL-SCH transmission on this SpCell; Do not monitor PDCCH for
(H) PDCCH for this SpCell with BWP activated and addressed to C-RNTI, MCS-C-RNTI and/or CS-RNTI indicating uplink grant in said BWP; and / Or do not monitor the PDCCH for this SpCell.
(I) Automatic Gain Control (AGC), beam management, including beam failure recovery, and/or radio link monitoring (Radio Link Monitoring) in this SpCell
Monitoring: RLM).
(J) Leave suspended some or all configured uplink grants ofgrant type 1 associated with this SpCell.
(K) Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) containing this SpCell.
(SD-1)
(A)このSpCellでSRSを送信しない。
(B)このSpCellのためのCSIを測定する。
(C)このSpCellのためのCSIを報告しない。
(D)このSpCellでPUCCH、UL-SCH、および/またはRACHを送信しない。
(E)このSpCellのPDCCH、および/またはこのSpCellに対するPDCCHをモニタしない。
(F)このSpCellで間欠受信(DRX)を行う。
(G)このSpCellでのUL-SCH送信のための上りリンクグラントを示すC-RNTI、MCS-C-RNTI、および/またはCS-RNTIにアドレスされた、このSpCellのPDCCH、および/またはこのSpCellに対するPDCCHをモニタしない。
(H)このSpCellでBWPが活性化されており、上述のBWPにおいて上りリンクグラントを示すC-RNTI、MCS-C-RNTI、および/またはCS-RNTIにアドレスされた、このSpCellのPDCCH、および/またはこのSpCellに対するPDCCHをモニタしない。
(I)このSpCellで自動増幅制御(Automatic Gain Control:AGC)、ビーム失敗回復を含むビーム制御(ビームマネジメント)、および/または無線リンクモニタリング(Radio Link
Monitoring:RLM)を行う。
(J)このSpCellに対応付けられている、グラントタイプ1の一部またはすべてのコンフィギュアード上りリンクグラントをサスペンドのままにする。
(K)このSpCellを含むTAG(PTAG)に関連付けられたtimeAlignmentTimer(TAT)を維持する。 In LTE and/or NR, the state in which the SCG is inactivated (the state in which the SCG is dormant) means that the terminal device performs one of the following (A) to (K) in the SCG SpCell (PSCell). It may be in a state of implementing part or all.
(SD-1)
(A) Do not transmit SRS on this SpCell.
(B) Measure CSI for this SpCell.
(C) Do not report CSI for this SpCell.
(D) Do not transmit PUCCH, UL-SCH and/or RACH on this SpCell.
(E) Do not monitor the PDCCH for this SpCell and/or the PDCCH for this SpCell.
(F) Perform discontinuous reception (DRX) in this SpCell.
(G) PDCCH for this SpCell and/or addressed to C-RNTI, MCS-C-RNTI and/or CS-RNTI indicating uplink grant for UL-SCH transmission on this SpCell; Do not monitor PDCCH for
(H) PDCCH for this SpCell with BWP activated and addressed to C-RNTI, MCS-C-RNTI and/or CS-RNTI indicating uplink grant in said BWP; and / Or do not monitor the PDCCH for this SpCell.
(I) Automatic Gain Control (AGC), beam management, including beam failure recovery, and/or radio link monitoring (Radio Link Monitoring) in this SpCell
Monitoring: RLM).
(J) Leave suspended some or all configured uplink grants of
(K) Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) containing this SpCell.
LTEおよび/またはNRにおいて、SCGが活性化されている状態(SCGが休眠していない状態)とは、端末装置が、そのSCGのSpCell(PSCell)において下記(A)から(K)の一部または全部を実施する状態であってよい。
(SA-1)
(A)このSpCellでSRSを送信する。
(B)このSpCellのためのCSIを測定する。
(C)このSpCellのためのCSIを報告する。
(D)このSpCellでPUCCH、UL-SCH、および/またはRACHを送信する。
(E)このSpCellのPDCCH、および/またはこのSpCellに対するPDCCHをモニタする。
(F)このSpCellで間欠受信(DRX)を行う。
(G)このSpCellでのUL-SCH送信のための上りリンクグラントを示すC-RNTI、MCS-C-RNTI、および/またはCS-RNTIにアドレスされた、このSpCellのPDCCH、および/またはこのSpCellに対するPDCCHをモニタする。
(H)このSpCellでBWPが活性化されており、上述のBWPにおいて上りリンクグラントを示すC-RNTI、MCS-C-RNTI、および/またはCS-RNTIにアドレスされた、このSpCellのPDCCH、および/またはこのSpCellに対するPDCCHをモニタする。
(I)このSpCellで自動増幅制御(Automatic Gain Control:AGC)、ビーム失敗回復を含むビーム制御(ビームマネジメント)、および/または無線リンクモニタリング(Radio Link
Monitoring:RLM)を行う。
(J)このSpCellに対応付けられている、グラントタイプ1の一部またはすべてのコンフィギュアード上りリンクグラントを維持する。
(K)このSpCellを含むTAG(PTAG)に関連付けられたtimeAlignmentTimer(TAT)を維持する。 In LTE and/or NR, the state in which the SCG is activated (the state in which the SCG is not dormant) means that the terminal device performs part of (A) to (K) below in the SCG SpCell (PSCell) Or it may be in a state of implementing all.
(SA-1)
(A) Send SRS on this SpCell.
(B) Measure CSI for this SpCell.
(C) Report CSI for this SpCell.
(D) Transmit PUCCH, UL-SCH and/or RACH on this SpCell.
(E) Monitor the PDCCH for this SpCell and/or the PDCCH for this SpCell.
(F) Perform discontinuous reception (DRX) in this SpCell.
(G) PDCCH for this SpCell and/or addressed to C-RNTI, MCS-C-RNTI and/or CS-RNTI indicating uplink grant for UL-SCH transmission on this SpCell; monitor the PDCCH for
(H) PDCCH for this SpCell with BWP activated and addressed to C-RNTI, MCS-C-RNTI and/or CS-RNTI indicating uplink grant in said BWP; and / Or monitor the PDCCH for this SpCell.
(I) Automatic Gain Control (AGC), beam management, including beam failure recovery, and/or radio link monitoring (Radio Link Monitoring) in this SpCell
Monitoring: RLM).
(J) Maintain some or all configured uplink grants ofgrant type 1 associated with this SpCell.
(K) Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) containing this SpCell.
(SA-1)
(A)このSpCellでSRSを送信する。
(B)このSpCellのためのCSIを測定する。
(C)このSpCellのためのCSIを報告する。
(D)このSpCellでPUCCH、UL-SCH、および/またはRACHを送信する。
(E)このSpCellのPDCCH、および/またはこのSpCellに対するPDCCHをモニタする。
(F)このSpCellで間欠受信(DRX)を行う。
(G)このSpCellでのUL-SCH送信のための上りリンクグラントを示すC-RNTI、MCS-C-RNTI、および/またはCS-RNTIにアドレスされた、このSpCellのPDCCH、および/またはこのSpCellに対するPDCCHをモニタする。
(H)このSpCellでBWPが活性化されており、上述のBWPにおいて上りリンクグラントを示すC-RNTI、MCS-C-RNTI、および/またはCS-RNTIにアドレスされた、このSpCellのPDCCH、および/またはこのSpCellに対するPDCCHをモニタする。
(I)このSpCellで自動増幅制御(Automatic Gain Control:AGC)、ビーム失敗回復を含むビーム制御(ビームマネジメント)、および/または無線リンクモニタリング(Radio Link
Monitoring:RLM)を行う。
(J)このSpCellに対応付けられている、グラントタイプ1の一部またはすべてのコンフィギュアード上りリンクグラントを維持する。
(K)このSpCellを含むTAG(PTAG)に関連付けられたtimeAlignmentTimer(TAT)を維持する。 In LTE and/or NR, the state in which the SCG is activated (the state in which the SCG is not dormant) means that the terminal device performs part of (A) to (K) below in the SCG SpCell (PSCell) Or it may be in a state of implementing all.
(SA-1)
(A) Send SRS on this SpCell.
(B) Measure CSI for this SpCell.
(C) Report CSI for this SpCell.
(D) Transmit PUCCH, UL-SCH and/or RACH on this SpCell.
(E) Monitor the PDCCH for this SpCell and/or the PDCCH for this SpCell.
(F) Perform discontinuous reception (DRX) in this SpCell.
(G) PDCCH for this SpCell and/or addressed to C-RNTI, MCS-C-RNTI and/or CS-RNTI indicating uplink grant for UL-SCH transmission on this SpCell; monitor the PDCCH for
(H) PDCCH for this SpCell with BWP activated and addressed to C-RNTI, MCS-C-RNTI and/or CS-RNTI indicating uplink grant in said BWP; and / Or monitor the PDCCH for this SpCell.
(I) Automatic Gain Control (AGC), beam management, including beam failure recovery, and/or radio link monitoring (Radio Link Monitoring) in this SpCell
Monitoring: RLM).
(J) Maintain some or all configured uplink grants of
(K) Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) containing this SpCell.
LTEおよび/またはNRにおいて、端末装置は、以下の(A)から(H)の一部または全部に基づいて、SCGが不活性状態となることを判断してよい。なお、下記(A)から(F)のメッセージや制御要素は、当該SCG以外のセルグループから端末装置に通知されてもよい。
(SD-2)
(A)SCGの不活性化を指示するRRCメッセージの受信
(B)SCGの不活性化を指示するMAC制御要素の受信
(C)SpCellの不活性化を指示するRRCメッセージの受信
(D)SpCellの不活性化を指示するMAC制御要素の受信
(E)その他のRRCメッセージの受信
(F)その他のMAC制御要素の受信
(G)SCGの不活性タイマーの満了
(H)PSCellの不活性タイマーの満了 In LTE and/or NR, the terminal device may determine that the SCG will be deactivated based on some or all of (A) to (H) below. Note that the messages and control elements (A) to (F) below may be notified to the terminal device from a cell group other than the SCG.
(SD-2)
(A) Reception of RRC message instructing deactivation of SCG (B) Reception of MAC control element instructing deactivation of SCG (C) Reception of RRC message instructing deactivation of SpCell (D) SpCell (E) Receipt of other RRC messages (F) Reception of other MAC control elements (G) Expiration of SCG inactivity timer (H) Expiration of PSCell inactivity timer expiration
(SD-2)
(A)SCGの不活性化を指示するRRCメッセージの受信
(B)SCGの不活性化を指示するMAC制御要素の受信
(C)SpCellの不活性化を指示するRRCメッセージの受信
(D)SpCellの不活性化を指示するMAC制御要素の受信
(E)その他のRRCメッセージの受信
(F)その他のMAC制御要素の受信
(G)SCGの不活性タイマーの満了
(H)PSCellの不活性タイマーの満了 In LTE and/or NR, the terminal device may determine that the SCG will be deactivated based on some or all of (A) to (H) below. Note that the messages and control elements (A) to (F) below may be notified to the terminal device from a cell group other than the SCG.
(SD-2)
(A) Reception of RRC message instructing deactivation of SCG (B) Reception of MAC control element instructing deactivation of SCG (C) Reception of RRC message instructing deactivation of SpCell (D) SpCell (E) Receipt of other RRC messages (F) Reception of other MAC control elements (G) Expiration of SCG inactivity timer (H) Expiration of PSCell inactivity timer expiration
図11は実施の形態の一例を示す図である。図11において、UE122の処理部502は、上記の(SD-2)に基づいてSCGが不活性状態となることを判断する (ステップS1100)。また、UE122の処理部502は、前記判断に基づき、不活性状態における動作を行う(ステップS1102)。
FIG. 11 is a diagram showing an example of an embodiment. In FIG. 11, the processing unit 502 of the UE 122 determines that the SCG becomes inactive based on (SD-2) above (step S1100). Also, the processing unit 502 of the UE 122 operates in the inactive state based on the determination (step S1102).
LTEおよび/またはNRにおいて、端末装置は、以下の(A)から(K)の一部または全部に基づいて、SCGが不活性状態とならないことを判断してよい。なお、下記(A)から(F)のメッセージや制御要素は、当該SCG以外のセルグループから端末装置に通知されてもよい。SCGが不活性状態とならないとは、SCGが活性状態となることであってもよい。
(SA-2)
(A)SCGの活性化を指示するRRCメッセージの受信
(B)SCGの活性化を指示するMAC制御要素の受信
(C)SpCellの活性化を指示するRRCメッセージの受信
(D)SpCellの活性化を指示するMAC制御要素の受信
(E)その他のRRCメッセージの受信
(F)その他のMAC制御要素の受信
(G)SCGの不活性タイマー
(H)PSCellの不活性タイマー
(I)MAC SDUが含まれるMAC PDUを送信するためにトリガされたスケジューリングリクエストに起因するランダムアクセス手順の開始
(J)ランダムアクセス手順の開始
(K)スケジューリングリクエストに起因する(言い換えると、MACエンティティ自身が開始した)ランダムアクセス手順の開始 In LTE and/or NR, the terminal device may determine that the SCG is not deactivated based on some or all of (A) to (K) below. Note that the messages and control elements (A) to (F) below may be notified to the terminal device from a cell group other than the SCG. The fact that the SCG is not in an inactive state may mean that the SCG is in an active state.
(SA-2)
(A) Reception of RRC message instructing activation of SCG (B) Reception of MAC control element instructing activation of SCG (C) Reception of RRC message instructing activation of SpCell (D) Activation of SpCell (E) Receipt of other RRC messages (F) Reception of other MAC Control elements (G) SCG inactivity timer (H) PSCell inactivity timer (I) MAC SDU included (J) Initiation of a random access procedure due to a scheduling request triggered to send a MAC PDU to be sent (K) Random access due to a scheduling request (in other words, initiated by the MAC entity itself) Start of procedure
(SA-2)
(A)SCGの活性化を指示するRRCメッセージの受信
(B)SCGの活性化を指示するMAC制御要素の受信
(C)SpCellの活性化を指示するRRCメッセージの受信
(D)SpCellの活性化を指示するMAC制御要素の受信
(E)その他のRRCメッセージの受信
(F)その他のMAC制御要素の受信
(G)SCGの不活性タイマー
(H)PSCellの不活性タイマー
(I)MAC SDUが含まれるMAC PDUを送信するためにトリガされたスケジューリングリクエストに起因するランダムアクセス手順の開始
(J)ランダムアクセス手順の開始
(K)スケジューリングリクエストに起因する(言い換えると、MACエンティティ自身が開始した)ランダムアクセス手順の開始 In LTE and/or NR, the terminal device may determine that the SCG is not deactivated based on some or all of (A) to (K) below. Note that the messages and control elements (A) to (F) below may be notified to the terminal device from a cell group other than the SCG. The fact that the SCG is not in an inactive state may mean that the SCG is in an active state.
(SA-2)
(A) Reception of RRC message instructing activation of SCG (B) Reception of MAC control element instructing activation of SCG (C) Reception of RRC message instructing activation of SpCell (D) Activation of SpCell (E) Receipt of other RRC messages (F) Reception of other MAC Control elements (G) SCG inactivity timer (H) PSCell inactivity timer (I) MAC SDU included (J) Initiation of a random access procedure due to a scheduling request triggered to send a MAC PDU to be sent (K) Random access due to a scheduling request (in other words, initiated by the MAC entity itself) Start of procedure
図10は実施の形態の一例を示す図である。図10において、UE122の処理部502は、上記の(SA-2)に基づいてSCGが不活性状態とならないことを判断する(ステップS1000)。また、UE122の処理部502は、前記判断に基づき、活性状態における動作を行う(ステップS1002)。
FIG. 10 is a diagram showing an example of an embodiment. In FIG. 10, processing unit 502 of UE 122 determines that the SCG is not inactive based on (SA-2) above (step S1000). Also, the processing unit 502 of the UE 122 operates in the active state based on the determination (step S1002).
SCGの不活性化を実行する端末装置は、当該SCGにおいて、以下の(A)から(F)の一部または全部の処理を実行してよい。
(SD-3)
(A)すべてのSCellを不活性状態とする。
(B)活性状態のSCellに関連付けられたSCell不活性タイマーのすべてが満了したとみなす。
(C)休眠状態のSCellに関連付けられたSCell不活性タイマーのすべてが満了したとみなす。
(D)すべてのSCellに関連付けられたSCell不活性タイマーをスタートまたは再スタートしない。
(E)SCellを活性化させるMAC CEを無視する。例えば、前記処理(AD)において、SCellを活性化させるMAC CEを受信して、かつ、SCGの不活性化を指示されてない(またはSCGの不活性状態でない)場合に、処理(AD-1)を行う。
(F)前記処理(AD-2)を実行する。例えば、前記処理(AD)において、SCGの不活性化を指示された(またはSCGの不活性状態となった)場合に、処理(AD-2)を行う。 A terminal device that performs SCG deactivation may perform some or all of the following processes (A) to (F) in the SCG.
(SD-3)
(A) All SCells are inactivated.
(B) Assume that all of the SCell inactivity timers associated with the active SCell have expired.
(C) Assume that all SCell inactivity timers associated with the dormant SCell have expired.
(D) Do not start or restart the SCell inactivity timers associated with all SCells.
(E) Ignore MAC CEs that activate SCells. For example, in the processing (AD), when MAC CE for activating SCell is received and SCG deactivation is not instructed (or SCG is not inactive), processing (AD-1 )I do.
(F) Execute the above process (AD-2). For example, when SCG is instructed to be inactivated (or SCG becomes inactive) in the processing (AD-2), processing (AD-2) is performed.
(SD-3)
(A)すべてのSCellを不活性状態とする。
(B)活性状態のSCellに関連付けられたSCell不活性タイマーのすべてが満了したとみなす。
(C)休眠状態のSCellに関連付けられたSCell不活性タイマーのすべてが満了したとみなす。
(D)すべてのSCellに関連付けられたSCell不活性タイマーをスタートまたは再スタートしない。
(E)SCellを活性化させるMAC CEを無視する。例えば、前記処理(AD)において、SCellを活性化させるMAC CEを受信して、かつ、SCGの不活性化を指示されてない(またはSCGの不活性状態でない)場合に、処理(AD-1)を行う。
(F)前記処理(AD-2)を実行する。例えば、前記処理(AD)において、SCGの不活性化を指示された(またはSCGの不活性状態となった)場合に、処理(AD-2)を行う。 A terminal device that performs SCG deactivation may perform some or all of the following processes (A) to (F) in the SCG.
(SD-3)
(A) All SCells are inactivated.
(B) Assume that all of the SCell inactivity timers associated with the active SCell have expired.
(C) Assume that all SCell inactivity timers associated with the dormant SCell have expired.
(D) Do not start or restart the SCell inactivity timers associated with all SCells.
(E) Ignore MAC CEs that activate SCells. For example, in the processing (AD), when MAC CE for activating SCell is received and SCG deactivation is not instructed (or SCG is not inactive), processing (AD-1 )I do.
(F) Execute the above process (AD-2). For example, when SCG is instructed to be inactivated (or SCG becomes inactive) in the processing (AD-2), processing (AD-2) is performed.
SCGの活性化を実行する端末装置は、当該SCGにおいて、以下の(A)および/または(B)の処理を実行してよい。
(SA-3)
(A)すべてのSCellを活性状態とするために、処理(AD-1)を実行する。
(B)SCGの活性化をRRCメッセージに基づいて実行する場合、このRRCメッセージに、SpCell(PSCell)に対するランダムアクセスに関するパラメータが含まれるなら、通知されたパラメータに基づき、このSpCellにおいてランダムアクセス手順を開始する。 A terminal device that activates an SCG may perform the following processes (A) and/or (B) in the SCG.
(SA-3)
(A) Execute processing (AD-1) to activate all SCells.
(B) If the activation of the SCG is performed based on the RRC message, if this RRC message contains parameters related to random access to SpCell (PSCell), based on the notified parameters, the random access procedure in this SpCell Start.
(SA-3)
(A)すべてのSCellを活性状態とするために、処理(AD-1)を実行する。
(B)SCGの活性化をRRCメッセージに基づいて実行する場合、このRRCメッセージに、SpCell(PSCell)に対するランダムアクセスに関するパラメータが含まれるなら、通知されたパラメータに基づき、このSpCellにおいてランダムアクセス手順を開始する。 A terminal device that activates an SCG may perform the following processes (A) and/or (B) in the SCG.
(SA-3)
(A) Execute processing (AD-1) to activate all SCells.
(B) If the activation of the SCG is performed based on the RRC message, if this RRC message contains parameters related to random access to SpCell (PSCell), based on the notified parameters, the random access procedure in this SpCell Start.
図9は実施の形態の一例を示す図である。図9において、UE122は、eNB102またはgNB108からSCGを不活性状態(休眠状態)とすることを通知するメッセージ(RRCメッセージ)を受信する(ステップS900)。UE122は、上記通知に基づき、SCGのSpCell(第2のセル)以外のセル(すなわちSCell)の一部または全部を不活性状態となるように制御する(ステップS902)。
FIG. 9 is a diagram showing an example of an embodiment. In FIG. 9, UE 122 receives a message (RRC message) notifying that SCG is to be inactive (dormant state) from eNB 102 or gNB 108 (step S900). Based on the notification, the UE 122 controls some or all of the cells (that is, SCells) other than the SCG SpCell (second cell) to be inactive (step S902).
上記の動作により、SCGを不活性化させる処理において、UE122の送信部504が当該SCGのSCellの状態を不活性状態に変更するためのMAC CEを独立して送信することなく、効率的な状態変更が可能となる。また、SCGの不活性化がRRCメッセージに基づいて実行される場合、従来では、初期状態の設定はRRC層でおこない、状態変更はMAC層でおこなっていたが、上記の動作により、RRC層の指示とMAC層の指示のミスマッチを回避しつつ効率的にSCGの状態変更を行うことができる。
Due to the above operation, in the process of deactivating the SCG, the transmission unit 504 of the UE 122 transmits independently the MAC CE for changing the SCell state of the SCG to the inactive state, and an efficient state change is possible. Further, when deactivation of the SCG is performed based on the RRC message, conventionally, the initial state is set in the RRC layer, and the state change is performed in the MAC layer. It is possible to efficiently change the state of the SCG while avoiding a mismatch between the instruction and the MAC layer instruction.
以上の説明をベースとして、本発明の様々な実施の形態を説明する。なお、以下の説明で省略される各処理については上記で説明した各処理が適用されてよい。
Various embodiments of the present invention will be described based on the above description. In addition, each process demonstrated above may be applied about each process abbreviate|omitted by the following description.
図5は本発明の実施の形態における端末装置(UE122)の構成を示すブロック図である。なお、説明が煩雑になることを避けるために、図5では、本発明の一形態と密接に関連する主な構成部のみを示す。
FIG. 5 is a block diagram showing the configuration of the terminal device (UE 122) according to the embodiment of the present invention. In order to avoid complicating the description, FIG. 5 shows only main components closely related to one embodiment of the present invention.
図5に示すUE122は、基地局装置よりRRCメッセージ等を受信する受信部500、及び受信したメッセージに含まれるパラメータに従って処理を行う処理部502、および基地局装置にRRCメッセージ等を送信する送信部504、から成る。上述の基地局装置とは、eNB102であっても良いし、gNB108であっても良い。また、処理部502には様々な層(例えば、物理層、MAC層、RLC層、PDCP層、SDAP層、RRC層、およびNAS層)の機能の一部または全部が含まれてよい。すなわち、処理部502には、物理層処理部、MAC層処理部、RLC層処理部、PDCP層処理部、SDAP処理部、RRC層処理部、およびNAS層処理部の一部または全てが含まれてよい。
UE 122 shown in FIG. 5 includes a receiving unit 500 that receives an RRC message or the like from a base station device, a processing unit 502 that performs processing according to parameters included in the received message, and a transmitting unit that transmits the RRC message or the like to the base station device. 504, consisting of The base station apparatus described above may be eNB 102 or gNB 108 . Also, processing unit 502 may include some or all of the functionality of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 502 includes part or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP processing unit, RRC layer processing unit, and NAS layer processing unit. you can
図6は本発明の実施の形態における基地局装置の構成を示すブロック図である。なお、説明が煩雑になることを避けるために、図6では、本発明の一形態と密接に関連する主な構成部のみを示す。上述の基地局装置とは、eNB102であっても良いし、gNB108であっても良い。
FIG. 6 is a block diagram showing the configuration of the base station apparatus according to the embodiment of the present invention. In order to avoid complicating the description, FIG. 6 shows only main components closely related to one embodiment of the present invention. The base station apparatus described above may be eNB 102 or gNB 108 .
図6に示す基地局装置は、UE122へRRCメッセージ等を送信する送信部600、及びパラメータを含むRRCメッセージを作成し、UE122に送信する事により、UE122の処理部502に処理を行わせる処理部602、およびUE122からRRCメッセージ等を受信する受信部604から成る。また、処理部602には様々な層(例えば、物理層、MAC層、RLC層、PDCP層、SDAP層、RRC層、およびNAS層)の機能の一部または全部が含まれてよい。すなわち、処理部602には、物理層処理部、MAC層処理部、RLC層処理部、PDCP層処理部、SDAP処理部、RRC層処理部、およびNAS層処理部の一部または全部が含まれてよい。
The base station apparatus shown in FIG. 6 includes a transmission unit 600 that transmits an RRC message and the like to UE 122, and a processing unit that creates an RRC message including parameters and transmits it to UE 122, thereby allowing processing unit 502 of UE 122 to perform processing. 602 and a receiver 604 that receives RRC messages and the like from the UE 122 . Also, processing unit 602 may include some or all of the functionality of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 602 includes part or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP processing unit, RRC layer processing unit, and NAS layer processing unit. you can
図10を用いて本発明の実施の形態における、端末装置の処理の一例を説明する。図10を用いて説明する、本発明の実施の形態の端末装置の処理によって、例えば、端末装置が複数のセルグループのモニタを行わなくてもよいことや、消費電力を削減できるといった効果が期待される。
An example of the processing of the terminal device according to the embodiment of the present invention will be described using FIG. By the processing of the terminal device according to the embodiment of the present invention, which will be described with reference to FIG. 10, for example, the terminal device does not need to monitor a plurality of cell groups and power consumption can be reduced. be done.
図10は本発明の実施の形態における、端末装置の処理の一例を示す図である。UE122の処理部502は、上記の(SA-2)に基づいてSCGが不活性状態とならないことを判断してもよい(ステップS1000)。また、UE122の処理部502は、前記判断に基づき、活性状態における動作を行ってもよい(ステップS1002)。
FIG. 10 is a diagram showing an example of processing of the terminal device according to the embodiment of the present invention. The processing unit 502 of the UE 122 may determine that the SCG will not become inactive based on (SA-2) above (step S1000). Also, the processing unit 502 of the UE 122 may operate in the active state based on the determination (step S1002).
活性状態におけるUE122の動作の一例を説明する。UE122は、活性状態において、あるセルグループのSpCellおよび/または1個以上のSCellのそれぞれにおいて、上記の(SA-1)で示したような処理の一部または全部を実施してよい。
An example of the operation of UE 122 in the active state will be explained. The UE 122, in the active state, may perform part or all of the processing shown in (SA-1) above in each of the SpCells and/or one or more SCells of a certain cell group.
活性状態は、SCGが活性化された状態であってよい。また、上述の活性状態は、SCGが休眠状態から復帰(Resume)した状態であってもよい。また、上述の活性状態は、上述のSCGが休眠状態でない状態であってよい。また、上述の活性状態は、MAC SDUが含まれるMAC PDUを送信するためにトリガされたスケジューリングリクエストに起因するランダムアクセス手順が開始される場合に、不活性状態から遷移する状態であってもよい。また、上述の活性状態は、RRCエンティティから休眠状態からの復帰が指示された場合に、不活性状態から遷移する状態であってもよい。
The active state may be a state in which the SCG is activated. Also, the active state described above may be a state in which the SCG has resumed from a dormant state. Also, the active state described above may be a state in which the SCG described above is not in a dormant state. Also, the active state described above may be the state transitioned from the inactive state when a random access procedure due to a scheduling request triggered to transmit a MAC PDU containing a MAC SDU is initiated. . Further, the active state described above may be a state that transitions from the inactive state when the RRC entity instructs to return from the dormant state.
ステップS1000において、SCGが不活性状態から活性状態への遷移が完了したときにUE122の処理部502が前記遷移を決定してよい。また、SCGが不活性状態から活性状態へ遷移する途中でUE122の処理部502が前記遷移を決定してよい。
In step S1000, the processing unit 502 of the UE 122 may determine the transition when the SCG completes the transition from the inactive state to the active state. Also, the processing unit 502 of the UE 122 may determine the transition while the SCG transitions from the inactive state to the active state.
UE122は、SCGを活性化する情報を受信すると、SCGを不活性状態から活性状態に遷移させてもよい(言い換えると、SCGを活性化してもよい)。また、UE122は、SCGの休眠状態からの復帰(Resume)を指示する情報を受信すると、SCGを不活性状態から活性状態に遷移させてもよい。また、UE122は、SpCellの休眠状態からの復帰を指示する情報を受信すると、SCGを不活性状態から活性状態に遷移させてもよい。また、UE122は、その他の情報を受信すると、SCGを不活性状態から活性状態に遷移させてもよい。また、UE122は、SCGの休眠に関するタイマーに基づいて、SCGを不活性状態から活性状態に遷移させてもよい。また、UE122は、PSCellの休眠に関するタイマーに基づいて、SCGを不活性状態から活性状態に遷移させてもよい。また、UE122は、MAC SDUが含まれるMAC PDUを送信するためにトリガされたスケジューリングリクエストに起因するランダムアクセス手順を開始する場合に、SCGを不活性状態から活性状態に遷移させてもよい。また、UE122は、ランダムアクセス手順を開始する場合に、SCGを不活性状態から活性状態に遷移させてもよい。また、UE122は、スケジューリングリクエストに起因する(言い換えると、MACエンティティ自身が開始した)ランダムアクセス手順を開始する場合に、SCGを不活性状態から活性状態に遷移させてもよい。また、UE122のMACエンティティは、SCGを活性化する指示、休眠SCGからの復帰の指示、SpCellの休眠状態からの復帰の指示、および/またはその他の情報をUE122のRRCエンティティから取得してもよい。また、UE122は、MACエンティティが前記情報をRRCエンティティから取得した後、上記の(SA-2)で示したように、SCGが不活性状態とならないと判断し、SCGを不活性状態から活性状態に遷移させてもよい。UE122は、SCGを不活性状態から活性状態に遷移させる際に、上記の(SA-3)で示したような処理を実行してよい。
Upon receiving information to activate the SCG, the UE 122 may transition the SCG from the inactive state to the active state (in other words, activate the SCG). Also, upon receiving information instructing the SCG to return from the dormant state (Resume), the UE 122 may cause the SCG to transition from the inactive state to the active state. Also, upon receiving information instructing the SpCell to return from the dormant state, the UE 122 may cause the SCG to transition from the inactive state to the active state. UE 122 may also transition the SCG from the inactive state to the active state upon receiving other information. Also, the UE 122 may transition the SCG from the inactive state to the active state based on the SCG dormancy timer. Also, the UE 122 may transition the SCG from the inactive state to the active state based on the PSCell sleep timer. 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 send a MAC PDU containing a MAC SDU. Also, the UE 122 may transition the SCG from the inactive state to the active state when starting the random access procedure. The UE 122 may also transition the SCG from inactive to active when initiating a random access procedure resulting from a scheduling request (in other words, initiated by the MAC entity itself). The MAC entity of UE 122 may also obtain an indication to activate an SCG, an indication to wake from a dormant SCG, an indication to wake SpCell from dormancy, and/or other information from the RRC entity of UE 122. . In addition, after the MAC entity obtains the information from the RRC entity, UE 122 determines that the SCG does not become inactive as shown in (SA-2) above, and changes the SCG from inactive to active. You can transition to The UE 122 may perform the processing shown in (SA-3) above when making the SCG transition from the inactive state to the active state.
図11を用いて本発明の実施の形態における、端末装置の処理の一例を説明する。
An example of the processing of the terminal device according to the embodiment of the present invention will be described using FIG.
図11は本発明の実施の形態における、端末装置の処理の一例を示す図である。UE122の処理部502は、上記の(SD-2)に基づいてSCGが不活性状態となることを判断してもよい(ステップS1100)。また、UE122の処理部502は、前記判断に基づき、不活性状態における動作を行ってもよい(ステップS1102)。
FIG. 11 is a diagram showing an example of processing of the terminal device according to the embodiment of the present invention. The processing unit 502 of the UE 122 may determine that the SCG becomes inactive based on (SD-2) above (step S1100). Also, the processing unit 502 of the UE 122 may operate in the inactive state based on the determination (step S1102).
上述の不活性状態におけるUE122の動作の一例を説明する。不活性状態は、あるセルグループのSpCellおよび/または1個以上のSCellにおいて、UE122が上記の(SD-1)で示したような処理の一部または全部を実施してよい。
An example of the operation of the UE 122 in the inactive state described above will be explained. In the inactive state, UE 122 may perform some or all of the processing as indicated in (SD-1) above in an SpCell and/or one or more SCells of a cell group.
不活性状態は、SCGが不活性化された状態であってよい。また、上述の不活性状態は、休眠SCGへの入場(Entering)であってもよい。また、上述の不活性状態は、上述のSCGの休眠状態であってよい。また、不活性状態は、SCGのSpCellおよび/または1個以上のSCellのActive BWPが休眠BWPである状態であってもよい。また、上述の不活性状態は、MAC SDUが含まれるMAC PDUを送信するためにトリガされたスケジューリングリクエストに起因するランダムアクセス手順が開始される場合に、活性状態から遷移する状態であってもよい。また、上述の不活性状態は、RRCエンティティから休眠状態への入場が指示された場合に、活性状態から遷移する状態であってもよい。
The inactive state may be a state in which the SCG is inactivated. Also, the inactive state described above may be Entering a dormant SCG. Also, the inactive state described above may be the dormant state of the SCG described above. The inactive state may also be a state in which the SpCell of the SCG and/or the Active BWP of one or more SCells are dormant BWPs. Also, the inactive state described above may be a state that transitions from the active state when a random access procedure due to a scheduling request triggered to transmit a MAC PDU containing a MAC SDU is initiated. . Also, the inactive state described above may be a state transitioned from the active state when the RRC entity instructs to enter the dormant state.
ステップS1100において、SCGが活性状態から不活性状態への遷移が完了したときにUE122の処理部502が前記遷移を決定してよい。また、SCGが活性状態から不活性状態へ遷移する途中でUE122の処理部502が前記遷移を決定してよい。
In step S1100, the processing unit 502 of the UE 122 may determine the transition when the SCG completes the transition from the active state to the inactive state. Also, the processing unit 502 of the UE 122 may determine the transition while the SCG transitions from the active state to the inactive state.
UE122は、SCGの不活性化を指示する情報を受信すると、SCGを活性状態から不活性状態に遷移させてもよい。また、UE122は、休眠SCGへの入場(Entering)を指示する情報を受信すると、SCGを活性状態から不活性状態に遷移させてもよい。また、UE122は、SpCellの休眠を指示する情報を受信すると、SCGを活性状態から不活性状態に遷移させてもよい。また、UE122は、その他の情報を受信すると、SCGを活性状態から不活性状態に遷移させてもよい。また、UE122は、SCGの休眠に関するタイマーが満了した場合に、SCGを活性状態から不活性状態に遷移させてもよい。また、UE122は、PSCellの休眠に関するタイマーが満了した場合に、SCGを活性状態から不活性状態に遷移させてもよい。また、UE122のMACエンティティは、SCGを不活性化する指示、休眠SCGへの入場の指示、SpCellの休眠の指示、および/またはその他の情報をUE122のRRCエンティティから取得してもよい。また、UE122は、MACエンティティが前記情報をRRCエンティティから取得した後、上記の(SD-2)で示したように、SCGが不活性状態となると判断し、SCGを活性状態から不活性状態に遷移させてもよい。UE122は、SCGを活性状態から不活性状態に遷移させる際に、上記の(SD-3)で示したような処理を実行してよい。
Upon receiving information instructing deactivation of the SCG, the UE 122 may transition the SCG from the active state to the inactive state. Also, upon receiving information instructing entry into the dormant SCG, the UE 122 may transition the SCG from the active state to the inactive state. Also, upon receiving information instructing SpCell dormancy, the UE 122 may transition the SCG from the active state to the inactive state. UE 122 may also transition the SCG from the active state to the inactive state upon receiving other information. Also, the UE 122 may cause the SCG to transition from the active state to the inactive state when the SCG dormancy timer expires. Also, the UE 122 may transition the SCG from the active state to the inactive state when the PSCell sleep timer expires. The MAC entity of UE 122 may also obtain an indication to deactivate an SCG, an indication to enter a dormant SCG, an indication to dormant SpCells, and/or other information from the RRC entity of UE 122. In addition, after the MAC entity obtains the information from the RRC entity, UE 122 determines that the SCG becomes inactive as shown in (SD-2) above, and changes the SCG from active to inactive state. You can transition. The UE 122 may perform the processing shown in (SD-3) above when making the SCG transition from the active state to the inactive state.
図12を用いて本発明の実施の形態における、端末装置の処理の一例を説明する。
An example of processing of the terminal device according to the embodiment of the present invention will be described using FIG.
図12は本発明の実施の形態における、端末装置の処理の一例を示す図である。UE122の処理部502は、UE122が受信したRRCコネクションの再設定に関するメッセージ内のSCGのSpCell設定情報要素に同期付再設定が含まれるときに(ステップS1200)、同期付再設定を実施してよい(ステップS1202)。またUE122の処理部502は、RRCコネクションの再設定に関するメッセージにSCGを不活性化させる指示が含まれていないときに(ステップS1200)、すべてのサスペンドされた無線ベアラを再開してよいし、すべての無線ベアラのためのSCGにおける送信を、サスペンドされていたら再開してよい。またUE122の処理部502は、RRCコネクションの再設定に関するメッセージにSCGを不活性化させる指示が含まれるときに(ステップS1200)、一部のサスペンドされた無線ベアラを再開せず、一部の無線ベアラのためのSCGにおける送信を再開しなくてよい(ステップS1204)。なお上述のSCGのSpCell設定情報要素は、図7で示される、SCGを設定するCellGroupConfigに含まれるSpCellConfigであってよい。また上述のSCGを不活性化させる指示は、RRCメッセージに含まれてよい。また上述のSCGを不活性化させる指示は、RRCメッセージの種類で識別されるもの(RRCメッセージ自体)であってよい。また上述のSCGを不活性化させる指示は、RRC再設定メッセージの中のセルグループ設定情報要素、又はSpCell設定情報要素に含まれてよい。また上述のSCGを不活性化させる指示は、RRC再設定メッセージの中のセルグループ設定情報要素、又はSpCell設定情報要素以外の情報要素に含まれてよい。なお上述の無線ベアラには、RLCベアラ、及び/又はRLCベアラ以外の無線ベアラが含まれてよい。また上述の無線ベアラには、MCGベアラ、SCGベアラ、スプリットベアラの一部または全部が含まれてよい。
FIG. 12 is a diagram showing an example of processing of the terminal device according to the embodiment of the present invention. The processing unit 502 of the UE 122 may perform reconfiguration with synchronization when the SpCell configuration information element of the SCG in the message regarding reconfiguration of the RRC connection received by the UE 122 includes reconfiguration with synchronization (step S1200). (Step S1202). Also, the processing unit 502 of the UE 122 may resume all suspended radio bearers when the message regarding reconfiguration of the RRC connection does not include an instruction to deactivate the SCG (step S1200). If suspended, transmissions on the SCG for the radio bearers may be resumed. Also, when the message regarding reconfiguration of the RRC connection includes an instruction to deactivate the SCG (step S1200), the processing unit 502 of the UE 122 does not restart some suspended radio bearers, Transmission on the SCG for the bearer may not resume (step S1204). Note that the SpCell configuration information element of the SCG described above may be SpCellConfig included in CellGroupConfig that configures the SCG shown in FIG. Also, an instruction to deactivate the SCG described above may be included in the RRC message. Also, the above-mentioned SCG deactivation instruction may be identified by the type of RRC message (the RRC message itself). Also, the above-mentioned SCG deactivation instruction may be included in the cell group configuration information element or the SpCell configuration information element in the RRC reconfiguration message. Also, the instruction to deactivate the SCG described above may be included in an information element other than the cell group configuration information element or the SpCell configuration information element in the RRC reconfiguration message. Note that the radio bearers described above may include RLC bearers and/or radio bearers other than RLC bearers. Also, the above-mentioned radio bearers may include some or all of MCG bearers, SCG bearers, and split bearers.
ステップS1202における同期付再設定の処理の一例を説明する。ステップS1200においてUE122が受信したRRCコネクションの再設定に関するメッセージに同期付再設定が含まれる場合、UE122は、同期付再設定を実施する際に、上記の(WS)で示したような処理を実行してよい。
An example of the process of resetting with synchronization in step S1202 will be described. If the message regarding RRC connection reconfiguration received by UE 122 in step S1200 includes reconfiguration with synchronization, UE 122 performs the processing shown in (WS) above when performing reconfiguration with synchronization. You can
ステップS1204における無線ベアラの処理の一例を説明する。ステップS1200においてUE122が受信したRRCコネクションの再設定に関するメッセージにSCGを不活性化させる指示が含まれていた場合、UE122の処理部502は、一部又は全部のサスペンドされた無線ベアラを再開せず、一部又は全部の無線ベアラのためのSCGにおける送信を再開しなくてよい。また、ステップS1200においてUE122が受信したRRCコネクションの再設定に関するメッセージにSCGを不活性化させる指示が含まれていた場合、UE122の処理部502は、一部又は全部のサスペンドされた無線ベアラを再開せず、すべての無線ベアラのためのSCGにおける送信を、サスペンドされていたら再開してよい。また、ステップS1200においてUE122が受信したRRCコネクションの再設定に関するメッセージにSCGを不活性化させる指示が含まれていた場合、UE122の処理部502は、すべてのサスペンドされた無線ベアラを再開し、一部又は全部の無線ベアラのためのSCGにおける送信を再開しなくてよい。ステップS1200においてUE122が受信したRRCコネクションの再設定に関するメッセージにSCGを不活性化させる指示が含まれていない場合、UE122の処理部502は、すべてのサスペンドされた無線ベアラを再開し、すべての無線ベアラのためのSCGにおける送信を、サスペンドされていたら再開してよい。なお無線ベアラのサスペンド及び/又は再開は、セルグループ毎に実施されてよいし、セルグループに関係なく実施されてもよい。また無線ベアラのためのSCGにおける送信のサスペンド及び/又は再開は、セルグループ毎に実施されてよいし、セルグループに関係なく実施されてもよい。
An example of radio bearer processing in step S1204 will be described. If the message regarding reconfiguration of the RRC connection received by UE 122 in step S1200 includes an instruction to deactivate the SCG, the processing unit 502 of UE 122 does not restart some or all of the suspended radio bearers. , may not restart transmissions on the SCG for some or all radio bearers. Further, when the message regarding reconfiguration of the RRC connection received by UE 122 in step S1200 includes an instruction to deactivate the SCG, the processing unit 502 of UE 122 resumes some or all of the suspended radio bearers. and may resume transmission on the SCG for all radio bearers if suspended. Also, if the message regarding reconfiguration of the RRC connection received by UE 122 in step S1200 includes an instruction to deactivate the SCG, processing unit 502 of UE 122 resumes all suspended radio bearers, Transmission on the SCG for some or all radio bearers may not be restarted. If the message regarding reconfiguration of the RRC connection received by UE 122 in step S1200 does not contain an instruction to deactivate the SCG, processing unit 502 of UE 122 resumes all suspended radio bearers, and resumes all radio bearers. Transmission on the SCG for the bearer may be resumed if suspended. Note that the suspension and/or resumption of radio bearers may be performed for each cell group, or may be performed regardless of the cell group. Also, suspension and/or resumption of transmission in the SCG for radio bearers may be performed for each cell group, or may be performed regardless of the cell group.
このように、本発明の実施の形態では、SCGの不活性状態においても必要な上りリンクの送信をトリガすることができる。また、SCGの不活性状態において、必要な信号のみをモニタすることで省電力化が可能となる。
Thus, according to the embodiment of the present invention, it is possible to trigger the necessary uplink transmission even in the inactive state of the SCG. In addition, power can be saved by monitoring only necessary signals while the SCG is inactive.
上記説明における無線ベアラは其々、DRBであって良いし、SRBであって良いし、DRB及びSRBであって良い。
The radio bearers in the above description may be DRB, SRB, or both DRB and SRB.
また上記説明において、「紐づける」、「対応付ける」、「関連付ける」等の表現は、互いに換言されてもよい。
Also, in the above description, expressions such as "associate", "associate", and "associate" may be replaced with each other.
また上記説明において、「含まれる」、「含まれている」、「含まれていた」等の表現は、互いに換言されてもよい。
Also, in the above description, expressions such as "included", "contained", and "was included" may be exchanged for each other.
また上記説明において、「前記~」を「上述の~」と言い換えてよい。
Also, in the above explanation, "the above-mentioned" may be replaced with "the above-mentioned".
また上記説明において、「SCGのSpCell」を「PSCell」と言い換えてよい。
Also, in the above explanation, "SCG SpCell" may be replaced with "PSCell".
また上記説明において、「~と確定した」、「~が設定されている」、「~が含まれる」等の表現は、互いに換言されてもよい。
Also, in the above description, expressions such as "determined as", "set with", and "including" may be exchanged for each other.
上記説明において、「休眠状態」を「不活性状態」と言い換えてよいし、「休眠状態から復帰した状態」を「活性状態」と言い換えてもよい。また上記説明において、「活性化」、「不活性化」をそれぞれ「活性状態」、「不活性状態」と言い換えてもよい。
In the above description, the "dormant state" may be replaced with the "inactive state", and the "state recovered from the dormant state" may be replaced with the "active state". In the above description, "activation" and "inactivation" may be replaced with "active state" and "inactive state", respectively.
上記説明において、「XからYに遷移する」を「XからYとなる」と言い換えてよい。また上記説明において、「遷移させる」を「遷移を決定する」と言い換えてよい。また、「活性化されたBWP」を「Active BWP」と言い換えてもよい。
In the above explanation, "transition from X to Y" can be rephrased as "transition from X to Y". Moreover, in the above description, "make a transition" may be rephrased as "determine a transition". Also, "activated BWP" may be replaced with "Active BWP".
また上記説明における各処理の例、又は各処理のフローの例において、ステップの一部または全ては実行されなくても良い。また上記説明における各処理の例、又は各処理のフローの例において、ステップの順番は異なっても良い。また上記説明における各処理の例、又は各処理のフローの例において、各ステップ内の一部または全ての処理は実行されなくても良い。また上記説明における各処理の例、又は各処理のフローの例において、各ステップ内の処理の順番は異なっても良い。また上記説明において「Aである事に基づいてBを行う」は、「Bを行う」と言い換えられても良い。即ち「Bを行う」事は「Aである事」と独立して実行されても良い。
Also, in the example of each process or the example of the flow of each process in the above description, some or all of the steps may not be executed. In addition, the order of the steps may be different in the example of each process or the example of the flow of each process in the above description. Also, in the examples of each process or the example of the flow of each process in the above description, some or all of the processes in each step may not be executed. Further, in the example of each process or the example of the flow of each process in the above description, the order of the processes in each step may be different. Also, in the above description, "perform B based on A" may be rephrased as "perform B." That is, "doing B" may be performed independently of "being A".
なお、上記説明において、「AをBと言い換えてよい」は、AをBと言い換えることに加え、BをAと言い換える意味も含んでよい。また上記説明において、「CはDであって良い」と「CはEであって良い」とが記載されている場合には、「DはEであって良い」事を含んでも良い。また上記説明において、「FはGであって良い」と「GはHであって良い」とが記載されている場合には、「FはHであっても良い」事を含んでも良い。
In addition, in the above explanation, "A may be rephrased as B" may include the meaning of rephrasing B as A in addition to rephrasing A as B. Further, in the above description, when "C may be D" and "C may be E" are described, "D may be E" may be included. Further, in the above description, when "F may be G" and "G may be H" are stated, "F may be H" may be included.
また上記説明において、「A」という条件と、「B」という条件が、相反する条件の場合には、「B」という条件は、「A」という条件の「その他」の条件として表現されても良い。
Also, in the above explanation, if the condition "A" and the condition "B" are contradictory conditions, the condition "B" may be expressed as the "other" condition of the condition "A". good.
以下、本発明の実施形態における、端末装置、および、方法の種々の態様について説明する。
Various aspects of the terminal device and method in the embodiments of the present invention will be described below.
(1)本発明の第1の実施の様態は、基地局装置と通信する端末装置であって、前記基地局装置から、RRCメッセージを受信する受信部と、処理部とを備え、前記処理部は、第1のセルグループと第2のセルグループを使用して通信を行い、前記RRCメッセージは、前記第2のセルグループに含まれる特別なセルを設定する第1の設定を含み、前記処理部は、前記第1の設定に同期付再設定が含まれていることに基づいて、同期付再設定を実施し、前記処理部は、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示が含まれていない場合、すべてのサスペンドされた無線ベアラを再開し、すべての無線ベアラのための前記第2のセルグループにおける送信を、サスペンドされていたら再開し、前記処理部は、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示が含まれていた場合、一部のサスペンドされた無線ベアラを再開せず、一部の無線ベアラのための前記第2のセルグループにおける送信を再開しない端末装置である。
(1) A first embodiment of the present invention is a terminal device that communicates with a base station device, comprising: a receiving unit that receives an RRC message from the base station device; performs communication using a first cell group and a second cell group, wherein the RRC message includes a first configuration for configuring a special cell included in the second cell group; The unit performs synchronous reconfiguration based on the synchronous reconfiguration being included in the first configuration, and the processing unit deactivates the second cell group in the RRC message. resumes all suspended radio bearers and resumes, if suspended, transmission in the second cell group for all radio bearers if no instructions are included to cause the processing unit to: , if the RRC message includes an instruction to deactivate the second cell group, the second cell group for some radio bearers without resuming some suspended radio bearers; terminal equipment that does not resume transmission in the cell group of
(2)本発明の第2の実施の様態は、端末装置と通信する基地局装置であって、前記端末装置に、RRCメッセージを送信する送信部と、処理部とを備え、前記処理部は、第1のセルグループと第2のセルグループを使用して通信を行い、前記RRCメッセージは、前記第2のセルグループに含まれる特別なセルを設定する第1の設定を含み、前記処理部は、前記第1の設定に同期付再設定を含めることによって、前記端末装置に対し、同期付再設定を実施させ、前記処理部は、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示を含めないことによって、前記端末装置に対し、すべてのサスペンドされた無線ベアラを再開させ、すべての無線ベアラのための前記第2のセルグループにおける送信を、サスペンドされていたら再開させ、前記処理部は、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示を含めることによって、前記端末装置に対し、一部のサスペンドされた無線ベアラを再開させず、一部の無線ベアラのための前記第2のセルグループにおける送信を再開させない基地局装置である。
(2) A second embodiment of the present invention is a base station apparatus that communicates with a terminal device, comprising: a transmission unit that transmits an RRC message to the terminal device; , communicating using a first cell group and a second cell group, wherein the RRC message includes a first configuration for configuring a special cell included in the second cell group, the processing unit causes the terminal device to perform synchronous reconfiguration by including synchronous reconfiguration in the first configuration, and the processing unit deactivates the second cell group in the RRC message. causing the terminal to resume all suspended radio bearers and resume transmission in the second cell group for all radio bearers if suspended , the processing unit includes an instruction for deactivating the second cell group in the RRC message, so that the terminal device does not resume some suspended radio bearers, is a base station apparatus that does not restart transmission in the second cell group for the radio bearer of the second cell group.
(3)本発明の第3の実施の様態は、基地局装置と通信する端末装置の方法であって、前記基地局装置から、RRCメッセージを受信し、第1のセルグループと第2のセルグループを使用して通信を行い、前記RRCメッセージは、前記第2のセルグループに含まれる特別なセルを設定する第1の設定を含み、前記第1の設定に同期付再設定が含まれていることに基づいて、同期付再設定を実施し、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示が含まれていない場合、すべてのサスペンドされた無線ベアラを再開し、すべての無線ベアラのための前記第2のセルグループにおける送信を、サスペンドされていたら再開し、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示が含まれていた場合、一部のサスペンドされた無線ベアラを再開せず、一部の無線ベアラのための前記第2のセルグループにおける送信を再開しない方法である。
(3) A third embodiment of the present invention is a method for a terminal device that communicates with a base station device, receiving an RRC message from the base station device, Communication is performed using a group, the RRC message includes a first configuration for configuring a special cell included in the second cell group, and the first configuration includes reconfiguration with synchronization. performing reconfiguration with synchronization based on the fact that the RRC message does not contain an indication to deactivate the second cell group, resuming all suspended radio bearers; If the RRC message includes an instruction to resume transmission in the second cell group for all radio bearers if suspended and deactivate the second cell group, then: a method of not resuming some suspended radio bearers and not resuming transmission in the second cell group for some radio bearers.
本発明の一態様に関わる装置で動作するプログラムは、本発明の一態様に関わる上述した実施形態の機能を実現するように、Central Processing Unit(CPU)等を制御してコンピュータを機能させるプログラムであっても良い。プログラムあるいはプログラムによって取り扱われる情報は、処理時に一時的にRandom Access Memory(RAM)などの揮発性メモリに読み込まれ、あるいはフラッシュメモリなどの不揮発性メモリやHard Disk Drive(HDD)に格納され、必要に応じてCPUによって読み出し、修正・書き込みが行なわれる。
A program that runs on a device according to one aspect of the present invention is a program that controls a Central Processing Unit (CPU) or the like to function a computer so as to realize the functions of the above-described embodiments according to one aspect of the present invention. It can be. The program or information handled by the program is temporarily read into volatile memory such as Random Access Memory (RAM) during processing, or stored in non-volatile memory such as flash memory or Hard Disk Drive (HDD), and The CPU reads, modifies, and writes accordingly.
なお、上述した実施形態における装置の一部、をコンピュータで実現するようにしてもよい。その場合、この制御機能を実現するためのプログラムは、コンピュータが読み取り可能な記録媒体に記録して、この記録媒体に記録されたプログラムをコンピュータシステムに読み込ませ、実行することによって実現されてもよい。ここでいう「コンピュータシステム」とは、装置に内蔵されたコンピュータシステムであって、オペレーティングシステムや周辺機器等のハードウェアを含むものとする。また、「コンピュータが読み取り可能な記録媒体」とは、半導体記録媒体、光記録媒体、磁気記録媒体等のいずれであってもよい。
It should be noted that part of the devices in the above-described embodiments may be realized by a computer. In that case, the program for realizing this control function may be recorded in a computer-readable recording medium, and the program recorded in this recording medium may be read into a computer system and executed. . The "computer system" here is a computer system built in the device, and includes hardware such as an operating system and peripheral devices. Further, the "computer-readable recording medium" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, and the like.
さらに「コンピュータが読み取り可能な記録媒体」とは、インターネット等のネットワークや電話回線等の通信回線を介してプログラムを送信する場合の通信線のように、短時間、動的にプログラムを保持するもの、その場合のサーバやクライアントとなるコンピュ-タシステム内部の揮発性メモリのように、一定時間プログラムを保持しているものも含んでもよい。また上記プログラムは、前述した機能の一部を実現するためのものであってもよく、さらに前述した機能をコンピュ-タシステムにすでに記録されているプログラムとの組み合わせで実現できるものであってもよい。
Furthermore, "computer-readable recording medium" means a medium that dynamically stores programs for a short period of time, such as a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line. , it may also include something that holds the program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in that case. Further, the program may be for realizing a part of the functions described above, or may be capable of realizing the functions described above in combination with a program already recorded in the computer system. .
また、上述した実施形態に用いた装置の各機能ブロック、または諸特徴は、電気回路、すなわち典型的には集積回路あるいは複数の集積回路で実装または実行され得る。本明細書で述べられた機能を実行するように設計された電気回路は、汎用用途プロセッサ、デジタルシグナルプロセッサ(DSP)、特定用途向け集積回路(ASIC)、フィールドプログラマブルゲートアレイ(FPGA)、またはその他のプログラマブル論理デバイス、ディスクリートゲートまたはトランジスタロジック、ディスクリートハードウェア部品、またはこれらを組み合わせたものを含んでよい。汎用用途プロセッサは、マイクロプロセッサであってもよいし、代わりにプロセッサは従来型のプロセッサ、コントローラ、マイクロコントローラ、またはステートマシンであってもよい。汎用用途プロセッサ、または前述した各回路は、デジタル回路で構成されていてもよいし、アナログ回路で構成されていてもよい。また、半導体技術の進歩により現在の集積回路に代替する集積回路化の技術が出現した場合、当該技術による集積回路を用いることも可能である。
Also, each functional block or feature of the apparatus used in the embodiments described above may be implemented or performed in an electrical circuit, typically an integrated circuit or multiple integrated circuits. Electrical circuits designed to perform the functions described herein may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general purpose processor may be a microprocessor, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The general-purpose processor or each circuit described above may be composed of digital circuits or may be composed of analog circuits. In addition, when an integrated circuit technology that replaces current integrated circuits emerges due to advances in semiconductor technology, it is also possible to use integrated circuits based on this technology.
なお、本発明の一態様は上述の実施形態に限定されるものではない。実施形態では、装置の一例を記載したが、本発明の一態様は、これに限定されるものではなく、屋内外に設置される据え置き型、または非可動型の電子機器、たとえば、AV機器、キッチン機器、掃除・洗濯機器、空調機器、オフィス機器、自動販売機、その他生活機器などの端末装置もしくは通信装置に適用出来る。
It should be noted that one aspect of the present invention is not limited to the above-described embodiments. Although an example of the apparatus has been described in the embodiment, one aspect of the present invention is not limited to this, and is a stationary or non-movable electronic device installed indoors or outdoors, such as an AV device, It can be applied to terminal devices or communication devices such as kitchen equipment, cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household equipment.
以上、この発明の実施形態に関して、図面を参照して詳述してきたが、具体的な構成はこの実施形態に限られるものではなく、この発明の要旨を逸脱しない範囲の設計変更等も含まれる。また、本発明の一態様は、請求項に示した範囲で種々の変更が可能であり、異なる実施形態にそれぞれ開示された技術的手段を適宜組み合わせて得られる実施形態についても本発明の技術的範囲に含まれる。また、上記実施形態に記載された要素であり、同様の効果を奏する要素同士を置換した構成も含まれる。
Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like are included within the scope of the gist of the present invention. . Further, one aspect of the present invention can be modified in various ways within the scope of the claims, and an embodiment obtained by appropriately combining technical means disclosed in different embodiments can also be Included in the scope. Further, it also includes a configuration in which the elements described in the above embodiments are replaced with the elements having the same effect.
本発明の一態様は、例えば、通信システム、通信機器(例えば、携帯電話装置、基地局装置、無線LAN装置、或いはセンサーデバイス)、集積回路(例えば、通信チップ)、又はプログラム等において、利用することができる。
One aspect of the present invention is, for example, a communication system, a communication device (e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (e.g., a communication chip), or a program, etc. be able to.
100 E-UTRA
102 eNB
104 EPC
106 NR
108 gNB
110 5GC
112、114、116、118、120、124 インタフェース
122 UE
200、300 PHY
202、302 MAC
204、304 RLC
206、306 PDCP
208、308 RRC
310 SDAP
210、312 NAS
500、604 受信部
502、602 処理部
504、600 送信部 100 E-UTRA
102 eNB
104 EPCs
106NR
108 gNB
110 5GC
112, 114, 116, 118, 120, 124 interfaces
122 UEs
200, 300 PHYs
202, 302 MACs
204, 304 RLC
206, 306 PDCP
208, 308 RRC
310 SDAP
210, 312 NAS
500, 604 Receiver
502, 602 processor
504, 600 transmitter
102 eNB
104 EPC
106 NR
108 gNB
110 5GC
112、114、116、118、120、124 インタフェース
122 UE
200、300 PHY
202、302 MAC
204、304 RLC
206、306 PDCP
208、308 RRC
310 SDAP
210、312 NAS
500、604 受信部
502、602 処理部
504、600 送信部 100 E-UTRA
102 eNB
104 EPCs
106NR
108 gNB
110 5GC
112, 114, 116, 118, 120, 124 interfaces
122 UEs
200, 300 PHYs
202, 302 MACs
204, 304 RLC
206, 306 PDCP
208, 308 RRC
310 SDAP
210, 312 NAS
500, 604 Receiver
502, 602 processor
504, 600 transmitter
Claims (3)
- 基地局装置と通信する端末装置であって、
前記基地局装置から、RRCメッセージを受信する受信部と、処理部とを備え、
前記処理部は、第1のセルグループと第2のセルグループを使用して通信を行い、
前記RRCメッセージは、前記第2のセルグループに含まれる特別なセルを設定する第1の設定を含み、
前記処理部は、前記第1の設定に同期付再設定が含まれていることに基づいて、同期付再設定を実施し、
前記処理部は、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示が含まれていない場合、
すべてのサスペンドされた無線ベアラを再開し、
すべての無線ベアラのための前記第2のセルグループにおける送信を、サスペンドされていたら再開し、
前記処理部は、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示が含まれていた場合、
一部のサスペンドされた無線ベアラを再開せず、
一部の無線ベアラのための前記第2のセルグループにおける送信を再開しない
端末装置。 A terminal device that communicates with a base station device,
A receiving unit for receiving an RRC message from the base station device, and a processing unit,
The processing unit communicates using a first cell group and a second cell group,
The RRC message includes a first configuration that configures a special cell included in the second cell group,
The processing unit performs resetting with synchronization based on the resetting with synchronization being included in the first setting,
The processing unit, if the RRC message does not include an instruction to deactivate the second cell group,
resume all suspended radio bearers,
resuming, if suspended, transmission in the second cell group for all radio bearers;
The processing unit, if the RRC message includes an instruction to deactivate the second cell group,
does not resume some suspended radio bearers,
A terminal device that does not resume transmission in the second cell group for some radio bearers. - 端末装置と通信する基地局装置であって、
前記端末装置に、RRCメッセージを送信する送信部と、処理部とを備え、
前記処理部は、第1のセルグループと第2のセルグループを使用して通信を行い、
前記RRCメッセージは、前記第2のセルグループに含まれる特別なセルを設定する第1の設定を含み、
前記処理部は、前記第1の設定に同期付再設定を含めることによって、前記端末装置に対し、同期付再設定を実施させ、
前記処理部は、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示を含めないことによって、前記端末装置に対し、
すべてのサスペンドされた無線ベアラを再開させ、
すべての無線ベアラのための前記第2のセルグループにおける送信を、サスペンドされていたら再開させ、
前記処理部は、前記RRCメッセージに前記第2のセルグループを不活性化させるための指示を含めることによって、前記端末装置に対し、
一部のサスペンドされた無線ベアラを再開させず、
一部の無線ベアラのための前記第2のセルグループにおける送信を再開させない
基地局装置。 A base station device that communicates with a terminal device,
A transmission unit for transmitting an RRC message to the terminal device, and a processing unit,
The processing unit communicates using a first cell group and a second cell group,
The RRC message includes a first configuration that configures a special cell included in the second cell group,
The processing unit causes the terminal device to perform resetting with synchronization by including resetting with synchronization in the first configuration,
By not including an instruction for deactivating the second cell group in the RRC message, the processing unit causes the terminal device to:
resume all suspended radio bearers,
resume transmission in the second cell group for all radio bearers if suspended;
By including an instruction for deactivating the second cell group in the RRC message, the processing unit causes the terminal device to:
Do not resume some suspended radio bearers,
A base station apparatus that does not restart transmission in the second cell group for some radio bearers. - 基地局装置と通信する端末装置の方法であって、
前記基地局装置から、RRCメッセージを受信し、
第1のセルグループと第2のセルグループを使用して通信を行い、
前記RRCメッセージは、前記第2のセルグループに含まれる特別なセルを設定する第1の設定を含み、
前記第1の設定に同期付再設定が含まれていることに基づいて、同期付再設定を実施し、
前記RRCメッセージに前記第2のセルグループを不活性化させるための指示が含まれていない場合、
すべてのサスペンドされた無線ベアラを再開し、
すべての無線ベアラのための前記第2のセルグループにおける送信を、サスペンドされていたら再開し、
前記RRCメッセージに前記第2のセルグループを不活性化させるための指示が含まれていた場合、
一部のサスペンドされた無線ベアラを再開せず、
一部の無線ベアラのための前記第2のセルグループにおける送信を再開しない
方法。 A method for a terminal device communicating with a base station device, comprising:
receive an RRC message from the base station device;
communicating using a first cell group and a second cell group;
The RRC message includes a first configuration that configures a special cell included in the second cell group,
performing reset with synchronization based on the fact that reset with synchronization is included in the first setting;
If the RRC message does not contain an instruction to deactivate the second cell group,
resume all suspended radio bearers,
resuming, if suspended, transmission in the second cell group for all radio bearers;
If the RRC message includes an instruction to deactivate the second cell group,
does not resume some suspended radio bearers,
A method of not resuming transmission in the second cell group for some radio bearers.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2023539701A JPWO2023013292A1 (en) | 2021-08-05 | 2022-06-24 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2021-128736 | 2021-08-05 | ||
JP2021128736 | 2021-08-05 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023013292A1 true WO2023013292A1 (en) | 2023-02-09 |
Family
ID=85154007
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2022/025375 WO2023013292A1 (en) | 2021-08-05 | 2022-06-24 | Terminal device, base station device, and method |
Country Status (2)
Country | Link |
---|---|
JP (1) | JPWO2023013292A1 (en) |
WO (1) | WO2023013292A1 (en) |
-
2022
- 2022-06-24 WO PCT/JP2022/025375 patent/WO2023013292A1/en active Application Filing
- 2022-06-24 JP JP2023539701A patent/JPWO2023013292A1/ja active Pending
Non-Patent Citations (1)
Title |
---|
ZTE CORPORATION, SANECHIPS: "Framework of SCG deactivation and activation", 3GPP DRAFT; R2-2006900, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911775 * |
Also Published As
Publication number | Publication date |
---|---|
JPWO2023013292A1 (en) | 2023-02-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022071234A1 (en) | Terminal device, communication method, and base station device | |
WO2022080306A1 (en) | Terminal device, base station device, and method | |
WO2022080419A1 (en) | Terminal device, base station device, and method | |
WO2022085663A1 (en) | Method and integrated circuit | |
WO2023013292A1 (en) | Terminal device, base station device, and method | |
WO2023042747A1 (en) | Terminal device, base station device, and method | |
WO2023042752A1 (en) | Terminal device, base station device, and method | |
WO2023100981A1 (en) | Terminal device, method, and integrated circuit | |
WO2023063342A1 (en) | Terminal device, base station device, and method | |
WO2023136231A1 (en) | Terminal device, method, and integrated circuit | |
WO2023063345A1 (en) | Terminal device, base station device, and method | |
WO2023132370A1 (en) | Terminal device, method, and integrated circuit | |
WO2023112531A1 (en) | Terminal device, method, and integrated circuit | |
WO2023112792A1 (en) | Terminal device, method, and integrated circuit | |
WO2023106315A1 (en) | Terminal device, base station device, and method | |
US12075510B2 (en) | Terminal apparatus, base station apparatus, and method | |
WO2023243571A1 (en) | Terminal device, method, and integrated circuit | |
WO2023153410A1 (en) | Terminal device, method, and integrated circuit | |
WO2023008043A1 (en) | Terminal device, method, and integrated circuit | |
WO2022196550A1 (en) | Terminal device, base station device, and method | |
WO2024005069A1 (en) | Terminal device, method, and integrated circuit | |
WO2024005010A1 (en) | Terminal device, method, and integrated circuit | |
WO2023204307A1 (en) | Terminal device, method, and integrated circuit | |
WO2023189963A1 (en) | Terminal device, method, and integrated circuit | |
WO2023189798A1 (en) | Terminal device, base station device, and method |
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: 22852718 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023539701 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 22852718 Country of ref document: EP Kind code of ref document: A1 |