The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
It is possible to configure the MME to support the Additional Mobile Subscriber ISDN (A-MSISDN) flag in the Features List AVP of the Update Location Request (ULR) messages.
This chapter looks at the MME's A-MSISDN functionality.
The MME includes the Additional Mobile Subscriber ISDN (A-MSISDN) flag in the Features List AVP of the Update Location Request (ULR) messages that are sent over the S6a interface to the Home Subscriber Server (HSS) at the time a UE Attaches. In response, if an A-MSISDN is available then the HSS sends a provisioned A-MSISDN and an MSISDN in the Subscription Data AVP in Update Location Answer (ULA) and IDR messages.
Support for A-MSISDN functionality enables the MME to use the A-MSISDN as a Correlation MSISDN (C-MSISDN) during SRVCC PS-to-CS handovers. For information on the purpose of the C-MSISDN, refer to 3GPP TS 23.003.
The MME's A-MSISDN functionality is applicable for ULR/ULA, IDR/IDA, and DSR/DSA command pairs sent over S6a interface.
The MME also supports the A-MSISDN withdrawal bit received in DSR Flags AVP. Receipt of this bit triggers the MME to delete an A-MSISDN from the UE context.
A-MSISDN support is not present for the S6d interface. This means that A-MSISDN will not be available to the MME when SGSN/MME-combo optimization is enabled and subscription data received by the SGSN is re-used by the MME.
Location services using A-MSISDN are not supported (PLR/LRR).
Lawful Intercept (LI) and Monitor Subscriber functions based on A-MSISDN as the identifier are not supported.
The MME's support of A-MSISDN complies with 3GPP 29.274 v11.10.0.
Enabling A-MSISDN is a two step process:
Both configuration steps are described below and both must be completed to fully enable A-MSISDN functionality.
By default, A-MSISDN is not supported. Use the following configuration sequence to enable the MME to support A-MSISDN functionality and to advertise that support to the HSS.
configure
call-control-profile profile_name
a-msisdn
remove a-msisdn
end Notes:
Use the output generated by the show call-control-profile full all command to verify the configuration status of the A-MSISDN functionality:
Call Control Profile Name = cp1
SAMOG Web-Authorization Mutiple Device Support : NO
...
Super Charger : Disabled
P-CSCF Restoration : Enabled
A-MSISDN : Enabled
Sending Radio Access Technology (RAT) IE : Enabled The following configuration sequence enables the MME to support AVPs available in Release 11 3GPP 29.272.
configure
context context_name
hss-peer-service service_name
diameter update-dictionary-avps { 3gpp-r10 | 3gpp-r11 | 3gpp-r9 }
no diameter update-dictionary-avps
end Notes:
The show commands in this section are available in support of the MME's A-MSISDN functionality.
The A-MSISDN field in the generated output indicates an A-MSISDN value if the A-MSISDN is received from the HSS. If no value is received from the HSS, then the value displayed will be n/a .
show mme-service session full all
SessMgr Instance: 1 ImsiMgr Instance: 1
MSID: 123456789012345 Callid: 00004e21
MME Service: mmesvc
MME HSS Service: mme1
SGTPC Service: sgtp1
EGTP S11 Service: egtp_mme
MME S1 Address: 192.80.80.2
EGTP S11 Address: 192.80.80.16
ME Identity: n/a GUTI: 123:456:32777:2:3221225473
MSISDN: 888012345679001
A-MSISDN : 988012345679002 
Feedback