阅读说明：本技术 终端装置、基站装置以及方法 (Terminal device, base station device, and method ) 是由 堀贵子 山田昇平 坪井秀和 于 2019-09-17 设计创作，主要内容包括：本发明提供与能够减少协议处理的复杂度并高效地进行通信的终端装置、基站装置、方法以及集成电路相关的技术。终端装置具有：接收部,其从基站装置接收RRC连接重新设定消息；以及处理部,其进行以下处理,即,在上述RRC连接重新设定消息中包括表示应用全设定的信息的情况下,基于上述终端装置执行E-UTRA/5GC或者NGEN-DC,相对于与上述终端装置设定的各DRB标识符对应的DRB,进行RLC实体的重新建立以及NR PDCP实体的释放以及RLC实体的释放以及逻辑信道的释放以及DRB标识符的释放,并对与上述DRB对应的SDAP实体通知上述DRB的释放。(The present invention provides a technique relating to a terminal device, a base station device, a method, and an integrated circuit that can reduce the complexity of protocol processing and efficiently perform communication. The terminal device includes: a reception unit that receives an RRC connection reconfiguration message from a base station apparatus; and a processing unit configured to execute E-UTRA/5GC or NGEN-DC based on the terminal device when the RRC connection reconfiguration message includes information indicating that the full configuration is applied, to perform re-establishment of an RLC entity and release of an NR PDCP entity and an RLC entity and release of a logical channel and release of a DRB identifier with respect to a DRB corresponding to each DRB identifier set by the terminal device, and to notify the release of the DRB to an SDAP entity corresponding to the DRB.)

1. A terminal device that communicates with a base station device, comprising:

a reception unit that receives an RRC connection reconfiguration message from a base station apparatus; and

and a processing unit configured to, when the RRC connection reconfiguration message includes information indicating that all the settings are applied, execute E-UTRA/5GC or NGEN-DC based on the terminal apparatus, perform re-establishment of an RLC entity and release of an NR PDCP entity and an RLC entity and release of a logical channel and release of a DRB identifier for a DRB corresponding to each DRB identifier set by the terminal apparatus, and notify an SDAP entity corresponding to the DRB of the release of the DRB.

2. A terminal device that communicates with a base station device, comprising:

a reception unit that receives an RRC connection reconfiguration message from a base station apparatus; and

a processor configured to, when the RRC connection reconfiguration message includes information indicating that full configuration is to be applied, perform, based on the terminal device not executing E-UTRA/5GC or NGEN-DC, a release of the E-UTRA PDCP entity for each DRB corresponding to a value of an EPS bearer identifier included in the RRC connection reconfiguration message among values of EPS bearer identifiers set in the terminal device, when the DRB is set with an E-UTRA PDCP entity, perform a re-establishment of an RLC entity and a release of an NR entity when the DRB is not set with an E-UTRA PDCP entity, and perform a release of an RLC entity and a release of a logical channel and a release of a DRB identifier after the E-UTRA PDCP entity or the NR PDCP entity is released, performing DRB release for each DRB corresponding to a value of the EPS bearer identifier not included in the RRC connection reconfiguration message among the values of the EPS bearer identifiers set in the terminal apparatus.

3. A terminal device according to claim 2,

the DRB release processing device includes a processing unit that, in the DRB release processing, performs processing for,

when the DRB is set with an E-UTRA PDCP entity, the E-UTRA PDCP entity is released,

and when the DRB is not set with the E-UTRA PDCP entity, the reestablishment of the RLC entity and the release of the NR PDCP entity are carried out.

4. A method of a terminal device communicating with a base station device,

receiving an RRC connection reset message from the base station apparatus,

in case that information indicating application all setup is included in the RRC connection reconfiguration message,

performing E-UTRA/5GC or NGEN-DC based on the end device,

for a DRB corresponding to each DRB identifier set by the terminal device,

re-establishment of the RLC entity and release of the NR PDCP entity and the RLC entity and release of the logical channel and release of the DRB identifier are performed,

and notifying the release of the DRB to the SDAP entity corresponding to the DRB.

5. A method of a terminal device communicating with a base station device,

receiving an RRC connection reset message from the base station apparatus,

in case that information indicating application all setup is included in the RRC connection reconfiguration message,

based on the terminal device not performing E-UTRA/5GC or NGEN-DC,

for each DRB corresponding to the value of the EPS bearer identifier included in the RRC connection reconfiguration message among the values of the EPS bearer identifiers set in the terminal device,

when the DRB is set with E-UTRA PDCP entity, the E-UTRA PDCP entity is released, when the DRB is not set with E-UTRA PDCP entity, the RLC entity is reestablished and the NR PDCP entity is released,

after the E-UTRA PDCP entity or the NR PDCP entity is released, the release of the RLC entity and the release of the logical channel and the release of the DRB identifier are carried out,

performing DRB release for each DRB corresponding to a value of the EPS bearer identifier not included in the RRC connection reconfiguration message among the values of the EPS bearer identifiers set in the terminal apparatus.

6. The method of claim 5,

in the process of the DRB release, the DRB is released,

when the DRB is set with an E-UTRA PDCP entity, the E-UTRA PDCP entity is released,

and when the DRB is not set with the E-UTRA PDCP entity, the reestablishment of the RLC entity and the release of the NR PDCP entity are carried out.

7. A base station apparatus that communicates with a terminal apparatus, comprising:

a transmission unit that transmits an RRC connection reconfiguration message to the terminal apparatus; and

a processing unit that causes the terminal device to perform processing in accordance with the RRC connection reconfiguration message,

the process is a process of, i.e.,

in case that information indicating application all setup is included in the RRC connection reconfiguration message,

performing E-UTRA/5GC or NGEN-DC based on the end device,

for a DRB corresponding to each DRB identifier set by the terminal device,

re-establishment of the RLC entity and release of the NR PDCP entity and the RLC entity and release of the logical channel and release of the DRB identifier are performed,

and notifying the release of the DRB to the SDAP entity corresponding to the DRB.

8. A base station apparatus that communicates with a terminal apparatus, comprising:

a transmission unit that transmits an RRC connection reconfiguration message to the terminal apparatus; and

a processing unit that causes the terminal device to perform processing in accordance with the RRC connection reconfiguration message,

the process is a process of, i.e.,

in case that information indicating application all setup is included in the RRC connection reconfiguration message,

based on the terminal device not performing E-UTRA/5GC or NGEN-DC,

for each DRB corresponding to the value of the EPS bearer identifier included in the RRC connection reconfiguration message among the values of the EPS bearer identifiers set in the terminal device,

when the DRB is set with E-UTRA PDCP entity, the E-UTRA PDCP entity is released, when the DRB is not set with E-UTRA PDCP entity, the RLC entity is reestablished and the NR PDCP entity is released,

after the E-UTRA PDCP entity or the NR PDCP entity is released, the release of the RLC entity and the release of the logical channel and the release of the DRB identifier are carried out,

for each DRB corresponding to a value of an EPS bearer identifier not included in the RRC connection reconfiguration message among the values of EPS bearer identifiers set in the terminal device,

