Patent Description:
A radio access method and a radio network for cellular mobile communications (which will hereinafter be referred to as "Long Term Evolution (LTE; trade name)"or "Evolved Universal Terrestrial Radio Access (E-UTRA)") and a core network (which will be referred to as "Evolved Packet Core or EPC") have been studied by the 3rd Generation Partnership Project (3GPP).

Furthermore, as a radio access method and a radio network technology for a 5th generation cellular system, technical studies and standardization of LTE-Advanced Pro which is an enhanced technology of LTE and New Radio technology (NR) which is a new radio access technology have been conducted by the 3GPP (NPL <NUM>). Furthermore, <NUM> Generation Core Network (5GC), which is a core network for the 5th generation cellular system, has also been studied (NPL <NUM>).

As one of the technical studies of NR, a mechanism called Multi -RAT Dual Connectivity (MR-DC) is being studied that allows cells of radio access technologies (RATs) of both E-UTRA and NR to be grouped into a cell group an a RAT basis and to be allocated to UE such that a terminal apparatus communicates with one or more base station apparatuses (NPL <NUM>).

However, since the formats and functions of the communication protocols used in the E-UTRA and the NR differ, there is a problem in that the protocol processing becomes complex compared to Dual Connectivity in existing LTE using only E-UTRA as a RAT, and thus a base station apparatus and a terminal apparatus are not able to efficiently communicate with each other.

One aspect of the present invention is realized with the situations described above taken into account, and one object thereof is to provide a terminal apparatus capable of efficiently communicating with a base station apparatus, a base station apparatus communicating with the terminal apparatus, a method used for the terminal apparatus, a method used for the base station apparatus, and an integrated circuit mounted in the terminal apparatus.

In order to accomplish the object described above, an aspect of the present invention is contrived to provide the following means. One aspect of the present invention is a terminal apparatus according to claim <NUM>.

One aspect of the present invention is a base station apparatus according to claim <NUM>.

An aspect of the present invention is a method performed by a terminal apparatus that communicates with one or multiple base station apparatuses, according to claim <NUM>.

An aspect of the present invention is a method performed by a base station apparatus that communicates with a terminal apparatus, according to claim <NUM>.

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

LTE (and LTE-A Pro) and NR may be defined as different RATs. The NR may be defined as a technology included in the LTE. The LTE may be defined as a technology included in the NR. In addition, the LTE that is connectable to the NR using Multi RAT Dual connectivity may be distinguished from the existing LTE. The present embodiment may be applied to the NR, the LTE and other RATs. Terms associated with the LTE and the NR are used in the following description. However, the present invention may be applied to other technologies using other terms. In this embodiment, the term "E-UTRA" may be replaced with "LTE," and the term "LTE" may be replaced with "E-UTRA".

<FIG> is a schematic diagram of a communication system according to an embodiment of the present invention.

An E-UTRA <NUM> is a radio access technology described in NPL <NUM> or the like, and includes a cell group (CG) configured in one or multiple frequency bands. An E-UTRAN Node B (eNB) <NUM> is a base station apparatus of the E-UTRA. An Evolved Packet Core (EPC) <NUM> is a core network described in NPL <NUM> or the like and is designed as a core network for the E-UTRA. An interface <NUM> is an interface between the eNB <NUM> and the EPC <NUM>, where there is a control plane (CP) through which control signals are transferred and a user plane (UP) through which user data is transferred.

A NR <NUM> is a new radio access technology that is currently being studied by the 3GPP and includes cell groups (CGs) that are configured in one or multiple frequency bands. A gNode B (gNB) <NUM> is an NR base station apparatus. A 5GC <NUM> is a new core network for the NR that is currently being studied by 3GPP, and is described in NPL <NUM> and the like.

An interface <NUM> is an interface between the eNB <NUM> and the 5GC <NUM>, an interface <NUM> is an interface between the gNB <NUM> and the 5GC <NUM>, an interface <NUM> is an interface between the gNB <NUM> and the EPC <NUM>, an interface <NUM> is an interface between the eNB <NUM> and the gNB <NUM>, and an interface <NUM> is an interface between the EPC <NUM> and 5GC <NUM>. The interface <NUM>, the interface <NUM>, the interface <NUM>, the interface <NUM>, and the interface <NUM> are interfaces that transfer CP only, UP only, or both the CP and the UP, and details are being discussed by 3GPP. Furthermore, the interface <NUM>, the interface <NUM>, the interface <NUM>, the interface <NUM>, and the interface <NUM> may not exist depending on communication systems provided by network operators.

