Terminal device, base station device, and wireless communication system

Abstract

When a signal is received from a base station device and a first signal indicating cell switching from the base station device to a first LTM candidate is received, the present invention releases a first bearer that is present in the current setting and is not present in a first setting for the first LTM candidate, and stores first information related to the first bearer. When second information related to a second bearer that is not present in the current setting and is present in the first setting for the first LTM candidate is stored in the second bearer, the second information and the first setting are both applied to the second bearer and the cell switching to the first LTM candidate is performed.

Description

Terminal device, base station device, and wireless communication system

[0001] The present invention relates to a terminal device, a base station device, and a wireless communication system.

[0002] Currently, wireless communication networks using mobile devices (smartphones, feature phones, etc.) are expanding. With the expansion of wireless communication, there is a demand for even faster speeds and larger capacities.

[0003] The 3rd Generation Partnership Project (3GPP), an international standardization project, is conducting technical studies and formulating standards for cellular mobile communication systems. For example, E-UTRA (Evolved Terrestrial Radio Access) has been standardized as a radio access technology (RAT: Radio Access Technology) for the 3.9th generation (3.9G) and the 4th generation (4G) of networks, and EPC (Evolved Packet Core) has been standardized as a core network (CN: Core Network) technology. In addition, NR (New Radio) has been standardized as a RAT for the 5th generation (5G), and 5GC (5G Core) has been standardized as a core network technology. These extension technologies are currently being continuously studied and standardized.

[0004] Technologies related to NR or 5G systems are described, for example, in the following Non-Patent Documents 1 to 12.

[0005] 3GPP TS38.300 V17.5.0 NR Overview Specification 3GPP TS38.211 V17.5.0 NR PHY Channel and Modulation Specification 3GPP TS38.321 V17.5.0 NR MAC Specification 3GPP TS38.322 V17.3.0 NR RLC Specification 3GPP TS38.323 V17.5.0 NR PDCP Specification 3GPP TS37.324 V17.0.0 NR SDAP Specification 3GPP TS38.304 V17.5.0 NR Idle Mode and Inactive Mode Specification 3GPP TS38.331 V17.5.0 NR RRC Specification RP-2235203GPP R2-22116423GPP R2-22117953GPP TS33.501 V17.11.05G System Security Specification

[0006] As one of the extension technologies, technical studies on improving mobility are being conducted. One of the items under study is a technology called LTM (L1 / L2-triggered mobility), which aims to achieve effects such as reducing delay time in mobility by changing the serving cell of a terminal device using layer 1 and / or layer 2 signaling (Non-Patent Document 9).

[0007] However, the specific method of LTM has not yet been determined as a standard specification, for example, the specific procedures for establishing and releasing radio bearers when performing cell change processing have not yet been determined.

[0008] Therefore, one object of the present disclosure is to provide a base station device, a terminal device, and a wireless communication system that enable efficient radio bearer establishment and release processing when performing cell change processing.

[0009] In one aspect, there is provided a terminal device having a receiving unit that receives a signal from a base station device and a processing unit, wherein when the receiving unit receives from the base station device a first signal instructing cell switching to a first LTM (L1 / L2-triggered mobility) candidate, the processing unit releases a first bearer that exists in the current configuration and does not exist in the first configuration for the first LTM candidate, stores first information related to the first bearer, and when the processing unit stores second information related to a second bearer that does not exist in the current configuration and exists in the first configuration for the first LTM candidate, applies the second information to the second bearer, applies the first configuration, and performs cell switching to the first LTM candidate.

[0010] In one aspect, a base station device is provided that includes a transmitting unit that transmits a signal to a terminal device and a processing unit, and when the transmitting unit transmits a first signal to the terminal device instructing cell switching to a first LTM (L1 / L2-triggered mobility) candidate, the processing unit causes the terminal device to release a first bearer that exists in the current setting but does not exist in the first setting for the first LTM candidate and store first information related to the first bearer, and when the terminal device stores second information related to a second bearer that does not exist in the current setting but exists in the first setting for the first LTM candidate, the processing unit applies the second information to the second bearer, applies the first setting, and performs cell switching to the first LTM candidate.

[0011] Also, in one aspect, there is provided a wireless communication system including a base station device and a terminal device that receives a signal from the base station device, wherein when the terminal device receives from the base station device a first signal instructing cell switching to a first LTM (L1 / L2-triggered mobility) candidate, the terminal device releases a first bearer that exists in the current configuration but does not exist in the first configuration for the first LTM candidate, stores first information related to the first bearer, and when a second bearer that does not exist in the current configuration but exists in the first configuration for the first LTM candidate has stored second information related to the second bearer, applies the second information to the second bearer, applies the first configuration, and performs cell switching to the first LTM candidate.

[0012] One disclosure enables communication that enables efficient radio bearer establishment and release processing when a terminal device performs cell change processing.

[0013] FIG. 1 is a diagram illustrating an example of the configuration of a communication system. FIG. 2 is a diagram illustrating an example of the configuration of a base station device. FIG. 3 is a diagram illustrating an example of the configuration of a terminal device. FIG. 4 is a diagram illustrating an example of a protocol stack in the U-Plane. FIG. 5 is a diagram illustrating an example of a protocol stack in the C-Plane. FIG. 6 is a diagram illustrating an example of a message format for RRC Reconfiguration. FIG. 7 is a diagram illustrating an example of the configuration of a cell group in a communication system. FIG. 8 is a diagram illustrating an example of synchronized reconfiguration. FIG. 9 is a diagram illustrating an example of a handover procedure using four-step random access. FIG. 10 is a diagram illustrating an example of an LTM sequence. FIG. 11 is a diagram illustrating an example of a sequence of cell switching failure detection and cell switching failure processing. FIG. 12 is a diagram illustrating an example of a first cell switching failure processing method. FIG. 13 is a diagram illustrating an example of a second cell switching failure processing method. FIG. 14 is a diagram illustrating an example of a third cell switching failure processing method. FIG. 15 is a diagram illustrating an example of a fourth cell switching failure processing method. FIG. 16 is a diagram illustrating an example of processing according to a selected cell. Fig. 17 is a diagram showing an example of parameters related to LTM, Fig. 18 is a diagram showing an example of a procedure for performing cell switching, and Fig. 19 is a diagram showing an example of a process in which a terminal device applies target settings.

[0014] The present embodiment will be described in detail below with reference to the drawings. The problems and examples in this specification are merely examples and do not limit the scope of the rights of the present application. In particular, even if the expressions used are different, the technology of the present application can be applied as long as they are technically equivalent, and do not limit the scope of the rights.

[0015] In this embodiment, the names and processes of each device, node, function, protocol, entity, signaling, message, parameter, etc. when the radio access technology is E-UTRA or NR and when the core network is EPC or 5GC are described, but the embodiment may be used for other radio access technologies. The names of each node and entity in each embodiment may be different names.

[0016] <Configuration Example of Communication System 10> Fig. 1 is a diagram showing a configuration example of a communication system 10. The communication system 10 has a terminal device 100, base station devices 200-1 and 200-2, and a core network 300. The communication system 10 may be a wireless communication system in which the terminal device 100 communicates with the base station device 200-1 or the base station device 200-2, or may be a wireless communication system in which the terminal device 100 communicates with the base station device 200-1 and the base station device 200-2 using MR-DC (Multi Radio Dual Connectivity) described below. When communicating using MR-DC, for example, the base station device 200-1 is a master base station device, and the base station device 200-2 is a secondary base station device. Hereinafter, the master base station device may be referred to as an MN (Master Node), and the secondary base station device may be referred to as an SN (Secondary Node).

[0017] The terminal device 100 is wirelessly connected to one or both of the base station device 200-1 and the base station device 200-2 and performs wireless communication. The RAT providing the wireless connection is, for example, E-UTRA or NR. The terminal device 100 is a terminal device that supports either or both of E-UTRA and NR.

[0018] The base station devices 200-1 and 200-2 (hereinafter, sometimes referred to as base station devices 200) are communication devices that are wirelessly connected to the terminal device 100 and perform wireless communication. The base station devices 200-1 and 200-2 are, for example, connected to each other via a wired line and perform communication. The base station device 200 is, for example, connected to the core network 300 via a wired line and performs communication. The base station device 200 is, for example, a base station device that is either an eNodeB (eNB) that provides E-UTRA as the RAT or a gNodeB (gNB) that provides NR as the RAT.

[0019] The core network 300 is a network corresponding to a certain generation. For example, the core network 300 is a 5GC that is a core network standardized for 5G, or an EPC that is a core network standardized for 4G.

[0020] The MR-DC implemented in the communication system 10 will be described in detail later.

[0021] 2 is a diagram illustrating an example of the configuration of the base station device 200. The base station device 200 is a communication device or a relay device having a CPU (Central Processing Unit) 210, a storage 220, a memory 230, a wireless communication circuit 240, and a network interface 250.

[0022] The storage 220 is an auxiliary storage device that stores programs and data, such as a flash memory, a hard disk drive (HDD), or a solid state drive (SSD). The storage 220 stores a wireless communication program 221 and a base station side program 222.

[0023] The memory 230 is an area into which the programs stored in the storage 220 are loaded. The memory 230 may also be used as an area in which the programs store data.

[0024] The wireless communication circuit 240 is a circuit that wirelessly connects to and communicates with the terminal device 100. The base station device 200 receives a signal transmitted from the terminal device 100 via the wireless communication circuit 240, and transmits a signal to the terminal device 100, for example.

[0025] The NI (network interface) 250 is, for example, a communication device that connects to other base station devices 200 and realizes inter-base station communication. The NI 250 is also, for example, a communication device that connects to the core network 300 (communication devices that constitute the core network 300) and performs communication. The NI 250 is, for example, a network interface card (NIC). The base station device 200 receives signals from other communication devices and transmits signals to other communication devices via the NI 250.

[0026] The CPU 210 is a processor that loads programs stored in the storage 220 into the memory 230, executes the loaded programs, configures each unit, and realizes each process.

[0027] The CPU 210 performs wireless communication processing by executing the wireless communication program 221. The wireless communication processing is processing for wirelessly connecting to the terminal device 100, communicating wirelessly with the terminal device 100, and relaying communication between the terminal device 100 and other communication devices.

[0028] The CPU 210 executes the base station side program 222 to configure a second transmitting unit, a second receiving unit, and a second processing unit, and perform base station side processing. When the base station device 200 communicates with the terminal device 100 using MR-DC, the base station side processing may include MR-DC master node processing and MR-DC secondary node processing. In this case, the MR-DC master node processing is processing for controlling the master node side of the MR-DC, and the MR-DC secondary node processing is processing for controlling the secondary node side of the MR-DC. In the MR-DC master node processing and the MR-DC secondary node processing, the base station device 200 performs communication corresponding to each type of MR-DC, which will be described later.

[0029] 3 is a diagram showing an example of the configuration of the terminal device 100. The terminal device 100 is a communication device having a CPU 110, a storage 120, a memory 130, and a wireless communication circuit 140.

[0030] The storage 120 is an auxiliary storage device such as a flash memory, HDD, or SSD that stores programs and data. The storage 120 stores a wireless communication program 121 and a terminal-side program 122.

[0031] The memory 130 is an area into which the programs stored in the storage 120 are loaded. The memory 130 may also be used as an area in which the programs store data.

[0032] The wireless communication circuit 140 is a circuit that wirelessly connects to and communicates with the base station device 200. The terminal device 100, for example, receives a signal transmitted from the base station device 200 via the wireless communication circuit 140 and transmits a signal to the base station device 200. The wireless communication circuit 140 is, for example, a network card that supports wireless connection.

[0033] The CPU 110 is a processor that loads programs stored in the storage 120 into the memory 130, executes the loaded programs, configures each unit, and realizes each process.

[0034] The CPU 110 performs wireless communication processing by executing the wireless communication program 121. The wireless communication processing is processing for wirelessly connecting to the base station device 200 and performing wireless communication with the base station device 200 or communication with another communication device via the base station device 200.

[0035] The CPU 110 executes the terminal-side program 122 to configure a transmitting unit, a receiving unit, and a processing unit, and to perform terminal-side processing. When the terminal device 100 communicates with the base station device 200 using MR-DC, the terminal-side processing may include terminal-side MR-DC processing. In this case, the terminal-side MR-DC processing is processing for controlling communication in the MR-DC. In the terminal-side MR-DC processing, the terminal device 100 performs communication corresponding to each type of MR-DC, which will be described later.

[0036] <Protocol Stack> An example of a protocol stack of the communication system 10 will be described. In the communication system 10, a series of protocols for transmitting and receiving data, shown in a hierarchical structure, is called a protocol stack. In the following example, a case will be described in which the base station device 200 is an eNB or a gNB, and the core network 300 is an EPC or a 5GC. In addition, the terminal device 100 (UE: User Equipment) is assumed to support one or both of E-UTRA and NR.

[0037] Below, we will explain the protocol stacks of the U-Plane (User Plane) and C-Plane (Control Plane). The U-Plane is used, for example, to send and receive user data in communications. The C-Plane is used, for example, to send and receive control signals (messages) in communications. In each embodiment, unless otherwise specified, "user data" or "control signal (message)" refers to either user data or control signal (message), or both.

