JP7271766B2 - TERMINAL DEVICE, BASE STATION DEVICE, COMMUNICATION METHOD, AND INTEGRATED CIRCUIT - Google Patents

Description

The present invention relates to a terminal device, a base station device, a communication method, and an integrated circuit.

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

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

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

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

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

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

In order to achieve the above object, one aspect of the present invention takes the following means. That is, one aspect of the present invention is a base station apparatus that supports EN-DC, comprising a communication unit that transmits an RRC connection reconfiguration message including a DRB setting to a terminal device, and the DRB setting includes the EN- A setting used in the process of establishing an MCG bearer of DC, the DRB setting includes a DRB identifier and a PDCP entity setting associated with the DRB identifier, and the PDCP entity setting is a PDCP entity setting for NR be. Also, one aspect of the present invention is a method performed by a base station device supporting EN-DC, wherein the method transmits an RRC connection reconfiguration message including DRB settings to a terminal device, and is a setting used in the process of establishing the MCG bearer of the EN-DC, the DRB setting includes a DRB identifier and a PDCP entity setting associated with the DRB identifier, the PDCP entity setting is NR This is the PDCP entity setting for

ADVANTAGE OF THE INVENTION According to one aspect of the present invention, a terminal apparatus and a base station apparatus can reduce the complexity of protocol processing and communicate efficiently.

1 is a schematic diagram of a communication system according to each embodiment of the present invention; FIG. 4 is a protocol stack diagram of UP and CP of a terminal device and a base station device in E-UTRA according to each embodiment of the present invention; FIG. FIG. 3 is a protocol stack diagram of UP and CP of a terminal device and a base station device in NR in each embodiment of the present invention; The figure which shows an example of the flow of the RRC connection resetting procedure in each embodiment of this invention. FIG. 2 is a block diagram of a terminal device (UE) according to each embodiment of the present invention; The figure which shows an example of DRB setting reception and setting in Embodiment 1 of this invention. ASN. 1 (Abstract Syntax Notation One). ASN. 1 (Abstract Syntax Notation One) is another part (second sheet) of a diagram showing an example. The figure which shows an example of PDCP setting determination in the setting part of the terminal device in Embodiment 1 of this invention. FIG. 10 is an example diagram showing the relationship between the EN-DC base station apparatus side radio protocol architecture and RBs according to Embodiment 2 of the present invention; The figure which shows an example of DRB setting reception and setting in the case of establishing an MCG bearer or an SCG bearer as a bearer of an anchor cell group in Embodiment 2 of this invention. In Embodiment 2 of the present invention, ASN. 1 (Abstract Syntax Notation One). The figure which shows an example of DRB setting reception and setting in Embodiment 3 of this invention. According to Embodiment 3 of the present invention, ASN. 1 (Abstract Syntax Notation One). According to Embodiment 3 of the present invention, ASN. 1 (Abstract Syntax Notation One). ASN. 1 (Abstract Syntax Notation One). ASN. 1 (Abstract Syntax Notation One) is another part (second sheet) of a diagram showing an example. ASN. 1 (Abstract Syntax Notation One).

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

LTE (and LTE-A Pro) and NR may be defined as different RATs. NR may also be defined as a technology included in LTE. LTE may be defined as a technology included in NR. Also, LTE that can be connected with NR by dual connectivity may be distinguished from conventional LTE. This embodiment may be applied to NR, LTE and other RATs. The following description uses terms related to LTE and NR, but may be applied to other technologies using other terms.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

FIG. 3 is a protocol stack diagram of UP and CP of terminal equipment and base station equipment in NR in each embodiment of the present invention.

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

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

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

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

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

SDAP (Service Data Adaptation Protocol) 310 may have a function of mapping QoS of data sent from 5GC 110 to gNB 108 and data sent from gNB to 5GC 110 and QoS of RB. (Non-Patent Document 9). If the eNB 102 is directly connected to the 5GC 110, i.e. connected to the 5GC via interface 114, or if the eNB 102 is indirectly connected to the 5GC 110, i.e. connected to the 5GC via the interface 120 and the interface 116, the SDAP 310 is E - May exist as a layer above PDCP 206, which is the UTRA PDCP. Details are under discussion in 3GPP.

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

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

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

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

In the embodiment of the present invention, in order to distinguish between the E-UTRA protocol and the NR protocol, the MAC 202, RLC 204, PDCP 206, and RRC 208 are respectively defined as MAC for E-UTRA, RLC for E-UTRA, and E-UTRA. It is also called PDCP for UTRA and RRC for E-UTRA. Also, the MAC 302, RLC 304, PDCP 306, and RRC 308 may be called MAC for NR, RLC for NR, PDCP for NR, and RRC for NR, respectively.

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

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

The RRC connection reconfiguration procedure (RRC connection reconfiguration) is described in Non-Patent Document 4, establishes, changes, and releases RBs in E-UTRA, and changes and releases secondary cells, as well as handover and measurement ( Measurement), etc., but may be used for establishment, change, and release of RBs in NR, addition, change, release, handover, measurement, etc. of secondary cells, It may be described in Non-Patent Document 10. In each embodiment of the present invention, the procedures used for establishing, changing, and releasing RBs in NR, and adding, changing, releasing, handover, and measuring (Measurement) of cell groups are referred to as RRC connection reconfiguration procedures. However, another name may be used. The RRC connection reconfiguration procedure in each embodiment of the present invention is an RRC connection reconfiguration procedure including RB establishment, change, and release in NR, addition, change, release, handover, measurement, etc. of cell groups. It can be.

As shown in FIG. 4, eNB 102 or gNB 108 or both eNB 102 and gNB 108 send an RRC connection reconfiguration request message (RRCConnectionReconfiguration message) to UE 122 when the need for RRC connection reconfiguration occurs (S400). The UE 122 that has received the RRC connection reset request message performs settings according to the information (Information Element: IE) included in the RRC connection reset request message, and notifies that the setting has been completed. The RRC connection reconfiguration complete message (RRCConnectionReconfigurationComplete message) may be transmitted to the eNB 102 or gNB 108, or both the eNB and the gNB, which are the source of the transmission (S402). Note that the message names of the RRCConnectionReconfiguration message and the RRCConnectionReconfigurationComplete message may not be exactly as described above. Also, the UE 122 may transmit the RRC connection reconfiguration complete message to both the eNB 102 and the gNB 108 regardless of whether the base station device that transmitted the RRC connection reconfiguration request is the eNB 102 or the gNB 108 . In addition, the UE 122, not only the RRC connection reconfiguration procedure, but also for all or part of other RRC-related means (RRC connection setting means, RRC connection reconfiguration means, etc.), eNB 102 or gNB 108, or both eNB 102 and gNB 108 In response to a request message (RRCConnectionSetup, RRCConnectionReestablishment, etc.) sent from, regardless of whether the base station device that sent the request message is eNB 102 or gNB 108, the completion message may be sent to both eNB 102 and gNB 108.

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

