JP2022106949A - Terminal device, base station device, communication method, and integrated circuit - Google Patents

Abstract

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

SOLUTION: A base station device that communicates with a terminal device transmits an RRC connection resetting request message containing a DRB (Data Radio Bearer) setting to the terminal device. The DRB setting is a setting used in processing to establish an MCG bearer of EN-DC, and includes a DRB identifier and a PDCP entity setting corresponding to the DRB identifier. The PDCP entity setting is a PDCP entity setting for NR.

SELECTED DRAWING: Figure 6

COPYRIGHT: (C)2022,JPO&INPIT

Description

The present invention relates to terminal devices, base station devices, communication methods, and integrated circuits.

Wireless access method and wireless network for cellular mobile communication (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, in 3GPP, as a wireless access method and wireless network technology for the 5th generation cellular system, technical studies of LTE-Advanced Pro, which is an extended technology of LTE, and NR (New Radio technology), which is a new wireless access technology. And standards have been established (Non-Patent Document 1). In addition, 5GC (5 Generation Core Network), which is a core network for the 5th generation cellular system, is also being studied (Non-Patent Document 2).

3GPP RP-170855, "Work Item on New Radio (NR) Access Technology" 3GPP TS 23.501, "System Architecture for the 5G System; Stage 2" 3GPP TS 36.300, "Evolved Universal Radio Access (E-UTRA) and Evolved Universal Radio Access Network (E-UTRAN); O-UTRAN); 3GPP TS 36.331, "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Access Control (RRC); Protocol specialties" 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) prototype" 3GPP TS 36.321, "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specialization" 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 specialties" 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 Protocol (MAC) protocol specification" 3GPP TS 23.401 v14.3.0, "General Packet Radio Service (GPRS) enhancements for Evolved Universal Radio Access Network" (E-UTRAN) ac

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

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

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

In order to achieve the above object, one aspect of the present invention has taken the following measures. That is, one aspect of the present invention is a base station device that supports EN-DC, including a communication unit that transmits an RRC connection reset message including a DRB setting to the terminal device, and the DRB setting is the EN-. It is a setting used in the process of establishing the 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. Further, one aspect of the present invention is a method executed by a base station device that supports EN-DC, in which the RRC connection reset message including the DRB setting is transmitted to the terminal device and the DRB setting is performed. 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, and the PDCP entity setting is NR. PDCP entity settings for.

According to one aspect of the present invention, the terminal device and the base station device can reduce the complexity of protocol processing and efficiently perform communication.

The schematic diagram of the communication system which concerns on each embodiment of this invention. The protocol stack diagram of UP and CP of the terminal device and the base station device in E-UTRA in each embodiment of the present invention. The protocol stack diagram of UP and CP of the terminal device and the 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 reset procedure in each embodiment of this invention. The block diagram of the terminal apparatus (UE) in each embodiment of this invention. The figure which shows an example of DRB setting reception and setting in Embodiment 1 of this invention. ASN. The DRB setting according to each embodiment of the present invention. A part (first sheet) of the figure which shows an example of 1 (Abstract Synchronization Notation One). ASN. The DRB setting according to each embodiment of the present invention. Another part (second sheet) of the figure which shows an example of 1 (Abstract Synchronization Notation One). The figure which shows an example of PDCP setting determination in the setting part of the terminal apparatus in Embodiment 1 of this invention. The figure which shows the relationship between the radio protocol architecture (protocol architecture) of the base station apparatus side of EN-DC and RB in Embodiment 2 of this invention. The figure which shows an example of DRB setting reception and setting at the time of establishing an MCG bearer or an SCG bearer as a bearer of an anchor group in Embodiment 2 of this invention. In the second embodiment of the present invention, the ASN. The figure which shows an example of 1 (Abstract Synchronization Notation One). The figure which shows an example of DRB setting reception and setting in Embodiment 3 of this invention. The ASN. The figure which shows an example of 1 (Abstract Synchronization Notation One). The ASN. The figure which shows an example of 1 (Abstract Synchronization Notation One). ASN. The DRB setting according to each embodiment of the present invention. A part (first sheet) of the figure which shows an example of 1 (Abstract Synchronization Notation One). ASN. The DRB setting according to each embodiment of the present invention. Another part (second sheet) of the figure which shows an example of 1 (Abstract Synchronization Notation One). ASN. The DRB setting according to each embodiment of the present invention. Yet another part (third sheet) of the figure showing an example of 1 (Abstract Synchronization 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 technique included in LTE. LTE may be defined as a technique included in NR. In addition, LTE that can be connected to NR by dual connectivity may be distinguished from conventional LTE. This embodiment may be applied to NR, LTE and other RATs. In the following description, terms related to LTE and NR will be used, but they may be applied in other techniques using other terms.

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

E-UTRA100 is a wireless access technique described in Non-Patent Document 3 and the like, and is composed of a cell group (Cell Group: CG) composed of one or a plurality of frequency bands. The eNB (E-UTRAN Node B) 102 is a base station device of the E-UTRA. The EPC (Evolved Packet Core) 104 is a core network described in Non-Patent Document 14 and the like, and was designed as a core network for E-UTRA. The interface 112 is an interface between the eNB 102 and the EPC 104, and has a control plane (Control Plane: CP) through which control signals pass and a user plane (User Plane: UP) through which user data passes.

NR106 is a new wireless access technology currently under consideration in 3GPP, and consists of a cell group (Cell Group: CG) composed of one or more frequency bands. gNB (g Node B) 108 is a base station device of NR. 5GC110 is a new core network for NR currently under consideration in 3GPP, and is described in Non-Patent Document 2 and the like.

Interface 114 is an interface between eNB 102 and 5GC110, interface 116 is an interface between gNB108 and 5GC110, interface 118 is an interface between gNB108 and EPC104, interface 120 is an interface between eNB102 and gNB108, and interface 124 is an interface between EPC104 and 5GC110. The interface between. Interface 114, interface 116, interface 118, interface 120, interface 124 are interfaces that pass only CP or UP, or both CP and UP, the details of which are under discussion in 3GPP. Further, the interface 114, the interface 116, the interface 118, the interface 120, and the interface 124 may not exist depending on the communication system provided by the telecommunications carrier.

The 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 a terminal device and a base station device in E-UTRA in each embodiment of the present invention.

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

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

MAC202 maps various logical channels to various transport channels. The MAC 202 is connected to a higher-level RLC (Radio Link Control layer) 204, which will be described later, via a logical channel. The logical channel is roughly classified according to the type of information to be transmitted, and is divided into a control channel for transmitting control information and a traffic channel for transmitting user information. The MAC202 has a function of controlling PHY200 for performing intermittent transmission (DRX / DTX), a function of executing a random access (Random Access) procedure, a function of notifying transmission power information, a function of performing HARQ control, and the like. Has (Non-Patent Document 7).

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

The PDCP206 may have a header compression function that compresses unnecessary control information in order to efficiently transmit an IP packet (IP Packet) which is user data in a wireless section. The PDCP206 may also have a data encryption function (Non-Patent Document 5).

The data processed by MAC202, RLC204, and PDCP206 are referred to as MAC PDU (Protocol Data Unit), RLC PDU, and PDCP PDU, respectively. The data passed from the upper layer to MAC202, RLC204, and PDU206 are called MAC SDU (Service Data Unit), RLC SDU, and PDU SDU, respectively.

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

In addition to PHY200, MAC202, RLC204, and PDCP206, the CP protocol stack includes RRC (Radio Resource Control layer) 208. The RRC208 sets and resets a radio bearer (RB), and controls a logical channel, a transport channel, and a physical channel. The RB may be divided into a Signaling Radio Bearer (SRB) and a Data Radio Bearer (DRB), and the SRB is used as a route for transmitting an RRC message which is control information. You may. The DRB may be used as a route for transmitting user data. Each RB may be set between the eNB 102 and the RRC 208 of the UE 122 (Non-Patent Document 4).

The above-mentioned functional classifications of MAC202, RLC204, PDCP206, and RRC208 are examples, and some or all of the functions may not be implemented. Further, a 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 the terminal device and the base station device in NR in each embodiment of the present invention.

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

The PHY (Physical layer) 300 is a wireless physical layer of NR, and a transmission service may be provided to an upper layer by using a physical channel. The PHY 300 may be connected to a higher-level MAC (Medium Access Control layer) 302 described later by a transport channel (Transport Channel). Data may be moved between MAC 302 and PHY 300 via the transport channel. Data may be transmitted and received between the UE 122 and the PHY of the gNB 108 via the radio physical channel. In detail, unlike the wireless physical layer PHY200 of E-UTRA, it is under discussion at 3GPP.

The MAC 302 may map various logical channels to various transport channels. The MAC 302 may be connected to a higher-level RLC (Radio Link Control layer) 304, which will be described later, by a logical channel. The logical channel is roughly classified according to the type of information to be transmitted, and may be divided into a control channel for transmitting control information and a traffic channel for transmitting user information. The MAC 302 has a function of controlling the PHY 300 for intermittent transmission (DRX / DTX), a function of executing a random access (Random Access) procedure, a function of notifying transmission power information, a function of performing HARQ control, and the like. You may have it (Non-Patent Document 13). In detail, unlike MAC202 of E-UTRA, it is under discussion at 3GPP.

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

The PDCP306 may have a header compression function that compresses unnecessary control information in order to efficiently transmit an IP packet (IP Packet) which is user data in a wireless section. The PDCP306 may also have a data encryption function (Non-Patent Document 11). In detail, unlike PDCP206 of E-UTRA, it is under discussion at 3GPP.

The SDAP (Service Data Adapter) 310 may have a function of mapping the QoS of the data sent from the 5GC110 to the gNB108 and the QoS of the data sent from the gNB to the 5GC110 and the QoS of the RB. (Non-Patent Document 9). The SDAP 310 is E when the eNB 102 is directly connected to the 5GC 110, that is, when the eNB 102 is indirectly connected to the 5GC 110 via the interface 114, or when the eNB 102 is indirectly connected to the 5GC 110, that is, when the eNB 102 is connected to the 5GC via the interface 120 and the interface 116. -It may exist as an upper layer of PDCP206, which is a PDCP of UTRA. Details are under discussion at 3GPP.

The data processed by MAC 302, RLC 304, PDCP 306, and SDA P 310 may be referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Further, the data passed from the upper layer to MAC202, RLC204, and PDCP206 may be referred to as MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively.

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

In addition to PHY300, MAC302, RLC304, and PDCP306, the CP protocol stack includes RRC (Radio Resource Control layer) 308. The RRC308 may set / reset the radio bearer (RB) and control the logical channel, the transport channel, and the physical channel. The RB may be divided into a Signaling Radio Bearer (SRB) and a Data Radio Bearer (DRB), and the SRB is used as a route for transmitting an RRC message which is control information. You may. The DRB may be used as a route for transmitting user data. Each RB may be set between the gNB 108 and the RRC 208 of the UE 122 (Non-Patent Document 10).

The above-mentioned functional classifications of MAC302, RLC304, PDCP306, SDAP310, and RRC208 are examples, and some or all of the functions may not be implemented. Further, a 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, MAC202, RLC204, PDCP206, and RRC208 are used as MAC for E-UTRA, RLC for E-UTRA, and E-, respectively. It may also be called PDCP for UTRA and RRC for E-UTRA. Further, MAC302, RLC304, PDCP306, and RRC308 may be referred to as NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.

Further, as shown in FIG. 1, the eNB 102, gNB 108, EPC 104, and 5GC 110 may be connected via the interface 112, the interface 116, the interface 118, the interface 120, and the interface 114. Therefore, the RRC208 in FIG. 2 may be replaced with the RRC308 in FIG. 3 in order to support various communication systems. Further, the PDCP206 of FIG. 2 may be replaced with the PDCP306 of FIG. Further, the RRC308 of FIG. 3 may include the function of the RRC208 of FIG. Further, the PDCP306 of FIG. 3 may be the PDCP206 of FIG.

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

The RRC connection reconfiguration procedure is described in Non-Patent Document 4 for establishing, changing, and releasing the RB in the E-UTRA, changing, releasing, and the like of the secondary cell, as well as handover and measurement (handover and measurement). Although it is a procedure used for (Measurement) etc., it may be used for establishing, changing and releasing RB in NR, and adding, changing, releasing, handover and measurement (Measurement) of secondary cells and the like. It may be described in Non-Patent Document 10. In each embodiment of the present invention, the procedure used for establishing, changing, and releasing RB in NR, and adding, changing, releasing, handover, measurement, etc. of a cell group is a procedure for resetting an RRC connection. However, it may have a different name. The RRC connection resetting procedure in each embodiment of the present invention is an RRC connection resetting procedure including establishment, change, and release of RB in NR, and addition, change, release, handover, measurement, and the like of a cell group. There may be.

As shown in FIG. 4, both the eNB 102 or the gNB 108, or both the eNB 102 and the gNB 108 transmit an RRC connection resetting request message (RRCCconnectionReconnection message) to the UE 122 when the need for the RRC connection resetting arises (S400). The UE 122 that has received the RRC connection reset request message makes settings according to the information (Information Element: IE) included in the RRC connection reset request message, and notifies that the setting is completed, so that the RRC connection reset request message is sent. The RRC connection resetting completion message (RRCCconnectionReconnectionComplete message) may be transmitted to both the eNB 102 and the gNB 108, or both the eNB and the gNB, which are the sources of the information (S402). The message names of the RRCConceptionReconfiguration message and the RRCConceptionReconnectionComplete message do not have to be the same. Further, the UE 122 may transmit an RRC connection reset completion message to both the eNB 102 and the gNB 108 regardless of whether the base station apparatus that has transmitted the RRC connection reset request is the eNB 102 or the gNB 108. Further, the UE 122 not only performs the RRC connection resetting procedure, but also for all or part of the other RRC-related means (RRC connection setting means, RRC connection resetting means, etc.), the eNB 102 or gNB 108, or both the eNB 102 and the gNB 108. In response to the request message (RRCCconnectionSeptup, RRCConceptionRestation, etc.) sent from, the completion message may be sent to both the eNB 102 and the gNB 108 regardless of whether the base station device that sent the request message is the eNB 102 or the gNB 108.

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

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

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

FIG. 6 is a diagram showing an example of DRB setting reception and setting according to the embodiment of the present invention. Both the eNB 102, or the gNB 108, or both the eNB 102 and the gNB 108 determine the DRB settings required for the UE 122 (S600). The eNB 102, or gNB 108, or both the eNB 102 and gNB 108, set the DRB settings to information from the core network (EPC104 or 5GC110, or both EPC104 and 5GC110), or the capacity of the UE 122, or information from the core network and the UE 122. It may be decided based on ability. The information from the core network may be determined based on the conditions of the application service such as voice call requested by the UE 122. Next, the eNB 102, or the gNB 108, or both the eNB 102 and the gNB 108 generate an RRC Connection Reconfiguration request message including the DRB setting and transmit it to the UE 122 (S602). The receiving unit 500 of the UE 122 receives the RRC connection reset request message including the DRB setting, and passes the DRB setting to the setting unit 502.

7 and 8 show the ASN. This is an example of 1 (Abust Syntax Notation One). In 3GPP, the specifications related to RRC (Non-Patent Document 4 and Non-Patent Document 10) include messages related to RRC, information (Information Element: IE), and the like in ASN. Described using 1. 7 and 8 are one diagram. That is, FIG. 7 shows the ASN. FIG. 8 is the first of the figures showing an example of 1, and FIG. 8 shows the ASN. This is the second of the figures showing an example of 1. 7 and 8 ASN. In the example of 1, <omitted> and <omitted> are ASN. Indicates that other information is omitted, not a part of the notation of 1. Information may be omitted even in places where there is no description of <omitted> or <omitted>.

In FIG. 7 and FIG. 8 of FIG. 8, DRB-ToAdMod included in the RRCConceptionReconnection message is the IE of the DRB setting. As shown in FIG. 7 and FIG. 8 of FIG. 8, the DRB-ToAd Mod may include the DRB-Identity which is the IE of the DRB identifier and the PDCP-Context which is the PDCP entity setting information corresponding to the DRB identifier. .. Further, as shown in FIG. 7 and FIG. 8 of FIG. 8, the PDCP-Config which is the PDCP entity setting information is the PDCP-EUTRA-Config which is the PDCP entity setting information for E-UTRA, or the PDCP entity setting for NR. PDCP-NR-Config, which is information, may be selected (CHOICE) and included. Further, as shown in FIG. 7 and FIG. 8 of FIG. 8, PDCP-EUTRA-Config and PDCP-NR-Config are pdcp-SN- indicating the length of the PDCP sequence number (Sequence Number: SN). The Size information may be included, and this pdcp-SN-Size may be an integer including 7.

16, 17, and 18 show the ASN. This is another example of 1 (Abust Syntax Notation One). Note that FIGS. 16, 17 and 18 are one diagram. That is, FIG. 16 shows the ASN. It is the first piece of the figure which shows another example of 1, and FIG. 17 is an ASN. It is the second piece of the figure which shows another example of 1, and FIG. 18 shows ASN. This is the third piece of the figure showing another example of 1. The ASNs of FIGS. 16, 17, and 18. In the example of 1, <omitted> and <omitted> are ASN. Indicates that other information is omitted, not a part of the notation of 1. Information may be omitted even in places where there is no description of <omitted> or <omitted>.

In FIG. 16 of FIGS. 16, 17, and 18, the RRCConceptionReconnection message is an IE of the RRC connection reset request for E-UTRA, an IE of the RRCconnectionReconnection-EUTRA-IE, or an IE of the RRC connection reset request for NR. A certain RRCConceptionReconnection-NR-IE may be selected (CHOICE) and included.

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

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

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

In S604 of FIG. 6, in the DRB setting passed from the receiving unit 500 of the UE 122 by the setting unit 502 of the UE 122, at least the DRB identifier and the PDCP entity setting for E-UTRA or the PDCP entity setting for NR as the PDCP entity setting corresponding to the DRB identifier are used. Contains one of the PDCP entity settings. The setting unit 502 of the UE 122 establishes or reestablishes the PDCP entity according to the DRB identifier and the PDCP entity setting 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 setting unit 502 of the UE 122 confirms whether or not the value of the DRB identifier exists in the current terminal device setting (S900). If it does not exist, check whether the PDCP entity setting information for E-UTRA is included in the PDCP entity setting corresponding to this DRB identifier (S902), and if it is included, according to the PDCP entity setting information for E-UTRA. Establish a PDCP entity for E-UTRA (S904). On the other hand, when the PDCP entity setting information for E-UTRA 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 included, establish a PDCP entity for NR according to the PDCP entity setting information for NR (S908). If the PDCP entity setting for NR is not included in the PDCP entity setting corresponding to the DRB identifier, other settings are made (S918).

On the other hand, if the value of the DRB identifier exists in the current terminal device setting, it is confirmed whether the PDCP entity setting information for E-UTRA is included in the PDCP entity setting corresponding to this DRB identifier (S910). , If included, reestablish the PDCP entity for E-UTRA according to the PDCP entity setting information for E-UTRA (S912). On the other hand, when the PDCP entity setting information for E-UTRA 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 included, reestablish the NR PDCP entity according to the NR PDCP entity setting information (S916). If the PDCP entity setting for NR is not included in the PDCP entity setting corresponding to the DRB identifier, other settings are made (S918). The PDCP entity for E-UTRA and the PDCP entity for NR may be switched by the reestablishment process. For example, when the PDCP entity setting corresponding to a certain DRB identifier (referred to as DRB identifier 1) existing in the current UE 122 setting is the PDCP entity setting for E-UTRA, it is included in the received RRC connection reset message. When the DRB setting includes the above-mentioned DRB identifier 1 and the PDCP entity setting corresponding to the DRB identifier 1 is the PDCP entity setting for NR, the PDCP entity corresponding to the DRB identifier 1 is reset as the PDCP entity for NR. do. Similarly, when the PDCP entity setting corresponding to a certain DRB identifier (referred to as DRB identifier 2) existing in the current UE 122 setting is the NR PDCP entity setting, the DRB included in the received RRC connection reset message. When the above-mentioned DRB identifier 2 is included in the setting and the PDCP entity setting corresponding to the DRB identifier 2 is the PDCP entity setting for E-UTRA, the PDCP entity corresponding to the DRB identifier 2 is the PDCP entity for E-UTRA. Reset as. In this way, the PDCP entity setting for E-UTRA and the PDCP entity setting for NR may be switched by the RRC connection reset 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 (RRCCconnectionReconnectionComplete) message to both the eNB 102 and the gNB 108, or both the eNB 102 and the gNB 108 (S606).

The DRB setting in the present embodiment may be included not only in the RRC connection resetting procedure, but also in the RRC connection setting (RRC Connection Establishment) procedure and the RRC connection resetting (RRC Connection Re-Establing) procedure. .. Further, the re-establishment of the PDCP entity in the present embodiment means, for example, a zero reset of the hyper frame number (HFN) described in Non-Patent Document 5 or an initial mode of header compression (Initialization and Refresh: IR). It may include changes to the specified cryptographic algorithm (algorithm) and changes to the cryptographic key. It should be noted that the hyperframe number (HFN) described in the non-patent document is reset to zero, the header compression is changed to the initial mode (Initialization and Refresh: IR), the specified algorithm (algorithm) and cipher. The change to the key is for E-UTRA, but may be applied for NR.

As described above, in the present embodiment, the E-UTRA base station apparatus (eNB) or the NR base station apparatus ( gNB), or the eNB and gNB select whether the PDCP entity used in communication with the UE is for E-UTRA or NR, and notify the UE using the RRC connection reset message. Therefore, it is possible to establish a PDCP entity suitable for the application service used by the UE, and it is possible to perform efficient communication while reducing the complexity of protocol processing.

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

The second embodiment will be described with reference to FIGS. 1 and 5 to 12.

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

In EN-DC, EPC is used as a core network, E-UTRA base station equipment is used as a master base station (Master eNB: MeNB), and NR base station equipment is used as a secondary base station (Secondary gNB: SgNB). Data using the radio resources of both the cell group composed of the base station equipment, that is, the master cell group (MCG) composed of the MeNB and the secondary cell group (Secondary Cell Group: SCG) composed of the SgNB. It may be a technique for communicating. In MR-DC, the master base station is the main RRC function related to MR-DC, for example, establishment, change, release of RB, addition, change, release, handover, etc. of additional cells such as secondary cells, etc. The secondary base station may be a base station having some RRC functions such as SCG change and release.

As shown in FIG. 10, in EN-DC, a part of the data to be transmitted / received is transmitted / received on the SgNB side, and the rest is transmitted / received on the MeNB side. In the EN-DC data transmission / reception method, the node in the EPC becomes the anchor point, which is the branching / merging point of the data, and each of the MeNB and SgNB is a bearer, which is a logical path to and from the EPC. The method of transmitting and receiving data by establishing the above, that is, using the MCG bearer on the MeNB side and the SCG bearer on the SgNB side, and the radio bearer (Radio Bearer: RB) which is the bearer on the wireless side when the MeNB or SeNB becomes an anchor point. ) May split (split) between MeNB and SeNB, and there may be a method of transmitting and receiving data using a split bearer. The split bearer changes the MCG bearer or SCG bearer to a split bearer by adding the radio bearer on the SCG side or the MCG side after establishing the MCG bearer or SCG bearer by the method established at the time of establishing the radio bearer. There may be a method. The establishment and modification of the MCG bearer, SCG bearer, and split bearer may be performed by the transmission RRC (Radio Resource Control) connection reconfiguration procedure performed between the MeNB and the 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 an additional cell group (additional cell). It is called group). The anchor group may be MCG and the additional cell group may be SCG, or the anchor group may be SCG and the additional cell group may be MCG. The split bearer when the anchor group is MCG may be referred to as MCG split bearer, and the split bearer when the anchor group is SCG may be referred to as SCG split bearer.

