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

Terminal device, base station device, method, and integrated circuit Download PDF

Info

Publication number
WO2020031664A1
WO2020031664A1 PCT/JP2019/028537 JP2019028537W WO2020031664A1 WO 2020031664 A1 WO2020031664 A1 WO 2020031664A1 JP 2019028537 W JP2019028537 W JP 2019028537W WO 2020031664 A1 WO2020031664 A1 WO 2020031664A1
Authority
WO
WIPO (PCT)
Prior art keywords
sdap
capability
information
capability information
base station
Prior art date
Application number
PCT/JP2019/028537
Other languages
French (fr)
Japanese (ja)
Inventor
秀和 坪井
山田　昇平
貴子 堀
Original Assignee
シャープ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by シャープ株式会社 filed Critical シャープ株式会社
Publication of WO2020031664A1 publication Critical patent/WO2020031664A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present invention.
  • FIG. 4 is a diagram illustrating a protocol stack of UP and CP of a terminal device and a base station device in E-UTRA according to the embodiment of the present invention.
  • FIG. 4 is a diagram illustrating a protocol stack of UP and CP of a terminal device and a base station device in NR in the embodiment of the present invention.
  • FIG. 1 is a block diagram showing a configuration of a terminal device according to an embodiment of the present invention.
  • FIG. 2 is a block diagram illustrating a configuration of a base station device according to the embodiment of the present invention.
  • Information related to radio bearer setting according to the embodiment of the present invention is a diagram showing an example of an (Abstract ⁇ Syntax ⁇ Notation ⁇ One) description. Information related to UE capability and ASN. The figure which shows an example of 1 description. Information related to UE capability and ASN. The figure which shows another example of one description.
  • LTE (and LTE-A Pro) and NR may be defined as different RATs.
  • NR may be defined as a technology included in LTE.
  • LTE may be defined as a technology included in NR.
  • LTE connectable with NR and Multi ⁇ RAT ⁇ Dual ⁇ connectivity may be distinguished from conventional LTE.
  • This embodiment may be applied to NR, LTE and other RATs. The following description will be made using terms related to LTE and NR, but may be applied in other technologies using other terms.
  • E-UTRA in the present embodiment may be replaced with the term LTE
  • LTE may be replaced with the term E-UTRA.
  • FIG. 1 is a schematic diagram of a communication system according to each embodiment of the present invention.
  • E-UTRA100 is a radio access technology described in Non-Patent Document 3 and the like, and is composed of a cell group (CellCGroup: CG) composed of one or a plurality of frequency bands.
  • the eNB (E-UTRAN ⁇ Node ⁇ B) 102 is an E-UTRA base station apparatus.
  • EPC (Evolved Packet Core) 104 is a core network described in Non-Patent Document 14 and the like, 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 (Control @ Plane: CP) through which control signals pass and a user plane (User @ Plane: UP) through which the user data passes.
  • Control @ Plane: CP Control @ Plane: CP
  • User @ Plane: UP user plane
  • the NR 106 is a radio access technology described in Non-Patent Document 9 and the like, and includes a cell group (Cell (Group: CG) configured with one or a plurality of frequency bands.
  • Cell Group: CG
  • gNB g Node B
  • the 5GC 110 is a core network described in Non-Patent Document 2 and the like, and is designed as an NR core network, but may be used as an E-UTRA core network having a function of connecting to 5CG.
  • E-UTRA may include E-UTRA having a function of connecting to 5CG.
  • An interface 114 is an interface between the eNB 102 and the 5GC 110, an interface 116 is an interface between the gNB 108 and the 5GC 110, an interface 118 is an interface between the gNB 108 and the EPC 104, an interface 120 is an interface between the eNB 102 and the gNB 108, and an interface 124 is an EPC 104 and the 5GC 110 Interface between the two.
  • the interface 114, the interface 116, the interface 118, the interface 120, and the interface 124 are interfaces that pass only the CP, only the UP, or both the CP and the UP.
  • the interface 114, the interface 116, the interface 118, the interface 120, and the interface 124 may not exist depending on the communication system provided by the communication carrier.
  • the @UE 122 is a terminal device (User @ Equipment: UE) that supports NR or supports both E-UTRA and NR.
  • the $ MAC 202 is a medium access control layer that maps various logical channels (Logical @ Channel) to various transport channels.
  • the MAC 202 is connected to a higher-order RLC (Radio Link Control layer) 204 described later by a logical channel.
  • Logical channels are roughly 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 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. (Non-Patent Document 7).
  • the RLC 204 divides (segments) data received from a higher-order PDCP (Packet Data Convergence Protocol Protocol) 206 described later, and adjusts the data size so that the lower layer (lower layer) can appropriately transmit data.
  • PDCP Packet Data Convergence Protocol Protocol
  • Wireless link control layer wireless link control layer.
  • the RLC 200 also has a function to guarantee 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).
  • $ PDCP 206 is a packet data convergence protocol layer (packet data convergence protocol layer) for efficiently transmitting an IP packet (IP @ Packet) as user data in a wireless section.
  • the PDCP 206 may have a header compression function for compressing unnecessary control information.
  • the PDCP 206 may also have a data encryption function (Non-Patent Document 5).
  • the data processed in the MAC 202, the RLC 204, and the PDCP 206 are referred to as a MAC PDU (Protocol Data Unit), an RLC PDU, and a PDCP PDU, respectively.
  • Data passed from the upper layer to the MAC 202, RLC 204, and PDCP 206 or data passed to the upper layer is called MAC @ SDU (Service @ Data @ Unit), RLC @ SDU, and PDCP @ SDU, respectively.
  • the $ CP protocol stack includes an RRC (Radio Resource Control layer) 208 in addition to the PHY 200, the MAC 202, the RLC 204, and the PDCP 206.
  • the RRC 208 is a radio link control layer (radio link control layer) that performs setting and resetting of a radio bearer (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 (Signaling Radio Bearer: SRB) and a data radio bearer (Data Radio Radio Bearer: DRB), and the SRB is used as a path for transmitting an RRC message that is control information. You may. 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-described function classification of the MAC 202, the RLC 204, the PDCP 206, and the RRC 208 is an example, and some or all of the functions may not be implemented. In addition, some or all of the functions of each layer may be included in another layer.
  • the IP layer, the Transmission Control Protocol (TCP) layer above the IP layer, the User Datagram Protocol (UDP) layer, the application layer, and the like are layers higher than the PDCP layer (not shown).
  • An RRC layer and a NAS (non Access String) layer are also upper layers of the SDAP layer (not shown).
  • the PDCP layer is an RRC layer, a NAS layer, an IP layer, a TCP (Transmission Control Protocol) layer above the IP layer, a UDP (User Datagram Protocol) layer, and a lower layer of an application layer.
  • FIG. 3 is a diagram illustrating a protocol stack (Protocol @ Stack) of UP and CP of the terminal device and the base station device in the NR radio access layer in each embodiment of the present invention.
  • Protocol stack Protocol @ Stack
  • FIG. 3A is a UP protocol stack diagram used when the UE 122 communicates with the gNB 108.
  • the $ MAC 302 is a medium access control layer that maps various logical channels (Logical @ Channel) to various transport channels.
  • the MAC 302 may be connected to a higher-level RLC (Radio Link Control layer) 304 described later by 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 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).
  • the RLC 304 divides (segments) data received from a higher-order PDCP (Packet Data Convergence Protocol Protocol) 206 described later, and adjusts the data size so that the lower layer can appropriately transmit the data.
  • Layer radio link control layer
  • the RLC 304 may 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).
  • the $ PDCP 306 is a packet data convergence protocol layer (packet data convergence protocol layer) for efficiently transmitting an IP packet (IP @ Packet) as user data in a wireless section.
  • the PDCP 306 may have a header compression function for compressing unnecessary control information.
  • the PDCP 306 may also have a data encryption function (Non-Patent Document 11).
  • the end marker PDU is an SDAP control PDU described in Non-Patent Document 16, in which the SDAP entity of the UE determines the QoS flow corresponding to the QoS flow identifier included in the QoS flow identifier field of the end marker PDU, and the end marker PDU. Is used to notify that the mapping with the transmitted radio bearer is finished.
  • FIG. 3B is a protocol stack diagram of the CP used when the UE 122 communicates with the gNB 108.
  • the $ CP protocol stack includes an RRC (Radio Resource Control layer) 308 in addition to the PHY 300, the MAC 302, the RLC 304, and the PDCP 306.
  • the RRC 308 is a radio link control layer (radio link control layer) that performs setting and resetting of a radio bearer (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 (Signaling Radio Bearer: SRB) and a data radio bearer (Data Radio Radio Bearer: DRB), and the SRB is used as a path for transmitting an RRC message that is control information. You may.
  • DRB may be used as a route for transmitting user data.
  • Each RB may be set between the gNB 108 and the RRC 308 of the UE 122. Further, a portion of the RB configured by the RLC 304 and the MAC 302 may be called an RLC bearer (Non-Patent Document 10).
  • each layer may be included in another layer (layer).
  • the MAC 202, the RLC 204, the PDCP 206, and the RRC 208 are respectively referred to as an E-UTRA MAC or an LTE MAC, an E-UTRA RLC or LTE RLC, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE.
  • the MAC 302, the RLC 304, the PDCP 306, and the RRC 308 may be referred to as an NR MAC, an NR RLC, an NR RLC, and an NR RRC, respectively.
  • the space may be described using a space such as E-UTRA @ PDCP, LTE @ PDCP, or NR @ PDCP.
  • the eNB 102, the gNB 108, the EPC 104, and the 5GC 110 may be connected via an interface 112, an interface 116, an interface 118, an interface 120, and an interface 114. Therefore, in order to support various communication systems, the RRC 208 of FIG. 2 may be replaced with the RRC 308 of FIG. Further, the PDCP 206 in FIG. 2 may be replaced with the PDCP 306 in FIG. Further, the RRC 308 in FIG. 3 may include the function of the RRC 208 in FIG. Further, the PDCP 306 in FIG. 3 may be the PDCP 206 in FIG.
  • FIG. 4 is a diagram showing an example of a flow of a UE capability (UE Capability) procedure and an RRC reset procedure in the embodiment of the present invention.
  • the RRC reset procedure may be an RRC connection reset procedure.
  • the UE Capability procedure is a means used to transfer the Radio Access capability information of the UE 122 from the UE 122 to the network in LTE and / or NR.
  • the RRC reconfiguration procedure (RRC @ Reconfiguration) performs establishment, change, and release of RB in NR and change, release, and the like of a secondary cell described in Non-Patent Document 10, and handover (reconfiguration with synchronization). And a procedure used for measurement and the like.
  • the RRC connection reconfiguration procedure (RRC Connection Reconfiguration) performs establishment, change, and release of an RB in LTE and change, release, and the like of LTE in LTE, as well as handover and measurement (Measurement). )).
  • the RRC connection resetting procedure is performed in the MR-DC, particularly when the core network is the EPC 104 and the master node is the eNB 102, the EN-DC (E-UTRA-NR @ Dual Connectivity) and the core network. Is the 5GC 110 and the MR-DC when the master node is the eNB 102 (also referred to as the extended eNB 102). If the NGEN-DC (NG-RAN @ E-UTRA-NR @ Dual @ Connectivity), the RRC connection is reconfigured.
  • the procedure includes not only LTE, but also part of establishment, change, and release of RB in NR, and change and release of a secondary cell described in Non-Patent Document 10, and handover and measurement (Measurement). Also used to do part of It is. In each embodiment of the present invention, in order to avoid complicating the description, the description will be made using the name of RRC reconfiguration procedure, and the description will be made using gNB 108 as the base station apparatus.
  • the gNB creates an RRC reconfiguration message (RRCReconfiguration) based on the UE capability information acquired in the UE capability procedure, and transmits the message to the UE 122 (step S404).
  • the UE 122 performs various settings, for example, a setting of a radio bearer, a setting of an SDAP, and the like, according to information elements included in the RRC reconfiguration message, which will be described later.
  • the UE 122 may send an RRC reconfiguration completion message (RRCReconfigurationComplete) or the like to the gNB 108 (not shown).
  • the RRC reconfiguration message may be rephrased as RRC reconfiguration
  • the RRC reconfiguration complete message may be rephrased as RRC reconfiguration complete.
  • the UE 122 illustrated in FIG. 5 performs processing in accordance with the receiving unit 500 that receives a UE capability inquiry message, an RRC reconfiguration message, and the like from the gNB 108, and various information elements (IE: Information @ Element) and various conditions included in the received message. And a transmitting unit 504 for transmitting a UE capability information message and the like to the gNB 108. Further, a control unit for controlling the operation of each unit based on various conditions may be separately provided.
  • IE Information @ Element
  • FIG. 6 is a block diagram showing a configuration of the base station apparatus (gNB 108) according to the embodiment of the present invention. Note that FIG. 6 illustrates only main components which are closely related to one embodiment of the present invention in order to avoid a complicated description.
  • the description may be made by replacing the “field” with the “information element”.
  • ⁇ abbreviation> and ⁇ omission> are ASN. It is not part of the notation of 1 but indicates that other information is omitted. Fields may be omitted even where there is no description of ⁇ omitted> or ⁇ omitted>.
  • the ASN. 1 is ASN. It does not follow the one notation method correctly, but is an example of RRC reset parameters in one embodiment of the present invention, and other names or other notations may be used. Also, the ASN.
  • the example 1 shows only an example related to main information which is closely related to one embodiment of the present invention in order to avoid a complicated description. Note that, unless otherwise explicitly described, other ASN. The above description also applies to one description.
  • the information element represented by DRB-ToAddModList or DRBToAddMod may be a list of information indicating the setting of a DRB (data radio bearer) to be added or changed, and in the embodiment of the present invention, the radio bearer setting information Element or data radio bearer information element.
  • the information element represented by cnAssociation in the radio bearer setting information element may be an information element indicating whether to use the EPC 104 or the 5GC 110 for the core network. It may be rephrased as an association information element. That is, when the UE 122 connects to the EPC, the DRB is associated with the EPS bearer identifier information element (eps-BearerIdentity) during cnAssociation or the EPS bearer identifier that is the value of the EPS bearer identifier information element, and the UE 122 connects to the 5GC 110.
  • the EPS bearer identifier information element eps-BearerIdentity
  • the information element represented by sdap-Config may be information on setting or resetting of an SDAP entity that determines a method of mapping a QoS flow and a DRB when the core network is 5GC110, In the embodiment of the present invention, it may be rephrased as an SDAP setting information element.
  • the information element indicated by pdu-session or PDU-Session ID included in the SDAP setting information element is a radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element.
  • the identifier of the PDU session described in Non-Patent Document 2 to which the QoS flow assigned to (map) belongs may be referred to. In the embodiment of the present invention, it may be rephrased as a PDU session information element.
  • the value of the PDU session information element may be a non-negative integer.
  • the information element indicated by sdap-HeaderUL included in the SDAP setting information element is an uplink SDAP to a radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element. It may be an information element indicating whether a header exists or not, and may be rephrased as an uplink information element in the embodiment of the present invention.
  • the information element indicated by mappedQoS-FlowsToRelease included in the SDAP setting information element corresponds to the radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element.
  • the information may be information indicating a list of QoS flow identifiers (QFI: QoS @ Flow @ Identity) information elements of the QoS flows for which the correspondence is released among the (mapped) QoS flows, according to an embodiment of the present invention. In the embodiment, it may be paraphrased as a QoS flow information element to be released.
  • the above-mentioned QoS flow may be a QoS flow of the PDU session indicated by the PDU session information element included in the present SDAP setting information element.
  • the information element indicated by QFI may be a QoS flow identifier that uniquely identifies a QoS flow described in Non-Patent Document 2, and may be rephrased as a QoS flow identifier information element in the embodiment of the present invention.
  • the value of the QoS flow identifier information element may be a non-negative integer. Also, the value of the QoS flow identifier information element may be unique for the PDU session.
  • the AS reflective QoS is a QoS field in the SDAP header when a downlink SDAP @ PDU is received from a lower layer of a radio bearer in which a downlink SDAP header is set by a downlink header information element.
  • the QoS flow identifier field of the SDP header when the RDI (Reflective QoS flow to DRB mapping Indication) field indicating whether or not the mapping information between the flow and the radio bearer needs to be updated is set to "1"
  • RDI Reflective QoS flow to DRB mapping Indication
  • the NAS reflective QoS is a field of the NAS header when the downlink SDAP @ PDU is received from the lower layer of the radio bearer in which the downlink header is set by the downlink header information element.
  • the RQI (Reflective QoS Indication) field is set to "1" indicating whether the layer needs to be notified that the service data flow (Service Data Flow: SDF) and the QoS mapping rule need to be updated or not.
  • SDF Service Data Flow
  • the QoS flow identifier field of the SDAP header is processed to identify the QoS flow, and the corresponding information between the QoS flow of the downlink SDAP @ PDU and the radio bearer is used to determine the QoS of the uplink.
  • the information element represented by pdcp-Config or PDCP-Config may be information related to the setting of the NR @ PDCP entity for establishing or changing the PDCP 306 for SRB or DRB. Often, in the embodiment of the present invention, it may be referred to as a PDCP setting information element.
  • the information related to the setting of the NR @ PDCP entity includes information indicating the size of the uplink sequence number, information indicating the size of the downlink sequence number, information indicating the profile of header compression (RoHC: Robust @ Header @ Compression), and reordering (RoHC: Robust @ Header @ Compression). re-ordering) timer information and the like may be included.
  • the information element represented by UE-CapabilityRAT-ContainerList included in the capability information message has a list of containers represented by UE-CapabilityRAT-Container of the information element as a value (Value), and the UE capability is RAT. Each container may be included in one container.
  • the UE-CapabilityRAT-Container includes a rat-Type field having information indicating a type (Type) of a radio access technology (Radio Access Technology: RAT) as a value, and a byte sequence indicating a UE capability of the RAT indicated by rat-Type.
  • a ueCapabilityRAT-Container field having a value may be included.
  • the UE-NR-Capability information element may be included in the value of the ueCapabilityRAT-Container field.
  • the SDAP-Parameters information element may include a field (supportHeaderUL) indicating that the UE 122 supports the SDAP header for the uplink.
  • supportHeaderUL a field indicating that the UE 122 supports the SDAP header for the uplink.
  • the SDAP-Parameters information element may include a field (supportDefaultDRB) indicating that the UE 122 supports the default DRB. In this case, if the SDAP-Parameters information element does not include the supportDefaultDRB field, it may indicate that the UE 122 does not support the default DRB.
  • the SDAP-Parameters information element includes a field (supportDefaultDRB) indicating that the UE 122 supports the default DRB, regardless of whether the supportHeaderUL field is included, the UE 122 determines whether the UE122 supports the default DRB. It may indicate that it supports an SDAP header for the uplink.
  • supportDefaultDRB supportDefaultDRB
  • a field indicating that the UE 122 supports the SDAP header for the uplink and does not support the default DRB, and the UE 122 supports the SDAP header for the uplink may be included.
  • supportSDAP having a value obtained by selecting (Choice) any of the fields indicating that the default DRB is supported may be included.
  • supportSDAP is not included in the SDAP-Parameters information element, it may indicate that the UE 122 does not support the SDAP header for the uplink.
  • FIG. 9 shows an ASN. Representing the SDAP-Parameters information element. It is another example of one description.
  • the SDAP-Parameters information element is information indicating whether UE 122 supports a SDAP header for the uplink, and / or information indicating whether UE 122 supports a default DRB, and / or It may include information indicating whether the UE 122 supports AS reflective QoS.
  • the SDAP-Parameters information element may include a field (supportHeaderUL) indicating that the UE 122 supports the SDAP header for the uplink.
  • supportHeaderUL a field indicating that the UE 122 supports the SDAP header for the uplink.
  • the SDAP-Parameters information element may include a field (supportDefaultDRB) indicating that the UE 122 supports the default DRB. In this case, if the SDAP-Parameters information element does not include the supportDefaultDRB field, it may indicate that the UE 122 does not support the default DRB.
  • the SDAP-Parameters information element includes a field (supportDefaultDRB) indicating that the UE 122 supports the default DRB and / or a field (supportAsReflective) indicating that the UE 122 supports the AS reflective QoS.
  • supportDefaultDRB a field indicating that the UE 122 supports the default DRB
  • supportAsReflective indicating that the UE 122 supports the AS reflective QoS.
  • the SDAP-Parameters information element may include information indicating whether the UE 122 supports mapping multiple QoS flows to one DRB.
  • the SDAP-Parameters information element may include a field (supportMultipleMapping) indicating that the UE 122 supports mapping of a plurality of QoS flows to one DRB.
  • supportMultipleMapping field is not included in the SDAP-Parameters information element, it may indicate that the UE 122 does not support mapping of a plurality of QoS flows to one DRB.
  • the SDAP-Parameters information element may include information indicating whether the UE 122 supports an end marker PDU.
  • the SDAP-Parameters information element may include a field (supportEndMarker) indicating that the UE 122 supports the end marker PDU.
  • supportEndMarker when the supportEndMarker field is not included in the SDAP-Parameters information element, it may indicate that the UE 122 does not support the end marker PDU.
  • the @gNB 108 may include information specifying a field to be included in the SDAP-Parameters information element in the UE capability inquiry message.
  • the gNB 108 can perform appropriate parameter setting for the SDAP to the UE 122 by the UE 122 notifying the UE of the capability information of the SDAP.
  • the message and / or information element fields used in the above description may be optional. That is, the message and / or information element fields used in the above description may be included in the RRC reconfiguration message as needed.
  • the radio bearer setting in each embodiment of the present invention may be included not only in the RRC connection re-establishment procedure, but also in the RRC establishment (RRC @ Establishment) procedure or the RRC re-establishment (RRC @ Re-Estimation) procedure.
  • the radio bearer in each embodiment of the present invention may be a DRB or an SRB.
  • a first aspect of the present invention is a terminal device for communicating with a base station device, comprising: a receiving unit that receives a User @ Equipment (UE) capability inquiry message; A transmission unit for notifying the base station apparatus, wherein the UE capability information includes UE capability information relating to a Service Data Adaptation Protocol (SDAP) layer, and the UE capability information relating to the SDAP layer is an LDAP header for uplink. And / or information indicating whether to support the default data radio bearer.
  • SDAP Service Data Adaptation Protocol
  • a second aspect of the present invention is a base station device communicating with a terminal device, wherein the transmitting unit transmits a UE capability inquiry message, the receiving unit receives UE capability information from the terminal device, A processing unit for generating an RRC re-establishment message including a data radio bearer configuration based on UE capability information on a Service Data Adaptation Protocol (SDAP) layer included in the UE capability information; Includes information indicating whether to support the SDAP header for the uplink and / or information indicating whether to support the default DRB.
  • SDAP Service Data Adaptation Protocol
  • a fourth aspect of the present invention is a method applied to a base station apparatus communicating with a terminal apparatus, wherein a step of transmitting a UE capability inquiry message and a step of receiving UE capability information from the terminal apparatus. And generating an RRC reconfiguration message including a data radio bearer configuration based on UE capability information on a Service Data Adaptation Protocol (SDAP) layer included in the UE capability information.
  • SDAP Service Data Adaptation Protocol
  • the UE capability information includes information indicating whether to support the SDAP header for the uplink and / or information indicating whether to support the default DRB.
  • the program that operates on the device according to the present invention may be a program that controls a Central Processing Unit (CPU) or the like so that the computer functions so as to realize the functions of the above-described embodiment according 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 is stored in a non-volatile memory such as a flash memory or a Hard Disk Drive (HDD). In response, reading, correction and writing are performed by the CPU.
  • a volatile memory such as a Random Access Memory (RAM) during processing
  • a non-volatile memory such as a flash memory or a Hard Disk Drive (HDD).
  • HDD Hard Disk Drive
  • a part of the device in the above-described embodiment may be realized by a computer.
  • a program for realizing this control function is recorded on a computer-readable recording medium, and the program recorded on this recording medium is read by a computer system and executed to realize the control function.
  • the "computer system” is a computer system built in the apparatus, and includes hardware such as an operating system and peripheral devices.
  • the "computer-readable recording medium” may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, and the like.
  • a "computer-readable recording medium” means that a program is dynamically held for a short time, such as a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line.
  • a program that holds a program for a certain period of time such as a volatile memory in a computer system serving as a server or a client in that case, may be included.
  • the above-mentioned program may be for realizing a part of the above-mentioned functions, or may be for realizing the above-mentioned functions in combination with a program already recorded in a computer system. .
  • each functional block or various features of the device used in the above-described embodiment may be implemented or executed by an electric circuit, that is, typically, an integrated circuit or a plurality of 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 Logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof.
  • a general purpose processor may be a microprocessor, or, in the alternative, the processor may be a conventional processor, controller, microcontroller, or state machine.
  • the general-purpose processor or each of the above-described circuits may be configured by a digital circuit, or may be configured by an analog circuit. Further, in the case where a technology for forming an integrated circuit that substitutes for a current integrated circuit appears due to the progress of semiconductor technology, an integrated circuit based on the technology can be used.
  • the present invention is not limited to the above embodiment.
  • an example of the device is described.
  • the present invention is not limited to this, and stationary or non-movable electronic devices installed indoors and outdoors, for example, AV devices, kitchen devices, It can be applied to terminal devices or communication devices such as cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other living equipment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Provided is a feature pertaining to a terminal device, a base station device, a method, and an integrated circuit with which it is possible to reduce the complexity of a protocol process and perform communication efficiently. A terminal device communicating with a base station device, the terminal device comprising a reception unit for receiving a user equipment (UE) capability inquiry message, and a transmission unit for notifying the base station device of UE capability information on the basis of the UE capability inquiry message, the UE capability information including information about UE capability pertaining to a service data adaptation protocol (SDAP) layer, and the information about the UE capability pertaining to the SDAP layer including information that indicates whether an uplink SDAP header is supported and/or information that indicates whether a default data wireless bearer is supported.