UE 122 shown in FIG. 5 includes a receiving unit 500 that receives an RRC connection reconfiguration request message from eNB 102, or gNB 108, or both eNB and gNB, and DRB configuration information (DRB configuration) is included in the RRC connection reconfiguration request message. If so, it consists of a setting section 502 that sets the DRB according to this DRB setting. UE 122 may include functions other than receiving section 500 and setting section 502 .

(Embodiment 1)
Embodiment 1 of the present invention will be described with reference to FIGS. 1 to 9. FIG.

FIG. 6 is a diagram showing an example of DRB setting reception and setting in the embodiment of the present invention. The eNB 102, or the gNB 108, or both the eNB 102 and the gNB 108, determines the DRB settings to request from the UE 122 (S600). The eNB 102, or the gNB 108, or both the eNB 102 and the gNB 108, set the DRB settings using information from the core network (EPC 104 or 5GC 110, or both EPC 104 and 5GC 110), or the Capability of the UE 122, or information from the core network and the information of the UE 122. You may decide based on your ability. Information from the core network may be determined based on the conditions of application services such as voice calls requested by the UE 122 . Next, eNB 102 or gNB 108 or both eNB 102 and gNB 108 generates an RRC connection reconfiguration request (RRCConnectionReconfiguration) message including DRB settings and sends it to UE 122 (S602). The receiving unit 500 of the UE 122 receives the RRC connection reconfiguration request message including the DRB settings and passes the DRB settings to the setting unit 502 .

7 and 8 show ASN. 1 (Abstract Syntax Notation One). In 3GPP, RRC-related specifications (Non-Patent Document 4, Non-Patent Document 10) specify messages and information (Information Element: IE) related to RRC as ASN. 1 is used for description. 7 and 8 are one figure. That is, FIG. 7 shows ASN. 1, and FIG. 8 shows ASN.1 related to DRB setting. 1 is the second sheet of the diagram showing an example. 7 and 8 ASN. 1, <omitted> and <omitted> are ASN. It is not part of the notation of 1, and indicates that other information has been omitted. Information may be omitted even where there is no description of <omitted> or <omitted>.

In FIG. 8 of FIGS. 7 and 8, DRB-ToAddMod included in the RRCConnectionReconfiguration message is an IE for DRB settings. As shown in FIG. 7 and FIG. 8 of FIG. 8, DRB-ToAddMod may include DRB-Identity, which is the IE of the DRB identifier, and PDCP-Config, which is PDCP entity configuration information corresponding to the DRB identifier. . Further, as shown in FIG. 8 of FIGS. 7 and 8, PDCP-Config, which is PDCP entity configuration information, is PDCP-EUTRA-Config, which is PDCP entity configuration information for E-UTRA, or PDCP entity configuration for NR. The information PDCP-NR-Config may be included by CHOICE. Also, as shown in FIG. 8 of FIGS. 7 and 8, PDCP-EUTRA-Config and PDCP-NR-Config include pdcp-SN- indicating the length of the PDCP sequence number (Sequence Number: SN). Size information may be included, and this pdcp-SN-Size may be an integer including seven.

16, 17 and 18 show ASN. 1 (Abstract Syntax Notation One). 16, 17 and 18 are one diagram. That is, FIG. 16 shows ASN. 1, and FIG. 17 shows ASN.1 related to DRB setting. 1, and FIG. 18 shows ASN.1 related to DRB setting. It is the third sheet in the figure showing another example of 1. 16, 17 and 18 ASN. 1, <omitted> and <omitted> are ASN. It is not part of the notation of 1, and indicates that other information has been omitted. Information may be omitted even where there is no description of <omitted> or <omitted>.

In FIG. 16 of FIGS. 16, 17, and 18, the RRCConnectionReconfiguration message is the RRCConnectionReconfiguration-EUTRA-IE, which is the IE for the RRC connection reconfiguration request for E-UTRA, or the IE for the RRC connection reconfiguration request for NR. A certain RRCConnectionReconfiguration-NR-IE may be included by CHOICE.

As shown in FIGS. 16 and 17 of FIGS. 16, 17, and 18, when the E-UTRA RRC connection reconfiguration request IE is selected, the E-UTRA DRB configuration IE, DRB -ToAddMod-EUTRA. Further, as shown in FIG. 17 of FIGS. 16, 17, and 18, DRB-ToAddMod-EUTRA includes DRB-Identity, which is the IE of the DRB identifier, and PDCP for E-UTRA corresponding to the DRB identifier. It may include PDCP-Config-EUTRA, which is entity configuration information. Further, as shown in FIGS. 17 and 18 of FIGS. 16, 17, and 18, PDCP-Config-EUTRA, which is PDCP entity configuration information for EUTRA, further includes E- PDCP-EUTRA-Config, which is PDCP entity configuration information for UTRA, or PDCP-NR-Config, which is PDCP entity configuration information for NR, may be included by CHOICE. Also, as shown in FIG. 18 of FIGS. 16, 17, and 18, PDCP-EUTRA-Config and PDCP-NR-Config include PDCP sequence number (Sequence Number: pdcp indicating the length of SN) -SN-Size information, and this pdcp-SN-Size may be an integer including seven.