When data is transmitted / received using a split bearer in EN-DC, for downlink data, a part of the downlink data transferred from the EPC is distributed by the base station apparatus of the anchor cell group to the base station apparatus of the additional cell group. The base station equipment of the additional cell group may transmit to the UE, and the remaining data may be transmitted from the base station equipment of the master cell group to the UE. Regarding the uplink data, the UE transmits a part of the uplink data to the base station apparatus of the additional cell group, and the base station apparatus of the additional cell group distributes a part of the uplink data to the base station apparatus of the master cell group. , The UE may transmit the remaining data to the base station apparatus of the master cell group.

As shown in FIG. 10, when the split bearer is used, the PDCP PDU may be transmitted and received between the base station device of the master cell group and the base station device of the additional cell group.

FIG. 11 is a diagram showing an example of DRB setting reception and setting when an MCG bearer or an SCG bearer is established as a bearer of an anchorage group in the embodiment of the present invention. Even when establishing as an anchor group, it is not necessary to change to a split bearer later. The eNB 102 determines the DRB setting required for the UE 122 (S1100). The eNB 102 may determine the DRB setting based on the information from the core network (EPC104) or the capability of the UE 122, or the information from the core network and the capability of the UE 122. The information from the core network may be determined based on the conditions of the application service such as voice call requested by the UE 122. Next, the eNB 102 generates an RRC connection reconfiguration request (RRCCconnectionReconnection) message including a DRB setting and transmits it to the UE 122 (S1102). The receiving unit 500 of the UE 122 receives the RRC connection reset request message including the DRB setting, and passes the DRB setting to the setting unit 502.