[0038] 4 is a diagram showing an example of a protocol stack of the U-Plane when the core network 300 is 5GC. Also, FIG. 5 is a diagram showing an example of a protocol stack of the C-Plane when the core network 300 is 5GC. In FIGS. 4 and 5, PHY (PHYsical), MAC (Medium Access Control), RLC (Radio Link Control), PDCP (Packet Data Convergence Protocol), SDAP (Service Data Adaptation Protocol), RRC (Radio Resource Control), and NAS (Non Access Stratum) indicate the names of the layers. Hereinafter, PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS may be referred to as the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer, respectively. MAC, RLC, PDCP, and SDAP may be referred to as the MAC sublayer, RLC sublayer, PDCP sublayer, and SDAP sublayer, respectively. MAC, RLC, PDCP, and SDAP may be referred to as the MAC entity, RLC entity, PDCP entity, and SDAP entity, respectively. Note that when the core network 300 is the EPC, the protocol stack of the U-Plane is the protocol stack in FIG. 4 that does not include SDAP. That is, the protocol stack is composed of PHY, MAC, RLC, and PDCP. In addition, in the protocol stack of the C-Plane when the core network 300 is the EPC, the NAS exists in the AMF (Access and Mobility management Function) in FIG. 5, whereas the NAS exists in the MME (Mobility Management Entity).

[0039] The functions in each layer may be common or different between the E-UTRA and NR RATs. In the following description, if there is no specification of E-UTRA or NR, the functions are common to both E-UTRA and NR.

[0040] In each sublayer, data provided from and to an upper layer is called an SDU (Service Data Unit). That is, data provided from and to an upper layer to MAC, RLC, PDCP, and SDAP are called MAC SDU, RLC SDU, PDCP SDU, and SDAP SDU, respectively.

[0041] In each sublayer, data provided to and from the lower layer is called a PDU (Protocol Data Unit). That is, data provided from MAC, RLC, PDCP, and SDAP to the lower layer, and data provided from the lower layer to MAC, RLC, PDCP, and SDAP are called MAC PDU, RLC PDU, PDCP PDU, and SDAP PDU, respectively. RLC, PDCP, and SDAP also have control PDUs, which are sometimes called control PDUs. To distinguish them from control PDUs, other PDUs are sometimes called data PDUs.

[0042] In Figure 4, the U-Plane consists of PHY, MAC, RLC, PDCP, and SDAP, and terminates at the terminal device 100 (e.g., UE) and the base station device 200 (e.g., gNB).

[0043] An example of the function of the PHY will be described. The PHY is a wireless physical layer, and transmits control information and data between the terminal device 100 and the base station device 200 using a physical channel. The direction from the base station device 200 to the terminal device 100 is sometimes called the downlink (downlink, DL), and the direction from the terminal device 100 to the base station device 200 is sometimes called the uplink (uplink, UL). Furthermore, within the terminal device 100 and the base station device 200, the PHY is connected to the MAC, which is an upper layer, via a transport channel, and data moves between the PHY and the MAC via the transport channel. In the PHY, an RNTI (Radio Network Temporary Identifier) ​​is used to identify various control information.

[0044] An example of the functions of the MAC will be described. The MAC is a medium access control layer, and performs mapping of transport channels and logical channels (LCHs), multiplexing and demultiplexing of MAC SDUs, scheduling reports (SRs), error correction through hybrid automatic repeat reQuest (HARQ), priority control, etc. In the terminal device 100 and the base station device 200, the MAC is connected to the RLC, which is an upper layer, via a logical channel, and data moves between the MAC and the RLC via the logical channel. The logical channel may be identified by a logical channel identifier (LCID). The base station device 200 also uses a MAC control element (CE) to control the terminal device 100. The terminal device 100 also uses a MAC CE to send reports to the base station device 200.

[0045] RLC is a radio link control layer and has three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). On the transmitting side, RLC transfers PDUs, assigns sequence numbers (in the case of UM and AM), segments SDUs (in the case of UM and AM), and resegments SDUs (in the case of AM). On the receiving side, RLC reassembles SDUs (in the case of UM and AM), detects duplicates (in the case of AM), discards SDUs (in the case of UM and AM), and also re-establishes RLC on the transmitting and receiving sides. Segmented SDUs are called SDU segments. Furthermore, the RLC has a data retransmission function and / or a retransmission request function (ARQ: Automatic Repeat reQuest) (in the case of AM). In addition, the E-UTRA RLC also has functions such as data combining on the transmitting side, and reordering and in-order delivery on the receiving side.

[0046] PDCP is a packet data convergence protocol layer, and performs data transfer between the U-Plane and C-Plane, PDCP sequence number management, header compression / decompression, encryption / decryption, integrity protection / integrity verification, timer-based SDU discard, routing for split bearers, reordering and in-order delivery, etc. In E-UTRA PDCP, functions such as timer-based SDU discard, reordering and in-order delivery may be limited to the case of split bearers, which will be described later.

[0047] SDAP is a service data adaptation protocol layer that performs mapping between QoS (Quality of service) flows and Data Radio Bearers (DRBs) (described later), and marking QoS flow identifiers (QFIs) on downlink (DL) packets and uplink (UL) packets.

[0048] The upper layers of the U-Plane include, for example, IP (Internet Protocol), TCP (Transmission Control Protocol), UDP (User Datagram Protocol), Ethernet (registered trademark), and application layers. A layer including IP, TCP, UDP, Ethernet, etc. may be called a PDU layer. Furthermore, IMS (IP Multimedia Subsystem), which controls sessions, may be included in the application layer.

[0049] 5, the C-Plane of the AS (Access Stratum) is composed of PHY, MAC, RLC, PDCP, and RRC, and terminates at the terminal device 100 and the base station device 200. The C-Plane of the NAS is composed of the NAS, and terminates between the terminal device 100 and the AMF, which is a device in the core network 300. The PHY, MAC, RLC, and PDCP are the same as those in the U-Plane.

[0050] The RRC broadcasts system information (SI) related to the AS and NAS, performs paging, establishes / maintains / releases RRC connections between the terminal device 100 and the base station device 200, adds / changes / releases carrier aggregation (CA), adds / changes / releases dual connectivity (DC), performs security functions including security key management, establishes / configures / maintains / releases signaling radio bearers (SRBs) and data radio bearers (DRBs), performs mobility functions, controls terminal device measurement reports and reporting, detects and recovers from radio link failures (RLFs), and transfers NAS messages.

[0051] The NAS performs authentication, mobility management, security control, etc. on the core network side.

[0052] <Channels> The channels used in the communication system 10 will be described. Below, examples of channels corresponding to NR are shown, but the channels used are not limited to the following. In addition, channels with the same name can be used for the same or similar purposes in RATs other than NR, such as E-UTRA.

[0053] <1. Physical Channel> The PBCH (Physical Broadcast Channel) is a channel used for transmitting broadcast information from the base station device 200 to the terminal device 100 .

[0054] The PDCCH (Physical Downlink Control Channel) is a channel used to transmit downlink control information (Downlink Control Information: DCI) and the like from the base station device 200 to the terminal device 100.

[0055] The PDSCH (Physical Downlink Shared Channel) is a channel used to transmit data from an upper layer from the base station device 200 to the terminal device 100.

[0056] The PUCCH (Physical Uplink Control CHannel) is a channel used to transmit uplink control information (UCI) and the like from the terminal device 100 to the base station device 200.

[0057] A PUSCH (Physical Uplink Shared Channel) is a channel used to transmit data from an upper layer from the terminal device 100 to the base station device 200.

[0058] The PRACH (Physical Random Access Channel) is a channel used to transmit a random access preamble and the like from the terminal device 100 to the base station device 200 .

[0059] 2. Transport Channels The BCH (Broadcast Channel) is mapped to the PBCH, which is a physical channel.

[0060] The DL-SCH (Downlink Shared Channel) is mapped to the PDSCH, which is a physical channel.

[0061] The PCH (Paging Channel) is mapped to the PDSCH, which is a physical channel.

[0062] The UL-SCH (Downlink Shared Channel) is mapped to the PUSCH, which is a physical channel.

[0063] The Random Access Channel(s) (RACH) are mapped to the PRACH, which is a physical channel.

[0064] <3. Logical Channel> The BCCH (Broadcast Control Channel) is a downlink channel for broadcasting system information, and is mapped to the transport channel BCH or DL-SCH.

[0065] A PCCH (Paging Control Channel) is a downlink channel for carrying paging messages and is mapped to the PCH of the transport channel.

[0066] The CCCH (Common Control Channel) is a channel for transmitting control information (such as RRC messages) between the terminal device 100 and the base station device 200, and is a channel used for the terminal device 100 that does not maintain (does not have) an RRC connection with the base station device 200, with the downlink mapped to the transport channel DL-SCH and the uplink mapped to the transport channel UL-SCH.

[0067] The DCCH (Dedicated Control Channel) is a point-to-point bidirectional channel that transmits dedicated control information (such as RRC messages) between the terminal device 100 and the base station device 200, and is used for the terminal device 100 that has an RRC connection with the base station device 200, with the downlink mapped to the transport channel DL-SCH and the uplink mapped to the transport channel UL-SCH.

[0068] The DTCH (Dedicated Transport Channel) is a point-to-point bidirectional channel dedicated to a terminal, which transmits user information (user data), and the downlink is mapped to the DL-SCH transport channel, and the uplink is mapped to the UL-SCH transport channel.

[0069] The MCCH (MBS Control Channel) is a point-to-multipoint downlink channel used to transmit MBS (Multicast Broadcast Service) broadcast control information corresponding to one or more MTCHs (MBS Traffic Channels) from the base station device 200 to the terminal device 100. It is mapped to the transport channel DL-SCH.

[0070] MTCH is a point-to-multipoint downlink channel used to transmit MBS multicast session data or broadcast session data from the base station device 200 to the terminal device 100. It is mapped to the transport channel DL-SCH.

[0071] <RRC State (Mode)> The RRC state of the terminal device 100 is a state related to the RRC connection of the terminal device 100. A state in which an RRC connection with the base station device 200 is not established is called an RRC idle mode (RRC_IDLE). A state in which an RRC connection with the base station device 200 is established is called an RRC connected mode (RRC_CONNECTED). A state in which the RRC connection with the base station device 200 is temporarily suspended is called an RRC inactive mode (RRC_INACTIVE). Note that when the core network 300 is an EPC, the state in which the RRC connection with the base station device 200 is temporarily suspended may be called another name, such as RRC suspended, instead of being called an RRC inactive mode.

[0072] <RRC Message> The RRC message will be described. The RRC message is a message including information necessary for communication in a cell, and includes a Master Information Block (MIB), a System Information Block (SIB), etc. Parameters included in the RRC message may be called fields or information elements (IEs).

[0073] Further, the RRC message includes a message related to the establishment of an RRC connection. Examples of messages related to the establishment of an RRC connection include, for example, in the case of NR, an RRC setup request message (RRCSetupRequest), an RRC setup message (RRCSetup), and an RRC setup complete message (RRCSetupComplete). Examples of messages related to the establishment of an RRC connection include, for example, in the case of E-UTRA, an RRC connection setup request message (RRCConnectionSetupRequest), an RRC connection setup message (RRCConnectionSetup), and an RRC connection setup complete message (RRCConnectionSetupComplete).

[0074] The RRC message also includes a message related to the initial activation of Access Stratum (AS) security, such as a security mode command message.

[0075] Further, the RRC message includes a message related to the reconfiguration of the RRC connection. For example, in the case of NR, messages related to the reconfiguration of the RRC connection include an RRC reconfiguration message (RRCReconfiguration) and an RRC reconfiguration complete message (RRCReconfigurationComplete). For example, in the case of E-UTRA, messages related to the reconfiguration of the RRC connection include an RRC connection reconfiguration message (RRCConnectionReconfiguration) and an RRC connection reconfiguration complete message (RRCConnectionReconfigurationComplete). Note that messages related to the reconfiguration of the RRC connection include the establishment, setting, modification, release, and synchronization of radio bearers and cell groups, as described later, as well as the establishment, setting, modification, and release of measurement information.

[0076] After initial activation of AS security, the terminal device 100 receives the first RRC reconfiguration message from the base station device 200, thereby obtaining all settings or all minimum required settings necessary for communication (data communication) with the base station device 200 in the cell to which the terminal device 100 is connected. These all settings or all minimum required settings necessary for communication (data communication) with the base station device 200 may be referred to as, for example, complete settings.

[0077] After initial activation of AS security for the terminal device 100, the base station device 200 can transmit a first RRC reconfiguration message and then another RRC reconfiguration message to cause the terminal device 100 to update the settings required for communication (data communication) with the base station device 200. In this case, the base station device 200 transmits an RRC reconfiguration message containing a differential setting from the complete setting currently set in the terminal device 100. This differential setting is sometimes called a delta setting. When the terminal device 100 receives an RRC reconfiguration message including the delta setting, it generates a new setting by applying the delta setting to the complete setting currently being used.

