JP2023082208A - Terminal device, base station device, and method - Google Patents

Abstract

To provide techniques related to a terminal device, a method, and an integrated circuit capable of reducing the complexity of protocol processing and efficiently performing communication.SOLUTION: In order to determine whether to notify an upper layer of information indicating both establishment of a data radio bearer (DRB) and an evolved packet system (EPS) bearer identifier of the established DRB, User equipment (UE) determines whether a plurality of conditions are met, including at least (a) a condition that an enhancements for evolved universal terrestrial radio access (E-UTRA) packet data convergence Protocol (PDCP) entity configuration is included in a radio resource control (RRC) connection reconfiguration message as a PDCP entity configuration of the DRB, and (b) a condition that a DRB identifier is not currently set in the terminal device, and performs the notification based on determining that the plurality of conditions are met.SELECTED DRAWING: Figure 7

Description

The present invention relates to a terminal device, base station device and method.

Cellular-mobile communication radio access scheme and radio network (hereinafter referred to as "Long Term Evolution (LTE: registered trademark)" or "Evolved Universal Terrestrial Radio Access: EUTRA"), and core network (hereinafter referred to as "Evolved Packet Core (EPC) is being considered in the 3rd Generation Partnership Project (3GPP®).

In addition, 3GPP is conducting a technical study of LTE-Advanced Pro, an extension of LTE, and NR (New Radio technology), a new radio access technology, as radio access schemes and radio network technologies for the 5th generation cellular system. and standards are being developed (Non-Patent Document 1). Also, 5GC (5 Generation Core Network), which is a core network for the 5th generation cellular system, is being studied (Non-Patent Document 2).

3GPP RP-170855, "Work Item on New Radio (NR) Access Technology" 3GPP TS 23.501, "System Architecture for the 5G System; Stage 2" 3GPP TS 36.300, "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; age 2” 3GPP TS 36.331, "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specifications" 3GPP TS 36.323, "Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification" 3GPP TS 36.322, "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification" 3GPP TS 36.321, "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification" 3GPP TS 37.340, "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-Connectivity; Stage 2" 3GPP TS 38.300, "NR; NR and NG-RAN Overall description; Stage 2" 3GPP TS 38.331, "NR; Radio Resource Control (RRC); Protocol specifications" 3GPP TS 38.323, "NR; Packet Data Convergence Protocol (PDCP) specification" 3GPP TS 38.322, "NR; Radio Link Control (RLC) protocol specification" 3GPP TS 38.321, "NR; Medium Access Control (MAC) protocol specification" 3GPP TS 23.401 v14.3.0, "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access" 3GPP TS 23.502, "Procedure for 5G System; Stage 2" 3GPP TS 38.324, "NR; Service Data Adaptation Protocol (SDAP) specification"

As one of the technical studies of NR, both E-UTRA and NR RAT (Radio Access Technology) cells are grouped for each RAT and assigned to UE, and the terminal device and one or more base station devices communicate. A mechanism (MR-DC: Multi-RAT Dual Connectivity) is being studied (Non-Patent Document 8).

However, since the formats and functions of the communication protocols used by E-UTRA and NR are different, the protocol processing becomes more complicated than Dual Connectivity in conventional LTE using only E-UTRA as RAT, and the base station device and There is a problem that communication with a terminal device cannot be performed efficiently.

One aspect of the present invention has been made in view of the circumstances described above, and includes a terminal device capable of efficiently communicating with a base station device, a method used in the terminal device, and a method implemented in the terminal device. One object is to provide an integrated circuit.

In order to achieve the above object, one aspect of the present invention takes the following means. That is, one aspect of the present invention is a terminal device that communicates with one or more base station devices, comprising: a processing unit; A receiving unit that receives an RRC connection reconfiguration message including either NR PDCP entity configuration or E-UTRA PDCP entity configuration as the DRB PDCP entity configuration corresponding to the DRB identifier, and transmits the information to the upper layer To determine whether to notify, the processing unit determines whether a plurality of conditions are met, the plurality of conditions being: (a) the E- including at least a condition that a UTRA PDCP entity configuration is included in the RRC connection reconfiguration message, and (b) a condition that the DRB identifier is not currently configured in the terminal device, the processing unit Based on determining that the plurality of conditions are satisfied, the information is notified to the upper layer, and the information is information indicating establishment of the DRB and an EPS bearer identifier of the established DRB. be.

Further, one aspect of the present invention is a base station apparatus that communicates with a terminal apparatus, and uses either an NR PDCP entity setting or an E-UTRA PDCP entity setting as a DRB PDCP entity setting corresponding to a DRB identifier. and a transmitting unit configured to transmit the RRC connection reset message to the terminal device, wherein the RRC connection reset message transmits information to the terminal device. It is a message for executing a judgment process for judging whether or not to notify the layer, the judgment process is a process for judging whether or not a plurality of conditions are satisfied, and the plurality of conditions are ( a) the condition that the E-UTRA PDCP entity configuration is included in the RRC connection reconfiguration message as the DRB PDCP entity configuration; and (b) the DRB identifier is currently configured in the terminal device. including at least the condition that no
The RRC connection reconfiguration message is a message to notify the information to the upper layer by causing the terminal device to determine that the plurality of conditions are satisfied, and the information is the establishment of the DRB. and the EPS bearer identifier of the established DRB.

Further, one aspect of the present invention is a method performed by a terminal device that communicates with one or more base station devices, wherein the terminal device communicates with one of the one or more base station devices. Receives an RRC connection reconfiguration message including either the NR PDCP entity configuration or the E-UTRA PDCP entity configuration as the DRB PDCP entity configuration corresponding to the DRB identifier from the base station apparatus, and notifies the information to the upper layer. to determine whether the terminal device determines whether a plurality of conditions are satisfied, the plurality of conditions being: (a) the E-UTRA as a PDCP entity configuration of the DRB; including at least the condition that a PDCP entity configuration is included in the RRC connection reconfiguration message; and (b) the DRB identifier is not currently configured in the terminal device, the terminal device comprising: Based on determining that a plurality of conditions are satisfied, the information is notified to the upper layer, the information is information indicating the establishment of the DRB and the EPS bearer identifier of the established DRB. .

ADVANTAGE OF THE INVENTION According to one aspect of the present invention, a terminal device can reduce the complexity of protocol processing and perform communication efficiently.

1 is a schematic diagram of a communication system according to an embodiment of the invention; FIG. FIG. 4 is a protocol stack diagram of UP and CP of a terminal device and a base station device in E-UTRA according to an embodiment of the present invention; FIG. 3 is a protocol stack diagram of UP and CP of a terminal device and a base station device in NR in an embodiment of the present invention; The figure which shows an example of the flow of the RRC connection resetting procedure in embodiment of this invention The block diagram which shows the structure of the terminal device in embodiment of this invention. Information related to DRB setting and ASN. 1 (Abstract Syntax Notation One) is a diagram showing an example of description. An example of a processing method according to an embodiment of the present invention. Another example of the processing method in the embodiment of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

LTE (and LTE-A Pro) and NR may be defined as different RATs. NR may also be defined as a technology included in LTE. LTE may be defined as a technology included in NR. Also, LTE that can be connected with NR and Multi RAT Dual connectivity may be distinguished from conventional LTE. This embodiment may be applied to NR, LTE and other RATs. The following description uses terms related to LTE and NR, but may be applied to other technologies using other terms. Also, the term E-UTRA in this 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 an embodiment of the invention.

E-UTRA 100 is a radio access technology described in Non-Patent Document 3, etc., and consists of a cell group (CG) consisting of one or more frequency bands. An eNB (E-UTRAN Node B) 102 is an E-UTRA base station device. EPC (Evolved Packet Core) 104 is a core network described in Non-Patent Document 14, etc., and is designed as a core network for E-UTRA. The interface 112 is an interface between the eNB 102 and the EPC 104, and includes a Control Plane (CP) through which control signals pass and a User Plane (UP) through which user data passes.

NR106 is a new radio access technology currently being studied by 3GPP, and consists of a cell group (CG) consisting of one or more frequency bands. A gNB (g Node B) 108 is an NR base station device. 5GC110 is a new core network for NR currently being studied by 3GPP, and is described in Non-Patent Document 2 and the like.

Interface 114 is the interface between eNB 102 and 5GC 110; interface 116 is the interface between gNB 108 and 5GC 110; interface 118 is the interface between gNB 108 and EPC 104; interface 120 is the interface between eNB 102 and gNB 108; It is the interface between Interface 114, interface 116, interface 118, interface 120, and interface 124 are interfaces through CP only, UP only, or both CP and UP, but the details are under discussion in 3GPP. Also, interfaces 114, 116, 118, 120, and 124 may not be present depending on the communication system provided by the carrier.

The UE 122 is a terminal device that supports NR or supports both E-UTRA and NR.

FIG. 2 is a protocol stack diagram of UP and CP of terminal equipment and base station equipment in the E-UTRA radio access layer in the embodiment of the present invention.

FIG. 2A is a protocol stack diagram of UP used when the UE 122 communicates with the eNB 102. FIG.

A PHY (Physical layer) 200 is a radio physical layer and provides transmission services to upper layers using physical channels. The PHY 200 is connected to an upper MAC (Medium Access Control layer) 202, which will be described later, via a transport channel. Data travels between MAC 202 and PHY 200 via transport channels. Data is transmitted and received between the PHYs of the UE 122 and the eNB 102 via radio physical channels.

MAC 202 maps various logical channels to various transport channels. The MAC 202 is connected to an upper RLC (Radio Link Control layer) 204, which will be described later, via a logical channel. Logical channels are largely classified according to the type of information to be transmitted, and are divided into control channels for transmitting control information and traffic channels for transmitting user information. The MAC 202 has a function of controlling the PHY 200 in order to perform intermittent reception transmission (DRX/DTX), a function of executing a random access procedure, a function of notifying transmission power information, a function of performing HARQ control, and the like. have (Non-Patent Document 7).

The RLC 204 segments data received from an upper PDCP (Packet Data Convergence Protocol Layer) 206, which will be described later, and adjusts the data size so that the lower layer can appropriately transmit data. The RLC 200 also has a function for guaranteeing the QoS (Quality of Service) required by each data. That is, the RLC 204 has functions such as data retransmission control (Non-Patent Document 6).

The PDCP 206 may have a header compression function for compressing unnecessary control information in order to efficiently transmit IP packets, which are user data, over a wireless section. The PDCP 206 may also have a data encryption function (Non-Patent Document 5).

The data processed by the MAC 202, RLC 204, and PDCP 206 are called MAC PDU (Protocol Data Unit), RLC PDU, and PDCP PDU, respectively. Data passed from the upper layer to the MAC 202, RLC 204, and PDCP 206, or data passed to the upper layer are called MAC SDU (Service Data Unit), RLC SDU, and PDCP SDU, respectively.

FIG. 2B is a CP protocol stack diagram used when the UE 122 communicates with the eNB 102 .

In addition to PHY200, MAC202, RLC204, PDCP206, RRC(RadioResourceControllayer)208 exists in the protocol stack of CP. The RRC 208 sets and resets a radio bearer (RB), and controls logical channels, transport channels, and physical channels. The RB can be divided into a signaling radio bearer (SRB) and a data radio bearer (DRB), and the SRB is used as a route for transmitting RRC messages, which are control information. may A DRB may be used as a path for transmitting user data. Each RB may be configured between the eNB 102 and the RRC 208 of the UE 122 (Non-Patent Document 4).

The functional classification of MAC 202, RLC 204, PDCP 206, and RRC 208 described above is an example, and some or all of each function may not be implemented. Also, part or all of the functions of each layer may be included in another layer.

FIG. 3 is a protocol stack diagram of the UP and CP of the terminal device and the base station device in the NR radio access layer according to the embodiment of the present invention.

FIG. 3A is a protocol stack diagram of UP used when the UE 122 communicates with the gNB 108. FIG.

A PHY (Physical layer) 300 is a radio physical layer of NR, and may provide transmission services to upper layers using physical channels. The PHY 300 may be connected to an upper MAC (Medium Access Control layer) 302, which will be described later, via a transport channel. Data may travel between MAC 302 and PHY 300 via transport channels. Data may be transmitted and received between the PHYs of the UE 122 and the gNB 108 over radio physical channels. The details are under discussion in 3GPP, unlike the radio physical layer PHY 200 of E-UTRA.

MAC 302 may map various logical channels to various transport channels. The MAC 302 may be connected to an upper RLC (Radio Link Control layer) 304, which will be described later, via a logical channel. Logical channels are largely classified according to the type of information to be transmitted, and may be divided into control channels for transmitting control information and traffic channels for transmitting user information. The MAC 302 has a function of controlling the PHY 300 to perform intermittent reception transmission (DRX/DTX), a function of executing a random access procedure, a function of notifying transmission power information, a function of performing HARQ control, and the like. You may have (Non-Patent Document 13). The details are under discussion in 3GPP, unlike MAC 202 in E-UTRA.

The RLC 304 may segment data received from an upper PDCP (Packet Data Convergence Protocol Layer) 206, which will be described later, and adjust the data size so that the lower layer can appropriately transmit data. . The RLC 304 may also have a function to guarantee the QoS (Quality of Service) required by each data. That is, the RLC 304 may have functions such as data retransmission control (Non-Patent Document 12). The details are under discussion in 3GPP, unlike RLC204 in E-UTRA.

The PDCP 306 may have a header compression function for compressing unnecessary control information in order to efficiently transmit IP packets, which are user data, over a wireless section. The PDCP 306 may also have a data encryption function (Non-Patent Document 11). The details are under discussion in 3GPP, unlike PDCP 206 in E-UTRA.

SDAP (Service Data Adaptation Protocol) 310 is a mapping between downlink QoS flows and DRBs sent from the core network to the terminal device via the base station device, and mapping from the terminal device to the core network via the base station device. It may also have a function of mapping the uplink QoS information flow sent to the DRB and storing the mapping rule information (Non-Patent Document 16). A QoS flow consists of one or more Service Data Flows (SDF) that are handled by the same QoS policy [2]. SDAP may also have a reflective QoS function that maps uplink QoS flows and DRB based on downlink QoS flow information (Non-Patent Document 2, Non-Patent Document 16). . Details are under discussion in 3GPP.

Note that the IP layer, a TCP (Transmission Control Protocol) layer above the IP layer, a UDP (User Datagram Protocol) layer, an application layer, and the like are upper layers of SDAP (not shown). Also, in the SDAP of the terminal device, the layer that associates the service data flow with the QoS flow is also an upper layer of the SDAP.

The data processed by MAC 302, RLC 304, PDCP 306, and SDAP 310 may also be called MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Also, the data passed from the upper layer to the MAC 202, RLC 204, and PDCP 206, or the data passed to the higher layer may be called MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively.

FIG. 3B is a CP protocol stack diagram used when the UE 122 communicates with the gNB 108. FIG.

In addition to PHY300, MAC302, RLC304, PDCP306, RRC(Radio Resource Control layer)308 exists in the protocol stack of CP. The RRC 308 may set and reset a radio bearer (RB), and may control logical channels, transport channels, and physical channels. The RB can be divided into a signaling radio bearer (SRB) and a data radio bearer (DRB), and the SRB is used as a route for transmitting RRC messages, which are control information. may A DRB may be used as a path for transmitting user data. Configuration of each RB may be performed between the gNB 108 and the RRC 308 of the UE 122 (Non-Patent Document 10).

The functional classifications of MAC 302, RLC 304, PDCP 306, SDAP 310, and RRC 308 described above are examples, and some or all of the functions may not be implemented. Also, part or all of the functions of each layer may be included in another layer.

In addition, in the embodiment of the present invention, in order to distinguish between the E-UTRA protocol and the NR protocol, the MAC 202, RLC 204, PDCP 206, and RRC 208 are respectively defined as MAC for E-UTRA or MAC for LTE and MAC for E-UTRA. They are also called RLC or RLC for LTE, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE. Also, the MAC 302, the RLC 304, the PDCP 306, and the RRC 308 may be called MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively. Alternatively, E-UTRA PDCP, LTE PDCP, NR PDCP, etc. may be described using a space.

Also, as shown in FIG. 1, eNB 102, gNB 108, EPC 104, 5GC 110 may be coupled via interface 112, interface 116, interface 118, interface 120, and interface 114. FIG. Therefore, RRC 208 of FIG. 2 may be replaced with RRC 308 of FIG. 3 to accommodate various communication systems. Also, PDCP 206 in FIG. 2 may be replaced with PDCP 306 in FIG. RRC 308 of FIG. 3 may also include the functionality of RRC 208 of FIG. Also, the PDCP 306 of FIG. 3 may be the PDCP 206 of FIG.

(Embodiment)
An embodiment of the present invention will be described with reference to FIGS. 1, 2 and 4 to 8. FIG.

FIG. 4 is a diagram showing an example of the flow of the RRC connection resetting procedure according to the embodiment of the present invention.

The RRC connection reconfiguration procedure (RRC Connection Reconfiguration) is described in Non-Patent Document 4, establishes, changes, and releases RBs in LTE, and changes and releases secondary cells, as well as handover and measurement (Measurement). etc. In addition, the RRC connection reconfiguration procedure is performed in MR-DC, especially when the core network is EPC 104 and the master node is eNB 102, which is MR-DC, EN-DC (E-UTRA-NR Dual Connectivity), and core network is MR-DC when is 5GC110 and the master node is eNB102, in NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity), the RRC connection reconfiguration procedure is not only for LTE but also non-patent In addition to performing part of the establishment, change, and release of RBs in NR and the change, release, etc. of secondary cells described in Document 10, it is also used to perform part of handover, measurement, etc. . In the embodiment of the present invention, the procedure used for establishment, change, and release of RB in NR, and cell group addition, change, release, handover and measurement (Measurement), etc., is the RRC connection reconfiguration procedure Although it is called, another name may be used. Also, procedures such as RB establishment, change, and release, and cell group addition, change, release, handover, and measurement (Measurement) in the embodiments of the present invention are procedures in NR described in Non-Patent Document 10. It may be named RRC reconfiguration procedure.