A UE <NUM> is a terminal apparatus supporting the NR or both the E-UTRA and the NR.

<FIG> is a diagram of protocol stacks of UP and CP of a terminal apparatus and a base station apparatus in an E-UTRA radio access layer according to an embodiment of the present invention.

<FIG> is a diagram of the protocol stack of the UP used in a case that the UE <NUM> communicates with the eNB <NUM>.

A physical layer (PHY) <NUM> is a radio physical layer for providing a transmission service to a higher layer by using a physical channel. The PHY <NUM> is connected with a Medium Access Control layer (MAC) <NUM> of a higher layer to be described below via transport channels. Data is exchanged between the MAC <NUM> and the PHY <NUM> via the transport channels. The data is transmitted and/or received via radio physical channels between the PHYs of the UE <NUM> and the eNB <NUM>.

The MAC <NUM> maps various logical channels to various transport channels. The MAC <NUM> is connected with a radio link control layer (RLC) <NUM> of a higher layer to be described below via logical channels. The major classifications of the logical channel depend on the type of information to be transmitted, specifically, the logical channels are classified into control channels for transmitting control information and traffic channels for transmitting user information. The MAC <NUM> has a function of controlling the PHY <NUM> in order to perform the Discontinuous Reception and Transmission (DRX and DTX), a function of performing a random access procedure, a function of reporting transmit power information, a function of performing HARQ control, and the like (NPL <NUM>).

An RLC <NUM> divides (Segmentation) the data received from a Packet Data Convergence Protocol Layer (PDCP) <NUM> of a higher layer to be described below, and adjusts the data size such that a lower layer can properly perform data transmission. Furthermore, the RLC <NUM> also has a function of ensuring Quality of Service (QoS) required for each piece of data. In other words, the RLC <NUM> has a function of data retransmission control or the like (NPL <NUM>).

A PDCP <NUM> may have a header compression function of compressing unnecessary control information in order to efficiently transmit an IP packet, which is user data, in a radio segment. Furthermore, the PDCP <NUM> may also have a data encryption function (NPL <NUM>).

Note that data processed in the MAC <NUM>, the RLC <NUM>, and the PDCP <NUM> are referred to as a MAC Protocol Data Unit (PDU), an RLC PDU, and a PDCP PDU, respectively. In addition, data delivered from a higher layer to the MAC <NUM>, the RLC <NUM>, and the PDCP <NUM> or data delivered therefrom to a higher layer are respectively referred to as a MAC Service Data Unit (SDU), an RLC SDU, and a PDCP SDU.

<FIG> is a diagram of the protocol stack of the CP used in a case that the UE <NUM> communicates with the eNB <NUM>.

In addition to the PHY <NUM>, the MAC <NUM>, the RLC <NUM>, and the PDCP <NUM>, there is a Radio Resource Control layer (RRC) <NUM> in the protocol stack of the CP. The RRC <NUM> controls logical channels, transport channels, and physical channels by configuring and reconfiguring Radio Bearers (RBs) and the like. The RBs may be classified 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 which is control information. The DRB may be used as a path for transmitting the user data. Each RB may be configured in the RRCs <NUM> of the eNB <NUM> and the UE <NUM> (NPL <NUM>).

The functional classification of the MAC <NUM>, the RLC <NUM>, the PDCP <NUM>, and the RRC <NUM> described above is an example, and some or all of the respective functions may not be implemented. Some or all of the functions of each layer may be included in another layer.

<FIG> is a diagram of protocol stacks of UP and CP of a terminal apparatus and a base station apparatus in an NR radio access layer according to an embodiment of the present invention.

<FIG> is a diagram of the protocol stack of the UP used in a case that the UE <NUM> communicates with the gNB <NUM>.