[0078] Further, the RRC message includes a message related to the re-establishment of the RRC connection. Examples of messages related to the re-establishment of the RRC connection include, for example, in the case of NR, an RRC re-establishment request message (RRCReestablishmentRequest), an RRC re-establishment message (RRCReestablishment), and an RRC re-establishment completion message (RRCReestablishmentComplete). Examples of messages related to the establishment of the RRC connection include, for example, in the case of E-UTRA, an RRC connection re-establishment request message (RRCConnectionReestablishmentRequest), an RRC connection re-establishment message (RRCConnectionReestablishment), and an RRC connection re-establishment completion message (RRCConnectionReestablishmentComplete).

[0079] In addition, the RRC messages further include messages regarding the release or suspension of the RRC connection, messages regarding the resumption of the RRC connection, messages regarding the capabilities of the terminal device, messages regarding terminal information, messages regarding MCG failure information, and messages regarding SCG failure information.

[0080] In MR-DC, when the master node is an eNB, the eNB may configure the terminal device 100 regarding NR by including the NR RRC message and parameters received from the gNB, which is the secondary node, as a container in the E-UTRA RRC message and transmitting it to the terminal device 100. The terminal device 100 may also include a completion message for the NR configuration as a container in the E-UTRA RRC message and transmit it to the eNB, which is the master node.

[0081] Also, in MR-DC, when the master node is a gNB, the gNB may configure the terminal device 100 for E-UTRA by including the E-UTRA RRC message and parameters received from the eNB, which is the secondary node, as a container in the NR RRC message and transmitting it to the terminal device 100. The terminal device 100 may also include a completion message for the E-UTRA configuration in the NR RRC message as a container and transmit it to the gNB, which is the master node.

[0082] 6 is a diagram showing an example of a message format of RRC Reconfiguration. Format E1 is a parameter of RRC Reconfiguration.

[0083] RRC Reconfiguration has radioBearerConfig, radioBearerConfig2, masterCellGroup, secondaryCellGroup, masterKeyUpdate, and sk-counter as parameters.

[0084] radioBearerConfig and radioBearerConfig2 are radio bearer settings related to an MN-terminated bearer or an SN-terminated bearer, and include SRB settings, DRB settings, security settings, etc. The SRB settings (DRB settings) include an SRB identifier (DRB identifier), PDCP settings, a parameter indicating PDCP re-establishment, etc. The security settings include a parameter (keyToUse) indicating whether to use a master key or a secondary key. The SRB identifier and / or DRB identifier are called radio bearer identifiers.

[0085] The masterCellGroup and secondaryCellGroup are MCG settings and SCG settings, respectively, and include a cell group identifier, an RLC bearer setting, an SpCell setting, etc. The RLC bearer setting includes a logical channel identifier, an RLC setting, a radio bearer identifier (SRB identifier or DRB identifier) ​​associated with the RLC bearer, etc. The SpCell setting includes information necessary for synchronized reconfiguration, etc.

[0086] masterKeyUpdate contains the information necessary for a master key update.

[0087] The sk-counter contains the information necessary for secondary key generation.

[0088] Format E11 is a diagram showing an example of parameters of RadioBearerConfig included in RRCReconfiguration.

[0089] Format E12 is a diagram showing an example of parameters of CellGroupConfig included in RRCReconfiguration.

[0090] Format E111 is a diagram showing an example of the SRB-ToAddMod parameters included in RadioBearerConfig.

[0091] Format E112 is a diagram showing an example of the DRB-ToAddMod parameters included in RadioBearerConfig.

[0092] Format E113 is a diagram showing an example of parameters of SecurityConfig included in RadioBearerConfig.

[0093] Format E121 is a diagram showing an example of parameters of RLC-BearerConfig included in CellGroupConfig.

[0094] Format E122 is a diagram showing an example of parameters of SpCellConfig included in CellGroupConfig.

[0095] <Radio Bearer> An example of a radio bearer in the communication system 10 will now be described.

[0096] <1. Signaling Radio Bearer> A signaling radio bearer (SRB) is a radio bearer for transmitting RRC messages and NAS messages.

[0097] SRB0 is the radio bearer for RRC messages that use the CCCH logical channel.

[0098] SRB1 is a radio bearer for RRC messages and NAS messages that uses the DCCH logical channel and is established before SRB2, which will be described later, is established.

[0099] SRB2 is a radio bearer for transmitting and receiving NAS messages, transmitting RRC messages including logged measurement information, etc., and uses the DCCH logical channel. The priority of SRB2 is lower than that of SRB1, and it may be set by the base station apparatus 200 after AS security is activated.

[0100] SRB3 is a radio bearer for RRC messages when EN-DC, NGEN-DC, or NR-DC is set in the terminal device 100, and uses the DCCH logical channel. Note that EN-DC, NGEN-DC, and NR-DC are types of MR-DC, and details of the types of MR-DC will be described later.

[0101] <2. Data Radio Bearer> A data radio bearer (DRB) is a radio bearer for transmitting user data.

[0102] <SRB and DRB Protocol Configuration> The SRB and DRB protocol configuration of the terminal device 100 will be described.

[0103] SRB0 does not have a PDCP entity and is configured with an RLC bearer. The RLC bearer is configured with an RLC entity and a MAC logical channel. The mode of the RLC entity of SRB0 is TM.

[0104] Each of SRB1 and SRB2 consists of one PDCP entity and one or more RLC bearers, where the RLC entity is in AM mode.

[0105] SRB3 consists of one PDCP entity and one RLC bearer, and the mode of the RLC entity is AM.

[0106] A DRB consists of one PDCP entity and one or more RLC bearers. The mode of the RLC entity is UM or AM. A DBR may be called a UM DBR if the RLC entity is UM, and may be called an AM DRB if the RLC entity is AM. Furthermore, a DRB is associated with one SDAP if the core network 300 is 5GC, and is associated with one EPS bearer (or EPS bearer identity) if the core network 300 is EPC.

[0107] It is assumed that one MAC entity exists for each cell group described below.

[0108] <Cells and Cell Groups> The cells and cell groups (CG) configured in the terminal device 100 will be described.

[0109] A cell group may be composed of one special cell (SpCell). A cell group may also be composed of one SpCell and one or more secondary cells (SCell). An SpCell in a master cell group (MCG) described later may be referred to as a primary cell (PCell). An SpCell in a secondary cell group (SCG) described later may be referred to as a primary SCG cell (PSCell).

[0110] The PCell is a primary frequency cell and is used to establish an RRC connection or re-establish an RRC connection. That is, when establishing an RRC connection or re-establishing an RRC connection, the cell selected by the terminal device 100 becomes the PCell. Furthermore, when the base station device 200 requests a handover (described later) from the terminal device 100, a new PCell designated by the base station device 200 is used for random access.

[0111] The SCell is a cell that provides additional radio resources in addition to the SpCell when carrier aggregation (CA) is configured in the terminal device 100.

[0112] The PSCell is a cell of the primary frequency on the SCG side. The PSCell is designated by the base station device 200 and is used for random access when adding or changing a PSCell in the SCG.

[0113] Note that the cell that the terminal device 100 in the RRC connected state uses for communication with the base station device 200 may be called the serving cell. When CA is not configured, the SpCell is the serving cell, and when CA is configured, the SpCell and SCell are the serving cells.

[0114] The MCG is a CG when DC (Dual Connectivity) is not set in the terminal device 100, or a CG that belongs to a master node (MN: Master Node) when DC is set in the terminal device 100. DC is a technology in which the terminal device 100 is wirelessly connected to a base station device 200 that is the master node and a base station device 200 that is a secondary node (SN: Secondary Node), and performs wireless communication using the carriers (cell groups) of the respective base station devices 200.

[0115] The SCG is a CG belonging to a secondary node that is set in addition to the MCG when a DC is set in the terminal device 100.

[0116] FIG. 7 is a diagram showing an example of the configuration of a cell group in the communication system 10. In FIG. 7, the master node (MN) is the base station device 200-1, and the secondary node (SN) is the base station device 200-2. The master node is the base station device 200 that provides a C-Plane connection to the core network 300 in DC. The secondary node is the base station device 200 that does not provide a C-Plane to the core network 300 in MR-DC, but provides additional radio resources to the terminal device 100. In FIG. 7, the MCG is composed of one PCell and two SCells. Also, in FIG. 7, the SCG is composed of one PSCell and two SCells.

[0117] The base station device 200 may set a BWP (BandWidth Part) for the cell set for the terminal device 100, and adjust the use of a limited frequency band from the entire frequency band of the cell. The BWP may be configured from a portion of the frequency band of each cell. Furthermore, multiple BWPs (for example, up to four) may be set for each cell. The BWP may be set by an RRC reconfiguration message. In each cell, the BWP to be used may be specified or switched by an RRC reconfiguration message or by using DCI.

[0118] <Reconfiguration with synchronization> Reconfiguration with synchronization will be described. Reconfiguration with synchronization (Reconfiguration With Sync) indicates a procedure executed in the terminal device 100 by including a parameter indicating that reconfiguration with synchronization is to be performed (reconfigurationWithSync: hereinafter, may be referred to as a reconfiguration parameter with synchronization) in an RRC reconfiguration message (RRCReconfiguration) transmitted from the base station device 200 to the terminal device 100.

[0119] The synchronized reconfiguration parameters are included separately under parameters for MCG configuration (hereinafter may be referred to as MCG configuration parameters) and under parameters for SCG configuration (hereinafter may be referred to as SCG configuration parameters). In other words, when included under the MCG configuration parameters, it means synchronized reconfiguration of the MCG, and when included under the SCG configuration parameters, it means synchronized reconfiguration of the SCG.

[0120] The synchronized reconfiguration is a procedure in which the terminal device 100 changes the SpCell, and includes operations such as random access to the new (target, changed to) SpCell, MAC reset, and PDCP data recovery (in the case of AM DRB).

[0121] The process when the synchronization-enabled reconfiguration parameters are included under the MCG configuration parameters may be called handover. The process when the synchronization-enabled reconfiguration parameters are included under the SCG configuration parameters may be called PSCell addition and / or PSCell change. The source PCell / PSCell may be called source PCell / source PSCell, and the destination PCell / PSCell may be called target PCell / target PSCell. Since synchronization-enabled reconfiguration may involve CA, the term serving cell may be used, and the cells may be referred to as source serving cell and target serving cell. The term "serving" may also be omitted, and the cells may be referred to as source cell and target cell.

[0122] The terminal device 100 may generate the target cell configuration by applying the delta configuration included in the RRC reconfiguration message to the source cell configuration.

[0123] Furthermore, synchronized re-establishment may involve changing security keys. In this case, in addition to the above, PDCP re-establishment is also performed.

[0124] When the security key is changed, a new key is generated by the RRC of the terminal device 100, and the PDCP is re-established, so that the new key is applied to the PDCP.

[0125] 8 is a diagram showing an example of processing when synchronization-related reconfiguration parameters are included under parameters for configuring an MCG. The synchronization-related reconfiguration parameters include settings such as a target PCell configuration, a new C-RNTI (Cell Radio Network Temporary Identifier), RACH configuration, and a timer for detecting handover failure. The terminal device 100 performs random access (RA) on the target PCell in accordance with the settings, and changes the current source PCell to the target PCell (S1).

[0126] <Random Access During Handover> Random access during handover includes contention-free random access (CFRA), which is random access without contention, and contention-based random access (CBRA), which is random access with contention, and each of these can be performed in four steps or two steps.

[0127] 9A and 9B are diagrams showing handover procedures using four-step random access, where Fig. 9A shows the handover procedure using four-step CFRA and Fig. 9B shows the handover procedure using four-step CBRA.

[0128] The sequence of FIG. 9A will be described.

[0129] The base station device 200 transmits an RRC reconfiguration message including synchronization-attached reconfiguration parameters to the terminal device 100 (S901).

[0130] The terminal device 100 executes a handover by 4-step CFRA when the synchronization-with reconfiguration parameters include a 4-step CFRA configuration and when, among the reference signals specified in the 4-step CFRA configuration, there is a reference signal whose RSRP (Reference Signal Received Power) is equal to or greater than a threshold. Also, the terminal device 100 executes a handover by 2-step CFRA when the synchronization-with reconfiguration parameters include a 2-step CFRA configuration and when, among the reference signals specified in the 2-step CFRA configuration, there is a reference signal whose RSRP is equal to or greater than a threshold. Furthermore, if the synchronized reconfiguration parameters do not include a 4-step CFRA setting or a 2-step CFRA setting, or if a 4-step CFRA setting or a 2-step CFRA setting is included but among the reference signals specified in the 4-step CFRA setting or the 2-step CFRA setting, there is no reference signal whose RSRP is greater than or equal to a threshold, the terminal device 100 performs a 4-step or 2-step CBRA.

[0131] The terminal device 100 transmits a random access preamble (RA preamble) to the base station device 200 via the target PCell (S902).

[0132] Upon receiving the random access preamble (S902), the base station device 200 transmits a random access response (RA response) (S903).

[0133] In the case of CFRA, the preamble is included in the CFRA configuration, so contention resolution is not required. Therefore, the handover is successful when the terminal device 100 receives a random access response from the target PCell.

[0134] When the terminal device 100 receives the random access response (S903), it transmits an RRC reconfiguration complete message, which is a response message to the RRC reconfiguration message, to the base station device 200 via the target serving cell (S904).