and performing DRB release.

9. The base station apparatus according to claim 8,

in the processing of the DRB release, the processing is performed,

when the DRB is set with an E-UTRA PDCP entity, the E-UTRA PDCP entity is released,

and when the DRB is not set with the E-UTRA PDCP entity, the reestablishment of the RLC entity and the release of the NR PDCP entity are carried out.

10. A method of a base station apparatus communicating with a terminal apparatus,

transmitting an RRC connection reset message to the terminal device,

causing the terminal device to perform processing according to the RRC connection reconfiguration message,

the process is a process of, i.e.,

in case that information indicating application all setup is included in the RRC connection reconfiguration message,

performing E-UTRA/5GC or NGEN-DC based on the end device,

for a DRB corresponding to each DRB identifier set by the terminal device,

re-establishment of the RLC entity and release of the NR PDCP entity and the RLC entity and release of the logical channel and release of the DRB identifier are performed,

and notifying the release of the DRB to the SDAP entity corresponding to the DRB.

11. A method of a base station apparatus communicating with a terminal apparatus,

transmitting an RRC connection reset message to the terminal device,

causing the terminal device to perform processing according to the RRC connection reconfiguration message,

the process is a process of, i.e.,

in case that information indicating application all setup is included in the RRC connection reconfiguration message,

based on the terminal device not performing E-UTRA/5GC or NGEN-DC,

for each DRB corresponding to the value of the EPS bearer identifier included in the RRC connection reconfiguration message among the values of the EPS bearer identifiers set in the terminal device,

when the DRB is set with E-UTRA PDCP entity, the E-UTRA PDCP entity is released, when the DRB is not set with E-UTRA PDCP entity, the RLC entity is reestablished and the NR PDCP entity is released,

after the E-UTRA PDCP entity or the NR PDCP entity is released, the release of the RLC entity and the release of the logical channel and the release of the DRB identifier are carried out,

for each DRB corresponding to a value of an EPS bearer identifier not included in the RRC connection reconfiguration message among the values of EPS bearer identifiers set in the terminal device,

and performing DRB release.

12. The method of claim 11,

in the processing of the DRB release, the processing is performed,

when the DRB is set with an E-UTRA PDCP entity, the E-UTRA PDCP entity is released,

and when the DRB is not set with the E-UTRA PDCP entity, the reestablishment of the RLC entity and the release of the NR PDCP entity are carried out.

Technical Field

The invention relates to a terminal device, a base station device and a method. The present application claims priority based on Japanese application No. 2018-176141, filed on 9/20/2018, the contents of which are incorporated herein by reference.

Background

In the third Generation Partnership Project (3rd Generation Partnership Project: 3GPP), a Radio Access scheme for cellular mobile communication, a Radio network (hereinafter referred to as "Long Term Evolution (LTE: registered trademark)"), an Evolved Universal Terrestrial Radio Access (EUTRA) ") and a Core network (hereinafter referred to as" Evolved Packet Core (EPC) ") have been studied.

In 3GPP, as a Radio access scheme and a Radio network technology suitable for a 5 th Generation (5G: 5Generation) cellular system, LTE-Advanced Pro, which is an extended technology of LTE, and nr (new Radio technology), which is a new Radio access technology, have been studied technically and standardized (non-patent document 1). Further, 5GC (5Generation Core Network) which is a Core Network suitable for the 5 th Generation cellular system has also been studied (non-patent document 2).

Documents of the prior art

Non-patent document

Non-patent document 1: 3GPP RP-170855, "Work Item on New Radio (NR) Access Technology"

Non-patent document 2: 3GPP TS 23.501v15.2.0, "System Architecture for the 5G System; stage 2 "

Non-patent document 3: 3GPP TS 36.300v15.2.0, "Evolved Universal Radio Access (E-UTRA) and Evolved Universal Radio Access Network (E-UTRAN); (ii) an Overall description; stage 2 "

Non-patent document 4: 3GPP TS 36.331v15.2.1, "Evolved Universal Radio Access (E-UTRA); radio Resource Control (RRC); protocol specifications "

Non-patent document 5: 3GPP TS 36.323v15.0.0, "Evolved Universal Radio Access (E-UTRA); packet Data Convergence Protocol (PDCP) specification "

Non-patent document 6: 3GPP TS 36.322v15.1.0, "Evolved Universal Radio Access (E-UTRA); radio Link Control (RLC) protocol specification "

Non-patent document 7: 3GPP TS 36.321V15.2.0, "Evolved Universal Radio Access (E-UTRA); medium Access Control (MAC) protocol specification "

Non-patent document 8: 3GPP TS 37.340v15.2.0, "EvalvedUniversal Radio Access (E-UTRA) and NR; Multi-Connectivity; stage 2 "

Non-patent document 9: 3GPP TS 38.300V15.2.0, "NR; NR and NG-RAN override description; stage 2 "

Non-patent document 10: 3GPP TS 38.331v15.2.1, "NR; radio Resource Control (RRC); protocol specifications "

Non-patent document 11: 3GPP TS 38.323v15.2.0, "NR; packet Data Convergence Protocol (PDCP) specification "

Non-patent document 12: 3GPP TS 38.322v15.2.0, "NR; radio Link Control (RLC) protocol specification "

Non-patent document 13: 3GPP TS 38.321v15.2.0, "NR; medium Access Control (MAC) protocol specification "

Non-patent document 14: 3GPP TS 23.401v14.3.0, "General Packet Radio Service (GPRS) enhancements for Evolved Universal Radio Access Network (E-UTRAN) Access"

Non-patent document 15: 3GPP TS 23.502v15.2.0, "Procedure for 5G System; stage 2 "

Non-patent document 16: 3GPP TS 37.324v15.0.0, "NR; service Data Addition Protocol (SDAP) specification "

Non-patent document 17: 3GPP RP-161266, "5G Architecture Options-Full Set"

Disclosure of Invention

Technical problem to be solved by the invention

As one of the studies of NR technology, the following mechanisms were studied: a configuration (MR-DC: Multi-RAT Dual Connectivity) in which cells of RATs (Radio Access technologies) of both E-UTRA and NR are grouped and allocated to UEs for each RAT, and a terminal apparatus communicates with one or more base station apparatuses (non-patent document 8).

However, there are the following problems: since the formats and functions of the communication protocols used in E-UTRA and NR are different from each other, the protocol processing becomes complicated as compared with the conventional Dual Connectivity (Dual Connectivity) in LTE in which only E-UTRA is used as a RAT, and communication between the base station apparatus and the terminal apparatus cannot be performed efficiently.

An aspect of the present invention has been made in view of the above circumstances, and an object thereof is to provide a terminal device, a base station device, a method for the terminal device, and an integrated circuit mounted on the terminal device, which can efficiently perform communication with the base station device.

Means for solving the problems

