6 PDUs and parameters specific to the present document

24.1613GPPNetwork-Based IP Flow Mobility (NBIFOM)Release 17Stage 3TS

6.0 General

The sending entity shall set value of a spare bit to zero. The receiving entity shall ignore value of a spare bit.

The sending entity shall not set value of a field to a reserved value. The receiving entity shall discard a message carrying a field with value set to a reserved value.

6.1 NBIFOM parameter list

6.1.1 General

The purpose of the NBIFOM parameter list is to transfer parameters associated with the network-based IP flow mobility (NBIFOM).

The NBIFOM parameter list is coded as shown in figure 6.1.1-1 and table 6.1.1-1.

8

7

6

5

4

3

2

1

Parameter identifier 1

octet 1

Length of parameter contents 1

octet 2

Parameter contents 1

octet 3

octet x

. . .

octet x+1

octet y

Parameter identifier n

octet y+1

Length of parameter contents n

octet y+2

Parameter contents n

octet y+3

octet z

Figure 6.1.1-1: NBIFOM parameter list

Table 6.1.1-1: NBIFOM parameter list

The NBIFOM parameter list contains a list of parameters, each one in a separate unit consisting of a parameter identifier field, a length of parameter contents field and a parameter contents field.

The parameter identifier field of a unit contains the hexadecimal coding of the parameter identifier. Bit 8 of the parameter identifier field contains the most significant bit.

The length of parameter contents field of a unit contains the binary coded representation of the length of the parameter contents field of the unit. Bit 8 of the length of parameter contents field contains the most significant bit.

The parameter contents field of a unit contains the binary coded representation of the value of the parameter identified in the parameter identifier field of the unit. Bit 8 of the parameter contents field contains the most significant bit.

If the parameter list contains a unit with a parameter identifier that is not supported by the receiving entity, the receiving entity ignores the unit and the receiving entity continues handling the rest of the units in the parameter list.

The receiving entity does not assume that a certain order of units will be used in the parameter list.

In this version of the protocol, the following parameter identifiers are specified:

MS to network direction:

– 00H (Not assigned).

– 01H (NBIFOM mode);

– 02H (NBIFOM default access);

– 03H (NBIFOM status);

– 04H (NBIFOM routing rules);

– 05H (NBIFOM IP flow mapping);

– 06H (Not assigned);

– 07H (NBIFOM Access stratum status); and

– 08H (NBIFOM access usability indication).

– 09H to FFH (Not assigned).

Network to MS direction:

– 00H (Not assigned).

– 01H (NBIFOM mode);

– 02H (NBIFOM default access);

– 03H (NBIFOM status);

– 04H (NBIFOM routing rules);

– 05H (Not assigned);

– 06H (NBIFOM RAN rules handling);

– 07H (Not assigned); and

– 08H (Not assigned).

– 09H to FFH (Not assigned).

6.1.2 NBIFOM default access parameter

When the parameter identifier field of a unit in the NBIFOM parameter list indicates the NBIFOM default access, the length of parameter contents field is set to one and the parameter contents field is coded according to table 6.1.2-1.

Table 6.1.2-1: Parameter contents field of a unit carrying NBIFOM default access parameter

The parameter contents field is coded as follows:

8

7

6

5

4

3

2

1

0

0

0

0

0

0

0

1

3GPP access

0

0

0

0

0

0

1

0

non-3GPP access

All other values are reserved.

6.1.3 NBIFOM status parameter

When the parameter identifier field of a unit in the NBIFOM parameter list indicates the NBIFOM status, the length of parameter contents field is set to one and the parameter contents field is coded according to table 6.1.3-1.

Table 6.1.3-1: Parameter contents field of a unit carrying NBIFOM status parameter

The status parameter is coded as follows:

8

7

6

5

4

3

2

1

0

0

0

0

0

0

0

0

Accepted

0

0

0

1

1

0

1

0

Insufficient resources

0

0

1

0

0

1

0

1

Requested service option not subscribed

0

0

1

0

0

0

1

0

Service option temporarily out of order

0

0

1

1

1

1

1

1

Request rejected, unspecified

