A.9 Inter-access flow mobility
24.3033GPPMobility management based on Dual-Stack Mobile IPv6Release 17Stage 3TS
A.9.1 Binding Update
The DSMIPv6 inter-access flow mobility procedure is described in subclause 5.5 and the fields of a BU message used for this procedure are depicted in table A.9.1-1.
The DSMIPv6 inter-access flow mobility procedure is described in subclause 5.5 and the Mobility Options in a BU message used for this procedure are depicted in table A.9.1-2.
Table A.9.1-1: Fields of a BU message for the DSMIPv6 inter-access flow mobility procedure
|
Fields |
Fields Description |
Reference |
|
Sequence Number |
Set to a monotonically increasing value. |
IETF RFC 6275 [27] |
|
Lifetime |
Set to the requested number of time in units of 4 seconds to indicate how long the binding will remain valid. |
IETF RFC 6275 [27] |
|
Home Registration (H) |
Set to "1" to indicate receiving node can act as this node’s HA |
IETF RFC 6275 [27] |
|
Link-local Address Compatibility (L) |
The Link-Local Address Compatibility (L) bit is set when the home address reported by the mobile node has the same interface identifier as the mobile node’s link-local address. |
IETF RFC 6275 [27] |
|
Key Management Mobility Capability (K) |
Set to "1" to indicate IKEv2 SA ability to survive mobility |
IETF RFC 6275 [27] |
|
Acknowledge (A) |
Set to "1" to request an acknowledgement message. |
IETF RFC 6275 [27] |
|
Force UDP encapsulation request (F) Flag |
Set to "0" to indicate no forced UDP encapsulation |
IETF RFC 5555 [2] |
|
Mobile Router Flag (R) |
Set to "1" to indicate home network prefix preservation for the UE. |
IETF RFC 3963 [29] |
|
Overwrite Flag (O) |
Set to "0" to indicate not replacing all binding cache entries at the HA with the entries listed in the Binding Update |
IETF RFC 5648 [31] |
Table A.9.1-2: Mobility Options in a BU message for the DSMIPv6 inter-access flow mobility procedure
|
Mobility Option |
Cat. |
Mobility Option Description |
Reference |
|
IPv4 Home Address option |
O |
For dynamic allocation, set to the value "0.0.0.0" to request allocation for the UE. |
IETF RFC 5555 [2] |
|
If the UE already has an IPv4 Home Address and wants to keep on using it, the IPv4 home address is set to the previously allocated value. |
|||
|
If the UE already has an IPv4 Home Address and wants to release it, the option is not inserted in the BU. |
|||
|
If the UE request allocation of IPv4 Home Address, the "P" flag is set to ‘0’. |
|||
|
If the UE already has an IPv4 Home Address and wants to keep on using it, the "P" flag is not set. |
|||
|
The Prefix Length is set to the requested prefix length of ’32’. |
|||
|
Binding Identifier mobility option |
O |
The BID is set to the value identifying the routing address used as Source IP Address of the Binding Update. |
IETF RFC 5648 [31], IETF RFC 6089 [32] |
|
The BID-PRI is set to the value assigned to the BID. |
|||
|
If the Binding Update message is sent on a home link, the "H" flag is set to "1". |
|||
|
If the Binding Update message is sent on a foreign link, the "H" flag is set to "0". |
|||
|
If the routing address used as IP Source Address of the Binding Update message is an IPv4 address, a NAT was detected and the UE is not exchanging data traffic, the Care-of Address field is set to the routing address. |
|||
|
Flow Identification mobility option |
O |
For creating routing rules, the FID and FID-PRI are set to an arbitrary value. |
IETF RFC 6089 [32], IETF RFC 6088 [33] |
|
For modifying routing rules, the FID and FID-PRI are set to the value identifying the routing filter the UE wants to modify. |
|||
|
The sub-option field conveys the Traffic Selector sub-option. |
|||
|
Flow Summary mobility option |
O |
Contain one or more FIDs present in the binding update list to refresh the respective flow bindings. |
IETF RFC 6089 [32] |
A.9.2 Binding Acknowledgement
The DSMIPv6 inter-access flow mobility procedure is described in subclause 5.5 and the fields of a BA message used for this procedure are depicted in table A.9.2-1.
The DSMIPv6 inter-access flow mobility procedure is described in subclause 5.5 and the Mobility Options in a BA message used for this procedure are depicted in table A.9.2-2.
Table A.9.2-1: Fields of a BA message for the DSMIPv6 inter-access flow mobility procedure
|
Fields |
Fields Description |
Reference |
|
Status |
Set to indicate the result. |
IETF RFC 6275 [27] |
|
Key Management Mobility Capability (K) |
Set as per HA ability to support the feature of updating the IKE SA based on Binding Update processing |
IETF RFC 6275 [27], IETF RFC 5555 [2] |
|
Mobile Router Flag (R) |
Set to "1" |
IETF RFC 3963 [29] |
|
Sequence Number |
Set to the value received in the corresponding Binding Update. |
IETF RFC 6275 [27] |
|
Lifetime |
Set to the granted number of time units of 4 seconds to indicate how long the binding will remain valid. |
IETF RFC 6275 [27] |
Table A.9.2-2: Mobility Options in a BA message for the DSMIPv6 inter-access flow mobility procedure
|
Mobility Option |
Cat. |
Mobility Option Description |
Reference |
|
IPv4 Address Acknowledgment option |
C |
If IPv4 Home Address option is present in the corresponding BU, IPv4 Home Address is set to the IPv4 Home Address either newly allocated for the UE or previously assigned prior to the Handover. |
IETF RFC 5555 [2] |
|
The supporting Status field is set accordingly. |
|||
|
Pref-len field is set to "32". |
|||
|
NAT Detection Option |
C |
When present the option contains the F Flag which indicates to the UE that UDP encapsulation is required. Option contains an optionally Refresh Time for the UE to refresh the NAT binding. |
IETF RFC 5555 [2] |
|
Binding Refresh Advice |
O |
Contains a Refresh Interval in units of 4 seconds indicating the remaining time until the UE could send a new home registration to the HA. |
IETF RFC 6275 [27] |
|
Binding Identifier mobility option |
C |
The option is present if the UE sent a Binding Identifier mobility option in the corresponding BU. The Status field is set accordingly. |
IETF RFC 5648 [31], IETF RFC 6089 [32] |
|
The BID and BID-PRI are set to the value indicated in the BID mobility option of the received Binding Update. |
|||
|
Flow Identification mobility option |
C |
The option is present if the UE sent a Flow Identification mobility option in the corresponding BU. The Status field is set accordingly. |
IETF RFC 5648 [31], IETF RFC 6089 [32] |
|
The FID, FID-PRI and sub-option field are set to the value indicated in the FID mobility option of the received Binding Update. |