In order to achieve the above object, one aspect of the present invention adopts the following aspects. That is, a terminal apparatus which communicates with a base station apparatus, includes: a reception unit that receives an RRC connection reconfiguration message from a base station apparatus; and a processing unit configured to execute E-UTRA/5GC or NGEN-DC based on the terminal device when the RRC connection reconfiguration message includes information indicating that the full configuration is applied, to perform re-establishment of an RLC entity and release of an NR PDCP entity and an RLC entity and release of a logical channel and release of a DRB identifier for a DRB corresponding to each DRB identifier set by the terminal device, and to notify the release of the DRB to an SDAP entity corresponding to the DRB.

Another aspect of the present invention is a terminal apparatus that communicates with a base station apparatus, including: a reception unit that receives an RRC connection reconfiguration message from a base station apparatus; and a processor configured to, when the RRC connection reconfiguration message includes information indicating that the full configuration is applied, perform, based on the terminal device not executing E-UTRA/5GC or NGEN-DC, release the E-UTRA PDCP entity for each DRB corresponding to a value of the EPS bearer identifier included in the RRC connection reconfiguration message among values of EPS bearer identifiers set in the terminal device, when the DRB has the E-UTRA PDCP entity set therein, perform re-establishment of the RLC entity and release of the NR entity when the DRB has no E-UTRA PDCP entity set therein, and perform release of the RLC entity and release of the logical channel and release of the DRB identifier after the E-UTRA PDCP entity or the NR PDCP entity has been released, and performing DRB release for each DRB corresponding to a value of the EPS bearer identifier not included in the RRC connection reconfiguration message among the values of the EPS bearer identifiers set in the terminal apparatus.

Another aspect of the present invention is a method of a terminal apparatus communicating with a base station apparatus, the method including receiving an RRC connection reconfiguration message from the base station apparatus, performing E-UTRA/5GC or NGEN-DC based on the terminal apparatus when the RRC connection reconfiguration message includes information indicating that all settings are applied, performing re-establishment of an RLC entity and release of an NR PDCP entity and release of an RLC entity and release of a logical channel and release of a DRB identifier for a DRB corresponding to each DRB identifier set by the terminal apparatus, and notifying an SDAP entity corresponding to the DRB of the release of the DRB.

In addition, an aspect of the present invention is a method of a terminal apparatus communicating with a base station apparatus, the method including receiving an RRC connection reconfiguration message from the base station apparatus, when the RRC connection reconfiguration message includes information indicating that full-provisioning is applied, based on the terminal apparatus not performing E-UTRA/5GC or NGEN-DC, performing release of an E-UTRA PDCP entity for each DRB corresponding to a value of an EPS bearer identifier included in the RRC connection reconfiguration message among values of EPS bearer identifiers set in the terminal apparatus, when the DRB is set with the E-UTRA PDCP entity, when the DRB is not set with the E-UTRA PDCP entity, performing re-establishment of an RLC entity and release of an NR PDCP entity, and after the E-UTRA PDCP entity or the NR PDCP entity is released, the RLC entity is released, the logical channel is released, and the DRB identifier is released, and the DRB is released for each DRB corresponding to a value of the EPS bearer identifier not included in the RRC connection reconfiguration message among values of the EPS bearer identifiers set in the terminal apparatus.

Another aspect of the present invention is a base station apparatus for communicating with a terminal apparatus, including: a transmission unit that transmits an RRC connection reconfiguration message to the terminal apparatus; and a processing unit configured to cause the terminal device to perform a process based on the RRC connection reconfiguration message, wherein the process is a process in which, when the RRC connection reconfiguration message includes information indicating that the full configuration is applied, the terminal device executes E-UTRA/5GC or NGEN-DC, and performs re-establishment of an RLC entity and release of an NR PDCP entity and release of an RLC entity and a logical channel and release of a DRB identifier for a DRB corresponding to each DRB identifier configured by the terminal device, and notifies an SDAP entity corresponding to the DRB of the release of the DRB.

Another aspect of the present invention is a base station apparatus for communicating with a terminal apparatus, including: a transmission unit that transmits an RRC connection reconfiguration message to the terminal apparatus; and a processing unit that causes the terminal device to perform a process based on the RRC connection reconfiguration message, wherein the process includes a process of, when the RRC connection reconfiguration message includes information indicating that the full configuration is applied, performing, based on the terminal device not executing E-UTRA/5GC or NGEN-DC, releasing the E-UTRA PDCP entity for each DRB corresponding to a value of an EPS bearer identifier included in the RRC connection reconfiguration message among values of EPS bearer identifiers set in the terminal device when the DRB has the E-UTRA PDCP entity set therein, performing re-establishment of an RLC entity and release of an NR PDCP entity when the DRB has no E-UTRA PDCP entity set therein, and after the E-UTRA PDCP entity or the NR PDCP entity has been released, the RLC entity is released, the logical channel is released, and the DRB identifier is released, and the DRB is released for each DRB corresponding to a value of the EPS bearer identifier not included in the RRC connection reconfiguration message among values of the EPS bearer identifiers set in the terminal apparatus.

Another aspect of the present invention is a method for a base station apparatus communicating with a terminal apparatus, the method including transmitting an RRC connection reconfiguration message to the terminal apparatus, and causing the terminal apparatus to perform a process based on the RRC connection reconfiguration message, wherein the process includes a process of performing E-UTRA/5GC or NGEN-DC based on the terminal apparatus, performing re-establishment of an RLC entity and release of an NR PDCP entity and release of an RLC entity and a logical channel and release of a DRB identifier for a DRB corresponding to each DRB identifier set by the terminal apparatus, and notifying an SDAP entity corresponding to the DRB of the release of the DRB, when the RRC connection reconfiguration message includes information indicating that all settings are applied.

In addition, an aspect of the present invention is a method of a base station apparatus communicating with a terminal apparatus, the method including transmitting an RRC connection reconfiguration message to the terminal apparatus, and causing the terminal apparatus to perform a process based on the RRC connection reconfiguration message, wherein the process includes a process of, when the RRC connection reconfiguration message includes information indicating that all settings are applied, performing, based on the terminal apparatus not executing E-UTRA/5GC or NGEN-DC, releasing an E-UTRA PDCP entity when the DRB is set with the E-UTRA PDCP entity for each DRB corresponding to a value of an EPS bearer identifier included in the RRC connection reconfiguration message among values of EPS bearer identifiers set in the terminal apparatus, and performing RLC entity re-establishment and NR PDCP entity release when the DRB is not set with the E-UTRA PDCP entity, after the E-UTRA PDCP entity or the NR PDCP entity is released, an RLC entity is released, a logical channel is released, and a DRB identifier is released, and the DRB is released for each DRB corresponding to an EPS bearer identifier value not included in the RRC connection reconfiguration message among EPS bearer identifier values set in the terminal device.

The general or specific aspects may be implemented by a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or any combination of the system, the apparatus, the method, the integrated circuit, the computer program, and the recording medium.

Effects of the invention

According to an aspect of the present invention, a terminal apparatus can efficiently perform communication by reducing the complexity of protocol processing.

Drawings

Fig. 1 is a schematic diagram of a communication system according to each embodiment of the present invention.

Fig. 2 is a protocol stack diagram of UP and CP of a terminal device and a base station device of E-UTRA according to each embodiment of the present invention.

