Terminal device and base station device

Abstract

This invention relates to a terminal device and a base station device. The terminal device of this invention, which communicates with the base station device, receives an RRC connection reset request message from the base station device, which includes DRB (Data Radio Bearer) settings. The DRB settings include a DRB identifier and PDCP entity settings corresponding to the DRB identifier. The PDCP entity settings information includes one of E-UTRA PDCP entity settings and NR PDCP entity settings. The PDCP entity is established according to the PDCP entity settings information.

Description

[0001] This application is a divisional application of the invention patent application filed on June 15, 2018, with application number 201880038474.1 and entitled "Terminal Device, Base Station Device, Communication Method and Integrated Circuit". Technical Field

[0002] This invention relates to terminal devices, base station devices, communication methods, and integrated circuits. Background Technology

[0003] The 3rd Generation Partnership Project (3GPP) studied radio access methods for cellular mobile communications, radio networks (hereinafter referred to as "Long Term Evolution (LTE: a registered trademark)" or "Evolved Universal Terrestrial Radio Access (EUTRA)"), and core networks (hereinafter referred to as "Evolved Packet Core (EPC)").

[0004] Furthermore, within 3GPP, technical research and standardization were conducted on LTE-Advanced Pro, an extension of LTE, and NR (New Radiotechnology), a new radio access technology, as radio access methods and wireless network technologies for fifth-generation cellular systems (Non-Patent Document 1). Additionally, research was also conducted on 5GC (5Generation Core Network), the core network for fifth-generation cellular systems (Non-Patent Document 2).

[0005] Existing technical documents

[0006] Non-patent literature

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

[0008] Non-patent document 2: 3GPP TS23.501, "System Architecture for the 5G System; Stage 2"

[0009] Non-patent document 3: 3GPP TS 36.300, "Evolved Universal Terestrial Radio Access (E-UTRA) and Evolved Universal Terestrial Radio Access Network (E-UTRAN); Overall description; Stage 2"

[0010] Non-patent literature 4: 3GPP TS 36.331, "Evolved Universal Terestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specifications"

[0011] Non-patent literature 5: 3GPP TS 36.323, "Evolved Universal Terestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification"

[0012] Non-patent document 6: 3GPP TS 36.322, "Evolved Universal Terestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification"

[0013] Non-patent document 7: 3GPP TS 36.321, "Evolved Universal Terestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification"

[0014] Non-patent literature 8: 3GPP TS 37.374, "Evolve Universal Terestrial Radio Access (E-UTRA) and NR; Multi-Connectivity; Stage 2"

[0015] Non-patent literature 9: 3GPP TS 38.300, "NR; NR and NG-RAN Overall description; Stage 2"

[0016] Non-patent literature 10: 3GPP TS 38.331, "NR; Radio Resource Control (RRC); Protocol specifications"

[0017] Non-patent literature 11: 3GPP TS 38.323, "NR; Packet Data Convergence Protocol (PDCP) specification"

[0018] Non-patent literature 12: 3GPP TS 38.322, "NR; Radio Link Control (RLC) protocol specification"

[0019] Non-patent literature 13: 3GPP TS 38.321, "NR; Medium Access Control (MAC) protocol specification"

[0020] Non-patent document 14: 3GPP TS23.401v14.3.0, "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access" Summary of the Invention

[0021] The problem the invention aims to solve

[0022] As part of the research on NR technology, the following mechanism was studied: the cells of both E-UTRA and NR RAT (Radio Access Technology) are grouped according to each RAT and assigned to the UE, and the terminal device communicates with more than one base station device (MR-DC: Multi-RAT Dual Connectivity) (Non-Patent Document 8).

[0023] However, the following problems exist: the communication protocols used in E-UTRA and NR have different formats and functions. Therefore, compared with the dual connectivity in the previous LTE which only used E-UTRA as RAT, the protocol processing becomes more complicated and cannot efficiently facilitate communication between base station devices and terminal devices.

[0024] One aspect of the present invention was made in view of the above circumstances, and one of its objectives is to provide a terminal device capable of efficiently communicating with a base station device, a base station device communicating with the terminal device, a communication method for the terminal device, a communication method for the base station device, an integrated circuit installed in the terminal device, and an integrated circuit installed in the base station device.

[0025] Technical solution

[0026] To achieve the above objectives, one solution of the present invention is as follows: A terminal device corresponding to EN-DC includes a receiving unit that receives an RRC connection reset message from a base station device. The RRC connection reset message includes a DRB identifier and a PDCP entity setting corresponding to the DRB identifier. The PDCP entity setting is either an E-UTRA PDCP entity setting or an NR PDCP entity setting. The terminal device includes a setting unit that determines whether the RRC connection reset message includes the E-UTRA PDCP entity setting. If the terminal device has not set the value of the DRB identifier, and if it is determined that the RRC connection reset message includes the E-UTRA PDCP entity setting, the setting unit establishes a PDCP entity based on the E-UTRA PDCP entity setting.

[0027] Furthermore, one aspect of the present invention is a base station apparatus corresponding to EN-DC, comprising: a generation unit for generating an RRC connection reset message; and a transmission unit for transmitting the RRC connection reset message to a terminal device. The RRC connection reset message includes a DRB (Data Radio Bearer) identifier and a PDCP entity setting corresponding to the DRB identifier. The PDCP entity setting is selected from an E-UTRA PDCP entity setting and an NR PDCP entity setting. If the terminal device does not set a value for the DRB identifier, and if it is determined that the RRC connection reset message includes the E-UTRA PDCP entity setting, the RRC connection reset message including the DRB identifier and the PDCP entity setting causes the terminal device to establish a PDCP entity based on the E-UTRA PDCP entity setting.

[0028] Furthermore, one aspect of the present invention is a method executed by a terminal device corresponding to EN-DC, wherein an RRC connection reset message is received from a base station device, the RRC connection reset message including a Data RadioBearer (DRB) identifier and a PDCP entity setting corresponding to the DRB identifier, the PDCP entity setting being either an E-UTRA PDCP entity setting or an NR PDCP entity setting; it is determined whether the RRC connection reset message includes the E-UTRA PDCP entity setting; if the terminal device has not set the value of the DRB identifier, and if it is determined that the RRC connection reset message includes the E-UTRA PDCP entity setting, a PDCP entity is established according to the E-UTRA PDCP entity setting.

[0029] Furthermore, one aspect of the present invention is a method executed by a base station device corresponding to EN-DC, wherein an RRC connection reset message is generated and sent to a terminal device, the RRC connection reset message including a DRB (Data Radio Bearer) identifier and a PDCP entity setting corresponding to the DRB identifier, the PDCP entity setting being selected from E-UTRA PDCP entity settings and NR PDCP entity settings, in the case where the terminal device has not set a value for the DRB identifier, and in the case where it is determined that the RRC connection reset message includes the E-UTRA PDCP entity setting, the RRC connection reset message including the DRB identifier and the PDCP entity setting causes the terminal device to establish a PDCP entity according to the E-UTRA PDCP entity setting.

[0030] Beneficial effects

[0031] According to one aspect of the present invention, the terminal device and the base station device can reduce the complexity of protocol processing and communicate efficiently. Attached Figure Description

[0032] Figure 1 This is a schematic diagram of the communication system according to various embodiments of the present invention.

[0033] Figure 2 This is a protocol stack diagram of the UP and CP of the terminal device and the base station device in the E-UTRA of various embodiments of the present invention.

[0034] Figure 3 This is a protocol stack diagram of the UP and CP of the terminal device and the base station device in the NR of various embodiments of the present invention.

[0035] Figure 4 This is a diagram illustrating an example of the flow chart of the RRC connection reset process according to various embodiments of the present invention.

[0036] Figure 5 This is a block diagram of a terminal device (UE) according to various embodiments of the present invention.

[0037] Figure 6 This diagram illustrates an example of DRB setting reception and setting according to Embodiment 1 of the present invention.

[0038] Figure 7 This is a portion of a diagram (first image) illustrating an example of the ASN.1 (Abstract Syntax Notation One) setting for various embodiments of the present invention.

[0039] Figure 8 This is another part of the diagram (second sheet) showing an example of the DRB setting of various embodiments of the present invention, ASN.1 (Abstract Syntax Notation One).

[0040] Figure 9 This diagram illustrates an example of PDCP setting determination in the setting unit of the terminal device according to Embodiment 1 of the present invention.

[0041] Figure 10 This is a diagram illustrating an example of the relationship between the wireless protocol architecture and the RB on the base station device side of the EN-DC according to Embodiment 2 of the present invention.

[0042] Figure 11 This diagram illustrates an example of DRB setting reception and setting in Embodiment 2 of the present invention, where an MCG bearer or an SCG bearer is established as a bearer for an anchor cell group.

[0043] Figure 12 This is a diagram illustrating an example of the ASN.1 (Abstract Syntax Notation One) setting for the additional cell group during a change from a CG bearer or SCG bearer to a fork bearer according to Embodiment 2 of the present invention.

[0044] Figure 13 This diagram illustrates an example of DRB setting reception and setting according to Embodiment 3 of the present invention.

[0045] Figure 14 This is a diagram illustrating an example of an ASN.1 (Abstract Syntax Notation One) of a DRB setting including SDAP information in Embodiment 3 of the present invention.

[0046] Figure 15 This is a diagram illustrating an example of an ASN.1 (Abstract Syntax Notation One) of a DRB setting including SDAP information in Embodiment 3 of the present invention.

[0047] Figure 16 This is a portion of a diagram (first sheet) illustrating an example of the DRB setting of various embodiments of the present invention, ASN.1 (Abstract Syntax Notation One).

[0048] Figure 17 This is another part of the diagram (second sheet) showing an example of the DRB setting of various embodiments of the present invention, ASN.1 (Abstract Syntax Notation One).

[0049] Figure 18 This is another part of the diagram (third sheet) showing an example of the DRB setting of various embodiments of the present invention, ASN.1 (Abstract Syntax Notation One).

[0050] Explanation of reference numerals in the attached figures

[0051] 100 E-UTRA

[0052] 102 eNB

[0053] 104 EPC

[0054] 106 NR

[0055] 108 gNB

[0056] 110 5GC

[0057] Interfaces 112, 114, 116, 118, 120, and 124

[0058] 122 UE

[0059] 200, 300 PHY

[0060] 202, 302 MAC

[0061] 204, 304 RLC

[0062] 206, 306 PDCP

[0063] 208, 308 RRC

[0064] 310 SDAP

[0065] 500 Receiving Unit

[0066] 502 Setting Department. Detailed Implementation

[0067] Hereinafter, various embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0068] LTE (and LTE-A Pro) and NR can be defined as different RATs. Furthermore, NR can be defined as a technology included in LTE. LTE can be defined as a technology included in NR. Additionally, LTE's ability to connect to NR via dual connectivity distinguishes it from conventional LTE. This implementation can be applied to NR, LTE, and other RATs. In the following description, terms associated with LTE and NR are used, but they can also be applied to other technologies using other terms.

[0069] Figure 1 This is a schematic diagram of the communication system according to various embodiments of the present invention.

[0070] E-UTRA 100 is a radio access technology described in Non-Patent Document 3, etc., including a Cell Group (CG) consisting of one or more frequency bands. 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., designed as an E-UTRA core network. Interface 112 is the interface between eNB 102 and EPC 104, containing a control plane (CP) through which control signals pass and a user plane (UP) through which user data passes.

[0071] NR106 is a new radio access technology currently under research in 3GPP, including cell groups (CGs) consisting of one or more frequency bands. gNB (g Node B) 108 is a base station device for NR. 5GC110 is a new core network for NR currently under research in 3GPP, described in Non-Patent Document 2, etc.

[0072] Interface 114 is the interface between eNB102 and 5GC110; interface 116 is the interface between gNB108 and 5GC110; interface 118 is the interface between gNB108 and EPC104; interface 120 is the interface between eNB102 and gNB108; and interface 124 is the interface between EPC104 and 5GC110. Interfaces 114, 116, 118, 120, and 124 can be used only through the CP, only through the UP, or through both the CP and UP. Details are under discussion in 3GPP. Furthermore, interfaces 114, 116, 118, 120, and 124 may not exist depending on the communication system provided by the telecom operator.

[0073] UE122 is the terminal device corresponding to both E-UTRA and NR.

[0074] Figure 2 This is a protocol stack diagram of the UP and CP of the terminal device and the base station device in the E-UTRA of various embodiments of the present invention.

[0075] Figure 2 (A) is the protocol stack diagram of the UP used when UE122 communicates with eNB102.

[0076] PHY (Physical Layer) 200 is the wireless physical layer, providing transmission services to the upper layers using a physical channel. PHY 200 connects to the upper-level MAC (Medium Access Control layer) 202 (described later) via a transport channel. Data moves between MAC 202 and PHY 200 via the transport channel. Data transmission and reception between the PHYs of UE122 and eNB102 are conducted via the wireless physical channel.

[0077] MAC202 maps multiple logical channels to multiple transmission channels. MAC202 connects to the higher-level RLC (Radio Link Control layer) 204 (described later) via these logical channels. Logical channels are broadly classified according to the type of information transmitted, into control channels for transmitting control information and service channels for transmitting user information. MAC202 has functions such as controlling PHY200 for intermittent transmit / receive (DRX / DTX), performing random access procedures, notifying transmit power, and performing HARQ control (Non-Patent Document 7).

[0078] RLC204 segments the data received from the upper-level PDCP (Packet Data Convergence Protocol Layer) described later, adjusting the data size to ensure appropriate data transmission by the lower layers. Furthermore, RLC204 also has functions to guarantee the requested QoS (Quality of Service) for each data transmission. That is, RLC204 has functions such as data retransmission control (Non-Patent Document 6).

[0079] The PDCP206 can have a header compression function to compress unnecessary control information in order to efficiently transmit IP packets (IP packets) as user data over wireless networks. Furthermore, the PDCP206 can also have data encryption functionality (Non-Patent Document 5).

[0080] It should be noted that the data processed in MAC202, RLC204, and PDCP206 are respectively called MAC PDU (Protocol Data Unit), RLCPDU, and PDCP PDU. Furthermore, the data transferred from the upper layer to MAC202, RLC204, and PDCP206 are respectively called MAC SDU (Service Data Unit), RLC SDU, and PDCP SDU.

[0081] Figure 2 (B) is the protocol stack diagram of the CP used by UE122 to communicate with eNB102.

[0082] In the CP protocol stack, in addition to PHY200, MAC202, RLC204, and PDCP206, there is also RRC (Radio Resource Control layer) 208. RRC208 configures / reconfigures radio bearers (RBs) and controls logical, transport, and physical channels. RBs can be divided into signaling radio bearers (SRBs) and data radio bearers (DRBs). SRBs can be used as paths for sending RRC messages as control information. DRBs can be used as paths for sending user data. The configuration of each RB can be performed between the eNB102 and UE122's RRC208 (Non-Patent Document 4).

[0083] The functional classification of MAC202, RLC204, PDCP206, and RRC208 is given as an example; it is also possible to omit some or all of these functions. Furthermore, some or all of the functions of each layer may be included in other layers.

[0084] Figure 3 This is a protocol stack diagram of the UP and CP of the terminal device and the base station device in the NR of various embodiments of the present invention.

[0085] Figure 3 (A) is the protocol stack diagram of the UP used when UE122 communicates with gNB108.

[0086] PHY (Physical layer) 300 is the radio physical layer of NR, which can provide transmission services to the upper layers using a physical channel. PHY 300 can connect to the upper-level MAC (Medium Access Control layer) 302 (described later) via a transport channel. Data can move between MAC 302 and PHY 300 via the transport channel. Data can be sent and received between the PHYs of UE122 and gNB108 via the radio physical channel. The details differ from those of the E-UTRA radio physical layer PHY 200 and are currently under discussion within 3GPP.

[0087] MAC302 can map multiple logical channels to multiple transport channels. MAC302 can connect to the higher-level RLC (Radio Link Control layer) 304 (described later) via logical channels. Logical channels can be broadly classified according to the type of information transmitted, into control channels transmitting control information and service channels transmitting user information. MAC302 may have functions such as controlling PHY300 for intermittent transmit / receive (DRX / DTX), executing random access procedures, notifying transmit power information, and performing HARQ control (Non-Patent Document 13). The details differ from those of E-UTRA's MAC202 and are currently under discussion within 3GPP.

[0088] RLC304 can segment data received from the upper-level PDCP (Packet Data Convergence Protocol Layer) described later, adjusting the data size to ensure appropriate data transmission by the lower layer. Furthermore, RLC304 can also have functions to guarantee the requested QoS (Quality of Service) for each data transmission. That is, RLC304 can have functions such as data retransmission control (Non-Patent Document 12). Details differ from E-UTRA's RLC204 and are currently under discussion within 3GPP.

[0089] PDCP306 may have a header compression function to compress unnecessary control information for efficient transmission of IP packets (IP packets) as user data over radio intervals. Furthermore, PDCP306 may also have data encryption functionality (Non-Patent Document 11). Details differ from those of PDCP206 for E-UTRA and are currently under discussion within 3GPP.

[0090] SDAP (Service Data Adaptation Protocol) 310 can have the function of mapping the QoS and RB QoS of data sent from 5GC110 to gNB108 and data sent from gNB to 5GC110 (Non-Patent Document 9). When eNB102 is directly connected to 5GC110, i.e., connected to 5GC via interface 114, or when eNB102 is indirectly connected to 5GC110, i.e., connected to 5GC via interfaces 120 and 116, SDAP 310 can exist as an upper layer of PDCP 206 of E-UTRA PDCP. Details are being discussed in 3GPP.

[0091] It should be noted that the data processed in MAC302, RLC304, PDCP306, and SDAP310 can be referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Furthermore, the data transferred from the upper layer to MAC202, RLC204, and PDCP206 can be referred to as MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively.

[0092] Figure 3 (B) is the protocol stack diagram of the CP used by UE122 to communicate with gNB108.

[0093] In the CP protocol stack, in addition to PHY300, MAC302, RLC304, and PDCP306, there is also RRC (Radio Resource Control layer) 308. RRC308 can configure / reconfigure radio bearers (RBs), and can also control logical channels, transport channels, and physical channels. RBs can be divided into signaling radio bearers (SRBs) and data radio bearers (DRBs). SRBs can be used as paths for sending RRC messages as control information. DRBs can be used as paths for sending user data. The configuration of each RB can be performed between gNB108 and UE122's RRC208 (Non-Patent Document 10).

[0094] The functional classification of MAC302, RLC304, PDCP306, SDAP310, and RRC208 is an example; it is also possible to omit some or all of these functions. Furthermore, some or all of the functions of each layer can be included in other layers.

[0095] It should be noted that, in the embodiments of the present invention, in order to distinguish between the following E-UTRA protocols and NR protocols, MAC202, RLC204, PDCP206, and RRC208 are respectively referred to as E-UTRA MAC, E-UTRA RLC, E-UTRA PDCP, and E-UTRA RRC. Furthermore, MAC302, RLC304, PDCP306, and RRC308 are also referred to as NR MAC, NR RLC, NR PDCP, and NR RRC.

[0096] In addition, such as Figure 1 As shown, eNB102, gNB108, EPC104, and 5GC110 can be connected via interfaces 112, 116, 118, 120, and 114. Therefore, to accommodate various communication systems, Figure 2 RRC208 can be replaced with Figure 3 RRC308. In addition, Figure 2 PDCP206 can also be replaced with Figure 3 PDCP306. In addition... Figure 3 The RRC308 may include Figure 2 The functions of RRC208. In addition. Figure 3 PDCP306 can be Figure 2 PDCP206.

[0097] Figure 4This is a diagram illustrating an example of the flow chart of the RRC connection reset process according to various embodiments of the present invention.

[0098] The RRC connection reconfiguration process, as described in Non-Patent Document 4, is a process used for handover and measurement, in addition to the establishment, modification, and release of RBs in E-UTRA and the modification and release of secondary cells. However, it can also be used for the establishment, modification, and release of RBs in NR and the addition, modification, release, handover, and measurement of secondary cells, and can be described in Non-Patent Document 10. In various embodiments of the present invention, the process used for the establishment, modification, and release of RBs in NR and the addition, modification, release, handover, and measurement of cell groups is referred to as the RRC connection reconfiguration process, but it may also be called by other names. The RRC connection reconfiguration process in various embodiments of the present invention may include the establishment, modification, and release of RBs in NR and the addition, modification, release, handover, and measurement of cell groups.

[0099] like Figure 4As shown, when RRC connection reconfiguration is required, eNB102 or gNB108, or both eNB102 and gNB108, send an RRC connection reconfiguration request message (RRCConnectionReconfiguration message) to UE122 (S400). Upon receiving the RRC connection reconfiguration request message, UE122 performs the necessary configuration based on the information included in the message (Information Element: IE). To notify that the configuration is complete, it can send an RRC connection reconfiguration completion message (RRCConnectionReconfigurationComplete message) to eNB102 or NB108, or both eNB and gNB, which were the senders of the RRC connection reconfiguration request message (S402). It should be noted that the message names of the RRCConnectionReconfiguration and RRCConnectionReconfigurationComplete messages may not be as described above. Furthermore, UE122 can send an RRC connection reset completion message to both eNB102 and gNB108, regardless of whether the base station device that sent the RRC connection reset request is eNB102 or gNB108. Moreover, not only during the RRC connection reset process, but also for all or part of other RRC-related units (RRC connection setup unit, RRC connection reset unit, etc.), and for request messages (RRCConnectionSetup, RRCConnectionReestablishment, etc.) sent from eNB102 or gNB108 or both eNB102 and gNB108, UE122 can send completion messages to both eNB102 and gNB108, regardless of whether the base station device that sent the request message is eNB102 or gNB108.

[0100] Figure 5 This is a block diagram illustrating the configuration of a terminal device (UE) according to various embodiments of the present invention. It should be noted that, to avoid unnecessary detail, in... Figure 5 Only the main components closely related to the present invention are shown.

[0101] Figure 5 The UE122 shown includes: a receiving unit 500 that receives an RRC connection reset request message from an eNB 102 or a gNB 108, or both an eNB and a gNB; and a setting unit 502 that, if the RRC connection reset request message includes DRB setting information (DRB setting), sets the DRB according to the DRB setting. The UE122 may also include functions other than the receiving unit 500 and the setting unit 502.

[0102] (Implementation Method 1)

[0103] use Figures 1-9 The following describes Embodiment 1 of the present invention.

[0104] Figure 6 This diagram illustrates an example of DRB setting reception and setting according to an embodiment of the present invention. eNB102 or gNB108, or both eNB102 and gNB108, determine the DRB setting requested from UE122 (S600). eNB102 or gNB108, or both eNB102 and gNB108, can also determine the DRB setting based on information from the core network (EPC104 or 5GC110, or both EPC104 and 5GC110) or based on the capabilities of UE122, or based on both information from the core network and the capabilities of UE122. It should be noted that the information from the core network can also be determined based on the conditions of application services such as voice calls requested by UE122. Next, eNB102 or gNB108, or both eNB102 and gNB108, generate an RRC Connection Reconfiguration request message including the DRB setting and send it to UE122 (S602). The receiving unit 500 of UE122 receives an RRC connection reset request message including DRB settings and forwards the DRB settings to the setting unit 502.

[0105] Figure 7 and Figure 8 This is an example of ASN.1 (Abstract Syntax Notation One) set by the DRB. In 3GPP, ASN.1 is used in RRC specifications (Non-Patent Document 4, Non-Patent Document 10) to describe RRC messages and information (Information Element: IE), etc. It should be noted that... Figure 7 and Figure 8 It's a picture. That is, Figure 7 The first image is an example of an ASN.1 setting for DRB. Figure 8 The second image is an example of an ASN.1 setting for DRB. Figure 7 and Figure 8 In the examples of ASN.1, <omitted> and <omitted in the middle> indicate that other information is omitted, rather than omitting a part of ASN.1. It should be noted that information may also be omitted where there is no mention of <omitted> or <omitted in the middle>.