0

0

1

1

1

0

0

1

Incorrect indication in the routing rule operation

0

0

1

1

1

0

1

0

Unknown information in IP flow filter(s)

0

1

1

0

1

1

1

1

Protocol error, unspecified

1

0

0

0

0

0

1

0

Unknown routing access information

All other values are interpreted as "Protocol error, unspecified".

Status parameter #26 – Insufficient resources

This status code is used by the UE or by the network to indicate that the requested routing rule cannot be accepted due to insufficient resources for the requested routing access.

Status parameter #33 – Requested service option not subscribed

This status code is used when the UE requested routing access cannot be used to transport the requested service due to the restriction of subscription.

Status parameter #34 – Service option temporarily out of order

This status code is used when the requested routing rule cannot be accepted due to temporary outage of one or more functions required for supporting the service via the requested routing access.

Status parameter #31 – Request rejected, unspecified

This status code is used by the network or by the UE to indicate that the requested routing rule cannot be accepted due to unspecified reasons.

Status parameter #57 –Incorrect indication in the routing rule operation

This status code is used by the network or the UE to indicate that the requested routing rule cannot be accepted due to incorrect operation code included in the request.

Status parameter #58 – Unknown information in IP flow filter(s)

This status code is used by the network or the UE to indicate that the requested routing rule cannot be accepted due to unknown information included in the routing rule’s IP flow filter(s).

Status parameter #111 – Protocol error, unspecified

This status code is used to report a protocol error event only when no other status code in the protocol error class applies.

Status parameter #130 –Unknown routing access information

This status code is used by the network or by the UE to indicate that the requested routing rule cannot be accepted due to unknown routing access information.

6.1.4 NBIFOM routing rules

When the parameter identifier field of a unit in the NBIFOM parameter list indicates the NBIFOM routing rules, the parameter contents field is coded according to figure 6.1.4-1 and table 6.1.4-1.

8

7

6

5

4

3

2

1

Length of routing rule 1

octet 1

Routing rule identifier 1

octet 2

Routing access 1

0

Spare

0

Spare

0

Spare

Operation code 1

octet 3

Routing rule priority 1

octet 4

Routing filter 1

octet 5

octet x

. . .

octet x+1

octet y

Length of routing rule n

octet y+1

Routing rule identifier n

octet y+2

Routing access n

0

Spare

0

Spare

0

Spare

Operation code n

octet y+3

Routing rule priority n

octet y+4

Routing filter n

octet y+5

octet z

Figure 6.1.4-1: Parameter contents field of a unit carrying NBIFOM routing rules parameter

Table 6.1.4-1: Parameter contents field of a unit carrying NBIFOM routing rules parameter

Routing rules (octets 1 to z)

The routing rules contain a list of routing rules, each one in a separate unit consisting of a length of routing rule field, and the routing rule contents. The routing rule contents consist of a routing rule identifier field, a routing access field, an operation code field, a routing rule priority field, and a routing filter field.

The length of routing rule field (octet 1) of a unit contains the binary coded representation of the length of the routing rule contents of the unit. Bit 8 of the length of routing filter field contains the most significant bit.

Routing rule identifier (octet 2) uniquely identifies the routing rule within one multi-access PDN connection. The routing rule identifier is allocated by the entity creating the routing rule, i.e. by the UE in the UE-initiated NBIFOM mode and by the PDN GW in the network-initiated NBIFOM mode.

Operation code (bits 1-3 in octet 3)

Bits

3

2

1

0

0

0

Spare

0

0

1

Create routing rule

0

1

0

Delete routing rule

0

1

1

Replace existing routing rule

1

0

0

Reserved

The values from "100" to "111" are reserved.

Routing access (bits 8-7 in octet 3)

Bits

8

7

0

1

3GPP access

1

0

non-3GPP access

The values "00" and "11" are reserved.

Routing rule priority (octet 4) indicates the order of the routing rule application when the IP packet matches more than one routing filter. The lower value indicates higher priority.

Routing filter (octet 5 to octet x) contains a routing filter and is coded according to figure 6.1.4-2 and table 6.1.4-2.