A physical layer (PHY) <NUM> is a radio physical layer of the NR and may provide a transmission service to a higher layer by using the physical channel. The PHY <NUM> may be connected with the Medium Access Control layer (MAC) <NUM> of a higher layer to be described below via the transport channels. Data may be exchanged between the MAC <NUM> and the PHY <NUM> via the transport channels. The data may be transmitted and/or received between the PHYs of the UE <NUM> and the gNB <NUM> via the radio physical channel. Details of the PHY <NUM> are different from those of the radio physical layer PHY <NUM> of E-UTRA and are under discussion by 3GPP.

The MAC <NUM> may map various logical channels to various transport channels. The MAC <NUM> may be connected with a Radio Link Control layer (RLC) <NUM> of is a high layer to be described below via the logical channels. The classification of the logical channel depends on the type of information to be transmitted, and the logical channels may be classified into the control channels for transmitting the control information and the traffic channels for transmitting the user information. The MAC <NUM> has a function of controlling the PHY <NUM> in order to perform the Discontinuous Reception and Transmission (DRX and DTX), a function of performing the random access procedure, a function of reporting the transmit power information, a function of performing the HARQ control, and the like (NPL <NUM>). Details of the MAC <NUM> are different from those of the MAC <NUM> of the E-UTRA, and are under discussion by 3GPP.

The RLC <NUM> may divide (Segmentation) the data received from the Packet Data Convergence Protocol Layer (PDCP) <NUM> of a higher layer to be described below, and adjust the data size such that the lower layer can properly perform data transmission. Furthermore, the RLC <NUM> may also have a function of ensuring Quality of Service (QoS) required for each piece of data. In other words, the RLC <NUM> may have a function of data retransmission control or the like (NPL <NUM>). Details of the RLC <NUM> are different from those of the RLC <NUM> of the E-UTRA, and are under discussion by 3GPP.

A PDCP <NUM> may have a header compression function of compressing unnecessary control information in order to efficiently transmit an IP packet, which is the user data, in a radio segment. Furthermore, the PDCP <NUM> may also have a data encryption function (NPL <NUM>). Details of the PDCP <NUM> are different from those of the PDCP <NUM> of the E-UTRA, and are under discussion by 3GPP.

A Service Data Adaptation Protocol (SDAP) <NUM> may have a function of mapping a QoS flow of a downlink transmitted from a core network to a terminal apparatus through a base station apparatus and a DRB, mapping a QoS information flow of an uplink transmitted from the terminal apparatus to the core network through the base station apparatus and the DRB, and storing mapping rule information (NPL <NUM>). The QoS flow includes one or multiple service data flows (SDFs) processed using the same QoS policy (NPL <NUM>). In addition, the SDAP may have a Reflective QoS function of mapping the QoS flow of the uplink and the DRB based on information of the QoS flow of the downlink (NPL <NUM> and NPL <NUM>). Details are under discussion by 3GPP.

In addition, an IP layer and a Transmission Control Protocol (TCP) layer, a User Datagram Protocol (UDP) layer, an application layer, and the like that are higher layers than the IP layer are higher layers than the SDAP (not illustrated). In addition, in the SDAP of the terminal apparatus, a layer for mapping the service data flow and the QoS flow is also a higher layer than the SDAP.

Note that the data processed in the MAC <NUM>, the RLC <NUM>, the PDCP <NUM>, and the SDAP <NUM> may be referred to as a MAC Protocol Data Unit (PDU), an RLC PDU, a PDCP PDU, and an SDAP PDU, respectively. In addition, the data delivered from higher layers to the MAC <NUM>, the RLC <NUM>, and the PDCP <NUM> or data delivered to higher layers therefrom may be respectively referred to as a MAC Service Data Unit (SDU), an RLC SDU, a PDCP SDU, and an SDAP SDU.

<FIG> is a diagram of the protocol stack of the CP used in a case that the UE <NUM> communicates with the gNB <NUM>.

In addition to the PHY <NUM>, the MAC <NUM>, the RLC <NUM>, and the PDCP <NUM>, there is a Radio Resource Control layer (RRC) <NUM> in the protocol stack of the CP. The RRC <NUM> may control logical channels, transport channels, and physical channels by configuring and reconfiguring Radio Bearers (RBs). The RBs may be classified 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 which is control information. The DRB may be used as a path for transmitting the user data. Each RB may be configured between RRCs <NUM> of the gNB <NUM> and the UE <NUM> (NPL <NUM>).