Description

端末装置、基地局装置、方法、および、集積回路Terminal device, base station device, method, and integrated circuit
　本発明は、端末装置、基地局装置、方法、および、集積回路に関する。本願は、２０１８年８月６日に日本に出願された特願２０１８－１４７６６０号に基づき優先権を主張し、その内容をここに援用する。 << The present invention relates to a terminal device, a base station device, a method, and an integrated circuit. This application claims priority based on Japanese Patent Application No. 2018-147660 for which it applied to Japan on August 6, 2018, and uses the content here.
　セルラ－移動通信の無線アクセス方式および無線ネットワーク（以下、「Ｌｏｎｇ　Ｔｅｒｍ　Ｅｖｏｌｕｔｉｏｎ（ＬＴＥ：登録商標）」、または、「Ｅｖｏｌｖｅｄ　Ｕｎｉｖｅｒｓａｌ　Ｔｅｒｒｅｓｔｒｉａｌ　Ｒａｄｉｏ　Ａｃｃｅｓｓ：ＥＵＴＲＡ」と称する。）、及びコアネットワーク（以下、「Ｅｖｏｌｖｅｄ　Ｐａｃｋｅｔ　Ｃｏｒｅ：ＥＰＣ」）が、第三世代パートナーシッププロジェクト（３ｒｄ　Ｇｅｎｅｒａｔｉｏｎ　Ｐａｒｔｎｅｒｓｈｉｐ　Ｐｒｏｊｅｃｔ：３ＧＰＰ）において検討されている。 Wireless access method and wireless network of cellular mobile communication (hereinafter referred to as “Long Term Evolution (LTE: registered trademark)” or “Evolved Universal Terrestrial Radio Access: EUTRA”) and core network (hereinafter “Evolved”). Packet @ Core: EPC ") is being considered in the third generation partnership project (3rd Generation | Partnership \ Project: 3GPP).
　また、３ＧＰＰにおいて、第５世代のセルラ－システムに向けた無線アクセス方式および無線ネットワーク技術として、ＬＴＥの拡張技術であるＬＴＥ－Ａｄｖａｎｃｅｄ　Ｐｒｏおよび新しい無線アクセス技術であるＮＲ（Ｎｅｗ　Ｒａｄｉｏ　ｔｅｃｈｎｏｌｏｇｙ）の技術検討及び規格策定が行われている（非特許文献１）。また第５世代セルラーシステムに向けたコアネットワークである、５ＧＣ（５　Ｇｅｎｅｒａｔｉｏｎ　Ｃｏｒｅ　Ｎｅｔｗｏｒｋ）の検討も行われている（非特許文献２）。 In 3GPP, as a wireless access method and a wireless network technology for a fifth generation cellular system, a technical study of LTE-Advanced Advanced, which is an extension of LTE, and NR (New Radio Technology), a new wireless access technology. And standards are being formulated (Non-Patent Document 1). Also, 5GC (5 Generation Core Network), which is a core network for the fifth generation cellular system, is being studied (Non-Patent Document 2).
　ＮＲの技術検討の一つとして、ＩＰ（Ｉｎｔｅｒｎｅｔ　Ｐｒｏｔｏｃｏｌ）レイヤ（ｌａｙｅｒ）以上の上位レイヤとＮＲの無線アクセスレイヤとの間のＱｏＳ（Ｑｕａｌｉｔｙ　ｏｆ　Ｓｅｒｖｉｃｅ）管理を行う、無線アクセスレイヤのプロトコルが検討されている。 As one of the technical studies on the NR, a protocol of a wireless access layer which performs QoS (Quality of Service) management between an upper layer above an IP (Internet Protocol) layer and a wireless access layer of the NR is studied. ing.
　しかしながら、上位レイヤと無線アクセスレイヤの間でのＱｏＳ管理が正しく行われない場合、基地局装置と端末装置との通信を効率的に行うことができないという課題があった。 However, when QoS management between the upper layer and the wireless access layer is not performed correctly, there is a problem that communication between the base station device and the terminal device cannot be performed efficiently.
　本発明の一態様は、上記した事情に鑑みてなされたもので、基地局装置との通信を効率的に行うことができる端末装置、基地局装置、該端末装置に用いられる方法、該端末装置に実装される集積回路を提供することを目的の一つとする。 One embodiment of the present invention has been made in view of the above circumstances, and a terminal device, a base station device, a method used for the terminal device, and a terminal device capable of efficiently performing communication with a base station device It is another object of the present invention to provide an integrated circuit mounted on a computer.
　（１）上記の目的を達成するために、本発明の一態様は、以下のような手段を講じた。すなわち、本発明の第１の態様は、基地局装置と通信する端末装置であって、Ｕｓｅｒ　Ｅｑｕｉｐｍｅｎｔ（ＵＥ）能力照会メッセージを受信する受信部と、前記ＵＥ能力照会メッセージに基づきＵＥ能力情報を基地局装置に通知する送信部とを備え、前記ＵＥ能力情報はＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報を含み、　前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトデ－タ無線ベアラをサポートするか否かを示す情報を含む。 (1) In order to achieve the above object, one embodiment of the present invention has the following measures. That is, a first aspect of the present invention is a terminal device that communicates with a base station device, the receiving unit receiving a User @ Equipment (UE) capability inquiry message, and a base station that transmits UE capability information based on the UE capability inquiry message. And a transmitting unit for notifying a station device, wherein the UE capability information includes UE capability information on a Service Data Adaptation Protocol (SDAP) layer, and the UE capability information on the SDAP layer includes an SDAP header for an uplink. It includes information indicating whether or not to support and / or whether to support default data radio bearers.
　（２）本発明の第２の態様は、端末装置と通信する基地局装置であって、ＵＥ能力照会メッセージを送信する送信部と、前記端末装置からＵＥ能力情報を受信する受信部と、前記ＵＥ能力情報に含まれるＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報に基づき、デ－タ無線ベアラの設定を含むＲＲＣ再設定メッセージを生成する処理部とを備え、前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトＤＲＢをサポートするか否かを示す情報を含む。 (2) A second aspect of the present invention is a base station device communicating with a terminal device, wherein the transmitting unit transmits a UE capability inquiry message, the receiving unit receives UE capability information from the terminal device, A processing unit for generating an RRC re-establishment message including a data radio bearer configuration based on UE capability information on a Service Data Adaptation Protocol (SDAP) layer included in the UE capability information; Includes information indicating whether to support the SDAP header for the uplink and / or information indicating whether to support the default DRB.
　（３）本発明の第３の態様は、基地局装置と通信する端末装置に適用される方法であって、Ｕｓｅｒ　Ｅｑｕｉｐｍｅｎｔ（ＵＥ）能力照会メッセージを受信するステップと、前記ＵＥ能力照会メッセージに基づきＵＥ能力情報を基地局装置に通知するステップとを含み、前記ＵＥ能力情報はＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報を含み、　前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトデ－タ無線ベアラをサポートするか否かを示す情報を含む。 (3) A third aspect of the present invention is a method applied to a terminal device communicating with a base station device, the method comprising: receiving a User @ Equipment (UE) capability inquiry message; Notifying the UE capability information to the base station apparatus, wherein the UE capability information includes UE capability information on a Service Data Adaptation Protocol (SDAP) layer, and the UE capability information on the SDAP layer is for uplink. And / or information indicating whether or not to support the default data radio bearer.
　（４）本発明の第４の態様は、端末装置と通信する基地局装置に適用される方法であって、ＵＥ能力照会メッセージを送信するステップと、前記端末装置からＵＥ能力情報を受信するステップと、前記ＵＥ能力情報に含まれるＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報に基づき、デ－タ無線ベアラの設定を含むＲＲＣ再設定メッセージを生成するステップとを含み、前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトＤＲＢをサポートするか否かを示す情報を含む。 (4) A fourth aspect of the present invention is a method applied to a base station apparatus communicating with a terminal apparatus, wherein a step of transmitting a UE capability inquiry message and a step of receiving UE capability information from the terminal apparatus. And generating an RRC reconfiguration message including a data radio bearer configuration based on UE capability information on a Service Data Adaptation Protocol (SDAP) layer included in the UE capability information. The UE capability information includes information indicating whether to support the SDAP header for the uplink and / or information indicating whether to support the default DRB.
　（５）本発明の第５の態様は、基地局装置と通信する端末装置に実装される集積回路であって、Ｕｓｅｒ　Ｅｑｕｉｐｍｅｎｔ（ＵＥ）能力照会メッセージを受信する機能と、　前記ＵＥ能力照会メッセージに基づきＵＥ能力情報を基地局装置に通知する機能とを前記端末装置に対して発揮させ、前記ＵＥ能力情報はＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報を含み、　前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトデ－タ無線ベアラをサポートするか否かを示す情報を含む。 (5) A fifth aspect of the present invention is an integrated circuit implemented in a terminal device that communicates with a base station device, the function of receiving a User @ Equipment (UE) capability inquiry message; And a function of notifying the base station apparatus of UE capability information based on the UE capability information, wherein the UE capability information includes UE capability information relating to a Service Data Adaptation Protocol (SDAP) layer, and a UE capability relating to the SDAP layer. May include information indicating whether to support an SDAP header for the uplink and / or information indicating whether to support a default data radio bearer.
　（６）本発明の第６の態様は、端末装置と通信する基地局装置に実装される集積回路であって、ＵＥ能力照会メッセージを送信する機能と、前記端末装置からＵＥ能力情報を受信する機能と、前記ＵＥ能力情報に含まれるＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報に基づき、デ－タ無線ベアラの設定を含むＲＲＣ再設定メッセージを生成する機能とを前記基地局装置に対いて発揮させ、前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトＤＲＢをサポートするか否かを示す情報を含む。 (6) A sixth aspect of the present invention is an integrated circuit mounted on a base station apparatus that communicates with a terminal apparatus, the function of transmitting a UE capability inquiry message, and receiving UE capability information from the terminal apparatus. The base station apparatus has a function and a function of generating an RRC reconfiguration message including a data radio bearer setting based on UE capability information relating to a Service Data Adaptation Protocol (SDAP) layer included in the UE capability information. The UE capability information for the SDAP layer includes information indicating whether to support an SDAP header for uplink and / or information indicating whether to support a default DRB.
　なお、これらの包括的または具体的な態様は、システム、装置、方法、集積回路、コンピュータプログラム、または、記録媒体で実現されてもよく、システム、装置、方法、集積回路、コンピュータプログラムおよび記録媒体の任意な組み合わせで実現されてもよい。 Note that these comprehensive or specific aspects may be realized by a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, and the system, the apparatus, the method, the integrated circuit, the computer program, and the recording medium May be realized by any combination.
　本発明の一態様によれば、端末装置は、プロトコル処理の複雑さを軽減し、効率的に通信を行うことができる。 According to one embodiment of the present invention, the terminal device can reduce the complexity of the protocol processing and perform efficient communication.
本発明の実施の形態に係る通信システムの概略図。1 is a schematic diagram of a communication system according to an embodiment of the present invention. 本発明の実施の形態における、Ｅ－ＵＴＲＡにおける端末装置と基地局装置のＵＰ及びＣＰのプロトコルスタック図。FIG. 4 is a diagram illustrating a protocol stack of UP and CP of a terminal device and a base station device in E-UTRA according to the embodiment of the present invention. 本発明の実施の形態における、ＮＲにおける端末装置と基地局装置のＵＰ及びＣＰのプロトコルスタック図。FIG. 4 is a diagram illustrating a protocol stack of UP and CP of a terminal device and a base station device in NR in the embodiment of the present invention. 本発明の実施の形態におけるＵＥ能力（ＵＥ　Ｃａｐａｂｉｌｉｔｙ）手順及びＲＲＣコネクション再設定手順のフローの一例を示す図。The figure which shows an example of the flow of UE capability (UE @ Capability) procedure and RRC connection reset procedure in embodiment of this invention. 本発明の実施の形態における端末装置の構成を示すブロック図。FIG. 1 is a block diagram showing a configuration of a terminal device according to an embodiment of the present invention. 本発明の実施の形態における基地局装置の構成を示すブロック図。FIG. 2 is a block diagram illustrating a configuration of a base station device according to the embodiment of the present invention. 本発明の実施の形態における無線ベアラ設定に係る情報、及び情報のＡＳＮ．１（Ａｂｓｔｒａｃｔ　Ｓｙｎｔａｘ　Ｎｏｔａｔｉｏｎ　Ｏｎｅ）記述の一例を示す図。Information related to radio bearer setting according to the embodiment of the present invention, and ASN. 1 is a diagram showing an example of an (Abstract \ Syntax \ Notation \ One) description. 本発明の実施の形態におけるＵＥ能力に係る情報、及び情報のＡＳＮ．１記述の一例を示す図。Information related to UE capability and ASN. The figure which shows an example of 1 description. 本発明の実施の形態におけるＵＥ能力に係る情報、及び情報のＡＳＮ．１記述の別の一例を示す図。Information related to UE capability and ASN. The figure which shows another example of one description.
　以下、本発明の実施の形態について、図面を参照して詳細に説明する。 Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
　ＬＴＥ（およびＬＴＥ－Ａ　Ｐｒｏ）とＮＲは、異なるＲＡＴとして定義されてもよい。またＮＲは、ＬＴＥに含まれる技術として定義されてもよい。ＬＴＥは、ＮＲに含まれる技術として定義されてもよい。また、ＮＲとＭｕｌｔｉ　ＲＡＴ　Ｄｕａｌ　ｃｏｎｎｅｃｔｉｖｉｔｙで接続可能なＬＴＥは、従来のＬＴＥと区別されてもよい。本実施形態はＮＲ、ＬＴＥおよび他のＲＡＴに適用されてよい。以下の説明では、ＬＴＥおよびＮＲに関連する用語を用いて説明するが、他の用語を用いる他の技術において適用されてもよい。また本実施形態でのＥ－ＵＴＲＡという用語は、ＬＴＥという用語に置き換えられても良いし、ＬＴＥという用語はＥ－ＵＴＲＡという用語に置き換えられても良い。 LTE (and LTE-A Pro) and NR may be defined as different RATs. Also, NR may be defined as a technology included in LTE. LTE may be defined as a technology included in NR. Also, LTE connectable with NR and Multi \ RAT \ Dual \ connectivity may be distinguished from conventional LTE. This embodiment may be applied to NR, LTE and other RATs. The following description will be made using terms related to LTE and NR, but may be applied in other technologies using other terms. Further, the term E-UTRA in the present embodiment may be replaced with the term LTE, and the term LTE may be replaced with the term E-UTRA.
　図１は本発明の各実施の形態に係る通信システムの概略図である。 FIG. 1 is a schematic diagram of a communication system according to each embodiment of the present invention.
　Ｅ－ＵＴＲＡ１００は非特許文献３等に記載の無線アクセス技術であり、１つ又は複数の周波数帯域で構成するセルグループ（Ｃｅｌｌ　Ｇｒｏｕｐ：ＣＧ）から成る。ｅＮＢ（Ｅ－ＵＴＲＡＮ　Ｎｏｄｅ　Ｂ）１０２は、Ｅ－ＵＴＲＡの基地局装置である。ＥＰＣ（Ｅｖｏｌｖｅｄ　Ｐａｃｋｅｔ　Ｃｏｒｅ）１０４は、非特許文献１４等に記載のコア網であり、Ｅ－ＵＴＲＡ用コア網として設計された。インタフェース１１２はｅＮＢ１０２とＥＰＣ１０４の間のインタフェース（ｉｎｔｅｒｆａｃｅ）であり、制御信号が通る制御プレーン（Ｃｏｎｔｒｏｌ　Ｐｌａｎｅ：ＣＰ）と、そのユーザデータが通るユーザプレーン（Ｕｓｅｒ　Ｐｌａｎｅ：ＵＰ）が存在する。 E-UTRA100 is a radio access technology 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 an E-UTRA base station apparatus. EPC (Evolved Packet Core) 104 is a core network described in Non-Patent Document 14 and the like, 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 (Control @ Plane: CP) through which control signals pass and a user plane (User @ Plane: UP) through which the user data passes.
　ＮＲ１０６は非特許文献９等に記載の無線アクセス技術であり、１つ又は複数の周波数帯域で構成するセルグループ（Ｃｅｌｌ　Ｇｒｏｕｐ：ＣＧ）から成る。ｇＮＢ（ｇ　Ｎｏｄｅ　Ｂ）１０８は、ＮＲの基地局装置である。５ＧＣ１１０は、非特許文献２等に記載のコア網であり、ＮＲ用コア網として設計されているが、５ＣＧに接続する機能をもつＥ－ＵＴＲＡのコア網として使われても良い。以下Ｅ－ＵＴＲＡとは５ＣＧに接続する機能をもつＥ－ＵＴＲＡを含んでも良い。 The NR 106 is a radio access technology described in Non-Patent Document 9 and the like, and includes a cell group (Cell （Group: CG) configured with one or a plurality of frequency bands. gNB (g Node B) 108 is an NR base station device. The 5GC 110 is a core network described in Non-Patent Document 2 and the like, and is designed as an NR core network, but may be used as an E-UTRA core network having a function of connecting to 5CG. Hereinafter, E-UTRA may include E-UTRA having a function of connecting to 5CG.
　インタフェース１１４はｅＮＢ１０２と５ＧＣ１１０の間のインタフェース、インタフェース１１６はｇＮＢ１０８と５ＧＣ１１０の間のインタフェース、インタフェース１１８はｇＮＢ１０８とＥＰＣ１０４の間のインタフェース、インタフェース１２０はｅＮＢ１０２とｇＮＢ１０８の間のインタフェース、インタフェース１２４はＥＰＣ１０４と５ＧＣ１１０間のインタフェースである。インタフェース１１４、インタフェース１１６、インタフェース１１８、インタフェース１２０、インタフェース１２４はＣＰのみ、又はＵＰのみ、又はＣＰ及びＵＰ両方を通すインタフェースである。また、インタフェース１１４、インタフェース１１６、インタフェース１１８、インタフェース１２０、インタフェース１２４は、通信事業者が提供する通信システムに応じて存在しない場合もある。 An interface 114 is an interface between the eNB 102 and the 5GC 110, an interface 116 is an interface between the gNB 108 and the 5GC 110, an interface 118 is an interface between the gNB 108 and the EPC 104, an interface 120 is an interface between the eNB 102 and the gNB 108, and an interface 124 is an EPC 104 and the 5GC 110 Interface between the two. The interface 114, the interface 116, the interface 118, the interface 120, and the interface 124 are interfaces that pass only the CP, only the UP, or both the CP and the UP. The interface 114, the interface 116, the interface 118, the interface 120, and the interface 124 may not exist depending on the communication system provided by the communication carrier.
　ＵＥ１２２はＮＲに対応、又はＥ－ＵＴＲＡ及びＮＲ両方対応した端末装置（Ｕｓｅｒ　Ｅｑｕｉｐｍｅｎｔ：ＵＥ）である。 The @UE 122 is a terminal device (User @ Equipment: UE) that supports NR or supports both E-UTRA and NR.
　図２は本発明の各実施の形態における、Ｅ－ＵＴＲＡ無線アクセスレイヤにおける端末装置と基地局装置のＵＰ及びＣＰのプロトコルスタック（Ｐｒｏｔｏｃｏｌ　Ｓｔａｃｋ）図である。 FIG. 2 is a diagram showing a protocol stack (Protocol @ Stack) of the UP and CP of the terminal device and the base station device in the E-UTRA radio access layer in each embodiment of the present invention.
　図２（Ａ）はＵＥ１２２がｅＮＢ１０２と通信を行う際に用いるＵＰのプロトコルスタック図である。 FIG. 2A is a UP protocol stack diagram used when the UE 122 communicates with the eNB 102.
　ＰＨＹ（Ｐｈｙｓｉｃａｌ　ｌａｙｅｒ）２００は、無線物理層（無線物理レイヤ）であり、物理チャネル（Ｐｈｙｓｉｃａｌ　Ｃｈａｎｎｅｌ）を利用して上位層（上位レイヤ）に伝送サービスを提供する。ＰＨＹ２００は、後述する上位のＭＡＣ（Ｍｅｄｉｕｍ　Ａｃｃｅｓｓ　Ｃｏｎｔｒｏｌ　ｌａｙｅｒ）２０２とトランスポートチャネル（Ｔｒａｎｓｐｏｒｔ　Ｃｈａｎｎｅｌ）で接続される。トランスポートチャネルを介して、ＭＡＣ２０２とＰＨＹ２００の間でデ－タが移動する。ＵＥ１２２とｅＮＢ１０２のＰＨＹ間において、無線物理チャネルを介してデ－タの送受信が行われる。 $ PHY (Physical @ layer) 200 is a wireless physical layer (wireless physical layer), and provides a transmission service to an upper layer (upper layer) using a physical channel (Physical @ Channel). The PHY 200 is connected to a higher-order MAC (Medium Access Control layer) 202 described later via a transport channel (Transport Channel). Data moves between the MAC 202 and the PHY 200 via the transport channel. Data transmission and reception are performed between the PHY of the UE 122 and the PHY of the eNB 102 via the radio physical channel.
　ＭＡＣ２０２は、多様な論理チャネル（Ｌｏｇｉｃａｌ　Ｃｈａｎｎｅｌ）を多様なトランスポートチャネルにマッピングを行う媒体アクセス制御層（媒体アクセス制御レイヤ）である。ＭＡＣ２０２は、後述する上位のＲＬＣ（Ｒａｄｉｏ　Ｌｉｎｋ　Ｃｏｎｔｒｏｌ　ｌａｙｅｒ）２０４と、論理チャネルで接続される。論理チャネルは、伝送される情報の種類によって大きく分けられ、制御情報を伝送する制御チャネルとユ－ザ情報を伝送するトラフィックチャネルに分けられる。ＭＡＣ２０２は、間欠受送信（ＤＲＸ・ＤＴＸ）を行うためにＰＨＹ２００の制御を行う機能、ランダムアクセス（Ｒａｎｄｏｍ　Ａｃｃｅｓｓ）手順を実行する機能、送信電力の情報を通知する機能、ＨＡＲＱ制御を行う機能などを持つ（非特許文献７）。 The $ MAC 202 is a medium access control layer that maps various logical channels (Logical @ Channel) to various transport channels. The MAC 202 is connected to a higher-order RLC (Radio Link Control layer) 204 described later by a logical channel. Logical channels are roughly 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 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. (Non-Patent Document 7).
　ＲＬＣ２０４は、後述する上位のＰＤＣＰ（Ｐａｃｋｅｔ　Ｄａｔａ　Ｃｏｎｖｅｒｇｅｎｃｅ　Ｐｒｏｔｏｃｏｌ　Ｌａｙｅｒ）２０６から受信したデ－タを分割（Ｓｅｇｍｅｎｔａｔｉｏｎ）し、下位層（下位レイヤ）が適切にデ－タ送信できるようにデ－タサイズを調節する無線リンク制御層（無線リンク制御レイヤ）である。また、ＲＬＣ２００は、各デ－タが要求するＱｏＳ（Ｑｕａｌｉｔｙ　ｏｆ　Ｓｅｒｖｉｃｅ）を保証するための機能も持つ。すなわち、ＲＬＣ２０４は、デ－タの再送制御等の機能を持つ（非特許文献６）。 The RLC 204 divides (segments) data received from a higher-order PDCP (Packet Data Convergence Protocol Protocol) 206 described later, and adjusts the data size so that the lower layer (lower layer) can appropriately transmit data. Wireless link control layer (wireless link control layer). The RLC 200 also has a function to guarantee 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).
　ＰＤＣＰ２０６は、ユーザデータであるＩＰパケット（ＩＰ　Ｐａｃｋｅｔ）を無線区間で効率的に伝送するためのパケットデータ収束プロトコル層（パケットデータ収束プロトコルレイヤ）である。ＰＤＣＰ２０６は、不要な制御情報の圧縮を行うヘッダ圧縮機能を持ってもよい。また、ＰＤＣＰ２０６は、デ－タの暗号化の機能も持ってもよい（非特許文献５）。 $ PDCP 206 is a packet data convergence protocol layer (packet data convergence protocol layer) for efficiently transmitting an IP packet (IP @ Packet) as user data in a wireless section. The PDCP 206 may have a header compression function for compressing unnecessary control information. The PDCP 206 may also have a data encryption function (Non-Patent Document 5).
　なお、ＭＡＣ２０２、ＲＬＣ２０４、ＰＤＣＰ２０６において処理されたデータの事を、それぞれＭＡＣ　ＰＤＵ（Ｐｒｏｔｏｃｏｌ　Ｄａｔａ　Ｕｎｉｔ）、ＲＬＣ　ＰＤＵ、ＰＤＣＰ　ＰＤＵと呼ぶ。また、ＭＡＣ２０２、ＲＬＣ２０４、ＰＤＣＰ２０６に上位層から渡されるデータ、又は上位層に渡すデータの事を、それぞれＭＡＣ　ＳＤＵ（Ｓｅｒｖｉｃｅ　Ｄａｔａ　Ｕｎｉｔ）、ＲＬＣ　ＳＤＵ、ＰＤＣＰ　ＳＤＵと呼ぶ。 The data processed in the MAC 202, the RLC 204, and the PDCP 206 are referred to as a MAC PDU (Protocol Data Unit), an RLC PDU, and a PDCP PDU, respectively. Data passed from the upper layer to the MAC 202, RLC 204, and PDCP 206 or data passed to the upper layer is called MAC @ SDU (Service @ Data @ Unit), RLC @ SDU, and PDCP @ SDU, respectively.
　図２（Ｂ）はＵＥ１２２がｅＮＢ１０２と通信を行う際に用いるＣＰのプロトコルスタック図である。 FIG. 2B is a protocol stack diagram of a CP used when the UE 122 communicates with the eNB 102.
　ＣＰのプロトコルスタックには、ＰＨＹ２００、ＭＡＣ２０２、ＲＬＣ２０４、ＰＤＣＰ２０６に加え、ＲＲＣ（Ｒａｄｉｏ　Ｒｅｓｏｕｒｃｅ　Ｃｏｎｔｒｏｌ　ｌａｙｅｒ）２０８が存在する。ＲＲＣ２０８は、無線ベアラ（Ｒａｄｉｏ　Ｂｅａｒｅｒ：ＲＢ）の設定・再設定などを行い、論理チャネル、トランスポートチャネル及び物理チャネルの制御を行う無線リンク制御層（無線リンク制御レイヤ）である。ＲＢは、シグナリグ無線ベアラ（Ｓｉｇｎａｌｉｎｇ　Ｒａｄｉｏ　Ｂｅａｒｅｒ：ＳＲＢ）とデ－タ無線ベアラ（Ｄａｔａ　Ｒａｄｉｏ　Ｂｅａｒｅｒ：ＤＲＢ）とに分けられてもよく、ＳＲＢは、制御情報であるＲＲＣメッセージを送信する経路として利用されてもよい。ＤＲＢは、ユーザデータを送信する経路として利用されてもよい。ｅＮＢ１０２とＵＥ１２２のＲＲＣ２０８間で各ＲＢの設定が行われてもよい（非特許文献４）。 The $ CP protocol stack includes an RRC (Radio Resource Control layer) 208 in addition to the PHY 200, the MAC 202, the RLC 204, and the PDCP 206. The RRC 208 is a radio link control layer (radio link control layer) that performs setting and resetting of a radio bearer (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 (Signaling Radio Bearer: SRB) and a data radio bearer (Data Radio Radio Bearer: DRB), and the SRB is used as a path for transmitting an RRC message that is control information. You may. 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-described function classification of the MAC 202, the RLC 204, the PDCP 206, and the RRC 208 is an example, and some or all of the functions may not be implemented. In addition, some or all of the functions of each layer may be included in another layer.
　なお、ＩＰレイヤ、及びＩＰレイヤより上のＴＣＰ（Ｔｒａｎｓｍｉｓｓｉｏｎ　Ｃｏｎｔｒｏｌ　Ｐｒｏｔｏｃｏｌ）レイヤ、ＵＤＰ（Ｕｓｅｒ　Ｄａｔａｇｒａｍ　Ｐｒｏｔｏｃｏｌ）レイヤ、アプリケーションレイヤなどは、ＰＤＣＰレイヤの上位レイヤとなる（不図示）。またＲＲＣレイヤやＮＡＳ（ｎｏｎ　Ａｃｃｅｓｓ　Ｓｔｒａｒｕｍ）レイヤもＳＤＡＰレイヤの上位レイヤとなる（不図示）。言い換えれば、ＰＤＣＰレイヤはＲＲＣレイヤ、ＮＡＳレイヤ、ＩＰレイヤ、及びＩＰレイヤより上のＴＣＰ（Ｔｒａｎｓｍｉｓｓｉｏｎ　Ｃｏｎｔｒｏｌ　Ｐｒｏｔｏｃｏｌ）レイヤ、ＵＤＰ（Ｕｓｅｒ　Ｄａｔａｇｒａｍ　Ｐｒｏｔｏｃｏｌ）レイヤ、アプリケーションレイヤの下位レイヤとなる。 Note that the IP layer, the Transmission Control Protocol (TCP) layer above the IP layer, the User Datagram Protocol (UDP) layer, the application layer, and the like are layers higher than the PDCP layer (not shown). An RRC layer and a NAS (non Access String) layer are also upper layers of the SDAP layer (not shown). In other words, the PDCP layer is an RRC layer, a NAS layer, an IP layer, a TCP (Transmission Control Protocol) layer above the IP layer, a UDP (User Datagram Protocol) layer, and a lower layer of an application layer.
　図３は本発明の各実施の形態における、ＮＲ無線アクセスレイヤにおける端末装置と基地局装置のＵＰ及びＣＰのプロトコルスタック（Ｐｒｏｔｏｃｏｌ　Ｓｔａｃｋ）図である。 FIG. 3 is a diagram illustrating a protocol stack (Protocol @ Stack) of UP and CP of the terminal device and the base station device in the NR radio access layer in each embodiment of the present invention.
　図３（Ａ）はＵＥ１２２がｇＮＢ１０８と通信を行う際に用いるＵＰのプロトコルスタック図である。 FIG. 3A is a UP protocol stack diagram used when the UE 122 communicates with the gNB 108.
　ＰＨＹ（Ｐｈｙｓｉｃａｌ　ｌａｙｅｒ）３００は、ＮＲの無線物理層（無線物理レイヤ）であり、物理チャネル（Ｐｈｙｓｉｃａｌ　Ｃｈａｎｎｅｌ）を利用して上位層に伝送サービスを提供してもよい。ＰＨＹ３００は、後述する上位のＭＡＣ（Ｍｅｄｉｕｍ　Ａｃｃｅｓｓ　Ｃｏｎｔｒｏｌ　ｌａｙｅｒ）３０２とトランスポートチャネル（Ｔｒａｎｓｐｏｒｔ　Ｃｈａｎｎｅｌ）で接続されてもよい。トランスポートチャネルを介して、ＭＡＣ３０２とＰＨＹ３００の間でデ－タが移動してもよい。ＵＥ１２２とｇＮＢ１０８のＰＨＹ間において、無線物理チャネルを介してデ－タの送受信が行われてもよい。 $ PHY (Physical @ layer) 300 is a wireless physical layer (wireless physical layer) of NR, and may provide a transmission service to an upper layer using a physical channel (Physical @ Channel). The PHY 300 may be connected to a higher-order MAC (Medium Access Control layer) 302 described later via a transport channel (Transport Channel). Data may move between MAC 302 and PHY 300 via a transport channel. Data transmission and reception may be performed between the UE 122 and the PHY of the gNB 108 via the radio physical channel.
　ＭＡＣ３０２は、多様な論理チャネル（Ｌｏｇｉｃａｌ　Ｃｈａｎｎｅｌ）を多様なトランスポートチャネルにマッピングを行う媒体アクセス制御層（媒体アクセス制御レイヤ）である。ＭＡＣ３０２は、後述する上位のＲＬＣ（Ｒａｄｉｏ　Ｌｉｎｋ　Ｃｏｎｔｒｏｌ　ｌａｙｅｒ）３０４と、論理チャネルで接続されてもよい。論理チャネルは、伝送される情報の種類によって大きく分けられ、制御情報を伝送する制御チャネルとユ－ザ情報を伝送するトラフィックチャネルに分けられてもよい。ＭＡＣ３０２は、間欠受送信（ＤＲＸ・ＤＴＸ）を行うためにＰＨＹ３００の制御を行う機能、ランダムアクセス（Ｒａｎｄｏｍ　Ａｃｃｅｓｓ）手順を実行する機能、送信電力の情報を通知する機能、ＨＡＲＱ制御を行う機能などを持ってもよい（非特許文献１３）。 The $ MAC 302 is a medium access control layer that maps various logical channels (Logical @ Channel) to various transport channels. The MAC 302 may be connected to a higher-level RLC (Radio Link Control layer) 304 described later by 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 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).
　ＲＬＣ３０４は、後述する上位のＰＤＣＰ（Ｐａｃｋｅｔ　Ｄａｔａ　Ｃｏｎｖｅｒｇｅｎｃｅ　Ｐｒｏｔｏｃｏｌ　Ｌａｙｅｒ）２０６から受信したデ－タを分割（Ｓｅｇｍｅｎｔａｔｉｏｎ）し、下位層が適切にデ－タ送信できるようにデ－タサイズを調節する無線リンク制御層（無線リンク制御レイヤ）である。また、ＲＬＣ３０４は、各デ－タが要求するＱｏＳ（Ｑｕａｌｉｔｙ　ｏｆ　Ｓｅｒｖｉｃｅ）を保証するための機能も持っても良い。すなわち、ＲＬＣ３０４は、デ－タの再送制御等の機能を持っても良い（非特許文献１２）。 The RLC 304 divides (segments) data received from a higher-order PDCP (Packet Data Convergence Protocol Protocol) 206 described later, and adjusts the data size so that the lower layer can appropriately transmit the data. Layer (radio link control layer). Further, the RLC 304 may 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).
　ＰＤＣＰ３０６は、ユーザデータであるＩＰパケット（ＩＰ　Ｐａｃｋｅｔ）を無線区間で効率的に伝送するパケットデータ収束プロトコル層（パケットデータ収束プロトコル層）である。ＰＤＣＰ３０６、不要な制御情報の圧縮を行うヘッダ圧縮機能を持ってもよい。また、ＰＤＣＰ３０６は、デ－タの暗号化の機能も持ってもよい（非特許文献１１）。 The $ PDCP 306 is a packet data convergence protocol layer (packet data convergence protocol layer) for efficiently transmitting an IP packet (IP @ Packet) as user data in a wireless section. The PDCP 306 may have a header compression function for compressing unnecessary control information. The PDCP 306 may also have a data encryption function (Non-Patent Document 11).
　ＳＤＡＰ（Ｓｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ）３１０は、コアネットワークから基地局装置を介して端末装置に送られるダウンリンクのＱｏＳフローとＤＲＢとの対応付け（マッピング：ｍａｐｐｉｎｇ）、及び端末装置から基地局装置を介してコアネットワークに送られるアップリンクのＱｏＳフローと、ＤＲＢとのマッピングを行い、マッピングルール情報を格納する機能を持もつ、サービスデータ適応プロトコル層（サービスデータ適応プロトコルレイヤ）である（非特許文献１６）。端末装置が上位レイヤよりＳＤＡＰ　ＳＤＵをＱｏＳフロー情報と共に受け取った際、格納されているＱｏＳフローとＤＲＢとのマッピングルールに基づいて、ＳＤＡＰ　ＳＤＵを該当するＤＲＢに割り当てる。ＱｏＳフローとＤＲＢとのマッピングルールが格納されていない場合、ＳＤＡＰ　ＳＤＵをデフォルト無線ベアラ（デフォルトＤＲＢ）に割り当てても良い。ＱｏＳフローは同じＱｏＳポリシーによって処理される、一つ又は複数のサービスデータフロー（Ｓｅｒｖｉｃｅ　Ｄａｔａ　Ｆｌｏｗ：ＳＤＦ）から成る（非特許文献２）。またＳＤＡＰはダウンリンクＱｏＳフローの情報を基に、アップリンクのＱｏＳフローとＤＲＢとのマッピングを行う、リフレクティブＱｏＳ（Ｒｅｆｌｅｃｔｉｖｅ　ＱｏＳ）の機能を持っても良い。またＱｏＳフローとＤＲＢとの対応付けルールが変更になった場合には、エンドマーカー（Ｅｎｄ　Ｍａｒｋｅｒ）ＰＤＵを作成し、変更前のＤＲＢに送信する事により、ＳＤＡＰ　ＳＤＵの順番通りの配信（ｉｎ－ｓｅｑｕｅｎｃｅ　ｄｅｌｉｖｅｒｙ）を保証しても良い（非特許文献２、非特許文献１６）。 An SDAP (Service Data Adaptation Protocol) 310 associates a downlink QoS flow sent from a core network to a terminal device via a base station device with a DRB (mapping), and transmits the downlink QoS flow from the terminal device to the base station device. A service data adaptation protocol layer (service data adaptation protocol layer) having a function of mapping an uplink QoS flow sent to a core network to a DRB and storing mapping rule information (Non-Patent Document 16) ). When the terminal device receives the SDAP @ SDU together with the QoS flow information from the upper layer, the terminal device allocates the SDAP @ SDU to the corresponding DRB based on the mapping rule between the stored QoS flow and the DRB. When the mapping rule between the QoS flow and the DRB is not stored, the SDAP @ SDU may be assigned to the default radio bearer (default DRB). A QoS flow is composed of one or more service data flows (Service \ Data \ Flow: SDF) that are processed according to the same QoS policy (Non-Patent Document 2). Also, the SDAP may have a reflective QoS (Reflective QoS) function of mapping the uplink QoS flow and the DRB based on the information of the downlink QoS flow. Further, when the association rule between the QoS flow and the DRB is changed, an end marker (End @ Marker) PDU is created and transmitted to the DRB before the change, so that the distribution (in-order) of the SDAP @ SDU is performed. (sequence @ delivery) may be guaranteed (Non-Patent Documents 2 and 16).
　エンドマーカーＰＤＵとは、非特許文献１６に記載のＳＤＡＰ制御ＰＤＵで、ＵＥのＳＤＡＰエンティティが、本エンドマーカーＰＤＵのＱｏＳフロー識別子フィールドに含まれるＱｏＳフロー識別子に対応したＱｏＳフローと、本エンドマーカーＰＤＵが送信された無線ベアラとの対応（ｍａｐｐｉｎｇ）が終了する事を通知するために使われる。 The end marker PDU is an SDAP control PDU described in Non-Patent Document 16, in which the SDAP entity of the UE determines the QoS flow corresponding to the QoS flow identifier included in the QoS flow identifier field of the end marker PDU, and the end marker PDU. Is used to notify that the mapping with the transmitted radio bearer is finished.
　なお、ＩＰレイヤ、及びＩＰレイヤより上のＴＣＰ（Ｔｒａｎｓｍｉｓｓｉｏｎ　Ｃｏｎｔｒｏｌ　Ｐｒｏｔｏｃｏｌ）レイヤ、ＵＤＰ（Ｕｓｅｒ　Ｄａｔａｇｒａｍ　Ｐｒｏｔｏｃｏｌ）レイヤ、アプリケーションレイヤなどは、ＳＤＡＰレイヤの上位レイヤとなる（不図示）。またＲＲＣレイヤやＮＡＳ（ｎｏｎ　Ａｃｃｅｓｓ　Ｓｔｒａｒｕｍ）レイヤもＳＤＡＰレイヤの上位レイヤとなる（不図示）。ＮＡＳレイヤにおいて、サービスデータフローとＱｏＳフローとの対応付が行われる。言い換えれば、ＳＤＡＰレイヤはＲＲＣレイヤ、ＮＡＳレイヤ、ＩＰレイヤ、及びＩＰレイヤより上のＴＣＰ（Ｔｒａｎｓｍｉｓｓｉｏｎ　Ｃｏｎｔｒｏｌ　Ｐｒｏｔｏｃｏｌ）レイヤ、ＵＤＰ（Ｕｓｅｒ　Ｄａｔａｇｒａｍ　Ｐｒｏｔｏｃｏｌ）レイヤ、アプリケーションレイヤの下位レイヤとなる。 Note that the IP layer, the Transmission Control Protocol (TCP) layer above the IP layer, the User Datagram Protocol (UDP) layer, and the application layer are upper layers of the SDAP layer (not shown). An RRC layer and a NAS (non Access String) layer are also upper layers of the SDAP layer (not shown). In the NAS layer, association between the service data flow and the QoS flow is performed. In other words, the SDAP layer is an RRC layer, a NAS layer, an IP layer, a TCP (Transmission Control Protocol) layer above the IP layer, a UDP (User Datagram Protocol) layer, and a lower layer of the application layer.
　なお、ＭＡＣ３０２、ＲＬＣ３０４、ＰＤＣＰ３０６、ＳＤＡＰ３１０において処理されたデータの事を、それぞれＭＡＣ　ＰＤＵ（Ｐｒｏｔｏｃｏｌ　Ｄａｔａ　Ｕｎｉｔ）、ＲＬＣ　ＰＤＵ、ＰＤＣＰ　ＰＤＵ、ＳＤＡＰ　ＰＤＵと呼んでも良い。また、ＭＡＣ２０２、ＲＬＣ２０４、ＰＤＣＰ２０６に上位層から渡されるデータ、又は上位層に渡すデータの事を、それぞれＭＡＣ　ＳＤＵ（Ｓｅｒｖｉｃｅ　Ｄａｔａ　Ｕｎｉｔ）、ＲＬＣ　ＳＤＵ、ＰＤＣＰ　ＳＤＵ、ＳＤＡＰ　ＳＤＵと呼んでも良い。 The data processed in the MAC 302, the RLC 304, the PDCP 306, and the SDAP 310 may be referred to as a MAC PDU (Protocol Data Unit), an RLC PDU, a PDCP PDU, and a SDAP PDU, respectively. Also, the data passed from the upper layer to the MAC 202, the RLC 204, and the PDCP 206 or the data passed to the upper layer may be called 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.
　ＣＰのプロトコルスタックには、ＰＨＹ３００、ＭＡＣ３０２、ＲＬＣ３０４、ＰＤＣＰ３０６に加え、ＲＲＣ（Ｒａｄｉｏ　Ｒｅｓｏｕｒｃｅ　Ｃｏｎｔｒｏｌ　ｌａｙｅｒ）３０８が存在する。ＲＲＣ３０８は、無線ベアラ（Ｒａｄｉｏ　Ｂｅａｒｅｒ：ＲＢ）の設定・再設定などを行い、論理チャネル、トランスポートチャネル及び物理チャネルの制御を行う無線リンク制御層（無線リンク制御レイヤ）である。ＲＢは、シグナリグ無線ベアラ（Ｓｉｇｎａｌｉｎｇ　Ｒａｄｉｏ　Ｂｅａｒｅｒ：ＳＲＢ）とデ－タ無線ベアラ（Ｄａｔａ　Ｒａｄｉｏ　Ｂｅａｒｅｒ：ＤＲＢ）とに分けられてもよく、ＳＲＢは、制御情報であるＲＲＣメッセージを送信する経路として利用されてもよい。ＤＲＢは、ユーザデータを送信する経路として利用されてもよい。ｇＮＢ１０８とＵＥ１２２のＲＲＣ３０８間で各ＲＢの設定が行われてもよい。またＲＢのうちＲＬＣ３０４とＭＡＣ３０２で構成される部分をＲＬＣベアラと呼んでも良い（非特許文献１０）。 The $ CP protocol stack includes an RRC (Radio Resource Control layer) 308 in addition to the PHY 300, the MAC 302, the RLC 304, and the PDCP 306. The RRC 308 is a radio link control layer (radio link control layer) that performs setting and resetting of a radio bearer (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 (Signaling Radio Bearer: SRB) and a data radio bearer (Data Radio Radio Bearer: DRB), and the SRB is used as a path for transmitting an RRC message that is control information. You may. DRB may be used as a route for transmitting user data. Each RB may be set between the gNB 108 and the RRC 308 of the UE 122. Further, a portion of the RB configured by the RLC 304 and the MAC 302 may be called an RLC bearer (Non-Patent Document 10).
　前述のＭＡＣ３０２、ＲＬＣ３０４、ＰＤＣＰ３０６、ＳＤＡＰ３１０、及びＲＲＣ３０８の機能分類は一例であり、各機能の一部あるいは全部が実装されなくてもよい。また、各層（各レイヤ）の機能の一部あるいは全部が他の層（レイヤ）に含まれてもよい。 The above-described function classifications of the MAC 302, the RLC 304, the PDCP 306, the SDAP 310, and the RRC 308 are merely examples, and some or all of the functions may not be implemented. In addition, some or all of the functions of each layer (each layer) may be included in another layer (layer).
　なお、本発明の各実施の形態では、以下Ｅ－ＵＴＲＡのプロトコルとＮＲのプロトコルを区別するため、ＭＡＣ２０２、ＲＬＣ２０４、ＰＤＣＰ２０６、及びＲＲＣ２０８を、それぞれＥ－ＵＴＲＡ用ＭＡＣ又はＬＴＥ用ＭＡＣ、Ｅ－ＵＴＲＡ用ＲＬＣ又はＬＴＥ用ＲＬＣ、Ｅ－ＵＴＲＡ用ＰＤＣＰ又はＬＴＥ用ＰＤＣＰ、及びＥ－ＵＴＲＡ用ＲＲＣ又はＬＴＥ用ＲＲＣと呼ぶ事もある。また、ＭＡＣ３０２、ＲＬＣ３０４、ＰＤＣＰ３０６、ＲＲＣ３０８を、それぞれＮＲ用ＭＡＣ、ＮＲ用ＲＬＣ、ＮＲ用ＲＬＣ、及びＮＲ用ＲＲＣと呼ぶ事もある。又は、Ｅ－ＵＴＲＡ　ＰＤＣＰ又はＬＴＥ　ＰＤＣＰ、ＮＲ　ＰＤＣＰなどとスペースを用いて記述する場合もある。 In the embodiments of the present invention, the MAC 202, the RLC 204, the PDCP 206, and the RRC 208 are respectively referred to as an E-UTRA MAC or an LTE MAC, an E-UTRA RLC or LTE RLC, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE. Also, the MAC 302, the RLC 304, the PDCP 306, and the RRC 308 may be referred to as an NR MAC, an NR RLC, an NR RLC, and an NR RRC, respectively. Alternatively, the space may be described using a space such as E-UTRA @ PDCP, LTE @ PDCP, or NR @ PDCP.
　また、図１に示す通り、ｅＮＢ１０２、ｇＮＢ１０８、ＥＰＣ１０４、５ＧＣ１１０は、インタフェース１１２、インタフェース１１６、インタフェース１１８、インタフェース１２０、及びインタフェース１１４を介して繋がってもよい。このため、多様な通信システムに対応するため、図２のＲＲＣ２０８は、図３のＲＲＣ３０８に置き換えられてもよい。また図２のＰＤＣＰ２０６は、図３のＰＤＣＰ３０６に置き換えられても良い。また、図３のＲＲＣ３０８は、図２のＲＲＣ２０８の機能を含んでも良い。また図３のＰＤＣＰ３０６は、図２のＰＤＣＰ２０６であっても良い。 As shown in FIG. 1, the eNB 102, the gNB 108, the EPC 104, and the 5GC 110 may be connected via an interface 112, an interface 116, an interface 118, an interface 120, and an interface 114. Therefore, in order to support various communication systems, the RRC 208 of FIG. 2 may be replaced with the RRC 308 of FIG. Further, the PDCP 206 in FIG. 2 may be replaced with the PDCP 306 in FIG. Further, the RRC 308 in FIG. 3 may include the function of the RRC 208 in FIG. Further, the PDCP 306 in FIG. 3 may be the PDCP 206 in FIG.
　（実施の形態）
　図１から図９を用いて、本発明の実施の形態を説明する。 (Embodiment)
An embodiment of the present invention will be described with reference to FIGS.
　図４は本発明の実施の形態におけるＵＥ能力（ＵＥ　Ｃａｐａｂｉｌｉｔｙ）手順及びＲＲＣ再設定手順のフローの一例を示す図である。なお。ＲＲＣ再設定手順はＲＲＣコネクション再設定手順であっても良い。 FIG. 4 is a diagram showing an example of a flow of a UE capability (UE Capability) procedure and an RRC reset procedure in the embodiment of the present invention. In addition. The RRC reset procedure may be an RRC connection reset procedure.
　ＵＥ能力（ＵＥ　Ｃａｐａｂｉｌｉｔｙ）手順（ＵＥ　ｃａｐａｂｉｌｉｔｙ　ｔｒａｎｓｆｅｒ）は、ＬＴＥおよび／またはＮＲにおける、ＵＥ１２２の無線アクセス能力（Ｒａｄｉｏ　ａｃｃｅｓｓ　ｃａｐａｂｉｌｉｔｙ）情報をＵＥ１２２からネットワークに転送（Ｔｒａｎｓｆｅｒ）するために用いられる手段である。 The UE Capability procedure is a means used to transfer the Radio Access capability information of the UE 122 from the UE 122 to the network in LTE and / or NR.
　ＲＲＣ再設定手順（ＲＲＣ　Ｒｅｃｏｎｆｉｇｕｒａｔｉｏｎ）は、非特許文献１０に記載の、ＮＲにおけるＲＢの確立、変更、及び解放、及びセカンダリセルの、変更、解放等を行う他、ハンドオーバ（同期を伴う再設定）及び測定（Ｍｅｓｕｒｅｍｅｎｔ）等のために用いられる手順である。一方ＲＲＣコネクション再設定手順（ＲＲＣ　Ｃｏｎｎｅｃｔｉｏｎ　Ｒｅｃｏｎｆｉｇｕｒａｔｉｏｎ）は、非特許文献４に記載の、ＬＴＥにおけるＲＢの確立、変更、及び解放、及びセカンダリセルの、変更、解放等を行う他、ハンドオーバ及び測定（Ｍｅｓｕｒｅｍｅｎｔ）等のために用いられる手順である。またＲＲＣコネクション再設定手順は、ＭＲ－ＤＣにおいて、特にコア網がＥＰＣ１０４で、マスターノードがｅＮＢ１０２である場合のＭＲ－ＤＣである、ＥＮ－ＤＣ（Ｅ－ＵＴＲＡ－ＮＲ　Ｄｕａｌ　Ｃｏｎｎｅｃｔｉｖｉｔｙ）、及びコア網が５ＧＣ１１０で、マスターノードがｅＮＢ１０２（拡張型ｅＮＢ１０２とも称する）である場合のＭＲ－ＤＣである、ＮＧＥＮ－ＤＣ（ＮＧ－ＲＡＮ　Ｅ－ＵＴＲＡ－ＮＲ　Ｄｕａｌ　Ｃｏｎｎｅｃｔｉｖｉｔｙ）である場合には、ＲＲＣコネクション再設定手順は、ＬＴＥだけでなく、非特許文献１０に記載の、ＮＲにおけるＲＢの確立、変更、及び解放、及びセカンダリセルの、変更、解放等の一部を行う他、ハンドオーバ及び測定（Ｍｅｓｕｒｅｍｅｎｔ）等の一部を行うためにも用いられる。本発明の各実施の形態では、説明が煩雑になることを避けるために、ＲＲＣ再設定手順という名称を用いて説明し、基地局装置としてｇＮＢ１０８を用いて説明する。 The RRC reconfiguration procedure (RRC @ Reconfiguration) performs establishment, change, and release of RB in NR and change, release, and the like of a secondary cell described in Non-Patent Document 10, and handover (reconfiguration with synchronization). And a procedure used for measurement and the like. On the other hand, the RRC connection reconfiguration procedure (RRC Connection Reconfiguration) performs establishment, change, and release of an RB in LTE and change, release, and the like of LTE in LTE, as well as handover and measurement (Measurement). )). The RRC connection resetting procedure is performed in the MR-DC, particularly when the core network is the EPC 104 and the master node is the eNB 102, the EN-DC (E-UTRA-NR @ Dual Connectivity) and the core network. Is the 5GC 110 and the MR-DC when the master node is the eNB 102 (also referred to as the extended eNB 102). If the NGEN-DC (NG-RAN @ E-UTRA-NR @ Dual @ Connectivity), the RRC connection is reconfigured. The procedure includes not only LTE, but also part of establishment, change, and release of RB in NR, and change and release of a secondary cell described in Non-Patent Document 10, and handover and measurement (Measurement). Also used to do part of It is. In each embodiment of the present invention, in order to avoid complicating the description, the description will be made using the name of RRC reconfiguration procedure, and the description will be made using gNB 108 as the base station apparatus.
　ＵＥ能力手順において、ｇＮＢ１０８はＵＥ１２２にＵＥ能力（ＵＥ　Ｃａｐａｂｉｌｉｔｙ）を照会するためのＵＥ能力照会（ＵＥＣａｐａｂｉｌｉｔｙＥｎｑｕｉｒｙ）メッセージをＵＥ１２２に送信する（ステップＳ４００）。ＵＥ１２２はｇＮＢ１０８より受信したＵＥ能力照会に基づき、ＵＥ能力情報（ＵＥＣａｐａｂｉｌｉｔｙＩｎｆｏｒｍａｉｏｎ）メッセージを作成し、ｇＮＢ１０８へ送信する（ステップＳ４０２）。なおＵＥ能力照会メッセージやＵＥ能力情報メッセージなどのメッセージは他の名称であっても良い。 In the UE capability procedure, the gNB 108 transmits a UE capability inquiry (UECapabilityEnquiry) message to the UE 122 to inquire the UE 122 of the UE capability (UE @ Capability) (step S400). The UE 122 creates a UE capability information (UE CapabilityInformation) message based on the UE capability inquiry received from the gNB 108, and transmits the message to the gNB 108 (step S402). Note that messages such as the UE capability inquiry message and the UE capability information message may have other names.
　次にＲＲＣ再設定手順において、ｇＮＢはＵＥ能力手順において取得したＵＥ能力情報に基づいてＲＲＣ再設定メッセージ（ＲＲＣＲｅｃｏｎｆｉｇｒａｔｉｏｎ）を作成し、ＵＥ１２２へ送信する（ステップＳ４０４）。ＵＥ１２２は、ＲＲＣ再設定メッセージに含まれる、後述する情報要素に従って各種設定、例えば無線ベアラの設定や、ＳＤＡＰの設定などの処理を行う。ステップＳ４０４の後、ＵＥ１２２はｇＮＢ１０８に、ＲＲＣ再設定完了メッセージ（ＲＲＣＲｅｃｏｎｆｉｇｒａｔｉｏｎＣｏｍｐｌｅｔｅ）などを送っても良い（不図示）。なお、ＲＲＣ再設定メッセージはＲＲＣ再設定と言い換えても良く、ＲＲＣ再設定完了メッセージはＲＲＣ再設定完了と言いかえても良い。 Next, in the RRC reconfiguration procedure, the gNB creates an RRC reconfiguration message (RRCReconfiguration) based on the UE capability information acquired in the UE capability procedure, and transmits the message to the UE 122 (step S404). The UE 122 performs various settings, for example, a setting of a radio bearer, a setting of an SDAP, and the like, according to information elements included in the RRC reconfiguration message, which will be described later. After step S404, the UE 122 may send an RRC reconfiguration completion message (RRCReconfigurationComplete) or the like to the gNB 108 (not shown). Note that the RRC reconfiguration message may be rephrased as RRC reconfiguration, and the RRC reconfiguration complete message may be rephrased as RRC reconfiguration complete.
　図５は本発明の実施の形態における端末装置（ＵＥ１２２）の構成を示すブロック図である。なお、説明が煩雑になることを避けるために、図５では、本発明の一態様と密接に関連する主な構成部のみを示す。 FIG. 5 is a block diagram showing a configuration of the terminal device (UE 122) according to the embodiment of the present invention. Note that FIG. 5 illustrates only main components which are closely related to one embodiment of the present invention in order to avoid complexity of description.
　図５に示すＵＥ１２２は、ｇＮＢ１０８よりＵＥ能力照会メッセージ、及びＲＲＣ再設定メッセージ等を受信する受信部５００、及び受信したメッセージに含まれる各種情報要素（ＩＥ：Ｉｎｆｏｒｍａｔｉｏｎ　Ｅｌｅｍｅｎｔ）及び各種条件等に従って処理を行う処理部５０２、ｇＮＢ１０８へＵＥ能力情報メッセージ等を送信する送信部５０４から成る。また様々な条件に基づき各部の動作を制御する制御部を別途備えてもよい。 The UE 122 illustrated in FIG. 5 performs processing in accordance with the receiving unit 500 that receives a UE capability inquiry message, an RRC reconfiguration message, and the like from the gNB 108, and various information elements (IE: Information @ Element) and various conditions included in the received message. And a transmitting unit 504 for transmitting a UE capability information message and the like to the gNB 108. Further, a control unit for controlling the operation of each unit based on various conditions may be separately provided.
　図６は本発明の実施の形態における基地局装置（ｇＮＢ１０８）の構成を示すブロック図である。なお、説明が煩雑になることを避けるために、図６では、本発明の一態様と密接に関連する主な構成部のみを示す。 FIG. 6 is a block diagram showing a configuration of the base station apparatus (gNB 108) according to the embodiment of the present invention. Note that FIG. 6 illustrates only main components which are closely related to one embodiment of the present invention in order to avoid a complicated description.
　図６に示すｇＮＢ１０８は、ＵＥ１２２へＵＥ能力照会メッセージ、及びＲＲＣ再設定メッセージ等を送信する送信部６００、及び各種情報要素（ＩＥ：Ｉｎｆｏｒｍａｔｉｏｎ　Ｅｌｅｍｅｎｔ）を含めたメッセージを作成し、ＵＥ１２２に送信する事により、ＵＥ１２２の処理部５０２に処理を行わせる処理部６０２、及びＵＥ１２２よりＵＥ能力情報を受信する受信部６０４から成る。なお、図６に示す構成は、ｅＮＢ１０２に適応されても良い。ｅＮＢ１０２に適応される場合、送信部６００よりＵＥ１２２へ送信されるメッセージはＲＲＣコネクション再設定メッセージであっても良い。また様々な条件に基づき各部の動作を制御する制御部を別途備えてもよい。 The gNB 108 illustrated in FIG. 6 creates a message including various information elements (IE: Information @ Element) and transmits the UE capability inquiry message and the RRC reset message to the UE 122. , A processing unit 602 that causes the processing unit 502 of the UE 122 to perform processing, and a receiving unit 604 that receives UE capability information from the UE 122. Note that the configuration illustrated in FIG. 6 may be applied to the eNB 102. When applied to the eNB 102, the message transmitted from the transmitting unit 600 to the UE 122 may be an RRC connection reconfiguration message. Further, a control unit for controlling the operation of each unit based on various conditions may be separately provided.
　図７は本発明の実施の形態において、図４におけるＲＲＣ再設定メッセージに含まれるフィールドを表すＡＳＮ．１（Ａｂｓｔｒａｃｔ　Ｓｙｎｔａｘ　Ｎｏｔａｔｉｏｎ　Ｏｎｅ）記述の一例である。３ＧＰＰにおいて、ＲＲＣに係る仕様書（非特許文献４、非特許文献１０）は、ＲＲＣに係るメッセージ、及び情報要素（Ｉｎｆｏｒｍａｔｉｏｎ　Ｅｌｅｍｅｎｔ：ＩＥ）等をＡＳＮ．１を用いて記述する。ＲＲＣに係るメッセージおよび／または情報要素は、一つまたは複数のフィールドおよびフィールドの値（Ｖａｌｕｅ）を含んで構成される。フィールドの値は、整数、バイト列、リストなどの他に、他の情報要素をとることができる。ＲＲＣに係るメッセージおよび／または情報要素の各フィールドの値が情報要素で示される場合、本願の実施形態においては、「フィールド」を「情報要素」と置き換えて説明する場合がある。図７のＡＳＮ．１の例で、＜略＞及び＜中略＞とは、ＡＳＮ．１の表記の一部ではなく、他の情報を省略している事を示す。なお＜略＞又は＜中略＞という記載の無い所でも、フィールドが省略されていても良い。なお図７におけるＡＳＮ．１の例はＡＳＮ．１表記方法に正しく従ったものではなく、本発明の一態様におけるＲＲＣ再設定のパラメータの一例を表記したものであり、他の名称や他の表記が使われても良い。また図７におけるＡＳＮ．１の例は、説明が煩雑になることを避けるために、本発明の一態様と密接に関連する主な情報に関する例のみを示す。なお、他の明示的な説明が無い限り、本願の実施形態における他のＡＳＮ．１記述についても上記説明が適用される。 FIG. 7 shows an embodiment of the present invention, in which ASN. Represents a field included in the RRC reconfiguration message in FIG. 1 (Abstract \ Syntax \ Notation \ One) description. In 3GPP, specifications related to RRC (Non-patent Document 4 and Non-Patent Document 10) include messages related to RRC, information elements (Information @ Element: IE), and the like as ASN. This is described using 1. The message and / or information element related to the RRC includes one or more fields and a value of the field (Value). Field values can take other information elements besides integers, byte strings, lists, and the like. When the value of each field of the message and / or the information element related to the RRC is indicated by the information element, in the embodiment of the present application, the description may be made by replacing the “field” with the “information element”. The ASN. In the example of <1>, <abbreviation> and <omission> are ASN. It is not part of the notation of 1 but indicates that other information is omitted. Fields may be omitted even where there is no description of <omitted> or <omitted>. Note that the ASN. 1 is ASN. It does not follow the one notation method correctly, but is an example of RRC reset parameters in one embodiment of the present invention, and other names or other notations may be used. Also, the ASN. The example 1 shows only an example related to main information which is closely related to one embodiment of the present invention in order to avoid a complicated description. Note that, unless otherwise explicitly described, other ASN. The above description also applies to one description.
　図７においてＤＲＢ－ＴｏＡｄｄＭｏｄＬｉｓｔ又はＤＲＢＴｏＡｄｄＭｏｄで表される情報要素は、追加又は変更するＤＲＢ（データ無線ベアラ）の設定を示す情報のリストであっても良く、本発明の実施の形態では無線ベアラ設定情報要素又はデータ無線ベアラ情報要素と言い換える事もある。 In FIG. 7, the information element represented by DRB-ToAddModList or DRBToAddMod may be a list of information indicating the setting of a DRB (data radio bearer) to be added or changed, and in the embodiment of the present invention, the radio bearer setting information Element or data radio bearer information element.
　無線ベアラ設定情報要素の中の、ＤＲＢ－Ｉｄｅｎｔｉｔｙで表される情報要素は、追加又は変更するＤＲＢのＤＲＢ識別子の情報であり、本発明の実施の形態では無線ベアラ識別子情報要素、またはデータ無線ベアラ識別子情報要素と言い換える事もある。図７の例では１から３２の整数値としているが、別の値を取っても良い。ＤＣの場合、ＤＲＢ識別子は、ＵＥ１２２のスコープ内で固有である。 The information element represented by DRB-Identity in the radio bearer setting information element is information on a DRB identifier of a DRB to be added or changed, and in the embodiment of the present invention, a radio bearer identifier information element or a data radio bearer. It may be rephrased as an identifier information element. In the example of FIG. 7, an integer value of 1 to 32 is used, but another value may be used. For DC, the DRB identifier is unique within the scope of UE 122.
　無線ベアラ設定情報要素の中の、ｃｎＡｓｓｏｃｉａｔｉｏｎで表される情報要素は、コア網にＥＰＣ１０４を用いるか、又は５ＧＣ１１０を用いるかを示す情報要素であっても良く、本発明の実施の形態ではコア網関連付け情報要素と言い換える事もある。即ち、ＵＥ１２２がＥＰＣと接続する際にはＤＲＢが、ｃｎＡｓｓｏｃｉａｔｉｏｎ中のＥＰＳベアラ識別子情報要素（ｅｐｓ－ＢｅａｒｅｒＩｄｅｎｔｉｔｙ）、又はＥＰＳベアラ識別子情報要素の値であるＥＰＳベアラ識別子に関連付けられ、ＵＥ１２２が５ＧＣ１１０と接続する際には、ＤＲＢが、後述のＳＤＡＰ設定情報要素（ｓｄａｐ－Ｃｏｎｆｉｇ）に従って設定されるＳＤＡＰエンティティ、又はＳＤＡＰ設定情報要素に含まれる、後述のＰＤＵセッション情報要素、又はＰＤＵセッション情報要素の値であるＰＤＵセッション識別子に関連付けられるようにしてもよい。即ち、ｃｎＡｓｓｏｃｉａｔｉｏｎで表される情報には、コア網にＥＰＣ１０４を用いる場合にはＥＰＳベアラ識別子情報要素（ｅｐｓ－ＢｅａｒｅｒＩｄｅｎｔｉｔｙ）を含み、コア網５ＧＣ１１０を用いる場合はＳＤＡＰ設定を示す情報要素（ｓｄａｐ－Ｃｏｎｆｉｇ）を含んでも良い。 The information element represented by cnAssociation in the radio bearer setting information element may be an information element indicating whether to use the EPC 104 or the 5GC 110 for the core network. It may be rephrased as an association information element. That is, when the UE 122 connects to the EPC, the DRB is associated with the EPS bearer identifier information element (eps-BearerIdentity) during cnAssociation or the EPS bearer identifier that is the value of the EPS bearer identifier information element, and the UE 122 connects to the 5GC 110. In doing so, the DRB is a SDAP entity set according to a later-described SDAP setting information element (sdap-Config) or a PDU session information element or a PDU session information element value included in the SDAP setting information element. It may be associated with a certain PDU session identifier. That is, the information represented by cnAssociation includes an EPS bearer identifier information element (eps-BearerIdentity) when the EPC 104 is used for the core network, and an information element (sdap-Config) indicating the SDAP setting when the core network 5GC110 is used. ) May be included.
　ｓｄａｐ－Ｃｏｎｆｉｇで表される情報要素は、コア網が５ＧＣ１１０であった場合に、ＱｏＳフローとＤＲＢの対応（ｍａｐ）方法を決定する、ＳＤＡＰエンティティの設定又は再設定に関する情報であってもよく、本発明の実施の形態ではＳＤＡＰ設定情報要素と言い換える事もある。 The information element represented by sdap-Config may be information on setting or resetting of an SDAP entity that determines a method of mapping a QoS flow and a DRB when the core network is 5GC110, In the embodiment of the present invention, it may be rephrased as an SDAP setting information element.
　ＳＤＡＰ設定情報要素に含まれる、ｐｄｕ－ｓｅｓｓｉｏｎ又はＰＤＵ－ＳｅｓｓｉｏｎＩＤで示される情報要素は、本ＳＤＡＰ設定情報要素を含む無線ベアラ設定情報要素に含まれる、無線ベアラ識別子情報要素の値に対応する無線ベアラと対応（ｍａｐ）付けられるＱｏＳフローが所属する、非特許文献２に記載のＰＤＵセッションの識別子でも良く、本発明の実施の形態ではＰＤＵセッション情報要素と言い換える事もある。ＰＤＵセッション情報要素の値は負でない整数であっても良い。 The information element indicated by pdu-session or PDU-Session ID included in the SDAP setting information element is a radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element The identifier of the PDU session described in Non-Patent Document 2 to which the QoS flow assigned to (map) belongs may be referred to. In the embodiment of the present invention, it may be rephrased as a PDU session information element. The value of the PDU session information element may be a non-negative integer.
　またＳＤＡＰ設定情報要素に含まれるｓｄａｐ－ＨｅａｄｅｒＤＬで示される情報要素は、本ＳＤＡＰ設定情報要素を含む無線ベアラ設定情報要素に含まれる、無線ベアラ識別子情報要素の値に対応する無線ベアラにダウンリンクＳＤＡＰヘッダが存在するか否かを示す情報要素であってもよく、本発明の実施の形態ではダウンリンクヘッダ情報要素と言い換える事も有る。 The information element indicated by sdap-HeaderDL included in the SDAP setting information element is a downlink SDAP to the radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element. It may be an information element indicating whether or not a header exists, and may be rephrased as a downlink header information element in the embodiment of the present invention.
　またＳＤＡＰ設定情報要素に含まれるｓｄａｐ－ＨｅａｄｅｒＵＬで示される情報要素は、本ＳＤＡＰ設定情報要素を含む無線ベアラ設定情報要素に含まれる、無線ベアラ識別子情報要素の値に対応する無線ベアラにアップリンクＳＤＡＰヘッダが存在するか否かを示す情報要素であってもよく、本発明の実施の形態ではアップリンク情報要素と言い換える事も有る。 The information element indicated by sdap-HeaderUL included in the SDAP setting information element is an uplink SDAP to a radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element. It may be an information element indicating whether a header exists or not, and may be rephrased as an uplink information element in the embodiment of the present invention.
　またＳＤＡＰ設定情報要素に含まれるｄｅｆａｕｌＤＲＢで示される情報要素は、本ＳＤＡＰ設定情報要素を含む無線ベアラ設定情報要素に含まれる、無線ベアラ識別子情報要素の値に対応する無線ベアラが、本ＳＤＡＰ設定情報要素に含まれるＰＤＵＰＤＵセッション情報要素に対応するＰＤＵセッションのデフォルト無線ベアラであるか否かを示す情報要素であってもよく、本発明の実施の形態ではデフォルトベアラ情報要素と言い換える事も有る。同じＰＤＵセッション情報要素の値を含むＳＤＡＰ設定情報要素の中で、多くとも１つＳＤＡＰ設定情報要素に含まれるデフォルトベアラ情報要素が「真（ＴＲＵＥ）」と設定され、他のＳＤＡＰ設定情報要素に含まれるデフォルトベアラ情報要素は「偽（ＦＡＬＳＥ）」と設定されても良い。 The information element indicated by defaultDRB included in the SDAP setting information element is a radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element. It may be an information element indicating whether or not the PDU is a default radio bearer of a PDU session corresponding to the PDU PDU session information element included in the element. In the embodiment of the present invention, the information element may be referred to as a default bearer information element. Among the SDAP setting information elements including the value of the same PDU session information element, at most one of the default bearer information elements included in the SDAP setting information element is set to “TRUE”, and the other The included default bearer information element may be set to “FALSE”.
　ＳＤＡＰ設定情報要素に含まれる、ｍａｐｐｅｄＱｏＳ－ＦｌｏｗｓＴｏＡｄｄで示される情報要素は、本ＳＤＡＰ設定情報要素を含む無線ベアラ設定情報要素に含まれる、無線ベアラ識別子情報要素の値に対応する無線ベアラに対応（ｍａｐ）させる、又は追加で対応（ｍａｐ）させる、ＱｏＳフローの、後述のＱｏＳフロー識別子（ＱＦＩ：ＱｏＳ　Ｆｌｏｗ　Ｉｄｅｎｔｉｔｙ）情報要素のリストを示す情報であっても良く、本発明の実施の形態では追加するＱｏＳフロー情報要素と言い換える事もある。上述のＱｏＳフローは本ＳＤＡＰ設定情報要素に含まれるＰＤＵセッション情報要素が示すＰＤＵセッションのＱｏＳフローであっても良い。 The information element indicated by mappedQoS-FlowsToAdd included in the SDAP setting information element corresponds to the radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element (map ), Or information indicating a list of QoS flow identifier (QFI: QoS @ Flow @ Identity) information elements of a QoS flow to be added (mapped), which will be added in the embodiment of the present invention. It may be paraphrased as a QoS flow information element. The above-mentioned QoS flow may be a QoS flow of the PDU session indicated by the PDU session information element included in the present SDAP setting information element.
　また、ＳＤＡＰ設定情報要素に含まれる、ｍａｐｐｅｄＱｏＳ－ＦｌｏｗｓＴｏＲｅｌｅａｓｅで示される情報要素は、本ＳＤＡＰ設定情報要素を含む無線ベアラ設定情報要素に含まれる、無線ベアラ識別子情報要素の値に対応する無線ベアラに対応（ｍａｐ）しているＱｏＳフローのうち、対応関係を解放するＱｏＳフローの、後述のＱｏＳフロー識別子（ＱＦＩ：ＱｏＳ　Ｆｌｏｗ　Ｉｄｅｎｔｉｔｙ）情報要素のリストを示す情報であっても良く、本発明の実施の形態では解放するＱｏＳフロー情報要素と言い換える事もある。上述のＱｏＳフローは本ＳＤＡＰ設定情報要素に含まれるＰＤＵセッション情報要素が示すＰＤＵセッションのＱｏＳフローであっても良い。 The information element indicated by mappedQoS-FlowsToRelease included in the SDAP setting information element corresponds to the radio bearer corresponding to the value of the radio bearer identifier information element included in the radio bearer setting information element including the present SDAP setting information element. The information may be information indicating a list of QoS flow identifiers (QFI: QoS @ Flow @ Identity) information elements of the QoS flows for which the correspondence is released among the (mapped) QoS flows, according to an embodiment of the present invention. In the embodiment, it may be paraphrased as a QoS flow information element to be released. The above-mentioned QoS flow may be a QoS flow of the PDU session indicated by the PDU session information element included in the present SDAP setting information element.
　ＱＦＩで示される情報要素は、非特許文献２に記載の、ＱｏＳフローを一意に識別するＱｏＳフロー識別子であってもよく、本発明の実施の形態ではＱｏＳフロー識別子情報要素と言い換える事もある。ＱｏＳフロー識別子情報要素の値は負でない整数であっても良い。またＱｏＳフロー識別子情報要素の値はＰＤＵセッションに対し一意であっても良い。 The information element indicated by QFI may be a QoS flow identifier that uniquely identifies a QoS flow described in Non-Patent Document 2, and may be rephrased as a QoS flow identifier information element in the embodiment of the present invention. The value of the QoS flow identifier information element may be a non-negative integer. Also, the value of the QoS flow identifier information element may be unique for the PDU session.
　なお、ＳＤＡＰ設定情報要素には上述の情報要素の他に、ＡＳリフレクティブＱｏＳを行う事を行うか否かに関する情報要素を含んでも良い。またＳＤＡＰ設定情報要素には上述の情報要素の他に、ＮＡＳリフレクティブＱｏＳを行う事を行うか否かに関する情報要素を含んでも良い。また、ＳＤＡＰ設定情報要素には上述の情報要素の他に、デフォルトＤＲＢをサポートするか否かに関する情報要素を含んでも良い。また、ＳＤＡＰ設定情報要素には上述の情報要素の他に、複数のＱｏＳフローを一つのＤＲＢにマッピングすることをサポートするか否かに関する情報要素を含んでも良い。 ＳＤIn addition, the SDAP setting information element may include an information element regarding whether or not to perform AS reflective QoS in addition to the above-described information element. In addition, the SDAP setting information element may include an information element related to whether or not to perform NAS reflective QoS in addition to the above-described information element. Further, the SDAP setting information element may include an information element related to whether or not to support the default DRB, in addition to the above-described information element. In addition, the SDAP setting information element may include, in addition to the above-described information elements, an information element regarding whether to support mapping of a plurality of QoS flows to one DRB.
　ＡＳリフレクティブＱｏＳとは、非特許文献１６に記載の通りダウンリンクヘッダ情報要素によりダウンリンクＳＤＡＰヘッダが設定された無線ベアラの下位レイヤよりダウンリンクＳＤＡＰ　ＰＤＵを受け取った時、ＳＤＡＰヘッダのフィールドで、ＱｏＳフローと無線ベアラとの対応（ｍａｐｐｉｎｇ）情報の更新が必要か否かを示すＲＤＩ（Ｒｅｆｌｅｃｔｉｖｅ　ＱｏＳ　ｆｌｏｗ　ｔｏ　ＤＲＢ　ｍａｐｐｉｎｇ　Ｉｎｄｉｃａｔｉｏｎ）フィールドが「１」に設定されている場合に、ＳＤＡＰヘッダのＱｏＳフロー識別子フィールドを処理してＱｏＳフローを特定し、本ダウンリンクＳＤＡＰ　ＰＤＵのＱｏＳフローと無線ベアラとの対応情報を、アップリンクのＱｏＳフローと無線ベアラとの対応情報として格納する機能である。 As described in Non-Patent Document 16, the AS reflective QoS is a QoS field in the SDAP header when a downlink SDAP @ PDU is received from a lower layer of a radio bearer in which a downlink SDAP header is set by a downlink header information element. The QoS flow identifier field of the SDP header when the RDI (Reflective QoS flow to DRB mapping Indication) field indicating whether or not the mapping information between the flow and the radio bearer needs to be updated is set to "1" To identify the QoS flow and store the correspondence information between the QoS flow of the downlink SDAP @ PDU and the radio bearer as the correspondence information between the QoS flow of the uplink and the radio bearer. That.
　ＮＡＳリフレクティブＱｏＳとは、非特許文献１６に記載の通りダウンリンクヘッダ情報要素によりダウンリンクＳＤＡＰヘッダが設定された無線ベアラの下位レイヤよりダウンリンクＳＤＡＰ　ＰＤＵを受け取った時、ＳＤＡＰヘッダのフィールドで、ＮＡＳレイヤがサービスデータフロー（Ｓｅｒｖｉｃｅ　Ｄａｔａ　Ｆｌｏｗ：ＳＤＦ）とＱｏＳマッピングルール―の更新が必要である事を通知される事が必要か否かを示す、ＲＱＩ（Ｒｅｆｌｅｃｔｉｖｅ　ＱｏＳ　Ｉｎｄｉｃａｔｉｏｎ）フィールドが「１」に設定されている情報に基づいて、ＳＤＡＰヘッダのＱｏＳフロー識別子フィールドを処理してＱｏＳフローを特定し、本ダウンリンクＳＤＡＰ　ＰＤＵのＱｏＳフローと無線ベアラとの対応情報が、アップリンクのＱｏＳフローと無線ベアラとの対応情報として格納されていない場合に、本ダウンリンクＳＤＡＰ　ＰＤＵのＱｏＳフローと無線ベアラとの対応情報を、アップリンクのＱｏＳフローと無線ベアラとの対応情報として格納する機能でても良い。 As described in Non-Patent Document 16, the NAS reflective QoS is a field of the NAS header when the downlink SDAP @ PDU is received from the lower layer of the radio bearer in which the downlink header is set by the downlink header information element. The RQI (Reflective QoS Indication) field is set to "1" indicating whether the layer needs to be notified that the service data flow (Service Data Flow: SDF) and the QoS mapping rule need to be updated or not. Based on the information, the QoS flow identifier field of the SDAP header is processed to identify the QoS flow, and the corresponding information between the QoS flow of the downlink SDAP @ PDU and the radio bearer is used to determine the QoS of the uplink. When the information is not stored as the correspondence information between the flow and the radio bearer, the function of storing the correspondence information between the QoS flow of the downlink SDAP @ PDU and the radio bearer as the correspondence information between the QoS flow of the uplink and the radio bearer. May be.
　また無線ベアラ設定情報要素の中の、ｐｄｃｐ－Ｃｏｎｆｉｇ又はＰＤＣＰ－Ｃｏｎｆｉｇで表される情報要素はＳＲＢ又はＤＲＢ用のＰＤＣＰ３０６の確立や変更を行うための、ＮＲ　ＰＤＣＰエンティティの設定に関する情報であっても良く、本発明の実施の形態ではＰＤＣＰ設定情報要素と言い換える事もある。ＮＲ　ＰＤＣＰエンティティの設定に関する情報には、アップリンク用シーケンス番号のサイズを示す情報、ダウンリンク用シーケンス番号のサイズを示す情報、ヘッダ圧縮（ＲｏＨＣ：ＲＯｂｕｓｔ　Ｈｅａｄｅｒ　Ｃｏｍｐｒｅｓｓｉｏｎ）のプロファイルを示す情報、リオーダリング（ｒｅ－ｏｒｄｅｒｉｎｇ）タイマー情報などが含まれても良い。 In the radio bearer configuration information element, the information element represented by pdcp-Config or PDCP-Config may be information related to the setting of the NR @ PDCP entity for establishing or changing the PDCP 306 for SRB or DRB. Often, in the embodiment of the present invention, it may be referred to as a PDCP setting information element. The information related to the setting of the NR @ PDCP entity includes information indicating the size of the uplink sequence number, information indicating the size of the downlink sequence number, information indicating the profile of header compression (RoHC: Robust @ Header @ Compression), and reordering (RoHC: Robust @ Header @ Compression). re-ordering) timer information and the like may be included.
　また無線ベアラ設定情報要素の中の、ＤＲＢ－ＴｏＲｅｌｅａｓｅＬｉｓｔで表される情報要素は、解放するＤＲＢのＤＲＢ識別子のリスト情報であっても良く、本発明の実施の形態では解放する無線ベアラ情報要素、又は解放するデータ無線ベアラ情報要素と言い換える事もある。 In the radio bearer setting information element, the information element represented by DRB-ToReleaseList may be list information of a DRB identifier of a DRB to be released, and in the embodiment of the present invention, a radio bearer information element to be released, Or, it may be paraphrased as a data radio bearer information element to be released.
　次にＵＥ能力手順で用いられる情報要素について説明する。 Next, information elements used in the UE capability procedure will be described.
　図８は本発明の実施の形態において、図４におけるＵＥ能力情報メッセージに含まれる情報要素を表すＡＳＮ．１記述の一例である。 FIG. 8 shows an embodiment of the present invention, in which ASN. Represents an information element included in the UE capability information message in FIG. It is an example of one description.
　図８において、能力情報メッセージに含まれるＵＥ－ＣａｐａｂｉｌｉｔｙＲＡＴ－ＣｏｎｔａｉｎｅｒＬｉｓｔで表される情報要素は、情報要素のＵＥ－ＣａｐａｂｉｌｉｔｙＲＡＴ－Ｃｏｎｔａｉｎｅｒで表されるコンテナのリストを値（Ｖａｌｕｅ）として持ち、ＵＥ能力がＲＡＴ毎に一つのコンテナに含まれてよい。ＵＥ－ＣａｐａｂｉｌｉｔｙＲＡＴ－Ｃｏｎｔａｉｎｅｒには無線アクセス技術（Ｒａｄｉｏ　Ａｃｃｅｓｓ　Ｔｅｃｈｎｏｌｏｇｙ：ＲＡＴ）の種類（Ｔｙｐｅ）を示す情報を値として持つｒａｔ－Ｔｙｐｅフィールドと、ｒａｔ－Ｔｙｐｅで示されるＲＡＴのＵＥ能力を示すバイト列を値として持つｕｅＣａｐａｂｉｌｉｔｙＲＡＴ－Ｃｏｎｔａｉｎｅｒフィールドとが含まれてよい。ＵＥ－ＣａｐａｂｉｌｉｔｙＲＡＴ－Ｃｏｎｔａｉｎｅｒのｒａｔ－Ｔｙｐｅの値がＮＲと対応付けられたものであるとき、ｕｅＣａｐａｂｉｌｉｔｙＲＡＴ－Ｃｏｎｔａｉｎｅｒフィールドの値にＵＥ－ＮＲ－Ｃａｐａｂｉｌｉｔｙ情報要素が含まれてもよい。 In FIG. 8, the information element represented by UE-CapabilityRAT-ContainerList included in the capability information message has a list of containers represented by UE-CapabilityRAT-Container of the information element as a value (Value), and the UE capability is RAT. Each container may be included in one container. The UE-CapabilityRAT-Container includes a rat-Type field having information indicating a type (Type) of a radio access technology (Radio Access Technology: RAT) as a value, and a byte sequence indicating a UE capability of the RAT indicated by rat-Type. A ueCapabilityRAT-Container field having a value may be included. When the rat-Type value of the UE-CapabilityRAT-Container is associated with the NR, the UE-NR-Capability information element may be included in the value of the ueCapabilityRAT-Container field.
　ＵＥ－ＮＲ－Ｃａｐａｂｉｌｉｔｙ情報要素に含まれるｓｄａｐ－Ｐａｒａｍｅｔｅｒｓフィールドは、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素を値として持ってもよい。ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素は、ＵＥ１２２が上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはＵＥ１２２がデフォルトＤＲＢをサポートするか否かを示す情報を含んでよい。 ＳThe sadap-Parameters field included in the UE-NR-Capability information element may have the SDAP-Parameters information element as a value. The SDAP-Parameters information element may include information indicating whether UE 122 supports a SDAP header for the uplink and / or information indicating whether UE 122 supports default DRB.
　例えば、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素には、ＵＥ１２２が上りリンクのためのＳＤＡＰヘッダをサポートすることを示すフィールド（ｓｕｐｐｏｒｔＨｅａｄｅｒＵＬ）が含まれてよい。この場合、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素にｓｕｐｐｏｒｔＨｅａｄｅｒＵＬフィールドが含まれない場合に、ＵＥ１２２が上りリンクのためのＳＤＡＰヘッダをサポートしないことを示してよい。同様に、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素には、ＵＥ１２２がデフォルトＤＲＢをサポートすることを示すフィールド（ｓｕｐｐｏｒｔＤｅｆａｕｌｔＤＲＢ）が含まれてよい。この場合、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素にｓｕｐｐｏｒｔＤｅｆａｕｌｔＤＲＢフィールドが含まれない場合に、ＵＥ１２２がデフォルトＤＲＢをサポートしないことを示してよい。 For example, the SDAP-Parameters information element may include a field (supportHeaderUL) indicating that the UE 122 supports the SDAP header for the uplink. In this case, if the supportHeaderUL field is not included in the SDAP-Parameters information element, it may indicate that the UE 122 does not support the SDAP header for the uplink. Similarly, the SDAP-Parameters information element may include a field (supportDefaultDRB) indicating that the UE 122 supports the default DRB. In this case, if the SDAP-Parameters information element does not include the supportDefaultDRB field, it may indicate that the UE 122 does not support the default DRB.
　また、上記例において、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素に、ＵＥ１２２がデフォルトＤＲＢをサポートすることを示すフィールド（ｓｕｐｐｏｒｔＤｅｆａｕｌｔＤＲＢ）が含まれる場合には、上記ｓｕｐｐｏｒｔＨｅａｄｅｒＵＬフィールドが含まれているか否かに関わらず、ＵＥ１２２が上りリンクのためのＳＤＡＰヘッダをサポートすることを示してもよい。 Also, in the above example, when the SDAP-Parameters information element includes a field (supportDefaultDRB) indicating that the UE 122 supports the default DRB, regardless of whether the supportHeaderUL field is included, the UE 122 determines whether the UE122 supports the default DRB. It may indicate that it supports an SDAP header for the uplink.
　また別の例として、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素に、ＵＥ１２２が上りリンクのためのＳＤＡＰヘッダをサポートして、且つデフォルトＤＲＢをサポートしないことを示すフィールドと、ＵＥ１２２が上りリンクのためのＳＤＡＰヘッダをサポートして、且つデフォルトＤＲＢをサポートすることを示すフィールドの何れかを選択（Ｃｈｏｉｃｅ）したものを値として持つフィールド（ｓｕｐｐｏｒｔＳＤＡＰ）が含まれるようにしてもよい。この場合、ｓｕｐｐｏｒｔＳＤＡＰがＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素に含まれない場合には、ＵＥ１２２が上りリンクのためのＳＤＡＰヘッダをサポートしないことを示してよい。 As another example, in the SDAP-Parameters information element, a field indicating that the UE 122 supports the SDAP header for the uplink and does not support the default DRB, and the UE 122 supports the SDAP header for the uplink In addition, a field (supportSDAP) having a value obtained by selecting (Choice) any of the fields indicating that the default DRB is supported may be included. In this case, if supportSDAP is not included in the SDAP-Parameters information element, it may indicate that the UE 122 does not support the SDAP header for the uplink.
　図９はＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素を表すＡＳＮ．１記述の別の一例である。 FIG. 9 shows an ASN. Representing the SDAP-Parameters information element. It is another example of one description.
　図９において、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素は、ＵＥ１２２が上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはＵＥ１２２がデフォルトＤＲＢをサポートするか否かを示す情報、および／またはＵＥ１２２がＡＳリフレクティブＱｏＳをサポートするか否かを示す情報を含んでよい。 In FIG. 9, the SDAP-Parameters information element is information indicating whether UE 122 supports a SDAP header for the uplink, and / or information indicating whether UE 122 supports a default DRB, and / or It may include information indicating whether the UE 122 supports AS reflective QoS.
　例えば、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素には、ＵＥ１２２が上りリンクのためのＳＤＡＰヘッダをサポートすることを示すフィールド（ｓｕｐｐｏｒｔＨｅａｄｅｒＵＬ）が含まれてよい。この場合、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素にｓｕｐｐｏｒｔＨｅａｄｅｒＵＬフィールドが含まれない場合に、ＵＥ１２２が上りリンクのためのＳＤＡＰヘッダをサポートしないことを示してよい。同様に、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素には、ＵＥ１２２がデフォルトＤＲＢをサポートすることを示すフィールド（ｓｕｐｐｏｒｔＤｅｆａｕｌｔＤＲＢ）が含まれてよい。この場合、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素にｓｕｐｐｏｒｔＤｅｆａｕｌｔＤＲＢフィールドが含まれない場合に、ＵＥ１２２がデフォルトＤＲＢをサポートしないことを示してよい。同様に、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素には、ＵＥ１２２がＡＳリフレクティブＱｏＳをサポートすることを示すフィールド（ｓｕｐｐｏｒｔＡｓＲｅｆｌｅｃｔｉｖｅ）が含まれてよい。この場合、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素にｓｕｐｐｏｒｔＡｓＲｅｆｌｅｃｔｉｖｅフィールドが含まれない場合に、ＵＥ１２２がＡＳリフレクティブＱｏＳをサポートしないことを示してよい。 For example, the SDAP-Parameters information element may include a field (supportHeaderUL) indicating that the UE 122 supports the SDAP header for the uplink. In this case, if the supportHeaderUL field is not included in the SDAP-Parameters information element, it may indicate that the UE 122 does not support the SDAP header for the uplink. Similarly, the SDAP-Parameters information element may include a field (supportDefaultDRB) indicating that the UE 122 supports the default DRB. In this case, if the SDAP-Parameters information element does not include the supportDefaultDRB field, it may indicate that the UE 122 does not support the default DRB. Similarly, the SDAP-Parameters information element may include a field (supportAsReflective) indicating that the UE 122 supports AS reflective QoS. In this case, if the supportAsReflective field is not included in the SDAP-Parameters information element, it may indicate that the UE 122 does not support AS reflective QoS.
　また、上記例において、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素に、ＵＥ１２２がデフォルトＤＲＢをサポートすることを示すフィールド（ｓｕｐｐｏｒｔＤｅｆａｕｌｔＤＲＢ）、および／またはＡＳリフレクティブＱｏＳをサポートすることを示すフィールド（ｓｕｐｐｏｒｔＡｓＲｅｆｌｅｃｔｉｖｅ）が含まれる場合には、上記ｓｕｐｐｏｒｔＨｅａｄｅｒＵＬフィールドが含まれているか否かに関わらず、ＵＥ１２２が上りリンクのためのＳＤＡＰヘッダをサポートすることを示してもよい。 In addition, in the above example, when the SDAP-Parameters information element includes a field (supportDefaultDRB) indicating that the UE 122 supports the default DRB and / or a field (supportAsReflective) indicating that the UE 122 supports the AS reflective QoS. , Regardless of whether the supportHeaderUL field is included or not, may indicate that the UE 122 supports a SDAP header for the uplink.
　ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素に含まれる様々なフィールドの一例について説明する。 An example of various fields included in the $ SDAP-Parameters information element will be described.
　（１）ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素は、ＵＥ１２２が複数のＱｏＳフローを一つのＤＲＢにマッピングすることをサポートするか否かを示す情報を含んでよい。例えば、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素には、ＵＥ１２２が複数のＱｏＳフローを一つのＤＲＢにマッピングすることをサポートすることを示すフィールド（ｓｕｐｐｏｒｔＭｕｌｔｉｐｌｅＭａｐｐｉｎｇ）が含まれてよい。この場合、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素にｓｕｐｐｏｒｔＭｕｌｔｉｐｌｅＭａｐｐｉｎｇフィールドが含まれない場合に、ＵＥ１２２が複数のＱｏＳフローを一つのＤＲＢにマッピングすることをサポートしないことを示してよい。 (1) The SDAP-Parameters information element may include information indicating whether the UE 122 supports mapping multiple QoS flows to one DRB. For example, the SDAP-Parameters information element may include a field (supportMultipleMapping) indicating that the UE 122 supports mapping of a plurality of QoS flows to one DRB. In this case, if the supportMultipleMapping field is not included in the SDAP-Parameters information element, it may indicate that the UE 122 does not support mapping of a plurality of QoS flows to one DRB.
　（２）ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素は、ＵＥ１２２がエンドマーカーＰＤＵをサポートするか否かを示す情報を含んでよい。例えば、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素には、ＵＥ１２２がエンドマーカーＰＤＵをサポートすることを示すフィールド（ｓｕｐｐｏｒｔＥｎｄＭａｒｋｅｒ）が含まれてよい。この場合、ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素にｓｕｐｐｏｒｔＥｎｄＭａｒｋｅｒフィールドが含まれない場合に、ＵＥ１２２がエンドマーカーＰＤＵをサポートしないことを示してよい。 (2) The SDAP-Parameters information element may include information indicating whether the UE 122 supports an end marker PDU. For example, the SDAP-Parameters information element may include a field (supportEndMarker) indicating that the UE 122 supports the end marker PDU. In this case, when the supportEndMarker field is not included in the SDAP-Parameters information element, it may indicate that the UE 122 does not support the end marker PDU.
　ｇＮＢ１０８は、上記ＳＤＡＰ－Ｐａｒａｍｅｔｅｒｓ情報要素に含めるフィールドを指定する情報をＵＥ能力照会メッセージに含めてもよい。 The @gNB 108 may include information specifying a field to be included in the SDAP-Parameters information element in the UE capability inquiry message.
　このように、本発明の実施の形態では、ＵＥ１２２がＳＤＡＰに関するＵＥの能力情報を通知することにより、ｇＮＢ１０８がＳＤＡＰに関する適切なパラメータ設定をＵＥ１２２に行うことができる。 As described above, in the embodiment of the present invention, the gNB 108 can perform appropriate parameter setting for the SDAP to the UE 122 by the UE 122 notifying the UE of the capability information of the SDAP.
　なお、上記説明で用いたメッセージおよび／または情報要素のフィールドの一部、又は全ては、オプショナルであっても良い。即ち上記説明で用いたメッセージおよび／または情報要素のフィールドは必要に応じてＲＲＣ再設定メッセージに含まれても良い。 Note that some or all of the fields of the message and / or information element used in the above description may be optional. That is, the message and / or information element fields used in the above description may be included in the RRC reconfiguration message as needed.
　なお、本発明の各実施の形態における無線ベアラ設定は、ＲＲＣコネクション再設定手順だけでなく、ＲＲＣ確立（ＲＲＣ　Ｅｓｔａｂｌｉｓｈｍｅｎｔ）手順や、ＲＲＣ再確立（ＲＲＣ　Ｒｅ－Ｅｓｔａｂｌｉｓｈｍｅｎｔ）手順に含まれていても良い。また本発明の各実施の形態における無線ベアラとは、ＤＲＢであっても良いし、ＳＲＢであっても良い。 In addition, the radio bearer setting in each embodiment of the present invention may be included not only in the RRC connection re-establishment procedure, but also in the RRC establishment (RRC @ Establishment) procedure or the RRC re-establishment (RRC @ Re-Estimation) procedure. . Further, the radio bearer in each embodiment of the present invention may be a DRB or an SRB.
　本発明の実施形態における、ＵＥ１２２およびｇＮＢ１０８の種々の態様について説明する。 Various aspects of the UE 122 and the gNB 108 in the embodiment of the present invention will be described.
　（１）本発明の第１の態様は、基地局装置と通信する端末装置であって、Ｕｓｅｒ　Ｅｑｕｉｐｍｅｎｔ（ＵＥ）能力照会メッセージを受信する受信部と、前記ＵＥ能力照会メッセージに基づきＵＥ能力情報を基地局装置に通知する送信部とを備え、前記ＵＥ能力情報はＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報を含み、　前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトデ－タ無線ベアラをサポートするか否かを示す情報を含む。 (1) A first aspect of the present invention is a terminal device for communicating with a base station device, comprising: a receiving unit that receives a User @ Equipment (UE) capability inquiry message; A transmission unit for notifying the base station apparatus, wherein the UE capability information includes UE capability information relating to a Service Data Adaptation Protocol (SDAP) layer, and the UE capability information relating to the SDAP layer is an LDAP header for uplink. And / or information indicating whether to support the default data radio bearer.
　（２）本発明の第２の態様は、端末装置と通信する基地局装置であって、ＵＥ能力照会メッセージを送信する送信部と、前記端末装置からＵＥ能力情報を受信する受信部と、前記ＵＥ能力情報に含まれるＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報に基づき、デ－タ無線ベアラの設定を含むＲＲＣ再設定メッセージを生成する処理部とを備え、前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトＤＲＢをサポートするか否かを示す情報を含む。 (2) A second aspect of the present invention is a base station device communicating with a terminal device, wherein the transmitting unit transmits a UE capability inquiry message, the receiving unit receives UE capability information from the terminal device, A processing unit for generating an RRC re-establishment message including a data radio bearer configuration based on UE capability information on a Service Data Adaptation Protocol (SDAP) layer included in the UE capability information; Includes information indicating whether to support the SDAP header for the uplink and / or information indicating whether to support the default DRB.
　（３）本発明の第３の態様は、基地局装置と通信する端末装置に適用される方法であって、Ｕｓｅｒ　Ｅｑｕｉｐｍｅｎｔ（ＵＥ）能力照会メッセージを受信するステップと、前記ＵＥ能力照会メッセージに基づきＵＥ能力情報を基地局装置に通知するステップとを含み、前記ＵＥ能力情報はＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報を含み、　前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトデ－タ無線ベアラをサポートするか否かを示す情報を含む。 (3) A third aspect of the present invention is a method applied to a terminal device communicating with a base station device, the method comprising: receiving a User @ Equipment (UE) capability inquiry message; Notifying the UE capability information to the base station apparatus, wherein the UE capability information includes UE capability information on a Service Data Adaptation Protocol (SDAP) layer, and the UE capability information on the SDAP layer is for uplink. And / or information indicating whether or not to support the default data radio bearer.
　（４）本発明の第４の態様は、端末装置と通信する基地局装置に適用される方法であって、ＵＥ能力照会メッセージを送信するステップと、前記端末装置からＵＥ能力情報を受信するステップと、前記ＵＥ能力情報に含まれるＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報に基づき、デ－タ無線ベアラの設定を含むＲＲＣ再設定メッセージを生成するステップとを含み、前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトＤＲＢをサポートするか否かを示す情報を含む。 (4) A fourth aspect of the present invention is a method applied to a base station apparatus communicating with a terminal apparatus, wherein a step of transmitting a UE capability inquiry message and a step of receiving UE capability information from the terminal apparatus. And generating an RRC reconfiguration message including a data radio bearer configuration based on UE capability information on a Service Data Adaptation Protocol (SDAP) layer included in the UE capability information. The UE capability information includes information indicating whether to support the SDAP header for the uplink and / or information indicating whether to support the default DRB.
　（５）本発明の第５の態様は、基地局装置と通信する端末装置に実装される集積回路であって、Ｕｓｅｒ　Ｅｑｕｉｐｍｅｎｔ（ＵＥ）能力照会メッセージを受信する機能と、　前記ＵＥ能力照会メッセージに基づきＵＥ能力情報を基地局装置に通知する機能とを前記端末装置に対して発揮させ、前記ＵＥ能力情報はＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報を含み、　前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトデ－タ無線ベアラをサポートするか否かを示す情報を含む。 (5) A fifth aspect of the present invention is an integrated circuit implemented in a terminal device that communicates with a base station device, the function of receiving a User @ Equipment (UE) capability inquiry message; And a function of notifying the base station apparatus of UE capability information based on the UE capability information, wherein the UE capability information includes UE capability information relating to a Service Data Adaptation Protocol (SDAP) layer, and a UE capability relating to the SDAP layer. May include information indicating whether to support an SDAP header for the uplink and / or information indicating whether to support a default data radio bearer.
　（６）本発明の第６の態様は、端末装置と通信する基地局装置に実装される集積回路であって、ＵＥ能力照会メッセージを送信する機能と、前記端末装置からＵＥ能力情報を受信する機能と、前記ＵＥ能力情報に含まれるＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報に基づき、デ－タ無線ベアラの設定を含むＲＲＣ再設定メッセージを生成する機能とを前記基地局装置に対いて発揮させ、前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトＤＲＢをサポートするか否かを示す情報を含む。 (6) A sixth aspect of the present invention is an integrated circuit mounted on a base station apparatus that communicates with a terminal apparatus, the function of transmitting a UE capability inquiry message, and receiving UE capability information from the terminal apparatus. The base station apparatus has a function and a function of generating an RRC reconfiguration message including a data radio bearer setting based on UE capability information relating to a Service Data Adaptation Protocol (SDAP) layer included in the UE capability information. The UE capability information for the SDAP layer includes information indicating whether to support an SDAP header for uplink and / or information indicating whether to support a default DRB.
　これにより、ＵＥ１２２がＳＤＡＰに関するＵＥの能力情報を通知することで、ｇＮＢ１０８がＳＤＡＰに関する適切なパラメータ設定をＵＥ１２２に行うことができる。 Thus, the UE 122 notifies the UE of the capability information of the SDAP, so that the gNB 108 can perform appropriate parameter setting for the SDAP to the UE 122.
　本発明に関わる装置で動作するプログラムは、本発明に関わる上述した実施形態の機能を実現するように、Ｃｅｎｔｒａｌ　Ｐｒｏｃｅｓｓｉｎｇ　Ｕｎｉｔ（ＣＰＵ）等を制御してコンピュ－タを機能させるプログラムであっても良い。プログラムあるいはプログラムによって取り扱われる情報は、処理時に一時的にＲａｎｄｏｍ　Ａｃｃｅｓｓ　Ｍｅｍｏｒｙ（ＲＡＭ）などの揮発性メモリに読み込まれ、あるいはフラッシュメモリなどの不揮発性メモリやＨａｒｄ　Ｄｉｓｋ　Ｄｒｉｖｅ（ＨＤＤ）に格納され、必要に応じてＣＰＵによって読み出し、修正・書き込みが行なわれる。 The program that operates on the device according to the present invention may be a program that controls a Central Processing Unit (CPU) or the like so that the computer functions so as to realize the functions of the above-described embodiment according 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 is stored in a non-volatile memory such as a flash memory or a Hard Disk Drive (HDD). In response, reading, correction and writing are performed by the CPU.
　なお、上述した実施形態における装置の一部、をコンピュ－タで実現するようにしてもよい。その場合、この制御機能を実現するためのプログラムをコンピュ－タが読み取り可能な記録媒体に記録して、この記録媒体に記録されたプログラムをコンピュ－タシステムに読み込ませ、実行することによって実現してもよい。ここでいう「コンピュ－タシステム」とは、装置に内蔵されたコンピュ－タシステムであって、オペレ－ティングシステムや周辺機器等のハ－ドウェアを含むものとする。また、「コンピュ－タが読み取り可能な記録媒体」とは、半導体記録媒体、光記録媒体、磁気記録媒体等のいずれであってもよい。 Note that a part of the device in the above-described embodiment may be realized by a computer. In this case, a program for realizing this control function is recorded on a computer-readable recording medium, and the program recorded on this recording medium is read by a computer system and executed to realize the control function. Is also good. Here, the "computer system" is a computer system built in the apparatus, and includes hardware such as an operating system and peripheral devices. The "computer-readable recording medium" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, and the like.
　さらに「コンピュ－タが読み取り可能な記録媒体」とは、インターネット等のネットワークや電話回線等の通信回線を介してプログラムを送信する場合の通信線のように、短時間、動的にプログラムを保持するもの、その場合のサーバやクライアントとなるコンピュ－タシステム内部の揮発性メモリのように、一定時間プログラムを保持しているものも含んでもよい。また上記プログラムは、前述した機能の一部を実現するためのものであってもよく、さらに前述した機能をコンピュ－タシステムにすでに記録されているプログラムとの組み合わせで実現できるものであってもよい。 Furthermore, a "computer-readable recording medium" means that a program is dynamically held for a short time, such as a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line. For example, a program that holds a program for a certain period of time, such as a volatile memory in a computer system serving as a server or a client in that case, may be included. Further, the above-mentioned program may be for realizing a part of the above-mentioned functions, or may be for realizing the above-mentioned functions in combination with a program already recorded in a computer system. .
　また、上述した実施形態に用いた装置の各機能ブロック、または諸特徴は、電気回路、すなわち典型的には集積回路あるいは複数の集積回路で実装または実行され得る。本明細書で述べられた機能を実行するように設計された電気回路は、汎用用途プロセッサ、デジタルシグナルプロセッサ（ＤＳＰ）、特定用途向け集積回路（ＡＳＩＣ）、フィールドプログラマブルゲートアレイ（ＦＰＧＡ）、またはその他のプログラマブル論理デバイス、ディスクリートゲートまたはトランジスタロジック、ディスクリートハードウェア部品、またはこれらを組み合わせたものを含んでよい。汎用用途プロセッサは、マイクロプロセッサであってもよいし、代わりにプロセッサは従来型のプロセッサ、コントロ－ラ、マイクロコントロ－ラ、またはステ－トマシンであってもよい。汎用用途プロセッサ、または前述した各回路は、デジタル回路で構成されていてもよいし、アナログ回路で構成されていてもよい。また、半導体技術の進歩により現在の集積回路に代替する集積回路化の技術が出現した場合、当該技術による集積回路を用いることも可能である。 Also, each functional block or various features of the device used in the above-described embodiment may be implemented or executed by an electric circuit, that is, typically, an integrated circuit or a plurality of 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 Logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof. A general purpose processor may be a microprocessor, or, in the alternative, the processor may be a conventional processor, controller, microcontroller, or state machine. The general-purpose processor or each of the above-described circuits may be configured by a digital circuit, or may be configured by an analog circuit. Further, in the case where a technology for forming an integrated circuit that substitutes for a current integrated circuit appears due to the progress of semiconductor technology, an integrated circuit based on the technology can be used.
　なお、本願発明は上述の実施形態に限定されるものではない。実施形態では、装置の一例を記載したが、本願発明は、これに限定されるものではなく、屋内外に設置される据え置き型、または非可動型の電子機器、たとえば、ＡＶ機器、キッチン機器、掃除・洗濯機器、空調機器、オフィス機器、自動販売機、その他生活機器などの端末装置もしくは通信装置に適用出来る。 発 明 Note that the present invention is not limited to the above embodiment. In the embodiment, an example of the device is described. However, the present invention is not limited to this, and stationary or non-movable electronic devices installed indoors and outdoors, for example, AV devices, kitchen devices, It can be applied to terminal devices or communication devices such as cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other 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 the embodiments, and may include design changes within the scope of the present invention. Further, the present invention can be variously modified within the scope shown in the claims, and the technical scope of the present invention includes embodiments obtained by appropriately combining technical means disclosed in different embodiments. It is. Further, the components described in the above-described embodiment also include a configuration in which components having the same effects are replaced with each other.