7 and 8 show the ASN. This is an example of 1 (Abust Syntax Notation One).

That is, in FIG. 7 and FIG. 8 of FIG. 8, the DRB-ToAdMod included in the RRCConceptionReconnection message is the IE of the DRB setting. As shown in FIG. 7 and FIG. 8 of FIG. 8, the DRB-ToAd Mod may include the DRB-Identity which is the IE of the DRB identifier and the PDCP-Context which is the PDCP entity setting information corresponding to the DRB identifier. .. Further, as shown in FIG. 7 and FIG. 8 of FIG. 8, the PDCP-Config which is the PDCP entity setting information is the PDCP-EUTRA-Config which is the PDCP entity setting information for E-UTRA, or the PDCP entity setting for NR. PDCP-NR-Config which is information may be selected (CHOICE) and included. Further, as shown in FIG. 7 and FIG. 8 of FIG. 8, PDCP-EUTRA-Config and PDCP-NR-Config are pdcp-SN- indicating the length of the PDCP sequence number (Sequence Number: SN). The Size information may be included, and this pdcp-SN-Size may be an integer including 7.

16, 17 and 18 show the ASN. This is another example of 1 (Abust Syntax Notation One).

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

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

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

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

In S1104 of FIG. 11, in the DRB setting passed from the receiving unit 500 of the UE 122 by the setting unit 502 of the UE 122, at least the DRB identifier and the PDCP entity setting for E-UTRA or the PDCP entity setting for NR as the PDCP entity setting corresponding to the DRB identifier are used. Contains one of the PDCP entity settings. The setting unit 502 of the UE 122 establishes or reestablishes the PDCP entity according to the DRB identifier and the PDCP entity setting corresponding to the DRB identifier.