The functional classification of the MAC <NUM>, the RLC <NUM>, the PDCP <NUM>, the SDAP <NUM>, and the RRC <NUM> described above is an example, and some or all of the functions may not be implemented. Some or all of the functions of each layer may be included in another layer.

Hereinafter, in an embodiment of the present invention, in order to distinguish an E-UTRA protocol and an NR protocol from each other, the MAC <NUM>, the RLC <NUM>, the PDCP <NUM>, and the RRC <NUM> may be respectively referred to as a MAC for E-UTRA or a MAC for LTE, an RLC for E-UTRA or an RLC for LTE, a PDCP for E-UTRA or a PDCP for LTE, and an RRC for E-UTRA or an RRC for LTE. Furthermore, the MAC <NUM>, the RLC <NUM>, the PDCP <NUM>, and the RRC <NUM> may also be referred to as MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively. Alternatively, there may be descriptions using a space such as an E-UTRA PDCP or an LTE PDCP, an NR PDCP, and the like.

As also illustrated in <FIG>, the eNB <NUM>, the gNB <NUM>, the EPC <NUM>, and the 5GC <NUM> may be connected to one another via the interface <NUM>, the interface <NUM>, the interface <NUM>, the interface <NUM>, and the interface <NUM>. Thus, the RRC <NUM> in <FIG> may be replaced with the RRC <NUM> in <FIG> to support various communication systems. Furthermore, the PDCP <NUM> in <FIG> may also be replaced with the PDCP <NUM> in <FIG>. Furthermore, the RRC <NUM> in <FIG> may include the function of the RRC <NUM> in <FIG>. Furthermore, the PDCP <NUM> in <FIG> may be the PDCP <NUM> in <FIG>.

An embodiment of the present invention will be described with reference to <FIG>, <FIG>, and <FIG>.

<FIG> is a diagram illustrating an example flow of an RRC connection reconfiguration procedure according to each embodiment of the present invention.

The RRC connection reconfiguration procedure (RRC Connection Reconfiguration) is a procedure used for handover, mesurement, and the like in addition to establishment, change, and release of an RB, a change, a release, and the like of a secondary cell in LTE described in NPL <NUM>. In addition, in the MR-DC, particularly in E-UTRA-NR Dual Connectivity (EN-DC) and NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC), the RRC connection reconfiguration procedure is used not only in LTE but also in NR to perform a part of handover, mesurement, and the like in addition to a part of establishing, changing, and releasing of a RB and changing, releasing, and the like of a secondary cell in NR, which is described in NPL <NUM>. The EN-DC is a case of MR-DC in which the core network is the EPC <NUM>, and the master node is the eNB <NUM>. The NGEN-DC is a case of MR-DC in which the core network is 5GC <NUM> and the master node is the eNB <NUM>. In an embodiment of the present invention, although the procedure used for establishing, changing, and releasing of the RB and adding, changing, releasing, handover, measurement, and the like of the cell group in the NR is referred to as an RRC connection reconfiguration procedure, a different designation may be used. In addition, in an embodiment of the present invention, the procedure of establishing, changing, and releasing of the RB and adding, changing, releasing, handover, mesurement, and the like of the cell group may be a procedure in the NR described in NPL <NUM> and may be designated as an RRC reconfiguration procedure.

In the RRC connection reconfiguration procedure, the UE <NUM> receives an RRC Connection Reconfiguration message (RRCConnectionReconfigration) from the eNB <NUM> (step S400) and performs processing of various configurations, for example, configuration of the DRB and the like based on information included in the RRC connection reconfiguration message (Step S402). After Step S402, the UE <NUM> may transmit an RRC connection reconfiguration completion message (RRCConnectionReconfigrationComplete) to the eNB <NUM> (not illustrated).

<FIG> is a block diagram illustrating a configuration of the terminal apparatus (UE <NUM>) according to an embodiment of the present invention. Note that <FIG> illustrates only the main components closely related to the present invention in order to avoid complexity of description.

