Cisco Cisco ASR 5000
Support for RAT/Frequency Selection Priority ID (RFSP-ID)
How it Works ▀
SGSN Administration Guide, StarOS Release 18 ▄
How it Works
Encoding and De-coding of RFSP Ids in different scenarios
Encoding of RFSP-Id in DL-unit data:RFSP Id is encoded as “Subscriber Profile ID for RAT/Frequency priority” IE
in DL-UnitData message as per 3GPP TS 48.018 (version 10.8.0, Section 10.2.1).
in DL-UnitData message as per 3GPP TS 48.018 (version 10.8.0, Section 10.2.1).
Figure 107. Subscriber Profile ID for RAT/Frequency priority coding
Encoding of Subscribed RFSP Index and RFSP Id in GTPC-V1 messages: RFSP ID will be encoded in GTPC-V1
message as per 3GPP TS 29.060 (version 11.8.0 Release 11, Section 7.7.88)
message as per 3GPP TS 29.060 (version 11.8.0 Release 11, Section 7.7.88)
Figure 108. Encoding of Subscribed RFSP Id in GTPC-V1 messages
De-coding of RFSP-ID in a MAP message: The RFSP-Id in EPS-Subscription Data IE is received as part of Insert
Subscriber Data request for Gn/Gp SGSN. The decoding of RFSP-Id is done as per 3GPP TS 29.272 (Version 11.9.0,
Section 7.3.46).
Subscriber Data request for Gn/Gp SGSN. The decoding of RFSP-Id is done as per 3GPP TS 29.272 (Version 11.9.0,
Section 7.3.46).
De-coding of RFSP-Id AVP in Subscription data from the S6d interface: The RFSP ID is grouped in Subscription
Data AVP on receiving ULA from HSS over the S6d interface. This is used in the S4-SGSN. This AVP is of type
Unsigned 32 as per 3GPP TS 29.272 (Version 11.9.0, Section 7.3.46).
Data AVP on receiving ULA from HSS over the S6d interface. This is used in the S4-SGSN. This AVP is of type
Unsigned 32 as per 3GPP TS 29.272 (Version 11.9.0, Section 7.3.46).
In the SGSN MAP module, the MAP module is enhanced to de-code the RFSP-Id in Insert Subscriber Data request as
part of Update GPRS Location procedure. Since RFSP-Id and APN profile are optional parameters the DB record will
be updated as follows:
part of Update GPRS Location procedure. Since RFSP-Id and APN profile are optional parameters the DB record will
be updated as follows:
1. If RFSP ID is present in EPS subscription and the override value is present in the Call Control Profile for that
RFSP-Id then the RFSP-Id is modified with the overridden value and stored in the mm-ctxt DB parameter. If
override value is not present in the Call Control Profile for RFSP-Id then RFSP Id received in ISD request is
used.
override value is not present in the Call Control Profile for RFSP-Id then RFSP Id received in ISD request is
used.
2. If RFSP-Id is not present in the EPS Subscription, then default override RFSP-Id is used.
In the 3G Access module, the RFSP ID for the UE is sent to the RNC through the following RANAP IEs: