Overview#
Mobile Device is a device that is mobile.Mobile Device that is connected to a Mobile Network is referred to as a Mobile Station and used by a Mobile Phone subscriber
Mobile Device may NOT be on a Mobile Network such as a Wi-Fi only Tablet (iPad)
We can think of these as Mobile Device:
- Electronic Fitness Device
- Mobile Phone (Mobile Station)
- Smart Watch
- Vehicle
Mobile Device Identifiers#
Each Mobile Device is identified by the International Mobile Subscriber Identity (IMSI) which is a unique identifier across all Mobile Networks- The first three digits represent the Mobile Country Code (MCC).
- The next two or three digits represent the Mobile Network Code (MNC) although E.212 allows three-digit MNC but are mainly used in the United States and Canada.
- The next digits represent the Mobile Subscriber Identification Number (MSIN).
More Information#
There might be more information for this subject on one of the following:- API Development
- AWS Lambda
- Acr_values
- App2app
- AppConfig Community
- Application
- Application Shell Architecture
- Assisted GPS
- Authentication Agent
- Authentication Center
- Authentication Context Class Values
- Authenticator App
- Authorization Cross Domain Code 1.0
- Binding_message
- Bluetooth
- Car Connectivity Consortium
- Cell-Site Simulators
- Cellebrite
- Client Device
- Credential
- Data Ownership
- Data Protection
- Derived Credential
- Device
- Device Inventory Service
- EMV Terms
- Electronic Fitness Device
- Emergency Location Service
- Enterprise Mobility Management
- FIDO Authenticator
- Firebase
- Geolocation
- Global Positioning System
- Global System for Mobile Communications
- Google Authenticator
- Grant Types
- Home Location Register
- Host Card Emulation
- Hypertext Transfer Protocol
- IDSA Integration Framework
- IPhone
- Identification
- Identity Relationship Management
- Implicit Grant
- Information Rights Management
- Instant Messaging
- International Direct Dialling
- International Mobile Equipment Identity
- International Mobile Equipment Identity Database
- International Mobile Subscriber Identity
- Internet
- Internet of Things
- Java Card
- Kerberos
- LTE
- Local device
- Location Area Identity
- Mobile
- Mobile App
- Mobile Connect
- Mobile Device Management
- Mobile Security Framework
- Mobile Station
- Mobile Station International Subscriber Directory Number
- Mobile Subscriber Identification Number
- Mobile TAN
- NFC
- NIST.SP.800-63C
- Native Applications Working Group
- Native application
- Near Field Communication
- Next Generation 9-1-1
- OAuth
- OAuth 2.0 Device Authorization Grant
- OAuth 2.0 Incremental Authorization
- OAuth 2.0 Use Cases
- OAuth Public Client
- OAuth Scope Example
- OpenID Connect Client
- OpenID Connect Client Initiated Backchannel Authentication Flow
- OpenID Connect MODRNA Authentication Profile 1.0
- OpenID Connect Mobile Discovery Profile
- Palantir Metropolis
- Password Validator
- Passwordless SMS Authentication
- Paym
- Payment Services Directive
- Platform Authenticator
- Progressive Web Application
- Public Safety Answering Point
- RCS Universal Profile
- Radio Interface Layer
- Reporting Body Identifier
- Roaming Authenticator
- SIM Swap
- Short Message Service
- Softcard
- Software Version Number
- Subscriber Identification Module
- Temporary Mobile Subscriber Identity
- Time-Division Multiple Access
- Trusted Execution Environment
- Trusted Service Manager
- Type Allocation Code
- Universal Inbox
- Universal Integrated Circuit Card
- Universal Mobile Telecommunications System
- Universal Serial Bus
- Universal Terrestrial Radio Access Network
- User Equipment
- Vehicle
- Web Blog_blogentry_030117_1
- Web Blog_blogentry_090217_1
- Web Blog_blogentry_110718_1
- Web Blog_blogentry_120618_1
- Web Blog_blogentry_130717_1
- Web Blog_blogentry_150816_1
- WebAuthn Client Device
- Who Owns the Data
- Why OpenID Connect
- Why Use Tokens
- XACML