Fig. 3 is a protocol stack diagram of UP and CP of the NR terminal device and the base station device according to each embodiment of the present invention.

Fig. 4 is a diagram showing an example of the flow of the RRC connection reconfiguration procedure according to each embodiment of the present invention.

Fig. 5 is a block diagram showing a configuration of a terminal device according to each embodiment of the present invention.

Fig. 6 is a block diagram showing a configuration of a base station apparatus according to each embodiment of the present invention.

Fig. 7 is a part (first page) of a diagram showing an example of information related to radio bearer setup and asn.1(Abstract Syntax Notation One) description of the information according to each embodiment of the present invention.

Fig. 8 is a part (second page) of a diagram showing an example of information related to radio bearer setup and asn.1(Abstract Syntax notification One) description of the information according to each embodiment of the present invention.

Fig. 9 shows an example of a processing method according to the embodiment of the present invention.

Fig. 10 shows another example of the processing method according to the embodiment of the present invention.

Detailed Description

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

LTE (as well as LTE-A Pro) and NR may be defined as different RATs. Further, NR may be defined as a technology included in LTE. LTE may be defined as the technology covered by NR. Note that LTE that can be connected to NR by Multi-RAT Dual connectivity (Multi RAT Dual connectivity) or LTE that can be connected to a 5G core network (5GC) can be distinguished from conventional LTE. The present embodiment can also be applied to NR, LTE, and other RATs. In the following description, terms related to LTE and NR are used, but the terms may be applied to other technologies using other terms. In addition, the term E-UTRA in the present embodiment may be replaced with the term LTE, and the term LTE may be replaced with the term E-UTRA.

Fig. 1 is a schematic diagram of a communication system according to each embodiment of the present invention.

E-UTRA100 is a radio access technology described in non-patent document 3 and the like, and is composed of a Cell Group (CG) composed of one or more frequency bands. The eNB (E-UTRAN Node B)102 is a base station apparatus of E-UTRA. Epc (evolved Packet core)104 is a core network described in non-patent document 14 and the like, and is designed as a core network for E-UTRA. The interface 112 is an interface (interface) between the eNB102 and the EPC104, and includes a Control Plane (CP) through which Control signals pass and a User Plane (UP) through which User data passes.

NR106 is a radio access technology described in non-patent document 9 and the like, and is composed of a Cell Group (CG) composed of one or more frequency bands. gNB (g Node B)108 is an NR base station apparatus. The 5GC110 is a 5G core network described in non-patent document 2 and the like, and is designed as a core network for NR, but may be used as a core network of E-UTRA having a function of connecting to the 5 GC. Hereinafter, the E-UTRA may include E-UTRA having a function of linking to 5 GC.

Interface 114 is an interface between eNB102 and 5GC110, interface 116 is an interface between gNB108 and 5GC110, interface 118 is an interface between gNB108 and EPC104, interface 120 is an interface between eNB102 and gNB108, and interface 124 is an interface between EPC104 and 5GC 110. The interfaces 114, 116, 118, 120, and 124 are CP-only or UP-only interfaces, or both CP and UP interfaces. In addition, interfaces 114, 116, 118, 120, 124 may also be absent depending on the communication system provided by the communication enterprise.

The UE122 is a terminal device corresponding to E-UTRA, NR, or both E-UTRA and NR.

Fig. 2 is a diagram of a Protocol Stack (Protocol Stack) of UP and CP of a terminal device and a base station device in an E-UTRA radio access layer according to each embodiment of the present invention.

Fig. 2 (a) is a protocol stack diagram of UP used when UE122 communicates with eNB 102.

The PHY (Physical Layer) 200 is a radio Physical Layer (radio Physical Layer) and provides a transport service to an upper Layer (upper Layer) by using a Physical Channel (Physical Channel). The PHY200 is connected to a higher mac (medium Access Control layer)202, which will be described later, via a Transport Channel (Transport Channel). Data moves between the MAC202 and the PHY200 via transport channels. Data is transmitted and received between the UE122 and the PHY of the eNB102 via a wireless physical channel.

The MAC202 is a medium access control Layer (medium access control Layer) that maps various Logical (LCH) channels to various transport channels. The MAC202 is connected to an rlc (radio Link Control layer)204, which is an upper layer, described later, via a logical channel. Logical channels are roughly classified into control channels for transmitting control information and traffic channels for transmitting user information, depending on the type of information to be transmitted. The MAC202 has a function of controlling the PHY200 to perform intermittent transmission/reception (DRX/DTX), a function of executing a Random Access (Random Access) procedure, a function of notifying information of transmission power, a function of performing HARQ control, and the like (non-patent document 7).

The RLC204 is a radio link control Layer (radio link control Layer) that divides (segments) Data received from a higher pdcp (packet Data conversion Protocol Layer)206 described later and adjusts the Data size so that a lower Layer (lower Layer) can appropriately transmit Data. In addition, the RLC200 has a function of guaranteeing qos (quality of service) of each data request. That is, the RLC204 has a function of controlling retransmission of data and the like (non-patent document 6).

The PDCP206 is a Packet data convergence protocol Layer (PDCP Layer) for efficiently transmitting IP packets (IP packets) as user data between radio zones. The PDCP206 may also have a header compression function that compresses unnecessary control information. Further, the PDCP206 may have a function of encrypting data (non-patent document 5).

The Data processed in the MAC202, RLC204, and PDCP206 are referred to as MAC PDU (Protocol Data Unit), RLC PDU, and PDCP PDU, respectively. Data transferred from the upper layer to the MAC202, RLC204, and PDCP206, or Data transferred to the upper layer is referred to as a MAC SDU (Service Data Unit), RLC SDU, and PDCP SDU, respectively.

Fig. 2 (B) is a protocol stack diagram of a CP used when UE122 communicates with eNB 102.

In the protocol stack of the CP, in addition to the PHY200, MAC202, RLC204, PDCP206, there is an rrc (radio Resource Control layer) 208. The RRC208 is a Radio link control Layer (Radio link control Layer) that performs control of logical channels, transport channels, and physical channels, such as setting and resetting of Radio Bearers (RBs). The RB may be divided into a Signaling Radio Bearer (SRB) and a Data Radio Bearer (DRB), and the SRB may be used as a path for transmitting an RRC message as control information. The DRB may be used as a path for transmitting user data. Each RB can be set between the eNB102 and the RRC208 of the UE122 (non-patent document 4).

The functions of the MAC202, the RLC204, the PDCP206, and the RRC208 are classified as an example, and a part or all of the functions may not be installed. In addition, a part or all of the functions of each layer may be included in other layers. The functions of the MAC202, RLC204, PDCP206, and RRC208 layers and/or the (and/or) layers may be referred to as entities (entities). That is, the MAC layer may be referred to as a MAC entity, the RLC layer may be referred to as an RLC entity, the PDCP layer may be referred to as a PDCP entity, and the RRC layer may be referred to as an RRC entity.