As described in the first embodiment, FIG. 9 is an example of PDCP setting determination in the setting unit of the terminal device. That is, the setting unit 502 of the UE 122 confirms whether or not the value of the DRB identifier exists in the current terminal device setting (S900). If it does not exist, check whether the PDCP entity setting information for E-UTRA is included in the PDCP entity setting corresponding to this DRB identifier (S902), and if it is included, according to the PDCP entity setting information for E-UTRA. Establish a PDCP entity for E-UTRA (S904). On the other hand, when the PDCP entity setting information for E-UTRA 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 included, establish a PDCP entity for NR according to the PDCP entity setting information for NR (S908). If the PDCP entity setting for NR is not included in the PDCP entity setting corresponding to the DRB identifier, other settings are made (S918).

On the other hand, if the value of the DRB identifier exists in the current terminal device setting, it is confirmed whether the PDCP entity setting information for E-UTRA is included in the PDCP entity setting corresponding to this DRB identifier (S910). , If included, reestablish the PDCP entity for E-UTRA according to the PDCP entity setting information for E-UTRA (S912). On the other hand, when the PDCP entity setting information for E-UTRA 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 included, reestablish the NR PDCP entity according to the NR PDCP entity setting information (S916). If the PDCP entity setting for NR is not included in the PDCP entity setting corresponding to the DRB identifier, other settings are made (S918). The PDCP entity for E-UTRA and the PDCP entity for NR may be switched by the reestablishment process. For example, when the PDCP entity setting corresponding to a certain DRB identifier (referred to as DRB identifier 1) existing in the current UE 122 setting is the PDCP entity for E-UTRA, the DRB included in the received RRC connection reset message. When the above-mentioned DRB identifier 1 is included in the setting and the PDCP entity setting corresponding to the DRB identifier 1 is the PDCP entity setting for NR, the PDCP entity setting corresponding to the DRB identifier 1 is reset as the PDCP entity for NR. do. Similarly, when the PDCP entity setting corresponding to a certain DRB identifier (referred to as DRB identifier 2) existing in the current UE 122 setting is the PDCP entity for NR, the DRB setting included in the received RRC connection reset message. When the above-mentioned DRB identifier 2 is included and the PDCP entity setting corresponding to the 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 PDCP entity setting for E-UTRA and the PDCP entity setting for NR may be switched by the RRC connection reset message.

