Terminal device, method, and integrated circuit

Abstract

This terminal device performs measurement on the basis of a measurement configuration, and generates a measurement report message including identifier information of each of one or more adjacent cells on the basis of the measurement configuration and the measurement. The measurement report message includes information indicating whether or not valid first information associated with the adjacent cell identified by the identifier information is held. The first information includes a cell-specific parameter that is set in the terminal device when the adjacent cell identified by the identifier information operates as a serving cell.

Description

Terminal device, method, and integrated circuit

[0001] The present invention relates to a terminal device, a method, and an integrated circuit.This application claims priority to Japanese Patent Application No. 2023-119838, filed on July 24, 2023, the contents of which are incorporated herein by reference.

[0002] The 3rd Generation Partnership Project (3GPP, registered trademark), a standardization project for cellular mobile communication systems, is conducting technical studies and formulating standards for cellular mobile communication systems, including radio access, core networks, services, etc.

[0003] For example, 3GPP has begun technical studies and standardization of E-UTRA (Evolved Universal Terrestrial Radio Access) as a radio access technology (RAT) for 3.9G and 4G cellular mobile communication systems. 3GPP is currently conducting technical studies and standardization of E-UTRA extension technologies. E-UTRA is also called Long Term Evolution (LTE: registered trademark), and the extension technologies are sometimes called LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).

[0004] Additionally, 3GPP has begun technical studies and standardization of NR (New Radio, or NR Radio access) as a radio access technology (RAT) for 5th Generation (5G) cellular mobile communication systems. 3GPP is currently conducting technical studies and standardization of NR extension technologies.

[0005] 3GPP TS 38.331 v17.0.0,"Evolved Universal Terrestrial Radio Access (E-UTRA);Radio Resource Control (RRC);Protocol specifications" pp70-116,pp218-223,pp316-1107

[0006] In 3GPP, as an extension technology of NR, in order to reduce the signaling overhead of the entire cell, a base station device is considering broadcasting common settings to multiple terminal devices within a cell and using those settings during handover, but the details of the settings have not been considered.

[0007] One aspect of the present invention has been made in consideration of the above-mentioned circumstances, and one of its objects is to provide a terminal device, a base station device, a communication method, and an integrated circuit that can efficiently perform communication control.

[0008] In order to achieve the above object, one aspect of the present invention provides the following: That is, one aspect of the present invention provides a terminal device comprising: a receiver that receives an RRC configuration message including a measurement configuration from a base station device; a transmitter that transmits a measurement report message to the base station device; and a processor that performs RRC layer processing, wherein the processor performs measurement based on the measurement configuration, and generates a measurement report message including identifier information of one or more neighboring cells based on the measurement configuration and the measurement, the measurement report message including information indicating whether valid first information associated with the neighboring cell identified by the identifier information is held, and the first information includes a cell-specific parameter that is set in the terminal device when the neighboring cell identified by the identifier information becomes a serving cell.

[0009] Another aspect of the present invention is a method applied to a terminal device, comprising the steps of receiving an RRC configuration message including a measurement configuration from a base station device, transmitting a measurement report message to the base station device, performing a measurement based on the measurement configuration, and generating a measurement report message including identifier information of one or more neighboring cells based on the measurement configuration and the measurement, wherein the measurement report message includes information indicating whether valid first information corresponding to the neighboring cell identified by the identifier information is held, and the first information includes cell-specific parameters that are set in the terminal device when the neighboring cell identified by the identifier information becomes a serving cell.

[0010] Another aspect of the present invention is an integrated circuit implemented in a terminal device, which enables the terminal device to perform the following functions: receiving an RRC configuration message including a measurement configuration from a base station device; transmitting a measurement report message to the base station device; performing measurements based on the measurement configuration; and generating a measurement report message including identifier information for one or more neighboring cells based on the measurement configuration and the measurements, wherein the measurement report message includes information indicating whether valid first information corresponding to the neighboring cell identified by the identifier information is held, and the first information includes cell-specific parameters that are set in the terminal device when the neighboring cell identified by the identifier information becomes a serving cell.

[0011] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium.

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

[0013] 1 is a schematic diagram of a communication system according to the present embodiment. 2 is a diagram of an example of an E-UTRA protocol configuration according to the present embodiment. 3 is a diagram of an example of an NR protocol configuration according to the present embodiment. 4 is a diagram showing an example of a procedure flow for various settings in RRC according to the present embodiment. 5 is a block diagram showing the configuration of a terminal device according to the present embodiment. 6 is a block diagram showing the configuration of a base station device according to the present embodiment. 7 is an example of an ASN.1 description of a message related to reconfiguration of an RRC connection in NR according to the present embodiment. 8 is an example of an ASN.1 description of a message related to reconfiguration of an RRC connection in NR according to the present embodiment. 9 is an example of an RRC reconfiguration process according to the present embodiment.

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

[0015] LTE (and LTE-A, LTE-A Pro) and NR may be defined as different radio access technologies (Radio Access Technologies: RATs). LTE connectable to NR via Multi-Radio Dual Connectivity (MR-DC) may be distinguished from conventional LTE. LTE using 5GC for the core network (Core Network: CN) may be distinguished from conventional LTE using EPC for the core network. Conventional LTE may refer to LTE that does not implement technologies standardized in 3GPP Release 15 or later. This embodiment may be applied to NR, LTE, and other RATs. While the following description uses terms related to LTE and NR, this embodiment may also be applied to technologies using other terms and / or other radio access technologies. In this embodiment, the terms E-UTRA and LTE may be interchangeable.

[0016] In this embodiment, the names of each node and entity, and the processes in each node and entity when the radio access technology is E-UTRA or NR will be described, but this embodiment may be applied to other radio access technologies. The names of each node and entity, and the names of parameters and messages in this embodiment may be different from those described in this embodiment.

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

[0018] E-UTRA 100 may be a radio access technology. E-UTRA 100 may also be an air interface between UE 122 and eNB 102. The air interface between UE 122 and eNB 102 may be referred to as a Uu interface. eNB (E-UTRAN Node B) 102 may be a base station device of E-UTRA 100. eNB 102 may have the E-UTRA protocol described below. The E-UTRA protocol may be configured from an E-UTRA User Plane (UP) protocol described below and an E-UTRA Control Plane (CP) protocol described below. eNB 102 may terminate the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol for UE 122. A radio access network configured by eNBs may be referred to as E-UTRAN.

[0019] The EPC (Evolved Packet Core) 104 may be a core network. The interface 112 is an interface between the eNB 102 and the EPC 104 and may be referred to as an S1 interface. The interface 112 may include a control plane interface through which control signals pass and / or a user plane interface through which user data passes. The control plane interface of the interface 112 may terminate at a Mobility Management Entity (MME: not shown) in the EPC 104. The user plane interface of the interface 112 may terminate at a Serving Gateway (S-GW: not shown) in the EPC 104. The control plane interface of the interface 112 may be referred to as an S1-MME interface. The user plane interface of the interface 112 may be referred to as an S1-U interface.

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

[0021] The NR 106 may be a radio access technology. The NR 106 may also be an air interface between the UE 122 and the gNB 108. The air interface between the UE 122 and the gNB 108 may be referred to as a Uu interface. The gNB (g Node B) 108 may be a base station device of the NR 106. The gNB 108 may have the NR protocol described below. The NR protocol may be composed of the NR user plane (User Plane: UP) protocol described below and the NR control plane (Control Plane: CP) protocol described below. The gNB 108 may terminate the NR user plane (User Plane: UP) protocol and the NR control plane (Control Plane: CP) protocol for the UE 122.

[0022] 5GC110 may be a core network. Interface 116 is an interface between gNB108 and 5GC110 and may be referred to as an NG interface. Interface 116 may have a control plane interface through which control signals pass and / or a user plane interface through which user data passes. The control plane interface of interface 116 may terminate in an Access and Mobility Management Function (AMF: not shown) in 5GC110. The user plane interface of interface 116 may terminate in a User Plane Function (UPF: not shown) in 5GC110. The control plane interface of interface 116 may be referred to as an NG-C interface. The user plane interface of interface 116 may be referred to as an NG-U interface.

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

[0024] The eNB 102 may have the capability to connect to the 5GC 110. The eNB 102 with the capability to connect to the 5GC 110 may be referred to as an ng-eNB. The interface 114 is an interface between the eNB 102 and the 5GC 110 and may be referred to as an NG interface. The interface 114 may have a control plane interface through which control signals pass and / or a user plane interface through which user data passes. The control plane interface of the interface 114 may terminate in the AMF within the 5GC 110. The user plane interface of the interface 114 may terminate in the UPF within the 5GC 110. The control plane interface of the interface 114 may be referred to as an NG-C interface. The user plane interface of the interface 114 may be referred to as an NG-U interface. A radio access network consisting of an ng-eNB or a gNB may be referred to as an NG-RAN. The NG-RAN, E-UTRAN, etc. may simply be referred to as a network. Furthermore, the network may include an eNB, ng-eNB, gNB, etc.

[0025] Note that one or more eNBs 102 may be connected to 5GC 110 via interface 114. An interface may exist between multiple eNBs 102 connected to 5GC 110 (not shown). The interface between multiple eNBs 102 connected to 5GC 110 may be called an Xn interface. Furthermore, an eNB 102 connected to 5GC 110 and a gNB 108 connected to 5GC 110 may be connected by interface 120. The interface 120 between an eNB 102 connected to 5GC 110 and a gNB 108 connected to 5GC 110 may be called an Xn interface.

[0026] The gNB 108 may have the function of connecting to the EPC 104. A gNB 108 with the function of connecting to the EPC 104 may be referred to as an en-gNB. Interface 118 is an interface between the gNB 108 and the EPC 104 and may be referred to as an S1 interface. A user plane interface through which user data passes may exist in interface 118. The user plane interface of interface 118 may terminate in an S-GW (not shown) in the EPC 104. The user plane interface of interface 118 may be referred to as an S1-U interface. Furthermore, the eNB 102 connecting to the EPC 104 and the gNB 108 connecting to the EPC 104 may be connected by interface 120. The interface 120 between the eNB 102 connecting to the EPC 104 and the gNB 108 connecting to the EPC 104 may be referred to as an X2 interface.

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

[0028] The UE 122 may be a terminal device capable of receiving system information and paging messages transmitted from the eNB 102 and / or the gNB 108. The UE 122 may also be a terminal device capable of wireless connection with the eNB 102 and / or the gNB 108. The UE 122 may also be a terminal device capable of simultaneously establishing a wireless connection with the eNB 102 and a wireless connection with the gNB 108. The UE 122 may have an E-UTRA protocol and / or an NR protocol. The wireless connection may be a Radio Resource Control (RRC) connection.

[0029] Furthermore, the UE 122 may be a terminal device capable of connecting to the EPC 104 and / or the 5GC 110 via the eNB 102 and / or the gNB 108. When the core network to which the eNB 102 and / or the gNB 108, with which the UE 122 communicates, is connected is the EPC 104, each Data Radio Bearer (DRB) (described later) established between the UE 122 and the eNB 102 and / or the gNB 108 may be further uniquely associated with each EPS (Evolved Packet System) bearer passing through the EPC 104. Each EPS bearer may be identified by an EPS bearer identifier (Identity, or ID). Furthermore, the same QoS may be guaranteed for data such as IP packets and Ethernet frames passing through the same EPS bearer.

[0030] Furthermore, if the core network to which the eNB102 and / or gNB108 with which the UE122 communicates is connected is the 5GC110, each DRB established between the UE122 and the eNB102 and / or gNB108 may be further linked to one of the PDU (Packet Data Unit) sessions established within the 5GC110. One or more QoS flows may exist in each PDU session. Each DRB may be mapped to one or more QoS flows, or may not be mapped to any QoS flow. Each PDU session may be identified by a PDU session identifier (Identity, or ID). Furthermore, each QoS flow may be identified by a QoS flow identifier (Identity, or ID). Furthermore, the same QoS may be guaranteed for data such as IP packets and Ethernet frames passing through the same QoS flow.

[0031] There may be no PDU sessions and / or QoS flows in the EPC 104, and no EPS bearers in the 5GC 110. When the UE 122 is connected to the EPC 104, the UE 122 has information about the EPS bearers, but may not have information about the PDU sessions and / or QoS flows. When the UE 122 is connected to the 5GC 110, the UE 122 has information about the PDU sessions and / or QoS flows, but may not have information about the EPS bearers.

[0032] In the following description, eNB102 and / or gNB108 will also be simply referred to as base station devices, and UE122 will also be simply referred to as terminal devices or UEs.

[0033] FIG. 2 is a diagram showing an example of an E-UTRA protocol architecture according to this embodiment. FIG. 3 is a diagram showing an example of an NR protocol architecture according to this embodiment. Note that the functions of each protocol described using FIG. 2 and / or FIG. 3 are only some of the functions closely related to this embodiment, and other functions may also be included. Note that in this embodiment, an uplink (UL) may be a link from a terminal device to a base station device. Also, in this embodiment, a downlink (DL) may be a link from a base station device to a terminal device. Also, in this embodiment, a sidelink (SL) may be a link from a terminal device to a terminal device that does not go through a base station device.

[0034] 2A is a diagram of an E-UTRA user plane (UP) protocol stack. As shown in FIG. 2A, the E-UTRA UP protocol may be a protocol between the UE 122 and the eNB 102. That is, the E-UTRA UP protocol may be a protocol that terminates at the eNB 102 on the network side. As shown in FIG. 2A, the E-UTRA user plane protocol stack may be composed of a PHY (Physical layer) 200, which is a radio physical layer, a MAC (Medium Access Control) 202, which is a medium access control layer, a RLC (Radio Link Control) 204, which is a radio link control layer, and a PDCP (Packet Data Convergence Protocol) 206, which is a packet data convergence protocol layer.

[0035] FIG. 3A is a diagram of an NR user plane (UP) protocol stack. As shown in FIG. 3A, the NRUP protocol may be a protocol between the UE 122 and the gNB 108. That is, the NR UP protocol may be a protocol that terminates at the gNB 108 on the network side. As shown in FIG. 3A, the NR user plane protocol stack may be composed of a radio physical layer, PHY 300, a medium access control layer, MAC 302, a radio link control layer, RLC 304, a packet data convergence protocol layer, PDCP 306, and a service data adaptation protocol layer, SDAP (Service Data Adaptation Protocol) 310.

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

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

[0038] The AS (Access Stratum) layer may be a layer that terminates between the UE 122 and the eNB 102 and / or the gNB 108. That is, the AS layer may be a layer that includes some or all of the PHY 200, the MAC 202, the RLC 204, the PDCP 206, and the RRC 208, and / or a layer that includes some or all of the PHY 300, the MAC 302, the RLC 304, the PDCP 306, the SDAP 310, and the RRC 308.

[0039] In the present embodiment, the E-UTRA protocol and the NR protocol may not be distinguished from each other, and the terms PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) may be used. In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) may respectively refer to the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the E-UTRA protocol, or the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the NR protocol. The SDAP (SDAP layer) may also be the SDAP (SDAP layer) of the NR protocol.

[0040] In this embodiment, when distinguishing between E-UTRA protocols and NR protocols, the PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208 may be referred to as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively. The PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208 may also be referred to as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively. Furthermore, when distinguishing between E-UTRA protocols and NR protocols, PHY300, MAC302, RLC304, PDCP306, and RRC308 may be referred to as NR PHY, NR MAC, NR RLC, NR RLC, and NR RRC, respectively. Furthermore, PHY300, MAC302, RLC304, PDCP306, and RRC308 may be referred to as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.

[0041] This section describes entities in the AS layer of E-UTRA and / or NR. An entity having some or all of the functions of the MAC layer may be referred to as a MAC entity. An entity having some or all of the functions of the RLC layer may be referred to as an RLC entity. An entity having some or all of the functions of the PDCP layer may be referred to as a PDCP entity. An entity having some or all of the functions of the SDAP layer may be referred to as an SDAP entity. An entity having some or all of the functions of the RRC layer may be referred to as an RRC entity. The MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be referred to as MAC, RLC, PDCP, SDAP, and RRC, respectively.

[0042] Note that data provided from MAC, RLC, PDCP, and SDAP to lower layers, and / or data provided from lower layers to MAC, RLC, PDCP, and SDAP, may be referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Data provided from higher layers to MAC, RLC, PDCP, and SDAP, and / or data provided from MAC, RLC, PDCP, and SDAP to higher layers, may be referred to as MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. A segmented RLC SDU may be referred to as an RLC SDU segment.

[0043] Here, the base station apparatus and the terminal apparatus exchange (transmit and receive) signals in a higher layer. The higher layer may be referred to as an upper layer, and the terms may be interchangeable. For example, the base station apparatus and the terminal apparatus may transmit and receive RRC messages (also referred to as RRC signaling) in a Radio Resource Control (RRC) layer. The base station apparatus and the terminal apparatus may also transmit and receive MAC control elements in a Medium Access Control (MAC) layer. The RRC layer of the terminal apparatus acquires system information broadcast from the base station apparatus. Here, the RRC messages, system information, and / or MAC control elements are also referred to as higher layer signals (higher layer signaling) or higher layer parameters (higher layer parameters). Each of the parameters included in the higher layer signals received by the terminal apparatus may be referred to as a higher layer parameter. For example, in PHY layer processing, an upper layer means a layer higher than the PHY layer, and therefore may mean one or more of a MAC layer, an RRC layer, an RLC layer, a PDCP layer, an NAS (Non Access Stratum) layer, etc. For example, in MAC layer processing, an upper layer may mean one or more of an RRC layer, an RLC layer, a PDCP layer, an NAS layer, etc.

[0044] Hereinafter, the meaning of "A is given (provided) by an upper layer" or "A is given (provided) by an upper layer" may mean that an upper layer (mainly an RRC layer, a MAC layer, etc.) of a terminal device receives A from a base station device, and the received A is given (provided) from the upper layer of the terminal device to a lower layer (mainly a MAC layer or a physical layer) of the terminal device. For example, in a terminal device, "an upper layer parameter is provided" may mean that an upper layer signal is received from a base station device, and the upper layer parameter included in the received upper layer signal is provided from the upper layer of the terminal device to the lower layer of the terminal device. Setting an upper layer parameter in a terminal device may mean that the upper layer parameter is given (provided) to the terminal device. For example, setting an upper layer parameter in a terminal device may mean that the terminal device receives an upper layer signal from a base station device and sets the received upper layer parameter in the upper layer. However, setting an upper layer parameter in a terminal device may also include setting a default parameter that is given in advance to the upper layer of the terminal device. When describing transmission of an RRC message from a terminal device to a base station device, the expression "submitting a message from the RRC entity of the terminal device to a lower layer" may be used. In the terminal device, "submitting a message to a lower layer" from the RRC entity may mean submitting a message to the PDCP layer. In the terminal device, "submitting a message to a lower layer" from the RRC layer may mean submitting a message to a PDCP entity corresponding to each SRB, since RRC messages are transmitted using SRBs (SRB0, SRB1, SRB2, SRB3, etc.). When the RRC entity of the terminal device receives an indication from a lower layer, the lower layer may mean one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, etc.

[0045] An example of the functions of the PHY will be described. The PHY of the terminal device may have a function to receive data transmitted from the PHY of the base station device via a downlink (DL) physical channel. The PHY of the terminal device may have a function to transmit data to the PHY of the base station device via an uplink (UL) physical channel. The PHY may be connected to a higher MAC via a transport channel. The PHY may pass data to the MAC via the transport channel. The PHY may also be provided with data from the MAC via the transport channel. In the PHY, an RNTI (Radio Network Temporary Identifier) ​​may be used to identify various control information.

[0046] Here, the physical channels will be described. The physical channels used for wireless communication between a terminal device and a base station device may include the following physical channels.

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

[0048] The PBCH may be used to broadcast system information required by a terminal device.

[0049] In addition, in NR, the PBCH may be used to broadcast a time index (SSB-Index) within a synchronization signal block (SSB) period.