The IP layer and a TCP (Transmission Control Protocol) layer, a UDP (User Datagram Protocol) layer, an application layer, and the like, which are layers higher than the IP layer, are higher layers (not shown) of the PDCP layer. The RRC layer and the nas (non Access stratum) layer also serve as an upper layer (not shown) of the PDCP layer. In other words, the PDCP layer is a lower layer of the RRC layer, the NAS layer, the IP layer, and a tcp (transmission Control protocol) layer, a udp (user data protocol) layer, and an application layer, which are upper layers than the IP layer.

Fig. 3 is a diagram of UP and CP Protocol stacks (Protocol stacks) of a terminal device and a base station device in an NR radio access layer according to each embodiment of the present invention.

Fig. 3 (a) is a protocol stack diagram of an UP used when UE122 communicates with gNB 108.

The phy (Physical Layer)300 may be a radio Physical Layer (radio Physical Layer) of the NR, and may provide a transport service to an upper Layer using a Physical Channel (Physical Channel). The PHY300 may be connected to a higher mac (medium Access Control layer)302, which will be described later, via a Transport Channel (Transport Channel). Data may move between the MAC302 and the PHY300 via transport channels. Data may be transmitted and received between UE122 and the PHY of gNB108 via a radio physical channel.

The MAC302 is a medium access control Layer (medium access control Layer) that maps various Logical (LCH) channels to various transport channels. The MAC302 may be connected to an upper rlc (radio Link Control layer)304 described later through a logical channel. Logical channels may be roughly classified according to the type of information to be transmitted, and may be classified into control channels for transmitting control information and traffic channels for transmitting user information. The MAC302 may have a function of controlling the PHY300 to perform intermittent transmission/reception (DRX/DTX), a function of executing a Random Access (Random Access) procedure, a function of notifying information of transmission power, a function of performing HARQ control, and the like (non-patent document 13).

The RLC304 is a radio link control Layer (radio link control Layer) that divides (segments) Data received from a higher pdcp (packet Data conversion Protocol Layer)306, which will be described later, and adjusts the Data size so that a lower Layer can appropriately transmit Data. In addition, the RLC304 may have a function of guaranteeing qos (quality of service) of each data request. That is, the RLC304 may have a function of controlling retransmission of data or the like (non-patent document 12).

The PDCP306 is a Packet data convergence protocol Layer (PDCP Layer) that efficiently transmits IP packets (IP packets) as user data between radio zones. The PDCP306 may also have a header compression function for compressing unnecessary control information. In addition, the PDCP306 may also have a function of ciphering data (non-patent document 11).

The SDAP (Service Data Adaptation Protocol) 310 is a Service Data Adaptation Protocol Layer (Service Data Adaptation Protocol Layer) that has the following functions: the mapping is performed to associate (map) a downlink QoS flow transmitted from the core network to the terminal device via the base station device with a DRB and to map an uplink QoS flow transmitted from the terminal device to the core network via the base station device with a DRB, and mapping rule information is stored (non-patent document 16). When the terminal device receives SDAP SDU and QoS flow information from an upper layer at the same time, the SDAP SDU is allocated to a corresponding DRB based on the stored mapping rule between the QoS flow and the DRB. The SDAP SDU can also be allocated to a default radio bearer (default DRB) in case no mapping rule of QoS flow and DRB is stored. The QoS Flow is composed of one or more Service Data Flows (SDFs) handled by the same QoS policy (non-patent document 2). The SDAP may also have a function of a reflection type QoS (reflective QoS) that maps an uplink QoS flow and a DRB based on information of a downlink QoS flow. Further, when the association rule between the QoS flow and the DRB is changed, an End Marker (End Marker) control PDU may be created and transmitted to the DRB before the change, thereby ensuring in-sequence delivery of the SDAP SDUs (non-patent document 2 and non-patent document 16).

The end-marker control PDU is the SDAP control PDU described in non-patent document 16, and is used to notify the SDAP entity of the UE to end the association (mapping) between the QoS flow corresponding to the QoS flow identifier included in the QoS flow identifier field of the end-marker PDU and the radio bearer that transmitted the end-marker PDU.

The IP layer and a tcp (transmission Control protocol) layer, udp (user data program) layer, application layer, and the like, which are layers higher than the IP layer, are higher layers (not shown) of the SDAP layer. The RRC layer and the nas (non Access stratum) layer also serve as an upper layer (not shown) of the SDAP layer. In the NAS layer, correspondence between service data flows and QoS flows is performed. In other words, the SDAP layer is a lower layer than the RRC layer, the NAS layer, the IP layer, and a tcp (transmission Control protocol) layer, a udp (user data protocol) layer, and an application layer that are higher than the IP layer.

The Data processed by the MAC302, RLC304, PDCP306, and SDAP310 may be referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Data transferred from the upper layer to the MAC202, RLC204, and PDCP206, or Data transferred to the upper layer may be referred to as MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively.

Fig. 3 (B) is a protocol stack diagram of a CP used when UE122 communicates with gNB 108.

In the protocol stack of the CP, in addition to the PHY300, MAC302, RLC304, PDCP306, there is an rrc (radio Resource Control layer) 308. The RRC308 is a Radio link control Layer (Radio link control Layer) that performs setting/resetting of Radio Bearers (RBs) and controls logical channels, transport channels, and physical channels. The RB may be divided into a Signaling Radio Bearer (SRB) and a Data Radio Bearer (DRB), and the SRB may be used as a path for transmitting an RRC message as control information. The DRB may be used as a path for transmitting user data. The RBs may be set between the gNB108 and the RRC308 of the UE 122. Note that a part of the RB including the RLC304 and the MAC302 may be referred to as an RLC bearer (non-patent document 10).

The functional classifications of the MAC302, RLC304, PDCP306, SDAP310, and RRC308 are examples, and some or all of the functions may not be installed. In addition, a part or all of the functions of each Layer (Layer) may be included in the other Layer (Layer). Each layer and/or function of each layer of the MAC302, RLC304, PDCP306, SDAP310, and RRC308 may be referred to as an entity (entity). That is, the MAC layer may also be referred to as a MAC entity, the RLC layer as an RLC entity, the PDCP layer as a PDCP entity, and the RRC layer as an RRC entity.

In each embodiment of the present invention, in order to distinguish the following E-UTRA protocol from NR protocol, MAC202, RLC204, PDCP206, and RRC208 are also referred to as E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively. The MAC302, RLC304, PDCP306, and RRC308 are also referred to as NR MAC, NR RLC, and NR RRC, respectively. Alternatively, the description may be described using spaces such as E-UTRA PDCP, LTE PDCP, NR PDCP, etc.

As shown in fig. 1, eNB102, gNB108, EPC104, 5GC110 may be connected via interface 112, interface 116, interface 118, interface 120, and interface 114. Therefore, in order to support various communication systems, the RRC208 in fig. 2 may be replaced with the RRC308 in fig. 3. In addition, the PDCP206 of fig. 2 may be replaced with the PDCP306 of fig. 3. In addition, RRC308 of fig. 3 may also include the functionality of RRC208 of fig. 2. In addition, the PDCP306 of FIG. 3 can also be the PDCP206 of FIG. 2.

