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

Abstract

PROBLEM TO BE SOLVED: To provide techniques related to a terminal device, a method, and an integrated circuit that can reduce the complexity of protocol processing and enable efficient communication.

SOLUTION: Based on the determination that a terminal device meets both of two conditions, the terminal device notifies an upper layer of information indicating that a DRB associated with a DRB identifier has been established and an EPS bearer identifier of the established DRB. The two conditions are that the DRB identifier is not currently set on the terminal device and that DRB settings associated with the DRB identifier include E-UTRA PDCP entity settings.

SELECTED DRAWING: Figure 7

COPYRIGHT: (C)2024,JPO&INPIT

Description

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

Radio access systems and radio networks for cellular mobile communications (hereinafter referred to as "Long Term Evolution (LTE: registered trademark)" or "Evolved Universal Terrestrial Radio Access: EUTRA"), and core networks (hereinafter referred to as "Evolved Packet Core: EPC'') is being considered in the 3rd Generation Partnership Project (3GPP: registered trademark).

In addition, 3GPP is conducting technical studies on LTE-Advanced Pro, which is an extension technology of LTE, and NR (New Radio technology), which is a new radio access technology, as a radio access method and radio network technology for the fifth generation cellular system. and standards are being formulated (Non-Patent Document 1). Further, 5 Generation Core Network (5GC), which is a core network for the 5th generation cellular system, is also 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-UTRA) RAN); Overall description; Stage 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 Netw ork (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 considerations for NR, cells of both E-UTRA and NR RAT (Radio Access Technology) are grouped by RAT and assigned to UE, so that terminal equipment and one or more base station equipment can communicate. A mechanism (MR-DC: Multi-RAT Dual Connectivity) is being considered (Non-Patent Document 8).

However, because the formats and functions of the communication protocols used by E-UTRA and NR are different, the protocol processing becomes more complex than the conventional Dual Connectivity in LTE that uses only E-UTRA as the RAT. There was a problem in that communication with the terminal device could not be performed efficiently.

One aspect of the present invention has been made in view of the above circumstances, and includes a terminal device that can efficiently communicate with a base station device, a method used in the terminal device, and a method implemented in the terminal device. One of its purposes is to provide integrated circuits.

In order to achieve the above object, one embodiment of the present invention takes the following measures. That is, one aspect of the present invention is a terminal device that communicates with one or more base station devices, which includes a processing unit and an RRC from one of the one or more base station devices. The RRC connection resetting message is equipped with a reception department that receives the connection resetting message, and the RRC connection resetting message is for DRB related to the DRB (Data Radio Bearer) identifier, NR (New Radio Technology) PDCP (PACKET DA). Ta Convergence PROTOCOL) Entiti Configuration and E-UTRA (Evolved Universal Terrestrial Radio Access) A message containing any of the PDCP entity configurations associated with the DRB identifier, if the DRB identifier is part of the current configuration of the terminal device. There are cases where the E-UTRA PDCP entity settings are included in the DRB settings related to the DRB identifier, and cases where the E-UTRA PDCP entity settings are not included in the DRB settings related to the DRB identifier. Based on the determination that both of the conditions are satisfied, information indicating that the DRB has been established and the EPS bearer identifier of the established DRB are notified to the upper layer, and the two conditions are satisfied. The DRB identifier is not part of the current configuration of the terminal, and the E-UTRA PDCP entity configuration is included in the DRB configuration associated with the DRB identifier.

Further, one aspect of the present invention is a base station device that communicates with a terminal device, the generation unit generating an RRC (Radio Resource Control) connection reconfiguration message, and transmitting the RRC connection reconfiguration message to the terminal device. The RRC connection reconfiguration message includes NR (New Radio technology) PDCP (Packet Data Convergence Protocol) entity configuration and E-UTR for DRB related to a DRB (Data Radio Bearer) identifier. A (Evolved Universal Terrestrial Radio Access) A message containing any of the PDCP entity configurations, and if the DRB identifier is not part of the current configuration of the terminal device, the DRB configuration associated with the DRB identifier is included. The E-UTRA PDCP entity configuration may be included in the E-UTRA PDCP entity configuration, or the E-UTRA PDCP entity configuration may not be included in the DRB configuration associated with the DRB identifier, and the RRC connection reconfiguration message is sent to the terminal device. On the other hand, it is a message that notifies an upper layer of information indicating that the DRB has been established and the EPS bearer identifier of the established DRB based on determining that both of the two conditions are satisfied, The two conditions are that the DRB identifier is not part of the current configuration of the terminal device, and that the DRB configuration associated with the DRB identifier includes the E-UTRA PDCP entity configuration. It is a condition.