8

7

6

5

4

3

2

1

H

G

F

E

D

C

B

A

octet 1

Z

Z

N

M

L

K

J

I

octet 2

Z

Z

Z

Z

Z

Z

Z

Z

octet 3

Z

Z

Z

Z

Z

Z

Z

Z

octet 4

(A) Source IPv4 address

octet 5

octet 8

(B) Destination IPv4 address

octet a

octet a+3

(C) Source IPv6 address

octet b

octet b+15

(D) Destination IPv6 address

octet c

octet c+15

(E) Source address prefix length

octet d

(F) Destination address prefix length

octet e

(G) IPSec security parameter Index

octet f

octet f+3

(H) Protocol type next header

octet g

(I) Start source port range

octet h

octet h+3

(J) End source port range

octet i

octet i+3

(K) Start destination port range

octet j

octet j+3

(L) End destination port range

octet k

octet k+3

(M) Type of service

octet l

(N) Flow label

octet m

octet m+3

Figure 6.1.4-2: Routing filter

Table 6.1.4-2: Routing filter

Routing filter component type indication ‘A’ to ‘N’ flags (octet 1 – octet 4)

Each flag in this field indicates whether the corresponding field is present in the IE as shown in Figure 6.1.4-2.

IPv4 address field and IPv6 address field shall not be present in the same routing rule item, i.e. if ‘A’ flag, ‘B’ flag or both are set, then ‘C’ flag and ‘D’ flag are not set.

End source port range can be present only when start source port range is present, i.e. if ‘J’ flag is set, then ‘I’ flag is set.

End destination port range can be present only when start destination port range is present, i.e. if ‘L’ flag is set, then ‘K’ flag is set.

The sending entity sets ‘Z’ flags to zero. If a ‘Z’ flag is set to zero, the receiving entity ignores the ‘Z’ flag. If a ‘Z’ flag is set to one, the receiving entity ignores the routing rule.

Source IPv4 address indicates the source IPv4 address of the uplink packet to be matched and indicates the destination IPv4 address of the downlink packet to be matched. If ‘A’ flag is set, then this field is present otherwise this field is not present.

Destination IPv4 address indicates the destination IPv4 address of the uplink packet to be matched and indicates the source IPv4 address of the downlink packet to be matched. If ‘B’ flag is set, then this field is present otherwise this field is not present.

Source IPv6 address indicates the source IPv6 address of the uplink packet to be matched and indicates the destination IPv6 address of the downlink packet to be matched. If ‘C’ flag is set, then this field is present otherwise this field is not present.

Destination IPv6 address indicates the destination IPv6 address of the uplink packet to be matched and indicates the source IPv6 address of the downlink packet to be matched. If ‘D’ flag is set, then this field is present otherwise this field is not present.

Source address prefix length indicates the subnet length of IPv4 source address or the prefix length of the IPv6 source address of the uplink packet to be matched and indicates the subnet length of IPv4 destination address or the prefix length of the IPv6 destination address of the downlink packet to be matched. If ‘E’ flag is set, then this field is present otherwise this field is not present.

Destination address prefix length indicates the subnet length of IPv4 destination address or the prefix length of the IPv6 destination address of the uplink packet to be matched and indicates the subnet length of IPv4 source address or the prefix length of the IPv6 source address of the downlink packet to be matched. If ‘F’ flag is set, then this field is present otherwise this field is not present.

IPSec security parameter index indicates the 32-bit IPSec SPI value of the packet to be matched. If ‘G’ flag is set, then this field is present otherwise this field is not present.

Protocol type next header indicates the 8-bit protocol type (for IPv4) or next header (for IPv6) value of the packet to be matched. If ‘H’ flag is set, then this field is present otherwise this field is not present.

Start source port range indicates the first value of a range of port numbers of the source port of the uplink packet to be matched and indicates the first value of a range of port numbers of the destination port of the downlink packet to be matched. If ‘I’ flag is set, then this field is present otherwise this field is not present.

End source port range indicates the end value of a range of port numbers of the source port of the uplink packet to be matched and indicates the end value of a range of port numbers of the destination port of the downlink packet to be matched. If ‘J’ flag is set, then this field is present otherwise this field is not present.

Start destination port range indicates the first value of a range of port numbers of the destination port of the uplink packet to be matched and indicates the first value of a range of port numbers of the source port of the downlink packet to be matched. If ‘K’ flag is set, then this field is present otherwise this field is not present.

End destination port range indicates the end value of a range of port numbers of the destination port of the uplink packet to be matched and indicates the end value of a range of port numbers of the source port of the downlink packet to be matched. If ‘L’ flag is set, then this field is present otherwise this field is not present.

Type of service indicates the type of service value of the packet to be matched. If ‘M’ flag is set, then this field is present otherwise this field is not present.

Flow label indicates the 20-bit IPv6 flow label value of the packet to be matched. The bits 8 through 5 of the first octet of this field are spare. If ‘N’ flag is set, then this field is present otherwise this field is not present.

6.1.5 NBIFOM IP flow mapping parameter

When the parameter identifier field of a unit in the NBIFOM parameter list indicates the NBIFOM IP flow mapping, the parameter contents field is coded according to figure 6.1.4-1 and table 6.1.4-1.

NOTE: Coding of the parameter contents field of the NBIFOM IP flow mapping parameter is the same as coding of the parameter contents field of the NBIFOM routing rules parameter.

6.1.6 NBIFOM RAN rules handling parameter

When the parameter identifier field of a unit in the NBIFOM parameter list indicates the NBIFOM RAN rules handling, the length of parameter contents field is set to one and the parameter contents field is coded according to table 6.1.6-1.

Table 6.1.6-1: Parameter contents field of a unit carrying NBIFOM RAN rules handling parameter

The parameter contents field is coded as follows:

8

7

6

5

4

3

2

1

0

0

0

0

0

0

0

1

RAN rules handling parameter is not set

0

0

0

0

0

0

1

0

RAN rules handling parameter is set

All other values are reserved.

6.1.7 NBIFOM Access stratum status parameter

When the parameter identifier field of a unit in the NBIFOM parameter list indicates the NBIFOM Access stratumstatus, the length of parameter contents field is set to one and the parameter contents field is coded according to table 6.1.7-1.

Table 6.1.7-1: Parameter contents field of a unit carrying NBIFOM Access stratumstatus parameter

The parameter contents field is coded as follows:

8

7

6

5

4

3

2

1

0

0

0

0

0

0

0

1

no indication

0

0

0

0

0

0

1

0

move-traffic-from-WLAN indication

0

0

0

0

0

0

1

1

move-traffic-to-WLAN indication

All other values are reserved.

6.1.8 NBIFOM access usability indication

When the parameter identifier field of a unit in the NBIFOM parameter list indicates the NBIFOM access usability indication, the length of parameter contents field is set to one and the parameter contents field is coded according to figure 6.1.8-1 and table 6.1.8-1.

8

7

6

5

4

3

2

1

0

Spare

0

Spare

0

Spare

0

Spare

WLAN access usable value

3GPP access usable value

octet 1

Figure 6.1.8-1: Parameter contents field of a unit carrying NBIFOM access usability indication parameter

Table 6.1.8-1: Parameter contents field of a unit carrying NBIFOM access usability indication parameter

3GPP access usable value (octet 1)

Bit

2

1

0

0

no change in usability of 3GPP access.

0

1

3GPP access becomes usable

1

0

3GPP access becomes unusable.

1

1

reserved.

WLAN access usable value (octet 1)

Bit

4

3

0

0

no change in usability of WLAN access.

0

1

WLAN access becomes usable.

1

0

WLAN access becomes unusable.

1

1

reserved.

6.1.9 NBIFOM mode parameter

When the parameter identifier field of a unit in the NBIFOM parameter list indicates the NBIFOM mode, the length of parameter contents field is set to one and the parameter contents field is coded according to table 6.1.9-1.

Table 6.1.9-1: Parameter contents field of a unit carrying NBIFOM mode parameter

The parameter contents field is coded as follows:

8

7

6

5

4

3

2

1

0

0

0

0

0

0

0

1

UE-initiated NBIFOM mode

0

0

0

0

0

0

1

0

Network-initiated NBIFOM mode

All other values are reserved.

Annex A (informative):
Change history

Change history

Date

TSG #

TSG Doc.

CR

Rev

Subject/Comment

Old

New

2015-10

Draft skeleton provided

0.0.0

2015-10

CT1#94

Includes the following contribution agreed by CT1 at CT1#94:

C1-153313, C1-153824, C1-153940.

0.0.0

0.1.0

2015-11

CT1#95

Includes the following contribution agreed by CT1 at CT1#95:

C1-154620, C1-154622, C1-154623, C1-154624, C1-154625, C1-154626, C1-154629, C1-154710, C1-154838, C1-154843.

0.1.0

0.2.0

2015-12

CT-70

CP-150736

Version 1.0.0 created for presentation for information

0.2.0

1.0.0

2016-01

CT1#95bis

Includes the following contribution agreed by CT1 at CT1#95bis:

C1-160040, C1-160536, C1-160537, C1-160538, C1-160539, C1-160540, C1-160541, C1-160542, C1-160544, C1-160545, C1-160547, C1-160549, C1-160550, C1-160729, C1-160730, C1-160781.

1.0.0

1.1.0

2016-02

CT1#96

Includes the following contribution agreed by CT1 at CT1#96:

C1-160995, C1-161289, C1-161290, C1-161291, C1-161406, C1-161408, C1-161410, C1-161411, C1-161449, C1-161450, C1-161462, C1-161463.

1.1.0

1.2.0

2016-03

CT-71

CP-160058

Version 2.0.0 created for presentation for approval

1.2.0

2.0.0

2016-03

CT-71

Version 13.0.0 created after approval

2.0.0

13.0.0

2016-06

CT-72

CP-160325

0001

Corrections for sematic of spare bits and reserved values

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0002

Corrections for SCM protocol configuration options item

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0003

Corrections for NBIFOM_GENERIC_CONTAINER attribute

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0004

Corrections for bit numbering in Figure 6.1.4-2

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0005

Update abbreviations list

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0006

2

Removal of editor’s notes and correction to Network-initiated IP flow mobility procedure

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0009

1

UE-initiated IP flow mobility

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0010

1

Scenario about the removal of an access from NBIFOM PDN

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0011

1

Re-title, re-naming, adjusting referencings, re-wordings and typo corrections

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0012

1

Perform 3GPP access specific procedures only when UE is in that 3GPP acccess

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0015

Correction to UE-initiated PDN connection establishment procedure

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0016

1

IP flow mobility procedure over which UE indicates default access

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0017

1

Correction of references to a non-existant subclause

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0018

BEARER RESOURCE ALLOCATION REJECT message

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0019

1

Network-initiated IP flow mobility over untrusted WLAN

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0020

1

Usability change and RAN rule indication

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0013

3

NW-initiated access removal for reactivation requested case

13.0.0

13.1.0

2016-06

CT-72

CP-160325

0021

2

UE feedback over GERAN or UTRAN

13.0.0

13.1.0

Change history

Date

Meeting

TDoc

CR

Rev

Cat

Subject/Comment

New version

2016-09

CT#73

CP-160506

0022

2

F

Correction to removal of an access from a multi-access PDN connection procedure with reactivation requested cause

13.2.0

2016-12

CT#74

CP-160735

0023

F

UE-initiated IP flow mapping

13.3.0

2016-12

CT#74

CP-160735

0024

F

Add the RCLWI case to the NBIFOM procedure

13.3.0

2017-03

CT#75

Upgrade to Rel-14

14.0.0

2017-06

CT#76

CP-171092

0026

1

F

Correction to the UE behavior for the UE-initiated IP flow mobility over GERAN or UTRAN

14.1.0

2018-06

SA#80

–

–

–

–

Update to Rel-15 version (MCC)

15.0.0

2020-07

SA-88e

–

–

–

–

Update to Rel-16 version (MCC)

16.0.0

2022-03

SA-95e

–

–

–

–

Update to Rel-17 version (MCC)

17.0.0