[0135] Next, the sequence of FIG. 9B will be described.

[0136] The base station device 200 transmits an RRC reconfiguration message including synchronization-enabled reconfiguration parameters to the terminal device 100 (S905). Since the synchronization-enabled reconfiguration parameters do not include a CFRA setting, the terminal device 100 executes a handover (two steps or four steps) using CBRA.

[0137] The terminal device 100 transmits a random access preamble to the base station device 200 via the target PCell (S906).

[0138] Upon receiving the random access preamble (S906), the base station device 200 transmits a random access response (S907).

[0139] In the case of CBRA, an arbitrary random access preamble is used, which may conflict with a random access preamble transmitted by another terminal device. Therefore, when the terminal device 100 receives the random access response (S907), the handover is not considered to be successful.

[0140] When the terminal device 100 receives the random access response (S907), it transmits an RRC reconfiguration completion message to the base station device 200 via the target serving cell (S908).

[0141] Upon receiving the RRC reconfiguration complete message (S908), the base station device 200 transmits a MAC CE indicating contention resolution in the target serving cell to the terminal device 100 (S909).

[0142] In the case of CBRA, the handover is successful when the terminal device 100 receives a MAC CE (S909) indicating contention resolution.

[0143] That is, in a four-step CFRA handover, the RRC reconfiguration complete message is sent (S904) after the handover is successful, but in a four-step CBRA handover, the RRC reconfiguration complete message is sent (S908) before the handover is successful.

[0144] Furthermore, if the uplink resources allocated in step S907 are sufficiently large, the terminal device 100 can transmit uplink data generated in the DRB in addition to the RRC reconfiguration completion message in step S908. That is, in a four-step handover using CBRA, there is a possibility that uplink data generated in the DRB will be transmitted before the handover is successful.

[0145] In the case of a handover by two-step random access, in both CBRA and CFRA, the terminal device 100 transmits an RRC reconfiguration complete message in step S904 after transmitting the random access preamble in step S902 and before receiving the random access response in step S903. That is, in the case of a handover by two-step random access, in either the case of CFRA or CBRA, the RRC reconfiguration complete message is transmitted before the handover is successful, and therefore, uplink data generated in the DRB before the handover is successful may be transmitted.

[0146] Furthermore, in handovers in E-UTRA, RACH-less handover, which is handover without random access, may be performed. In RACH-less handover, an RRC reconfiguration complete message is transmitted from the target serving cell to the base station device 200 without performing random access, and the handover is successful when the target serving cell receives a MAC CE indicating contention resolution from the base station device 200. In other words, in RACH-less handover, the RRC reconfiguration complete message is sent before the handover is successful, and therefore, there is a possibility that uplink data generated in the DRB before the handover is successful may be transmitted.

[0147] <Handover Failure Processing> If the terminal device 100 receives an RRC reconfiguration message including a synchronization-enabled reconfiguration parameter and the handover is not successful within a certain time, the handover fails. The handover not being successful within the certain time may mean that the timer for detecting handover failure, which starts when the terminal device 100 receives an RRC reconfiguration message including a synchronization-enabled reconfiguration parameter, expires before the handover is successful.

[0148] If the handover fails, the terminal device 100 restores the settings to those used in the source PCell and performs a procedure to re-establish the RRC connection. When restoring the settings to those used in the source PCell, the values ​​of the state variables in each entity of each radio bearer are also restored to the values ​​used in the source (values ​​immediately before the handover process).

[0149] In the RRC connection re-establishment procedure, the terminal device 100 performs cell selection, and if an NR cell is selected, it transmits an RRC re-establishment request message (RRCReestablishmentRequest) to the base station device 200. The RRC re-establishment request message is transmitted through SRB0. Since no PDCP entity exists in SRB0, security processing by PDCP is not performed on the RRC re-establishment request message. Furthermore, when an RRC re-establishment message (RRCReestablishment), which is a response message to the RRC re-establishment request message, is received from the base station device 200, the security key of the terminal device 200 is updated.

[0150] <Conditional Handover> A conditional handover (CHO) is a handover that is executed (initiated) by the terminal device 100 when one or more handover execution conditions are satisfied. The terminal device 100 receives an RRC reconfiguration message including conditional reconfiguration parameters from the base station device 200 and stores the conditional reconfiguration parameters. The conditional reconfiguration parameters include one or more pairs of configuration parameters for a PCell changeover target candidate, including synchronization reconfiguration parameters, and execution condition parameters for executing a handover to the PCell changeover target candidate. The execution condition parameters include, for example, parameters related to measurement configuration. Upon receiving the conditional reconfiguration parameters, the terminal device 100 starts cell measurement, and when any PCell of the measured cells satisfies the execution conditions, the terminal device 100 applies the configuration parameters of the PCell changeover target candidate for the PCell that satisfies the execution conditions and performs a conditional handover to the PCell. After the conditional handover is successful, the terminal device 100 releases the conditional reset parameters.

[0151] The conditional reconfiguration parameters can include one or more pairs of SCG-side configuration, i.e., configuration parameters of a PSCell change destination candidate and execution condition parameters for executing a change to the PSCell change destination candidate. Upon receiving the SCG-side conditional reconfiguration parameters, the terminal device 100 starts measuring the execution conditions, and if the measurement result satisfies the execution conditions, performs a conditional PSCell change (CPC).

[0152] In a conditional handover, handover failure is detected in the same way as in a non-conditional handover (hereinafter, sometimes simply referred to as handover), and processing after the handover failure is performed. In a conditional handover failure or in a procedure for re-establishing an RRC connection after a handover failure, if the selected cell is a PCell changeover candidate, the terminal device 100 can attempt handover and recover the RRC connection by transmitting an RRC reconfiguration complete message instead of transmitting an RRC re-establishment request message to the base station device 200. Note that, if the cell selected by the terminal device 100 is a PCell changeover candidate, the terminal device 100 can transmit an RRC reconfiguration complete message instead of transmitting an RRC re-establishment request message to the base station device 200 only if a conditional reconfiguration attempt parameter (attemptCondReconfig), which is a parameter that permits this processing, is set in the terminal device 100.

[0153] <AS Security and Key Stream> The AS security processing is performed in the PDCP entity of the radio bearer other than SRB0, using security keys (ciphering key, integrity protection key) generated by the RRC. The AS security processing includes ciphering and integrity protection, which are performed using the ciphering key and integrity protection key, respectively.

[0154] When a PDCP entity of each radio bearer receives a PDCP SDU from a higher layer, it performs AS security processing on the received PDCP SDU using an input called a key stream, which consists of four elements, for example, KEY, COUNT, BEARER, and DIRECTION.

[0155] KEY indicates, for example, a security key.

[0156] COUNT is one of the state variables of the PDCP entity, and indicates, for example, a sequence number. The COUNT value is initially set to '0' and is incremented by 1 each time a PDCP PDU is passed to a lower layer. The maximum value of the COUNT value is, for example, 2^32 minus 1, i.e., '4294967295'.

[0157] BEARER indicates, for example, the value of a radio bearer identifier. DIRECTION indicates whether it is an uplink or a downlink, and is '0' for an uplink and '1' for a downlink.

[0158] In AS security, from a security viewpoint, key stream reuse is prohibited. For example, when the terminal device 100 transmits data from a certain radio bearer, it is prohibited to perform AS security processing using a COUNT value previously used on this radio bearer unless the security key is updated.

[0159] The definition of the term "keystream" may vary slightly depending on the specification. In this embodiment, the keystream will be explained as consisting of four elements: KEY, COUNT, BEARER, and DIRECTION.

[0160] [Embodiments] Each embodiment will be described below.

[0161] <L1 / L2 Triggered Mobility> An example of an overview of L1 / L2 Triggered Mobility (LTM), the specifications of which are currently being developed, will be described.

[0162] Fig. 17 is a diagram showing an example of parameters related to LTM included in the RRCReconfiguration message. Note that the parameters described in Fig. 6 are omitted in Fig. 17. Furthermore, parameters other than the example parameters shown in Fig. 17 may be included. Furthermore, the names of the parameters are merely examples and do not have to be as shown.

[0163] Format E2 is a parameter of RRC Reconfiguration. RRC Reconfiguration includes ltm-Config, which means LTM configuration. If LTM-Config is included in SetupRelease, ltm-Config means that the LTM configuration is newly configured or changed. If SetupRelease does not include any ltm-Config, it means that the LTM configuration is resolved.

[0164] Format E21 is a parameter included in the LTM setting. ltm-ReferenceConfiguration is a reference setting, which will be described later. ltm-CandidateToAddModList is a list of settings of candidate cell change destinations. In other words, ltm-CandidateToAddModList includes one or more settings of candidate cell change destinations. ltm-ServingCellNoResetID is an identifier used by the terminal device 100 when determining whether or not an L2 reset (Layer 2 reset) is required when switching cells, which will be described later. The ltm-ServingCellNoResetID or the initial value of ltm-ServingCellNoResetID may be a group identifier of the serving cell used when the base station device 200 transmits an RRC reconfiguration message including the configuration of cell change destination candidates to the terminal device 100 in step S1001 described later. The ltm-ServingCellNoResetID may be stored in the terminal device 100 as a variable indicating the group identifier of the current serving cell. Furthermore, the ltm-ServingCellNoResetID is a parameter that is essential when a new LTM configuration is configured and is not present in other cases.

[0165] Format E211 is a parameter included in the configuration of a cell change destination candidate. LTM-Candidate is the configuration of a cell change destination candidate. ltm-CandidateId is an identifier or index that uniquely identifies one or more configured cell change destination candidate configurations within the terminal device 100. ltm-CandidateConfig is a parameter for generating a configuration to be used at the cell change destination (target). ltm-CandidateConfig may be a complete configuration or a delta configuration, as described below. ltm-CandidateConfig may be configured with parameters included in an RRC reconfiguration message. ltm-NoResetID is an identifier used by the terminal device 100 when determining whether or not an L2 reset (Layer 2 reset) is required at the time of cell change, as described below. ltm-NoResetID may be a group identifier of a cell that is a cell change destination candidate. The cell change destination candidate is an example of an LTM candidate or an LTM cell candidate, for example.

[0166] FIG. 10 is a diagram showing an example of an LTM sequence.

[0167] The base station device 200 includes one or more cell change destination candidate settings (target cell candidate settings) in an RRC reconfiguration message and transmits the message to the terminal device 100 (S1001).

[0168] Upon receiving an RRC reconfiguration message (S1001), the terminal device 100 stores the LTM configuration information (including the configuration of candidate cell change destinations) included in the received message. The terminal device 100 may also store the value of ltm-ServingCellNoResetID included in the LTM configuration in a variable indicating the group identifier of the current serving cell.

[0169] Note that the cell change destination candidate may be, for example, only the PCell or may include the SCell. The configuration of each cell change destination candidate may be uniquely identified within the terminal device 100 using an index (ltm-CandidateId). Furthermore, the configuration of the cell change destination candidate does not include a parameter indicating an update of the security key. In other words, the security key by LTM is not updated. Furthermore, the configuration of the cell change destination candidate may include parameters similar to the synchronized reconfiguration parameters.

[0170] The terminal device 100 may retain the configuration of the cell change destination candidate received and stored in step S1001 without releasing it after the cell change is successful, as described below. In this case, the retained configuration of the cell change destination candidate may be used for a subsequent cell switch. However, when the configuration of the cell change destination candidate is retained and used for a subsequent cell switch, it may not be possible to set the configuration of the cell change destination candidate to a delta configuration and apply the delta configuration to the source configuration to generate a target cell configuration. This phenomenon occurs because the source configuration differs depending on the order of cells changed by cell change.

[0171] For this reason, in step S1001, the RRC reconfiguration message may include a reference configuration in addition to the configuration of the cell change destination candidate, or as part of the configuration of the cell change destination candidate. The reference configuration is used, for example, to complete the configuration to be used at the cell change destination (target). When the RRC reconfiguration message includes a reference configuration, the configuration of each cell change destination candidate included in the RRC reconfiguration message may be a differential configuration (delta configuration) from the reference configuration. In other words, the terminal device 100 can generate the configuration to be used at the cell change destination (target), i.e., the complete configuration to be used at the cell change destination, from the reference configuration and the configuration of the cell change destination candidate (delta configuration). For example, when the terminal device 100 receives a cell change signal to cell X, which is a cell change destination candidate, from the base station device 200 in step S1002 described below, the terminal device 100 generates the configuration to be used in cell X by applying the configuration of cell X to the reference configuration.

[0172] Also, in step S1001, the RRC reconfiguration message may not include a reference configuration. When the RRC reconfiguration message does not include a reference configuration, the configuration of each cell change destination candidate included in the RRC reconfiguration message is, for example, a complete configuration. That is, the terminal device 100 can generate the configuration to be used at the cell change destination (target) by replacing the configuration used in the current cell with the configuration of the cell change destination candidate. For example, in step S1002 described below, when the terminal device 100 receives a cell change signal to cell X, which is a cell change destination candidate, from the base station device 200, the terminal device 100 generates the configuration to be used in cell X by replacing the configuration of the current cell with the configuration of cell X. However, when the configuration of the cell change destination candidate is set to a complete configuration, some of the configurations may not be included. The partial configuration includes, for example, configurations that do not change due to cell change (fixed configurations). The configurations that do not change due to cell change (fixed configurations) include, for example, some or all of the radio bearer configurations. In this case, when the terminal device 100 receives a cell switching signal from the base station device 200 to cell X, which is a candidate cell change destination, it generates settings to be used in cell X by replacing the current cell settings with the cell X settings, except for fixed settings.