[0050] The PDCCH may be used to transmit (or carry) downlink control information (DCI) in downlink wireless communication (wireless communication from a base station device to a terminal device). Here, one or more DCIs (which may also be referred to as DCI formats) may be defined for transmitting the downlink control information. That is, a field for the downlink control information may be defined as DCI and mapped to information bits. The PDCCH may be transmitted in PDCCH candidates. The terminal device may 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. Furthermore, the terminal device may monitor the PDCCH candidates at configured monitoring occasions in one or more configured control resource sets (CORESETs) configured by search space configuration. The DCI format may be used for scheduling the PUSCH in the serving cell. The PUSCH may be used for transmitting user data, transmitting RRC messages (described later), and the like.

[0051] The PUCCH may be used to transmit uplink control information (UCI) in uplink wireless communication (wireless communication from a terminal device to a base station device). Here, the uplink control information may include channel state information (CSI) used to indicate the state of a downlink channel. The uplink control information may also include a scheduling request (SR) used to request an uplink shared channel (UL-SCH) resource. The uplink control information may also include a hybrid automatic repeat reQuest ACKnowledgement (HARQ-ACK).

[0052] The PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer, and may also be used to transmit system information (SI) and random access responses (RAR) in the downlink.

[0053] The PUSCH may be used to transmit uplink data from the MAC layer (UL-SCH: Uplink Shared CHannel) or HARQ-ACK and / or CSI together with uplink data. The PUSCH may also be used to transmit only CSI, or only HARQ-ACK and CSI. That is, the PUSCH may be used to transmit only UCI. The PDSCH or PUSCH may also be used to transmit RRC messages and MAC CE (described later). Here, in the PDSCH, an RRC message transmitted from a base station apparatus may be signaling common to multiple terminal apparatuses within a cell. The RRC message transmitted from a base station apparatus may also be signaling dedicated to a certain terminal apparatus. That is, terminal apparatus-specific information may be transmitted using signaling dedicated to a certain terminal apparatus. The PUSCH may also be used to transmit UE capabilities in the uplink.

[0054] The PRACH may be used to transmit a random access preamble and may be used to indicate initial connection establishment procedures, handover procedures, connection re-establishment procedures, synchronization (timing adjustment) for uplink transmissions, and requests for UL-SCH resources.

[0055] An example of the MAC function will be described. The MAC may be referred to as a MAC sublayer. The MAC may have the function of mapping various logical channels to corresponding transport channels. The logical channels may be identified by a logical channel identity (or logical channel ID). The MAC may be connected to the higher-level RLC via a logical channel. Depending on the type of information to be transmitted, the logical channels may be divided into control channels that transmit control information and traffic channels that transmit user information. The logical channels may also be divided into uplink logical channels and downlink logical channels. The MAC may have the function 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 MAC PDUs provided by the PHY and providing them to the higher layer via the logical channel to which each MAC SDU belongs. The MAC may also have the function of performing error correction through HARQ (Hybrid Automatic Repeat reQuest). The MAC may also have a scheduling report function that reports scheduling information. The MAC may also have a function to prioritize processing between terminal devices using dynamic scheduling. The MAC may also have a function to prioritize processing between logical channels within a single terminal device. The MAC may also have a function to prioritize processing of overlapping resources within a single terminal device. The MAC may also have a function to identify Multimedia Broadcast Multicast Services (MBMS). The NR MAC may also have a function to identify Multicast / Broadcast Services (MBS). The MAC may also have a function to select a transport format.The MAC may have functions such as discontinuous reception (DRX) and / or discontinuous transmission (DTX), a random access (RA) procedure, a power headroom report (PHR) function that notifies information about available transmission power, and a buffer status report (BSR) function that notifies information about the amount of data in the transmission buffer. The NR MAC may have a bandwidth adaptation (BA) function. The MAC PDU format used in the E-UTRA MAC may differ from that used in the NR MAC. The MAC PDU may also include a MAC control element (MAC CE), which is an element for controlling the MAC.

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

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

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

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

[0060] A DCCH (Dedicated Control Channel) may be a logical channel for transmitting dedicated control information bidirectionally, point-to-point, between a terminal device and a base station device. The dedicated control information may be control information dedicated to each terminal device. The DCCH may be used when the terminal device has an RRC connection.

[0061] A DTCH (Dedicated Traffic Channel) may be a logical channel for transmitting user data point-to-point between a terminal device and a base station device. A DTCH may be a logical channel for transmitting dedicated user data. Dedicated user data may be user data dedicated to each terminal device. A DTCH may exist in both uplink and downlink.

[0062] This section describes the mapping of logical channels and transport channels for the uplink in E-UTRA and / or NR.

[0063] The CCCH may be mapped to an uplink shared channel (UL-SCH), which is an uplink transport channel.

[0064] The DCCH may be mapped to an uplink shared channel (UL-SCH), which is an uplink transport channel.

[0065] The DTCH may be mapped to an uplink shared channel (UL-SCH), which is an uplink transport channel.

[0066] This section describes the mapping of logical channels and transport channels for the downlink in E-UTRA and / or NR.

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

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

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

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

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

[0072] An example of the RLC function will be described. The RLC may also be called an RLC sublayer. The E-UTRA RLC may have the function of segmenting and / or concatenating data provided by the PDCP in the upper layer and providing it to the lower layer. The E-UTRA RLC may have the function of reassembling and reordering data provided by the lower layer and providing it to the upper layer. The NR RLC may have the function of adding a sequence number independent of the sequence number added by PDCP to data provided by the PDCP in the upper layer. The NR RLC may also have the function of segmenting data provided by PDCP and providing it to the lower layer. The NR RLC may also have the function of reassembling data provided by the lower layer and providing it to the upper layer. The RLC may also have the function of data retransmission and / or retransmission request (Automatic Repeat reQuest: ARQ). RLC may also have the function of performing error correction using ARQ. The control information sent from the receiving side of RLC to the transmitting side to indicate data that needs to be retransmitted in order to perform ARQ may be called a status report. The status report transmission instruction sent from the transmitting side of RLC to the receiving side may be called a poll. RLC may also have the function of detecting data duplication. RLC may also have the function of discarding data. RLC may have three modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). In TM, data received from the upper layer is not segmented, and an RLC header does not need to be added. The TM RLC entity is a unidirectional entity and may be configured as a transmitting TM RLC entity or a receiving TM RLC entity.In UM, the RLC entity performs functions such as segmenting and / or concatenating data received from a higher layer and adding an RLC header, but does not require data retransmission control. A UM RLC entity may be a unidirectional or bidirectional entity. If the UM RLC entity is unidirectional, it may be configured as a transmitting UM RLC entity or a receiving UM RLC entity. If the UM RLC entity is bidirectional, it may be configured as a UM RLC entity consisting of a transmitting side and a receiving side. In AM, the RLC entity may perform functions such as segmenting and / or concatenating data received from a higher layer, adding an RLC header, and controlling data retransmission. An AM RLC entity is a bidirectional entity and may be configured as an AM RLC consisting of a transmitting side and a receiving side. Note that data provided to a lower layer in TM and / or data provided from a lower layer may be referred to as a TMD PDU. Data provided to a lower layer in UM and / or data provided from a lower layer may be referred to as a UMD PDU. Furthermore, data provided to or from a lower layer in AM may be referred to as an AMD PDU. The RLC PDU format used in E-UTRA RLC may differ from the RLC PDU format used in NR RLC. RLC PDUs may include data RLC PDUs and control RLC PDUs. Data RLC PDUs may be referred to as RLC DATA PDUs (RLC Data PDUs). Control RLC PDUs may be referred to as RLC CONTROL PDUs (RLC Control PDUs).

[0073] An example of PDCP functions will be described. PDCP may be called a PDCP sublayer. PDCP may have a function for maintaining sequence numbers. PDCP may also have a header compression / decompression function for efficiently transmitting user data such as IP packets and Ethernet frames over wireless interfaces. 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 the EHC (Ethernet (registered trademark) Header Compression) protocol. PDCP may also have a data encryption / decryption function. PDCP may also have a data integrity protection / verification function. PDCP may also have a reordering function. PDCP may also have a PDCP SDU retransmission function. PDCP may also have a data discard function using a discard timer. PDCP may also have a duplication function. PDCP may also have a function for discarding duplicately received data. The PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. The PDCP PDU format used in E-UTRA PDCP may differ from that used in NR PDCP. PDCP PDUs may include data PDCP PDUs and control PDCP PDUs. The data PDCP PDU may be called a PDCP DATA PDU (PDCP Data PDU). The control PDCP PDU may be called a PDCP CONTROL PDU (PDCP Control PDU).

[0074] An example of the SDAP function will be described. The SDAP is a service data adaptation protocol layer. The SDAP may have the function of mapping the downlink QoS flow sent from the 5GC 110 to the terminal device via the base station device to a data radio bearer (DRB), and / or the function of mapping the uplink QoS flow sent from the terminal device to the 5GC 110 via the base station device to a DRB. The SDAP may also have the function of storing mapping rule information. The SDAP may also have the function of marking a QoS flow identifier (QoS Flow ID: QFI). Note that SDAP PDUs may include data SDAP PDUs and control SDAP PDUs. The data SDAP PDU may be called an SDAP DATA PDU (SDAP Data PDU). The control SDAP PDU may be called an SDAP CONTROL PDU (SDAP Control PDU). Note that one SDAP entity in the terminal device may exist for each PDU session.

[0075] An example of the functions of the RRC will be described. The RRC may have a broadcast function. The RRC may have a paging function from the EPC 104 and / or the 5GC 110. The RRC may have a paging function from the eNB 102 connected to the gNB 108 or the 5GC 110. The RRC may also have an RRC connection management function. The RRC may also have a radio bearer control function. The RRC may also have a cell group control function. The RRC may also have a mobility control function. The RRC may also have terminal device measurement reporting and terminal device measurement reporting control functions. The RRC may also have a QoS management function. The RRC may also have a radio link failure detection and recovery function. The RRC may use RRC messages to perform broadcasting, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, radio link failure detection and recovery, etc. Note that the RRC messages and parameters used in E-UTRA RRC may differ from the RRC messages and parameters used in NR RRC.

[0076] RRC messages may be sent using the logical channel BCCH, the logical channel PCCH, the logical channel CCCH, or the logical channel DCCH, and RRC messages sent using the DCCH are referred to as dedicated RRC signaling, or RRC signaling.

[0077] The RRC messages sent using the BCCH may include, for example, a Master Information Block (MIB), various types of System Information Blocks (SIBs), or other RRC messages.The RRC messages sent using the PCCH may include, for example, paging messages or other RRC messages.