(embodiment mode)

An embodiment of the present invention will be described with reference to fig. 1 to 10.

Fig. 4 is a diagram showing an example of the flow of the RRC connection reconfiguration procedure according to each embodiment of the present invention. Further, the RRC connection reconfiguration procedure may be an RRC reconfiguration procedure.

The RRC Connection Reconfiguration procedure (RRC Connection Reconfiguration) is a procedure for setting up, changing, and releasing Radio Bearers (RBs) of LTE, changing and releasing secondary cells, and setting up handover, Measurement (Measurement), and the like, in addition to the procedure described in non-patent document 4. On the other hand, the RRC Reconfiguration procedure (RRC Reconfiguration) is a procedure for setting up, changing, and releasing the RBs of the NR, changing and releasing the secondary cell, and the like, and also for switching (Reconfiguration with synchronization), Measurement (Measurement), and the like, in addition to the setting of the RBs of the NR described in non-patent document 10. In order to set up, change, release, change of secondary cell, release, handover, measurement, and the like of the above-described RB, information included in each message of the RRC connection reconfiguration procedure is referred to as setting information in the embodiment of the present invention. The setting information is not limited to the above setting, and may be other settings, and may be included in each message of other procedures, without being limited to the RRC connection reconfiguration procedure.

In addition, in the case of the RRC connection reconfiguration procedure in MR-DC, particularly in EN-DC (E-UTRA-NR Dual Connectivity) which is MR-DC in the case where the core network is the EPC104 and the primary node is the eNB102 (also referred to as the extended eNB102) (option 3 and option 3a described in non-patent document 17), in NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity) which is MR-DC in the case where the core network is the 5GC110 and the primary node is the eNB102 (option 7 and option 7a described in non-patent document 17), and in the case where the eNB102 (extended eNB) uses 5GC as the E-UTRA/5GC of the core network (option 5 described in non-patent document 17), the RRC connection reconfiguration procedure includes not only the setting information of LTE but also the setting information of NR described in non-patent document 10 in the form of contents. In each embodiment of the present invention, in order to avoid the complexity of the description, the description will be given using the name of the RRC connection reconfiguration procedure, and the eNB102 will be used as the base station apparatus. Further, the names of the structures such as EN-DC, NGEN-DC, and E-UTRA/5GC may be referred to as other names instead of the names described above.

In the RRC connection reconfiguration procedure, the UE122 receives an RRC connection reconfiguration message (rrccnnectionreconfiguration) from the eNB102 (step S400), and performs various processes such as setting of radio bearers based on the setting information included in the RRC connection reconfiguration message (step S402). After step S402, the UE122 may transmit an RRC connection reconfiguration complete message (rrcconnectionreconfiguration complete) or the like (not shown) to the eNB 102. Further, the RRC connection reconfiguration message may be alternatively referred to as RRC connection reconfiguration, and the RRC connection reconfiguration complete message may be alternatively referred to as RRC connection reconfiguration complete.

Fig. 5 is a block diagram showing a configuration of a terminal apparatus (UE122) according to each embodiment of the present invention. In order to avoid the complicated description, fig. 5 shows only the main components that are closely related to one aspect of the present invention.

The UE122 shown in fig. 5 includes: a reception unit 500 that receives an RRC connection reconfiguration message and the like from the eNB 102; and a processing unit 502 for performing processing based on the setting information and the like included in the received message.

Fig. 6 is a block diagram showing a configuration of a base station apparatus (eNB102) according to each embodiment of the present invention. In order to avoid the complicated description, fig. 6 shows only the main components that are closely related to one aspect of the present invention.

The eNB102 shown in fig. 6 includes: a transmitter 600 that transmits an RRC connection reconfiguration message and the like to the UE 122; and a processing unit 602 that causes the processing unit 502 of the UE122 to perform processing by creating an RRC connection reconfiguration message including various kinds of configuration information and the like and transmitting the RRC connection reconfiguration message to the UE 122. The structure shown in fig. 6 can also be applied to the gNB 108. When applied to the gNB108, the message transmitted from the transmitter 600 to the UE122 may be an RRC reconfiguration message.

Fig. 7 is a part (first page) of a diagram showing an example of a description of asn.1(Abstract Syntax notification One) of the configuration information and the like included in the RRC connection reconfiguration message in fig. 4 according to the embodiments of the present invention. Fig. 8 is a part (second page) of a diagram showing an example of the description of asn.1 of the configuration information and the like included in the RRC connection reconfiguration message in fig. 4 in each embodiment of the present invention. In 3GPP, specifications related to RRC (non-patent document 4 and non-patent document 10) describe messages, configuration information, and the like using asn.1. The setting Information of asn.1 mainly includes fields and Information Elements (IE). In the example of asn.1 in fig. 7 and 8, < abbreviated > and < abbreviated > indicate that other information is omitted, rather than part of the expression of asn.1. Note that, where the description of < abbreviated > or < abbreviated > is not provided, the information element may be omitted. The asn.1 example of fig. 7 and 8 is not an example of a method accurately expressed by asn.1, and an example of the setting information for RRC connection reconfiguration according to the present invention is shown, and other names and other expressions may be used for the fields and information elements. In addition, the examples of asn.1 in fig. 7 and 8 only show examples of main information that is closely related to one aspect of the present invention in order to avoid the description becoming complicated.

In the example of fig. 7, the symbol ": : the setting information included in RRC connection reconfiguration (rrcconnectionreconfiguration) is denoted by SEQUENCE. In the example of fig. 7, the setting information included in the RRC connection reconfiguration may include setting information indicated by the radioResourceConfigDedicated field and setting information indicated by the fullConfig field, and may be included as an option (option) as setting information of the RRC connection reconfiguration when separate setting is required, in other words. The details of the radioResourceConfigDedicated field may be additionally described by an information element shown in the radioResourceConfigDedicated field. The setting information indicated by the fullConfig field may be setting information indicating that the full setting is applied after the radio bearer is reestablished at the time of handover, or may be expressed as "true" when the full setting is applied.

In fig. 7, the information element indicated by the RadioResourceConfigDedicated may be used for establishment (setup), modification (modify), release (release), setting of the MAC entity, and the like of the radio bearer. In the example of fig. 7, the information element represented by the RadioResourceConfigDedicated may have setting information represented by srb-ToAddModList field and drb-ToAddModList field, and may be set as an option when setting is required, in other words, the setting information may be included as the information element represented by the RadioResourceConfigDedicated. The details of such a field SRB-ToAddModList and the DRB-ToAddModList field may also be described separately by the information element represented by SRB-ToAddModList and the information element represented by DRB-ToAddModList, respectively.

As shown in the example of fig. 7, the information elements represented by SRB-ToAddModList may be a list of information elements represented by SRB-ToAddMod, and the information elements represented by SRB-ToAddMod may be setting information related to the added (add) or changed (modify) SRB. As shown in the example of fig. 7, the information element indicated by SRB-ToAddMod may include the setting information indicated by the SRB-Identity field, and the setting information indicated by the SRB-Identity field may be an SRB identifier that uniquely identifies the SRB, or may have any value of 1 or 2.