[0173] Note that, regardless of whether or not the RRC reconfiguration message includes a reference configuration, when generating a configuration to be used at the cell switching destination, the terminal device 100 does not need to reset some or all of the values ​​of state variables, timers, etc. used in each entity (SDAP entity, PDCP entity, RLC entity, MAC entity, etc.) to their initial states. Furthermore, the terminal device 100 does not need to discard some or all of the buffers in each entity. In other words, the terminal device 100 can retain some or all of the values ​​of state variables, timers, etc. used in each entity. Furthermore, the terminal device 100 may retain some or all of the buffers in each entity.

[0174] The base station device 200 transmits to the terminal device 100 a cell switching signal for switching the serving cell of the terminal device 100 from the current serving cell to one of the cell switching destination candidates (S1002).

[0175] The terminal device 100 receives a cell switching signal in the current serving cell (S1002). The cell switching signal may be, for example, a MAC CE. Alternatively, the cell switching signal may be a physical layer signal such as DCI.

[0176] The cell switching signal includes at least an index (ltm-CandidateId). The terminal device 100 applies the setting of the cell change destination (cell X) specified by the received cell switching signal. Note that cell X may be configured only with a PCell, or may be configured with a PCell and one or more SCells.

[0177] The terminal device 100 performs four-step or two-step CFRA or CBRA between the base station device 200 in cell X in accordance with the configuration of cell X (S1003). Furthermore, if the configuration of cell X includes a parameter indicating that RACH-less cell switching is to be performed, the processing in step S1003 is not executed. Furthermore, if the ltm-NoResetID of cell X is the same as the ltm-ServingCellNoResetID or the variable indicating the group identifier of the current serving cell, the terminal device 100 does not perform an L2 reset. Furthermore, if the ltm-NoResetID of cell X is not the same as the ltm-ServingCellNoResetID or the variable indicating the group identifier of the current serving cell, the terminal device 100 performs an L2 reset and overwrites the ltm-ServingCellNoResetID or the variable indicating the group identifier of the current serving cell with the ltm-NoResetID of cell X. An example of an L2 reset is an RLC re-establishment. Also, an example of an L2 reset is a PDCP data recovery.

[0178] The terminal device 100 transmits a notification indicating that the cell has been switched to the base station device 200 in cell X (S1004). This notification corresponds to an RRC reconfiguration complete message in handover or conditional handover. The notification indicating that the cell has been switched may use an RRC message such as an RRC reconfiguration complete message or a MAC CE. Furthermore, the notification indicating that the cell has been switched may use a physical signal such as UCI.

[0179] Furthermore, the notification indicating that the cell has been switched may include at least an identifier of cell X of the terminal device 100. Note that, if two-step CFRA or CFRA has been performed in step S1003, the notification indicating that the cell has been switched is transmitted before receiving the random access response in step S1003. Furthermore, uplink data generated in the DRB may be transmitted together with the notification indicating that the cell has been switched.

[0180] If four-step or two-step CBRA is performed in step S1003, or if RACH-less cell switching is performed, the base station apparatus 200 transmits a contention resolution signal to the terminal apparatus 100 (S1005).

[0181] The terminal device 100 receives a contention resolution signal in, for example, cell X (S1005). The contention resolution signal may include at least an identifier of the terminal device 100 in cell X.

[0182] The timing of successful cell switching may be the same as that of successful handover in handover or conditional handover. That is, in the case of cell switching using four-step or two-step CFRA, the cell switching is successful when a random access response is received. Also, in the case of cell switching using four-step or two-step CBRA or RACH-less cell switching, the cell switching is successful when contention resolution is performed. If the timing of successful cell switching is the same as that of successful handover in handover or conditional handover, as in handover or conditional handover, in cell switching using four-step CFRA, no notification indicating the cell switching or uplink data generated in the DRB is transmitted before the cell switching is successful. However, in the case of cell switching using four-step CBRA, cell switching using two-step CFRA or CBRA, and RACH-less cell switching, a notification indicating the cell switching may be transmitted before the cell switching is successful, and uplink data generated in the DRB may be transmitted together with this notification.

[0183] After executing step S1001, the terminal device 100 may perform downlink synchronization and / or uplink synchronization with one or more cell change destination candidates before transmitting the cell change destination signal in step S1002. In uplink synchronization, the base station device 200 may measure a timing advance (TA) of the terminal device 100 for one or more cell change destination candidates. Uplink synchronization may be performed by the base station device 200 instructing the terminal device 100 to transmit a random access preamble. The base station device 200 may instruct the terminal device 100 to transmit different random access preambles to one or more cell change destination candidates, or may instruct the terminal device 100 to transmit a common random access preamble to a group of multiple cell change destination candidates. The TA measured by the base station device 200 may be transmitted to the terminal device 100 using a random access response (RAR), or may be transmitted to the terminal device 100 using the cell change destination signal in step S1002. In this way, performing uplink synchronization after the terminal device 100 executes step S1001 and before the cell switching signal is sent in step S1002 may be called early TA measurement or early TA acquisition.

[0184] Note that the cell switching may be referred to as LTM. Also, the cell switching may be referred to as another term that represents a cell switching by LTM. Hereinafter, the cell switching and the cell change may be treated as terms that mean the same thing.

[0185] <Cell Switch Failure Handling> In the event of a cell switch failure, an RRC connection re-establishment procedure may be performed, similar to a certain handover failure handling or a conditional handover failure handling.

[0186] 11 is a diagram showing an example of a sequence of detecting a cell switching failure and processing the cell switching failure. The processing of steps S1001 and S1002 in FIG. 11 is the same as the processing of steps S1001 and S1002 in FIG.

[0187] When the terminal device 100 receives a cell switching signal (S1002), it starts a timer to detect cell switching failure (S1101) and starts cell switching processing to the cell (cell X) specified by the received cell switching signal (not shown).

[0188] If the cell switch is successful before the timer expires, the terminal device 100 stops the timer (not shown). On the other hand, if the timer expires, the terminal device 100 detects that the cell switch to cell X has failed (S1102).

[0189] When the terminal device 100 detects a cell switching failure (S1102), the terminal device 100 performs a cell switching failure process (S1103). In the cell switching failure process, the terminal device 100 may return to the settings used in the source PCell and perform an RRC connection re-establishment procedure.

[0190] <Keystream reuse issue in cell switching failure processing> LTM proposes that in the RRC connection re-establishment procedure in cell switching failure processing, if the selected cell is one of the candidate cell change destinations, the RRC connection is recovered as in the case of conditional handover, i.e., cell switching to the selected cell is performed instead of transmitting an RRC re-establishment request message in the selected cell (e.g., Non-Patent Document 10, Non-Patent Document 11).

[0191] However, in the RRC connection re-establishment procedure after a cell switch failure using four-step CBRA, or a cell switch failure using two-step CFRA or CBRA, or a RACH-less cell switch failure, if the selected cell is one of the cell change destination candidates, the process of cell switching to the selected cell instead of sending an RRC re-establishment request message in the selected cell may cause a key stream reuse problem.

[0192] As described above, in cell switch using four-step CBRA, cell switch using two-step CFRA or CBRA, and RACH-less cell switch, uplink data may be transmitted together with a notification indicating the cell switch before the cell switch is successful. If the notification indicating the cell switch is an RRC message transmitted from an SRB other than SRB0 (e.g., SRB1), the RRC message is processed, including security processing, in the PDCP entity of SRB1 and transmitted as a PDCP data PDU through a lower layer. Assume that the COUNT value used for security processing in the PDCP entity of the RRC message is, for example, n.

[0193] Furthermore, when uplink data is transmitted from a certain DRB (DRB1) together with a notification indicating a cell change, the uplink data undergoes processing, including security processing, in the PDCP entity of DRB1, and is transmitted as a PDCP data PDU through a lower layer. The COUNT value used for the security processing of the uplink data (in the PDCP entity of the uplink data) is assumed to be, for example, m.

[0194] If the cell switch fails, the terminal device 100 restores the settings to those used in the source PCell and performs an RRC connection re-establishment procedure. When restoring the settings to those used in the source PCell, the values ​​of the state variables in each entity of each radio bearer are also restored to the values ​​used in the source, so the COUNT value returns to the state before the cell switch signal was received. In the RRC connection re-establishment procedure, if the selected cell is one of the cell change destination candidates and the terminal device 100 performs cell switch to the selected cell, it transmits an RRC message that is a notification indicating that the cell has been switched in the selected cell. When transmitting this RRC message, the COUNT value n is used again in security processing in the PDCP entity of SRB1. Furthermore, when the first uplink message is transmitted from DRB1 in the cell, the COUNT value m is used again in security processing in the PDCP entity of DRB1. In cell switching in LTM, no security key change is performed, and the same security key and the same COUNT value are used for the same radio bearer in the same direction (uplink), i.e., the key stream reuse problem may occur.

[0195] <Cell switching failure process 1 to avoid the key stream reuse problem> Fig. 12 is a diagram showing an example of a first cell switching failure process method. The first cell switching failure process method is a method in which, when the cell selected by the terminal device 100 is an NR cell in the RRC connection re-establishment procedure in the cell switching failure process, the selected NR cell transmits an RRC re-establishment request message to the base station device 200, regardless of whether this NR cell is one of the cell change destination candidates.

[0196] The terminal device 100 detects a failure in cell switching to cell X (S1102).

[0197] Next, the terminal device 100 restores the settings to those of the source PCell and performs an RRC connection re-establishment procedure (S1201). When restoring the settings used in the source PCell, the values ​​of the state variables in each entity of each radio bearer are also restored to the values ​​used in the source (the values ​​at the time of receiving the cell switching signal in step S1002 of FIG. 11 or the values ​​immediately before the reception). Note that, when performing the RRC connection re-establishment procedure, the terminal device 100 may release the stored settings of cell change destination candidates. When releasing the stored settings of cell change destination candidates, the release process may be performed before the process of step S1202 described below.

[0198] In the RRC connection re-establishment procedure, the terminal device 100 performs cell selection, for example, selects an NR cell. The terminal device 100 transmits an RRC re-establishment request message to the base station device 200 in the selected NR cell (S1202).

[0199] In addition, in the procedure for re-establishing the RRC connection, if the selected cell is a RAT other than NR, the terminal device 100 transitions to the RRC idle mode. Also, if the terminal device 100 cannot select a cell within a certain time, it transitions to the RRC idle mode.

[0200] <Cell switching failure process 2 to avoid the key stream reuse problem> Fig. 13 is a diagram showing an example of a second cell switching failure process method. The second cell switching failure method is a method in which, in a procedure for re-establishing an RRC connection in cell switching failure process, if the cell selected by the terminal device 100 is one of the cells that satisfies the second condition and also satisfies at least the first condition, the cell switching process to the selected cell is performed by applying the settings of the selected cell as a cell change destination candidate.

[0201] The second condition includes, for example, that the cell is a cell change destination candidate stored in the terminal device 100. Furthermore, the second condition includes, for example, that the cell is a cell in which recovery of the RRC connection after cell switching failure is permitted.

[0202] A cell for which recovery of the RRC connection after cell switching failure is permitted includes, for example, a cell that is a cell change destination candidate stored by the terminal device 100 and that belongs to the same group as the cell for which cell switching failed (for example, cell X). Determination of whether the cell belongs to the same group as cell X is performed, for example, by a group identifier that is set in advance in the setting of the cell change destination candidate. The group identifier may be rephrased as a reset-unnecessary identifier.

[0203] Furthermore, a cell in which recovery of the RRC connection after a cell switching failure is permitted includes, for example, a cell change destination candidate stored by the terminal device 100, and a cell in which the setting of the cell change destination candidate includes information indicating that recovery of the RRC connection after a cell switching failure is permitted.

[0204] In addition, when the cell selected by the above-mentioned terminal device 100 is one of the cells that satisfies the second condition and also satisfies at least the first condition, the process of applying the settings of the selected cell as a candidate cell change destination and performing cell switching processing to the selected cell may be performed, for example, when at least the first parameter is set in the terminal device 100.

[0205] The terminal device 100 detects a failure in cell switching to cell X (S1102).

[0206] Next, the terminal device 100 restores the settings to those of the source PCell and performs an RRC connection re-establishment procedure (S1301). When restoring the settings used in the source PCell, the terminal device 100 also restores the values ​​of the state variables in each entity of each radio bearer to the values ​​used in the source (the values ​​at the time of receiving the cell switching signal in step S1002 of FIG. 11 or the values ​​immediately before receiving the signal).

[0207] In the procedure for re-establishing the RRC connection, the terminal device 100 performs cell selection and performs processing according to the selected cell and the first condition (S1302).

