Diameter LTE Location Update

Question

Hello LTE n/w experts,

I have a Query regarding the UpdateLocation Diamter message. I have a issue in the legacy code, where the AVP "Supported-Features" which is optional is not handled. Now when we are testing with different vendor PGW, we are getting the following AVPS
AVP format

 Supported-Features ::=  < AVP Header: 628 10415 >
                         { Vendor-Id (AVP code 266)}
                         { Feature-List-ID (629)}
                         { Feature-List (630)}
                        *[ AVP ]

AVP format

MIP6-Agent-Info ::=  < AVP Header: 486 >
                    *2[ MIP-Home-Agent-Address (334)]
                      [ MIP-Home-Agent-Host (348)]
                      [ MIP6-Home-Link-Prefix (125)]
                     *[ AVP ]
  MIP6-Agent-Info ::=  < AVP Header: 486 >
                    *2[ MIP-Home-Agent-Address (334)]
                      [ MIP-Home-Agent-Host (348)]
                      [ MIP6-Home-Link-Prefix (125)]
                     *[ AVP ]

I am not sure why the Location Update has these new IEs. I am new to network side. So any help in this regard will be greatly appreciated.

Answer 1

Supported-Features AVP
it may inform the destination host about the features that the origin host supports. The Feature-List AVP contains a list of supported features of the origin host. The Vendor-Id AVP and the Feature-List AVP shall together identify which feature list is carried in the Supported-Features AVP.
Where a Supported-Features AVP is used to identify features that have been defined by 3GPP, the Vendor-Id AVP shall contain the vendor ID of 3GPP. Vendors may define proprietary features, but it is strongly recommended that the possibility is used only as the last resort. Where the Supported-Features AVP is used to identify features that have been defined by a vendor other than 3GPP, it shall contain the vendor ID of the specific vendor in question.

MIP6-Agent-Info
This contains the contains the IPv6 or the IPv4 address information of the HA. (Probably look at the RFC 5778 section 6.6)

Comments

Thanks a lot for the answer. Looked into the RFC, not able to make out exactly what this AVP indicates.
Not sure whether this indicates from UE perspective, and what triggers this AVP.

---

Can you be more specific (I think first one is clear to you, MIP6-Agent-Info is the confusion)