In the RRC connection reconfiguration procedure, the UE 122 receives an RRC connection reconfiguration message (RRCConnectionReconfiguration) from the eNB 102 (step S400), and performs various settings according to the information included in the RRC connection reconfiguration message, such as DRB settings ( step S402). After step S402, the UE 122 may send an RRC connection reconfiguration complete message (RRCConnectionReconfigurationComplete) or the like to the eNB 102 (not shown).

FIG. 5 is a block diagram showing the configuration of the terminal device (UE 122) according to the embodiment of the present invention. In order to avoid complicating the description, FIG. 5 shows only main components closely related to the present invention.

UE 122 shown in FIG. 5 comprises a receiving unit 500 that receives an RRC connection reconfiguration message from eNB 102 and a processing unit 502 that processes the message.

FIG. 6 shows, among the information included in the RRC connection reconfiguration message in FIG. 1 (Abstract Syntax Notation One) description. In 3GPP, RRC-related specifications (Non-Patent Document 4, Non-Patent Document 10) specify messages and information (Information Element: IE) related to RRC as ASN. 1 is used for description. ASN. 1, <omitted> and <omitted> are ASN. It is not part of the notation of 1, and indicates that other information has been omitted. Information may be omitted even where there is no description of <omitted> or <omitted>. Note that the ASN. 1 example is ASN. 1 notation method, but is an example notation for the DRB configuration parameters in the present invention, and other names and other notations may be used. Also, ASN. In order to avoid complicating the explanation, Example 1 shows only examples relating to main information closely related to the present invention.