[0208] The first condition is, for example, that the cell switching process to cell X after receiving the cell switching signal in step S1002 of FIG. 11 has been performed using a four-step CFRA, i.e., that the setting of the cell change destination candidate for cell X includes a four-step CFRA setting.

[0209] Furthermore, the first condition may be, for example, that after receiving the cell switching signal in step S1002 of FIG. 11, only the cell switching process using the four-step CFRA was performed during the cell switching process to cell X, i.e., that the setting of cell change destination candidates for cell X includes the four-step CFRA setting, and further, that in the initial random access resource selection, there was a reference signal whose RSRP was equal to or greater than a threshold value.

[0210] Furthermore, the first condition may be, for example, that a cell switching process using a four-step CFRA was performed during the cell switching process to cell X after receiving the cell switching signal in step S1002 of FIG. 11, i.e., that the setting of cell change destination candidates for cell X includes a four-step CFRA setting, and that this is the first cell selection after detecting a cell switching failure in step S1102.

[0211] Furthermore, the first condition may be, for example, that, during the cell switching process to cell X after receiving the cell switching signal in step S1002 of FIG. 11, only the cell switching process using the four-step CFRA has been performed; that is, the setting of cell change destination candidates for cell X includes a four-step CFRA setting, and in the initial random access resource selection, there is a reference signal whose RSRP is equal to or greater than a threshold, and this is the first cell selection after detecting a cell switching failure in step S1102.

[0212] Note that the fact that only the cell switching process by the 4-step CFRA has been performed may be rephrased as the fact that the cell switching process by the 4-step CFRA has been performed and the MAC PDU in the Msg3 (message 3) buffer has not been transmitted. In addition, the fact that only the cell switching process by the 4-step CFRA has been performed may be rephrased as the fact that the 4-step or 2-step CBRA has not been performed before the cell switching process by the 4-step CFRA.

[0213] Furthermore, the first condition may be, for example, that after receiving the cell switching signal in step S1002 of FIG. 11, until cell switching failure is detected in step S1102, no PDCP data PDU is transmitted from the terminal device 100 through a lower layer, i.e., no RRC message is transmitted from an SRB other than SRB0, and / or no uplink data is transmitted from a DRB.

[0214] Furthermore, the first condition may be, for example, that after receiving the cell switching signal in step S1002 of FIG. 11, no PDCP data PDU is transmitted from the terminal device 100 through a lower layer until a cell switching failure is detected in step S1102, i.e., that no RRC message is transmitted from an SRB other than SRB0, and / or that no uplink data is transmitted from a DRB, and that this is the first cell selection after the cell switching failure is detected in step S1102.

[0215] Furthermore, the first condition may be, for example, that only the first signal is sent from the terminal device 100 after receiving the cell switching signal in step S1002 of FIG. 11 and before detecting a cell switching failure in step S1102.

[0216] Furthermore, the first condition may be, for example, that after receiving the cell switching signal in step S1002 of FIG. 11, only the first signal is sent from the terminal device 100 until a cell switching failure is detected in step S1102, and that this is the first cell selection after the cell switching failure is detected in step S1102.

[0217] The first signal is the notification sent in step S1004 of Fig. 10. The first signal may be, for example, a MAC CE. The first signal may also be a physical layer signal.

[0218] Furthermore, the terminal device 100 may transmit only the first signal, which may mean that the terminal device 100 does not transmit a MAC SDU.

[0219] In the RRC connection re-establishment procedure, the terminal device 100 performs cell selection. The terminal device 100 selects an NR cell, and if this NR cell is one of the cells (for example, cell Y) that satisfies the second condition and also satisfies the first condition, it applies the cell change destination candidate setting for cell Y and performs cell switching processing to cell Y. Note that the cell switching processing to cell Y may be limited to cases where a first parameter has been set in the terminal device 100. The first parameter is, for example, a parameter indicating that if the cell selected in the cell switching failure processing is one of the cells that satisfies the second condition and also satisfies the first condition, cell switching processing is to be performed on this cell.

[0220] Furthermore, in the procedure for re-establishing the RRC connection, if the selected cell is an NR cell and satisfies some or all of the following conditions A to C, the terminal device 100 transmits an RRC re-establishment request message to the base station device 200 in the selected cell. At this time, before transmitting the RRC re-establishment request message to the base station device 200, the terminal device 100 may release the stored settings of the cell change destination candidate.

[0221] Condition A: The selected cell is not one of the cells that meets the second condition.

[0222] Condition B: The first condition is not met.

[0223] Condition C: The first parameter is not set.

[0224] In addition, in the RRC connection re-establishment procedure, if the selected cell is a cell of a RAT other than NR, or if cell selection cannot be made within a specified time, the terminal device 100 transitions to RRC idle mode.

[0225] Note that the terminal device 100 may be configured or designed (hereinafter, sometimes referred to as a transmission prohibition setting) so as not to transmit a PDCP data PDU during the period from when the terminal device 100 receives a cell switching signal in step S1002 in Fig. 11 until when a cell switching failure is detected in step S1102. The transmission prohibition setting means, for example, being configured or designed so as to use only a four-step CFRA for random access in the cell switching process. Also, being configured or designed so as to use only a four-step CFRA for random access in the cell switching process means including a four-step CFRA setting in the setting of each cell change destination candidate.

[0226] The transmission prohibition setting is, for example, using MAC CE or physical layer signaling for notification in step S1004 of Fig. 10, and not transmitting uplink data generated by DRB or the like in step S1004. Not transmitting uplink data generated by DRB or the like means, for example, not transmitting MAC SDU.

[0227] If transmission prohibition is set, the terminal device 100 performs the process of step S1302 as follows.

[0228] In the RRC connection re-establishment procedure, the terminal device 100 performs cell selection. If the selected cell is an NR cell and is one of the cells that satisfies the second condition (for example, cell Y), the terminal device 100 applies the cell change destination candidate setting to cell Y and performs cell switching processing to cell Y. Note that the cell switching processing to cell Y may be limited to cases where the second parameter has been set in the terminal device 100.

[0229] The second parameter is, for example, a parameter indicating that if the cell selected in the cell switching failure process is one of the cells for which the terminal device 100 satisfies a second condition, the cell switching process is to be performed on that cell.

[0230] Furthermore, the second parameter may be, for example, a parameter indicating that if the cell selected in the cell switching failure process is one of the cells that satisfy the second condition and is the first cell selection after the detection of cell switching failure in step S1102, cell switching process should be performed on that cell.

[0231] Furthermore, when transmission prohibition is set, in the procedure for re-establishing an RRC connection, if the cell selected by the terminal device 100 is an NR cell and meets some or all of the following conditions D and E, the terminal device 100 transmits an RRC re-establishment request message to the base station device 200 in the selected cell. At this time, before transmitting the RRC re-establishment request message to the base station device 200, the terminal device 100 releases the stored settings of the cell change destination candidates.

[0232] Condition D: The selected cell is not one of the cells that meets the second condition.

[0233] Condition E: The first parameter is not set.

[0234] In addition, in the RRC connection re-establishment procedure, if the selected cell is a cell of a RAT other than NR, or if cell selection cannot be made within a specified time, the terminal device 100 transitions to RRC idle mode.

[0235] <Cell Switching Failure Process 3 to Avoid the Keystream Reuse Problem> Figure 14 is a diagram showing an example of a third cell switching failure processing method. The third cell switching failure method is a process in which, when the terminal device 100 returns the settings to the source PCell settings after detecting a cell switching failure, the values ​​of some or all of the state variables are retained, and if the cell selected by the terminal device 100 is an NR cell and one of the cells that satisfies a second condition in the RRC connection re-establishment procedure, the cell switching to the selected cell is performed by applying the cell switching destination candidate settings of the selected cell. Note that, when the terminal device 100 returns the settings to the source PCell settings after detecting the above-mentioned cell switching failure, the process of retaining the values ​​of some or all of the state variables is performed, for example, when at least a second parameter is configured in the terminal device 100. Furthermore, in the RRC connection re-establishment procedure, if the cell selected by the terminal device 100 is one of the cells that satisfies the second condition, the process of applying the cell switching destination candidate settings of the selected cell and performing cell switching to the selected cell is performed, for example, when at least the second parameter is configured in the terminal device 100. In addition, when the terminal device 100 transmits an RRC re-establishment request message to the base station device 200 in the selected cell, it returns the state variables it has held to the settings of the source PCell before transmitting the RRC re-establishment request message.

[0236] The terminal device 100 detects a failure in cell switching to cell X (S1102).

[0237] Next, the terminal device 100 restores the settings to those of the source PCell and performs an RRC connection re-establishment procedure (S1401). When restoring the settings used in the source PCell, some or all of the values ​​of the state variables in each entity of each radio bearer are retained rather than restored to the values ​​used in the source PCell (the values ​​at the time of receiving the cell switch signal in step S1002 of FIG. 11 or the values ​​immediately before the reception). The retained state variables include, for example, the COUNT value in the PDCP entity. Furthermore, the process of retaining the values ​​of some or all of the state variables in each entity of each radio bearer when restoring the settings used in the source PCell is performed, for example, when a second parameter is set in the terminal device 100.

[0238] Next, in the procedure for re-establishing the RRC connection, the terminal device 100 performs cell selection and performs processing according to the selected cell and the first condition (S1402).

[0239] When the selected cell is an NR cell and is one of the cells that satisfies the second condition (for example, cell Y), the terminal device 100 applies the setting of the cell change destination candidate to cell Y and performs cell switching processing to cell Y. Note that the processing for cell Y is performed, for example, when a second parameter is set in the terminal device 100.

[0240] The second parameter is, for example, a parameter indicating that if the cell selected in the cell switching failure process is one of the cells for which the terminal device 100 satisfies a second condition, the cell switching process is to be performed on that cell.

[0241] Furthermore, the second parameter may be, for example, a parameter indicating that if the cell selected in the cell switching failure process is one of the cells that satisfy the second condition and is the first cell selection after the detection of cell switching failure in step S1102, cell switching process should be performed on that cell.

[0242] In addition, the values ​​of some or all of the state variables in each entity of each radio bearer are, for example, the values ​​of some or all of the state variables in each entity of each DRB.

[0243] Furthermore, in the RRC connection re-establishment procedure, if the selected cell is an NR cell and meets some or all of the following conditions F and G, the terminal device 100 transmits an RRC re-establishment request message to the base station device 200 in the selected cell. At this time, the terminal device 100, for example, releases the stored configuration of the cell change destination candidate before transmitting the RRC re-establishment request message to the base station device 200. Also, at this time, the terminal device 100 may, for example, restore the values ​​of the state variables held in step S1401 to the values ​​used in the source PCell (the values ​​at the time of receiving the cell switching signal in step S1002 of FIG. 11 or the values ​​immediately before receiving the cell switching signal) before transmitting the RRC re-establishment request message to the base station device 200. The process of restoring the values ​​of the state variables held in step S1401 to the values ​​used in the source PCell before transmitting this RRC re-establishment request message to the base station device 200 is performed, for example, when the second parameter is set.

[0244] Condition F: The selected cell is not one of the cells that meets the second condition.

[0245] Condition G: The second parameter is not set.

[0246] In addition, in the RRC connection re-establishment procedure, if the selected cell is a cell of a RAT other than NR, or if cell selection cannot be made within a specified time, the terminal device 100 transitions to RRC idle mode.

[0247] <Cell Switching Failure Processing 4 to Avoid Keystream Reuse Problem> FIG. 15 is a diagram showing an example of a fourth cell switching failure processing method.

[0248] The terminal device 100 detects a failure in cell switching to cell X (S1102).

[0249] Next, the terminal device 100 performs a cell selection procedure (S1501). Before performing the cell selection procedure, the terminal device 100 may stop some or all of the timers that are running. Furthermore, the terminal device 100 may start a timer for limiting the time for performing the cell selection procedure to a certain period of time. The terminal device 100 may perform the cell selection procedure using the settings of the terminal device 100 at the time of cell switching failure, without restoring the settings to the settings of the source PCell.

[0250] Also, when performing the cell selection procedure, if the terminal device 100 returns the settings to the settings of the source PCell, it retains some or all of the values ​​of state variables, timers, etc. in each entity, and some or all of the buffers in each entity.

[0251] When the terminal device 100 does not restore the settings to the source PCell, it performs the cell selection procedure using the settings of the terminal device 100 at the time of cell switching failure. Furthermore, when the terminal device 100 restores the settings to the source PCell, it performs the cell selection procedure while retaining some or all of the values ​​of state variables, timers, etc., and some or all of the buffers in each entity. The processing of performing these cell selection procedures is performed, for example, when either or both of the following conditions are met: a parameter indicating that LTM is to be performed is set in the terminal device 100; or at least a second parameter is set in the terminal device 100.

[0252] Furthermore, the cell selection procedure may be performed as part of the RRC connection re-establishment procedure or may be performed separately from the RRC connection re-establishment procedure. Furthermore, if at least the second parameter is not set, the terminal device 100 may perform the processes of steps S1604 and S1605 without performing the process of step S1602 described below.

[0253] Next, the terminal device 100 performs processing according to the selected cell (S1502).

[0254] 16 is a diagram showing an example of processing according to the selected cell in step S1502. The terminal device 100 starts processing according to the selected cell (S1601).

[0255] The terminal device 100 determines whether the selected cell is one of the cells that satisfies the second condition (S1602).

[0256] If the selected cell is one of the cells that satisfy the second condition (for example, cell Y) (S1602: Yes), the terminal device 100 performs cell switching to this selected cell (cell Y) (S1603). The process of performing cell switching to the selected cell when the selected cell is one of the cells that satisfy the second condition is performed, for example, when a parameter indicating that LTM is to be performed is set in the terminal device 100, or when at least the second parameter is set in the terminal device 100, or when both of these conditions are met.

[0257] The second parameter is, for example, a parameter indicating that if the cell selected in the cell switching failure process is one of the cells that satisfy the second condition, the cell switching process is to be performed on that cell.

[0258] Furthermore, the second parameter may be, for example, a parameter indicating that cell switching processing should be performed on the cell selected in the cell switching failure processing when the cell selected in the cell switching failure processing is one of the cells that satisfy the second condition and is the first cell selection after the detection of cell switching failure in step S1102.

[0259] When performing cell switching to cell Y or before performing cell switching, the terminal device 100 may release some of the information it holds. The part of the information it holds may include, for example, information obtained by early TA measurement or early TA acquisition. The information obtained by early TA measurement or early TA acquisition may include, for example, information including TA information and the value of the TA timer for the TA.

[0260] When performing cell switching to cell Y or before performing cell switching, the terminal device 100 may generate a configuration of cell Y to be used in cell Y. That is, when storing a reference configuration, the terminal device 100 generates a configuration to be used in cell Y by applying the stored configuration of cell Y to the reference configuration. Furthermore, when not storing a reference configuration or when the stored configuration of the cell change destination candidate is a complete configuration, the terminal device 100 may generate a configuration to be used in cell Y by replacing the configuration to be used in the current cell with the stored configuration of cell Y, or by replacing the configuration to be used in the current cell, excluding the fixed configuration, with the stored configuration of cell Y. When generating a configuration to be used at the cell change destination, the terminal device 100 may not reset some or all of the values ​​of state variables, timers, etc. used in each entity (SDAP entity, PDCP entity, RLC entity, MAC entity, etc.) to their initial states. That is, the terminal device 100 may retain some or all of the values ​​of state variables, timers, etc. used in each entity. Furthermore, when generating a setting to be used at the cell switching destination, the terminal device 100 may not discard some or all of the buffers in each entity. That is, the terminal device 100 may hold some or all of the values ​​of state variables, timers, etc. used in each entity. Furthermore, the terminal device 100 may hold some or all of the buffers in each entity.

[0261] Furthermore, when performing cell switching to cell Y, the terminal device 100 may perform cell switching using four-step or two-step CFRA, four-step or two-step CBRA, or RACH-less. The terminal device 100 may determine which cell switching method to use (whether to use four-step or two-step CFRA, four-step or two-step CBRA, or RACH-less for cell switching) according to the setting of cell Y. Furthermore, when performing cell switching to cell Y, the terminal device 100 may perform cell switching using RACH-less if a third condition is satisfied. The third condition includes, for example, a case where the terminal device 100 holds a valid TA for cell Y. A valid TA includes, for example, a case where a TA timer for the TA has not expired.

[0262] The terminal device 100 transmits a notification indicating that the cell has been switched when switching to cell Y or after switching to cell Y (the process of step S1004 in FIG. 10 ). The notification indicating that the cell has been switched may include information indicating that the RRC connection has been recovered after a cell switching failure. Information regarding uplink resources for sending the notification indicating that the cell has been switched may be included in the RAR, dynamically assigned by the base station device 200 after the cell switching, or included in the configuration of cell Y, for example.

[0263] In step S1602, the terminal device 100 determines whether the selected cell is one of the cells that satisfy the second condition, and if the selected cell is not one of the cells that satisfy the second condition (S1602: No), it restores the settings to the settings of the source PCell (S1604). At this time, the terminal device 100 may also restore the values ​​of state variables, timers, etc. used in each entity to the values ​​used in the source PCell.

[0264] Next, the terminal device 100 re-establishes the RRC connection or transitions to RRC idle mode (S1605). For example, if the selected cell is an NR cell, the terminal device 100 re-establishes the RRC connection. If the selected cell is an NR cell, the terminal device 100 transmits an RRC re-establishment request message to the base station device 200 in the selected cell. At this time, before transmitting the RRC re-establishment request message to the base station device 200, the terminal device 100 releases, for example, the stored cell change destination candidate settings. Also, for example, if the selected cell is a cell of a RAT other than NR, or if cell selection cannot be performed within a specified time, the terminal device 100 transitions to RRC idle mode.

[0265] The processing of step S1605 is performed, for example, as part of the RRC connection re-establishment procedure. Note that if the cell selection processing of step S1501 is performed separately from the RRC connection re-establishment procedure, the terminal device 100 does not need to perform the cell selection procedure in the RRC connection re-establishment procedure. Also, the terminal device 100 may reset the MAC and suspend some or all radio bearers before performing the processing of step S1605. The radio bearers to be suspended do not need to include at least SRB0. Also, the terminal device 100 may release some or all of the information it holds before performing the processing of step S1605. Also, the terminal device 100 may stop some or all of the timers that are running before performing the processing of step S1605.

[0266] As a result, the terminal device 100 and the base station device 200 can avoid the key stream reuse problem in the cell switching failure processing of the terminal device 100 and perform secure communication.

[0267] Note that in the cell switching failure process, the selected cell being one of the cell switching destination candidates stored in the terminal device 100 includes, for example, the selected cell being one of the PCells of the cell switching destination candidates stored in the terminal device 100. Also, the selected cell being one of the cell switching destination candidates stored in the terminal device 100 includes, for example, the selected cell being one of the PCells included in the setting of the cell switching destination candidates received in step S1001 of Fig. 11. In other words, in the cell switching failure process, even if the selected cell is one of the cells included in the cell switching destination candidates stored in the terminal device 100, if the selected cell is an SCell, there are cases in which the terminal device 100 does not regard the selected cell as one of the cell switching destination candidates stored.

[0268] Similarly, in the cell switching failure process, the selected cell being one of the cells that satisfy the second condition includes, for example, the selected cell being one of the PCells that satisfy the second condition.

[0269] Although the present embodiment has been described with respect to the process after a cell switching failure by LTM, it may be applied to other techniques, for example, the present embodiment may be applied to the process after a handover (synchronized reconfiguration) failure in an NTN (Non Terrestrial Network).

[0270] Furthermore, although this embodiment has been described regarding processing after a cell switching failure due to LTM, it may also be applied to processing after a handover (synchronized reconfiguration) failure. That is, the signal received by the terminal device 100 from the base station device in step S1002 may be an RRC reconfiguration message including synchronized reconfiguration parameters. In this case, the handover target does not have to be a cell change destination candidate stored in the terminal device 100. In this case, the cell switching failure detection in step S1102 may be a handover failure detection. After detecting a handover failure, the terminal device 100 may perform the cell switching failure processing disclosed in this embodiment. Furthermore, when the terminal device 100 performs the cell switching failure processing disclosed in this embodiment after detecting a handover failure, some of the processing of the cell switching failure processing may be performed when the RRC reconfiguration message including synchronized reconfiguration parameters does not include a parameter indicating a master key update. The part of the processing of the cell switching failure processing is, for example, processing of retaining the values ​​of some or all of the state variables when returning the configuration of the terminal device 100 to the configuration of the source PCell.

[0271] Although four cell switching failure processes have been disclosed in this embodiment, the cell switching failure process method to be applied may be selected depending on whether the process is a process after a cell switching failure by LTM or a process after a handover (synchronized reconfiguration) failure. For example, in the case of a process after a cell switching failure by LTM, cell switching failure 4 is applied, and in the case of a process after a handover (synchronized reconfiguration) failure, cell switching failure 1, cell switching failure 2, or cell failure process 3 is applied.

[0272] <Radio bearer processing during cell switching> A method for processing radio bearers and each entity when generating settings to be used at a cell switching destination (target) by replacing settings used in the current cell with settings of a candidate cell switching destination during cell switching will be described with reference to FIG. 10 and FIGS. 18 to 19 .

[0273] In step S1002 of FIG. 10, the terminal device 100 receives the cell switching signal from the base station device 200 and executes cell switching.

[0274] FIG. 18 shows an example of a procedure for performing cell switching.

[0275] The terminal device 100 that has received a cell switching signal from the base station device 200 performs a first process (S1800). The first process is a process of releasing some of the radio settings configured in the terminal device 100 and retaining the remaining settings. When performing the first process, the terminal device 100 may determine which settings to release and which settings not to release, and perform the first process based on that determination.

[0276] For example, when the cell group that performs the cell switch is an MCG, the terminal device 100 holds the AS security settings related to the MCG C-RNTI and / or the master key without releasing them. Also, for example, when the cell group that performs the cell switch is an SCG, the terminal device 100 holds the AS security settings related to the secondary key without releasing them.

[0277] Furthermore, the terminal device 100 retains, for example, some or all of the information related to SDAP without releasing it. The information related to SDAP includes, for example, an SDAP entity and an SDAP configuration. The terminal device 100 retains, for example, the SDAP entity and the SDAP configuration without releasing it. Furthermore, the terminal device 100 retains, for example, the SDAP entity without releasing it, and releases some or all of the SDAP configuration. The SDAP configuration is, for example, parameters set in the SDAP configuration. The parameters set in the SDAP configuration are, for example, mapping of QoS flows and DRBs, uplink / downlink header settings, default DRB settings, etc.

[0278] The terminal device 100 also retains, for example, some or all of the information related to radio bearers without releasing them. The information related to radio bearers includes, for example, radio bearers, radio bearer configurations, and RLC bearer configurations. The terminal device 100 retains, for example, all of the radio bearers, radio bearer configurations, and RLC bearer configurations without releasing them. The terminal device 100 also retains, for example, some or all of the radio bearers without releasing them, and releases some or all of the radio bearer configurations and RLC bearer configurations for the retained radio bearers. The terminal device 100 also retains, for example, some or all of the radio bearers without releasing them, and releases the radio bearers that are not retained and / or the RLC bearers associated with the radio bearers. The release of the radio bearers may include the release of radio bearer identifiers and / or the release of PDCP entities. The release of the RLC bearers may include the release of RLC entities and / or the release of logical channels. The radio bearer is, for example, an SRB, and / or a DRB, and / or a multicast MRB (MBS Radio Bearer). The multicast MRB is, for example, a radio bearer for multicast distribution in MBS (Multicast / Broadcast Service). The radio bearer setting is, for example, a parameter set in the radio bearer setting. The RLC bearer setting is, for example, a parameter set in the RLC bearer setting.

[0279] Parameters set in radio bearer setting are, for example, parameters set in SRB setting, DRB setting, MRB setting, etc. Parameters set in SRB setting are, for example, SRB identifiers, parameters set in PDCP setting, etc. Parameters set in DRB setting are, for example, DRB identifiers, parameters set in PDCP setting, etc. Parameters set in MRB setting are, for example, multicast MRB identifiers, parameters set in PDCP setting, etc. Parameters set in RLC bearer setting are, for example, logical channel identifiers, parameters set in RLC setting, radio bearer identifiers to which the RLC bearer is associated, etc. Note that the radio bearer identifier may be an SRB identifier, a DRB identifier, or a multicast MRB identifier.

[0280] Next, the terminal device 100 performs a second process (S1801). The second process is a process of applying a configuration of a cell switching destination (target) specified by a cell switching signal received from the base station device 200. The second process is shown in FIG. 19. FIG. 19 is a diagram showing an example of a process of the terminal device 100 applying the target configuration. The terminal device 100 compares a radio bearer identifier present in the current configuration (the configuration immediately before receiving the cell switching signal) with a radio bearer identifier present in the target configuration (S1900). The terminal device 100 performs a third process on a radio bearer corresponding to a radio bearer identifier present in the current configuration but not in the target configuration (S1901). Furthermore, the terminal device 100 performs a fourth process on a radio bearer corresponding to a radio bearer identifier present in the target configuration but not in the current configuration (S1902).

[0281] The third process is, for example, a process of releasing a target radio bearer and / or an RLC bearer associated with the radio bearer. Releasing a radio bearer and / or an RLC bearer associated with the radio bearer in the third process is, for example, a process of releasing a radio bearer identifier and / or a logical channel identifier and retaining a PDCP entity and / or an RLC entity. When retaining the PDCP entity and / or an RLC entity, the terminal device 100 stores the PDCP entity and / or the RLC entity as an RRC terminal device variable (UE variable). Furthermore, releasing a radio bearer and / or an RLC bearer associated with the radio bearer in the third process is, for example, a process of releasing a radio bearer identifier and / or a logical channel identifier, retaining information held by the PDCP entity and / or the RLC entity, and releasing the PDCP entity and / or the RLC entity. When retaining information held by the PDCP entity and / or the RLC entity, the terminal device 100 stores, for example, the information held by the PDCP entity and / or the RLC entity as RRC terminal device variables (UE variables). The information held by the PDCP entity and / or the RLC entity is, for example, some or all of the values ​​of state variables and / or timer values. Furthermore, the information held by the PDCP entity and / or the RLC entity is, for example, some or all of the data present in the buffers held by the PDCP entity and / or the RLC entity. Furthermore, for example, when releasing the PDCP entity and / or the RLC entity, the terminal device 100 configures the PDCP entity and / or the RLC entity to retain the information held by the PDCP entity and / or the RLC entity.

