.rs .\" Troff code generated by TPS Convert from ITU Original Files .\" Not Copyright ( c) 1991 .\" .\" Assumes tbl, eqn, MS macros, and lots of luck. .TA 1c 2c 3c 4c 5c 6c 7c 8c .ds CH .ds CF .EQ delim @@ .EN .nr LL 40.5P .nr ll 40.5P .nr HM 3P .nr FM 6P .nr PO 4P .nr PD 9p .po 4P .rs \v | 5i' .sp 1P .ce 1000 \v'12P' \s12FASCICLE\ VI.12 \v'4P' .RT .ce 0 .sp 1P .LP .EF '% \ \ \ ^'' .OF ''' \ \ \ ^ %' .sp 1P .ce 1000 \fBRecommendations Q.1000 to Q.1032\fR \v'2P' .ce 0 .sp 1P .ce 1000 \fBPUBLIC\ LAND\ MOBILE\ NETWORK\fR .ce 0 .sp 1P .ce 1000 \fBINTERWORKING\ WITH\ ISDN\ AND\ PSTN\fR .ce 0 .sp 1P .LP .rs .sp 28P .ad r BLANC .ad b .RT .LP .bp .LP \fBMontage page 2 \ =\ Page blanche\fR .sp 1P .RT .LP .bp .sp 1P .ce 1000 \v'3P' SECTION\ 1 .ce 0 .sp 1P .ce 1000 \fBPUBLIC\ LAND\ MOBILE\ NETWORK \fR .ce 0 .sp 1P .sp 2P .LP \fBRecommendation\ Q.1000\fR .RT .sp 2P .ce 1000 \fBSTRUCTURE OF THE Q.1000\(hySERIES RECOMMENDATIONS\fR .EF '% Fascicle\ VI.12\ \(em\ Rec.\ Q.1000'' .OF '''Fascicle\ VI.12\ \(em\ Rec.\ Q.1000 %' .ce 0 .sp 1P .ce 1000 \fBFOR PUBLIC LAND MOBILE NETWORKS\fR .ce 0 .sp 1P .LP \fB1\fR \fBGeneral\fR .sp 1P .RT .PP This Recommendation provides an overview of the Q.1000\(hySeries Recommendations specifically aimed at specifying the requirements for the Public Land Mobile Network. .PP The purpose of the Q.1000\(hySeries Recommendations is to provide smoothly: .RT .LP 1) realization of roaming and interworking between PLMNs, .LP 2) portability of terminal equipments, and .LP 3) independent evolution of each PLMN and terminal equipments. .PP In addition some Recommendations of other series are indicated in section 7 because of their interest to the Q.1000\(hySeries. .sp 2P .LP \fB2\fR \fBGeneral Recommendations on \fR \fBPublic Land Mobile Networks\fR .sp 1P .RT .PP Q.1000: Structure of the Q.1000\(hySeries Recommendations for Public Land Mobile Networks .PP This Recommendation gives an overview of the Q.1000\(hySeries and some other Recommendations of interest to them. .RT .PP Q.1001: General aspects of Public Land Mobile Networks .PP This Recommendation covers definitions, architectures and services in public land mobile networks. .RT .PP Q.1002: Network functions .PP This Recommendation defines network functions requiring signalling on the radio path either as subscriber line signalling or as mobile management signalling necessary to support services and facilities provided by PLMNs. .RT .PP Q.1003: Location registration procedures .PP This Recommendation identifies the procedures related to location registration, location cancellation, periodic registration and international mobile subscriber identity attach/detach operations. .RT .PP Q.1004: Location register restoration procedures .PP This Recommendation describes methods that provide security of the data stored in the location registers and details procedures required to restore the location data and supplementary services data after a location register failure. .RT .PP Q.1005: Handover .PP This Recommendation identifies the handling procedures between: radio channels of the same base station; base stations of the same MSC; base stations of different MSCs of the same PLMN; and base stations of MSCs in different PLMNs during handover operations. .bp .RT .sp 2P .LP \fB3\fR \fBTechnical aspects of the services offered in the Public Land Mobile Networks\fR .sp 1P .RT .PP Q.1012: Handling of supplementary services .PP This Recommendation contains the stage 2 descriptions of the supplementary services which can be provided in a PLMN. .PP \fINote\fR \ \(em\ This Recommendation is not published in the Blue Book. It will be finalized and brought into the accelerated procedure early in the next study period. .RT .sp 2P .LP \fB4\fR \fBInterworking with ISDN/PSTN\fR .sp 1P .RT .PP Q.1031: General signalling requirements on interworking between ISDN or PSTN and a PLMN .PP This Recommendation specifies the general signalling requirements to be met in order to ensure a correct integration of the mobile service in the fixed networks. .RT .PP Q.1032: Signalling requirements relating to routing of calls to mobile subscribers .PP This Recommendation specifies the signalling requirements that the fixed networks have to comply with, in order to route a mobile terminating call to the actual MSC. .RT .sp 2P .LP \fB5\fR \fBMobile application part\fR .sp 1P .RT .PP Q.1051: Mobile application part .PP This Recommendation describes network procedures and relevant protocols required to provide the functions listed in Recommendation\ Q.1002. The mobile application part is based on Signalling System No.\ 7. .RT .sp 2P .LP \fB6\fR \fBDigital PLMN access interfaces\fR .sp 1P .RT .PP Q.1061: General aspects and principles relating to digital PLMN access signalling reference points .PP This Recommendation introduces the concept and definition of access signalling reference points which are used as the basis for the specification of signalling required at the Mobile Station and the Base Station. .RT .PP Q.1062: Digital PLMN access signalling reference configurations .PP This Recommendation describes the reference configurations used to identify the various possible physical access arrangements to the digital PLMN. .RT .PP Q.1063: Digital PLMN channel structures and access capabilities at the radio interface (Um reference point) .PP This Recommendation defines the set of channel types, access capabilities and channel configurations with respect to the radio interface. .RT .sp 2P .LP \fB7\fR \fBOther Recommendations of interest to the Q.1000\(hySeries\fR .sp 1P .RT .sp 1P .LP 7.1 \fICharging\fR .sp 9p .RT .PP D.93: Charging and accounting in the international land mobile telephone service (provided via cellular radio systems) .PP This Recommendation covers principles for charging, accounting and settlements between PLMNs. An annex to the Recommendation gives examples of the practical use of the established principles. .bp .RT .sp 1P .LP 7.2 \fINumbering and Routing\fR .sp 9p .RT .PP E.212: Identification plan for land mobile stations .PP This Recommendation covers definitions and mobile station identification plan principles. An annex to the Recommendation contains a list of mobile country or geographical area codes. .RT .PP E.213: Telephone and ISDN numbering plan for land mobile stations in public land mobile networks (PLMN) .PP This Recommendation covers basic requirements for a numbering plan to be used for public land mobile networks. .RT .PP E.214: The structure of the land mobile global title for the signalling connection control part (SCCP). .PP This Recommendation defines and describes the structure of the mobile global title. \v'1P' .RT .sp 2P .LP \fBRecommendation\ Q.1001\fR .RT .sp 2P .sp 1P .ce 1000 \fBGENERAL ASPECTS OF PUBLIC LAND MOBILE NETWORKS\fR .EF '% Fascicle\ VI.12\ \(em\ Rec.\ Q.1001'' .OF '''Fascicle\ VI.12\ \(em\ Rec.\ Q.1001 %' .ce 0 .sp 1P .LP \fR \fB1\fR \fBGeneral\fR .sp 1P .RT .PP This Recommendation covers definitions, architectures and services in Public Land Mobile Networks. .PP The definition section is subdivided into basic, roaming and handover subheadings. .PP The architecture section covers examples of Public Land Mobile Network architecture in roaming and handover situations. .PP The services section covers introductory descriptions of basic and supplementary services that can be provided to the user. .RT .LP \fB2\fR \fBDefinitions\fR .sp 1P .RT .sp 2P .LP 2.1 \fIBasic definitions\fR .sp 1P .RT .sp 1P .LP 2.1.1 \fBPublic Land Mobile Services\fR .sp 9p .RT .PP Telecommunications services provided to moving subscribers (terrestrial applications). .RT .sp 1P .LP 2.1.2 \fBPublic Land Mobile Network\fR .sp 9p .RT .PP A Public Land Mobile Network (PLMN) is established and operated by an administration or RPOA for the specific purpose of providing land mobile telecommunication services to the public. A PLMN may be regarded as an extension of a fixed network (e.g. PSTN) or as an integral part of the PSTN. In the first case, it can be considered as a collection of mobile services switching centre (MSC) areas within a common numbering plan (e.g. service access codes) and a common routing plan (e.g. definition of crossover point); in this case the MSCs are the functional interfaces between the fixed network and a PLMN for call set\(hyup. In the second case, it can be considered as an assemblage of special logic in existing or future PSTN/ISDN stored program controlled digital local exchanges, conceptually integrated within a common numbering and routing plan. .PP Functionally the PLMNs may be regarded as independent telecommunications entities even though different PLMNs may be interconnected through the PSTN and PDNs for forwarding of calls or network information. A\ similar type of interconnection may exist for the interaction between the MSCs of one PLMN. .bp .PP The location register system of a PLMN may be centralized, distributed or segmented. So long as we are concerned with functions of a PLMN, such as routing and interworking, the configuration and operation of the location register system have no influence on external networks. .PP The use of the concept PLMN is illustrated in Figure 1/Q.1001 where various PLMNs are shown with their interfaces to the fixed networks. It should be noted that a PLMN may have several interfaces with the fixed network (e.g. one for each MSC). Interworking between two PLMNs may be performed via an international gateway. .PP Figure\ 1/Q.1001 also shows the information paths between a PSTN and a PLMN and between two different PLMNs. The solid lines indicate a possible physical path between the PLMNs through the PSTN. The dotted line indicates that, for some interactions, an end\(hyto\(hyend information path (established through the physical path) may exist between the two PLMNs. .RT .LP .rs .sp 10P .ad r \fBFigure 1/Q.1001, p. \fR .sp 1P .RT .ad b .RT .sp 1P .LP 2.1.3 \fBMobile Services Switching Centre\fR .sp 9p .RT .PP In an automatic system the Mobile Services Switching Centre (MSC) constitutes the interface between the radio system and the public switched telephone network. The MSC performs all necessary signalling functions in order to establish calls to and from mobile stations. .PP In order to obtain radio coverage of a given geographical area a number of base stations (radio transmittersB/Freceivers) are normally required; i.e. each MSC would thus have to interface several base stations. In addition several MSCs may be required in order to cover a country. The definition of the MSC may be prefixed by the terms \*Qland\*U or \*Qmaritime\*U if that is more suitable in a specific application. .RT .sp 1P .LP 2.1.4 \fBbase station\fR .sp 9p .RT .PP The base station (BS) is the common name for all the radio equipment located at one and the same place used for serving one or several cells. .RT .sp 1P .LP 2.1.5 \fBmobile station\fR .sp 9p .RT .PP The mobile station (MS) is the interface equipment used to terminate the radio path at the user side. It includes terminal functions required to provide services to the user, e.g. terminal equipment and terminal adaptors. .RT .sp 1P .LP 2.1.6 \fBcell\fR .sp 9p .RT .PP The area covered by a base station, or by a sub\(hysystem (sector antenna) of that base station corresponding to a specific logical identification on the radio path, whichever is smaller. .PP Every mobile station in a cell may be reached by the corresponding radio equipment of the base station. .RT .sp 1P .LP 2.1.7 \fBbase station area\fR .sp 9p .RT .PP The area covered by all the cells served by a base station. .RT .sp 1P .LP 2.1.8 \fBlocation area\fR .sp 9p .RT .PP The location area is defined as an area in which a mobile station may move freely without updating the location register. A location area may comprise several cells. .bp .RT .sp 1P .LP 2.1.9 \fBMSC area\fR .sp 9p .RT .PP The part of the network covered by an MSC. An MSC area may consist of several location areas. .RT .sp 1P .LP 2.1.10 \fBservice area\fR .sp 9p .RT .PP The service area is defined as an area in which a mobile station is obtainable by another PLMN, PSTN or ISDN subscriber without the subscriber's knowledge of the actual location of the mobile station within the area. A service area may consist of several PLMNs. One service area may consist of one country, be a part of a country or comprise several countries. The location registration system associated with each service area must thus contain a list of all mobile stations located within that service area. .PP Figure 2/Q.1001 shows an example of the composition of a service area. .PP \fINote\fR \ \(em\ This definition does not take into account any constraints on routing imposed by the international telephone network. .RT .LP .rs .sp 39P .ad r \fBFigure 2/Q.1001, p. \fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP 2.1.11 \fBsystem area\fR .sp 9p .RT .PP The system area consists of one or more service areas with fully compatible MS\(hyBS interfaces. .PP \fINote\fR \ \(em\ The location registers of the individual service areas remain autonomous; updating of the location information is not performed when a roaming mobile station moves from one service area to another. The overall composition of the international land mobile system is shown in Figure\ 3/Q.1001. .RT .LP .rs .sp 25P .ad r \fBFigure 3/Q.1001, p.\fR .sp 1P .RT .ad b .RT .sp 1P .LP 2.1.12 \fBMobile Subscriber International ISDN Number\fR .sp 9p .RT .PP The Mobile Subscriber International ISDN Number is defined as the number which has to be dialled in order to reach a mobile subscriber in a service area. See also Recommendations E.164 and E.213. .RT .sp 1P .LP 2.1.13 \fBinternational mobile station identity\fR .sp 9p .RT .PP The mobile station's identification uniquely identifies the MS internationally. The identity is composed as defined in Recommendation\ E.212. .RT .sp 1P .LP 2.1.14 \fBradio traffic path\fR .sp 9p .RT .PP The radio communication facility between a mobile station and a base station intended to carry a call and uniquely assigned to the mobile station during that call. .RT .sp 1P .LP 2.1.15 \fBradio control path\fR .sp 9p .RT .PP The radio communication facility between a mobile station and a base station intended to carry all the information transfer between the mobile station and the MSC, in which area the mobile station currently is located, during the time that no radio traffic path between that base station and that mobile station is assigned. .bp .RT .sp 2P .LP 2.2 \fIRoaming definitions\fR .sp 1P .RT .sp 1P .LP 2.2.1 \fBlocation register\fR .sp 9p .RT .PP To establish a call to a mobile station the network must know where this mobile station is located. This information is stored in a function named location register. A mobile station is registered at one location register which functions as its home centre for charging and billing purposes and for administering its subscriber parameters. .RT .sp 1P .LP 2.2.2 \fBlocation information\fR .sp 9p .RT .PP The location register should as a minimum contain the following information about a mobile station: .RT .LP \(em international mobile station identity; .LP \(em actual location of the mobile station (e.g. PLMN, MSC area, location area, as required). .sp 1P .LP 2.2.3 \fBhome PLMN\fR .sp 9p .RT .PP The PLMN in which a mobile station is permanently registered. .RT .sp 1P .LP 2.2.4 \fBhome location register\fR .sp 9p .RT .PP The location register to which a mobile station is assigned for record purposes such as subscriber information. .RT .sp 1P .LP 2.2.5 \fBhome MSC\fR .sp 9p .RT .PP The term home MSC (HMSC) may be used in cases where the home location register is implemented in an MSC. .RT .sp 1P .LP 2.2.6 \fBequipment Identity Register\fR .sp 9p .RT .PP The register to which an international mobile equipment identity is assigned for record purposes. .RT .sp 1P .LP 2.2.7 \fBvisited PLMN\fR .sp 9p .RT .PP The PLMN, other than the home PLMN, in which a roaming subscriber is currently located. .RT .sp 1P .LP 2.2.8 \fBvisitor location register\fR .sp 9p .RT .PP The location register, other than the home location register used by an MSC to retrieve information for, for instance, handling of calls to or from a roaming mobile station, currently located in its area. .RT .sp 1P .LP 2.2.9 \fBvisited MSC\fR .sp 9p .RT .PP The term visited MSC (VMSC) may be used in cases where the visitor location register is implemented in an MSC. .RT .sp 1P .LP 2.2.10 \fBgateway PLMN\fR .sp 9p .RT .PP The PLMN which receives a call from a fixed subscriber, via a public switched network, for extension to a mobile station. The gateway PLMN may vary for interconnection with different public networks. .PP The gateway PLMN could be the home PLMN or the visited PLMN or any other. .RT .sp 1P .LP 2.2.11 \fBgateway MSC\fR .sp 9p .RT .PP The MSC which receives a call from a fixed subscriber, via a public switched network, for extension to a mobile station. The gateway MSC may vary for interconnection with different public networks. .PP The gateway MSC may be any MSC of the PLMN, including the HMSC or VMSC if the home and visited location registers are implemented in the MSC. .bp .RT .sp 1P .LP 2.2.12 \fBdesignation method\fR .sp 9p .RT .PP The calling subscriber must know the actual location area of any mobile station. The call is established according to the dialled information only, i.e. the call is not rerouted by the location register when the mobile station currently is in another location area. .RT .sp 1P .LP 2.2.13 \fBnon\(hydesignation method\fR .sp 9p .RT .PP The calling subscriber is not required to know the actual location area of the mobile station. The call is routed according to the dialled information and, if required, rerouted on additional information given by a location register. .RT .sp 1P .LP 2.2.14 \fBmobile station roaming number\fR .sp 9p .RT .PP The network internal number used for routing of calls to the mobile station. See Recommendation\ E.213. .RT .sp 2P .LP 2.3 \fIHandover definitions\fR .sp 1P .RT .sp 1P .LP 2.3.1 \fBhandover\fR .sp 9p .RT .PP Handover is the action of switching a call in progress from one cell to another (or between radio channels in the same cell). Handover is used to allow established calls to continue when mobile stations move from one cell to another (or as a method to minimize co\(hychannel interference). .RT .sp 1P .LP 2.3.2 \fBMSC\(hyA (Controlling MSC)\fR .sp 9p .RT .PP The MSC which first established the radio connection to or from a mobile station for mobile terminating or originating calls respectively. This MSC will be the call controlling MSC for the duration of the call also in cases where a call is handed over to another MSC. .RT .sp 1P .LP 2.3.3 \fBMSC\(hyB\fR .sp 9p .RT .PP The first MSC to which a call is handed over. .RT .sp 1P .LP 2.3.4 \fBMSC\(hyB`\fR .sp 9p .RT .PP The second (or subsequent) MSC to which a call is handed over. .PP \fINote\fR \ \(em\ After the handover is completed and the circuit between MSC\(hyA and MSC\(hyB has been released. MSC\(hyB' will look, from the point of view of MSC\(hyA and the network, like MSC\(hyB did before the handover. .RT .sp 1P .LP 2.3.5 \fBcandidate MSC\fR .sp 9p .RT .PP A Candidate MSC is an MSC which controls cells that could be candidates for receiving a call in case of a handover. .RT .sp 1P .LP 2.3.6 \fBtarget MSC\fR .sp 9p .RT .PP The Target MSC is the MSC controlling the cell(s) selected as target(s) for a handover. .RT .sp 1P .LP 2.3.7 \fBserving MSC\fR .sp 9p .RT .PP The Serving MSC is the MSC which handles the call at the moment. .RT .sp 1P .LP 2.3.8 \fBold serving MSC\fR .sp 9p .RT .PP The old serving MSC is the MSC which was the serving MSC before a handover, other than MSC\(hyA. .bp .RT .LP \fB3\fR \fBArchitecture of the Public Land Mobile Network\fR .sp 1P .RT .sp 2P .LP 3.1 \fIConfiguration of a Public Land Mobile Network\fR .sp 1P .RT .sp 1P .LP 3.1.1 \fIGeneral\fR .sp 9p .RT .PP Figure 4/Q.1001 presents PLMN entities and the associated signalling interfaces. The specific implementation in each country (or PLMN, if more than one in each country) may be different; some of the functional entities may be combined in the same equipment and this may result in some interfaces becoming internal. The configuration of a PLMN must in any case have no impact on the relationship with other PLMNs. Example: PLMN entities and associated signalling interfaces are shown in Figure\ 5/Q.1001. To illustrate some implementation possibilities three examples of configurations are presented in Figures\ 6/Q.1001, 7/Q.1001 and 8/Q.1001. In addition, it can be mentioned that HLR and VLR can be physically implemented in the same equipment, as an integrated Location Register. .RT .sp 1P .LP 3.1.2 \fIConfiguration example No. 1 (No co\(hylocation of functional\fR \fIentities)\fR .sp 9p .RT .PP This configuration is presented in Figure 6/Q.1001. All functions are implemented in dedicated equipment. The interfaces within the PLMN are equipment external and therefore need the support of the Mobile Application Part (MAP) of Signalling System No.\ 7 to exchange the data necessary to provide the mobile service. All PLMN configurations can be deducted from this basic configuration. In instances where some functions are contained in the same equipment, the relevant interfaces become equipment internal to that equipment and the use of the MAP is not necessary. Some examples are given in\ \(sc\(sc\ 3.1.3 and 3.1.4. .RT .sp 1P .LP 3.1.3 \fIConfiguration example No.\ 2 (VLR co\(hylocated with VMSC)\fR .sp 9p .RT .PP This configuration is presented in Figure 7/Q.1001. The Visited Location Register is co\(hylocated with or implemented in the VMSC for the following reasons. The main type of data stored in the VLR is the practical location information (i.e. location area) which has to be updated by the VMSC when the mobile station moves from one location area to another. The VMSC also has to interrogate the VLR at call set\(hyup in order to know the relevant subscriber data (e.g. restrictions and supplementary services). .RT .sp 1P .LP 3.1.4 \fIConfiguration example No. 3 (HLR and VLR co\(hylocated with a MSC)\fR .sp 9p .RT .PP This configuration is presented in Figure 8/Q.1001. In cases where the HLR is implemented in the MSC, this MSC will become the HMSC for the subscribers managed by the Location Register. The two functions HLR and MSC are not of the same type: the HLR is a pure network data base function, interrogated when needed and the MSC is mainly in charge of call handling. The HMSC performs the call handling function for all its subscribers, as defined by their allocation to the HLR, when they are located in the HMSC area. Call set\(hyup to mobile stations handled by the HMSC uses only the international mobile subscriber ISDN/PSTN number and no roaming number is allocated to these mobile stations. .RT .sp 1P .LP 3.2 \fIInterconnection between PLMNs\fR .sp 9p .RT .PP As the configuration of a PLMN does not have any impact on other PLMNs, the specified signalling interfaces can be implemented between entities within a PLMN or between PLMNs, with or without intermediate interface equipment providing a gateway function at the application level. .PP A difference in the interface can be found at lower levels (SCCP), since different signalling networks can be involved in the exchange of messages and they are at least independent with respect to the signalling network addressing plan. .PP A specific interconnection with a PLMN gateway may be needed in cases where the organization and configuration of a PLMN does not meet the international specifications. The specific interconnection is used in this case to mask, from other PLMNs, a national configuration which is not in line with the international specifications. .bp .RT .LP .rs .sp 16P .ad r \fBFigure 4/Q.1001, p.4\fR .sp 1P .RT .ad b .RT .LP .rs .sp 29P .ad r \fBFigure 5/Q.1001, p.5\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 24P .ad r \fBFigure 6/Q.1001, p.6\fR .sp 1P .RT .ad b .RT .LP .rs .sp 24P .ad r \fBFigure 7/Q.1001, p.7\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 28P .ad r \fBFigure 8/Q.1001, p.8\fR .sp 1P .RT .ad b .RT .sp 2P .LP 3.3 \fIPLMN interfaces\fR .sp 1P .RT .sp 1P .LP 3.3.1 \fIGeneral\fR .sp 9p .RT .PP The implementation of the public land mobile service with international roaming and handover implies the exchange of mobile specific signalling information between the equipment involved in the service. The introduction of Signalling System\ No.\ 7 and its signalling network will be an opportunity to transfer the data needed to support the Public Land Mobile Service. Signalling System No. 7 should be used to convey the information, where applicable. In addition some parts of the equipment will have signalling interworking with the fixed network. The descriptions given below are limited to the mobile application. The Mobile Application Part will be supported by the Transaction Capabilities. .RT .sp 1P .LP 3.3.2 \fIInterface between MSC and base station (A interface)\fR .sp 9p .RT .PP The exact definition of the interface between a base station and its MSC depends on the division of functions between BS and MSC. Call handling as well as mobile station management may be split between the two entities. .PP However, the BS\(hyMSC interface will in any case carry information concerning: .RT .LP \(em Call handling .LP \(em Mobility management .LP \(em BS management .LP \(em Mobile station management .bp .sp 1P .LP 3.3.3 \fIInterface between MSC and VLR (B interface)\fR .sp 9p .RT .PP The VLR is the location and management data base for the mobile stations roaming in the area controlled by the associated MSC or MSCs. The MSC interrogates the VLR whenever it needs information relating to a given mobile station currently located in the MSC area. When a mobile station initiates a location updating procedure with an MSC, the MSC informs its VLR which stores the relevant information in its tables. This procedure occurs whenever a mobile station roams to another location area. The MSC also informs the VLR when a subscriber for instance activates a specific supplementary service or modifies some information related to a service. The VLR stores these modifications and updates the HLR, if required. .RT .sp 1P .LP 3.3.4 \fIInterface between MSC and HLR (C interface)\fR .sp 9p .RT .PP This interface is used to exchange signalling information for administrative and routing purposes. .PP In cases where charging information is transferred from an MSC, using Signalling System\ No.\ 7, this interface will be used. .PP In cases where the fixed network is unable to interrogate the HLR, an interrogation from a gateway MSC will be necessary in order to get the call routing information from the HLR, for instance the roaming number (if\ the mobile station is roaming). .RT .sp 1P .LP 3.3.5 \fIInterface between HLR and VLR (D interface)\fR .sp 9p .RT .PP This interface is used to exchange the signalling information related to the location of the mobile station and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to set\(hyup or to receive calls within the service area. To support this, the location registers must exchange signalling information. The VLR informs the HLR of the location of a mobile station managed by the HLR and provides the HLR with the roaming number of that mobile station. The HLR sends to the VLR information needed to support the service to the mobile station. The HLR also informs a VLR which previously served the mobile station to delete all relevant information regarding a mobile station, which has roamed to an MSC area served by another VLR. Exchange of signalling information can also occur for instance when the mobile subscriber activates a supplementary service, when the subscriber wants to change some information related to his subscription or when the administration modifies some parameter of the subscription. .RT .sp 1P .LP 3.3.6 \fIInterface between MSCs (E interface)\fR .sp 9p .RT .PP This interface is used mainly for handover related information exchange between MSCs. A handover is required when a mobile station moves from one MSC area to another during a call in order to continue communication. The MSCs exchange signalling information as a part of the process to determine the best cell for handover and finally to perform the handover if the best cell is in another MSC than the Serving MSC. .RT .sp 1P .LP 3.3.7 \fIInterface between MSC and EIR (F interface)\fR .sp 9p .RT .PP This interface is used for information transfer between an MSC and the equipment identity register, EIR, related to management of national and international mobile equipment identities. .RT .sp 1P .LP 3.3.8 \fIInterface between VLRs (G interface)\fR .sp 9p .RT .PP This interface is used for information transfer between VLRs when a mobile station registers in a new VLR using a temporary mobile station identity, TMSI, assigned by another VLR. This interface is used to retrieve the international mobile subscriber identity, IMSI, from the VLR which assigned the TMSI. .RT .sp 1P .LP 3.3.9 \fIInterface between BS and MS (Um interface)\fR .sp 9p .RT .PP The exact definitions of the interface between base station and mobile station are not part of this specification. .bp .PP However, the BS\(hyMS interface is characterized by the Um reference point: .RT .LP \(em the Um reference point is the traditional over\(hythe\(hyair radio\(hyinterface that is RF technology dependent and includes the physical aspects of the interface to the Base Station. .sp 1P .LP 3.3.10 \fIInterface between user and network\fR .sp 9p .RT .PP The Digital PLMN User\(hyNetwork interface provides: .RT .LP a) flexibility of user terminals with respect to Digital PLMN network interconnection: .LP b) flexibility of separate user terminal evolution and PLMN technology evolution; and .LP c) flexibility of definition and provisioning for PLMN basic bearer services, teleservices and supplementary services. .PP The definition of the User\(hyNetwork interface is for further study. .sp 2P .LP \fB4\fR \fBServices in the public land mobile network\fR .sp 1P .RT .PP The services to be provided in a public land mobile network can be described according to the ISDN service definition principles (see Recommendation\ I.210) as basic services and supplementary services. Examples of these two types of services are telephone service and call forwarding unconditional respectively. .PP The basic services to be provided in the PLMN includes teleservices and bearer services, e.g. telephone and data services (for further study) as well as most other services provided in the ISDN (for further study). .PP The supplementary services to be provided are additional to one or more basic services. .RT .sp 2P .LP \fB5\fR \fBList of Acronyms (Additional acronyms will be included)\fR .sp 1P .RT .LP BS Base Station .LP EIR Equipment Identity Register .LP GMSC Gateway MSC .LP HLR Home Location Register .LP HPLMN Home PLMN .LP IMEI International Mobile Equipment Identity .LP IMSI International Mobile Station Identity .LP MAP Mobile Application Part .LP MCC Mobile Country Code .LP MNC Mobile Network Code .LP MS Mobile Station .LP MSC Mobile Services Switching Centre .LP MSC\(hyA MSC with call control at handover .LP MSC\(hyB MSC to which a handover is done .LP MSC\(hyB` MSC to which a subsequent handover is done .LP MSIN Mobile Station Identity .LP MTP Message Transfer Part .LP NMSI National Mobile Station Identity .LP PLMN Public Land Mobile Network .LP SCCP Signalling Connection Control Part .LP SP Signalling Point .LP TMSI Temporary Mobile Station Identity .LP VLR Visitor Location Register .LP VPLMN Visited PLMN .bp .sp 2P .LP \fBRecommendation\ Q.1002\fR .RT .sp 2P .sp 1P .ce 1000 \fBNETWORK\ FUNCTIONS\fR .EF '% Fascicle\ VI.12\ \(em\ Rec.\ Q.1002'' .OF '''Fascicle\ VI.12\ \(em\ Rec.\ Q.1002 %' .ce 0 .sp 1P .LP \fR \fB1\fR \fBIntroduction\fR .sp 1P .RT .PP This Recommendation defines network functions which may be necessary to support services and facilities provided by PLMNs. A summary of the network functions is given in Table\ 1/Q.1002. The table also indicates whether or not a function requires internetwork signalling between PLMNs (i.e., use of Mobile Application Part, Recommendation\ Q.1051). .RT .LP .sp 1 .ce \fBH.T. [T1.1002]\fR .ce TABLE\ 1/Q.1002 .ce \fBOverview of network functions\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(72p) | cw(90p) | cw(48p) . { Class of network function (NF) } Network function Interworking with MAP _ .T& lw(72p) | lw(90p) | cw(48p) . { NF needed for basic service provision } { Call handling Subscriber authentication Emergency calls Supplementary services } X X \(em X _ .T& lw(72p) | lw(90p) | cw(48p) . { Additional NF needed for call handling } { Queuing Call duration limitation OACSU Mobile station with priority Mobile station with preference Security related services } X \(em \(em \(em \(em X _ .T& lw(72p) | lw(90p) | cw(48p) . { NF needed for supporting cellular operation } { Location registration Hand\(hyover \(em\ in the same BS \(em\ in the same MSC \(em\ in the same PLMN \(em\ between PLMNs Power control Dynamic channel allocation } X \(em \(em \(em X X \(em (X) _ .T& lw(72p) | lw(90p) | cw(48p) . { Operation and maintenance oriented NF } { Test loops Operation Maintenance Charging Traffic survey Malicious call identification Tracing of mobile stations } \(em X X X (X) \(em \(em _ .TE .nr PS 9 .RT .ad r \fBTable 1/Q.1002 [T1.1002], p.\fR .sp 1P .RT .ad b .RT .PP .sp 2 All functions require signalling on the radio path either as subscriber line signalling or as mobile management signalling. .bp .sp 2P .LP \fB2\fR \fBNetwork functions for basic service provision\fR .sp 1P .RT .sp 1P .LP 2.1 \fICall handling\fR .sp 9p .RT .PP This set of functions enables the establishment of communications between a mobile subscriber and another network subscriber in one of the following types of networks: PSTN, ISDN, PSPDN, CSPDN and other PLMNs. .RT .sp 1P .LP 2.1.1 \fICall from MS registered in VLR\fR .sp 9p .RT .PP This is the normal case where the call is routed according to the dialled number. After the call, the MSC shall send the charging information to the HLR, a billing entity and/or store the charging data on tapes or discs. .RT .sp 1P .LP 2.1.2 \fICall from MS not registered in VLR\fR .sp 9p .RT .PP When the VLR receives a request for call set\(hyup 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 toward the HLR and in response parameters are given concerning category, services and restrictions. The call is then set up as in \(sc\ 2.1.1. .RT .sp 1P .LP 2.1.3 \fICall to a mobile subscriber\fR .sp 9p .RT .PP The call is routed (rerouted or forwarded) according to location data obtained from the HLR to the actual MSC. .RT .sp 1P .LP 2.1.4 \fICall handling functions in HLR\fR .sp 9p .RT .PP The HLR should accommodate call routing functions as described in \(sc\ 2.1.3. .PP The HLR should also support control functions for handling of supplementary services. .RT .sp 1P .LP 2.1.5 \fICall handling functions in VLR\fR .sp 9p .RT .PP The VLR should provide subscriber parameters to the MSC as required for call handling. .PP The VLR should also support control functions for handling of supplementary services. .RT .sp 1P .LP 2.1.6 \fICall handling functions in MSC\fR .sp 9p .RT .PP The MSC should perform normal call routing and call control functions. The MSC will obtain subscriber parameters from its associated VLR. .PP The MSC should also be capable of performing handover as defined in \(sc\ 3.2. .PP In some cases the MSC should be able to act as a gateway MSC. .RT .sp 1P .LP 2.2 \fISubscriber authentication\fR .sp 9p .RT .PP Authentication procedures should be implemented in order to protect the network from access by non\(hyregistered or fraudulent MSs. The authentication method is for further study. .PP A possible procedure could be as follows. .PP The procedure is based upon a challenge/signed response method which goes as follows: .RT .LP \(em the fixed subsystem transmits a non\(hypredictable number RAND (the challenge) to the MS; .LP \(em the MS calculates the signature SRES (the signed response) of RAND; .LP \(em the MS transmits the signature SRES to the fixed subsystem; and .LP \(em the fixed subsystem tests the signature for validity. .PP Authentication may take place in the following cases: .LP i) at location registration, .LP ii) at call set\(hyup, .LP iii) when requesting operation of a supplementary service, or .LP iv) after handover. .bp .sp 2P .LP 2.3 \fIEmergency call\fR .sp 1P .RT .sp 1P .LP 2.3.1 \fIGeneral\fR .sp 9p .RT .PP The land mobile system should be capable of efficient handling of emergency calls from mobile stations. Signalling procedures on the radio path require further study. .RT .PP 2.3.2 The call should be routed automatically to an appropriate emergency centre based on the geographical location of the mobile station. For this purpose the accuracy of geographical location determination may be the cell serving the MS. .sp 9p .RT .sp 1P .LP 2.3.3 \fICard operated stations\fR .sp 9p .RT .PP It may be permissible to initiate emergency calls from card operated MSs also when the card is not inserted. This point is for further study. .RT .sp 1P .LP 2.4 \fISupplementary services\fR .sp 9p .RT .PP The support of supplementary services may require control procedures in HLRs, VLRs and MSCs in addition to the control procedures in the fixed network. .RT .LP \fB3\fR \fBNetwork functions for supporting cellular operation\fR .sp 1P .RT .sp 2P .LP 3.1 \fILocation registration\fR .sp 1P .RT .sp 1P .LP 3.1.1 \fIDefinitions\fR .sp 9p .RT .PP Location registration means that the PLMNs keep track of where mobile stations are located in the system area. The location information is stored in functional units called location registers. Functionally there are two types of location registers: .RT .LP \(em the \fBhome location register\fR where the current location and all subscriber parameters of a mobile station are permanently stored, and .LP \(em the \fBvisitor location register\fR where all relevant parameters concerning a mobile station are stored so long as the station is within the area controlled by that visited location register. .PP See also Recommendation Q.1001 where the network architecture is described. .sp 1P .LP 3.1.2 \fIProcedures\fR .sp 9p .RT .PP Procedures related to location registration are specified in Recommendation\ Q.1003. .PP They comprise: .RT .LP i) location register updating which enables the MS to inform the network that its location 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\(hyvolatile memory in the MS; .LP ii) location cancellation which is used to delete an MS from a previous VLR; .LP iii) periodic location updating which enables the location of silent and stationary MSs to be updated at a reasonable rate; and .LP iv) as a network option, IMSI detach/attach operation which will enable MSs to inform the network that they have entered a power down/power up state. .PP The procedures also include mechanisms for restoration of location registers after failure. These procedures are defined in Recommendation\ Q.1004. .sp 1P .LP 3.1.3 \fIInformation stored in location registers\fR .sp 9p .RT .PP Information to be stored in location registers is listed in Recommendation\ Q.1003. .bp .RT .sp 2P .LP 3.2 \fIHandover\fR .sp 1P .RT .sp 1P .LP 3.2.1 \fIDefinitions\fR .sp 9p .RT .PP The following cases are considered: .RT .LP i) handover between radio channels of the same base station; .LP \fINote\fR \ \(em\ This capability could be used in the following situations: .LP \(em when the radio channel carrying the call is subject to interference or other disturbances; and/or .LP \(em when a radio channel or channel equipment carrying a call has to be taken out of service for maintenance or other reasons. .LP ii) handover between base stations of the same MSC in order to ensure continuity of the connection when an MS moves from one BS area to another; .LP iii) handover between base stations of different MSCs of the same PLMN; and .LP iv) handover between base stations of MSCs in difference PLMNs. .LP For cases iii) and iv) two procedures are defined: .LP a) \fBbasic handover procedure\fR where the call is handed over from the controlling MSC (MSC\(hyA) to another MSC (MSC\(hyB); and .LP b) \fBsubsequent handover procedure\fR where the call is handed over from MSC\(hyB to MSC\(hyA or to a third MSC (MSC\(hyB`). .sp 1P .LP 3.2.2 \fIProcedures\fR .sp 9p .RT .PP The procedures are described in Recommendation Q.1005. .RT .sp 1P .LP 3.3 \fIPower control\fR .sp 9p .RT .PP For further study. .RT .sp 1P .LP 3.4 \fIDynamic channel allocation\fR .sp 9p .RT .PP For further study. .RT .LP \fB4\fR \fBAdditional network functions for call handling facilities\fR .sp 1P .RT .sp 2P .LP 4.1 \fIQueuing\fR .sp 1P .RT .sp 1P .LP 4.1.1 \fIGeneral\fR .sp 9p .RT .PP Queuing of calls from fixed and mobile subscribers may be offered as an optional facility. Calls should only be queued when there is congestion on the radio path when the call arrives. The queuing facility is accommodated in the MSC. .RT .sp 1P .LP 4.1.2 \fIQueuing of MS originating calls\fR .sp 9p .RT .PP When an MS originated call is placed in a queue, a queuing indicator should be provided to the MS as display information. The maximum time that the call will be kept in the queue should also be indicated. This would enable timers to be set in the MS in accordance with the queuing arrangements of each PLMN. .PP The MS should be marked as busy when the call is placed in the queue. .PP The call is cancelled when: .RT .LP \(em the MSC receives a clearing message from the MS; .LP \(em there is time\(hyout on the queuing time; or .LP \(em the VLR receives a location cancellation message from the HLR. .LP \fINote\fR \ \(em\ It is for further study whether or not this is practicable. .bp .sp 1P .LP 4.1.3 \fIQueuing of MS terminating calls\fR .sp 9p .RT .PP Queuing facilities for MS terminating calls may also be provided in the MSC. If so, general PSTN/ISDN specifications on abnormal release conditions and post dialling delays should be taken into account. Further study is required on interworking with the fixed network. .PP The MS should be marked as busy when the call is placed in the queue. .PP MS terminating calls should be released if a location cancellation message is received while the call is being queued. .PP \fINote\fR \ \(em\ It is for further study whether or not this is practicable. .RT .sp 1P .LP 4.1.4 \fIQueuing conditions\fR .sp 9p .RT .PP Not more than one call should be queued for each MS. .PP Calls should be queued and serviced in the order they arrive at the MSC, except for calls subject to some priority condition, e.g. calls which are handed over should have priority over normal calls and emergency calls should have priority over any other call. .PP Calls arriving when all positions in the queue are occupied, should be rejected with a congestion indication provided to the calling party. .PP Calls which have been queued for a time longer than the maximum queuing time should be released from the queue. MS terminating calls should be cleared with a congestion indication provided to the calling party. .RT .sp 2P .LP 4.2 \fICall duration limitation\fR .sp 1P .RT .sp 1P .LP 4.2.1 \fIGeneral\fR .sp 9p .RT .PP This is an optional facility. .PP PLMNs may support functions whereby the call duration is limited in order to increase the call handling capacity of the PLMN. Call duration limitation may apply independently to each cell depending on the current traffic load of the cell. If possible, an indication should be provided to the subscribers that a call is subject to call duration limitation. Procedures are for further study. .RT .sp 2P .LP 4.3 \fIOff\(hyair\(hycall\(hyset\(hyup (OACSU)\fR .sp 1P .RT .sp 1P .LP 4.3.1 \fIGeneral\fR .sp 9p .RT .PP OACSU may be implemented in PLMNs in order to increase the call handling capacity of the PLMN. .PP OACSU may be implemented in PLMNs on an optional basis subject to the following conditions: .RT .LP i) OACSU should not be used for calls to an international number; .LP ii) OACSU should not be used for incoming international calls; .LP iii) foreign MSs not supporting the OACSU procedure should be allowed to access the PLMNs where OACSU is used; .LP iv) MSs supporting OACSU should be capable of operating in PLMNs where OACSU is not implemented; .LP v) OACSU must not be used for calls involving an ISDN or a PDN or for non\(hyvoice services in the PSTN. .sp 1P .LP 4.3.2 \fISignalling procedures\fR .sp 9p .RT .PP Interworking requirements for supporting OACSU are described in Recommendation\ Q.1031. .bp .RT .sp 1P .LP 4.4 \fIMobile stations with priority\fR .sp 9p .RT .PP This is an optional facility. .PP It may be possible to offer priority for certain subscribers for: .RT .LP \(em incoming calls; .LP \(em outgoing calls; or .LP \(em all calls. .PP Priority could comprise priority in queuing systems, preemption of outgoing calls in order to service a call with priority, etc. .PP Procedures for handling MSs with priority are for further study. .RT .sp 1P .LP 4.5 \fIMobile stations with preference\fR .sp 9p .RT .PP This is an optional facility. .PP Preference means that in certain circumstances only MSs with preference are allowed to access the network. The condition may be controlled by the BS by inserting a preference indication in the messages sent on the common signalling channel on the radio interface. .PP Procedures for handling of MSs with preference is for further study. .PP It should be possible to set the preference condition individually in each cell. .RT .sp 1P .LP 4.6 \fISecurity related supplementary services\fR .sp 9p .RT .PP PLMNs may offer encryption of information sent on the radio path. Procedures for encryption and key distribution are for further study. .RT .sp 1P .LP 4.7 \fIDiscontinuous reception\fR .sp 9p .RT .PP Discontinuous reception is a technique used to reduce the average battery consumption of mobile stations. The operation of this function is for further study. .RT .sp 1P .LP 4.8 \fIDiscontinuous transmission\fR .sp 9p .RT .PP Discontinuous transmission is a technique used to reduce the battery consumption of mobile stations. The operation of this function is for further study. .RT .sp 2P .LP \fB5\fR \fBOperation and maintenance oriented network functions\fR .sp 1P .RT .sp 1P .LP 5.1 \fITest facilities\fR .sp 9p .RT .PP The public land mobile systems may contain test facilities which can perform tests similar to those defined for the ISDN subscriber line. .PP Further study is required. .RT .sp 2P .LP 5.2 \fIOperation\fR .sp 1P .RT .sp 1P .LP 5.2.1 \fIGeneral\fR .sp 9p .RT .PP In PLMNs tasks related to system operation are divided among several functional units: .RT .LP \(em home location registers, .LP \(em visitor location registers, .LP \(em MSCs, .LP \(em BSs, .LP \(em national operation and maintenance centres, .LP \(em encryption key distribution centres, and .LP \(em centres for management of equipment identities. .bp .PP It should be noted that several of these functional units may be co\(hylocated or even be accommodated in the same physical equipment. .PP In addition, other aspects concerning system operation will be the responsibility of subscribers, MS\ manufacturers, sales agents,\ etc. .PP Tasks allocated to each of the functional units are described below. .RT .sp 1P .LP 5.2.2 \fIResponsibilities of HLRs\fR .sp 9p .RT .PP The main responsibilities of the HLRs are: .RT .LP i) subscriber administration, i.e. management of all subscriber parameters of MSs registered in the HLR. Subscriber administration also includes the possibility of making changes to subscription conditions and subscriber parameters. It may also include additional administrative functions related to CUGs and MSs with preference; .LP ii) charging administration, e.g. relaying of charging information from a foreign PLMN to the charging point in the home PLMN; and .LP iii) updating of VLRs. .sp 1P .LP 5.2.3 \fIResponsibilities of VLRs\fR .sp 9p .RT .PP The main responsibilities of the VLRs are: .RT .LP i) management of mobile station roaming numbers; .LP ii) management of temporary mobile station identities, if implemented; .LP iii) subscriber administration of visiting MSs; .LP iv) updating of HLRs; .LP v) management of MSC areas, location areas and BS areas; and .LP vi) radio channel management (e.g. channel allocation tables, dynamic channel allocation management, channel blocking status). .LP \fINote\fR \ \(em\ Some or all of the functions in vi) may be in the MSC or the BS. This is for further study. .sp 1P .LP 5.2.4 \fIResponsibilities of MSCs\fR .sp 9p .RT .PP The main responsibilities of the MSCs are: .RT .LP i) routing administration; .LP ii) charging and tariff administration; .LP iii) traffic administration, e.g. traffic monitoring; and .LP iv) sending of relevant traffic and charging information to the HLR (see \(sc\ 5.4). .sp 1P .LP 5.2.5 \fIResponsibilities of\fR \fInational 0 & M centres\fR .sp 9p .RT .PP The operational responsibilities of national O & M centres could be remote control and monitoring of the operation of functional units, e.g. remote management of subscriber parameters. .RT .sp 1P .LP 5.2.6 \fIResponsibilities of BSs\fR .sp 9p .RT .PP For further study. .RT .sp 1P .LP 5.2.7 \fIResponsibilities of encryption key distribution centres\fR .sp 9p .RT .PP For further study. .RT .sp 1P .LP 5.2.8 \fIResponsibilities of centres for management of equipment\fR \fIidentities\fR .sp 9p .RT .PP For further study. .bp .RT .sp 2P .LP 5.3 \fIMaintenance\fR .sp 1P .RT .sp 1P .LP 5.3.1 \fIGeneral\fR .sp 9p .RT .PP Maintenance of PLMNs may require activities in several functional units. Some maintenance activities are autonomous, i.e. within one functional unit, and others require cooperation between several functional units. Functional units which may be involved in cooperative maintenance activities are: .RT .LP \(em mobile stations, .LP \(em base stations, .LP \(em MSCs, .LP \(em visitor location registers, .LP \(em home location registers, and .LP \(em national operation and maintenance centres. .PP In some cases maintenance activities may require international cooperation. In such cases the maintenance responsibilities, the information exchanges and the activities required for restoration of service should be in accordance with rules set down for the PSTN/ISDN (M\(hySeries of Recommendations). .sp 1P .LP 5.3.2 \fIMaintenance responsibilities of MSs\fR .sp 9p .RT .PP To some degree the MS should be capable of detecting faulty operation. When faults are detected, the MS should initiate internal testing and prevent accidental transmission. .RT .sp 1P .LP 5.3.3 \fIMaintenance responsibilities of the BSs\fR .sp 9p .RT .PP The BS should monitor the radio path. If faulty operation is detected, information should be sent to the MSC and/or to a national operation and maintenance centre. .PP The BS may also have facilities for blocking and unblocking of radio channels and BS\(hyMSC circuits. .RT .sp 1P .LP 5.3.4 \fIMaintenance responsibilities of MSCs\fR .sp 9p .RT .PP The MSC should include maintenance facilities and support maintenance functions as for exchanges of the PSTN/ISDN. These functions include: .RT .LP i) maintenance of the MSC\(hyBS circuits and signalling links, including: .LP \(em test, observation and measurement of MSC\(hyBS (MSC\(hyMS) protocols; and .LP \(em blocking and unblocking of MSC\(hyBS circuits and radio channels. .LP ii) maintenance of circuits to exchanges of the PSTN/ISDN, .LP iii) maintenance of signalling links to a signalling network, .LP iv) fault reporting to operation and maintenance centres, and .LP v) maintenance of their own equipment. .sp 1P .LP 5.3.5 \fIMaintenance responsibilities of location registers\fR .sp 9p .RT .PP The location registers will be responsible for: .RT .LP i) maintenance of signalling links; and .LP ii) restoration after restarts including information exchange with other location registers. .sp 1P .LP 5.3.6 \fIMaintenance responsibilities of operation and maintenance\fR \fIcentres\fR .sp 9p .RT .PP For further study. .RT .sp 1P .LP 5.4 \fICharging\fR .sp 9p .RT .PP The MSC and the BS must be capable of obtaining all information required for determining call charges for MS originating calls. .bp .PP For charging of MS originating calls information as follows may be required: .RT .LP \(em address of called party, .LP \(em IMSI, .LP \(em time of the call, .LP \(em charging rate for the called destination, .LP \(em call duration and possibly also parameters such as traffic volume and radio channel resources used, .LP \(em additional charges, e.g. for use of supplementary services, .LP \(em charging conditions, e.g. normal charging, debit card, credit card, and .LP \(em location of MS (e.g. cell, location area, MSC area). .PP For calls within the same PLMN the information is directed to the relevant billing entity. How this is achieved is a national concern, however, examples could be: .LP i) by use of the Mobile Application Part; .LP ii) by use of a public data network; .LP iii) by use of dedicated links; .LP iv) by use of physical transfer of magnetic tapes containing the billing information; or .LP v) a combination of the above. .PP Case i) above is specified in Recommendation Q.1051. .PP The need for Recommendations covering the other alternatives is a matter for further study. They may be required to permit different manufacturers equipment to interwork. .PP It should be noted that the use of the Mobile Application Part will only allow charging data on a per call basis to be transferred, though not necessarily immediately after the call has been terminated. For instance if the Mobile Application Part signalling or network processing load is such that the transfer of billing information would compromise normal call set\(hyup procedures, then the transfer of billing information should be delayed until the signalling load decreases (e.g. overnight transmission of stored billing data). .PP In the longer term it is not clear, even if overnight transfer of billing information is used, whether the Mobile Application Part will have sufficient capacity, therefore a move to another technique will be necessary. .PP For calls involving a roaming mobile in a visited PLMN, the same techniques as above can be applied by bilateral agreement. For instance the situation could be imagined where a roaming service is opened between two networks, but the level of roaming traffic does not justify either the use of a public data network, or physical transfer of magnetic tapes, therefore the Mobile Application Part is used initially. .PP The destination for international billing information should be the relevant billing entity of the home network, however, when using the Mobile Application Part, addressing difficulties may mean that only the HLR can be addressed. .PP The MSC may support facilities for debit card calls. The signalling procedure on the radio path should support this type of operation. .PP The MSC may also support facilities for credit card calls. This involves facilities and procedures for authentication of the credit card number and transfer of the required information to the billing authority. The procedures will not be specified for the Mobile Application Part. On a national basis Signalling System No.\ 7, public data networks or other networks convenient for the administration may be used for these purposes. .PP For MS terminating calls where part of or the whole charge is to be paid by the MS, the information to be stored would be similar to that of MS originating calls. Further study is required. .RT .sp 1P .LP 5.5 \fITraffic survey\fR .sp 9p .RT .PP For further study. .bp .RT .sp 1P .LP 5.6 \fIMalicious call identification\fR .sp 9p .RT .PP If required and regulatory and technical constraints permit, the MSC may support the malicious call identification (MCI) facility for MS originating and MS terminating calls. The exact implementation of this facility will depend upon national variations of the signalling system being used. .RT .sp 1P .LP 5.7 \fITracing of mobile stations\fR .sp 9p .RT .PP For further study. \v'1P' .RT .sp 2P .LP \fBRecommendation\ Q.1003\fR .RT .sp 2P .sp 1P .ce 1000 \fBLOCATION\ REGISTRATION\ PROCEDURES\fR .EF '% Fascicle\ VI.12\ \(em\ Rec.\ Q.1003'' .OF '''Fascicle\ VI.12\ \(em\ Rec.\ Q.1003 %' .ce 0 .sp 1P .LP \fR \fB1\fR \fBIntroduction\fR .sp 1P .RT .PP This Recommendation specifies the procedures related to location registration. They include: .RT .LP \(em location registration; .LP \(em location cancellation; .LP \(em periodic registration; and .LP \(em IMSI attach/detach. .PP The procedures in the MS, MSC, VLR and HLR are also given. The procedures utilize the Mobile Application Part (MAP) and details concerning the exchange of information are contained in Recommendation\ Q.1051. .sp 2P .LP \fB2\fR \fBDefinitions\fR .sp 1P .RT .sp 1P .LP 2.1 \fILocation registration\fR .sp 9p .RT .PP Location registration means that the PLMNs keep track of where mobile stations are located in the system area. The location information is stored in functional units called location registers. Functionally there are two types of location registers: .RT .LP \(em the \fBhome location register\fR where the current location and all subscriber parameters of a mobile station are permanently stored; and .LP \(em the \fBvisitor location register\fR where all relevant parameters concerning a mobile station are stored so long as the station is within the area controlled by that visitor location register. .PP See also Recommendation\ Q.1001 where the network architecture is described. .PP The action taken by a mobile station in order to provide location information to the PLMN will be referred to as \fIlocation updating\fR . .RT .sp 1P .LP 2.2 \fILocation area and MSC area\fR .sp 9p .RT .PP The MSC area is composed of the area covered by all base stations controlled by the MSC. An MSC area may consist of several location areas. .PP A location area is an area in which mobile stations may roam without updating the location registers. A location area consists of one or more base station areas. .bp .PP Paging procedures will be required on the radio path if the location area consists of more than one base station area. The paging procedure is used to determine the base station area in which the MS is located. .PP For further details of the network architecture and for definitions, see Recommendation\ Q.1001. .RT .sp 1P .LP 2.3 \fILocation area identification\fR .sp 9p .RT .PP The location area idenfication plan is part of the base station identification plan. The base stations should be identified uniquely and the base station identity should include mobile country code, mobile network (PLMN) code, location area code and base station code within the location area where the location area identification consists of the first three elements. .PP Furthermore, it is viewed that based on network considerations, the mobile country code and base station code may be optional in identifying where the location area identification is included in all messages sent on common signalling channels on the radio path. .RT .sp 1P .LP 2.4 \fIIMSI detach/attach operation\fR .sp 9p .RT .PP IMSI detach operation is the action taken by an MS to indicate to the PLMN that the station has entered an inactive state (e.g.\ the station is powered down). IMSI attach operation is the action taken by an MS to indicate that the station has re\(hyentered an active state (e.g.\ the station is powered up). .PP IMSI detach/attach operation is an optional facility in PLMNs. .RT .sp 1P .LP 2.5 \fIUse of the term mobile station (MS) in this Recommendation\fR .sp 9p .RT .PP In order to simplify the text the term \fImobile station (MS)\fR | s used in relation to location registration refers to the entity where the IMSI is stored, i.e.,\ in the card operated MSs the term \fImobile station (MS)\fR | efers to the card. .RT .sp 2P .LP \fB3\fR \fBProcedures in the MS related to location registration\fR .sp 1P .RT .sp 1P .LP 3.1 \fIInitiation of location register updating\fR .sp 9p .RT .PP Automatic location updating should take place as follows. .PP The mobile station initiates location updating when it detects that it has entered into a new location area. The location area identification should be stored in a non\(hyvolatile memory in the MS so that the memory content does not disappear when the MS is turned off. This will avoid unnecessary location updating when the MS is still in the same location area when it is turned on again. .PP If the MS has lost the location information from memory, it will initiate location updating as soon as it is in an operational state and within radio coverage. .PP Location updating is also initiated on time\(hyout of the timer T defined in \(sc\ 3.2. .PP Location updating via manual intervention in the MS is for further study. .RT .sp 1P .LP 3.2 \fIPeriodic location updating\fR .sp 9p .RT .PP A timer T with the following characteristics could be optionally implemented in the MS: .RT .LP i) timer T is reset to 0 and started when a signalling activity has taken place on the radio path; .LP ii) when the MS is powered down the current value of T is kept in memory, so that when the MS is powered up the timer starts running from the value thus contained in memory; and .LP iii) when timer T reaches its time\(hyout value, the MS initiates a location updating. .PP Timer T thus measures the accumulated time between signalling activities in the MS while the MS is in the powered up state. .PP In order to ensure: .RT .LP a) that the location of silent and stationary MSs are checked at a reasonable rate; and .LP b) that the timer T does not mature to time\(hyout in the majority of cases. .PP The time\(hyout value of timer T should be of the order of several hours (e.g.\ in the range of 12\ to 24\ hours). See also Recommendation\ Q.1004. .bp .sp 1P .LP 3.3 \fIReceiving acknowledgement from the PLMN\fR .sp 9p .RT .PP The MS may receive either of the following acknowledgements from the PLMN. .RT .LP i) \fILocation updated, roaming allowed\fR . In this case normal call handling operations will take place in the MS. .LP ii) \fILocation updated, roaming not allowed\fR . In this case, the MS will not be allowed to make calls. The MS should follow the procedure of \(sc\(sc\ 3.1 and\ 3.2 above. The MS will resume normal operation if it receives a location updated, roaming allowed indication from the PLMN. .LP iii) \fIUpdating failure\fR , indicating that the procedure in the PLMN failed. In this case, the MS should initiate a new updating after a given time. If this attempt fails, the MS should follow the normal procedures of \(sc\(sc\ 3.1 and\ 3.2. When receiving the updating failure indication, the MS should be capable of normal call handling operation. .LP iv) \fIInsufficient identification\fR , indicating that the PLMN was not capable of identifying the MS. The MS should then initiate a new updating using the IMSI. The MS should follow the procedures of \(sc\(sc\ 3.1 and\ 3.2 above. .LP v) \fINot registered\fR , indicating that the MS is not known in the HLR. The MS should then reject any call attempts from the user. However, the MS should follow the normal procedures of \(sc\(sc\ 3.1 and\ 3.2. .LP vi) \fIIllegal subscriber\fR , indicating that the MS is not allowed access to the system for authenticity reasons. The MS may follow the normal procedures of \(sc\(sc\ 3.1 and\ 3.2. .sp 1P .LP 3.4 \fIProcedure when acknowledgement is not received\fR .sp 9p .RT .PP If the MS does not receive an acknowledgement (on layer\ 3) on an updating request, the MS may retransmit the message three times with at least ten seconds (see \(sc\ 3.5) between consecutive attempts. If the procedure fails also for the third time, the general procedures of \(sc\(sc\ 3.1 and\ 3.2 should be followed. .RT .sp 1P .LP 3.5 \fIMinimum time between location updatings\fR .sp 9p .RT .PP The minimum time between consecutive location updatings should be ten\ seconds in order to avoid erroneous location information to be stored because of delays in the signalling network for information transfer via the mobile application part. .RT .sp 1P .LP 3.6 \fIIMSI detach/attach operation\fR .sp 9p .RT .PP IMSI detach/attach operation is an optional facility in PLMNs. The facility is also optional in MSs. .PP The network should provide an indicator to the MS indicating whether or not IMSI detach/attach operation is allowed in a PLMN. MSs which are not equipped for IMSI detach/attach operation will ignore this indicator. MSs which are equipped for IMSI detach/attach operation shall operate in accordance with the received value of the indicator. .PP When IMSI detach/attach operation applies, an MS equipped for this type of operation and located in an area where roaming is allowed should send the IMSI detach signal to the MSC when the MS enters the inactive state (e.g.\ when the MS is powered down). When the MS again enters the active state, .PP the IMSI attach signal is sent to the PLMN, provided that the MS is still in the same location area. If the location area has changed, the normal location upating of \(sc\ 3.1 shall take place. .PP The IMSI detach signal will not be acknowledged from the PLMN. .PP The IMSI attach signal will be acknowledged from the PLMN. If the acknowledgement indicates that the MS is not registered or that the identification is insufficient, the MS should initiate the normal location updating procedure of \(sc\ 3.1. .PP If the acknowledgement is not received, the MS should retransmit the IMSI attach signal after a given time. If the second attempt fails, the MS should follow the procedure of \(sc\ 3.2. However, in this state the MS is allowed to make calls. .bp .RT .sp 1P .LP 3.7 \fILocation updating after handover\fR .sp 9p .RT .PP See Recommendation Q.1005. .RT .sp 1P .LP 3.8 \fISDL description of the procedures in the MS\fR .sp 9p .RT .PP Figure 1/Q.1003 shows state transition diagrams for procedures in the MS related to location updating. The diagrams are intended for guidance. .RT .LP .rs .sp 44P .ad r \fBFigure 1/Q.1003 (Feuillet 1/5), p.10\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 1/Q.1003 (Feuillet 2/5), p.11\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 1/Q.1003 (Feuillet 3/5), p.12\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 1/Q.1003 (Feuillet 4/5), p.13\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 33P .ad r \fBFigure 1/Q.1003 (Feuillet 5/5), p.14\fR .sp 1P .RT .ad b .RT .PP The following states are identified: .sp 1P .LP \fIState 0: inactive\fR .sp 9p .RT .PP This state would in most cases correspond to the powered down state of an\ MS. The input signal IMSI attached may correspond to power up of the station. .RT .sp 1P .LP \fIState 1: Roaming allowed, updated\fR .sp 9p .RT .PP In this state the MS is fully operational. .RT .sp 1P .LP \fIState 2: Wait for updating\fR .sp 9p .RT .PP This is a transitional state where location updating takes place. In this state the MS cannot make or receive calls. .RT .sp 1P .LP \fIState 3: Wait for IMSI attached\fR .sp 9p .RT .PP This transitional state is only required in MSs which are designed for IMSI detach/attach operation. In this state the MS cannot make or receive calls. .bp .RT .sp 1P .LP \fIState 4: Roaming not allowed\fR .sp 9p .RT .PP In this state the MS is not allowed to make calls (except emergency calls) and will not receive calls. .RT .sp 1P .LP \fIState 5: Not updated\fR .sp 9p .RT .PP This state is entered if the location updating or IMSI attach procedure fails. In this state the MS will not receive calls. .RT .sp 2P .LP \fB4\fR \fBProcedures in the MSC/BS related to location updating\fR .sp 1P .RT .PP The MSC/BS will pass messages related to location updating between the MS and the VLR. .PP The MSC/BS will provide the location area identification and IMSI detach/attach supported information to the MS. .RT .sp 2P .LP \fB5\fR \fBProcedures in the location registers\fR .sp 1P .RT .sp 1P .LP 5.1 \fIInformation to be stored in location registers\fR .sp 9p .RT .PP The home and visitor location registers should contain information as defined in Annex\ A. .RT .sp 1P .LP 5.2 \fIInformation transfer between MSCs/BSs and the associated visitor\fR \fIlocation register\fR .sp 9p .RT .PP The procedures for information transfer between MSCs/BSs and the associated visitor location registers using Signalling System No.\ 7 are defined in Recommendation\ Q.1051. .RT .sp 1P .LP 5.2.1 \fINormal location updating and IMSI detach/attach operation\fR .sp 9p .RT .PP When receiving a location register updating message or an IMSI detach/attach message from an MS, the MSC/BS will convey the message to its associated visitor location register. The response from the location register will similarly be conveyed to the MS. .RT .sp 1P .LP 5.2.2 \fILocation updating as part of call set\(hyup\fR .sp 9p .RT .PP Location registration may also take place during call set\(hyup if the request for call set\(hyup comes from an MS which is not registered in the visited location register. This applies in particular to the case where a previous updating was unsuccessful. In such cases the MSC/BS should not establish the call until the location register updating has been completed. .PP Location register updating will also take place if the visitor location register receives signalling information from an unknown MS, e.g.\ a request for activation of a supplementary service. .RT .sp 1P .LP 5.3 \fIIMSI enquiry procedure\fR .sp 9p .RT .PP The MS may either identify itself by the IMSI or the TMSI plus location area identification of the previous VLR. In the latter case the new VLR will enquire the IMSI from the previous VLR by methods defined in Recommendation\ Q.1051. .RT .sp 2P .LP 5.4 \fIInformation transfer between visitor and home location\fR \fIregisters\fR .sp 1P .RT .sp 1P .LP 5.4.1 \fIInterconnection of location registers\fR .sp 9p .RT .PP Location registers may be interconnected by use of Signalling\ System No.\ 7 by procedures defined in Recommendation\ Q.1051. On a national basis other networks may be used for this purpose. .bp .RT .sp 1P .LP 5.4.2 \fIProcedures for location registration\fR .sp 9p .RT .PP Detailed procedures for exchange of location registration and location register updating information between visitor and home location .PP registers are given in Recommendation\ Q.1051. Below follows an overview of these procedures. .RT .sp 1P .LP 5.4.2.1 \fILocation updating procedure\fR .sp 9p .RT .PP This procedure is used when an MS registers with a visitor location register. It will also be used if the visitor location register has to reallocate the mobile station roaming number for an MS (see Recommendation\ E.213). .PP The visitor location register provides routing information to the home location register. This information consists of the mobile station roaming number which is used for routing of calls to the MS. .PP The home location register will then convey the subscriber parameters of the MS which need to be known by the visitor location register for proper call handling. .RT .sp 1P .LP 5.4.2.2 \fILocation cancellation procedure\fR .sp 9p .RT .PP The procedure is used by the home location register to remove a mobile station from a visitor location register. The procedure will normally be used when the MS has moved to an area controlled by a different location .PP register. The procedure can also be used in other cases, e.g.\ an MS ceases to be a subscriber of the home PLMN. .RT .sp 1P .LP 5.4.2.3 \fIDeregistration procedure\fR .sp 9p .RT .PP If supported, the deregistration procedure is initiated by the VLR when it receives an IMSI detach request, see \(sc\ 3.6. The corresponding IMSI is then deleted from the VLR tables. The HLR marks the subscriber as not registered and will reject all calls to that subscriber until a new updating procedure has taken place. .RT .sp 1P .LP 5.4.2.4 \fILocation information requested procedure\fR .sp 9p .RT .PP This procedure enables a visitor register to enquire whether or not an MS is still to be kept in the register. .RT .sp 1P .LP 5.4.2.5 \fILocation information retrieval procedure\fR .sp 9p .RT .PP By use of this procedure the home location register may obtain information on which of its MSs are registered with a visitor location register. The procedure may be used after a restart of the location register. The actual use of this procedure is for further study. .RT .sp 1P .LP 5.4.2.6 \fIReset procedure\fR .sp 9p .RT .PP The reset procedure is used for recovering from a restart of a home location register. A reset message is sent to visitor location registers so that recovery procedures can be initiated. .RT .sp 1P .LP 5.4.2.7 \fIRecovery procedure\fR .sp 9p .RT .PP Recovery and restoration procedures for location registers are defined in Recommendations\ Q.1004 and\ Q.1051. .PP Recovery arrangements should be such that MSs with valid subscriptions are not deleted from the HLR as a result of HLR failure. The worst result of an HLR failure will thus be that some MSs are stored with errors in the temporary subscriber data. .RT .sp 1P .LP 5.5 \fIOverview state diagrams for location registers\fR .sp 9p .RT .PP Figures 2/Q.1003 and 3/Q.1003 contain overview state transition diagrams for the home location register and the visitor location register, respectively, with regard to one MS. Reset procedures are not included in these diagrams, i.e.\ only the normal case is shown. .bp .PP The state description is as follows. .RT .LP i) \fIHome location register\fR .LP \fIState 0: Null\fR . In this state the MS has no subscription with the PLMN. Restart arrangements of the home location register should be such that this state is not reached for any MSs which have a subscription with the PLMN which is valid at the time of the restart. .LP \fIState 1: MS not registered\fR . In this state the location of the MS is not known. The MS is not offered any communication capabilities in this state. .LP \fIState 2: MS in visitor location register (VLR), roaming\fR \fIallowed\fR . In this state the MS is offered communication capabilities in the visitor location register in accordance with those established by the location updating procedure of \(sc\ 5.4.2.1. .LP \fIState 3: MS in visitor location register, roaming not\fR \fIallowed\fR . In this state the MS is not offered any communication capabilities, except emergency calls, in the visitor location register. The home location register will contain an indication that the MS is in an area where the roaming not allowed condition applies. The visitor location register will not store any information concerning that MS. .LP ii) \fIVisitor location register\fR .LP \fIState 0: Null\fR . In this state the MS is not known to the visitor location register. .LP \fIState 1: MS in visitor location register, roaming allowed\fR . In this state the MS is offered communication capabilities in accordance with those established by the location updating procedure of \(sc\ 5.4.2.1. .LP \fIState 2: IMSI detached\fR . In this state the MS is not offered communication capabilities. .sp 2P .LP 5.6 \fIAdditional updating procedures\fR .sp 1P .RT .sp 1P .LP 5.6.1 \fIRegistration/erasure, activation/deactivation, invocation and\fR \fIinterrogation of supplementary services\fR .sp 9p .RT .PP The procedures defined in Recommendation Q.1051 enable MSs to register/erase, activate/deactivate, invoke or interrogate supplementary services in the visitor location register. The visitor location register conveys the necessary information to the home location register. .RT .sp 1P .LP 5.6.2 \fIUpdating of other parameters\fR .sp 9p .RT .PP Recommendation Q.1051 also contains procedures by which the home location register may update any set of subscriber parameters in a visitor location register if they are changed when the MS is in the area controlled by that visitor register. This may correspond to changes in subscription or of other parameters such as authentication parameters. .RT .sp 2P .LP 5.7 \fICall handling functions of location registers\fR .sp 1P .RT .sp 1P .LP 5.7.1 \fIRetrieval of subscriber parameters on a per call basis\fR .sp 9p .RT .PP All subscriber parameters are stored in the home location register. A subset of these parameters are stored in the visitor location register (see Annex\ A). .PP There are also cases where the visitor location register must obtain subscriber parameters on a per call basis from the home location register of the MS. The procedures are defined in Recommendation\ Q.1051. .RT .sp 1P .LP 5.7.2 \fIInterrogation procedures\fR .sp 9p .RT .PP In fixed networks using the ISDN User Part of Signalling System\ No.\ 7 it may be possible for an exchange of the fixed network to .PP retrieve routing information from the home location register of an MS prior to establishing a physical connection for a call. If this is not possible, a gateway MSC will perform this interrogation. \v'1P' .bp .RT .LP .rs .sp 47P .ad r \fBFigure 2/Q.1003 (feuillet 1/3), p.15\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2/Q.1003 (feuillet 2/3), p.16\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2/Q.1003 (feuillet 3/3), p.17\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 24P .ad r \fBFigure 3/Q.1003 (feuillet 1/2), p.18\fR .sp 1P .RT .ad b .RT .LP .rs .sp 23P .ad r \fBFigure 3/Q.1003 (feuillet 2/2), p.19\fR .sp 1P .RT .ad b .RT .LP .bp .ce 1000 ANNEX\ A .ce 0 .ce 1000 (to Recommendation Q.1003) .sp 9p .RT .ce 0 .ce 1000 \fBOrganization of \fR \fBsubscriber data\fR .sp 1P .RT .ce 0 .LP A.1 \fIIntroduction\fR .sp 1P .RT .sp 1P .LP A.1.1 \fIDefinitions\fR .sp 9p .RT .PP For the purpose of this Recommendation the following terms are used. .RT .LP \fBmobile station (MS)\fR : either a physical equipment or a card for which subscriber data are stored. .LP \fBsubscriber data\fR : all information concerning a specific MS which is required for service provisions, identification, authentication, routing, call handling, charging, operation and maintenance purposes. Some subscriber data are referred to as permanent subscriber data, i.e.\ they can only be changed by .LP administrative means. Other data are temporary subscriber data which may change as a result of normal operation of the system. Some data are referred to as flexible length data, i.e.\ further values than those listed may be required in the future. .sp 1P .LP A.1.2 \fIStorage facilities\fR .sp 9p .RT .PP Subscriber data is stored in two types of functional units. .RT .LP \fBhome location register (HLR)\fR : which contains all permanent subscriber data and all relevant temporary subscriber data for all MSs permanently registered in the HLR. .LP \fBvisitor location register (VLR)\fR : which contains all subscriber data required for call handling and other purposes for MSs currently located in the area controlled by the VLR. .PP \fINote\fR \ \(em\ It is for further study whether other types of functional units containing MS parameters are to be included in this Recommendation or not. Such units could include encryption key distribution centres, maintenance centres,\ etc. .sp 2P .LP A.2 \fIDefinition of subscriber data\fR .sp 1P .RT .sp 1P .LP A.2.1 \fIData related to identification and numbering\fR .sp 9p .RT .PP A.2.1.1 \fBinternational mobile station identity (IMSI)\fR is defined in Recommendation\ E.212. It consists of three parts MCC, MNC and MSIN. The MCC consists of 3\ digits and the MNC consists of 1\ or 2\ digits. The IMSI has variable length depending on national requirements. The maximum length is 15\ digits. .PP Only numerical characters (0 through 9) are used in the IMSI. .PP The IMSI is permanent subscriber data, and is stored in both the HLR and the VLR. .PP \fINote\fR \ \(em\ The IMSI for mobile PBXs is for further study. .RT .PP A.2.1.2 \fBinternational mobile station number\fR is defined in Recommendation\ E.213. It is a PSTN/ISDN number and has a variable length which complies with the requirements of the PSTN/ISDN in each country. .sp 9p .RT .PP The international mobile station number is permanent subscriber data. .PP The international mobile station number is stored in both the HLR and the VLR. .PP \fINote\fR \ \(em\ Mobile station numbers for mobile PBXs are for further study. .bp .RT .PP A.2.1.3 \fBtemporary mobile station identity (TMSI)\fR is assigned by the VLR and is used for identification of an MS within the area controlled by the VLR. The purpose of the TMSI is to support location confidentiality to mobile subscribers. TMSIs may not be allocated to all MSs, e.g.\ if the location confidentiality service is offered only on a subscription basis. .sp 9p .RT .PP The TMSI is temporary subscriber data. .PP The TMSI is stored in the VLR. .RT .sp 2P .LP A.2.2 \fIData related to mobile station types\fR .sp 1P .RT .sp 1P .LP A.2.2.1 \fIMobile station category\fR | omprises the following categories: .sp 9p .RT .PP For further study. .PP Only one category is assigned for each MS. .PP Mobile station category is permanent subscriber data. .PP The length of the parameter is one octet. .PP Mobile station category is stored in the HLR and the VLR. .RT .PP A.2.2.2 \fBmode of operation\fR defines whether or not the MS is card operated. Only two possibilities exist: .sp 9p .RT .LP \(em card operated; and .LP \(em not card operated. .PP Mode of operation is permanent subscriber data. .PP The mode of operation is stored in the HLR and the VLR. .PP \fINote\fR \ \(em\ It is for further study whether this data is required or not. .RT .PP A.2.2.3 \fBpreference\fR indicates whether or not an MS is given preference access to the PLMN under certain circumstances. This point is for further study. .sp 9p .RT .PP Preference is permanent subscriber data. .PP Preference is stored in the HLR and the VLR. .RT .sp 1P .LP A.2.3 \fIData related to authentication\fR .sp 9p .RT .PP For further study. .RT .sp 2P .LP A.2.4 \fIData related to roaming\fR .sp 1P .RT .PP A.2.4.1 \fBmobile station roaming number\fR is defined in Recommendation\ E.213. It is a PSTN/ISDN number and has a variable length which complies with the requirements of the PSTN/ISDN in each country. .sp 9p .RT .PP The mobile station roaming number is temporary subscriber data. .PP The mobile station roaming number is stored in the HLR and the VLR. .RT .PP A.2.4.2 \fBlocation area identification\fR consists of three parts: MCC, MNC and LAC, where MCC is the Mobile Country Code and MNC is the Mobile Network Code of Recommendation\ E.212 and LAC is a Location Area Code identifying a location area within a PLMN. MCC and MNC are composed of numerical characters (0 through\ 9). LAC may have a variable length and may be coded using full haxadecimal representation. .sp 9p .RT .PP The overall length of the location area identification is for further study. .PP The location area identification is temporary subscriber data. .PP The location area identification is stored in the VLR. It may also be required in the HLR; this is for further study. .RT .PP A.2.4.3 \fBVLR address\fR is a PSTN/ISDN number and has variable length which complies with the requirements of the PSTN/ISDN in each country. .sp 9p .RT .PP The VLR address is temporary subscriber data. .PP The VLR address is stored in HLR. .bp .RT .sp 1P .LP A.2.5 \fIData related to supplementary services\fR .sp 9p .RT .PP For further study. .RT .sp 2P .LP A.2.6 \fIMobile station status data\fR .sp 1P .RT .PP A.2.6.1 \fBMS registered/deregistered\fR is a parameter indicating whether the MS is in the registered or deregistered state. The parameter takes the following values: .sp 9p .RT .LP \(em registered, or .LP \(em not registered. .PP The parameter is temporary subscriber data. The parameter is stored in the HLR. .sp 1P .LP A.2.7 \fIOther subscriber data\fR .sp 9p .RT .PP This is for further study. .RT .sp 1P .LP A.3 \fISubscriber data stored in HLR\fR .sp 9p .RT .PP The following information should be stored in the HLR for each MS: .RT .LP i) international mobile station identity (\(sc A.2.1.1); .LP ii) international mobile station number (\(sc A.2.1.2); .LP iii) mobile station roaming number (\(sc A.2.4.1); .LP iv) mobile station category (\(sc A.2.2.1) and mode of operation (\(sc\ A.2.2.2); .LP v) preference (if implemented) (\(sc A.2.2.3); .LP vi) authentication parameters (\(sc A.2.3); .LP vii) VLR address (if received) (\(sc A.2.4.3); .LP viii) location area identification (if required) (\(sc A.2.4.2); .LP ix) supplementary service type (\(sc A.2.5.1.1); .LP x) mobile station status data (\(sc A.2.6); and .LP xi) other subscriber data, if required (\(sc A.2.7). .sp 1P .LP A.4 \fISubscriber data stored in VLR\fR .sp 9p .RT .PP The following information should be stored in the VLR for each visiting MS: .RT .LP i) international mobile station identity (\(sc A.2.1.1); .LP ii) international mobile station number (\(sc A.2.1.2); .LP iii) mobile station roaming number (\(sc A.2.4.1); .LP iv) temporary mobile station identity (\(sc A.2.1.3); .LP v) mobile station category (\(sc A.2.2.1) and mode of operation (\(sc A.2.2.2.); .LP vi) preference (if implemented) (\(sc A.2.2.3); .LP vii) authentication parameters (\(sc A.2.3); .LP viii) location area identification (\(sc A.2.4.2); and .LP ix) other subscriber data, if required (\(sc A.2.7). .sp 1P .LP A.5 \fIAccessing subscriber data\fR .sp 9p .RT .PP It should be possible to retrieve or store subscriber data concerning a specific MS from the HLR by use of each of the following references: .RT .LP \(em international mobile station identity; or .LP \(em international mobile station number. .PP It should be possible to retrieve or store subscriber data concerning a specific MS from the VLR by use of each of the following references: .LP \(em international mobile station identity; .LP \(em mobile station roaming number; or .LP \(em temporary mobile station identity. .LP .bp