Information represented by fullConfig in FIG. 6 is information indicating that the full configuration is applied, and true, enable, or the like may be used to indicate that the full configuration is applied. The information represented by DRB-ToAddModList may be a list of information representing DRB settings to be added or changed, represented by DRBToAddMod. Information represented by eps-BearerIdentity in DRB-ToAddMod (information indicating DRB settings to be added or changed) is EPS bearer identifier information that identifies the EPS bearer described in Non-Patent Document 3. can be In the example of FIG. 6, integer values from 0 to 15 are used, but other values may be used. The EPS bearer identifier information may correspond one-to-one with the DRB to be set. The information represented by DRB-Identity in the information indicating the setting of the DRB to be added or changed is information of the DRB identifier of the DRB to be added or changed. In the example of FIG. 6, integer values from 1 to 32 are used, but other values may be used. Also, the information represented by pdcp-Config in the information indicating the DRB settings to be added or changed may be information on the settings of the LTE PDCP entity for establishing or changing the PDCP 206 .

Also, part or all of the information shown in FIG. 6 may be optional. That is, the information shown in FIG. 6 may be included in the RRC connection reconfiguration message as required. For example, as PDCP of DRB in UE122 corresponding to EN-DC, when using LTE PDCP, information on the configuration of the LTE PDCP entity may be included, and when using NR PDCP, the LTE PDCP entity Information about settings need not be included.

