Skip to main content

3gpp UE Identities

IMSI # MSISDN # External Identifier # IP address # IoT # 5G # 6G


IMSI # (15 Digits/ E.164/ )
The IMSI number is subscriber identification with given operator/ network (PLMN) with a maximum length of 15 digits. The IMSI is consists of an MCC (Mobile Country Code), an MNC (Mobile Network Code), and an MSIN (Mobile Subscriber Identity) 
formation IMSI (15) = MCC (3) + MNC (2-3) + MSIN (9-10)
format - TBCD format

MSISDN format (15 digits/ E.164/ TBCD Format)
The ITU-T recommendation E.164 limits the maximum length of an MSISDN to 15 digits. wherein 1-3 digits are reserved for country code. Prefixes are not included (e.g., 00 prefixes an international MSISDN when dialing from Sweden).


http://www.3gpp.org/wiki/index.php?title=Current%20Capacity%20of%20IMSI%2C%20MSISDN%2C%20and%20IPv6%20Identifiers
https://www.linkedin.com/pulse/mobile-numbering-basics-explained-imsi-vs-msisdn-atte-miettinen/

From 3GPP TS 23.003: 
IMSI: No more than 15 digits. Is composed of three fields: The Mobile Country Code (MCC), the Mobile Network Code (MNC) and the Mobile Subscriber Identification Number (MSIN). The MCC is 3 digits, the MNC is 2 or 3 digits, leaving 9 or 10 digits for the MSIN. This means an operator is alloted between 1 and 10 billion MSIN. This means that between 70 and 700 MCC and MNC values would be needed.
Since the MSIN+MCC together a 12 digit value, any country could be assigned the maximum value.
MSISDN : No more than 15 digits. The Country Code is 1 to 3 digits, and the National Destination Code (NDC) and Subscriber Number (SN) together are 12 to 14 digits. So again, the MSISDN could contain the 12 digits needed for MTC.

There are cases where the diameter AVP can considered to carry either IMSI/ MSISDN. 
User configure, type of Routing Entity type - IMSI, IMPI, MSISDN, IMPU and AVP - will selection of decoding formula of value as MSISDN or IMSI
valid pair (IMSI, IMPI) and (MSISDN, IMPU)

Comments

Popular posts from this blog

NSSF - an 5G network function to support the network slicing

NSSF - Network Slice Selector Function The 5G System architecture (3GPP TS 23.501: 5G SA; Stage 2) consists of the following network functions (NF). - Authentication Server Function (AUSF) - Core Access and Mobility Management Function (AMF) - Data network (DN), e.g. operator services, Internet access or 3rd party services - Structured Data Storage network function (SDSF) - Unstructured Data Storage network function (UDSF) - Network Exposure Function (NEF) - NF Repository Function (NRF) - Network Slice Selection Function (NSSF) ======>>> our focus - Policy Control function (PCF) - Session Management Function (SMF) - Unified Data Management (UDM) - Unified Data Repository (UDR) - User plane Function (UPF) - Application Function (AF) - User Equipment (UE) - (Radio) Access Network ((R)AN)

SMS-SG on LTE/ MTC networks

SMS with LTE  (SG-SMS) SMS (Short Messaging Service) was quite popular among people during 2G/3G, but now with the advent of 4G losing the shine/ attraction. With 4G people are moving to always-on kind of data connectivity and thus market rising with many application options to provide the messaging capabilities. The examples are such as whatsapp, snapchat etc Now here we are going to discuss, “can an SMS possible in LTE technology ?” and if so “how?” One possibility of using IMS framework and delivering SMS to/from UE. IMS provides the data (e.g. data, media-voice/video) usage overlaid on LTE technology. The bigger question and climax is on market pace in adapting and deployment of the IMS. To address the feature availability, an interim solution (SG interfaces) are suggested in specs. (its similar on the lines on how CS fallback option before LTE supporting Voice calls) Lets revisit the past (2G) on how SMS are delivered. SMS is delivered over signaling channel. This me

Cloud based Frameworks/ Kubernetes environment

Cloud based microservice frameworks Some of open source platforms available are Swarm (Docker), Kubernetes (google), mesos, The most popular in communities and internet industry seems to be kubernetes and picking steam in telecom front as well for upcoming 5G Service based architecture. The kubernetes has the default container solution based on Rket ? but the most popular combinations are using Docker as container. Kubernetes/ an Cloud orachastrator !! Deployment automation of scaling in (zooming in/ increasing) and out (zooming out, decreasing) Network plugin available such as flannel (popular, support only IPv4), calico (support IPv4, IPv6), weavenet Kubernetes currently does not support dual stack IPv4, IPv6 inter-working etc capabilities till version 1.13 (dec 2018). Another limitation, it does not recognize the multiple interfaces in case enable to POD's for configuring services exposure and external communication till version 1.13 (dec 2018) Will be adding more