[0078] RRC messages transmitted in the uplink (UL) direction using the CCCH may include, for example, an RRC setup request message (RRC Setup Request), an RRC resume request message (RRC Resume Request), an RRC reestablishment request message (RRC Reestablishment Request), an RRC system information request message (RRC System Info Request), etc. Also, for example, an RRC connection request message (RRC Connection Request), an RRC connection resume request message (RRC Connection Resume Request), an RRC connection reestablishment request message (RRC Connection Reestablishment Request), etc. Other RRC messages may also be included.

[0079] The RRC message transmitted in the downlink (DL) direction using the CCCH may include, for example, an RRC connection reject message (RRC Connection Reject), an RRC connection setup message (RRC Connection Setup), an RRC connection reestablishment message (RRC Connection Reestablishment Reject), an RRC connection reestablishment reject message (RRC Connection Reestablishment Reject), etc. Also, for example, an RRC reject message (RRC Reject), an RRC setup message (RRC Setup), etc. Also, other RRC messages may be included.

[0080] The RRC signaling sent in the uplink (UL) direction using the DCCH may include, for example, a Measurement Report message, an RRC Connection Reconfiguration Complete message, an RRC Connection Setup Complete message, an RRC Connection Reestablishment Complete message, a Security Mode Complete message, a UE Capability Information message, etc. Also, for example, a Measurement Report message, an RRC Reconfiguration Complete message, an RRC Setup Complete message, an RRC Reestablishment Complete message, an RRC Resume Complete message, a Security Mode Complete message, a UE Capability Information message, etc. Also, other RRC signaling may be included.

[0081] The RRC signaling sent in the downlink (DL) direction using the DCCH may include, for example, an RRC connection reconfiguration message, an RRC connection release message, a security mode command message, a UE capability inquiry message, etc. Also, for example, an RRC reconfiguration message, an RRC resume message, an RRC release message, an RRC reestablishment message, a security mode command message, a UE capability inquiry message, etc. Also, other RRC signaling may be included.

[0082] An example of the functions of the NAS will be described. The NAS may have an authentication function. The NAS may also have a function for performing mobility management. The NAS may also have a security control function.

[0083] The above-mentioned functions of PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS are merely examples, and some or all of the functions may not be implemented. Also, some or all of the functions of each layer may be included in other layers.

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

[0085] Note that when UE 122 is connected to the EPC, it does not have the RRC_INACTIVE state, but the E-UTRAN may initiate suspension of the RRC connection. When UE 122 is connected to the EPC, when the RRC connection is suspended, UE 122 may transition to the RRC_IDLE state while retaining the UE AS context and an identifier (resumeIdentity) used for resuming. A layer above the RRC layer of UE 122 (e.g., the NAS layer) may initiate the resumption of the suspended RRC connection when UE 122 retains the UE AS context, the E-UTRAN has permitted resumption of the RRC connection, and UE 122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state.

[0086] The definition of dormancy may be different for UE 122 connected to EPC 104 and UE 122 connected to 5GC 110. In addition, some or all of the procedures for UE 122 to return from dormancy may be different when UE 122 is connected to EPC (when UE 122 is dormant in RRC_IDLE state) and when UE 122 is connected to 5GC (when UE 122 is dormant in RRC_INACTIVE state).

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

[0088] The UE AS context held by the UE 122 may be information including all or some of the following: a current RRC configuration, a current security context, a PDCP state including a ROHC (Robust Header Compression) state, a C-RNTI (Cell Radio Network Temporary Identifier) ​​used in the source PCell, a cell identifier (cellIdentity), and a physical cell identifier of the source PCell. Note that the UE AS context held by one or all of the eNB 102 and the gNB 108 may include the same information as the UE AS context held by the UE 122, or may include information different from the information included in the UE AS context held by the UE 122.

[0089] The security context may be information that includes all or part of the following: encryption keys at the AS level, the Next Hop parameter (NH), the Next Hop Chaining Counter parameter (NCC) used to derive the next hop access key, an identifier for the selected AS level encryption algorithm, and a counter used for replay protection.

[0090] Next, the serving cell will be described. In a terminal device in an RRC connected state in which CA and / or DC, which will be described later, are not configured, the serving cell may be configured with one primary cell (PCell). In addition, in a terminal device in an RRC connected state in which CA and / or DC, which will be described later, are configured, multiple serving cells may refer to a set of multiple cells (set of cell(s)) configured with one or more special cells (SpCells) and all of one or more secondary cells (SCells). The SpCell may support PUCCH transmission and contention-based random access (CBRA), and the SpCell may be always activated. The PCell may be a cell used in the RRC connection establishment procedure when a terminal device in an RRC idle state transitions to an RRC connected state. The PCell may also be a cell used in the RRC connection re-establishment procedure in which the terminal device re-establishes the RRC connection. The PCell may also be a cell used in the random access procedure during handover. The PSCell may be a cell used for a random access procedure when adding a secondary node, which will be described later. The SpCell may be a cell used for purposes other than those described above.

[0091] When a group of serving cells configured for a terminal device is composed of an SpCell and one or more SCells, it may be considered that carrier aggregation (CA) is configured for the terminal device. Also, for a terminal device in which CA is configured, a cell providing additional radio resources to the SpCell may refer to an SCell.

[0092] A cell group configured by a base station device for a terminal device will now be described. A cell group may be configured with one SpCell. A cell group may also be configured with one SpCell and one or more SCells. That is, a cell group may be configured with one SpCell and, optionally, one or more SCells. A cell group may also be expressed as a set of cells (set of cell(s)).

[0093] Dual Connectivity (DC) may be a technology for performing data communication using radio resources of cell groups configured by a first base station device (first node) and a second base station device (second node). When DC or MR-DC (described later) is performed, a cell group may be added from the base station device to a terminal device. To perform DC, the first base station device may add a second base station device. The first base station device may be called a master node (MN). A cell group configured by the master node may be called a master cell group (MCG). The second base station device may be called a secondary node (SN). A cell group configured by the 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 device.

[0094] Furthermore, when DC is not configured, the cell group configured in the terminal device may be called an MCG. Furthermore, when DC is not configured, the SpCell configured in the terminal device may be a PCell. Furthermore, an NR in which DC is not configured may be called an NR standalone (NR SA).

[0095] Note that Multi-Radio Dual Connectivity (MR-DC) may be a technology that performs DC using E-UTRA for MCG and NR for SCG. MR-DC may also be a technology that performs DC using NR for MCG and E-UTRA for SCG. MR-DC may also be a technology that performs DC using NR for both MCG and SCG. MR-DC may be a technology included in DC. Examples of MR-DC that use 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 (NG-RAN E-UTRA-NR Dual Connectivity) that uses 5GC in the core network. Examples of MR-DC that use NR for MCG and E-UTRA for SCG include NE-DC (NR-E-UTRA Dual Connectivity) that uses 5GC in the core network. Examples of MR-DC that use NR for both MCG and SCG include NR-DC (NR-NR Dual Connectivity) that uses 5GC in the core network.

[0096] In addition, in a 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 the MCG and one MAC entity for the SCG. The MAC entity for the MCG in the terminal device may always be established in the terminal device in all states (such as RRC idle state, RRC connected state, and RRC inactive state). The MAC entity for the SCG in the terminal device may be created by the terminal device when an SCG is configured in the terminal device. The MAC entity for each cell group in the terminal device may be configured by the terminal device receiving RRC signaling from a base station device. When the MAC entity is associated with an MCG, the SpCell may refer to the PCell. When the MAC entity is associated with an SCG, the SpCell may refer to the primary SCG cell (PSCell). When the MAC entity is not associated with a cell group, the SpCell may refer to the PCell. The PCell, PSCell, and SCell are serving cells. In the EN-DC and the NGEN-DC, the MAC entity for the MCG may be an E-UTRA MAC entity, and the MAC entity for the SCG may be an NR MAC entity. Also, in the NE-DC, the MAC entity for the MCG may be an NR MAC entity, and the MAC entity for the SCG may be an E-UTRA MAC entity. Also, in the NR-DC, the MAC entities for the MCG and the SCG may both be NR MAC entities. The existence of one MAC entity for each cell group may be rephrased as the existence of one MAC entity for each SpCell. Also, the existence of one MAC entity for each cell group may be rephrased as the existence of one MAC entity for each SpCell.

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

[0098] In FIG. 4, the base station device creates an RRC message (step S400). The base station device may create an RRC message in order to deliver system information (SI) or a paging message. The base station device may also create an RRC message in order to transmit RRC signaling that causes a specific terminal device to perform a process. The process that the specific terminal device is to perform may include, for example, security-related settings, RRC connection reconfiguration, handover to a different RAT, RRC connection suspension, and RRC connection release. The RRC connection reconfiguration process may include, for example, radio bearer control (establishment, modification, release, etc.), cell group control (establishment, addition, modification, release, etc.), measurement configuration, handover, security key update, etc. The base station device may also create an RRC message in order to respond to RRC signaling transmitted from the terminal device. A response to an RRC signaling transmitted from a terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, etc. An RRC message includes information (parameters) for various information notifications and settings. These parameters may be fields of an RRC message and / or information elements, or field values ​​(including information elements). The structure of an RRC message may be described using a description method called ASN.1 (Abstract Syntax Notation One).

[0099] 4, the base station device then transmits the created RRC signaling to the terminal device (step S402). Next, the terminal device performs processing such as setting according to the received RRC signaling if necessary (step S404). After performing the processing, the terminal device may transmit RRC signaling as a response to the base station device (not shown).

[0100] RRC signaling may be used for other purposes, not limited to the above examples.

[0101] In the MR-DC, the RRC on the master node side may be used to transfer RRC signaling for SCG-side configuration (cell group configuration, radio bearer configuration, measurement configuration, etc.) between the terminal device and the UE. For example, in the EN-DC or the NGEN-DC, the E-UTRA RRC signaling transmitted and received between the eNB 102 and the UE 122 may include the NR RRC signaling in the form of a container. In the NE-DC, the E-UTRA RRC signaling transmitted and received between the gNB 108 and the UE 122 may include the E-UTRA RRC signaling in the form of a container. The RRC signaling for the SCG-side configuration may be transmitted and received between the master node and the secondary node.