The UE <NUM> illustrated in <FIG> includes a receiver <NUM> configured to receive an RRC connection reconfiguration message from the eNB <NUM> and a processing unit <NUM> configured to process a message.

<FIG> is one example of information relating to LTE in a DRB configuration for a cell group of a master node in the EN-DC and the NGEN-DC, the DRB configuration being part of information included in the RRC connection reconfiguration message illustrated in <FIG> and an Abstract Syntax Notation One (ASN. <NUM>) description of information. In the 3GPP, in the specifications relating to the RRC (NPL <NUM> and NPL <NUM>), a message, information (Information Element: IE), and the like relating to the RRC are described using ASN. In the example of ASN. <NUM> illustrated in <FIG>, <omitted> and <partly omitted> are not part of the notation of ASN. <NUM> and mean that other information is omitted. Note that there may also be omitted information in a part where neither <omitted> nor <partly omitted> is indicated. In addition, the example of ASN. <NUM> illustrated in <FIG> does not correctly follow the ASN. <NUM> notation method but is an example notation of parameters for the DRB configuration according to the present invention, and other designations and other notations may be used. In addition, in order to avoid complexity of description, the example of ASN. <NUM> illustrated in <FIG> represents only an example relating to main information that is closely related to the present invention.

Information denoted by fullConfig in <FIG> is information for indicating that a full configuration is applied, and the application of the full configuration may be indicated using true, enable, or the like. Information denoted by DRB-ToAddModList may be a list of information for indicating a configuration of the DRB to be added or changed that is denoted by DRBToAddMod. Information denoted by eps-BearerIdentity included in DRB-ToAddMod (the information for indicating a configuration of the DRB to be added or changed) may be information of an EPS bearer identity for identifying an EPS bearer described in NPL <NUM>. In the example illustrated in <FIG>, although eps-BearerIdentity is configured to be an integer value in the range of <NUM> to <NUM>, other values may be configured. The information of the EPS bearer identity may correspond to the DRB to be configured on a one-to-one basis. Information denoted by DRB-Identity included in the information for indicating the configuration of the DRB to be added or changed is information of the DRB identity of the DRB to be added or changed. In the example illustrated in <FIG>, DRB-Identity is configured to be an integer value in the range of <NUM> to <NUM>, other values may be configured. Information denoted by pdcp-Config included in the information for indicating the configuration of the DRB to be added or changed may be information relating to a configuration of an LTE PDCP entity for establishing or changing the PDCP <NUM>.

Some or all of the information illustrated in <FIG> may be optional. In other words, the information illustrated in <FIG> may be included in an RRC connection reconfiguration message when necessary. For example, in a case that an LTE PDCP is used as the PDCP of the DRB in the UE <NUM> corresponding to EN-DC, information relating to a configuration of the LTE PDCP entity may be included. In a case that an NR PDCP is used, information relating to the LTE PDCP entity may not be included.

In the UE <NUM>, the configuration of the PDCP entity is configured using a corresponding RRC entity. In other words, the configuration of an LTE PDCP entity is configured using an RRC entity for LTE described in NPL <NUM>, and the configuration of an NR PDCP entity is configured using an RRC entity for NR described in NPL <NUM>. In addition, in a process performed by the RRC entity for LTE, whether the LTE PDCP is established or configured is determined. In a process performed by the RRC entity for NR, whether the NR PDCP is established or configured is determined. In a case that information of a configuration relating to NR such as information relating to the configuration of the NR PDCP entity is included in an RRC connection reconfiguration message received from the eNB <NUM> in the form of a container or the like, the UE <NUM> decodes the information using the RRC entity for NR and performs configuration.

Hereinafter, in this embodiment, the information relating to the configuration of the DRB to be added or changed may be referred to as a DRB configuration, the information of the EPS bearer identity may be referred to as an EPS bearer identity, the information of the DRB identity may be referred to as a DRB identity, and the information relating to the configuration of the LTE PDCP entity may be referred to as an LTE PDCP configuration.