In addition, in the UE 122, the setting of the PDCP entity is set by the corresponding RRC entity. That is, the LTE PDCP entity configuration is configured by the LTE RRC entity described in Non-Patent Document 4, and the NR PDCP entity configuration is configured by the NR RRC entity described in Non-Patent Document 10. Further, in the process performed by the RRC entity for LTE, it is determined whether LTE PDCP is established or configured, and in the process performed by the RRC entity for NR, it is determined whether NR PDCP is established or configured. In addition, UE122, in the RRC connection reconfiguration message received from eNB102, such as information on the configuration of the NR PDCP entity, if the configuration information related to NR is included in the form of a container or the like, in the NR RRC entity Decode and set.

In the present embodiment, hereinafter, the information indicating the setting of the DRB to be added or changed is DRB setting, the information of EPS bearer identifier is EPS bearer identifier, the information of DRB identifier is DRB identifier, LTE PDCP entity LTE PDCP settings may also be described as information related to the settings of .

FIG. 7 shows an example of the processing method of the processing unit 502 of the UE 122 in FIG. 5 according to the embodiment of the present invention, and FIG. An example of each is shown. In the following description, it is assumed that the DRB settings are included in the list of DRB settings, and the processing for DRB settings in the processing unit 502 of the UE 122 is performed for each DRB setting included in the list of DRB settings. and

