hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.1.11 RIMS and RIFP | The generation of Ka through algorithm B2 involves the use of two random values RIMS and RIFP. RIMS is sent from CTS-FP to CTS-MS and RIFP is sent from CTS-MS to CTS-FP. Both RIMS and RIFP are 64 bits long. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.1.12 SRES1 and SRES2 | The response expected by the CTS-FP (XSRES1) and the response expected by the CTS-MS (XSRES2) are 32 bit values computed from the authentication key (Ka) and the challenges CH1 and CH2 respectively. XSRES1=B3(Ka,CH1) and XSRES2=B3(Ka,CH2). |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.2 Interfaces to the Algorithm | The dimensioning and definition of the interface parameters to the algorithms described in subclause 6.1 are listed below. In this listing X[i] denoted the i-th bit of the variable X.
FPAC 128 bits: FPAC[0], FPAC[1], …, FPAC[127]
CH1 128 bits: CH1[0], CH1[1],…, CH1[127]
CH2 128 bits: CH2[0], CH2[1],…, CH2[127]
Ka 128 b... |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.3 Implementation and Operational Considerations | The algorithm should be designed for software implementations
As a reference, the set of the algorithms should be implementable on a 6805-family of microprocessors, in particular the Motorola SC21 series and Philips 83C852 series, running at 4 MHz. However the performance of the implementation of the algorithms should ... |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 6.4 Resilience of Algorithm set | The algorithm set should be designed with a view to its continued use for a period of at least 15 years.
The algorithm set should be designed such that:
- the strength of the individual algorithms should not be significantly less than indicated by its key parameter(s);
- the requirements on the individual algorithms li... |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 7 Algorithm specification and test data requirements | ETSI SAGE are required to provide four separate deliverables: a specification of the algorithm, a set of design conformance test data, a set of algorithm input/output test data and a design and evaluation report. Requirements on the specification and test data deliverables are given in this clause, those on the design ... |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 7.1 Specification of the algorithm set | An unambiguous specification of the algorithm set needs to be provided which is suitable for use by implementors of the algorithm set.
The specification shall include an annex which provides simulation code for the algorithm set written in ANSI C. The specification may also include an annex containing illustrations of ... |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 7.2 Design conformance test data | Design conformance test data is required to allow implementors of the algorithm set to test their implementations.
The test data needs to be designed to give a high degree of confidence in the correctness of implementations of the algorithm set.
The test data shall be designed so that significant points in the executio... |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 7.3 Algorithm set input/output test data | Algorithm set input/output test data is required to allow users of the algorithm set to test each member of the algorithm set as a "black box" function.
The input/output test data shall consist solely of data passed across the interfaces to the algorithm set members. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 7.4 Format and handling of deliverables | The specification of the algorithm set shall be produced on paper, and provided only to the ETSI appointed custodian (see subclause 5.4). The document shall be marked "Strictly ETSI confidential" and carry the warning "This information is subject to a licence and confidentiality agreement".
The design conformance test ... |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 8 Quality assurance requirements | This clause advises ETSI SAGE on measures needed to provide users of the algorithm set with confidence that it is fit for purpose, and users of the algorithm set specification and test data assurance that appropriate quality control has been exercised in their production.
The measures shall be recorded by ETSI SAGE in ... |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 8.1 Quality assurance for the algorithm set | Prior to its release to the ETSI custodian, the algorithm set needs to be approved as meeting the technical requirements specified in clause 6 by all members of ETSI SAGE. |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 8.2 Quality assurance for the specification and test data | Prior to delivery of the algorithm set specification, two independent simulations of each algorithm in the set needs to be made using the specification, and confirmed against test data designed to allow verification of significant points in the execution of each algorithm in the set.
Design conformance and algorithm in... |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 8.3 Design and evaluation report | The design and evaluation report is intended to provide evidence to potential users of the algorithm set, specification and test data that appropriate and adequate quality control has been applied to their production. The report shall explain the following:
- the algorithm set and test data design criteria;
- the algor... |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 9 Summary of ETSI SAGE deliverables | - Specification of the algorithm set:
- a confidential document for delivery only to the ETSI custodian;
The specification shall include a simulation code of the algorithm set written in ANSI C.
- Design conformance test data:
- a confidential document for delivery only to the ETSI custodian;
- Algorithm set input/outp... |
7e80bf24517beeb9be2fa8c530e8ca88 | 01.56 | 9.1 Pre-evaluation phase deliverables | - Specification of the algorithm set at the pre-evaluation version of the algorithm set:
- a confidential document for delivery only to manufacturers that have contributed to funding of the algorithm design;
The specification shall include a simulation code of the algorithm set written in ANSI C.
Annex A (informative):... |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 0 Scope | The present document describes and defines a recommended set of Teleservices to be supported by a GSM PLMN in connection with other networks as a basis for defining the network capabilities required.
Teleservices not included in the present document should not be introduced unilaterally by a mobile network operator, if... |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 0.1 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• Fo... |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 0.2 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04 [1]. |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 1 Framework for describing teleservices supported by a GSM PLMN | Teleservices supported by a GSM PLMN are described by a number of attributes which are intended to be largely independent.
These attributes are described and defined in specification GSM 02.01 [2].
They are grouped into three categories:
- High layer attributes;
- Low layer attributes (describing the Bearer capabilitie... |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2 List of the teleservice attributes | Table 1 gives the list of the attributes. For the definitions and possible values of these attributes, see GSM 02.01 [2].
Table 1: List of Teleservice attributes
1. High layer capabilities
1.1 Type of user information
1.2 Layer 4 protocol functions
1.3 Layer 5 " "
1.4 Layer 6 " "
1.5 Layer 7 "... |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1 Information transfer | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1.1 Information transfer capabilities | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1.2 Information transfer mode | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1.3 Information transfer rate | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1.4 Structure | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1.5 Establishment of communication | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1.6 Communication configuration | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.1.7 Symmetry | " "
" "
" "
Individual services (in the category)
2.2 Access (GSM 02.01) |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.2.1 Signalling access | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.2.2 Information access | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.3 Interworking | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.3.1 Terminating network type | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.3.2 National/international interworking | |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2.3.3 Interface of terminal equipment | Qualifying attributes
" "
" "
" "
" "
Further specify the individual services
3. General
3.1 Supplementary services provided
3.2 Quality of service
3.3 Operational and commercial |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 3 List of teleservice categories and individual teleservices | Table 2 presents a list of all Teleservices categories and of individual Teleservices and the associated dominant and secondary attributes. |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 4 Description of individual teleservices | The annex contains a data sheet per Teleservice with all attributes and comments. |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 5 Bearer capabilities supporting teleservices | According to specification GSM 02.01 [2] the Bearer Capability defines the technical features of a Teleservice as they appear to the user at the customer access point or an appropriate interface of a fixed network. The Bearer Capability is characterized by information transfer, access and interworking attributes. The s... |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 6 Possible further evolution phases of teleservices in a GSM PLMN | Possible further evolution phases according to the definition in GSM 01.06 could become necessary. For instance, speech coding procedures (half rate speech codec) will provide for the reduction of the bit rate for speech transmission and thus increase the network capacity.
Table 2: Teleservice categories and Teleservic... |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 1 Introduction | The purpose of this annex is to describe the short message teleservice.
Three different types of short messages are defined, namely short message MT/PP (Mobile Terminated/Point-to-point), short message MO/PP (Mobile Originated/Point-to-point) and Cell Broadcast short messages. |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 2 Definition of the short message service MT/PP and MO/PP | For both mobile originated and mobile terminated services the Service Centre acts as store and forward centre. The Service Centre is functionally separate from the PLMN although this does not preclude an integrated implementation. More than one service centre may be connected to a PLMN. Messages may be input to the ser... |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 3 Reply path | The reply path facility is an enhancement to the point-to-point SMS. In the mobile originated case the mobile user will request his Service Centre to guarantee to forward a single reply to his message back to him (Reply Path).
In the mobile terminated case the recipient of the Short Message will get an indication by th... |
19cea01fe8b3b3d7ca234265f0afe140 | 02.03 | 4 Definition of the cell broadcast short message | The cell broadcast is a Teleservice which enables an Information Provider to submit short messages for broadcasting to a specified area within the PLMN.
The cell broadcast service is characterized by the following aspects:
(i) No acknowledgement is sent from the MS.
(ii) The cell broadcast message is sent on control ch... |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 1 Scope | This TS defines Mobile Station (MS) features and to classifies them according to their type and whether they are mandatory or optional. The MS features detailed in this TS do not represent an exhaustive list. Those MS features which are subject to Type Approval are described in GSM 11.10 [13]. |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 1.1 Normative references | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- Fo... |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 1.2 Definitions and abbreviations | For the purposes of this TS, the following definitions apply:
An MS feature is defined as a piece of equipment of function which directly relates to the operation of the MS. On the basis of this, three categories of features can be distinguished: basic, supplementary and additional features.
Basic MS features: A basic ... |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 2 Requirements for implementing MS features | MS features are qualified as mandatory or optional. Mandatory features have to be implemented as long as they are relevant to the MS type, and will be subject to Type Approval when applied according to GSM 11.10 [13]. Whether or not an optional feature is implemented is left to the manufacturers' discretion. The method... |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 19 User alerting, no answer; | |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 27 Destination out of order; | |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 34 No circuit/channel available; | |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 41 Temporary failure; | |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 42 Switching Equipment congestion; | |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 44 Requested circuit/channel not available; | 47 Resources unavailable, unspecified.
3) "Unobtainable destination - permanent/long term":
Cause number 1 Unassigned (unallocated) number; |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 3 No route to destination; | |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 22 Number changed; | |
dc99f11e189ece5e1f94f5fea750aabc | 02.07 | 28 Invalid number format (uncompleted number); | 38 Network out of order.
NOTE 1: Optionally, it is allowed to implement cause number 27 in Category 3, instead of Category 2, as this is desirable already in Phase 1.
The table below describes a repeat call restriction pattern to any B number. This pattern defines a maximum number (n) of call repeat attempts; when this... |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 1 Scope | The present document defines requirements for call progress and related information to be provided to users of the GSM system. |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 1.1 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• Fo... |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 1.2 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04. |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 1.3 General | There are aspects of the Man Machine Interface (MMI) of the GSM Network which relate to users, but which are not covered by GSM 02.30, which deals specifically with the MMI of the Mobile Station (MS). The present TS covers the means by which mobile users, and callers to a GSM network, will be given information regardin... |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 2 Supervisory tones | |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 2.1 General | Supervisory Tones, indicating primarily ringing, engaged and unobtainable numbers, may be generated by both the PLMN and PSTN.
Except for ring tone, all tones indicating call progress to a MS user shall be generated in the MS, on the basis of signals from the network where available, and are according to the standard d... |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 2.2 Method | In the interests of early release of the traffic channel on failure to succeed in setting up a (mobile originated) call, where possible supervisory tones should be indicated over signalling channels. The MS will then generate the required tones. However, if the network generates an in-band announcement this will be ind... |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 2.3 Standard tones | MS generated tones will be generally in accordance with CEPT (GSM 900 and DCS 1800), or ANSI T1.607 (PCS 1900 for NA) recommendations, where appropriate, and are listed in table 1. Any network originated tones will be according to PLMN or PSTN choice. |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 2.4 Applicability | This method will apply in all cases where signalling is capable of indicating the supervisory tone required. However, for connection to certain fixed networks where this signalling is not possible, fixed network tones will be carried over the traffic channel.
Mobile Stations may employ any suitable technique to indicat... |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 2.5 Point of introduction | Introduction E1. |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 2.6 Comfort tones | If desired by the PLMN operator, the network may optionally introduce "comfort tones" while the call is being connected, during what would otherwise be silence. This would be overridden by indication of a supervisory tone, an announcement or by traffic. PLMNs may offer this feature optionally to incoming or outgoing ca... |
ba0f3e809f4055a7af9e98ebb7feeab9 | 02.40 | 3 Recorded announcements | In present networks, both fixed and cellular, the language of recorded announcements and displayed information is invariably that of the country of origin. However, this is generally undesirable in a multi-lingual environment such as is encountered on a pan-European network with international roaming. It is therefore p... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 1 Scope | The present document defines network functions which are necessary to support services and facilities provided by PLMNs. A summary of the network functions is given in Table 1, where also an indication is given whether the network must support the function. The table also indicates whether or not a function requires in... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 1.1 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• Fo... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 1.2 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2 Network functions for basic service provision | |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1 Call handling | This set of functions enables the establishment of communications between a mobile subscriber and another network subscriber in one of the following types of network PSTN, ISDN, PSPDN, CSPDN and other PLMNs. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1.1 Call from a mobile subscriber registered in VLR | This is the normal case where the call is routed according to the dialled number. After the call, the MSC will send the charging information to the HLR, a billing entity and/or store the charging data on tapes or discs as described in Technical Specification GSM 12.05. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1.2 Call from a mobile subscriber not registered in VLR | When the VLR receives a request for call set-up parameters from an MSC for an MS originating call, where the MS is not registered in the VLR, the VLR shall initiate a location updating procedure towards the HLR and in response parameters are given concerning category, services and restrictions. The call is then set up ... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1.3 Call to a mobile subscriber | The call is routed (re-routed or forwarded) according to location data obtained from the HLR to the actual MSC and the MS is paged over the standardised radio interface.
For MSs in mode of operation A and B the paging may be performed via SGSN. This optional network function is further described in the Technical Specif... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1.4 Call handling functions in HLR | The HLR should also support control functions for handling of supplementary services as described for each service in the GSM 03.8x series of Technical Specifications.
The HLR should provide information to the gateway MSC to allow it to route calls directed to a mobile subscriber: either a Mobile Station Roaming Numbe... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1.5 Call handling functions in VLR | The VLR must provide subscriber parameters to the MSC as required for call handling.
The VLR must also support control functions for handling of supplementary services as described for each service in the GSM 03.8x series of Technical Specifications.
For a MS in mode of operation A or B, the VLR may optionally support ... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1.6 Call handling functions in MSC | The MSC must perform normal call routing and call control functions. The MSC will obtain subscriber parameters from its associated VLR.
The MSC must also be capable of performing handover as defined in section 3.2.
In some cases, the MSC must be able to act as a gateway MSC to provide an interface to other circuit-swit... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.1.7 Call handling functions in SGSN | For a MS in mode of operation A or B, the SGSN may optionally support establishment and maintenance of an association with a VLR. This allows paging for a circuit switched call to be performed via SGSN. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.2 Subscriber identity authentication | The purpose of subscriber identity authentication is defined in Technical Specification GSM 02.09.
The authentication mechanism is defined in Technical Specification GSM 03.20 and corresponding procedures on the MS-BSS interface are defined in Technical Specification GSM 04.08. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.3 Emergency call | |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.3.1 General | The land mobile system should be capable of efficient handling of emergency calls fromMS. The signalling procedures on the radio path for emergency calls are given in Technical Specification GSM 04.08. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.3.2 Routeing | The call should be routed automatically to an appropriate emergency centre based on the geographical location of the MS(e.g. based on the identity of the cell on which the call is established). |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.4 Supplementary services | PLMN may offer supplementary services as shown in Technical Specification GSM 02.04. The support of supplementary services will require control procedures in HLRs, VLRs and MSCs in addition to the control procedure in the fixed network. The technical realisation of supplementary services is given in the GSM 03.8x serie... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.5 Voice group services | The PLMN may offer the voice group services. These are the voice group call service (VGCS) and voice broadcast service (VBS), as shown in GSM 02.68 and GSM 02.69, respectively. The support of the voice group call and voice broadcast services will require control procedures in HLRs, VLRs, MSCs and Group Call Register (G... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.6 Short Message Service | This set of functions allows the transfer of short messages i either direction between a mobile station and a short message service centre. More detailed information is given in Technical Specification GSM 03.40. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.6.1 Short Message Handling functions in the HLR | The HLR should be able to provide information to allow a short message to be routed from the SMS gateway MSC to the visited MSC and/or visited SGSN and then to the required MS. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.6.2 Short Message Handling Functions in the VLR | The VLR should provide subscriber parameters to the MSC as required for handling short messages. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.6.3 Short Message Handling Functions in the MSC | The MSC should perform the functions of relaying short messages in both directions between the fixed network of the PLMN and the BSS.
In some cases the MSC should be able to act as an SMS Gateway MSC to relay short messages from a Short Message Service Centre (SC) to a PLMN, or an SMS Interworking MSC to relay short me... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.6.4 Short Message Handling Functions in the SGSN | The SGSN should perform the functions of relaying short messages in both directions between the fixed network of the PLMN and the BSS. The SGSN should also provide subscriber parameters required for handling the short messages relaying function. The SGSN should also download (from HLR or another SGSN) and store subscri... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.7 Signalling information element confidentiality | A procedure should be implemented providing for the confidentiality of signalling information elements on the radio path. In Technical Specification GSM 02.09 the signalling information elements which need to be protected are given.
The Encryption Key is calculated in both the MS and the network. Detailed information i... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.8 Packet Handling | This set of functions enables routing of packets between an MS and a network host in one of the following types of network: PSPDN, networks based on the Internet Protocol (IP) and other PLMNs.
2.8.1 Packet handling functions in SGSN.
The SGSN should perform the functions of routing packets in both directions between on... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.8.2 Packet handling functions in GGSN | The GGSN should act as a gateway that provides interface(s) to other packet data networks. The GGSN should further perform the functions of routing packets in both directions between these networks and one or more SGSN’s. The GGSN should also download (from SGSN) and store subscriber parameters required for handling th... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 2.8.3 Packet switched service functions in HLR | The HLR should provide permanent storage of subscriber data.
The HLR should provide the identity of the visited SGSN to the SMS gateway MSC to allow it to route short messages directed to a mobile subscriber; further detail is given in Technical Specification GSM 03.40. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 3 Network functions for supporting cellular operation | |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 3.1 Location registration | |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 3.1.1 Definitions | Location registration means that the PLMNs keep track of where MSs are located in the system area. The location information is stored in functional units called location registers. Functionally there are four types of location registers:
- the home location register (HLR) where the current location and all subscriber p... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 3.1.2 Procedures | Procedures related to location registration are specified in Technical Specification GSM 03.12.
They comprise:
i) location updating which enables the MS to inform the network that its location area has to be updated, i.e. the MS has received a location area identity which is different from that contained in its memory... |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 3.1.3 Information stored in location registers | Information to be stored in location registers is listed in Technical Specification GSM 03.08. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.