[0282] In the third process, the terminal device 100 stores, for example, information that can identify a radio bearer to which the held PDCP entity and / or RLC entity is associated, or a radio bearer to which information held by the held PDCP entity and / or RLC entity is associated. The information that can identify a radio bearer to which the stored information about the PDCP entity and / or RLC entity is associated may be a radio bearer identifier itself.

[0283] Furthermore, in the third process, holding the PDCP entity and / or the RLC entity may mean suspending or deactivating the PDCP entity and / or the RLC entity.

[0284] Also, when releasing a radio bearer and / or an RLC bearer associated with the radio bearer in the third process, the terminal device 100 may notify the SDAP entity associated with the radio bearer of the release of the radio bearer.

[0285] In the third process, the stored information is an example of the first information. In the third process, the bearer (radio bearer and / or RLC bearer) to be released is an example of the first bearer. The first bearer is, for example, the first DRB.

[0286] The fourth process is, for example, a process of establishing and / or configuring a target radio bearer and / or an RLC bearer associated with the radio bearer. In establishing and / or configuring a radio bearer and / or an RLC bearer associated with the radio bearer in the fourth process, the terminal device 100 determines whether the target radio bearer and / or the RLC bearer associated with the radio bearer has been established and / or configured since the LTM configuration was performed or since the LTM configuration was updated. If the target radio bearer and / or the RLC bearer associated with the radio bearer has not been established and / or configured since the LTM configuration was performed or since the LTM configuration was updated, the terminal device 100 newly establishes / configures the RLC bearer associated with the target radio bearer and / or the radio bearer. The new establishment / configuration of a radio bearer and / or an RLC bearer associated with a radio bearer may include some or all of the following: establishment of a PDCP entity, security configuration for the established PDCP entity, association of a radio bearer with an SDAP entity, and configuration of an SDAP entity, establishment of an RLC entity, configuration of a MAC entity, and association of a logical channel with a PDCP entity.

[0287] In a fourth process, if the target radio bearer and / or an RLC bearer associated with the radio bearer have been established and / or configured since the LTM configuration was performed or since the LTM configuration was updated, the terminal device 100 re-establishes / configures the target radio bearer and / or the RLC bearer associated with the radio bearer. The re-establishment / configuration of the radio bearer may include some or all of the following: establishing a PDCP entity, configuring security for the established PDCP entity, associating the radio bearer with an SDAP entity, configuring the SDAP entity, establishing an RLC entity, configuring a MAC entity, and associating a logical channel with a PDCP entity. The establishment of a PDCP entity in the re-establishment / configuration of the radio bearer and / or the RLC bearer associated with the radio bearer may, for example, associate a PDCP entity corresponding to the target radio bearer identifier stored in the terminal device 100 with the target radio bearer. When associating a PDCP entity corresponding to a radio bearer identifier of a target radio bearer stored in the terminal device 100 with the target radio bearer, the PDCP entity may be resumed or activated. The establishment of a PDCP entity in the radio bearer resumption establishment / configuration may, for example, establish a PDCP entity and perform a first configuration for the established PDCP entity. The first configuration may, for example, be a configuration of a state variable continuation, a timer continuation, and / or a buffer continuation. When performing the first configuration, the terminal device 100 may pass related information stored in an RRC terminal state variable to the PDCP entity. The establishment of an RLC entity in the radio bearer resumption establishment / configuration may, for example, be associating an RLC entity corresponding to a radio bearer identifier of a target radio bearer stored in the terminal device 100 with the target radio bearer and / or the RLC bearer associated with the radio bearer.When associating an RLC entity corresponding to the radio bearer identifier of the target radio bearer stored in the terminal device 100 with the target radio bearer and / or an RLC bearer associated with the radio bearer, the RLC entity may be resumed or activated. Furthermore, establishing an RLC entity in the resumption establishment / configuration of the radio bearer and / or an RLC bearer associated with the radio bearer may, for example, establish an RLC entity and perform a first configuration for the established RLC entity. The first configuration may, for example, be a configuration of continuation of a state variable, and / or a timer continuation, and / or a buffer continuation. When performing the first configuration, the terminal device 100 may pass related information stored in the RRC terminal state variables to the RLC entity. Note that in the fourth process, the information stored in the terminal device 100 is an example of second information.

[0288] In the fourth process, a method for determining whether a target radio bearer and / or an RLC bearer associated with the radio bearer has been established and / or configured since the LTM configuration was performed or since the LTM configuration was updated may be based on whether information capable of identifying the target radio bearer is stored in the terminal device 100. In addition, in the fourth process, the target bearer (radio bearer and / or RLC bearer) is an example of a second bearer. Note that the second bearer is, for example, a second DRB.

[0289] Next, the terminal device 100 applies the target configuration and performs cell switching to the target (S1802). When performing cell switching to the target, the terminal device 100 transmits an RRC reconfiguration completion message to the base station device 200 through the target cell.

[0290] Note that the new establishment / configuration of a radio bearer and the restoration establishment / configuration of a radio bearer in the fourth process may simply be referred to as the establishment / configuration of a radio bearer. Furthermore, the restoration establishment / configuration of a radio bearer in the fourth process may be called by a name different from the conventional establishment / configuration of a radio bearer, such as the establishment / configuration of a radio bearer in LTM.

[0291] In the fourth process, "since the LTM setting was performed" may be rephrased as "since the LTM setting was last performed." Furthermore, "since the LTM setting was updated" may be rephrased as "since the LTM setting was last updated."

[0292] In the third process, instead of releasing the radio bearer, the radio bearer may be suspended or deactivated, and in the fourth process, instead of re-establishing / setting up the radio bearer, the suspended or deactivated radio bearer may be resumed or activated.

[0293] In the second process, the radio bearer identifier present in the target configuration may be a radio bearer identifier included in the SRB-ToAddMod parameter, the DRB-ToAddMod parameter (E11 in FIG. 6), or the parameter named MRB-ToAddMod in the target configuration. Furthermore, the target configuration or the cell change destination candidate configuration in LTM may be restricted so that the setting of the SRB list to be released (parameter named srb-ToReleaseList), and / or the setting of the DRB list to be released (parameter named drb-ToReleaseList), and / or the setting of the multicast MRB list to be released (parameter named mrb-ToReleaseList) are not present.

[0294] Note that some or all of the first process to the fourth process may be applied when recovering the RRC connection after a cell switching failure. When some or all of the first process to the fourth process are performed when recovering the RRC connection after a cell switching failure, the current setting of the terminal device 100 may be the setting immediately before recovering the RRC connection.

[0295] <Others> Some of the messages in the above-described sequence may not be executed in the correct order, or the order may be changed. Also, some of the messages in the sequence may not be executed at all.

[0296] Furthermore, what is described as a function or process of the terminal device 100 may be a function or process of the base station device 200. Furthermore, what is described as a function or process of the base station device 200 may be a function or process of the terminal device 100.

[0297] Furthermore, when the term "radio bearer" is used without distinguishing between a signaling radio bearer and a data radio bearer, the radio bearer may be a signaling radio bearer, a data radio bearer, or both a signaling radio bearer and a data radio bearer.

[0298] Furthermore, "A may be replaced with B" and "A may be replaced with B" include the meaning of replacing B with A in addition to replacing A with B.

[0299] Furthermore, if condition "A" and condition "B" are contradictory conditions, condition "B" may be expressed as an "other" condition of condition "A."

[0300] To summarize, the following is the case.

[0301] (1) A terminal device comprising: a receiving unit that receives a signal from a base station device; and a processing unit, wherein, when the processing unit receives from the base station device a first signal instructing cell switching to a first LTM candidate, the processing unit releases a first bearer that exists in a current configuration and does not exist in a first configuration for the first LTM candidate, stores first information associated with the first bearer, and, when the processing unit stores second information associated with a second bearer that does not exist in the current configuration and exists in the first configuration for the first LTM candidate, applies the second information to the second bearer, applies the first configuration, and performs cell switching to the first LTM candidate. (2) The terminal device according to (1), wherein the first information includes any or all of information of a first bearer DRB identifier, a first PDCP entity, a first RLC entity, and a first logical channel identifier associated with the first bearer. (3) The terminal device according to (1) or (2), wherein the second information includes any or all of information of a second bearer identifier, a second PDCP entity, a second RLC entity, and a second logical channel identifier, which are associated with the second bearer. (4) The terminal device according to (1), (2), or (3), wherein the processing unit further releases an SDAP setting when the first signal instructing cell switching to the first LTM candidate is received from the base station device.

[0302] Although an example of a device has been described in each embodiment, the method of the present disclosure is not limited to cellular phones, smartphones, tablet terminals, base station devices, etc., but can also be applied to other electronic devices, such as electronic devices mounted on automobiles, trains, airplanes, artificial satellites, electronic devices mounted on drones, robots, AV equipment, home appliances, office equipment, vending machines, other household equipment, industrial equipment, and other devices.

[0303] In addition, in each embodiment, E-UTRA and NR are used as radio access technologies, and EPC and 5GC are used as core networks. However, the application of the method of the present disclosure is not limited to these. For example, the method of the present disclosure may be applied to radio access technologies and networks of different generations, such as 6th generation and 7th generation.

[0304] Furthermore, the present invention is not limited to the above-described embodiment, and various modifications can be made.

[0305] Although each embodiment has been described in detail with reference to the drawings, the specific configuration is not limited to the disclosed drawings and the described embodiments.

[0306] 10: Communication system 100: Terminal device 110: CPU 120: Storage 121: Wireless communication program 122: Terminal side program 130: Memory 140: Wireless communication circuit 200: Base station device 210: CPU 220: Storage 221: Wireless communication program 222: Base station side program 230: Memory 240: Wireless communication circuit 250: Network interface 300: Core network

Claims

1. A terminal device having a receiving unit that receives a signal from a base station device and a processing unit, wherein when the receiving unit receives from the base station device a first signal instructing cell switching to a first LTM (L1 / L2-triggered mobility) candidate, the processing unit: releases a first bearer that exists in a current setting and does not exist in a first setting for the first LTM candidate, and stores first information related to the first bearer; if a second bearer that does not exist in the current setting and exists in the first setting for the first LTM candidate and stores second information related to the second bearer, applies the second information to the second bearer; and applies the first setting and performs cell switching to the first LTM candidate.

2. The terminal device according to claim 1, wherein the first information includes any or all of information related to the first bearer: a first bearer identifier, a first Packet Data Convergence Protocol (PDCP) entity, a first Radio Link Control (RLC) entity, and a first logical channel identifier.

3. The terminal device according to claim 1 or claim 2, wherein the second information includes any or all of information related to the second bearer, including a second bearer identifier, a second PDCP entity, a second RLC entity, and a second logical channel identifier.

4. The terminal device according to claim 1 or 2, wherein the processing unit further releases a Service Data Adaptation Protocol (SDAP) setting when the processing unit receives the first signal from the base station device instructing cell switching to the first LTM candidate.

5. The terminal device according to claim 1 or 2, wherein the first bearer is a first data radio bearer, and the second bearer is a second data radio bearer.

6. A base station device comprising: a transmission unit that transmits a signal to a terminal device; and a processing unit, wherein when the transmission unit transmits a first signal to the terminal device instructing cell switching to a first LTM (L1 / L2-triggered mobility) candidate, the processing unit causes the terminal device to release a first bearer that exists in a current setting and does not exist in a first setting for the first LTM candidate, and store first information related to the first bearer; and when the terminal device stores second information related to the second bearer that does not exist in the current setting and exists in the first setting for the first LTM candidate, causes the terminal device to apply the second information to the second bearer; and applies the first setting and causes cell switching to the first LTM candidate.

7. The base station device according to claim 6, wherein the first information includes any or all of information related to the first bearer, including a first bearer identifier, a first Packet Data Convergence Protocol (PDCP) entity, a first Radio Link Control (RLC) entity, and a first logical channel identifier.

8. The base station device according to claim 6 or 7, wherein the second information includes any or all of information related to the second bearer, including a second bearer identifier, a second PDCP entity, a second RLC entity, and a second logical channel identifier.

9. The base station device according to claim 6 or 7, wherein the processing unit further releases a Service Data Adaptation Protocol (SDAP) setting in the terminal device when the processing unit transmits, to the terminal device, the first signal instructing the terminal device to switch cells to the first LTM candidate.

10. A wireless communication system comprising: a base station device; and a terminal device that receives a signal from the base station device, wherein the terminal device, when receiving a first signal from the base station device instructing cell switching to a first LTM (L1 / L2-triggered mobility) candidate, releases a first bearer that exists in a current setting and does not exist in a first setting for the first LTM candidate, and stores first information related to the first bearer; if a second bearer that does not exist in the current setting and exists in the first setting for the first LTM candidate and stores second information related to the second bearer, applies the second information to the second bearer; and applies the first setting and performs cell switching to the first LTM candidate.

Images