An example of the DRB setting procedure will be described with reference to FIGS. 5 to 7. FIG.

The processing unit 502 of the UE 122 confirms that information indicating that the full setting is applied is included in the RRC connection reconfiguration message including the DRB setting received from the receiving unit 500 (step S700).

Next, the processing unit 502 of the UE 122 determines if the DRB identifier value included in the DRB configuration is not part of the current configuration of the UE 122 and the LTE PDCP entity is established in the established DRB having the DRB identifier. If so, associate the established DRB with the EPS bearer identifier (step S702). The processing unit 502 of the UE 122 determines if the DRB identifier value included in the DRB configuration is not part of the current configuration of the UE 122 and the LTE PDCP entity is established in the established DRB with the DRB identifier. Otherwise, do not associate the established DRB with the EPS bearer identifier. In addition, the above "when an LTE PDCP entity is established in the established DRB having the above DRB identifier" corresponds to "when a PDCP entity is established by LTE in the established DRB having the above DRB identifier". or "when the DRB configuration includes the LTE PDCP entity configuration". In addition, "when the LTE PDCP entity is established" indicates that the establishment of the PDCP entity is established in the RRC entity for LTE, and "the DRB setting includes the LTE PDCP setting" is for LTE Indicates that the PDCP configuration is included in the DRB configuration of the RRC entity. In addition, the above "when the LTE PDCP entity is not established in the established DRB having the above DRB identifier" corresponds to "when the PDCP entity is not established by LTE in the established DRB having the above DRB identifier". or "when the DRB configuration does not include the LTE PDCP entity configuration". In addition, "when the LTE PDCP entity is not established" indicates that the establishment of the PDCP entity is not established in the RRC entity for LTE, and "the LTE PDCP setting is not included in the DRB setting" means that the LTE It indicates that the PDCP configuration is not included in the DRB configuration of the RRC entity for