<FIG> illustrates an example of a processing method using the processing unit <NUM> of the UE <NUM> illustrated in <FIG> according to an embodiment of the present invention, and <FIG> illustrates another example of a processing method using the processing unit <NUM> of the UE <NUM> illustrated in <FIG> according to an embodiment of the present invention. In description presented below, DRB configurations are included in a list of the DRB configuration, and processing for the DRB configuration in the processing unit <NUM> of the UE <NUM> is performed for each DRB configuration included in the list of the DRB configuration.

An example of a DRB configuration procedure will be described with reference to <FIG>.

The processing unit <NUM> of the UE <NUM> checks that information indicating that a full configuration is applied is included in an RRC connection reconfiguration message including the DRB configuration received from the receiver <NUM> (step S700).

Next, in a case that a value of the DRB identity included in the DRB configuration is not present in a part of the current configuration of the UE <NUM>, and an LTE PDCP entity is established in an established DRB having the DRB identity, the processing unit <NUM> of the UE <NUM> associates the established DRB with the EPS bearer identity (step S702). In a case that a value of the DRB identity included in the DRB configuration is not present in a part of the current configuration of the UE <NUM>, and an LTE PDCP entity is not established in an established DRB having the DRB identity, the processing unit <NUM> of the UE <NUM> does not associate the established DRB with the EPS bearer identity. "A case that an LTE PDCP entity is established in an established DRB having the DRB identity" described above may be replaced with "a case that a PDCP entity is established using LTE in an established DRB having the DRB identity" or may be replaced with "a case that an LTE PDCP entity configuration is included in the DRB configuration". "A case that an LTE PDCP entity is established" represents a case that a PDCP entity is established in an RRC entity for LTE, and "an LTE PDCP configuration is included in a DRB configuration" indicates that a PDCP configuration is included in the DRB configuration of an RRC entity for LTE. "A case that an LTE PDCP entity has not been established in an established DRB having the DRB identity" described above may be replaced with "a case that a PDCP entity is not established using LTE in an established DRB having the DRB identity" or may be replaced with "a case that an LTE PDCP entity configuration is not included in the DRB configuration". "A case that an LTE PDCP entity is not established" represents a case that a PDCP entity is not established in an RRC entity for LTE, and "an LTE PDCP configuration is not included in the DRB configuration" indicates that a PDCP configuration is not included in the DRB configuration of an RRC entity for LTE.

Each of pieces of information may be checked according to a different order from the order in <FIG>. The checking of inclusion of information indicating that a full configuration is applied may be performed after checking that a value of information of the DRB identity is not present in a part of the current configuration of the UE <NUM> or checking that an LTE PDCP entity is established in Step S702.

Next, another example of the DRB configuration procedure will now be described with reference to <FIG>, <FIG>, and <FIG>.

The processing unit <NUM> of the UE <NUM> checks that information indicating that a full configuration is applied is not included in an RRC connection reconfiguration message including the DRB configuration received from the receiver <NUM> (step S800).

Next, in a case that a value of the DRB identity included in the DRB configuration is not present in a part of the current configuration of the UE <NUM>, and an LTE PDCP entity is established in an established DRB having the DRB identity, the processing unit <NUM> of the UE <NUM> notifies a higher layer of information indicating that the DRB is established and the EPS bearer identity of the established DRB (step S802). In a case that a value of the DRB identity included in the DRB configuration is not present in a part of the current configuration of the UE <NUM>, and an LTE PDCP entity is not established in an established DRB having the DRB identity, the processing unit <NUM> of the UE <NUM> does not notify a higher layer of information indicating that the DRB is established and the EPS bearer identity of the established DRB. "A case that an LTE PDCP entity is established in an established DRB having the DRB identity" described above may be replaced with "a case that a PDCP entity has been established using LTE in an established DRB having the DRB identity" or may be replaced with "a case that an LTE PDCP entity configuration is included in the DRB configuration ". "A case that an LTE PDCP entity is established" represents a case that a PDCP entity is established in an RRC entity for LTE, and "an LTE PDCP configuration is included in the DRB configuration" indicates that a PDCP configuration is included in the DRB configuration of an RRC entity for LTE. "A case that an LTE PDCP entity is not established in an established DRB having the DRB identity" described above may be replaced with "a case in a PDCP entity is not established using LTE in an established DRB having the DRB identity" or may be replaced with "a case that an LTE PDCP entity configuration is not included in the DRB configuration". "A case that an LTE PDCP entity is not established" represents a case that a PDCP entity is not established in an RRC entity for LTE, and "an LTE PDCP configuration is not included in the DRB configuration" indicates that a PDCP configuration is not included in the DRB configuration of an RRC entity for LTE.