As shown in the example of fig. 8, the information elements represented by DRB-ToAddModList may be a list of information elements represented by DRB-ToAddMod, and the information elements represented by DRB-ToAddMod may be setting information related to the DRB to be added (add) or changed (modify). As shown in the example of fig. 8, the information element indicated by DRB-ToAddMod may include setting information indicated by DRB-Identity field, and the setting information indicated by DRB-Identity field may be a DRB identifier that uniquely identifies a DRB, or may be any one of integers from 1 to 32. In the case of DC, the DRB identifier may also be inherent within the range of the UE 122.

As shown in the example of fig. 8, the information element represented by DRB-ToAddMod may include an EPS-bearer identity field as an option, and the setting information represented by the EPS-bearer identity field may be an EPS bearer identifier used in the EPC104 to uniquely identify the EPS bearer described in non-patent document 3, or may use any one of integers from 0 to 15. In addition, the corresponding information of the EPS bearer identifier and the aforementioned DRB identifier may also be maintained within the UE 122.

As shown in the example of fig. 8, the information element indicated by DRB-ToAddMod may optionally include setting information indicated by the PDCP-Config field and the PDCP-Config information element, and the setting information indicated by the PDCP-Config field and the PDCP-Config information element may be information related to the setting of the PDCP entity. The setting information indicated by the PDCP-Config field and the PDCP-Config information element included in the RRC connection reconfiguration message may be the setting information of the E-UTRA PDCP entity. In other words, the RRC connection reconfiguration message including the setting information represented by the PDCP-Config field and the PDCP-Config information element may also refer to setting the E-UTRA PDCP.

As shown in the example of fig. 8, the information element indicated by DRB-ToAddMod may optionally include setting information indicated by the RLC-Config field and the RLC-Config information element, and the setting information indicated by the RLC-Config field and the RLC-Config information element may be information related to the setting of the RLC entity.

As shown in the example of fig. 8, the information element indicated by DRB-ToAddMod may include, as options, setting information indicated by the Logical channelconfig field and the Logical channelconfig information element, and the setting information indicated by the Logical channelconfig field and the Logical channelconfig information element may be information related to setting of a dtch (differentiated Traffic channel) Logical (Logical) channel. Further, the information element indicated by DRB-ToAddMod may include setting information indicated by a locatalchannel identity field, and the setting information indicated by the locatalchannel identity field may be a logical channel identifier that uniquely identifies the DTCH logical channel, or may take any one of integers of 3 to 10.

An example of a processing method of the UE122 according to the embodiment of the present invention will be described with reference to fig. 9.

The processor 602 of the eNB102 creates an RRC connection reconfiguration message including a fullConfig field which is configuration information indicating application-wide configuration for processing by the UE122, and transmits the RRC connection reconfiguration message to the UE122 from the transmitter 600 (not shown). The receiver 500 of the UE122 receives the RRC connection reconfiguration message including the fullConfig field from the eNB102 (step S900).

Next, the processing unit 502 of the UE122 confirms that the RRC connection reconfiguration message includes the fullConfig field, which is the configuration information indicating that the full configuration is applied, and performs the following processing (the processing of step S904 and/or step S906 to be described later) based on the fullConfig field (step S902).

When the E-UTRA/5GC or NGEN-DC is executed, the processor 502 of the UE122 performs the release of the PDCP entity and/or the RLC entity and/or the release of the logical channel and/or the release of the DRB identifier for all DRB identifiers set in the UE122 or DRBs corresponding to the DRB identifiers, based on the execution of the E-UTRA/5GC or the NGEN-DC (step S904).

Further, in step S904, the release of the PDCP entity may also be a release of the NR PDCP entity. In addition, in step S904, the (Re-establish) RLC entity may also be Re-established before the PDCP entity is released. In addition, in step S904, the logical channel may be a DTCH logical channel. In addition, in step S904, the MCG security setting may also be released. The release of the MCG security settings described above may also be performed based on whether the core network is handed over from 5GC110 to EPC104 or redirected from 5GC110 to EPC 104. The determination may be made based on the fact that the setting information not accompanying the change of the core network or the setting information in the 5GC110 is not included in the setting information related to the NR RRC reestablishment included in the RRC connection reconfiguration or the RRC connection reconfiguration, or the determination may be made that the core network is involved in the handover from the 5GC110 to the EPC104 or the redirection from the 5GC110 to the EPC104 based on the fact that the setting information related to the NR RRC reestablishment included in the RRC connection reconfiguration or the RRC connection reconfiguration includes the setting information for the change from the 5GC110 to the EPC 104. Further, it is also possible to determine that the above-described core network is a handover accompanied by a change from the 5GC110 to the EPC104 or a redirection from the 5GC110 to the EPC104 based on a case where the DRB-ToAddModList or DRB-ToAddMod, which is the setting information related to the added or changed DRB included in the RRC connection reconfiguration message, includes information related to the setting of the PDCP entity, that is, a case where the PDCP-Config or PDCP-Config is included, that is, the E-UTRA PDCP entity is set.

When the E-UTRA/5GC or NGEN-DC is executed, the processing unit 502 of the UE122 may notify the release of the DRB to the SDAP entity corresponding to the DRB based on the execution of the E-UTRA/5GC or NGEN-DC (step S906). When the E-UTRA/5GC or the NGEN-DC is executed, the processing unit 502 of the UE122 may release all the SDAP entities set in the UE122 after performing DRBs for all the DRB identifiers set in the UE122 or for DRBs corresponding to the DRB identifiers based on the execution of the E-UTRA/5GC or the NGEN-DC, that is, after the process of step S904 is completed.

In addition, when the RRC connection reconfiguration message includes the fullConfig field to execute E-UTRA/5GC or NGEN-DC, the processor 502 of the UE122 may release (release) and/or remove (clear) all the dedicated (Radio configuration) information except the C-rnti (cell Radio Network Temporary identifier) setting information based on the execution of E-UTRA/5GC or NGEN-DC. In this case, there is other setting information that is not the target of the release and/or removal processing described above in addition to the C-RNTI. In addition, at this time, the C-RNTI may also be released. The determination of what configuration information is to be removed from the release and/or removal process may be determined based on whether or not the application of the full configuration involves a change of the core network. For example, the MCG security setting may be removed from the release and/or removal processing described above based on the full setting that does not involve the change of the core network or the full setting in the 5GC core network. The determination of the above-described all-setup without changing the core network or all-setup in the 5GC core network may be determined based on the fact that the setting information associated with the NR RRC reestablishment included as a content in the RRC connection reconfiguration or the RRC connection reconfiguration includes the setting information not associated with the change of the core network or the setting information in the 5GC110, or may be determined based on the fact that the setting information associated with the NR RRC reestablishment included as a content in the RRC connection reconfiguration or the RRC connection reconfiguration does not include the setting information associated with the change from the 5GC110 to the EPC 104. The determination that the core network is switched with the change from the 5GC110 to the EPC104 or the redirection from the 5GC110 to the EPC104 may be performed based on a case where the DRB-ToAddModList or DRB-ToAddMod, which is the setting information on the added or changed DRB included in the RRC connection reconfiguration message, does not include information on the setting of the PDCP entity, that is, a case where the PDCP-Config or PDCP-Config is not included, that is, the NR PDCP entity is set.

