|
TECHNICAL SPECIFICATION
5G;
NG-RAN;
NR user plane protocol
(3GPP TS 38.425 version 15.3.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 38.425 version 15.3.0 Release 15 1 ETSI TS 138 425 V15.3.0 (2018-09)
Reference
RTS/TSGR-0338425vf30
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
If you find errors in the present document, please send your comment to one of the following services:
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 38.425 version 15.3.0 Release 15 2 ETSI TS 138 425 V15.3.0 (2018-09)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
---------------------- Page: 3 ----------------------
3GPP TS 38.425 version 15.3.0 Release 15 3 ETSI TS 138 425 V15.3.0 (2018-09)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 General . 7
4.1 General aspects . 7
5 NR user plane protocol . 7
5.1 General . 7
5.2 NR user plane protocol layer services . 7
5.3 Services expected from the Transport Network Layer . 8
5.4 Elementary procedures . 9
5.4.1 Transfer of Downlink User Data . 9
5.4.1.1 Successful operation. 9
5.4.1.2 Unsuccessful operation . 9
5.4.2 Downlink Data Delivery Status . 10
5.4.2.1 Successful operation. 10
5.4.2.2 Unsuccessful operation . 11
5.4.3 Transfer of Assistance Information . 11
5.4.3.1 Successful operation. 11
5.5 Elements for the NR user plane protocol . 12
5.5.1 General . 12
5.5.2 Frame format for the NR user plane protocol . 13
5.5.2.1 DL USER DATA (PDU Type 0) . 13
5.5.2.2 DL DATA DELIVERY STATUS (PDU Type 1) . 13
5.5.2.3 ASSISTANCE INFORMATION DATA (PDU Type 2) . 14
5.5.3 Coding of information elements in frames . 15
5.5.3.1 PDU Type . 15
5.5.3.2 Spare . 15
5.5.3.3 Report polling . 15
5.5.3.4 NR-U Sequence Number . 15
5.5.3.5 Desired buffer size for the data radio bearer . 16
5.5.3.6 Desired Data Rate . 16
5.5.3.7 DL Flush . 16
5.5.3.8 DL discard NR PDCP PDU SN . 16
5.5.3.9 DL Discard Blocks . 16
5.5.3.10 DL discard NR PDCP PDU SN start . 16
5.5.3.11 DL discard Number of blocks . 16
5.5.3.12 Discarded Block size . 16
5.5.3.13 Lost Packet Report . 17
5.5.3.14 Final Frame Indication . 17
5.5.3.15 Number of lost NR-U Sequence Number ranges reported . 17
5.5.3.16 Start of lost NR-U Sequence Number range . 17
5.5.3.17 End of lost NR-U Sequence Number range . 17
5.5.3.18 Highest Delivered NR PDCP SN Ind . 17
5.5.3.19 Highest successfully delivered NR PDCP Sequence Number . 17
5.5.3.20 Highest Transmitted NR PDCP SN Ind . 18
5.5.3.21 Highest transmitted NR PDCP Sequence Number . 18
5.5.3.22 Cause Report . 18
5.5.3.23 Cause Value . 18
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 38.425 version 15.3.0 Release 15 4 ETSI TS 138 425 V15.3.0 (2018-09)
5.5.3.24 Padding . 18
5.5.3.28 Void. 18
5.5.3.29 Retransmission flag . 18
5.5.3.30 Highest Delivered Retransmitted NR PDCP SN Ind . 18
5.5.3.31 Highest Retransmitted NR PDCP SN Ind . 19
5.5.3.32 Highest successfully delivered retransmitted NR PDCP Sequence Number . 19
5.5.3.33 Highest retransmitted NR PDCP Sequence Number . 19
5.5.3.34 Data Rate Indication . 19
5.5.3.35 PDCP Duplication Indication . 19
5.5.3.36 PDCP Duplication Activation Suggestion . 19
5.5.3.37 Number of Assistance Information Field . 19
5.5.3.38 Assistance Information Type . 20
5.5.3.39 Radio Quality Assistance Information . 20
5.5.3.40 Assistance Information Report Polling Flag . 20
5.5.3.41 Report Delivered . 20
5.5.3.42 DL report NR PDCP PDU SN . 20
5.5.3.43 User data existence flag . 20
5.5.3.44 Number of octets for Radio Quality Assistance Information Field . 20
5.5.3.45 Assistance Information Indication . 21
5.5.4 Timers . 21
5.6 Handling of unknown, unforeseen and erroneous protocol data . 21
Annex A (informative): Example of using future Extension . 22
A.1 Example of using Future Extension field . 22
A.1.1 New IE Flags . 22
Annex B (informative): Change history . 23
History . 24
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 38.425 version 15.3.0 Release 15 5 ETSI TS 138 425 V15.3.0 (2018-09)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 38.425 version 15.3.0 Release 15 6 ETSI TS 138 425 V15.3.0 (2018-09)
1 Scope
The present document specifies the NR user plane protocol functions used within NG-RAN and, for EN-DC, within E-
UTRAN. NR user plane protocol functions may reside in nodes terminating either the X2-U (for EN-DC) or the Xn-U
or the F1-U interface.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane
(GTPv1-U)".
[3] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2".
[4] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access
Control (MAC) protocol specification".
[5] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
[6] 3GPP TS 36.322: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control
(RLC) protocol specification".
[7] 3GPP TS 38.322: "NR; Radio Link Control (RLC) protocol specification".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP
TR 21.905 [1].
Corresponding node: a node interacting with a node hosting NR PDCP for flow control.
Master node: as defined in TS 37.340 [3].
Secondary node: as defined in TS 37.340 [3].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
EN-DC E-UTRA-NR Dual Connectivity
MR-DC Multi-RAT Dual Connectivity
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 38.425 version 15.3.0 Release 15 7 ETSI TS 138 425 V15.3.0 (2018-09)
4 General
4.1 General aspects
The NR user plane protocol is located in the User Plane of the Radio Network layer over either the Xn or the X2 or the
F1 interface.
The NR user plane protocol is used to convey control information related to the user data flow management of data
radio bearers.
Each NR user plane protocol instance is associated to one data radio bearer only.
If configured, NR user plane protocol instances exist at the Master node and the Secondary node in the context of DC or
at nodes hosting F1-U protocol terminations. The NR user plane protocol supports direct communication between NR
user plane protocol entities, regardless of whether they terminate the same or different user plane interfaces.
NOTE: User data radio bearers may be setup for data forwarding purposes during Xn HO or during DC related
mobility without requiring the execution of any additional data radio bearer related user plane protocol
functions related to an NR user plane protocol instance.
On each data radio bearer, the NR user plane protocol operates with RLC AM or RLC UM.
In this version of the present document, NR user plane protocol data is conveyed by GTP-U protocol means, more
specifically, by means of the "NR RAN Container" GTP-U extension header as defined in TS 29.281 [2].
5 NR user plane protocol
5.1 General
The NR user plane protocol layer is using services of the transport network layer in order to allow flow control of user
data packets transferred from the node hosting NR PDCP to the corresponding node.
5.2 NR user plane protocol layer services
The following functions are provided by the NR user plane protocol:
- Provision of NR user plane specific sequence number information for user data transferred from the node hosting
NR PDCP to the corresponding node for a specific data radio bearer.
- Information of successful in sequence delivery of NR PDCP PDUs to the UE from the corresponding node for
user data associated with a specific data radio bearer.
- Information of NR PDCP PDUs that were not delivered to the UE or the lower layers.
- Information of NR PDCP PDUs transmitted to the lower layers for user data associated with a specific data radio
bearer.
- Information of downlink NR PDCP PDUs to be discarded for user data associated with a specific data radio
bearer;
- Information of the currently desired buffer size at the corresponding node for transmitting to the UE user data
associated with a specific data radio bearer.
- Information of the currently desired data rate in bytes at the corresponding node for transmitting to the UE user
data associated with a specific data radio bearer configured for the UE at the corresponding node;
- Information of successful in sequence delivery of NR PDCP PDUs to the UE from the corresponding node for
retransmission user data associate with a specific data radio bearer;
- Information of NR PDCP PDUs transmitted to the lower layers for retransmission user data associated with a
specific data radio bearer.
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 38.425 version 15.3.0 Release 15 8 ETSI TS 138 425 V15.3.0 (2018-09)
- Information of the specific events at the corresponding node.
- Information on Radio Link Quality from the corresponding node for user data associated with a specific data
radio bearer.
5.3 Services expected from the Transport Network Layer
The NR user plane protocol layer expects the following services from the Transport Network Layer:
- Transfer of user data.
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 38.425 version 15.3.0 Release 15 9 ETSI TS 138 425 V15.3.0 (2018-09)
5.4 Elementary procedures
5.4.1 Transfer of Downlink User Data
5.4.1.1 Successful operation
The purpose of the Transfer of Downlink User Data procedure is to provide NR-U specific sequence number
information at the transfer of user data carrying a DL NR PDCP PDU from the node hosting the NR PDCP entity to the
corresponding node.
An NR user plane instance making use of the Transfer of Downlink User Data procedure is associated to a single data
radio bearer only.
The node hosting the NR PDCP entity shall assign consecutive NR-U sequence numbers to each transferred NR-U
packet.
The node hosting the NR PDCP entity indicates to the corresponding node whether this NR-U packet is a
retransmission of NR PDCP PDU.
The node hosting the NR PDCP entity can indicate to the corresponding node to either discard all NR PDCP PDUs up
to and including a defined DL discard NR PDCP PDU SN or discard one or a number of blocks of downlink NR PDCP
PDUs.
If the Assistance Information Report Polling Flag is equal to 1, the corresponding node shall, if supported, send the
ASSISTANCE INFORMATION DATA to the node hosting the NR PDCP entity.
The corresponding node shall detect whether an NR-U packet was lost and memorise the respective sequence number
after it has declared the respective NR-U packet as being "lost".
The corresponding node shall transfer the remaining NR PDCP PDUs towards the UE and memorise the highest NR
PDCP PDU sequence number of the NR PDCP PDU that was successfully delivered (as defined in TS 36.322 [6] and
TS 38.322 [7]) in sequence towards the UE (in case RLC AM is used) and the highest NR PDCP PDU sequence
number of the NR PDCP PDU that was transmitted to the lower layers.
The corresponding node shall send the DL DATA DELIVERY STATUS if the Report Polling Flag is set or when the
NR PDCP PDU with the indicated sequence number has been successfully delivered, unless a situation of overload at
the corresponding node is encountered.
NOTE: The Transfer of Downlink User Data procedure and the associated feedback of lost NR-U packets assist
the node hosting the NR PDCP entity in avoiding NR PDCP HFN de-synchronisation. If a deployment
decides to not use the Transfer of Downlink User Data procedure, NR PDCP HFN synchronization
should be ensured by other means.
If the User data existence flag is set to 1, the corresponding node assumes that the node hosting the NR PDCP entity has
some user data for the concerned data radio bearer. The corresponding node decides whether and when to use DRX for
the UE (i.e. the corresponding node may indicate the UE to use DRX even if the flag is set to 1 and the received DL
USER DATA frame contains no user data).
node hosting corresponding
NR PDCP node
DL USER DATA
Figure 5.4.1.1-1: Successful Transfer of Downlink User Data
5.4.1.2 Unsuccessful operation
Void.
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 38.425 version 15.3.0 Release 15 10 ETSI TS 138 425 V15.3.0 (2018-09)
5.4.2 Downlink Data Delivery Status
5.4.2.1 Successful operation
The purpose of the Downlink Data Delivery Status procedure is to provide feedback from the corresponding node to the
node hosting the NR PDCP entity to allow the node hosting the NR PDCP entity to control the downlink user data flow
via the corresponding node for the respective data radio bearer. The corresponding node may also transfer uplink user
data for the concerned data radio bearer to the node hosting the NR PDCP entity together with a DL DATA
DELIVERY STATUS frame within the same GTP-U PDU.
The Downlink Data Delivery Status procedure is also used to provide feedback from the corresponding node to the
node hosting the NR PDCP entity to allow the node hosting the NR PDCP entity to control the successful delivery of
DL control data to the corresponding node.
When the corresponding node decides to trigger the feedback for Downlink Data Delivery procedure it shall report as
specified in section 5.2:
a) in case of RLC AM, the highest NR PDCP PDU sequence number successfully delivered in sequence to the UE
among those NR PDCP PDUs received from the node hosting the NR PDCP entity i.e. excludes those
retransmission NR PDCP PDUs;
b) the desired buffer size in bytes for the concerned data radio bearer;
c) optionally, the desired data rate in bytes associated with a specific data radio bearer configured for the UE;
d) the NR-U packets that were declared as being "lost" by the corresponding node and have not yet been reported to
the node hosting the NR PDCP entity within the DL DATA DELIVERY STATUS frame;
e) if retransmission NR PDCP PDUs have been delivered, the highest NR PDCP PDU sequence number
successfully delivered in sequence to the UE among those retransmission NR PDCP PDUs received from the
node hosting the NR PDCP entity;
f) if retransmission NR PDCP PDUs have been transmitted, the highest NR PDCP PDU sequence number
transmitted to the lower layers among those retransmission NR PDCP PDUs received from the node hosting the
NR PDCP entity;
g) the highest NR PDCP PDU sequence number transmitted to the lower layers among those NR PDCP PDUs
received from the node hosting the NR PDCP entity i.e. excludes those retransmission NR PDCP PDUs.
NOTE: If a deployment has decided not to use the Transfer of Downlink User Data procedure, d), e) and f)
...