Also, as shown in FIGS. 16 and 17 of FIGS. 16, 17, and 18, when the RRC connection reset request IE for NR is selected, DRB-ToAddMod-NR, which is the DRB setting IE for NR, is selected. may contain Further, as shown in FIG. 17 of FIGS. 16, 17, and 18, DRB-ToAddMod-NR includes DRB-Identity, which is the IE of the DRB identifier, and PDCP entity configuration information for NR corresponding to the DRB identifier PDCP-Config-NR may be included. Further, as shown in FIGS. 17 and 18 of FIGS. 16, 17, and 18, PDCP-Config-NR, which is PDCP entity configuration information for NR, is further used as PDCP entity configuration for NR, and for E-UTRA PDCP-EUTRA-Config, which is PDCP entity configuration information, or PDCP-NR-Config, which is PDCP entity configuration information for NR, may be included by CHOICE. Also, as shown in FIG. 18 of FIGS. 16, 17, and 18, PDCP-EUTRA-Config and PDCP-NR-Config include PDCP sequence number (Sequence Number: pdcp indicating the length of SN) -SN-Size information, and this pdcp-SN-Size may be an integer including seven.

7, 8, 16, 17 and 18, ASN. The message name, IE name, parameter name, etc. of 1 are examples, and other names may be used. 7, 8, 16, 17, and 18, in the same manner as described the PDCP entity for E-UTRA and the PDCP entity for NR, the RLC entity for E-UTRA, and the RLC entity for NR may be described. 7, 8, 16, 17, and 18, the E-UTRA MAC entity (MACMainConfig (not shown), logicalChannelConfig, etc.) and the MAC entity for NR may be described.

In S604 of FIG. 6, the DRB setting passed from the receiving unit 500 of the UE 122 to the setting unit 502 of the UE 122 includes at least a DRB identifier and a PDCP entity setting for E-UTRA as a PDCP entity setting corresponding to the DRB identifier, or a PDCP entity setting for NR. Any of the PDCP entity settings are included. The configuration unit 502 of the UE 122 establishes or re-establishes the PDCP entity according to the DRB identifier and the PDCP entity configuration corresponding to the DRB identifier.

FIG. 9 is an example of PDCP setting determination in the setting unit of the terminal device according to the embodiment of the present invention. The configuration unit 502 of the UE 122 checks whether the DRB identifier value exists in the current configuration of the terminal device (S900). If not, check whether the PDCP entity setting information corresponding to this DRB identifier includes E-UTRA PDCP entity setting information (S902), and if it is included, according to the E-UTRA PDCP entity setting information, A PDCP entity for E-UTRA is established (S904). On the other hand, if the E-UTRA PDCP entity setting information is not included in the PDCP entity setting corresponding to the DRB identifier, the PDCP entity setting information for NR is further included in the PDCP entity setting corresponding to the DRB identifier. (S906), and if it is included, the PDCP entity for NR is established according to the PDCP entity setting information for NR (S908). Further, when the PDCP entity setting information for NR is not included in the PDCP entity setting corresponding to the DRB identifier, other setting is performed (S918).

On the other hand, if the DRB identifier value exists in the current terminal device settings, it is checked whether PDCP entity setting information for E-UTRA is included in the PDCP entity setting corresponding to this DRB identifier (S910). , if included, re-establishes the E-UTRA PDCP entity according to the E-UTRA PDCP entity configuration information (S912). On the other hand, if the E-UTRA PDCP entity setting information is not included in the PDCP entity setting corresponding to the DRB identifier, the PDCP entity setting information for NR is further included in the PDCP entity setting corresponding to the DRB identifier. (S914), and if it is included, the PDCP entity for NR is re-established according to the PDCP entity setting information for NR (S916). Further, when the PDCP entity setting information for NR is not included in the PDCP entity setting corresponding to the DRB identifier, other setting is performed (S918). The re-establishment process may switch between the E-UTRA PDCP entity and the NR PDCP entity. For example, if the PDCP entity configuration corresponding to a certain DRB identifier (let it be DRB identifier 1) that exists in the current UE 122 configuration is the PDCP entity configuration for E-UTRA, included in the received RRC connection reconfiguration message If the DRB configuration includes the above-described DRB identifier 1 and the PDCP entity configuration corresponding to this DRB identifier 1 is the NR PDCP entity configuration, the PDCP entity corresponding to the DRB identifier 1 is reconfigured as the NR PDCP entity. do. Similarly, when the PDCP entity setting corresponding to a certain DRB identifier (assumed as DRB identifier 2) that exists in the current UE 122 setting is the PDCP entity setting for NR, the DRB included in the received RRC connection reconfiguration message If the setting includes the DRB identifier 2 described above and the PDCP entity setting corresponding to this DRB identifier 2 is the PDCP entity setting for E-UTRA, the PDCP entity corresponding to the DRB identifier 2 is set as the PDCP entity for E-UTRA Reset as In this way, the E-UTRA PDCP entity setting and the NR PDCP entity setting may be switched by the RRC connection reconfiguration message.

After completing the setting in the setting unit 502 of the UE 122, in FIG. 6, the UE 122 transmits an RRC connection reconfiguration complete (RRCConnectionReconfigurationComplete) message to the eNB 102 or gNB 108, or both the eNB 102 and gNB 108 (S606).

Note that the DRB setting in the present embodiment may be included not only in the RRC connection re-establishment procedure, but also in the RRC connection establishment procedure and the RRC connection re-establishment procedure. . In addition, the re-establishment of the PDCP entity in the present embodiment means, for example, zero reset of the hyper frame number (Hyper Frame Number: HFN) described in Non-Patent Document 5, initialization of header compression (Initialization and Refresh: IR) mode , changes to specified encryption algorithms and encryption keys, and the like. In addition, zero reset of hyper frame number (Hyper Frame Number: HFN) described in non-patent literature, change to initial (Initialization and Refresh: IR) mode of header compression, specified encryption algorithm (algorithm) and encryption The changes to the key are for E-UTRA, but may also be applied for NR.

Thus, in the present embodiment, based on the conditions of application services such as voice calls requested by the terminal device (UE), the E-UTRA base station device (eNB) or the NR base station device ( gNB), or eNB and gNB select whether the PDCP entity used in communication with the UE is for E-UTRA or for NR, and notify the UE using an RRC connection reconfiguration message. Therefore, it is possible to establish a PDCP entity suitable for the application service used by the UE, and to perform efficient communication with reduced complexity of protocol processing.

(Embodiment 2)
In Embodiment 2 of the present invention, cells of both E-UTRA and NR radio access technologies (Radio Access Technology: RAT), which are being studied as one of NR technologies, are grouped for each RAT and UE In MR-DC (Multi-RAT Dual Connectivity), which is a mechanism in which the UE and one or more base station devices communicate, especially the EPC as the core network, and the base station device on the E-UTRA side is described later. DRB settings in the case of EN-DC (E-UTRAN supports Multi-RAT Dual Connectivity (MR-DC) via E-UTRA-NR Dual Connectivity), which is the master base station device, will be described.

Embodiment 2 will be described with reference to FIGS. 1 and 5 to 12. FIG.

FIG. 10 is a diagram showing an example of the relationship between the EN-DC base station apparatus side radio protocol architecture and RBs according to the embodiment of the present invention.

EN-DC has EPC as a core network, E-UTRA base station equipment as a master base station (Master eNB: MeNB), and NR base station equipment as a secondary base station (Secondary gNB: SgNB). Cell groups each configured by the base station device, i.e., a master cell group configured by MeNB (Master Cell Group: MCG) and a secondary cell group configured by SgNB (Secondary Cell Group: SCG) Data using both radio resources It may be a technology for communication. In MR-DC, the master base station is the main RRC functions related to MR-DC, such as establishment, change and release of RB, and addition, change, release and handover of additional cells such as secondary cells, etc. A secondary base station may be a base station with some RRC functionality, such as SCG modification and release.

As shown in FIG. 10, EN-DC transmits and receives part of the data transmitted and received on the SgNB side, and transmits and receives the rest on the MeNB side. In the EN-DC data transmission and reception method, the node in the EPC becomes an anchor point that is a data branching/merging point, and each MeNB and SgNB is a logical path between the EPC and a bearer (bearer) is established to transmit and receive data, that is, a method of transmitting and receiving data using an MCG bearer on the MeNB side and an SCG bearer on the SgNB side, and MeNB or SeNB becomes an anchor point, and a radio bearer (Radio Bearer: RB ) is split between MeNB and SeNB, there may be a method of transmitting and receiving data using a split bearer. The split bearer is established during radio bearer establishment, and after establishing the MCG bearer or SCG bearer, the MCG bearer or SCG bearer is changed to the split bearer in the form of adding the SCG side or the radio bearer on the MCG side. There may be a method. Establishment of MCG bearer, SCG bearer, split bearer, change may be performed by RRC (Radio Resource Control) connection reconfiguration (Connection Reconfiguration) procedure to be transmitted between MeNB and UE. In the present embodiment, the cell group of the base station device that becomes the anchor point of the split bearer is called an anchor cell group, and the cell group of the base station device that does not become the anchor point of the split bearer is called an additional cell group. group). The anchor cell group may be the MCG and the additional cell group may be the SCG, or the anchor cell group may be the SCG and the additional cell group may be the MCG. A split bearer when the anchor cell group is MCG may be called an MCG split bearer, and a split bearer when the anchor cell group is SCG may be called an SCG split bearer.

In EN-DC, when data is transmitted and received using a split bearer, with regard to downlink data, the anchor cell group base station device distributes part of the downlink data transferred from the EPC to the additional cell group base station device, The remaining data may be transmitted from the base station equipment of the master cell group to the UE while the base station equipment of the additional cell group transmits to the UE. Regarding uplink data, the UE transmits part of the uplink data to the base station equipment of the additional cell group, and the base station equipment of the additional cell group distributes part of this uplink data to the base station equipment of the master cell group. , the UE may transmit the remaining data to the base station equipment of the master cell group.

As shown in FIG. 10, when split bearers are used, PDCP PDUs may be transmitted and received between the base station apparatus of the master cell group and the base station apparatus of the additional cell group.

FIG. 11 is a diagram showing an example of DRB setting reception and setting when establishing an MCG bearer or SCG bearer as a bearer of an anchor cell group in the embodiment of the present invention. Even if it is established as an anchor cell group, it does not have to be changed to a split bearer later. The eNB 102 determines the DRB settings to be requested from the UE 122 (S1100). The eNB 102 may determine DRB settings based on information from the core network (EPC 104), or the Capabilities of the UE 122, or information from the core network and the capabilities of the UE 122. Information from the core network may be determined based on the conditions of application services such as voice calls requested by the UE 122 . Next, the eNB 102 generates an RRC connection reconfiguration request (RRCConnectionReconfiguration) message including DRB settings and transmits it to the UE 122 (S1102). The receiving unit 500 of the UE 122 receives the RRC connection reconfiguration request message including the DRB settings and passes the DRB settings to the setting unit 502 .

7 and 8 show ASN. 1 (Abstract Syntax Notation One).

That is, in FIG. 8 of FIGS. 7 and 8, DRB-ToAddMod included in the RRCConnectionReconfiguration message is an IE for DRB settings. As shown in FIG. 7 and FIG. 8 of FIG. 8, DRB-ToAddMod may include DRB-Identity, which is the IE of the DRB identifier, and PDCP-Config, which is PDCP entity configuration information corresponding to the DRB identifier. . Further, as shown in FIG. 8 of FIGS. 7 and 8, PDCP-Config, which is PDCP entity configuration information, is PDCP-EUTRA-Config, which is PDCP entity configuration information for E-UTRA, or PDCP entity configuration for NR. The information PDCP-NR-Config may be included by CHOICE. Also, as shown in FIG. 8 of FIGS. 7 and 8, PDCP-EUTRA-Config and PDCP-NR-Config include pdcp-SN- indicating the length of the PDCP sequence number (Sequence Number: SN). Size information may be included, and this pdcp-SN-Size may be an integer including seven.

16, 17, and 18 show ASN. 1 (Abstract Syntax Notation One).

That is, in FIG. 16 of FIGS. 16, 17, and 18, the RRCConnectionReconfiguration message is the RRCConnectionReconfiguration-EUTRA-IE, which is the IE for the RRC connection reconfiguration request for E-UTRA, or the IE for the RRC connection reconfiguration request for NR. RRCConnectionReconfiguration-NR-IE may be included by CHOICE.

As shown in FIGS. 16 and 17 of FIGS. 16, 17, and 18, when the E-UTRA RRC connection reconfiguration request IE is selected, the E-UTRA DRB configuration IE, DRB -ToAddMod-EUTRA. Further, as shown in FIG. 17 of FIGS. 16, 17, and 18, DRB-ToAddMod-EUTRA includes DRB-Identity, which is the IE of the DRB identifier, and PDCP for E-UTRA corresponding to the DRB identifier. It may include PDCP-Config-EUTRA, which is entity configuration information. Further, as shown in FIGS. 17 and 18 of FIGS. 16, 17, and 18, PDCP-Config-EUTRA, which is PDCP entity configuration information for EUTRA, further includes E- PDCP-EUTRA-Config, which is PDCP entity configuration information for UTRA, or PDCP-NR-Config, which is PDCP entity configuration information for NR, may be included by CHOICE. Also, as shown in FIG. 18 of FIGS. 16, 17, and 18, PDCP-EUTRA-Config and PDCP-NR-Config include PDCP sequence number (Sequence Number: pdcp indicating the length of SN) -SN-Size information, and this pdcp-SN-Size may be an integer including seven.

Also, as shown in FIGS. 16 and 17 of FIGS. 16, 17, and 18, when the RRC connection reconfiguration request IE for NR is selected, the DRB-ToAddMod- NR may be included. Further, as shown in FIG. 17 of FIGS. 16, 17, and 18, DRB-ToAddMod-NR includes DRB-Identity, which is the IE of the DRB identifier, and PDCP entity configuration information for NR corresponding to the DRB identifier PDCP-Config-NR may be included. Further, as shown in FIGS. 17 and 18 of FIGS. 16, 17, and 18, PDCP-Config-NR, which is PDCP entity configuration information for NR, is further used as PDCP entity configuration for NR, and for E-UTRA PDCP-EUTRA-Config, which is PDCP entity configuration information, or PDCP-NR-Config, which is PDCP entity configuration information for NR, may be included by CHOICE. Also, as shown in FIG. 18 of FIGS. 16, 17, and 18, PDCP-EUTRA-Config and PDCP-NR-Config include PDCP sequence number (Sequence Number: pdcp indicating the length of SN) -SN-Size information, and this pdcp-SN-Size may be an integer including seven.

As described in Embodiment 1, ASN. The message name, IE name, parameter name, etc. of 1 are examples, and other names may be used. 7, 8, 16, 17, and 18, in the same manner as described the PDCP entity for E-UTRA and the PDCP entity for NR, the RLC entity for E-UTRA, and the RLC entity for NR may be described. 7, 8, 16, 17, and 18, the E-UTRA MAC entity ( MACMainConfig (not shown), logicalChannelConfig, etc.) and MAC entity for NR may be described.

In S1104 of FIG. 11, the DRB setting passed from the receiving unit 500 of the UE 122 to the setting unit 502 of the UE 122 includes at least a DRB identifier and a PDCP entity setting for E-UTRA as a PDCP entity setting corresponding to the DRB identifier, or a PDCP entity setting for NR. Any of the PDCP entity settings are included. The configuration unit 502 of the UE 122 establishes or re-establishes the PDCP entity according to the DRB identifier and the PDCP entity configuration corresponding to the DRB identifier.

FIG. 9 is an example of PDCP setting determination in the setting unit of the terminal device, as described in the first embodiment. That is, the configuration unit 502 of the UE 122 checks whether or not the DRB identifier value exists in the current configuration of the terminal device (S900). If not, check whether the PDCP entity setting information corresponding to this DRB identifier includes E-UTRA PDCP entity setting information (S902), and if it is included, according to the E-UTRA PDCP entity setting information, A PDCP entity for E-UTRA is established (S904). On the other hand, if the E-UTRA PDCP entity setting information is not included in the PDCP entity setting corresponding to the DRB identifier, the PDCP entity setting information for NR is further included in the PDCP entity setting corresponding to the DRB identifier. (S906), and if it is included, the PDCP entity for NR is established according to the PDCP entity setting information for NR (S908). Further, when the PDCP entity setting information for NR is not included in the PDCP entity setting corresponding to the DRB identifier, other setting is performed (S918).

On the other hand, if the DRB identifier value exists in the current terminal device settings, it is checked whether PDCP entity setting information for E-UTRA is included in the PDCP entity setting corresponding to this DRB identifier (S910). , if included, re-establishes the E-UTRA PDCP entity according to the E-UTRA PDCP entity configuration information (S912). On the other hand, if the E-UTRA PDCP entity setting information is not included in the PDCP entity setting corresponding to the DRB identifier, the PDCP entity setting information for NR is further included in the PDCP entity setting corresponding to the DRB identifier. (S914), and if it is included, the PDCP entity for NR is re-established according to the PDCP entity setting information for NR (S916). Further, when the PDCP entity setting information for NR is not included in the PDCP entity setting corresponding to the DRB identifier, other setting is performed (S918). The re-establishment process may switch between the E-UTRA PDCP entity and the NR PDCP entity. For example, when the PDCP entity configuration corresponding to a certain DRB identifier (assumed as DRB identifier 1) that exists in the current UE 122 configuration is the PDCP entity for E-UTRA, the DRB included in the received RRC connection reconfiguration message If the setting includes the DRB identifier 1 described above and the PDCP entity setting corresponding to this DRB identifier 1 is the PDCP entity setting for NR, the PDCP entity setting corresponding to the DRB identifier 1 is reconfigured as the PDCP entity for NR. do. Similarly, when the PDCP entity setting corresponding to a certain DRB identifier (assumed as DRB identifier 2) that exists in the current UE 122 setting is the PDCP entity for NR, the DRB setting included in the received RRC connection reconfiguration message contains the above-mentioned DRB identifier 2, and if the PDCP entity setting corresponding to this DRB identifier 2 is the PDCP entity setting for E-UTRA, the PDCP entity setting corresponding to the DRB identifier 2 is set to the PDCP entity for E-UTRA Reset as In this way, the E-UTRA PDCP entity setting and the NR PDCP entity setting may be switched by the RRC connection reconfiguration message.

After completing the setting in the setting unit 502 of the UE 122, the UE 122 transmits an RRC connection reconfiguration complete (RRCConnectionReconfigurationComplete) message to the eNB 102 in FIG. 11 (S1106).

Note that the DRB setting in the present embodiment may be included not only in the RRC connection re-establishment procedure, but also in the RRC connection establishment procedure and the RRC connection re-establishment procedure. . In addition, the re-establishment of the PDCP entity in the present embodiment means, for example, zero reset of the hyper frame number (Hyper Frame Number: HFN) described in Non-Patent Document 5, initialization of header compression (Initialization and Refresh: IR) mode , changes to specified encryption algorithms and encryption keys, and the like. In addition, zero reset of hyper frame number (Hyper Frame Number: HFN) described in non-patent literature, change to initial (Initialization and Refresh: IR) mode of header compression, specified encryption algorithm (algorithm) and encryption The changes to the key are for E-UTRA, but may also be applied for NR.

Next, the change from the MCG bearer or SCG bearer to the split bearer will be explained.

FIG. 12 shows the ASN. related to the DRB setting of the additional cell group when changing from the MCG bearer or SCG bearer to the split bearer. 1 (Abstract Syntax Notation One). ASN. 1, <omitted> and <omitted> are ASN. It is not part of the notation of 1, and indicates that other information has been omitted. Information may be omitted even where there is no description of <omitted> or <omitted>. ASN. 1 examples are the ANS. It may be part of one example. The DRB-ToAddModADDCG-NR IE shown in FIG. 12 relates to the DRB configuration of the additional cell group and may be called another name. Also, the DRB-ToAddModADDCG-NR IE shown in FIG. 12 may be part of the upper IE regarding additional cell group configuration.

In FIG. 11, the eNB 102 determines the DRB setting of the anchor cell group and the DRB setting of the additional cell group to be requested from the UE 122 (S1100). However, it is not necessary to change the DRB setting of the anchor cell group. When changing the DRB configuration of the anchor cell group, the DRB configuration of the anchor cell group may include the DRB identifier and the corresponding entity configuration information such as PDCP entity configuration to be changed. Also, when the DRB setting of the anchor cell group is not changed, only the DRB identifier may be provided in the DRB setting of the anchor cell group. The eNB 102 may decide whether to change the DRB setting of the anchor cell group based on information from the core network (EPC 104), the capability of the UE 122, or information from the core network and the capability of the UE 122. good. Information from the core network may be determined based on the conditions of application services such as voice calls requested by the UE 122 . Next, the eNB 102 generates an RRC connection reconfiguration request (RRCConnectionReconfiguration) message including the DRB setting of the anchor cell and the DRB setting of the additional cell, and transmits it to the UE 122 (S1102). The receiving unit 500 of the UE 122 receives the RRC connection reconfiguration request message including the DRB configuration of the anchor cell and the DRB configuration of the additional cell, and passes the DRB configuration of the anchor cell and the DRB configuration of the additional cell to the configuration unit 502 .

In configuration section 502 of UE 122, if the value of the DRB identifier included in the DRB configuration of the anchor cell group exists in the current configuration of UE 122, and the DRB identifier included in the DRB configuration of the anchor cell group is If the DRB identifier is included in the DRB configuration, that is, if the value of the DRB identifier of the anchor cell group and the value of the DRB identifier of the additional cell group are the same, and the DRB type of the additional cell group (drb-Type -NR, etc.) is a split, determine to change the existing MCG bearer or SCG bearer to a split bearer. Note that the method of determining whether to change an existing MCG bearer or SCG bearer to a split bearer is not limited to this, and another method may be used.

Configuration section 502 of UE 122 establishes the DRB of the additional cell group according to the DRB configuration of the additional cell group, and if there is a PDCP entity configuration corresponding to the DRB identifier in the DRB configuration of the anchor cell group, the PDCP entity configuration The PDCP entity may be re-established according to. The re-establishment process may switch between the E-UTRA PDCP entity and the NR PDCP entity. For example, when the PDCP entity configuration corresponding to a certain DRB identifier (assumed as DRB identifier 1) that exists in the current UE 122 configuration is the PDCP entity for E-UTRA, the DRB included in the received RRC connection reconfiguration message If the configuration includes the DRB identifier 1 described above and the PDCP entity configuration corresponding to this DRB identifier 1 is the PDCP entity configuration for NR, the PDCP entity corresponding to DRB identifier 1 is reconfigured as the PDCP entity for NR. . Similarly, when the PDCP entity setting corresponding to a certain DRB identifier (assumed as DRB identifier 2) that exists in the current UE 122 setting is the PDCP entity for NR, the DRB setting included in the received RRC connection reconfiguration message contains the above-mentioned DRB identifier 2, and if the PDCP entity setting corresponding to this DRB identifier 2 is the PDCP entity setting for E-UTRA, the PDCP entity corresponding to the DRB identifier 2 as a PDCP entity for E-UTRA Reset. In this way, the E-UTRA PDCP entity setting and the NR PDCP entity setting may be switched by the RRC connection reconfiguration message.

Thus, in the present embodiment, even in the case of EN-DC, the anchor cell group can communicate with the UE based on the conditions of application services such as voice calls requested by the terminal device (UE). The PDCP entity used in selects whether it is for E-UTRA or for NR, and notifies the UE using an RRC connection reconfiguration message. Therefore, even the EN-DC can establish a PDCP entity suitable for the application service used by the UE, and can perform efficient communication with reduced complexity of protocol processing.

(Embodiment 3)
Embodiment 3 of the present invention describes DRB configuration including SDAP entity configuration when the core network is 5GC110. In Embodiment 3, the UE 122 may communicate with 5GC 110 via gNB, may communicate with 5GC via eNB, and may communicate with 5GC using MR-DC that performs both gNB and eNB. You can communicate.

Embodiment 3 will be described with reference to FIGS. 1, 5, 7 and 8, 13 to 15, 16, 17 and 18. FIG.

FIG. 13 is a diagram showing an example of DRB setting reception and setting in the embodiment of the present invention. The eNB 102, or the gNB 108, or both the eNB 102 and the gNB 108 determine the DRB configuration including the SDAP entity configuration to request from the UE 122 (S1300). The eNB 102, or the gNB 108, or both the eNB 102 and the gNB 108, set the DRB settings using information from the core network (EPC 104 or 5GC 110, or both EPC 104 and 5GC 110), or the Capability of the UE 122, or information from the core network and the information of the UE 122. You may decide based on your ability. Information from the core network may be determined based on the conditions of application services such as voice calls requested by the UE 122 . The DRB configuration may also include information about SDAP, such as SDAP header length. Information about SDAP may be included in SDAP entity settings, or may be included in other entity settings such as PDCP entity settings. Next, eNB 102 or gNB 108 or both eNB 102 and gNB 108 generates an RRC connection reconfiguration request (RRCConnectionReconfiguration) message including DRB configuration and sends it to UE 122 (S1302). The receiving unit 500 of the UE 122 receives the RRC connection reconfiguration request message including the DRB settings and passes the DRB settings to the setting unit 502 .

14 and 15 show ASN. 1 (Abstract Syntax Notation One). 14 and 15 ASN. 1, <omitted> and <omitted> are ASN. It is not part of the notation of 1, and indicates that other information has been omitted. Information may be omitted even where there is no description of <omitted> or <omitted>.

FIG. 14 is an example in which SDCP header length information is included in SDCP entity settings, and FIG. 15 is an example in which SDCP header lengths are included in other PDCP entity settings. The SDCP header length information may be information included in either the SDCP entity setting or the PDCP entity setting, or may be information included in both the SDCP entity setting and the PDCP entity setting. The SDAP header length may be a multiple of 8 including zero (zero:0). For example, in the examples of FIGS. 14 and 15, "len0bits", "len8bits", "len16bits", and "len24bits" may be 0 bits, 8 bits, 12 bits, and 24 bits, respectively. Also, instead of this, the notation in units of bytes or octets such as "len0bytes", "len1bytes", "len2bytes", and "len3bytes" may be used. Note that the SDAP header length of zero may mean that there is no SDAP header. Also, the notation and name of the SDAP header length are not limited to this, and another notation and name may be used. 14 and 15 ASN. The message name, IE name, parameter name, etc. of 1 are examples, and other names may be used. Also, the ASN. 1 is the ASN.1 shown in FIGS. 7 and 8, or FIGS. It may be part of one example.

The configuration unit 502 of the UE 122 will be described using the example of FIG. 14, ie, the case where the SDAP entity configuration includes the SDAP header length. In S1304 of FIG. 13, the DRB setting passed from the receiving unit 500 of the UE 122 to the setting unit 502 of the UE 122 includes at least the DRB identifier and the SDAP entity setting corresponding to the DRB identifier. is included. The configuration unit 502 of the UE 122 establishes or re-establishes the SDAP entity according to the DRB identifier and SDAP entity configuration corresponding to the DRB identifier. That is, if the DRB identifier value passed from the receiving unit 500 does not exist in the settings of the current terminal device, the SDAP entity is established, and the DRB identifier value passed from the receiving unit 500 is set to the current terminal device. The SDAP entity may be re-established if present in the configuration. When the SDAP header length is zero, the SDAP entity is established, but the processing may be such that the SDAP header does not exist, or the processing may be such that the SDAP entity is not established.

The configuration unit 502 of the UE 122 will be described using the example of FIG. 15, ie, the case where the SDAP header length is included in the PDCP entity configuration. In S1304 of FIG. 13, the DRB setting passed from the receiving unit 500 of the UE 122 to the setting unit 502 of the UE 122 includes at least the DRB identifier and the PDCP entity setting corresponding to the DRB identifier. is included. The configuration unit 502 of the UE 122 establishes or re-establishes the PDCP entity according to the DRB identifier and the PDCP entity configuration corresponding to the DRB identifier. That is, if the DRB identifier value passed from the receiving unit 500 does not exist in the settings of the current terminal device, the PDCP entity is established, and the DRB identifier value passed from the receiving unit 500 is the current terminal device. The PDCP entity may be re-established if present in the configuration. The established or re-established PDCP entity may identify the starting position of the SDAP SDU, ie the IP packet, from the SDAP header length information and perform header compression processing. Even if the SDAP header length is not included in the PDCP entity setting and is included in the SDAP entity setting, the PDCP entity can determine the starting position of the SDAP SDU, that is, the IP packet from the information of the SDAP header length included in the SDAP entity setting. may be specified and header compression processing may be performed.

After completing the setting in the setting unit 502 of the UE 122, the UE 122 in FIG. 13 transmits an RRC connection reconfiguration complete (RRCConnectionReconfigurationComplete) message to the eNB 102 or gNB 108, or both the eNB 102 and gNB 108 (S1306).

Note that the DRB setting in the present embodiment may be included not only in the RRC connection re-establishment procedure, but also in the RRC connection establishment procedure and the RRC connection re-establishment procedure. . In addition, the re-establishment of the PDCP entity in the present embodiment means, for example, zero reset of the hyper frame number (Hyper Frame Number: HFN) described in Non-Patent Document 5, initialization of header compression (Initialization and Refresh: IR) mode , changes to specified encryption algorithms and encryption keys, and the like. It should be noted that the zero reset of the hyper frame number (Hyper Frame Number: HFN) described in non-patent literature and the initialization of header compression
and Refresh (IR) mode, and changes to specified cryptographic algorithms and cryptographic keys are for E-UTRA, but may also be applied for NR.

Also, the DRB setting in the present embodiment assumes a case where the core network is 5GC, but it may also be applied when the core network is EPC.

Thus, in the present embodiment, based on the conditions of application services such as voice calls requested by the terminal device (UE), the E-UTRA base station device (eNB) or the NR base station device ( gNB), or eNB and gNB perform SDAP entity setting including SDAP header length, or PDCP entity setting including SDAP header length to be used in communication with UE, and use RRC connection reconfiguration message to UE Notice. Therefore, it is possible to use the SDAP header length suitable for the application service used by the UE, and perform header compression by the PDCP entity as necessary, thereby reducing the complexity of protocol processing and performing efficient communication. can.

It should be noted that the description about RRC in each embodiment of the present invention, messages such as RRC connection reconfiguration request message, and ASN. 1, etc., assumes RRC for NR (for example, RRC described in Non-Patent Document 9 and Non-Patent Document 10), but may be for LTE extension, E-UTRA base station apparatus and It may be transmitted/received to/from a terminal device compatible with MR-DC.

Also, the re-establishment of each entity such as the PDCP entity in each embodiment of the present invention may be performed by the RRC connection re-establishment procedure at the time of handover. Also, when re-establishing each entity such as the PDCP entity in each embodiment of the present invention, security-related settings may also be re-configured.

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

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

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

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

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

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

As described above, a terminal device that communicates with a base station device includes a receiving unit that receives an RRC connection reset request message including a DRB (Data Radio Bearer) setting from the base station device, and a DRB setting according to the DRB setting. and the DRB configuration includes a DRB identifier and a PDCP entity configuration corresponding to the DRB identifier, the value of the DRB identifier does not exist in the current terminal device configuration, and the When the PDCP entity configuration information includes one of the PDCP entity configuration for E-UTRA and the PDCP entity configuration for NR, and the PDCP entity configuration information includes the information on the PDCP entity configuration for E-UTRA , a PDCP entity is established according to the PDCP entity configuration information, and if the PDCP entity configuration information includes the PDCP entity configuration information for NR, a PDCP entity is established according to the PDCP entity configuration information.

Further, one aspect of the present invention is a terminal device that communicates with a base station device, and includes a receiving unit that receives an RRC connection reset request message including a DRB (Data Radio Bearer) setting from the base station device, and the DRB setting. a setting unit that sets a DRB according to, the DRB setting includes a DRB identifier and a PDCP entity setting corresponding to the DRB identifier, and the value of the DRB identifier is present in the current terminal device setting. , the PDCP entity configuration information includes one of PDCP entity configuration for E-UTRA and PDCP entity configuration for NR, and the PDCP entity configuration information includes information on the PDCP entity configuration for E-UTRA If yes, the PDCP entity is re-established according to the PDCP entity configuration information, and if the PDCP entity configuration information includes the PDCP entity configuration information for NR, the PDCP entity is established according to the PDCP entity configuration information.

Further, one aspect of the present invention provides E-UTRA (Evolved Universal Terrestrial Radio Access) and MR-DC (Multi Radio Access Technology Dual to NR (New Radio)
Connectivity), and when the E-UTRA becomes the master cell group, receives an RRC connection reconfiguration request message including DRB (Data Radio Bearer) settings of the anchor cell group from the master base station device and a setting unit for setting the DRB according to the DRB setting, wherein the DRB setting includes a DRB identifier and a PDCP entity setting corresponding to the DRB identifier, and the value of the DRB identifier is currently , the PDCP entity setting information includes one of PDCP entity setting for E-UTRA and PDCP entity setting for NR, and the PDCP entity setting information includes the E - if the PDCP entity configuration information for UTRA is included, establish a PDCP entity according to the PDCP entity configuration information; if the PDCP entity configuration information includes the PDCP entity configuration information for NR, the PDCP entity configuration information; Establish a PDCP entity according to

Further, one aspect of the present invention is a terminal device compatible with MR-DC (Multi Radio Access Technology Dual Connectivity) to E-UTRA (Evolved Universal Terrestrial Radio Access) and NR (New Radio), When UTRA becomes a master cell group, a receiving unit that receives an RRC connection reconfiguration request message including DRB (Data Radio Bearer) settings of an anchor cell group from a master base station device, and performs DRB settings according to the DRB settings. A setting unit, wherein the DRB setting includes a DRB identifier and a PDCP entity setting corresponding to the DRB identifier, the value of the DRB identifier is present in the current terminal device setting, and is included in the PDCP entity setting information includes one of the PDCP entity setting for E-UTRA and the PDCP entity setting for NR, and if the PDCP entity setting information includes the information of the PDCP entity setting for E-UTRA, the PDCP entity setting A PDCP entity is re-established according to the information, and if the PDCP entity configuration information includes the PDCP entity configuration information for NR, the PDCP entity is re-established according to the PDCP entity configuration information.

Further, one aspect of the present invention provides E-UTRA (Evolved Universal Terrestrial Radio Access) and MR-DC (Multi Radio Access Technology Dual to NR (New Radio)
Connectivity), and when the E-UTRA becomes the master cell group, the DRB (Data Radio Bearer) setting of the anchor cell group from the master base station device and the DRB setting of the additional cell group are included. a receiving unit for receiving an RRC connection reconfiguration request message; and a setting unit for setting the DRB according to the DRB setting, wherein the DRB setting of the anchor cell group includes a DRB identifier of the anchor cell group and the anchor cell group. and the DRB configuration of the additional cell group includes the DRB identifier of the anchor cell group and information that the DRB type is split, corresponding to the DRB identifier of the anchor cell group. re-establish the PDCP entity of the anchor cell group according to the PDCP entity configuration information contained in the DRB configuration of the anchor cell group.

Further, one aspect of the present invention is a terminal device that communicates with a base station device, and includes a receiving unit that receives an RRC connection reset request message including a DRB (Data Radio Bearer) setting from the base station device, and the DRB setting. a setting unit for setting a DRB according to, the DRB setting includes a DRB identifier and an SDAP entity setting corresponding to the DRB identifier, and the value of the DRB identifier is present in the current terminal device setting No, the SDAP entity configuration includes an SDAP header length, wherein the SDAP header length is one or more of integer multiples of 8 including zero, and establishes an SDAP entity according to the SDAP configuration information.

Further, one aspect of the present invention is a terminal device that communicates with a base station device, and includes a receiving unit that receives an RRC connection reset request message including a DRB (Data Radio Bearer) setting from the base station device, and the DRB setting. a setting unit for setting a DRB according to, the DRB setting includes a DRB identifier and an SDAP entity setting corresponding to the DRB identifier, and the value of the DRB identifier is present in the current terminal device setting. , the SDAP entity configuration includes an SDAP header length, the SDAP header length is one or more of integer multiples of 8 including zero, and reestablishing the SDAP entity according to the SDAP configuration information.

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

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

Claims (2)

A base station device that supports EN-DC,
A communication unit that transmits an RRC connection reset message including DRB setting to the terminal device,
The DRB setting is a setting used in the process of establishing the MCG bearer of the EN-DC,
the DRB configuration includes a DRB identifier and a PDCP entity configuration associated with the DRB identifier;
The PDCP entity setting is a PDCP entity setting for NR. Base station apparatus. A method performed by a base station device supporting EN-DC, comprising:
The method includes sending an RRC connection reconfiguration message including a DRB configuration to the terminal device;
The DRB setting is a setting used in the process of establishing the MCG bearer of the EN-DC,
the DRB configuration includes a DRB identifier and a PDCP entity configuration associated with the DRB identifier;
The method, wherein the PDCP entity configuration is a PDCP entity configuration for NR.

Images