In addition, in FIG. 7, the order of confirming each piece of information does not have to be exactly this. Confirmation that the information indicating that the full configuration is applied is included, in step S702, after confirming that the value of the information of the DRB identifier is not part of the current configuration of the UE 122, or the LTE PDCP entity It may be done after confirming that it is established.

Next, another example of the DRB setting procedure will be described with reference to FIGS. 5, 6 and 8. FIG.

The processing unit 502 of the UE 122 confirms that the RRC connection reconfiguration message including the DRB setting received from the receiving unit 500 does not include information indicating that the full setting is applied (step S800).

Next, the processing unit 502 of the UE 122 determines if the DRB identifier value included in the DRB configuration is not part of the current configuration of the UE 122 and the LTE PDCP entity is established in the established DRB having the DRB identifier. If so, the information that the DRB has been established and the EPS bearer identifier of the established DRB are notified to the upper layer (step S802). The processing unit 502 of the UE 122 determines if the DRB identifier value included in the DRB configuration is not part of the current configuration of the UE 122 and the LTE PDCP entity is established in the established DRB with the DRB identifier. If not, the information that the DRB is established and the EPS bearer identifier of the established DRB are not notified to the upper layer. In addition, the above "when an LTE PDCP entity is established in the established DRB having the above DRB identifier" corresponds to "when a PDCP entity is established by LTE in the established DRB having the above DRB identifier". or "when the DRB configuration includes the LTE PDCP entity configuration". In addition, "when the LTE PDCP entity is established" indicates that the establishment of the PDCP entity is established in the RRC entity for LTE, and "the DRB setting includes the LTE PDCP setting" is for LTE Indicates that the PDCP configuration is included in the DRB configuration of the RRC entity. In addition, the above "when the LTE PDCP entity is not established in the established DRB having the above DRB identifier" corresponds to "when the PDCP entity is not established by LTE in the established DRB having the above DRB identifier". or "when the DRB configuration does not include the LTE PDCP entity configuration". In addition, "when the LTE PDCP entity is not established" indicates that the establishment of the PDCP entity is not established in the RRC entity for LTE, and "the LTE PDCP setting is not included in the DRB setting" means that the LTE It indicates that the PDCP configuration is not included in the DRB configuration of the RRC entity for

