Parameter: Sub-System Number
The Sub-System Number parameter is used to assign a sub-system number to an object within the SS7
SCCP control layer.
Integer values for this parameter are entered into a field.
Allowable values are from 1 to 255.
SSN value SSN SCCP user Description
0 Unknown SSN not known or not used.
1 SCCP management SCCP management
3 ISUP ISDN user part
4 OMAP Operation, Maintenance and Administration Part
5 MAP Mobile Application Part
6 HLR Home Location Register (MAP)
7 VLR Visitor Location Register (MAP)
8 MSC Mobile Switching Center (MAP)
9 EIR Equipment Identifier Register (MAP)
10 AUC Authentication Center
11 ISDN supplementary ISDN Supplementary services
13 BISDNE2EAPP Broadband ISDN Edge-to-Edge Application
14 TCTR TC Test Responder
142 RANAP Radio Access Network Application Part
143 RNSAP Radio Network Subsystem Application Part
145 GMLC Gateway Mobile Location Centre (MAP)
146 CAP CAMEL application part
147 gsmSCF Global System for Mobile Service Control Function (MAP)
148 SIWF Serving GPRS Support Node (MAP)
149 SGSN Serving GPRS Support Node (MAP)
150 GGSN Gateway GPRS Support Node (MAP)
249 PCAP Positioning Calculation Application Part
250 BSC BSSAP BSC Base Station System Application Part (BSSAP-LE)
251 MSC BSSAP MSC Base Station System Application Part (BSSAP-LE)
252 SMLC BSSAP Serving Mobile Location Center (BSSAP-LE)
253 BSSOM Base Station System Operation & Maintenance (A-interface)
254 BSSAP Base Station System Application Part (A-interface)
SAI - Service Area
Identifier
The Service Area Identifier is used to identify an area consisting of one
or more cells belonging to the same LA (Location Area). Such an area is
called a Service Area and can be used for indicating the location of a UE
(User Equipment) to the CN (Core Network). The SAC (Service Area
Code) together with the PLMN -Id (Public Land Mobile Network
Identifier) and the LAC (Location Area Code) will constitute the Service
Area Identifier. SAI = PLMN-Id + LAC + SAC.
Non-access stratum (NAS) is a functional layer in the UMTS and LTE wireless
telecom protocol stacks between the core network and user equipment.[1] This layer is used
to manage the establishment of communication sessions and for maintaining continuous
communications with the user equipment as it moves. The NAS is defined in contrast to
the Access Stratum which is responsible for carrying information over the wireless portion of
the network. A further description of NAS is that it is a protocol for messages passed
between the User Equipment, also known as mobiles, and Core Nodes (e.g. Mobile
Switching Center, Serving GPRS Support Node, or Mobility Management Entity) that is
passed transparently through the radio network. Examples of NAS messages include
Update or Attach messages, Authentication Messages, Service Requests and so forth.
Once the User Equipment (UE) establishes a radio connection, the UE uses the radio
connection to communicate with the core nodes to coordinate service. The distinction is that
the Access Stratum is for dialogue explicitly between the mobile equipment and the radio
network and the NAS is for dialogue between the mobile equipment and core network
nodes. For LTE, the Technical Standard for NAS is 3GPP TS 24.301.
Service Access Point Identifier (SAPI) SAPI identifies a point at which LLC services are provided by an LLE
to a layer-3 entity. Consequently, SAPI identifies an LLE that should process an LLC frame and also a
layer-3 entity that is to receive information carried by the LLC frame. SAPI allows 16 service access
points to be specified. The SAPI values are allocated as shown in table 2. Table 2: Allocation of SAPI
values SAPI Related Service SAP Name 0000 Reserved - 0001 GPRS Mobility Management LLGMM 0010
Tunnelling of messages 2 TOM2 0011 User data 3 LL3 0100 Reserved - 0101 User data 5 LL5 0110
Reserved - 0111 SMS LLSMS 1000 Tunnelling of messages 8 TOM8 1001 User data 9 LL9 1010 Reserved -
1011 User data 11 LL11 1100 Reserved - 1101 Reserved - 1110 Reserved - 1111 Reserved –
MAP-OPEN MAP-DELIMITER User specific service- primitive < a) Opening User specific service MAP-
DELIMITER primitive < < b) Continuing MAP-CLOSE User specific service primitive < c) Closing MAP-U-
ABORT MAP-P-ABORT d) Aborting Figure 5.4/1: Sequencing of services