[0102] Regardless of whether MR-DC is used or not, the RRC signaling for E-UTRA transmitted from eNB102 to UE122 may include RRC signaling for NR, and the RRC signaling for NR transmitted from gNB108 to UE122 may include RRC signaling for E-UTRA.

[0103] An example of parameters included in the message regarding the re-establishment of the RRC connection will be described with reference to FIGS.

[0104] 7 and 8, a message related to reconfiguration of an RRC connection may include an information element (CellGroupConfig information element) used for configuring, modifying, releasing, etc., a cell group of an NR MCG or SCG. A message related to reconfiguration of an RRC connection may include a CellGroupConfig information element for configuring an MCG and a CellGroupConfig information element for configuring an SCG independently. The CellGroupConfig information element may also be referred to as a cell group configuration information element or a cell group configuration.

[0105] The CellGroupConfig information element may include a cellGroupId information element as identifier information for identifying this cell group.

[0106] The CellGroupConfig information element may include an RLC-BearerConfig information element as information used to configure an RLC entity.

[0107] The CellGroupConfig information element may include a MAC-CellGroupConfig information element as information used to configure MAC parameters in the cell group.

[0108] The CellGroupConfig information element may include a PhysicalCellGroupConfig information element as information used to configure PHY (L1) parameters specific to the cell group.

[0109] The CellGroupConfig information element may include an SpCellConfig information element as information used to configure parameters for the SpCell of the cell group. The SpCellConfig information element may also be referred to as an SpCell configuration information element or an SpCell configuration.

[0110] The CellGroupConfig information element may include an SCellConfig information element for each SCell as information used to configure parameters for one or more SCells in the cell group. The SCellConfig information element may also be referred to as an SCell configuration information element or SCell configuration.

[0111] The SpCellConfig information element may include a ServingCellConfig information element as information used to configure UE-specific parameters for the SpCell. Also, the SCellConfig information element may include this ServingCellConfig information element as information used to configure UE-specific parameters for the SCell. The CellGroupConfig information element may include a ServingCellConfig information element for each serving cell to configure UE-specific parameters for the SpCell and each SCell.

[0112] The SpCellConfig information element may include a ReconfigurationWithSync information element, which is an information element including parameters necessary for a synchronous reconfiguration process from a source SpCell to a target SpCell. When the SpCellConfig information element of the MCG includes a ReconfigurationWithSync information element, the synchronous reconfiguration process to the target SpCell may be a handover. When the SpCellConfig information element of the SCG includes a ReconfigurationWithSync information element, the synchronous reconfiguration process to the target SpCell may be a PSCell addition or a PSCell modification.

[0113] The synchronized reconfiguration information element and the SCellConfig information element may include a ServingCellConfigCommon information element as information used to configure cell-specific parameters of the serving cell. The ServingCellConfigCommon information element may include parameters typically acquired from the SSB, MIB, or one or more SIBs of the cell when the terminal device accesses the cell from the idle state.

[0114] The synchronization-with-reconfiguration information element may include, for example, information on the value of the C-RNTI used in the cell group of the target SpCell. The synchronization-with-reconfiguration information element may include, for example, information required for executing a contention-free random access procedure in the target SpCell.

[0115] The ServingCellConfigCommon information element may include the physical cell identifier (physCellId) of the cell.

[0116] The ServingCellConfigCommon information element may include a DownlinkConfigCommon information element as information providing cell-specific (cell-common) downlink parameters. The DownlinkConfigCommon information element is also referred to as downlink common configuration.

[0117] The ServingCellConfigCommon information element may include an UplinkConfigCommon information element as information that provides cell-specific (cell-common) uplink parameters. The UplinkConfigCommon information element is also referred to as an uplink common configuration.

[0118] The ServingCellConfigCommon information element may include the value of N_{TA,offset} that applies to all uplink transmissions in that cell.

[0119] The ServingCellConfigCommon information element may include an NTN-Config information element as information required to connect to a network via NTN access.

[0120] The NTN-Config information element may include cell ephemeris information, parameters used for timing adjustment of uplink transmission, and / or uplink synchronization validity period information. The uplink synchronization validity period information may be information indicating a maximum period during which the terminal device may apply uplink synchronization assistance information included in the NTN-Config information element without needing to update it. The uplink synchronization validity period information may be a parameter named ntn-UlSyncValidityDuration. The uplink synchronization assistance information may include the ephemeris information and / or parameters used for timing adjustment of the uplink transmission.

[0121] The DownlinkConfigCommon information element may include a FrequencyInfoDL information element as basic information related to a downlink carrier and transmission on the downlink carrier. For example, the FrequencyInfoDL information element may include frequency information of an SSB.

[0122] The DownlinkConfigCommon information element may include a BWP-DownlinkCommon information element as the initial downlink BWP configuration of the cell. The BWP-DownlinkCommon information element is also referred to as a downlink BWP common configuration.

[0123] The BWP-DownlinkCommon information element may include a BWP information element as information for setting generic parameters of the BWP.

[0124] The BWP-DownlinkCommon information element may include a PDCCH-ConfigCommon information element as information for configuring cell-specific parameters for the PDCCH of this BWP. The PDCCH-ConfigCommon information element is also referred to as PDCCH common configuration.

[0125] The BWP-DownlinkCommon information element may include a PDSCH-ConfigCommon information element as information for configuring cell-specific parameters for the PDSCH of this BWP. The PDSCH-ConfigCommon information element is also referred to as PDSCH common configuration.

[0126] The PDCCH-ConfigCommon information element may include a SearchSpaceZero information element as information for setting parameters of a common search space (CSS) #0. This SearchSpaceZero information element may be included in the PDCCH-ConfigCommon information element only when the BWP is an initial downlink BWP.

[0127] The PDCCH-ConfigCommon information element may include a ControlResourceSetZero information element as information for setting parameters of a common CORESET#0 used in one or more common search spaces and one or more UE-specific search spaces. This ControlResourceSetZero information element may be included in the PDCCH-ConfigCommon information element only when the BWP is an initial downlink BWP.

[0128] The PDCCH-ConfigCommon information element may include a ControlResourceSet information element as information for configuring parameters of an additional common CORESET.

[0129] The PDCCH-ConfigCommon information element may include a list (commonSearchSpaceList) of information elements (SearchSpace information elements) indicating the configuration of one or more additional CSSs.

[0130] The PDCCH-ConfigCommon information element may include information (searchSpaceSIB1) indicating which CSS setting in the commonSearchSpaceList is the search space setting for the system information (SIB1).

[0131] The PDCCH-ConfigCommon information element may include information (searchSpaceOtherSystemInformation) indicating which CSS in the commonSearchSpaceList is used as the search space setting for system information (SIB2 and subsequent information).

[0132] The PDCCH-ConfigCommon information element may include information (pagingSearchSpace) indicating which CSS in the commonSearchSpaceList is used to configure the search space for the paging message.

[0133] Each of the above information elements may include information other than the information described above.

[0134] To execute synchronous reconfiguration, the terminal device may perform some or all of steps (A) to (E) of the following process RWS. "Executing synchronous reconfiguration" may be rephrased as "implementing synchronous reconfiguration" or "triggering synchronous reconfiguration." (Process RWS) (A) If the synchronous reconfiguration information element includes a frequencyInfoDL information element, the terminal device determines that the target SpCell is a cell located at the SSB frequency indicated by the frequencyInfoDL information element and indicated by the physical cell identifier included in the synchronous reconfiguration information element. If the synchronous reconfiguration information element does not include a frequencyInfoDL information element, the terminal device determines that the target SpCell is a cell located at the same SSB frequency as the source SpCell and indicated by the physical cell identifier included in the synchronous reconfiguration information element. (B) Initiate downlink synchronization to the target SpCell. (C) If the terminal device does not have timing information required for the random access procedure, acquire the MIB of the target SpCell. (C) Reset the MAC entity of the cell group to be subject to synchronous reconfiguration. (D) The value of the new UE identifier (newUE-Identity) included in the synchronized reconfiguration information element is applied as the C-RNTI for the cell group that is the target of synchronized reconfiguration. (E) Configure the lower layers of the RRC layer (PHY, etc.) according to the SpCell common configuration (ServingCellConfigCommon information element).

[0135] Measurement will now be described. Note that in the following description, a base station apparatus may be read as a network. The base station apparatus may configure a terminal apparatus in an RRC connected state to perform measurements. The base station apparatus may configure the terminal apparatus to report measurement results. The base station apparatus may notify the terminal apparatus of RRC signaling to cause the terminal apparatus to perform synchronization reconfiguration based on the reported measurement results. Additionally or alternatively, the base station apparatus may configure the terminal apparatus to perform conditional reconfiguration, which will be described later, based on the reported measurement results. The measurement configuration may be provided from the base station apparatus to the terminal apparatus by RRC signaling (for example, an RRCReconfiguration message or an RRCResume message).

[0136] The base station device may configure the terminal device to perform, for example, the following types of measurements: (a) NR measurements, (b) Inter-RAT measurements on E-UTRA frequencies, and (c) Inter-RAT measurements on UTRA-FDD frequencies.

[0137] The base station device may configure the terminal device to report the following measurement information based on, for example, SSB: (a) measurement results per SSB; (b) measurement results per cell based on SSB; and (c) SSB index.

[0138] The base station apparatus may configure the terminal apparatus to report the following measurement information based on, for example, CSI-RS: (a) Measurement results for each CSI-RS resource; (b) Measurement results for each cell based on CSI-RS; and (c) CSI-RS resource measurement identifiers.

[0139] The measurement configuration may be notified to the terminal device by an information element (IE) of RRC signaling. The IE indicating the measurement configuration (measurement configuration IE) may include some or all of one or more measurement object IEs indicating measurement objects, one or more reporting configuration IEs indicating reporting configuration, one or more measurement identities used to associate the measurement objects with the reporting configuration, a quantity configuration IE indicating a quantity configuration, a measurement gap configuration IE indicating a measurement gap configuration, and a serving cell quality threshold configuration (s-Measure configuration).

[0140] <Quantity Config> The quantity Config specifies the L3 filtering coefficient when the measurement object is NR and / or E-UTRA. The L3 filtering coefficient specifies the ratio between the latest measurement result and the past filtered measurement result. The filtering result may be used for event evaluation in the terminal device.

[0141] <Measurement gap configuration (measGapConfig)> The measurement gap configuration includes information on the length and period of the measurement gap. The measurement gap configuration may be set independently for each terminal device or for each predetermined frequency range.

[0142] <Measurement Identifier (measId)> The measurement identifier is used to associate (or associate or link) a measurement object with a reporting configuration. Specifically, it links a measurement object identifier (measObjectId) for uniquely identifying each measurement object with a reporting configuration identifier (reportConfigId) for uniquely identifying each reporting configuration. One measurement object identifier and one reporting configuration identifier are associated with each other in the measurement identifier. The measurement configuration may be configured so that measurement identifiers, measurement objects, and / or reporting configurations can be added, modified, or deleted.

[0143] <Measurement Objects> Measurement objects may be defined for each RAT, frequency, and / or subcarrier spacing.

[0144] The measurement object IE may include a measurement object NR (measObjectNR) IE indicating information of a measurement object whose measurement object associated with a measurement object identifier is NR, and a measurement object EUTRA (measObjectEUTRA) IE indicating information of a measurement object whose measurement object is E-UTRA. Also, the measurement object may include some or all of a measurement object UTRA (measObjectUTRA) IE indicating information of a measurement object whose measurement object is UTRA, a measurement object GERAN (measObjectGERAN) IE indicating information of a measurement object whose measurement object is GERAN, and a measurement object CDMA2000 (measObjectCDMA2000) IE indicating information of a measurement object whose measurement object is CDMA2000.

[0145] The NR IE to be measured may include some or all of the following: frequency information (ssbFrequency) of the block (SSB) containing the synchronization signal, subcarrier spacing of the SSB (ssbSubcarrierSpacing), information on the list of cells to be measured, information on the blacklist to be excluded from measurement, and information on the whitelist to be measured.

[0146] The information on the list of cells to be measured includes information on cells to be subject to event evaluation and measurement reporting, and may include physical cell IDs and cell-specific offsets (cellIndividualOffsets, which indicate measurement offset values ​​to be applied to neighboring cells).

[0147] <Reporting Configurations> The reporting configuration IE may include a reporting configuration NR (reportConfigNR) IE and / or a reporting configuration InterRAT (reportConfigInterRAT) IE associated with a reporting configuration identifier (reportConfigId).

[0148] The reporting configuration identifier is an identifier used to identify a reporting configuration for measurements. The reporting configuration IE may include information for NR measurement reporting, information for measurement reporting of RATs other than NR (some or all of UTRA, GERAN, CDMA2000, E-UTRA), and information for NR Sidelink measurement reporting. The reporting configuration NR (reportConfigNR) IE, which is an information element used for NR measurement reporting, may include information indicating a reporting type. The reporting type may include periodic, event triggered, etc. If the reporting type is event triggered, the reporting configuration NR IE may include information such as triggering criteria.

[0149] The reporting configuration NR IE may include some or all of the following: an event identifier (eventId), a trigger quantity (triggerQuantity), a hysteresis (hysteresis), a trigger time (timeToTrigger), a report quantity (reportQuantity), a maximum number of reporting cells (maxReportCells), a report interval (reportInterval), and a report count (reportAmount). The reporting configuration NR IE may also include trigger conditions for events used for conditional reconfiguration in NR.

[0150] <Regarding event trigger conditions> Multiple event trigger conditions for measurement reporting are defined, and each may have an entering condition and a leaving condition. A terminal device that satisfies the entering condition for an event specified by the base station device may transmit a measurement report to the base station device. Also, a terminal device that satisfies the leaving condition for an event specified by the base station device may transmit a measurement report to the base station device if the base station device has configured the terminal device to trigger a report when the leaving condition is satisfied (if reportOnLeave is included in the report configuration IE).

[0151] In addition, for reporting configurations for RATs other than NR, multiple triggering criteria for events used to report measurements in RATs other than NR may be defined. For example, if the measurement result of a neighboring cell (other RAT) is better than a threshold b1_Threshold set for each RAT after applying each parameter, event B1 occurs. Also, if the measurement result of the PCell is worse than a threshold b2_Threshold1 after applying each parameter and the measurement result of a neighboring cell (other RAT) is better than a threshold b2_Threshold2 set for each RAT after applying each parameter, event B2 may occur. Information about these events may be included in a reporting configuration InterRAT (reportConfigInterRAT) IE.

[0152] Measurement reporting will now be described. The terminal device transfers measurement results to the network based on the measurement configuration. For each measurement identifier for which a measurement reporting procedure is triggered, the terminal device sets the measurement results in a measurement report message. The measurement result may include information on the measurement identifier for which the measurement report is triggered. The measurement result may also include information on the RSRP, RSRQ, and / or average SINR of the serving cell derived based on the reference signal. The measurement result may also include information on the identifier of the serving cell. The measurement result may also include information on the RSRP, RSRQ, and / or average SINR of a neighboring cell derived based on the reference signal. The measurement result may also include information on the identifier of the neighboring cell. The reference signal may be SSB, CSI-RS, or another signal.

[0153] Conditional reconfiguration will now be described. The network configures one or more conditional reconfiguration information elements for the terminal device, thereby configuring candidate target SpCells associated with the conditional reconfiguration information elements for the terminal device. The terminal device evaluates the states of the configured candidate target SpCells. The terminal device performs the evaluation and applies one of the conditional RRC reconfiguration information elements included in the conditional reconfiguration information elements associated with one or more candidate target SpCells that satisfy an execution condition. The terminal device may also retain a list of entries (VarConditionalReconfig) described below for conditional reconfiguration.

[0154] The conditional reconfiguration may be referred to as a conditional handover if the candidate target SpCell is an SpCell (i.e., a PCell) of an MCG, and may be referred to as a conditional PSCell addition and / or a conditional PSCell modification if the candidate target SpCell is an SpCell (i.e., a PSCell) of an SCG.

[0155] As a setting process for conditional reconfiguration, a terminal device may, based on receiving information about conditional reconfiguration (e.g., a conditional reconfiguration information element), delete (remove) the conditional reconfiguration settings specified in the entry deletion list from the settings held by the terminal device if the information about the conditional reconfiguration includes an entry deletion list (condReconfigToRemoveList). Specifically, if an entry identifier (condReconfigId) included in the entry deletion list is included in the list of entries held by the terminal device, the terminal device may delete the entry corresponding to the entry identifier from the list of entries held by the terminal device.

[0156] In the following description, the list of conditional reset entries held by the terminal device will also be simply referred to as the entry list. In other words, the "entry list" in the following description refers to the list of conditional reset entries held by the terminal device unless otherwise specified. The conditional reset entry list may also be a variable named VarConditionalReconfig. The identifier of an entry will also be simply referred to as the entry identifier.

[0157] When the information regarding the conditional reconfiguration includes an entry add / modify list (condReconfigToAddModList), the terminal device may add or modify the conditional reconfiguration configuration included in the entry add / modify list to the configuration held by the terminal device as a configuration process for conditional reconfiguration. The entry add / modify list may be a list of one or more conditional reconfiguration information elements. Each entry may be configured by a conditional reconfiguration information element. The conditional reconfiguration information element may include an entry identifier, an execution condition, and a conditional RRC reconfiguration information element.

[0158] Specifically, when an entry identifier included in the addition modification list of an entry exists in an entry in the entry list, the terminal device may perform the following processes (A) and / or (B): (A) When an entry included in the addition modification list of an entry includes an execution condition (condExecutionCond), the execution condition of an entry in the entry list that matches the entry identifier of this entry is replaced with the execution condition included in the addition modification list of that entry. (B) When an entry included in the addition modification list of an entry includes a conditional RRC reconfiguration information element (condRRCReconfig), the conditional RRC reconfiguration information element in the entry list that matches the entry identifier of this entry is replaced with the conditional RRC reconfiguration information element included in the addition modification list of that entry.

[0159] Furthermore, if an entry identifier included in the entry addition / modification list is not included in the entry list, the terminal device may add a new entry corresponding to the entry identifier not included in the entry list to the entry list.

[0160] The entry deletion list may be a list of one or more entry identifiers to be deleted. Each entry included in the entry addition / modification list includes an entry identifier and may additionally include an execution condition and / or a conditional RRC reconfiguration information element. Each entry may be associated with one of one or more candidate target SpCells. The entry identifier may be an identifier used to identify each entry of the CHO, CPA, and CPC. The entry list may include one or more entries. Each entry may include one entry identifier, one or more execution conditions, and one conditional RRC reconfiguration information element. If the entry list held by the terminal device does not include any entries, the terminal device may hold an empty list.

[0161] The execution condition may be a condition that needs to be satisfied to trigger execution of the conditional reconfiguration. For example, a measurement identifier may be specified as the execution condition. Furthermore, the conditional RRC reconfiguration information element of the measurement event may be a message related to reconfiguration of the RRC connection that is applied when the execution condition is satisfied. The message related to reconfiguration of the RRC connection may be a message used to connect to a candidate target SpCell.

[0162] The terminal device may evaluate the execution conditions of the entries included in the entry list held by the terminal device. If the entry list held by the terminal device is empty or if the terminal device does not hold an entry list, the execution conditions do not need to be evaluated.

[0163] Execution of conditional RRC reconfiguration may mean, for example, that the terminal device evaluates whether a join condition or a leave condition of a measurement event associated with a measurement identifier indicated in an execution condition of an entry included in an entry list held by the terminal device is satisfied, and if the join condition of one or more measurement events is satisfied, applies a conditional RRC reconfiguration information element included in an entry including the execution condition. Applying a conditional RRC reconfiguration information element may mean executing an RRC reconfiguration procedure using the conditional RRC reconfiguration information element.

[0164] In addition, when the conditional RRC reconfiguration information element of each entry identified by the entry identifier includes a synchronized reconfiguration information element, the terminal device may determine that a cell whose value matches the physical cell identifier indicated in the synchronized reconfiguration information element is an applicable cell.

