hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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 series of Technical Specifications. |
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 (GCR) and possibly control procedures in the fixed network. The technical realisation of these services is given in GSM 03.68 and GSM 03.69, respectively. |
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 messages from a PLMN to an SC. |
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 subscriber parameters required for handling the short message relaying functions. |
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 is given in Technical Specification GSM 03.20. |
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 one or more GGSN’s and the BSS. The SGSN should also download (from HLR or another SGSN) and store subscriber parameters required for handling the packet routing functions. |
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 the packet routing functions. |
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 parameters of a MSare permanently stored;
• the visitor location register (VLR) where all relevant parameters concerning a MS are stored aslong as the station is within the area controlled by that visitor location register.
• the serving GPRS support node (SGSN) where all relevant parameters concerning a MS using packet switched services are stored as long as the MS is controlled by that SGSN,
- the GGSN node where routing information for all static PDP addresses related to a mobile subscriber is stored.
See also Technical Specification GSM 03.02 where the network architecture is described. |
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. In order to avoid unnecessary updating, the current location area identity should be stored in a non-volatile memory in the MS;
ii) location cancellation which is used to delete an MS from a VLR or from an SGSN;
iii) periodic location updating which enables the location of stationary MSs to be confirmed at a rate determined by the operator;
iv) as a network option, IMSI detach/attach operation. When a MS has informed the network that it is IMSI detached, the network is aware that the subscriber is not active;
v) routing updating which enables the MS to inform the network that its routing area has to be updated;
vi) periodic routing updating which enables the location of stationary MSs to be confirmed at a rate determined by the operator;
vii) GPRS detach/attach operation. When a MS has informed the network that it is GPRS detached, the network is aware that the subscriber is not active;
viii) cell updating which enables the MS to inform the network that its cell has been updated.
The procedures i) to iv) are defined for circuit switched services, and ii) and v) to viii) are defined for packet switched services. Combined procedures for circuit and packet switched services are also defined in GSM 03.60 for GPRS. The procedure i) may be combined with v), iii) may be combined with vi) and iv) may be combined with vii).
The procedures also include mechanisms for restoration of location registers after failure. These procedures are defined in Technical Specification GSM 03.07. |
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. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 3.2 Handover | |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 3.2.1 Definitions | The following case are required:
i) handover between physical channels of the same Base Station System (BSS). This capability could be used in the following situations:
- when the physical channel carrying the call is subject to interference or other disturbances;
- when a physical channel or channel equipment carrying a call has be to be taken out of service for maintenance or other reasons;
ii) handover between Base Station Systems (BSSs) of the same MSC;
iii) handover between BSSs of different MSCs of the same PLMN.
Cases ii) and iii) are used in order to ensure continuity of the connection when an MS moves from one BSS area to another.
For case iii) two procedures are defined:
a) basic handover procedure where the call is handed over from the controlling MSC (MSC-A) to another MSC (MSC-B);
b) subsequent handover procedure where the call is handed over from MSC-B to MSC-A or to a third MSC (MSC-B'). |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 3.2.2 Procedures | The procedures are described in Technical Specification GSM 03.09. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 3.3 Call re-establishment | Re-establishment of a call may be performed when a traffic channel (TCH) has been lost during the call, e.g. when a handover could not be completed in time.
Call re-establishment is only performed on TCHs and when the call is in the connected state (see Technical Specification GSM 04.08). The procedures are specified in Technical Specification GSM 04.08. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4 Additional network functions for call handling | |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.1 Queuing | As a PLMN option MS originating and/or MS terminating calls may be queued at the BSS. (NOTE: this queuing is additional to that for normal call handling). However, the following condition must be met:
- for MS terminating calls the queuing must not conflict with abnormal release conditions in the fixed network. In general, calls that may have passed international circuits should not be queued, i.e. it should not be applied to calls where the originating network is not known to the PLMN. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.2 Off-Air-Call-Set-Up (OACSU) | |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.2.1 General | OACSU may be implemented in PLMNs in order to increase the call handling capacity of the PLMN.
OACSU may be implemented in PLMNs on an optional basis subject to the following conditions:
i) OACSU should not be used for calls to an international number;
ii) OACSU should not be used for incoming international calls, except where bilateral agreement has been reached to allow such an application of OACSU. For the avoidance of doubt, OACSU shall not be applied to calls where the call type or originating network is not known by the PLMN;
iii) foreign MSs not supporting the OACSU procedure should be allowed to access the PLMNs where OACSU is used;
iv) MSs supporting OACSU should be capable of operating in PLMNs where OACSU is not implemented;
v) OACSU should only be used for telephone calls. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.2.2 Signalling procedures | Signalling procedures supporting OACSU are specified in Technical Specification GSM 04.08. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.3 Security related services | PLMNs will offer three security related services on the radio path: confidentiality of the user identity, confidentiality of user data and confidentiality of signalling information elements and connectionless user data. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.3.1 Identity confidentiality | This service provides for the privacy of the identities of subscribers. An intruder cannot identify which subscriber is using a certain resource on the radio path. Instead of IMSI a temporary identity is used. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.3.1.1 Circuit switched services | This identity (TMSI) is a local number only valid in a given location area. The TMSI is allocated by the VLR and is sent to the MS in a ciphered mode, when ciphering is available as a network option. The IMSI and IMEI should also be transmitted in ciphered mode, whenever the procedure allows this, and when ciphering is available as a network option.
The structure of the TMSI is defined in Technical Specification GSM 03.03. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.3.1.2 Packet switched services | The packet temporary mobile subscriber identity (P-TMSI) is a local number only valid in a given routing area. The P-TMSI is allocated by the SGSN and is sent to the MS in a ciphered mode, when ciphering is available as a network option.
The structure of the TLLI is defined in Technical Specification GSM 03.03. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.3.2 User data confidentiality | This service provides for the confidentiality of anything transmitted on a traffic channel. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.3.2.1 Circuit switched services | Encryption/decryption is done in the MS and BSS with a key which is calculated in both the MS and network. Detailed information is given in Technical Specification GSM 03.20. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.3.2.2 Packet switched services | Encryption/decryption is done in the MS and SGSN with a key which is calculated in both the MS and network. Detailed information is given in Technical Specification GSM 03.20. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.3.3 Signalling Information Element Confidentiality | This service provides for the confidentiality of anything transmitted on a signalling channel |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.3.3.1 Circuit switched services | Signalling information to control the service offered to a subscriber or connectionless user data can be encrypted/decrypted. Encryption/decryption is done in the MS and BSS with a key which is calculated in both the MS and the network. Detailed information is given in Technical Specification GSM 03.20. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.3.3.2 Packet switched services | Signalling information to control the service offered to a subscriber can be encrypted/decrypted. Encryption/decryption is done in the MS and SGSN with a key which is calculated in both the MS and the network. Detailed information is given in Technical Specification GSM 03.20. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.4 Discontinuous Reception | Discontinuous reception is a technique used to reduce the battery consumption ofMSs. The operation of the technique is specified in Technical Specification GSM 03.13. This function must be supported by the network, but is optional forMSs. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.5 Discontinuous Transmission | Discontinuous transmission is a technique used to reduce overall interference level on the radio interface, and to reduce the battery consumption in the MSs. The operation of the technique is specified in Technical Specification GSM 05.08. This function must be supported by the MSs, whereas only the receiver requirements are mandatory in the network. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 4.6 Support of DTMF | DTMF is supported as defined in Technical Specification GSM 03.14. |
5a0e7a8690c6d7a6c171103231d5c462 | 03.01 | 5 Network management oriented network functions | Network management functions are dealt with in the 12 series of GSM Technical Specifications. An overview is given in Technical Specification GSM 12.00.
Annex A (informative):
Change Request History
Change history
SMG No.
TDoc. No.
CR. No.
Section affected
New version
Subject/Comments
SMG#07
4.0.4
ETSI Publication
SMG#17
101/96
B001
5.0.0
Inclusion of "Voice group services" as network function
Release 1996 version
SMG#18
287/96
A003
5.1.0
Queuing indication to the MS in case of Mobile Originating Calls
SMG#27
6.0.0
Release 1997 version
SMG#28
P-99-153
A004
6.1.0
SMG#29
7.0.0
Release 1998 version
History
Document history
V7.0.0
September 1999
Publication |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 1 Scope | The present document describes the support of Videotex service within the GSM PLMN network, taking into account the service definition as per CCITT Recommendation F.300 and Bearer Services specified in GSM 02.02 for a GSM PLMN. |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 2 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.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] ETS 300 072: "Terminal Equipment (TE): Videotext presentation layer protocol Videotext presentation layer syntax".
[2] ETS 300 073: "Videotext presentation layer data syntax; Geometric Display".
[3] ETS 300 075: "Terminal Equipment (TE): Videotext processable data".
[4] ETS 300 079: "Integrated Services Digital Network (ISDN); Syntax based Videotex End-to-end protocols circuit mode DTE-DTE".
[5] ETS 300 080: "Integrated Services Digital Network (ISDN); Lower layer protocols for telematic terminals".
[6] ETS 300 218: "Integrated Services Digital Network (ISDN); Syntax based Videotex Lower layer protocols using packet mode (X.31 Case A abd Case B)".
[7] ETS 300 221: "Terminal Equipment (TE): Syntax based Videotex Lower layer protocols using packet mode access over the Public Switched Telephone Network (PSTN)".
[8] ETS 300 222: "Framework of Videotext Terminal Protocols".
[9] ETS 300 223: "Terminal Equipment (TE): Syntax based Videotex End-to-end protocols".
[10] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms".
[11] GSM 02.02: "Digital cellular telecommunications system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)".
[12] GSM 03.10: "Digital cellular telecommunication system (Phase 2+); GSM Public Land Mobile Network (PLMN) connection types".
[13] GSM 03.70: "Digital cellular telecommunication system (Phase 2+); Routeing of calls to/from Public Data Networks (PDN)".
[14] GSM 07.01: "Digital cellular telecommunications system (Phase 2+); General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
[15] GSM 07.02: "Digital cellular telecommunications system (Phase 2+); Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities".
[16] GSM 07.03: "Digital cellular telecommunications system (Phase 2+); Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities".
[17] GSM 08.20: "Digital cellular telecommunication system (Phase 2+); Rate adaption on the Base Station System ‑ Mobile‑services Switching Centre (BSS ‑ MSC) interface".
[18] CCITT Recommendation E.163: "Numbering plan for the international telephone service".
[19] CCITT Recommendation E.164: "Numbering plan for the ISDN era".
[20] CCITT Recommendation F.300: "Videotext service".
[21] CCITT Recommendation X.31: "Support by Packet Mode Terminal Equipment in ISDN".
[22] CCITT Recommendation X.32: "Interface between Data Terminal Equipment (DTE) and Data Circuit Terminating Equipment (DCE) for terminals operating in Packet Mode and accessing a PSPDN through a PSTN or an ISDN or a CSPDN".
[23] CCITT Recommendation X.75: "Packet -switched signalling system between public networks providing data transmission services". |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 2.1 Abbreviations | In addition to those below, abbreviations used in the present document are listed in GSM 01.04.
AU Access Unit
SBVT Syntax Based Videotex Terminal
VAP Videotex Access Point
VSC Videotex Service Centre
VTX host The computer dedicated to Videotex service |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 3 Service definition | The Videotex service is an interactive service that by means of proper access points and standardized procedures provide the access to data base information stored in host computers external to the PLMN, via public telecommunication networks.
The basic elements considered for a Videotex system are:
- the user terminal;
- the telecommunication network;
- the Videotex host computer or Videotex service access function (PAD/VAP/VSC).
The specific features that are relevant to the service are:
- a Videotex call is usually a mobile originated call, but mobile terminated call are supported as well;
- it is an interactive service;
- the requested information is generally in form of text and/or pictures;
- the information access is under the control of the user;
- there are different Videotex syntax standards , depending on high layer attributes of the service (Profile 1, Profile 2, Profile 3, Profile 4, "ASCII"), ETS 300 073 (Geometric Display), ETS 300 075 (Processable Data), ETS 300 177 (Photographic Syntax).
Common end-to-end protocols for syntax-based Videotex are specified in ETS 300 223 and ETS 300 079. |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 3.1 Videotex service in the GSM context | Figure1 shows the basic concept underlying all the GSM Bearer Services, as defined in GSM 02.02.
The most general case is the GSM PLMN interworking with a Transit Network (PSTN and/or ISDN, none), interconnected to a Terminating Network (PSPDN, PSTN and/or ISDN).
Figure 1/03.43: GSM Bearer Service scheme
As the information transfer mode attribute on the PLMN is always "Circuit", and the information transfer capability is always "UDI", the end-to-end Bearer Service attributes depend mainly on the combination of Transit/Terminating networks utilized in the overall connection.
This means that both "circuit mode" and "packet mode" bearer services are appropriate for Videotex on a GSM PLMN; in particular (see table 4/GSM 02.02):
- BS 21 to BS 26, covering data circuit duplex asynchronous rates up to 9 600 bit/s;
- BS 41 to BS 44 covering PAD access asynchronous rates up to 9 600 bit/s;
- BS 31 to BS 34, covering data circuit duplex synchronous rates up to 9 600 bit/s;
- BS 51 to BS 53, covering packet mode synchronous rates up to 9 600 bit/s;
Concerning packet mode services, the GSM PLMN network supports both:
- basic packet/PAD mode, allowing the GSM users to access dial-in asynchronous (PAD) or synchronous (AU/PH) ports of a PSPDN (to which individual subscriber is subscribed to), using respectively BS 2x or BS 3x GSM Bearer Services;
- dedicated packet/PAD mode, allowing the GSM users a "seemingly immediate" access to the PSPDN word, without any explicit intermediate passage on the transit network to access the PSPDN port; BS 4x and BS 5x are used in this case. |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 4 Network architecture | As identified in CCITT Recommendation F.300, various configurations are permitted for the structure of a Videotex system. A terminal can be connected to a Videotex host server:
- directly by a telecommunication network;
- via a Packet Assembly/Disassembly (PAD);
- via a Videotex Access Point (VAP);
- via a Videotex Service Centre (VSC) which may also act as a Videotex host.
All these configurations can be supported by a GSM PLMN, as detailed in the following network schemes. |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 4.1 Videotex host directly connected to PSTN/ISDN | When it is assumed that the Videotex centre is directly connected to the PSTN/ISDN, the network scheme is as shown in figureig.2 /03.43.
Figure 2/03.43: VTX host directly connected to PSTN/ISDN
With reference to the general scheme in figure1/03.43, the terminating network (in this case working as transit network as well) uses a 3,1 kHz audio information transfer capability; at both ends of the terminating network (MSC/IWF and VTX host) a voiceband modem is allocated, whose actual bit-rate is selected in the BC-IE at Call Establishment, within the GSM standard rates (maximun 9 600 bit/s).
BS 2x series apply in this case. |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 4.2 Videotex host accessed via PAD | Figure 3/03.43 summarizes this configuration, outlining all possible network alternatives.
Figure 3/03.43: VTX host accessed via PAD
The main service alternative concerns basic/dedicated PAD access.
In case of basic PAD access, the transit network (PSTN and/or ISDN) is utilized to access the PAD, remotely located with respected to MSC/IWF; the Videotex customer has to make a E.164 Call to the desired PAD, then a second step is necessary to access the Videotex host.
BS 2x are utilized in this case; the information transfer capability on the transit network is 3.1 kHz audio (PSTN or ISDN).
In case of dedicated PAD access, two options are still possible (see GSM 09.05):
- the PAD is remotely located with respect to the IWF, and automatically connected to IWF, via a dedicated circuit or a data circuit on a public network (PSTN or ISDN), so that the Videotex user has "direct" access to the PAD;
- the PAD is located in the MSC/IWF and connected to the PSPDN via X.25 or X.75.
The dedicated PAD access provides the shortest possible connection from the PLMN to a PAD for both home subscribers staying in the home PLMN and foreign subscribers roaming in a visited PLMN.
BS 4x are utilized for dedicated PAD access. |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 4.3 Videotex host accessed via VAP | Figure 4/03.43 summarizes this configuration, outlining all possible network alternatives.
Figure 4/03.43: VTX host accessed via VAP
Circuit Mode access to the VAP via ISDN transit network (and BS 3x) is according to ETS 300 079 and ETS 300 080.
Concerning Packet Mode access to VAP, again the main choice concerns basic/dedicated packet mode.
In case of basic packet mode configuration, the transit network is utilized to access a conventional X.32 dial port in the PSPDN or a PH function (X.31 Case A), remotely located with respected to MSC/IWF and functionally operating as VAP with respect to Videotex service.
The Videotex customer has to make a E.164/E.163 Call to the desired dial port/PH, then a second step is necessary to access the Videotex host.
BS 3x are utilized in this case; the information transfer capability on the transit network is 3,1 kHz audio (PSTN or ISDN) or UDI (ISDN).
In case of dedicated packet mode, the PH is logically part of the PLMN. The interface between the PH and the PSPDN is X.75 or proprietary; two options are still possible for its physical location:
- the PH is remotely located with respect to the IWF;
- the PH (VAP function) is located in the PLMN.
BS 5x are utilized in this case.
The dedicated packet mode provides the shortest possible connection from the PLMN to a PSPDN for both home subscribers staying in the home PLMN and foreign subscribers roaming in a visited PLMN. |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 4.4 Videotex host accessed via VSC | Though the Videotex Access Function is explicitly separate with respect to the Videotex host, no impact results on the overall Network architecture.
Actually the VSC can be considered a front-end function of the same Videotex host (either physically separate or integrated), so that all the above configuration in principle apply.
In particular the network schemes in Figures 3, 4/03.43 are appropriate, and all the above considerations on basic/dedicated PAD access/packet mode are still relevant. |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 5 Reference configuration of the Mobile Station (MS) | The following types of reference configuration of the MS are possible:
Figure 5/03.43: Reference Configuration of the MS
The definitions of the functional blocks shown in figure 5 are reported in GSM 04.02.
Concerning specific Videotex functions of the terminal, full support of end-to-end protocols for Syntax-based Videotex is granted in a GSM PLMN, within the limitation of 9 600 bit/s as maximum speed, due to inherent bounds of GSM system.
In this respect, TE2 shall be:
- either a conventional Videotex terminal operating in asynchronous circuit mode on a V.series standard interface;
- or a fully compliant SBVT equipment operating in synchronous packet mode as per ETS 300 221 standard (lower layers) and ETS 300 223.
TE1 shall be a typical ISDN-SBVT equipment, operating according to either ISDN Circuit mode (ETS 300 079 and ETS 300 080 standards) or ISDN packet mode (ETS 300 218 and 300 223 standards).
MT0 integrates in a single equipment both Videotex and mobile termination functions. |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 6 Bearer Service configuration and settings | Support of Videotex service on the the GSM PLMN is via GSM standard Bearer Services, as specified in various GSM Technical Specificationa. In the following specific reference on the main technical aspects are reviewed. |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 6.1 Connection Types | Transparent or non-transparent network support can be requested to the GSM PLMN for Videotex service.
The information transfer protocol models are those in figure 6/GSM 03.10, models 1a, 2a, 3a, 4a for ISDN-related MS configurations, and models 1b, 2b, 3b, 4b for PSTN-related MS configurations.
Concerning "Circuit mode" Videotex, the choice between transparent (error prone, fixed delay connection) and non-transparent (error resilient, variable delay connection) network support affects just the QOS general attribute.
For "packet mode" Videotex the transparent support, due to inherent constraints will only work in case of access to a X.32 dial port (see section 8.7/GSM 09.06); therefore "Dedicated packet mode" Videotex is only possible with non-transparent support. |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 6.2 Terminal Adaption functions | The TAFs used for Videotex are the asynchronous and synchronous standards defined in GSM 07-series; rate adaption functions are those specified in GSM 04.21 and GSM 08.20. |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 6.3 Signalling aspects | All GSM standard rates (up to 9 600 bit/s) can be used for Videotex on a GSM PLMN; appropriate settings in BC-IE and LLC (where applicable) fix the rate on the GSM connection, and identify the voiceband modem to be used (when applicable) by the IWF.
When a 1 200/75 bit/s Bearer Capability is requested, the 75 bit/s rate is intended for MS to Network direction only; no provision for "reversing" the channel rates is provided on the GSM Network.
GSM 07.01 is the reference for all technical aspects concerning BC/LLC/HLC on a GSM PLMN. |
157bacc4edc4bb5d3eed6ec0265827dd | 03.43 | 6.4 Network interworking | Ad-hoc Specifications are devoted in the GSM normative to explicitly cover the aspects of PLMN interworking; being Videotex service a generic application running on top of GSM standard Bearer services, all technical aspects in those GSM specifications apply.
The reference are:
- GSM 09.07, which details interworking requirements towards PSTN/ISDN;
- GSM 09.05 and GSM 09.06, which detail interworking requirements towards PSPDN;
- GSM 03.70, defining general Call routing scenarios to/from PDNs.
Concerning packet mode it should be stressed that X.31 Case B is currently not feasible within PLMN (see section 7.4/GSM 09.06).
Moreover for dedicated packet mode, whilst Mobile Originated Calls are fully supported, Mobile Terminated Calls are not supported (see section 9.1/GSM 09.06).
Annex A (informative):
Change Request History
Change history
SMG No.
TDoc. No.
CR. No.
Section affected
New version
Subject/Comments
SMG#07
4.1.2
ETSI Publication
SMG#20
5.0.0
Release 1996 version
SMG#27
6.0.0
Release 1997 version
SMG#29
7.0.0
Release 1998 version
History
Document history
V7.0.0
August 1999
Publication |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7 Indicates GSM Phase 2+ Release 1998; | x the second digit is incremented for technical enhancements, corrections, updates, etc
y the third digit is incremented when editorial only changes have been incorporated in the specification.
National transposition dates
Date of adoption of this EN:
21 July 2000
Date of latest announcement of this EN (doa):
31 October 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e):
30 April 2001
Date of withdrawal of any conflicting National Standard (dow):
30 April 2001
Introduction
This system architecture stage 2 description is part of the overall standard for a GSM based Cordless Telephony System (GSM-CTS).
The system is intended to provide a cordless connection between the PSTN/ISDN network or a GSM network and GSM-based CTS Mobile Stations (GSM-MS) via a private CTS Fixed Part (CTS-FP). |
fcc930975597116eb21de958d20d3f3d | 03.56 | 1 Scope | The present document defines the stage 2 description for the Cordless Telephony System (CTS) based on GSM radio. As the second stage of a three-level structure, it is derived from the stage 1 service description.
As mentioned already in the stage 1 description, a phased approach is indispensable to have an early first specification ready for market needs. The first phase focuses on the requirements necessary to elaborate the radio interface and the security aspects for an application supporting the speech tele-service (including DTMF support) in a residential single cell environment.
The standardisation of the physical layers of the GSM-CTS fixed network interface is not in the scope of the present document. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 2 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.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
1 GSM 01.04: "Abbreviations and Acronyms", Version 5.0.0.
[2] GSM 02.56: "Digital cellular telecommunications system (Phase 2+), Phase 1; GSM Cordless Telephony System (CTS), Phase 1; Service Description; Stage 1".
[3] GSM 03.03 "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification".
[4] GSM 03.20: "Digital cellular telecommunication system (Phase 2+); GSM Cordless Telephony System (CTS), Phase 1, Security related network functions; stage 2".
[5] GSM 03.52 "Digital cellular telecommunication system (Phase 2+); GSM Cordless Telephony System (CTS), Phase 1, Lower layers of the CTS radio interface".
6 GSM 03.40: " Digital Cellular Telecommunications System (Phase 2+); Technical Realisation of the Short Message Service (SMS) Point-to-Point (PP)". |
fcc930975597116eb21de958d20d3f3d | 03.56 | 3 Definitions and abbreviations | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 3.1 Definitions | Besides the definitions according to the CTS stage 1 service description [2] the following definitions are applicable to the present document:
Fixed network: A PSTN or ISDN network.
Access network: the network on which the CTS-FP is connected and which carries the incoming and outgoing calls to the CTS-FP. It could be either a fixed network or a GSM network.
CTS radio interface: The radio interface between CTS-MS and CTS-FP.
CTS-MSIx: CTS Local Mobile Subscriber Identity related to the xth CTS-MS initialised on a CTS-FP
CTS-MS attachment: CTS-MS attachment is a procedure which a CTS-MS initiates when the CTS-MS detects that it is within coverage of a CTS-FP to which the CTS-MS is enrolled.
CTS-MS detachment: CTS-MS detachment is a procedure that the CTS-MS initiates, and indicates to the CTS-FP that the CTS-MS will be no longer reachable by the CTS-FP.
Enrollment: The procedure by which a CTS-MS is made known to a CTS-FP in order that the CTS-FP can provide CTS service. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 3.2 Abbreviations | The following list describes the abbreviations and acronyms used in the present document. The GSM abbreviations explained in GSM 01.04 [1] are not included below.
CTS Cordless Telephony System
CTS FRA CTS Frequency allocation functional entity
CTS HLR CTS Home Location Register Functional entity
CTS-FP CTS-Fixed Part
CTS-MS CTS-Mobile Station
CTS-MSI CTS Mobile Subscriber Identity in the CTS-FP
CTS-MSN CTS Mobile Station Number
CTS-SAP CTS Service Access Point
CTS-SIM CTS Subscriber Identity Module
DPLMN Donor PLMN
GFL Generic Frequency List |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4 Main concepts | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.1 CTS definition | The CTS operator can provide a CTS service which allows (using a modified GSM radio interface) to provide a cordless telephone service attached to the fixed network or to a cellular network. The services offered by CTS are limited to the type of network to which the CTS-FP is connected. In order to offer this service the CTS operator needs to have an agreement with a GSM operator in order to use the frequencies belonging to his PLMN by the CTS FP. This type of PLMN is termed to be a Donor PLMN (DPLMN).
NOTE: The CTS operator may be a GSM operator.
Depending upon the operator agreements a person wanting to operate a CTS-FP (the CTS FP subscriber) may be required to have at least three subscriptions: one with the CTS operator, and one with the GSM operator; and in addition to these subscriptions the CTS FP subscriber needs to have either a subscription to a fixed or GSM operator to which the CTS FP is to be connected or access to a fixed line interface.
The frequencies which the CTS service uses may be controlled by the operator which holds the license for the GSM frequency band used for the service.
The CTS FP subscriber can have agreements with other CTS MS subscribers to use his base station.
The role model is described in [2]. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.2 CTS Network | A CTS network is defined to be made up of one or more CTS cells. When a CTS network has more than one cell these cells are synchronised (in frequency, at TDMA frame edges and TDMA frame number) on the radio interface. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.3 CTS Role models | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.3.1 CTS FP owner's role model | CTS role model for a CTS FP subscriber
In order to receive a valid CTS-GFL the CTS-FP owner needs to have a subscription (2) with a CTS operator. This subscription is materialised by a CTS-SIM card stored in the CTS-FP. The CTS operator has an agreement (3) with a DPLMN part of a GSM operator1 to use its frequencies for CTS allocation.
When the CTS-FP is used in licence exempt mode, the CTS-FP owner does not need to have a subscription (2) with a CTS operator. In this case the frequency allocation to CTS usage is made directly by national authorities.
CTS-FP owner shall also enrol (4) at least one CTS-MS, which has a valid GSM subscription (5) with the GSM operator1.
In parallel, CTS-FP owner needs a subscription (1) with an access network operator in order establish communication over the network. This access network could be either a fixed network or a GSM network depending of CTS-FP capabilities. When the CTS-FP is connected to a GSM network, this GSM operator does not need to have any relation with the GSM operator1 who provides CTS frequencies (DPLMN). |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.3.2 CTS MS subscriber's role model | CTS MS subscriber's role model
The CTS-MS subscriber has a valid subscription (1) with a GSM operator who allows CTS operations. In case of roaming, the VPLMN shall confirm the authorisation to do CTS operations to this CTS-MS.
The CTS MS subscriber has agreement (2) with one CTS-FP owner that allows him to enrol on his CTS FP.
In order to enrol on a CTS-FP, a CTS-MS subscriber may need a subscription (3) with the CTS-operator who control (4) this CTS-FP. This CTS-operator may have an agreement (5) with the GSM-operator of this CTS-MS.
NOTE: this GSM operator may be different from the one who provides frequencies to the CTS-operator.
In order to have access to value added Fixed Mobile Convergence services (e.g. unified number), the CTS-MS subscriber needs a subscription (6) with a FMC service provider. These services and this subscription are outside of the scope of the GSM-CTS standard. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.4 CTS Radio interface | The CTS radio interface is based on the use of a modified GSM radio interface as specified in [5].
The concept is to construct a modified GSM radio interface which requires no change of ME hardware, only software need be changed. The modified GSM radio interface shall (on both uplink and downlink) only cause minimal disturbance to the DPLMN.
In order to achieve this, three concepts have been adopted:
• A modified low power radio interface using GSM burst formats that cause limited disturbance to present GSM mobiles and infrastructure, see [5];
• Adaptive Frequency Allocation (AFA), see [5];
• Total Frequency Hopping (TFH), see [5]. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.4.1 Adaptive Frequency Allocation | In order to minimise interference between CTS networks and GSM networks, an Adaptive Frequency Allocation (AFA) mechanism is adopted, where by the CTS FP chooses frequencies within a valid GFL where the up link and down link is interfered the least. The concept and the mechanisms used are described in more detail in [5]. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.4.2 Total Frequency Hopping | To reduce further the possibility of interference (with the GSM PLMNs and others CTS-FP/MS pairs) a Total Frequency Hopping (TFH) mechanism is adopted. The concept of TFH and the mechanisms used are described in more detail in [5]. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.4.3 CTS and GSM compatibility issues | CTS service cannot be offered to existing mobile implementations without a change of software.
Compatibility issues for GSM mobiles which are not operating in CTS mode may be solved by two ways:
• the CTS radio interface is designed in order to create minimum disturbance to existing mobile implementations as specified in [5];
• and by offering the GSM operator control over the frequencies used for CTS operation. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.5 CTS operational requirements | The CTS operator together with agreements from the GSM operator can define the coverage conditions under which CTS service can be offered to the subscriber. The following coverage conditions are identified:
• GSM coverage from the DPLMN. That is to say where the coverage of the DPLMN meets the cell (re)selection criteria for obtaining DPLMN service.
• Limited coverage from the DPLMN. That is to say where the coverage of the DPLMN doesn't meet cell (re)selection criteria for obtaining service where the CTS-FP is installed.
• No GSM coverage from the DPLMN. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.5.1 GSM coverage from DPLMN | In this case the CTS FP's coverage is fully within the coverage of the DPLMN.
Figure 1: GSM coverage from DPLMN |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.5.2 Limited GSM coverage from DPLMN | Two cases are identified.
Figure 2: Limited GSM coverage from DPLMN
The coverage of the DPLMN is partially achieved in the range of the CTS FP.
Figure 3: Limited coverage from DPLMN within T TRANSPORT
The coverage of the DPLMN is not achieved in the range of the CTS FP but is located within a distance, such that, the time it takes between loss of contact from the DPLMN to the time the CTS MS can be brought into coverage of the CTS FP is within T_TRANSPORT. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.5.3 No GSM coverage from DPLMN | The time between leaving DPLMN and entering the CTS FP coverage is longer than T_TRANSPORT.
Figure 4: No GSM coverage |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.6 CTS Reference Model | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.6.1 General CTS Reference Model | The general reference model of the CTS service has the following additional network elements:
• the CTS-HLR is the functional entity handling CTS-FP subscriptions;
• the CTS-SN is the functional entity performing the communication with CTS-FP via the Cf interface which uses the fixed network as a bearer.
The Cd' interface between CTS-SN and CTS-HLR is used for subscription control of the CTS FPSIM.
The CTS-SN has an interface (Cd) to the GSM HLR in order to receive the challenge/response pairs for authentication of the GSM SIM when authentication of the GSM SIM is required to be performed via the fixed network;
• the CTS-FRA is the functional entity handling the CTS frequency allocation;
• the Local Exchange (is a part of the fixed network), it is accessed by the CTS-MS via the CTS-FP for user communication.
The Local Exchange may be used as a bearer to provide dialogue between CTS-SN to CTS-FP and CTS-SN to CTS-MS.
Figure 5: CTS reference model |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.6.2 Simplified CTS reference model (limited enrolment control) | Initial CTS introduction should may allow an easy introduction of the service. This section deals with simplified CTS reference model.
Simplification of the CTS reference model can be achieved if the CTS operator chooses that enrolment is only checked locally in the CTS-FP see section 4.9.1 Enrolment control at the CTS-FP. In this simplified mode of operation the CTS-FP SIM (which is programmed by the CTS operator) holds information as to which IMSI ranges can be accepted for enrolment. In the case where the IMSI of a CTS-MS is not within the ranges, then the enrolment of the CTS-MS is refused by the CTS-FP. Security for those CTS-MS which can be enrolled is assured at the CTS-FP by local security procedures as specified in [4].
In this case authentication of the CTS-MS by the CTS-SN can be avoided and thus the interface between the CTS-SN and GSM-HLR need not be implemented. The simplified CTS reference model is shown below.
Figure 6: Simplified CTS reference model (limited enrolment control) |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.6.3 Simplified CTS reference model (Licence exempt CTS band) | This section is relative to the usage of CTS capable devices with a CTS license exempt radio band.
In this case the frequency allocation for CTS usage is defined directly by national authorities. All the radio information relative to CTS usage are stored in the CTS-FP by the CTS-FP manufacturer. These radio information are linked with a geographical information which informs the CTS-FP in which country (or region) these frequencies can be used.
When the CTS-FP is used in licence exempt mode, the CTS-FP owner does not need to have a subscription with a CTS operator. Therefore the CTS-FP can work without CTS-SIM card and no exchange with a CTS-SN is necessary.
However when a CTS-SIM card is inserted in the CTS-FP, the CTS-FP shall no more consider the CTS licence exempt information stored in its memory, and shall work operate in licence mode.
The CTS mobile is not informed about the status of the frequency used for CTS (i.e. licensed or licence exempt). The mobile operations are the same in both cases. As in licensed mode all the CTS operations made by the mobile are conditioned to the reception by the MS of the "CTS allowed" information sent by the V-MSC (see chapter 9.2) |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.6.4 CTS connected to PLMN reference model | In the case of a CTS-FP connected to a GSM network the general reference model is modified as described below:
Figure 7: Simplified CTS reference model (limited enrolment control)
The Cf interface between the CTS-FP and the fixed network is replaced by a GSM standard Um interface with a GSM network. On this Um interface the CTS-FP is considered by the GSM network as a standard GSM MS: ie a GSM-ME with a valid GSM SIM card.
It is possible that the GSM network on which the CTS-FP is connected is different from the one used by CTS-MS.
All the exchange between the CTS-SN and the CTS-FP are made via a standard GSM circuit switched data connection, and using the same application signalling than the one defined for the CTS connected to PSTN.
The Cs interface between the CTS-SN and the MSC, will be the most appropriate link to support this circuit switched data stream.
The modifications due to simplified enrolment control (section 4.5.2) are also applicable is the case of CTS connected to PLMN. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.7 GSM Operator control of CTS service | The GSM operator has control of the CTS service that is operating in his PLMN. The stage 3 CTS specifications shall ensure that it shall not be possile to operate a CTS service without the permission of the GSM operator.
When a CTS capable mobile accesses a GSM PLMN it will be provided with information in order to allow the MS to operate CTS within the GSM PLMN. This may be provided to all CTS_MS or on a per CTS-MS basis depending on the GSM operators requirements. If no information is provided for CTS operation then the CTS MS is prohibited from from operating in CTS mode. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.7.1 CTS System control | Control of the CTS operation depends of the frequency scenario of the country (or region) in which CTS service is to be provided. Two scenarios are foreseen:
• licence exempt frequency band is used for CTS operation; this is where the relevant authority in a country (or region) has allocated a frequency band for CTS service and the CTS-FP can determine that it is in that country (or region); and
• shared frequency bands for CTS operation; this is where a GSM operator in a country has allocated part of his frequency for CTS service. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.7.2 GSM Operator control of CTS frequency list | One of the major concepts of CTS is the control of the frequencies for use by the CTS-FPs. The frequency allocation for CTS operation is termed the GFL (Generic Frequency List).
The GFL is the frequency allocation that either a GSM operator has agreed to give to the CTS operator for the operation of a CTS service within a specific geographical area for a specific period of time or a dedicated frequency allocation for CTS operation.
The GFL is made up of a valid period and one or more frequency information.
[Editor's note: frequency information may be valid for specific periods of time during the day (operational period). In this case the clock in the CTS-FP in the CTS-MS should be aligned with the DPLMN; this could be done e.g. by using the GSM NITZ procedure which gives extra mobility information one of which is the local time]
The diagram below represents the structure of a GFL. For a GFL to be valid it must have a current valid period.
Figure 8: GFL structure
The initialisation of a CTS-FP requires a GFL to be given to a CTS-FP. In some cases the GFL needs to be controlled based on location information within the GSM PLMN. Information on the position of the CTS-FP within the DPLMN may be requested to allocate the correct GFL. As the CTS-FP architecture has no capability to transmit and receive like a normal GSM MS, it can not carry out a direct dialogue using the Um interface with the GSM DPLMN and thus its general position can not be ascertained without the help of the CTS-MS. Therefore the CTS-MS is used to provide positional information that can be used by the DPLMN to allocate a GFL to the CTS-FP.
In order that both DPLMN coverage and limited DPLMN coverage scenarios are catered for, a validity time concept is introduced during which positional information provided by the CTS MS is deemed valid. This allows the CTS-FP location to be ascertained and thus the allocation of the GFL to the CTS-FP can be made. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.7.3 CTS system initialisation for license exempt frequency band for CTS operation | In this case the frequency allocation for CTS usage is defined directly by national authorities. All the radio information relative to CTS usage are stored in the CTS-FP by the CTS-FP manufacturer. These radio information are linked with a geographical information which informs the CTS-FP in which country (or region) these frequencies can be used.
When the CTS-FP is connected to both mains power and power supply, the CTS-FP can start to make CTS operations (transmit and received radio bursts according with GSM-CTS specification, enrolled CTS-MS, establish call with PSTN network,…). All these operations are made in respect with the radio information (mainly the CTS-GFL) defined by national authorities and stored in the CTS-FP. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.7.4 CTS system initialisation with DPLMN coverage and limited coverage | In order to avoid that the CTS service be too cumbersome to own, the initialisation of the CTS FP is such that the precise GFL for CTS operational purposes may be obtained sometime after CTS operation has been started. This means that for a short period of time the CTS-FP need not be using the GFL that is best suited to the DPLMN environment in which the CTS-FP is located. During this period the CTS-FP shall operate using a reduced power output. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.7.4.1 First stage CTS-FP initialisation (Temporary GFL allocation) | The CTS-FP SIM shall have a telephone number which is preloaded by the CTS operator when the service is subscribed. This Telephone number is used by the CTS-FP to call the CTS-SN. The CTS-SN can verify the validity of the subscription and perform authentication of the CTS-FP at this stage. The CTS-FP shall also perform the mutual authentication procedures as defined in ref [4].
In most cases location information will not be available on the first initialisation and thus the CTS-SN/CTS-FRA should allocate a Temporary GFL to allow operation of the Um* interface. The CTS-SN can also pass extra information in order to control other operational modes of the CTS-FP.
As part of the GFL maintenance the CTS-FP will be asked to call back the CTS-SN before the expiry of the temporary GFL. The CTS-FP is now able to operate and provide CTS services using a Temporary GFL.
The CTS-MS need not be present during this operation. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.7.4.2 Second stage CTS-FP initialisation (GFL confirmation) | As part of the signalling procedures the CTS-FP shall demand the CTS-MS to provide location information to the CTS‑FP see "9.1.2 Update of CTS FP frequencies". The CTS-FP stores this information and provides it to the CTS‑SN the next time the CTS-FP contacts the CTS-SN. The CTS-SN/CTS-FRA uses this information to allocate/maintain the GFL for CTS operation. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.7.5 CTS system initialisation without DPLMN coverage | The initialisation of a GFL without DPLMN coverage is FFS. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.7.6 GFL update | Once a GFL is confirmed, the GFL may be updated by the operator as part of the regular changes he makes in his frequency plan of the network. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.7.6.1 CTS FP GFL update | Subsequent GFL allocations need not involve the CTS-MS and can be made directly by dialogue between the CTS–FP and the CTS-SN.
In order that frequency planning of the DPLMN can be taken into account when the GFL is updated the CTS-FP with the help of the CTS-MS(s) collects the identity of DPLMN cells which surround the CTS-FP and report this information to the CTS-SN as and when contact to the CTS-FP is made.
These cells are given by the CTS-FP to the CTS-SN network when demanded and are used by the network in the reallocation of the GFL.
The CTS-MSs role in this information gathering is to remember the last cell(s) and time that it camped on before attaching to the CTS FP.
GFL update is controlled by the CTS SN.
The subsequent GFL allocation allows:
• Confirmation of the location of the CTS FP;
• Mutual authentication of the CTS FP and CTS SN (03.20);
• Reallocation of the GFL is based on the analysis of the cell identities and time stamp information and the T_TRANSPORT timer value by the CTS-FRA.
The new GFL is valid when the old GFL expires unless otherwise specified by the CTS-SN.
It should be also possible to update the old GFL during this procedure.
The CTS FP shall handle the two GFLs simultaneously and is responsible for updating the CTS frequencies with the mobiles that are enrolled, as and when, they contact the CTS FP. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.7.7 Erasure of GFL in the CTS FP | The CTS FP will erase a GFL when the period of validity for a GFL expires. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.8 De-initialisation of CTS FP | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.8.1 CTS Operator control mode | A CTS FP will become de-initialised if the CTS FP is:
• Disconnected from the mains power for a period of time [10 minutes]; and/or
• Disconnected from the PSTN connection for a period of time [10 minutes]; and/or
• When the CTS-SIM is removed from the CTS-FP;
• When specifically commanded by CTS SN.
In addition to this a CTS-FP will de-initialise itself if after initialisation there is no valid attachment received within [1 week]. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.8.2 Licence exempt mode | A CTS-FP will de-initialise itself if the country code reported by any attached mobiles does not correspond with the country code stored in the CTS-FP. This is made according with the following procedure:
• In order to avoid illegal roaming of CTS-FP, the CTS-MS(s) collects the identity of DPLMN cells which surround the CTS-FP and report this information to the CTS-FP at each attachment.
• The CTS-MSs role in this information gathering is to remember the last cell(s) and time that it camped on before attaching to the CTS FP.
• The CTS-FP only considers as valid cell identity, the cell identity with the lowest time stamp information inferior or equal than the T_TRANSPORT timer value defined by the national authorities and stored in the CTS-FP. (ref. 9.4)
• If [2] consecutive valid cell identity does not correspond with the country (or the region) where the CTS-FP is allowed to work in licence exempt mode, the CTS-FP shall de-initialise itself.
In complement, the CTS-FP is de-initialised:
• if it is disconnected from the mains power for a period of time 10 minutes; or
• if it is disconnected from the PSTN connection for a period of time 10 minutes; or
• if within 1 week after initialisation, there is no valid attachment received;
• If no valid cell identity is reported to the CTS-FP during a period of 1 month.
In addition, if a CTS-SIM card is inserted in the CTS-FP or if a CTS-SN number is reported to the CTS-FP by a CTS-MS, the CTS-FP shall de-initialised itself from licence exempt mode, and shall to make an attempt of GSM controlled CTS initialisation as specified in section 4.6.4 |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.9 CTS MS Enrolment | Enrolment is the process of obtaining permission to use the CTS service of a CTS-FP by a CTS-MS. The enrolment process may involve the verification of agreements between a CTS-MS subscriber with a CTS operator, a GSM operator and a CTS-FP subscriber and the exchange of information for control of the CTS subscription at the CTS FP.
The process of enrolment is guarded by security procedures at the CTS FP as specified in [4].
Enrolment can be controlled at two levels (defined by the CTS operator). The first level of enrolment control is at the CTS-FP. The second level of control is at the CTS-SN.
A CTS network can be operated using both methods of control. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.