After the setting is completed by the setting unit 502 of the UE 122, the UE 122 transmits an RRC connection resetting complete message to the eNB 102 in FIG. 11 (S1106).

The DRB setting in the present embodiment may be included not only in the RRC connection resetting procedure but also in the RRC connection setting (RRC Connection Establishment) procedure and the RRC connection resetting (RRC Connection Re-Establing) procedure. .. Further, the re-establishment of the PDCP entity in the present embodiment means, for example, a zero reset of the hyper frame number (HFN) described in Non-Patent Document 5 or an initial mode of header compression (Initialization and Refresh: IR). Changes to the specified cryptographic algorithm (algorithm) and changes to the cryptographic key may be included. It should be noted that the hyperframe number (HFN) described in the non-patent document is reset to zero, the header compression is changed to the initial mode (Initialization and Refresh: IR), the specified algorithm (algorithm) and cipher. The change to the key is for E-UTRA, but may be applied for NR.

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

FIG. 12 shows the ASN. This is an example of 1 (Abust Syntax Notation One). ASN. Of FIG. In the example of 1, <omitted> and <omitted> are ASN. Indicates that other information is omitted, not a part of the notation of 1. Information may be omitted even in places where there is no description of <omitted> or <omitted>. The ASN. An example of 1 is the ANS shown in FIGS. 7 and 8, or FIGS. 16, 17, and 18. It may be a part of the example of 1. The DRB-ToAdModADDCG-NR IE shown in FIG. 12 relates to the DRB setting of the additional cell group, and may have another name. Further, the DRB-ToAdModADDCG-NR IE shown in FIG. 12 may be a part of the upper IE related to the additional cell group setting.

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

