hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
01cf386a661f37797b151545792903a0 | 123 110 | 6.2.4.1 Dedicated control SAPs | ........................................................................................................................ 23 |
01cf386a661f37797b151545792903a0 | 123 110 | 6.2.4.1.1 Connection loss indication | .............................................................................................................. 23 |
01cf386a661f37797b151545792903a0 | 123 110 | 6.3 Parameters structure | ......................................................................................................................................... 24 |
01cf386a661f37797b151545792903a0 | 123 110 | 6.3.1 Local | ........................................................................................................................................................... 24 |
01cf386a661f37797b151545792903a0 | 123 110 | 6.3.2 Bit string | ..................................................................................................................................................... 24 |
01cf386a661f37797b151545792903a0 | 123 110 | 6.3.3 Enumerated | ................................................................................................................................................ 24 |
01cf386a661f37797b151545792903a0 | 123 110 | 6.3.4 Geographical description | ............................................................................................................................ 24 |
01cf386a661f37797b151545792903a0 | 123 110 | 6.3.5 QoS | ............................................................................................................................................................ 24 |
01cf386a661f37797b151545792903a0 | 123 110 | 6.3.6 Route | .......................................................................................................................................................... 24 |
01cf386a661f37797b151545792903a0 | 123 110 | 6.3.7 Transaction identifier | ................................................................................................................................. 24 |
01cf386a661f37797b151545792903a0 | 123 110 | 6.3.8 Transaction list | ........................................................................................................................................... 24 |
01cf386a661f37797b151545792903a0 | 123 110 | 6.3.9 Transmission mode | .................................................................................................................................... 25 6.3.10 AN/CN Point List....................................................................................................................................... 25 |
01cf386a661f37797b151545792903a0 | 123 110 | 6.3.11 Localisation | ................................................................................................................................................ 25 Annex A (informative): Change history...............................................................................................26 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 5 Release 1999 Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). 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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater 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 document. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 6 Release 1999 1 Scope The present document specifies the services provided by the Access Stratum to the rest of the system. The adopted architecture is given by 3G TS 23.101 [2]. The present document describes the main functions visible at the boundary between the Access Stratum and the rest of the system, it describes in general terms the information flows, both control and user data, over this boundary and relevant for the Access Stratum. The present document is the basis of the detailed specifications of the protocols which rule the information flows, both control and user data, between the Access Stratum and the parts of UMTS outside the Access Stratum, and of the detailed specifications of the UTRAN. These detailed specifications are to be found in other Technical Specifications. 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. [1] 3G TS 22.101: "Universal Mobile Telecommunications System (UMTS): Service aspects; Service principles". [2] 3G TS 23.101: "Universal Mobile Telecommunications System (UMTS): General UMTS Architecture". [3] 3G TS 23.105: "Universal Mobile Telecommunications System (UMTS): Network Principles". [4] ITU-T Recommendation X.210 (November 1993): "Information Technology - Open Systems Interconnection - Basic Reference Model: Conventions for the Definition of OSI Services". [5] 3G TS 23.107: "QoS Concept and Architecture". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3G TS 23.101 [2] and the following apply. Access Stratum: defined in [2]. Access Network: defined in [2]. Edge-Node: core network node which is connected to the URAN at a particular instance. URAN: defined in [TBD]. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 7 Release 1999 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AN Access Network AS Access Stratum CC Call Control DC Dedicated Control SAP CN Core Network FFS For Further Study GC General Control (SAP) GPRS General Packet Radio Service GSM Global System for Mobile communications HPLMN Home Public Land Mobile Network IF Infrastructure ME Mobile Equipment MM Mobility Management MS Mobile Station NAS Non Access Stratum Nt Notification (SAP) PDN Packet Data Network PTM Point to Multipoint RAN Radio Access Network SAP Service Access Point SAPI Service Access Point Identifier [???] SIM Subscriber Identity Module SMS Short Message Service SS Supplementary Services TBD To Be Defined UE User Equipment UMTS Universal Mobile Telecommunications System URAN UMTS Radio Access Network USIM UMTS Subscriber Identity Module USSD Unstructured Supplementary Service Data UTRA UMTS Terrestrial Radio Access UTRAN UMTS Terrestrial Radio Access Network VBS Voice Broadcast Service VGCS Voice Group Call Service VPLMN Visited Public Land Mobile Network 4 Basic Assumptions 4.1 Boundaries of the Access Stratum The Access Stratum (AS) is defined in [2]. It consists of a functional grouping which includes all the layers embedded in the URAN; and part of the layers in the User Equipment (UE) and the infrastructure (IF); i.e. the edge-node. Its boundary is the frontier between the layers which are independent of the access technique and the ones which are dependent on it. This frontier is located in the UE (mobile boundary) and in an edge-node (fixed boundary). There is a direct or "transparent" dialogue (i.e. not interpreted by the AS) between the UE and the edge-node for the Non-Access Stratum layers. 4.2 Main design guidelines 1) The Access Stratum contains all access specific functionality, e.g. all mode specific functionality in case of the UTRAN. 2) Reconfiguration of the AN, or changes in the AN domain functionality shall have minimal impact on Core Network functions, and vice-versa. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 8 Release 1999 3) A given Access Network (e.g., the UTRAN) may provide access to different type of Core Networks via the Iu reference point. 4) The services, access signalling, mobility and subscriber management specific to each Core Network are completely outside the Access Stratum, and are transferred transparently by the Access Stratum. 5) The Access Stratum provides flexible radio access bearers characterised by parameters describing the type of information and QoS transported over the radio interface (i.e. not the actual radio resources). Some radio access bearers may be asymmetric, i.e., have different parameters on uplink and downlink. 6) There are radio access bearers for both connection oriented packet-switched services, connectionless (store-and- forward) services, and circuit-switched traffic. 7) Parameters for connection-oriented radio access bearers may change during connection (bandwidth on demand, quality management). 8) Whether a terminal can be registered and have connections to several Core Networks simultaneously (i.e., over different instances of Iu) is FFS. 9) The Access Stratum can provide several parallel and independent radio access bearers to one user equipment each with its own characteristics. 10)Multimedia is handled outside the Access Stratum by multiplexing several streams onto one radio access bearer or by requesting several parallel radio access bearers. In the latter case, the possibly needed synchronisation is handled outside the Access Stratum. 11)Connection of a user equipment to several URAN at a time has to be studied. 12)Handover and if applied macrodiversity within one Access Network is handled within the Access Stratum. 13)Handover between two Access Networks (e.g., two UTRANs, or between UTRAN and GSM BSS) may use support from the Core Network. 14)The Access Stratum should hide all access -specific parameters, e.g., location data provided to the Core Networks should be independent from the actual configuration of the Access Network. 15)The user equipment can be connected to different AN/CN points via a single Access Network. The Access Stratum should be able to provide a flexible routing to the appropriate AN/CN point. 5 Functions location inside/outside Access Stratum Following table shows the functional split between Access Stratum and the rest of the system. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 9 Release 1999 Table 1: Functions inside/outside the Access Stratum LOCATION \ FUNCTION Outside the Access Stratum Inside the Access Stratum Call set up/release yes no (Connection) Bearer Set-Up Release CN bearer [tbd] Radio Access Bearer [tbd] Supplementary Services yes no Location management yes (IWF/CN related) yes (Radio related) Attach/ Detach yes FFS, Contr expected Resource Management yes (for NAS resource) yes (for AS resource incl. radio) Handover yes* yes Macrodiversity [ffs] yes* yes Encryption yes yes** Authentication yes no compression (non source dependent) yes yes source dependent coding yes no radio channel coding (could be many) no yes (could be many) UE location identification may be supported yes Charging yes no NOTE *: Optionally execution. In some CNs, it may not be present but not full service will be supported (e.g. limited to RLL type of service). NOTE **: Contributions expected to clarify the role between encryption and subscriber data. 5.1 Call Control This Functionality is placed in the NAS, since it manipulates the call state machine. An example is termination of Q.931 message and sending of ISUP. Not part of AS. NAS specific signalling messages, e.g. Q.931, Q.2931 and ISUP. 5.2 (Connection) Bearer Control It is distinguished between the bearers used in the NAS and the common bearer used in the AS (radio access bearer). Basic principles for radio access bearers are: 1) Radio access bearers provide information transport between the non-access stratum parts of the infrastructure side (i.e. the edge node) and the user equipment side. Radio access bearers shall support real time as well as non real time user traffic. 2) Radio access bearers must be flexible enough to support different traffic types, activity levels, throughput rates, transfer delays and bit error rates. Attributes allowing efficient use of radio resources are crucial. 3) Efficient mapping from the traffic attributes used by non-UMTS applications, given by dominating external network technologies, to the attributes of the radio access bearer layer of the access stratum is essential. Complexity in mapping procedures should be avoided. 4) Definitions of traffic attributes and traffic management for radio access bearers shall be consistent with the predominant networking technology on the market (e.g. N-ISDN and IP networks for UMTS phase 1). As networking technologies emerge, adapted radio access bearer attributes and types shall gradually be added. 5) Radio access bearer definitions must allow for straightforward and efficient traffic management and resource handling of the radio resources in the access stratum. This procedure is part of the NAS. Example are 13.0 kbit/s (for GSM speech) and 2B+D (for ISDN BRI). 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 10 Release 1999 The protocols required in AS to provide a radio access bearer should be able to describe both packet switch and circuit switch types of connections. 5.3 Supplementary Services (CLIP, CF etc.) Supplementary services are part of the NAS, since they manipulate the Call state machine. Supplementary services are not part of AS since they manipulate the call state machine. 5.4 Location Management "Location Updating Management" and "Paging" is an existing example of Location Management. Location Management may be supported in the NAS. Radio related Location Management may be part of the AS. 5.5 Attach/ Detach If the Attach/ Detach procedures are supported in the NAS they use CN specific identifiers to mark the attached/detached subscriber. As an example in GSM, the attach/detach procedure is performed on the IMSI flag, and therefore it is a NAS functionality. Attach/Detach may be performed in the AS using the URAN unique identifiers. This is FFS. 5.6 Resource management This function allocates resources for a given information stream, as to allow to convey it with a given QoS. This information stream may support either signalling data (CC, MM, ...) or user data. Both circuit switched and packet access are supported, offering both connection oriented and connectionless services. The AS resource management is transparent for the NAS and vice versa. 5.7 Handover 5.7.1 Handover - outside Access Stratum Handover may be a NAS functionality, but it can not be expected that all CNs will support handover therefore the IWF may take care of any required handover functionality. The AN may leave certain parameters, e.g. the address to a new IWF/CN-AN connection point, to which the IWF/CN may switch if it has the capabilities. 5.7.2 Handover - inside Access Stratum Handover is performed in the AS, to hide all radio specific details from the NAS. 5.7.3 Handover scenarios supported by the Iu interface The following sections describe which functions will be supported by the Iu interface. Some functions have no impact on the Iu interface and therefore will be supported de-facto, nevertheless they are explicitly mentioned for completeness of the scenarios. 5.7.3.1 Classification A Classification A describes the way the handover is prepared: 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 11 Release 1999 HO A1: the network has informed the target cell before the MS changes cell; HO A2: the network has not informed the target cell before the MS changes cell; HO A3: the mobile has informed the target cell before it leaves the source cell. HO A1 is typical of the existing handover in GSM. HO A2 reflects the call re-establishment in GSM, mobile directed handovers in general, or even GPRS to some extent (although the GPRS vocabulary is different). HO A1, HO A2 and HO A3 shall be supported by the service primitives of the Iu interface. 5.7.3.2 Classification B Classification B describes the way the decision to initiate a handover is taken: HO B1: decision is taken by the terminal; HO B2: decision is taken by the network. When the network takes the decision, it can be either in the RAN (HO B2a), or in the CN (probably based on information provided by the RAN and/or the MS) (HO B2b). In order to keep the radio independence from the CN, it would be desirable that the decision be taken only in the RAN. This means that a communication mechanism is needed between URANs, that interface being logically different from the Iu interface. HO B1 and HO B2 shall be supported by the service primitives of the Iu interface. NOTE 1: FFS:For HO B2 cases, handover initiation/decisions shall be taken by the source URAN. NOTE 2: FFS: There is a URAN to URAN signalling mechanism transparent to the CN. A standardised protocol will be implemented across that interface to allow handover decisions by the URAN in HO B2 cases. 5.7.3.3 Classification C Classification C concerns the kind of handover performed: 1) intra-cell handover; 2) intra-URAN handover; 3) inter-URAN handover (without change of CN access point); 4) intra-CN handover with same URAN type; 5) intra-CN handover with different URAN type; 6) inter-CN handover with same URAN type and same CN type; 7) inter-CN handover with different URAN type and same CN type; 8) inter-CN handover with same URAN type and different CN type; 9) inter-CN handover with different URAN type and different CN type; 10)inter-CN handover without change of URAN. The type of URAN type should be relatively transparent to the Iu interface. Regarding handovers across multiple CN, it is proposed that this is supported (and this is already possible with GSM). C1 to C7 scenarios shall be supported by the service primitives of the Iu interface. NOTE: FFS: scenarios C8 to C10 shall be supported by the service primitives of the Iu interface. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 12 Release 1999 5.7.3.4 Classification D Regarding how a handover is performed, there is the possibility to either have the notion of anchor point, or not to have it. Example is circuit switched GSM, using anchor points, and GPRS, not using that notion. Furthermore, the notion of anchor point may be handled differently for the signalling plane and the transmission plane. The notion of anchor point shall be supported by the service primitives of the Iu interface. NOTE 1: FFS: the notion of transmission plane anchor point is supported by the service primitives of the Iu interface. NOTE 2: FFS: the notion of signalling plane anchor point is supported by the service primitives of the Iu interface. NOTE 3: FFS: the anchor points for the signalling plane and transmission plane need not necessarily be the same or even exist simultaneously. The flexibility should be left in UMTS by the Iu service principles. 5.8 Macrodiversity (if needed, dependent of the choice of multiple access technology) Not all IWF/CNs will support macrodiversity. Macrodiversity may be supported in the AS, dependent on the choice of multiple access technology. 5.9 Encryption The NAS may support encryption to protect the transmitted data. The AS needs to support encryption to prevent from eavesdropping at the radio interface. 5.10 Authentication of Subscriber Subscriber data is stored in the NAS and therefore authentication should be considered a NAS functionality. NAS data is not stored in the URAN, and subscriber authentication can therefore not be a URAN functionality. 5.11 (Non source dependent coding) Compression NAS may support compression. The AS should support compression to optimise usage of radio resources. 5.12 Source (e.g. voice or video) Coding Source coding is different dependent on IWF/CN and is therefore a NAS functionality. 5.13 Radio Channel Coding Radio Channel coding is needed due to the radio interface and could therefore be considered a radio functionality. Radio Channel coding is not a NAS functionality. Radio Channel coding is supported by URAN. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 13 Release 1999 5.14 UE Location Identification The UE location identification may be supported by the UE and/or the access network side of the AS; i.e., URAN; e.g., as defined in the GSM LCS (Location Services) specifications or by some other means. The UE location identification is provided to identify the likely location of specific UEs. This is meant to be used for charging, location-based services, lawful interception, emergency calls, etc., as well as the positioning services. When location identification is supported by URAN, the following apply: 1) URAN obtains ‘Area ID’ and/or geographic co-ordinates with uncertainty parameters for identification of the likely location of UE, to be sent to the NAS entity side of the CN (i.e., edge node) ‘Area ID’ represents either a radio access cell/sector or a geographic area. ‘Area ID’ is coded in the same format as Cell Global Identification (CGI), for compatibility to GSM. 2) Location information is categorised to two levels of accuracy. The Basic Level of information is what URAN obtains without extra signalling with the UE. The advanced level is obtained through extra signalling for positioning. Both levels can be used for both, Positioning services and other applications. 3) Location information is always at least obtained from URAN by the appropriate edge node(s) at the activation of a Call/PDP Context. Mechanism to make it possible to obtain the location information at the release of a Call/PDP Context should be specified. Location information sent to the edge node at other occasions is on the basis of asynchronous requests from the edge node to URAN. An edge node can request URAN to send the location information with the two types of requests, Type 1 (Direct request) where URAN sends location information only once at the request and Type 2 (Event request) where URAN sends location information at each specified event (e.g. Cell Update) requested by the edge node. 5.15 Charging The functions related to charging are not part of the AS. These functions are mainly: - charging information generation; - charging processing. 6 Access Stratum services The modelling of the services follow the basic principles as set by ITU-T Recommendation X.210 [4]. In this recommendation the following figure is given as an example for peer-to-peer connection-mode services. TISO2530-94/d03 Service User A Service User B OSI-Service-Provider Request (requestor.submit) Confirm (requestor.deliver) Indication (acceptor.deliver) Response (acceptor.submit) Figure 1: Example of a peer-to-peer connection-mode service [4] For connectionless-mode services the basic primitives are "request" and "indication". 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 14 Release 1999 6.1 Service Access Points (SAPs) The SAPs offered by the Access Stratum (AS) to the rest of the system (Non Access Stratum: NAS) are reflected in the following figure. UE-Uu CN-Iu NAS NAS IF-Uu RAN-Iu Edge node RAN UE Infrastructure Side User Equipment Side AS AS RNC Functions GC GC GC Nt GC GC GC Nt Nt Nt Nt Nt DC DC DC DC DC DC Uu Svcs: e.g., RRC Iu Svcs: e.g., RANAP : SAPs Figure 2: Service Access Points (SAPs) offered by the Access Stratum (AS) For the time being, the SAPs offered be the AS are symmetric, i.e. the same SAPs are offered on the infrastructure side (CN-AS) and on the user equipment side (UE-AS). These SAPs are: GC: General Control (see 6.1.1 for a general presentation and 6.2.2.1 for a detailed information). Nt: Notification (see 6.1.2 for a general presentation and 6.2.2.2 for a detailed information). DC: Dedicated Control (see 6.1.3 for a general presentation and 6.2.2.3 for a detailed information). Note: Broadcast and Multicast services can not be described using the services and functions defined so far in the present document. The nature of Broadcast and Multicast services, like Cell Broadcast Service (CBS), is very different from other specified services. The following model characteristics are missing to fulfil the CBS requirements, namely: 1. CBS uses two segments with different QoS requirements to deliver CB messages to the UE: 1a. From Cell Broadcast Center (CBC) to RNC, a SAP is required where for instance, 1 second turnaround time, interactive class, with a reliable transport is required. 1b. From RNC to UE, a SAP is required where for instance, a maximum delay of 10 seconds and a background class is required. 2. Because of (item 1), the service primitives used by each of the segments may also be different; i.e., the related SAPs to those primitives may differ in the two segments and a combination of GC, Nt, and DC SAPs requires study. 3. CBS traffic is asymmetric in nature. The communication flow is only in one direction from the CBC to the UE . There is no uplink channel needed and the UE can not initiate a communication or request specific information. At least two changes are envisaged and thus detailed contributions are expected: i. Introduce a new SAP type. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 15 Release 1999 ii. Mapping example between the two communication segments. Figure 2 shows also, as an example, some details of the AS architecture. The details are out of the scope of this document and are further specified in the 25-series. This model does not exclude, nor imply, which protocol is specified between the UE-AS entity and the CN-AS entity. These protocols are ‘transparent’ for the AN, but participate in the service provided by the AS. 6.1.1 General Control SAPs These SAPs are used to enable the Core Network to provide information and to give commands that do not relate to specific users or specific [sessions] (group calls, conference). There is typically one General Control SAP per AN/CN connection point. On the UE side, a possible model is to consider that there is a single General Control SAP in an MS. 6.1.2 Notification SAPs These SAPs are used to broadcast data to identified Users. The typical use is for initiating paging in the AN. There is typically one Notification SAP per AN/CN connection point. On the UE side, a possible model is to consider that there is a single Notification SAP (a Paging SAP) in an MS. 6.1.3 Dedicated Control SAPs These SAPs are used to establish, release connections with specific User Equipment, and to exchange information related to these connections. A connection is a relationship between temporary contexts respectively in the AN and in the CN. The context in the AN is initiated at the establishment of the connection, and erased when the connection is released. Several types of connections are identified, such as point connection (single user) and group connections. There are typically a great number of Dedicated Control SAPs per AN/CN connection point. SAPs are identified by a SAPI at the AS boundary. During the lifetime of a connection, the connection can be identified unambiguously by the SAPI of the associated SAP, and the SAPI is used as a reference in the exchanges at the AS boundary on the infrastructure side. A SAPI is used as a connection identifier allocated unambiguously to each connection during its lifetime, and used in the exchanges at the AS boundary on the infrastructure side. On the UE side, a possible modelling is to consider that there is a single dedicated control SAP in an MS. NOTE 1: On the UE side, an open issue is whether simultaneous services from distinct ANs can be provided to an MS. Settling this issue may lead to a different model, for instance with the possibility to have several Dedicated Control SAPs, one per AN with which an active context exists. Another issue, visible when analysing Point-to-Multipoint services in GSM, is the SAP modelling for those PTM services. NOTE 2: The model is limited in this version to the cases where all the activity between a User Equipment and the infrastructure pertains to the same subscriber. Extension to cases with several subscriber sharing a User Equipment requires further study. 6.2 Operations 6.2.1 General The operations are described both for the AS boundary on the Infrastructure side and on the User Equipment side. The description of the operations on the Infrastructure side is given with sufficient details to develop on this basis a concrete control protocol at the AN/CN inter-connection. The description of the operations on the User Equipment side may be used [to be discussed] for developing a concrete API, allowing an open modular design of the User Equipment software. The operations are described in three sections, one for operations that involve both the IF side and the UE side, one for operations local to the IF and finally one for operations local to the UE side. In each sections, operations are sorted per SAP category. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 16 Release 1999 Request and confirm primitives are always toward the Access Stratum. Indication and response primitives are always from the Access Stratum. 6.2.2 Common operations 6.2.2.1 General Control SAP 6.2.2.1.1 Information broadcast This operation consists in the broadcast from IF toward User Equipment of some information in some geographical area. This information is to be used by the User Equipment for instance to choose among access points or to be taken into account during initial access. The information can also be destinated to an application. NOTE: This concerns only information to be broadcasted on behalf of Non Access Strata. Other information may be broadcasted for the internal use of the Access Stratum. 6.2.2.1.1.1 Information broadcast request, IF side The parameters are: Category enumerated (access point selection, initial access, application) Geographical area geographical area Information to broadcast bit string The size of the information to broadcast is not bound by this description, but may be constrained by the access system. The geographical area is used by the AN to determine which access points are concerned. The rules are not specified in the external specification of the AS, but must exist and must be consistent with other translations between geographical descriptions and access points (e.g., in the connection establishment). The category is used by the AN to determine priority and more generally the parameters governing information repetition over time. NOTE: The category field could be enhanced, e.g., to allow a more precise control of priorities and repetitions. 6.2.2.1.1.2 Information Broadcast Indication, UE Side The parameters are: Access point reference local Broadcast information bit string The access point reference identifies the point on the access boundary (e.g., the cell) where the information was received. NOTE: The access point reference is a local reference, to be used in other primitives at the AS/NAS boundary in the same UE. 6.2.2.2 Notification SAPs Notification operations consists of sending information to a dedicated user/terminal, or a group of users/terminals over a defined geographic area. Typically the request is forwarded to the user/terminal on a broadcast resource. If the AN knows of an existing signalling relation to the user/terminal, the information might be sent through the existing relation, according to Access Stratum specifications. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 17 Release 1999 6.2.2.2.1 Paging Request, IF side The parameters are the following: User/Terminal Identity pageable identity Geographical area where to broadcast geographical area Paging resource parameters paging resource parameters Information to send bit string The user/terminal identity is provided to determine if a signalling relation with the user/terminal exists. The geographical area indicates the area in which the Core Network knows the User/Terminal(s) to be. The size of the information to send is not bound by this description, but may be constrained by the access system. The paging resource parameters are used to determine which paging resource to be used when several are available. The organisation of paging resources is known in advance by the User Equipment, and are used by the User Equipment to choose the paging resources to listen to. The exact use of the paging resource parameters is specified as part of Access Stratum specifications. NOTE: This function is typically used for paging, i.e., to trigger an access from the User/Terminal. However, this is not relevant to the Access Stratum, and other uses can be envisaged without impacting the Access Stratum. The action required from the MS, if any, is indicated, implicitly or explicitly, in the information to send, the content of which being part of the Non Access Strata specifications and not of the Access Stratum specifications. 6.2.2.2.2 Notification Broadcast Request, IF side The parameters are the following: Geographical area where to broadcast geographical area Notification resource parameters paging resource parameters Information to broadcast bit string The size of the information to broadcast is not bound by this description, but may be constrained by the access system. The paging resource parameters are used to determine which paging resource to be used when several are available. The organisation of paging resources is known in advance by the User Equipment, and are used by the User Equipment to choose the paging resources to listen to. The exact use of the paging resource parameters is specified as part of Access Stratum specifications. NOTE: This operation is used typically to inform all MSes of some starting or on-going activities, such as group calls. 6.2.2.2.3 Notification Indication, UE side Parameters Access point reference local Broadcast information bit string NOTE: This primitive applies both for a paging sent on broadcast resources and for the reception of an information broadcast to many users. 6.2.2.3 Dedicated Control SAPs Dedicated Control operations are done within the scope of a connection, embodied by corresponding SAPs on the UE and IF sides. This scope is determined by local references (respectively on the UE side and on the IF side). All operations contain such a local reference, and, at a given AN/CN interconnection point, all operations with the same local reference from the establishment event to the release event pertain to the same connection. The correspondence 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 18 Release 1999 between Dedicated Control SAPs on the UE and IF side is dynamic, and established through the connection establishment operations. The local connection references have only a local scope, and their values do not necessarily have any predictable relationship with the corresponding reference local to the other side, or with a reference used over some interface to multiplex the messages pertaining to the connection with messages pertaining to other connections. 6.2.2.3.1 UE Side Initiated Connection Establishment This operation consists in the establishment of a new connection at the initiative of NAS on the User Equipment side. 6.2.2.3.1.1 UE Side Initiated Connection Establishment Request, UE side Parameters Local connection reference local Routing parameters routing parameters Initial message bit string The routing parameters are to be used by the AS on the Infrastructure side to choose the AN/CN connection point through which the connection is to be established. The initial message is to be forwarded to the non-access strata. The size of the initial message should not be constrained by the access system. 6.2.2.3.1.2 UE Side Initiated Connection Establishment Indication, IF side Parameters Local connection reference local Initial message bit string Localisation data localisation data The localisation data indicate the knowledge the AN has of the localisation of the initiating User Equipment. It includes typically a geographical area and some accuracy indication. 6.2.2.3.1.3 UE Side Initiated Connection Establishment Confirm, IF Side Parameters Local connection reference local Status enumerated (terminated by NAS, going on) Initial answer bit string The NAS can choose not to pursue the connection (status = terminated by NAS). Reasons can be that the information provided by the User Equipment did not require more than a single message answer (e.g., store-and-forward service), or some exception conditions prevented the CN to pursue the connection. The initial answer is to be provided to the requesting part in the non-access strata. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 19 Release 1999 6.2.2.3.1.4 UE Side Initiated Connection Establishment Response, UE side Parameters Local connection reference local Status enumerated (terminated by NAS, terminated by AS, going on) Initial answer bit string The initial answer is not provided in the case the status is 'terminated by AS'. The status 'going on' and 'terminated by NAS' indicates that the initial message was delivered to the NAS; on the other hand, the status 'terminated by AS' can happen whether or not the initial message was delivered to the NAS. 6.2.2.3.2 Connection Release This operation is the termination of a connection, at the request of non-access strata on the Infrastructure side. The use of this operation may lead to the non-completion of other previously started operations in the same connection (e.g., transparent data transfer). 6.2.2.3.2.1 IF Initiated Connection Release Request, IF Side Parameter Local connection reference local 6.2.2.3.2.2 IF Initiated Connection Release Indication UE side Parameter Local connection reference local 6.2.2.3.3 Information Transfer These operations allow the transfer of messages between Non-Access Strata elements on each side of the access interface. The service is essentially that of a transport layer, with multiplexing, and possibly guarantee of order and correct transmission (transmission difficulties lead to connection loss), including the effect of user movements. The operation caters only for transmission from AS boundary to access boundary. Upper layers of protocol are typically added for addressing and routing beyond this boundary. Several independent streams can exist simultaneously on the same connection, as distinguished by a routing and transaction identifiers. Message order is guaranteed, if applicable, on a stream basis. Routing identifiers are typically used to indicate originator and destination (e.g., USIM to Home, ME to Serving, and also distinctions such as GSM between MM and CC for instance...). Transaction identifiers are used to distinguish streams with the same originator and destination. Messages can be sent within a transaction or not. Transactions are explicitly set up and released, either in-band (i.e., together with information transfer) or out-band. Transaction identifiers have only a local significance. NOTE 1: There is a difficulty behind the message order. In some cases it may be important to keep message order in a combination of streams, e.g., within a route, or even involving two routes. The model presented so far is too simple to cope with such cases. A quality of service indication is present in sending requests. This covers such aspects as message order, effect on other on-going traffic (e.g., speech pre-emption), delay. A finite number of quality of service classes will be identified, and the one to apply to a message indicated. With each transaction is associated a default quality of service, established at transaction establishment or by a subsequent modification request. A transmission mode indication is present in reception indications. This gives information from the Access Stratum on the aspects of the transmission related to service quality of service (e.g., speech has been pre-empted). 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 20 Release 1999 NOTE 2: This covers circuit data transport, including cases where each message is very small (down to 1 bit or other information quantum). Obviously, in such cases these primitives are a model not to be followed in implementations. 6.2.2.3.3.1 Data Transfer Request, IF Side Parameters Local connection reference local Route route Transaction identification local Transaction management enumerated (single, first, subsequent, last) Quality of Service indication QoS Message bit string The transaction management field indicates if the message is independent from transactions (single), is the first of the transaction and hence initialises the transaction (first), is the last of the transaction and hence releases the transaction (last), or is in the middle of a transaction. The primitive can be used with an empty message for transaction management alone (value 'single' is then meaningless). 6.2.2.3.3.2 Data Transfer Indication, UE Side Parameters Local connection reference local Route route Transaction identification local Transaction management enumerated (single, first, subsequent, last) Transmission mode indication transmission mode Message bit string 6.2.2.3.3.3 Data Transfer Request, UE Side Parameters Local connection reference local Route route Transaction identification local Transaction management enumerated (single, first, subsequent, last) Quality of Service indication QoS Message bit string 6.2.2.3.3.4 Data Transfer Indication, IF Side Parameters Local connection reference local Route route Transaction identification local Transaction management enumerated (single, first, subsequent, last) Transmission mode indication transmission mode Message bit string 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 21 Release 1999 6.2.2.3.4 IF Side Initiated Radio Access Bearer Establishment These operations allow the transfer of control messages for radio access bearer establishment between non-access strata elements on each side of the access interface. The operations pertain to the connection identified by the local connection reference parameter. The operations allow the IF side to initialise a radio access bearer. The operation also implies a request to the AS to allocate transmission resources to the radio access bearer. A radio access bearer identification uniquely identifies the radio access bearer. It is used in all primitives that pertain to the radio access bearer. It also serves as the binding to a NAS call. The Iu bearer identification identifies the Iu connection. A quality of service request specifies the bearer characteristics that apply to the radio access bearer. 6.2.2.3.4.1 IF Side Initiated Radio Access Bearer Establishment Request, IF Side Parameters Local connection reference local Radio access bearer identification bit string Iu bearer identification bit string Quality of Service request QoS 6.2.2.3.4.2 IF Side Initiated Radio Access Bearer Establishment Indication, UE Side Parameters Local connection reference local Radio access bearer identification bit string Iu bearer identification bit string 6.2.2.3.4.3 IF Side Initiated Radio Access Bearer Establishment Response, UE Side Parameters Local connection reference local Radio access bearer identification bit string Status enumerated (terminated by NAS, going on) 6.2.2.3.4.4 IF Side Initiated Radio Access Bearer Establishment Confirm, IF Side Parameters Local connection reference local Radio access bearer identification bit string Status enumerated (terminated by NAS, terminated by AS, going on) 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 22 Release 1999 6.2.2.3.5 IF Side Initiated Radio Access Bearer Release These operations allow the transfer of radio access bearer release messages between non-access strata elements on each side of the access interface. The operations pertain to the connection identified by the local connection reference parameter. The operations allow IF side to release a radio access bearer. NOTE: A radio access bearer release procedure is normally initiated by the IF side. Abnormal cases such as termination by the AS are FFS. 6.2.2.3.5.1 IF Side Initiated Radio Access Bearer Release Request, IF Side Parameters Local connection reference local Radio access bearer identification bit string 6.2.2.3.5.2 IF Side Initiated Radio Access Bearer Release Indication, UE Side Parameters Local connection reference local Radio access bearer identification bit string 6.2.3 IF side only operations 6.2.3.1 Dedicated control SAPs 6.2.3.1.1 Position update indication Parameters Local connection reference local Position position 6.2.3.1.2 Connection loss indication Parameters Local connection reference local 6.2.3.1.3 Streamlining required indication This operation is used by the AS to indicate that the connection runs the risk to be aborted unless a streamlining is done. Parameters Local connection reference local Proposed list of alternative AN/CN points AN/CN point list 6.2.3.1.4 Branch establishment request This operation establishes a new branch supporting dedicated mode transport for a given UE. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 23 Release 1999 Parameters Local connection reference local Transaction list transaction list The transaction list describes the transactions for which the establishment prior the first transmission of data is required. 6.2.3.1.5 Branch establishment confirm This indicates that the branch is successfully established up to the UE and can then be used for transmission. As a result, the NAS may decide to remove the old branch. Parameters Local connection reference local 6.2.3.1.6 UE location information request This operation is sent from the NAS entity inside the CN (i.e. edge node) to the access network side of AS (i.e. URAN) to request the location information of a specific UE. Parameters: Local connection reference local Level of accuracy basic level or advanced level Type of request direct request or event request Event conditions to send information The level of accuracy describes the granularity required on the UE location information, either basic or advanced. The type of request describes whether the request is to get the current UE location or to get the location when some conditions specified by event are satisfied. 6.2.3.1.7 UE location information confirm This operation is sent in response to the UE location information request operation. Parameters: Local connection reference local Area ID UE location information in terms of CGI format Geographic coordinates UE location information in terms of coordinates Event conditions met The Area ID is to be formatted in accordance with the CGI (Cell Global Identity). The geographic co-ordinates represents the physical co-ordinates on the earth and uncertainty parameters. [To be completed] 6.2.4 UE side only operations 6.2.4.1 Dedicated control SAPs 6.2.4.1.1 Connection loss indication Parameters 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 24 Release 1999 Local connection reference local [To be completed] 6.3 Parameters structure 6.3.1 Local The structure is not relevant in the scope of this document, and can be decided on an implementation basis. 6.3.2 Bit string A finite ordered sequence of bit values. 6.3.3 Enumerated The parameter can take one value out of a list explicitly given. 6.3.4 Geographical description TBI 6.3.5 QoS This section describes the radio access bearer (RAB) by referencinga list of attributes related to the QoS. The radio access bearers are divided into two categories: - Restricted radio access bearers; - Unrestricted radio access bearers. An unrestricted radio access bearer is meant for data requiring bit sequence integrity (;e.g., N-ISDN data transport), whereas a restricted radio access bearer contains a description of the nature of the information (;e.g., encoded voice). For a restricted radio access bearer, the characteristics are implicitly given. The characterisation of a radio access bearer is made by using a set of attributes. A radio access bearer attribute is a specific characteristic that distinguishes it from other radio access bearer services. Refer to ref. [5] for a list of these QoS attributes. Particular values are also indicated in that specification for different services. In order to describe the desired radio access bearer service, QoS attributes are defined at the SAP. Note that it is not necessary, nor meaningful to support all possible combinations of parameter settings. NOTE: In case of an unrestricted radio access bearer, for every SDU provided at the SAP, bit sequence integrity should be maintained. 6.3.6 Route TBI 6.3.7 Transaction identifier Local. 6.3.8 Transaction list A list of transactions, each described by a transaction identifier (local) and by QoS parameters. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 25 Release 1999 6.3.9 Transmission mode TBI 6.3.10 AN/CN Point List TBI TBI 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 26 Release 1999 Annex A (informative): Change history Document history 23.110 3.0.0 Approved at SMG#28. Document for Transfer to TSG-SA Document history 0.0.0 04.04.97 Initial Draft; preliminarily indicated as 23.yy 0.1.0 19.05.97 Second Draft; major improvements in clause 4.2 0.1.1 12.06.97 Revised version according to - decisions during the meeting 20-22.05.97, Sophia Antipolis - ETSI drafting rules, renamed as "23.10" 0.2.0 07.07.97 Revised version according to decisions during the meeting 30.06.-04.07.97, Sophia Antipolis. Major improvements in clause 5. 0.2.1 28.08.97 Revised version according to decisions during the meeting 30.06.-04.07.97, Sophia Antipolis. Some changes in clause 5. 0.3.0 22.09.97 Renumbered due to ETSI Drafting Rules, no changes since 0.2.1 0.3.1 12.11.97 Some editorial changes, in particular adding notes to invite contributions in order to align "older parts" of the document and "scope" 0.4.0 08.01.98 Revised version according to decisions during the meeting 17.-21.11.97, Kista: - adoption of document incl. title to the scope - improvements in clauses 4, 4.3.6 and 5.2.2.2. 0.5.0 23.01.98 Revised version according to decisions during the meeting 19.-21.01.98, Malmö: - figure 1 in clause 5.1 added 0.6.0 1998-04 Revised version according to decisions during the meeting 23.-27.03.98, Bad Aibling: - chapter 4 restructured (=> new chapter 5) - table on functions in-/outside Access stratum revised - some improvements in new chapter 5.6 0.6.1 1998-06 No changes since 0.6.0 but deletion of revision marks and reformatting to paper size "LETTER" instead of "A4" 0.7.0 1998-08 Revisions as agreed on TD 98s357 in June meeting (Chicago). NOTE: Other agreed revisions could not be inserted as the relevant documents were not electronically available (TDocs 466, 467, 469, 476) 0.7.1 1998-08 Editorial changes: - Some information from X.210 added. - some further textual alignment to the current state of 23.01 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 27 Release 1999 0.8.0 1998-08 Revisions as agreed in August meeting (Sophia Antipolis). NOTE: Revisions according to TDocs 466, 467, 469, 476 are integrated also. 0.8.1 1998-09 Editorial alignment due to rapporteur´s notes on revisions as provided by TD 98s654 and additional text alignment. 1.0.0 1998-09 Version 1.0.0 for presentation for information to SMG#27 1.0.1 draft 1998-11 Editorial updates from ver. 0.8.0 to ver. 0.8.1, and text alignments. Addition of primitives, sections 6.2.2.3.4 and 6.2.2.3.5, for Control messages (Dedicated Control SAP) - RAB control procedures, Tdoc 98S720 (Rome). 1.0.1 1998-12 Addition of editorial comments from November (Castle Combe) meeting. 1.1.0 1999-01 Replacement of previous Section 5.14, Terminal Positioning, by new Section: UE Location Identification. With two enumerated bullet items, as agreed in the San Francisco meeting. 1.2.0 1999-02 Addition of third enumerated item into section 5.14. In same section, an editor´s note was inserted, regarding the need of primitives and operations, when the location services item is finalized. Title of section 5.4, replaced from ‘MS Tracking’ to ‘Location Management’. In Table 1, replacement of ‘UE positioning’ to ‘UE location identification’ and ‘UE Tracking’ to ‘UE location management’. Remove superfluous editor`s notes throughout the specification. 2.0.0 1999-02 Update in revision numbering for presentation to SMG#28 and provision to 3GPP for their baseline documentation. 3.0.0 1999-02 Approved at SMG#28. Document for Transfer to TSG-SA 3.1.0 1999-03 Addition of background information on UE location identification to section 5.14. Addition of primitives related to UE location information, sections 6.2.3.1.6-7: UE location information request and confirm, respectively. Both updates approved in S2#3, Nynaeshamn. Update related to transcoder location at the core network and source depending coding belonging to the non-access stratum. Updates agreed in Ad hoc in February in Paris and approved in S2#3. Table 1, editorial section 5.12, section 6.3.5, QoS, and Table A.1 - speech codec in access stratum. 3.2.0 1999-11 Inclusion of CR 002 (editorial) and CR003 (removal of the QoS parameters) as agreed by TSG SA#5. 3.3.0 2000-01 Inclusion of CR004 (note on CBS functions) and introduction of the figure in CR 003 (removal of the QoS parameters) not introduced by error in v.3.2.0, as approved by TSG SA#6. 3.4.0 2000-04 Inclusion of CR005 to clarify that the RAB identity can be used to by NAS elements to bind a RAB to the NAS API or corresponding. 3G TS 23.110 version 3.4.0 Release 1999 28 ETSI ETSI TS 123 110 V3.4.0 (2000-03) 3G TS 23.110 version 3.4.0 Release 1999 History Document history V3.4.0 March 2000 Publication |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 1 Scope | ........................................................................................................................................................5 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 1.1 Scope of the Technical Specification | ................................................................................................................. 5 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 1.2 Application to the interface structures | ............................................................................................................... 5 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 1.3 Structure of layer 3 procedures | .......................................................................................................................... 5 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 1.4 Test procedures | .................................................................................................................................................. 5 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 1.5 Use of logical channels | ...................................................................................................................................... 6 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 1.6 Overview of control procedures | ......................................................................................................................... 6 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 1.6.1 List of procedures | ......................................................................................................................................... 6 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 1.7 Applicability of implementations | ...................................................................................................................... 8 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 1.7.1 Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS) | .................................................... 8 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 1.7.2 General Packet Radio Service (GPRS) | ......................................................................................................... 8 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 2 References | ................................................................................................................................................9 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 2.1 Definitions and abbreviations | .......................................................................................................................... 12 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 2.1.1 Random values | ........................................................................................................................................... 12 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 2.2.2 Vocabulary | ................................................................................................................................................. 12 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 3 Radio Resource management procedures | ..............................................................................................13 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 4 Elementary procedures for Mobility Management | ................................................................................13 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 5 Elementary procedures for circuit-switched Call Control | .....................................................................13 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 6 Support for packet services | ....................................................................................................................13 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7 Examples of structured procedures | ........................................................................................................13 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.1 General | ............................................................................................................................................................. 13 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.1.1 Paging request | ............................................................................................................................................ 14 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.1.2 Immediate assignment | ................................................................................................................................ 14 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.1.3 Service request and contention resolution | .................................................................................................. 14 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.1.4 Authentication | ............................................................................................................................................ 15 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.1.5 Ciphering mode setting | .............................................................................................................................. 15 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.1.6 Transaction phase | ....................................................................................................................................... 15 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.1.6.1 Channel mode modify | .......................................................................................................................... 15 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.1.7 Channel release | .......................................................................................................................................... 16 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.2 Abnormal cases | ................................................................................................................................................ 16 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.3 Selected examples | ............................................................................................................................................ 16 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.3.1 Location updating | ....................................................................................................................................... 17 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.3.2 Mobile originating call establishment | ........................................................................................................ 18 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.3.3 Mobile terminating call establishment | ....................................................................................................... 21 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.3.4 Call clearing | ............................................................................................................................................... 23 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.3.5 DTMF protocol control | .............................................................................................................................. 25 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.3.6 Handover | .................................................................................................................................................... 25 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.3.7 In-call modification | .................................................................................................................................... 27 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.3.8 Call re-establishment | .................................................................................................................................. 27 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 7.3.9 Network initiated mobile originating call $(CCBS)$ | ................................................................................. 28 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 8 Handling of unknown, unforeseen, and erroneous protocol data | ..........................................................32 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 9 Message functional definitions and contents | .........................................................................................33 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 10 General message format and information elements coding | ...................................................................33 |
68bc2b39288c8c858c2e033e2c457f4f | 123 108 | 11 List of system parameters | ......................................................................................................................33 Annex A (informative): Change Record ..............................................................................................34 ETSI ETSI TS 123 108 V3.2.0 (2000-03) 4 3G TS 23.108 version 3.2.0 Release 1999 Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The present document specifies the procedures used at the radio interface core network protocols within the 3rd generation mobile telecommunications system and 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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater 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 document. Introduction The present document includes references to features which are not part of the Phase 2+ Release 96 of the GSM Technical specifications. All subclauses which were changed as a result of these features contain a marker (see table below) relevant to the particular feature. ETSI ETSI TS 123 108 V3.2.0 (2000-03) 5 3G TS 23.108 version 3.2.0 Release 1999 1 Scope The present document specifies the procedures used at the radio interface (Reference Point Um, see GSM 04.02) for Call Control (CC), Mobility Management (MM), and Session Management (SM). When the notations for "further study" or "FS" or "FFS" are present in the present document they mean that the indicated text is not a normative portion of this standard. These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in GSM 04.03. The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in TS 24.007. 1.1 Scope of the Technical Specification The procedures currently described in the present document are for the call control of circuit-switched connections, session management for GPRS services, mobility management and radio resource management for circuit-switched and GPRS services. TS 24.010 contains functional procedures for support of supplementary services. GSM 04.11 contains functional procedures for support of point-to-point short message services. GSM 04.12 contains functional description of short message - cell broadcast. GSM 04.60 contains procedures for radio link control and medium access control (RLC/MAC) of packet data physical channels. GSM 04.18 contains the procedures for the RR protocol. TS 24.008 contains the procedures for the CN protocols. TS 24.071 contains functional descriptions and procedures for support of location services. NOTE: "layer 3" includes the functions and protocols described in this Technical Specification. The terms "data link layer" and "layer 2" are used interchangeably to refer to the layer immediately below layer 3. 1.2 Application to the interface structures The layer 3 procedures apply to the interface structures defined in GSM 04.03. They use the functions and services provided by layer 2 defined in GSM 04.05 and GSM 04.06. TS 24.007 gives the general description of layer 3 including procedures, messages format and error handling. 1.3 Structure of layer 3 procedures A building block method is used to describe the layer 3 procedures. The basic building blocks are "elementary procedures" provided by the protocol control entities of the three sublayers, i.e. radio resource management, mobility management and connection management sublayer. Complete layer 3 transactions consist of specific sequences of elementary procedures. The term "structured procedure" is used for these sequences. 1.4 Test procedures Test procedures of the GSM radio interface signalling are described in GSM 11.10 and GSM 11.2x series. ETSI ETSI TS 123 108 V3.2.0 (2000-03) 6 3G TS 23.108 version 3.2.0 Release 1999 1.5 Use of logical channels The logical control channels are defined in GSM 05.02. In the following those control channels are considered which carry signalling information or specific types of user packet information: i) Broadcast Control CHannel (BCCH): downlink only, used to broadcast Cell specific information; ii) Synchronization CHannel (SCH): downlink only, used to broadcast synchronization and BSS identification information; iii) Paging CHannel (PCH): downlink only, used to send page requests to Mobile Stations (MSs); iv) Random Access CHannel (RACH): uplink only, used to request a Dedicated Control CHannel; v) Access Grant CHannel (AGCH): downlink only, used to allocate a Dedicated Control CHannel; vi) Standalone Dedicated Control CHannel (SDCCH): bi-directional; vii)Fast Associated Control CHannel (FACCH): bi-directional, associated with a Traffic CHannel; viii)Slow Associated Control CHannel (SACCH): bi-directional, associated with a SDCCH or a Traffic CHannel; ix) Cell Broadcast CHannel (CBCH): downlink only used for general (not point to point) short message information. x) Notification CHannel (NCH): downlink only, used to notify mobile stations of VBS (Voice Broadcast Service) calls or VGCS (Voice Group Call Service) calls. Two service access points are defined on signalling layer 2 which are discriminated by their Service Access Point Identifiers (SAPI) (see GSM 04.06): i) SAPI 0: supports the transfer of signalling information including user-user information; ii) SAPI 3: supports the transfer of user short messages. Layer 3 selects the service access point, the logical control channel and the mode of operation of layer 2 (acknowledged, unacknowledged or random access, see GSM 04.05 and GSM 04.06) as required for each individual message. 1.6 Overview of control procedures 1.6.1 List of procedures The following procedures are specified in the Technical Specification: a) Clause 4 specifies elementary procedures for Mobility Management: - mobility management common procedures (subclause 4.3); - TMSI reallocation procedure (subclause 4.3.1); - authentication procedure (subclause 4.3.2); - identification procedure (subclause 4.3.3); - IMSI detach procedure (subclause 4.3.4); - abort procedure (subclause 4.3.5); - MM information procedure (subclause 4.3.6); - mobility management specific procedures (subclause 4.4); - location updating procedure (subclause 4.4.1); - periodic updating (subclause 4.4.2); ETSI ETSI TS 123 108 V3.2.0 (2000-03) 7 3G TS 23.108 version 3.2.0 Release 1999 - IMSI attach procedure (subclause 4.4.3); - generic location updating procedure (subclause 4.4); - connection management sublayer service provision; - mobility management connection establishment (subclause 4.5.1); - mobility management connection information transfer phase (subclause 4.5.2); - mobility management connection release (subclause 4.5.3); - GPRS specific mobility management procedures (subclause 4.7); - GPRS attach procedure (subclause 4.7.3); - GPRS detach procedure (subclause 4.7.4); - GPRS routing area updating procedure (subclause 4.7.5); - GPRS common mobility management procedures (subclause 4.7); - GPRS P-TMSI reallocation procedure (subclause 4.7.6); - GPRS authentication and ciphering procedure (subclause 4.7.7); - GPRS identification procedure (subclause 4.7.8); - GPRS information procedure (subclause 4.7.12); b) Clause 5 specifies elementary procedures for circuit switched Call Control comprising the following elementary procedures: - mobile originating call establishment (subclause 5.2.1); - mobile terminating call establishment (subclause 5.2.2); - signalling procedures during the active state (subclause 5.3); - user notification procedure (subclause 5.3.1); - call rearrangements (subclause 5.3.2); - DTMF protocol control procedure (subclause 5.5.7); - in-call modification (subclause 5.3.4); - call clearing initiated by the mobile station (subclause 5.4.3); - call clearing initiated by the network (subclause 5.4.4); - miscellaneous procedures; - in-band tones and announcements (subclause 5.5.1); - status enquiry procedure (subclause 5.5.3); - call re-establishment procedure (subclause 5.5.4); d) Clause 6 specifies elementary procedures for session management: - GPRS session management procedures (subclause 6.1); - PDP context activation (subclause 6.1.1); - PDP context modification (subclause 6.1.2); - PDP context deactivation (subclause 6.1.3); - anonymous PDP context activation (subclause 6.1.4); ETSI ETSI TS 123 108 V3.2.0 (2000-03) 8 3G TS 23.108 version 3.2.0 Release 1999 - anonymous PDP context deactivation (subclause 6.1.5). The elementary procedures can be combined to form structured procedures. Examples of such structured procedures are given in clause 7. This part of the Technical Specification is only provided for guidance to assist implementations. Clause 8 specifies actions to be taken on various error conditions and also provides rules to ensure compatibility with future enhancements of the protocol. 1.7 Applicability of implementations The applicability of procedures of this technical specification for the mobile station is dependent on the services and functions which are to be supported by a mobile station. 1.7.1 Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS) For mobile stations supporting the Voice Group Call Service or the Voice Broadcast Service, it is explicitly mentioned throughout this technical specification if a certain procedure is applicable only for such a service and, if necessary, how mobile stations not supporting such a service shall behave. For VGCS and VBS, the following possible mobile station implementations exist: - support of listening to voice broadcast calls (VBS listening); - support of originating a voice broadcast call (VBS originating); - support of listening to voice group calls (VGCS listening); - support of talking in voice group calls (VGCS talking. This always includes the implementation for VGCS listening); - support of originating a voice group call (VGCS originating. This always includes the implementation for VGCS talking). Apart from the explicitly mentioned combinations, all possible combinations are optional and supported by this technical specification. The related terms are used in this technical specification, if information on these implementation options is required. 1.7.2 General Packet Radio Service (GPRS) For mobile stations supporting the General Packet Radio Service (GPRS), it is explicitly mentioned throughout the technical specification if a certain procedure is applicable only for such a service and, if necessary, how mobile stations not supporting such a service shall behave. A GPRS MS may operate in one of the following MS operation modes, see 03.60 [74]: - MS operation mode A; - MS operation mode B; or - MS operation mode C. The MS operation mode depends on the services that the MS is attached to, i.e., only GPRS or both GPRS and non- GPRS services, and upon the MS's capabilities to operate GPRS and other GSM services simultaneously. Mobile stations that are capable to operate GPRS services are referred to as GPRS MSs. NOTE: Other GSM technical specifications may refer to the MS operation modes A, B, and C as GPRS class-A MS, GPRS class-B MS, and GPRS class-C MS. It should be noted that it is possible that for a GPRS MS, the GMM procedures currently described in the ETS do not support combinations of VGCS, VBS and GPRS. The possible interactions are not studied yet. ETSI ETSI TS 123 108 V3.2.0 (2000-03) 9 3G TS 23.108 version 3.2.0 Release 1999 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. [1] GSM 01.02: "Digital cellular telecommunications system (Phase 2+); General description of a GSM Public Land Mobile Network (PLMN)". [2] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [3] TS 22.002: "Digital cellular telecommunications system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)". [4] GSM 02.03: "Digital cellular telecommunications system (Phase 2+); Teleservices supported by a GSM Public Land Mobile Network (PLMN)". [5] GSM 02.09: "Digital cellular telecommunications system (Phase 2+); Security aspects". [6] TS 22.011: "Digital cellular telecommunications system (Phase 2+); Service accessibility". [7] GSM 02.17: "Digital cellular telecommunications system (Phase 2+); Subscriber identity modules Functional characteristics". [8] GSM 02.40: "Digital cellular telecommunications system (Phase 2+); Procedures for call progress indications". [9] GSM 03.01: "Digital cellular telecommunications system (Phase 2+); Network functions". [10] TS 23.003: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification". [11] GSM 03.13: "Digital cellular telecommunications system (Phase 2+); Discontinuous Reception (DRX) in the GSM system". [12] TS 23.014: "Digital cellular telecommunications system (Phase 2+); Support of Dual Tone Multi- Frequency signalling (DTMF) via the GSM system". [12a] TS 23.071: "Digital cellular telecommunications system (Phase 2+); Location Services; Functional description – Stage 2". [13] GSM 03.20: "Digital cellular telecommunications system (Phase 2+); Security related network functions". [14] TS 23.022: "Digital cellular telecommunications system (Phase 2+); Functions related to Mobile Station (MS) in idle mode". [15] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [16] GSM 04.03: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface Channel structures and access capabilities". [17] GSM 04.04: "Digital cellular telecommunications system (Phase 2+); layer 1 General requirements". [18] GSM 04.05: "Digital cellular telecommunications system (Phase 2+); Data Link (DL) layer General aspects". ETSI ETSI TS 123 108 V3.2.0 (2000-03) 10 3G TS 23.108 version 3.2.0 Release 1999 [19] GSM 04.06: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification". [20] TS 24.007: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3 General aspects". [21] TS 24.010: "Digital cellular telecommunications system ; Mobile radio interface layer 3 Supplementary services specification General aspects". [22] GSM 04.11: "Digital cellular telecommunications system (Phase 2); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". [23] GSM 04.12: "Digital cellular telecommunications system (Phase 2+); Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". [23a] TS 24.071: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 location services specification". [23b] GSM 04.31 "Digital cellular telecommunication system (Phse 2+);Location Services;Mobile Station (MS) - Serving Mobile Location Centre (SMLC); Radio Resource LCS Protocol (RRLP)". [24] TS 24.080: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification Formats and coding". [25] TS 24.081: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 3". [26] TS 24.082: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 3". [27] TS 24.083: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". [28] TS 24.084: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 3". [29] TS 24.085: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 3". [30] TS 24.086: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 3". [31] GSM 04.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 3". [32] GSM 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path". [33] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception". [34] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control". [35] GSM 05.10: "Digital cellular telecommunications system (Phase 2+); Radio subsystem synchronization". [36] TS 27.001: "Digital cellular telecommunications system (Phase 2+); General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". [37] TS 29.002: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". [38] TS 29.007: "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)". ETSI ETSI TS 123 108 V3.2.0 (2000-03) 11 3G TS 23.108 version 3.2.0 Release 1999 [39] GSM 11.10: "Digital cellular telecommunications system (Phase 2+); Mobile Station (MS) conformity specification". [40] GSM 11.21: "Digital cellular telecommunications system (Phase 2); The GSM Base Station System (BSS) equipment specification". [41] ISO/IEC 646 (1991): "Information technology - ISO 7-bit coded character set for information interchange". [42] ISO/IEC 6429: "Information technology - Control functions for coded character sets". [43] ISO 8348 (1987): "Information processing systems - Data communications - Network service definition". [44] CCITT Recommendation E.163: "Numbering plan for the international telephone service". [45] CCITT Recommendation E.164: "Numbering plan for the ISDN era". [46] CCITT Recommendation E.212: "Identification plan for land mobile stations". [47] ITU-T Recommendation F.69 (1993): "Plan for telex destination codes". [48] CCITT Recommendation I.330: "ISDN numbering and addressing principles". [49] CCITT Recommendation I.440 (1989): "ISDN user-network interface data link layer - General aspects". [50] CCITT Recommendation I.450 (1989): "ISDN user-network interface layer 3 General aspects". [51] ITU-T Recommendation I.500 (1993): "General structure of the ISDN interworking recommendations". [52] CCITT Recommendation T.50: "International Alphabet No. 5". [53] CCITT Recommendation Q.931: ISDN user-network interface layer 3 specification for basic control". [54] CCITT Recommendation V.21: "300 bits per second duplex modem standardized for use in the general switched telephone network". [55] CCITT Recommendation V.22: "1200 bits per second duplex modem standardized for use in the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". [56] CCITT Recommendation V.22bis: "2400 bits per second duplex modem using the frequency division technique standardized for use on the general switched telephone network and on point- to-point 2-wire leased telephone-type circuits". [57] CCITT Recommendation V.23: "600/1200-baud modem standardized for use in the general switched telephone network". [58] CCITT Recommendation V.26ter: "2400 bits per second duplex modem using the echo cancellation technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". [59] CCITT Recommendation V.32: "A family of 2-wire, duplex modems operating at data signalling rates of up to 9600 bit/s for use on the general switched telephone network and on leased telephone-type circuits". [60] CCITT Recommendation V.110: "Support of data terminal equipments (DTEs) with V-Series interfaces by an integrated services digital network". [61] CCITT Recommendation V.120: "Support by an ISDN of data terminal equipment with V-Series type interfaces with provision for statistical multiplexing". [62] CCITT Recommendation X.21: "Interface between data terminal equipment (DTE) and data circuit-terminating equipment (DCE) for synchronous operation on public data networks". ETSI ETSI TS 123 108 V3.2.0 (2000-03) 12 3G TS 23.108 version 3.2.0 Release 1999 [63] 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". [64] CCITT Recommendation X.28: "DTE/DCE interface for a start-stop mode data terminal equipment accessing the packet assembly/disassembly facility (PAD) in a public data network situated in the same country". [65] CCITT Recommendation X.30: "Support of X.21, X.21 bis and X.20 bis based data terminal equipments (DTEs) by an integrated services digital network (ISDN)". [66] CCITT Recommendation X.31: "Support of packet mode terminal equipment by an ISDN". [67] 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 public data network through a public switched telephone network or an integrated services digital network or a circuit switched public data network". [68] CCITT Recommendation X.75 (1988): "Packet-switched signalling system between public networks providing data transmission services". [69] CCITT Recommendation X.121: "International numbering plan for public data networks". [70] ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-network interface layer 3 Specifications for basic call control". [71] ETS 300 102-2: "Integrated Services Digital Network (ISDN); User-network interface layer 3 Specifications for basic call control". [72] ISO/IEC 10646: "Universal Multiple-Octet Coded Character Set (UCS)"; UCS2, 16 bit coding. [73] TS 22.060: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service Description; Stage 1". [74] TS 23.060: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service Description; Stage 2". [75] GSM 03.64: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Overall description of the GPRS radio interface; Stage 2". [76] GSM 04.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Mobile Station - Base Station System (MS-BSS) interface; Radio Link Control and Medium Access Control (RLC/MAC) layer specification". [77] IETF RFC 1034: "Domain names - Concepts and Facilities " (STD 7). [78] GSM 04.65: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Subnetwork Dependent Convergence Protocol (SNDCP)". [79] TS 23.135: "Multicall supplementary service - Stage 2". 2.1 Definitions and abbreviations Abbreviations used in this specification are listed in GSM 01.04 2.1.1 Random values For the RR protocol see GSM 04.18 and for the CN protocols see TS 24.008. 2.2.2 Vocabulary For the RR protocol see GSM 04.18 and for the CN protocols see TS 24.008. ETSI ETSI TS 123 108 V3.2.0 (2000-03) 13 3G TS 23.108 version 3.2.0 Release 1999 3 Radio Resource management procedures See GSM 04.18 4 Elementary procedures for Mobility Management See TS 24.008. 5 Elementary procedures for circuit-switched Call Control See TS 24.008. 6 Support for packet services See TS 24.008. 7 Examples of structured procedures Clause 7 is informative. 7.1 General Clause 7 contains examples of how the network may group together the elementary procedures (i.e. the procedures defined in clauses 3 to 5) in order to provide normal service. The layer 3 signalling at the radio interface may be divided into so-called structured procedures which consist of specific combinations of elementary procedures. In subclause 7.3, selected examples of structured procedures are described. A structured procedure consists of (not necessarily all) components shown in figure 7.1. These components are characterized by the purpose of their use in structured procedures and their message flow in the following subclauses 7.1.1 to 7.1.7. +- -+ G 3DJLQJ UHTXHVW G 55 FRQQHFWLRQ G ,PPHGLDWH DVVLJQPHQW G HVWDEOLVKPHQW +- -+ +- -+ G 6HUYLFH UHTXHVW DQG G G &RQWHQWLRQ UHVROXWLRQ G +- -+ +- -+ G $XWKHQWLFDWLRQ G +- -+ +- -+ G &LSKHULQJ PRGH VHWWLQJ G +- -+ +- -+ G 7UDQVDFWLRQ SKDVH G +- -+ +- -+ G &KDQQHO UHOHDVH G 55 FRQQHFWLRQ +- -+ release Figure 7.1/GSM 04.08: Components of structured procedures ETSI ETSI TS 123 108 V3.2.0 (2000-03) 14 3G TS 23.108 version 3.2.0 Release 1999 7.1.1 Paging request The paging procedure is used to locate a mobile station to which a connection shall be established. Upon receipt of a PAGING REQUEST message the addressed mobile station initiates the immediate assignment procedure. Mobile Station Network PAGING REQUEST <------------------- Figure 7.2/GSM 04.08: Paging request 7.1.2 Immediate assignment The immediate assignment procedure is always initiated by the mobile station. It may be triggered by a paging request or by a mobile originating service request. The mobile station sends a CHANNEL REQUEST message on the Random Access Channel. The network responds with an IMMEDIATE ASSIGNMENT message which causes the mobile station to seize the indicated dedicated channel. Mobile Station Network CHANNEL REQUEST -------------------------> IMMEDIATE ASSIGNMENT <------------------------ Figure 7.3/GSM 04.08: Immediate assignment 7.1.3 Service request and contention resolution The initial service request message (a PAGING RESPONSE, LOCATION UPDATING REQUEST, IMSI DETACH, CM SERVICE REQUEST, or CM RE-ESTABLISHMENT REQUEST message) is sent by the mobile station to the network piggy-backed in the L2 SABM frames establishing the main signalling link. Its purpose is: - to provide non-confidential information relevant to the service requested for the RR and MM sublayer in the network; - in particular to identify the user in the network without jeopardising the confidentiality of the user's identity; this is achieved by using as mobile identity the TMSI, which was never before transmitted un-encrypted over the radio interface; - to allow for contention resolution; - optionally, in the CM SERVICE REQUEST message to inform the network of the priority level associated with the call. Contention resolution provides a resolution process when more than one MS try to seize a channel allocated during the immediate assignment procedure (because they happened to use the same random reference at the same time during random access). This is achieved by the network including in a L2 UA frame the same information field as that one received in the L2 SABM frame to which the UA frame responds. By comparing the two information fields the MS can verify whether it was the originator of the L2 establishment, because the service request contains the mobile identity. Mobile Station Network SABM(service request) -------------------------> UA(service request) <------------------------ Figure 7.4/GSM 04.08: Service request and contention resolution ETSI ETSI TS 123 108 V3.2.0 (2000-03) 15 3G TS 23.108 version 3.2.0 Release 1999 7.1.4 Authentication The purpose of authentication is to validate the identity provided by the mobile station . It is initiated by the network. The authentication procedure also provides the mobile station with information from which a new ciphering key can be derived. The network decides whether or not to use authentication. This may depend on the context. Mobile Station Network AUTHentication REQuest <-------------------------- AUTHentication RESponse ---------------------------> Figure 7.5/GSM 04.08: Authentication 7.1.5 Ciphering mode setting Ciphering mode setting is initiated by the network. Its purpose is to instruct the mobile station whether or not to use ciphering and which algorithm to use. Where ciphering is used, this procedure synchronizes the start of ciphering at the mobile station and in the network. Mobile Station Network CIPHer MODE CoMmanD <---------------------- CIPHer MODe COMplete -----------------------> Figure 7.6/GSM 04.08: Ciphering mode setting 7.1.6 Transaction phase A variety of elementary procedures described in clauses 3 to 5 may be performed during the transaction phase. In this subclause, only the channel mode modify procedure is characterized. 7.1.6.1 Channel mode modify The channel mode modify procedure may be used when a traffic channel has been assigned e.g.: - during the in-call modification procedure in order that the channel mode of the TCH be changed to that one requested by call control; - during call establishment with very early assignment in order that the channel mode of the TCH be changed from signalling only to the mode requested by call control; - during the active phase of a data call in order that the speed of the data transmission be changed. The channel mode modify procedure is initiated by the network sending a CHANNEL MODE MODIFY message and completed by the mobile station changing the mode of the TCH and sending back a CHANNEL MODE MODIFY ACKNOWLEDGE message. Mobile Station Network CHANNEL MODE MODIFY <----------------------------------- CHANNEL MODE MODIFY ACKNOWLEDGE ------------------------------------> Figure 7.7/GSM 04.08: Channel mode change ETSI ETSI TS 123 108 V3.2.0 (2000-03) 16 3G TS 23.108 version 3.2.0 Release 1999 7.1.7 Channel release Once the transaction phase has been completed, the channel is released by the channel release procedure. The data link layer is released explicitly as described in GSM 04.06. After the channel release is completed, the radio resources which were in use may be reallocated by the network. Mobile Station Network CHANNEL RELEASE <---------------------- Figure 7.8/GSM 04.08 Channel release 7.2 Abnormal cases Abnormal cases are not described in the examples of clause 7. They may arise from: a) failure at a lower layer (e.g. loss of radio connection); b) failure of an elementary procedure; c) errors in an elementary procedure. 7.3 Selected examples The following examples are considered: - location updating; - mobile originating call establishment; a) without OACSU (early assignment); b) with OACSU; c) with very early assignment; - mobile terminating call establishment; a) without OACSU (early assignment); b) with OACSU; - call clearing: a) network initiated; b) mobile initiated; - DTMF protocol control. - handover: a) between finely synchronized cells; b) between non-synchronized cells; c) handover failure, where reconnection of the old channel is possible; - in-call modification; - call re-establishment; - network initiated MO call, e.g. CCBS Recall $(CCBS)$: a) assignment before A party alerting; ETSI ETSI TS 123 108 V3.2.0 (2000-03) 17 3G TS 23.108 version 3.2.0 Release 1999 b) assignment before B party alerting; c) assignment after A and B party alerting. 7.3.1 Location updating The location updating procedure is always initiated by the mobile station e.g. when it finds itself in a different location area from the one in which it was registered before. The cases where the procedure is triggered are described in clause 4. The procedure is shown in figure 7.9/GSM 04.08. The network may decide whether to allocate a new TMSI during location updating, and this option is reflected in this example. The mobile station initiates immediate assignment, service request using the LOCATION UPDATING REQUEST message, and contention resolution. The network requires authentication (this again is an option). As the network intends to allocate a new TMSI, it should activate ciphering. The network includes the new TMSI in the LOCATION UPDATING ACCEPT message (it could also use the explicit TMSI reallocation procedure, see clause 4). The mobile station sends a TMSI REALLOCATION COMPLETE message to the network to acknowledge the receipt of the new TMSI. Upon receipt of the TMSI REALLOCATION COMPLETE message the network initiates the channel release if no further transactions are scheduled. Mobile Station Network +- -+ G &+$11(/ 5(48(67 G 55 FRQQHFWLRQ G ! G HVWDEOLVKPHQW G G 02 G G G ,00(',$7( $66,*10(17 G G G +- -+ +- -+ G G G /2&$7,21 83'$7,1* 5(48(67 G G ! G 6HUYLFH UHTXHVW G G G G G G G G +- -+ +- -+ G $87+(17,&$7,21 5(48(67 G G G $XWKHQWLFDWLRQ G G G $87+(17,&$7,21 5(63216( G G ! G +- -+ +- -+ G G G &,3+(5 02'( &200$1' G G G &LSKHULQJ PRGH G G VHWWLQJ G &,3+(5 02'( &203/(7( G G !G +- -+ +- -+ G /2&$7,21 83'$7,1* $&&(37 G G G G G G 706, 5($//2&$7,21 &203/(7( G G ! G +- -+ +- -+ G &+$11(/ 5(/($6( G 55 FRQQHFWLRQ G G UHOHDVH G G +- -+ Figure 7.9/GSM 04.08: Location updating: successful case ETSI ETSI TS 123 108 V3.2.0 (2000-03) 18 3G TS 23.108 version 3.2.0 Release 1999 7.3.2 Mobile originating call establishment The mobile station initiates immediate assignment, service request using the CM SERVICE REQUEST message, and contention resolution. The network may initiate authentication and may start the ciphering mode setting. After sending the CIPHERING MODE COMPLETE message, the mobile station initiates call establishment by sending the SETUP message to the network. The network answers with a CALL PROCEEDING message. a) Non-OACSU option (early assignment): With this option the network allocates a traffic channel to the mobile station before it initiates call establishment in the fixed network. If call queuing is applied, it may cause variable delay in the traffic channel assignment. When user alerting has been initiated at the called side, an ALERTING message is sent to the mobile station. The network may optionally instruct the MS to attach the user connection at this stage of the call, by means of the progress indicator information element set to the value #1 or #8(if the ringing tone will be sent by the remote end) in the ALERTING message. In that case, an alerting ringing tone has to be generated by the network. NOTE: The speech codec is transparent for supervisory tones. A CONNECT message and its acknowledgement CONNECT ACKNOWLEDGE complete the call establishment when the called party has answered. The mobile originating call setup with early assignment is shown in figure 7.10a/GSM 04.08. b) OACSU option (late assignment): The network determines when the traffic channel is to be assigned. The assignment may be performed at any time after call establishment has been initiated in the fixed network. In the following the case is considered where the network will only allocate a traffic channel after the called party has answered the call (late assignment). As in a) an ALERTING message is sent to the mobile station when user alerting has been initiated at the called side. If the ringing tone is needed, it has to be generated locally at the mobile station as no traffic channel is allocated. When the called party has answered, the network will initiate the channel assignment procedure in order to allocate a traffic channel to the mobile station. If call queuing is applied, it may cause variable delay in the traffic channel assignment. Once the channel assignment has been completed the network will send a CONNECT message to the mobile station. The MS attaches then the user connection. The CONNECT ACKNOWLEDGE message will complete the call setup. The mobile originating call setup with late assignment is shown in figure 7.10b/GSM 04.08. c) Very early assignment: The network assigns the traffic channel at the earliest possible moment, i.e. in the immediate assignment procedure. The mode of the traffic channel is changed from signalling only to the mode necessary for the call by means of the channel mode change procedure. An appropriate moment for that change is after the network has sent the CALL PROCEEDING message, when the call is established towards the called user. With this option, call queuing is never applied. The further establishment of the call is as in a). The mobile originating call setup with very early assignment is shown in figure 7.10c/GSM 04.08. ETSI ETSI TS 123 108 V3.2.0 (2000-03) 19 3G TS 23.108 version 3.2.0 Release 1999 ß Mobile Station Network +- -+ G &+$11(/ 5(48(67 G 55 FRQQHFWLRQ G ! G HVWDEOLVKPHQW G ,00(',$7( $66,*10(17 G 02 G G +- -+ +- -+ G &0 6(59,&( 5(48(67 G G ! G 6HUYLFH UHTXHVW G G +- -+ +- -+ G $87+(17,&$7,21 5(48(67 G $XWKHQWLFDWLRQ G G G $87+(17,&$7,21 5(63216( G G ! G +- -+ +- -+ G &,3+(5 02'( &200$1' G G G &LSKHULQJ G &,3+(5 02'( &203/(7( G PRGH VHWWLQJ G ! G +- -+ +- -+ G 6(783 G G ! G &DOO LQLWLDWLRQ G &$// 352&((',1* G G G +- -+ +- -+ G $66,*10(17 &200$1' G G G $VVLJQPHQW RI G $66,*10(17 &203/(7( G D WUDIILF G ! G FKDQQHO +- -+ +- -+ G $/(57,1* G G G 8VHU DOHUWLQJ +- -+ +- -+ G &211(&7 G G G &DOO DFFHSWHG G &211(&7 $&.12:/('*( G G ! G +- -+ Figure 7.10a/GSM 04.08: Mobile originating call establishment without OACSU (early assignment) ETSI ETSI TS 123 108 V3.2.0 (2000-03) 20 3G TS 23.108 version 3.2.0 Release 1999 Mobile Station Network +- -+ G &+$11(/ 5(48(67 G 55 FRQQHFWLRQ G ! G HVWDEOLVKPHQW G ,00(',$7( $66,*10(17 G 02 G G +- -+ +- -+ Service indication G &0 6(59,&( 5(48(67 G G ! G G G G G +- -+ +- -+ G $87+(17,&$7,21 5(48(67 G $XWKHQWLFDWLRQ G G G $87+(17,&$7,21 5(63216( G G ! G +- -+ +- -+ G &,3+(5 02'( &200$1' G G G &LSKHULQJ G &,3+(5 02'( &203/(7( G PRGH VHWWLQJ G ! G +- -+ +- -+ G 6(783 G G ! G &DOO LQLWLDWLRQ G &$// 352&((',1* G G G +- -+ +- -+ G $/(57,1* G G G 8VHU DOHUWLQJ +- -+ +- -+ G $66,*10(17 &200$1' G G G $VVLJQPHQW RI G $66,*10(17 &203/(7( G D WUDIILF G ! G FKDQQHO +- -+ +- -+ G &211(&7 G G G &DOO DFFHSWHG G &211(&7 $&.12:/('*( G G ! G +- -+ Figure 7.10b/GSM 04.08: Mobile originating call establishment with OACSU (late assignment) ETSI ETSI TS 123 108 V3.2.0 (2000-03) 21 3G TS 23.108 version 3.2.0 Release 1999 Mobile Station Network +- -+ G &+$11(/ 5(48(67 G 55 FRQQHFWLRQ G ! G HVWDEOLVKPHQW G ,00(',$7( $66,*10(17 7&+ G 02 G G +- -+ +- -+ G &0 6(59,&( 5(48(67 G G ! G 6HUYLFH UHTXHVW G G +- -+ +- -+ G $87+HQWLFDWLRQ 5(4XHVW G $XWKHQWLFDWLRQ G G G $87+(17,&$7,21 5(63216( G G ! G +- -+ +- -+ G &,3+(5 02'( &200$1' G G G &LSKHULQJ G &,3+HU 02'H &20SOHWH G PRGH VHWWLQJ G ! G +- -+ +- -+ G 6(783 G G ! G &DOO LQLWLDWLRQ G &$// 352&HHGLQJ G G G +- -+ +- -+ G &+$11(/ 02'( 02',)< G G G 7UDQVPLVVLRQ G &+$11(/ 02'( 02',)< $&.12:/('*( G PRGH G ! G FKDQJH +- -+ +- -+ G $/(57,1* G G G 8VHU DOHUWLQJ +- -+ +- -+ G &211HFW G G G &DOO DFFHSWHG G &211HFW $&.QRZOHGJH G G ! G +- -+ Figure 7.10c/GSM 04.08: Mobile originating call establishment with very early assignment 7.3.3 Mobile terminating call establishment Mobile terminating call establishment is initiated by the network sending a PAGING REQUEST message (see figure 7.11a/GSM 04.08). Upon receiving this message the mobile station initiates the immediate assignment procedure and responds to the network by sending the PAGING RESPONSE message within a layer 2 SABM frame. The network returns a layer 2 UA frame containing the same information field as was sent in the SABM frame. Authentication and ciphering are treated by the network in the same way as defined for the mobile originating call establishment (subclause 7.3.2). After ciphering has been started, the network sends a SETUP message to the mobile station. The capability of the mobile station (at that time) to accept the call is confirmed when the mobile station returns a CALL CONFIRMED message to the network. a) Non-OACSU option (early assignment): With this option the network initiates the assignment of a traffic channel upon receiving the CALL CONFIRMED message. The signal IE is not included in the SETUP message, therefore user alerting is initiated only after a traffic channel has been allocated. An ALERTING message will be sent to the network. When the called user answers, the mobile station sends a CONNECT message to the network. Upon receiving the CONNECT message the network completes the through connection of the communication path and sends a CONNECT ACK message to the mobile station. ETSI ETSI TS 123 108 V3.2.0 (2000-03) 22 3G TS 23.108 version 3.2.0 Release 1999 b) OACSU option (late assignment): In that option, the signalling IE is included in the SETUP message. Consequently, user alerting is initiated as soon as the MS has accepted the call. The network determines when the traffic channel is to be assigned. The assignment may be performed at any time after user alerting has been initiated. In the following the case is considered where the network will only allocate a traffic channel to the mobile station after having received the CONNECT message sent from the mobile station (see figure 7.11b). Upon receiving the ASSIGNMENT COMPLETE message from the mobile station, the network completes the through connection of the communication path and sends a CONNECT ACKNOWLEDGE message to the mobile station. Mobile Station Network +- -+ G 3$*,1* 5(48(67 G G G G &+$11(/ 5(48(67 G 55 FRQQHFWLRQ G ! G HVWDEOLVKPHQW G ,00(',$7( $66,*10(17 G 07 G G +- -+ +- -+ G 3$*,1* 5(63216( G G ! G 6HUYLFH UHTXHVW +- -+ +- -+ G $87+(17,&$7,21 5(48(67 G $XWKHQWLFDWLRQ G G G $87+(17,&$7,21 5(63216( G G ! G +- -+ +- -+ G &,3+HU 02'H &200$1' G G G &LSKHULQJ G &,3+(5 02'( &203/(7( G PRGH VHWWLQJ G ! G +- -+ +- -+ G 6(783 G G G &DOO LQLWLDWLRQ G &$// &21),50(' G G ! G +- -+ +- -+ G $66,*10(17 &200$1' G G G $VVLJQPHQW RI G $66,*10(17 &203/(7( G D WUDIILF G ! G FKDQQHO +- -+ +- -+ G $/(57,1* G G ! G 8VHU DOHUWLQJ +- -+ information +- -+ G &211(&7 G G ! G &DOO DFFHSWHG G &211(&7 $&.12:/('*( G G G +- -+ Figure 7.11a/GSM 04.08: Mobile terminating: call establishment without OACSU (early assignment) ETSI ETSI TS 123 108 V3.2.0 (2000-03) 23 3G TS 23.108 version 3.2.0 Release 1999 Mobile Station Network +- -+ G 3$*,1* 5(48(67 G G G G &+$11(/ 5(48(67 G 55 FRQQHFWLRQ G ! G HVWDEOLVKPHQW G ,00(',$7( $66,*10(17 G 07 G G +- -+ +- -+ G 3$*,1* 5(63216( G G ! G 6HUYLFH UHTXHVW +- -+ +- -+ G $87+(17,&$7,21 5(48(67 G $XWKHQWLFDWLRQ G G G $87+(17,&$7,21 5(63216( G G ! G +- -+ +- -+ G &,3+HU 02'H &200$1' G G G &LSKHULQJ G &,3+(5 02'( &203/(7( G PRGH VHWWLQJ G ! G +- -+ +- -+ G 6(783 G G G &DOO LQLWLDWLRQ G &$// &21),50(' G G ! G +- -+ +- -+ G $/(57,1* G G ! G 8VHU DOHUWLQJ +- -+ information +- -+ G &211(&7 G G ! G +- -+ +- -+ G $66,*10(17 &200$1' G G G $VVLJQPHQW RI G $66,*10(17 &203/(7( G D WUDIILF G ! G FKDQQHO +- -+ +- -+ G &211(&7 $&.12:/('*( G G G +- -+ Figure 7.11b/GSM 04.08: Mobile terminating: call establishment with OACSU (late assignment) 7.3.4 Call clearing a) initiated by the network The network initiates the clearing of a call by sending a DISCONNECT message to the mobile station (see also subclause 5.4.4). Upon receiving the DISCONNECT message from the network the mobile station sends a RELEASE message to the network. Upon receiving the RELEASE message from the mobile station, the network sends a RELEASE COMPLETE to the mobile station and, if the traffic channel is longer needed (e.g. last activity on the traffic channel), performs the channel release procedure as described in subclause 7.1.7. Upon receiving the RELEASE COMPLETE message and if the cleared call was the last activity on the traffic channel, the mobile station waits for the release of the channel which is always initiated by the network. When there exist multiple traffic channels in the Multicall environment the network does not release (i.e. retains) a traffic channel even if the cleared call was the last activity on the traffic channel under the condition as follows; ETSI ETSI TS 123 108 V3.2.0 (2000-03) 24 3G TS 23.108 version 3.2.0 Release 1999 - a waiting call exists and the mobile station does not indicates to the network which bearer will be used for accepting the waiting call yet; and - there exists no retained bearer for the waiting call. When the mobile station receives SETUP message with Signal IE indicating Call Waiting, which means the network cannot provide any additional traffic channel, then: - the MS shall not request a new SI value before releasing any other call (that leads to release any other bearers than the retained bearer); - If the mobile station indicates the different SI value from the retained bearer after releasing any other calls (that leads to release any other bearer than the retained bearer), the network allocates a new TCH for the call, and releases the retained bearer. Call clearing initiated by the network is shown in figure 7.12a. b) initiated by the mobile station: The mobile station initiates the clearing of a call by sending a DISCONNECT message to the network (see also subclause 5.4.3). Upon receiving the DISCONNECT message from the mobile station the network sends a RELEASE message to the mobile station. Upon receiving the RELEASE message from the network, the mobile station sends a RELEASE COMPLETE to the network, which, if the traffic channel is no longer needed (e.g. last activity on the traffic channel), performs the channel release procedure as described in subclause 7.1.6. When there exist multiple traffic channels in the Multicall environment the network does not release (i.e. retains) a traffic channel even if the cleared call was the last activity on the traffic channel under the condition as follows: - a waiting call exists and the mobile station does not indicates to the network which bearer will be used for accepting the waiting call yet; and - there exists no retained bearer for the waiting call. When the mobile station receives SETUP message with Signaling IE indicating Call Waiting, which means network cannot provide any additional traffic channel, then: - The MS shall not request a new SI value before releasing any other call (that leads to release any other bearers than the retained bearer); - If the mobile station indicates the different SI value from the retained bearer after releasing any other calls (that leads to release any other bearer than the retained bearer), the network allocates a new TCH for the call, and releases the retained bearer. Call clearing initiated by the mobile station is shown in figure 7.12b. Mobile Station Network +- -+ G ',6&211(&7 G G G &DOO FOHDULQJ G 5(/($6( G G ! G G 5(/($6( &203/(7( G G G +- -+ +- -+ G &+$11(/ 5(/($6( G 55 FRQQHFWLRQ G G UHOHDVH +- -+ a) Call clearing initiated by the network Figure 7.12a/GSM 04.08: Call clearing ETSI ETSI TS 123 108 V3.2.0 (2000-03) 25 3G TS 23.108 version 3.2.0 Release 1999 a) Mobile Station Network +- -+ G ',6&211(&7 G G ! G &DOO FOHDULQJ G 5(/($6( G G G G 5(/($6( &203/(7( G G ! G +- -+ +- -+ G &+$11(/ 5(/($6( G 55 FRQQHFWLRQ G G UHOHDVH +- -+ b) Call clearing initiated by the MS Figure 7.12b/GSM 04.08: Call clearing 7.3.5 DTMF protocol control Figure 7.13 shows the structured procedure for DTMF protocol control. Mobile Station Network +- -+ G G DFWLYH FDOO G G +- -+ . +- -+ G 67$57 '70) G '70) JHQHUDWLRQ G ! G VWDUWHG G 67$57 '70) $&.12:/('*( G G G +- -+ +- -+ G 6723 '70) G '70) JHQHUDWLRQ VWRSSHG G ! G G 6723 '70) $&.12:/('*( G G G +- : -+ : +- -+ G G DFWLYH FDOO G G +- -+ Figure 7.13/GSM 04.08: DTMF protocol control 7.3.6 Handover Figure 7.14 shows the structured procedure for handover to a finely synchronized cell, successful case. Figure 7.15 shows the structured procedure for handover to a non-synchronized cell, successful case. Figure 7.16 shows the structured procedure for handover failure, and reconnection to the old traffic channel. ETSI ETSI TS 123 108 V3.2.0 (2000-03) 26 3G TS 23.108 version 3.2.0 Release 1999 Mobile Station Network +- -+ G G G G 55 FRQQHFWLRQ HVWDEOLVKHG G G +- -+ +- -+ handover G +$1'29(5 &200$1' G ROG FKDQQHO G G ROG FHOO -G G G +$1'29(5 $&&(66 G QHZ FKDQQHO G !G QHZ FHOO G G G +$1'29(5 $&&(66 G G !G G G G +$1'29(5 $&&(66 G G !G G G G +$1'29(5 $&&(66 G G !G G G G +$1'29(5 &203/(7( G G !G +- -+ Figure 7.14/GSM 04.08: Handover to a finely synchronized cell, successful case Mobile Station Network +- -+ G G G G 55 FRQQHFWLRQ HVWDEOLVKHG G G +- -+ +- -+ handover G +$1'29(5 &200$1' G ROG FKDQQHO G G ROG FHOO -G G G +$1'29(5 $&&(66 G QHZ FKDQQHO G !G QHZ FHOO G G G G G G G +$1'29(5 $&&(66 G QHZ FKDQQHO G !G QHZ FHOO G G G 3+<6,&$/ ,1)250$7,21 G G G G +$1'29(5 &203/(7( G G !G +- -+ +- -+ G G G G G G +- -+ Figure 7.15/GSM 04.08: Handover to a non-synchronized cell, successful case ETSI ETSI TS 123 108 V3.2.0 (2000-03) 27 3G TS 23.108 version 3.2.0 Release 1999 Mobile Station Network +- -+ G G G G 55 FRQQHFWLRQ HVWDEOLVKHG G G +- -+ +- -+ handover G +$1'29(5 &200$1' G ROG FKDQQHO G G ROG FHOO -G G G 7 H[SLU\ RU G QHZ FKDQQHO G ORZHU OD\HU IDLOXUH G QHZ FHOO -G G G +$1'29(5 )$,/85( G ROG FKDQQHO G !G ROG FHOO +- -+ +- -+ G G G G G G +- -+ Figure 7.16/GSM 04.08: Handover failure, reconnection to the old traffic channel 7.3.7 In-call modification Figure 7.17/GSM 04.08 shows the structured procedure for in-call modification. Mobile Station Network +- -+ G G DFWLYH FDOO G G +- -+ . +- -+ G 02',)< G G ! G LQFDOO PRGLILFDWLRQ G G HJ IURP VSHHFK G G WR GDWD +- -+ channel G G PRGH PRGLI\ G G +- -+ G G G 02',)< &203/(7( G G G +- -+ +- -+ G G DFWLYH FDOO G G +- -+ Figure 7.17/GSM 04.08: In-call modification 7.3.8 Call re-establishment Figure 7.18/GSM 04.08 shows the structured procedure for call re-establishment. ETSI ETSI TS 123 108 V3.2.0 (2000-03) 28 3G TS 23.108 version 3.2.0 Release 1999 Mobile Station Network +- -+ G G DFWLYH FDOO G G +- -+ -------------------------------------- radio link failure +- -+ G &+$11(/ 5(48(67 G 55 FRQQHFWLRQ G ! G HVWDEOLVKPHQW G ,00(',$7( $66,*10(17 G 02 G G +- -+ +- -+ G &0 5((67$%/,6+0(17 5(48(67 G G ! G 6HUYLFH UHTXHVW +- -+ +- -+ G &,3+HU 02'H &200$1' G G G &LSKHULQJ G &,3+(5 02'( &203/(7( G PRGH VHWWLQJ G ! G +- -+ +- -+ G $66,*10(17 &200$1' G G G DVVLJQPHQW RI G $66,*10(17 &203/(7( G D WUDIILF FKDQQHO G ! G +- -+ +- -+ G G DFWLYH FDOO G G +- -+ Figure 7.18/GSM 04.08: Call re-establishment 7.3.9 Network initiated mobile originating call $(CCBS)$ Network initiated mobile originating call establishment (which is used, for example, for CCBS Service) is initiated by the network sending a PAGING REQUEST message. Upon receiving this message the mobile station initiates the immediate assignment procedure and responds to the network by sending the PAGING RESPONSE message within a layer 2 SABM frame. The network returns a layer 2 UA frame containing the same information field as was sent in the SABM frame. Authentication and ciphering are treated by the network in the same way as defined for the mobile originating call establishment (subclause 7.3.2). After ciphering has been started, the network sends a CM SERVICE PROMPT message, indicating that the CM protocol is to be started, to the mobile station. The basic capability of the mobile station to accept any form of recall service is confirmed when the mobile station returns a START CC message to the network. a) assignment before A party alerting: With this option the network allocates a traffic channel to the mobile station before the mobile station alerts its user. The network responds to the START CC message with a CC-ESTABLISHMENT message. The MS answers with a CC-ESTABLISHMENT CONFIRMED message indicating the wanted channel characteristics. The network then initiates traffic channel assignment. When the traffic channel has been assigned, the network indicates a pending recall by sending a RECALL message. If the calling user accepts the recall, a SETUP message is sent to the network. The network responds with a CALL PROCEEDING message and initiates call establishment in the fixed network. When user alerting has been initiated at the called side, an ALERTING message is sent to the mobile station. The network may optionally instruct the MS to attach the user connection at this stage of the call, by means of the progress indicator information element set to the value #1 or #8(if the ringing tone will be sent by the remote end) in the ALERTING message. In that case, an alerting ringing tone has to be generated by the network. ETSI ETSI TS 123 108 V3.2.0 (2000-03) 29 3G TS 23.108 version 3.2.0 Release 1999 NOTE 1: The speech codec is transparent for supervisory tones. A CONNECT message and its acknowledgement CONNECT ACKNOWLEDGE complete the call establishment when the called party has answered. The network initiated mobile originating call establishment with assignment before A part alerting is shown in figure 7.19/GSM 04.08. b) assignment before B party alerting: With this option the network allocates a traffic channel to the mobile station after the mobile station has alerted its user and after its user has accepted the recall but before the network initiates call establishment in the fixed network. The network responds to the START CC message with a CC-ESTABLISHMENT message. The MS answers with a CC-ESTABLISHMENT CONFIRMED message indicating the wanted channel characteristics. The network indicates a pending recall by sending a RECALL message. If the calling user accepts the recall, a SETUP message is sent to the network. The network responds with a CALL PROCEEDING message and initiates traffic channel assignment. When the traffic channel has been assigned, the network initiates call establishment in the fixed network. When user alerting has been initiated at the called side, an ALERTING message is sent to the mobile station. The network may optionally instruct the MS to attach the user connection at this stage of the call, by means of the progress indicator information element set to the value #1 or #8(if the ringing tone will be sent by the remote end) in the ALERTING message. In that case, an alerting ringing tone has to be generated by the network. NOTE 2: The speech codec is transparent for supervisory tones. A CONNECT message and its acknowledgement CONNECT ACKNOWLEDGE complete the call establishment when the called party has answered. The network initiated mobile originating call establishment with assignment before B party alerting is shown in figure 7.20/GSM 04.08. c) assignment after A and B party alerting With this option, the network determines when the traffic channel is to be assigned. The assignment may be performed at any time after call establishment has been initiated in the fixed network. In the following, the case is considered where the network will only allocate a traffic channel after the called party has answered the call (late assignment). The network responds to the START CC message with a CC-ESTABLISHMENT. The MS answers with a CC- ESTABLISHMENT CONFIRMED message indicating the wanted channel characteristics. The network indicates a pending recall by sending a RECALL message. If the calling user accepts the recall, a SETUP message is sent to the network. The network responds with a CALL PROCEEDING message and initiates call establishment in the fixed network. As in a) and b) an ALERTING message is sent to the mobile station when user alerting has been initiated at the called side. If the ringing tone is needed, it has to be generated locally at the mobile station as no traffic channel is allocated. When the called party has answered, the network will initiate the channel assignment procedure in order to allocate a traffic channel to the mobile station. Once the channel assignment has been completed the network will send a CONNECT message to the mobile station. The MS attaches then the user connection. The CONNECT ACKNOWLEDGE message will complete the call setup. The network initiated mobile originating call establishment with assignment after A and B party alerting is shown in figure 7.21/GSM 04.08. ETSI ETSI TS 123 108 V3.2.0 (2000-03) 30 3G TS 23.108 version 3.2.0 Release 1999 Mobile Station Network +- -+ G 3$*,1* 5(48(67 G G G G &+$11(/ 5(48(67 G 55 FRQQHFWLRQ G ! G HVWDEOLVKPHQW G ,00(',$7( $66,*10(17 G 07 G G +- -+ +- -+ G 3$*,1* 5(63216( G G ! G +- -+ +- -+ G $87+(17,&$7,21 5(48(67 G $XWKHQWLFDWLRQ G G G $87+(17,&$7,21 5(63216( G G ! G +- -+ +- -+ G &,3+HU 02'H &200$1' G G G &LSKHULQJ G &,3+(5 02'( &203/(7( G PRGH VHWWLQJ G ! G +- -+ +- -+ G &0 6(59,&( 352037 G G G 6HUYLFH 5HTXHVW G 67$57 && G G ! G +- -+ +- -+ G &&(67$%/,6+0(17 G G B G 5HFDOO LQLWLDWLRQ G &&(67$%/,6+0(17 &21),50(' G G ! G +- -+ +- -+ G $66,*10(17 &200$1' G G G $VVLJQPHQW RI G $66,*10(17 &203/(7( G D WUDIILF FKDQQHO G ! G +- -+ +- -+ G 5(&$// G G G 8VHU QRWLILHG DERXW UHFDOO G 6(783 G G ! G 5HFDOO DFFHSWHG DQG G &$// 352&((',1* G FDOO LQLWLDWLRQ G G +- -+ +- -+ G $/(57,1* G G G &DOOHG XVHU DOHUWLQJ +- -+ information +- -+ G &211(&7 G G G &DOO DFFHSWHG G &211(&7 $&.12:/('*( G G ! G +- -+ ß Figure 7.19/GSM 04.08: Network initiated mobile originating call establishment with assignment before A party alerting ETSI ETSI TS 123 108 V3.2.0 (2000-03) 31 3G TS 23.108 version 3.2.0 Release 1999 Mobile Station Network +- -+ G 3$*,1* 5(48(67 G G G G &+$11(/ 5(48(67 G 55 FRQQHFWLRQ G ! G HVWDEOLVKPHQW G ,00(',$7( $66,*10(17 G 07 G G +- -+ +- -+ G 3$*,1* 5(63216( G G ! G +- -+ +- -+ G $87+(17,&$7,21 5(48(67 G $XWKHQWLFDWLRQ G G G $87+(17,&$7,21 5(63216( G G ! G +- -+ +- -+ G &,3+HU 02'H &200$1' G G G &LSKHULQJ G &,3+(5 02'( &203/(7( G PRGH VHWWLQJ G ! G +- -+ +- -+ G &0 6(59,&( 352037 G G G 6HUYLFH 5HTXHVW G 67$57 && G G ! G +- -+ +- -+ G &&(67$%/,6+0(17 G G B G 5HFDOO LQLWLDWLRQ G &&(67$%/,6+0(17 &21),50(' G G ! G +- -+ +- -+ G 5(&$// G G G 8VHU QRWLILHG DERXW UHFDOO G 6(783 G G ! G 5HFDOO DFFHSWHG DQG G &$// 352&((',1* G FDOO LQLWLDWLRQ G G +- -+ +- -+ G $66,*10(17 &200$1' G G G $VVLJQPHQW RI G $66,*10(17 &203/(7( G D WUDIILF G ! G FKDQQHO +- -+ +- -+ G $/(57,1* G G G &DOOHG XVHU DOHUWLQJ +- -+ information +- -+ G &211(&7 G G G &DOO DFFHSWHG G &211(&7 $&.12:/('*( G G ! G +- -+ ß ß Figure 7.20/GSM 04.08: Network initiated mobile originating call establishment with assignment before B party alerting ETSI ETSI TS 123 108 V3.2.0 (2000-03) 32 3G TS 23.108 version 3.2.0 Release 1999 Mobile Station Network +- -+ G 3$*,1* 5(48(67 G G G G &+$11(/ 5(48(67 G 55 FRQQHFWLRQ G ! G HVWDEOLVKPHQW G ,00(',$7( $66,*10(17 G 07 G G +- -+ +- -+ G 3$*,1* 5(63216( G G ! G +- -+ +- -+ G $87+(17,&$7,21 5(48(67 G $XWKHQWLFDWLRQ G G G $87+(17,&$7,21 5(63216( G G ! G +- -+ +- -+ G &,3+HU 02'H &200$1' G G G &LSKHULQJ G &,3+(5 02'( &203/(7( G PRGH VHWWLQJ G ! G +- -+ +- -+ G &0 6(59,&( 352037 G G G 6HUYLFH 5HTXHVW G 67$57 && G G ! G +- -+ +- -+ G &&(67$%/,6+0(17 G G B G 5HFDOO LQLWLDWLRQ G &&(67$%/,6+0(17 &21),50(' G G ! _ +- -+ +- -+ G 5(&$// G G G 8VHU QRWLILHG DERXW UHFDOO G 6(783 G G ! G 5HFDOO DFFHSWHG DQG G &$// 352&((',1* G FDOO LQLWLDWLRQ G G +- -+ +- -+ G $/(57,1* G G G &DOOHG XVHU DOHUWLQJ +- -+ information +- -+ G $66,*10(17 &200$1' G G G $VVLJQPHQW RI G $66,*10(17 &203/(7( G D WUDIILF G ! G FKDQQHO +- -+ +- -+ G &211(&7 G G G &DOO DFFHSWHG G &211(&7 $&.12:/('*( G G ! G +- -+ ß Figure 7.21/GSM 04.08: Network initiated mobile originating call establishment with assignment after A and B party alerting 8 Handling of unknown, unforeseen, and erroneous protocol data For the RR protocol see GSM 04.18 and for the CN protocols see TS 24.008. ETSI ETSI TS 123 108 V3.2.0 (2000-03) 33 3G TS 23.108 version 3.2.0 Release 1999 9 Message functional definitions and contents For the RR protocol see GSM 04.18 and for the CN protocols see TS 24.008. 10 General message format and information elements coding For the RR protocol see GSM 04.18 and for the CN protocols see TS 24.008. For the RR protocol see GSM 04.18 and for the CN protocols see TS 24.008. ETSI ETSI TS 123 108 V3.2.0 (2000-03) 34 3G TS 23.108 version 3.2.0 Release 1999 Annex A (informative): Change Record Document history V3.0.0 July 1999 Unpublished. V3.1.0 December 1999 Approved by TSGN#6 V3.2.0 March 2000 Approved by TSGN#7 Based on GSM 04.08 version 7.1.1 and inclusion of CRs Tdoc SPEC CR RE VER SUBJECT CAT NEW P-99-510 24.008 A371 2 7.1.0 BCIE modifications due to EDGE B 8.0.0 P-99-523 24.008 A515 1 7.1.0 Split of 24.008 in RR and CN parts (Clause 7, "L3 F 8.0.0 P-99-388 24.008 A562 7.1.0 CR to 24.008 due to EDGE SMG2 EDGE WS B 8.0.0 P-99-523 24.008 A567 1 7.1.0 Split of 24.008 in RR and CN parts F 8.0.0 P-99-390 24.008 A592 1 7.1.0 GSM 400 and Mobile Station Classmark B 8.0.0 P-99-523 24.008 A611 1 7.1.0 Split of 24.008 in RR and CN parts F 8.0.0 P-99-523 24.008 A613 1 7.1.0 Split of 24.008 in RR and CN parts F 8.0.0 P-99-512 24.008 A621 2 7.1.0 IE Daylight saving time B 8.0.0 P-99-461 24.008 A687 7.1.0 Transfer of the LSA Information to the MS B 8.0.0 3.0.0 Transferred to TSGN / June 1999 Tdoc SPEC CR RE VER SUBJECT CAT NEW NP-99446 23.108 002 3.0.0 mirror R99 LCS CR A 3.1.0 NP-000095 23.108 004 3.1.0 Clarification on timing to release TCH C 3.2.0 ETSI 35 ETSI ETSI TS 123 108 V3.2.0 (2000-03) 3G TS 23.108 version 3.2.0 Release 1999 History Document history V3.2.0 March 2000 Publication |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 1 Scope | ........................................................................................................................................................6 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 2 References | ................................................................................................................................................6 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 3 Definitions and abbreviations | ..................................................................................................................7 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 3.1 Definitions | ......................................................................................................................................................... 7 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 3.2 Abbreviations | ..................................................................................................................................................... 7 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 4 Features needed to support MSP Phase 2 | ................................................................................................7 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 5 Additional Information stored in network entities | ...................................................................................8 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 5.1 Data stored in the HLR | ...................................................................................................................................... 8 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 5.2 Data stored in the VLR | ...................................................................................................................................... 8 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 6 Additional procedures in network entities | ...............................................................................................8 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 6.1 OCB_flag | ........................................................................................................................................................... 8 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 6.2 ODB flags | .......................................................................................................................................................... 9 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 6.3 HOLD_flag | ........................................................................................................................................................ 9 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 6.4 CW_flag | ............................................................................................................................................................. 9 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 6.5 MPTY_flag | ........................................................................................................................................................ 9 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 6.6 ECT_flag | ........................................................................................................................................................... 9 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 6.7 CCBS_flag | ....................................................................................................................................................... 10 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 6.8 CLIR_flag | ........................................................................................................................................................ 10 7 Description of Multiple Subscriber Profile...........................................................................................10 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.1 Overview | .......................................................................................................................................................... 10 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.2 Registration of a Profile | ................................................................................................................................... 10 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.3 Interrogation | .................................................................................................................................................... 12 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.4 Call Handling for an MSP subscriber | .............................................................................................................. 15 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.4.1 Mobile Originating (MO) call handling | ..................................................................................................... 15 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.4.2 Mobile Terminating (MT) call handling | .................................................................................................... 15 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5 Functions and Information Flows | .................................................................................................................... 15 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.1 MO call handling in the gsmSCF | ............................................................................................................... 15 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.1.1 Process MO_MSP_Call_gsmSCF | ........................................................................................................ 15 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.1.2 Procedure Set_Calling_Profile_gsmSCF | .............................................................................................. 15 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.1.3 Procedure Send_FCI_gsmSCF | ............................................................................................................. 15 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.2 MT call handling in the gsmSCF | ............................................................................................................... 22 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.2.1 Process MT_MSP_Call_gsmSCF | ......................................................................................................... 22 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3 SS handling in the gsmSCF | ........................................................................................................................ 27 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.1 Procedure Check_CLIR_gsmSCF | ........................................................................................................ 27 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.2 Procedure Forwarded_MSP_Call_gsmSCF | ......................................................................................... 27 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.3 Procedure Check_CFU_gsmSCF | ......................................................................................................... 27 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.4 Procedure Check_Early_CF_gsmSCF | .................................................................................................. 27 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.5 Procedure Check_Late_CF_gsmSCF | ................................................................................................... 27 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.6 Procedure Check_CFNRy_gsmSCF | ..................................................................................................... 27 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.7 Procedure Check_CFB_gsmSCF | .......................................................................................................... 27 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.8 Procedure Check_CFNRc_gsmSCF | ..................................................................................................... 27 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.9 Procedure Check_CW_gsmSCF | ........................................................................................................... 27 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.10 Procedure Check_HOLD_gsmSCF | ...................................................................................................... 27 |
eab3ca939332f488ce7be5825d2eede5 | 123 097 | 7.5.3.11 Procedure Check_MPTY_gsmSCF | ...................................................................................................... 27 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.