Claims (6)

  1. 　基地局装置と通信する端末装置であって、
    　Ｕｓｅｒ　Ｅｑｕｉｐｍｅｎｔ（ＵＥ）能力照会メッセージを受信する受信部と、
    　前記ＵＥ能力照会メッセージに基づきＵＥ能力情報を基地局装置に通知する送信部とを備え、
    　前記ＵＥ能力情報はＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報を含み、　前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトデ－タ無線ベアラをサポートするか否かを示す情報を含む
    　端末装置。     A terminal device that communicates with a base station device,
    A receiving unit for receiving a User Equipment (UE) capability inquiry message;
    A transmitting unit that notifies the UE capability information to the base station apparatus based on the UE capability inquiry message,
    The UE capability information includes UE capability information on a Service Data Adaptation Protocol (SDAP) layer, the UE capability information on the SDAP layer includes information indicating whether or not to support an SDAP header for uplink, and / or Or a terminal device including information indicating whether or not to support a default data radio bearer.
  2. 　端末装置と通信する基地局装置であって、
    　ＵＥ能力照会メッセージを送信する送信部と、
    　前記端末装置からＵＥ能力情報を受信する受信部と、
    　前記ＵＥ能力情報に含まれるＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報に基づき、デ－タ無線ベアラの設定を含むＲＲＣ再設定メッセージを生成する処理部とを備え、
    　前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトＤＲＢをサポートするか否かを示す情報を含む
    　基地局装置。     A base station device communicating with the terminal device,
    A transmitting unit for transmitting a UE capability inquiry message;
    A receiving unit that receives UE capability information from the terminal device;
    A processing unit for generating an RRC re-establishment message including a data radio bearer configuration based on UE capability information on a Service Data Adaptation Protocol (SDAP) layer included in the UE capability information;
    The base station device, wherein the UE capability information on the SDAP layer includes information indicating whether to support an SDAP header for uplink and / or information indicating whether to support a default DRB.
  3. 　基地局装置と通信する端末装置に適用される方法であって、
    　Ｕｓｅｒ　Ｅｑｕｉｐｍｅｎｔ（ＵＥ）能力照会メッセージを受信するステップと、
    　前記ＵＥ能力照会メッセージに基づきＵＥ能力情報を基地局装置に通知するステップとを含み、
    　前記ＵＥ能力情報はＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報を含み、　前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトデ－タ無線ベアラをサポートするか否かを示す情報を含む方法。     A method applied to a terminal device communicating with a base station device,
    Receiving a User Equipment (UE) capability inquiry message;
    Notifying the base station apparatus of UE capability information based on the UE capability inquiry message,
    The UE capability information includes UE capability information on a Service Data Adaptation Protocol (SDAP) layer, the UE capability information on the SDAP layer includes information indicating whether or not to support an SDAP header for uplink, and / or Or a method including information indicating whether to support a default data radio bearer.
  4. 　端末装置と通信する基地局装置に適用される方法であって、
    　ＵＥ能力照会メッセージを送信するステップと、
    　前記端末装置からＵＥ能力情報を受信するステップと、
    　前記ＵＥ能力情報に含まれるＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報に基づき、デ－タ無線ベアラの設定を含むＲＲＣ再設定メッセージを生成するステップとを含み、
    　前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトＤＲＢをサポートするか否かを示す情報を含む方法。     A method applied to a base station device communicating with a terminal device,
    Sending a UE capability inquiry message;
    Receiving UE capability information from the terminal device;
    Generating an RRC re-establishment message including a data radio bearer configuration based on UE capability information on a Service Data Adaptation Protocol (SDAP) layer included in the UE capability information;
    A method wherein the UE capability information for the SDAP layer includes information indicating whether to support an SDAP header for an uplink and / or information indicating whether to support a default DRB.
  5. 　基地局装置と通信する端末装置に実装される集積回路であって、
    　Ｕｓｅｒ　Ｅｑｕｉｐｍｅｎｔ（ＵＥ）能力照会メッセージを受信する機能と、
    　前記ＵＥ能力照会メッセージに基づきＵＥ能力情報を基地局装置に通知する機能とを前記端末装置に対して発揮させ、
    　前記ＵＥ能力情報はＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報を含み、　前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトデ－タ無線ベアラをサポートするか否かを示す情報を含む集積回路。     An integrated circuit mounted on a terminal device that communicates with the base station device,
    A function of receiving a User Equipment (UE) capability inquiry message;
    A function of notifying the base station device of UE capability information based on the UE capability inquiry message is exerted on the terminal device,
    The UE capability information includes UE capability information on a Service Data Adaptation Protocol (SDAP) layer, the UE capability information on the SDAP layer includes information indicating whether or not to support an SDAP header for uplink, and / or Or an integrated circuit including information indicating whether to support a default data radio bearer.
  6. 　端末装置と通信する基地局装置に実装される集積回路であって、
    　ＵＥ能力照会メッセージを送信する機能と、
    　前記端末装置からＵＥ能力情報を受信する機能と、
    　前記ＵＥ能力情報に含まれるＳｅｒｖｉｃｅ　Ｄａｔａ　Ａｄａｐｔａｔｉｏｎ　Ｐｒｏｔｏｃｏｌ（ＳＤＡＰ）レイヤに関するＵＥ能力の情報に基づき、デ－タ無線ベアラの設定を含むＲＲＣ再設定メッセージを生成する機能とを前記基地局装置に対いて発揮させ、
    　前記ＳＤＡＰレイヤに関するＵＥ能力の情報は、上りリンクのためのＳＤＡＰヘッダをサポートするか否かを示す情報、および／またはデフォルトＤＲＢをサポートするか否かを示す情報を含む集積回路。     An integrated circuit mounted on a base station device that communicates with the terminal device,
    Sending a UE capability inquiry message;
    A function of receiving UE capability information from the terminal device;
    A function of generating an RRC reconfiguration message including a data radio bearer configuration based on UE capability information on a Service Data Adaptation Protocol (SDAP) layer included in the UE capability information is demonstrated to the base station apparatus. Let
    An integrated circuit, wherein the UE capability information for the SDAP layer includes information indicating whether to support an SDAP header for uplink and / or information indicating whether to support a default DRB.