In the setting unit 502 of the UE 122, when the value of the DRB identifier included in the DRB setting of the anchor cell group exists in the current setting of the UE 122, and the DRB identifier included in the DRB setting of the anchor cell group is the additional cell group. When it is a DRB identifier included in the DRB setting, that is, when 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 in FIG. 12). -NR, etc.) is split, it is determined that the existing MCG bearer or SCG bearer is changed to the split bearer. The method of determining to change an existing MCG bearer or SCG bearer to a split bearer is not limited to this, and may be another method.

The setting unit 502 of the UE 122 establishes the DRB of the additional cell group according to the DRB setting of the additional cell group, and if the DRB setting of the anchor cell group has the PDCP entity setting corresponding to the DRB identifier, the PDCP entity setting is set. The PDCP entity may be reestablished accordingly. The PDCP entity for E-UTRA and the PDCP entity for NR may be switched by the reestablishment process. For example, when the PDCP entity setting corresponding to a certain DRB identifier (referred to as DRB identifier 1) existing in the current UE 122 setting is the PDCP entity for E-UTRA, the DRB included in the received RRC connection reset message. When the above-mentioned DRB identifier 1 is included in the setting and the PDCP entity setting corresponding to the DRB identifier 1 is the PDCP entity setting for NR, the PDCP entity corresponding to the DRB identifier 1 is reset as the PDCP entity for NR. .. Similarly, when the PDCP entity setting corresponding to a certain DRB identifier (referred to as DRB identifier 2) existing in the current UE 122 setting is the PDCP entity for NR, the DRB setting included in the received RRC connection reset message. When the above-mentioned DRB identifier 2 is included and the PDCP entity setting corresponding to the 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. In this way, the PDCP entity setting for E-UTRA and the PDCP entity setting for NR may be switched by the RRC connection reset message.

As described above, in the present embodiment, even in the case of EN-DC, the anchor cell group communicates with the UE based on the conditions of the application service such as voice call required by the terminal device (UE). Select whether the PDCP entity used in is for E-UTRA or NR, and notify the UE using the RRC connection reset message. Therefore, even with EN-DC, it is possible to establish a PDCP entity suitable for the application service used by the UE, and it is possible to perform efficient communication with reduced complexity of protocol processing.

(Embodiment 3)
In Embodiment 3 of the present invention, the DRB setting including the SDAP entity setting when the core network is 5GC110 will be described. In the third embodiment, the UE 122 may communicate with the 5GC110 via the gNB, may communicate with the 5GC via the eNB, or may communicate with the 5GC using an MR-DC that performs both the gNB and the eNB. You may communicate.

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

FIG. 13 is a diagram showing an example of DRB setting reception and setting according to the embodiment of the present invention. The eNB 102, or gNB 108, or both the eNB 102 and gNB 108 determine the DRB configuration, including the SDAP entity configuration required of the UE 122 (S1300). The eNB 102, or gNB 108, or both the eNB 102 and gNB 108, set the DRB settings to information from the core network (EPC104 or 5GC110, or both EPC104 and 5GC110), or the capacity of the UE 122, or information from the core network and the UE 122. It may be decided based on ability. The information from the core network may be determined based on the conditions of the application service such as voice call requested by the UE 122. Further, the DRB setting may include information about SDAP such as the SDAP header length. Further, the information about SDAP may be included in the SDAP entity setting, or may be included in other entity settings such as PDCP entity setting. Next, the eNB 102, or the gNB 108, or both the eNB 102 and the gNB 108 generate an RRC Connection Reconfiguration request message including the DRB setting and transmit it to the UE 122 (S1302). The receiving unit 500 of the UE 122 receives the RRC connection reset request message including the DRB setting, and passes the DRB setting to the setting unit 502.