Further, one aspect of the present invention is a method performed by a terminal device that communicates with one or more base station devices, the method comprising: receiving RRC ( NR (New Radio technology) PDCP (Packet Data Convex) for a DRB associated with a DRB (Data Radio Bearer) identifier; (Protocol) entity settings and E-UTRA (Evolved Universal Terrestrial Radio Access) A message containing any of the PDCP entity configurations, and if the DRB identifier is not part of the current configuration of the terminal device, the DRB associated with the DRB identifier. There are cases in which the configuration includes the E-UTRA PDCP entity configuration, and cases in which the DRB configuration associated with the DRB identifier does not include the E-UTRA PDCP entity configuration, and both of the two conditions are satisfied. Based on the determination, information indicating that the DRB has been established and the EPS bearer identifier of the established DRB are notified to the upper layer, and the two conditions are such that the DRB identifier is the terminal device. and the E-UTRA PDCP entity configuration is included in the DRB configuration associated with the DRB identifier.

Another aspect of the present invention is a method performed by a base station device that communicates with a terminal device, the method generating an RRC (Radio Resource Control) connection reconfiguration message and transmitting the RRC connection reconfiguration message to the terminal device. The RRC connection reconfiguration message includes NR (New Radio technology) PDCP (Packet Data Convergence Protocol) entity settings and E-UTRA (Evo lved Universal Terrestrial Radio Access ) a message containing any of the E-UTRA PDCP entity configurations in the DRB configuration associated with the DRB identifier, if the DRB identifier is not part of the current configuration of the terminal device; In some cases, the DRB configuration related to the DRB identifier does not include the E-UTRA PDCP entity configuration, and the RRC connection reconfiguration message sends the RRC connection reconfiguration message to the terminal device under two conditions. This is a message that notifies an upper layer of information indicating that the DRB has been established and the EPS bearer identifier of the established DRB based on the determination that both conditions are satisfied, and the two conditions are: The DRB identifier is not part of the current configuration of the terminal, and the E-UTRA PDCP entity configuration is included in the DRB configuration associated with the DRB identifier.

According to one aspect of the present invention, a terminal device can reduce the complexity of protocol processing and communicate efficiently.

1 is a schematic diagram of a communication system 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 E-UTRA in an embodiment of the present invention. FIG. 4 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. A diagram showing an example of the flow of an RRC connection reconfiguration procedure in an embodiment of the present invention FIG. 1 is a block diagram showing the configuration of a terminal device in an embodiment of the present invention. Information related to DRB settings and ASN of the information in the embodiment of the present invention. 1 is a diagram showing an example of an Abstract Syntax Notation One (1) description. An example of a processing method in an embodiment of the present invention. Another example of the processing method in the embodiment of the present invention.

Embodiments of the present invention will be described in detail below with reference to the drawings.

LTE (and 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 a technology included in NR. Furthermore, LTE that can be connected to NR with 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 in other technologies using other terms. Furthermore, 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 present invention.

The E-UTRA 100 is a radio access technology described in Non-Patent Document 3, etc., and is composed of a cell group (CG) made up of one or more frequency bands. The 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 and the like, and was 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 considered by 3GPP, and consists of a cell group (CG) made up of one or more frequency bands. gNB (g Node B) 108 is an NR base station device. The 5GC 110 is a new core network for NR currently being considered by 3GPP, and is described in Non-Patent Document 2 and the like.

Interface 114 is an interface between eNB 102 and 5GC 110, interface 116 is an interface between gNB 108 and 5GC 110, interface 118 is an interface between gNB 108 and EPC 104, interface 120 is an interface between eNB 102 and gNB 108, interface The base 124 is EPC104 and 5GC110 It is an interface between The interfaces 114, 116, 118, 120, and 124 are interfaces that pass only CP, only UP, or both CP and UP, but the details are under discussion in 3GPP. Further, the interface 114, the interface 116, the interface 118, the interface 120, and the interface 124 may not exist depending on the communication system provided by the communication carrier.

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 the UP and CP of the terminal device and the base station device in the E-UTRA radio access layer in the embodiment of the present invention.

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

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

The MAC 202 maps various logical channels to various transport channels. The MAC 202 is connected to a higher-level RLC (Radio Link Control layer) 204, which will be described later, through a logical channel. Logical channels are broadly classified according to the type of information to be transmitted, and are divided into control channels that transmit control information and traffic channels that transmit user information. The MAC 202 has functions such as a function to control the PHY 200 to perform intermittent reception and transmission (DRX/DTX), a function to execute a random access procedure, a function to notify information on transmission power, a function to perform HARQ control, etc. (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 the data. The RLC 200 also has a function to guarantee the QoS (Quality of Service) required by each piece of 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 that compresses unnecessary control information in order to efficiently transmit IP packets, which are user data, over a wireless section. Furthermore, the PDCP 206 may also have a data encryption function (Non-Patent Document 5).

Note that the data processed in the MAC 202, RLC 204, and PDCP 206 are respectively referred to as MAC PDU (Protocol Data Unit), RLC PDU, and PDCP PDU. Further, data passed from the upper layer to the MAC 202, RLC 204, and PDCP 206, or data passed to the upper layer, are respectively referred to as MAC SDU (Service Data Unit), RLC SDU, and PDCP SDU.

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

In addition to the PHY 200, MAC 202, RLC 204, and PDCP 206, the CP protocol stack includes an RRC (Radio Resource Control layer) 208. The RRC 208 configures/reconfigures 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 is used as a path for transmitting an RRC message that is control information. You can. The 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 the MAC 202, RLC 204, PDCP 206, and RRC 208 described above is an example, and some or all of the functions may not be implemented. Further, part or all of the functions of each layer may be included in other layers.

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 in the embodiment of the present invention.

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

A PHY (Physical layer) 300 is a wireless physical layer of NR, and may provide a transmission service to an upper layer using a physical channel. The PHY 300 may be connected to a higher-level MAC (Medium Access Control layer) 302, which will be described later, via a transport channel. Data may be moved between MAC 302 and PHY 300 via a transport channel. Data may be transmitted and received between the PHY of the UE 122 and the gNB 108 via a wireless physical channel. The details are different from the wireless physical layer PHY 200 of E-UTRA, and are under discussion in 3GPP.

The MAC 302 may map various logical channels to various transport channels. The MAC 302 may be connected to a higher-level RLC (Radio Link Control layer) 304, which will be described later, through a logical channel. Logical channels are broadly classified according to the type of information to be transmitted, and may be divided into control channels that transmit control information and traffic channels that transmit user information. The MAC 302 has a function of controlling the PHY 300 to perform intermittent reception and transmission (DRX/DTX), a function of executing a random access procedure, a function of notifying information on transmission power, a function of performing HARQ control, etc. (Non-patent Document 13). The details are different from E-UTRA's MAC 202 and are under discussion in 3GPP.

The RLC 304 may segment the data received from the 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 the data. . Furthermore, 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 different from E-UTRA's RLC204 and are under discussion in 3GPP.

The PDCP 306 may have a header compression function that compresses unnecessary control information in order to efficiently transmit IP packets, which are user data, over a wireless section. Furthermore, the PDCP 306 may also have a data encryption function (Non-Patent Document 11). The details are different from E-UTRA's PDCP206 and are under discussion in 3GPP.

SDAP (Service Data Adaptation Protocol) 310 performs mapping between a downlink QoS flow sent from the core network to a terminal device via a base station device and a DRB, and a 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 with the DRB and storing mapping rule information (Non-Patent Document 16). A QoS flow consists of one or more service data flows (SDF) that are processed by the same QoS policy (Non-Patent Document 2). SDAP may also have a reflective QoS function that maps uplink QoS flows and DRBs 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 and the TCP (Transmission Control Protocol) layer, UDP (User Datagram Protocol) layer, application layer, etc. above the IP layer are upper layers of SDAP (not shown). Furthermore, in the SDAP of the terminal device, a layer that associates service data flows with QoS flows is also an upper layer of the SDAP.

Note that the data processed in the MAC 302, RLC 304, PDCP 306, and SDAP 310 may be referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Furthermore, data passed from the upper layer to the MAC 202, RLC 204, and PDCP 206, or data passed to the upper layer, may be respectively referred to as MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU.

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

In addition to the PHY 300, MAC 302, RLC 304, and PDCP 306, the CP protocol stack includes an RRC (Radio Resource Control layer) 308. The RRC 308 may configure/reconfigure radio bearers (RBs) and control 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 is used as a path for transmitting an RRC message that is control information. You can. The DRB may be used as a path for transmitting user data. Each RB may be configured between the gNB 108 and the RRC 308 of the UE 122 (Non-Patent Document 10).

The functional classification of the MAC 302, RLC 304, PDCP 306, SDAP 310, and RRC 308 described above is an example, and some or all of the functions may not be implemented. Further, part or all of the functions of each layer may be included in other layers.

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 designated as MAC for E-UTRA, MAC for LTE, and MAC for E-UTRA. It is also called RLC or RLC for LTE, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE. Furthermore, the MAC 302, RLC 304, PDCP 306, and RRC 308 may be referred to as NR MAC, NR RLC, NR RLC, and NR RRC, respectively. Alternatively, it may be written as E-UTRA PDCP, LTE PDCP, NR PDCP, etc. using spaces.

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

(Embodiment)
Embodiments of the present invention will be described using FIGS. 1, 2, and 4 to 8.

FIG. 4 is a diagram showing an example of the flow of the RRC connection reconfiguration procedure in the embodiment of the present invention.

The RRC connection reconfiguration procedure (RRC Connection Reconfiguration) includes establishing, changing, and releasing an RB in LTE and changing and releasing a secondary cell, as well as performing handover and measurement, as described in Non-Patent Document 4. This is the procedure used for 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, EN-DC (E-UTRA-NR Dual Connectivity), and core network. In NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity), which is an MR-DC when the 5GC 110 is the master node and the eNB 102 is the master node, the RRC connection reconfiguration procedure is not only for LTE but also for non-patent In addition to performing some of the establishment, modification, and release of RBs in NR, and modification and release of secondary cells, as described in Document 10, it is also used to perform part of handover, measurement, etc. . In an embodiment of the present invention, the procedures used for establishing, changing, and releasing RBs, and adding, changing, and releasing cell groups, handovers, and measurements in NR are replaced with RRC connection reconfiguration procedures. However, it may be called by another name. Furthermore, procedures such as establishment, modification, and release of RBs, addition, modification, and release of cell groups, handover, and measurement in the embodiment of the present invention are the procedures in NR described in Non-Patent Document 10. It may also be called an 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, such as DRB settings, according to the information included in the RRC connection reconfiguration message (step S400). Step S402). After step S402, the UE 122 may send an RRC connection reconfiguration complete message (RRCConnectionReconfigurationComplete) to the eNB 102 (not shown).

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

The UE 122 shown in FIG. 5 includes a receiving unit 500 that receives an RRC connection reconfiguration message from the 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. 4, information related to LTE and ASN of the DRB configuration in the cell group of the master node in EN-DC and NGEN-DC. 1 (Abstract Syntax Notation One) description. In 3GPP, specifications related to RRC (Non-Patent Document 4, Non-Patent Document 10) specify messages and information (Information Element: IE), etc. related to RRC as ASN. 1. ASN in Figure 6. In example 1, <omitted> and <omitted> refer to ASN. It is not a part of the notation in item 1, and indicates that other information is omitted. Note that information may be omitted even in places where there is no description of <omitted> or <omitted>. Note that the ASN in FIG. An example of 1 is ASN. 1 notation method, but is an example of the DRB setting parameters in the present invention, and other names and other notation may be used. Also, the ASN in FIG. In order to avoid complicating the explanation, Example 1 shows only examples related to main information closely related to the present invention.

The information represented by fullConfig in FIG. 6 is information indicating that full configuration is applied, and may also indicate that full configuration is applied using true, enable, or the like. The information represented by DRB-ToAddModList may be a list of information representing DRB settings to be added or changed, represented by DRBToAddMod. The information represented by eps-BearerIdentity in DRB-ToAddMod (information indicating the DRB settings to be added or changed) is EPS bearer identifier information that identifies the EPS bearer described in Non-Patent Document 3. It's okay. In the example of FIG. 6, an integer value from 0 to 15 is used, but another value may be used. The information on the EPS bearer identifier may have a one-to-one correspondence with the DRB to be set. Further, the information represented by DRB-Identity in the information indicating the settings of the DRB to be added or changed is information on the DRB identifier of the DRB to be added or changed. In the example of FIG. 6, an integer value from 1 to 32 is used, but another value may be used. Furthermore, the information represented by pdcp-Config in the information indicating the configuration of the DRB to be added or changed may be information regarding the configuration of the LTE PDCP entity for establishing or changing the PDCP 206.

Further, some 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 necessary. For example, when LTE PDCP is used as the DRB PDCP in the UE 122 that supports EN-DC, information regarding the settings of the LTE PDCP entity may be included, and when NR PDCP is used, the information regarding the settings of the LTE PDCP entity may be included. Information regarding settings does not need to be included.

Note that in the UE 122, the settings of the PDCP entity are configured 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. Note that if the RRC connection reconfiguration message received from the eNB 102 includes configuration information related to NR in the form of a container or the like, such as information related to the configuration of the NR PDCP entity, the UE 122 transmits the information at the NR RRC entity. Decode and configure.

In this embodiment, the information indicating the DRB settings to be added or changed will be referred to as DRB settings, the EPS bearer identifier information will be referred to as EPS bearer identifier, the DRB identifier information will be referred to as DRB identifier, and LTE PDCP entity. The information regarding the settings may be referred to as LTE PDCP settings.

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

An example of the DRB setting procedure will be explained using FIGS. 5 to 7.

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

Next, the processing unit 502 of the UE 122 establishes an LTE PDCP entity in the established DRB having the DRB identifier when the value of the DRB identifier included in the DRB configuration is not part of the current configuration of the UE 122. If so, the established DRB is associated with the EPS bearer identifier (step S702). The processing unit 502 of the UE 122 determines whether the value of the DRB identifier included in the DRB configuration is not part of the current configuration of the UE 122, and if an LTE PDCP entity is established in the established DRB having the DRB identifier. If not, the established DRB is not associated with the EPS bearer identifier. Note that the above ``If an LTE PDCP entity is established in the established DRB with the above DRB identifier'' means ``If a PDCP entity is established with LTE in the established DRB with the above DRB identifier''. or may be replaced with "If the above DRB settings include LTE PDCP entity settings". Note that "when the LTE PDCP entity is established" means that the PDCP entity is established with the RRC entity for LTE, and "DRB settings include LTE PDCP settings" means that the PDCP entity is established with the RRC entity for LTE. Indicates that the DRB settings of the RRC entity include the PDCP settings. Note that the above ``If no LTE PDCP entity is established in the established DRB with the above DRB identifier'' means ``If no PDCP entity is established with LTE in the established DRB with the above DRB identifier''. It may be replaced with "If the LTE PDCP entity setting is not included in the above DRB setting". Note that "when the LTE PDCP entity is not established" means that the PDCP entity is not established with the RRC entity for LTE, and "DRB settings do not include LTE PDCP settings" means that the LTE PDCP entity is not established in the LTE RRC entity. This indicates that the PDCP settings are not included in the DRB settings of the RRC entity.

Note that in FIG. 7, the order in which each piece of information is checked does not have to be the same. Confirmation that information indicating that the full configuration is applied is included is confirmed in step S702 after confirming that the value of the DRB identifier information is not part of the current configuration of the UE 122, or when the LTE PDCP entity This may be done after confirming that it has been established.

Next, another example of the DRB setting procedure will be described using FIGS. 5, 6, and 8.

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

Next, the processing unit 502 of the UE 122 establishes an LTE PDCP entity in the established DRB having the DRB identifier when the value of the DRB identifier included in the DRB configuration is not part of the current configuration of the UE 122. If so, the upper layer is notified of the information that the DRB has been established and the EPS bearer identifier of the established DRB (step S802). The processing unit 502 of the UE 122 determines whether the value of the DRB identifier included in the DRB configuration is not part of the current configuration of the UE 122, and if an LTE PDCP entity is established in the established DRB having the DRB identifier. If not, the upper layer is not notified of the information that the DRB has been established and the EPS bearer identifier of the established DRB. Note that the above ``If an LTE PDCP entity is established in the established DRB with the above DRB identifier'' means ``If a PDCP entity is established with LTE in the established DRB with the above DRB identifier''. or may be replaced with "If the above DRB settings include LTE PDCP entity settings". Note that "when the LTE PDCP entity is established" means that the PDCP entity is established with the RRC entity for LTE, and "DRB settings include LTE PDCP settings" means that the PDCP entity is established with the RRC entity for LTE. Indicates that the DRB settings of the RRC entity include the PDCP settings. Note that the above ``If no LTE PDCP entity is established in the established DRB with the above DRB identifier'' means ``If no PDCP entity is established with LTE in the established DRB with the above DRB identifier''. It may be replaced with "If the LTE PDCP entity setting is not included in the above DRB setting". Note that "when the LTE PDCP entity is not established" means that the PDCP entity is not established with the RRC entity for LTE, and "DRB settings do not include LTE PDCP settings" means that the LTE PDCP entity is not established in the LTE RRC entity. This indicates that the PDCP settings are not included in the DRB settings of the RRC entity.

Note that in FIG. 8, the order in which each piece of information is checked does not have to be the same. Confirmation that information indicating that the full configuration is applied is not included is confirmed 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 by the LTE PDCP entity. This may be done after confirming that the

In this way, in the embodiment of the present invention, the terminal device can reduce the complexity of protocol processing and communicate efficiently.

Note that the DRB configuration in the embodiment of the present invention may be included not only in the RRC connection reconfiguration procedure but also in the RRC Establishment procedure and the RRC Re-Establishment procedure.

In addition, although "LTE PDCP" is described in the embodiment of the present invention, if it is clear that the PDCP is set in the RRC entity for LTE described in Non-Patent Document 4, LTE is not added. It may also be "PDCP".

The program that runs on the device related to the present invention may be a program that controls the Central Processing Unit (CPU) or the like to make the computer function so as to realize the functions of the above-described embodiments related to the present invention. . Programs or information handled by programs are temporarily read into volatile memory such as Random Access Memory (RAM) during processing, or stored in non-volatile memory such as flash memory or Hard Disk Drive (HDD), and then transferred as needed. Reading, modification, and writing are performed by the CPU accordingly.

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

Furthermore, a ``computer-readable recording medium'' refers to a computer-readable storage medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. It may also include a device that retains a program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client. Further, the above-mentioned program may be one for realizing a part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system. .

Additionally, 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, or in the alternative, the processor may be a conventional processor, controller, microcontroller, or state machine. The general-purpose processor or each of the circuits described above may be configured with a digital circuit or an analog circuit. Further, if an integrated circuit technology that replaces the current integrated circuit emerges due to advances in semiconductor technology, it is also possible to use an integrated circuit based on this technology.

Note that the present invention is not limited to the above-described embodiments. Although an example of the device has been described in the embodiment, the present invention is not limited thereto, and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as AV devices, kitchen devices, 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 embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to these embodiments, and may include design changes within the scope of the gist of the present invention. Further, the present invention can be modified in various ways within the scope shown in the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments are also included within the technical scope of the present invention. It will be done. Also included are configurations in which the elements described in the above embodiments are replaced with each other and have similar effects.

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

Further, one aspect of the present invention is a terminal device that communicates with one or more base station devices, the receiving section receiving an RRC connection reconfiguration request including DRB configuration from the base station device, and the receiving section If the received RRC connection reconfiguration message does not include information indicating that 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 If an LTE PDCP entity is established in an established DRB having an identifier, a processing unit that notifies an upper layer of information that the DRB is established and an 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, the terminal device performing RRC connection replay including DRB configuration from the base station device. A receiving unit receives a configuration message, and the RRC connection reconfiguration message received by the receiving unit includes information indicating that full configuration is applied, and the DRB identifier included in the DRB configuration information is If it is not part of the current configuration of the device, and an LTE PDCP entity is established in an established DRB with the DRB identifier, the information included in the established DRB and the 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 reconfiguration including DRB configuration 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 full configuration is applied, and the DRB identifier included in the DRB configuration is the current one of the terminal device. If the LTE PDCP entity is established in an 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, the method comprising: receiving an RRC connection reconfiguration message including DRB configuration from the base station device; If the RRC connection reconfiguration message received by the unit includes information indicating that 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. If an LTE PDCP entity is established in the established DRB having the DRB identifier, the established DRB is associated with the EPS bearer identifier included in the DRB configuration information.

Note that these comprehensive or specific aspects may be realized by a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium. It may be realized by any combination of the following.

100 E-UTRA
102 eNB
104 EPC
106NR
108 gNB
110 5GC
112, 114, 116, 118, 120, 124 Interface 122 UE
200, 300 PHY
202, 302 MAC
204, 304 RLC
206, 306 PDCP
208, 308 RRC
310 SDAP
500 Receiving unit 502 Processing unit

Claims (4)

A terminal device that communicates with one or more base station devices,
a processing section;
a receiving unit that receives an RRC connection reconfiguration message from one of the one or more base station devices,
The RRC connection reconfiguration message includes NR (New Radio technology) PDCP (Packet Data Convergence Protocol) entity configuration and E-UTRA (Evolve) for DRB related to a DRB (Data Radio Bearer) identifier. d Universal Terrestrial Radio Access) PDCP entity A message containing one of the settings,
If the DRB identifier is not part of the current configuration of the terminal device, and the DRB configuration associated with the DRB identifier includes the E-UTRA PDCP entity configuration, and the DRB configuration associated with the DRB identifier may not include the E-UTRA PDCP entity settings,
The processing unit notifies an upper layer of information indicating that the DRB has been established and an EPS bearer identifier of the established DRB based on determining that both of the two conditions are satisfied;
The two conditions are that the DRB identifier is not part of the current configuration of the terminal device, and that the DRB configuration associated with the DRB identifier includes the E-UTRA PDCP entity configuration. The terminal device is a condition. A base station device that communicates with a terminal device,
a generation unit that generates an RRC (Radio Resource Control) connection reconfiguration message;
a transmitter that transmits the RRC connection reconfiguration message to the terminal device,
The RRC connection reconfiguration message includes NR (New Radio technology) PDCP (Packet Data Convergence Protocol) entity configuration and E-UTRA (Evolve) for DRB related to a DRB (Data Radio Bearer) identifier. d Universal Terrestrial Radio Access) PDCP entity A message containing one of the settings,
If the DRB identifier is not part of the current configuration of the terminal device, and the DRB configuration associated with the DRB identifier includes the E-UTRA PDCP entity configuration, and the DRB configuration associated with the DRB identifier may not include the E-UTRA PDCP entity settings,
The RRC connection reconfiguration message sends information indicating that the DRB has been established and an EPS bearer of the established DRB to the terminal device based on the determination that both of two conditions are satisfied. This is a message that notifies the upper layer of the identifier.
The two conditions are that the DRB identifier is not part of the current configuration of the terminal device, and that the DRB configuration associated with the DRB identifier includes the E-UTRA PDCP entity configuration. Base station equipment is a condition. A method performed by a terminal device that communicates with one or more base station devices, the method comprising:
receiving an RRC (Radio Resource Control) connection reconfiguration message from one base station device of the one or more base station devices;
The RRC connection reconfiguration message includes NR (New Radio technology) PDCP (Packet Data Convergence Protocol) entity configuration and E-UTRA (Evolve) for DRB related to a DRB (Data Radio Bearer) identifier. d Universal Terrestrial Radio Access) PDCP entity A message containing one of the settings,
If the DRB identifier is not part of the current configuration of the terminal device, and the DRB configuration associated with the DRB identifier includes the E-UTRA PDCP entity configuration, and the DRB configuration associated with the DRB identifier may not include the E-UTRA PDCP entity settings,
Based on determining that both of the two conditions are satisfied, notifying an upper layer of information indicating that the DRB has been established and an EPS bearer identifier of the established DRB;
The two conditions are that the E-UTRA PDCP entity configuration is not part of the current configuration of the terminal device, and that the DRB configuration associated with the DRB identifier includes the E-UTRA PDCP entity configuration. Method. A method performed by a base station device that communicates with a terminal device, the method comprising:
Generates an RRC (Radio Resource Control) connection reconfiguration message,
transmitting the RRC connection reconfiguration message to the terminal device;
The RRC connection reconfiguration message includes NR (New Radio technology) PDCP (Packet Data Convergence Protocol) entity configuration and E-UTRA (Evolve) for DRB related to a DRB (Data Radio Bearer) identifier. d Universal Terrestrial Radio Access) PDCP entity A message containing one of the settings,
If the DRB identifier is not part of the current configuration of the terminal device, and the DRB configuration associated with the DRB identifier includes the E-UTRA PDCP entity configuration, and the DRB configuration associated with the DRB identifier may not include the E-UTRA PDCP entity settings,
The RRC connection reconfiguration message sends information indicating that the DRB has been established and an EPS bearer of the established DRB to the terminal device based on the determination that both of two conditions are satisfied. This is a message that notifies the upper layer of the identifier.
The two conditions are that the E-UTRA PDCP entity configuration is not part of the current configuration of the terminal device, and that the DRB configuration associated with the DRB identifier includes the E-UTRA PDCP entity configuration. Method.

Images