PCT/JP2019/028537 2018-08-06 2019-07-19 Terminal device, base station device, method, and integrated circuit WO2020031664A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2018147660A JP2020025160A (en) 2018-08-06 2018-08-06 Terminal device, base station device, method, and integrated circuit
JP2018-147660 2018-08-06

Publications (1)

Publication Number Publication Date
WO2020031664A1 true WO2020031664A1 (en) 2020-02-13

Family

ID=69413548

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2019/028537 WO2020031664A1 (en) 2018-08-06 2019-07-19 Terminal device, base station device, method, and integrated circuit

Country Status (2)

Country Link
JP (1) JP2020025160A (en)
WO (1) WO2020031664A1 (en)

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
INTEL CORP.: "Measurement gap capability information for NR SA", 3GPP TSG RAN WG2 ADHOC_2018_07_NR R2-1809801, 22 June 2018 (2018-06-22), XP051525639 *
INTEL CORPORATION: "Email Disc on [99bis#27][NR] L2/3 capabilities", 3GPP TSG RAN WG2 #100 R2-1712678, 2 December 2017 (2017-12-02), XP051372669 *
QUALCOMM INC.: "SDAP UE capability", 3GPP TSG RAN WG2 ADHOC_2018_07_NR R2-1809487, 22 June 2018 (2018-06-22), XP051525345 *
SHARP: "UE capability for SDAP", 3GPP TSG RAN WG2 #103 R2-1811945, 10 August 2018 (2018-08-10), XP051521575 *