[0106] exist Figure 7 and Figure 8 In Figure 8 In the RRCConnectionReconfiguration message, the DRB-ToAddMod parameter is the IE configured for DRB. For example... Figure 7 and Figure 8 In Figure 8 As shown, DRB-ToAddMod can include DRB-Identity (the IE's identifier for DRB) and PDCP-Config (the PDCP entity setting information corresponding to the DRB identifier). Furthermore, as... Figure 7 and Figure 8 In Figure 8 As shown, the PDCP-Config, which serves as the PDCP entity configuration information, can be selected (CHOICE) as either PDCP-EUTRA-Config (as E-UTRA PDCP entity configuration information) or PDCP-NR-Config (as NR PDCP entity configuration information). Furthermore, as... Figure 7 and Figure 8 In Figure 8 As shown, PDCP-EUTRA-Config and PDCP-NR-Config may include pdcp-SN-Size information representing the length of the PDCP Sequence Number (SN), which may be an integer containing 7.

[0107] Figure 16 , Figure 17 and Figure 18 This is another example of ASN.1 (Abstract Syntax Notation One) set by DRB. It should be noted that... Figure 16 , Figure 17 and Figure 18 It's a picture. That is, Figure 16 The first image in the diagram represents another example of ASN.1 set by DRB. Figure 17 The second image is another example of ASN.1 set by DRB. Figure 18 This is the third diagram in the series, representing another example of ASN.1 set by DRB. Figure 16 , Figure 17 and Figure 18 In the examples of ASN.1, <omitted> and <omitted in the middle> indicate that other information is omitted, rather than omitting a part of ASN.1. It should be noted that information may also be omitted where there is no mention of <omitted> or <omitted in the middle>.

[0108] exist Figure 16 , Figure 17 and Figure 18 In Figure 16 In the RRCConnectionReconfiguration message, the choice (CHOICE) can be either RRCConnectionReconfiguration-EUTRA-IE (as an E-UTRA request for RRC connection reconfiguration) or RRCConnectionReconfiguration-NR-IE (as an NR request for RRC connection reconfiguration).

[0109] like Figure 16 , Figure 17 as well as Figure 18 In Figure 16 and Figure 17 As shown, when an IE is selected to reset the E-UTRA connection using RRC, it can include DRB-ToAddMod-EUTRA for IEs configured with E-UTRA DRB. Furthermore, as... Figure 16 , Figure 17 as well as Figure 18 In Figure 17 As shown, DRB-ToAddMod-EUTRA can include the DRB-Identity of the IE as the DRB identifier and the PDCP, Config-EUTRA, which is the PDCP entity setting information for the E-UTRA corresponding to the DRB identifier. Furthermore, as... Figure 16 , Figure 17 as well as Figure 18 In Figure 17 and Figure 18 As shown, PDCP-Config-EUTRA, which serves as the PDCP entity configuration information for EUTRA, can also be selected (CHOICE) to include PDCP-EUTRA-Config, which serves as the PDCP entity configuration information for E-UTRA, or PDCP-NR-Config, which serves as the PDCP entity configuration information for NR, for use as the PDCP entity configuration for EUTRA. Furthermore, as... Figure 16 , Figure 17 as well as Figure 18 In Figure 18 As shown, PDCP-EUTRA-Config and PDCP-NR-Config may include pdcp-SN-Size information representing the length of the PDCP Sequence Number (SN), which may be an integer containing 7.

[0110] In addition, such as Figure 16 , Figure 17 as well as Figure 18 In Figure 16 and Figure 17 As shown, when an IE is selected to reset the NR connection using RRC, DRB-ToAddMod-NR can be included as an IE configured for NR using DRB. Furthermore, as... Figure 16 , Figure 17 as well as Figure 18 In Figure 17 As shown, DRB-ToAddMod-NR can include DRB-Identity (the IE's identifier for DRB) and PDCP-Config-NR (the NR's configuration information using the PDCP entity corresponding to the DRB identifier). Furthermore, as... Figure 16 , Figure 17 as well as Figure 18 In Figure 17 and Figure 18 As shown, PDCP-Config-NR, which serves as PDCP entity configuration information for NR, can also be selected (CHOICE) to include PDCP-EUTRA-Config, which serves as PDCP entity configuration information for E-UTRA, or PDCP-NR-Config, which serves as PDCP entity configuration information for NR, for use as PDCP entity configuration for NR. Furthermore, as... Figure 16 , Figure 17 as well as Figure 18 In Figure 18 As shown, PDCP-EUTRA-Config and PDCP-NR-Config may include pdcp-SN-Size information representing the length of the PDCP Sequence Number (SN), which may be an integer containing 7.

[0111] It should be noted that, Figure 7 and Figure 8 as well as Figure 16 , Figure 17 and Figure 18 The message name, IE name, parameter name, etc. in ASN.1 are just one example; they can also be other names. Furthermore, in Figure 7 and Figure 8 as well as Figure 16 , Figure 17 and Figure 18 In this context, the E-UTRA RLC entity and the NR RLC entity can be described using the same method as the method used to describe the E-UTRA PDCP entity and the NR PDCP entity. Furthermore, in... Figure 7 and Figure 8 as well as Figure 16 , Figure 17 and Figure 18In addition, the MAC entities for E-UTRA (MACMainConfig (not shown), logicalChannelConfig, etc.) and MAC entities for NR can also be described in the same way as the PDCP entities for E-UTRA and PDCP entities for NR.

[0112] exist Figure 6 In S604, the DRB settings transferred from the receiving unit 500 of UE122 to the setting unit 502 of UE122 include at least one of the PDCP entity settings for E-UTRA or PDCP entity settings for NR as the DRB identifier and the PDCP entity settings corresponding to the DRB identifier. The setting unit 502 of UE122 establishes or re-establishes the PDCP entity based on the DRB identifier and the PDCP entity settings corresponding to the DRB identifier.

[0113] Figure 9 This is an example of PDCP setting determination in the setting unit of the terminal device according to an embodiment of the present invention. The setting unit 502 of UE122 checks whether the value of the DRB identifier exists in the current terminal device settings (S900). If it does not exist, it checks whether the PDCP entity settings corresponding to the DRB identifier include an E-UTRA PDCP entity (S902). If it does, an E-UTRA PDCP entity is established based on the E-UTRA PDCP entity setting information (S904). On the other hand, if the E-UTRA PDCP entity settings corresponding to the DRB identifier do not include an E-UTRA PDCP entity, it further checks whether the PDCP entity settings corresponding to the DRB identifier include an NR PDCP entity (S906). If it does, an NR PDCP entity is established based on the NR PDCP entity setting information (S908). Furthermore, if the NR PDCP entity settings corresponding to the DRB identifier do not include an NR PDCP entity, other settings are performed (S918).

[0114] Furthermore, on one hand, if the value of the DRB identifier exists in the current terminal device settings, it is checked whether the PDCP entity settings corresponding to the DRB identifier include an E-UTRA PDCP entity (S910). If it does, the E-UTRA PDCP entity is re-established based on the E-UTRA PDCP entity setting information (S912). On the other hand, if the E-UTRA PDCP entity settings corresponding to the DRB identifier do not include the PDCP entity settings, it is further checked whether the NR PDCP entity settings corresponding to the DRB identifier include the NR PDCP entity (S914). If it does, the NR PDCP entity is re-established based on the NR PDCP entity setting information (S916). Furthermore, if the NR PDCP entity settings corresponding to the DRB identifier do not include the PDCP entity settings, other settings are performed (S918). The E-UTRA PDCP entity and the NR PDCP entity can be switched through the above-described re-establishment process. For example, if in the current UE122 configuration, the PDCP entity corresponding to a certain DRB identifier (let's call it DRB identifier 1) is set as an E-UTRA PDCP entity, then DRB identifier 1 is included in the DRB settings included in the received RRC connection reset message. If the PDCP entity corresponding to DRB identifier 1 is set as an NR PDCP entity, then the PDCP entity corresponding to DRB identifier 1 will be reset to an NR PDCP entity. Similarly, if in the current UE122 configuration, the PDCP entity corresponding to a certain DRB identifier (let's call it DRB identifier 2) is set as an NR PDCP entity, then DRB identifier 2 is included in the DRB settings included in the received RRC connection reset message. If the PDCP entity corresponding to DRB identifier 2 is set as an E-UTRA PDCP entity, then the PDCP entity corresponding to DRB identifier 2 will be reset to an E-UTRA PDCP entity. Thus, the E-UTRA PDCP entity setting and the NR PDCP entity setting can be switched via the RRC connection reset message.

[0115] After the settings are completed via the setting unit 502 of UE122, Figure 6 In the process, UE122 sends an RRC connection reconfiguration complete message (S606) to eNB102 or gNB108 or both eNB102 and gNB108.

[0116] It should be noted that the DRB setting in this embodiment can include not only the RRC connection reset process, but also the RRC connection establishment process and the RRC connection re-Establishment process. Furthermore, the re-establishment of the PDCP entity in this embodiment can include, for example, resetting the Hyper Frame Number (HFN) to zero, changing the Initialization and Refresh (IR) mode for header compression, and changing the specified encryption algorithm and encryption key, as described in Non-Patent Document 5. It should be noted that the resetting of the Hyper Frame Number (HFN) to zero, the changing of the Initialization and Refresh (IR) mode for header compression, and the changing of the specified encryption algorithm and encryption key described in Non-Patent Document are for E-UTRA, but can also be applied to NR.

[0117] Thus, in this embodiment, the E-UTRA base station device (eNB) or the NR base station device (gNB), or both the eNB and gNB, select whether the PDCP entity used in communication with the UE is for E-UTRA or NR based on conditions such as the application services requested by the terminal device (UE), and notify the UE using an RRC connection reset message. This allows for the establishment of a PDCP entity suitable for the application services used by the UE, enabling efficient communication with reduced protocol processing complexity.

[0118] (Implementation Method 2)

[0119] In Embodiment 2 of the present invention, the following will be explained: In MR-DC (Multi-RAT Dual Connectivity), which has been studied as one of the NR technologies, the cells of both E-UTRA and NR Radio Access Technology (RAT) are grouped according to each RAT and assigned to the UE, and the UE communicates with more than one base station device. In particular, the DRB setting is in the case of EN-DC (E-UTRAN supports Multi-RAT Dual Connectivity (MR-DC) via E-UTRA-NR Dual Connectivity: E-UTRAN supports multi-RAT dual connectivity (MR-DC) through E-UTRA-NR dual connectivity) where the E-UTRA side base station device is the main base station device described below.

[0120] use Figure 1 and Figures 5-12 The following describes Embodiment 2.

[0121] Figure 10 This is a diagram illustrating an example of the relationship between the wireless protocol architecture and the RB on the base station device side of an EN-DC embodiment of the present invention.

[0122] EN-DC can utilize the following technology: It uses EPC as the core network, E-UTRA base station equipment as the master base station (Master eNB: MeNB), and NR base station equipment as the secondary base station (Secondary gNB: SgNB), forming a cell group consisting of two base station equipment. Specifically, the MeNB-based master cell group (MCG) and the SgNB-based secondary cell group (SCG) communicate using their respective radio resources. In MR-DC, the master base station can refer to a base station with the main RRC functions of MR-DC, such as RB establishment, modification, and release, as well as the addition, modification, release, and handover of secondary cells. The secondary base station can refer to a base station with some RRC functions, such as SCG modification and release.

[0123] like Figure 10As shown, a portion of the data transmitted and received via EN-DC is transmitted and received on the SgNB side, while the remaining portion is transmitted and received on the MeNB side. The EN-DC data transmission and reception methods can include the following: nodes within the EPC serve as anchor points for data branching / merging; the MeNB and SgNB each establish bearers as logical paths between themselves and the EPC for data transmission and reception, i.e., using MCG bearers on the MeNB side and SCG bearers on the SgNB side; and a method where the MeNB or SeNB serves as an anchor point, and the radio bearer (RB) used as the radio side forks at the MeNB and SeNB, using forked bearers for data transmission and reception. Forked bearers can be established in the following ways: during radio bearer establishment; or after the MCG or SCG bearer is established, by adding SCG-side or MCG-side radio bearers, changing the MCG or SCG bearer to a forked bearer. The establishment and modification of MCG bearers, SCG bearers, and fork bearers can be performed through the RRC (Radio Resource Control) connection reconfiguration process transmitted between the MeNB and the UE. In this embodiment, the cell group of the base station device that serves as the anchor point for the fork bearer is called the anchor cell group, and the cell group of the base station device that does not serve as the anchor point for the fork bearer is called the additional cell group. The anchor cell group can be MCG and the additional cell group can be SCG, or vice versa. Alternatively, the fork bearer when the anchor cell group is MCG can be called an MCG fork bearer, and the fork bearer when the anchor cell group is SCG can be called an SCG fork bearer.

[0124] In EN-DC, when using forked bearers for data transmission and reception, for downlink data, the anchor cell group's base station may distribute a portion of the downlink data transmitted from the EPC to the additional cell group's base station, which then transmits it to the UE. The remaining data is transmitted from the primary cell group's base station to the UE. For uplink data, the UE may transmit a portion of the uplink data to the additional cell group's base station, which then distributes this portion to the primary cell group's base station. The UE then transmits the remaining data to the primary cell group's base station.

[0125] like Figure 10As shown, when using a forked bearer, PDCP PDUs can be sent and received between the base station devices of the primary cell group and the base station devices of the additional cell group.

[0126] Figure 11 This diagram illustrates an example of DRB setting reception and setting when an MCG bearer or SCG bearer is established as an anchor cell group according to an embodiment of the present invention. It should be noted that, even when established as an anchor cell group, it may later be changed to a forked bearer. eNB 102 determines the DRB setting requested from UE 122 (S1100). eNB 102 may also determine the DRB setting based on information from the core network (EPCI04), or based on the capabilities of UE 122, or based on both information from the core network and the capabilities of UE 122. It should be noted that the information from the core network may also be determined based on the conditions of application services such as voice calls requested by UE 122. Next, eNB 102 generates an RRC connection reconfiguration request message including the DRB setting and sends it to UE 122 (S1102). The receiving unit 500 of UE 122 receives the RRC connection reconfiguration request message including the DRB setting and forwards the DRB setting to the setting unit 502.

[0127] Figure 7 and Figure 8 This is an example of ASN.1 (Abstract Syntax Notation One) of the DRB setting described in Implementation 1.

[0128] That is, in Figure 7 and Figure 8 In Figure 8 In the RRCConnectionReconfiguration message, the DRB-ToAddMod parameter is the IE configured for DRB. For example... Figure 7 and Figure 8 In Figure 8 As shown, DRB-ToAddMod can include DRB-Identity (the IE's identifier for DRB) and PDCP-Config (the PDCP entity setting information corresponding to the DRB identifier). Furthermore, as... Figure 7 and Figure 8 In Figure 8 As shown, the PDCP-Config, which serves as the PDCP entity configuration information, can be selected (CHOICE) as either PDCP-EUTRA-Config (as E-UTRA PDCP entity configuration information) or PDCP-NR-Config (as NR PDCP entity configuration information). Furthermore, as... Figure 7 and Figure 8 In Figure 8 As shown, PDCP-EUTRA-Config and PDCP-NR-Config may include pdcp-SN-Size information representing the length of the PDCP Sequence Number (SN), which may be an integer containing 7.

[0129] Figure 16 , Figure 17 and Figure 18 This is another example of the ASN.1 (Abstract Syntax Notation One) of the DRB setting described in Implementation 1.

[0130] That is, in Figure 16 , Figure 17 and Figure 18 In Figure 16 In the RRCConnectionReconfiguration message, the choice (CHOICE) can be either RRCConnectionReconfiguration-EUTRA-IE (as an E-UTRA request for RRC connection reconfiguration) or RRCConnectionReconfiguration-NR-IE (as an NR request for RRC connection reconfiguration).

[0131] like Figure 16 , Figure 17 and Figure 18 In Figure 16 and Figure 17 As shown, when an IE is selected to reset the E-UTRA connection using RRC, it can include DRB-ToAddMod-EUTRA for IEs configured with E-UTRA DRB. Furthermore, as... Figure 16 , Figure 17 and Figure 18 In Figure 17 As shown, DRB-ToAddMod-EUTRA can include DRB-Identity (the IE's identifier for DRB) and PDCP-Config-EUTRA (PDCP entity configuration information for the E-UTRA corresponding to the DRB identifier). Furthermore, as... Figure 16 , Figure 17 and Figure 18 In Figure 17 and Figure 18As shown, PDCP-Config-EUTRA, which serves as the PDCP entity configuration information for EUTRA, can also be selected (CHOICE) to include PDCP-EUTRA-Config, which serves as the PDCP entity configuration information for E-UTRA, or PDCP-NR-Config, which serves as the PDCP entity configuration information for NR, for use as the PDCP entity configuration for EUTRA. Furthermore, as... Figure 16 , Figure 17 and Figure 18 In Figure 18 As shown, PDCP-EUTRA-Config and PDCP-NR-Config may include pdcp-SN-Size information representing the length of the PDCP Sequence Number (SN), which may be an integer containing 7.

[0132] In addition, such as Figure 16 , Figure 17 and Figure 18 In Figure 16 and Figure 17 As shown, when an IE is selected to reset the NR connection using RRC, DRB-ToAddMod-NR can be included as an IE configured for NR using DRB. Furthermore, as... Figure 16 , Figure 17 and Figure 18 In Figure 17 As shown, DRB-ToAddMod-NR can include DRB-Identity (the IE's identifier for DRB) and PDCP-Config-NR (the NR's configuration information using the PDCP entity corresponding to the DRB identifier). Furthermore, as... Figure 16 , Figure 17 and Figure 18 In Figure 17 and Figure 18 As shown, PDCP-Config-NR, which serves as PDCP entity configuration information for NR, can also be selected (CHOICE) to include PDCP-EUTRA-Config, which serves as PDCP entity configuration information for E-UTRA, or PDCP-NR-Config, which serves as PDCP entity configuration information for NR, for use as PDCP entity configuration for NR. Furthermore, as... Figure 16 , Figure 17 and Figure 18 In Figure 18 As shown, PDCP-EUTRA-Config and PDCP-NR-Config may include pdcp-SN-Size information representing the length of the PDCP sequence number (SequenceNumber: SN), which may be an integer containing 7.

[0133] It should be noted that, as described in Implementation Method 1, Figure 7 and Figure 8 as well as Figure 16 , Figure 17 and Figure 18 The message name, IE name, parameter name, etc. in ASN.1 are just one example; they can also be other names. Furthermore, in Figure 7 and Figure 8 as well as Figure 16 , Figure 17 and Figure 18 In this context, the E-UTRA RLC entity and the NR RLC entity can be described using the same method as the method used to describe the E-UTRA PDCP entity and the NR PDCP entity. Furthermore, in... Figure 7 and Figure 8 as well as Figure 16 , Figure 17 and Figure 18 In addition, the MAC entities for E-UTRA (MACMainConfig (not shown), logicalChannelConfig, etc.) and MAC entities for NR can also be described in the same way as the PDCP entities for E-UTRA and PDCP entities for NR.

[0134] exist Figure 11 In S1104, the DRB settings transferred from the receiving unit 500 of UE122 to the setting unit 502 of UE122 include at least one of E-UTRA PDCP entity settings or NR PDCP entity settings as the DRB identifier and the corresponding PDCP entity settings. The setting unit 502 of UE122 establishes or re-establishes the PDCP entity based on the DRB identifier and the corresponding PDCP entity settings.

[0135] Figure 9This is an example of the PDCP setting determination in the setting unit of the terminal device as described in Embodiment 1. Specifically, the setting unit 502 of UE122 checks whether the value of the DRB identifier exists in the current terminal device settings (S900). If it does not exist, it checks whether the PDCP entity settings corresponding to the DRB identifier include E-UTRA PDCP entity setting information (S902). If it does, an E-UTRA PDCP entity is established based on the E-UTRA PDCP entity setting information (S904). On the other hand, if the PDCP entity settings corresponding to the DRB identifier do not include E-UTRA PDCP entity setting information, it further checks whether the PDCP entity settings corresponding to the DRB identifier include NR PDCP entity setting information (S906). If it does, an NR PDCP entity is established based on the NR PDCP entity setting information (S908). Furthermore, if the PDCP entity settings corresponding to the DRB identifier do not include NR PDCP entity setting information, other settings are performed (S918).

[0136] Furthermore, on one hand, if the value of the DRB identifier exists in the current terminal device settings, it is checked whether the PDCP entity settings corresponding to the DRB identifier include an E-UTRA PDCP entity (S910). If it does, the E-UTRA PDCP entity is re-established based on the E-UTRA PDCP entity setting information (S912). On the other hand, if the E-UTRA PDCP entity settings corresponding to the DRB identifier do not include the PDCP entity settings, it is further checked whether the NR PDCP entity settings corresponding to the DRB identifier include the NR PDCP entity (S914). If it does, the NR PDCP entity is re-established based on the NR PDCP entity setting information (S916). Furthermore, if the NR PDCP entity settings corresponding to the DRB identifier do not include the PDCP entity settings, other settings are performed (S918). The E-UTRA PDCP entity and the NR PDCP entity can be switched through the above-described re-establishment process. For example, if in the current UE122 configuration, the PDCP entity corresponding to a certain DRB identifier (let's call it DRB identifier 1) is set as an E-UTRA PDCP entity, then DRB identifier 1 is included in the DRB settings included in the received RRC connection reset message. If the PDCP entity corresponding to DRB identifier 1 is set as an NR PDCP entity, then the PDCP entity corresponding to DRB identifier 1 will be reset to an NR PDCP entity. Similarly, if in the current UE122 configuration, the PDCP entity corresponding to a certain DRB identifier (let's call it DRB identifier 2) is set as an NR PDCP entity, then DRB identifier 2 is included in the DRB settings included in the received RRC connection reset message. If the PDCP entity corresponding to DRB identifier 2 is set as an E-UTRA PDCP entity, then the PDCP entity corresponding to DRB identifier 2 will be reset to an E-UTRA PDCP entity. Thus, the E-UTRA PDCP entity setting and the NR PDCP entity setting can be switched via the RRC connection reset message.

[0137] After the settings are completed via the setting unit 502 of UE122, Figure 11 In the middle, UE122 sends an RRC connection reconfiguration complete message (RRCConnectionReconfigurationComplete) to eNB102 (S1106).

[0138] It should be noted that the DRB setting in this embodiment can include not only the RRC connection reset process, but also the RRC connection establishment process and the RRC connection re-Establishment process. Furthermore, the re-establishment of the PDCP entity in this embodiment can include, for example, resetting the Hyper Frame Number (HFN) to zero, changing the Initialization and Refresh (IR) mode for header compression, and changing the specified encryption algorithm and encryption key, as described in Non-Patent Document 5. It should be noted that the resetting of the Hyper Frame Number (HFN) to zero, the changing of the Initialization and Refresh (IR) mode for header compression, and the changing of the specified encryption algorithm and encryption key described in Non-Patent Document are for E-UTRA, but can also be applied to NR.

[0139] Next, the change from MCG or SCG bearer to fork bearer will be explained.

[0140] Figure 12 This is an example of ASN.1 (Abstract Syntax Notation One) for the DRB settings of additional cell groups when changing from an MCG or SCG bearer to a fork bearer. Figure 12 In the examples of ASN.1, <omitted> and <omitted in the middle> indicate that other information is omitted, rather than omitting a part of ASN.1. It should be noted that information may also be omitted where there is no mention of <omitted> or <omitted in the middle>. Figure 12 The example shown for ASN.1 can be... Figure 7 and Figure 8 or Figure 16 , Figure 17 and Figure 18 A portion of the example shown in ANS.1. Figure 12 The DRB-ToAddModADDCG-NR IE shown can be related to the DRB settings for adding a cell group, or it can have other names. Furthermore, Figure 12 The DRB-ToAddModADDCG-NR IE shown can also be part of a higher-level IE related to additional cell group settings.

[0141] exist Figure 11In step S1100, eNB102 determines the DRB settings of the anchor cell group and the additional cell group requested from UE122. However, the DRB settings of the anchor cell group may not be changed. If the DRB settings of the anchor cell group are changed, the DRB settings may include the DRB identifier and corresponding changed PDCP entity settings, etc. Alternatively, if the DRB settings of the anchor cell group are not changed, the DRB settings may only contain the DRB identifier. eNB102 may also determine whether to change the DRB settings of the anchor cell group based on information from the core network (EPC104) or the capabilities of UE122, or information from the core network and the capabilities of UE122. It should be noted that the information from the core network may also be based on the conditions of application services such as voice calls requested by UE122. Next, eNB102 generates an RRC Connection Reconfiguration request message including the DRB settings of the anchor cell and the additional cell, and sends it to UE122 (S602). The receiving unit 500 of UE122 receives an RRC connection reset request message including the DRB settings of the anchor cell and the DRB settings of the additional cell, and forwards the DRB settings of the anchor cell and the DRB settings of the additional cell to the setting unit 502.

[0142] In the setting unit 502 of UE122, if the value of the DRB identifier included in the DRB setting of the anchor cell group exists in the current setting of UE122, and the DRB identifier included in the DRB setting of the anchor cell group is the same as the DRB identifier included in the DRB setting of the additional cell group, that is, if the value of the DRB identifier of the anchor cell group is the same as the value of the DRB identifier of the additional cell group, and the DRB type of the additional cell group ( Figure 12 If the drb-Type-NR (or similar identifier) ​​is forked, it is determined that the existing MCG or SCG bearer should be changed to a forked bearer. It should be noted that the method for determining whether to change an existing MCG or SCG bearer to a forked bearer is not limited to this; other methods may also be used.

[0143] The setting unit 502 of UE122 can establish the DRB of the additional cell group according to the DRB settings of the additional cell group, and if there is a PDCP entity setting corresponding to the DRB identifier in the DRB settings of the anchor cell group, it can re-establish the PDCP entity according to the PDCP entity setting. The above-described re-establishment process can switch between the E-UTRA PDCP entity and the NR PDCP entity. For example, if the PDCP entity corresponding to a certain DRB identifier (let's say DRB identifier 1) in the current UE122 settings is set to be an E-UTRA PDCP entity, and the aforementioned DRB identifier 1 is included in the DRB settings included in the received RRC connection resetting message, and if the PDCP entity corresponding to DRB identifier 1 is set to be an NR PDCP entity, the PDCP entity corresponding to DRB identifier 1 is re-set to an NR PDCP entity. Similarly, if the PDCP entity corresponding to a certain DRB identifier (let's call it DRB identifier 2) is set as an NR PDCP entity in the current UE122 settings, and this DRB identifier 2 is included in the DRB settings included in the received RRC connection reset message, and if the PDCP entity corresponding to this DRB identifier 2 is set as an E-UTRA PDCP entity, then the PDCP entity corresponding to DRB identifier 2 will be reset to an E-UTRA PDCP entity. Thus, the E-UTRA PDCP entity setting and the NR PDCP entity setting can be switched via the RRC connection reset message.

[0144] Thus, in this embodiment, under EN-DC conditions, the PDCP entity used in the communication between the anchor cell group and the UE can be selected as either E-UTRA or NR based on conditions such as the application services requested by the terminal device (UE), and an RRC connection reset message can be used to notify the UE. Therefore, under EN-DC conditions, a PDCP entity suitable for the application services used by the UE can be established, enabling efficient communication with reduced protocol processing complexity.

[0145] (Implementation Method 3)

[0146] In Embodiment 3 of the present invention, the DRB settings, including SDAP entity settings, are described when the core network is 5GC110. In Embodiment 3, UE122 can communicate with 5GC110 via gNB, communicate with 5GCI via eNB, or communicate with 5GC using MR-DC of both gNB and eNB.

[0147] use Figure 1 , Figure 5 , Figure 7 and Figure 8 ,as well as Figures 13-15 , Figure 16 , Figure 17 and Figure 18 Implementation method 3 will be described.

[0148] Figure 13 This diagram illustrates an example of DRB setting reception and setting according to an embodiment of the present invention. eNB102 or gNB108, or both eNB102 and gNB108, determine the DRB setting (S1300) requested from UE122, including SDAP entity settings. eNB102 or gNB108, or both eNB102 and gNB108, can also determine the DRB setting based on information from the core network (EPC104 or 5GC110, or both EPC104 and 5GC110), or based on the capabilities of UE122, or based on both information from the core network and the capabilities of UE122. It should be noted that the information from the core network can also be determined based on the conditions of application services such as voice calls requested by UE122. Furthermore, the DRB setting may include SDAP-related information such as the SDAP header length. Additionally, SDAP-related information may be included in the SDAP entity settings, or in other entity settings such as the PDCP entity settings. Next, eNB102 or gNB108, or both eNB102 and gNB108, generate an RRC Connection Reconstruction Request message including DRB settings and send it to UE122 (S1302). UE122's receiving unit 500 receives the RRC Connection Reconstruction Request message including DRB settings and forwards the DRB settings to the setting unit 502.

[0149] Figure 14 and Figure 15 This is an example of an ASN.1 (Abstract Syntax Notation One) indicating a DRB setting including SDAP information, representing an embodiment of the present invention. Figure 14 and Figure 15 In the examples of ASN.1, <omitted> and <omitted in the middle> indicate that other information is omitted, rather than omitting a part of ASN.1. It should be noted that information may also be omitted where there is no mention of <omitted> or <omitted in the middle>.

[0150] Figure 14 This is an example of SDCP entity settings including SDCP header length information. Figure 15This is an example of other PDCP entity settings including the SDCP header length. The SDCP header length information can be included in either the SDCP entity setting or the PDCP entity setting, or it can be included in both. The SDAP header length can be a multiple of 8 containing zeros (0). For example, in... Figure 14 and Figure 15 In the examples, "lenobits", "len8bits", "len16bits", and "len24bits" can represent 0 bits, 8 bits, 12 bits, and 24 bits, respectively. Alternatively, they can be represented in bytes or octets, such as "len0bytes", "len1bytes", "len2bytes", and "len3bytes". It should be noted that an SDAP header length of 0 can mean that an SDAP header does not exist. Furthermore, the representation and name of the SDAP header length are not limited to this and can use other representations and names. Figure 14 and Figure 15 The message name, IE name, parameter name, etc. in ASN.1 are just examples; they can also be other names. Furthermore, Figure 14 and Figure 15 The example shown for ASN.1 can be... Figure 7 and Figure 8 or Figure 16 , Figure 17 and Figure 18 Part of the example shown for ASN.1.

[0151] use Figure 14 An example, specifically an example where the SDAP header length exists in the SDAP entity settings, will be used to explain the setting section 502 of UE122. Figure 13 In S1304, the DRB settings transferred from the receiving unit 500 of UE122 to the setting unit 502 of UE122 include at least a DRB identifier and the SDAP entity settings corresponding to the DRB identifier. The SDAP entity settings include the SDAP header length. The setting unit 502 of UE122 establishes or re-establishes the SDAP entity based on the DRB identifier and the SDAP entity settings corresponding to the DRB identifier. That is, if the value of the DRB identifier transferred from the receiving unit 500 does not exist in the current terminal device settings, the SDAP entity is established; if the value of the DRB identifier transferred from the receiving unit 500 exists in the current terminal device settings, the SDAP entity is re-established. It should be noted that when the SDAP header length is 0, the process can be either establishing the SDAP entity but not having an SDAP header, or not establishing the SDAP entity at all.

[0152] use Figure 15 An example, specifically an example where the SDAP header length exists in the PDCP entity settings, will be used to explain the setting section 502 of UE122. Figure 13 In S1304, the DRB settings transferred from the receiving unit 500 of UE122 to the setting unit 502 of UE122 include at least a DRB identifier and a PDCP entity setting corresponding to the DRB identifier. The PDCP entity setting includes the SDAP header length. The setting unit 502 of UE122 establishes or re-establishes the PDCP entity based on the DRB identifier and the PDCP entity setting corresponding to the DRB identifier. That is, the PDCP entity may be established if the value of the DRB identifier transferred from the receiving unit 500 does not exist in the current terminal device settings, and re-established if the value of the DRB identifier transferred from the receiving unit 500 exists in the current terminal device settings. The established or re-established PDCP entity can determine the SDAP SDU, i.e., the start position of the IP packet, based on the SDAP header length information and perform header compression processing. It should be noted that when the SDAP header length is included in the SDAP entity settings but not in the PDCP entity settings, the PDCP entity can also determine the SDAP SDU, i.e. the start position of the IP packet, based on the SDAP header length information included in the SDAP entity settings, and perform header compression processing.

[0153] After the settings are completed via the setting unit 502 of UE122, Figure 13 In the process, UE122 sends an RRC connection reconfiguration complete message (S1306) to eNB102 or gNB108 or both eNB102 and gNB108.

[0154] It should be noted that the DRB setting in this embodiment can include not only the RRC connection reset process, but also the RRC connection establishment process and the RRC connection re-Establishment process. Furthermore, the re-establishment of the PDCP entity in this embodiment can include, for example, resetting the Hyper Frame Number (HFN) to zero, changing the Initialization and Refresh (IR) mode for header compression, and changing the specified encryption algorithm and encryption key, as described in Non-Patent Document 5. It should be noted that the resetting of the Hyper Frame Number (HFN) to zero, the changing of the Initialization and Refresh (IR) mode for header compression, and the changing of the specified encryption algorithm and encryption key described in Non-Patent Document are for E-UTRA, but can also be applied to NR.

[0155] Furthermore, the DRB setting in this embodiment assumes that the core network is 5GC, but it can also be applied to the case where the core network is EPC.

[0156] Thus, in this embodiment, the E-UTRA base station device (eNB) or the NR base station device (gNB), or both the eNB and gNB, set the SDAP entity (including the SDAP header length) used in communication with the UE based on conditions such as application services requested by the terminal device (UE), including voice calls, and set the PDCP entity (including the SDAP header length). The PDCP entity is then notified to the UE using an RRC connection reset message. This allows for the use of SDAP header lengths suitable for the application services used by the UE, and enables efficient communication with reduced protocol processing complexity by performing header compression based on the PDCP entity as needed.

[0157] It should be noted that the descriptions related to RRC in the various embodiments of the present invention, such as RRC connection reset request messages and ASN.1, are assumed to be NR-use RRC (e.g., the RRC described in Non-Patent Documents 9 and 10), but may also be extensions for LTE, and may be transmitted and received between E-UTRA base station devices and terminal devices corresponding to MR-DC.

[0158] Furthermore, the re-establishment of entities such as the PDCP entity in each embodiment of the present invention can be performed through the RRC connection reset process during handover. Additionally, during the re-establishment of entities such as the PDCP entity in each embodiment of the present invention, security-related settings can also be reset.

[0159] The program operating in the apparatus of the present invention can be a program that controls the Central Processing Unit (CPU) or similar components to enable the computer to perform its functions in a manner that achieves the functions described in the embodiments of the present invention. During processing, the program or the information processed by the program is temporarily read into volatile memory such as Random Access Memory (RAM) or stored in non-volatile memory such as Flash Memory or Hard Disk Drive (HDD), and is read, modified, and written by the CPU as needed.

[0160] It should be noted that a portion of the device described in the above embodiments can be implemented using a computer. In this case, the program for implementing the control function can be recorded on a computer-readable recording medium, and the control function can be implemented by reading the program recorded on the recording medium into a computer system and executing it. The term "computer system" here refers to a computer system built into the device, including hardware such as an operating system and peripherals. Furthermore, the "computer-readable recording medium" can be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, etc.

[0161] Furthermore, a "computer-readable recording medium" can include: a medium that dynamically stores a program for a short period of time, such as a communication line in the case of transmitting a program via a network such as the Internet or a communication line such as a telephone line; or a medium that stores a program for a fixed period of time, such as volatile memory within a computer system that serves as a server or client in this case. In addition, the program can be a program used to implement the aforementioned functions, or it can be a program that can be further implemented by combining the aforementioned functions with a program already recorded in the computer system.

[0162] Furthermore, the functional blocks or features of the apparatus used in the above embodiments can be installed or executed via circuitry, typically via integrated circuits or multiple integrated circuits. Circuits designed to perform the functions described in this specification may include: general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic elements, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general-purpose processor may be a microprocessor, or alternatively, a conventional processor, controller, microcontroller, or state machine. The general-purpose processor or the aforementioned circuits may be constructed from digital circuits or analog circuits. Furthermore, in cases where advancements in semiconductor technology have led to the development of integrated circuit technologies that replace existing integrated circuits, integrated circuits based on such technologies may also be used.

[0163] [Summarize]

[0164] The terminal device of Scheme 1 of the present invention is a terminal device that communicates with a base station device, and is configured to include: a receiving unit that receives an RRC connection reset request message including DRB (Data Radio Bearer) settings from the base station device; and a setting unit that sets the DRB according to the DRB settings, wherein the DRB settings include a DRB identifier and a PDCP entity setting corresponding to the DRB identifier, the value of the DRB identifier is not present in the current settings of the terminal device, and the PDCP entity setting information includes one of E-UTRA PDCP entity setting and NR PDCP entity setting. When the PDCP entity setting information includes information of the E-UTRA PDCP entity setting, the setting unit establishes a PDCP entity according to the PDCP entity setting information. When the PDCP entity setting information includes information of the NR PDCP entity setting, the setting unit establishes a PDCP entity according to the PDCP entity setting information.

[0165] The terminal device of embodiment 2 of the present invention is a terminal device that communicates with a base station device, and is configured to include: a receiving unit that receives an RRC connection reset request message including DRB (Data Radio Bearer) settings from the base station device; and a setting unit that sets the DRB according to the DRB settings, wherein the DRB settings include a DRB identifier and a PDCP entity setting corresponding to the DRB identifier, the value of the DRB identifier is present in the current settings of the terminal device, and the PDCP entity setting information includes one of E-UTRA PDCP entity setting and NR PDCP entity setting. When the PDCP entity setting information includes information of the E-UTRA PDCP entity setting, the setting unit re-establishes the PDCP entity according to the PDCP entity setting information; when the PDCP entity setting information includes information of the NR PDCP entity setting, the setting unit establishes the PDCP entity according to the PDCP entity setting information.

[0166] The terminal device of Solution 3 of the present invention is a terminal device corresponding to MR-DC (Multi-Radio Access Technology Dual Connectivity) supporting E-UTRA (Evolved Universal Terrestrial Radio Access) and NR (New Radio), and is configured to include: a receiving unit that, when E-UTRA is the primary cell group, receives from the primary base station device an RRC connection reset request message including the DRB (Data Radio Bearer) setting of the anchor cell group; and a setting unit that sets the DRB according to the DRB setting. The DRB setting includes a DRB identifier and a PDCP entity setting corresponding to the DRB identifier. The value of the DRB identifier is not present in the current terminal device settings. The PDCP entity setting information includes one of E-UTRA PDCP entity setting and NR PDCP entity setting. When the PDCP entity setting information includes E-UTRA PDCP entity setting information, the setting unit establishes the PDCP entity based on the PDCP entity setting information. When the PDCP entity setting information includes NR PDCP entity setting information, the setting unit establishes the PDCP entity based on the PDCP entity setting information.

[0167] The terminal device of Scheme 4 of the present invention is a terminal device corresponding to MR-DC (Multi Radio Access Technology Dual Connectivity) supporting E-UTRA (Evolved Universal Terrestrial Radio Access) and NR (New Radio). It is configured to include: a receiving unit that, when E-UTRA is the primary cell group, receives from a primary base station device an RRC connection reset request message including the DRB (Data Radio Bearer) setting of the anchor cell group; and a setting unit that sets the DRB according to the DRB setting, the DRB setting including a DRB identifier and a PDCP entity setting corresponding to the DRB identifier, the value of the DRB identifier existing in the current terminal device settings, the PDCP entity setting information including one of an E-UTRA PDCP entity setting and an NR PDCP entity setting, wherein, when the PDCP entity setting information includes information of the E-UTRA PDCP entity setting, the setting unit re-establishes the PDCP entity according to the PDCP entity setting information, and when the PDCP entity setting information includes information of the NR PDCP entity setting, the setting unit re-establishes the PDCP entity according to the PDCP entity setting information.

[0168] The terminal device of Scheme 5 of the present invention can be configured such that the anchor cell group described in Scheme 3 or 4 above is the main cell group.

[0169] The terminal device of Scheme 6 of the present invention can be configured such that the anchor cell group described in Scheme 3 or 4 above is an auxiliary cell group.

[0170] The terminal device of Scheme 7 of the present invention is a terminal device corresponding to MR-DC (Multi Radio Access Technology Dual Connectivity) that supports E-UTRA (Evolved Universal Terrestrial Radio Access) and NR (New Radio). It is configured to include: a receiving unit that, when the E-UTRA is the primary cell group, receives from the primary base station device an RRC connection reset request message including the DRB (Data Radio Bearer) setting of the anchor cell group and the DRB setting of the additional cell group; and a setting unit that sets the DRB according to the DRB setting, wherein the DRB setting of the anchor cell group includes the DRB identifier of the anchor cell group and the PDCP entity setting corresponding to the DRB identifier of the anchor cell group, and the DRB setting of the additional cell group includes the DRB identifier of the anchor cell group and information that the DRB type is forked, and re-establishes the PDCP entity of the anchor cell group according to the PDCP entity setting information included in the DRB setting of the anchor cell group corresponding to the DRB identifier of the anchor cell group.

[0171] The terminal device of Scheme 8 of the present invention can be configured such that the anchor cell group in Scheme 7 is the main cell group, and the additional cell group is the auxiliary cell group.

[0172] The terminal device of Scheme 9 of the present invention can be configured such that the anchor cell group in Scheme 7 is the auxiliary cell group, and the additional cell group is the main cell group.

[0173] The terminal device of Scheme 10 of the present invention can be configured such that, in Schemes 1 to 9 above, the PDCP entity setting information includes the PDCP serial number length, including information representing the PDCP entity setting, and the PDCP serial number length is one or more of an integer value containing 7.

[0174] The terminal device of Scheme 11 of the present invention is a terminal device corresponding to EN-DC, which can be configured as follows: a receiving unit that receives an RRC connection reset message from a base station device, the RRC connection reset message including a DRB identifier and a PDCP entity setting corresponding to the DRB, the PDCP entity setting being either an E-UTRA PDCP entity setting or an NR PDCP entity setting, including a setting unit that determines whether the RRC connection reset message includes the E-UTRA PDCP entity setting, and the setting unit, if the terminal device does not set the value of the DRB identifier, and if it is determined that the RRC connection reset message includes the E-UTRA PDCP entity setting, establishes a PDCP entity according to the E-UTRA PDCP entity setting.

[0175] The terminal device of Scheme 12 of the present invention can be configured such that the PDCP entity in Scheme 11 above corresponds to the MCG bearer of the EN-DC.

[0176] The base station apparatus of embodiment 13 of the present invention is a base station apparatus corresponding to EN-DC, configured to include: a generation unit for generating an RRC connection reset message; and a transmission unit for transmitting the RRC connection reset message to a terminal device. The RRC connection reset message includes a DRB (Data Radio Bearer) identifier and a PDCP entity setting corresponding to the DRB identifier. The PDCP entity setting is selected from an E-UTRA PDCP entity setting and an NR PDCP entity setting. If the terminal device does not set a value for the DRB identifier, and if it is determined that the RRC connection reset message includes the E-UTRA PDCP entity setting, the RRC connection reset message including the DRB identifier and the PDCP entity setting causes the terminal device to establish a PDCP entity according to the E-UTRA PDCP entity setting.

[0177] The terminal device of embodiment 14 of the present invention can be configured such that the PDCP entity in embodiment 13 above corresponds to the MCG bearer of the EN-DC.

[0178] Furthermore, the method of Scheme 15 of the present invention is a method performed by a terminal device corresponding to EN-DC, the method being as follows: receiving an RRC connection reset message from a base station device, the RRC connection reset message including a Data Radio Bearer (DRB) identifier and a PDCP entity setting corresponding to the DRB identifier, the PDCP entity setting being either an E-UTRA PDCP entity setting or an NR PDCP entity setting; determining whether the RRC connection reset message includes the E-UTRA PDCP entity setting; if the terminal device has not set the value of the DRB identifier, and if it is determined that the RRC connection reset message includes the E-UTRA PDCP entity setting, establishing a PDCP entity according to the E-UTRA PDCP entity setting.

[0179] The method of Scheme 16 of the present invention can be adopted as follows: In Scheme 15 above, the PDCP entity corresponds to the MCG bearer of the EN-DC.

[0180] The method of Scheme 17 of the present invention is a method performed by a base station device corresponding to EN-DC, the method being as follows: generating an RRC connection reset message, sending the RRC connection reset message to a terminal device, the RRC connection reset message including a DRB (Data Radio Bearer) identifier and a PDCP entity setting corresponding to the DRB identifier, the PDCP entity setting being selected from E-UTRA PDCP entity setting and NR PDCP entity setting, in the case where the terminal device has not set a value for the DRB identifier, and in the case where it is determined that the RRC connection reset message includes the E-UTRA PDCP entity setting, the RRC connection reset message including the DRB identifier and the PDCP entity setting causes the terminal device to establish a PDCP entity according to the E-UTRA PDCP entity setting.

[0181] The method of Scheme 18 of the present invention can be adopted as follows: In Scheme 17 above, the PDCP entity corresponds to the MCG bearer of the EN-DC.

[0182] The terminal device of embodiment 19 of the present invention is a terminal device that communicates with a base station device, comprising: a receiving unit that receives an RRC connection reset request message including DRB (Data Radio Bearer) settings from the base station device; and a setting unit that sets the DRB according to the DRB settings, wherein the DRB settings include a DRB identifier and PDCP entity settings corresponding to the DRB identifier, the value of the DRB identifier not existing in the current settings of the terminal device, and the PDCP entity setting information includes one of E-UTRA PDCP entity settings and NR PDCP entity settings. When the PDCP entity setting information includes E-UTRA PDCP entity settings, the setting unit establishes a PDCP entity according to the PDCP entity setting information; when the PDCP entity setting information includes NR PDCP entity settings, the setting unit establishes a PDCP entity according to the PDCP entity setting information.

[0183] Furthermore, the terminal device of Solution 20 of the present invention is a terminal device that communicates with a base station device, comprising: a receiving unit that receives an RRC connection reset request message including DRB (Data Radio Bearer) settings from the base station device; and a setting unit that sets the DRB according to the DRB settings, wherein the DRB settings include a DRB identifier and PDCP entity settings corresponding to the DRB identifier, the value of the DRB identifier being present in the current settings of the terminal device, and the PDCP entity setting information including one of E-UTRA PDCP entity settings and NR PDCP entity settings. When the PDCP entity setting information includes E-UTRA PDCP entity settings, the setting unit re-establishes the PDCP entity according to the PDCP entity setting information; when the PDCP entity setting information includes NR PDCP entity settings, the setting unit establishes the PDCP entity according to the PDCP entity setting information.

[0184] Furthermore, the terminal device of Solution 21 of the present invention is a terminal device corresponding to MR-DC (Multi Radio Access Technology Dual Connectivity) supporting E-UTRA (Evolved Universal Terrestrial Radio Access) and NR (New Radio), comprising: a receiving unit that, when the E-UTRA is the primary cell group, receives from a primary base station device an RRC connection reset request message including the DRB (Data Radio Bearer) setting of the anchor cell group; and a setting unit that sets the DRB according to the DRB setting, the DRB setting including a DRB identifier and a PDCP entity setting corresponding to the DRB identifier, the value of the DRB identifier not existing in the current terminal device setting, the PDCP entity setting information including one of E-UTRA PDCP entity setting and NR PDCP entity setting, when the PDCP entity setting information includes the information of the E-UTRA PDCP entity setting, the setting unit establishes a PDCP entity according to the PDCP entity setting information, and when the PDCP entity setting information includes the NR PDCP entity setting information, the setting unit establishes a PDCP entity according to the PDCP entity setting information.

[0185] Furthermore, the terminal device of Solution 22 of the present invention is a terminal device corresponding to MR-DC (Multi Radio Access Technology Dual Connectivity) supporting E-UTRA (Evolved Universal Terrestrial Radio Access) and NR (New Radio), comprising: a receiving unit that, when the E-UTRA is the primary cell group, receives from a primary base station device an RRC connection reset request message including the DRB (Data Radio Bearer) setting of the anchor cell group; and a setting unit that performs DRB setting according to the DRB setting, the DRB setting including a DRB identifier and a PDCP entity setting corresponding to the DRB identifier, the value of the DRB identifier being present in the current terminal device setting, the PDCP entity setting information including one of E-UTRA PDCP entity setting and NR PDCP entity setting, wherein, when the PDCP entity setting information includes information of the E-UTRA PDCP entity setting, the setting unit re-establishes the PDCP entity according to the PDCP entity setting information, and when the PDCP entity setting information includes information of the NR PDCP entity setting, the setting unit re-establishes the PDCP entity according to the PDCP entity setting information.

[0186] Furthermore, the terminal device of Solution 23 of the present invention is a terminal device corresponding to MR-DC (Multi Radio Access Technology Dual Connectivity) that supports E-UTRA (Evolved Universal Terrestrial Radio Access) and NR (New Radio), comprising: a receiving unit that, when the E-UTRA is the primary cell group, receives from the primary base station device an RRC connection reset request message including the DRB (Data Radio Bearer) setting of the anchor cell group and the DRB setting of the additional cell group; and a setting unit that sets the DRB according to the DRB setting, wherein the DRB setting of the anchor cell group includes the DRB identifier of the anchor cell group and the PDCP entity setting corresponding to the DRB identifier of the anchor cell group, and the DRB setting of the additional cell group includes the DRB identifier of the anchor cell group and information that the DRB type is forked, and re-establishes the PDCP entity of the anchor cell group according to the PDCP entity setting information included in the DRB setting of the anchor cell group corresponding to the DRB identifier of the anchor cell group.

[0187] Furthermore, the terminal device of embodiment 24 of the present invention is a terminal device that communicates with a base station device, comprising: a receiving unit that receives an RRC connection reset request message including DRB (Data Radio Bearer) settings from the base station device; and a setting unit that sets the DRB according to the DRB settings, wherein the DRB settings include a DRB identifier and an SDAP entity setting corresponding to the DRB identifier, wherein the value of the DRB identifier is not present in the current settings of the terminal device, and the SDAP entity setting includes an SDAP header length, wherein the SDAP header length is one or more values ​​that are integer multiples of 8 including 0, and establishes an SDAP entity according to the SDAP setting information.

[0188] Furthermore, the terminal device of embodiment 25 of the present invention is a terminal device that communicates with a base station device, comprising: a receiving unit that receives an RRC connection reset request message including DRB (Data Radio Bearer) settings from the base station device; and a setting unit that sets the DRB according to the DRB settings, wherein the DRB settings include a DRB identifier and an SDAP entity setting corresponding to the DRB identifier, the value of the DRB identifier being present in the current terminal device settings, the SDAP entity setting including an SDAP header length, wherein the SDAP header length is one or more values ​​that are integer multiples of 8 including 0, and re-establishes the SDAP entity according to the SDAP setting information.

[0189] It should be noted that these specific solutions can be implemented by systems, devices, methods, integrated circuits, computer programs, or recording media, or by any combination of systems, devices, methods, integrated circuits, computer programs, and recording media.

[0190] It should be noted that the invention described in this application is not limited to the embodiments described above. While one example of the device is described in the embodiments, the invention is not limited thereto and can be applied to fixed or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other terminal devices or communication devices in daily life.

[0191] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the specific configuration is not limited to these embodiments, and design changes that do not depart from the spirit of the present invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the technical solutions shown, and embodiments obtained by appropriately combining technical solutions disclosed in different embodiments are also included within the technical scope of the present invention. In addition, it also includes configurations obtained by substituting elements that serve the same effect as those described in the above embodiments.

[0192] (Mutual reference in related applications)

[0193] This application is based on the interest claimed by Japanese Patent Application No. 2017-117491, filed on June 15, 2017, the entire contents of which are incorporated herein by reference.

Claims

1. A user equipment (UE) supporting Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity (EN-DC), the UE comprising: The receiving unit is configured to receive RRCConnectionReconfiguration messages from the primary E-UTRAN node B, i.e., the MeNB; as well as The configuration unit is configured to establish a DRB by referring to the DRB configuration information when the data radio bearer DRB configuration information is included in the RRCConnectionReconfiguration message, wherein... The DRB is the primary cell group (MCG) bearer of the EN-DC. The DRB is used as a path for transmitting user data. The user data is transmitted between the UE and the MeNB via the user plane UP. The Physical PHY layer, Media Access Control (MAC) layer, Radio Link Control (RLC) layer, and Packet Data Convergence Protocol (PDCP) layer exist in the protocol stack of the UP. The MAC layer and the RLC layer are layers used for evolving Universal Terrestrial Radio Access (E-UTRA), and The PDCP layer is a layer used for the new wireless NR.

2. A primary E-UTRAN node B, or MeNB, supporting Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity (EN-DC), wherein the MeNB comprises: The transmitting unit is configured to send an RRCConnectionReconfiguration message to a user equipment (UE), the RRCConnectionReconfiguration message including data radio bearer (DRB) configuration information, so that the UE can establish a DRB. The DRB is the primary cell group (MCG) bearer of the EN-DC. The DRB is used as a path for transmitting user data. The user data is transmitted between the UE and the MeNB via the user plane UP. The Physical PHY layer, Media Access Control (MAC) layer, Radio Link Control (RLC) layer, and Packet Data Convergence Protocol (PDCP) layer exist in the protocol stack of the UP. The MAC layer and the RLC layer are layers used for evolving Universal Terrestrial Radio Access (E-UTRA), and The PDCP layer is a layer used for the new wireless NR.

Images