14 and 15 show the ASN. This is an example of 1 (Abust Syntax Notation One). The ASNs of FIGS. 14 and 15. In the example of 1, <omitted> and <omitted> are ASN. Indicates that other information is omitted, not a part of the notation of 1. Information may be omitted even in places where there is no description of <omitted> or <omitted>.

FIG. 14 is an example in which the SDCP header length information is included in the SDCP entity setting, and FIG. 15 is an example in which the SDCP header length is included in the 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, "len0 bits", "len8 bits", "len16 bits", and "len24 bits" may be 0 bits, 8 bits, 12 bits, and 24 bits, respectively. Further, instead of this, the notation may be in byte (byte) or octet (octet) units such as “len0bytes”, “len1bytes”, “len2bytes”, and “len3bytes”. Note that the SDAP header length of zero may mean that the SDAP header does not exist. The notation and name of the SDAP header length is not limited to this, and may be another notation or name. Further, the ASN. The message name, IE name, parameter name, etc. of 1 are examples, and other names may be used. In addition, the ASN. An example of 1 is the ASN. It may be a part of the example of 1.

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

The setting unit 502 of the UE 122 will be described with reference to the example of FIG. 15, that is, the case where the SDAP header length is included in the PDCP entity setting. In S1304 of FIG. 13, the DRB setting passed by the setting unit 502 of the UE 122 from the receiving unit 500 of the UE 122 includes at least the DRB identifier and the PDCP entity setting corresponding to the DRB identifier, and the PDCP entity setting includes the SDAP header length. Is included. The setting unit 502 of the UE 122 establishes or reestablishes the PDCP entity according to the DRB identifier and the PDCP entity setting corresponding to the DRB identifier. That is, if the value of the DRB identifier passed from the receiver 500 does not exist in the current terminal device settings, a PDCP entity is established and the value of the DRB identifier passed from the receiver 500 is the value of the current terminal device. The PDCP entity may be reestablished if it is present in the configuration. The established or re-established PDCP entity may specify the SDAP SDU, that is, the start position of the IP packet from the information of the SDAP header length, and perform the header compression process. In the PDCP entity, even when the SDAP header length is not included in the PDCP entity setting and is included in the SDAP entity setting, the SDAP SDU, that is, the start position of the IP packet is obtained 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 the setting is completed by the setting unit 502 of the UE 122, in FIG. 13, the UE 122 transmits an RRC connection reconfiguration complete message to both the eNB 102 or gNB 108, or both the eNB 102 and the gNB 108 (S1306).

The DRB setting in the present embodiment may be included not only in the RRC connection resetting procedure but also in the RRC connection setting (RRC Connection Establishment) procedure and the RRC connection resetting (RRC Connection Re-Establing) procedure. .. Further, the re-establishment of the PDCP entity in the present embodiment means, for example, a zero reset of the hyper frame number (HFN) described in Non-Patent Document 5 or an initial mode of header compression (Initialization and Refresh: IR). Changes to the specified cryptographic algorithm (algorithm) and changes to the cryptographic key may be included. It should be noted that the hyperframe number (HFN) described in the non-patent document is reset to zero, and the initial stage of header compression (Initialization).
The change to and Refresh (IR) mode, the specified algorithm (algorithm) and the change to the encryption key are for E-UTRA, but may be applied for NR.

Further, although the DRB setting in the present embodiment assumes the case where the core network is 5GC, it may be applied even when the core network is EPC.

As described above, in the present embodiment, the E-UTRA base station apparatus (eNB) or the NR base station apparatus ( gNB), or eNB and gNB set the SDAP entity including the SDAP header length or PDCP entity setting including the SDAP header length to be used in communication with the UE, and use the RRC connection reset message to the UE. Notice. Therefore, it is possible to use the SDAP header length suitable for the application service used by the UE, and to perform header compression by the PDCP entity as needed, and to reduce the complexity of protocol processing and perform efficient communication. can.

In addition, a description about RRC in each embodiment of the present invention, for example, a message such as an RRC connection reset request message, and ASN. 1st class is assumed to be RRC for NR (for example, RRC described in Non-Patent Document 9 and Non-Patent Document 10), but it may be for extension of LTE, and it may be used as a base station device for E-UTRA. It may be transmitted and received to and from a terminal device compatible with MR-DC.

Further, 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 resetting procedure at the time of handover. Further, when reestablishing each entity such as the PDCP entity in each embodiment of the present invention, the security-related settings may also be reset.

The program that operates in the apparatus according to the present invention may be a program that controls the Central Processing Unit (CPU) or the like to operate the computer so as to realize the functions of the above-described embodiments related to the present invention. .. The program or the information handled by the program is temporarily read into a volatile memory such as Random Access Memory (RAM) at the time of processing, or stored in a non-volatile memory such as a flash memory or a Hard Disk Drive (HDD), and is required. The CPU reads, corrects, and writes accordingly.

In addition, a part of the apparatus in the above-described embodiment may be realized by a computer. In that case, the program for realizing this control function is recorded on a recording medium that can be read by the computer, and the program recorded on the recording medium is read by the computer system and executed. May be good. The "computer system" referred to here is a computer system built into the device, and includes hardware such as an operating system and peripheral devices. Further, the "recording medium that can be read by a computer" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, and the like.