In addition, in FIG. 8, the order of confirming each piece of information does not have to be exactly this. Confirmation that the information indicating that the full configuration is applied is not included is, in step S802, after confirming that the value of the DRB identifier information is not part of the current configuration of the UE 122, or the LTE PDCP entity This may be done after confirming that the

Thus, according to the embodiment of the present invention, the terminal device can reduce the complexity of protocol processing and perform communication efficiently.

Note that the DRB setting in the embodiment of the present invention may be included in not only the RRC connection resetting procedure but also the RRC establishment (RRC establishment) procedure and the RRC re-establishment (RRC re-establishment) procedure.

Also, although it is described as "LTE PDCP" in the embodiment of the present invention, if it is clear that it is PDCP set by the RRC entity for LTE described in Non-Patent Document 4, LTE is not attached, It is good also as "PDCP."

The program that runs on the apparatus according to the present invention may be a program that controls a central processing unit (CPU) or the like to make a computer function so as to realize the functions of the above-described embodiments related to the present invention. . The program or information handled by the program is temporarily read into a volatile memory such as a random access memory (RAM) during processing, or stored in a non-volatile memory such as a flash memory or a hard disk drive (HDD). The CPU reads, modifies, and writes accordingly.

It should be noted that part of the devices in the above-described embodiments may be realized by a computer. In that case, a program for realizing this control function is recorded in a computer-readable recording medium, and the program recorded in this recording medium is read into a computer system and executed. good too. The "computer system" referred to here is a computer system built in the device, and includes hardware such as an operating system and peripheral devices. The "computer-readable recording medium" may be any of semiconductor recording media, optical recording media, magnetic recording media, and the like.

Furthermore, "computer-readable recording medium" refers to a medium that dynamically stores programs for a short period of time, like a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line. It may also include a memory that holds the program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in that case. Further, the above program may be for realizing a part of the functions described above, or may be a program capable of realizing the functions described above in combination with a program already recorded in the computer system. .

Also, each functional block, or feature, of the apparatus used in the embodiments described above may be implemented or performed in an electrical circuit, typically an integrated circuit or multiple integrated circuits. An electrical circuit designed to perform the functions described herein may be a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general purpose processor may be a microprocessor, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The general-purpose processor or each of the circuits described above may be composed of digital circuits or may be composed of analog circuits. In addition, when an integrated circuit technology that replaces current integrated circuits emerges due to advances in semiconductor technology, it is also possible to use integrated circuits based on this technology.

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

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like are included within the scope of the present invention. In addition, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments are also included in the technical scope of the present invention. be Further, it also includes a configuration in which the elements described in the above embodiments are replaced with the elements having the same effect.

As described above, one aspect of the present invention is a terminal device that communicates with one or more base station devices, comprising: a receiving unit that receives an RRC connection reconfiguration message including DRB settings from the base station device; , the RRC connection reconfiguration message received by the receiving unit includes information indicating that the full configuration is applied, and the DRB identifier included in the DRB configuration information is part of the current configuration of the terminal device. , and if an LTE PDCP entity is established in the established DRB having the DRB identifier, associate the established DRB with the EPS bearer identifier included in the DRB configuration information. and a processing unit.

Further, one aspect of the present invention is a terminal device that communicates with one or more base station devices, the receiving unit receiving an RRC connection reconfiguration request including DRB settings from the base station device, and the receiving unit When the received RRC connection reconfiguration message does not include information indicating that the full configuration is applied and the DRB identifier included in the DRB configuration is not part of the current configuration of the terminal device, the DRB a processing unit that, when an LTE PDCP entity is established in an established DRB having an identifier, informs an upper layer of information that the DRB is established and the EPS bearer identifier of the established DRB; .

Further, one aspect of the present invention is a terminal device that communicates with an E-UTRA base station device and an NR base station device using MR-DC, wherein RRC connection reconnection including DRB setting is performed from the base station device. a receiving unit for receiving a configuration message, and an RRC connection reconfiguration message received by the receiving unit includes information indicating that full configuration is applied, and a DRB identifier included in the DRB configuration information is included in the terminal. If not part of the device's current configuration, and if an LTE PDCP entity has been established in an established DRB with said DRB identifier, then said established DRB and included in said DRB configuration information. and a processing unit that associates the EPS bearer identifier with the EPS bearer identifier.

Further, one aspect of the present invention is a terminal device that communicates with an E-UTRA base station device and an NR base station device using MR-DC, in which RRC connection reset including DRB setting is performed from the base station device. The receiving unit that receives the request and the RRC connection reconfiguration message received by the receiving unit do not include information indicating that the full configuration is applied, and the DRB identifier included in the DRB configuration is the current state of the terminal device. and if an LTE PDCP entity has been established in the established DRB with said DRB identifier, the DRB established information and the EPS bearer identifier of said established DRB and a processing unit that notifies the upper layer.

Another aspect of the present invention is a method performed by a terminal device that communicates with one or more base station devices, comprising: receiving an RRC connection reconfiguration message including DRB settings from the base station device; When the RRC connection reconfiguration message received by the unit includes information indicating that the full configuration is applied, and the DRB identifier included in the DRB configuration information is not part of the current configuration of the terminal device. Then, when the LTE PDCP entity is established in the established DRB having the DRB identifier, the established DRB and the EPS bearer identifier included in the DRB configuration information are associated.

In addition, these generic or specific aspects may be realized by systems, devices, methods, integrated circuits, computer programs, or recording media. may be realized by any combination of

100 E-UTRA
102 eNBs
104 EPCs
106NR
108 gNB
110 5GC
112, 114, 116, 118, 120, 124 interface 122 UE
200, 300 PHYs
202, 302 MACs
204, 304 RLC
206, 306 PDCP
208, 308 RRC
310 SDAP
500 receiving unit 502 processing unit

Claims (3)

A terminal device that communicates with one or more base station devices,
a processing unit;
RRC including either NR PDCP entity configuration or E-UTRA PDCP entity configuration as a DRB PDCP entity configuration corresponding to the DRB identifier from one base station device of the one or more base station devices a receiver that receives a connection reset message,
In order to determine whether to notify information to an upper layer, the processing unit determines whether a plurality of conditions are satisfied,
The plurality of conditions are: (a) a condition that the E-UTRA PDCP entity configuration is included in the RRC connection reconfiguration message as a PDCP entity configuration of the DRB; and (b) the DRB identifier is the including at least the condition that it is not currently set in the terminal device,
The processing unit notifies the information to the upper layer based on determining that the plurality of conditions are satisfied,
The terminal device, wherein the information is information indicating establishment of the DRB and an EPS bearer identifier of the established DRB. A base station device that communicates with a terminal device,
a generation unit for generating an RRC connection reconfiguration message including either an NR PDCP entity configuration or an E-UTRA PDCP entity configuration as a DRB PDCP entity configuration corresponding to the DRB identifier;
a transmission unit that transmits the RRC connection reconfiguration message to the terminal device,
The RRC connection reconfiguration message is a message that causes the terminal device to execute determination processing for determining whether or not to notify information to an upper layer,
The determination process is a process of determining whether a plurality of conditions are satisfied,
The plurality of conditions are: (a) a condition that the E-UTRA PDCP entity configuration is included in the RRC connection reconfiguration message as a PDCP entity configuration of the DRB; and (b) the DRB identifier is the including at least the condition that it is not currently set in the terminal device,
The RRC connection reconfiguration message is a message for notifying the upper layer of the information by causing the terminal device to determine that the plurality of conditions are satisfied,
The base station apparatus, wherein the information is information indicating establishment of the DRB and an EPS bearer identifier of the established DRB. A method performed by a terminal device communicating with one or more base station devices, comprising:
The terminal device, from one of the one or more base station devices, as a DRB PDCP entity configuration corresponding to the DRB identifier, NR PDCP entity configuration and E-UTRA PDCP entity configuration receive an RRC connection reconfiguration message containing any
In order to determine whether to notify information to an upper layer, the terminal device determines whether a plurality of conditions are satisfied,
The plurality of conditions are: (a) a condition that the E-UTRA PDCP entity configuration is included in the RRC connection reconfiguration message as a PDCP entity configuration of the DRB; and (b) the DRB identifier is the including at least the condition that it is not currently set in the terminal device,
The terminal device notifies the information to the upper layer based on determining that the plurality of conditions are satisfied,
The method, wherein the information is information indicating establishment of the DRB and an EPS bearer identifier of the established DRB.

Images