Also Published As

Publication number Publication date
JP2020025160A (en) 2020-02-13

Similar Documents

Publication Publication Date Title
WO2019131345A1 (en) Terminal device, method, and integrated circuit
JP7145603B2 (en) Terminal device, base station device and method
JP7142426B2 (en) Terminal device and method
US11375563B2 (en) Terminal apparatus, method, and integrated circuit
US11382165B2 (en) Terminal apparatus, method, and integrated circuit
JP2023176001A (en) Terminal device, communication method and base station device
JP7390149B2 (en) Terminal device, base station device, method, and integrated circuit
WO2020031934A1 (en) Terminal device, base station device, and method
WO2020059720A1 (en) Terminal device, base station device, and method
TWI787389B (en) Terminal device and wireless communication method
JP7145611B2 (en) TERMINAL DEVICE, METHOD AND INTEGRATED CIRCUIT
WO2020031664A1 (en) Terminal device, base station device, method, and integrated circuit
WO2020013029A1 (en) Terminal device, base station device, and method
WO2020095838A1 (en) Terminal device, base station device, and method
WO2019244615A1 (en) Terminal device, base station device, method, and integrated circuit
JP2022118227A (en) Terminal device, base station device, and method
WO2019098266A1 (en) Terminal device and method
JP2022185122A (en) Terminal device, base station device, and method
JP2023082208A (en) Terminal device, base station device, and method

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19846397

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19846397

Country of ref document: EP

Kind code of ref document: A1