Each of pieces of information may be checked according to a different order from the order in <FIG>. The checking of non-inclusion of information indicating that a full configuration is applied may be performed after checking that a value of the information of the DRB identity is not present in a part of the current configuration of the UE <NUM> or after checking that an LTE PDCP entity is established in step S802.

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

The DRB configuration according to an embodiment of the present invention may be included not only in the RRC connection reconfiguration procedure but also in an RRC establishment procedure or an RRC re-establishment procedure.

In the embodiment of the present invention, although "LTE PDCP" is described, in a case that the PDCP is definitely a PDCP configured in an RRC entity for LTE described in NPL <NUM>, "PDCP" may be used without attaching the term LTE thereto.

A program operating on an apparatus according to the present invention may serve as a program that controls a Central Processing Unit (CPU) and the like to cause a computer to operate in such a manner as to realize the functions of the above-described embodiments according to the present invention. Programs or the information handled by the programs are temporarily read into a volatile memory, such as a Random Access Memory (RAM) while being processed, or stored in a non-volatile memory, such as a flash memory, or a Hard Disk Drive (HDD), and then read by the CPU to be modified or rewritten, as necessary.

Note that the apparatuses in the above-described embodiments may be partially enabled by a computer. In such a case, a program for realizing such control functions may be recorded on a computer-readable recording medium to cause a computer system to read the program recorded on the recording medium to perform the program. It is assumed that the "computer system" mentioned here refers to a computer system built into the apparatuses, and the computer system includes an operating system and hardware components such as a peripheral device. Furthermore, the "computer-readable recording medium" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, and the like.

Moreover, the "computer-readable recording medium" may include a medium that dynamically retains a program for a short period of time, such as a communication line that is used to transmit the program over a network such as the Internet or over a communication line such as a telephone line, and may also include a medium that retains a program for a fixed period of time, such as a volatile memory within the computer system for functioning as a server or a client in such a case. Furthermore, the above-described program may be configured to realize some of the functions described above, and additionally may be configured to realize the functions described above, in combination with a program already recorded in the computer system.

Furthermore, each functional block or various characteristics of the apparatuses used in the above-described embodiments may be implemented or performed on an electric circuit, that is, typically an integrated circuit or multiple integrated circuits. An electric circuit designed to perform the functions described in the present specification may include a general-purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or the processor may be a processor of known type, a controller, a microcontroller, or a state machine instead. The general-purpose processor or the above-mentioned circuits may include a digital circuit, or may include an analog circuit. Furthermore, in a case that with advances in semiconductor technology, a circuit integration technology appears that replaces the present integrated circuits, it is also possible to use an integrated circuit based on the technology.

Claim 1:
A terminal apparatus (<NUM>) for communicating with one or multiple base station apparatuses (<NUM>, <NUM>), the terminal apparatus (<NUM>) comprising:
a processing unit (<NUM>); and
a receiver (<NUM>) configured to receive a Radio Resource Control, RRC, connection reconfiguration message including, for a Data Radio Bearer, DRB, associated with a DRB identity, a New Radio, NR, Packet Data Convergence Protocol, PDCP, entity configuration or an Evolved Universal Terrestrial Radio Access, E-UTRA, PDCP entity configuration, from a base station apparatus (<NUM>) of the one or multiple base station apparatuses (<NUM>, <NUM>);
the terminal apparatus is characterised in that
the processing unit (<NUM>) is configured to notify a higher layer of information indicating that the DRB is established and an EPS bearer identity of the DRB established, based on a determination that both of the following conditions hold: a) the DRB identity is not currently configured in the terminal apparatus (<NUM>), and b) the E-UTRA PDCP entity configuration for the DRB is included in a DRB configuration included in the RRC connection reconfiguration message.