The processor 502 of the UE122 may also set up an E-UTRA PDCP entity by releasing the NR PDCP entity based on the UE122 executing E-UTRA/5GC or NGEN-DC with respect to the SRB corresponding to the value of each SRB-Identity included in the SRB-ToAddModList included in the RRC connection reconfiguration message based on the fullConfig field included in the RRC connection reconfiguration message.

Another example of the processing method of the UE122 according to the embodiment of the present invention will be described with reference to fig. 10.

The processing unit 602 of the eNB102 creates an RRC connection reconfiguration message including the fullConfig field, which is configuration information indicating application-wide configuration to be processed by the UE122, and transmits the message from the transmission unit 600 to the UE122 (not shown). The receiver 500 of the UE122 receives the RRC connection reconfiguration message from the eNB102 (step S1000).

Next, the processing unit 502 of the UE122 confirms that the RRC connection reconfiguration message includes the fullConfig field, which is the configuration information indicating that the full configuration is applied, and performs the following processing (the processing of step S1004 and/or step S1006 described later) based on the fullConfig field (step S1002).

The processing unit 502 of the UE122 performs the release of the PDCP entity and/or the RLC entity and/or the release of the logical channel and/or the release of the DRB identifier for each DRB corresponding to the value of the EPS bearer identifier included in the RRC connection reconfiguration message set in the EPS bearer identifier of the UE122 (step S1004). The processing of step S1004 described above may be performed based on the UE122 not performing E-UTRA/5GC or NGEN-DC.

In addition, in step S1004, the release of the PDCP entity may be alternatively referred to as the release of the NR PDCP entity or the E-UTRA PDCP entity. In addition, in step S1004, the release of the PDCP entity may be referred to as releasing the E-UTRA PDCP entity when the E-UTRA PDCP entity is set in the DRB, or may be referred to as releasing the NR PDCP entity otherwise, that is, when the NR PDCP entity is set in the DRB. In addition, a (re-established-invalid) RLC entity may also be re-established before the NR PDCP entity is released.

The processing unit 502 of the UE122 may perform DRB release processing for each DRB corresponding to a value of an EPS bearer identifier not included in the RRC connection reconfiguration message, among the EPS bearer identifiers set in the UE122 (step S1006). The aforementioned processing of step 1006 may also be performed based on the UE122 not performing E-UTRA/5GC or NGEN-DC. In step S1006, the DRB release process may be a process of releasing the NR PDCP entity when the E-UTRA PDCP entity is not set in the DRB, that is, when the NR PDCP entity is set. In addition, a (re-established-invalid) RLC entity may also be re-established before the NR PDCP entity is released.

Further, the processor 502 of the UE122 may release the NR PDCP entity and establish the E-UTRA PDCP entity based on the setting information that the UE122 does not perform E-UTRA/5GC or NGEN-DC or that the security key is not changed with respect to the SRB corresponding to the value of each SRB-Identity included in the SRB-ToAddModList included in the RRC connection reconfiguration message based on the fullConfig field included in the RRC connection reconfiguration message, and may apply the security setting set for the UE 122.

The radio bearer configuration according to each embodiment of the present invention may be included not only in the RRC connection reconfiguration procedure but also in the RRC connection establishment procedure, the RRC connection reconfiguration procedure, and the like. In the embodiments of the present invention, DRBs may be referred to as SRBs, and SRBs may be referred to as DRBs. Further, DRBs and/or SRBs may also be referred to as radio bearers instead.

In each embodiment of the present invention, when a change is made to a core network, for example, when a change is made from 5GC110 to EPC104 or when a change is made from EPC104 to 5GC110, radio bearer release processing and radio bearer addition processing may be performed by one RRC connection reconfiguration message and/or one RRC reconfiguration message. That is, the setting information on the release of all radio bearers or DRBs set in the terminal device and the setting information on the radio bearers or DRBs added to the terminal device may be included in one RRC connection reconfiguration message and/or one RRC reconfiguration message. In addition, at this time, the same radio bearer identifier may also be used.

As described above, according to the embodiments of the present invention, by performing the full setting in consideration of the MR-DC addition, it is possible to reduce the complexity of the protocol processing and efficiently perform communication between the base station apparatus and the terminal apparatus.

The program that operates in the apparatus according to the present invention may be a program that controls a Central Processing Unit (CPU) or the like to function as a computer so as to realize the functions of the above-described embodiments according to the present invention. The program or information processed by the program is temporarily read into a volatile Memory such as a Random Access Memory (RAM), or stored in a nonvolatile Memory such as a flash Memory, or a Hard Disk Drive (HDD) during processing, and read, corrected, and written by the CPU as necessary.

Further, a part of the apparatus of the above-described embodiment may be realized by a computer. In this case, the program for realizing the control function may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read and executed by a computer system. The term "computer system" as used herein refers to a computer system built in the apparatus, and includes hardware such as an operating system and peripheral devices. In addition, the "computer-readable recording medium" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, and the like.

Also, the "computer-readable recording medium" may include: a medium that dynamically stores a program in a short time such as a communication line when the program is transmitted via a network such as the internet or a communication line such as a telephone line; a medium that holds a program for a constant time is used as a volatile memory in a computer system as a server or a client in this case. The program may be a program for realizing a part of the above-described functions, or may be a program that can be further realized by combining the above-described functions with a program already recorded in a computer system.

In addition, each functional block or each feature of the device used in the above-described embodiments can be mounted or executed by a circuit, that is, typically, an integrated circuit or a plurality of integrated circuits. A circuit designed in such a way as to perform the functions described in this specification may include: general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic elements, discrete gate or transistor logic, discrete hardware elements, or combinations thereof. A general purpose processor may be a microprocessor, which may instead be a conventional processor, controller, microcontroller, or state machine. The general-purpose processor or each of the circuits described above may be configured by a digital circuit or an analog circuit. In addition, when a technology for forming an integrated circuit that replaces a conventional integrated circuit has appeared with the progress of semiconductor technology, an integrated circuit based on the technology may be used.

The present invention is not limited to the above-described embodiments. In the embodiments, although an example of the device is described, the present invention is not limited to this, and can be applied to stationary or non-movable electronic devices installed indoors and outdoors, for example, terminal devices or communication devices such as AV equipment, kitchen equipment, cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other living equipment.

While the embodiments of the present invention have been described above with reference to the drawings, the specific configuration is not limited to the embodiments, and design changes and the like are included without departing from the scope of the present invention. The present invention can be variously modified within the scope shown in the claims, and embodiments obtained by appropriately combining the technical means disclosed in the respective embodiments are also included in the technical scope of the present invention. The present invention also includes a configuration in which elements having the same effects as those described in the above embodiments are replaced with each other.