hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.4.1 Subscriber on home PLMN | ........................................................................................................................ 14 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.4.2 Subscriber on visited PLMN | ...................................................................................................................... 14 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.5 Mobile originated mobile terminated calls | ...................................................................................................... 14 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.6 Subscriber profiles | ........................................................................................................................................... 14 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.7 GSM bearer services quality of service | ........................................................................................................... 14 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9 Dedicated packet mode service | ..............................................................................................................15 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9.1 General | ............................................................................................................................................................. 15 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9.2 General application rules | ................................................................................................................................. 16 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9.3 Specific application of rules for dedicated packet mode service | ..................................................................... 16 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9.4 Mobile originated calls | .................................................................................................................................... 17 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9.4.1 General | ....................................................................................................................................................... 17 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9.4.2 Short code | .................................................................................................................................................. 18 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9.5 Particular packet access functionality | .............................................................................................................. 18 Annex A: Change history......................................................................................................................19 History..............................................................................................................................................................20 (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 4 3G TS 29.006 version 3.0.0 Foreword This Technical Specification has been produced by the 3GPP. This TS identifies the Interworking Functions (IWFs) and requirements for the interworking between a GSM Public Land Mobile Network (PLMN) and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet services in GSM PLMNs within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 5 3G TS 29.006 version 3.0.0 1 Scope The present document identifies the Interworking Functions (IWF's) and requirements for the interworking between a GSM PLMN and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet services in GSM PLMNs. In the GSM PLMN context the packet services are associated with bearer services and are described in GSM 02.02. The generally defined GSM PLMN user-network access as defined in the respective GSM specifications (see references) forms the basis for defining the particularities for the provision of packet services to the GSM PLMN subscribers. Network internal interfaces for the support of packet services in the pan-European ISDN are defined in ETSI standards, which are also taken as a basis. User-network access and network internal interfaces are defined to provide the packet services. 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. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] CCITT Recommendation X.25: "Interface between data terminal equipment (DTE) and data circuit-terminating equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit". [3] CCITT Recommendation X.31: "Support of packet mode terminal equipment by an ISDN". [4] CCITT Recommendation X.32: "Interface between data terminal equipment (DTE) and data circuit-terminating equipment (DCE) for terminals operating in the packet mode and accessing a packet switched telephone network or an integrated services digital network or a circuit switched public data network". [5] ETS 300 007: "Integrated Services Digital Network (ISDN); Support of packet-mode terminal equipment by an ISDN". [6] ETS 300 099: "Integrated Services Digital Network (ISDN); Specification of the Packet Handler access point Interface (PHI)". [7] ETS 300 102: "Integrated Services Digital Network (ISDN); User-network interface layer 3 Specifications for basic call control Specification Description Language (SDL) diagrams". [8] ETR 010: "ISDN Standards Management (ISM); The ETSI basic guide on the European integrated services digital network". [9] GSM 02.02: "Digital cellular telecommunications system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)". [10] GSM 02.03: "Digital cellular telecommunications system (Phase 2+); Teleservices supported by a GSM Public Land Mobile Network (PLMN)". (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 6 3G TS 29.006 version 3.0.0 [11] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [12] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of charge (AoC) Supplementary Services - Stage 1". [13] GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) Supplementary Services - Stage 1". [14] GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification". [15] GSM 03.10: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) connection types". [16] GSM 03.70: "Digital cellular telecommunications system (Phase 2+); Routeing of calls to/from Public Data Networks (PDN) and the GSM Public Land Mobile Network (PLMN)". [17] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [18] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [19] GSM 04.21: "Digital cellular telecommunications system (Phase 2+); Rate adaption on the Mobile Station - Base Station System (MS - BSS) Interface". [20] GSM 04.22: "Digital cellular telecommunications system (Phase 2+); Radio Link Protocol (RLP) for data and telematic services on the Mobile Station - Base Station System (MS - BSS) interface and the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [21] GSM 07.01: "Digital cellular telecommunications system (Phase 2+); General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". [22] GSM 07.03: "Digital cellular telecommunications system (Phase 2+); Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities". [23] GSM 08.20: "Digital cellular telecommunications system (Phase 2+); Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [24] GSM 09.03: "Digital cellular telecommunications system (Phase 2+); Signalling requirements on interworking between the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) and the Public Land Mobile Network (PLMN)". [25] GSM 09.07: "Digital cellular telecommunications system (Phase 2+); General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 7 3G TS 29.006 version 3.0.0 3 Definitions and abbreviations Use is made of the following terms within the present document. These terms refer to information requirements necessary to support interworking functions, some of these terms will be identifiable with their use in other specifications. For the purposes of the present document, the following definitions apply: bearer capability information: Specific information defining the lower layer characteristics required within the network. lower layer capability information: Information defining the lower layer characteristics of the terminal. higher layer capability information: Information defining the higher layer characteristics of a teleservice active on the terminal. protocol identifier: Information defining the specific protocols utilised for the support of data transfer by a terminal. service profile: Set of values of the network default and user selectable attributes selected for a particular DTE identity. loop detection: Detection of the situation, where a call, which has left the originating network, re-appears at the originating network. GSM packet mode services "Use of X.31 case A": A circuit connection shall be used for accessing the packet service (according to ETS 300 099), with the significant characteristics of the connection identified by the following setting of the respective parameters of the BC-IE: - information transfer capability = unrestricted digital information; - transfer mode = circuit mode. The issue of "loop detection" is of no concern in the case of X.31 Case A (ETS 300 099) because the PH inserts - irrespective of being accessed by a home or a foreign roaming subscriber - into the "calling address" of an outgoing X.25 "call request" packet the address of the B-channel port. GSM packet mode services "Use of X.31 case B": A packet connection shall be used for accessing the packet service (according to ETS 300 099), with the significant characteristics of the connection identified by the following setting of the respective parameters of the BC-IE: - information transfer capability = unrestricted digital information; - transfer mode = packet mode. service number: A service number is a special E.164 number of the HPLMN which indicates to the HPLMN that, in case of an access to a PH X.31 case B, case A/B conversion is necessary. It is translated in the HPLMN into the actual E.164 number of the PH. The service number is used by the subscriber for the access of the PH case B when the subscriber is in the HPLMN or in the VPLMN. packet mode services via PSTN (X.32): A circuit connection shall be used for accessing the packet service with the significant characteristics of the connection identified by the following setting of the respective parameters of the Bearer Capability Information Element in access from a PLMN: - information transfer capability = 3,1 kHz exPLMN; - transfer mode = circuit mode. home PLMN: That GSM PLMN where the mobile subscriber has his subscription for mobile services. visited PLMN: That GSM PLMN on which the mobile subscriber is roamed to when leaving his home PLMN (HPLMN) and logged-in there. basic MSisdn: The MSisdn stored in VLR for a visiting mobile subscriber. PSPDN port: Unit providing incoming/outgoing demand access to a PSPDN (X.32). (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 8 3G TS 29.006 version 3.0.0 Table 1/GSM 09.06: Specification reference list Term Specification where defined CCITT, ETS GSM Bearer service I.112, I.210, I.211 02.02 Exchange I.112 Terminal Adaptor (Functions) I.411 07 series Interworking Function X.300 09.06, 09.07 Attributes I.112,I.140, I.211 02.01 Connection capabilities I.340 03.10 Control channel (D/Dm channel) I.412 04.03 Traffic channel (B/TCH channel) I.412 04.03 Service profile ETS 300 099 09.06 In addition to those below, abbreviations used in the present document are listed in GSM 01.04. AU Access Unit Cct Circuit CRP Call Request Packet IWMSC MSC accessing the PH 4 Introduction General Network Interworking Scenarios are described in GSM 09.01. When two dissimilar networks are required to interwork in order to support a communication between two subscribers, one on each network, a number of functions performing the interworking are required to support the communication. Some of these are related to the differences in signalling and are dealt with in GSM 09.03. Examples of other aspects of interworking are: i) the need of specific packet functions; ii) the need of modem pools and network-based rate adaptation. From the mobile subscriber's point of view, there have been defined two types of services within GSM PLMNs: - basic packet mode services: These services provide access either to the Packet handler(PH) and/or the PSPDN Port to which the individual subscriber is subscribed to. - dedicated packet mode services: These services provide access to the PH provided by the visited GSM PLMN, i.e. the "real packet world" is entered as soon as possible. Packet services are provided in the context of the present document by means of the "circuit" transfer mode. For the purposes of determining the required IWF functionality, it is necessary, however, to consider separately each type of service i.e. the basic and the dedicated packet mode service. 5 Network characteristics The key characteristics of networks concerned are listed in table 2/09.06. 5.1 Characteristics of GSM PLMNs The GSM PLMN is fully defined in the GSM series of specifications. (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 9 3G TS 29.006 version 3.0.0 5.2 Characteristics of PSPDNs These are defined in the relevant CCITT X series recommendations, such as X.1, X.2, X.10, X.25, and X.75. 5.3 Characteristics of ISDN These are defined in the CCITT I-series recommendations. The services and standards for the pan-European ISDN are identified in ETR 010. 5.4 Characteristics of the packet service provided by the PH The packet services supported via the packet handler interface (PHI) are defined in ETS 300 099. Support for both the ISDN X.31 Case A and Case B are specified there. Table 2/GSM 09.06: Key characteristics of networks concerned Characteristics GSM PLMN ISDN PSPDN User-network interface Digital Digital User-network signalling GSM 04.08 I.441/I.451 X.25, X.31, X.32 User-terminal equipment MT0, Digital TE DTE support DTE+MT1, (ISDN NT, DTE+MT2 TE1 or TE2+TA) see GSM 04.02 see I.441 Inter-exchange SS No.7 SS No.7 Proprietary, signalling ISUP,TUP+, ISUP, TUP+ X.75 MAP X.75 Transmission facilities Digital Digital Digital Exchange types Digital Digital Digital Information transfer mode Circuit Cct or Packet Information transfer Speech, Speech, unrestr.digital capabilities unrestr.digital, unrestr.digital altern. speech/ 3.1 kHz audio fax group 3, etc. video, etc. 5.5 Characteristics of the packet service provided by a PH assuming the role of an AU or by X.32 The packet services provided by the PH assuming the role of an AU is defined in the ETS 300 099 (X.31 Case A). The packet service provided via a modem is defined in CCITT X.32. 6 Interworking classifications Generally the distinction is made between the service interworking and the network interworking. 6.1 Service interworking Service interworking is required when the Teleservices at the calling and called terminals are different (e.g. Teletex interworking with facsimile). These aspects are not dealt with in the present document. 6.2 Network interworking Network interworking is required whenever a GSM PLMN and a non-GSM PLMN together are involved to provide an end to end connection and may be required in instances of GSM PLMN to GSM PLMN connections. The first case applies to the subject matter of the present document and thus dealt with herein after. (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 10 3G TS 29.006 version 3.0.0 7 Network interworking scenarios 7.1 General There are two sets of routing scenarios for connecting a GSM PLMN to a PSPDN/ISDN, namely: - via a transit ISDN or PSTN; or - direct connection. These are identified in GSM 03.70. What concerns the numbering please see GSM 03.03, GSM 03.70, and ETS 300 099. 7.2 Interworking through transit networks "In this scenario an PH or an PSPDN port is considered to be part of the ISDN or the PSPDN, as shown in figures 1 and 2/GSM 09.06." Figure 1/GSM 09.06 shows the access to a conventional X.32 PSPDN port of the PSPDN via transit networks ISDN and/or PSTN. The information transfer capability attribute value indicated in the GSM PLMN is "3.1 kHz audio, ex PLMN". In this case, modems are used. Figure 2/GSM 09.06 shows the access to the packet mode service provided according to the concept of the ETSI Packet Handler (PH) with AU functionality as specified in ETS 300 099 clause 5 for Case A. The information transfer capability attribute value is "unrestricted digital information". The application of this scenario requires an arrangement with the ISDN operator for granting access to the PH for GSM PLMN subscribers. "PHs supporting only X.31 case B can also be used. For these PHs agreements should exist between the PLMN and the fixed network operators to signal the case B between PLMN and ISDN. The GSM HPLMN shall take care of the X.31 case A/B conversion in order to proceed the call. The location of this conversion within the HPLMN is network dependent." The procedures used for mobile originated and mobile terminated calls to establish the circuit connection are defined in clauses 8 and 9 for the basic and dedicated packet services, respectively. PSPDN PSPDN port M O D E M PSTN ISDN PLMN MS MSC-A /IWF MODEM Figure 1/GSM 09.06: Interworking through ISDN and PSTN (3,1 kHz exPLMN) PLMN MS MSC-A /IWF ISDN CRF-P PH PSPDN PHI Figure 2/GSM 09.06: Interworking through ISDN (unrestricted digital information) NOTE: The packet handler logically is a part of the ISDN. (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 11 3G TS 29.006 version 3.0.0 7.3 Direct Interworking In this scenario the PH logically is part of the GSM PLMN (figure 3/GSM 09.06) and may be physically located in the GSM PLMN, the PSPDN or the ISDN. In the latter two cases, an arrangement with the PSPDN or ISDN operators is required in order to arrange for GSM PLMN particularities for dedicated access to cope with the "loop detection" issue. The interface between the MSC and the PH shall be the PH interface (PHI) as specified in ETS 300 099 for Case A. In cases where the available PH only supports the ISDN X.31 Case B, the PH is required to perform a GSM specific function, i.e. to substitute in the X.25 "call request" packet the PH port address in place of a foreign subscribers calling address. The GSM PLMN shall take care of the X.31 Case A/B conversion in order to proceed the call. MS MSC /IWF PHI PLMN PH X.75 or propriatory PSPDN Figure 3/GSM 09.06: Direct interworking Mobile originated and mobile terminated call procedures are defined in clauses 8 and 9. 8 Basic packet mode service 8.1 General Basic packet mode services are the services offered to the mobile users, as described in GSM 02.02, 3x-series. Offering the basic packet mode services requires that GSM PLMNs support the demand access to the PSPDN port in the PSPDN according to CCITT X.32 or to a packet handler of the ISDN (X.31 Case A). See note. This may be either in the network associated with the home PLMN of the respective mobile subscriber or in any other network to which the subscriber is entitled to establish calls. NOTE: The Case B is currently not feasible within GSM PLMNs because this case neither allows for addressing of PHs of different providers of packet switched data transmission services nor enables the handling of connections for roaming subscribers. The missing prerequisites for accomplishing this functionality in X.31 Case B are: - for calls from roaming foreign subscribers to the home PH --> support of the according addresses; and - for calls to roaming foreign subscribers via the PH, --> the PSPDN to provide redirection functionality as the gateway of home PLMNs does for routing circuit switched calls for their roaming subscribers. The scenarios described in clause 7 shall apply. The mobile user may have to subscribe separately to the services offered by the PSPDN port of a PSPDN or by the PH of the ISDN or PSPDN and/or home PLMN, which may depend on the policy or agreements reached between GSM PLMN operator and ISDN or PSPDN operators. The GSM PLMN networks shall provide only the circuit connection to/from the PH or the PSPDN port. The routing is based on the E.164/E.163 numbering plan because the location of both PH and PSPDN port is identified by E.164/E.163 numbers. Once the connection to the PH or PSPDN port has been established the GSM PLMN is transparent for the user information and in-band control information. The mobile user shall set in the SETUP message the GSM BC-IE, LLC-IE, and HLC-IE according to GSM 07.01 for 30-series type of services and the applicable variant and shall insert as the called address the E.164/E.163 number associated with the PH or the PSPDN port. That kind of access allows for mobile users to use customized and standard profiles according to CCITT X.32. These profiles are invisible to the GSM PLMNs. The characteristics of the service are those offered via the packet handler interface for X.31 Case A. (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 12 3G TS 29.006 version 3.0.0 The address of the called subscriber for mobile originated calls is sent to the PH or PSPDN port in the "called address" field of the X.25 CALL REQUEST packet and is a number in the format as required by the PH or the PSPDN port. On the basis of this number the PH or the PSPDN port is able to initiate the call establishment to the called subscriber. 8.2 Service provided by the GSM PLMN network Within the GSM PLMN a subscription to the bearer services BS 32, 33 and/or 34 is required. In order to select the basic packet mode service the mobile subscriber indicates during the call setup the GSM bearer capability IE according to GSM 07.01 "Bearer service 3x; X.32 case" and as the called address the E.164/E.163 address of the PH or the PSPDN port. The MSC-A shall insert for this type of call the calling party information element containing the Basic MSisdn of the calling mobile subscriber. This information shall be free for being used in conjunction with the calling line identification presentation supplementary service to be performed by the PH, unless the respective GSM PLMN supports the supplementary service Calling Line Identification Restriction and the mobile subscriber wants to apply Calling Line Identification Restriction also to the basic packet mode service. In this case only packet services for unidentified subscribers (see ETS 300 099) would be available to the mobile subscriber. For roaming subscribers using the basic packet mode services the connection shall be established by the visited PLMN to the PSPDN port or to the PH either in the home country of the respective mobile subscriber or in any other country to which the subscriber is entitled to establish calls, i.e. via an international ISDN/PSTN link. 8.3 Mobile originated calls 8.3.1 Subscriber on home PLMN This case illustrates a mobile subscriber being in its own GSM PLMN area. The subscriber requires the packet services to be supported by the GSM PLMN network he is subscribed to. The subscriber requests the appropriate 3x-series service stated in GSM 02.02 by using the BC_IE setting according to GSM 07.01 (restrictions see subclause 8.7). The SETUP message shall contain the E.164/E.163 address of the PH or PSPDN port. The MSC-A shall select the appropriate IWF and shall establish a circuit connection to the addressed PH or to the PSPDN port. "In case where the PH only supports X.31 case B, the PLMN shall take care of the X.31 case A/B conversion to proceed the call." 8.3.2 Subscriber on visited PLMN In this case the MSC-A of the VPLMN shall allocate the appropriate interworking functions within the VPLMN, identified from the mobile call set-up request. If the subscriber is accordingly entitled to, the call shall be routed via the visited PLMN's national transit ISDN or PSTN to the PH or PSPDN port identified by the E.164/E.163 ("Dial-in"-case of figure 4 and 5/GSM 09.06). The location of this PH or PSPDN port can be the ISDN or PSTN of the home PLMN or the home PLMN itself or any other ISDN or PSTN. The routing is exactly as for normal data or telephony call addressed to any other subscriber. "In case where the PH only supports X.31 case B, the PLMN shall take care of the X.31 case A/B conversion to proceed the call." In this case the visited PLMN may not have any knowledge that the mobile subscriber requests a packet service and no additional functions are required, to those necessary for a corresponding "data circuit duplex synchronous" (3x-series) service. (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 13 3G TS 29.006 version 3.0.0 MS MS HPLMN VPLMN ISDN/ PSTN ISDN/PSTN PSPDN PSPDN DTE DTE Home Country Visited Country roaming PSPDN port dial in dial out Figure 4/GSM 09.06: VPLMN and ISDN/PSTN transit network; 3,1 kHz audio ex PLMN MS MS HPLMN VPLMN ISDN ISDN DTE DTE Home Country Visited Country roaming PH dial in and dial in to PH case B (Note) dial out NOTE: In case of a PH only supporting case B, the case A/B conversion is necessary in the HPLMN. This is indicated by the mobile using a service number (see clause 3). Figure 5/GSM 09.06: VPLMN and ISDN transit network; unrestricted digital information (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 14 3G TS 29.006 version 3.0.0 8.4 Mobile terminated calls 8.4.1 Subscriber on home PLMN The scenarios applicable are those given in figures 1 to 3/GSM 09.06. The PH or PSPDN port translates, if required, the called address received in the X.25 INCOMING CALL packet to the E.164 mobile subscriber number and initiates a circuit connection to be routed firstly through to the GMSC of the home PLMN. From there on, the call shall be managed in the same manner as any other data call (see GSM 09.07 and GSM 07.03). "In case of more than one subscribed basic packet mode service in the HLR, the highest subscribed user rate is used. If in the Visited PLMN this user rate is not supported, the call will fail." 8.4.2 Subscriber on visited PLMN "The scenarios applicable are those given in figure 1 to 3. In this case the call will be handled as for any other data call for MS in VPLMN (see "Dial out"-case of figures 4 and 5/GSM 09.06)." 8.5 Mobile originated mobile terminated calls The call will be handled for the mobile originated part according to subclause 8.3 and for the mobile terminated part according to subclause 8.4. The X.25 packet switching function will be performed in the PSPDN. 8.6 Subscriber profiles All in-band access identification procedures between the DTE associated with the MS and the PSPDN port or the PH, if applicable, shall be passed "transparently" through the GSM PLMN. The service profile selection at the PSPDN port or the PH shall be established on the basis of those identification procedures. The subscriber may have a "default", a "standard" or a "customized service profile" according to ETS 300 099/X.32. 8.7 GSM bearer services quality of service GSM 03.10 identifies the protocol layer structures for both the transparent and the non-transparent mode. Both transparent and non-transparent mode of operation are applicable to the PSPDN Port scenario identified in figure 1. For the PH scenario shown in figure 2 only the non-transparent mode is possible. The scenario shown in figure 2 assumes a 64 kbit/s service provided via the ISDN and supported by the PH using "X.31 flag stuffing" capabilities. This form of service is not supportable by means of the transparent mode because of the inherent higher throughput rate required, i.e. 64 kbit/s. The non-transparent mode can support this form of service because it is able to remove/add flags and bring the actual "real" throughput rate down/up to one, which GSM and the PH, respectively, can support. For the transparent mode the GSM PLMN shall provide a synchronous data service with no provision for higher layer capabilities over and above layer 1 (see GSM 09.07 and GSM 07.03). In case of the non-transparent mode, the call set-up procedures are comparable to those identified above with the exception that the "connection element" in the call set-up message indicates "non-transparent". The receipt of this attribute value causes the MT and the IWF to select the L2R/RLP capabilities (see GSM 07.03 and GSM 09.07). The X.25 data link layer is terminated by the L2R at the MT towards the terminal and reconstituted at the IWF towards the transit network. In case of access to packet handler flag stuffing type of rate adaptation is used between the IWF and the PH. The data link layer parameters to be used at the R and S reference points, respectively, are listed in table 3/GSM 09.06. (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 15 3G TS 29.006 version 3.0.0 The following is applicable for mobile terminated calls: The IWF will not initiate the establishment of the LAPB link to the PH/PSPDN port, but will wait for an SABM, DM, or DISC, to be able to determine the link layer address to be used. The IWF will use this address until the circuit switched connection to the PH/PSPDN port is released. XID information received from the MS prior to the IWF's LAPB link establishment must either be discarded by the IWF or stored for later transmission if no DM, DISC or XID frames have been received from the fixed network. The first XID frame received (if any) from the PSPDN port prior to LAPB link establishment will be interpreted as a command. The link layer address derived from this first XID will be used for XID information exchange until an SABM, DM or DISC is received. NOTE: This use of LAPB address allows calls from a PH using any of the two alternative address assignment mechanisms defined in CCITT Rec.X.32 and applicable for X.31 case A. In addition, direct interworking of X.25 DTEs (DTE-DTE operation) between an X.25 DTE on a PLMN and an X.25 DTE on a PLMN or ISDN is possible. In this case the DTE address is used instead of the PH address. The X.25 packet layer information shall be passed transparently from the terminal to the PSPDN. 9 Dedicated packet mode service 9.1 General The "dedicated packet mode service" shall provide to the mobile subscriber the shortest possible connection from the GSM PLMN to the PH for both subscribers staying in the HPLMN as well as for roaming foreign subscribers staying in the VPLMN. Interworking with the PH through the ISDN or directly may be used in the GSM PLMN to satisfy this requirement (see figures 2, 3, and 6/GSM 09.06). Only mobile originated calls are supported. DTE DTE PSPDN PSPDN HPLMN VPLMN PH PH roaming MS MS Home Country Visited Country Figure 6/GSM 09.06: Dedicated packet mode service; mobile originated call for roaming MS NOTE: The support of mobile terminated calls for roaming subscribers would require the PSPDN to provide redirection functionality at the GMSC of home PLMNs does for routing circuit switched calls for their roaming subscribers. This is currently not the case. Thus the support cannot be provided. (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 16 3G TS 29.006 version 3.0.0 In the dedicated packet mode service, the MT or TA does not use the E.164 address of the PH. A common access procedure as described below shall be applied by all GSM PLMNs supporting this type of service hiding the differences of existing PSPDNs in GSM countries for GSM PLMN subscribers. The mobile subscriber has only a subscription to his HPLMN for the use of packet mode service. The applicable bearer services are those of the 50-series in GSM 02.02. No special E.164 number for addressing the PH or performing the registration with the PSPDN in satisfying the identification needs is necessary for the mobile subscriber in this case. The advantage of this procedure to the mobile subscriber is that the service offered by the GSM PLMN is completely compatible irrespective of the nature of the packet service in any transit or terminating network, which the GSM PLMN is working to. Additionally the mobile subscriber may receive all billing information for this service, the charges of GSM PLMN and PSPDN from the home GSM PLMN operator/retailer. If this is required, it may be necessary for the GSM PLMN to generate both volume and duration related charging parameters. User access to the PSPDN at the user/network interface of GSMN PLMN is the same for any type of implementation. Uniform functionality is assumed in the obligatory set-up of the "dedicated packet mode service". Standard procedures are supported over the air interface to support this service. Concerning the aspects of transparent/non-transparent mode the PH scenario part of subclause 8.7 - in essence only non-transparent mode - applies. Three distinct areas of this service - being realized according to the PH interface (X.31 Case A) of the pan-European ISDN - impact upon the overall GSM PLMN interworking requirements: - general application rules; - specific application rules for this service; - connection establishment procedures for this service. 9.2 General application rules The dedicated packet mode service supports the X.31 Case A with a default service profile which is applicable for non-registered subscribers. This X.31 Case A default service profile is set up as defined for the GSM profile in table 3/GSM 09.06. X.31 Case A customized service profiles are not supported. Support of the OSI Network Layer Service by this service is a general requirement. 9.3 Specific application of rules for dedicated packet mode service Particularly, the following rules apply for the PH interface (X.31 Case A) in support of the dedicated packet mode service: - The calling party number IE of the SETUP message towards the PH is mandatory to provide the PH with the basic MSisdn of the calling mobile subscriber as stored in the VLR. The insertion of the value of the calling party number is an act of the network, thus the PH can take this entry as a verified E.164 number (MSisdn) of the MS. - The calling party number may be used by the packet handler for charging purposes. - In cases where the available PH only supports the ISDN X.31 Case B, the PH is required to perform a GSM specific function, i.e. to substitute in the X.25 "call request" packet the PH port address in place of a foreign subscribers calling address. - There is no need for administration of the DTE identity at the PH because of the MS has only subscription with the PLMN operator. - Mobile originated calls arriving at the PH shall be accepted as a result of a respective pre-arrangement with the PLMN operator. (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 17 3G TS 29.006 version 3.0.0 - Mobile terminated calls are not supported in its purity according to the dedicated packet mode services. However, the support of mobile terminated calls for home subscribers according to the basic packet mode service may be provided by the same PH equipment, which performs the dedicated packet mode service. Table 3/GSM 09.06: GSM profile for layer 3 and layer 2 attributes and parameters, respectively Attribute/parameter Value DTE identity Provided. Verified E.164 number of MS (MSisdn). Packet sequence numbering Modulo 8. Logical channel assignment n = 2 (outgoing virtual circuits). Packet length 128 octets. Window size 2 Fast select and fast select acceptance Allowed. Default throughput class Half of user rate. Throughput class negotiation Available. Transit delay Negotiable, if applicable (exclusive of inherent GSM PLMN delay budget). RPOA selection Provided, if required and supported by the accessed PSPDN. UIL2P (note) X.25 link level X.75 layer 2 modified (CAPI) Link procedure Single link procedure. Link Layer Address Assignment as for LAPB X.25. Frame sequence numbering Modulo 8. Window size k = 7. k = 2. Max. frame length N1 = 2 104 bit. N1 = 16 440 bit. Retransmission attempts N2 = 10. Acknowledge timer T1 = [3] s (both directions). T1 = [10] s (both directions). NOTE: The link layer parameter values depend on the value of the UIL2P parameter of the GSM-BC. The value "X.75 layer 2 modified (CAPI)" is restricted to the direct DTE-DTE-interworking. 9.4 Mobile originated calls 9.4.1 General Within the GSM PLMN a subscription to the bearer services BS 51, 52 and/or 53 is required. In addition either the GSM PLMN or the PH ensures that only calls from subscribers of GSM PLMNs for which roaming agreement exists are progressed. The MS indicates in the call set-up the appropriate bearer capability IE according to GSM 07.01 for 50-series Bearer Services. In the called party number IE of the setup message the following parameters are included to select the dedicated packet mode service: - Type Of Number (TON) = "dedicated access, short code". - Numbering Plan Identification (NPI) = "Private Numbering Plan". - number digits = "short code" (see subclause 9.4.2). The connection shall be established in line with GSM 09.07 and 07.03. The MSC/IWF uses the short code number to select, if applicable, the PH and routes the connection to the appropriate PH. The interworking function (MSC/IWF) would need to determine the following points: - User rate from the call set-up request. - Selection of the RLP function and rate for the non-transparent service. - Routing information for PH. (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 18 3G TS 29.006 version 3.0.0 9.4.2 Short code The value "0000" of the short code is used for the case of one PH operator "visible" to the mobile subscriber and the single GSM profile according to table 3/GSM 09.06, thus serving currently as the "dedicated indicator" only. The individual PLMN operator may arrange for establishing the connections to the PSPDN through networks of different PSPDN operators, but this is currently not at the disposal of the mobile subscribers. All other values of the short code are reserved for future enhancements, e.g. introduction of a selection procedure for selecting a particular PSPDN operator and/or a particular profile. A number of particular capabilities may be necessary for the support of dedicated packet mode service: - Charging It may be necessary to generate both volume and duration related charging information. This shall be done within the PH. - Supplementary services interworking Interworking of GSM PLMN supplementary services with PSPDN optional user facilities is not provided. The following SS apply: call barring of all outgoing calls and advice of charge. The advice of charge shall be applied for the circuit switched portion only. (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.006 V3.0.0 (1999-05) 19 3G TS 29.006 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 09.06 6.0.0 Transferred to 3GPP CN1 CN#03 29.006 3.0.0 Approved at CN#03 (3G TS 29.006 version 3.0.0 Release 1999) ETSI TS 129 006 V3.0.0 (2000-01) ETSI 20 ETSI ETSI TS 129 006 V3.0.0 (2000-01) (3G TS 29.006 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 1 Scope | ........................................................................................................................................................5 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 1.1 References | .......................................................................................................................................................... 5 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 1.2 Abbreviations | ..................................................................................................................................................... 5 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 2 General description | ..................................................................................................................................5 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 2.1 Scheduling Information | ..................................................................................................................................... 6 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3 Message format on BTS-MS Interface | ....................................................................................................6 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.1 General | ............................................................................................................................................................... 6 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.2 Format convention | ............................................................................................................................................. 7 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.2.1 Numbering convention | ................................................................................................................................. 7 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.2.2 Order of bit transmission | .............................................................................................................................. 7 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.3 Block content | ..................................................................................................................................................... 7 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.3.1 Block Type | ................................................................................................................................................... 7 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.4 SMSCB Message | ............................................................................................................................................... 8 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5 Schedule Message | .............................................................................................................................................. 8 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.1 Header | .......................................................................................................................................................... 9 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.2 New CBSMS Message Bitmap | .................................................................................................................... 9 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.3 New CBSMS Message Description | ............................................................................................................. 9 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.4 Other Message Descriptions | ....................................................................................................................... 10 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.5 Message description encoding | .................................................................................................................... 10 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.5.1 First transmission of an SMSCB within the Schedule Period | .............................................................. 10 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.5.2 Retransmission indication | ..................................................................................................................... 11 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.5.3 Free Message Slot, optional reading | ..................................................................................................... 11 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.5.4 Free Message Slot, reading advised | ...................................................................................................... 11 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.5.5 Reserved Codepoints | ............................................................................................................................ 11 Annex A (informative): Sample Implementation of SMSCB DRX Mode ................................................12 Annex B: Change history ..............................................................................................................................14 History..............................................................................................................................................................15 ETSI TS 124 012 V3.0.0 (2000-01) (3G TS 24.012 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.012 V3.0.0 (1999-09) 4 3G TS 24.012 version 3.0.0 Foreword This Technical Specification has been produced by the 3GPP. This TS describes how the Short Message Service Cell Broadcast (SMSCB) is supported over the mobile radio interface within the digital cellular telecommunications system The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; ETSI TS 124 012 V3.0.0 (2000-01) (3G TS 24.012 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.012 V3.0.0 (1999-09) 5 3G TS 24.012 version 3.0.0 1 Scope This TS describes how the Short Message Service Cell Broadcast (SMSCB) (Teleservice 23 as specified in GSM 02.03) is supported over the mobile radio interface. 1.1 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • 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: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.03: "Digital cellular telecommunication system (Phase 2+); Teleservices supported by a GSM Public Land Mobile Network (PLMN)". [3] GSM 03.41: "Digital cellular telecommunication system (Phase 2+); Technical realization of Short Message Service Cell Broadcast (SMSCB)". [4] GSM 04.04: "Digital cellular telecommunication system; layer 1 General requirements". [5] GSM 04.06: "Digital cellular telecommunication system; Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification". [6] GSM 05.02: "Digital cellular telecommunication system (Phase 2+); Multiplexing and multiple access on the radio path". 1.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.04. 2 General description SMSCB is a service in which short messages may be broadcast from a PLMN to Mobile Stations (MS)s. SMSCB messages come from different sources (e.g. traffic reports, weather reports). The source and subject of the SMSCB message is identified by a message identifier in the SMSCB message header. A sequence number in the SMSCB message header enables the MS to determine when a new message from a given source is available. SMSCB messages are not acknowledged by the MS. Reception of SMSCB messages by the MS is only possible in idle mode. The geographical area over which each SMSCB message is transmitted is selected by the PLMN operator, by agreement with the provider of the information. A SMSCB message is an end-to-end message that is formatted by/for the SMSCB application, and which is intended for customer viewing. Its format is described in detail in GSM 03.41. A CB message is any message sent on the basic or extended CBCH (see GSM 05.02). It can be an occurrence of a SMSCB message, or a schedule message. ETSI TS 124 012 V3.0.0 (2000-01) (3G TS 24.012 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.012 V3.0.0 (1999-09) 6 3G TS 24.012 version 3.0.0 The SMS Cell Broadcast service is designed to minimize the battery usage requirements for a MS. A MS can read the first part of a CB message and then decide whether or not to read the rest of the message. In addition, the network may broadcast Schedule Messages, providing information in advance about the CB messages that will be sent immediately afterwards. The MS may use this scheduling information to restrict reception to those messages the customer is interested in receiving. This SMSCB DRX feature is optional in the network and the MS. 2.1 Scheduling Information The network supporting the SMSCB DRX feature transmits Schedule Messages. A Schedule Message includes information about a number of immediately following consecutive CB messages, planned for that cell. The length of time covered by the CB messages referred to in a Schedule Message is called the Schedule Period of that message. For optimum DRX, a new Schedule Message should follow the last message of a Schedule Period. When no information is known about a CB message, e.g., because no Schedule Message has been received referring to that CB message, a MS shall read (at least) the first part of the CB message. Schedule Messages shall be sent on the basic and extended CBCH independently. The network may override the published schedule to transmit new high-priority SMSCB messages. However, after any schedule deviation, the network shall resume the schedule, by transmitting the scheduled CB messages at the scheduled times listed in the Schedule Message. The Schedule Message contains a Message Description for each CB message to be broadcast during the scheduling period, in order of transmission. The position of a CB message is called the "message slot number" of the CB message, and it indicates the position of the CB message within the schedule period. Each Message Description includes various information, including for SMSCB messages directly or indirectly all or part of their message identifier, and whether an occurrence is a repetition or not. Each Schedule Message includes a Begin Slot Number field and an End Slot Number field. The End Slot Number field indicates the length of the schedule period (i.e., specifically the number of CB message slots about which information is provided). In the case where the network uses Schedule Messages to describe all message slots in advance, the first Schedule Message of the next schedule period will be transmitted in the message slot pointed by End Slot Number plus 1. The Begin Slot Number is defined to allow the network to broadcast several Schedule Messages referring to the same schedule period. The Begin Slot Number field indicates the message slot number of the CB message following the received Schedule Message. The networks may send unscheduled Schedule Messages during empty message slots. The network need only update the Begin Slot Number in an unscheduled Schedule Message to reflect the current offset within the Schedule Message of the next message to be transmitted. 3 Message format on BTS-MS Interface 3.1 General A CB message consists of a 88 octets of information. The 88 octet block is segmented into four 22 octet blocks. A 1 octet Block type is added as a header to each 22 octet block. The overall blocks are thus 23 octets in length. The message blocks are sent on the channel allocated as CBCH by GSM 05.02. The timing of the messages is defined in GSM 05.02. If the network has no cell broadcast information to transmit, then it may choose to transmit a null message. ETSI TS 124 012 V3.0.0 (2000-01) (3G TS 24.012 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.012 V3.0.0 (1999-09) 7 3G TS 24.012 version 3.0.0 3.2 Format convention 3.2.1 Numbering convention The basic convention used in this technical specification is illustrated in figure 1. The bits are grouped into octets. The bits of an octet are shown horizontally and are numbered from 1 to 8. Multiple octets are shown vertically and are numbered from 1 to 23. 8 7 6 5 4 3 2 1 Octet: 1 2 23 Figure 1/GSM 04.12: Format convention 3.2.2 Order of bit transmission The message blocks are sent on the CBCH as defined in GSM 05.02 using the coding defined for that channel. The order of bit transmission is defined in GSM 04.04. 3.3 Block content The 23 octet blocks are coded as follows: 8 7 6 5 4 3 2 1 Octet: Block type 1 2 Information 23 Figure 2/GSM 04.12: Block content 3.3.1 Block Type The purpose of the Block Type is to identify the function of the block and message being sent. The block type is coded as shown in figure 3/GSM 04.12. 8 7 6 5 4 3 2 1 Octet: Spare LPD LB Sequence Number 1 0 0 1 Figure 3/GSM 04.12: Block type content Bits 8 is spare and set to zero by the sender. In order to allow compatibility with future modifications to this protocol, bits 8 shall be ignored by the receiver and messages shall not be rejected because it is set to one. The Link Protocol Discriminator (LPD) takes the value "0 1". Other values of LPD indicate other protocols which are outside the scope of GSM 04.12, and shall cause the message to be ignored when the Cell Broadcast LPD is expected instead. NOTE: LPD = "0 0" corresponds to the data link protocol used by LAPDm (see GSM 04.06). In an SMSCB message the last block containing SMSCB information is signalled by the Last Block (LB) bit. When the LB bit is set to "0", the next block may contain SMSCB information. When the LB bit is set to "1", the remaining block(s) do(es) not contain SMSCB information. ETSI TS 124 012 V3.0.0 (2000-01) (3G TS 24.012 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.012 V3.0.0 (1999-09) 8 3G TS 24.012 version 3.0.0 Table 1/GSM 04.12: Sequence number coding Bit No 4 3 2 1 0 0 0 0 First block 0 0 0 1 Second block 0 0 1 0 Third block 0 0 1 1 Fourth block 1 0 0 0 First schedule block: Message contains SMSCB scheduling information 1 1 1 1 Null message (does not contain valid SMSCB information) All other values of bits 4 to 1 are reserved for future use. The use of a reserved code point shall cause the message to be ignored. 3.4 SMSCB Message The SMSCB message is a message with four consecutive blocks, with Block Types "first block", "second block", "third block" and "fourth block". A null message (which is indicated by the Sequence Number 1111 (binary)) shall have octets 2 to 23, inclusive, filled with the value 2B (hex). The SMSCB message coding is defined in GSM 03.41. 3.5 Schedule Message The text of the Schedule Message provides information pertaining to the CB messages sent afterward. A Schedule Message consists of 4 consecutive blocks with Block Types "first schedule block", "second block", "third block" and "fourth block". A Schedule Message containing scheduling data which does not fill the 88 octets shall be padded with the hexadecimal value "2B" after the end of the used part of the message. The Schedule Message comprises a 2-octet header followed by three parts, the first of them of 6 octets, and the two others of variable length, as indicated in the following figure: 8 7 6 5 4 3 2 1 Octet: Type Begin Slot Number 1 0 0 Spare Spare End Slot Number 2 0 0 New CBSMS Message Bitmap 3 - 8 New CBSMS Message Description 9 - 2m Other Message Descriptions (m+1)-n Figure 4/GSM 04.12: Schedule Message coding Octets following the last part (n+1 to 88 inclusive), if any, shall be ignored. In the following subclauses, when bits are indicated as spare, they shall be set to the indicated value (0 or 1) by the network, and their value shall be ignored by the MS. ETSI TS 124 012 V3.0.0 (2000-01) (3G TS 24.012 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.012 V3.0.0 (1999-09) 9 3G TS 24.012 version 3.0.0 3.5.1 Header Type (Octet 1): Set to 00 for messages formatted as specified in subclause 3.5. Schedule messages with another "Type" value shall be ignored by the receiver. Begin Slot Number (octet 1): Message slot number, relative to the schedule period, of the message slot following the Schedule Message. The Begin Slot Number field is coded in binary. Value range: 1 to 48. End Slot Number (octet 2): Last message slot number described by this Schedule Message. The End Slot Number field shall be coded in binary, and must be greater than or equal to the value of Begin Slot Number. Value range 1 to 48. NOTE: - For a scheduled Schedule message, the Begin Slot Number is set to "1". - For an unscheduled Schedule message, the Begin Slot Number is set in the range 2 to 48. If either of the two preceding fields are out of range, or if the value of the End Slot Number field is less than the value of the Begin Slot Number field, the Schedule Message shall be ignored by the receiver. 3.5.2 New CBSMS Message Bitmap This 6-octet fields encodes one bit per message slot, with the following indexation: 8 7 6 5 4 3 2 1 Octet: NM 1 NM 2 NM 3 NM 4 NM 5 NM 6 NM 7 NM 8 1 NM 9 NM 10 NM 11 NM 12 NM 13 NM 14 NM 15 NM 16 2 NM 17 NM 18 NM 19 NM 20 NM 21 NM 22 NM 23 NM 24 3 NM 25 NM 26 NM 27 NM 28 NM 29 NM 30 NM 31 NM 32 4 NM 33 NM 34 NM 35 NM 36 NM 37 NM 38 NM 39 NM 40 5 NM 41 NM 42 NM 43 NM 44 NM 45 NM 46 NM 47 NM 48 6 Figure 5/GSM 04.12: New CBSMS Message Bitmap coding NM i: The New Message bit i refers to the content of message slot i. Its meaning is as follows: 1 The message slot contains an SMSCB message page which was either not sent during the previous schedule period, or sent unscheduled during the preceding schedule period; or, the message is indicated as of free usage, reading advised. The value is 1 both for the first transmission of a given SMSCB message page in the schedule period or a repetition of it within the schedule period. 0 The message slot is such that value 1 is not suitable. An SMSCB message fulfilling the criterion for bit value 1 is said in the following to be "new". It should be noted that the broadcasting is not necessarily the first one. The network can choose not to send a given SMSCB message in all schedule periods. In this case it will be "new" each time it has not been sent in the previous schedule period. Another case is when a message is scheduled but its first transmission in the schedule period is pre-empted ; the next time the SMSCB message is "new". 3.5.3 New CBSMS Message Description This part contains as many Message Descriptions as there are bits set to 1 in the New Message Bitmap. This part can then be empty. A message description is 1 or 2 octets long: 8 7 6 5 4 3 2 1 Octet: Message Description 1 1 Message Description p Figure 6/GSM 04.12: New CBSMS Message Description coding ETSI TS 124 012 V3.0.0 (2000-01) (3G TS 24.012 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.012 V3.0.0 (1999-09) 10 3G TS 24.012 version 3.0.0 New Message Description j: This one or two octet long field contains information about what is sent in the jth message slot for which NM i is set to 1. The different possible encodings are specified in subclause 3.5.5. All descriptions pertaining to the first transmission of a new message shall be put at the beginning, so that mobile stations can determine rapidly where the new messages are. 3.5.4 Other Message Descriptions This part contains a one or two octet message description for each of the remaining message slots in the schedule period, in the order of transmission. This part can be empty. 8 7 6 5 4 3 2 1 Octet: Message Description 1 1 Message Description p Figure 7/GSM 04.12: Other Messages Part coding The Message Slot Number for each description must be derived from the New CBSMS Message Bitmap. The different cases are encoded as specified in subclause 3.5.5. 3.5.5 Message description encoding Four different encoding formats are specified, respectively: 1) for the first transmission of an SMSCB message in the schedule period, 2) for the repetition of an SMSCB message, 3) for a message slot of unindicated usage that MSs can skip, and 4) for a message slot of unindicated usage that MSs should not skip. The different encoding formats are identified by the Message Description Type (MDT) field. The MDT field is of variable length. The length of a description can be determined from the value of bit 8 of the first octet, which can then be understood as a "more" bit. Value 0 indicates a single-octet field, and value 1 a 2-octet field. 3.5.5.1 First transmission of an SMSCB within the Schedule Period This describes the content of a message slot which contains the first transmission of an SMSCB message page within the period: 8 7 6 5 4 3 2 1 Octet: MDT Message Identifier (high part) 1 1 Message Identifier (low part) 2 Figure 8/GSM 04.12: Message Description coding, First Transmission of an SMSCB MDT, Message Description Type (octet 1 of Message Description, bit 8): 1-bit field set to 1 for the message description of a message slot containing the first transmission during the schedule period of a given SMSCB message page. MESSAGE IDENTIFIER (octet 1 bits 7 to 1 and octet 2 of Message Description): Consists of the low-order 15 bits of the corresponding field of the SMSCB message, as defined in GSM 03.41. ETSI TS 124 012 V3.0.0 (2000-01) (3G TS 24.012 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.012 V3.0.0 (1999-09) 11 3G TS 24.012 version 3.0.0 3.5.5.2 Retransmission indication When a message slot contains the repetition of a SMSCB message page within the schedule period, the corresponding message description is coded on one octet, as follows: Bit 8 7 6 5 4 3 2 1 Octet: MDT 1 0 0 Repeated Message Slot Number Figure 9/GSM 04.12: Message Description coding, Retransmission of an SMSCB MDT, Message Description Type (octet 1 of Message Description, bits 8 and 7): 2-bit field set to "00" for the message description of a message slot containing the repetition of a SMSCB message page. Repeated Message Slot Number (octet 1 of Message Description, bits 6 to 1): This field encodes the message slot number of the first transmission during the schedule period of the repeated SMSCB message page. The field is encoded in binary, range 1 to 47. 3.5.5.3 Free Message Slot, optional reading When no specific information about a message slot is provided, and MSs need not read its contents, the Message Description is coded as follows: 8 7 6 5 4 3 2 1 Octet: MDT 1 0 1 0 0 0 0 0 0 Figure 10/GSM 04.12: Message Description coding, Free Message Slot, optional reading MDT, Message Description Type (octet 1 of Message Description): 8-bit field set to "01000000". The network can use such a message slot as needed, e.g., for unscheduled messages or for unscheduled Schedule Messages. 3.5.5.4 Free Message Slot, reading advised When no specific information about a message slot is provided, and MSs should read its contents, the Message Description is coded as follows: 8 7 6 5 4 3 2 1 Octet: MDT 1 0 1 0 0 0 0 0 1 Figure 11/GSM 04.12: Message Description coding, Free Message Slot, reading advised MDT, Message Description Type (octet 1 of Message Description): 8-bit field set to "01000001". The network can use such a message slot as needed, e.g., for sending high-priority messages. The values of MDT other than those specified in the previous sections are reserved for future use. They shall be treated as encoding a one octet message description, and understood as specified in subclause 3.5.5.3. ETSI TS 124 012 V3.0.0 (2000-01) (3G TS 24.012 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.012 V3.0.0 (1999-09) 12 3G TS 24.012 version 3.0.0 Annex A (informative): Sample Implementation of SMSCB DRX Mode This informative annex describes an implementation of SMSCB DRX functions, both on the network side and on the MS side. The network includes Schedule Messages to provide the MSs with information about the contents of the message slots following the Schedule Messages. The simplest implementation consists in sending Schedule Messages regularly, in a way all message slots are part of the schedule period of some Schedule Message. For the MS, there may be 3 main reception modes for the CBCH: 1) No DRX. The MS reads the first block of all message slots, and reads the remaining blocks when the message header indicates this is useful. A MS operates in this mode either when it does not support the other modes, or when it has not received a schedule message applicable to the next message slot. 2) First DRX mode. The MS has received a schedule message applicable to the next message slot, but either did not receive the first schedule message of the schedule period previous to the current one, or has not received all messages sent in that period (during that period or before). 3) Second DRX mode. The MS knows all the messages of interest sent in the schedule period previous to the current one, and has received the first schedule message of the current period. More information about these modes is given below. When a MS first enters a cell, or more generally when it knows no information pertaining to a message slot, it should read the first block of each message slot. According to the information found in this first block the MS can choose to read the rest of the message slot. Typically it will do so when it is a Schedule Message, or when it is an SMSCB message that it has not received before, in that cell or in a another. The complete reading of a first schedule message allows the MS to enter a first DRX mode for the rest of the schedule period. In this mode the MS reads the first block of each message slot for which the "message identifier", as indicated in the Schedule Message, is of interest to the user until the end of the schedule period, except that the MS may ignore retransmissions of messages it has already received during the same schedule period. When the MS has correctly read during a Schedule Period all messages of interest for its user, it can enter a second DRX mode. In this mode, it reads the first block of the CB message immediately after the end of the schedule period. If it is not a schedule message, or if the reception fails, it reads all first blocks until it receives a schedule message. In case of missed reception of the very first block, it enters the second DRX mode only if the first block of the next received schedule message shows that there is no gap between the corresponding schedule period and the previous one (it is the only way to be sure that there was no intervening schedule period). In the second DRX mode, the MS can understand from the first block of the schedule message how many new messages there are, when they will be transmitted, their message identifiers if there are less than 6 new messages, and possibly the positions of their repetitions. If the first block indicates that there are no new messages, or sufficiently few so that their message identifiers and the positions of their repetitions are known, the MS can refrain from reading the other blocks of the Schedule Message. Otherwise it reads the next block, and so on, until all the information pertaining to new messages is known. Then the MS reads only the new messages with a message identifier of interest for its user, and possibly corresponding repetitions in case of reception failures. Free message slots can be used for different purposes by the network. MSs wanting to save as much battery as possible at the expense of the delay for receiving messages can skip those message slots. As a trade-off, MSs can implement DRX with reception of the free messages slots with reading advised: this will speed up reception of new messages, with a higher battery consumption in proportion to the use of such messages slots by the network. Free message slots with optional reading should be used typically for unscheduled schedule messages, and can be skipped by mobile stations implementing DRX. ETSI TS 124 012 V3.0.0 (2000-01) (3G TS 24.012 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.012 V3.0.0 (1999-09) 13 3G TS 24.012 version 3.0.0 The network can broadcast unscheduled SMSCB messages. The different possibilities are as follows: - The network can send a new message in a free-usage message slot with reading advised. MSs implementing DRX but reading the first block of message slots so indicated will receive the message. The message must still be indicated as "new" the first time it is sent scheduled in a schedule period. - The network can pre-empt a "new" message with a more recent "new" message of the same message identifier if it happens that its first transmission has not yet happened; this is the only case where all MSs will read the unscheduled message. The network should repeat the pre-empting message instead of the pre-empted one in the messages slots scheduled for the repetitions of this message. If the pre-empted message is to be transmitted later, it has to be sent as "new" in the next schedule period within which it is sent. - If a message has been sent in the previous schedule period, the network can pre-empt the first transmission in the schedule period with a more recent message of the same message identifier. In this case, the MSs in second DRX mode will not receive immediately the message, but will receive it in the next schedule period if the message is repeated afterward (the network will indicate it as a "new" message even if it has been sent in the previous schedule period, since it would not have been scheduled during that period). If the pre-empted message is to be transmitted again, it has to be sent as "new" in the next schedule period within which it is sent. - If a message has been sent in the previous schedule period, the network can pre-empt the first transmission in the schedule period with a more recent message of a different message identifier. In this case, it is unlikely that a mobile station implementing DRX will immediately receive the message, it will receive it in the next schedule period if the message is repeated afterward (the network will indicate it as a "new" message even if it has been sent in the previous schedule period, since it would not have been scheduled during that period). The pre-empted message has to be sent as "new" in the next schedule period within which it is sent. - The network can pre-empt a retransmission (of the same message identifier or not), or send the new message in a free message slot of optional reading. In these cases it is unlikely that a MS implementing DRX will receive it at that moment. In free message slots the network can broadcast for instance unscheduled Schedule Messages. These messages hasten the entry into DRX mode of fast-moving MSs. ETSI TS 124 012 V3.0.0 (2000-01) (3G TS 24.012 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.012 V3.0.0 (1999-09) 14 3G TS 24.012 version 3.0.0 Annex B: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Sept 1999 GSM 04.12 7.0.0 Transferred to 3GPP CN2 CN#04 24.012 3.0.0 Approved by mail exploder at CN#04 ETSI TS 124 012 V3.0.0 (2000-01) (3G TS 24.012 version 3.0.0 Release 1999) ETSI 15 ETSI ETSI TS 124 012 V3.0.0 (2000-01) (3G TS 24.012 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 1 Scope | ........................................................................................................................................................5 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 2 References | ................................................................................................................................................5 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 3 Definitions and abbreviations | ..................................................................................................................6 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 4 Introduction | ..............................................................................................................................................6 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 4.1 Short and long term network characteristics | ...................................................................................................... 7 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 5 General discussion of numbering related issues on routeing to and from a PDN | ....................................7 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 5.1 Routeing from and to a PSPDN | ......................................................................................................................... 7 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 5.1.1 Mobile originated PSPDN terminated connection | ....................................................................................... 8 5.1.2 PSPDN/ISDN originated Mobile terminated connection............................................................................. 9 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 5.2 Routeing from and to other PDNs | ................................................................................................................... 10 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 5.2.1 Mobile originated PDN terminated connection | .......................................................................................... 10 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 5.2.1.1 Use of ESCAPE Code | .......................................................................................................................... 10 5.2.1.2 Use of NPI/TON indication.................................................................................................................. 11 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 5.2.2 PDN originated mobile terminated connection | .......................................................................................... 11 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 5.2.2.1 Pre T Phase Case | .................................................................................................................................. 11 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 5.2.2.1.1 Interworking via the ISDN, MS has E.164 number, PDN supports ESCAPE code concept | .......... 12 5.2.2.1.2 Interworking between PLMN and PDN via ISDN, MS has X.121 number, PDN supports non-zoned service concept.............................................................................................................. 13 5.2.2.1.3 Interworking directly from PDN to PLMN, MS has E.164 number, PDN supports ESCAPE code and additional number analysing capabilities......................................................................... 13 5.2.2.1.4 Interworking directly from PDN to PLMN, MS has X.121 number, PDN supports non-zoned service concept................................................................................................................................ 14 5.2.2.2 Post-T Phase Case ................................................................................................................................ 14 5.2.2.2.1 Interworking between PLMN and PDN via ISDN, MS has E.164 number, PDN supports NPI/TON capability........................................................................................................................ 14 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 6 Routeing scenarios to cater for roaming mobiles for PDN originated calls | ..........................................15 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 6.1 Routeing scenarios to cater for roaming mobiles for PSPDN originated calls | ................................................ 15 6.1.1 Basic Packet Mode Access; PH is part of PLMN/PSPDN......................................................................... 15 6.1.2 Basic Packet Mode Access; PH is part of ISDN/PSPDN........................................................................... 16 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 6.1.3 Basic Packet Mode Access; X.32 dial port (modem in PSPDN) | ............................................................... 16 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 6.2 Scenarios to cater for interworking with other PDNs | ...................................................................................... 17 Annex A: Change history......................................................................................................................18 History..............................................................................................................................................................19 ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 4 3G TS 23.070 version 3.0.0 Foreword This Technical Specification has been produced by the 3GPP. This specification identifies the routeing scenarios possible for calls between Public Data Networks (PDN's) and the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 5 3G TS 23.070 version 3.0.0 1 Scope The present document identifies the routeing scenarios possible for calls between Public Data Networks (PDN's) and the GSM PLMN. As one of the prime means of routeing is based on the subscriber number, this recommendation initially defines the numbering principles for interworking between PLMN's and PDN's. These principles indicate: - present PDN procedures when aiming at single stage interworking for the near term; and - future PDN procedures exploiting the 15 digit and intelligent signalling capabilities of the ISDN as the long term solution. Further routeing scenarios are presented for PDN originated calls to mobile subscribers who are roaming on a foreign PLMN. 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. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification". [3] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [4] GSM 04.21: "Digital cellular telecommunications system (Phase 2+); Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". [5] GSM 09.04: "Digital cellular telecommunications system (Phase 2+); Interworking between the Public Land Mobile Network (PLMN) and the Circuit Switched Public Data Network (CSPDN)". [6] GSM 09.05: "Digital cellular telecommunications system (Phase 2+); Interworking between the Public Land Mobile Network (PLMN) and the Packet Switched Public Data Network (PSPDN) for Packet Assembly/Disassembly facility (PAD) access". [7] GSM 09.06: "Digital cellular telecommunications system (Phase 2+); Interworking between a Public Land Mobile Network (PLMN) and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet switched data transmission services". [8] GSM 09.07: "Digital cellular telecommunications system (Phase 2+); General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". [9] CCITT Recommendation E.163: "Numbering plan for the international telephone service". [10] CCITT Recommendation E.164: "Numbering plan for the ISDN era". ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 6 3G TS 23.070 version 3.0.0 [11] CCITT Recommendation E.165: "Timetable for co-ordinated implementation of the full capability of the numbering plan for the ISDN ear". [12] CCITT Recommendation E.166: "Numbering plan interworking in the ISDN era". [13] CCITT Recommendation E.213: "Telephone and ISDN numbering plan for land mobile stations". [14] CCITT Recommendation I.332: "Numbering Principles for interworking between ISDNs and Dedicated Networks with different Numbering Plans". [15] CCITT Recommendation X.25: "Interface between data terminal equipment (DTE) and data circuit-terminating equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit". [16] CCITT Recommendation X.110: "International routing principles and routing plan for public data networks". [17] CCITT Recommendation X.121: "International numbering plan for public data networks". [18] CCITT Recommendation X.122: "Numbering plan interworking between a packet switched public data network (PSPDN) and an integrated services digital network (ISDN) or public switched telephone network (PSTN) in the short term". [19] ETS 300 099: "Integrated Services Digital Network (ISDN); Specification of the Packet Handler access point Interface (PHI)". 3 Definitions and abbreviations In addition to those below, abbreviations used in the present document are listed in GSM 01.04. Concept of time "T": CCITT Recommendation E.165 specifies that by the time "T" (set to 31.12.1996) full capability of the numbering plan for the ISDN era (CCITT Recommendation E.164) will be implemented. Short Code: see GSM 09.06 Cd Called Number Cg Calling Number CRP Call Request Packet in CCITT Recommendation X.25 4 Introduction The GSM PLMN uses the same numbering plan as the ISDN. PDN's - in particular the CSPDN and the PSPDN - are dedicated networks which use a non ISDN/GSM PLMN numbering plan. Because of the disparity in the networks (PLMN/ISDN to PDN), calls from subscribers on one network to a subscriber on the other network need to be directed via gateways, housing Interworking Functions (IWF's). This requires the originating network to determine an unambiguous indication of the gateway/route to take, which may not be possible on the basis of the called party number alone. This constitutes a major interworking issue which has been dealt with for the ISDN/PDN case already by CCITT. Because of the affinity of the ISDN and GSM PLMN numbering plans it is therefore obvious to try to seek some commonality between the ISDN and the PLMN in the approach for routeing. Two prime routeing scenarios have been considered: a) interworking between the PLMN and the PDN will be by means of an intermediate ISDN/PSTN e.g. the PLMN interworks to the ISDN, with the ISDN then providing the necessary interworking to the PDN; b) interworking directly between the PLMN and the PDN. ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 7 3G TS 23.070 version 3.0.0 4.1 Short and long term network characteristics In the CCITT Recommendation. I.332 the distinction is made between a short term and a long term solution for ISDN-numbering interworking with PDNs. The commencement of the long term solution is determined by the concept of Time "T". Further the directive is given, that "Between now and "T", any network or user equipment, in ISDNs, or networks intending to interwork with ISDNs, should be installed with the identified relevant post-"T" capability(ies)." The implications on the routeing requirements for pre and post-"T" are: The post-"T" phase is mainly characterized by the: - obligation to use the NPI/TON indication in the signalling at least at the international boundary; - allowed exploitation of the 15 digit capability of the ISDN Number (E.164); while the pre-"T" phase is characterized by the: - 12 digit capability according to CCITT Recommendation. E.163; - ESCAPE Code concept with its limited set of codes according to CCITT Recommendation. X.121; - DNIC according to "non-zoned services" of CCITT Recommendation.X.121; - Potential need for allocating a number from the X.121 Number Plan to a GSM PLMN subscriber in order to meet specific numbering requirements within the respective PDN; - Potential limitations for national PDNs to examine additional digits for routeing purposes. 5 General discussion of numbering related issues on routeing to and from a PDN Concerning the issue of numbering for GSM PLMN/PDN interworking, the concept of time "T" will be applied in the following. This entails distinguishing between a pre-"T" and a post-"T" phase. 5.1 Routeing from and to a PSPDN The interworking with the PSPDN will be provided in accordance with ETS 300 099 (see GSM 09.06). An E.164 number (provided by the user or inserted by the network) will be used to access the Packet Handler (PH). Standard PLMN procedures will be used to route to this number. The routeing from the PH to the destination DTE and from the destination DTE to the PH is based on the called address in the X.25 call packets. This information is not used in the PLMN (it is transparent and not visible to the PLMN). The presentation of this address information depends for the basic packet mode access on the accessed PH. For the dedicated GSM packet mode access an address presentation is defined in order to allow user friendly roaming. ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 8 3G TS 23.070 version 3.0.0 5.1.1 Mobile originated PSPDN terminated connection There are no specific requirements for the basic packet mode. Calls are always routed to the called address given by the user in the SETUP message. As circuit switched calls are always routed to the home PH, international addresses must be supported by the PH. The address information in the Call Request Packet (CRP) depends on the requirement of the home PH. The routeing scenarios for the dedicated packet mode are given in figures 03.70/1 and 03.70/2. NOTE 1: The PH is required to remove and insert ESCAPE code digit(s) as appropriate. NOTE 2: The PLMN customer may be able to utilize a variety of services offered by the PSPDN by dialling an E.164 number. In some situations the E.164 may mean (9/0 + X.121) number. Figure 03.70/1: Numbering Plan Interworking PLMN to PSPDN for Dedicated Packet Mode Services, Use of ESCAPE Code NOTE: A specific PSPDN or ISDN may use NPI/TON or ESCAPE Code as required. Figure 03.70/2: Numbering Plan Interworking PLMN to PSPDN for Dedicated Packet Mode Services, Use of NPI/TON indication ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 9 3G TS 23.070 version 3.0.0 5.1.2 PSPDN/ISDN originated Mobile terminated connection Only the Basic Packet Mode supports mobile terminated connections. The call is routed in the PSPDN according to the called address (E.164 or optionally X.121). The PH sets up a circuit switched connection to the MS if it does not already exist. For this call the E.164 of the MS is used (either available from the calling user or translated in the PH from the X.121 number). The addresses in the X.25 call packets (invisible to PLMN) is as required by the home PH. An example is given in figures 03.70/3 and 03.70/4. Figure 03.70/3: Example of Numbering Plan Interworking PSPDN to PLMN for Basic Packet Mode Services, Use of ESCAPE Code NOTE: A specific PSPDN or ISDN may use NPI/TON or ESCAPE Code as required. Figure 03.70/4: Example of Numbering Plan Interworking PSPDN to PLMN for Basic Packet Mode Services, Use of NPI/TON indication ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 10 3G TS 23.070 version 3.0.0 5.2 Routeing from and to other PDNs 5.2.1 Mobile originated PDN terminated connection As a general case in establishing a connection from the PLMN to the PDN, routeing will be possible by either direct means or via the ISDN/PSTN. The PLMN will be able to determine that a connection needs to be established to a PDN by analysis of the called number in conjunction with either: - an ESCAPE code; or - NPI/TON indication or equivalent in the call set up message. 5.2.1.1 Use of ESCAPE Code Within the framework of existing types of PDNs the use of an ESCAPE code will be constrained by the need to define an unique value to it. Additionally interworking may be necessary both to the ISDN/PSTN - to generate nationally used PREFIX code - and for direct connections to remove the ESCAPE code. The structure of the called and calling number applicable to the individual connection elements in case of mobile originated PDN terminated connections following the ESCAPE code approach is shown in figure 03.70/5. Interworking through ISDN. Figure 03.70/5: Numbering Plan Interworking PLMN to PDN, Use of ESCAPE Code ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 11 3G TS 23.070 version 3.0.0 5.2.1.2 Use of NPI/TON indication The use of NPI/TON has no constraints for either direct or via ISDN interworking. Figure 03.70/6 shows the CSPDN case. It should be noted that the procedures at the Man Machine Interface (MMI) are not yet defined. NOTE 1: It is understood that the signalling protocol mapping function implemented in TAF will support NPI/TON as defined in GSM 04.08. NOTE 2: TAF provides mapping from X.21/X.21bis protocol to D-channel protocol. Figure 03.70/6: Numbering Plan interworking PLMN to CSPDN for Circuit Switched Data Services (Short-Term and Long-Term) 5.2.2 PDN originated mobile terminated connection In the case of establishing a connection from the PDN to PLMN the routeing possibilities are constrained by the capabilities of the originating PDN some of which have been already listed under subclause 4.1 for the pre-"T" phase. The various options are described below. 5.2.2.1 Pre T Phase Case The following is a list of possible options which provide for interworking between the PDN and the PLMN. This list places no constraints on the mobile network operator as to which option should be provided. The choice will largely depend upon the capabilities of the national PDN/ISDN. ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 12 3G TS 23.070 version 3.0.0 5.2.2.1.1 Interworking via the ISDN, MS has E.164 number, PDN supports ESCAPE code concept All the calls from the individual PDN to the PLMN are routed via the ISDN. In this case the Mobile Station terminal has an E.164 number only, which is the directory number of the MS and is applicable to the respective Bearer Service as described in GSM 09.07 subclause 9.2.2. The PDN works on E.164 numbers on the basis of the CCITT defined concept of ESCAPE CODES by analysing up to the four first digits for routeing. The PDN on identifying the ISDN ESCAPE code routes the call to the ISDN. The ISDN routes then to the PLMN on the basis of the requested E.164 number. This procedure is fully in harmony with the CCITT defined ISDN/PDN interworking, constituting therefore a solution commonly applicable to all PDNs and leaving the ISDN/PLMN free from any burden due to routeing on and administration of X.121 numbers for incoming calls. Figure 03.70/7: Interworking PDN-ISDN-PLMN (PDN 4 digits analysis) ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 13 3G TS 23.070 version 3.0.0 5.2.2.1.2 Interworking between PLMN and PDN via ISDN, MS has X.121 number, PDN supports non-zoned service concept All calls from the individual PDN to the PLMN are routed via the ISDN. In this case the ISDN/PLMN may use NPI/TON for signalling. The MS terminal has an X.121 number in addition to the E.164 directory number of the MS, which is applicable to the respective Bearer Service on the same way as described in GSM 09.07 subclause 9.2.2. The PDN is capable of dealing with, and the organization of the PDNs in the individual country allows for a dedicated DNIC for the ISDN identifier e.g. as a "non-zoned service", in conformance with CCITT and routes all calls on that basis to the ISDN. The ISDN has to provide the necessary function for converting the X.121 number into the required E.164 number suitable for routeing use within the ISDN and the PLMN. Figure 03.70/8: Interworking PDN-ISDN-PLMN (PDN "ISDN non-zoned service DNIC") 5.2.2.1.3 Interworking directly from PDN to PLMN, MS has E.164 number, PDN supports ESCAPE code and additional number analysing capabilities All calls from the individual PDN to the PLMN are routed directly to the PLMN via the MSC/IWF. The MS of the PLMN has an E.164 number. The PDN works on E.164 numbers on the basis of the CCITT defined concept of ESCAPE codes. In this case the PLMN may use NPI/TON for signalling. ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 14 3G TS 23.070 version 3.0.0 Figure 03.70/9: Direct-Interworking PDN-PLMN 5.2.2.1.4 Interworking directly from PDN to PLMN, MS has X.121 number, PDN supports non-zoned service concept All calls from the individual PDN to the PLMN are routed directly to the PLMN via the MSC/IWF. The PLMNs MS terminal has an X.121 number in addition to the MS's E.164 one, which is applicable to the respective Bearer Service in the same way as described in GSM 09.07. The PDN is capable of dealing with, and the organization of the PDN in the individual country allows for, a dedicated DNIC for the PLMN e.g. as a " non-zoned service" in conformance with CCIT. This routes all PLMN destined calls identified by that DNIC directly to the PLMN via the MSC/IWF. The PLMN (MSC/IWF) has to provide the necessary functions for converting the X.121 number into required E.164 number suitable for routeing use within the PLMN: Figure 03.70/10: Direct Interworking PDN-PLMN (PDN "non-zoned services" DNIC for PLMNs) 5.2.2.2 Post-T Phase Case The transition to this phase enforces at least at the international boundary the use of the NPI/TON for signalling in case of interworking with ISDN and allows the exploitation of the 15 digits capability of the ISDN number. Networks not following this procedure must not burden those which do follow it. This removes any limitation on number plan identification capacity. 5.2.2.2.1 Interworking between PLMN and PDN via ISDN, MS has E.164 number, PDN supports NPI/TON capability. PDN routes calls to the ISDN on the basis of the NPI/TON indication and E.164 number. The ISDN IWF will route the connection to the PLMN on the basis of the E.164 number indicated. ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 15 3G TS 23.070 version 3.0.0 6 Routeing scenarios to cater for roaming mobiles for PDN originated calls 6.1 Routeing scenarios to cater for roaming mobiles for PSPDN originated calls Mobile terminated calls are currently only possible for the Basic Packet Mode Access (see GSM 09.06). The call is always routed to the Home PSPDN and from there to the Home PLMN. Only the Home PLMN has access to the HLR. The HLR provides the information about the location of the called user. The Home PLMN establishes then a circuit switched connection to the user on the VPLMN. Details are given in the following sections. 6.1.1 Basic Packet Mode Access; PH is part of PLMN/PSPDN Terminals with E.164 numbers: Routeing: PSPDN A to Home PLMN A to ISDN A to ISDN B to Visited PLMN B to the called user Terminals with X.121 Numbers: Routeing as above for E.164 numbers. Calls are routed on the X.121 number in the PSPDN. The PH translates the X.121 number into an E.164 number. This E.164 number is used to establish a circuit switched connection from the PH to the called user. X.121 numbers may then be used in X.25 call packets. This is transparent to the PLMN. ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 16 3G TS 23.070 version 3.0.0 6.1.2 Basic Packet Mode Access; PH is part of ISDN/PSPDN Terminals with E.164 numbers Routeing: PSPDN A to ISDN A to Home PLMN A to ISDN A to ISDN B to Visited PLMN B to the called user Terminals with X.121 Numbers Routeing as above for E.164 numbers. Calls are routed on the X.121 number in the PSPDN. The PH translates the X.121 number into an E.164 number. This E.164 number is used to establish a circuit switched connection from the PH to the called user. X.121 numbers may then be used in X.25 call packets. This is transparent to the PLMN. 6.1.3 Basic Packet Mode Access; X.32 dial port (modem in PSPDN) Terminals with E.164 numbers Routeing: PSPDN A to PSTN A to ISDN A to Home PLMN A to ISDN A to ISDN B to Visited PLMN B to the called user Terminals with X.121 Numbers Routeing as above for E.164 numbers. Calls are routed on the X.121 number in the PSPDN. The PSPDN translates the X.121 number into an E.164 number. This E.164 number is used to establish a circuit switched connection from the PSPDN to the called user. X.121 numbers may then be used in X.25 call packets. This is transparent to the PLMN. ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 17 3G TS 23.070 version 3.0.0 Assuming the NPI/TON information exists, or the use of the ESCAPE code 0. Terminals with E.164 numbers Routeing Options recognized: 1) PDN A to ISDN B 2) ISDN A to ISDN B 3) ISDN A to PDN A to PDN B 4) ISDN A to PDN A to PDN B to ISDN B 5) PDN A to PDN B to ISDN B There is no way to ensure which route will be used, except if the PLMNs agree bilaterally which is the primary or preferred route. Terminals with X.121 Numbers Routeing options as above for E.164 numbers. ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.070 V3.0.0 (1999-05) 18 3G TS 23.070 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 03.70 6.0.0 Transferred to 3GPP CN1 CN#03 23.070 3.0.0 Approved at CN#03 ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) ETSI 19 ETSI ETSI TS 123 070 V3.0.0 (2000-01) (3G TS 23.070 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication |
e86401852833419ce79b64126702606c | 123 054 | 1 Scope | ........................................................................................................................................................6 |
e86401852833419ce79b64126702606c | 123 054 | 2 References | ................................................................................................................................................6 |
e86401852833419ce79b64126702606c | 123 054 | 3 Definitions and Abbreviations | .................................................................................................................7 |
e86401852833419ce79b64126702606c | 123 054 | 3.1 Definitions | ......................................................................................................................................................... 7 |
e86401852833419ce79b64126702606c | 123 054 | 3.2 Abbreviations | ..................................................................................................................................................... 7 |
e86401852833419ce79b64126702606c | 123 054 | 4 Architecture | .............................................................................................................................................8 |
e86401852833419ce79b64126702606c | 123 054 | 4.1 General | ............................................................................................................................................................... 8 |
e86401852833419ce79b64126702606c | 123 054 | 4.2 Routeing principles | ............................................................................................................................................ 8 |
e86401852833419ce79b64126702606c | 123 054 | 4.3 Visited MSC with additional SIWF functionality (SIWFC) | ............................................................................ 10 |
e86401852833419ce79b64126702606c | 123 054 | 4.4 SIWFS - Shared Inter Working Function Server | ............................................................................................. 10 |
e86401852833419ce79b64126702606c | 123 054 | 4.4.1 General | ....................................................................................................................................................... 10 |
e86401852833419ce79b64126702606c | 123 054 | 4.4.2 IWU | ............................................................................................................................................................ 11 |
e86401852833419ce79b64126702606c | 123 054 | 4.4.3 Data call Routeing Mechanism (DRM) | ...................................................................................................... 11 |
e86401852833419ce79b64126702606c | 123 054 | 4.5 K Interface and Signalling | ............................................................................................................................... 11 |
e86401852833419ce79b64126702606c | 123 054 | 4.6 Fixed Network | ................................................................................................................................................. 11 |
e86401852833419ce79b64126702606c | 123 054 | 5 Procedures | ..............................................................................................................................................12 |
e86401852833419ce79b64126702606c | 123 054 | 5.1 General | ............................................................................................................................................................. 12 |
e86401852833419ce79b64126702606c | 123 054 | 5.2 Mobile Originated calls | ................................................................................................................................... 12 |
e86401852833419ce79b64126702606c | 123 054 | 5.2.1 Call flow MOC (Loop Method) | ................................................................................................................. 14 |
e86401852833419ce79b64126702606c | 123 054 | 5.2.2 Call flow for MOC (Non Loop Method) | .................................................................................................... 15 |
e86401852833419ce79b64126702606c | 123 054 | 5.3 Mobile Terminated calls | .................................................................................................................................. 15 |
e86401852833419ce79b64126702606c | 123 054 | 5.3.1 Call flow for MTC (Loop Method) | ............................................................................................................ 17 |
e86401852833419ce79b64126702606c | 123 054 | 5.3.2 Call Flow for MTC (Non-Loop Method) | ................................................................................................... 17 |
e86401852833419ce79b64126702606c | 123 054 | 5.4 In Call Modification (ICM) | ............................................................................................................................. 17 5.4.1 Call in Data/Fax Mode............................................................................................................................... 18 |
e86401852833419ce79b64126702606c | 123 054 | 5.4.2 Call in Speech Mode | .................................................................................................................................. 18 |
e86401852833419ce79b64126702606c | 123 054 | 5.4.3 Call Flow for ICM Procedure | ..................................................................................................................... 20 |
e86401852833419ce79b64126702606c | 123 054 | 5.5 Modifications in a connection | .......................................................................................................................... 20 |
e86401852833419ce79b64126702606c | 123 054 | 5.5.1 Channel Mode Modify (CMM) | .................................................................................................................. 20 |
e86401852833419ce79b64126702606c | 123 054 | 5.5.2 User initiated resource up- and down grading | ............................................................................................ 21 |
e86401852833419ce79b64126702606c | 123 054 | 5.5.3 Network Resource up- and downgrading | ................................................................................................... 21 |
e86401852833419ce79b64126702606c | 123 054 | 5.6 Release | ............................................................................................................................................................. 22 |
e86401852833419ce79b64126702606c | 123 054 | 5.7 Negotiation of parameters | ................................................................................................................................ 22 |
e86401852833419ce79b64126702606c | 123 054 | 5.8 Inter MSC handover | ......................................................................................................................................... 22 |
e86401852833419ce79b64126702606c | 123 054 | 5.9 Reset | ................................................................................................................................................................ 22 |
e86401852833419ce79b64126702606c | 123 054 | 6 SIWF and Supplementary Services | .......................................................................................................22 |
e86401852833419ce79b64126702606c | 123 054 | 6.1 Number Identification Supplementary Services | .............................................................................................. 23 |
e86401852833419ce79b64126702606c | 123 054 | 6.2 Call Offering Supplementary Services | ............................................................................................................ 23 |
e86401852833419ce79b64126702606c | 123 054 | 6.3 Call Waiting (CW) | ........................................................................................................................................... 23 |
e86401852833419ce79b64126702606c | 123 054 | 6.4 Closed User Group (CUG) | .............................................................................................................................. 23 |
e86401852833419ce79b64126702606c | 123 054 | 6.5 User-to-User Supplementary Services | ............................................................................................................. 23 |
e86401852833419ce79b64126702606c | 123 054 | 6.6 Charging Supplementary Services | ................................................................................................................... 23 |
e86401852833419ce79b64126702606c | 123 054 | 6.7 Call Restrictions | ............................................................................................................................................... 23 |
e86401852833419ce79b64126702606c | 123 054 | 6.8 Support of Private Numbering Plan (SPNP) | .................................................................................................... 23 |
e86401852833419ce79b64126702606c | 123 054 | 6.9 Call Completion on Busy Subscriber (CCBS) | ................................................................................................. 23 ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 4 3G TS 23.054 version 3.0.0 |
e86401852833419ce79b64126702606c | 123 054 | 7 Interaction with CAMEL | .......................................................................................................................23 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.