Furthermore, a "recording medium that can be read by a computer" is a communication line that dynamically holds a program for a short time, like a communication line when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. It may also include a program that holds a program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or a client in that case. Further, the above program may be for realizing a part of the above-mentioned functions, and may be further realized by combining the above-mentioned functions with a program already recorded in the computer system. ..

Also, each functional block, or feature, of the device used in the embodiments described above may be implemented or implemented in an electrical circuit, i.e., typically an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein are general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or others. Programmable logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general purpose processor may be a microprocessor, or instead the processor may be a conventional processor, controller, microprocessor, or state machine. The general-purpose processor or each of the above-mentioned circuits may be composed of a digital circuit or an analog circuit. In addition, when an integrated circuit technology that replaces the current integrated circuit appears due to advances in semiconductor technology, it is also possible to use an integrated circuit based on this technology.

The invention of the present application is not limited to the above-described embodiment. In the embodiment, an example of the device has been described, but the present invention is not limited to this, and the present invention is not limited to this, and is a stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device, a kitchen device, and the like. It can be applied to terminal devices or communication devices such as cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other living equipment.

Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within a range not deviating from the gist of the present invention are also included. Further, the present invention can be variously modified within the scope of the claims, and the technical scope of the present invention also includes embodiments obtained by appropriately combining the technical means disclosed in the different embodiments. Is done. Further, the elements described in each of the above-described embodiments, and the configuration in which the elements having the same effect are replaced with each other is also included.

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

Further, one aspect of the present invention is a terminal device that communicates with the base station device, and is 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. The DRB setting includes a DRB identifier and a PDCP entity setting corresponding to the DRB identifier, and the value of the DRB identifier exists in the current terminal device setting. , The PDCP entity setting information includes one of the PDCP entity setting for E-UTRA and the PDCP entity setting for NR, and the PDCP entity setting information includes the information of the PDCP entity setting for E-UTRA. If so, the PDCP entity is reestablished according to the PDCP entity setting information, and if the PDCP entity setting information includes the PDCP entity setting information for NR, the PDCP entity is established according to the PDCP entity setting information.

Moreover, one aspect of the present invention is MR-DC (Multi Radio Access Technology Dual) to E-UTRA (Evolved Universal Radio Access) and NR (New Radio).
In the terminal device corresponding to Entity), when the E-UTRA becomes the master cell group, the RRC connection reset request message including the DRB (Data Radio Bearer) setting of the anchor cell group is received from the master base station device. 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 set. The PDCP entity setting information includes one of the PDCP entity setting for E-UTRA and the PDCP entity setting for NR, and the PDCP entity setting information includes the E. -When the information of the PDCP entity setting for UTRA is included, the PDCP entity is established according to the PDCP entity setting information, and when the PDCP entity setting information includes the PDCP entity setting information for NR, the PDCP entity setting information. Establish PDCP entity according to.

Further, one aspect of the present invention corresponds to the MR-DC (Multi Radio Access Technology Dual Connect Device) to E-UTRA (Evolved Universal Terrestrial Radio Access) and NR (New Radio). When the UTRA is a master cell group, the receiving unit that receives the RRC connection reset request message including the DRB (Data Radio Bearer) setting of the anchor cell group from the master base station apparatus, and the DRB are set according to the DRB setting. The DRB setting includes a DRB identifier and a PDCP entity setting corresponding to the DRB identifier, and the value of the DRB identifier exists 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 when the PDCP entity setting information includes the information of the PDCP entity setting for E-UTRA, the PDCP entity setting According to the information, the PDCP entity is reestablished, and when the PDCP entity setting information includes the PDCP entity setting information for NR, the PDCP entity is reestablished according to the PDCP entity setting information.

Moreover, one aspect of the present invention is MR-DC (Multi Radio Access Technology Dual) to E-UTRA (Evolved Universal Radio Access) and NR (New Radio).
In the case of a terminal device corresponding to (Connectivity) and the E-UTRA is a master cell group, the DRB (Data Radio Bearer) setting of the anchor cell group and the DRB setting of the additional cell group are included from the master base station device. A receiving unit that receives an RRC connection reset request message and a setting unit that sets the DRB according to the DRB setting are provided, and the DRB setting of the anchor cell group includes a DRB identifier of the anchor cell group and the anchor cell group. The PDCP entity setting corresponding to the DRB identifier of the additional cell group includes the DRB identifier of the anchor cell group and the information that the DRB type is split, and corresponds to the DRB identifier of the anchor cell group. The PDCP entity of the anchor group is reestablished according to the PDCP entity setting information included in the DRB setting of the anchor group.

Further, one aspect of the present invention is a terminal device that communicates with the base station device, and is 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. The DRB setting includes a DRB identifier and a SDAP entity setting corresponding to the DRB identifier, and the value of the DRB identifier is present in the current terminal device setting. Instead, the SDAP entity setting includes the SDAP header length, and the SDAP header length is one or more of an integral multiple of 8 including zero, establishing the SDAP entity according to the SDAP setting information.

Further, one aspect of the present invention is a terminal device that communicates with the base station device, and is 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. The DRB setting includes a DRB identifier and a SDAP entity setting corresponding to the DRB identifier, and the value of the DRB identifier exists in the current terminal device setting. , The SDAP entity setting includes the SDAP header length, the SDAP header length is one or more of an integral multiple of 8 including zero, and the SDAP entity is reestablished according to the SDAP setting information.

Note that these comprehensive or specific embodiments may be realized in a system, device, method, integrated circuit, computer program, or recording medium, and the system, device, method, integrated circuit, computer program, and recording medium. It may be realized by any combination of.

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

Claims (2)

A base station device that supports EN-DC
It is equipped with a communication unit that sends an RRC connection reset message including DRB settings 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 base station device that is a PDCP entity setting for NR. A method performed by a base station appliance that supports EN-DC.
The method sends an RRC connection reset message, including DRB settings, 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 in which the PDCP entity setting is a PDCP entity setting for NR.

Images