[0165] The terminal device may determine that a measurement event associated with a measurement identifier indicated by a certain execution condition is satisfied when a join condition for the measurement event associated with the applicable cell is satisfied. Also, the terminal device may determine that a measurement event associated with the measurement identifier is not satisfied when a leave condition for the measurement event associated with the measurement identifier indicated by a certain execution condition is satisfied. When the terminal device determines that all measurement events for a certain applicable cell are satisfied, it may regard this cell as a triggered cell and perform conditional reconfiguration.

[0166] If there are multiple entries that satisfy the execution conditions, the terminal device may select one entry from the multiple entries and apply the conditional RRC reconfiguration information element of the selected entry.

[0167] Based on the above description, various embodiments of the present invention will be described. Note that the above-described processes may be applied to processes that are omitted in the following description.

[0168] Fig. 5 is a block diagram showing the configuration of a terminal device (UE 122) in this embodiment. To avoid complicating the explanation, Fig. 5 shows only the main components closely related to this embodiment.

[0169] 5 includes a receiver 500 that receives control information (such as DCI, MAC control elements, and RRC signaling) from a base station device, a processor 502 that performs processing according to parameters included in the received control information, and a transmitter 504 that transmits the control information (such as UCI, MAC control elements, and RRC signaling) to the base station device. This base station device may be the eNB 102 or the gNB 108. The processor 502 may include some or all of the functions of various layers (e.g., the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processor 502 may include some or all of the physical layer processor (PHY processor), MAC layer processor (MAC processor), RLC layer processor (RLC processor), PDCP layer processor (PDCP processor), SDAP processor (SDAP processor), RRC layer processor (RRC processor), and NAS layer processor (NAS processor).

[0170] Fig. 6 is a block diagram showing the configuration of a base station device in this embodiment. To avoid complicating the explanation, Fig. 6 shows only main components closely related to this embodiment. This base station device may be an eNB 102 or a gNB 108.

[0171] The base station apparatus shown in FIG. 6 includes a transmitter 600 that transmits control information (DCI, RRC signaling, etc.) to UE 122, a processor 602 that creates control information (DCI, RRC signaling including parameters, etc.) and transmits it to UE 122, causing processing unit 502 of UE 122 to process the information, and a receiver 604 that receives control information (UCI, RRC signaling, etc.) from UE 122. Furthermore, processing unit 602 may include some or all of the functions of various layers (e.g., physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, processing unit 602 may include some or all of the functions of a physical layer processing unit, a MAC layer processing unit, an RLC layer processing unit, a PDCP layer processing unit, an SDAP processing unit, an RRC layer processing unit, and an NAS layer processing unit.

[0172] An example of the processing of the terminal device in this embodiment will be described with reference to FIG.

[0173] 9 is a diagram showing an example of processing by a terminal device (UE 122) in this embodiment. The processing unit 502 of the UE 122 receives first information and / or second information from a base station device (step S900). The processing unit 502 of the UE 122 determines whether a first identifier is included in an RRC reconfiguration information element included in the received second information (step S902). The processing unit 502 of the UE 122 performs an operation based on the determination (step S904).

[0174] The first information may include one or more information elements related to a cell, each of which may be identified by a first identifier. The information elements related to a cell may include settings related to different cells. The information elements related to a cell may be information elements used to configure cell-specific parameters. For example, the information elements related to a cell may include parameters typically acquired from the SSB, MIB, and / or one or more SIBs of the cell when the terminal device accesses the cell from an idle state. For example, the information elements related to a cell may be a ServingCellConfigCommon information element used to configure the cell-specific parameters of the cell in the terminal device. For example, the information elements related to a cell may be one or more information elements included in a reconfigurationWithSync information element, which is an information element used for synchronous reconfiguration to the cell. Furthermore, the first information may be information broadcast using a BCCH in the serving cell of the terminal device, information notified to the terminal device using a DCCH, or information notified to the terminal device using an MCCH. For example, the first information may be broadcast using SIB3 and / or SIB4, which are SIBs that broadcast information about neighboring cells, in the serving cell of the terminal device. Furthermore, for example, the first information may be broadcast using another SIB. In this case, for example, the SIB may include a list of neighboring cell information, and each of the neighboring cell information may include one of the information elements about the cell.

[0175] Furthermore, the first information may include information (first validity determination information) used by the terminal device to determine whether part or all of the first information is valid or invalid. Additionally or alternatively, the information elements regarding the cell may include information (second validity determination information) used by the terminal device to determine whether part or all of the information elements regarding the cell are valid or invalid. Additionally or alternatively, when the first information is broadcast by an SIB, if the value of a Value Tag for an SIB broadcasting the first information, among one or more Value Tags (Value Tag fields) broadcast in SIB1, is different from the value of a Value Tag for an SIB broadcasting the first information held in the terminal device, the terminal device may determine that the information of the SIB broadcasting the first information held in the terminal device is invalid. That is, the terminal device may determine that the first information held in the terminal device is invalid. Furthermore, the terminal device may determine that it does not hold valid information elements regarding the cell based on the determination that the first information is invalid. Furthermore, the terminal device may determine that it holds valid information elements regarding the cell based on determining that the first information is valid.

[0176] The first validity determination information may include first timer information. An RRC entity of the terminal device may start or restart a timer (first validity determination timer) based on acquiring the first timer information from the first information. The terminal device may determine that the first validity determination timer has expired when a period (time) set based on the first timer information has elapsed. The terminal device may determine that part or all of the first information held by the terminal device is invalid based on the expiration of the first validity determination timer. Furthermore, the terminal device may determine that part or all of the first information held by the terminal device is invalid based on the stop of the first validity determination timer. The first validity determination timer may be stopped by the terminal device based on the expiration of the first validity determination timer. Furthermore, the first validity determination timer may be stopped by the terminal device based on other conditions. In other words, the terminal device may determine that part or all of the first information held by the terminal device is valid based on the first validity determination timer being running (not stopped). For example, the terminal device may determine that all information elements related to the cell that are included in the first information and held by the terminal device are invalid based on the first validity determination timer being stopped.

[0177] The second validity determination information may include second timer information. An RRC entity of the terminal device may start or restart a timer (second validity determination timer) based on acquiring the second timer information from the first information. The terminal device may determine that the second validity determination timer has expired when the second validity determination timer has elapsed a period (time) set based on the second timer information. The terminal device may determine that some or all of the information elements related to the cell held by the terminal device are invalid based on the expiration of the second validity determination timer. Furthermore, the terminal device may determine that some or all of the information elements related to the cell held by the terminal device are invalid based on the stop of the second validity determination timer. The second validity determination timer may be stopped by the terminal device based on the expiration of the second validity determination timer. Furthermore, the second validity determination timer may be stopped by the terminal device based on other conditions. In other words, the terminal device may determine that some or all of the information elements related to the cell held by the terminal device are valid based on the second validity determination timer being running (not stopped). Furthermore, the second validity determination timer may not be included in the information elements related to the cell. The terminal device may determine that the first information is valid based on the information elements related to the cell not including the second validity determination timer. Furthermore, when the second validity determination timer is included in the information elements related to the cell, the terminal device may ignore the second validity determination timer. This allows the terminal device to determine that the first information is valid.

[0178] In addition, when the terminal device maintains both the first validity determination timer and the second validity determination timer, the terminal device may determine that some or all of the information elements related to the cell held by the terminal device are invalid based on whether either timer has expired or stopped. In other words, the terminal device may determine that some or all of the information elements related to the cell held by the terminal device are valid based on whether both timers are running (not stopped). Furthermore, the terminal device may discard the information elements related to the cell held by the terminal device based on whether the second validity determination timer has expired or stopped. In other words, the terminal device may consider that it does not hold the information elements related to the cell by discarding the information elements related to the cell held by the terminal device based on whether the second validity determination timer has expired or stopped.

[0179] Furthermore, if the terminal device has not acquired the first information in the current serving cell, it may determine that the first information held by the terminal device is invalid, and in addition or instead, it may determine that the terminal device does not hold valid first information.

[0180] Furthermore, if the terminal device has not acquired the first information in the current serving cell, it may determine that the information element regarding the cell held by the terminal device is invalid, or, in addition or instead, it may determine that the terminal device does not hold a valid information element regarding the cell.

[0181] The information element regarding the cell may be, for example, a ServingCellConfigCommon information element. Alternatively, the information element regarding the cell may be, for example, an information element including the ServingCellConfigCommon information element. The information element regarding the cell may include information required for connecting to a network via NTN access. For example, the information element regarding the cell may include an NTN-Config information element. In this case, for example, the timer information included in the second validity determination information may be uplink synchronization validity period information or other information different from the uplink synchronization validity period information. If the uplink synchronization validity period information is the timer information, the terminal device may start a second validity determination timer and determine that the second validity determination timer has expired based on the elapse of the period (time) indicated by the uplink synchronization validity period information.

[0182] The first identifier may be an identifier included in an information element regarding the cell. Alternatively, the first identifier may be an identifier that is not included in an information element regarding the cell, but is associated with an information element regarding the cell and included in the first information for notification. Alternatively, the first identifier may be an identifier that is not included in the first information and indicates the ordinal number of one or more set information elements regarding the cell. For example, the first identifier may be a physical cell identifier. For example, the first identifier may be configured with any or all combinations of a physical cell identifier, a frequency, and a subcarrier spacing. For example, the first identifier may be an identifier that is uniquely associated with any or all combinations of a physical cell identifier, a frequency, and a subcarrier spacing. For example, when the maximum number of information elements regarding the cell included in the first information is two or less, the first identifier may be one-bit information. Alternatively, when the maximum number of information elements regarding the cell included in the first information is four or less, the first identifier may be two-bit information.

[0183] The second information may be a message including an RRC reconfiguration information element, and may also be, for example, an RRC reconfiguration message. The second information may include a synchronized reconfiguration information element. For example, the second information may be an RRC reconfiguration message. Alternatively, for example, the second information may be a conditional RRC reconfiguration information element used in conditional reconfiguration. Alternatively, for example, the second information may be an information element or an RRC message notified to the terminal device by other RRC signaling.

[0184] An example of the operation of UE 122 in step S904 will be described. When the processing unit 502 of UE 122 determines that a first identifier is included in the RRC reconfiguration information element included in the received second information and determines that an information element related to the cell of the first information indicated by the first identifier, which is held by the terminal device, is valid, the processing unit 502 may configure a lower layer of the RRC layer (e.g., a PDCP layer, an RLC layer, a MAC layer, and / or a PHY layer) according to the information element related to the cell of the first information indicated by the first identifier. Furthermore, when the processing unit 502 of UE 122 determines that a first identifier is not included in the RRC reconfiguration information element included in the received second information, if the second information includes an information element related to the cell, the processing unit 502 may configure a lower layer of the RRC layer (e.g., a PDCP layer, an RLC layer, a MAC layer, and / or a PHY layer) according to the information element related to the cell included in the second information. Furthermore, the processing unit 502 of the UE 122 may apply the value of a new UE identifier (newUE-Identity) included in the synchronized reconfiguration information element of the second information as a C-RNTI for a cell group subject to synchronized reconfiguration, regardless of whether a first identifier is included in the RRC reconfiguration information element included in the received RRC signaling. Furthermore, when the processing unit 502 of the UE 122 determines that a first identifier is included in the RRC reconfiguration information element included in the received second information, if the processing unit 502 determines that the UE 122 does not hold information elements related to the cell indicated by the first identifier or that information elements related to the cell indicated by the first identifier held by the terminal device in the first information are invalid, the processing unit 502 may perform some or all of the following processes (A) to (F): (A) Do not apply (ignore) all RRC reconfiguration information elements included in the second information; (B) Generate RRC signaling and transmit it to the base station device; (C) Determine that a reconfiguration failure or a handover failure has occurred; and (D) Start an RRC reestablishment procedure. (E) Reacquiring the first information in the serving cell.(F) Obtaining information equivalent to an information element related to the cell of the first information indicated by the first identifier in the cell of the first information indicated by the first identifier.

[0185] In the above process (B), the RRC signaling may be, for example, a message (RRCReconfigurationComplete message) used to notify the network of completion of RRC reconfiguration. In this case, the processing unit 502 of the UE 122 may include, in the RRCReconfigurationComplete message, information indicating that the UE does not retain information elements related to the cell identified by the first identifier included in the second information. Furthermore, the RRC signaling may be, for example, a message (UEAssistanceInformation message) used to notify the network of UE assistance information. In this case, the processing unit 502 of the UE 122 may include, in the UEAssistanceInformation message, information indicating that the UE does not retain information elements related to the cell identified by the first identifier included in the second information. Furthermore, the information indicating that the UE does not retain information elements related to the cell identified by the first identifier included in the second information may be information indicating that the UE has not acquired information elements related to the cell identified by the first identifier included in the second information.

[0186] In step S904, the terminal device may set a period (time) applied to timer T304, which is a timer used to determine failure of synchronization reconfiguration, based on a parameter (e.g., parameter t304) for setting timer T304 included in the synchronization with reconfiguration information element of the second information. Timer T304 may be set to a value of the period (time) indicated by the parameter for setting timer T304, and may be started or restarted by the terminal device based on the terminal device receiving an RRC message including the synchronization with reconfiguration information element of the second information including the parameter for setting timer T304. The terminal device may determine that timer T304 has expired based on the elapse of the period (time) set for timer T304. The terminal device may determine that synchronization reconfiguration has failed based on the expiration of timer T304. Here, the processing unit 502 of the UE 122 may use, as a value to be set in the timer T304, a value obtained by adding a specific period (time) to the value of the period (time) indicated by the parameter for setting the timer T304, based on determining that the RRC reconfiguration information element included in the received second information includes a first identifier and that the terminal device does not hold an information element regarding the cell indicated by the first identifier, or that the information element of the first information held by the terminal device regarding the cell indicated by the first identifier is invalid. For example, the specific period (time) may be a predetermined period (time) or a period (time) set by the base station device via RRC signaling. When performing the above process (E) and / or process (F), the terminal device may use, as a value to be set in the timer T304, a value obtained by adding the specific period (time) to the value of the period (time) indicated by the parameter for setting the timer T304.

[0187] A terminal device having a measurement configuration configured therein may perform measurements based on the measurement configuration, include the measurement results in a measurement report message, and transfer the measurement results to the network. The terminal device may include identifier information of neighboring cells in the measurement report message. The terminal device may further include, in the measurement report message, information indicating whether it holds valid first information, or alternatively, whether it holds valid information elements related to the neighboring cells included in the first information.

[0188] For example, the terminal device may include, in the measurement report message, information indicating whether valid first information has been acquired. Additionally or alternatively, for example, the terminal device may include, in the measurement result, identifier information of one or more neighboring cells, and may include, in the measurement result, information indicating whether valid information elements related to the cell are held for each cell indicated by the identifier information of the neighboring cells.

[0189] The base station device may include, in the measurement configuration, information indicating whether or not information indicating whether the terminal device holds valid first information is to be included in the measurement result. Additionally or alternatively, the base station device may include, in the measurement configuration, information indicating whether or not information indicating whether the terminal device holds valid information elements regarding the neighboring cells included in the first information is to be included in the measurement result.

[0190] This allows the base station device to determine whether or not it is necessary to include information elements regarding the cell in the second information based on whether or not the terminal device holds valid first information and / or whether or not the terminal device holds valid information elements regarding the neighboring cell included in the first information.

[0191] In addition, the terminal device may transmit information indicating whether the terminal device holds valid first information and / or whether the terminal device holds valid information elements regarding the neighboring cell included in the first information to the base station device in an RRC reconfiguration complete message and / or a UE Assistance Information message.

[0192] In the above description, the processing unit 502 of the UE 122 may be a processing unit that performs processing of the RRC layer.

[0193] In addition, in the above description, "valid" and "not invalid" may be interchangeable. In addition, in the above description, "invalid" and "not valid" may be interchangeable.

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

[0195] In addition, in the above description, expressions such as "link to," "corresponding to," and "associate with" may be interchangeable.

[0196] In the above description, expressions such as "determined to be A," "A is set," and "A is included" may be interchangeable.

[0197] In the above description, "transition from X to Y" may be rephrased as "X becomes Y." Also, in the above description, "cause a transition" may be rephrased as "determine a transition."

[0198] In addition, in the above-described examples of processes or process flows, some or all of the steps may not be executed. In addition, in the above-described examples of processes or process flows, the order of the steps may be different. In addition, in the above-described examples of processes or process flows, some or all of the processing within each step may not be executed.

[0199] In the above explanation, "A may be replaced with B" may mean replacing A with B, as well as replacing B with A. Also, in the above explanation, when it is written that "C may be D" and "C may be E", it may also mean that "D may be E". Also, in the above explanation, when it is written that "F may be G" and "G may be H", it may also mean that "F may be H".

[0200] The program that runs on the device according to this embodiment may be a program that controls a central processing unit (CPU) or the like to make a computer function so as to realize the functions of this embodiment. The program or the information handled by the program is temporarily loaded into a volatile memory such as a random access memory (RAM) during processing, or stored in a nonvolatile memory such as a flash memory or a hard disk drive (HDD), and is read, modified, and written by the CPU as needed.

[0201] Note that a part of the device in the above-described embodiment may be realized by a computer. In this case, a program for realizing this control function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read and executed by a computer system. The "computer system" here refers to a computer system built into the device, including hardware such as an operating system and peripheral devices. Furthermore, the "computer-readable recording medium" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, etc.

[0202] Furthermore, the term "computer-readable recording medium" may also include a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, or a medium that stores a program for a certain period of time, such as a volatile memory within a computer system that serves as a server or client in such cases. The program may also be one that realizes part of the above-mentioned functions, or one that can realize the above-mentioned functions in combination with a program already stored in the computer system.

[0203] Furthermore, each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an electrical circuit, typically an integrated circuit or multiple integrated circuits. The electrical circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, controller, microcontroller, or state machine. The general-purpose processor or each of the aforementioned circuits may be composed of digital circuits or analog circuits. Furthermore, if advances in semiconductor technology result in the emergence of integrated circuit technology that replaces current integrated circuits, integrated circuits based on that technology may also be used.

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

[0205] Although this embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the gist of this embodiment. Furthermore, this embodiment can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this embodiment. Furthermore, configurations in which elements described in the above embodiment are substituted with elements that achieve the same effect are also included.

[0206] The present invention can be used in, for example, a communication system, a communication device (for example, a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (for example, a communication chip), or a program.

[0207] 100 E-UTRA 102 eNB 104 EPC 106 NR 108 gNB 110 5GC 112, 114, 116, 118, 120, 124 Interface 122 UE 200, 300 PHY 202, 302 MAC 204, 304 RLC 206, 306 PDCP 208, 308 RRC 310 SDAP 210, 312 NAS 500, 604 Receiver 502, 602 Processor 504, 600 Transmitter

Claims

1. A terminal device comprising: a receiving unit that receives an RRC setting message including a measurement configuration from a base station device; a transmitting unit that transmits a measurement report message to the base station device; and a processing unit that performs RRC layer processing, wherein the processing unit performs measurements based on the measurement configuration; and generates a measurement report message including identifier information of one or more neighboring cells based on the measurement configuration and the measurements, wherein the measurement report message includes information indicating whether or not valid first information corresponding to the neighboring cell identified by the identifier information is held, and the first information includes cell-specific parameters that are set in the terminal device when the neighboring cell identified by the identifier information becomes a serving cell.

2. A method applicable to a terminal device, comprising the steps of: receiving an RRC configuration message including a measurement configuration from a base station device; transmitting a measurement report message to the base station device; performing a measurement based on the measurement configuration; and generating a measurement report message including identifier information of one or more neighboring cells based on the measurement configuration and the measurement, wherein the measurement report message includes information indicating whether or not valid first information corresponding to a neighboring cell identified by the identifier information is held, and the first information includes cell-specific parameters that are set in the terminal device when the neighboring cell identified by the identifier information becomes a serving cell.

3. An integrated circuit implemented in a terminal device, which enables the terminal device to perform the following functions: receiving an RRC configuration message including a measurement configuration from a base station device; transmitting a measurement report message to a base station device; performing measurements based on the measurement configuration; and generating a measurement report message including identifier information of one or more neighboring cells based on the measurement configuration and the measurements, wherein the measurement report message includes information indicating whether or not valid first information corresponding to a neighboring cell identified by the identifier information is held, and the first information includes cell-specific parameters that are set in the terminal device when the neighboring cell identified by the identifier information becomes a serving cell.

Images